Unnamed: 0,id,type,created_at,repo,repo_url,action,title,labels,body,index,text_combine,label,text,binary_label
756811,26486646570.0,IssuesEvent,2023-01-17 18:36:53,cse110-fall21-group9/Digital-Cookbook-App,https://api.github.com/repos/cse110-fall21-group9/Digital-Cookbook-App,closed,Implement Recipe Search and then Recipe Sort,enhancement frontend high priority wishful,"Start with search by name and sort by date changed/name. Strengthen the date format that is stored in the JSON so that it contains the date AND time, OR one option is saving the time in milliseconds from the [Unix epoch](https://en.wikipedia.org/wiki/Unix_time).",1.0,"Implement Recipe Search and then Recipe Sort - Start with search by name and sort by date changed/name. Strengthen the date format that is stored in the JSON so that it contains the date AND time, OR one option is saving the time in milliseconds from the [Unix epoch](https://en.wikipedia.org/wiki/Unix_time).",0,implement recipe search and then recipe sort   start with search by name and sort by date changed name  strengthen the date format that is stored in the json so that it contains the date and time  or one option is saving the time in milliseconds from the    ,0
113310,17117951111.0,IssuesEvent,2021-07-11 18:53:08,turkdevops/design-language-website,https://api.github.com/repos/turkdevops/design-language-website,opened,"CVE-2021-23382 (Medium) detected in postcss-6.0.23.tgz, postcss-7.0.35.tgz",security vulnerability,"## CVE-2021-23382 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>postcss-6.0.23.tgz</b>, <b>postcss-7.0.35.tgz</b></p></summary>
<p>

<details><summary><b>postcss-6.0.23.tgz</b></p></summary>

<p>Tool for transforming styles with JS plugins</p>
<p>Library home page: <a href=""https://registry.npmjs.org/postcss/-/postcss-6.0.23.tgz"">https://registry.npmjs.org/postcss/-/postcss-6.0.23.tgz</a></p>
<p>Path to dependency file: design-language-website/package.json</p>
<p>Path to vulnerable library: design-language-website/node_modules/postcss</p>
<p>

Dependency Hierarchy:
  - gatsby-2.32.12.tgz (Root Library)
    - css-loader-1.0.1.tgz
      - :x: **postcss-6.0.23.tgz** (Vulnerable Library)
</details>
<details><summary><b>postcss-7.0.35.tgz</b></p></summary>

<p>Tool for transforming styles with JS plugins</p>
<p>Library home page: <a href=""https://registry.npmjs.org/postcss/-/postcss-7.0.35.tgz"">https://registry.npmjs.org/postcss/-/postcss-7.0.35.tgz</a></p>
<p>Path to dependency file: design-language-website/package.json</p>
<p>Path to vulnerable library: design-language-website/node_modules/postcss</p>
<p>

Dependency Hierarchy:
  - gatsby-2.32.12.tgz (Root Library)
    - optimize-css-assets-webpack-plugin-5.0.4.tgz
      - cssnano-4.1.10.tgz
        - :x: **postcss-7.0.35.tgz** (Vulnerable Library)
</details>

<p>Found in HEAD commit: <a href=""https://github.com/turkdevops/design-language-website/commit/187b6c70cc572cc46890f19fe80fcaddc53857c4"">187b6c70cc572cc46890f19fe80fcaddc53857c4</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>  
  
The package postcss before 8.2.13 are vulnerable to Regular Expression Denial of Service (ReDoS) via getAnnotationURL() and loadAnnotation() in lib/previous-map.js. The vulnerable regexes are caused mainly by the sub-pattern \/\*\s* sourceMappingURL=(.*).

<p>Publish Date: 2021-04-26
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23382>CVE-2021-23382</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23382"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23382</a></p>
<p>Release Date: 2021-04-26</p>
<p>Fix Resolution: postcss - 8.2.13</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-23382 (Medium) detected in postcss-6.0.23.tgz, postcss-7.0.35.tgz - ## CVE-2021-23382 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>postcss-6.0.23.tgz</b>, <b>postcss-7.0.35.tgz</b></p></summary>
<p>

<details><summary><b>postcss-6.0.23.tgz</b></p></summary>

<p>Tool for transforming styles with JS plugins</p>
<p>Library home page: <a href=""https://registry.npmjs.org/postcss/-/postcss-6.0.23.tgz"">https://registry.npmjs.org/postcss/-/postcss-6.0.23.tgz</a></p>
<p>Path to dependency file: design-language-website/package.json</p>
<p>Path to vulnerable library: design-language-website/node_modules/postcss</p>
<p>

Dependency Hierarchy:
  - gatsby-2.32.12.tgz (Root Library)
    - css-loader-1.0.1.tgz
      - :x: **postcss-6.0.23.tgz** (Vulnerable Library)
</details>
<details><summary><b>postcss-7.0.35.tgz</b></p></summary>

<p>Tool for transforming styles with JS plugins</p>
<p>Library home page: <a href=""https://registry.npmjs.org/postcss/-/postcss-7.0.35.tgz"">https://registry.npmjs.org/postcss/-/postcss-7.0.35.tgz</a></p>
<p>Path to dependency file: design-language-website/package.json</p>
<p>Path to vulnerable library: design-language-website/node_modules/postcss</p>
<p>

Dependency Hierarchy:
  - gatsby-2.32.12.tgz (Root Library)
    - optimize-css-assets-webpack-plugin-5.0.4.tgz
      - cssnano-4.1.10.tgz
        - :x: **postcss-7.0.35.tgz** (Vulnerable Library)
</details>

<p>Found in HEAD commit: <a href=""https://github.com/turkdevops/design-language-website/commit/187b6c70cc572cc46890f19fe80fcaddc53857c4"">187b6c70cc572cc46890f19fe80fcaddc53857c4</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>  
  
The package postcss before 8.2.13 are vulnerable to Regular Expression Denial of Service (ReDoS) via getAnnotationURL() and loadAnnotation() in lib/previous-map.js. The vulnerable regexes are caused mainly by the sub-pattern \/\*\s* sourceMappingURL=(.*).

<p>Publish Date: 2021-04-26
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23382>CVE-2021-23382</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23382"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23382</a></p>
<p>Release Date: 2021-04-26</p>
<p>Fix Resolution: postcss - 8.2.13</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      medium  detected in postcss       tgz  postcss       tgz      cve       medium severity vulnerability     vulnerable libraries    postcss       tgz    postcss       tgz          postcss       tgz      tool for transforming styles with js plugins   library home page   a href     path to dependency file  design language website package json   path to vulnerable library  design language website node modules postcss     dependency hierarchy      gatsby       tgz  root library        css loader       tgz          x    postcss       tgz    vulnerable library       postcss       tgz      tool for transforming styles with js plugins   library home page   a href     path to dependency file  design language website package json   path to vulnerable library  design language website node modules postcss     dependency hierarchy      gatsby       tgz  root library        optimize css assets webpack plugin       tgz         cssnano       tgz            x    postcss       tgz    vulnerable library      found in head commit   a href     found in base branch   master              vulnerability details         the package postcss before       are vulnerable to regular expression denial of service  redos  via getannotationurl   and loadannotation   in lib previous map js  the vulnerable regexes are caused mainly by the sub pattern      s  sourcemappingurl         publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  low   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  postcss                       step up your open source security game with whitesource    ,0
98417,29832995921.0,IssuesEvent,2023-06-18 13:54:45,abetlen/llama-cpp-python,https://api.github.com/repos/abetlen/llama-cpp-python,closed,Install with CLBlast requires CLBlast libraries,documentation build,"# Expected Behavior

With command ""CMAKE_ARGS=""-DLLAMA_CLBLAST=on"" FORCE_CMAKE=1 pip install llama-cpp-python  --force-reinstall --upgrade --no-cache-dir"", I would expect a llama.cpp build with CLBlast to be installed. Which when a model loaded, I would see BLAS = 1 and my graphic card get used during inference.

# Current Behavior

Llama.cpp shows BLAS = 0, and my GPU doesn't move at all during inference.

# Environment and Context
Linux Mint 21.1 Cinnamon (which is basically Ubuntu)
My GPU: Radeon VII
`$ lscpu`
```
架构：                   x86_64
  CPU 运行模式：         32-bit, 64-bit
  Address sizes:         48 bits physical, 48 bits virtual
  字节序：               Little Endian
CPU:                     12
  在线 CPU 列表：        0-11
厂商 ID：                AuthenticAMD
  型号名称：             AMD Ryzen 5 5500
    CPU 系列：           25
    型号：               80
    每个核的线程数：     2
    每个座的核数：       6
    座：                 1
    步进：               0
    Frequency boost:     enabled
    CPU 最大 MHz：       3600.0000
    CPU 最小 MHz：       1400.0000
    BogoMIPS：           7186.38
    标记：               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mc
                         a cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall n
                         x mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_go
                         od nopl nonstop_tsc cpuid extd_apicid aperfmperf rapl p
                         ni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 x2api
                         c movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_le
                         gacy svm extapic cr8_legacy abm sse4a misalignsse 3dnow
                         prefetch osvw ibs skinit wdt tce topoext perfctr_core p
                         erfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw
                         _pstate ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 
                         avx2 smep bmi2 erms invpcid cqm rdt_a rdseed adx smap c
                         lflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cq
                         m_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero 
                         irperf xsaveerptr rdpru wbnoinvd cppc arat npt lbrv svm
                         _lock nrip_save tsc_scale vmcb_clean flushbyasid decode
                         assists pausefilter pfthreshold avic v_vmsave_vmload vg
                         if v_spec_ctrl umip pku ospke vaes vpclmulqdq rdpid ove
                         rflow_recov succor smca fsrm
Virtualization features: 
  虚拟化：               AMD-V
Caches (sum of all):     
  L1d:                   192 KiB (6 instances)
  L1i:                   192 KiB (6 instances)
  L2:                    3 MiB (6 instances)
  L3:                    16 MiB (1 instance)
NUMA:                    
  NUMA 节点：            1
  NUMA 节点0 CPU：       0-11
Vulnerabilities:         
  Itlb multihit:         Not affected
  L1tf:                  Not affected
  Mds:                   Not affected
  Meltdown:              Not affected
  Mmio stale data:       Not affected
  Retbleed:              Not affected
  Spec store bypass:     Mitigation; Speculative Store Bypass disabled via prctl
                          and seccomp
  Spectre v1:            Mitigation; usercopy/swapgs barriers and __user pointer
                          sanitization
  Spectre v2:            Mitigation; Retpolines, IBPB conditional, IBRS_FW, STIB
                         P always-on, RSB filling, PBRSB-eIBRS Not affected
  Srbds:                 Not affected
  Tsx async abort:       Not affected
```

`$ uname -a`
`Linux fgdfgfthgr-MS-7C95 5.15.0-73-generic #80-Ubuntu SMP Mon May 15 15:18:26 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux`


```
$ python3 --version
Python 3.10.11
$ make --version
GNU Make 4.3
为 x86_64-pc-linux-gnu 编译
Copyright (C) 1988-2020 Free Software Foundation, Inc.
许可证：GPLv3+：GNU 通用公共许可证第 3 版或更新版本<http://gnu.org/licenses/gpl.html>。
本软件是自由软件：您可以自由修改和重新发布它。
在法律允许的范围内没有其他保证。
$ g++ --version
g++ (Ubuntu 11.3.0-1ubuntu1~22.04.1) 11.3.0
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
```
'$ pip list'
```
Package             Version
------------------- ----------------
accelerate          0.20.0.dev0
aiofiles            23.1.0
aiohttp             3.8.4
aiosignal           1.3.1
altair              5.0.1
anyio               3.7.0
async-timeout       4.0.2
attrs               23.1.0
bitsandbytes        0.37.2
certifi             2022.12.7
charset-normalizer  2.1.1
click               8.1.3
cmake               3.25.0
colorama            0.4.6
contourpy           1.0.7
cycler              0.11.0
datasets            2.12.0
dill                0.3.6
einops              0.6.1
exceptiongroup      1.1.1
fastapi             0.95.2
ffmpy               0.3.0
filelock            3.9.0
flexgen             0.1.7
fonttools           4.39.4
frozenlist          1.3.3
fsspec              2023.5.0
gradio              3.31.0
gradio_client       0.2.5
h11                 0.14.0
httpcore            0.17.2
httpx               0.24.1
huggingface-hub     0.14.1
idna                3.4
Jinja2              3.1.2
jsonschema          4.17.3
kiwisolver          1.4.4
linkify-it-py       2.0.2
lit                 15.0.7
llama-cpp-python    0.1.57
Markdown            3.4.3
markdown-it-py      2.2.0
MarkupSafe          2.1.2
matplotlib          3.7.1
mdit-py-plugins     0.3.3
mdurl               0.1.2
mpmath              1.2.1
multidict           6.0.4
multiprocess        0.70.14
networkx            3.0
numpy               1.24.3
orjson              3.8.14
packaging           23.1
pandas              2.0.2
peft                0.4.0.dev0
Pillow              9.5.0
pip                 23.0.1
psutil              5.9.5
PuLP                2.7.0
pyarrow             12.0.0
pydantic            1.10.8
pydub               0.25.1
Pygments            2.15.1
pyparsing           3.0.9
pyrsistent          0.19.3
python-dateutil     2.8.2
python-multipart    0.0.6
pytorch-triton-rocm 2.0.1
pytz                2023.3
PyYAML              6.0
quant-cuda          0.0.0
regex               2023.5.5
requests            2.28.1
responses           0.18.0
safetensors         0.3.1
scipy               1.10.1
semantic-version    2.10.0
sentencepiece       0.1.99
setuptools          67.8.0
six                 1.16.0
sniffio             1.3.0
starlette           0.27.0
sympy               1.11.1
tokenizers          0.13.3
toolz               0.12.0
torch               2.0.1+rocm5.4.2
torchaudio          2.0.2+rocm5.4.2
torchvision         0.15.2+rocm5.4.2
tqdm                4.65.0
transformers        4.30.0.dev0
typing_extensions   4.6.2
tzdata              2023.3
uc-micro-py         1.0.2
urllib3             1.26.13
uvicorn             0.22.0
websockets          11.0.3
wheel               0.38.4
xxhash              3.2.0
yarl                1.9.2
```


# Failure Logs
```
$ CMAKE_ARGS=""-DLLAMA_CLBLAST=on"" FORCE_CMAKE=1 pip install llama-cpp-python  --force-reinstall --upgrade --no-cache-dir
Collecting llama-cpp-python
  Downloading llama_cpp_python-0.1.57.tar.gz (1.4 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.4/1.4 MB 6.6 MB/s eta 0:00:00
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting typing-extensions>=4.5.0
  Downloading typing_extensions-4.6.2-py3-none-any.whl (31 kB)
Collecting numpy>=1.20.0
  Downloading numpy-1.24.3-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (17.3 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 17.3/17.3 MB 8.5 MB/s eta 0:00:00
Building wheels for collected packages: llama-cpp-python
  Building wheel for llama-cpp-python (pyproject.toml) ... done
  Created wheel for llama-cpp-python: filename=llama_cpp_python-0.1.57-cp310-cp310-linux_x86_64.whl size=212476 sha256=9c83c78ef597f128db8bfc5ad6ceac144a5eb63a122952e021c47ca3bbb242dc
  Stored in directory: /tmp/pip-ephem-wheel-cache-6ct6wx1l/wheels/87/9b/55/22559358a9af8074053b6c39406f5c06f0d391c052f77ca0c2
Successfully built llama-cpp-python
Installing collected packages: typing-extensions, numpy, llama-cpp-python
  Attempting uninstall: typing-extensions
    Found existing installation: typing_extensions 4.4.0
    Uninstalling typing_extensions-4.4.0:
      Successfully uninstalled typing_extensions-4.4.0
  Attempting uninstall: numpy
    Found existing installation: numpy 1.24.1
    Uninstalling numpy-1.24.1:
      Successfully uninstalled numpy-1.24.1
Successfully installed llama-cpp-python-0.1.57 numpy-1.24.3 typing-extensions-4.6.2
```
```

INFO:Loading llamacpp_30b...
INFO:llama.cpp weights detected: models/llamacpp_30b/ggml-model-q5_0.bin

INFO:Cache capacity is 0 bytes
llama.cpp: loading model from models/llamacpp_30b/ggml-model-q5_0.bin
llama_model_load_internal: format     = ggjt v2 (pre #1508)
llama_model_load_internal: n_vocab    = 32000
llama_model_load_internal: n_ctx      = 2048
llama_model_load_internal: n_embd     = 6656
llama_model_load_internal: n_mult     = 256
llama_model_load_internal: n_head     = 52
llama_model_load_internal: n_layer    = 60
llama_model_load_internal: n_rot      = 128
llama_model_load_internal: ftype      = 8 (mostly Q5_0)
llama_model_load_internal: n_ff       = 17920
llama_model_load_internal: n_parts    = 1
llama_model_load_internal: model size = 30B
llama_model_load_internal: ggml ctx size =    0.13 MB
llama_model_load_internal: mem required  = 23634.31 MB (+ 3124.00 MB per state)
.
llama_init_from_file: kv self size  = 3120.00 MB
AVX = 1 | AVX2 = 1 | AVX512 = 0 | AVX512_VBMI = 0 | AVX512_VNNI = 0 | FMA = 1 | NEON = 0 | ARM_FMA = 0 | F16C = 1 | FP16_VA = 0 | WASM_SIMD = 0 | BLAS = 0 | SSE3 = 1 | VSX = 0 | 
INFO:Loaded the model in 4.37 seconds.


llama_print_timings:        load time =  1245.53 ms
llama_print_timings:      sample time =    43.12 ms /    19 runs   (    2.27 ms per token)
llama_print_timings: prompt eval time =  1245.47 ms /     3 tokens (  415.16 ms per token)
llama_print_timings:        eval time = 11416.53 ms /    18 runs   (  634.25 ms per token)
llama_print_timings:       total time = 12735.25 ms
Output generated in 13.04 seconds (1.46 tokens/s, 19 tokens, context 3, seed 1337143409)

```",1.0,"Install with CLBlast requires CLBlast libraries - # Expected Behavior

With command ""CMAKE_ARGS=""-DLLAMA_CLBLAST=on"" FORCE_CMAKE=1 pip install llama-cpp-python  --force-reinstall --upgrade --no-cache-dir"", I would expect a llama.cpp build with CLBlast to be installed. Which when a model loaded, I would see BLAS = 1 and my graphic card get used during inference.

# Current Behavior

Llama.cpp shows BLAS = 0, and my GPU doesn't move at all during inference.

# Environment and Context
Linux Mint 21.1 Cinnamon (which is basically Ubuntu)
My GPU: Radeon VII
`$ lscpu`
```
架构：                   x86_64
  CPU 运行模式：         32-bit, 64-bit
  Address sizes:         48 bits physical, 48 bits virtual
  字节序：               Little Endian
CPU:                     12
  在线 CPU 列表：        0-11
厂商 ID：                AuthenticAMD
  型号名称：             AMD Ryzen 5 5500
    CPU 系列：           25
    型号：               80
    每个核的线程数：     2
    每个座的核数：       6
    座：                 1
    步进：               0
    Frequency boost:     enabled
    CPU 最大 MHz：       3600.0000
    CPU 最小 MHz：       1400.0000
    BogoMIPS：           7186.38
    标记：               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mc
                         a cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall n
                         x mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_go
                         od nopl nonstop_tsc cpuid extd_apicid aperfmperf rapl p
                         ni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 x2api
                         c movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_le
                         gacy svm extapic cr8_legacy abm sse4a misalignsse 3dnow
                         prefetch osvw ibs skinit wdt tce topoext perfctr_core p
                         erfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw
                         _pstate ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 
                         avx2 smep bmi2 erms invpcid cqm rdt_a rdseed adx smap c
                         lflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cq
                         m_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero 
                         irperf xsaveerptr rdpru wbnoinvd cppc arat npt lbrv svm
                         _lock nrip_save tsc_scale vmcb_clean flushbyasid decode
                         assists pausefilter pfthreshold avic v_vmsave_vmload vg
                         if v_spec_ctrl umip pku ospke vaes vpclmulqdq rdpid ove
                         rflow_recov succor smca fsrm
Virtualization features: 
  虚拟化：               AMD-V
Caches (sum of all):     
  L1d:                   192 KiB (6 instances)
  L1i:                   192 KiB (6 instances)
  L2:                    3 MiB (6 instances)
  L3:                    16 MiB (1 instance)
NUMA:                    
  NUMA 节点：            1
  NUMA 节点0 CPU：       0-11
Vulnerabilities:         
  Itlb multihit:         Not affected
  L1tf:                  Not affected
  Mds:                   Not affected
  Meltdown:              Not affected
  Mmio stale data:       Not affected
  Retbleed:              Not affected
  Spec store bypass:     Mitigation; Speculative Store Bypass disabled via prctl
                          and seccomp
  Spectre v1:            Mitigation; usercopy/swapgs barriers and __user pointer
                          sanitization
  Spectre v2:            Mitigation; Retpolines, IBPB conditional, IBRS_FW, STIB
                         P always-on, RSB filling, PBRSB-eIBRS Not affected
  Srbds:                 Not affected
  Tsx async abort:       Not affected
```

`$ uname -a`
`Linux fgdfgfthgr-MS-7C95 5.15.0-73-generic #80-Ubuntu SMP Mon May 15 15:18:26 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux`


```
$ python3 --version
Python 3.10.11
$ make --version
GNU Make 4.3
为 x86_64-pc-linux-gnu 编译
Copyright (C) 1988-2020 Free Software Foundation, Inc.
许可证：GPLv3+：GNU 通用公共许可证第 3 版或更新版本<http://gnu.org/licenses/gpl.html>。
本软件是自由软件：您可以自由修改和重新发布它。
在法律允许的范围内没有其他保证。
$ g++ --version
g++ (Ubuntu 11.3.0-1ubuntu1~22.04.1) 11.3.0
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
```
'$ pip list'
```
Package             Version
------------------- ----------------
accelerate          0.20.0.dev0
aiofiles            23.1.0
aiohttp             3.8.4
aiosignal           1.3.1
altair              5.0.1
anyio               3.7.0
async-timeout       4.0.2
attrs               23.1.0
bitsandbytes        0.37.2
certifi             2022.12.7
charset-normalizer  2.1.1
click               8.1.3
cmake               3.25.0
colorama            0.4.6
contourpy           1.0.7
cycler              0.11.0
datasets            2.12.0
dill                0.3.6
einops              0.6.1
exceptiongroup      1.1.1
fastapi             0.95.2
ffmpy               0.3.0
filelock            3.9.0
flexgen             0.1.7
fonttools           4.39.4
frozenlist          1.3.3
fsspec              2023.5.0
gradio              3.31.0
gradio_client       0.2.5
h11                 0.14.0
httpcore            0.17.2
httpx               0.24.1
huggingface-hub     0.14.1
idna                3.4
Jinja2              3.1.2
jsonschema          4.17.3
kiwisolver          1.4.4
linkify-it-py       2.0.2
lit                 15.0.7
llama-cpp-python    0.1.57
Markdown            3.4.3
markdown-it-py      2.2.0
MarkupSafe          2.1.2
matplotlib          3.7.1
mdit-py-plugins     0.3.3
mdurl               0.1.2
mpmath              1.2.1
multidict           6.0.4
multiprocess        0.70.14
networkx            3.0
numpy               1.24.3
orjson              3.8.14
packaging           23.1
pandas              2.0.2
peft                0.4.0.dev0
Pillow              9.5.0
pip                 23.0.1
psutil              5.9.5
PuLP                2.7.0
pyarrow             12.0.0
pydantic            1.10.8
pydub               0.25.1
Pygments            2.15.1
pyparsing           3.0.9
pyrsistent          0.19.3
python-dateutil     2.8.2
python-multipart    0.0.6
pytorch-triton-rocm 2.0.1
pytz                2023.3
PyYAML              6.0
quant-cuda          0.0.0
regex               2023.5.5
requests            2.28.1
responses           0.18.0
safetensors         0.3.1
scipy               1.10.1
semantic-version    2.10.0
sentencepiece       0.1.99
setuptools          67.8.0
six                 1.16.0
sniffio             1.3.0
starlette           0.27.0
sympy               1.11.1
tokenizers          0.13.3
toolz               0.12.0
torch               2.0.1+rocm5.4.2
torchaudio          2.0.2+rocm5.4.2
torchvision         0.15.2+rocm5.4.2
tqdm                4.65.0
transformers        4.30.0.dev0
typing_extensions   4.6.2
tzdata              2023.3
uc-micro-py         1.0.2
urllib3             1.26.13
uvicorn             0.22.0
websockets          11.0.3
wheel               0.38.4
xxhash              3.2.0
yarl                1.9.2
```


# Failure Logs
```
$ CMAKE_ARGS=""-DLLAMA_CLBLAST=on"" FORCE_CMAKE=1 pip install llama-cpp-python  --force-reinstall --upgrade --no-cache-dir
Collecting llama-cpp-python
  Downloading llama_cpp_python-0.1.57.tar.gz (1.4 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.4/1.4 MB 6.6 MB/s eta 0:00:00
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting typing-extensions>=4.5.0
  Downloading typing_extensions-4.6.2-py3-none-any.whl (31 kB)
Collecting numpy>=1.20.0
  Downloading numpy-1.24.3-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (17.3 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 17.3/17.3 MB 8.5 MB/s eta 0:00:00
Building wheels for collected packages: llama-cpp-python
  Building wheel for llama-cpp-python (pyproject.toml) ... done
  Created wheel for llama-cpp-python: filename=llama_cpp_python-0.1.57-cp310-cp310-linux_x86_64.whl size=212476 sha256=9c83c78ef597f128db8bfc5ad6ceac144a5eb63a122952e021c47ca3bbb242dc
  Stored in directory: /tmp/pip-ephem-wheel-cache-6ct6wx1l/wheels/87/9b/55/22559358a9af8074053b6c39406f5c06f0d391c052f77ca0c2
Successfully built llama-cpp-python
Installing collected packages: typing-extensions, numpy, llama-cpp-python
  Attempting uninstall: typing-extensions
    Found existing installation: typing_extensions 4.4.0
    Uninstalling typing_extensions-4.4.0:
      Successfully uninstalled typing_extensions-4.4.0
  Attempting uninstall: numpy
    Found existing installation: numpy 1.24.1
    Uninstalling numpy-1.24.1:
      Successfully uninstalled numpy-1.24.1
Successfully installed llama-cpp-python-0.1.57 numpy-1.24.3 typing-extensions-4.6.2
```
```

INFO:Loading llamacpp_30b...
INFO:llama.cpp weights detected: models/llamacpp_30b/ggml-model-q5_0.bin

INFO:Cache capacity is 0 bytes
llama.cpp: loading model from models/llamacpp_30b/ggml-model-q5_0.bin
llama_model_load_internal: format     = ggjt v2 (pre #1508)
llama_model_load_internal: n_vocab    = 32000
llama_model_load_internal: n_ctx      = 2048
llama_model_load_internal: n_embd     = 6656
llama_model_load_internal: n_mult     = 256
llama_model_load_internal: n_head     = 52
llama_model_load_internal: n_layer    = 60
llama_model_load_internal: n_rot      = 128
llama_model_load_internal: ftype      = 8 (mostly Q5_0)
llama_model_load_internal: n_ff       = 17920
llama_model_load_internal: n_parts    = 1
llama_model_load_internal: model size = 30B
llama_model_load_internal: ggml ctx size =    0.13 MB
llama_model_load_internal: mem required  = 23634.31 MB (+ 3124.00 MB per state)
.
llama_init_from_file: kv self size  = 3120.00 MB
AVX = 1 | AVX2 = 1 | AVX512 = 0 | AVX512_VBMI = 0 | AVX512_VNNI = 0 | FMA = 1 | NEON = 0 | ARM_FMA = 0 | F16C = 1 | FP16_VA = 0 | WASM_SIMD = 0 | BLAS = 0 | SSE3 = 1 | VSX = 0 | 
INFO:Loaded the model in 4.37 seconds.


llama_print_timings:        load time =  1245.53 ms
llama_print_timings:      sample time =    43.12 ms /    19 runs   (    2.27 ms per token)
llama_print_timings: prompt eval time =  1245.47 ms /     3 tokens (  415.16 ms per token)
llama_print_timings:        eval time = 11416.53 ms /    18 runs   (  634.25 ms per token)
llama_print_timings:       total time = 12735.25 ms
Output generated in 13.04 seconds (1.46 tokens/s, 19 tokens, context 3, seed 1337143409)

```",0,install with clblast requires clblast libraries     expected behavior    with command  cmake args   dllama clblast on  force cmake   pip install llama cpp python    force reinstall   upgrade   no cache dir   i would expect a llama cpp build with clblast to be installed  which when a model loaded  i would see blas     and my graphic card get used during inference       current behavior    llama cpp shows blas      and my gpu doesn t move at all during inference       environment and context  linux mint     cinnamon  which is basically ubuntu   my gpu  radeon vii     lscpu        架构：                          cpu 运行模式：           bit    bit    address sizes            bits physical    bits virtual    字节序：               little endian  cpu                           在线 cpu 列表：             厂商 id：                authenticamd    型号名称：             amd ryzen          cpu 系列：                  型号：                      每个核的线程数：            每个座的核数：              座：                        步进：                      frequency boost      enabled      cpu 最大 mhz：                cpu 最小 mhz：                bogomips：                    标记：               fpu vme de pse tsc msr pae mce   apic sep mtrr pge mc                           a cmov pat   clflush mmx fxsr sse   ht syscall n                           x mmxext fxsr opt   rdtscp lm constant tsc rep go                           od nopl nonstop tsc cpuid extd apicid aperfmperf rapl p                           ni pclmulqdq monitor   fma                                       c movbe popcnt aes xsave avx   rdrand lahf lm cmp le                           gacy svm extapic   legacy abm   misalignsse                             prefetch osvw ibs skinit wdt tce topoext perfctr core p                           erfctr nb bpext perfctr llc mwaitx cpb cat   cdp   hw                            pstate ssbd mba ibrs ibpb stibp vmmcall fsgsbase                                smep   erms invpcid cqm rdt a rdseed adx smap c                           lflushopt clwb sha ni xsaveopt xsavec   xsaves cq                           m llc cqm occup llc cqm mbm total cqm mbm local clzero                            irperf xsaveerptr rdpru wbnoinvd cppc arat npt lbrv svm                            lock nrip save tsc scale vmcb clean flushbyasid decode                           assists pausefilter pfthreshold avic v vmsave vmload vg                           if v spec ctrl umip pku ospke vaes vpclmulqdq rdpid ove                           rflow recov succor smca fsrm  virtualization features      虚拟化：               amd v  caches  sum of all                                  kib    instances                            kib    instances                             mib    instances                             mib    instance   numa                         numa 节点：                 numa   cpu：            vulnerabilities              itlb multihit          not affected                        not affected    mds                    not affected    meltdown               not affected    mmio stale data        not affected    retbleed               not affected    spec store bypass      mitigation  speculative store bypass disabled via prctl                            and seccomp    spectre               mitigation  usercopy swapgs barriers and   user pointer                            sanitization    spectre               mitigation  retpolines  ibpb conditional  ibrs fw  stib                           p always on  rsb filling  pbrsb eibrs not affected    srbds                  not affected    tsx async abort        not affected            uname  a    linux fgdfgfthgr ms           generic    ubuntu smp mon may         utc               gnu linux                  version  python          make   version  gnu make      为     pc linux gnu 编译  copyright  c      free software foundation  inc   许可证：  ：gnu 通用公共许可证第   版或更新版本    本软件是自由软件：您可以自由修改和重新发布它。  在法律允许的范围内没有其他保证。    g     version  g    ubuntu                       copyright  c    free software foundation  inc   this is free software  see the source for copying conditions   there is no  warranty  not even for merchantability or fitness for a particular purpose           pip list        package             version                                        accelerate                   aiofiles                   aiohttp                    aiosignal                  altair                     anyio                      async timeout              attrs                      bitsandbytes               certifi                    charset normalizer         click                      cmake                      colorama                   contourpy                  cycler                     datasets                   dill                       einops                     exceptiongroup             fastapi                    ffmpy                      filelock                   flexgen                    fonttools                  frozenlist                 fsspec                     gradio                     gradio client                                       httpcore                   httpx                      huggingface hub            idna                                           jsonschema                 kiwisolver                 linkify it py              lit                        llama cpp python           markdown                   markdown it py             markupsafe                 matplotlib                 mdit py plugins            mdurl                      mpmath                     multidict                  multiprocess               networkx                 numpy                      orjson                     packaging                pandas                     peft                         pillow                     pip                        psutil                     pulp                       pyarrow                    pydantic                   pydub                      pygments                   pyparsing                  pyrsistent                 python dateutil            python multipart           pytorch triton rocm        pytz                     pyyaml                   quant cuda                 regex                      requests                   responses                  safetensors                scipy                      semantic version           sentencepiece              setuptools                 six                        sniffio                    starlette                  sympy                      tokenizers                 toolz                      torch                            torchaudio                       torchvision                      tqdm                       transformers                 typing extensions          tzdata                   uc micro py                                     uvicorn                    websockets                 wheel                      xxhash                     yarl                                  failure logs         cmake args   dllama clblast on  force cmake   pip install llama cpp python    force reinstall   upgrade   no cache dir  collecting llama cpp python    downloading llama cpp python       tar gz      mb        ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━         mb     mb s eta          installing build dependencies     done    getting requirements to build wheel     done    preparing metadata  pyproject toml      done  collecting typing extensions           downloading typing extensions         none any whl    kb   collecting numpy           downloading numpy           manylinux               whl      mb        ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━         mb     mb s eta        building wheels for collected packages  llama cpp python    building wheel for llama cpp python  pyproject toml      done    created wheel for llama cpp python  filename llama cpp python           linux     whl size          stored in directory   tmp pip ephem wheel cache   wheels          successfully built llama cpp python  installing collected packages  typing extensions  numpy  llama cpp python    attempting uninstall  typing extensions      found existing installation  typing extensions            uninstalling typing extensions               successfully uninstalled typing extensions          attempting uninstall  numpy      found existing installation  numpy            uninstalling numpy               successfully uninstalled numpy        successfully installed llama cpp python       numpy       typing extensions                    info loading llamacpp       info llama cpp weights detected  models llamacpp   ggml model     bin    info cache capacity is   bytes  llama cpp  loading model from models llamacpp   ggml model     bin  llama model load internal  format       ggjt    pre      llama model load internal  n vocab         llama model load internal  n ctx           llama model load internal  n embd          llama model load internal  n mult          llama model load internal  n head          llama model load internal  n layer         llama model load internal  n rot           llama model load internal  ftype           mostly       llama model load internal  n ff            llama model load internal  n parts         llama model load internal  model size      llama model load internal  ggml ctx size          mb  llama model load internal  mem required        mb        mb per state      llama init from file  kv self size        mb  avx                         vbmi         vnni       fma       neon       arm fma                 va       wasm simd       blas               vsx         info loaded the model in     seconds       llama print timings         load time        ms  llama print timings       sample time          ms        runs            ms per token   llama print timings  prompt eval time        ms         tokens        ms per token   llama print timings         eval time       ms        runs          ms per token   llama print timings        total time       ms  output generated in     seconds      tokens s    tokens  context    seed          ,0
85521,10618369025.0,IssuesEvent,2019-10-13 03:48:17,carbon-design-system/ibm-dotcom-library,https://api.github.com/repos/carbon-design-system/ibm-dotcom-library,closed,Write guidelines for how to use Personae and Journey maps,design design: research migrate priority: low sprint demo website: cupcake website: wedding cake,"_Benjamin-Hansen1 created the following on May 24:_  

 ## User story

As a DDS team member or maker, I need to understand our users, their behaviors, needs, processes, drivers, and how to put that knowledge into my work, etc.- so that I can make sure that the work I do translates all the way to the end user.


## Deliverables

- [ ] Guideline

## Acceptance Criteria

- [ ] Published presented to DDS team (Playback) 

_Original issue: https://github.ibm.com/webstandards/digital-design/issues/888_",2.0,"Write guidelines for how to use Personae and Journey maps - _Benjamin-Hansen1 created the following on May 24:_  

 ## User story

As a DDS team member or maker, I need to understand our users, their behaviors, needs, processes, drivers, and how to put that knowledge into my work, etc.- so that I can make sure that the work I do translates all the way to the end user.


## Deliverables

- [ ] Guideline

## Acceptance Criteria

- [ ] Published presented to DDS team (Playback) 

_Original issue: https://github.ibm.com/webstandards/digital-design/issues/888_",0,write guidelines for how to use personae and journey maps    benjamin   created the following on may            user story  as a dds team member or maker  i need to understand our users  their behaviors  needs  processes  drivers  and how to put that knowledge into my work  etc   so that i can make sure that the work i do translates all the way to the end user       deliverables      guideline     acceptance criteria      published presented to dds team  playback     original issue   ,0
22376,4793115396.0,IssuesEvent,2016-10-31 17:17:26,golang/go,https://api.github.com/repos/golang/go,closed,reflect: NumMethod doesn't return not exported members of method sets,Documentation,"### What version of Go are you using (`go version`)?

go version go1.7.1 darwin/amd64

### What operating system and processor architecture are you using (`go env`)?

```
> go env
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/mlowicki/projects/golang/spec""
GORACE=""""
GOROOT=""/usr/local/go""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
```

### Repro
https://play.golang.org/p/eXoyuqajG6

### Expected result
I expect to see method `n` also printed out and language spec doesn't enforce that method set contains only exported identifiers.

Currently it displays only info about `M`:
```
Number of methods: 1
Method {M  func(main.T) <func(main.T) Value> %!s(int=0)}
	Name: M
	PkgPath: 
```",1.0,"reflect: NumMethod doesn't return not exported members of method sets - ### What version of Go are you using (`go version`)?

go version go1.7.1 darwin/amd64

### What operating system and processor architecture are you using (`go env`)?

```
> go env
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/mlowicki/projects/golang/spec""
GORACE=""""
GOROOT=""/usr/local/go""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
```

### Repro
https://play.golang.org/p/eXoyuqajG6

### Expected result
I expect to see method `n` also printed out and language spec doesn't enforce that method set contains only exported identifiers.

Currently it displays only info about `M`:
```
Number of methods: 1
Method {M  func(main.T) <func(main.T) Value> %!s(int=0)}
	Name: M
	PkgPath: 
```",1,reflect  nummethod doesn t return not exported members of method sets       what version of go are you using   go version       go version       darwin          what operating system and processor architecture are you using   go env              go env  goarch      gobin     goexe     gohostarch      gohostos  darwin   goos  darwin   gopath   users mlowicki projects golang spec   gorace     goroot   usr local go   gotooldir   usr local go pkg tool darwin     cc  clang   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    gno record gcc switches  fno common   cxx  clang     cgo enabled                 repro           expected result  i expect to see method  n  also printed out and language spec doesn t enforce that method set contains only exported identifiers     currently it displays only info about  m         number of methods     method  m  func main t      s int      	name  m  	pkgpath       ,1
34246,6306261836.0,IssuesEvent,2017-07-21 20:31:35,golang/go,https://api.github.com/repos/golang/go,opened,unclear docs causing races in sql/driver implementations,Documentation,"### What version of Go are you using (`go version`)?

`go version go1.8.3 darwin/amd64`

### What did you do?

Unlike `Conn` or `Stmt` there's no guidance on `Tx` indicating how the stdlib uses implementations. This seems to cause bugs in driver implementations, as a `Tx` is expected to handle concurrent calls from multiple goroutines unlike most of the other interfaces in the package.

This came up as I was debugging [a panic inside of lib/pq](https://github.com/lib/pq/issues/614) and discovered it was a data race due to the authors not assuming that their `Tx` would have to deal with calls from multiple goroutines. Out of curiosity, I looked at `go-sql-driver/mysql` and the lack of a race there seems like a happy accident - the Context expiring occasionally causes [an internal error to bubble up](https://github.com/go-sql-driver/mysql/blob/a825be04c652d01442384e9dcdf2cdc3f1eda67f/packets.go#L441-L443), since the authors appear to aggressively check their invariants.

I'm not sure whether this is a documentation problem or if there's something database/sql could do to make life easier for driver implementors.

",1.0,"unclear docs causing races in sql/driver implementations - ### What version of Go are you using (`go version`)?

`go version go1.8.3 darwin/amd64`

### What did you do?

Unlike `Conn` or `Stmt` there's no guidance on `Tx` indicating how the stdlib uses implementations. This seems to cause bugs in driver implementations, as a `Tx` is expected to handle concurrent calls from multiple goroutines unlike most of the other interfaces in the package.

This came up as I was debugging [a panic inside of lib/pq](https://github.com/lib/pq/issues/614) and discovered it was a data race due to the authors not assuming that their `Tx` would have to deal with calls from multiple goroutines. Out of curiosity, I looked at `go-sql-driver/mysql` and the lack of a race there seems like a happy accident - the Context expiring occasionally causes [an internal error to bubble up](https://github.com/go-sql-driver/mysql/blob/a825be04c652d01442384e9dcdf2cdc3f1eda67f/packets.go#L441-L443), since the authors appear to aggressively check their invariants.

I'm not sure whether this is a documentation problem or if there's something database/sql could do to make life easier for driver implementors.

",1,unclear docs causing races in sql driver implementations       what version of go are you using   go version        go version       darwin           what did you do     unlike  conn  or  stmt  there s no guidance on  tx  indicating how the stdlib uses implementations  this seems to cause bugs in driver implementations  as a  tx  is expected to handle concurrent calls from multiple goroutines unlike most of the other interfaces in the package     this came up as i was debugging     and discovered it was a data race due to the authors not assuming that their  tx  would have to deal with calls from multiple goroutines  out of curiosity  i looked at  go sql driver mysql  and the lack of a race there seems like a happy accident   the context expiring occasionally causes     since the authors appear to aggressively check their invariants     i m not sure whether this is a documentation problem or if there s something database sql could do to make life easier for driver implementors     ,1
50425,7603623484.0,IssuesEvent,2018-04-29 16:24:49,golang/go,https://api.github.com/repos/golang/go,closed,cmd/compile: improve the help message of go tool compile -d ssa/help,Documentation NeedsFix,"I noticed it was somewhat difficult to read the ssa/help output:

```
  $ go tool compile -d ssa/help
  compile: GcFlag -d=ssa/<phase>/<flag>[=<value>]|[:<function_name>]
  <phase> is one of:
  check, all, build, intrinsics, early_phielim, early_copyelim
  early_deadcode, short_circuit, decompose_user, opt, zero_arg_cse
  opt_deadcode, generic_cse, phiopt, nilcheckelim, prove, loopbce
  decompose_builtin, dec, late_opt, generic_deadcode, check_bce
  writebarrier, fuse, dse, insert_resched_checks, tighten, lower
  lowered_cse, lowered_deadcode, checkLower, late_phielim, late_copyelim
  phi_tighten, late_deadcode, critical, likelyadjust, layout, schedule
  late_nilcheck, flagalloc, regalloc, stackframe, trim
  <flag> is one of on, off, debug, mem, time, test, stats, dump
  <value> defaults to 1
  <function_name> is required for ""dump"", specifies name of function to dump after <phase>
  Except for dump, output is directed to standard out; dump appears in a file.
  Phase ""all"" supports flags ""time"", ""mem"", and ""dump"".
  Phases ""intrinsics"" supports flags ""on"", ""off"", and ""debug"".
  Interpretation of the ""debug"" value depends on the phase.
  Dump files are named <phase>__<function_name>_<seq>.dump.
```

With a few tweaks here and there it looks more pleasing to the eye:

```
  $ go tool compile -d ssa/help
  compile: usage: -d=ssa/<phase>/<flag>[=<value>|<function_name>]

  <phase> is one of:

  	check, all, build, intrinsics, early_phielim, early_copyelim, early_deadcode
  	short_circuit, decompose_user, opt, zero_arg_cse, opt_deadcode, generic_cse
  	phiopt, nilcheckelim, prove, loopbce, decompose_builtin, dec, late_opt
  	generic_deadcode, check_bce, writebarrier, fuse, dse, insert_resched_checks
  	tighten, lower, lowered_cse, lowered_deadcode, checkLower, late_phielim
  	late_copyelim, phi_tighten, late_deadcode, critical, likelyadjust, layout
  	schedule, late_nilcheck, flagalloc, regalloc, stackframe, trim

  <flag> is one of on, off, debug, mem, time, test, stats, dump.
  Phase all supports flags time, mem, and dump.
  Phase intrinsics supports flags on, off, and debug.

  <value> defaults to 1.

  <function_name> is required for dump, specifies name of function to dump after <phase>.

  Except for dump, output is directed to standard out; dump appears in a file.
  Dump files are named <phase>__<function_name>_<seq>.dump.
```",1.0,"cmd/compile: improve the help message of go tool compile -d ssa/help - I noticed it was somewhat difficult to read the ssa/help output:

```
  $ go tool compile -d ssa/help
  compile: GcFlag -d=ssa/<phase>/<flag>[=<value>]|[:<function_name>]
  <phase> is one of:
  check, all, build, intrinsics, early_phielim, early_copyelim
  early_deadcode, short_circuit, decompose_user, opt, zero_arg_cse
  opt_deadcode, generic_cse, phiopt, nilcheckelim, prove, loopbce
  decompose_builtin, dec, late_opt, generic_deadcode, check_bce
  writebarrier, fuse, dse, insert_resched_checks, tighten, lower
  lowered_cse, lowered_deadcode, checkLower, late_phielim, late_copyelim
  phi_tighten, late_deadcode, critical, likelyadjust, layout, schedule
  late_nilcheck, flagalloc, regalloc, stackframe, trim
  <flag> is one of on, off, debug, mem, time, test, stats, dump
  <value> defaults to 1
  <function_name> is required for ""dump"", specifies name of function to dump after <phase>
  Except for dump, output is directed to standard out; dump appears in a file.
  Phase ""all"" supports flags ""time"", ""mem"", and ""dump"".
  Phases ""intrinsics"" supports flags ""on"", ""off"", and ""debug"".
  Interpretation of the ""debug"" value depends on the phase.
  Dump files are named <phase>__<function_name>_<seq>.dump.
```

With a few tweaks here and there it looks more pleasing to the eye:

```
  $ go tool compile -d ssa/help
  compile: usage: -d=ssa/<phase>/<flag>[=<value>|<function_name>]

  <phase> is one of:

  	check, all, build, intrinsics, early_phielim, early_copyelim, early_deadcode
  	short_circuit, decompose_user, opt, zero_arg_cse, opt_deadcode, generic_cse
  	phiopt, nilcheckelim, prove, loopbce, decompose_builtin, dec, late_opt
  	generic_deadcode, check_bce, writebarrier, fuse, dse, insert_resched_checks
  	tighten, lower, lowered_cse, lowered_deadcode, checkLower, late_phielim
  	late_copyelim, phi_tighten, late_deadcode, critical, likelyadjust, layout
  	schedule, late_nilcheck, flagalloc, regalloc, stackframe, trim

  <flag> is one of on, off, debug, mem, time, test, stats, dump.
  Phase all supports flags time, mem, and dump.
  Phase intrinsics supports flags on, off, and debug.

  <value> defaults to 1.

  <function_name> is required for dump, specifies name of function to dump after <phase>.

  Except for dump, output is directed to standard out; dump appears in a file.
  Dump files are named <phase>__<function_name>_<seq>.dump.
```",1,cmd compile  improve the help message of go tool compile  d ssa help   i noticed it was somewhat difficult to read the ssa help output              go tool compile  d ssa help    compile  gcflag  d ssa             is one of     check  all  build  intrinsics  early phielim  early copyelim    early deadcode  short circuit  decompose user  opt  zero arg cse    opt deadcode  generic cse  phiopt  nilcheckelim  prove  loopbce    decompose builtin  dec  late opt  generic deadcode  check bce    writebarrier  fuse  dse  insert resched checks  tighten  lower    lowered cse  lowered deadcode  checklower  late phielim  late copyelim    phi tighten  late deadcode  critical  likelyadjust  layout  schedule    late nilcheck  flagalloc  regalloc  stackframe  trim      is one of on  off  debug  mem  time  test  stats  dump      defaults to        is required for  dump   specifies name of function to dump after      except for dump  output is directed to standard out  dump appears in a file     phase  all  supports flags  time    mem   and  dump      phases  intrinsics  supports flags  on    off   and  debug      interpretation of the  debug  value depends on the phase     dump files are named        dump          with a few tweaks here and there it looks more pleasing to the eye              go tool compile  d ssa help    compile  usage   d ssa             is one of       	check  all  build  intrinsics  early phielim  early copyelim  early deadcode    	short circuit  decompose user  opt  zero arg cse  opt deadcode  generic cse    	phiopt  nilcheckelim  prove  loopbce  decompose builtin  dec  late opt    	generic deadcode  check bce  writebarrier  fuse  dse  insert resched checks    	tighten  lower  lowered cse  lowered deadcode  checklower  late phielim    	late copyelim  phi tighten  late deadcode  critical  likelyadjust  layout    	schedule  late nilcheck  flagalloc  regalloc  stackframe  trim        is one of on  off  debug  mem  time  test  stats  dump     phase all supports flags time  mem  and dump     phase intrinsics supports flags on  off  and debug         defaults to           is required for dump  specifies name of function to dump after         except for dump  output is directed to standard out  dump appears in a file     dump files are named        dump      ,1
745745,25998759920.0,IssuesEvent,2022-12-20 13:46:10,lukovdm/bf2-www,https://api.github.com/repos/lukovdm/bf2-www,opened,Pronouns only show when you choose non-binary option in signup form,priority: High,"This should always be an option, but leave them the option to keep it open",1.0,"Pronouns only show when you choose non-binary option in signup form - This should always be an option, but leave them the option to keep it open",0,pronouns only show when you choose non binary option in signup form   this should always be an option  but leave them the option to keep it open,0
79738,3546323310.0,IssuesEvent,2016-01-20 01:48:12,KPB-US/tars,https://api.github.com/repos/KPB-US/tars,closed,enable/disable car rental explanation and nonbudgeted explanation,Priority - High,based on their corresponding checkboxes on the request form,1.0,enable/disable car rental explanation and nonbudgeted explanation - based on their corresponding checkboxes on the request form,0,enable disable car rental explanation and nonbudgeted explanation   based on their corresponding checkboxes on the request form,0
347253,10427366251.0,IssuesEvent,2019-09-16 19:46:10,ansible/awx,https://api.github.com/repos/ansible/awx,closed,Console error thrown when selecting a credential type on a different page.,component:ui priority:medium state:in_progress type:bug,"##### ISSUE TYPE
 - Bug Report

##### COMPONENT NAME
 - UI

##### SUMMARY
A console error is raised (with no noticeable impact to UI) when selecting a credential type that isn't on the currently selected page in pagination. To explain further...click the magnifying glass in the box for ""Credential Type"":
![screenshot from 2018-12-14 09-22-03](https://user-images.githubusercontent.com/19942822/50008344-e012e980-ff81-11e8-9ef7-5e8cc3c50422.png)

Button-highlight one of the options on the first page of listed options, like ""Insights"" is selected here:
![screenshot from 2018-12-14 09-24-00](https://user-images.githubusercontent.com/19942822/50008408-13557880-ff82-11e8-8673-3e65e94af059.png)

Instead of clicking save, navigate to page 2 or 3 of the options, so that ""Insights"" is still selected but no longer visible, _then_ click save. Insights is successfully selected, but a console error propagates:
```
TypeError: Cannot set property '_disabled' of undefined
    at EditCredentialsController.vm.gceOnReplaceKeyChanged (app.25b0416915d00468df69.js:29)
    at Scope.$digest (vendor.876e40cd69678d43e470.js:570)
    at Scope.$apply (vendor.876e40cd69678d43e470.js:570)
    at done (vendor.876e40cd69678d43e470.js:570)
    at completeRequest (vendor.876e40cd69678d43e470.js:570)
    at XMLHttpRequest.xhr.onload (vendor.876e40cd69678d43e470.js:570)
```

##### ENVIRONMENT
* AWX version: latest
* AWX install method: docker on linux
* Ansible version:  2.6.10.post0
* Operating System: Fedora
* Web Browser: Chrome

##### STEPS TO REPRODUCE

See summary for detailed steps. 

##### EXPECTED RESULTS
No console errors.
##### ACTUAL RESULTS
Console errors.",1.0,"Console error thrown when selecting a credential type on a different page. - ##### ISSUE TYPE
 - Bug Report

##### COMPONENT NAME
 - UI

##### SUMMARY
A console error is raised (with no noticeable impact to UI) when selecting a credential type that isn't on the currently selected page in pagination. To explain further...click the magnifying glass in the box for ""Credential Type"":
![screenshot from 2018-12-14 09-22-03](https://user-images.githubusercontent.com/19942822/50008344-e012e980-ff81-11e8-9ef7-5e8cc3c50422.png)

Button-highlight one of the options on the first page of listed options, like ""Insights"" is selected here:
![screenshot from 2018-12-14 09-24-00](https://user-images.githubusercontent.com/19942822/50008408-13557880-ff82-11e8-8673-3e65e94af059.png)

Instead of clicking save, navigate to page 2 or 3 of the options, so that ""Insights"" is still selected but no longer visible, _then_ click save. Insights is successfully selected, but a console error propagates:
```
TypeError: Cannot set property '_disabled' of undefined
    at EditCredentialsController.vm.gceOnReplaceKeyChanged (app.25b0416915d00468df69.js:29)
    at Scope.$digest (vendor.876e40cd69678d43e470.js:570)
    at Scope.$apply (vendor.876e40cd69678d43e470.js:570)
    at done (vendor.876e40cd69678d43e470.js:570)
    at completeRequest (vendor.876e40cd69678d43e470.js:570)
    at XMLHttpRequest.xhr.onload (vendor.876e40cd69678d43e470.js:570)
```

##### ENVIRONMENT
* AWX version: latest
* AWX install method: docker on linux
* Ansible version:  2.6.10.post0
* Operating System: Fedora
* Web Browser: Chrome

##### STEPS TO REPRODUCE

See summary for detailed steps. 

##### EXPECTED RESULTS
No console errors.
##### ACTUAL RESULTS
Console errors.",0,console error thrown when selecting a credential type on a different page          issue type     bug report          component name     ui          summary  a console error is raised  with no noticeable impact to ui  when selecting a credential type that isn t on the currently selected page in pagination  to explain further   click the magnifying glass in the box for  credential type            button highlight one of the options on the first page of listed options  like  insights  is selected here           instead of clicking save  navigate to page   or   of the options  so that  insights  is still selected but no longer visible   then  click save  insights is successfully selected  but a console error propagates        typeerror  cannot set property   disabled  of undefined      at editcredentialscontroller vm gceonreplacekeychanged  app   js         at scope  digest  vendor   js         at scope  apply  vendor   js         at done  vendor   js         at completerequest  vendor   js         at xmlhttprequest xhr onload  vendor   js                  environment    awx version  latest    awx install method  docker on linux    ansible version              operating system  fedora    web browser  chrome          steps to reproduce    see summary for detailed steps            expected results  no console errors         actual results  console errors ,0
32182,6038104812.0,IssuesEvent,2017-06-09 20:29:49,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: typo in test.go doc,Documentation NeedsFix Suggested,"In the doc string in src/cmd/go/test.go, line 65 it says: '...no arguments.  It compiles...'.
There are two spaces before the 'It', should be only one.",1.0,"cmd/go: typo in test.go doc - In the doc string in src/cmd/go/test.go, line 65 it says: '...no arguments.  It compiles...'.
There are two spaces before the 'It', should be only one.",1,cmd go  typo in test go doc   in the doc string in src cmd go test go  line   it says      no arguments   it compiles       there are two spaces before the  it   should be only one ,1
40193,2867308955.0,IssuesEvent,2015-06-05 12:30:29,alexeyxo/protobuf-swift,https://api.github.com/repos/alexeyxo/protobuf-swift,closed,Handled case of parsing negative integers.,bug high priority,"I had to change code to get my protobuf working. I was getting an exception when deserializing negative value of type Int32.
    
Along with that, in the function 
```
readRawData(size:Int32)
```
below mentioned case was turning out to be true when it tries to deserialize negative integer number in function 

```
public func readRawData(size:Int32) -> NSData
```

```
if (totalBytesRetired + bufferPos + size > currentLimit) {
```

I had to change whole function 
```
readRawVarint32()
```
to look like Java protobuf function.",1.0,"Handled case of parsing negative integers. - I had to change code to get my protobuf working. I was getting an exception when deserializing negative value of type Int32.
    
Along with that, in the function 
```
readRawData(size:Int32)
```
below mentioned case was turning out to be true when it tries to deserialize negative integer number in function 

```
public func readRawData(size:Int32) -> NSData
```

```
if (totalBytesRetired + bufferPos + size > currentLimit) {
```

I had to change whole function 
```
readRawVarint32()
```
to look like Java protobuf function.",0,handled case of parsing negative integers    i had to change code to get my protobuf working  i was getting an exception when deserializing negative value of type           along with that  in the function        readrawdata size          below mentioned case was turning out to be true when it tries to deserialize negative integer number in function          public func readrawdata size       nsdata              if  totalbytesretired   bufferpos   size   currentlimit            i had to change whole function                  to look like java protobuf function ,0
362934,10735256653.0,IssuesEvent,2019-10-29 08:19:37,webcompat/web-bugs,https://api.github.com/repos/webcompat/web-bugs,closed,www.fujitsu.com - site is not usable,browser-firefox-mobile engine-gecko priority-normal type-mobify,"<!-- @browser: Firefox Mobile 68.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0 -->
<!-- @reported_with: mobile-reporter -->
<!-- @extra_labels: type-mobify -->

**URL**: https://www.fujitsu.com/global/about/resources/news/press-releases/2019/1015-01.html

**Browser / Version**: Firefox Mobile 68.0
**Operating System**: Android
**Tested Another Browser**: No

**Problem type**: Site is not usable
**Description**: without requesting the desktop view, the site appears only white 
**Steps to Reproduce**:
visit site on my browser
[![Screenshot Description](https://webcompat.com/uploads/2019/10/3b8131e3-9076-4ea1-af37-5fb58de89b74-thumb.jpeg)](https://webcompat.com/uploads/2019/10/3b8131e3-9076-4ea1-af37-5fb58de89b74.jpeg)

<details>
<summary>Browser Configuration</summary>
<ul>
  <li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20191014163636</li><li>channel: beta</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li><li>hasMobify: true</li>
</ul>
<p>Console Messages:</p>
<pre>
['[JavaScript Warning: ""An unbalanced tree was written using document.write() causing data from the network to be reparsed. For more information https://developer.mozilla.org/en/Optimizing_Your_Pages_for_Speculative_Parsing"" {file: ""https://www.fujitsu.com/global/about/resources/news/press-releases/2019/1015-01.html"" line: 14}]', '[JavaScript Warning: ""Loading failed for the <script> with source https://cdn.mobify.com/sites/fj/production/adaptive.min.js."" {file: ""https://www.fujitsu.com/global/about/resources/news/press-releases/2019/1015-01.html"" line: 1}]']
</pre>
</details>

_From [webcompat.com](https://webcompat.com/) with ❤️_",1.0,"www.fujitsu.com - site is not usable - <!-- @browser: Firefox Mobile 68.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0 -->
<!-- @reported_with: mobile-reporter -->
<!-- @extra_labels: type-mobify -->

**URL**: https://www.fujitsu.com/global/about/resources/news/press-releases/2019/1015-01.html

**Browser / Version**: Firefox Mobile 68.0
**Operating System**: Android
**Tested Another Browser**: No

**Problem type**: Site is not usable
**Description**: without requesting the desktop view, the site appears only white 
**Steps to Reproduce**:
visit site on my browser
[![Screenshot Description](https://webcompat.com/uploads/2019/10/3b8131e3-9076-4ea1-af37-5fb58de89b74-thumb.jpeg)](https://webcompat.com/uploads/2019/10/3b8131e3-9076-4ea1-af37-5fb58de89b74.jpeg)

<details>
<summary>Browser Configuration</summary>
<ul>
  <li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20191014163636</li><li>channel: beta</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li><li>hasMobify: true</li>
</ul>
<p>Console Messages:</p>
<pre>
['[JavaScript Warning: ""An unbalanced tree was written using document.write() causing data from the network to be reparsed. For more information https://developer.mozilla.org/en/Optimizing_Your_Pages_for_Speculative_Parsing"" {file: ""https://www.fujitsu.com/global/about/resources/news/press-releases/2019/1015-01.html"" line: 14}]', '[JavaScript Warning: ""Loading failed for the <script> with source https://cdn.mobify.com/sites/fj/production/adaptive.min.js."" {file: ""https://www.fujitsu.com/global/about/resources/news/press-releases/2019/1015-01.html"" line: 1}]']
</pre>
</details>

_From [webcompat.com](https://webcompat.com/) with ❤️_",0,    site is not usable              url         browser   version    firefox mobile       operating system    android   tested another browser    no    problem type    site is not usable   description    without requesting the desktop view  the site appears only white    steps to reproduce    visit site on my browser          browser configuration       gfx webrender all  false  gfx webrender blob images  true  gfx webrender enabled  false  image mem shared  true  buildid     channel  beta  hastouchscreen  true  mixed active content blocked  false  mixed passive content blocked  false  tracking content blocked  false  hasmobify  true     console messages                    from     with ❤️ ,0
711006,24446960648.0,IssuesEvent,2022-10-06 18:51:00,google/ground-android,https://api.github.com/repos/google/ground-android,opened,[Code health] Convert all `@Singleton`s to Kotlin `object`s,type: cleanup priority: p2,"Kotlin has nice native support for declaring singletons using `object` declarations. Unfortunately, Dagger does not support injecting classes into `objects`, which at the moment pretty much prevents us from using an object for any construct that needs to depend on classes we'd normally inject.

If we convert all the classes we've currently marked as `@Singleton` into `objects` we can drop the several injections which should make kotlin code easier to refactor.",1.0,"[Code health] Convert all `@Singleton`s to Kotlin `object`s - Kotlin has nice native support for declaring singletons using `object` declarations. Unfortunately, Dagger does not support injecting classes into `objects`, which at the moment pretty much prevents us from using an object for any construct that needs to depend on classes we'd normally inject.

If we convert all the classes we've currently marked as `@Singleton` into `objects` we can drop the several injections which should make kotlin code easier to refactor.",0,  convert all   singleton s to kotlin  object s   kotlin has nice native support for declaring singletons using  object  declarations  unfortunately  dagger does not support injecting classes into  objects   which at the moment pretty much prevents us from using an object for any construct that needs to depend on classes we d normally inject     if we convert all the classes we ve currently marked as   singleton  into  objects  we can drop the several injections which should make kotlin code easier to refactor ,0
26718,5282807590.0,IssuesEvent,2017-02-07 19:46:38,golang/go,https://api.github.com/repos/golang/go,closed,runtime/pprof: document the requirement to wait to capture any CPU profile samples,Documentation,"Package's godoc example starts the CPU profiling and defers pprof.StopCPUProfile, but it fails to document that the function need to spend sometime before returning in order for any samples to be collected. We might want to add a time.Sleep to make it more obvious and document it throughly that time is required to collect samples.

```
if err := pprof.StartCPUProfile(f); err != nil {
    log.Fatal(""could not start CPU profile: "", err)
}
defer pprof.StopCPUProfile()
```",1.0,"runtime/pprof: document the requirement to wait to capture any CPU profile samples - Package's godoc example starts the CPU profiling and defers pprof.StopCPUProfile, but it fails to document that the function need to spend sometime before returning in order for any samples to be collected. We might want to add a time.Sleep to make it more obvious and document it throughly that time is required to collect samples.

```
if err := pprof.StartCPUProfile(f); err != nil {
    log.Fatal(""could not start CPU profile: "", err)
}
defer pprof.StopCPUProfile()
```",1,runtime pprof  document the requirement to wait to capture any cpu profile samples   package s godoc example starts the cpu profiling and defers pprof stopcpuprofile  but it fails to document that the function need to spend sometime before returning in order for any samples to be collected  we might want to add a time sleep to make it more obvious and document it throughly that time is required to collect samples          if err    pprof startcpuprofile f   err    nil        log fatal  could not start cpu profile     err      defer pprof stopcpuprofile       ,1
82545,10295314096.0,IssuesEvent,2019-08-27 20:54:09,golang/go,https://api.github.com/repos/golang/go,closed,net: document where service names come from?,Documentation NeedsFix Suggested help wanted,"Found in `net/http/server.go`:
 
```
type Server struct {
	Addr    string  // TCP address to listen on, "":http"" if empty
```

What is this "":http"" exactly? Presumably an alias, but I can't find any concrete documentation to know what it resolves to.

https://github.com/golang/go/blob/964fe4b80ff7a9e5490f11de0e216ae34a019ebc/src/net/http/server.go#L2477",1.0,"net: document where service names come from? - Found in `net/http/server.go`:
 
```
type Server struct {
	Addr    string  // TCP address to listen on, "":http"" if empty
```

What is this "":http"" exactly? Presumably an alias, but I can't find any concrete documentation to know what it resolves to.

https://github.com/golang/go/blob/964fe4b80ff7a9e5490f11de0e216ae34a019ebc/src/net/http/server.go#L2477",1,net  document where service names come from    found in  net http server go            type server struct    	addr    string     tcp address to listen on    http  if empty         what is this   http  exactly  presumably an alias  but i can t find any concrete documentation to know what it resolves to      ,1
41707,6927746650.0,IssuesEvent,2017-12-01 00:25:54,golang/go,https://api.github.com/repos/golang/go,closed,testing: are T.Run and B.Run safe for concurrent use?,Documentation NeedsFix release-blocker,"I do not see any documentation specifying if T.Run is safe for concurrent use. I see the following doc for [testing.T](https://tip.golang.org/pkg/testing/#T), which does not mention T.Run:

> A test ends when its Test function returns or calls any of the methods FailNow, Fatal, Fatalf, SkipNow, Skip, or Skipf. Those methods, as well as the Parallel method, must be called only from the goroutine running the Test function.
>
> The other reporting methods, such as the variations of Log and Error, may be called simultaneously from multiple goroutines.

There is a similar doc for [testing.B](https://tip.golang.org/pkg/testing/#B).

I ask because I believe T.Run was safe for concurrent use in go 1.7. Then, [this line](https://github.com/golang/go/blob/7fb16406139e934d84f7ec66ba440a772747270a/src/testing/testing.go#L663) was added in go 1.8, which made T.Run no longer safe for concurrent use. I don't particularly care whether T.Run is safe for concurrent use, but I think the semantics should be clarified.

Optimistically labeling this go1.8.

/cc @dsnet ",1.0,"testing: are T.Run and B.Run safe for concurrent use? - I do not see any documentation specifying if T.Run is safe for concurrent use. I see the following doc for [testing.T](https://tip.golang.org/pkg/testing/#T), which does not mention T.Run:

> A test ends when its Test function returns or calls any of the methods FailNow, Fatal, Fatalf, SkipNow, Skip, or Skipf. Those methods, as well as the Parallel method, must be called only from the goroutine running the Test function.
>
> The other reporting methods, such as the variations of Log and Error, may be called simultaneously from multiple goroutines.

There is a similar doc for [testing.B](https://tip.golang.org/pkg/testing/#B).

I ask because I believe T.Run was safe for concurrent use in go 1.7. Then, [this line](https://github.com/golang/go/blob/7fb16406139e934d84f7ec66ba440a772747270a/src/testing/testing.go#L663) was added in go 1.8, which made T.Run no longer safe for concurrent use. I don't particularly care whether T.Run is safe for concurrent use, but I think the semantics should be clarified.

Optimistically labeling this go1.8.

/cc @dsnet ",1,testing  are t run and b run safe for concurrent use    i do not see any documentation specifying if t run is safe for concurrent use  i see the following doc for     which does not mention t run       a test ends when its test function returns or calls any of the methods failnow  fatal  fatalf  skipnow  skip  or skipf  those methods  as well as the parallel method  must be called only from the goroutine running the test function        the other reporting methods  such as the variations of log and error  may be called simultaneously from multiple goroutines     there is a similar doc for        i ask because i believe t run was safe for concurrent use in go      then      was added in go      which made t run no longer safe for concurrent use  i don t particularly care whether t run is safe for concurrent use  but i think the semantics should be clarified     optimistically labeling this          cc  dsnet ,1
24695,12371582883.0,IssuesEvent,2020-05-18 18:49:38,modin-project/modin,https://api.github.com/repos/modin-project/modin,closed,Everything after DataFrame.sample() running out of memory,Performance 🚀 bug :bug:,"### System information
- **OS Platform and Distribution (e.g., Linux Ubuntu 16.04)**: Linux (remote machine) 
- **Modin version** (`modin.__version__`): 0.7.0
- **Python version**: 3.7
- **Code we can use to reproduce**:
```python
import modin.pandas as pd

# read data files
df1 = pd.read_parquet(""data1.parquet"")
df2 = pd.read_parquet(""data2.parquet"") 

# do some operations
df = pd.merge(df1, df2, right_index=True, left_index=True, sort=False)

# write out the result
df.to_parquet(""new_data.parquet"")

# but if you sample down
df = df.sample(n=10000, random_state=42)

# then do anything after it, nothing works
df.to_parquet(""new_data2.parquet"") #<-- doesn't complete
```
<!--
You can obtain the Modin version with

python -c ""import modin; print(modin.__version__)""
-->

### Describe the problem
<!-- Describe the problem clearly here. -->

Everything after `DataFrame.sample()` is not working/killing the process/workers running out of memory (similar to this [issue](https://github.com/dask/dask/issues/4256) on Dask)

The same code runs beautifully without `.sample()` on the same machine. Whenever `.sample()` is summoned, the workers start running out of memory and the run gets killed after a couple of retries. 

What's worth noting here that modin is doing a beautiful job on the complete data file (~ 1M records), but then whenever I sub-sample to say 100,000 records, it starts running out of memory!

PS: I'm running modin + dask

### Source code / logs
<!-- Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached. Try to provide a reproducible test case that is the bare minimum necessary to generate the problem. -->
",True,"Everything after DataFrame.sample() running out of memory - ### System information
- **OS Platform and Distribution (e.g., Linux Ubuntu 16.04)**: Linux (remote machine) 
- **Modin version** (`modin.__version__`): 0.7.0
- **Python version**: 3.7
- **Code we can use to reproduce**:
```python
import modin.pandas as pd

# read data files
df1 = pd.read_parquet(""data1.parquet"")
df2 = pd.read_parquet(""data2.parquet"") 

# do some operations
df = pd.merge(df1, df2, right_index=True, left_index=True, sort=False)

# write out the result
df.to_parquet(""new_data.parquet"")

# but if you sample down
df = df.sample(n=10000, random_state=42)

# then do anything after it, nothing works
df.to_parquet(""new_data2.parquet"") #<-- doesn't complete
```
<!--
You can obtain the Modin version with

python -c ""import modin; print(modin.__version__)""
-->

### Describe the problem
<!-- Describe the problem clearly here. -->

Everything after `DataFrame.sample()` is not working/killing the process/workers running out of memory (similar to this [issue](https://github.com/dask/dask/issues/4256) on Dask)

The same code runs beautifully without `.sample()` on the same machine. Whenever `.sample()` is summoned, the workers start running out of memory and the run gets killed after a couple of retries. 

What's worth noting here that modin is doing a beautiful job on the complete data file (~ 1M records), but then whenever I sub-sample to say 100,000 records, it starts running out of memory!

PS: I'm running modin + dask

### Source code / logs
<!-- Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached. Try to provide a reproducible test case that is the bare minimum necessary to generate the problem. -->
",0,everything after dataframe sample   running out of memory       system information      os platform and distribution  e g   linux ubuntu         linux  remote machine        modin version     modin   version                 python version             code we can use to reproduce        python  import modin pandas as pd      read data files      pd read parquet    parquet        pd read parquet    parquet         do some operations  df   pd merge       right index true  left index true  sort false       write out the result  df to parquet  new data parquet        but if you sample down  df   df sample n    random state         then do anything after it  nothing works  df to parquet  new   parquet        doesn t complete             you can obtain the modin version with    python  c  import modin  print modin   version                 describe the problem       everything after  dataframe sample    is not working killing the process workers running out of memory  similar to this     on dask     the same code runs beautifully without   sample    on the same machine  whenever   sample    is summoned  the workers start running out of memory and the run gets killed after a couple of retries      what s worth noting here that modin is doing a beautiful job on the complete data file      records   but then whenever i sub sample to say     records  it starts running out of memory     ps  i m running modin   dask        source code   logs     ,0
9371,8614551588.0,IssuesEvent,2018-11-19 17:48:36,terraform-providers/terraform-provider-aws,https://api.github.com/repos/terraform-providers/terraform-provider-aws,closed,Feature request: IAM user and group tagging,enhancement service/iam,"Tagging for IAM users and groups [recently released](https://github.com/aws/aws-sdk-go/releases/tag/v1.15.77).
Requires:
* https://github.com/terraform-providers/terraform-provider-aws/pull/6484",1.0,"Feature request: IAM user and group tagging - Tagging for IAM users and groups [recently released](https://github.com/aws/aws-sdk-go/releases/tag/v1.15.77).
Requires:
* https://github.com/terraform-providers/terraform-provider-aws/pull/6484",0,feature request  iam user and group tagging   tagging for iam users and groups      requires      ,0
134826,30194540295.0,IssuesEvent,2023-07-04 19:06:45,AllenInstitute/MIES,https://api.github.com/repos/AllenInstitute/MIES,opened,Improve function documentation for channel numbers,CodeQuality,"Functions that take channel number as argument often do not precisely specify if they take

- GUI channel numbers
- hardware channel numbers
- active channel number (index in config wave)

While GUI and Hardware channel numbers are the same for DAC/ADC they are not for TTL + ITC.

",1.0,"Improve function documentation for channel numbers - Functions that take channel number as argument often do not precisely specify if they take

- GUI channel numbers
- hardware channel numbers
- active channel number (index in config wave)

While GUI and Hardware channel numbers are the same for DAC/ADC they are not for TTL + ITC.

",0,improve function documentation for channel numbers   functions that take channel number as argument often do not precisely specify if they take      gui channel numbers    hardware channel numbers    active channel number  index in config wave     while gui and hardware channel numbers are the same for dac adc they are not for ttl   itc     ,0
5805,2974838461.0,IssuesEvent,2015-07-15 05:13:26,golang/go,https://api.github.com/repos/golang/go,closed,time: document how to render milli/micro/nano in time.Format,Documentation,"The reference time described in the docstring for Format doesn't provide a value for nanoseconds. This hides the functionality provided by the Format function to render milli, micro and nanoseconds.

This has led to some confusion that Format can't handle sub-second precision: https://groups.google.com/forum/#!topic/golang-nuts/TIinEnPu5wE

One option for a solution might just be to add '.000000000' to the reference time in the doc comment.",1.0,"time: document how to render milli/micro/nano in time.Format - The reference time described in the docstring for Format doesn't provide a value for nanoseconds. This hides the functionality provided by the Format function to render milli, micro and nanoseconds.

This has led to some confusion that Format can't handle sub-second precision: https://groups.google.com/forum/#!topic/golang-nuts/TIinEnPu5wE

One option for a solution might just be to add '.000000000' to the reference time in the doc comment.",1,time  document how to render milli micro nano in time format   the reference time described in the docstring for format doesn t provide a value for nanoseconds  this hides the functionality provided by the format function to render milli  micro and nanoseconds     this has led to some confusion that format can t handle sub second precision       one option for a solution might just be to add      to the reference time in the doc comment ,1
543499,15883071269.0,IssuesEvent,2021-04-09 16:52:40,musescore/MuseScore,https://api.github.com/repos/musescore/MuseScore,closed,[MU4 Issue] Hiding voices doesn't do anything,Medium Priority,"**Describe the bug**
Hiding voices doesn't do anything

**To Reproduce**
Steps to reproduce the behavior:
1. Create a score
2. Add notes to Voice 1 and Voice 2
3. Open Parts dialog
4. Hide Voice 1

**Expected behavior**
Hidden voices should not be visible on the Part

**Screenshots**
![2021-03-31 05_27_06-Window](https://user-images.githubusercontent.com/71372310/113081806-09eb8b00-91e2-11eb-8902-a905c2f90899.jpg)



**Desktop (please complete the following information):**
MacOS
Windows 10

**Additional context**
Add any other context about the problem here.
",1.0,"[MU4 Issue] Hiding voices doesn't do anything - **Describe the bug**
Hiding voices doesn't do anything

**To Reproduce**
Steps to reproduce the behavior:
1. Create a score
2. Add notes to Voice 1 and Voice 2
3. Open Parts dialog
4. Hide Voice 1

**Expected behavior**
Hidden voices should not be visible on the Part

**Screenshots**
![2021-03-31 05_27_06-Window](https://user-images.githubusercontent.com/71372310/113081806-09eb8b00-91e2-11eb-8902-a905c2f90899.jpg)



**Desktop (please complete the following information):**
MacOS
Windows 10

**Additional context**
Add any other context about the problem here.
",0,  hiding voices doesn t do anything     describe the bug    hiding voices doesn t do anything      to reproduce    steps to reproduce the behavior      create a score     add notes to voice   and voice       open parts dialog     hide voice        expected behavior    hidden voices should not be visible on the part      screenshots                  desktop  please complete the following information      macos  windows        additional context    add any other context about the problem here   ,0
81979,10265943341.0,IssuesEvent,2019-08-22 20:08:58,golang/go,https://api.github.com/repos/golang/go,closed,"os, syscall: changes to os.Err* and syscall.Errno not mentioned in release notes and syscall package docs",Documentation NeedsFix release-blocker,"The changes made to the `os` and `syscall` package for #30322 are not mentioned in the Go 1.13 release notes, nor in the documentation for `syscall.Errno` or the `syscall` package.

Because users in general cannot redefine the error behavior of the errors defined by their dependencies, as a user I would not expect `syscall.Errno` errors to be defined as equivalent to errors defined in the higher-level `os` package. As noted in #32463 and #33411, the fact that they are has significant, non-trivial implications.

If `errors.Is` is now recommended and supported for checking the properties of `syscall.Errno` errors, the `syscall.Errno` documentation and the Go 1.13 release notes should be updated to mention that.

CC @neild @jba @mpvl @rsc @andybons @ianlancetaylor ",1.0,"os, syscall: changes to os.Err* and syscall.Errno not mentioned in release notes and syscall package docs - The changes made to the `os` and `syscall` package for #30322 are not mentioned in the Go 1.13 release notes, nor in the documentation for `syscall.Errno` or the `syscall` package.

Because users in general cannot redefine the error behavior of the errors defined by their dependencies, as a user I would not expect `syscall.Errno` errors to be defined as equivalent to errors defined in the higher-level `os` package. As noted in #32463 and #33411, the fact that they are has significant, non-trivial implications.

If `errors.Is` is now recommended and supported for checking the properties of `syscall.Errno` errors, the `syscall.Errno` documentation and the Go 1.13 release notes should be updated to mention that.

CC @neild @jba @mpvl @rsc @andybons @ianlancetaylor ",1,os  syscall  changes to os err  and syscall errno not mentioned in release notes and syscall package docs   the changes made to the  os  and  syscall  package for    are not mentioned in the go     release notes  nor in the documentation for  syscall errno  or the  syscall  package     because users in general cannot redefine the error behavior of the errors defined by their dependencies  as a user i would not expect  syscall errno  errors to be defined as equivalent to errors defined in the higher level  os  package  as noted in    and     the fact that they are has significant  non trivial implications     if  errors is  is now recommended and supported for checking the properties of  syscall errno  errors  the  syscall errno  documentation and the go     release notes should be updated to mention that     cc  neild  jba  mpvl  rsc  andybons  ianlancetaylor ,1
30283,14500249536.0,IssuesEvent,2020-12-11 17:46:49,sergiorribeiro/webmetry,https://api.github.com/repos/sergiorribeiro/webmetry,opened,[SidekiqJob] OtherTransaction/SidekiqJob/SyncAccountsJob/perform,prodops transaction-performance,"The transaction **`OtherTransaction/SidekiqJob/SyncAccountsJob/perform` (SidekiqJob)** violated a performance threshold.

## Weekly transaction performance:

### Evolution graph (percentile 95):

```
[2020-12-04] ~ [2020-12-11]▐████████████████████3.7 hr
[2020-11-27] ~ [2020-12-04]▐█████████████████  3.2 hr
[2020-11-20] ~ [2020-11-27]▐██████████████     2.7 hr
[2020-11-13] ~ [2020-11-20]▐██████████████     2.7 hr

```
### Weekly indicators:

| Indicator | Week -3 | Week -2 | Week -1 | Week 0 |
|-|-|-|-|-|
| Above average hits | 19 | 18 | 21 | 20 |
| Max | 3.0 hr | 2.7 hr | 3.2 hr | 3.7 hr |
| Average | 2.2 hr | 2.2 hr | 2.1 hr | 2.5 hr |
| Percentile 95 | 2.7 hr | 2.7 hr | 3.2 hr | 3.7 hr |

### Month totals:

| Indicator | Value |
|-|-|
| Max | 3.7 hr |
| Average | 2.2 hr |
| Percentile 95 | 3.2 hr |

## Violations:
- [2020-12-11] Maximum execution duration during the current week exceded reference       value of 1.0 hr by 2.7 hr <!-- /// -->

<!-- [EPID:4c8e6bbe3cc3ecaae12d95052e3a0a000f6ff836] -->",True,"[SidekiqJob] OtherTransaction/SidekiqJob/SyncAccountsJob/perform - The transaction **`OtherTransaction/SidekiqJob/SyncAccountsJob/perform` (SidekiqJob)** violated a performance threshold.

## Weekly transaction performance:

### Evolution graph (percentile 95):

```
[2020-12-04] ~ [2020-12-11]▐████████████████████3.7 hr
[2020-11-27] ~ [2020-12-04]▐█████████████████  3.2 hr
[2020-11-20] ~ [2020-11-27]▐██████████████     2.7 hr
[2020-11-13] ~ [2020-11-20]▐██████████████     2.7 hr

```
### Weekly indicators:

| Indicator | Week -3 | Week -2 | Week -1 | Week 0 |
|-|-|-|-|-|
| Above average hits | 19 | 18 | 21 | 20 |
| Max | 3.0 hr | 2.7 hr | 3.2 hr | 3.7 hr |
| Average | 2.2 hr | 2.2 hr | 2.1 hr | 2.5 hr |
| Percentile 95 | 2.7 hr | 2.7 hr | 3.2 hr | 3.7 hr |

### Month totals:

| Indicator | Value |
|-|-|
| Max | 3.7 hr |
| Average | 2.2 hr |
| Percentile 95 | 3.2 hr |

## Violations:
- [2020-12-11] Maximum execution duration during the current week exceded reference       value of 1.0 hr by 2.7 hr <!-- /// -->

<!-- [EPID:4c8e6bbe3cc3ecaae12d95052e3a0a000f6ff836] -->",0,  othertransaction sidekiqjob syncaccountsjob perform   the transaction    othertransaction sidekiqjob syncaccountsjob perform   sidekiqjob    violated a performance threshold      weekly transaction performance       evolution graph  percentile               ▐████████████████████    hr      ▐█████████████████      hr      ▐██████████████         hr      ▐██████████████         hr          weekly indicators     indicator   week      week      week      week                   above average hits                     max       hr       hr       hr       hr     average       hr       hr       hr       hr     percentile         hr       hr       hr       hr        month totals     indicator   value           max       hr     average       hr     percentile         hr       violations      maximum execution duration during the current week exceded reference       value of     hr by     hr     ,0
81947,10265284653.0,IssuesEvent,2019-08-22 18:28:08,golang/go,https://api.github.com/repos/golang/go,reopened,doc: update release notes for library support for new literals,Documentation release-blocker,"The release notes don't mention all the library changes related to the new number literals.
In particular there is new printing in fmt, new parsing in strconv, math/big, and text/scanner.

I started to update the notes but there's a lot to add. Filing so I don't forget.",1.0,"doc: update release notes for library support for new literals - The release notes don't mention all the library changes related to the new number literals.
In particular there is new printing in fmt, new parsing in strconv, math/big, and text/scanner.

I started to update the notes but there's a lot to add. Filing so I don't forget.",1,doc  update release notes for library support for new literals   the release notes don t mention all the library changes related to the new number literals  in particular there is new printing in fmt  new parsing in strconv  math big  and text scanner   i started to update the notes but there s a lot to add  filing so i don t forget ,1
467106,13441189512.0,IssuesEvent,2020-09-08 03:21:02,MicrosoftDocs/typography-issues,https://api.github.com/repos/MicrosoftDocs/typography-issues,closed,Soften Mac cmap requirements,OpenType spec Priority 3,"The ""Macintosh 'cmap' Table"" section on this Recommendations page says:

""When building a font containing Roman characters that will be used on the Macintosh, an additional subtable is required, specifying platform ID of 1 and encoding ID of 0 (this subtable may use 'cmap' formats 0, 2, 4, or 6).""

Since we are revisiting the platform ID 1 'name' requirements (https://github.com/MicrosoftDocs/typography-issues/issues/443), it would be a good time to revise the above platform ID 1 'cmap' requirement as well.

I see several system fonts on my Mac (macOS 10.15.6) which support Latin but don’t have a platform ID 1 cmap subtable, which suggests that such a subtable isn’t always needed for such fonts on modern macOS versions.

The rest of that section is quaint and outdated as well:

""In order for the Macintosh 'cmap' table to be useful, the glyphs required for the Macintosh must have glyph indices less than 256 (since the 'cmap' subtable format 0 uses uint8 indices and therefore cannot index any glyph above 255).
The Apple 'cmap' subtable should be constructed according to Apple guidelines.""

and I'd recommend it simply be removed (the first sentence assumes only format 0 is needed, possibly dating from TT's early days; the second sentence seems unnecessary: all the info to construct platform ID 1 cmap subtables should already be in the OT 'cmap' spec).

---
#### Document Details

⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*

* ID: 95e88b53-d670-0240-422c-72748258ab2a
* Version Independent ID: b5fff1ee-cf03-e424-a2dc-aee58e0429e4
* Content: [Recommendations for OpenType Fonts - Typography](https://docs.microsoft.com/en-us/typography/opentype/spec/recom)
* Content Source: [typographydocs/opentype/spec/recom.md](https://github.com/MicrosoftDocs/typography/blob/live/typographydocs/opentype/spec/recom.md)
* Product: **typography**
* GitHub Login: @PeterCon
* Microsoft Alias: **PeterCon**",1.0,"Soften Mac cmap requirements - The ""Macintosh 'cmap' Table"" section on this Recommendations page says:

""When building a font containing Roman characters that will be used on the Macintosh, an additional subtable is required, specifying platform ID of 1 and encoding ID of 0 (this subtable may use 'cmap' formats 0, 2, 4, or 6).""

Since we are revisiting the platform ID 1 'name' requirements (https://github.com/MicrosoftDocs/typography-issues/issues/443), it would be a good time to revise the above platform ID 1 'cmap' requirement as well.

I see several system fonts on my Mac (macOS 10.15.6) which support Latin but don’t have a platform ID 1 cmap subtable, which suggests that such a subtable isn’t always needed for such fonts on modern macOS versions.

The rest of that section is quaint and outdated as well:

""In order for the Macintosh 'cmap' table to be useful, the glyphs required for the Macintosh must have glyph indices less than 256 (since the 'cmap' subtable format 0 uses uint8 indices and therefore cannot index any glyph above 255).
The Apple 'cmap' subtable should be constructed according to Apple guidelines.""

and I'd recommend it simply be removed (the first sentence assumes only format 0 is needed, possibly dating from TT's early days; the second sentence seems unnecessary: all the info to construct platform ID 1 cmap subtables should already be in the OT 'cmap' spec).

---
#### Document Details

⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*

* ID: 95e88b53-d670-0240-422c-72748258ab2a
* Version Independent ID: b5fff1ee-cf03-e424-a2dc-aee58e0429e4
* Content: [Recommendations for OpenType Fonts - Typography](https://docs.microsoft.com/en-us/typography/opentype/spec/recom)
* Content Source: [typographydocs/opentype/spec/recom.md](https://github.com/MicrosoftDocs/typography/blob/live/typographydocs/opentype/spec/recom.md)
* Product: **typography**
* GitHub Login: @PeterCon
* Microsoft Alias: **PeterCon**",0,soften mac cmap requirements   the  macintosh  cmap  table  section on this recommendations page says      when building a font containing roman characters that will be used on the macintosh  an additional subtable is required  specifying platform id of   and encoding id of    this subtable may use  cmap  formats          or         since we are revisiting the platform id    name  requirements    it would be a good time to revise the above platform id    cmap  requirement as well     i see several system fonts on my mac  macos        which support latin but don’t have a platform id   cmap subtable  which suggests that such a subtable isn’t always needed for such fonts on modern macos versions     the rest of that section is quaint and outdated as well      in order for the macintosh  cmap  table to be useful  the glyphs required for the macintosh must have glyph indices less than    since the  cmap  subtable format   uses   indices and therefore cannot index any glyph above      the apple  cmap  subtable should be constructed according to apple guidelines      and i d recommend it simply be removed  the first sentence assumes only format   is needed  possibly dating from tt s early days  the second sentence seems unnecessary  all the info to construct platform id   cmap subtables should already be in the ot  cmap  spec                document details    ⚠  do not edit this section  it is required for docs microsoft com ➟ github issue linking        id               version independent id               content         content source         product    typography      github login   petercon    microsoft alias    petercon  ,0
202515,23077428187.0,IssuesEvent,2022-07-26 01:58:58,AlexRogalskiy/github-action-node-dependency,https://api.github.com/repos/AlexRogalskiy/github-action-node-dependency,reopened,CVE-2021-35065 (High) detected in glob-parent-5.1.2.tgz,security vulnerability,"## CVE-2021-35065 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>glob-parent-5.1.2.tgz</b></p></summary>

<p>Extract the non-magic parent path from a glob string.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz"">https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz</a></p>
<p>

Dependency Hierarchy:
  - eslint-7.24.0.tgz (Root Library)
    - :x: **glob-parent-5.1.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://api.github.com/repos/AlexRogalskiy/github-action-node-dependency/git/commits/7557b6be7ecb09025024a5fb56ec93d5aba43c03"">7557b6be7ecb09025024a5fb56ec93d5aba43c03</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The package glob-parent before  6.0.1 are vulnerable to Regular Expression Denial of Service (ReDoS) 

<p>Publish Date: 2021-06-22
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35065>CVE-2021-35065</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/advisories/GHSA-cj88-88mr-972w"">https://github.com/advisories/GHSA-cj88-88mr-972w</a></p>
<p>Release Date: 2021-06-22</p>
<p>Fix Resolution (glob-parent): 6.0.1</p>
<p>Direct dependency fix Resolution (eslint): 8.0.0</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2021-35065 (High) detected in glob-parent-5.1.2.tgz - ## CVE-2021-35065 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>glob-parent-5.1.2.tgz</b></p></summary>

<p>Extract the non-magic parent path from a glob string.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz"">https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz</a></p>
<p>

Dependency Hierarchy:
  - eslint-7.24.0.tgz (Root Library)
    - :x: **glob-parent-5.1.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://api.github.com/repos/AlexRogalskiy/github-action-node-dependency/git/commits/7557b6be7ecb09025024a5fb56ec93d5aba43c03"">7557b6be7ecb09025024a5fb56ec93d5aba43c03</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The package glob-parent before  6.0.1 are vulnerable to Regular Expression Denial of Service (ReDoS) 

<p>Publish Date: 2021-06-22
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35065>CVE-2021-35065</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/advisories/GHSA-cj88-88mr-972w"">https://github.com/advisories/GHSA-cj88-88mr-972w</a></p>
<p>Release Date: 2021-06-22</p>
<p>Fix Resolution (glob-parent): 6.0.1</p>
<p>Direct dependency fix Resolution (eslint): 8.0.0</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in glob parent       tgz      cve       high severity vulnerability     vulnerable library    glob parent       tgz      extract the non magic parent path from a glob string    library home page   a href       dependency hierarchy      eslint       tgz  root library         x    glob parent       tgz    vulnerable library   found in head commit   a href     found in base branch   master              vulnerability details         the package glob parent before        are vulnerable to regular expression denial of service  redos     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  glob parent           direct dependency fix resolution  eslint                       step up your open source security game with mend    ,0
720864,24809271767.0,IssuesEvent,2022-10-25 08:09:16,YangCatalog/backend,https://api.github.com/repos/YangCatalog/backend,closed,Avoid re-parsing modules just to add implementations,enhancement Priority: Low,"We determine whether to parse a vendor module by trying to look it up by file name and platform. If are unable to find either of these, the module gets fully parsed. This means that each module gets parsed once for every platform that implements it.

We should avoid doing a full parse of any module we've already seen even if implementation metadata is new. We need a way to update only implementation metadata that's dumped into `normal.json` without having to provide all the module properties that go into `prepare.json`.
The `FileHasher` must also be able to tell us whether we've parsed a vendor module before even if the metadata was previously for a different platform.",1.0,"Avoid re-parsing modules just to add implementations - We determine whether to parse a vendor module by trying to look it up by file name and platform. If are unable to find either of these, the module gets fully parsed. This means that each module gets parsed once for every platform that implements it.

We should avoid doing a full parse of any module we've already seen even if implementation metadata is new. We need a way to update only implementation metadata that's dumped into `normal.json` without having to provide all the module properties that go into `prepare.json`.
The `FileHasher` must also be able to tell us whether we've parsed a vendor module before even if the metadata was previously for a different platform.",0,avoid re parsing modules just to add implementations   we determine whether to parse a vendor module by trying to look it up by file name and platform  if are unable to find either of these  the module gets fully parsed  this means that each module gets parsed once for every platform that implements it     we should avoid doing a full parse of any module we ve already seen even if implementation metadata is new  we need a way to update only implementation metadata that s dumped into  normal json  without having to provide all the module properties that go into  prepare json    the  filehasher  must also be able to tell us whether we ve parsed a vendor module before even if the metadata was previously for a different platform ,0
54426,11233634951.0,IssuesEvent,2020-01-09 01:59:22,Regalis11/Barotrauma,https://api.github.com/repos/Regalis11/Barotrauma,reopened,Using a custom built drone is causing the game to crash.,Code Crash,"I made a drone. It was working fine before, now the game crashes when I use it. Below are the crash logs and sub files.

I have also included the main sub that has the drone's control terminal, just in case you want to do in-game testing, or just in case the crash is due to a combination of both subs. This statement is based on the advice hubismal gave in response to my post on Discord, as I recently made some changes (including but not limited to inventory changes) to the main sub.

The name of the drone is RD 1.3 and the main sub with the control terminal is the Dart 2.10.

As for when the game crashed and how to possibly reproduce it, I believe it happened most often when I was trying to dock the drone.

The game version is 0.9.5.1 and I am using Windows 10.

Thanks for taking a look at it.

[mrjpjr drone sub crash files.zip](https://github.com/Regalis11/Barotrauma/files/3950386/mrjpjr.drone.sub.crash.files.zip)


- [x] I have searched the issue tracker to check if the issue has already been reported.

**Description**
A clear and concise description of what the bug is.

**Steps To Reproduce**
If possible, describe how the developers can reproduce the issue. It is often extremely hard to fix a bug if we don't know how to make it happen.

**Version**
Which version of the game did the bug happen in. You can see the version number at the bottom left corner of the main menu, and in a file called ""Version.txt"" inside the game folder.
Also, please include the operating system you're using (Windows/Linux/Mac).

**Additional information**
Add any other context about the problem here.
",1.0,"Using a custom built drone is causing the game to crash. - I made a drone. It was working fine before, now the game crashes when I use it. Below are the crash logs and sub files.

I have also included the main sub that has the drone's control terminal, just in case you want to do in-game testing, or just in case the crash is due to a combination of both subs. This statement is based on the advice hubismal gave in response to my post on Discord, as I recently made some changes (including but not limited to inventory changes) to the main sub.

The name of the drone is RD 1.3 and the main sub with the control terminal is the Dart 2.10.

As for when the game crashed and how to possibly reproduce it, I believe it happened most often when I was trying to dock the drone.

The game version is 0.9.5.1 and I am using Windows 10.

Thanks for taking a look at it.

[mrjpjr drone sub crash files.zip](https://github.com/Regalis11/Barotrauma/files/3950386/mrjpjr.drone.sub.crash.files.zip)


- [x] I have searched the issue tracker to check if the issue has already been reported.

**Description**
A clear and concise description of what the bug is.

**Steps To Reproduce**
If possible, describe how the developers can reproduce the issue. It is often extremely hard to fix a bug if we don't know how to make it happen.

**Version**
Which version of the game did the bug happen in. You can see the version number at the bottom left corner of the main menu, and in a file called ""Version.txt"" inside the game folder.
Also, please include the operating system you're using (Windows/Linux/Mac).

**Additional information**
Add any other context about the problem here.
",0,using a custom built drone is causing the game to crash    i made a drone  it was working fine before  now the game crashes when i use it  below are the crash logs and sub files     i have also included the main sub that has the drone s control terminal  just in case you want to do in game testing  or just in case the crash is due to a combination of both subs  this statement is based on the advice hubismal gave in response to my post on discord  as i recently made some changes  including but not limited to inventory changes  to the main sub     the name of the drone is rd     and the main sub with the control terminal is the dart         as for when the game crashed and how to possibly reproduce it  i believe it happened most often when i was trying to dock the drone     the game version is         and i am using windows       thanks for taking a look at it                  i have searched the issue tracker to check if the issue has already been reported       description    a clear and concise description of what the bug is       steps to reproduce    if possible  describe how the developers can reproduce the issue  it is often extremely hard to fix a bug if we don t know how to make it happen       version    which version of the game did the bug happen in  you can see the version number at the bottom left corner of the main menu  and in a file called  version txt  inside the game folder   also  please include the operating system you re using  windows linux mac        additional information    add any other context about the problem here   ,0
14688,2831388457.0,IssuesEvent,2015-05-24 15:53:22,nobodyguy/dslrdashboard,https://api.github.com/repos/nobodyguy/dslrdashboard,closed,Not connecting to D40,auto-migrated Priority-Medium Type-Defect,"```
What steps will reproduce the problem?
1. problem occurs every time
2.
3.

What is the expected output? What do you see instead?
I would expect the App to find my camera but it doesn't. Switching the D40 to M 
doesn't help either.

What version of the product are you using? On what operating system?
Samsung Galaxy Tab 3 7.0 (SM-T 110), Android 4.2.2

Please provide any additional information below.
- Connecting Galaxy Tab via USB
- Application is running
- when tapping on ""search for USB camera"" nothing happens at all
- is my tablet suitable?


```

Original issue reported on code.google.com by `mrt.jns...@gmail.com` on 16 Apr 2014 at 3:59",1.0,"Not connecting to D40 - ```
What steps will reproduce the problem?
1. problem occurs every time
2.
3.

What is the expected output? What do you see instead?
I would expect the App to find my camera but it doesn't. Switching the D40 to M 
doesn't help either.

What version of the product are you using? On what operating system?
Samsung Galaxy Tab 3 7.0 (SM-T 110), Android 4.2.2

Please provide any additional information below.
- Connecting Galaxy Tab via USB
- Application is running
- when tapping on ""search for USB camera"" nothing happens at all
- is my tablet suitable?


```

Original issue reported on code.google.com by `mrt.jns...@gmail.com` on 16 Apr 2014 at 3:59",0,not connecting to         what steps will reproduce the problem     problem occurs every time        what is the expected output  what do you see instead  i would expect the app to find my camera but it doesn t  switching the   to m  doesn t help either   what version of the product are you using  on what operating system  samsung galaxy tab        sm t     android        please provide any additional information below    connecting galaxy tab via usb   application is running   when tapping on  search for usb camera  nothing happens at all   is my tablet suitable         original issue reported on code google com by  mrt jns    gmail com  on   apr   at    ,0
35613,6485394162.0,IssuesEvent,2017-08-19 09:51:17,golang/go,https://api.github.com/repos/golang/go,opened,doc: Install from source doc at golang.org/doc inconsistent with install output,Documentation,"### What version of Go are you using (`go version`)?
go version go1.8.3 darwin/amd64

### Does this issue reproduce with the latest release?
Yes.

### What operating system and processor architecture are you using (`go env`)?
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""

### What did you do?
Installed Go from source after a `git clone` (in addition to a system Go).
```bash
$ cd ~/dev/go/src
$ ./make.bash
```

### What did you expect to see?
The docs at https://golang.org/doc/install/source#install says:

> If all goes well, it will finish by printing output like:

```
ALL TESTS PASSED

---
Installed Go for linux/amd64 in /home/you/go.
Installed commands in /home/you/go/bin.
*** You need to add /home/you/go/bin to your $PATH. ***
```
### What did you see instead?
It's really minor, but after a source install I don't see the `*** You need to add /home/you/go/bin to your $PATH. ***` line. Either there is a bug printing the line or the doc is outdated? I was making some standard library changes and building the source, but using my system go `/usr/local/bin/go` to test changes instead of the newly-built binary and wondering why the changes weren't applied :) The line helps to avoid this sort of beginner mistake, especially when you have multiple Go versions installed. 

Thanks!
",1.0,"doc: Install from source doc at golang.org/doc inconsistent with install output - ### What version of Go are you using (`go version`)?
go version go1.8.3 darwin/amd64

### Does this issue reproduce with the latest release?
Yes.

### What operating system and processor architecture are you using (`go env`)?
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""

### What did you do?
Installed Go from source after a `git clone` (in addition to a system Go).
```bash
$ cd ~/dev/go/src
$ ./make.bash
```

### What did you expect to see?
The docs at https://golang.org/doc/install/source#install says:

> If all goes well, it will finish by printing output like:

```
ALL TESTS PASSED

---
Installed Go for linux/amd64 in /home/you/go.
Installed commands in /home/you/go/bin.
*** You need to add /home/you/go/bin to your $PATH. ***
```
### What did you see instead?
It's really minor, but after a source install I don't see the `*** You need to add /home/you/go/bin to your $PATH. ***` line. Either there is a bug printing the line or the doc is outdated? I was making some standard library changes and building the source, but using my system go `/usr/local/bin/go` to test changes instead of the newly-built binary and wondering why the changes weren't applied :) The line helps to avoid this sort of beginner mistake, especially when you have multiple Go versions installed. 

Thanks!
",1,doc  install from source doc at golang org doc inconsistent with install output       what version of go are you using   go version     go version       darwin          does this issue reproduce with the latest release   yes         what operating system and processor architecture are you using   go env     gohostarch      gohostos  darwin   goos  darwin         what did you do   installed go from source after a  git clone   in addition to a system go       bash    cd   dev go src      make bash             what did you expect to see   the docs at   says       if all goes well  it will finish by printing output like          all tests passed         installed go for linux   in  home you go   installed commands in  home you go bin       you need to add  home you go bin to your  path                what did you see instead   it s really minor  but after a source install i don t see the      you need to add  home you go bin to your  path       line  either there is a bug printing the line or the doc is outdated  i was making some standard library changes and building the source  but using my system go   usr local bin go  to test changes instead of the newly built binary and wondering why the changes weren t applied    the line helps to avoid this sort of beginner mistake  especially when you have multiple go versions installed      thanks   ,1
783702,27542630629.0,IssuesEvent,2023-03-07 09:36:34,gardener/machine-controller-manager-provider-aws,https://api.github.com/repos/gardener/machine-controller-manager-provider-aws,closed,Provide config for AWS Metadata version: V2 only,kind/enhancement priority/1 needs/planning,"**What would you like to be added**:
The EC2 instances should be able to configured with ""Metadata version: V2 only"" as seen in attached screenshot (taken from AWS console).
![image](https://user-images.githubusercontent.com/1555662/202209258-5c2bb23e-520b-48d6-8bc7-9d54aa5a75e4.png)

**Why is this needed**:
For security improvements, we need to disable the [AWS metadata service](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instancedata-data-retrieval.html) in v1.",1.0,"Provide config for AWS Metadata version: V2 only - **What would you like to be added**:
The EC2 instances should be able to configured with ""Metadata version: V2 only"" as seen in attached screenshot (taken from AWS console).
![image](https://user-images.githubusercontent.com/1555662/202209258-5c2bb23e-520b-48d6-8bc7-9d54aa5a75e4.png)

**Why is this needed**:
For security improvements, we need to disable the [AWS metadata service](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instancedata-data-retrieval.html) in v1.",0,provide config for aws metadata version    only     what would you like to be added     the   instances should be able to configured with  metadata version    only  as seen in attached screenshot  taken from aws console              why is this needed     for security improvements  we need to disable the     in   ,0
19235,4357258516.0,IssuesEvent,2016-08-02 00:47:06,golang/go,https://api.github.com/repos/golang/go,closed,doc: specify new automatic HTTP/2 behavior of net/http.Server.Serve,Documentation,"Please answer these questions before submitting your issue. Thanks!

1. What version of Go are you using (`go version`)?
go version go1.7rc3 linux/amd64

2. What operating system and processor architecture are you using (`go env`)?
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""

3. What did you do?

Compile github.com/mholt/caddy

4. What did you expect to see?

Caddy serves HTTP/2.

5. What did you see instead?

Caddy serves HTTP/1.1 only. 


The semantics of net/http/(*Server).Serve() [have changed](https://tip.golang.org/pkg/net/http/#Server.Serve):

>  If srv.TLSConfig is non-nil and doesn't include the string ""h2"" in Config.NextProtos, HTTP/2 support is not enabled. 

Apparently that was not the case with Go 1.6. Caddy used to use (or still uses) an empty slice for NextProtos and HTTP/2 worked fine. Adding ""h2"" works.

**I did not expect this change**, as it is not mentioned in the Go 1.7 Release Notes DRAFT. Please add a note about that changed behaviour.

Thanks

See also mholt/caddy#975.",1.0,"doc: specify new automatic HTTP/2 behavior of net/http.Server.Serve - Please answer these questions before submitting your issue. Thanks!

1. What version of Go are you using (`go version`)?
go version go1.7rc3 linux/amd64

2. What operating system and processor architecture are you using (`go env`)?
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""

3. What did you do?

Compile github.com/mholt/caddy

4. What did you expect to see?

Caddy serves HTTP/2.

5. What did you see instead?

Caddy serves HTTP/1.1 only. 


The semantics of net/http/(*Server).Serve() [have changed](https://tip.golang.org/pkg/net/http/#Server.Serve):

>  If srv.TLSConfig is non-nil and doesn't include the string ""h2"" in Config.NextProtos, HTTP/2 support is not enabled. 

Apparently that was not the case with Go 1.6. Caddy used to use (or still uses) an empty slice for NextProtos and HTTP/2 worked fine. Adding ""h2"" works.

**I did not expect this change**, as it is not mentioned in the Go 1.7 Release Notes DRAFT. Please add a note about that changed behaviour.

Thanks

See also mholt/caddy#975.",1,doc  specify new automatic http   behavior of net http server serve   please answer these questions before submitting your issue  thanks        what version of go are you using   go version     go version     linux         what operating system and processor architecture are you using   go env     gohostarch      gohostos  linux        what did you do     compile github com mholt caddy       what did you expect to see     caddy serves http          what did you see instead     caddy serves http     only        the semantics of net http   server  serve             if srv tlsconfig is non nil and doesn t include the string     in config nextprotos  http   support is not enabled      apparently that was not the case with go      caddy used to use  or still uses  an empty slice for nextprotos and http   worked fine  adding     works       i did not expect this change    as it is not mentioned in the go     release notes draft  please add a note about that changed behaviour     thanks    see also mholt caddy   ,1
277988,30702092244.0,IssuesEvent,2023-07-27 01:01:40,feemstr/pyprojects-jira,https://api.github.com/repos/feemstr/pyprojects-jira,opened,certifi-2022.12.7-py3-none-any.whl: 1 vulnerabilities (highest severity is: 7.5),Mend: dependency security vulnerability,"<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>certifi-2022.12.7-py3-none-any.whl</b></p></summary>

<p>Python package for providing Mozilla's CA Bundle.</p>
<p>Library home page: <a href=""https://files.pythonhosted.org/packages/71/4c/3db2b8021bd6f2f0ceb0e088d6b2d49147671f25832fb17970e9b583d742/certifi-2022.12.7-py3-none-any.whl"">https://files.pythonhosted.org/packages/71/4c/3db2b8021bd6f2f0ceb0e088d6b2d49147671f25832fb17970e9b583d742/certifi-2022.12.7-py3-none-any.whl</a></p>
<p>


<p>Found in HEAD commit: <a href=""https://github.com/feemstr/pyprojects-jira/commit/c27d0db6ae7d771ddcdbe344ed839d25efb9c799"">c27d0db6ae7d771ddcdbe344ed839d25efb9c799</a></p></details>

## Vulnerabilities

| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (certifi version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2023-37920](https://www.mend.io/vulnerability-database/CVE-2023-37920) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | certifi-2022.12.7-py3-none-any.whl | Direct | certifi - 2023.7.22 | &#10060; |


## Details

<details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2023-37920</summary>


###  Vulnerable Library - <b>certifi-2022.12.7-py3-none-any.whl</b></p>

<p>Python package for providing Mozilla's CA Bundle.</p>
<p>Library home page: <a href=""https://files.pythonhosted.org/packages/71/4c/3db2b8021bd6f2f0ceb0e088d6b2d49147671f25832fb17970e9b583d742/certifi-2022.12.7-py3-none-any.whl"">https://files.pythonhosted.org/packages/71/4c/3db2b8021bd6f2f0ceb0e088d6b2d49147671f25832fb17970e9b583d742/certifi-2022.12.7-py3-none-any.whl</a></p>
<p>

Dependency Hierarchy:
  - :x: **certifi-2022.12.7-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/feemstr/pyprojects-jira/commit/c27d0db6ae7d771ddcdbe344ed839d25efb9c799"">c27d0db6ae7d771ddcdbe344ed839d25efb9c799</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
Certifi is a curated collection of Root Certificates for validating the trustworthiness of SSL certificates while verifying the identity of TLS hosts. Certifi prior to version 2023.07.22 recognizes ""e-Tugra"" root certificates. e-Tugra's root certificates were subject to an investigation prompted by reporting of security issues in their systems. Certifi 2023.07.22 removes root certificates from ""e-Tugra"" from the root store.

<p>Publish Date: 2023-07-25
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-37920>CVE-2023-37920</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: High
  - Availability Impact: None
</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/certifi/python-certifi/security/advisories/GHSA-xqr8-7jwr-rhp7"">https://github.com/certifi/python-certifi/security/advisories/GHSA-xqr8-7jwr-rhp7</a></p>
<p>Release Date: 2023-07-25</p>
<p>Fix Resolution: certifi - 2023.7.22</p>

</p>

<p></p>

</details>",True,"certifi-2022.12.7-py3-none-any.whl: 1 vulnerabilities (highest severity is: 7.5) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>certifi-2022.12.7-py3-none-any.whl</b></p></summary>

<p>Python package for providing Mozilla's CA Bundle.</p>
<p>Library home page: <a href=""https://files.pythonhosted.org/packages/71/4c/3db2b8021bd6f2f0ceb0e088d6b2d49147671f25832fb17970e9b583d742/certifi-2022.12.7-py3-none-any.whl"">https://files.pythonhosted.org/packages/71/4c/3db2b8021bd6f2f0ceb0e088d6b2d49147671f25832fb17970e9b583d742/certifi-2022.12.7-py3-none-any.whl</a></p>
<p>


<p>Found in HEAD commit: <a href=""https://github.com/feemstr/pyprojects-jira/commit/c27d0db6ae7d771ddcdbe344ed839d25efb9c799"">c27d0db6ae7d771ddcdbe344ed839d25efb9c799</a></p></details>

## Vulnerabilities

| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (certifi version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2023-37920](https://www.mend.io/vulnerability-database/CVE-2023-37920) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | certifi-2022.12.7-py3-none-any.whl | Direct | certifi - 2023.7.22 | &#10060; |


## Details

<details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2023-37920</summary>


###  Vulnerable Library - <b>certifi-2022.12.7-py3-none-any.whl</b></p>

<p>Python package for providing Mozilla's CA Bundle.</p>
<p>Library home page: <a href=""https://files.pythonhosted.org/packages/71/4c/3db2b8021bd6f2f0ceb0e088d6b2d49147671f25832fb17970e9b583d742/certifi-2022.12.7-py3-none-any.whl"">https://files.pythonhosted.org/packages/71/4c/3db2b8021bd6f2f0ceb0e088d6b2d49147671f25832fb17970e9b583d742/certifi-2022.12.7-py3-none-any.whl</a></p>
<p>

Dependency Hierarchy:
  - :x: **certifi-2022.12.7-py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/feemstr/pyprojects-jira/commit/c27d0db6ae7d771ddcdbe344ed839d25efb9c799"">c27d0db6ae7d771ddcdbe344ed839d25efb9c799</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
Certifi is a curated collection of Root Certificates for validating the trustworthiness of SSL certificates while verifying the identity of TLS hosts. Certifi prior to version 2023.07.22 recognizes ""e-Tugra"" root certificates. e-Tugra's root certificates were subject to an investigation prompted by reporting of security issues in their systems. Certifi 2023.07.22 removes root certificates from ""e-Tugra"" from the root store.

<p>Publish Date: 2023-07-25
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-37920>CVE-2023-37920</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: High
  - Availability Impact: None
</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/certifi/python-certifi/security/advisories/GHSA-xqr8-7jwr-rhp7"">https://github.com/certifi/python-certifi/security/advisories/GHSA-xqr8-7jwr-rhp7</a></p>
<p>Release Date: 2023-07-25</p>
<p>Fix Resolution: certifi - 2023.7.22</p>

</p>

<p></p>

</details>",0,certifi         none any whl    vulnerabilities  highest severity is             vulnerable library    certifi         none any whl      python package for providing mozilla s ca bundle    library home page   a href         found in head commit   a href        vulnerabilities    cve   severity     cvss   dependency   type   fixed in  certifi version    remediation available                                                                                             high         certifi         none any whl   direct   certifi                       details        cve             vulnerable library    certifi         none any whl     python package for providing mozilla s ca bundle    library home page   a href       dependency hierarchy       x    certifi         none any whl    vulnerable library   found in head commit   a href     found in base branch   main               vulnerability details        certifi is a curated collection of root certificates for validating the trustworthiness of ssl certificates while verifying the identity of tls hosts  certifi prior to version       recognizes  e tugra  root certificates  e tugra s root certificates were subject to an investigation prompted by reporting of security issues in their systems  certifi       removes root certificates from  e tugra  from the root store    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  high     availability impact  none   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution  certifi                   ,0
2234,3588114851.0,IssuesEvent,2016-01-30 20:06:16,elmsln/elmsln,https://api.github.com/repos/elmsln/elmsln,closed,allow for httprl non-blocking elmsln api calls,infrastructure,"enhance elmsln api to allow for the request wrapper to call multiple items in parallel via the httprl non-blocking call capability. This requires a higher level of bootstrap though (which HTTPL will do on demand) so it will slow down the overall initial bootstrap (technically). This is fine though if we're pinging all other systems / spidering over to all authorities (which if its going to sync data might take awhile per each one) so 1 full bootstrap that's blocking is better then N+1 network wide blocking calls.
- [x] support httprl option in _elmsln_api_request call
- [x] explore making this a different kind of request (because it needs to queue them all and THEN ship off which is just a different method of assembling things)",1.0,"allow for httprl non-blocking elmsln api calls - enhance elmsln api to allow for the request wrapper to call multiple items in parallel via the httprl non-blocking call capability. This requires a higher level of bootstrap though (which HTTPL will do on demand) so it will slow down the overall initial bootstrap (technically). This is fine though if we're pinging all other systems / spidering over to all authorities (which if its going to sync data might take awhile per each one) so 1 full bootstrap that's blocking is better then N+1 network wide blocking calls.
- [x] support httprl option in _elmsln_api_request call
- [x] explore making this a different kind of request (because it needs to queue them all and THEN ship off which is just a different method of assembling things)",0,allow for httprl non blocking elmsln api calls   enhance elmsln api to allow for the request wrapper to call multiple items in parallel via the httprl non blocking call capability  this requires a higher level of bootstrap though  which httpl will do on demand  so it will slow down the overall initial bootstrap  technically   this is fine though if we re pinging all other systems   spidering over to all authorities  which if its going to sync data might take awhile per each one  so   full bootstrap that s blocking is better then n   network wide blocking calls       support httprl option in  elmsln api request call      explore making this a different kind of request  because it needs to queue them all and then ship off which is just a different method of assembling things ,0
74447,7430323379.0,IssuesEvent,2018-03-25 00:04:12,tomato42/tlsfuzzer,https://api.github.com/repos/tomato42/tlsfuzzer,opened,Test with large signature algorithms list ,good first issue help wanted new-test-script,"https://blog.fuzzing-project.org/63-Stack-buffer-overflow-in-WolfSSL-before-3.13.0.html
https://github.com/wolfSSL/wolfssl/pull/1231/commits/9f7e40ad5c8097ff38d7caff4a9989db260981cc

wolfssl crashes when the sigalgs extension has more than 32 entries and it's compiled with asan",1.0,"Test with large signature algorithms list  - https://blog.fuzzing-project.org/63-Stack-buffer-overflow-in-WolfSSL-before-3.13.0.html
https://github.com/wolfSSL/wolfssl/pull/1231/commits/9f7e40ad5c8097ff38d7caff4a9989db260981cc

wolfssl crashes when the sigalgs extension has more than 32 entries and it's compiled with asan",0,test with large signature algorithms list            wolfssl crashes when the sigalgs extension has more than   entries and it s compiled with asan,0
152015,13441559559.0,IssuesEvent,2020-09-08 04:31:42,golang/go,https://api.github.com/repos/golang/go,opened,testing: document rules for using TB,Documentation,"There's rules about what a `TestFoo` may do with the `*testing.T` it is given. Some are documented (e.g. https://golang.org/pkg/testing/#T puts restrictions on invoking `Fatalf` and friends), but some are not (e.g. `Logf` and probably most other methods should not be called after `TestFoo` returns). Same applies to `*testing.B` and any future such values/types.

I came across this while trying to diagnose a problem that seems to be due to #40908, but realised I couldn't find the rules written down anywhere.",1.0,"testing: document rules for using TB - There's rules about what a `TestFoo` may do with the `*testing.T` it is given. Some are documented (e.g. https://golang.org/pkg/testing/#T puts restrictions on invoking `Fatalf` and friends), but some are not (e.g. `Logf` and probably most other methods should not be called after `TestFoo` returns). Same applies to `*testing.B` and any future such values/types.

I came across this while trying to diagnose a problem that seems to be due to #40908, but realised I couldn't find the rules written down anywhere.",1,testing  document rules for using tb   there s rules about what a  testfoo  may do with the   testing t  it is given  some are documented  e g    puts restrictions on invoking  fatalf  and friends   but some are not  e g   logf  and probably most other methods should not be called after  testfoo  returns   same applies to   testing b  and any future such values types     i came across this while trying to diagnose a problem that seems to be due to     but realised i couldn t find the rules written down anywhere ,1
5864,2981785951.0,IssuesEvent,2015-07-17 05:31:30,golang/go,https://api.github.com/repos/golang/go,closed,"cmd/go,cmd/trace: document the trace command",Documentation,"go help testflag does not mention the -trace flag

The output of go tool trace -help is unhelpful:

Usage of 'go tool trace':
Given a trace file produced by 'go test':
	go test -trace=trace.out pkg

Open a web browser displaying trace:
	go tool trace [flags] pkg.test trace.out

Flags:
	-http=addr: HTTP service address (e.g., ':6060')

Also, shortly after the 1.5 release, there should be a blog post about the feature.
",1.0,"cmd/go,cmd/trace: document the trace command - go help testflag does not mention the -trace flag

The output of go tool trace -help is unhelpful:

Usage of 'go tool trace':
Given a trace file produced by 'go test':
	go test -trace=trace.out pkg

Open a web browser displaying trace:
	go tool trace [flags] pkg.test trace.out

Flags:
	-http=addr: HTTP service address (e.g., ':6060')

Also, shortly after the 1.5 release, there should be a blog post about the feature.
",1,cmd go cmd trace  document the trace command   go help testflag does not mention the  trace flag    the output of go tool trace  help is unhelpful     usage of  go tool trace    given a trace file produced by  go test    	go test  trace trace out pkg    open a web browser displaying trace   	go tool trace   pkg test trace out    flags   	 http addr  http service address  e g            also  shortly after the     release  there should be a blog post about the feature   ,1
28530,5512073658.0,IssuesEvent,2017-03-17 08:10:02,golang/go,https://api.github.com/repos/golang/go,closed,doc: Golang FAQ on go get versioning needs updating,Documentation,It should be updated to reflect that the behaviour exposed via GO15VENDOREXPERIMENT=1 is now the default behaviour of the go command. Perhaps also include something about future plans (`dep`)?,1.0,doc: Golang FAQ on go get versioning needs updating - It should be updated to reflect that the behaviour exposed via GO15VENDOREXPERIMENT=1 is now the default behaviour of the go command. Perhaps also include something about future plans (`dep`)?,1,doc  golang faq on go get versioning needs updating   it should be updated to reflect that the behaviour exposed via     is now the default behaviour of the go command  perhaps also include something about future plans   dep   ,1
748663,26131743273.0,IssuesEvent,2022-12-29 06:24:43,nimblehq/android-templates,https://api.github.com/repos/nimblehq/android-templates,closed,Avoid defining app credentials via BuildConfig,type : chore status : need voting priority : normal,"## Issue

Currently, we're having a sample to define [BASE_API_URL](https://github.com/nimblehq/android-templates/blob/develop/CoroutineTemplate/app/build.gradle.kts#L41) via `BuildConfig`. **BuildConfig will not be obfuscated by proguard** so this way is not safe to go, especially when we have more secrets like `API_KEY` or `API_SECRET`. We should provide them through a separate class which will be obfuscated in each `flavor` folder instead.

## Solution

By having 2 environments as default: `production` and `staging`, we will need to define 2 new `ApiEndpointUrl` classes in each flavor.

![image](https://user-images.githubusercontent.com/16315358/163514486-2fe2bf1d-924a-4571-8fec-335ed0ec298b.png)



## Who Benefits?

Developers

I think this is **essential** because app credentials management is very important.

## What's Next?

- [ ] Remove [BASE_API_URL](https://github.com/nimblehq/android-templates/blob/develop/CoroutineTemplate/app/build.gradle.kts#L41) definition via `BuildConfig`
- [ ] Define 2 new `ApiEndpointUrl` classes in each flavor to provide API endpoint urls.
",1.0,"Avoid defining app credentials via BuildConfig - ## Issue

Currently, we're having a sample to define [BASE_API_URL](https://github.com/nimblehq/android-templates/blob/develop/CoroutineTemplate/app/build.gradle.kts#L41) via `BuildConfig`. **BuildConfig will not be obfuscated by proguard** so this way is not safe to go, especially when we have more secrets like `API_KEY` or `API_SECRET`. We should provide them through a separate class which will be obfuscated in each `flavor` folder instead.

## Solution

By having 2 environments as default: `production` and `staging`, we will need to define 2 new `ApiEndpointUrl` classes in each flavor.

![image](https://user-images.githubusercontent.com/16315358/163514486-2fe2bf1d-924a-4571-8fec-335ed0ec298b.png)



## Who Benefits?

Developers

I think this is **essential** because app credentials management is very important.

## What's Next?

- [ ] Remove [BASE_API_URL](https://github.com/nimblehq/android-templates/blob/develop/CoroutineTemplate/app/build.gradle.kts#L41) definition via `BuildConfig`
- [ ] Define 2 new `ApiEndpointUrl` classes in each flavor to provide API endpoint urls.
",0,avoid defining app credentials via buildconfig      issue    currently  we re having a sample to define     via  buildconfig     buildconfig will not be obfuscated by proguard   so this way is not safe to go  especially when we have more secrets like  api key  or  api secret   we should provide them through a separate class which will be obfuscated in each  flavor  folder instead        solution    by having   environments as default   production  and  staging   we will need to define   new  apiendpointurl  classes in each flavor                    who benefits     developers    i think this is   essential   because app credentials management is very important        what s next         remove     definition via  buildconfig       define   new  apiendpointurl  classes in each flavor to provide api endpoint urls   ,0
48722,7451765286.0,IssuesEvent,2018-03-29 05:09:23,golang/go,https://api.github.com/repos/golang/go,closed,testing: document cap the number of concurrent goroutines with -race,Documentation NeedsFix,"### What version of Go are you using (`go version`)?

1.9.2
GOOS=linux
GOARCH=amd64

### What did you do?

```
package main

import (
	""math/rand""
	""strconv""
	""testing""
	""time""
)

func TestGoRoutines(t *testing.T) {
	for i := 0; i < 1<<15; i++ {
		t.Run(strconv.Itoa(i), func(t *testing.T) {
			t.Parallel()
			time.Sleep(time.Duration(rand.Intn(500000000)))
		})
	}
}
```

saved as `x_test.go` and run with `go test -race`

### What did you expect to see?

The tests to pass. Instead,

```
race: limit on 8192 simultaneously alive goroutines is exceeded, dying
```

As I understand it, this is likely a technical limitation on Go's race detector. However, it would be nice for the `testing` package to be aware of this and, if raceenabled, cap the number of parallel tests at something below the 8192 limit (say, 7000?). Perhaps a better way would be a warning, but I know Go doesn't really like warnings.


",1.0,"testing: document cap the number of concurrent goroutines with -race - ### What version of Go are you using (`go version`)?

1.9.2
GOOS=linux
GOARCH=amd64

### What did you do?

```
package main

import (
	""math/rand""
	""strconv""
	""testing""
	""time""
)

func TestGoRoutines(t *testing.T) {
	for i := 0; i < 1<<15; i++ {
		t.Run(strconv.Itoa(i), func(t *testing.T) {
			t.Parallel()
			time.Sleep(time.Duration(rand.Intn(500000000)))
		})
	}
}
```

saved as `x_test.go` and run with `go test -race`

### What did you expect to see?

The tests to pass. Instead,

```
race: limit on 8192 simultaneously alive goroutines is exceeded, dying
```

As I understand it, this is likely a technical limitation on Go's race detector. However, it would be nice for the `testing` package to be aware of this and, if raceenabled, cap the number of parallel tests at something below the 8192 limit (say, 7000?). Perhaps a better way would be a warning, but I know Go doesn't really like warnings.


",1,testing  document cap the number of concurrent goroutines with  race       what version of go are you using   go version              goos linux  goarch          what did you do          package main    import    	 math rand   	 strconv   	 testing   	 time        func testgoroutines t  testing t     	for i       i         i      		t run strconv itoa i   func t  testing t     			t parallel    			time sleep time duration rand intn       		    	             saved as  x test go  and run with  go test  race         what did you expect to see     the tests to pass  instead          race  limit on   simultaneously alive goroutines is exceeded  dying         as i understand it  this is likely a technical limitation on go s race detector  however  it would be nice for the  testing  package to be aware of this and  if raceenabled  cap the number of parallel tests at something below the   limit  say       perhaps a better way would be a warning  but i know go doesn t really like warnings       ,1
297429,22356717394.0,IssuesEvent,2022-06-15 16:16:18,golang/go,https://api.github.com/repos/golang/go,reopened,x/website: changes in code not highlighted in grettings-multiple-people tutorial,Documentation NeedsFix website,"### What did you expect to see?

On the site https://golang.org/doc/tutorial/greetings-multiple-people Step 2  in the code block:

```
// Request greeting messages for the names.
    messages, err := greetings.Hellos(names)
```

I think the font color should be blue, because this part changed from ""Hello"" to  ""Hellos"".

### What did you see instead?

Font color is black. 
",1.0,"x/website: changes in code not highlighted in grettings-multiple-people tutorial - ### What did you expect to see?

On the site https://golang.org/doc/tutorial/greetings-multiple-people Step 2  in the code block:

```
// Request greeting messages for the names.
    messages, err := greetings.Hellos(names)
```

I think the font color should be blue, because this part changed from ""Hello"" to  ""Hellos"".

### What did you see instead?

Font color is black. 
",1,x website  changes in code not highlighted in grettings multiple people tutorial       what did you expect to see     on the site   step    in the code block             request greeting messages for the names       messages  err    greetings hellos names          i think the font color should be blue  because this part changed from  hello  to   hellos          what did you see instead     font color is black    ,1
5178,7960904690.0,IssuesEvent,2018-07-13 08:56:08,Open-EO/openeo-api,https://api.github.com/repos/Open-EO/openeo-api,closed,filter_daterange: ISO8601 date/time ranges for temporal extents,data discovery processes,"All temporal references should simply follow (a subset of) ISO8601. 

For example, the time attribute for datasets should be changed from 
```
  ""time"": {
    ""from"": ""2016-01-01"",
    ""to"": ""2017-10-01""
  },
```
to
`  ""time"": ""2016-01-01/2017-10-01"",`

and so on...

For filtering, we probably need to think about an extension to the ISO standard, e.g. get all files starting from 2016-01-01 (could be `2016-01-01/`?) or get all files prior to 2017-10-01 (could be `/2017-10-01`). STAC is thinking about something similar, maybe we can check what they use, but at the moment it seems to be something like a literal, e.g. gt, eq, lte, ... Related to #62 .

Tempotal extents should not be restricted on days, but could also be in some other unit",1.0,"filter_daterange: ISO8601 date/time ranges for temporal extents - All temporal references should simply follow (a subset of) ISO8601. 

For example, the time attribute for datasets should be changed from 
```
  ""time"": {
    ""from"": ""2016-01-01"",
    ""to"": ""2017-10-01""
  },
```
to
`  ""time"": ""2016-01-01/2017-10-01"",`

and so on...

For filtering, we probably need to think about an extension to the ISO standard, e.g. get all files starting from 2016-01-01 (could be `2016-01-01/`?) or get all files prior to 2017-10-01 (could be `/2017-10-01`). STAC is thinking about something similar, maybe we can check what they use, but at the moment it seems to be something like a literal, e.g. gt, eq, lte, ... Related to #62 .

Tempotal extents should not be restricted on days, but could also be in some other unit",0,filter daterange    date time ranges for temporal extents   all temporal references should simply follow  a subset of         for example  the time attribute for datasets should be changed from           time           from                  to                       to      time                      and so on       for filtering  we probably need to think about an extension to the iso standard  e g  get all files starting from        could be            or get all files prior to        could be            stac is thinking about something similar  maybe we can check what they use  but at the moment it seems to be something like a literal  e g  gt  eq  lte      related to         tempotal extents should not be restricted on days  but could also be in some other unit,0
68452,9187649226.0,IssuesEvent,2019-03-06 03:52:15,golang/go,https://api.github.com/repos/golang/go,closed,doc: Effective Go contains outdated map print result,Documentation,It would be better to either update them or add a note mentioning the print results are for Go 1.12-.,1.0,doc: Effective Go contains outdated map print result - It would be better to either update them or add a note mentioning the print results are for Go 1.12-.,1,doc  effective go contains outdated map print result   it would be better to either update them or add a note mentioning the print results are for go      ,1
13996,3790734864.0,IssuesEvent,2016-03-21 22:39:49,golang/go,https://api.github.com/repos/golang/go,closed,website: establish a no-me-too policy,Documentation,"@adg and I realized our ""no-me-too"" policy has only ever been ""documented"" in the golang-dev mailing list. Let's make it more official.
",1.0,"website: establish a no-me-too policy - @adg and I realized our ""no-me-too"" policy has only ever been ""documented"" in the golang-dev mailing list. Let's make it more official.
",1,website  establish a no me too policy    adg and i realized our  no me too  policy has only ever been  documented  in the golang dev mailing list  let s make it more official   ,1
700632,24067437225.0,IssuesEvent,2022-09-17 17:48:30,Baystation12/Baystation12,https://api.github.com/repos/Baystation12/Baystation12,closed,Multiple visors on a hardsuit,Priority: Low Could Reproduce,"<!--
	Anything inside tags like these is a comment and will not be displayed in the final issue.
	Be careful not to write inside them!

	Every field other than 'specific information for locating' is required.
	If you do not fill out the 'specific information' field, please delete the header.
	/!\ Omitting or not answering a required field will result in your issue being closed. /!\
	Repeated violation of this rule, or joke or spam issues, will result in punishment.
	
	PUT YOUR ANSWERS ON THE BLANK LINES BELOW THE HEADERS 
	(The lines with four #'s) 
	Don't edit them or delete them - it's part of the formatting
-->

#### Description of issue
Night vision, medical hud, and mesons on hardsuit seem to be conflicting. Must be the same with all visors, I just only tried these.


#### Difference between expected and actual behavior
Switch vision mode swiches beween visors


#### Steps to reproduce
In a robotics fab fabricate a void nullsuit
In protolathe fabricae RIG modules: mesons, medical hud, night vision
Crowbar open the nullsuit, install the RIG modules
Wear and activate the suit
Acivate any vision module, then try switching



#### Specific information for locating
<!-- e.g. an object name, paste specific message outputs... -->
""switch vision mode"" gives ""Your sensors only have one mode.""


#### Length of time in which bug has been known to occur
<!--
	Be specific if you approximately know the time it's been occurring
	for—this can speed up finding the source. If you're not sure
	about it, tell us too!
-->
Just found out Sep 5th 2020


#### Client version, Server revision & Game ID
<!-- Found with the ""Show server revision"" verb in the OOC tab in game. -->
Client Version: 513
Server Revision: 9b24a0d456d4818f1fd51169aa1e9522ca618858 - 1fd51169aa1e9522ca618858 - 2020-09-03


#### Issue bingo
<!-- Check these by writing an x inside the [ ] (like this: [x])-->
<!-- Don't forget to remove the space between the brackets, or it won't work! -->
- [x] Issue could be reproduced at least once
- [ ] Issue could be reproduced by different players
- [ ] Issue could be reproduced in multiple rounds
- [x] Issue happened in a recent (less than 7 days ago) round
- [x] [Couldn't find an existing issue about this](https://github.com/Baystation12/Baystation12/issues)
",1.0,"Multiple visors on a hardsuit - <!--
	Anything inside tags like these is a comment and will not be displayed in the final issue.
	Be careful not to write inside them!

	Every field other than 'specific information for locating' is required.
	If you do not fill out the 'specific information' field, please delete the header.
	/!\ Omitting or not answering a required field will result in your issue being closed. /!\
	Repeated violation of this rule, or joke or spam issues, will result in punishment.
	
	PUT YOUR ANSWERS ON THE BLANK LINES BELOW THE HEADERS 
	(The lines with four #'s) 
	Don't edit them or delete them - it's part of the formatting
-->

#### Description of issue
Night vision, medical hud, and mesons on hardsuit seem to be conflicting. Must be the same with all visors, I just only tried these.


#### Difference between expected and actual behavior
Switch vision mode swiches beween visors


#### Steps to reproduce
In a robotics fab fabricate a void nullsuit
In protolathe fabricae RIG modules: mesons, medical hud, night vision
Crowbar open the nullsuit, install the RIG modules
Wear and activate the suit
Acivate any vision module, then try switching



#### Specific information for locating
<!-- e.g. an object name, paste specific message outputs... -->
""switch vision mode"" gives ""Your sensors only have one mode.""


#### Length of time in which bug has been known to occur
<!--
	Be specific if you approximately know the time it's been occurring
	for—this can speed up finding the source. If you're not sure
	about it, tell us too!
-->
Just found out Sep 5th 2020


#### Client version, Server revision & Game ID
<!-- Found with the ""Show server revision"" verb in the OOC tab in game. -->
Client Version: 513
Server Revision: 9b24a0d456d4818f1fd51169aa1e9522ca618858 - 1fd51169aa1e9522ca618858 - 2020-09-03


#### Issue bingo
<!-- Check these by writing an x inside the [ ] (like this: [x])-->
<!-- Don't forget to remove the space between the brackets, or it won't work! -->
- [x] Issue could be reproduced at least once
- [ ] Issue could be reproduced by different players
- [ ] Issue could be reproduced in multiple rounds
- [x] Issue happened in a recent (less than 7 days ago) round
- [x] [Couldn't find an existing issue about this](https://github.com/Baystation12/Baystation12/issues)
",0,multiple visors on a hardsuit         	anything inside tags like these is a comment and will not be displayed in the final issue   	be careful not to write inside them     	every field other than  specific information for locating  is required   	if you do not fill out the  specific information  field  please delete the header   	    omitting or not answering a required field will result in your issue being closed       	repeated violation of this rule  or joke or spam issues  will result in punishment   	  	put your answers on the blank lines below the headers   	 the lines with four   s    	don t edit them or delete them   it s part of the formatting              description of issue  night vision  medical hud  and mesons on hardsuit seem to be conflicting  must be the same with all visors  i just only tried these            difference between expected and actual behavior  switch vision mode swiches beween visors           steps to reproduce  in a robotics fab fabricate a void nullsuit  in protolathe fabricae rig modules  mesons  medical hud  night vision  crowbar open the nullsuit  install the rig modules  wear and activate the suit  acivate any vision module  then try switching             specific information for locating      switch vision mode  gives  your sensors only have one mode             length of time in which bug has been known to occur        	be specific if you approximately know the time it s been occurring  	for—this can speed up finding the source  if you re not sure  	about it  tell us too        just found out sep               client version  server revision   game id     client version     server revision                          issue bingo            issue could be reproduced at least once      issue could be reproduced by different players      issue could be reproduced in multiple rounds      issue happened in a recent  less than   days ago  round           ,0
48767,7457013818.0,IssuesEvent,2018-03-30 01:12:59,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.9.html: should go/types.Package.Imports behavior change be included?,Documentation,"_(It's not quite clear to me what's the criteria for inclusion of a change to warrant being mentioned in the release notes under the ""Minor changes to the library"" section (is it documented somewhere?), that's why this is a question.)_

https://godoc.org/go/types#Package.Imports changed behavior slightly. In Go 1.8, it was documented as:

> Imports returns the list of packages directly imported by pkg; the list is in source order. Package unsafe is excluded.
>
> [...]

In Go 1.9:

> Imports returns the list of packages directly imported by pkg; the list is in source order.
>
> [...]

So package unsafe is no longer excluded.

Should this be mentioned in doc/go1.9.html? It would've been saved me some time debugging an unexpected behavior change if I saw it mentioned there, so maybe it'll be helpful to others too.

Related to #20587.
Related to [CL 37694](https://golang.org/cl/37694). /cc @griesemer @alandonovan",1.0,"doc/go1.9.html: should go/types.Package.Imports behavior change be included? - _(It's not quite clear to me what's the criteria for inclusion of a change to warrant being mentioned in the release notes under the ""Minor changes to the library"" section (is it documented somewhere?), that's why this is a question.)_

https://godoc.org/go/types#Package.Imports changed behavior slightly. In Go 1.8, it was documented as:

> Imports returns the list of packages directly imported by pkg; the list is in source order. Package unsafe is excluded.
>
> [...]

In Go 1.9:

> Imports returns the list of packages directly imported by pkg; the list is in source order.
>
> [...]

So package unsafe is no longer excluded.

Should this be mentioned in doc/go1.9.html? It would've been saved me some time debugging an unexpected behavior change if I saw it mentioned there, so maybe it'll be helpful to others too.

Related to #20587.
Related to [CL 37694](https://golang.org/cl/37694). /cc @griesemer @alandonovan",1,doc     html  should go types package imports behavior change be included      it s not quite clear to me what s the criteria for inclusion of a change to warrant being mentioned in the release notes under the  minor changes to the library  section  is it documented somewhere    that s why this is a question         changed behavior slightly  in go      it was documented as       imports returns the list of packages directly imported by pkg  the list is in source order  package unsafe is excluded             in go           imports returns the list of packages directly imported by pkg  the list is in source order             so package unsafe is no longer excluded     should this be mentioned in doc     html  it would ve been saved me some time debugging an unexpected behavior change if i saw it mentioned there  so maybe it ll be helpful to others too     related to      related to      cc  griesemer  alandonovan,1
226184,17315474220.0,IssuesEvent,2021-07-27 05:08:31,golang/go,https://api.github.com/repos/golang/go,closed,testing: unclear if T.Name includes sub-tests as part of its string,Documentation NeedsFix help wanted,"The current docs say:

>  Name returns the name of the running test or benchmark. 

For a `func TestFoo(t *testing.T)`, I think it's reasonably clear that Name will be `TestFoo`.

However, for a sub-test like `t.Run(""Bar"", ...)`, it's not clear from the documentation if Name will return `TestFoo/Bar` or just `TestFoo`.

Another open question is whether the name will be altered, just like it is when printing output. For example, `t.Run(""bar baz"", ...)` ends up printing `TestFoo/bar_baz` in the terminal, so if the subtest name is included in the Name method, I'm not sure which of the two I'd expect.

cc @mpvl as per the owners doc
cc @adg @bradfitz since they added the Name method",1.0,"testing: unclear if T.Name includes sub-tests as part of its string - The current docs say:

>  Name returns the name of the running test or benchmark. 

For a `func TestFoo(t *testing.T)`, I think it's reasonably clear that Name will be `TestFoo`.

However, for a sub-test like `t.Run(""Bar"", ...)`, it's not clear from the documentation if Name will return `TestFoo/Bar` or just `TestFoo`.

Another open question is whether the name will be altered, just like it is when printing output. For example, `t.Run(""bar baz"", ...)` ends up printing `TestFoo/bar_baz` in the terminal, so if the subtest name is included in the Name method, I'm not sure which of the two I'd expect.

cc @mpvl as per the owners doc
cc @adg @bradfitz since they added the Name method",1,testing  unclear if t name includes sub tests as part of its string   the current docs say        name returns the name of the running test or benchmark      for a  func testfoo t  testing t    i think it s reasonably clear that name will be  testfoo      however  for a sub test like  t run  bar          it s not clear from the documentation if name will return  testfoo bar  or just  testfoo      another open question is whether the name will be altered  just like it is when printing output  for example   t run  bar baz         ends up printing  testfoo bar baz  in the terminal  so if the subtest name is included in the name method  i m not sure which of the two i d expect     cc  mpvl as per the owners doc  cc  adg  bradfitz since they added the name method,1
59281,8355975310.0,IssuesEvent,2018-10-02 17:08:19,golang/go,https://api.github.com/repos/golang/go,closed,net/http: document that Header.Set canonicalizes the header key,Documentation NeedsFix help wanted,"Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
1.10.3

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
darwin, amd64

### What did you do?

https://play.golang.org/p/l-3GJBY-vWA

### What did you expect to see?

Expected key to be the same string HeyHey when adding it to the http header rather then Heyhey.

### What did you see instead?
Saw that after adding or setting  a string to a header it does not keep the n+1 capital letter causing a check for the same key to fail.  ",1.0,"net/http: document that Header.Set canonicalizes the header key - Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
1.10.3

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
darwin, amd64

### What did you do?

https://play.golang.org/p/l-3GJBY-vWA

### What did you expect to see?

Expected key to be the same string HeyHey when adding it to the http header rather then Heyhey.

### What did you see instead?
Saw that after adding or setting  a string to a header it does not keep the n+1 capital letter causing a check for the same key to fail.  ",1,net http  document that header set canonicalizes the header key   please answer these questions before submitting your issue  thanks         what version of go are you using   go version                  does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env     darwin           what did you do              what did you expect to see     expected key to be the same string heyhey when adding it to the http header rather then heyhey         what did you see instead   saw that after adding or setting  a string to a header it does not keep the n   capital letter causing a check for the same key to fail   ,1
95610,8564853893.0,IssuesEvent,2018-11-09 17:58:56,mozilla-mobile/android-components,https://api.github.com/repos/mozilla-mobile/android-components,reopened,Intermittently failing test: BrowserAwesomeBar cancels previous jobs,<awesomebar> ✅ testing,"```
mozilla.components.browser.awesomebar.BrowserAwesomeBarTest > BrowserAwesomeBar cancels previous jobs if onInputStarted gets called again FAILED
    java.lang.AssertionError at BrowserAwesomeBarTest.kt:170
```

See also #1288.",1.0,"Intermittently failing test: BrowserAwesomeBar cancels previous jobs - ```
mozilla.components.browser.awesomebar.BrowserAwesomeBarTest > BrowserAwesomeBar cancels previous jobs if onInputStarted gets called again FAILED
    java.lang.AssertionError at BrowserAwesomeBarTest.kt:170
```

See also #1288.",0,intermittently failing test  browserawesomebar cancels previous jobs        mozilla components browser awesomebar browserawesomebartest   browserawesomebar cancels previous jobs if oninputstarted gets called again failed      java lang assertionerror at browserawesomebartest kt           see also    ,0
62192,25898748576.0,IssuesEvent,2022-12-15 02:18:27,Azure/azure-cli,https://api.github.com/repos/Azure/azure-cli,closed,"New Isolated v2 (I4v2, I5v2, I6v2) Azure App Service Plan Tiers Not Supported in CLI",bug App Services customer-reported needs-team-attention CXP Attention Auto-Assign App Service Environments,"<!--- 🛑 Please check existing issues first before continuing: https://github.com/Azure/azure-cli/issues --->

> ### `az feedback` auto-generates most of the information requested below, as of CLI version 2.0.62

**Related command**
<!--- Please provide the related command with az {command} if you can, so that we can quickly route to the related team for help. --->

`az appservice list-locations --sku I5v2 `

`az appservice plan update --name PLAN_NAME -g PLAN_RG --sku ""I4v2"" `

**Describe the bug**
<!--- A clear and concise description of what the bug is. --->

I was taking a look at the new Isolated v2 SKUs announced on the [appservice blog](https://azure.github.io/AppService/2022/12/01/Announcing-Larger-Isolatedv2-SKUs.html) and tried to use CLI appservice commands like `list-locations` and `update` with the new SKUs (I4v2, I5v2, I6v2) but they appear to not work with the CLI even though they're referenced in the blog as being available with the latest CLI 2.43.0 and are referenced throughout the help documentation

![Screen Shot 2022-12-09 at 3 38 55 PM](https://user-images.githubusercontent.com/45158195/206792324-086f90e6-1652-4981-af1d-c8b94ef1f8bd.png)



**To Reproduce**


1. Verify CLI is on version 2.43.0 with `az version`
2. Perform `az appservice list-locations --sku I5v2`
3. See CLI returns error ""Invalid sku(pricing tier), please refer to command help for valid values
"" when SKUs I(4-6)v2 are passed in 
4. If testing update/create, provision an ASEv3 in North Central US & provision a plan on it.
5. Perform an update `az appservice plan update --name PLAN_NAME -g PLAN_RG --sku ""I4v2"" `
6. See CLI returns error ""Invalid sku(pricing tier), please refer to command help for valid values""

**Expected behavior**

Expected that the CLI existing behaviors (list-locations, update) work with the newly added Azure App Service SKUs I4v2, I5v2, I6v2.

**Environment summary**
<!--- Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build) / CLI version (`az --version`) / OS version / Shell Type (e.g. bash, cmd.exe, Bash on Windows)  --->

- CLI Version: 2.43.0
- OS Version: Mac OS Monterey 12.6
- Shell Type: fish

**Additional context**

These tiers were released recently and the other older tiers in the Isolatedv2 family appear to work with the CLI.
",2.0,"New Isolated v2 (I4v2, I5v2, I6v2) Azure App Service Plan Tiers Not Supported in CLI - <!--- 🛑 Please check existing issues first before continuing: https://github.com/Azure/azure-cli/issues --->

> ### `az feedback` auto-generates most of the information requested below, as of CLI version 2.0.62

**Related command**
<!--- Please provide the related command with az {command} if you can, so that we can quickly route to the related team for help. --->

`az appservice list-locations --sku I5v2 `

`az appservice plan update --name PLAN_NAME -g PLAN_RG --sku ""I4v2"" `

**Describe the bug**
<!--- A clear and concise description of what the bug is. --->

I was taking a look at the new Isolated v2 SKUs announced on the [appservice blog](https://azure.github.io/AppService/2022/12/01/Announcing-Larger-Isolatedv2-SKUs.html) and tried to use CLI appservice commands like `list-locations` and `update` with the new SKUs (I4v2, I5v2, I6v2) but they appear to not work with the CLI even though they're referenced in the blog as being available with the latest CLI 2.43.0 and are referenced throughout the help documentation

![Screen Shot 2022-12-09 at 3 38 55 PM](https://user-images.githubusercontent.com/45158195/206792324-086f90e6-1652-4981-af1d-c8b94ef1f8bd.png)



**To Reproduce**


1. Verify CLI is on version 2.43.0 with `az version`
2. Perform `az appservice list-locations --sku I5v2`
3. See CLI returns error ""Invalid sku(pricing tier), please refer to command help for valid values
"" when SKUs I(4-6)v2 are passed in 
4. If testing update/create, provision an ASEv3 in North Central US & provision a plan on it.
5. Perform an update `az appservice plan update --name PLAN_NAME -g PLAN_RG --sku ""I4v2"" `
6. See CLI returns error ""Invalid sku(pricing tier), please refer to command help for valid values""

**Expected behavior**

Expected that the CLI existing behaviors (list-locations, update) work with the newly added Azure App Service SKUs I4v2, I5v2, I6v2.

**Environment summary**
<!--- Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build) / CLI version (`az --version`) / OS version / Shell Type (e.g. bash, cmd.exe, Bash on Windows)  --->

- CLI Version: 2.43.0
- OS Version: Mac OS Monterey 12.6
- Shell Type: fish

**Additional context**

These tiers were released recently and the other older tiers in the Isolatedv2 family appear to work with the CLI.
",0,new isolated             azure app service plan tiers not supported in cli               az feedback  auto generates most of the information requested below  as of cli version            related command          az appservice list locations   sku         az appservice plan update   name plan name  g plan rg   sku            describe the bug         i was taking a look at the new isolated   skus announced on the     and tried to use cli appservice commands like  list locations  and  update  with the new skus           but they appear to not work with the cli even though they re referenced in the blog as being available with the latest cli       and are referenced throughout the help documentation                  to reproduce           verify cli is on version       with  az version      perform  az appservice list locations   sku        see cli returns error  invalid sku pricing tier   please refer to command help for valid values    when skus i       are passed in      if testing update create  provision an   in north central us   provision a plan on it      perform an update  az appservice plan update   name plan name  g plan rg   sku           see cli returns error  invalid sku pricing tier   please refer to command help for valid values       expected behavior      expected that the cli existing behaviors  list locations  update  work with the newly added azure app service skus               environment summary           cli version           os version  mac os monterey        shell type  fish      additional context      these tiers were released recently and the other older tiers in the   family appear to work with the cli   ,0
137202,12747833315.0,IssuesEvent,2020-06-26 18:46:11,golang/go,https://api.github.com/repos/golang/go,closed,doc: BuildNameToCertificate deprecated in go 1.14 not mentioned in the release notes [1.14 backport],CherryPickApproved Documentation,"@FiloSottile requested issue #37626 to be considered for backport to the next 1.14 minor release.

> @gopherbot please open a backport issue for Go 1.14, this is a documentation change that needs to go live on golang.org.
",1.0,"doc: BuildNameToCertificate deprecated in go 1.14 not mentioned in the release notes [1.14 backport] - @FiloSottile requested issue #37626 to be considered for backport to the next 1.14 minor release.

> @gopherbot please open a backport issue for Go 1.14, this is a documentation change that needs to go live on golang.org.
",1,doc  buildnametocertificate deprecated in go     not mentioned in the release notes      filosottile requested issue    to be considered for backport to the next     minor release      gopherbot please open a backport issue for go      this is a documentation change that needs to go live on golang org  ,1
113319,17118004249.0,IssuesEvent,2021-07-11 19:07:24,dotnet/runtime,https://api.github.com/repos/dotnet/runtime,opened,Persisted-key AesCng in CFB mode always uses CFB8,area-System.Security bug,"### Description

When using `AesCng` with the `CipherMode` in CFB mode with a persisted CNG key, it appears that CFB8 is always used for the actual feedback size, even if `FeedbackSize` is set to 128.

Steps to reproduce:

Run the following snippet (with package reference to `System.Security.Cryptography.Cng`):

```csharp
using System;
using System.Security.Cryptography;

// Create the key
CngAlgorithm aesAlgorithm = new CngAlgorithm(""AES"");
CngKeyCreationParameters opts =  new CngKeyCreationParameters
{
    ExportPolicy = CngExportPolicies.AllowPlaintextExport,
};

try
{
    CngKey key = CngKey.Create(aesAlgorithm, ""potato-key"", opts);
    key.Dispose();
}
catch (CryptographicException ce) when ((uint)ce.HResult == 0x8009000F)
{
    // Don't worry about the key already existing.
}

static byte[] Encrypt(Aes aes, int feebackSizeBits)
{
    aes.FeedbackSize = feebackSizeBits;
    aes.Mode = CipherMode.CFB;
    aes.Padding = PaddingMode.PKCS7;
    aes.IV = new byte[aes.BlockSize / 8];

    var input = new byte[] { 1, 2, 3, 4, 5 };
    using ICryptoTransform transform = aes.CreateEncryptor();
    byte[] result = transform.TransformFinalBlock(input, 0, input.Length);
    return result;
}

AesCng cng = new AesCng(""potato-key"");
Aes aes = Aes.Create();
aes.Key = cng.Key;

byte[] cng8Result = Encrypt(cng, 8);
byte[] aes8Result = Encrypt(aes, 8);

Console.WriteLine(""CNG  8: "" + Convert.ToHexString(cng8Result));
Console.WriteLine(""AES  8: "" + Convert.ToHexString(aes8Result));


byte[] cng128Result = Encrypt(cng, 128);
byte[] aes128Result = Encrypt(aes, 128);

Console.WriteLine(""CNG128: "" + Convert.ToHexString(cng128Result));
Console.WriteLine(""AES128: "" + Convert.ToHexString(aes128Result));
```

It will produce an output that looks something like this. The output will be different from this one since the code generates a key, but this illustrates the pattern.

```
CNG  8: 3CF1DB609559
AES  8: 3CF1DB609559
CNG128: 3CF1DB6095538DD2611E7FBC7531083C
AES128: 3CD079280665EE399880253D9B40D035
```

`AesCng` and `Aes.Create()` agree for CFB8. However for CFB128, the results do not agree. The CNG128 line differs from the AES128 line. In this case, the CNG128 line's first 5 bytes match the result of CNG8, indicating CFB8 was actually used for the encryption, however it was padded as if CFB128 were used.

### Configuration

Occurs in .NET 5 and `main` on all versions of Windows.

### Other information

I suspect this is also the same for `TripleDESCng` with CFB64.",True,"Persisted-key AesCng in CFB mode always uses CFB8 - ### Description

When using `AesCng` with the `CipherMode` in CFB mode with a persisted CNG key, it appears that CFB8 is always used for the actual feedback size, even if `FeedbackSize` is set to 128.

Steps to reproduce:

Run the following snippet (with package reference to `System.Security.Cryptography.Cng`):

```csharp
using System;
using System.Security.Cryptography;

// Create the key
CngAlgorithm aesAlgorithm = new CngAlgorithm(""AES"");
CngKeyCreationParameters opts =  new CngKeyCreationParameters
{
    ExportPolicy = CngExportPolicies.AllowPlaintextExport,
};

try
{
    CngKey key = CngKey.Create(aesAlgorithm, ""potato-key"", opts);
    key.Dispose();
}
catch (CryptographicException ce) when ((uint)ce.HResult == 0x8009000F)
{
    // Don't worry about the key already existing.
}

static byte[] Encrypt(Aes aes, int feebackSizeBits)
{
    aes.FeedbackSize = feebackSizeBits;
    aes.Mode = CipherMode.CFB;
    aes.Padding = PaddingMode.PKCS7;
    aes.IV = new byte[aes.BlockSize / 8];

    var input = new byte[] { 1, 2, 3, 4, 5 };
    using ICryptoTransform transform = aes.CreateEncryptor();
    byte[] result = transform.TransformFinalBlock(input, 0, input.Length);
    return result;
}

AesCng cng = new AesCng(""potato-key"");
Aes aes = Aes.Create();
aes.Key = cng.Key;

byte[] cng8Result = Encrypt(cng, 8);
byte[] aes8Result = Encrypt(aes, 8);

Console.WriteLine(""CNG  8: "" + Convert.ToHexString(cng8Result));
Console.WriteLine(""AES  8: "" + Convert.ToHexString(aes8Result));


byte[] cng128Result = Encrypt(cng, 128);
byte[] aes128Result = Encrypt(aes, 128);

Console.WriteLine(""CNG128: "" + Convert.ToHexString(cng128Result));
Console.WriteLine(""AES128: "" + Convert.ToHexString(aes128Result));
```

It will produce an output that looks something like this. The output will be different from this one since the code generates a key, but this illustrates the pattern.

```
CNG  8: 3CF1DB609559
AES  8: 3CF1DB609559
CNG128: 3CF1DB6095538DD2611E7FBC7531083C
AES128: 3CD079280665EE399880253D9B40D035
```

`AesCng` and `Aes.Create()` agree for CFB8. However for CFB128, the results do not agree. The CNG128 line differs from the AES128 line. In this case, the CNG128 line's first 5 bytes match the result of CNG8, indicating CFB8 was actually used for the encryption, however it was padded as if CFB128 were used.

### Configuration

Occurs in .NET 5 and `main` on all versions of Windows.

### Other information

I suspect this is also the same for `TripleDESCng` with CFB64.",0,persisted key aescng in cfb mode always uses         description    when using  aescng  with the  ciphermode  in cfb mode with a persisted cng key  it appears that   is always used for the actual feedback size  even if  feedbacksize  is set to       steps to reproduce     run the following snippet  with package reference to  system security cryptography cng          csharp  using system   using system security cryptography        create the key  cngalgorithm aesalgorithm   new cngalgorithm  aes     cngkeycreationparameters opts    new cngkeycreationparameters         exportpolicy   cngexportpolicies allowplaintextexport         try         cngkey key   cngkey create aesalgorithm   potato key   opts        key dispose        catch  cryptographicexception ce  when   uint ce hresult                  don t worry about the key already existing        static byte  encrypt aes aes  int feebacksizebits          aes feedbacksize   feebacksizebits       aes mode   ciphermode cfb       aes padding   paddingmode         aes iv   new byte          var input   new byte                          using icryptotransform transform   aes createencryptor         byte  result   transform transformfinalblock input     input length        return result        aescng cng   new aescng  potato key     aes aes   aes create     aes key   cng key     byte      encrypt cng       byte      encrypt aes         console writeline  cng         convert tohexstring       console writeline  aes         convert tohexstring           byte      encrypt cng       byte      encrypt aes         console writeline         convert tohexstring       console writeline         convert tohexstring              it will produce an output that looks something like this  the output will be different from this one since the code generates a key  but this illustrates the pattern          cng        aes                            aescng  and  aes create    agree for    however for    the results do not agree  the   line differs from the   line  in this case  the   line s first   bytes match the result of    indicating   was actually used for the encryption  however it was padded as if   were used         configuration    occurs in  net   and  main  on all versions of windows         other information    i suspect this is also the same for  tripledescng  with   ,0
217161,16681008807.0,IssuesEvent,2021-06-07 23:45:02,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.17: document changes to the language for Go 1.17,Documentation NeedsInvestigation help wanted release-blocker,"As of filing this issue, the [Go 1.17 draft release notes](https://tip.golang.org/doc/go1.17) contained the following HTML:

<h2 id=""language"">Changes to the language</h2>

<p><!-- CL 216424 -->
  TODO: <a href=""https://golang.org/cl/216424"">https://golang.org/cl/216424</a>: allow conversion from slice to array ptr
</p>

<p>
  TODO: complete this section
</p>

---

This TODO needs to be resolved by July 1 so that we can have complete release notes for [Beta 1](https://golang.org/s/release#june-1--december-1-beta-1-issued).

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.17:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.17) and include ""For #44513. Fixes #46020."" in the body.",1.0,"doc/go1.17: document changes to the language for Go 1.17 - As of filing this issue, the [Go 1.17 draft release notes](https://tip.golang.org/doc/go1.17) contained the following HTML:

<h2 id=""language"">Changes to the language</h2>

<p><!-- CL 216424 -->
  TODO: <a href=""https://golang.org/cl/216424"">https://golang.org/cl/216424</a>: allow conversion from slice to array ptr
</p>

<p>
  TODO: complete this section
</p>

---

This TODO needs to be resolved by July 1 so that we can have complete release notes for [Beta 1](https://golang.org/s/release#june-1--december-1-beta-1-issued).

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.17:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.17) and include ""For #44513. Fixes #46020."" in the body.",1,doc      document changes to the language for go       as of filing this issue  the     contained the following html      changes to the language           todo   a href    allow conversion from slice to array ptr            todo  complete this section              this todo needs to be resolved by july   so that we can have complete release notes for        a sequence of steps to resolve this issue may be        come up with a draft release note entry in this issue  then move the issue to needsfix state      send a cl with  doc           and include  for     fixes      in the body ,1
94401,10821477545.0,IssuesEvent,2019-11-08 18:46:23,golang/go,https://api.github.com/repos/golang/go,closed,net: IPMask docs aren't great,Documentation NeedsFix help wanted,"The docs for `net.IPMask` say:

https://golang.org/pkg/net/#IPMask

> An IP mask is an IP address.
>
> `type IPMask []byte`

That's, uh, pretty brief.

We should say more because as-is my first reaction would be, ""Well, then why don't I juse use an IP address?""

For Go 1.13 at least, but Go 1.12 would be fine too.

/cc @ianlancetaylor @mikioh ",1.0,"net: IPMask docs aren't great - The docs for `net.IPMask` say:

https://golang.org/pkg/net/#IPMask

> An IP mask is an IP address.
>
> `type IPMask []byte`

That's, uh, pretty brief.

We should say more because as-is my first reaction would be, ""Well, then why don't I juse use an IP address?""

For Go 1.13 at least, but Go 1.12 would be fine too.

/cc @ianlancetaylor @mikioh ",1,net  ipmask docs aren t great   the docs for  net ipmask  say            an ip mask is an ip address         type ipmask  byte     that s  uh  pretty brief     we should say more because as is my first reaction would be   well  then why don t i juse use an ip address      for go     at least  but go     would be fine too      cc  ianlancetaylor  mikioh ,1
335807,10166906497.0,IssuesEvent,2019-08-07 16:54:24,web-platform-tests/wpt,https://api.github.com/repos/web-platform-tests/wpt,closed,Move wptserve docs into web-platform-tests.org,docs infra priority:roadmap wptserve,"web-platform-tests.org currently covers some features of wptserve, e.g. https://web-platform-tests.org/writing-tests/server-features.html , but there is still a large chunk missing (notably pipes, custom handlers, etc.) and can only be found in https://wptserve.readthedocs.io/en/latest/

@jgraham @gsnedders do you think we should move the documentation into GitHub Pages? If not, we should at least provide an easy-to-find pointer linking to the full docs.",1.0,"Move wptserve docs into web-platform-tests.org - web-platform-tests.org currently covers some features of wptserve, e.g. https://web-platform-tests.org/writing-tests/server-features.html , but there is still a large chunk missing (notably pipes, custom handlers, etc.) and can only be found in https://wptserve.readthedocs.io/en/latest/

@jgraham @gsnedders do you think we should move the documentation into GitHub Pages? If not, we should at least provide an easy-to-find pointer linking to the full docs.",0,move wptserve docs into web platform tests org   web platform tests org currently covers some features of wptserve  e g      but there is still a large chunk missing  notably pipes  custom handlers  etc   and can only be found in       jgraham  gsnedders do you think we should move the documentation into github pages  if not  we should at least provide an easy to find pointer linking to the full docs ,0
2684,3963126338.0,IssuesEvent,2016-05-02 19:18:00,jillix/flow-app,https://api.github.com/repos/jillix/flow-app,closed,Server code from modules is exposed on the client,modules security,The server code from modules is exposed on the client via the `bundle.js` files. This is terrible because it could contain sensitive information.,True,Server code from modules is exposed on the client - The server code from modules is exposed on the client via the `bundle.js` files. This is terrible because it could contain sensitive information.,0,server code from modules is exposed on the client   the server code from modules is exposed on the client via the  bundle js  files  this is terrible because it could contain sensitive information ,0
435607,30509701922.0,IssuesEvent,2023-07-18 19:46:38,golang/go,https://api.github.com/repos/golang/go,opened,x/tools/go/packages: document that different package loads lead to different type identities,Documentation NeedsFix,"When loading the same set of package twice, user-defined types are not guaranteed to have the same type identity.
This should be explicitly documented.

See #61412 for an example where not understanding this property causes problems.

cc: @findleyr @alandonovan ",1.0,"x/tools/go/packages: document that different package loads lead to different type identities - When loading the same set of package twice, user-defined types are not guaranteed to have the same type identity.
This should be explicitly documented.

See #61412 for an example where not understanding this property causes problems.

cc: @findleyr @alandonovan ",1,x tools go packages  document that different package loads lead to different type identities   when loading the same set of package twice  user defined types are not guaranteed to have the same type identity   this should be explicitly documented     see    for an example where not understanding this property causes problems     cc   findleyr  alandonovan ,1
166288,26336360819.0,IssuesEvent,2023-01-10 14:37:14,brave/brave-browser,https://api.github.com/repos/brave/brave-browser,closed,"In Spanish,`I have a sync code` button overlaps the white background on brave://settings/braveSync/setup",bug l10n design priority/P4 OS/Desktop,"<!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue. 

PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE. 
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->

## Description 
<!--Provide a brief description of the issue-->

In Spanish,`I have a sync code` button overlaps the white background on brave://settings/braveSync/setup

## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->

   1. switch system language to Spanish
   2. new profile
   3. launch Brave
   4. open `brave://settings/braveSync/setup`
   5. look at the buttons in relation to the white background

## Actual result:
<!--Please add screenshots if needed-->
<img width=""1747"" alt=""Captura de pantalla 2022-02-01 a las 13 07 27"" src=""https://user-images.githubusercontent.com/387249/152059803-88e47f8a-1491-4a25-8e9e-380b628f4970.png"">



## Expected result:

Should probably have the white background be wider, to accommodate the extra length of these buttons

## Reproduces how often: 
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->
100%

## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->



Brave | 1.35.99 Chromium: 98.0.4758.87 (Official Build) (x86_64)
-- | --
Revision | e4cd00f135fb4d8edc64c8aa6ecbe7cc79ebb3b2-refs/branch-heads/4758@{#1002}
OS | macOS Version 11.6.1 (Build 20G224)",1.0,"In Spanish,`I have a sync code` button overlaps the white background on brave://settings/braveSync/setup - <!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue. 

PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE. 
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->

## Description 
<!--Provide a brief description of the issue-->

In Spanish,`I have a sync code` button overlaps the white background on brave://settings/braveSync/setup

## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->

   1. switch system language to Spanish
   2. new profile
   3. launch Brave
   4. open `brave://settings/braveSync/setup`
   5. look at the buttons in relation to the white background

## Actual result:
<!--Please add screenshots if needed-->
<img width=""1747"" alt=""Captura de pantalla 2022-02-01 a las 13 07 27"" src=""https://user-images.githubusercontent.com/387249/152059803-88e47f8a-1491-4a25-8e9e-380b628f4970.png"">



## Expected result:

Should probably have the white background be wider, to accommodate the extra length of these buttons

## Reproduces how often: 
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->
100%

## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->



Brave | 1.35.99 Chromium: 98.0.4758.87 (Official Build) (x86_64)
-- | --
Revision | e4cd00f135fb4d8edc64c8aa6ecbe7cc79ebb3b2-refs/branch-heads/4758@{#1002}
OS | macOS Version 11.6.1 (Build 20G224)",0,in spanish  i have a sync code  button overlaps the white background on brave   settings bravesync setup        have you searched for similar issues  before submitting this issue  please check the open issues and add a note before logging a new issue      please use the template below to provide information about the issue    insufficient info will get the issue closed  it will only be reopened after sufficient info is provided          description        in spanish  i have a sync code  button overlaps the white background on brave   settings bravesync setup       steps to reproduce             switch system language to spanish        new profile        launch brave        open  brave   settings bravesync setup         look at the buttons in relation to the white background       actual result       img width     alt  captura de pantalla       a las        src              expected result     should probably have the white background be wider  to accommodate the extra length of these buttons       reproduces how often                brave version  brave   version info            brave         chromium           official build                  revision     refs branch heads         os   macos version        build   ,0
110797,24010539592.0,IssuesEvent,2022-09-14 18:23:34,withfig/fig,https://api.github.com/repos/withfig/fig,closed,Sometimes Fig doesn't recognise switching to iTerm2 hotkey window,codebase:macos terminal:iTerm,"### Sanity checks

- [X] I have searched [github.com/withfig/fig/issues](https://github.com/withfig/fig/issues?q=) and there are no duplicates of my issue
- [X] My issue does not relate to a specific CLI completion spec (e.g. `git checkout` is missing options in `git` completion spec). If it does, please create your issue here: [withfig/autocomplete](https://github.com/withfig/autocomplete/issues?q=)

### Issue Details

### Summary
Sometimes Fig doesn't recognise switching to iTerm2 hotkey window. Thus autocomplete doesn't work.
If I click on the fig icon in the top menu bar it says previous active program (for example chrome) is not supported, but I switched to the iTerm hotkey window with the hotkey.

### Steps to Reproduce
1. Focus a window of some unsupported environment, for example chrome browser.
2. Switch to iTerm hotkey window with the hotkey
3. type a command that should have autocomplete, no autocomplete appears


### Expected Results
Autocomplete suggestion box should always pop up.



### Actual Results
Autocomplete doesn't appear. When clicking on Fig. It says `chrome is not supported`.



### Environment

```bash
Version 1.0.46 (B250) [ABC]
UserShell: /bin/zsh
Bundle path: /Applications/Fig.app
Autocomplete: true
Settings.json: true
CLI installed: true
CLI tool path: /Users/hayk/.fig/bin/fig
Accessibility: true
Number of specs: 146
SSH Integration: true
Tmux Integration: true
Keybindings path: /Users/hayk/.fig/user/keybindings
iTerm Integration: true [Authenticated]
Hyper Integration: false
VSCode Integration: true
Docker Integration: false
Symlinked dotfiles: false
Only insert on tab: false
Installation Script: true
PseudoTerminal Path: /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/hayk/.fig/bin
SecureKeyboardInput: false
SecureKeyboardProcess: <none>
Current active process: ??? (???) - ???
Current working directory: ???
Current window identifier: ???
PATH: /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/hayk/.fig/bin
FIG_INTEGRATION_VERSION: 4
```


### More Detail

terminal::iTerm2

### Is this issue related to the docs?

- [ ] Yes
- [X] No

### Anything else?

_No response_",1.0,"Sometimes Fig doesn't recognise switching to iTerm2 hotkey window - ### Sanity checks

- [X] I have searched [github.com/withfig/fig/issues](https://github.com/withfig/fig/issues?q=) and there are no duplicates of my issue
- [X] My issue does not relate to a specific CLI completion spec (e.g. `git checkout` is missing options in `git` completion spec). If it does, please create your issue here: [withfig/autocomplete](https://github.com/withfig/autocomplete/issues?q=)

### Issue Details

### Summary
Sometimes Fig doesn't recognise switching to iTerm2 hotkey window. Thus autocomplete doesn't work.
If I click on the fig icon in the top menu bar it says previous active program (for example chrome) is not supported, but I switched to the iTerm hotkey window with the hotkey.

### Steps to Reproduce
1. Focus a window of some unsupported environment, for example chrome browser.
2. Switch to iTerm hotkey window with the hotkey
3. type a command that should have autocomplete, no autocomplete appears


### Expected Results
Autocomplete suggestion box should always pop up.



### Actual Results
Autocomplete doesn't appear. When clicking on Fig. It says `chrome is not supported`.



### Environment

```bash
Version 1.0.46 (B250) [ABC]
UserShell: /bin/zsh
Bundle path: /Applications/Fig.app
Autocomplete: true
Settings.json: true
CLI installed: true
CLI tool path: /Users/hayk/.fig/bin/fig
Accessibility: true
Number of specs: 146
SSH Integration: true
Tmux Integration: true
Keybindings path: /Users/hayk/.fig/user/keybindings
iTerm Integration: true [Authenticated]
Hyper Integration: false
VSCode Integration: true
Docker Integration: false
Symlinked dotfiles: false
Only insert on tab: false
Installation Script: true
PseudoTerminal Path: /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/hayk/.fig/bin
SecureKeyboardInput: false
SecureKeyboardProcess: <none>
Current active process: ??? (???) - ???
Current working directory: ???
Current window identifier: ???
PATH: /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/hayk/.fig/bin
FIG_INTEGRATION_VERSION: 4
```


### More Detail

terminal::iTerm2

### Is this issue related to the docs?

- [ ] Yes
- [X] No

### Anything else?

_No response_",0,sometimes fig doesn t recognise switching to   hotkey window       sanity checks      i have searched     and there are no duplicates of my issue     my issue does not relate to a specific cli completion spec  e g   git checkout  is missing options in  git  completion spec   if it does  please create your issue here           issue details      summary  sometimes fig doesn t recognise switching to   hotkey window  thus autocomplete doesn t work   if i click on the fig icon in the top menu bar it says previous active program  for example chrome  is not supported  but i switched to the iterm hotkey window with the hotkey         steps to reproduce     focus a window of some unsupported environment  for example chrome browser      switch to iterm hotkey window with the hotkey     type a command that should have autocomplete  no autocomplete appears          expected results  autocomplete suggestion box should always pop up             actual results  autocomplete doesn t appear  when clicking on fig  it says  chrome is not supported            environment     bash version              usershell   bin zsh  bundle path   applications fig app  autocomplete  true  settings json  true  cli installed  true  cli tool path   users hayk  fig bin fig  accessibility  true  number of specs     ssh integration  true  tmux integration  true  keybindings path   users hayk  fig user keybindings  iterm integration  true    hyper integration  false  vscode integration  true  docker integration  false  symlinked dotfiles  false  only insert on tab  false  installation script  true  pseudoterminal path   usr local bin  usr bin  bin  usr sbin  sbin  users hayk  fig bin  securekeyboardinput  false  securekeyboardprocess     current active process                   current working directory       current window identifier       path   usr local bin  usr bin  bin  usr sbin  sbin  users hayk  fig bin  fig integration version              more detail  terminal         is this issue related to the docs       yes     no      anything else    no response ,0
146730,13190199780.0,IssuesEvent,2020-08-13 09:46:23,golang/go,https://api.github.com/repos/golang/go,opened,cmd/link: help text for linkmode isn't helpful,Documentation,"```
$ go version
go version devel +5c7748dc9d Mon Aug 10 23:44:58 2020 +0000 linux/amd64
$ go tool link -h 2>&1 | grep -A1 linkmode
  -linkmode mode
    	set link mode
```

At least, it could tell me what the modes are, and ideally point me at the docs for what they do.

I realise that the compiler and linker are fairly low level and mostusers shouldn't be looking at `go tool link -h`, but given that `-linkmode=external` is somewhat well known and widely used, it's confusing that it's hard to find its definition without looking at the code.

CC @cherrymui @jeremyfaller ",1.0,"cmd/link: help text for linkmode isn't helpful - ```
$ go version
go version devel +5c7748dc9d Mon Aug 10 23:44:58 2020 +0000 linux/amd64
$ go tool link -h 2>&1 | grep -A1 linkmode
  -linkmode mode
    	set link mode
```

At least, it could tell me what the modes are, and ideally point me at the docs for what they do.

I realise that the compiler and linker are fairly low level and mostusers shouldn't be looking at `go tool link -h`, but given that `-linkmode=external` is somewhat well known and widely used, it's confusing that it's hard to find its definition without looking at the code.

CC @cherrymui @jeremyfaller ",1,cmd link  help text for linkmode isn t helpful          go version  go version devel    mon aug              linux      go tool link  h        grep    linkmode     linkmode mode      	set link mode         at least  it could tell me what the modes are  and ideally point me at the docs for what they do     i realise that the compiler and linker are fairly low level and mostusers shouldn t be looking at  go tool link  h   but given that   linkmode external  is somewhat well known and widely used  it s confusing that it s hard to find its definition without looking at the code     cc  cherrymui  jeremyfaller ,1
119034,4759755637.0,IssuesEvent,2016-10-24 23:53:03,dondi/GRNsight,https://api.github.com/repos/dondi/GRNsight,opened,Task List for Week of 10/24,logistics priority 0,"- [ ] #285, @anuvarsh will work on hiding or showing all the weights 
- [ ] #300 @yshin4 and @mihirsamdarshi will work on refactoring the test suite. @yshin4 will work on creating the semantic test for excluding all special characters except for _ and -; @mihirsamdarshi will work on creating the semanticChecker function, moving the code testing for gene name length to the checker, calling it from SIF and GraphML.
- [ ] #345 @NAnguiano will work on fixing the bug with reload #347, and then doing the rest of the toggle switches so we can have the design discussion about size/zoom/scroll/hard v. infinite boundary
- [ ] #326: @kdahlquist still has a review requested on this.",1.0,"Task List for Week of 10/24 - - [ ] #285, @anuvarsh will work on hiding or showing all the weights 
- [ ] #300 @yshin4 and @mihirsamdarshi will work on refactoring the test suite. @yshin4 will work on creating the semantic test for excluding all special characters except for _ and -; @mihirsamdarshi will work on creating the semanticChecker function, moving the code testing for gene name length to the checker, calling it from SIF and GraphML.
- [ ] #345 @NAnguiano will work on fixing the bug with reload #347, and then doing the rest of the toggle switches so we can have the design discussion about size/zoom/scroll/hard v. infinite boundary
- [ ] #326: @kdahlquist still has a review requested on this.",0,task list for week of                anuvarsh will work on hiding or showing all the weights             and  mihirsamdarshi will work on refactoring the test suite     will work on creating the semantic test for excluding all special characters except for   and     mihirsamdarshi will work on creating the semanticchecker function  moving the code testing for gene name length to the checker  calling it from sif and graphml           nanguiano will work on fixing the bug with reload     and then doing the rest of the toggle switches so we can have the design discussion about size zoom scroll hard v  infinite boundary           kdahlquist still has a review requested on this ,0
132842,12519748930.0,IssuesEvent,2020-06-03 14:52:44,golang/go,https://api.github.com/repos/golang/go,closed,cmd/internal/obj/arm64: minor mistake in pre-increment example,Documentation NeedsFix arch-arm64,"The following URL contains a minor mistake: https://golang.org/pkg/cmd/internal/obj/arm64/ 

Under point 2 (""Go uses .P and .W suffixes to indicate post-increment and pre-increment."") there is a mismatch between the Go assembly and the GNU syntax (for the pre-increment with .W suffix).

Specifically Go assembly loads a signed-byte with `MOVB` whereas the GNU syntax loads an (unsigned) 64-bit double-word with `ldr`.

So either the example should be this

```
MOVB.W 16(R16), R10        <=>      ldrsb x10, [x16,#16]!
```

or 

```
MOVD.W 16(R16), R10        <=>      ldr x10, [x16,#16]!
```

or even 

```
MOVBU.W 16(R16), R10        <=>     ldrb x10, [x16,#16]!
```
",1.0,"cmd/internal/obj/arm64: minor mistake in pre-increment example - The following URL contains a minor mistake: https://golang.org/pkg/cmd/internal/obj/arm64/ 

Under point 2 (""Go uses .P and .W suffixes to indicate post-increment and pre-increment."") there is a mismatch between the Go assembly and the GNU syntax (for the pre-increment with .W suffix).

Specifically Go assembly loads a signed-byte with `MOVB` whereas the GNU syntax loads an (unsigned) 64-bit double-word with `ldr`.

So either the example should be this

```
MOVB.W 16(R16), R10        <=>      ldrsb x10, [x16,#16]!
```

or 

```
MOVD.W 16(R16), R10        <=>      ldr x10, [x16,#16]!
```

or even 

```
MOVBU.W 16(R16), R10        <=>     ldrb x10, [x16,#16]!
```
",1,cmd internal obj    minor mistake in pre increment example   the following url contains a minor mistake        under point     go uses  p and  w suffixes to indicate post increment and pre increment    there is a mismatch between the go assembly and the gnu syntax  for the pre increment with  w suffix      specifically go assembly loads a signed byte with  movb  whereas the gnu syntax loads an  unsigned    bit double word with  ldr      so either the example should be this         movb w                       ldrsb               or          movd w                       ldr               or even          movbu w                      ldrb             ,1
24087,5027454411.0,IssuesEvent,2016-12-15 15:35:36,golang/go,https://api.github.com/repos/golang/go,closed,net: fix comment on IPv4bcast,Documentation,"The comment says `IPv4bcast = IPv4(255, 255, 255, 255) // broadcast`, but it's a limited broadcast address and should be distinguished from directed broadcast addresses.
",1.0,"net: fix comment on IPv4bcast - The comment says `IPv4bcast = IPv4(255, 255, 255, 255) // broadcast`, but it's a limited broadcast address and should be distinguished from directed broadcast addresses.
",1,net  fix comment on     the comment says                       broadcast   but it s a limited broadcast address and should be distinguished from directed broadcast addresses   ,1
163627,20363970483.0,IssuesEvent,2022-02-21 01:52:00,UNO-NULLify/eCTF20,https://api.github.com/repos/UNO-NULLify/eCTF20,opened,CVE-2022-0512 (High) detected in url-parse-1.4.7.tgz,security vulnerability,"## CVE-2022-0512 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>url-parse-1.4.7.tgz</b></p></summary>

<p>Small footprint URL parser that works seamlessly across Node.js and browser environments</p>
<p>Library home page: <a href=""https://registry.npmjs.org/url-parse/-/url-parse-1.4.7.tgz"">https://registry.npmjs.org/url-parse/-/url-parse-1.4.7.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/url-parse/package.json</p>
<p>

Dependency Hierarchy:
  - vuepress-1.4.1.tgz (Root Library)
    - core-1.4.1.tgz
      - webpack-dev-server-3.10.3.tgz
        - sockjs-client-1.4.0.tgz
          - :x: **url-parse-1.4.7.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>  
  
Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.6.

<p>Publish Date: 2022-02-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0512>CVE-2022-0512</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>8.8</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0512"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0512</a></p>
<p>Release Date: 2022-02-14</p>
<p>Fix Resolution: url-parse - 1.5.6</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-2022-0512 (High) detected in url-parse-1.4.7.tgz - ## CVE-2022-0512 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>url-parse-1.4.7.tgz</b></p></summary>

<p>Small footprint URL parser that works seamlessly across Node.js and browser environments</p>
<p>Library home page: <a href=""https://registry.npmjs.org/url-parse/-/url-parse-1.4.7.tgz"">https://registry.npmjs.org/url-parse/-/url-parse-1.4.7.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/url-parse/package.json</p>
<p>

Dependency Hierarchy:
  - vuepress-1.4.1.tgz (Root Library)
    - core-1.4.1.tgz
      - webpack-dev-server-3.10.3.tgz
        - sockjs-client-1.4.0.tgz
          - :x: **url-parse-1.4.7.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>  
  
Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.6.

<p>Publish Date: 2022-02-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0512>CVE-2022-0512</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>8.8</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0512"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0512</a></p>
<p>Release Date: 2022-02-14</p>
<p>Fix Resolution: url-parse - 1.5.6</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in url parse       tgz      cve       high severity vulnerability     vulnerable library    url parse       tgz      small footprint url parser that works seamlessly across node js and browser environments   library home page   a href     path to dependency file   package json   path to vulnerable library   node modules url parse package json     dependency hierarchy      vuepress       tgz  root library        core       tgz         webpack dev server       tgz           sockjs client       tgz              x    url parse       tgz    vulnerable library             vulnerability details         authorization bypass through user controlled key in npm url parse prior to          publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  low     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  url parse                       step up your open source security game with whitesource    ,0
71632,9531775812.0,IssuesEvent,2019-04-29 16:50:43,golang/go,https://api.github.com/repos/golang/go,closed,net: incorrect docs on KeepAlive field of Dialer,Documentation NeedsFix help wanted,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

tip

### Does this issue reproduce with the latest release?

yes

### What operating system and processor architecture are you using (`go env`)?

doesn't matter

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

Run ""go doc net Dialer"" and took a look at the output

### What did you expect to see?

At least the docs introduced by #23459 never uses the phrase ""keep-alive period"" because the existing implementation tries to tweak the keepalive idle and probe intervals, not the entire keepalive period.

### What did you see instead?`

```
// KeepAlive specifies the keep-alive period for an active
// network connection.
// If zero, keep-alives are enabled if supported by the protocol
// and operating system. Network protocols or operating systems
// that do not support keep-alives ignore this field.
// If negative, keep-alives are disabled.
KeepAlive time.Duration
```

FWIW, SetKeepAlivePeriod on TCPConn says:
```
// SetKeepAlivePeriod sets period between keep alives.
func (c *TCPConn) SetKeepAlivePeriod(d time.Duration) error {
```",1.0,"net: incorrect docs on KeepAlive field of Dialer - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

tip

### Does this issue reproduce with the latest release?

yes

### What operating system and processor architecture are you using (`go env`)?

doesn't matter

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

Run ""go doc net Dialer"" and took a look at the output

### What did you expect to see?

At least the docs introduced by #23459 never uses the phrase ""keep-alive period"" because the existing implementation tries to tweak the keepalive idle and probe intervals, not the entire keepalive period.

### What did you see instead?`

```
// KeepAlive specifies the keep-alive period for an active
// network connection.
// If zero, keep-alives are enabled if supported by the protocol
// and operating system. Network protocols or operating systems
// that do not support keep-alives ignore this field.
// If negative, keep-alives are disabled.
KeepAlive time.Duration
```

FWIW, SetKeepAlivePeriod on TCPConn says:
```
// SetKeepAlivePeriod sets period between keep alives.
func (c *TCPConn) SetKeepAlivePeriod(d time.Duration) error {
```",1,net  incorrect docs on keepalive field of dialer            what version of go are you using   go version       tip        does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env       doesn t matter        what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best          run  go doc net dialer  and took a look at the output        what did you expect to see     at least the docs introduced by    never uses the phrase  keep alive period  because the existing implementation tries to tweak the keepalive idle and probe intervals  not the entire keepalive period         what did you see instead              keepalive specifies the keep alive period for an active     network connection      if zero  keep alives are enabled if supported by the protocol     and operating system  network protocols or operating systems     that do not support keep alives ignore this field      if negative  keep alives are disabled   keepalive time duration         fwiw  setkeepaliveperiod on tcpconn says           setkeepaliveperiod sets period between keep alives   func  c  tcpconn  setkeepaliveperiod d time duration  error       ,1
84098,10475220849.0,IssuesEvent,2019-09-23 15:53:45,flutter/flutter,https://api.github.com/repos/flutter/flutter,closed,TextField's toolbar options look very ugly,d: api docs d: examples f: material design framework proposal,"Hi! 
I need to customize TextField's toolbar options view' somehow, but I just can't find a way to do it. There seems to be nothing except for boolean values that will turn some of them on and off. 
Look at this screenshot 
[Preview](https://i.ibb.co/HgytBMd/Screenshot-2019-09-22-13-21-27-219.jpg)
I need to replace the texts with icons. The problem is that those text must be in Russian, and Russian words are even longer than the English, so they won't fit the screen at all. 

Is there any way to do it? (even a hacky way will do)

 Here's the doc's stuff 
```
> $ flutter doctor
> Doctor summary (to see all details, run flutter doctor -v):
> [√] Flutter (Channel dev, v1.10.0, on Microsoft Windows [Version 6.1.7601], locale ru-RU)
> [√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
> [√] Android Studio (version 3.5)
> [!] IntelliJ IDEA Ultimate Edition (version 2018.1)
>     X Flutter plugin not installed; this adds Flutter specific functionality.
>     X Dart plugin not installed; this adds Dart specific functionality.
> [√] IntelliJ IDEA Ultimate Edition (version 2019.1)
> [!] VS Code (version 1.38.1)
>     X Flutter extension not installed; install from
>       https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
> [√] Connected device (1 available)
> 
> ! Doctor found issues in 2 categories.
```",1.0,"TextField's toolbar options look very ugly - Hi! 
I need to customize TextField's toolbar options view' somehow, but I just can't find a way to do it. There seems to be nothing except for boolean values that will turn some of them on and off. 
Look at this screenshot 
[Preview](https://i.ibb.co/HgytBMd/Screenshot-2019-09-22-13-21-27-219.jpg)
I need to replace the texts with icons. The problem is that those text must be in Russian, and Russian words are even longer than the English, so they won't fit the screen at all. 

Is there any way to do it? (even a hacky way will do)

 Here's the doc's stuff 
```
> $ flutter doctor
> Doctor summary (to see all details, run flutter doctor -v):
> [√] Flutter (Channel dev, v1.10.0, on Microsoft Windows [Version 6.1.7601], locale ru-RU)
> [√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
> [√] Android Studio (version 3.5)
> [!] IntelliJ IDEA Ultimate Edition (version 2018.1)
>     X Flutter plugin not installed; this adds Flutter specific functionality.
>     X Dart plugin not installed; this adds Dart specific functionality.
> [√] IntelliJ IDEA Ultimate Edition (version 2019.1)
> [!] VS Code (version 1.38.1)
>     X Flutter extension not installed; install from
>       https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
> [√] Connected device (1 available)
> 
> ! Doctor found issues in 2 categories.
```",0,textfield s toolbar options look very ugly   hi    i need to customize textfield s toolbar options view  somehow  but i just can t find a way to do it  there seems to be nothing except for boolean values that will turn some of them on and off    look at this screenshot        i need to replace the texts with icons  the problem is that those text must be in russian  and russian words are even longer than the english  so they won t fit the screen at all      is there any way to do it   even a hacky way will do      here s the doc s stuff            flutter doctor    doctor summary  to see all details  run flutter doctor  v        flutter  channel dev         on microsoft windows    locale ru ru       android toolchain   develop for android devices  android sdk version             android studio  version           intellij idea ultimate edition  version             x flutter plugin not installed  this adds flutter specific functionality         x dart plugin not installed  this adds dart specific functionality       intellij idea ultimate edition  version           vs code  version               x flutter extension not installed  install from                 connected device    available           doctor found issues in   categories      ,0
4069,2814167590.0,IssuesEvent,2015-05-18 18:30:28,golang/go,https://api.github.com/repos/golang/go,closed,"spec: ""TO"" != ""T0"" in spec",Documentation,"In [this example](https://github.com/golang/go/blob/master/doc/go_spec.html#L2608):

````go
t.x          // (*t.TO).x
````

I think it is supposed to read:

````go
t.x          // (*t.T0).x
````
",1.0,"spec: ""TO"" != ""T0"" in spec - In [this example](https://github.com/golang/go/blob/master/doc/go_spec.html#L2608):

````go
t.x          // (*t.TO).x
````

I think it is supposed to read:

````go
t.x          // (*t.T0).x
````
",1,spec   to         in spec   in            go  t x               t to  x          i think it is supposed to read         go  t x               t    x        ,1
71319,9489547682.0,IssuesEvent,2019-04-22 23:01:25,golang/go,https://api.github.com/repos/golang/go,closed,net/http: document that Request.SetBasicAuth doesn't do any additional escaping,Documentation NeedsFix,"### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.12.4 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What did you do?

Call [`req.SetBasicAuth(user, pass)`](https://golang.org/pkg/net/http/#Request.SetBasicAuth) with special characters in either the username or the password, e.g.:
```go
	req, err := http.NewRequest(""POST"", ""http://127.0.0.1/foo"", nil)
	req.SetBasicAuth(""foo"", ""bar+baz"")
	if err != nil {
		panic(err)
	}
	fmt.Println(req.Header.Get(""Authorization""))
```

### What did you expect to see?

The above program should probably print `Basic Zm9vOmJhciUyQmJheg==`

### What did you see instead?

The above program prints `Basic Zm9vOmJhcitiYXo=`

### Discussion

So I spent a long long _long_ time debugging some OpenID Connect authentication issue with `kubectl` and [dex](https://github.com/dexidp/dex). Long story short, it turns out that the random client secret I had generated contained a `+` sign and it needed to be URL encoded before being base64-encoded when used with basic auth.

After looking at the code in Kubernetes and various other projects, I realized that nobody ever escapes the arguments passed to `SetBasicAuth()`. So this issue is extremely widespread.  In fact the bug was even present in Go's own OAuth2 implementation until golang/oauth2#237 fixed it.

The godoc doesn't say anything about escaping so it's not clear to me whether the intent was to have users do it themselves (and, clearly, they don't) or, more likely, this was just an unfortunate omission (i.e. a bug) when the library was implemented.

Given how widespread this issue is, I think the standard library should do the URL encoding automagically.  Now since there are some callers that already do it (e.g. the OAuth2 library after the fix mentioned above), this means that the code should probably make a pass through the strings it's given and if they contain anything that needs escaping, then escape the whole string, otherwise use the string as-is.

If you guys disagree that the library should take care of escaping the arguments, then at the very least the godoc should be updated to explicitly state that the strings must be URL-safe or URL encoded.  But I strongly think that the library should just make it work automatically given that virtually none of the existing code out there does this properly.

Granted this problem is probably not that likely to occur in practice, again I hit it because I used a random string of ASCII characters as a client secret, and there was a `+` in there.  So `kubectl` worked for a while but once it needed to refresh its token, I'd get a mysterious 401 due to this bug.",1.0,"net/http: document that Request.SetBasicAuth doesn't do any additional escaping - ### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.12.4 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What did you do?

Call [`req.SetBasicAuth(user, pass)`](https://golang.org/pkg/net/http/#Request.SetBasicAuth) with special characters in either the username or the password, e.g.:
```go
	req, err := http.NewRequest(""POST"", ""http://127.0.0.1/foo"", nil)
	req.SetBasicAuth(""foo"", ""bar+baz"")
	if err != nil {
		panic(err)
	}
	fmt.Println(req.Header.Get(""Authorization""))
```

### What did you expect to see?

The above program should probably print `Basic Zm9vOmJhciUyQmJheg==`

### What did you see instead?

The above program prints `Basic Zm9vOmJhcitiYXo=`

### Discussion

So I spent a long long _long_ time debugging some OpenID Connect authentication issue with `kubectl` and [dex](https://github.com/dexidp/dex). Long story short, it turns out that the random client secret I had generated contained a `+` sign and it needed to be URL encoded before being base64-encoded when used with basic auth.

After looking at the code in Kubernetes and various other projects, I realized that nobody ever escapes the arguments passed to `SetBasicAuth()`. So this issue is extremely widespread.  In fact the bug was even present in Go's own OAuth2 implementation until golang/oauth2#237 fixed it.

The godoc doesn't say anything about escaping so it's not clear to me whether the intent was to have users do it themselves (and, clearly, they don't) or, more likely, this was just an unfortunate omission (i.e. a bug) when the library was implemented.

Given how widespread this issue is, I think the standard library should do the URL encoding automagically.  Now since there are some callers that already do it (e.g. the OAuth2 library after the fix mentioned above), this means that the code should probably make a pass through the strings it's given and if they contain anything that needs escaping, then escape the whole string, otherwise use the string as-is.

If you guys disagree that the library should take care of escaping the arguments, then at the very least the godoc should be updated to explicitly state that the strings must be URL-safe or URL encoded.  But I strongly think that the library should just make it work automatically given that virtually none of the existing code out there does this properly.

Granted this problem is probably not that likely to occur in practice, again I hit it because I used a random string of ASCII characters as a client secret, and there was a `+` in there.  So `kubectl` worked for a while but once it needed to refresh its token, I'd get a mysterious 401 due to this bug.",1,net http  document that request setbasicauth doesn t do any additional escaping       what version of go are you using   go version            go version  go version       darwin             does this issue reproduce with the latest release     yes         what did you do     call     with special characters in either the username or the password  e g       go  	req  err    http newrequest  post      nil   	req setbasicauth  foo    bar baz    	if err    nil    		panic err   	   	fmt println req header get  authorization                what did you expect to see     the above program should probably print  basic             what did you see instead     the above program prints  basic            discussion    so i spent a long long  long  time debugging some openid connect authentication issue with  kubectl  and     long story short  it turns out that the random client secret i had generated contained a     sign and it needed to be url encoded before being   encoded when used with basic auth     after looking at the code in kubernetes and various other projects  i realized that nobody ever escapes the arguments passed to  setbasicauth     so this issue is extremely widespread   in fact the bug was even present in go s own   implementation until golang     fixed it     the godoc doesn t say anything about escaping so it s not clear to me whether the intent was to have users do it themselves  and  clearly  they don t  or  more likely  this was just an unfortunate omission  i e  a bug  when the library was implemented     given how widespread this issue is  i think the standard library should do the url encoding automagically   now since there are some callers that already do it  e g  the   library after the fix mentioned above   this means that the code should probably make a pass through the strings it s given and if they contain anything that needs escaping  then escape the whole string  otherwise use the string as is     if you guys disagree that the library should take care of escaping the arguments  then at the very least the godoc should be updated to explicitly state that the strings must be url safe or url encoded   but i strongly think that the library should just make it work automatically given that virtually none of the existing code out there does this properly     granted this problem is probably not that likely to occur in practice  again i hit it because i used a random string of ascii characters as a client secret  and there was a     in there   so  kubectl  worked for a while but once it needed to refresh its token  i d get a mysterious   due to this bug ,1
91145,3838119293.0,IssuesEvent,2016-04-02 06:01:53,cs2103jan2016-f13-4j/main,https://api.github.com/repos/cs2103jan2016-f13-4j/main,opened,Store user preferences in JSON format,priority.high type.task,Includes information of where user wants to store Task data ,1.0,Store user preferences in JSON format - Includes information of where user wants to store Task data ,0,store user preferences in json format   includes information of where user wants to store task data ,0
238468,19722455615.0,IssuesEvent,2022-01-13 16:35:08,infoderm/patients,https://api.github.com/repos/infoderm/patients,opened,"Write first automated ""button-clicking"" test",testing,"Examples:
  - [ ] Use should log in with a non-existing account and fail.
  - [ ] User should create an account, log in, see the home screen, log out.
  - [ ] User should create an account, log in, change their password, log out, log in with new password.

See: 
  - https://www.benmvp.com/blog/asynchronous-testing-with-enzyme-react-jest/",1.0,"Write first automated ""button-clicking"" test - Examples:
  - [ ] Use should log in with a non-existing account and fail.
  - [ ] User should create an account, log in, see the home screen, log out.
  - [ ] User should create an account, log in, change their password, log out, log in with new password.

See: 
  - https://www.benmvp.com/blog/asynchronous-testing-with-enzyme-react-jest/",0,write first automated  button clicking  test   examples         use should log in with a non existing account and fail         user should create an account  log in  see the home screen  log out         user should create an account  log in  change their password  log out  log in with new password     see         ,0
361577,25344101415.0,IssuesEvent,2022-11-19 02:32:39,golang/go,https://api.github.com/repos/golang/go,closed,net/http: Server.Serve returns an error when the Listener is closed,Documentation,"net/http.Server.Serve returns an error when the Listener argument is closed, which means you cannot gracefully stop the server (no error returned). It should instead check if the Listener is closed and return nil if so.
",1.0,"net/http: Server.Serve returns an error when the Listener is closed - net/http.Server.Serve returns an error when the Listener argument is closed, which means you cannot gracefully stop the server (no error returned). It should instead check if the Listener is closed and return nil if so.
",1,net http  server serve returns an error when the listener is closed   net http server serve returns an error when the listener argument is closed  which means you cannot gracefully stop the server  no error returned   it should instead check if the listener is closed and return nil if so  ,1
46957,19553283820.0,IssuesEvent,2022-01-03 03:31:57,PreMiD/Presences,https://api.github.com/repos/PreMiD/Presences,opened,Veepee | veepee.com,🌍 Region Restricted Service Request,"### Discussed in https://github.com/PreMiD/Presences/discussions/4544

<div type='discussions-op-text'>

<sup>Originally posted by **MaXfAa** January 19, 2021</sup>
**Prerequisites and essential questions** <!--- Required, please answer the following questions as honestly as possible by changing the ""[ ]"" to ""[x]"" or by marking it after creating the issue (easier), not marking a question counts as ""No"". -->
- [x] Is it a popular site?
- [x] Is the website older than 2 months? <!--- It is necessary for the website to be older than 2 months. -->
- [ ] Is the site locked to a specific country/region?
- [ ] Is the site a paid service? (e.g. Netflix, Hulu)
- [ ] Does the website feature NSFW content? (e.g. porn, etc...)
- [ ] Are you a donator/patron?
- [x] Do you acknowledge that coding presences is completely voluntary and may take time for your service to be added regardless of priority?

**What's your Discord username?** <!--- Optional, unless you are a donator/patron. Ex. Clyde#0000 -->
Maxou#1909

**What's the name of the service?** <!--- Required, Ex. www.youtube.com | YouTube -->
Veepee |
1. https://www.veepee.fr/
2. https://www.veepee.be/
3. https://www.veepee.com/

**What should the Presence display?** <!--- Required, make sure to be as clear as possible on what should be added. -->
A bit like Zalando

**If possible, please provide a logo for the service (512x512 minimum)** <!--- Optional, it is recommended to upload the image here instead of using a 3rd-party host. -->
https://s1.qwant.com/thumbr/0x380/b/4/88b8e2c08f2ce747af0abc8d671297f4107abd79bb92846fcf0347408d7946/512x512bb.jpg?u=https%3A%2F%2Fis2-ssl.mzstatic.com%2Fimage%2Fthumb%2FPurple124%2Fv4%2F07%2F54%2F61%2F0754611c-ff41-6f8a-1697-f9d9721097fb%2Fsource%2F512x512bb.jpg&q=0&b=1&p=0&a=1
</div>",1.0,"Veepee | veepee.com - ### Discussed in https://github.com/PreMiD/Presences/discussions/4544

<div type='discussions-op-text'>

<sup>Originally posted by **MaXfAa** January 19, 2021</sup>
**Prerequisites and essential questions** <!--- Required, please answer the following questions as honestly as possible by changing the ""[ ]"" to ""[x]"" or by marking it after creating the issue (easier), not marking a question counts as ""No"". -->
- [x] Is it a popular site?
- [x] Is the website older than 2 months? <!--- It is necessary for the website to be older than 2 months. -->
- [ ] Is the site locked to a specific country/region?
- [ ] Is the site a paid service? (e.g. Netflix, Hulu)
- [ ] Does the website feature NSFW content? (e.g. porn, etc...)
- [ ] Are you a donator/patron?
- [x] Do you acknowledge that coding presences is completely voluntary and may take time for your service to be added regardless of priority?

**What's your Discord username?** <!--- Optional, unless you are a donator/patron. Ex. Clyde#0000 -->
Maxou#1909

**What's the name of the service?** <!--- Required, Ex. www.youtube.com | YouTube -->
Veepee |
1. https://www.veepee.fr/
2. https://www.veepee.be/
3. https://www.veepee.com/

**What should the Presence display?** <!--- Required, make sure to be as clear as possible on what should be added. -->
A bit like Zalando

**If possible, please provide a logo for the service (512x512 minimum)** <!--- Optional, it is recommended to upload the image here instead of using a 3rd-party host. -->
https://s1.qwant.com/thumbr/0x380/b/4/88b8e2c08f2ce747af0abc8d671297f4107abd79bb92846fcf0347408d7946/512x512bb.jpg?u=https%3A%2F%2Fis2-ssl.mzstatic.com%2Fimage%2Fthumb%2FPurple124%2Fv4%2F07%2F54%2F61%2F0754611c-ff41-6f8a-1697-f9d9721097fb%2Fsource%2F512x512bb.jpg&q=0&b=1&p=0&a=1
</div>",0,veepee   veepee com       discussed in            originally posted by   maxfaa   january          prerequisites and essential questions          is it a popular site       is the website older than   months         is the site locked to a specific country region       is the site a paid service   e g  netflix  hulu       does the website feature nsfw content   e g  porn  etc          are you a donator patron       do you acknowledge that coding presences is completely voluntary and may take time for your service to be added regardless of priority       what s your discord username       maxou        what s the name of the service       veepee                          what should the presence display       a bit like zalando      if possible  please provide a logo for the service    minimum           ,0
83763,10338182641.0,IssuesEvent,2019-09-03 16:19:15,golang/go,https://api.github.com/repos/golang/go,opened,Proposal: move mature wiki content behind Gerrit,Documentation Proposal,"### Summary

The [Go Wiki](https://github.com/golang/go/wiki) has over 160 pages, and a set of rules that aren't being followed. There also isn't an effective review process in place, as we explain further below.

I propose that we move the mature content behind Gerrit, to better ensure its quality and maintainability, and so that it can be blessed without fear of uncontrolled edits.

This proposal does not cover what to do with the rest of the wiki content, or what to do with the existing wiki itself. That is left for another proposal to tackle.

### Problem statement

It's only possible to have Go's wiki [readable or writable by everyone](https://help.github.com/en/articles/changing-access-permissions-for-wikis). The Go project opted for anyone to edit them.

This has the advantage that the barrier to entry is low. However, this also means that there's no review process involved, and anyone can create a new wiki page at any time. The main wiki page reads:

> * This wiki is open to editing by any member of the Go community with a GitHub account.
> * If you would like to add a new page, please first open an issue in the [Go issue tracker](https://github.com/golang/go/issues) [...].
> * [...] please open an issue before renaming or removing any wiki page.

However, it doesn't look like the process to add new pages works. With 160 pages, I could only find about a dozen issues requesting the addition of a new wiki page after a five minute search, with queries like `is:issue wiki page in:title`.

The quality of the pages also varies greatly. Some of them were written or maintained by the Go team, such as [CodeReviewComments](https://github.com/golang/go/wiki/CodeReviewComments), [Modules](https://github.com/golang/go/wiki/Modules), and [AssemblyPolicy](https://github.com/golang/go/wiki/AssemblyPolicy). These are well reviewed, and are often considered ""blessed"" by the Go project.

On the other hand, many others have never been approved by a Go issue and have gone through no proper reviews anywhere public. Note that I'm not attaching any examples here to not point any fingers at any wiki authors.

The other side of the problem is that, while the wiki is often cited as being ""maintained by the Go community"", many Go users treat anything under the `golang/go` repository as being blessed by the Go team. This is an understandable misconception, as the repository is otherwise under the team's supervision.

Finally, there is https://groups.google.com/forum/#!forum/golang-wikichanges, but that's a system that requires lots of active attention and ultimately isn't as effective as code review. As an example, the Modules page was deleted on August 26th, so the page was gone until someone noticed and reverted the edit.

### Proposed solution

Important documentation should go through the review process, just like code and godoc changes do. There's currently no way to do that with GitHub Wikis.

I propose the following steps:

1) Announce the plan below to golang-dev and golang-nuts, and update the main wiki page
2) Gradually move relevant wiki pages somewhere under Gerrit, such as an `x/doc` or `x/wiki` repository
3) Start making these pages available somewhere official, such as under golang.org/doc or golang.org/wiki
4) Modify the moved Wiki pages to link or redirect to their new locations",1.0,"Proposal: move mature wiki content behind Gerrit - ### Summary

The [Go Wiki](https://github.com/golang/go/wiki) has over 160 pages, and a set of rules that aren't being followed. There also isn't an effective review process in place, as we explain further below.

I propose that we move the mature content behind Gerrit, to better ensure its quality and maintainability, and so that it can be blessed without fear of uncontrolled edits.

This proposal does not cover what to do with the rest of the wiki content, or what to do with the existing wiki itself. That is left for another proposal to tackle.

### Problem statement

It's only possible to have Go's wiki [readable or writable by everyone](https://help.github.com/en/articles/changing-access-permissions-for-wikis). The Go project opted for anyone to edit them.

This has the advantage that the barrier to entry is low. However, this also means that there's no review process involved, and anyone can create a new wiki page at any time. The main wiki page reads:

> * This wiki is open to editing by any member of the Go community with a GitHub account.
> * If you would like to add a new page, please first open an issue in the [Go issue tracker](https://github.com/golang/go/issues) [...].
> * [...] please open an issue before renaming or removing any wiki page.

However, it doesn't look like the process to add new pages works. With 160 pages, I could only find about a dozen issues requesting the addition of a new wiki page after a five minute search, with queries like `is:issue wiki page in:title`.

The quality of the pages also varies greatly. Some of them were written or maintained by the Go team, such as [CodeReviewComments](https://github.com/golang/go/wiki/CodeReviewComments), [Modules](https://github.com/golang/go/wiki/Modules), and [AssemblyPolicy](https://github.com/golang/go/wiki/AssemblyPolicy). These are well reviewed, and are often considered ""blessed"" by the Go project.

On the other hand, many others have never been approved by a Go issue and have gone through no proper reviews anywhere public. Note that I'm not attaching any examples here to not point any fingers at any wiki authors.

The other side of the problem is that, while the wiki is often cited as being ""maintained by the Go community"", many Go users treat anything under the `golang/go` repository as being blessed by the Go team. This is an understandable misconception, as the repository is otherwise under the team's supervision.

Finally, there is https://groups.google.com/forum/#!forum/golang-wikichanges, but that's a system that requires lots of active attention and ultimately isn't as effective as code review. As an example, the Modules page was deleted on August 26th, so the page was gone until someone noticed and reverted the edit.

### Proposed solution

Important documentation should go through the review process, just like code and godoc changes do. There's currently no way to do that with GitHub Wikis.

I propose the following steps:

1) Announce the plan below to golang-dev and golang-nuts, and update the main wiki page
2) Gradually move relevant wiki pages somewhere under Gerrit, such as an `x/doc` or `x/wiki` repository
3) Start making these pages available somewhere official, such as under golang.org/doc or golang.org/wiki
4) Modify the moved Wiki pages to link or redirect to their new locations",1,proposal  move mature wiki content behind gerrit       summary    the     has over   pages  and a set of rules that aren t being followed  there also isn t an effective review process in place  as we explain further below     i propose that we move the mature content behind gerrit  to better ensure its quality and maintainability  and so that it can be blessed without fear of uncontrolled edits     this proposal does not cover what to do with the rest of the wiki content  or what to do with the existing wiki itself  that is left for another proposal to tackle         problem statement    it s only possible to have go s wiki     the go project opted for anyone to edit them     this has the advantage that the barrier to entry is low  however  this also means that there s no review process involved  and anyone can create a new wiki page at any time  the main wiki page reads         this wiki is open to editing by any member of the go community with a github account       if you would like to add a new page  please first open an issue in the               please open an issue before renaming or removing any wiki page     however  it doesn t look like the process to add new pages works  with   pages  i could only find about a dozen issues requesting the addition of a new wiki page after a five minute search  with queries like  is issue wiki page in title      the quality of the pages also varies greatly  some of them were written or maintained by the go team  such as         and     these are well reviewed  and are often considered  blessed  by the go project     on the other hand  many others have never been approved by a go issue and have gone through no proper reviews anywhere public  note that i m not attaching any examples here to not point any fingers at any wiki authors     the other side of the problem is that  while the wiki is often cited as being  maintained by the go community   many go users treat anything under the  golang go  repository as being blessed by the go team  this is an understandable misconception  as the repository is otherwise under the team s supervision     finally  there is   but that s a system that requires lots of active attention and ultimately isn t as effective as code review  as an example  the modules page was deleted on august    so the page was gone until someone noticed and reverted the edit         proposed solution    important documentation should go through the review process  just like code and godoc changes do  there s currently no way to do that with github wikis     i propose the following steps        announce the plan below to golang dev and golang nuts  and update the main wiki page     gradually move relevant wiki pages somewhere under gerrit  such as an  x doc  or  x wiki  repository     start making these pages available somewhere official  such as under golang org doc or golang org wiki     modify the moved wiki pages to link or redirect to their new locations,1
104411,16615839753.0,IssuesEvent,2021-06-02 16:32:27,idonthaveafifaaddiction/minio,https://api.github.com/repos/idonthaveafifaaddiction/minio,opened,CVE-2020-7789 (Medium) detected in node-notifier-5.4.3.tgz,security vulnerability,"## CVE-2020-7789 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-notifier-5.4.3.tgz</b></p></summary>

<p>A Node.js module for sending notifications on native Mac, Windows (post and pre 8) and Linux (or Growl as fallback)</p>
<p>Library home page: <a href=""https://registry.npmjs.org/node-notifier/-/node-notifier-5.4.3.tgz"">https://registry.npmjs.org/node-notifier/-/node-notifier-5.4.3.tgz</a></p>
<p>Path to dependency file: minio/browser/package.json</p>
<p>Path to vulnerable library: minio/browser/node_modules/node-notifier/package.json</p>
<p>

Dependency Hierarchy:
  - jest-23.6.0.tgz (Root Library)
    - jest-cli-23.6.0.tgz
      - :x: **node-notifier-5.4.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/idonthaveafifaaddiction/minio/commit/faa7ae734fc4db219ed0f110588840a84a6e277d"">faa7ae734fc4db219ed0f110588840a84a6e277d</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>  
  
This affects the package node-notifier before 9.0.0. It allows an attacker to run arbitrary commands on Linux machines due to the options params not being sanitised when being passed an array.

<p>Publish Date: 2020-12-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7789>CVE-2020-7789</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.6</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7789"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7789</a></p>
<p>Release Date: 2020-12-11</p>
<p>Fix Resolution: 9.0.0</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":false,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""node-notifier"",""packageVersion"":""5.4.3"",""packageFilePaths"":[""/browser/package.json""],""isTransitiveDependency"":true,""dependencyTree"":""jest:23.6.0;jest-cli:23.6.0;node-notifier:5.4.3"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""9.0.0""}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""CVE-2020-7789"",""vulnerabilityDetails"":""This affects the package node-notifier before 9.0.0. It allows an attacker to run arbitrary commands on Linux machines due to the options params not being sanitised when being passed an array."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7789"",""cvss3Severity"":""medium"",""cvss3Score"":""5.6"",""cvss3Metrics"":{""A"":""Low"",""AC"":""High"",""PR"":""None"",""S"":""Unchanged"",""C"":""Low"",""UI"":""None"",""AV"":""Network"",""I"":""Low""},""extraData"":{}}</REMEDIATE> -->",True,"CVE-2020-7789 (Medium) detected in node-notifier-5.4.3.tgz - ## CVE-2020-7789 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-notifier-5.4.3.tgz</b></p></summary>

<p>A Node.js module for sending notifications on native Mac, Windows (post and pre 8) and Linux (or Growl as fallback)</p>
<p>Library home page: <a href=""https://registry.npmjs.org/node-notifier/-/node-notifier-5.4.3.tgz"">https://registry.npmjs.org/node-notifier/-/node-notifier-5.4.3.tgz</a></p>
<p>Path to dependency file: minio/browser/package.json</p>
<p>Path to vulnerable library: minio/browser/node_modules/node-notifier/package.json</p>
<p>

Dependency Hierarchy:
  - jest-23.6.0.tgz (Root Library)
    - jest-cli-23.6.0.tgz
      - :x: **node-notifier-5.4.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/idonthaveafifaaddiction/minio/commit/faa7ae734fc4db219ed0f110588840a84a6e277d"">faa7ae734fc4db219ed0f110588840a84a6e277d</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>  
  
This affects the package node-notifier before 9.0.0. It allows an attacker to run arbitrary commands on Linux machines due to the options params not being sanitised when being passed an array.

<p>Publish Date: 2020-12-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7789>CVE-2020-7789</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.6</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7789"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7789</a></p>
<p>Release Date: 2020-12-11</p>
<p>Fix Resolution: 9.0.0</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":false,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""node-notifier"",""packageVersion"":""5.4.3"",""packageFilePaths"":[""/browser/package.json""],""isTransitiveDependency"":true,""dependencyTree"":""jest:23.6.0;jest-cli:23.6.0;node-notifier:5.4.3"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""9.0.0""}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""CVE-2020-7789"",""vulnerabilityDetails"":""This affects the package node-notifier before 9.0.0. It allows an attacker to run arbitrary commands on Linux machines due to the options params not being sanitised when being passed an array."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7789"",""cvss3Severity"":""medium"",""cvss3Score"":""5.6"",""cvss3Metrics"":{""A"":""Low"",""AC"":""High"",""PR"":""None"",""S"":""Unchanged"",""C"":""Low"",""UI"":""None"",""AV"":""Network"",""I"":""Low""},""extraData"":{}}</REMEDIATE> -->",0,cve      medium  detected in node notifier       tgz      cve       medium severity vulnerability     vulnerable library    node notifier       tgz      a node js module for sending notifications on native mac  windows  post and pre    and linux  or growl as fallback    library home page   a href     path to dependency file  minio browser package json   path to vulnerable library  minio browser node modules node notifier package json     dependency hierarchy      jest       tgz  root library        jest cli       tgz          x    node notifier       tgz    vulnerable library   found in head commit   a href     found in base branch   master              vulnerability details         this affects the package node notifier before        it allows an attacker to run arbitrary commands on linux machines due to the options params not being sanitised when being passed an array    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  low     integrity impact  low     availability impact  low   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                     isopenpronvulnerability  false  ispackagebased  true  isdefaultbranch  true  packages     istransitivedependency  true  dependencytree   jest       jest cli       node notifier         isminimumfixversionavailable  true  minimumfixversion             basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   this affects the package node notifier before        it allows an attacker to run arbitrary commands on linux machines due to the options params not being sanitised when being passed an array    vulnerabilityurl        ,0
360854,25313917602.0,IssuesEvent,2022-11-17 19:50:13,golang/go,https://api.github.com/repos/golang/go,closed,sync/atomic: document hint in the old APIs to point out that the new named types exist,Documentation compiler/runtime,"I posted the proposal of deprecated old APIs of sync/atomic.
ref: https://github.com/golang/go/issues/55302

Finally, this proposal was declined, but I think it's better to have a hint to the old APIs to point out and recommend that the new named types exist.",1.0,"sync/atomic: document hint in the old APIs to point out that the new named types exist - I posted the proposal of deprecated old APIs of sync/atomic.
ref: https://github.com/golang/go/issues/55302

Finally, this proposal was declined, but I think it's better to have a hint to the old APIs to point out and recommend that the new named types exist.",1,sync atomic  document hint in the old apis to point out that the new named types exist   i posted the proposal of deprecated old apis of sync atomic   ref       finally  this proposal was declined  but i think it s better to have a hint to the old apis to point out and recommend that the new named types exist ,1
135077,12663369662.0,IssuesEvent,2020-06-18 01:08:03,golang/go,https://api.github.com/repos/golang/go,closed,net/rpc: unclear documentation for Call.Done,Documentation NeedsDecision,"```
$ go doc net/rpc Call.Done
package rpc // import ""net/rpc""

type Call struct {
    Done chan *Call  // Strobes when call is complete.

    // ... other fields elided ...
}
```

What does ""strobes"" mean in this context? Let's reword.

cc @robpike 
",1.0,"net/rpc: unclear documentation for Call.Done - ```
$ go doc net/rpc Call.Done
package rpc // import ""net/rpc""

type Call struct {
    Done chan *Call  // Strobes when call is complete.

    // ... other fields elided ...
}
```

What does ""strobes"" mean in this context? Let's reword.

cc @robpike 
",1,net rpc  unclear documentation for call done          go doc net rpc call done  package rpc    import  net rpc     type call struct        done chan  call     strobes when call is complete                other fields elided                what does  strobes  mean in this context  let s reword     cc  robpike   ,1
6503,3025028806.0,IssuesEvent,2015-08-03 04:01:35,golang/go,https://api.github.com/repos/golang/go,closed,doc: 1.5 release notes don't mention linker's new -X pkg.name=value syntax,Documentation,"[CL 10310](https://go-review.googlesource.com/#/c/10310/) introduced the new syntax for linker's -X flag. While the old syntax is still accepted, the CL states that it may be deprecated some day. It should be added to the release notes, possibly with a recommendation to replace scripts with old syntax to the new one.",1.0,"doc: 1.5 release notes don't mention linker's new -X pkg.name=value syntax - [CL 10310](https://go-review.googlesource.com/#/c/10310/) introduced the new syntax for linker's -X flag. While the old syntax is still accepted, the CL states that it may be deprecated some day. It should be added to the release notes, possibly with a recommendation to replace scripts with old syntax to the new one.",1,doc      release notes don t mention linker s new  x pkg name value syntax       introduced the new syntax for linker s  x flag  while the old syntax is still accepted  the cl states that it may be deprecated some day  it should be added to the release notes  possibly with a recommendation to replace scripts with old syntax to the new one ,1
270956,20616352457.0,IssuesEvent,2022-03-07 13:36:53,golang/go,https://api.github.com/repos/golang/go,closed,doc: update FAQ for the arrival of parametric polymorphism,Documentation NeedsFix,"Many sections of the FAQ need tweaking, a few need replacement. Update before release.

For example, here's a question there that needs to be rethought: ""Why does Go not have generic types?""",1.0,"doc: update FAQ for the arrival of parametric polymorphism - Many sections of the FAQ need tweaking, a few need replacement. Update before release.

For example, here's a question there that needs to be rethought: ""Why does Go not have generic types?""",1,doc  update faq for the arrival of parametric polymorphism   many sections of the faq need tweaking  a few need replacement  update before release     for example  here s a question there that needs to be rethought   why does go not have generic types  ,1
316583,9651980988.0,IssuesEvent,2019-05-18 13:11:19,the-blue-alliance/the-blue-alliance-ios,https://api.github.com/repos/the-blue-alliance/the-blue-alliance-ios,closed,Teams are not sorted until pulling down to refresh,bug high priority,"<!--- Provide a general summary of the issue in the Title above -->
When selecting the competition (in this particular instance, 2019 Daly Championship Division), but I saw it with other divisions, the teams are not sorted by rank until pulled down (to refresh).


## Expected Behavior
When I tap on the rankings tab, all teams should be sorted by ranking

## Current Behavior
After not using the app for some time (in my case, it was several hours), I tapped on a competition name, In this case, 2019 Daly Championship Division, and saw the teams were not sorted by rank. I can't remember if I had accessed the app after matches had ended the day prior to noticing this bug. After pulling down to refresh, the teams were sorted. My conjecture is that it pulled updated data from the TBA API when I opened up the competition, but did not perform a sort operation.

## Screenshots
<!--- Screenshots demonstrating bugs or existing functionality -->
![IMG_0594](https://user-images.githubusercontent.com/1720392/56842399-b25c7c00-6862-11e9-89f9-967801621ffc.PNG)

## Steps to Reproduce
<!--- Provide steps for how to reproduce this bug or state -->
1. During a competition day (when rankings are changing), use the app to view different active competitions (and probably view rankings at some point)
2. Wait a few hours
3. Open up the app back up and access the same competitions accessed in step 1. (this can be after competition is done for the day)
4. Tap on the rankings (At this point, they will probably be unsorted, but wins/losses/ranking appear to be complete and correct)
5. Pull down to refresh (teams are now sorted by ranking).

## Your Environment
<!--- Include as many relevant details about the environment you experienced the bug in -->
* Device: iPhone X
* iOS version: 12.2
* TBA for iOS version: v1.0.11 (35)

## Context
<!--- How has this issue affected you? What are you trying to accomplish? -->
<!--- Providing context helps us come up with a solution that is most useful in the real world -->
I am just a user wanting to know how a few teams I am interested in are doing and to see how the rankings have panned out at the championship competitions.

## Possible Solution
<!--- Not obligatory, but suggest a fix/reason for the bug, -->
<!--- or ideas how to implement the addition or change -->
I don't know anything about iOS programming, but my gut feeling is that while data is pulled from the TBA API when clicking on the ranking tab (or at some point prior), sorting by ranking isn't accomplished by this operation. Perhaps there's some race condition? Does sorting happen when the ranking tab is tapped, but doesn't have the data from the API yet?",1.0,"Teams are not sorted until pulling down to refresh - <!--- Provide a general summary of the issue in the Title above -->
When selecting the competition (in this particular instance, 2019 Daly Championship Division), but I saw it with other divisions, the teams are not sorted by rank until pulled down (to refresh).


## Expected Behavior
When I tap on the rankings tab, all teams should be sorted by ranking

## Current Behavior
After not using the app for some time (in my case, it was several hours), I tapped on a competition name, In this case, 2019 Daly Championship Division, and saw the teams were not sorted by rank. I can't remember if I had accessed the app after matches had ended the day prior to noticing this bug. After pulling down to refresh, the teams were sorted. My conjecture is that it pulled updated data from the TBA API when I opened up the competition, but did not perform a sort operation.

## Screenshots
<!--- Screenshots demonstrating bugs or existing functionality -->
![IMG_0594](https://user-images.githubusercontent.com/1720392/56842399-b25c7c00-6862-11e9-89f9-967801621ffc.PNG)

## Steps to Reproduce
<!--- Provide steps for how to reproduce this bug or state -->
1. During a competition day (when rankings are changing), use the app to view different active competitions (and probably view rankings at some point)
2. Wait a few hours
3. Open up the app back up and access the same competitions accessed in step 1. (this can be after competition is done for the day)
4. Tap on the rankings (At this point, they will probably be unsorted, but wins/losses/ranking appear to be complete and correct)
5. Pull down to refresh (teams are now sorted by ranking).

## Your Environment
<!--- Include as many relevant details about the environment you experienced the bug in -->
* Device: iPhone X
* iOS version: 12.2
* TBA for iOS version: v1.0.11 (35)

## Context
<!--- How has this issue affected you? What are you trying to accomplish? -->
<!--- Providing context helps us come up with a solution that is most useful in the real world -->
I am just a user wanting to know how a few teams I am interested in are doing and to see how the rankings have panned out at the championship competitions.

## Possible Solution
<!--- Not obligatory, but suggest a fix/reason for the bug, -->
<!--- or ideas how to implement the addition or change -->
I don't know anything about iOS programming, but my gut feeling is that while data is pulled from the TBA API when clicking on the ranking tab (or at some point prior), sorting by ranking isn't accomplished by this operation. Perhaps there's some race condition? Does sorting happen when the ranking tab is tapped, but doesn't have the data from the API yet?",0,teams are not sorted until pulling down to refresh      when selecting the competition  in this particular instance    daly championship division   but i saw it with other divisions  the teams are not sorted by rank until pulled down  to refresh           expected behavior  when i tap on the rankings tab  all teams should be sorted by ranking       current behavior  after not using the app for some time  in my case  it was several hours   i tapped on a competition name  in this case    daly championship division  and saw the teams were not sorted by rank  i can t remember if i had accessed the app after matches had ended the day prior to noticing this bug  after pulling down to refresh  the teams were sorted  my conjecture is that it pulled updated data from the tba api when i opened up the competition  but did not perform a sort operation        screenshots                steps to reproduce        during a competition day  when rankings are changing   use the app to view different active competitions  and probably view rankings at some point      wait a few hours     open up the app back up and access the same competitions accessed in step     this can be after competition is done for the day      tap on the rankings  at this point  they will probably be unsorted  but wins losses ranking appear to be complete and correct      pull down to refresh  teams are now sorted by ranking         your environment       device  iphone x    ios version         tba for ios version                  context        i am just a user wanting to know how a few teams i am interested in are doing and to see how the rankings have panned out at the championship competitions        possible solution        i don t know anything about ios programming  but my gut feeling is that while data is pulled from the tba api when clicking on the ranking tab  or at some point prior   sorting by ranking isn t accomplished by this operation  perhaps there s some race condition  does sorting happen when the ranking tab is tapped  but doesn t have the data from the api yet ,0
63502,12336111622.0,IssuesEvent,2020-05-14 13:06:23,vincentarelbundock/countrycode,https://api.github.com/repos/vincentarelbundock/countrycode,closed,Consider moving regex handling to `stringr` or `stringi`,code improvement,"I'm only half serious, because introducing a new dependency should not be done lightly, but this issue really annoyed me:

https://stackoverflow.com/questions/51470095/r-regular-expression-using-b-with-%C3%85-vs-a-characters",1.0,"Consider moving regex handling to `stringr` or `stringi` - I'm only half serious, because introducing a new dependency should not be done lightly, but this issue really annoyed me:

https://stackoverflow.com/questions/51470095/r-regular-expression-using-b-with-%C3%85-vs-a-characters",0,consider moving regex handling to  stringr  or  stringi    i m only half serious  because introducing a new dependency should not be done lightly  but this issue really annoyed me      ,0
250879,21367609657.0,IssuesEvent,2022-04-20 04:39:45,KSPP/linux,https://api.github.com/repos/KSPP/linux,opened,create self-tests for latent_entropy GCC plugin,good first issue [Feature] self-tests gcc-plugins,"It should be possible to see expected effects with something that builds a simple .c file and emits details:

```
gcc -fplugin=latent_entropy_plugin.so a.c -frandom-seed=stuffhere && ./a.out
```",1.0,"create self-tests for latent_entropy GCC plugin - It should be possible to see expected effects with something that builds a simple .c file and emits details:

```
gcc -fplugin=latent_entropy_plugin.so a.c -frandom-seed=stuffhere && ./a.out
```",0,create self tests for latent entropy gcc plugin   it should be possible to see expected effects with something that builds a simple  c file and emits details          gcc  fplugin latent entropy plugin so a c  frandom seed stuffhere      a out     ,0
196894,15613232927.0,IssuesEvent,2021-03-19 16:12:29,golang/go,https://api.github.com/repos/golang/go,closed,"net/http: mention Context and Client.Do in docs for Get, Head, Post, PostForm",Documentation Proposal Proposal-Accepted,"The documentation for `Client.Do` says ""Generally Get, Post, or PostForm will be used instead of Do."" However, there is no way to pass a `context.Context` into those methods, so we cannot, for example, set a per-request timeout without resorting to `Do`. I propose adding the following new methods to `http.Client`.

- `GetContext(ctx context.Context, url string) (resp *Response, err error)`
- `HeadContext(ctx context.Context, url string) (resp *Response, err error)`
- `PostContext(ctx context.Context, url, contentType string, body io.Reader) (resp *Response, err error)`
- `PostFormContext(ctx context.Context, url string, data url.Values) (resp *Response, err error)`

This would effectively deprecate the existing `Get`, `Head`, `Post`, and `PostForm` methods.

We should also make a corresponding global function for each of these, and deprecate the existing `http.Get`, `http.Head`, `http.Post`, and `http.PostForm` functions.",1.0,"net/http: mention Context and Client.Do in docs for Get, Head, Post, PostForm - The documentation for `Client.Do` says ""Generally Get, Post, or PostForm will be used instead of Do."" However, there is no way to pass a `context.Context` into those methods, so we cannot, for example, set a per-request timeout without resorting to `Do`. I propose adding the following new methods to `http.Client`.

- `GetContext(ctx context.Context, url string) (resp *Response, err error)`
- `HeadContext(ctx context.Context, url string) (resp *Response, err error)`
- `PostContext(ctx context.Context, url, contentType string, body io.Reader) (resp *Response, err error)`
- `PostFormContext(ctx context.Context, url string, data url.Values) (resp *Response, err error)`

This would effectively deprecate the existing `Get`, `Head`, `Post`, and `PostForm` methods.

We should also make a corresponding global function for each of these, and deprecate the existing `http.Get`, `http.Head`, `http.Post`, and `http.PostForm` functions.",1,net http  mention context and client do in docs for get  head  post  postform   the documentation for  client do  says  generally get  post  or postform will be used instead of do   however  there is no way to pass a  context context  into those methods  so we cannot  for example  set a per request timeout without resorting to  do   i propose adding the following new methods to  http client         getcontext ctx context context  url string   resp  response  err error       headcontext ctx context context  url string   resp  response  err error       postcontext ctx context context  url  contenttype string  body io reader   resp  response  err error       postformcontext ctx context context  url string  data url values   resp  response  err error      this would effectively deprecate the existing  get    head    post   and  postform  methods     we should also make a corresponding global function for each of these  and deprecate the existing  http get    http head    http post   and  http postform  functions ,1
40769,6847922552.0,IssuesEvent,2017-11-13 16:48:29,golang/go,https://api.github.com/repos/golang/go,closed,doc: add a link to code of conduct,Documentation,"GitHub has defined a set of standard meta files to include with projects hosted on GitHub. According to the [GitHub Insights Community](https://github.com/golang/go/community) page for this project the only one missing is the code of conduct.

<img src=""https://user-images.githubusercontent.com/351529/32713179-f04dd5de-c7fc-11e7-97ae-ea2f2ffdaed4.png"" width=""75%"" />

Go has a code of conduct on it's website and we should link to it in the prescribed `.github/CODE_OF_CONDUCT.md` so that developers who go looking for it in the standard location on GitHub projects can find it easily.

This would be consistent with the contribution guidelines that are linked to in `.github/CONTRIBUTING.md`.

Ref: https://help.github.com/articles/adding-a-code-of-conduct-to-your-project/",1.0,"doc: add a link to code of conduct - GitHub has defined a set of standard meta files to include with projects hosted on GitHub. According to the [GitHub Insights Community](https://github.com/golang/go/community) page for this project the only one missing is the code of conduct.

<img src=""https://user-images.githubusercontent.com/351529/32713179-f04dd5de-c7fc-11e7-97ae-ea2f2ffdaed4.png"" width=""75%"" />

Go has a code of conduct on it's website and we should link to it in the prescribed `.github/CODE_OF_CONDUCT.md` so that developers who go looking for it in the standard location on GitHub projects can find it easily.

This would be consistent with the contribution guidelines that are linked to in `.github/CONTRIBUTING.md`.

Ref: https://help.github.com/articles/adding-a-code-of-conduct-to-your-project/",1,doc  add a link to code of conduct   github has defined a set of standard meta files to include with projects hosted on github  according to the     page for this project the only one missing is the code of conduct          go has a code of conduct on it s website and we should link to it in the prescribed   github code of conduct md  so that developers who go looking for it in the standard location on github projects can find it easily     this would be consistent with the contribution guidelines that are linked to in   github contributing md      ref   ,1
209436,16193852463.0,IssuesEvent,2021-05-04 12:19:48,golang/go,https://api.github.com/repos/golang/go,closed,"x/image: LineTo has an unexpected behaviour, or is not enough documented",Documentation NeedsInvestigation,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?
<pre>
$ go version
go version go1.15.6 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/olivierwulveryck/Library/Caches/go-build""
GOENV=""/Users/olivierwulveryck/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/olivierwulveryck/GOPROJECTS/pkg/mod""
GONOPROXY=""github.com/dktunited""
GONOSUMDB=""github.com/dktunited""
GOOS=""darwin""
GOPATH=""/Users/olivierwulveryck/GOPROJECTS""
GOPRIVATE=""github.com/dktunited""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/olivierwulveryck/GOPROJECTS/src/github.com/owulveryck/linesToGo/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/j3/t2_lsqzd5mgbv7tqvxg9ty5r0000gn/T/go-build500293275=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?

I am trying to draw a simple line on a picture with the `vector` package. 
I cannot figure out how the package work.

I made a trivial test and I expect it to see in the mask two identical values (representing the horizontal line) and two identical nil values.

```go
func TestMe(t *testing.T) {
	z := vector.NewRasterizer(2, 2)
	z.DrawOp = draw.Src
	// . | .
	// -----
	// . | .

	z.MoveTo(0, 0)
	z.LineTo(1, 0)
	// x | x
	// -----
	// . | .

	dst := image.NewAlpha(z.Bounds())
	z.Draw(dst, dst.Bounds(), image.Opaque, image.Point{})
	expected := []uint8{255, 255, 0, 0}
	if !reflect.DeepEqual(dst.Pix, expected) {
		t.Fatal(dst.Pix)

	}
}
```

https://play.golang.org/p/RnHAWhUwP7K

I tried to debug the code without success. I may have completely misunderstood how to use the package. Therefore an example would help 
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

### What did you expect to see?

Eventually, the representation of a line

### What did you see instead?

A blank mask or a black picture",1.0,"x/image: LineTo has an unexpected behaviour, or is not enough documented - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?
<pre>
$ go version
go version go1.15.6 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/olivierwulveryck/Library/Caches/go-build""
GOENV=""/Users/olivierwulveryck/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/olivierwulveryck/GOPROJECTS/pkg/mod""
GONOPROXY=""github.com/dktunited""
GONOSUMDB=""github.com/dktunited""
GOOS=""darwin""
GOPATH=""/Users/olivierwulveryck/GOPROJECTS""
GOPRIVATE=""github.com/dktunited""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/olivierwulveryck/GOPROJECTS/src/github.com/owulveryck/linesToGo/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/j3/t2_lsqzd5mgbv7tqvxg9ty5r0000gn/T/go-build500293275=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?

I am trying to draw a simple line on a picture with the `vector` package. 
I cannot figure out how the package work.

I made a trivial test and I expect it to see in the mask two identical values (representing the horizontal line) and two identical nil values.

```go
func TestMe(t *testing.T) {
	z := vector.NewRasterizer(2, 2)
	z.DrawOp = draw.Src
	// . | .
	// -----
	// . | .

	z.MoveTo(0, 0)
	z.LineTo(1, 0)
	// x | x
	// -----
	// . | .

	dst := image.NewAlpha(z.Bounds())
	z.Draw(dst, dst.Bounds(), image.Opaque, image.Point{})
	expected := []uint8{255, 255, 0, 0}
	if !reflect.DeepEqual(dst.Pix, expected) {
		t.Fatal(dst.Pix)

	}
}
```

https://play.golang.org/p/RnHAWhUwP7K

I tried to debug the code without success. I may have completely misunderstood how to use the package. Therefore an example would help 
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

### What did you expect to see?

Eventually, the representation of a line

### What did you see instead?

A blank mask or a black picture",1,x image  lineto has an unexpected behaviour  or is not enough documented         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version          go version  go version       darwin             does this issue reproduce with the latest release   yes          what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   users olivierwulveryck library caches go build   goenv   users olivierwulveryck library application support go env   goexe     goflags     gohostarch      gohostos  darwin   goinsecure     gomodcache   users olivierwulveryck goprojects pkg mod   gonoproxy  github com dktunited   gonosumdb  github com dktunited   goos  darwin   gopath   users olivierwulveryck goprojects   goprivate  github com dktunited   goproxy     goroot   usr local go   gosumdb  sum golang org   gotmpdir     gotooldir   usr local go pkg tool darwin     gccgo  gccgo   ar  ar   cc  clang   cxx  clang     cgo enabled      gomod   users olivierwulveryck goprojects src github com owulveryck linestogo go mod   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders       t go    tmp go build  gno record gcc switches  fno common             what did you do     i am trying to draw a simple line on a picture with the  vector  package    i cannot figure out how the package work     i made a trivial test and i expect it to see in the mask two identical values  representing the horizontal line  and two identical nil values        go  func testme t  testing t     	z    vector newrasterizer        	z drawop   draw src  	          	          	            	z moveto        	z lineto        	   x   x  	          	            	dst    image newalpha z bounds     	z draw dst  dst bounds    image opaque  image point     	expected                    	if  reflect deepequal dst pix  expected     		t fatal dst pix     	                  i tried to debug the code without success  i may have completely misunderstood how to use the package  therefore an example would help         if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best              what did you expect to see     eventually  the representation of a line        what did you see instead     a blank mask or a black picture,1
56718,6998039958.0,IssuesEvent,2017-12-16 22:13:11,agune15/EisherzProject,https://api.github.com/repos/agune15/EisherzProject,closed,Map & Level Design Exterior,2D Art Game Design,"The level design and a map of the exterior.

**EXPECTED RESULT:** 

_Four maps with a good and an strategic level design_",1.0,"Map & Level Design Exterior - The level design and a map of the exterior.

**EXPECTED RESULT:** 

_Four maps with a good and an strategic level design_",0,map   level design exterior   the level design and a map of the exterior       expected result         four maps with a good and an strategic level design ,0
319673,23785006807.0,IssuesEvent,2022-09-02 09:15:52,golang/go,https://api.github.com/repos/golang/go,closed,encoding/asn1: BitString.At wrong doc return type ,Documentation help wanted NeedsFix,"https://github.com/golang/go/blob/2882786bf4cd779f166e9ced82a4da2ea0f8b1f9/src/encoding/asn1/asn1.go#L164-L173

The doc comment says it returns false when it returns zero.

(I'd submit a PR but the contributor process is too onerous for a one-liner like this.)",1.0,"encoding/asn1: BitString.At wrong doc return type  - https://github.com/golang/go/blob/2882786bf4cd779f166e9ced82a4da2ea0f8b1f9/src/encoding/asn1/asn1.go#L164-L173

The doc comment says it returns false when it returns zero.

(I'd submit a PR but the contributor process is too onerous for a one-liner like this.)",1,encoding    bitstring at wrong doc return type         the doc comment says it returns false when it returns zero      i d submit a pr but the contributor process is too onerous for a one liner like this  ,1
154709,19752246242.0,IssuesEvent,2022-01-15 06:54:28,smb-h/nn-lab,https://api.github.com/repos/smb-h/nn-lab,opened,CVE-2021-43854 (High) detected in nltk-3.3.0.zip,security vulnerability,"## CVE-2021-43854 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>nltk-3.3.0.zip</b></p></summary>

<p>Natural Language Toolkit</p>
<p>Library home page: <a href=""https://files.pythonhosted.org/packages/50/09/3b1755d528ad9156ee7243d52aa5cd2b809ef053a0f31b53d92853dd653a/nltk-3.3.0.zip"">https://files.pythonhosted.org/packages/50/09/3b1755d528ad9156ee7243d52aa5cd2b809ef053a0f31b53d92853dd653a/nltk-3.3.0.zip</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>

Dependency Hierarchy:
  - hazm-0.7.0-py3-none-any.whl (Root Library)
    - :x: **nltk-3.3.0.zip** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/smb-h/nn-lab/commit/11224a09bd2416657d465ed77014523b84b35867"">11224a09bd2416657d465ed77014523b84b35867</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>  
  
NLTK (Natural Language Toolkit) is a suite of open source Python modules, data sets, and tutorials supporting research and development in Natural Language Processing. Versions prior to 3.6.5 are vulnerable to regular expression denial of service (ReDoS) attacks. The vulnerability is present in PunktSentenceTokenizer, sent_tokenize and word_tokenize. Any users of this class, or these two functions, are vulnerable to the ReDoS attack. In short, a specifically crafted long input to any of these vulnerable functions will cause them to take a significant amount of execution time. If your program relies on any of the vulnerable functions for tokenizing unpredictable user input, then we would strongly recommend upgrading to a version of NLTK without the vulnerability. For users unable to upgrade the execution time can be bounded by limiting the maximum length of an input to any of the vulnerable functions. Our recommendation is to implement such a limit.

<p>Publish Date: 2021-12-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-43854>CVE-2021-43854</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-43854"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-43854</a></p>
<p>Release Date: 2021-12-23</p>
<p>Fix Resolution: nltk - 3.6.6</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-43854 (High) detected in nltk-3.3.0.zip - ## CVE-2021-43854 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>nltk-3.3.0.zip</b></p></summary>

<p>Natural Language Toolkit</p>
<p>Library home page: <a href=""https://files.pythonhosted.org/packages/50/09/3b1755d528ad9156ee7243d52aa5cd2b809ef053a0f31b53d92853dd653a/nltk-3.3.0.zip"">https://files.pythonhosted.org/packages/50/09/3b1755d528ad9156ee7243d52aa5cd2b809ef053a0f31b53d92853dd653a/nltk-3.3.0.zip</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>

Dependency Hierarchy:
  - hazm-0.7.0-py3-none-any.whl (Root Library)
    - :x: **nltk-3.3.0.zip** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/smb-h/nn-lab/commit/11224a09bd2416657d465ed77014523b84b35867"">11224a09bd2416657d465ed77014523b84b35867</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>  
  
NLTK (Natural Language Toolkit) is a suite of open source Python modules, data sets, and tutorials supporting research and development in Natural Language Processing. Versions prior to 3.6.5 are vulnerable to regular expression denial of service (ReDoS) attacks. The vulnerability is present in PunktSentenceTokenizer, sent_tokenize and word_tokenize. Any users of this class, or these two functions, are vulnerable to the ReDoS attack. In short, a specifically crafted long input to any of these vulnerable functions will cause them to take a significant amount of execution time. If your program relies on any of the vulnerable functions for tokenizing unpredictable user input, then we would strongly recommend upgrading to a version of NLTK without the vulnerability. For users unable to upgrade the execution time can be bounded by limiting the maximum length of an input to any of the vulnerable functions. Our recommendation is to implement such a limit.

<p>Publish Date: 2021-12-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-43854>CVE-2021-43854</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-43854"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-43854</a></p>
<p>Release Date: 2021-12-23</p>
<p>Fix Resolution: nltk - 3.6.6</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in nltk       zip      cve       high severity vulnerability     vulnerable library    nltk       zip      natural language toolkit   library home page   a href     path to dependency file   requirements txt   path to vulnerable library   requirements txt     dependency hierarchy      hazm         none any whl  root library         x    nltk       zip    vulnerable library   found in head commit   a href     found in base branch   main              vulnerability details         nltk  natural language toolkit  is a suite of open source python modules  data sets  and tutorials supporting research and development in natural language processing  versions prior to       are vulnerable to regular expression denial of service  redos  attacks  the vulnerability is present in punktsentencetokenizer  sent tokenize and word tokenize  any users of this class  or these two functions  are vulnerable to the redos attack  in short  a specifically crafted long input to any of these vulnerable functions will cause them to take a significant amount of execution time  if your program relies on any of the vulnerable functions for tokenizing unpredictable user input  then we would strongly recommend upgrading to a version of nltk without the vulnerability  for users unable to upgrade the execution time can be bounded by limiting the maximum length of an input to any of the vulnerable functions  our recommendation is to implement such a limit    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  nltk                       step up your open source security game with whitesource    ,0
316288,9640119808.0,IssuesEvent,2019-05-16 14:52:50,STAMP-project/dspot,https://api.github.com/repos/STAMP-project/dspot,closed,DSpot 2.1.0 release,chore high priority,"Announcing the new release of DSpot.

A lot of change occurs recently, and it is time to release time.

Waiting for #726, ~~#736~~, ~~#750~~, ~~#751~~, #753, ~~#755~~ and #757 to be merged/closed/resolved.

The current change log is:

# New features

* Split now the value of parameter amplifiers and init well the list.
* Recover from errors when first exec of tests.
* Forbid the class java.net.URL in the observations.
* Can now specify a list of package to forbid in the observations.
* Allow snapshot versions for PIT and Descartes.
* Generate after class.
* Pitest minimizer.
* Dspot prettifier process.
* Code2vec parser.
* Using maven to execute tests.
* Prettifier code2vec executor.


# Bug Fixes

* Get filter automatic builder helper Fix #744.
* Can generate a value for type stack over flow.
* Is test junit3.
* Assertion remover on returned values.
* The output path is now well configured.
* Fix gradle properties and skip compile test.
* Rm try with resource.
* Typo in the constant of isEqualsTo and isNotEqualsTo.
* Use now the complete classpath to compile the newly amplified test class.
* Fix is collection and is map in observations.
* Fix code2vec parser.
* GoogleTruth is now a Decorator and uses another implementation.
* Compilation errors due to amplification during the process.
* Use the property outputDirectory.
* Negate the conditional to take all but total instead of only total.
* Cloner avoid npe in init.
* Remove generic actual type arguments.
* Fix remove assertion npe.


# Documentation

* Improve diff test selection documentation FIX #768.
* Rename filter property Fix #747.
* Add example to improve coverage with Maven plugin.
* Split the README to push forward the usage.
* Patching issue#605. Fixing DSpot Maven usage example.


# Refactoring

* Report architecture fix #745.
* Remove all the old files that was not used anymore.
* Remove all files related to an experimentation.


# Performance

* Memory optimization.
* Optimization4.
* Optimization#3.
* In DSpotUtils.printAndCompileToCheck(): extract invocation type.getMethods() out of stream filter loop, since it is an invariant.

# Unknown

* Bump jacoco and spoon.
* Prettifier set exe jar.

# Authors
| Name    | Nb Commit |
|---------|-----------|
| Benjamin DANGLOT | 37 |
| Jesús Gorroñogoitia Cruz | 4 |
| Oscar Luis Vera Pérez | 1 |
| Martin Monperrus | 1 |
",1.0,"DSpot 2.1.0 release - Announcing the new release of DSpot.

A lot of change occurs recently, and it is time to release time.

Waiting for #726, ~~#736~~, ~~#750~~, ~~#751~~, #753, ~~#755~~ and #757 to be merged/closed/resolved.

The current change log is:

# New features

* Split now the value of parameter amplifiers and init well the list.
* Recover from errors when first exec of tests.
* Forbid the class java.net.URL in the observations.
* Can now specify a list of package to forbid in the observations.
* Allow snapshot versions for PIT and Descartes.
* Generate after class.
* Pitest minimizer.
* Dspot prettifier process.
* Code2vec parser.
* Using maven to execute tests.
* Prettifier code2vec executor.


# Bug Fixes

* Get filter automatic builder helper Fix #744.
* Can generate a value for type stack over flow.
* Is test junit3.
* Assertion remover on returned values.
* The output path is now well configured.
* Fix gradle properties and skip compile test.
* Rm try with resource.
* Typo in the constant of isEqualsTo and isNotEqualsTo.
* Use now the complete classpath to compile the newly amplified test class.
* Fix is collection and is map in observations.
* Fix code2vec parser.
* GoogleTruth is now a Decorator and uses another implementation.
* Compilation errors due to amplification during the process.
* Use the property outputDirectory.
* Negate the conditional to take all but total instead of only total.
* Cloner avoid npe in init.
* Remove generic actual type arguments.
* Fix remove assertion npe.


# Documentation

* Improve diff test selection documentation FIX #768.
* Rename filter property Fix #747.
* Add example to improve coverage with Maven plugin.
* Split the README to push forward the usage.
* Patching issue#605. Fixing DSpot Maven usage example.


# Refactoring

* Report architecture fix #745.
* Remove all the old files that was not used anymore.
* Remove all files related to an experimentation.


# Performance

* Memory optimization.
* Optimization4.
* Optimization#3.
* In DSpotUtils.printAndCompileToCheck(): extract invocation type.getMethods() out of stream filter loop, since it is an invariant.

# Unknown

* Bump jacoco and spoon.
* Prettifier set exe jar.

# Authors
| Name    | Nb Commit |
|---------|-----------|
| Benjamin DANGLOT | 37 |
| Jesús Gorroñogoitia Cruz | 4 |
| Oscar Luis Vera Pérez | 1 |
| Martin Monperrus | 1 |
",0,dspot       release   announcing the new release of dspot     a lot of change occurs recently  and it is time to release time     waiting for                                        and    to be merged closed resolved     the current change log is       new features      split now the value of parameter amplifiers and init well the list     recover from errors when first exec of tests     forbid the class java net url in the observations     can now specify a list of package to forbid in the observations     allow snapshot versions for pit and descartes     generate after class     pitest minimizer     dspot prettifier process       parser     using maven to execute tests     prettifier   executor         bug fixes      get filter automatic builder helper fix        can generate a value for type stack over flow     is test       assertion remover on returned values     the output path is now well configured     fix gradle properties and skip compile test     rm try with resource     typo in the constant of isequalsto and isnotequalsto     use now the complete classpath to compile the newly amplified test class     fix is collection and is map in observations     fix   parser     googletruth is now a decorator and uses another implementation     compilation errors due to amplification during the process     use the property outputdirectory     negate the conditional to take all but total instead of only total     cloner avoid npe in init     remove generic actual type arguments     fix remove assertion npe         documentation      improve diff test selection documentation fix        rename filter property fix        add example to improve coverage with maven plugin     split the readme to push forward the usage     patching issue    fixing dspot maven usage example         refactoring      report architecture fix        remove all the old files that was not used anymore     remove all files related to an experimentation         performance      memory optimization           optimization       in dspotutils printandcompiletocheck    extract invocation type getmethods   out of stream filter loop  since it is an invariant       unknown      bump jacoco and spoon     prettifier set exe jar       authors    name      nb commit                               benjamin danglot          jesús gorroñogoitia cruz          oscar luis vera pérez          martin monperrus        ,0
189841,15208220023.0,IssuesEvent,2021-02-17 02:05:03,golang/go,https://api.github.com/repos/golang/go,closed,embed: warn about dotfiles in embed.FS documentation,Documentation NeedsFix,"### What version of Go are you using (`go version`)?

Tip.

<pre>
$ gotip version
go version devel +48be3ed Sat Oct 31 00:35:33 2020 +0000 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What did you do?

Tried out the new embed.FS feature.

example.go:

```
package main

import (
	""embed""
	""fmt""
	""io/fs""
)

func main() {
	//go:embed example/*
	var files embed.FS
	des, _ := fs.ReadDir(files, ""example"")
	for _, de := range des {
		fmt.Printf(""%q\n"", de.Name())
	}
}
```

example:

```
total 1504
drwxr-xr-x@ 6 adhoc  staff   192 Oct 30 21:49 .
drwx------  8 adhoc  staff   256 Nov  1 13:34 ..
-rw-r--r--@ 1 adhoc  staff  6148 Oct 30 21:49 .DS_Store
-rw-r--r--  1 adhoc  staff     0 Oct 30 21:47 .dot
-rw-r--r--@ 1 adhoc  staff     0 Oct 30 21:48 Icon
-rw-r--r--  1 adhoc  staff     0 Oct 30 21:47 one.txt
```

### What did you expect to see?

```
$ gotip run .
""one.txt""
```

### What did you see instead?

```
$ gotip run .
"".DS_Store""
"".dot""
""Icon\r""
""one.txt""
```

- - - -

There should be a warning in the documentation that dotfiles and hidden files are included.",1.0,"embed: warn about dotfiles in embed.FS documentation - ### What version of Go are you using (`go version`)?

Tip.

<pre>
$ gotip version
go version devel +48be3ed Sat Oct 31 00:35:33 2020 +0000 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What did you do?

Tried out the new embed.FS feature.

example.go:

```
package main

import (
	""embed""
	""fmt""
	""io/fs""
)

func main() {
	//go:embed example/*
	var files embed.FS
	des, _ := fs.ReadDir(files, ""example"")
	for _, de := range des {
		fmt.Printf(""%q\n"", de.Name())
	}
}
```

example:

```
total 1504
drwxr-xr-x@ 6 adhoc  staff   192 Oct 30 21:49 .
drwx------  8 adhoc  staff   256 Nov  1 13:34 ..
-rw-r--r--@ 1 adhoc  staff  6148 Oct 30 21:49 .DS_Store
-rw-r--r--  1 adhoc  staff     0 Oct 30 21:47 .dot
-rw-r--r--@ 1 adhoc  staff     0 Oct 30 21:48 Icon
-rw-r--r--  1 adhoc  staff     0 Oct 30 21:47 one.txt
```

### What did you expect to see?

```
$ gotip run .
""one.txt""
```

### What did you see instead?

```
$ gotip run .
"".DS_Store""
"".dot""
""Icon\r""
""one.txt""
```

- - - -

There should be a warning in the documentation that dotfiles and hidden files are included.",1,embed  warn about dotfiles in embed fs documentation       what version of go are you using   go version       tip          gotip version  go version devel    sat oct              darwin             does this issue reproduce with the latest release     yes         what did you do     tried out the new embed fs feature     example go          package main    import    	 embed   	 fmt   	 io fs        func main      	  go embed example    	var files embed fs  	des       fs readdir files   example    	for    de    range des    		fmt printf   q n   de name     	             example          total    drwxr xr x    adhoc  staff     oct          drwx          adhoc  staff     nov             rw r  r      adhoc  staff    oct        ds store   rw r  r      adhoc  staff       oct        dot   rw r  r      adhoc  staff       oct       icon   rw r  r      adhoc  staff       oct       one txt             what did you expect to see            gotip run     one txt              what did you see instead            gotip run      ds store     dot    icon r    one txt                     there should be a warning in the documentation that dotfiles and hidden files are included ,1
153069,5874216033.0,IssuesEvent,2017-05-15 15:35:25,uclibs/scholar_uc,https://api.github.com/repos/uclibs/scholar_uc,closed,Modify Batch Create Form for base metadata fields,bug Priority A Scholar 3.0,"### Descriptive summary
The current batch create form is out of sync with the metadata profile of Scholar 3.

There will be some complex logic needed or simplified set of requirements to make sure the form renders useful for all work types.
",1.0,"Modify Batch Create Form for base metadata fields - ### Descriptive summary
The current batch create form is out of sync with the metadata profile of Scholar 3.

There will be some complex logic needed or simplified set of requirements to make sure the form renders useful for all work types.
",0,modify batch create form for base metadata fields       descriptive summary  the current batch create form is out of sync with the metadata profile of scholar       there will be some complex logic needed or simplified set of requirements to make sure the form renders useful for all work types   ,0
90246,11360138919.0,IssuesEvent,2020-01-26 03:36:39,davidrodjen/ByteClub--Ticket-System,https://api.github.com/repos/davidrodjen/ByteClub--Ticket-System,opened,Create Options form/dialog box,UI design,"## Form should contain
- Minutes per window
- Guests per window
- Start time
- End time
- First ticket number
- OK button",1.0,"Create Options form/dialog box - ## Form should contain
- Minutes per window
- Guests per window
- Start time
- End time
- First ticket number
- OK button",0,create options form dialog box      form should contain    minutes per window    guests per window    start time    end time    first ticket number    ok button,0
85668,10667305937.0,IssuesEvent,2019-10-19 11:22:58,elementary/tasks,https://api.github.com/repos/elementary/tasks,opened,Set tasks status to complete or incomplete by changing its checkbox state,Needs Design,What the title says.,1.0,Set tasks status to complete or incomplete by changing its checkbox state - What the title says.,0,set tasks status to complete or incomplete by changing its checkbox state   what the title says ,0
79693,28496460977.0,IssuesEvent,2023-04-18 14:33:50,vector-im/element-desktop,https://api.github.com/repos/vector-im/element-desktop,opened,Start on Boot for more then one profile,T-Defect,"#### Description

Because of vector-im/element-web#2320 I need a secondary profile.

But i didn't both profiles to start on boot.
I only get one of them to boot from startup. That one where i deactivate and activate the startup.
When you deactivate the startup on one of them, it's activated in both and vice versa.

Describe how what happens differs from what you expected.

I expected that both profiles start on boot or that i can change it for each of them separate in the options.
#### Version information
- **Platform**: Desktop 
- **OS**: Ubuntu Mate 20.04
- **Version**: 1.7.3 3
",1.0,"Start on Boot for more then one profile - #### Description

Because of vector-im/element-web#2320 I need a secondary profile.

But i didn't both profiles to start on boot.
I only get one of them to boot from startup. That one where i deactivate and activate the startup.
When you deactivate the startup on one of them, it's activated in both and vice versa.

Describe how what happens differs from what you expected.

I expected that both profiles start on boot or that i can change it for each of them separate in the options.
#### Version information
- **Platform**: Desktop 
- **OS**: Ubuntu Mate 20.04
- **Version**: 1.7.3 3
",0,start on boot for more then one profile        description    because of vector im element web   i need a secondary profile     but i didn t both profiles to start on boot   i only get one of them to boot from startup  that one where i deactivate and activate the startup   when you deactivate the startup on one of them  it s activated in both and vice versa     describe how what happens differs from what you expected     i expected that both profiles start on boot or that i can change it for each of them separate in the options        version information      platform    desktop       os    ubuntu mate          version             ,0
88857,8179550129.0,IssuesEvent,2018-08-28 16:41:26,ntop/ntopng,https://api.github.com/repos/ntop/ntopng,closed,NTOPNG - starts dropping after 10mins,testing needed,"Hi

We are running the latest version 3.6.1 and we have the same issue we have in 3.4.

After 10 minutes ntop starts dropping packets.

We are doing approximately 300 flows/s and 60k pps and 400 Mbits/s.

I downgraded to 2.4 and that worked fine, although was missing some of the features we needed.
We also tried  having ntopng as an nprobe collector, rather that getting the flows in itself and this also worked and did not drop packets.
We run on Centos 7.

I have tried several configurations as suggested by previous issues, but nothing seemed to work, such as disabling alerting, increasing and decreasing the Hosts and Flows (x and X) numbers, packet filters etc.
We have one GB interface being used, no PF_Ring.

I am interested to know what may be causing this, as although using nprobe to ntopng works, we lose some of the features like RTT, some of the TCP information on the flows and the new PCAP download feature.

Any suggestions would be much appreciated. We are running the Professional version.",1.0,"NTOPNG - starts dropping after 10mins - Hi

We are running the latest version 3.6.1 and we have the same issue we have in 3.4.

After 10 minutes ntop starts dropping packets.

We are doing approximately 300 flows/s and 60k pps and 400 Mbits/s.

I downgraded to 2.4 and that worked fine, although was missing some of the features we needed.
We also tried  having ntopng as an nprobe collector, rather that getting the flows in itself and this also worked and did not drop packets.
We run on Centos 7.

I have tried several configurations as suggested by previous issues, but nothing seemed to work, such as disabling alerting, increasing and decreasing the Hosts and Flows (x and X) numbers, packet filters etc.
We have one GB interface being used, no PF_Ring.

I am interested to know what may be causing this, as although using nprobe to ntopng works, we lose some of the features like RTT, some of the TCP information on the flows and the new PCAP download feature.

Any suggestions would be much appreciated. We are running the Professional version.",0,ntopng   starts dropping after     hi    we are running the latest version       and we have the same issue we have in         after   minutes ntop starts dropping packets     we are doing approximately   flows s and   pps and   mbits s     i downgraded to     and that worked fine  although was missing some of the features we needed   we also tried  having ntopng as an nprobe collector  rather that getting the flows in itself and this also worked and did not drop packets   we run on centos       i have tried several configurations as suggested by previous issues  but nothing seemed to work  such as disabling alerting  increasing and decreasing the hosts and flows  x and x  numbers  packet filters etc   we have one gb interface being used  no pf ring     i am interested to know what may be causing this  as although using nprobe to ntopng works  we lose some of the features like rtt  some of the tcp information on the flows and the new pcap download feature     any suggestions would be much appreciated  we are running the professional version ,0
16517,4056662158.0,IssuesEvent,2016-05-24 19:23:40,golang/go,https://api.github.com/repos/golang/go,closed,doc: give more tips on proper commit message style,Documentation NeedsFix,In https://go-review.googlesource.com/#/c/21815/1//COMMIT_MSG @bradfitz offers a good tip on how to phrase commit titles. Writing titles and messages is touched on briefly in the [contribution guidelines](https://golang.org/doc/contribute.html#change) but would be nice to mention this and other tips and/or style guidelines.,1.0,doc: give more tips on proper commit message style - In https://go-review.googlesource.com/#/c/21815/1//COMMIT_MSG @bradfitz offers a good tip on how to phrase commit titles. Writing titles and messages is touched on briefly in the [contribution guidelines](https://golang.org/doc/contribute.html#change) but would be nice to mention this and other tips and/or style guidelines.,1,doc  give more tips on proper commit message style   in    bradfitz offers a good tip on how to phrase commit titles  writing titles and messages is touched on briefly in the     but would be nice to mention this and other tips and or style guidelines ,1
416732,28097698583.0,IssuesEvent,2023-03-30 16:58:38,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/go/analysis: pkgsite documentation for golang.org/x/tools/go/analysis/passes/* often lacks details,Documentation Tools pkgsite,"I am not sure if this is a feature request for pkgsite, or it's just because the go analysis analyzer code was structured in a way not friendly with go documentation. Analyzers often place the helpful details in Doc constant, but this long doc is hidden from documentation

https://pkg.go.dev/golang.org/x/tools/go/analysis/passes/nilness

![Screenshot 2023-03-09 at 9 10 51 AM](https://user-images.githubusercontent.com/4999471/224050682-c293e809-ffd5-4726-95c7-98f68e79b49d.png)

```
$ go doc
package nilness // import ""golang.org/x/tools/go/analysis/passes/nilness""

Package nilness inspects the control-flow graph of an SSA function and reports
errors such as nil pointer dereferences and degenerate nil pointer comparisons.

const Doc = ...
var Analyzer = &analysis.Analyzer{ ... }

$ go doc Doc
```

Would be nice if the documentation page of analyzers presents sufficient details. 
The pattern I saw in similar situation was to generate the package doc (doc.go) from the types but not sure if that's the best way.

cc @adonovan @golang/tools-team ",1.0,"x/tools/go/analysis: pkgsite documentation for golang.org/x/tools/go/analysis/passes/* often lacks details - I am not sure if this is a feature request for pkgsite, or it's just because the go analysis analyzer code was structured in a way not friendly with go documentation. Analyzers often place the helpful details in Doc constant, but this long doc is hidden from documentation

https://pkg.go.dev/golang.org/x/tools/go/analysis/passes/nilness

![Screenshot 2023-03-09 at 9 10 51 AM](https://user-images.githubusercontent.com/4999471/224050682-c293e809-ffd5-4726-95c7-98f68e79b49d.png)

```
$ go doc
package nilness // import ""golang.org/x/tools/go/analysis/passes/nilness""

Package nilness inspects the control-flow graph of an SSA function and reports
errors such as nil pointer dereferences and degenerate nil pointer comparisons.

const Doc = ...
var Analyzer = &analysis.Analyzer{ ... }

$ go doc Doc
```

Would be nice if the documentation page of analyzers presents sufficient details. 
The pattern I saw in similar situation was to generate the package doc (doc.go) from the types but not sure if that's the best way.

cc @adonovan @golang/tools-team ",1,x tools go analysis  pkgsite documentation for golang org x tools go analysis passes   often lacks details   i am not sure if this is a feature request for pkgsite  or it s just because the go analysis analyzer code was structured in a way not friendly with go documentation  analyzers often place the helpful details in doc constant  but this long doc is hidden from documentation                        go doc  package nilness    import  golang org x tools go analysis passes nilness     package nilness inspects the control flow graph of an ssa function and reports  errors such as nil pointer dereferences and degenerate nil pointer comparisons     const doc        var analyzer    analysis analyzer             go doc doc         would be nice if the documentation page of analyzers presents sufficient details    the pattern i saw in similar situation was to generate the package doc  doc go  from the types but not sure if that s the best way     cc  adonovan  golang tools team ,1
54357,7884721313.0,IssuesEvent,2018-06-27 10:00:35,golang/go,https://api.github.com/repos/golang/go,closed,No pkg installed,Documentation NeedsFix,"Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
go version go1.10.3 windows/amd64

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\p4446\AppData\Local\go-build
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\Users\XXXXX\Documents\go-work
set GORACE=
set GOROOT=C:\Go
set GOTMPDIR=
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\XXXXX\AppData\Local\Temp\go-build121904390=/tmp/go-build -gno-record-gcc-switches

### What did you do?
I followed the tutorial on https://golang.org/doc/code.html till the section **Your First Library**. 


### What did you expect to see?
When I run command **go install github.com/user/hello**, it's expected to install **hello.exe** in folder **bin** and pakage **stringutil.a** in folder **pkg**.

### What did you see instead?
I got only hello.exe in bin, but nothing in pkg. 
",1.0,"No pkg installed - Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
go version go1.10.3 windows/amd64

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\p4446\AppData\Local\go-build
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\Users\XXXXX\Documents\go-work
set GORACE=
set GOROOT=C:\Go
set GOTMPDIR=
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\XXXXX\AppData\Local\Temp\go-build121904390=/tmp/go-build -gno-record-gcc-switches

### What did you do?
I followed the tutorial on https://golang.org/doc/code.html till the section **Your First Library**. 


### What did you expect to see?
When I run command **go install github.com/user/hello**, it's expected to install **hello.exe** in folder **bin** and pakage **stringutil.a** in folder **pkg**.

### What did you see instead?
I got only hello.exe in bin, but nothing in pkg. 
",1,no pkg installed   please answer these questions before submitting your issue  thanks           what version of go are you using   go version     go version       windows          does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env     set goarch    set gobin   set gocache c  users   appdata local go build  set goexe  exe  set gohostarch    set gohostos windows  set goos windows  set gopath c  users xxxxx documents go work  set gorace   set goroot c  go  set gotmpdir   set gotooldir c  go pkg tool windows    set gccgo gccgo  set cc gcc  set cxx g    set cgo enabled    set cgo cflags  g     set cgo cppflags   set cgo cxxflags  g     set cgo fflags  g     set cgo ldflags  g     set pkg config pkg config  set gogccflags     mthreads  fmessage length    fdebug prefix map c  users xxxxx appdata local temp go    tmp go build  gno record gcc switches        what did you do   i followed the tutorial on   till the section   your first library              what did you expect to see   when i run command   go install github com user hello    it s expected to install   hello exe   in folder   bin   and pakage   stringutil a   in folder   pkg           what did you see instead   i got only hello exe in bin  but nothing in pkg    ,1
26146,5226057057.0,IssuesEvent,2017-01-27 20:08:35,golang/go,https://api.github.com/repos/golang/go,closed,doc: broken wiki Images in golang/go/wiki/Mobile,Documentation NeedsFix,"I'm reading the Go Mobile docs, and some images is not found


* Deploying app bundle
https://camo.githubusercontent.com/fbc28cc15ba04a995fe26925658557d8be5565fe/68747470733a2f2f676f6f676c6564726976652e636f6d2f686f73742f30427966536a64505673394d5a626b686a6555684d597a52546545452f676f77696b692f676f6d6f62696c652d696f732d6465706c6f792e706e67

* Xcode project layout with hello.framework
https://camo.githubusercontent.com/ca8480d267fa6fba06cd69ddbd7a157083a7dab9/68747470733a2f2f676f6f676c6564726976652e636f6d2f686f73742f30427966536a64505673394d5a626b686a6555684d597a52546545452f676f77696b692f676f6d6f62696c652d696d706f72742d616e64726f696473747564696f2e706e67

* Drag and drop Hello.framework
https://camo.githubusercontent.com/4056086ee93aa86233588f92a7e180374d11807d/68747470733a2f2f676f6f676c6564726976652e636f6d2f686f73742f30427966536a64505673394d5a626b686a6555684d597a52546545452f676f77696b692f676f6d6f62696c652d62696e642d696f73647261672e706e67

* Xcode project layout with Hello.framework
https://camo.githubusercontent.com/158aaea172021b5c38d1cf2fcccfa39336384a77/68747470733a2f2f676f6f676c6564726976652e636f6d2f686f73742f30427966536a64505673394d5a626b686a6555684d597a52546545452f676f77696b692f676f6d6f62696c652d62696e642d696f732e706e67

Should this be reported here? If I know which image should be there I can send a fix, but as I am a begginer looking for how to start to work with go, I'm not familiar with this documentation yet.
",1.0,"doc: broken wiki Images in golang/go/wiki/Mobile - I'm reading the Go Mobile docs, and some images is not found


* Deploying app bundle
https://camo.githubusercontent.com/fbc28cc15ba04a995fe26925658557d8be5565fe/68747470733a2f2f676f6f676c6564726976652e636f6d2f686f73742f30427966536a64505673394d5a626b686a6555684d597a52546545452f676f77696b692f676f6d6f62696c652d696f732d6465706c6f792e706e67

* Xcode project layout with hello.framework
https://camo.githubusercontent.com/ca8480d267fa6fba06cd69ddbd7a157083a7dab9/68747470733a2f2f676f6f676c6564726976652e636f6d2f686f73742f30427966536a64505673394d5a626b686a6555684d597a52546545452f676f77696b692f676f6d6f62696c652d696d706f72742d616e64726f696473747564696f2e706e67

* Drag and drop Hello.framework
https://camo.githubusercontent.com/4056086ee93aa86233588f92a7e180374d11807d/68747470733a2f2f676f6f676c6564726976652e636f6d2f686f73742f30427966536a64505673394d5a626b686a6555684d597a52546545452f676f77696b692f676f6d6f62696c652d62696e642d696f73647261672e706e67

* Xcode project layout with Hello.framework
https://camo.githubusercontent.com/158aaea172021b5c38d1cf2fcccfa39336384a77/68747470733a2f2f676f6f676c6564726976652e636f6d2f686f73742f30427966536a64505673394d5a626b686a6555684d597a52546545452f676f77696b692f676f6d6f62696c652d62696e642d696f732e706e67

Should this be reported here? If I know which image should be there I can send a fix, but as I am a begginer looking for how to start to work with go, I'm not familiar with this documentation yet.
",1,doc  broken wiki images in golang go wiki mobile   i m reading the go mobile docs  and some images is not found        deploying app bundle         xcode project layout with hello framework         drag and drop hello framework         xcode project layout with hello framework       should this be reported here  if i know which image should be there i can send a fix  but as i am a begginer looking for how to start to work with go  i m not familiar with this documentation yet   ,1
33320,14060025648.0,IssuesEvent,2020-11-03 04:53:12,MicrosoftDocs/azure-docs,https://api.github.com/repos/MicrosoftDocs/azure-docs,closed,Incorrect AZURE_RESOURCE_GROUP when using a custom ARO domain,Pri2 container-service/svc cxp doc-bug triaged,"This step is incorrect when using a customer ARO domain:

```sh
export AZURE_RESOURCE_GROUP=aro-$(az aro show --name <name of cluster> --resource-group <name of resource group> | jq -r '.clusterProfile.domain')
```

it should be:

```sh
export AZURE_RESOURCE_GROUP=$((az aro show --name <name of cluster> --resource-group <name of resource group> | jq -r .clusterProfile.resourceGroupId | cut -d '/' -f 5,5)
```



---
#### Document Details

⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*

* ID: 2c0baeb2-508c-942c-f010-f3227f0eec36
* Version Independent ID: 74896c7a-5dd0-a588-0b5d-99d038e3f6ed
* Content: [Create an Azure Red Hat OpenShift 4 cluster application backup using Velero](https://docs.microsoft.com/en-us/azure/openshift/howto-create-a-backup)
* Content Source: [articles/openshift/howto-create-a-backup.md](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/openshift/howto-create-a-backup.md)
* Service: **container-service**
* GitHub Login: @troy0820
* Microsoft Alias: **b-trconn**",1.0,"Incorrect AZURE_RESOURCE_GROUP when using a custom ARO domain - This step is incorrect when using a customer ARO domain:

```sh
export AZURE_RESOURCE_GROUP=aro-$(az aro show --name <name of cluster> --resource-group <name of resource group> | jq -r '.clusterProfile.domain')
```

it should be:

```sh
export AZURE_RESOURCE_GROUP=$((az aro show --name <name of cluster> --resource-group <name of resource group> | jq -r .clusterProfile.resourceGroupId | cut -d '/' -f 5,5)
```



---
#### Document Details

⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*

* ID: 2c0baeb2-508c-942c-f010-f3227f0eec36
* Version Independent ID: 74896c7a-5dd0-a588-0b5d-99d038e3f6ed
* Content: [Create an Azure Red Hat OpenShift 4 cluster application backup using Velero](https://docs.microsoft.com/en-us/azure/openshift/howto-create-a-backup)
* Content Source: [articles/openshift/howto-create-a-backup.md](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/openshift/howto-create-a-backup.md)
* Service: **container-service**
* GitHub Login: @troy0820
* Microsoft Alias: **b-trconn**",0,incorrect azure resource group when using a custom aro domain   this step is incorrect when using a customer aro domain        sh  export azure resource group aro   az aro show   name     resource group     jq  r   clusterprofile domain           it should be        sh  export azure resource group    az aro show   name     resource group     jq  r  clusterprofile resourcegroupid   cut  d      f                            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    container service      github login        microsoft alias    b trconn  ,0
825566,31394577423.0,IssuesEvent,2023-08-26 19:16:50,Jaspero/web-components,https://api.github.com/repos/Jaspero/web-components,opened,Add component dependencies to specific components in docs,Complexity: 1 Priority: Low,Curranty they are listed out on the installation page but I think it isn't redundant to list them out on the individual components as well.,1.0,Add component dependencies to specific components in docs - Curranty they are listed out on the installation page but I think it isn't redundant to list them out on the individual components as well.,0,add component dependencies to specific components in docs   curranty they are listed out on the installation page but i think it isn t redundant to list them out on the individual components as well ,0
249500,26941058841.0,IssuesEvent,2023-02-08 02:15:32,sigp/lighthouse,https://api.github.com/repos/sigp/lighthouse,opened,Update `warp` to upstream,security HTTP-API dependencies,"## Description

We currently depend on a forked version of `warp` with some extra TLS features added.

It would be great to upstream those features so we can depend on the main crate again. This would allow us to keep up with security updates more easily, e.g. this recent advisory:

https://github.com/advisories/GHSA-8v4j-7jgf-5rg9

That advisory doesn't affect Lighthouse, but it would still be nice to update so that automated tools understand this.
",True,"Update `warp` to upstream - ## Description

We currently depend on a forked version of `warp` with some extra TLS features added.

It would be great to upstream those features so we can depend on the main crate again. This would allow us to keep up with security updates more easily, e.g. this recent advisory:

https://github.com/advisories/GHSA-8v4j-7jgf-5rg9

That advisory doesn't affect Lighthouse, but it would still be nice to update so that automated tools understand this.
",0,update  warp  to upstream      description    we currently depend on a forked version of  warp  with some extra tls features added     it would be great to upstream those features so we can depend on the main crate again  this would allow us to keep up with security updates more easily  e g  this recent advisory          that advisory doesn t affect lighthouse  but it would still be nice to update so that automated tools understand this   ,0
800316,28360753530.0,IssuesEvent,2023-04-12 10:32:36,OpenNebula/one,https://api.github.com/repos/OpenNebula/one,closed,Extend LXD marketplace import procedure with supported distros,Type: Backlog Category: MarketPlace Status: Accepted Priority: Low Category: LXD/LXC,"**Description**
Available images on [the public LXD image server that backs the LXD marketplace](https://images.linuxcontainers.org) matching the [context supported OS](https://github.com/OpenNebula/addon-context-linux#tested-platforms) should all be handled by the import procedure.

**Use case**
Auto-contextualize apps when importing them.

<!--////////////////////////////////////////////-->
<!-- THIS SECTION IS FOR THE DEVELOPMENT TEAM   -->
<!-- BOTH FOR BUGS AND ENHANCEMENT REQUESTS     -->
<!-- PROGRESS WILL BE REFLECTED HERE            -->
<!--////////////////////////////////////////////-->

[context supported apps](https://github.com/OpenNebula/addon-context-linux#tested-platforms)

## Progress Status

AlmaLinux
- [x] 8

Alpine Linux
- [x] 3.11
- [x] 3.12
- [x] 3.13
- [x] 3.14

ALT Linux
- [x] p9
- [x] p10
- [x] Sisyphus

Amazon Linux
- [x] 2

CentOS
- [x] 7
- [x] 8
- [x] 8 Stream

Debian
- [x] 8
- [x] 9
- [x] 10
- [x] 11

Devuan
- [x] 2

Fedora
- [x] 32
- [x] 33
- [x] 34

openSUSE
- [x] 15
- [ ] Tumbleweed

Oracle Linux
- [x] 7
- [x] 8

Rocky Linux
- [x] 8

Springdale Linux
- [x] 8

Ubuntu
- [x] 14.04
- [x] 16.04
- [x] 18.04
- [x] 20.04
- [x] 21.04
- [x] 21.10
- [x] 22.04",1.0,"Extend LXD marketplace import procedure with supported distros - **Description**
Available images on [the public LXD image server that backs the LXD marketplace](https://images.linuxcontainers.org) matching the [context supported OS](https://github.com/OpenNebula/addon-context-linux#tested-platforms) should all be handled by the import procedure.

**Use case**
Auto-contextualize apps when importing them.

<!--////////////////////////////////////////////-->
<!-- THIS SECTION IS FOR THE DEVELOPMENT TEAM   -->
<!-- BOTH FOR BUGS AND ENHANCEMENT REQUESTS     -->
<!-- PROGRESS WILL BE REFLECTED HERE            -->
<!--////////////////////////////////////////////-->

[context supported apps](https://github.com/OpenNebula/addon-context-linux#tested-platforms)

## Progress Status

AlmaLinux
- [x] 8

Alpine Linux
- [x] 3.11
- [x] 3.12
- [x] 3.13
- [x] 3.14

ALT Linux
- [x] p9
- [x] p10
- [x] Sisyphus

Amazon Linux
- [x] 2

CentOS
- [x] 7
- [x] 8
- [x] 8 Stream

Debian
- [x] 8
- [x] 9
- [x] 10
- [x] 11

Devuan
- [x] 2

Fedora
- [x] 32
- [x] 33
- [x] 34

openSUSE
- [x] 15
- [ ] Tumbleweed

Oracle Linux
- [x] 7
- [x] 8

Rocky Linux
- [x] 8

Springdale Linux
- [x] 8

Ubuntu
- [x] 14.04
- [x] 16.04
- [x] 18.04
- [x] 20.04
- [x] 21.04
- [x] 21.10
- [x] 22.04",0,extend lxd marketplace import procedure with supported distros     description    available images on     matching the     should all be handled by the import procedure       use case    auto contextualize apps when importing them                                progress status    almalinux           alpine linux                                        alt linux                    sisyphus    amazon linux           centos                      stream    debian                                devuan           fedora                         opensuse             tumbleweed    oracle linux                  rocky linux           springdale linux           ubuntu                                                               ,0
173134,14403476115.0,IssuesEvent,2020-12-03 16:06:10,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.16: document net/http changes for Go 1.16,Documentation NeedsInvestigation help wanted release-blocker,"As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

<dl id=""net/http""><dt><a href=""/pkg/net/http/"">net/http</a></dt>
  <dd>
    <p>[...]</p>
    <p><!-- CL 250039 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/250039"">https://golang.org/cl/250039</a>: set Content-Length:0 for empty PATCH requests as with POST, PATCH
    </p>
    <p><!-- CL 249440 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/249440"">https://golang.org/cl/249440</a>: match http scheme when selecting http_proxy
    </p>
  </dd>
</dl><!-- net/http -->

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.",1.0,"doc/go1.16: document net/http changes for Go 1.16 - As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

<dl id=""net/http""><dt><a href=""/pkg/net/http/"">net/http</a></dt>
  <dd>
    <p>[...]</p>
    <p><!-- CL 250039 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/250039"">https://golang.org/cl/250039</a>: set Content-Length:0 for empty PATCH requests as with POST, PATCH
    </p>
    <p><!-- CL 249440 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/249440"">https://golang.org/cl/249440</a>: match http scheme when selecting http_proxy
    </p>
  </dd>
</dl><!-- net/http -->

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.",1,doc      document net http changes for go       as of filing this issue  the     contained the following html        net http                                 todo    a href    set content length   for empty patch requests as with post  patch                        todo    a href    match http scheme when selecting http proxy                           per     it s a release blocker for go     beta   to have a complete draft of the eventual release notes  and so the todo needs to be resolved     a sequence of steps to resolve this issue may be        come up with a draft release note entry in this issue  then move the issue to needsfix state      send a cl with  doc           and include  for     fixes   this issue    in the body ,1
804101,29390141995.0,IssuesEvent,2023-05-30 00:49:04,TimerTiTi/backend,https://api.github.com/repos/TimerTiTi/backend,opened,BusinessException Class 및 Exception Handler 구현,✈ feature priority: high ⭐⭐⭐,"<!--
[제목] title (개발소요 예상시간) ex) 소셜 로그인 기능 추가 (3h)
-->
## Background
비즈니스 로직에서 발생하는 예외를 의미하는 최상위 클래스를 생성한다.
비즈니스 예외를 포함한 여러 가지 예외를 한 곳에서 처리하는 글로벌 핸들러를 구현한다.

## AC
| Given   | When  | Then  |
|:--------|:------|:------|
|  |   | 비즈니스 로직에서 발생하는 예외를 의미하는 최상위 클래스를 생성한다. |
| 비즈니스 로직이 수행될 때  | 예외가 발생하면  | Global Exception Handler가 예외를 처리한다. |

## In scope
- BusinessException Class 생성
- Exception Handler 구현 (아래 예외들에 대한 핸들러를 구현한다.)
    - BusinessException
    - ConstraintViolationException
    - MethodArgumentNotValidException
    - BindException
    - MissingServletRequestParameterException
    - MissingServletRequestPartException
    - MethodArgumentTypeMismatchException
    - HttpMessageNotReadableException
    - HttpRequestMethodNotSupportedException
    - Exception

## Out of Scope
- 위에 기재된 Exception을 제외한 나머지 Exception에 대한 핸들러 구현
",1.0,"BusinessException Class 및 Exception Handler 구현 - <!--
[제목] title (개발소요 예상시간) ex) 소셜 로그인 기능 추가 (3h)
-->
## Background
비즈니스 로직에서 발생하는 예외를 의미하는 최상위 클래스를 생성한다.
비즈니스 예외를 포함한 여러 가지 예외를 한 곳에서 처리하는 글로벌 핸들러를 구현한다.

## AC
| Given   | When  | Then  |
|:--------|:------|:------|
|  |   | 비즈니스 로직에서 발생하는 예외를 의미하는 최상위 클래스를 생성한다. |
| 비즈니스 로직이 수행될 때  | 예외가 발생하면  | Global Exception Handler가 예외를 처리한다. |

## In scope
- BusinessException Class 생성
- Exception Handler 구현 (아래 예외들에 대한 핸들러를 구현한다.)
    - BusinessException
    - ConstraintViolationException
    - MethodArgumentNotValidException
    - BindException
    - MissingServletRequestParameterException
    - MissingServletRequestPartException
    - MethodArgumentTypeMismatchException
    - HttpMessageNotReadableException
    - HttpRequestMethodNotSupportedException
    - Exception

## Out of Scope
- 위에 기재된 Exception을 제외한 나머지 Exception에 대한 핸들러 구현
",0,businessexception class 및 exception handler 구현           title  개발소요 예상시간  ex  소셜 로그인 기능 추가              background  비즈니스 로직에서 발생하는 예외를 의미하는 최상위 클래스를 생성한다   비즈니스 예외를 포함한 여러 가지 예외를 한 곳에서 처리하는 글로벌 핸들러를 구현한다        ac    given     when    then                                           비즈니스 로직에서 발생하는 예외를 의미하는 최상위 클래스를 생성한다       비즈니스 로직이 수행될 때    예외가 발생하면    global exception handler가 예외를 처리한다          in scope    businessexception class 생성    exception handler 구현  아래 예외들에 대한 핸들러를 구현한다          businessexception        constraintviolationexception        methodargumentnotvalidexception        bindexception        missingservletrequestparameterexception        missingservletrequestpartexception        methodargumenttypemismatchexception        httpmessagenotreadableexception        httprequestmethodnotsupportedexception        exception       out of scope    위에 기재된 exception을 제외한 나머지 exception에 대한 핸들러 구현  ,0
110350,11698917430.0,IssuesEvent,2020-03-06 14:44:51,golang/go,https://api.github.com/repos/golang/go,closed,doc: missing documentation of quoting the URL of url.Errors in go1.14 release notes,Documentation NeedsFix help wanted,"### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/fraenky8/Library/Caches/go-build""
GOENV=""/Users/fraenky8/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOOS=""darwin""
GOPATH=""/Users/fraenky8/Coding/Go""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/Cellar/go/1.14/libexec""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/1.14/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/8v/jgh2dzcn62n0lfyws13mc_rw0000gp/T/go-build103321297=/tmp/go-build -gno-record-gcc-switches -fno-common""

</pre></details>

### What did you do?

Print a `url.Error`:

```go
err := &url.Error{
	Op:  ""Get"",
	URL: ""http://localhost/test/path"",
	Err: errors.New(""EOF""),
}

fmt.Printf(""something went wrong: %v"", err)
```

### What did you expect to see?

```
something went wrong: Get http://localhost/test/path: EOF
```

### What did you see instead?
```
something went wrong: Get ""http://localhost/test/path"": EOF
```
The URL is now quoted.

This originates from PR https://github.com/golang/go/pull/29384 and is mentioned here: https://github.com/stellar/go/pull/2325#discussion_r385321367 

The documentation in the release notes of go1.14 is missing for this change.",1.0,"doc: missing documentation of quoting the URL of url.Errors in go1.14 release notes - ### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/fraenky8/Library/Caches/go-build""
GOENV=""/Users/fraenky8/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOOS=""darwin""
GOPATH=""/Users/fraenky8/Coding/Go""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/Cellar/go/1.14/libexec""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/1.14/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/8v/jgh2dzcn62n0lfyws13mc_rw0000gp/T/go-build103321297=/tmp/go-build -gno-record-gcc-switches -fno-common""

</pre></details>

### What did you do?

Print a `url.Error`:

```go
err := &url.Error{
	Op:  ""Get"",
	URL: ""http://localhost/test/path"",
	Err: errors.New(""EOF""),
}

fmt.Printf(""something went wrong: %v"", err)
```

### What did you expect to see?

```
something went wrong: Get http://localhost/test/path: EOF
```

### What did you see instead?
```
something went wrong: Get ""http://localhost/test/path"": EOF
```
The URL is now quoted.

This originates from PR https://github.com/golang/go/pull/29384 and is mentioned here: https://github.com/stellar/go/pull/2325#discussion_r385321367 

The documentation in the release notes of go1.14 is missing for this change.",1,doc  missing documentation of quoting the url of url errors in     release notes       what version of go are you using   go version            go version  go version     darwin             does this issue reproduce with the latest release     yes         what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   users   library caches go build   goenv   users   library application support go env   goexe     goflags     gohostarch      gohostos  darwin   goinsecure     goos  darwin   gopath   users   coding go   goproxy     goroot   usr local cellar go     libexec   gosumdb  sum golang org   gotmpdir     gotooldir   usr local cellar go     libexec pkg tool darwin     gccgo  gccgo   ar  ar   cc  clang   cxx  clang     cgo enabled      cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders       t go    tmp go build  gno record gcc switches  fno common               what did you do     print a  url error         go  err     url error   	op    get    	url      	err  errors new  eof          fmt printf  something went wrong   v   err              what did you expect to see          something went wrong  get   eof             what did you see instead        something went wrong  get    eof       the url is now quoted     this originates from pr   and is mentioned here        the documentation in the release notes of     is missing for this change ,1
425606,12342896117.0,IssuesEvent,2020-05-15 02:16:05,slackapi/python-slackclient,https://api.github.com/repos/slackapi/python-slackclient,closed,Slack RTM caching Run_async,Priority: Medium Version: 2x area:concurrency bug rtm-client v2.6 in-progress,"### Description

Describe your issue here.

### What type of issue is this? (place an `x` in one of the `[ ]`)
- [x] bug
- [ ] enhancement (feature request)
- [ ] question
- [ ] documentation related
- [ ] testing related
- [ ] discussion

### Requirements (place an `x` in each of the `[ ]`)
* [x] I've read and understood the [Contributing guidelines](https://github.com/slackapi/python-slackclient/blob/master/.github/contributing.md) and have done my best effort to follow them.
* [x] I've read and agree to the [Code of Conduct](https://slackhq.github.io/code-of-conduct).
* [x] I've searched for any related issues and avoided creating a duplicate issue.

---

### Bug Report

Filling out the following details about bugs will help us solve your issue sooner.

#### Reproducible in:

slackclient version: 1.3.1

python version: 3.6.8

OS version(s): Windows 10

#### Steps to reproduce:

1. Start RTM client with run_async set to false
2. Cancel and change to true and rerun
3. Cancel and remove arg and rerun
4. Try a web_api get method I was user_info
#### Expected result:

What you expected to happen 
Wait until client returns with a response
#### Actual result: 

What actually happened
Returns an async task item
#### Attachments:

Logs, screenshots, screencast, sample project, funny gif, etc.
`    assert result[""ok""] == True
TypeError: '_asyncio.Task' object is not subscriptable`",1.0,"Slack RTM caching Run_async - ### Description

Describe your issue here.

### What type of issue is this? (place an `x` in one of the `[ ]`)
- [x] bug
- [ ] enhancement (feature request)
- [ ] question
- [ ] documentation related
- [ ] testing related
- [ ] discussion

### Requirements (place an `x` in each of the `[ ]`)
* [x] I've read and understood the [Contributing guidelines](https://github.com/slackapi/python-slackclient/blob/master/.github/contributing.md) and have done my best effort to follow them.
* [x] I've read and agree to the [Code of Conduct](https://slackhq.github.io/code-of-conduct).
* [x] I've searched for any related issues and avoided creating a duplicate issue.

---

### Bug Report

Filling out the following details about bugs will help us solve your issue sooner.

#### Reproducible in:

slackclient version: 1.3.1

python version: 3.6.8

OS version(s): Windows 10

#### Steps to reproduce:

1. Start RTM client with run_async set to false
2. Cancel and change to true and rerun
3. Cancel and remove arg and rerun
4. Try a web_api get method I was user_info
#### Expected result:

What you expected to happen 
Wait until client returns with a response
#### Actual result: 

What actually happened
Returns an async task item
#### Attachments:

Logs, screenshots, screencast, sample project, funny gif, etc.
`    assert result[""ok""] == True
TypeError: '_asyncio.Task' object is not subscriptable`",0,slack rtm caching run async       description    describe your issue here         what type of issue is this   place an  x  in one of the           bug      enhancement  feature request       question      documentation related      testing related      discussion        requirements  place an  x  in each of the           i ve read and understood the     and have done my best effort to follow them       i ve read and agree to the          i ve searched for any related issues and avoided creating a duplicate issue                bug report    filling out the following details about bugs will help us solve your issue sooner          reproducible in     slackclient version           python version           os version s   windows           steps to reproduce        start rtm client with run async set to false     cancel and change to true and rerun     cancel and remove arg and rerun     try a web api get method i was user info       expected result     what you expected to happen   wait until client returns with a response       actual result      what actually happened  returns an async task item       attachments     logs  screenshots  screencast  sample project  funny gif  etc        assert result     true  typeerror    asyncio task  object is not subscriptable ,0
272738,29795080844.0,IssuesEvent,2023-06-16 01:09:23,billmcchesney1/hadoop,https://api.github.com/repos/billmcchesney1/hadoop,closed,CVE-2019-20444 (Critical) detected in netty-all-4.1.42.Final.jar - autoclosed,Mend: dependency security vulnerability,"## CVE-2019-20444 - Critical Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>netty-all-4.1.42.Final.jar</b></p></summary>

<p>Netty is an asynchronous event-driven network application framework for
    rapid development of maintainable high performance protocol servers and
    clients.</p>
<p>Library home page: <a href=""https://netty.io/"">https://netty.io/</a></p>
<p>Path to vulnerable library: /hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice-hbase/hadoop-yarn-server-timelineservice-hbase-client/target/lib/netty-all-4.1.42.Final.jar</p>
<p>

Dependency Hierarchy:
  - :x: **netty-all-4.1.42.Final.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/billmcchesney1/hadoop/commit/6dcd8400219941dcbd7fb0f6b980cc2c6a2a6b0a"">6dcd8400219941dcbd7fb0f6b980cc2c6a2a6b0a</a></p>
<p>Found in base branch: <b>trunk</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>  
  
HttpObjectDecoder.java in Netty before 4.1.44 allows an HTTP header that lacks a colon, which might be interpreted as a separate header with an incorrect syntax, or might be interpreted as an ""invalid fold.""

<p>Publish Date: 2020-01-29
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-20444>CVE-2019-20444</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.1</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: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20444"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20444</a></p>
<p>Release Date: 2020-01-29</p>
<p>Fix Resolution: 4.1.44.Final</p>

</p>
</details>
<p></p>
",True,"CVE-2019-20444 (Critical) detected in netty-all-4.1.42.Final.jar - autoclosed - ## CVE-2019-20444 - Critical Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>netty-all-4.1.42.Final.jar</b></p></summary>

<p>Netty is an asynchronous event-driven network application framework for
    rapid development of maintainable high performance protocol servers and
    clients.</p>
<p>Library home page: <a href=""https://netty.io/"">https://netty.io/</a></p>
<p>Path to vulnerable library: /hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice-hbase/hadoop-yarn-server-timelineservice-hbase-client/target/lib/netty-all-4.1.42.Final.jar</p>
<p>

Dependency Hierarchy:
  - :x: **netty-all-4.1.42.Final.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/billmcchesney1/hadoop/commit/6dcd8400219941dcbd7fb0f6b980cc2c6a2a6b0a"">6dcd8400219941dcbd7fb0f6b980cc2c6a2a6b0a</a></p>
<p>Found in base branch: <b>trunk</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>  
  
HttpObjectDecoder.java in Netty before 4.1.44 allows an HTTP header that lacks a colon, which might be interpreted as a separate header with an incorrect syntax, or might be interpreted as an ""invalid fold.""

<p>Publish Date: 2020-01-29
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-20444>CVE-2019-20444</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.1</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: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20444"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20444</a></p>
<p>Release Date: 2020-01-29</p>
<p>Fix Resolution: 4.1.44.Final</p>

</p>
</details>
<p></p>
",0,cve      critical  detected in netty all       final jar   autoclosed      cve       critical severity vulnerability     vulnerable library    netty all       final jar      netty is an asynchronous event driven network application framework for     rapid development of maintainable high performance protocol servers and     clients    library home page   a href     path to vulnerable library   hadoop yarn project hadoop yarn hadoop yarn server hadoop yarn server timelineservice hbase hadoop yarn server timelineservice hbase client target lib netty all       final jar     dependency hierarchy       x    netty all       final jar    vulnerable library   found in head commit   a href     found in base branch   trunk              vulnerability details         httpobjectdecoder java in netty before       allows an http header that lacks a colon  which might be interpreted as a separate header with an incorrect syntax  or might be interpreted as an  invalid fold     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  none   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution        final          ,0
26717,5282655565.0,IssuesEvent,2017-02-07 19:24:18,golang/go,https://api.github.com/repos/golang/go,closed,time: behavior of function Parse for Feburary 31,Documentation NeedsFix,"### What version of Go are you using (`go version`)?
go version go1.7.5 darwin/amd64

### What did you do?
https://play.golang.org/p/R4HlVseTm2

### What did you expect to see?
A behavior which corresponds the documentation.

Actually I expect to see an error, but the current documentation says that it should be parsed successfully.
> For example February 31 and even February 99 are valid dates, specifying dates in March and May.

Documentation was introduced by CL https://golang.org/cl/14123
but that behavior was changed later by CL https://golang.org/cl/17710",1.0,"time: behavior of function Parse for Feburary 31 - ### What version of Go are you using (`go version`)?
go version go1.7.5 darwin/amd64

### What did you do?
https://play.golang.org/p/R4HlVseTm2

### What did you expect to see?
A behavior which corresponds the documentation.

Actually I expect to see an error, but the current documentation says that it should be parsed successfully.
> For example February 31 and even February 99 are valid dates, specifying dates in March and May.

Documentation was introduced by CL https://golang.org/cl/14123
but that behavior was changed later by CL https://golang.org/cl/17710",1,time  behavior of function parse for feburary         what version of go are you using   go version     go version       darwin          what did you do            what did you expect to see   a behavior which corresponds the documentation     actually i expect to see an error  but the current documentation says that it should be parsed successfully     for example february   and even february   are valid dates  specifying dates in march and may     documentation was introduced by cl    but that behavior was changed later by cl  ,1
17659,4184067055.0,IssuesEvent,2016-06-23 04:32:07,golang/go,https://api.github.com/repos/golang/go,closed,testing: output failure report to stderr as per docu instead of stdout,Documentation,"Please answer these questions before submitting your issue. Thanks!

1. What version of Go are you using (`go version`)?
1.6.2
(installed via go1.6.2.linux-amd64.tar.gz at https://golang.org/dl/)

2. What operating system and processor architecture are you using (`go env`)?
The OS is Fedora 23 (Workstation Edition).  The `go env` output doesn't quite capture that fully:

GOARCH=""amd64""
GOBIN=""/usr/src/go/bin""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/usr/src/go""
GORACE=""""
GOROOT=""/usr/src/golang-1.6""
GOTOOLDIR=""/usr/src/golang-1.6/pkg/tool/linux_amd64""
GO15VENDOREXPERIMENT=""1""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0""
CXX=""g++""
CGO_ENABLED=""1""

3. What did you do?
go code https://play.golang.org/p/6GR6cTzVcM
go test case for that code https://play.golang.org/p/ZEJ2iNJMPV

Run a simple test case that fails, outputting a t.Fatal(err).

4. What did you expect to see?

https://golang.org/pkg/testing/#T indicates that testing logs are accumulated and output to stderr so I expect the t.Fatal() output report to be on stderr.

5. What did you see instead?

The report output is on stdout.

It seems like something as trivial as https://github.com/tpepper/go/commit/c60fccd1231de145ec81f35b8693000e91eafbe5 (which is on top of tip's changes to allow subtests) could bring the report output in line with the documentation.  But as noted in that tentative commit message, this might break users who have coded to the behavior without reporting the inconsistency.  Perhaps the answer is to change the documentation, except the enabling the distinction between stdout and stderr is actually useful.

",1.0,"testing: output failure report to stderr as per docu instead of stdout - Please answer these questions before submitting your issue. Thanks!

1. What version of Go are you using (`go version`)?
1.6.2
(installed via go1.6.2.linux-amd64.tar.gz at https://golang.org/dl/)

2. What operating system and processor architecture are you using (`go env`)?
The OS is Fedora 23 (Workstation Edition).  The `go env` output doesn't quite capture that fully:

GOARCH=""amd64""
GOBIN=""/usr/src/go/bin""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/usr/src/go""
GORACE=""""
GOROOT=""/usr/src/golang-1.6""
GOTOOLDIR=""/usr/src/golang-1.6/pkg/tool/linux_amd64""
GO15VENDOREXPERIMENT=""1""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0""
CXX=""g++""
CGO_ENABLED=""1""

3. What did you do?
go code https://play.golang.org/p/6GR6cTzVcM
go test case for that code https://play.golang.org/p/ZEJ2iNJMPV

Run a simple test case that fails, outputting a t.Fatal(err).

4. What did you expect to see?

https://golang.org/pkg/testing/#T indicates that testing logs are accumulated and output to stderr so I expect the t.Fatal() output report to be on stderr.

5. What did you see instead?

The report output is on stdout.

It seems like something as trivial as https://github.com/tpepper/go/commit/c60fccd1231de145ec81f35b8693000e91eafbe5 (which is on top of tip's changes to allow subtests) could bring the report output in line with the documentation.  But as noted in that tentative commit message, this might break users who have coded to the behavior without reporting the inconsistency.  Perhaps the answer is to change the documentation, except the enabling the distinction between stdout and stderr is actually useful.

",1,testing  output failure report to stderr as per docu instead of stdout   please answer these questions before submitting your issue  thanks        what version of go are you using   go version             installed via       linux   tar gz at         what operating system and processor architecture are you using   go env     the os is fedora    workstation edition    the  go env  output doesn t quite capture that fully     goarch      gobin   usr src go bin   goexe     gohostarch      gohostos  linux   goos  linux   gopath   usr src go   gorace     goroot   usr src golang       gotooldir   usr src golang     pkg tool linux            cc  gcc   gogccflags   fpic     pthread  fmessage length     cxx  g     cgo enabled           what did you do   go code    go test case for that code      run a simple test case that fails  outputting a t fatal err         what did you expect to see       indicates that testing logs are accumulated and output to stderr so i expect the t fatal   output report to be on stderr        what did you see instead     the report output is on stdout     it seems like something as trivial as    which is on top of tip s changes to allow subtests  could bring the report output in line with the documentation   but as noted in that tentative commit message  this might break users who have coded to the behavior without reporting the inconsistency   perhaps the answer is to change the documentation  except the enabling the distinction between stdout and stderr is actually useful     ,1
111948,14174032277.0,IssuesEvent,2020-11-12 19:15:47,mdn/yari,https://api.github.com/repos/mdn/yari,closed,Unbreak the home page post-fiori,design system,"Not really an important page but we just mustn't forget to fix it. 
<img width=""1505"" alt=""Screen Shot 2020-10-27 at 10 33 12 AM"" src=""https://user-images.githubusercontent.com/26739/97316222-e2158700-183f-11eb-823f-d91ac3f1fe3f.png"">
",1.0,"Unbreak the home page post-fiori - Not really an important page but we just mustn't forget to fix it. 
<img width=""1505"" alt=""Screen Shot 2020-10-27 at 10 33 12 AM"" src=""https://user-images.githubusercontent.com/26739/97316222-e2158700-183f-11eb-823f-d91ac3f1fe3f.png"">
",0,unbreak the home page post fiori   not really an important page but we just mustn t forget to fix it     img width     alt  screen shot       at       am  src     ,0
251403,8014888414.0,IssuesEvent,2018-07-25 08:16:10,Radboud-University/osc-nijmegen,https://api.github.com/repos/Radboud-University/osc-nijmegen,opened,create contents in about.md,high priority website,"Create contents in the 'About' page. The about section should minimally include the following:
- goals of the community
- types of activities
- targeted members of the community

Proposed action:

- [ ] prepare a draft either by modifying /_pages/about.md directly on GitHub and create a pull request or use a collaborative editing tool (google docs) and propose contents there.
 
Proposals welcome on how to structure this.",1.0,"create contents in about.md - Create contents in the 'About' page. The about section should minimally include the following:
- goals of the community
- types of activities
- targeted members of the community

Proposed action:

- [ ] prepare a draft either by modifying /_pages/about.md directly on GitHub and create a pull request or use a collaborative editing tool (google docs) and propose contents there.
 
Proposals welcome on how to structure this.",0,create contents in about md   create contents in the  about  page  the about section should minimally include the following     goals of the community    types of activities    targeted members of the community    proposed action         prepare a draft either by modifying   pages about md directly on github and create a pull request or use a collaborative editing tool  google docs  and propose contents there      proposals welcome on how to structure this ,0
299398,9205455451.0,IssuesEvent,2019-03-08 10:37:17,xwikisas/application-meeting,https://api.github.com/repos/xwikisas/application-meeting,opened,Many deprecation messages in the Console while working with the Meeting app,Priority: Minor Type: Bug,"While doing some tests on the Meeting app I've encounter many ""Deprecated usage of getter"" messages in the Console. I've noticed that some times it takes a bit more of time to save a meeting when this messages keep appearing in the console.

Environment: Windows 10, XWiki 11.1 with MySQL 5.7 and Edge 18

`2019-03-08 12:07:44,647 [http://localhost:8080/xwiki/bin/create/Meeting/WebHome?type=Meeting.Code.MeetingTemplateProvider] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 18:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:07:53,130 [http://localhost:8080/xwiki/bin/edit/Meeting/New%20meet/WebHome?template=Meeting.Code.MeetingTemplate&parent=Meeting.WebHome&title=New+meet] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 12:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:08:17.994:INFO:oejshC.xwiki:http://localhost:8080/xwiki/rest/wikis/xwiki/classes/Meeting.Code.MeetingClass/properties/leader/values?fp=&limit=10: RestletServlet: [Restlet] ServerServlet: component class is null
2019-03-08 12:08:21.722:INFO:oejshC.xwiki:http://localhost:8080/xwiki/rest/wikis/xwiki/classes/Meeting.Code.MeetingClass/properties/leader/values?fp=&limit=10: RestletServlet: [Restlet] Attaching application: org.xwiki.rest.internal.XWikiRestletJaxRsApplication@812155 to URI: /xwiki/rest
2019-03-08 12:08:36,358 [http://localhost:8080/xwiki/bin/view/Meeting/New%20meet/] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 20:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:08:47,756 [http://localhost:8080/xwiki/bin/view/Meeting/] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 13:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:20:37,730 [http://localhost:8080/xwiki/bin/edit/Meeting/New%20meet/WebHome] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 148:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:20:41,141 [http://localhost:8080/xwiki/bin/edit/Meeting/New%20meet/WebHome] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 12:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:20:41,980 [http://localhost:8080/xwiki/bin/edit/Meeting/New%20meet/WebHome] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 180:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:20:42,369 [http://localhost:8080/xwiki/bin/edit/Meeting/New%20meet/WebHome] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 18:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:21:33,611 [http://localhost:8080/xwiki/bin/view/Meeting/New%20meet/] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 14:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:30:11,977 [http://localhost:8080/xwiki/bin/view/Meeting/] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 180:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:30:15,032 [http://localhost:8080/xwiki/bin/create/Meeting/WebHome?type=Meeting.Code.MeetingTemplateProvider] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 180:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:30:23,366 [http://localhost:8080/xwiki/bin/edit/Meeting/Past%20Meeting%202/WebHome?template=Meeting.Code.MeetingTemplate&parent=Meeting.WebHome&title=Past+Meeting+2] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 13:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:30:41,313 [http://localhost:8080/xwiki/bin/view/Meeting/Past%20Meeting%202/] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 18:xwiki:Meeting.Code.MeetingSheet@12,26
2019-03-08 12:30:41,529 [http://localhost:8080/xwiki/bin/view/Meeting/Past%20Meeting%202/] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 18:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:31:53,863 [http://localhost:8080/xwiki/bin/view/Meeting/Past%20Meeting%202/?createPoll=true&parent=Meeting.WebHome&template=XPoll.XPollTemplate] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 20:xwiki:Meeting.Code.MeetingSheet@12,26
2019-03-08 12:31:54,117 [http://localhost:8080/xwiki/bin/view/Meeting/Past%20Meeting%202/?createPoll=true&parent=Meeting.WebHome&template=XPoll.XPollTemplate] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 20:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:31:54,323 [http://localhost:8080/xwiki/bin/edit/XPoll/XPoll%20for%20the%20Meeting%20Past%20Meeting%202?createPoll=true&parent=Meeting.WebHome&template=XPoll.XPollTemplate] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 20:xwiki:XPoll.XPollSheet@1,150
2019-03-08 12:31:54,342 [http://localhost:8080/xwiki/bin/edit/XPoll/XPoll%20for%20the%20Meeting%20Past%20Meeting%202?createPoll=true&parent=Meeting.WebHome&template=XPoll.XPollTemplate] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 20:xwiki:XPoll.XPollSheet@1,150
2019-03-08 12:31:54,359 [http://localhost:8080/xwiki/bin/edit/XPoll/XPoll%20for%20the%20Meeting%20Past%20Meeting%202?createPoll=true&parent=Meeting.WebHome&template=XPoll.XPollTemplate] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 20:xwiki:XPoll.XPollSheet@1,150
2019-03-08 12:31:54,555 [http://localhost:8080/xwiki/bin/edit/XPoll/XPoll%20for%20the%20Meeting%20Past%20Meeting%202?createPoll=true&parent=Meeting.WebHome&template=XPoll.XPollTemplate] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 20:xwiki:XPoll.XPollSheet@1,150`",1.0,"Many deprecation messages in the Console while working with the Meeting app - While doing some tests on the Meeting app I've encounter many ""Deprecated usage of getter"" messages in the Console. I've noticed that some times it takes a bit more of time to save a meeting when this messages keep appearing in the console.

Environment: Windows 10, XWiki 11.1 with MySQL 5.7 and Edge 18

`2019-03-08 12:07:44,647 [http://localhost:8080/xwiki/bin/create/Meeting/WebHome?type=Meeting.Code.MeetingTemplateProvider] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 18:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:07:53,130 [http://localhost:8080/xwiki/bin/edit/Meeting/New%20meet/WebHome?template=Meeting.Code.MeetingTemplate&parent=Meeting.WebHome&title=New+meet] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 12:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:08:17.994:INFO:oejshC.xwiki:http://localhost:8080/xwiki/rest/wikis/xwiki/classes/Meeting.Code.MeetingClass/properties/leader/values?fp=&limit=10: RestletServlet: [Restlet] ServerServlet: component class is null
2019-03-08 12:08:21.722:INFO:oejshC.xwiki:http://localhost:8080/xwiki/rest/wikis/xwiki/classes/Meeting.Code.MeetingClass/properties/leader/values?fp=&limit=10: RestletServlet: [Restlet] Attaching application: org.xwiki.rest.internal.XWikiRestletJaxRsApplication@812155 to URI: /xwiki/rest
2019-03-08 12:08:36,358 [http://localhost:8080/xwiki/bin/view/Meeting/New%20meet/] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 20:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:08:47,756 [http://localhost:8080/xwiki/bin/view/Meeting/] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 13:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:20:37,730 [http://localhost:8080/xwiki/bin/edit/Meeting/New%20meet/WebHome] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 148:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:20:41,141 [http://localhost:8080/xwiki/bin/edit/Meeting/New%20meet/WebHome] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 12:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:20:41,980 [http://localhost:8080/xwiki/bin/edit/Meeting/New%20meet/WebHome] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 180:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:20:42,369 [http://localhost:8080/xwiki/bin/edit/Meeting/New%20meet/WebHome] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 18:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:21:33,611 [http://localhost:8080/xwiki/bin/view/Meeting/New%20meet/] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 14:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:30:11,977 [http://localhost:8080/xwiki/bin/view/Meeting/] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 180:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:30:15,032 [http://localhost:8080/xwiki/bin/create/Meeting/WebHome?type=Meeting.Code.MeetingTemplateProvider] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 180:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:30:23,366 [http://localhost:8080/xwiki/bin/edit/Meeting/Past%20Meeting%202/WebHome?template=Meeting.Code.MeetingTemplate&parent=Meeting.WebHome&title=Past+Meeting+2] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 13:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:30:41,313 [http://localhost:8080/xwiki/bin/view/Meeting/Past%20Meeting%202/] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 18:xwiki:Meeting.Code.MeetingSheet@12,26
2019-03-08 12:30:41,529 [http://localhost:8080/xwiki/bin/view/Meeting/Past%20Meeting%202/] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 18:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:31:53,863 [http://localhost:8080/xwiki/bin/view/Meeting/Past%20Meeting%202/?createPoll=true&parent=Meeting.WebHome&template=XPoll.XPollTemplate] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 20:xwiki:Meeting.Code.MeetingSheet@12,26
2019-03-08 12:31:54,117 [http://localhost:8080/xwiki/bin/view/Meeting/Past%20Meeting%202/?createPoll=true&parent=Meeting.WebHome&template=XPoll.XPollTemplate] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 20:xwiki:Meeting.Code.NextMeetingsPanel@11,28
2019-03-08 12:31:54,323 [http://localhost:8080/xwiki/bin/edit/XPoll/XPoll%20for%20the%20Meeting%20Past%20Meeting%202?createPoll=true&parent=Meeting.WebHome&template=XPoll.XPollTemplate] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 20:xwiki:XPoll.XPollSheet@1,150
2019-03-08 12:31:54,342 [http://localhost:8080/xwiki/bin/edit/XPoll/XPoll%20for%20the%20Meeting%20Past%20Meeting%202?createPoll=true&parent=Meeting.WebHome&template=XPoll.XPollTemplate] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 20:xwiki:XPoll.XPollSheet@1,150
2019-03-08 12:31:54,359 [http://localhost:8080/xwiki/bin/edit/XPoll/XPoll%20for%20the%20Meeting%20Past%20Meeting%202?createPoll=true&parent=Meeting.WebHome&template=XPoll.XPollTemplate] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 20:xwiki:XPoll.XPollSheet@1,150
2019-03-08 12:31:54,555 [http://localhost:8080/xwiki/bin/edit/XPoll/XPoll%20for%20the%20Meeting%20Past%20Meeting%202?createPoll=true&parent=Meeting.WebHome&template=XPoll.XPollTemplate] WARN  o.x.v.i.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getName] in 20:xwiki:XPoll.XPollSheet@1,150`",0,many deprecation messages in the console while working with the meeting app   while doing some tests on the meeting app i ve encounter many  deprecated usage of getter  messages in the console  i ve noticed that some times it takes a bit more of time to save a meeting when this messages keep appearing in the console     environment  windows    xwiki     with mysql     and edge                       warn  o x v i defaultvelocityengine    deprecated usage of getter   in   xwiki meeting code nextmeetingspanel                      warn  o x v i defaultvelocityengine    deprecated usage of getter   in   xwiki meeting code nextmeetingspanel                    info oejshc xwiki   restletservlet    serverservlet  component class is null                info oejshc xwiki   restletservlet    attaching application  org xwiki rest internal xwikirestletjaxrsapplication   to uri   xwiki rest                  warn  o x v i defaultvelocityengine    deprecated usage of getter   in   xwiki meeting code nextmeetingspanel                      warn  o x v i defaultvelocityengine    deprecated usage of getter   in   xwiki meeting code nextmeetingspanel                      warn  o x v i defaultvelocityengine    deprecated usage of getter   in   xwiki meeting code nextmeetingspanel                      warn  o x v i defaultvelocityengine    deprecated usage of getter   in   xwiki meeting code nextmeetingspanel                      warn  o x v i defaultvelocityengine    deprecated usage of getter   in   xwiki meeting code nextmeetingspanel                      warn  o x v i defaultvelocityengine    deprecated usage of getter   in   xwiki meeting code nextmeetingspanel                      warn  o x v i defaultvelocityengine    deprecated usage of getter   in   xwiki meeting code nextmeetingspanel                      warn  o x v i defaultvelocityengine    deprecated usage of getter   in   xwiki meeting code nextmeetingspanel                      warn  o x v i defaultvelocityengine    deprecated usage of getter   in   xwiki meeting code nextmeetingspanel                      warn  o x v i defaultvelocityengine    deprecated usage of getter   in   xwiki meeting code nextmeetingspanel                      warn  o x v i defaultvelocityengine    deprecated usage of getter   in   xwiki meeting code meetingsheet                      warn  o x v i defaultvelocityengine    deprecated usage of getter   in   xwiki meeting code nextmeetingspanel                      warn  o x v i defaultvelocityengine    deprecated usage of getter   in   xwiki meeting code meetingsheet                      warn  o x v i defaultvelocityengine    deprecated usage of getter   in   xwiki meeting code nextmeetingspanel                      warn  o x v i defaultvelocityengine    deprecated usage of getter   in   xwiki xpoll xpollsheet                      warn  o x v i defaultvelocityengine    deprecated usage of getter   in   xwiki xpoll xpollsheet                      warn  o x v i defaultvelocityengine    deprecated usage of getter   in   xwiki xpoll xpollsheet                      warn  o x v i defaultvelocityengine    deprecated usage of getter   in   xwiki xpoll xpollsheet     ,0
69168,14973457801.0,IssuesEvent,2021-01-28 01:07:38,TreyM-WSS/catalog-profiler-examples,https://api.github.com/repos/TreyM-WSS/catalog-profiler-examples,opened,CVE-2020-36182 (Medium) detected in jackson-databind-2.9.8.jar,security vulnerability,"## CVE-2020-36182 - 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.8.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: catalog-profiler-examples/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.9.8/11283f21cc480aa86c4df7a0a3243ec508372ed2/jackson-databind-2.9.8.jar</p>
<p>

Dependency Hierarchy:
  - jersey-media-json-jackson-2.27.jar (Root Library)
    - jackson-module-jaxb-annotations-2.8.10.jar
      - :x: **jackson-databind-2.9.8.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/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.dbcp2.cpdsadapter.DriverAdapterCPDS.

<p>Publish Date: 2021-01-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36182>CVE-2020-36182</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.8"",""isTransitiveDependency"":true,""dependencyTree"":""org.glassfish.jersey.media:jersey-media-json-jackson:2.27;com.fasterxml.jackson.module:jackson-module-jaxb-annotations:2.8.10;com.fasterxml.jackson.core:jackson-databind:2.9.8"",""isMinimumFixVersionAvailable"":false}],""vulnerabilityIdentifier"":""CVE-2020-36182"",""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.dbcp2.cpdsadapter.DriverAdapterCPDS."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36182"",""cvss2Severity"":""medium"",""cvss2Score"":""6.8"",""extraData"":{}}</REMEDIATE> -->",True,"CVE-2020-36182 (Medium) detected in jackson-databind-2.9.8.jar - ## CVE-2020-36182 - 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.8.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: catalog-profiler-examples/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.9.8/11283f21cc480aa86c4df7a0a3243ec508372ed2/jackson-databind-2.9.8.jar</p>
<p>

Dependency Hierarchy:
  - jersey-media-json-jackson-2.27.jar (Root Library)
    - jackson-module-jaxb-annotations-2.8.10.jar
      - :x: **jackson-databind-2.9.8.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/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.dbcp2.cpdsadapter.DriverAdapterCPDS.

<p>Publish Date: 2021-01-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36182>CVE-2020-36182</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.8"",""isTransitiveDependency"":true,""dependencyTree"":""org.glassfish.jersey.media:jersey-media-json-jackson:2.27;com.fasterxml.jackson.module:jackson-module-jaxb-annotations:2.8.10;com.fasterxml.jackson.core:jackson-databind:2.9.8"",""isMinimumFixVersionAvailable"":false}],""vulnerabilityIdentifier"":""CVE-2020-36182"",""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.dbcp2.cpdsadapter.DriverAdapterCPDS."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36182"",""cvss2Severity"":""medium"",""cvss2Score"":""6.8"",""extraData"":{}}</REMEDIATE> -->",0,cve      medium  detected in jackson databind       jar      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  catalog profiler examples build gradle   path to vulnerable library   home wss scanner  gradle caches modules   files     com fasterxml jackson core jackson databind         jackson databind       jar     dependency hierarchy      jersey media json jackson     jar  root library        jackson module jaxb annotations       jar          x    jackson databind       jar    vulnerable library   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   cpdsadapter driveradaptercpds    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   cpdsadapter driveradaptercpds    vulnerabilityurl        ,0
129745,18109732590.0,IssuesEvent,2021-09-23 01:01:10,maorkuriel/ksa,https://api.github.com/repos/maorkuriel/ksa,opened,CVE-2017-12611 (High) detected in struts2-core-2.3.31.jar,security vulnerability,"## CVE-2017-12611 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>struts2-core-2.3.31.jar</b></p></summary>

<p>Apache Struts 2</p>
<p>Library home page: <a href=""http://struts.apache.org/struts2-core/"">http://struts.apache.org/struts2-core/</a></p>
<p>Path to dependency file: ksa/ksa-web-root/ksa-statistics-web/pom.xml</p>
<p>Path to vulnerable library: er/.m2/repository/org/apache/struts/struts2-core/2.3.31/struts2-core-2.3.31.jar,er/.m2/repository/org/apache/struts/struts2-core/2.3.31/struts2-core-2.3.31.jar,er/.m2/repository/org/apache/struts/struts2-core/2.3.31/struts2-core-2.3.31.jar,er/.m2/repository/org/apache/struts/struts2-core/2.3.31/struts2-core-2.3.31.jar,er/.m2/repository/org/apache/struts/struts2-core/2.3.31/struts2-core-2.3.31.jar,er/.m2/repository/org/apache/struts/struts2-core/2.3.31/struts2-core-2.3.31.jar,ksa-web-root/ksa-web/target/ROOT/WEB-INF/lib/struts2-core-2.3.31.jar,er/.m2/repository/org/apache/struts/struts2-core/2.3.31/struts2-core-2.3.31.jar,er/.m2/repository/org/apache/struts/struts2-core/2.3.31/struts2-core-2.3.31.jar</p>
<p>

Dependency Hierarchy:
  - :x: **struts2-core-2.3.31.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
In Apache Struts 2.0.0 through 2.3.33 and 2.5 through 2.5.10.1, using an unintentional expression in a Freemarker tag instead of string literals can lead to a RCE attack.

<p>Publish Date: 2017-09-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-12611>CVE-2017-12611</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://cwiki.apache.org/confluence/display/WW/S2-053"">https://cwiki.apache.org/confluence/display/WW/S2-053</a></p>
<p>Release Date: 2017-09-20</p>
<p>Fix Resolution: org.apache.struts:struts2-core:2.3.34;org.apache.struts:struts2-core:2.5.12</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""org.apache.struts"",""packageName"":""struts2-core"",""packageVersion"":""2.3.31"",""packageFilePaths"":[""/ksa-web-root/ksa-statistics-web/pom.xml"",""/ksa-web-root/ksa-web/pom.xml"",""/ksa-web-root/ksa-logistics-web/pom.xml"",""/ksa-web-root/ksa-system-web/pom.xml"",""/ksa-web-root/ksa-finance-web/pom.xml"",""/ksa-web-root/ksa-security-web/pom.xml"",""/ksa-web-core/pom.xml"",""/ksa-web-root/ksa-bd-web/pom.xml""],""isTransitiveDependency"":false,""dependencyTree"":""org.apache.struts:struts2-core:2.3.31"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""org.apache.struts:struts2-core:2.3.34;org.apache.struts:struts2-core:2.5.12""}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""CVE-2017-12611"",""vulnerabilityDetails"":""In Apache Struts 2.0.0 through 2.3.33 and 2.5 through 2.5.10.1, using an unintentional expression in a Freemarker tag instead of string literals can lead to a RCE attack."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-12611"",""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-2017-12611 (High) detected in struts2-core-2.3.31.jar - ## CVE-2017-12611 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>struts2-core-2.3.31.jar</b></p></summary>

<p>Apache Struts 2</p>
<p>Library home page: <a href=""http://struts.apache.org/struts2-core/"">http://struts.apache.org/struts2-core/</a></p>
<p>Path to dependency file: ksa/ksa-web-root/ksa-statistics-web/pom.xml</p>
<p>Path to vulnerable library: er/.m2/repository/org/apache/struts/struts2-core/2.3.31/struts2-core-2.3.31.jar,er/.m2/repository/org/apache/struts/struts2-core/2.3.31/struts2-core-2.3.31.jar,er/.m2/repository/org/apache/struts/struts2-core/2.3.31/struts2-core-2.3.31.jar,er/.m2/repository/org/apache/struts/struts2-core/2.3.31/struts2-core-2.3.31.jar,er/.m2/repository/org/apache/struts/struts2-core/2.3.31/struts2-core-2.3.31.jar,er/.m2/repository/org/apache/struts/struts2-core/2.3.31/struts2-core-2.3.31.jar,ksa-web-root/ksa-web/target/ROOT/WEB-INF/lib/struts2-core-2.3.31.jar,er/.m2/repository/org/apache/struts/struts2-core/2.3.31/struts2-core-2.3.31.jar,er/.m2/repository/org/apache/struts/struts2-core/2.3.31/struts2-core-2.3.31.jar</p>
<p>

Dependency Hierarchy:
  - :x: **struts2-core-2.3.31.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
In Apache Struts 2.0.0 through 2.3.33 and 2.5 through 2.5.10.1, using an unintentional expression in a Freemarker tag instead of string literals can lead to a RCE attack.

<p>Publish Date: 2017-09-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-12611>CVE-2017-12611</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://cwiki.apache.org/confluence/display/WW/S2-053"">https://cwiki.apache.org/confluence/display/WW/S2-053</a></p>
<p>Release Date: 2017-09-20</p>
<p>Fix Resolution: org.apache.struts:struts2-core:2.3.34;org.apache.struts:struts2-core:2.5.12</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""org.apache.struts"",""packageName"":""struts2-core"",""packageVersion"":""2.3.31"",""packageFilePaths"":[""/ksa-web-root/ksa-statistics-web/pom.xml"",""/ksa-web-root/ksa-web/pom.xml"",""/ksa-web-root/ksa-logistics-web/pom.xml"",""/ksa-web-root/ksa-system-web/pom.xml"",""/ksa-web-root/ksa-finance-web/pom.xml"",""/ksa-web-root/ksa-security-web/pom.xml"",""/ksa-web-core/pom.xml"",""/ksa-web-root/ksa-bd-web/pom.xml""],""isTransitiveDependency"":false,""dependencyTree"":""org.apache.struts:struts2-core:2.3.31"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""org.apache.struts:struts2-core:2.3.34;org.apache.struts:struts2-core:2.5.12""}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""CVE-2017-12611"",""vulnerabilityDetails"":""In Apache Struts 2.0.0 through 2.3.33 and 2.5 through 2.5.10.1, using an unintentional expression in a Freemarker tag instead of string literals can lead to a RCE attack."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-12611"",""cvss3Severity"":""high"",""cvss3Score"":""9.8"",""cvss3Metrics"":{""A"":""High"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""High"",""UI"":""None"",""AV"":""Network"",""I"":""High""},""extraData"":{}}</REMEDIATE> -->",0,cve      high  detected in   core       jar      cve       high severity vulnerability     vulnerable library      core       jar      apache struts     library home page   a href     path to dependency file  ksa ksa web root ksa statistics web pom xml   path to vulnerable library  er    repository org apache struts   core         core       jar er    repository org apache struts   core         core       jar er    repository org apache struts   core         core       jar er    repository org apache struts   core         core       jar er    repository org apache struts   core         core       jar er    repository org apache struts   core         core       jar ksa web root ksa web target root web inf lib   core       jar er    repository org apache struts   core         core       jar er    repository org apache struts   core         core       jar     dependency hierarchy       x      core       jar    vulnerable library   found in base branch   master              vulnerability details         in apache struts       through       and     through          using an unintentional expression in a freemarker tag instead of string literals can lead to a rce 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  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 struts   core       org apache struts   core                    isopenpronvulnerability  true  ispackagebased  true  isdefaultbranch  true  packages     istransitivedependency  false  dependencytree   org apache struts   core         isminimumfixversionavailable  true  minimumfixversion   org apache struts   core       org apache struts   core           basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   in apache struts       through       and     through          using an unintentional expression in a freemarker tag instead of string literals can lead to a rce attack    vulnerabilityurl        ,0
46223,11800930869.0,IssuesEvent,2020-03-18 18:27:15,GoogleCloudPlatform/python-docs-samples,https://api.github.com/repos/GoogleCloudPlatform/python-docs-samples,opened,dialogflow.cloud-client.delete_knowledge_base_test: test_delete_knowledge_base failed,buildcop: issue priority: p1 type: bug,"This test failed!

To configure my behavior, see [the Build Cop Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/master/packages/buildcop).

If I'm commenting on this issue too often, add the `buildcop: quiet` label and
I will stop commenting.

---

commit: d4014b02717e27b7b15348188395e71d4d9cb786
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/7ddff38d-02c7-4cdb-8899-9f0ae79ada1c), [Sponge](http://sponge2/7ddff38d-02c7-4cdb-8899-9f0ae79ada1c)
status: failed",1.0,"dialogflow.cloud-client.delete_knowledge_base_test: test_delete_knowledge_base failed - This test failed!

To configure my behavior, see [the Build Cop Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/master/packages/buildcop).

If I'm commenting on this issue too often, add the `buildcop: quiet` label and
I will stop commenting.

---

commit: d4014b02717e27b7b15348188395e71d4d9cb786
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/7ddff38d-02c7-4cdb-8899-9f0ae79ada1c), [Sponge](http://sponge2/7ddff38d-02c7-4cdb-8899-9f0ae79ada1c)
status: failed",0,dialogflow cloud client delete knowledge base test  test delete knowledge base failed   this test failed   to configure my behavior  see      if i m commenting on this issue too often  add the  buildcop  quiet  label and i will stop commenting        commit    buildurl          status  failed,0
11703,3516782940.0,IssuesEvent,2016-01-12 01:56:40,golang/go,https://api.github.com/repos/golang/go,closed,doc: $GOPATH is opaque even if you find the doc,Documentation,"Rick and Austin both ran into problems with trying to set up $GOPATH. They both found https://golang.org/doc/code.html but it didn't help either of them. Perhaps the doc should start out more prescriptive and only _then_ move into the description of what a workspace is.

Also, the recipe given uses $HOME/go as $GOPATH, which is just about the worst possible suggestion, because it's where we tell people to check out Go trees in http://golang.org/doc/install/source. This doc should probably use $HOME/work. People will be able to figure out how to generalize to other values of 'work'.

It looks like all the necessary information _is_ in the doc, it's just too hard to find if you're skimming trying to solve a problem. Maybe there should be a short intro that hits the highlights:

(1) mkdir $HOME/work; export GOPATH=$HOME/work; export PATH=$GOPATH/bin:$PATH
(2) Your own work goes in $GOPATH/src/github.com/you/project. Your version control applies to that subdirectory tree, not to all of $GOPATH.

and then the rest of the doc can elaborate.

@adg @aclements @rlh ",1.0,"doc: $GOPATH is opaque even if you find the doc - Rick and Austin both ran into problems with trying to set up $GOPATH. They both found https://golang.org/doc/code.html but it didn't help either of them. Perhaps the doc should start out more prescriptive and only _then_ move into the description of what a workspace is.

Also, the recipe given uses $HOME/go as $GOPATH, which is just about the worst possible suggestion, because it's where we tell people to check out Go trees in http://golang.org/doc/install/source. This doc should probably use $HOME/work. People will be able to figure out how to generalize to other values of 'work'.

It looks like all the necessary information _is_ in the doc, it's just too hard to find if you're skimming trying to solve a problem. Maybe there should be a short intro that hits the highlights:

(1) mkdir $HOME/work; export GOPATH=$HOME/work; export PATH=$GOPATH/bin:$PATH
(2) Your own work goes in $GOPATH/src/github.com/you/project. Your version control applies to that subdirectory tree, not to all of $GOPATH.

and then the rest of the doc can elaborate.

@adg @aclements @rlh ",1,doc   gopath is opaque even if you find the doc   rick and austin both ran into problems with trying to set up  gopath  they both found   but it didn t help either of them  perhaps the doc should start out more prescriptive and only  then  move into the description of what a workspace is     also  the recipe given uses  home go as  gopath  which is just about the worst possible suggestion  because it s where we tell people to check out go trees in   this doc should probably use  home work  people will be able to figure out how to generalize to other values of  work      it looks like all the necessary information  is  in the doc  it s just too hard to find if you re skimming trying to solve a problem  maybe there should be a short intro that hits the highlights         mkdir  home work  export gopath  home work  export path  gopath bin  path      your own work goes in  gopath src github com you project  your version control applies to that subdirectory tree  not to all of  gopath     and then the rest of the doc can elaborate      adg  aclements  rlh ,1
32555,6086436434.0,IssuesEvent,2017-06-18 01:00:11,golang/go,https://api.github.com/repos/golang/go,closed,Website. Documentation,Documentation,"Please clarify the language for Go comments, Git comments in
*Contribution Guide*
https://golang.org/doc/contribute.html

In my point of view, the Go project expected - English language.",1.0,"Website. Documentation - Please clarify the language for Go comments, Git comments in
*Contribution Guide*
https://golang.org/doc/contribute.html

In my point of view, the Go project expected - English language.",1,website  documentation   please clarify the language for go comments  git comments in   contribution guide        in my point of view  the go project expected   english language ,1
269606,28960227407.0,IssuesEvent,2023-05-10 01:25:03,dpteam/RK3188_TABLET,https://api.github.com/repos/dpteam/RK3188_TABLET,reopened,CVE-2013-1792 (Medium) detected in linuxv3.0,Mend: dependency security vulnerability,"## CVE-2013-1792 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxv3.0</b></p></summary>
<p>

<p>Linux kernel source tree</p>
<p>Library home page: <a href=https://github.com/verygreen/linux.git>https://github.com/verygreen/linux.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/dpteam/RK3188_TABLET/commit/0c501f5a0fd72c7b2ac82904235363bd44fd8f9e"">0c501f5a0fd72c7b2ac82904235363bd44fd8f9e</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (3)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/security/keys/process_keys.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/security/keys/process_keys.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/security/keys/process_keys.c</b>
</p>
</details>
<p></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>  
  
Race condition in the install_user_keyrings function in security/keys/process_keys.c in the Linux kernel before 3.8.3 allows local users to cause a denial of service (NULL pointer dereference and system crash) via crafted keyctl system calls that trigger keyring operations in simultaneous threads.

<p>Publish Date: 2013-03-22
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2013-1792>CVE-2013-1792</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.1</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2013-1792"">https://nvd.nist.gov/vuln/detail/CVE-2013-1792</a></p>
<p>Release Date: 2013-03-22</p>
<p>Fix Resolution: 3.8.3</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2013-1792 (Medium) detected in linuxv3.0 - ## CVE-2013-1792 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxv3.0</b></p></summary>
<p>

<p>Linux kernel source tree</p>
<p>Library home page: <a href=https://github.com/verygreen/linux.git>https://github.com/verygreen/linux.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/dpteam/RK3188_TABLET/commit/0c501f5a0fd72c7b2ac82904235363bd44fd8f9e"">0c501f5a0fd72c7b2ac82904235363bd44fd8f9e</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (3)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/security/keys/process_keys.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/security/keys/process_keys.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/security/keys/process_keys.c</b>
</p>
</details>
<p></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>  
  
Race condition in the install_user_keyrings function in security/keys/process_keys.c in the Linux kernel before 3.8.3 allows local users to cause a denial of service (NULL pointer dereference and system crash) via crafted keyctl system calls that trigger keyring operations in simultaneous threads.

<p>Publish Date: 2013-03-22
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2013-1792>CVE-2013-1792</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.1</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2013-1792"">https://nvd.nist.gov/vuln/detail/CVE-2013-1792</a></p>
<p>Release Date: 2013-03-22</p>
<p>Fix Resolution: 3.8.3</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      medium  detected in          cve       medium severity vulnerability     vulnerable library               linux kernel source tree   library home page   a href    found in head commit   a href      found in base branch   master             vulnerable source files                  security keys process keys c        security keys process keys c        security keys process keys c                    vulnerability details         race condition in the install user keyrings function in security keys process keys c in the linux kernel before       allows local users to cause a denial of service  null pointer dereference and system crash  via crafted keyctl system calls that trigger keyring operations in simultaneous threads    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  local     attack complexity  high     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                      step up your open source security game with mend    ,0
330123,24248159560.0,IssuesEvent,2022-09-27 12:19:50,golang/go,https://api.github.com/repos/golang/go,closed,unsafe: document valid uses of `unsafe.Pointer` for non-Go memory,Documentation WaitingForInfo,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14.10 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

N/A

### What operating system and processor architecture are you using (`go env`)?

N/A

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

Read the documentation for `unsafe.Pointer`

### What did you expect to see?

A documented method for accessing memory outside of the garbage-collected heap, such as memory allocated by C’s `malloc`.

### What did you see instead?

No such method.",1.0,"unsafe: document valid uses of `unsafe.Pointer` for non-Go memory - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14.10 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

N/A

### What operating system and processor architecture are you using (`go env`)?

N/A

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

Read the documentation for `unsafe.Pointer`

### What did you expect to see?

A documented method for accessing memory outside of the garbage-collected heap, such as memory allocated by C’s `malloc`.

### What did you see instead?

No such method.",1,unsafe  document valid uses of  unsafe pointer  for non go memory         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version            go version  go version       linux             does this issue reproduce with the latest release     n a        what operating system and processor architecture are you using   go env       n a        what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best          read the documentation for  unsafe pointer         what did you expect to see     a documented method for accessing memory outside of the garbage collected heap  such as memory allocated by c’s  malloc          what did you see instead     no such method ,1
34081,9259632681.0,IssuesEvent,2019-03-18 01:02:32,haskell/haskell-ide-engine,https://api.github.com/repos/haskell/haskell-ide-engine,closed,Purpose of target `dist` in install.hs,build type: discussion type: refactor,"In the PR #1056 it is noted that target `dist` is usually not necessary for installation of HIE, thus, the dependency `zlib` could be removed from install.hs.

Things we could do with `dist`:
* Drop it without replacement
* Leave it unchanged in install.hs
* Extract a build script, potentially written in `shake`

",1.0,"Purpose of target `dist` in install.hs - In the PR #1056 it is noted that target `dist` is usually not necessary for installation of HIE, thus, the dependency `zlib` could be removed from install.hs.

Things we could do with `dist`:
* Drop it without replacement
* Leave it unchanged in install.hs
* Extract a build script, potentially written in `shake`

",0,purpose of target  dist  in install hs   in the pr    it is noted that target  dist  is usually not necessary for installation of hie  thus  the dependency  zlib  could be removed from install hs     things we could do with  dist      drop it without replacement    leave it unchanged in install hs    extract a build script  potentially written in  shake     ,0
26942,12499292458.0,IssuesEvent,2020-06-01 19:53:15,OpenLiberty/open-liberty,https://api.github.com/repos/OpenLiberty/open-liberty,opened,JAX-WS: Add support for new HTTP conduit properties,in:Web Services team:Bobcats,"CXF 3.X added support for an extended list of HTTP Conduit Configuration Properties. Especially, the Connection=""Keep-Alive"" to allow Sockets to be reused across multiple Request/Response cycles. Work should be done to ensure that these new properties are supported in our bindings configuration. See https://cxf.apache.org/docs/client-http-transport-including-ssl-support.html",1.0,"JAX-WS: Add support for new HTTP conduit properties - CXF 3.X added support for an extended list of HTTP Conduit Configuration Properties. Especially, the Connection=""Keep-Alive"" to allow Sockets to be reused across multiple Request/Response cycles. Work should be done to ensure that these new properties are supported in our bindings configuration. See https://cxf.apache.org/docs/client-http-transport-including-ssl-support.html",0,jax ws  add support for new http conduit properties   cxf   x added support for an extended list of http conduit configuration properties  especially  the connection  keep alive  to allow sockets to be reused across multiple request response cycles  work should be done to ensure that these new properties are supported in our bindings configuration  see  ,0
326642,9958719846.0,IssuesEvent,2019-07-05 22:50:02,beelabhmc/ant_tracker,https://api.github.com/repos/beelabhmc/ant_tracker,closed,Compute ingress/egress polygon edges from ant tracks.,priority,"With the automatic polygon detection, ant tracks need to be converted to how the ant entered and exited the polygon RoI.

Which edge corresponds to which label in the code needs to be exported in a human-friendly way. I discussed this with Prof. Donaldson and she said that it would be good to make an output image for each RoI labeling the edges with the labels that the code gives.",1.0,"Compute ingress/egress polygon edges from ant tracks. - With the automatic polygon detection, ant tracks need to be converted to how the ant entered and exited the polygon RoI.

Which edge corresponds to which label in the code needs to be exported in a human-friendly way. I discussed this with Prof. Donaldson and she said that it would be good to make an output image for each RoI labeling the edges with the labels that the code gives.",0,compute ingress egress polygon edges from ant tracks    with the automatic polygon detection  ant tracks need to be converted to how the ant entered and exited the polygon roi     which edge corresponds to which label in the code needs to be exported in a human friendly way  i discussed this with prof  donaldson and she said that it would be good to make an output image for each roi labeling the edges with the labels that the code gives ,0
12083,3039978024.0,IssuesEvent,2015-08-07 12:54:08,algolia/instantsearch.js,https://api.github.com/repos/algolia/instantsearch.js,closed,[Widget proposal]: toggle button ('boolean' facet),api design enhancement low-priority,"I would like to have a widget able to toggle a single facet value.

![2015-08-04-114907_276x214_scrot](https://cloud.githubusercontent.com/assets/123822/9058103/fdab6ad6-3a9e-11e5-8f02-eca110965466.png)

what do you think?",1.0,"[Widget proposal]: toggle button ('boolean' facet) - I would like to have a widget able to toggle a single facet value.

![2015-08-04-114907_276x214_scrot](https://cloud.githubusercontent.com/assets/123822/9058103/fdab6ad6-3a9e-11e5-8f02-eca110965466.png)

what do you think?",0,   toggle button   boolean  facet    i would like to have a widget able to toggle a single facet value             what do you think ,0
184167,14970769893.0,IssuesEvent,2021-01-27 20:06:56,golang/go,https://api.github.com/repos/golang/go,opened,doc/go1.16: document new go/build/constraint package,Documentation NeedsFix help wanted release-blocker,"The new `go/build/constraint` package in Go 1.16 should be documented in the Go 1.16 release notes as part of #40700.

CC @rsc.",1.0,"doc/go1.16: document new go/build/constraint package - The new `go/build/constraint` package in Go 1.16 should be documented in the Go 1.16 release notes as part of #40700.

CC @rsc.",1,doc      document new go build constraint package   the new  go build constraint  package in go     should be documented in the go     release notes as part of        cc  rsc ,1
164517,13956469825.0,IssuesEvent,2020-10-24 01:17:37,golang/go,https://api.github.com/repos/golang/go,closed,crypto/x509: IsEncryptedPEMBlock returns false on valid encrypted keys. ParseRawPrivateKeyWithPassphrase fails on PKCS8 format encrypted key.,Documentation NeedsFix,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.15.2 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
YES

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/harikrishnanbalagopal/Library/Caches/go-build""
GOENV=""/Users/harikrishnanbalagopal/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/harikrishnanbalagopal/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/harikrishnanbalagopal/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/Cellar/go/1.15.2/libexec""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/1.15.2/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/harikrishnanbalagopal/go/src/github.com/konveyor/testkey/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/09/5yjxv27n6njfskvvmkv9v8m40000gn/T/go-build525969776=/tmp/go-build -gno-record-gcc-switches -fno-common""
GOROOT/bin/go version: go version go1.15.2 darwin/amd64
GOROOT/bin/go tool compile -V: compile version go1.15.2
uname -v: Darwin Kernel Version 19.6.0: Thu Jun 18 20:49:00 PDT 2020; root:xnu-6153.141.1~1/RELEASE_X86_64
ProductName:	Mac OS X
ProductVersion:	10.15.6
BuildVersion:	19G2021
lldb --version: lldb-1103.0.22.10
Apple Swift version 5.2.4 (swiftlang-1103.0.32.9 clang-1103.0.32.53)
</pre></details>

### What did you do?
Example with the command to use to generate the keys and the keys themselves:
https://play.golang.org/p/F2nUIO_S6hT

Called `x509.IsEncryptedPEMBlock` on `pem.Block`s created using `pem.Decode`.
`pem.Decode` is called on valid encrypted RSA private keys generated using the following commands:
`ssh-keygen -m PEM -t rsa -b 4096 -C 'foobar@example.com'`
`ssh-keygen -m PKCS8 -t rsa -b 4096 -C 'foobar@example.com'`
`ssh-keygen -m RFC4716 -t rsa -b 4096 -C 'foobar@example.com'`

Also called `ssh.ParseRawPrivateKeyWithPassphrase` on each of those keys.

### What did you expect to see?
The `x509.IsEncryptedPEMBlock` function should report true in all the cases given in the example.
The `ssh.ParseRawPrivateKeyWithPassphrase` should succeed on the `PKCS8` key instead of failing as it does in the example.

Note that `ssh-keygen -yf mykey` is able to detect that the file is a valid encrypted key and decrypt it given the correct password in all the 3 cases. So `IsEncryptedPEMBlock` and `ParseRawPrivateKeyWithPassphrase` should be able to handle them as well.


### What did you see instead?
`x509.IsEncryptedPEMBlock` incorrectly returns false when given the `pem.Block`s of the `PKCS8` and `RFC4716` keys.

`ssh-keygen` lets you specify the format for the key file using the `-m` flag:
https://www.man7.org/linux/man-pages/man1/ssh-keygen.1.html
There are 3 supported formats: `PEM`, `PKCS8` and `RFC4716`. `x509.IsEncryptedPEMBlock` only reports correctly on keys generated using `PEM`. This is because keys generated using `PKCS8` and `RFC4716` no longer have headers that indicate that the data is encrypted and the decryption algorithm to use. `x509.IsEncryptedPEMBlock` checks for those headers in order to determine whether the data is encrypted: https://github.com/golang/go/blob/5b509d993d3a3a212b4033815be8b7b439fac672/src/crypto/x509/pem_decrypt.go#L99-L102

Interestingly the `ssh.ParseRawPrivateKeyWithPassphrase` function fails on `PKCS8` but is able to handle `RFC4716` because of this special case: https://github.com/golang/crypto/blob/master/ssh/keys.go#L1156-L1158

I have tried the example with `go version go1.15.2 darwin/amd64` and the latest `golang.org/x/crypto v0.0.0-20201012173705-84dcc777aaee` on my Macbook Pro `macOS Catalina 10.15.6`
",1.0,"crypto/x509: IsEncryptedPEMBlock returns false on valid encrypted keys. ParseRawPrivateKeyWithPassphrase fails on PKCS8 format encrypted key. - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.15.2 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
YES

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/harikrishnanbalagopal/Library/Caches/go-build""
GOENV=""/Users/harikrishnanbalagopal/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/harikrishnanbalagopal/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/harikrishnanbalagopal/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/Cellar/go/1.15.2/libexec""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/1.15.2/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/harikrishnanbalagopal/go/src/github.com/konveyor/testkey/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/09/5yjxv27n6njfskvvmkv9v8m40000gn/T/go-build525969776=/tmp/go-build -gno-record-gcc-switches -fno-common""
GOROOT/bin/go version: go version go1.15.2 darwin/amd64
GOROOT/bin/go tool compile -V: compile version go1.15.2
uname -v: Darwin Kernel Version 19.6.0: Thu Jun 18 20:49:00 PDT 2020; root:xnu-6153.141.1~1/RELEASE_X86_64
ProductName:	Mac OS X
ProductVersion:	10.15.6
BuildVersion:	19G2021
lldb --version: lldb-1103.0.22.10
Apple Swift version 5.2.4 (swiftlang-1103.0.32.9 clang-1103.0.32.53)
</pre></details>

### What did you do?
Example with the command to use to generate the keys and the keys themselves:
https://play.golang.org/p/F2nUIO_S6hT

Called `x509.IsEncryptedPEMBlock` on `pem.Block`s created using `pem.Decode`.
`pem.Decode` is called on valid encrypted RSA private keys generated using the following commands:
`ssh-keygen -m PEM -t rsa -b 4096 -C 'foobar@example.com'`
`ssh-keygen -m PKCS8 -t rsa -b 4096 -C 'foobar@example.com'`
`ssh-keygen -m RFC4716 -t rsa -b 4096 -C 'foobar@example.com'`

Also called `ssh.ParseRawPrivateKeyWithPassphrase` on each of those keys.

### What did you expect to see?
The `x509.IsEncryptedPEMBlock` function should report true in all the cases given in the example.
The `ssh.ParseRawPrivateKeyWithPassphrase` should succeed on the `PKCS8` key instead of failing as it does in the example.

Note that `ssh-keygen -yf mykey` is able to detect that the file is a valid encrypted key and decrypt it given the correct password in all the 3 cases. So `IsEncryptedPEMBlock` and `ParseRawPrivateKeyWithPassphrase` should be able to handle them as well.


### What did you see instead?
`x509.IsEncryptedPEMBlock` incorrectly returns false when given the `pem.Block`s of the `PKCS8` and `RFC4716` keys.

`ssh-keygen` lets you specify the format for the key file using the `-m` flag:
https://www.man7.org/linux/man-pages/man1/ssh-keygen.1.html
There are 3 supported formats: `PEM`, `PKCS8` and `RFC4716`. `x509.IsEncryptedPEMBlock` only reports correctly on keys generated using `PEM`. This is because keys generated using `PKCS8` and `RFC4716` no longer have headers that indicate that the data is encrypted and the decryption algorithm to use. `x509.IsEncryptedPEMBlock` checks for those headers in order to determine whether the data is encrypted: https://github.com/golang/go/blob/5b509d993d3a3a212b4033815be8b7b439fac672/src/crypto/x509/pem_decrypt.go#L99-L102

Interestingly the `ssh.ParseRawPrivateKeyWithPassphrase` function fails on `PKCS8` but is able to handle `RFC4716` because of this special case: https://github.com/golang/crypto/blob/master/ssh/keys.go#L1156-L1158

I have tried the example with `go version go1.15.2 darwin/amd64` and the latest `golang.org/x/crypto v0.0.0-20201012173705-84dcc777aaee` on my Macbook Pro `macOS Catalina 10.15.6`
",1,crypto    isencryptedpemblock returns false on valid encrypted keys  parserawprivatekeywithpassphrase fails on   format encrypted key             what version of go are you using   go version            go version  go version       darwin             does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   users harikrishnanbalagopal library caches go build   goenv   users harikrishnanbalagopal library application support go env   goexe     goflags     gohostarch      gohostos  darwin   goinsecure     gomodcache   users harikrishnanbalagopal go pkg mod   gonoproxy     gonosumdb     goos  darwin   gopath   users harikrishnanbalagopal go   goprivate     goproxy     goroot   usr local cellar go       libexec   gosumdb  sum golang org   gotmpdir     gotooldir   usr local cellar go       libexec pkg tool darwin     gccgo  gccgo   ar  ar   cc  clang   cxx  clang     cgo enabled      gomod   users harikrishnanbalagopal go src github com konveyor testkey go mod   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders     t go    tmp go build  gno record gcc switches  fno common   goroot bin go version  go version       darwin    goroot bin go tool compile  v  compile version        uname  v  darwin kernel version        thu jun         pdt    root xnu         release      productname 	mac os x  productversion 	       buildversion 	   lldb   version  lldb          apple swift version        swiftlang         clang                     what did you do   example with the command to use to generate the keys and the keys themselves        called    isencryptedpemblock  on  pem block s created using  pem decode     pem decode  is called on valid encrypted rsa private keys generated using the following commands    ssh keygen  m pem  t rsa  b    c  foobar example com     ssh keygen  m    t rsa  b    c  foobar example com     ssh keygen  m    t rsa  b    c  foobar example com      also called  ssh parserawprivatekeywithpassphrase  on each of those keys         what did you expect to see   the    isencryptedpemblock  function should report true in all the cases given in the example   the  ssh parserawprivatekeywithpassphrase  should succeed on the     key instead of failing as it does in the example     note that  ssh keygen  yf mykey  is able to detect that the file is a valid encrypted key and decrypt it given the correct password in all the   cases  so  isencryptedpemblock  and  parserawprivatekeywithpassphrase  should be able to handle them as well           what did you see instead      isencryptedpemblock  incorrectly returns false when given the  pem block s of the     and     keys      ssh keygen  lets you specify the format for the key file using the   m  flag      there are   supported formats   pem       and         isencryptedpemblock  only reports correctly on keys generated using  pem   this is because keys generated using     and     no longer have headers that indicate that the data is encrypted and the decryption algorithm to use     isencryptedpemblock  checks for those headers in order to determine whether the data is encrypted       interestingly the  ssh parserawprivatekeywithpassphrase  function fails on     but is able to handle     because of this special case       i have tried the example with  go version       darwin    and the latest  golang org x crypto            on my macbook pro  macos catalina         ,1
404271,27456528702.0,IssuesEvent,2023-03-02 21:53:12,golang/go,https://api.github.com/repos/golang/go,closed,net: macOS link of Go c-archive now requires -lresolv in 1.20,Documentation OS-Darwin WaitingForInfo NeedsInvestigation,"Go 1.20rc3.

I tried to convert our application (@Tailscale) over to Go 1.20 but hit macOS compilation errors in Xcode for our target (a network extension) that links in Go code:

```
    /Applications/Xcode-13.4.1.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -target arm64-apple-macos10.13 -isysroot /Applications/Xcode-13.4.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk -L/Users/github-ci/Library/Developer/Xcode/DerivedData/IPN-dcmqhkiofztpxzcjkertpymoivvw/Build/Intermediates.noindex/ArchiveIntermediates/IPN-macOS/BuildProductsPath/Release -F/Users/github-ci/Library/Developer/Xcode/DerivedData/IPN-dcmqhkiofztpxzcjkertpymoivvw/Build/Intermediates.noindex/ArchiveIntermediates/IPN-macOS/BuildProductsPath/Release -filelist /Users/github-ci/Library/Developer/Xcode/DerivedData/IPN-dcmqhkiofztpxzcjkertpymoivvw/Build/Intermediates.noindex/ArchiveIntermediates/IPN-macOS/IntermediateBuildFilesPath/IPN.build/Release/IPNExtension-macOS.build/Objects-normal/arm64/IPNExtension.LinkFileList -exported_symbols_list IPNExtension/exported-symbols.exp -Xlinker -rpath -Xlinker /usr/lib/swift -Xlinker -rpath -Xlinker @executable_path/../Frameworks -Xlinker -rpath -Xlinker @executable_path/../../../../Frameworks -dead_strip -Xlinker -object_path_lto -Xlinker /Users/github-ci/Library/Developer/Xcode/DerivedData/IPN-dcmqhkiofztpxzcjkertpymoivvw/Build/Intermediates.noindex/ArchiveIntermediates/IPN-macOS/IntermediateBuildFilesPath/IPN.build/Release/IPNExtension-macOS.build/Objects-normal/arm64/IPNExtension_lto.o -fapplication-extension -fobjc-link-runtime -L/Applications/Xcode-13.4.1.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/macosx -L/usr/lib/swift -Xlinker -add_ast_path -Xlinker /Users/github-ci/Library/Developer/Xcode/DerivedData/IPN-dcmqhkiofztpxzcjkertpymoivvw/Build/Intermediates.noindex/ArchiveIntermediates/IPN-macOS/IntermediateBuildFilesPath/IPN.build/Release/IPNExtension-macOS.build/Objects-normal/arm64/IPNExtension.swiftmodule -e _NSExtensionMain -lipn-go-arm64\ x86_64 -framework NetworkExtension -Xlinker -dependency_info -Xlinker /Users/github-ci/Library/Developer/Xcode/DerivedData/IPN-dcmqhkiofztpxzcjkertpymoivvw/Build/Intermediates.noindex/ArchiveIntermediates/IPN-macOS/IntermediateBuildFilesPath/IPN.build/Release/IPNExtension-macOS.build/Objects-normal/arm64/IPNExtension_dependency_info.dat -o /Users/github-ci/Library/Developer/Xcode/DerivedData/IPN-dcmqhkiofztpxzcjkertpymoivvw/Build/Intermediates.noindex/ArchiveIntermediates/IPN-macOS/IntermediateBuildFilesPath/IPN.build/Release/IPNExtension-macOS.build/Objects-normal/arm64/Binary/IPNExtension
Undefined symbols for architecture arm64:
  ""_res_9_nsearch"", referenced from:
      _internal/syscall/unix.libresolv_res_9_nsearch_trampoline.abi0 in libipn-go-arm64 x86_64.a(go.o)
  ""_res_9_nclose"", referenced from:
      _internal/syscall/unix.libresolv_res_9_nclose_trampoline.abi0 in libipn-go-arm64 x86_64.a(go.o)
  ""_res_9_ninit"", referenced from:
      _internal/syscall/unix.libresolv_res_9_ninit_trampoline.abi0 in libipn-go-arm64 x86_64.a(go.o)
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

...

The following build commands failed:
	Ld /Users/github-ci/Library/Developer/Xcode/DerivedData/IPN-dcmqhkiofztpxzcjkertpymoivvw/Build/Intermediates.noindex/ArchiveIntermediates/IPN-macOS/IntermediateBuildFilesPath/IPN.build/Release/IPNExtension-macOS.build/Objects-normal/arm64/Binary/IPNExtension normal arm64 (in target 'IPNExtension-macOS' from project 'IPN')
```

I assume this is fallout from https://tip.golang.org/doc/go1.20#cgo ...

> On macOS, the net and os/user packages have been rewritten not to use cgo: the same code is now used for cgo and non-cgo builds as well as cross-compiled builds.

Unfortunately I don't have a small easy repro. (Nothing is small or easy with Xcode)

/cc @rsc @ianlancetaylor 

",1.0,"net: macOS link of Go c-archive now requires -lresolv in 1.20 - Go 1.20rc3.

I tried to convert our application (@Tailscale) over to Go 1.20 but hit macOS compilation errors in Xcode for our target (a network extension) that links in Go code:

```
    /Applications/Xcode-13.4.1.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -target arm64-apple-macos10.13 -isysroot /Applications/Xcode-13.4.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk -L/Users/github-ci/Library/Developer/Xcode/DerivedData/IPN-dcmqhkiofztpxzcjkertpymoivvw/Build/Intermediates.noindex/ArchiveIntermediates/IPN-macOS/BuildProductsPath/Release -F/Users/github-ci/Library/Developer/Xcode/DerivedData/IPN-dcmqhkiofztpxzcjkertpymoivvw/Build/Intermediates.noindex/ArchiveIntermediates/IPN-macOS/BuildProductsPath/Release -filelist /Users/github-ci/Library/Developer/Xcode/DerivedData/IPN-dcmqhkiofztpxzcjkertpymoivvw/Build/Intermediates.noindex/ArchiveIntermediates/IPN-macOS/IntermediateBuildFilesPath/IPN.build/Release/IPNExtension-macOS.build/Objects-normal/arm64/IPNExtension.LinkFileList -exported_symbols_list IPNExtension/exported-symbols.exp -Xlinker -rpath -Xlinker /usr/lib/swift -Xlinker -rpath -Xlinker @executable_path/../Frameworks -Xlinker -rpath -Xlinker @executable_path/../../../../Frameworks -dead_strip -Xlinker -object_path_lto -Xlinker /Users/github-ci/Library/Developer/Xcode/DerivedData/IPN-dcmqhkiofztpxzcjkertpymoivvw/Build/Intermediates.noindex/ArchiveIntermediates/IPN-macOS/IntermediateBuildFilesPath/IPN.build/Release/IPNExtension-macOS.build/Objects-normal/arm64/IPNExtension_lto.o -fapplication-extension -fobjc-link-runtime -L/Applications/Xcode-13.4.1.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/macosx -L/usr/lib/swift -Xlinker -add_ast_path -Xlinker /Users/github-ci/Library/Developer/Xcode/DerivedData/IPN-dcmqhkiofztpxzcjkertpymoivvw/Build/Intermediates.noindex/ArchiveIntermediates/IPN-macOS/IntermediateBuildFilesPath/IPN.build/Release/IPNExtension-macOS.build/Objects-normal/arm64/IPNExtension.swiftmodule -e _NSExtensionMain -lipn-go-arm64\ x86_64 -framework NetworkExtension -Xlinker -dependency_info -Xlinker /Users/github-ci/Library/Developer/Xcode/DerivedData/IPN-dcmqhkiofztpxzcjkertpymoivvw/Build/Intermediates.noindex/ArchiveIntermediates/IPN-macOS/IntermediateBuildFilesPath/IPN.build/Release/IPNExtension-macOS.build/Objects-normal/arm64/IPNExtension_dependency_info.dat -o /Users/github-ci/Library/Developer/Xcode/DerivedData/IPN-dcmqhkiofztpxzcjkertpymoivvw/Build/Intermediates.noindex/ArchiveIntermediates/IPN-macOS/IntermediateBuildFilesPath/IPN.build/Release/IPNExtension-macOS.build/Objects-normal/arm64/Binary/IPNExtension
Undefined symbols for architecture arm64:
  ""_res_9_nsearch"", referenced from:
      _internal/syscall/unix.libresolv_res_9_nsearch_trampoline.abi0 in libipn-go-arm64 x86_64.a(go.o)
  ""_res_9_nclose"", referenced from:
      _internal/syscall/unix.libresolv_res_9_nclose_trampoline.abi0 in libipn-go-arm64 x86_64.a(go.o)
  ""_res_9_ninit"", referenced from:
      _internal/syscall/unix.libresolv_res_9_ninit_trampoline.abi0 in libipn-go-arm64 x86_64.a(go.o)
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

...

The following build commands failed:
	Ld /Users/github-ci/Library/Developer/Xcode/DerivedData/IPN-dcmqhkiofztpxzcjkertpymoivvw/Build/Intermediates.noindex/ArchiveIntermediates/IPN-macOS/IntermediateBuildFilesPath/IPN.build/Release/IPNExtension-macOS.build/Objects-normal/arm64/Binary/IPNExtension normal arm64 (in target 'IPNExtension-macOS' from project 'IPN')
```

I assume this is fallout from https://tip.golang.org/doc/go1.20#cgo ...

> On macOS, the net and os/user packages have been rewritten not to use cgo: the same code is now used for cgo and non-cgo builds as well as cross-compiled builds.

Unfortunately I don't have a small easy repro. (Nothing is small or easy with Xcode)

/cc @rsc @ianlancetaylor 

",1,net  macos link of go c archive now requires  lresolv in       go         i tried to convert our application   tailscale  over to go     but hit macos compilation errors in xcode for our target  a network extension  that links in go code               applications xcode       app contents developer toolchains xcodedefault xctoolchain usr bin clang  target   apple      isysroot  applications xcode       app contents developer platforms macosx platform developer sdks     sdk  l users github ci library developer xcode deriveddata ipn dcmqhkiofztpxzcjkertpymoivvw build intermediates noindex archiveintermediates ipn macos buildproductspath release  f users github ci library developer xcode deriveddata ipn dcmqhkiofztpxzcjkertpymoivvw build intermediates noindex archiveintermediates ipn macos buildproductspath release  filelist  users github ci library developer xcode deriveddata ipn dcmqhkiofztpxzcjkertpymoivvw build intermediates noindex archiveintermediates ipn macos intermediatebuildfilespath ipn build release ipnextension macos build objects normal   ipnextension linkfilelist  exported symbols list ipnextension exported symbols exp  xlinker  rpath  xlinker  usr lib swift  xlinker  rpath  xlinker  executable path    frameworks  xlinker  rpath  xlinker  executable path             frameworks  dead strip  xlinker  object path lto  xlinker  users github ci library developer xcode deriveddata ipn dcmqhkiofztpxzcjkertpymoivvw build intermediates noindex archiveintermediates ipn macos intermediatebuildfilespath ipn build release ipnextension macos build objects normal   ipnextension lto o  fapplication extension  fobjc link runtime  l applications xcode       app contents developer toolchains xcodedefault xctoolchain usr lib swift macosx  l usr lib swift  xlinker  add ast path  xlinker  users github ci library developer xcode deriveddata ipn dcmqhkiofztpxzcjkertpymoivvw build intermediates noindex archiveintermediates ipn macos intermediatebuildfilespath ipn build release ipnextension macos build objects normal   ipnextension swiftmodule  e  nsextensionmain  lipn go         framework networkextension  xlinker  dependency info  xlinker  users github ci library developer xcode deriveddata ipn dcmqhkiofztpxzcjkertpymoivvw build intermediates noindex archiveintermediates ipn macos intermediatebuildfilespath ipn build release ipnextension macos build objects normal   ipnextension dependency info dat  o  users github ci library developer xcode deriveddata ipn dcmqhkiofztpxzcjkertpymoivvw build intermediates noindex archiveintermediates ipn macos intermediatebuildfilespath ipn build release ipnextension macos build objects normal   binary ipnextension  undefined symbols for architecture         res   nsearch   referenced from          internal syscall unix libresolv res   nsearch trampoline   in libipn go       a go o       res   nclose   referenced from          internal syscall unix libresolv res   nclose trampoline   in libipn go       a go o       res   ninit   referenced from          internal syscall unix libresolv res   ninit trampoline   in libipn go       a go o   ld  symbol s  not found for architecture    clang  error  linker command failed with exit code    use  v to see invocation            the following build commands failed   	ld  users github ci library developer xcode deriveddata ipn dcmqhkiofztpxzcjkertpymoivvw build intermediates noindex archiveintermediates ipn macos intermediatebuildfilespath ipn build release ipnextension macos build objects normal   binary ipnextension normal    in target  ipnextension macos  from project  ipn           i assume this is fallout from            on macos  the net and os user packages have been rewritten not to use cgo  the same code is now used for cgo and non cgo builds as well as cross compiled builds     unfortunately i don t have a small easy repro   nothing is small or easy with xcode      cc  rsc  ianlancetaylor     ,1
33152,6160113552.0,IssuesEvent,2017-06-29 03:29:53,golang/go,https://api.github.com/repos/golang/go,closed,time: RFC3339Nano does not guarantee natural ordering,Documentation,"Hi!

When the time.Time used in Format(time.RFC3339Nano) is rounded to the nearest second (or anything lower than nanosecond), any trailing 0s are not formatted due to the formatting string.
RFC3339Nano should format to a natural/string sortable value. This is mentioned in section 5.1 of RFC3339 https://www.ietf.org/rfc/rfc3339.txt
```
5.1. Ordering

   If date and time components are ordered from least precise to most
   precise, then a useful property is achieved.  Assuming that the time
   zones of the dates and times are the same (e.g., all in UTC),
   expressed using the same string (e.g., all ""Z"" or all ""+00:00""), and
   all times have the same number of fractional second digits, then the
   date and time strings may be sorted as strings (e.g., using the
   strcmp() function in C) and a time-ordered sequence will result.  The
   presence of optional punctuation would violate this characteristic. 
```
I propose that time.RFC3339Nano is updated to the following formatting string:

`""2006-01-02T15:04:05.000000000Z07:00""`

or that a time.RFC3339NanoNatural (or similar) constant is declared

thanks for your time!

### What version of Go are you using (`go version`)?
go version go1.8 darwin/amd64


### What operating system and processor architecture are you using (`go env`)?
```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/alex/dev/go""
GORACE=""""
GOROOT=""/usr/local/go""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/l5/x43qw4sd10j_459gxsy9h3j80000gn/T/go-build164235018=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
PKG_CONFIG=""pkg-config""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
```

### What did you do?
I formatted two time.Time values using RFC3339Nano
https://play.golang.org/p/qY81JM6Np8

### What did you expect to see?
```
Hello, playground
2009-11-10T23:00:00.00000000Z
2009-11-10T23:00:00.00000001Z
```
### What did you see instead?

```
Hello, playground
2009-11-10T23:00:00Z
2009-11-10T23:00:00.00000001Z
```



",1.0,"time: RFC3339Nano does not guarantee natural ordering - Hi!

When the time.Time used in Format(time.RFC3339Nano) is rounded to the nearest second (or anything lower than nanosecond), any trailing 0s are not formatted due to the formatting string.
RFC3339Nano should format to a natural/string sortable value. This is mentioned in section 5.1 of RFC3339 https://www.ietf.org/rfc/rfc3339.txt
```
5.1. Ordering

   If date and time components are ordered from least precise to most
   precise, then a useful property is achieved.  Assuming that the time
   zones of the dates and times are the same (e.g., all in UTC),
   expressed using the same string (e.g., all ""Z"" or all ""+00:00""), and
   all times have the same number of fractional second digits, then the
   date and time strings may be sorted as strings (e.g., using the
   strcmp() function in C) and a time-ordered sequence will result.  The
   presence of optional punctuation would violate this characteristic. 
```
I propose that time.RFC3339Nano is updated to the following formatting string:

`""2006-01-02T15:04:05.000000000Z07:00""`

or that a time.RFC3339NanoNatural (or similar) constant is declared

thanks for your time!

### What version of Go are you using (`go version`)?
go version go1.8 darwin/amd64


### What operating system and processor architecture are you using (`go env`)?
```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/alex/dev/go""
GORACE=""""
GOROOT=""/usr/local/go""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/l5/x43qw4sd10j_459gxsy9h3j80000gn/T/go-build164235018=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
PKG_CONFIG=""pkg-config""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
```

### What did you do?
I formatted two time.Time values using RFC3339Nano
https://play.golang.org/p/qY81JM6Np8

### What did you expect to see?
```
Hello, playground
2009-11-10T23:00:00.00000000Z
2009-11-10T23:00:00.00000001Z
```
### What did you see instead?

```
Hello, playground
2009-11-10T23:00:00Z
2009-11-10T23:00:00.00000001Z
```



",1,time    does not guarantee natural ordering   hi     when the time time used in format time    is rounded to the nearest second  or anything lower than nanosecond   any trailing   are not formatted due to the formatting string     should format to a natural string sortable value  this is mentioned in section     of                ordering       if date and time components are ordered from least precise to most     precise  then a useful property is achieved   assuming that the time     zones of the dates and times are the same  e g   all in utc       expressed using the same string  e g   all  z  or all          and     all times have the same number of fractional second digits  then the     date and time strings may be sorted as strings  e g   using the     strcmp   function in c  and a time ordered sequence will result   the     presence of optional punctuation would violate this characteristic         i propose that time   is updated to the following formatting string                          or that a time    or similar  constant is declared    thanks for your time         what version of go are you using   go version     go version     darwin            what operating system and processor architecture are you using   go env          goarch      gobin     goexe     gohostarch      gohostos  darwin   goos  darwin   gopath   users alex dev go   gorace     goroot   usr local go   gotooldir   usr local go pkg tool darwin     gccgo  gccgo   cc  clang   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders       t go    tmp go build  gno record gcc switches  fno common   cxx  clang     cgo enabled      pkg config  pkg config   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g                 what did you do   i formatted two time time values using             what did you expect to see        hello  playground                                     what did you see instead          hello  playground                                     ,1
173129,14403475534.0,IssuesEvent,2020-12-03 16:06:08,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.16: document flag changes for Go 1.16,Documentation NeedsInvestigation help wanted release-blocker,"As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

<dl id=""flag""><dt><a href=""/pkg/flag/"">flag</a></dt>
  <dd>
    <p><!-- CL 240014 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/240014"">https://golang.org/cl/240014</a>: add Func
    </p>
  </dd>
</dl><!-- flag -->

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.",1.0,"doc/go1.16: document flag changes for Go 1.16 - As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

<dl id=""flag""><dt><a href=""/pkg/flag/"">flag</a></dt>
  <dd>
    <p><!-- CL 240014 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/240014"">https://golang.org/cl/240014</a>: add Func
    </p>
  </dd>
</dl><!-- flag -->

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.",1,doc      document flag changes for go       as of filing this issue  the     contained the following html        flag                        todo    a href    add func                           per     it s a release blocker for go     beta   to have a complete draft of the eventual release notes  and so the todo needs to be resolved     a sequence of steps to resolve this issue may be        come up with a draft release note entry in this issue  then move the issue to needsfix state      send a cl with  doc           and include  for     fixes   this issue    in the body ,1
31506,7374527370.0,IssuesEvent,2018-03-13 20:38:37,Microsoft/PTVS,https://api.github.com/repos/Microsoft/PTVS,closed,Stack overflow resolving lazy module import,area:Code Intelligence bug priority:P0 tenet:Reliability,"We've seen some crash reports containing unbounded recursion on the following trace:

```
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Default.CPythonInterpreter.LoadModuleFromDirectory
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Default.CPythonInterpreter.ImportModule
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstNestedPythonModule.GetModule
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstNestedPythonModule.GetMember
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.NameLookupContext.GetValueFromExpression
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.NameLookupContext.GetValueFromExpression
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstAnalysisFunctionWalker.GetMethodType
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstAnalysisFunctionWalker.Walk
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstAnalysisWalker.PostWalk
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Parsing.Ast.PythonAst.Walk
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstPythonModule..ctor
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstPythonModule.FromStream
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstPythonModule.FromFile
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Default.CPythonInterpreter.LoadModuleFromDirectory
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Default.CPythonInterpreter.ImportModule
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstNestedPythonModule.GetModule
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstNestedPythonModule.GetMember
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.NameLookupContext.GetValueFromExpression
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.NameLookupContext.GetValueFromExpression
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstAnalysisFunctionWalker.GetMethodType
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstAnalysisFunctionWalker.Walk
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstAnalysisWalker.PostWalk
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Parsing.Ast.PythonAst.Walk
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstPythonModule..ctor
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstPythonModule.FromStream
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstPythonModule.FromFile
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Default.CPythonInterpreter.LoadModuleFromDirectory
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Default.CPythonInterpreter.ImportModule
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstNestedPythonModule.GetModule
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstNestedPythonModule.GetMember
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.NameLookupContext.GetValueFromExpression
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.NameLookupContext.GetValueFromExpression
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstAnalysisFunctionWalker.GetMethodType
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstAnalysisFunctionWalker.Walk
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstAnalysisWalker.PostWalk
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Parsing.Ast.PythonAst.Walk
```

At a guess, we aren't correctly protecting against lazily importing our own module. But this may also be a long chain of imports that we have no way to protect against.",1.0,"Stack overflow resolving lazy module import - We've seen some crash reports containing unbounded recursion on the following trace:

```
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Default.CPythonInterpreter.LoadModuleFromDirectory
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Default.CPythonInterpreter.ImportModule
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstNestedPythonModule.GetModule
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstNestedPythonModule.GetMember
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.NameLookupContext.GetValueFromExpression
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.NameLookupContext.GetValueFromExpression
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstAnalysisFunctionWalker.GetMethodType
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstAnalysisFunctionWalker.Walk
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstAnalysisWalker.PostWalk
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Parsing.Ast.PythonAst.Walk
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstPythonModule..ctor
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstPythonModule.FromStream
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstPythonModule.FromFile
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Default.CPythonInterpreter.LoadModuleFromDirectory
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Default.CPythonInterpreter.ImportModule
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstNestedPythonModule.GetModule
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstNestedPythonModule.GetMember
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.NameLookupContext.GetValueFromExpression
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.NameLookupContext.GetValueFromExpression
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstAnalysisFunctionWalker.GetMethodType
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstAnalysisFunctionWalker.Walk
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstAnalysisWalker.PostWalk
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Parsing.Ast.PythonAst.Walk
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstPythonModule..ctor
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstPythonModule.FromStream
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstPythonModule.FromFile
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Default.CPythonInterpreter.LoadModuleFromDirectory
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Default.CPythonInterpreter.ImportModule
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstNestedPythonModule.GetModule
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstNestedPythonModule.GetMember
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.NameLookupContext.GetValueFromExpression
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.NameLookupContext.GetValueFromExpression
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstAnalysisFunctionWalker.GetMethodType
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstAnalysisFunctionWalker.Walk
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Interpreter.Ast.AstAnalysisWalker.PostWalk
Microsoft_PythonTools_Analysis!Microsoft.PythonTools.Parsing.Ast.PythonAst.Walk
```

At a guess, we aren't correctly protecting against lazily importing our own module. But this may also be a long chain of imports that we have no way to protect against.",0,stack overflow resolving lazy module import   we ve seen some crash reports containing unbounded recursion on the following trace          microsoft pythontools analysis microsoft pythontools interpreter default cpythoninterpreter loadmodulefromdirectory  microsoft pythontools analysis microsoft pythontools interpreter default cpythoninterpreter importmodule  microsoft pythontools analysis microsoft pythontools interpreter ast astnestedpythonmodule getmodule  microsoft pythontools analysis microsoft pythontools interpreter ast astnestedpythonmodule getmember  microsoft pythontools analysis microsoft pythontools interpreter ast namelookupcontext getvaluefromexpression  microsoft pythontools analysis microsoft pythontools interpreter ast namelookupcontext getvaluefromexpression  microsoft pythontools analysis microsoft pythontools interpreter ast astanalysisfunctionwalker getmethodtype  microsoft pythontools analysis microsoft pythontools interpreter ast astanalysisfunctionwalker walk  microsoft pythontools analysis microsoft pythontools interpreter ast astanalysiswalker postwalk  microsoft pythontools analysis microsoft pythontools parsing ast pythonast walk  microsoft pythontools analysis microsoft pythontools interpreter ast astpythonmodule  ctor  microsoft pythontools analysis microsoft pythontools interpreter ast astpythonmodule fromstream  microsoft pythontools analysis microsoft pythontools interpreter ast astpythonmodule fromfile  microsoft pythontools analysis microsoft pythontools interpreter default cpythoninterpreter loadmodulefromdirectory  microsoft pythontools analysis microsoft pythontools interpreter default cpythoninterpreter importmodule  microsoft pythontools analysis microsoft pythontools interpreter ast astnestedpythonmodule getmodule  microsoft pythontools analysis microsoft pythontools interpreter ast astnestedpythonmodule getmember  microsoft pythontools analysis microsoft pythontools interpreter ast namelookupcontext getvaluefromexpression  microsoft pythontools analysis microsoft pythontools interpreter ast namelookupcontext getvaluefromexpression  microsoft pythontools analysis microsoft pythontools interpreter ast astanalysisfunctionwalker getmethodtype  microsoft pythontools analysis microsoft pythontools interpreter ast astanalysisfunctionwalker walk  microsoft pythontools analysis microsoft pythontools interpreter ast astanalysiswalker postwalk  microsoft pythontools analysis microsoft pythontools parsing ast pythonast walk  microsoft pythontools analysis microsoft pythontools interpreter ast astpythonmodule  ctor  microsoft pythontools analysis microsoft pythontools interpreter ast astpythonmodule fromstream  microsoft pythontools analysis microsoft pythontools interpreter ast astpythonmodule fromfile  microsoft pythontools analysis microsoft pythontools interpreter default cpythoninterpreter loadmodulefromdirectory  microsoft pythontools analysis microsoft pythontools interpreter default cpythoninterpreter importmodule  microsoft pythontools analysis microsoft pythontools interpreter ast astnestedpythonmodule getmodule  microsoft pythontools analysis microsoft pythontools interpreter ast astnestedpythonmodule getmember  microsoft pythontools analysis microsoft pythontools interpreter ast namelookupcontext getvaluefromexpression  microsoft pythontools analysis microsoft pythontools interpreter ast namelookupcontext getvaluefromexpression  microsoft pythontools analysis microsoft pythontools interpreter ast astanalysisfunctionwalker getmethodtype  microsoft pythontools analysis microsoft pythontools interpreter ast astanalysisfunctionwalker walk  microsoft pythontools analysis microsoft pythontools interpreter ast astanalysiswalker postwalk  microsoft pythontools analysis microsoft pythontools parsing ast pythonast walk         at a guess  we aren t correctly protecting against lazily importing our own module  but this may also be a long chain of imports that we have no way to protect against ,0
11592,3508074157.0,IssuesEvent,2016-01-08 16:15:47,golang/go,https://api.github.com/repos/golang/go,closed,encoding/json: add note in  src/encoding/json/decode.go about exporting struct members,Documentation,"file src/encoding/json/decode.go 
around the struct docs for the Unmarshall object (around line 39)
// NOTE: you most likely want to ""export"" your struct fields, to do that, make
//        sure the field name starts with an Uppercase character. 
//        see http://golang.org/ref/spec#Exported_identifiers for more information.

this is basically a drive-by ""patch"", to make the documentation more sane for go idiots having to wack on some broken code somwhere (i.e. me the go idiot wasting hours digging thru json.Unmarshal because I didn't know I had to ""export"" my struct.  I want other people to not have to waste as much time.",1.0,"encoding/json: add note in  src/encoding/json/decode.go about exporting struct members - file src/encoding/json/decode.go 
around the struct docs for the Unmarshall object (around line 39)
// NOTE: you most likely want to ""export"" your struct fields, to do that, make
//        sure the field name starts with an Uppercase character. 
//        see http://golang.org/ref/spec#Exported_identifiers for more information.

this is basically a drive-by ""patch"", to make the documentation more sane for go idiots having to wack on some broken code somwhere (i.e. me the go idiot wasting hours digging thru json.Unmarshal because I didn't know I had to ""export"" my struct.  I want other people to not have to waste as much time.",1,encoding json  add note in  src encoding json decode go about exporting struct members   file src encoding json decode go   around the struct docs for the unmarshall object  around line        note  you most likely want to  export  your struct fields  to do that  make            sure the field name starts with an uppercase character              see   for more information     this is basically a drive by  patch   to make the documentation more sane for go idiots having to wack on some broken code somwhere  i e  me the go idiot wasting hours digging thru json unmarshal because i didn t know i had to  export  my struct   i want other people to not have to waste as much time ,1
45735,11727016852.0,IssuesEvent,2020-03-10 15:20:25,VOREStation/VOREStation,https://api.github.com/repos/VOREStation/VOREStation,closed,Secondary Command Powernet is not connected to Main,Status: Works in latest build,"#### Brief description of the bug
The Secondary Command powernet wiring is such that none of the APCs are connected to the main powernet at roundstart.

#### What you expected to happen
Secondary Command's powernet is connected to main, and so charges from the main powernet as all other station APCs do.

#### What actually happened
The APCs aren't connected to the powernet (though are mostly connected to each other), so none of the APCs in secondary command charge.

#### Steps to reproduce
N/A

#### Code Revision
58026a3b27d82f3ab4049a4f9295a9abbec89975 
 
#### Anything else you may wish to add:
Location: Secondary Command.
Secondary Command Office APC isn't connected to the other APCs in Secondary Command, but the other APCs are connected to each other. It can be fixed in-game by wiring from the Central Hallway into Secondary Command, and connecting the Office APC to the grid and the grid to the other APCs.
",1.0,"Secondary Command Powernet is not connected to Main - #### Brief description of the bug
The Secondary Command powernet wiring is such that none of the APCs are connected to the main powernet at roundstart.

#### What you expected to happen
Secondary Command's powernet is connected to main, and so charges from the main powernet as all other station APCs do.

#### What actually happened
The APCs aren't connected to the powernet (though are mostly connected to each other), so none of the APCs in secondary command charge.

#### Steps to reproduce
N/A

#### Code Revision
58026a3b27d82f3ab4049a4f9295a9abbec89975 
 
#### Anything else you may wish to add:
Location: Secondary Command.
Secondary Command Office APC isn't connected to the other APCs in Secondary Command, but the other APCs are connected to each other. It can be fixed in-game by wiring from the Central Hallway into Secondary Command, and connecting the Office APC to the grid and the grid to the other APCs.
",0,secondary command powernet is not connected to main        brief description of the bug  the secondary command powernet wiring is such that none of the apcs are connected to the main powernet at roundstart          what you expected to happen  secondary command s powernet is connected to main  and so charges from the main powernet as all other station apcs do          what actually happened  the apcs aren t connected to the powernet  though are mostly connected to each other   so none of the apcs in secondary command charge          steps to reproduce  n a         code revision              anything else you may wish to add   location  secondary command   secondary command office apc isn t connected to the other apcs in secondary command  but the other apcs are connected to each other  it can be fixed in game by wiring from the central hallway into secondary command  and connecting the office apc to the grid and the grid to the other apcs   ,0
397999,11736573602.0,IssuesEvent,2020-03-11 13:18:51,Badgie/spotirec,https://api.github.com/repos/Badgie/spotirec,closed,Catch KeyboardInterrupt exceptions gracefully,bug priority: medium,"When prompting for custom input a `ctrl + c` will print a stacktrace from the line of the input function call.

```
user@thinktop ~> spotirec -gc
OAuth token is expired, refreshing...
Did not receive new refresh token, saving old
0: hip-hop                                 1: pop                                     2: disco
3: soul                                    4: indie-pop                               5: rock
6: electro                                 7: edm
Enter integer identifiers for 1-5 whitespace separated selections that you wish to include [default: top 5]:
^CTraceback (most recent call last):
  File ""/usr/bin/spotirec"", line 727, in <module>
    parse()
  File ""/usr/bin/spotirec"", line 694, in parse
    print_choices(data=get_user_top_genres(), sort=True)
  File ""/usr/bin/spotirec"", line 194, in print_choices
    input_string = input('Enter integer identifiers for 1-5 whitespace separated selections that you wish to '
KeyboardInterrupt
```

Catching this exception and simply exiting with a non-zero should suffice.",1.0,"Catch KeyboardInterrupt exceptions gracefully - When prompting for custom input a `ctrl + c` will print a stacktrace from the line of the input function call.

```
user@thinktop ~> spotirec -gc
OAuth token is expired, refreshing...
Did not receive new refresh token, saving old
0: hip-hop                                 1: pop                                     2: disco
3: soul                                    4: indie-pop                               5: rock
6: electro                                 7: edm
Enter integer identifiers for 1-5 whitespace separated selections that you wish to include [default: top 5]:
^CTraceback (most recent call last):
  File ""/usr/bin/spotirec"", line 727, in <module>
    parse()
  File ""/usr/bin/spotirec"", line 694, in parse
    print_choices(data=get_user_top_genres(), sort=True)
  File ""/usr/bin/spotirec"", line 194, in print_choices
    input_string = input('Enter integer identifiers for 1-5 whitespace separated selections that you wish to '
KeyboardInterrupt
```

Catching this exception and simply exiting with a non-zero should suffice.",0,catch keyboardinterrupt exceptions gracefully   when prompting for custom input a  ctrl   c  will print a stacktrace from the line of the input function call          user thinktop    spotirec  gc  oauth token is expired  refreshing     did not receive new refresh token  saving old     hip hop                                    pop                                        disco     soul                                       indie pop                                  rock     electro                                    edm  enter integer identifiers for     whitespace separated selections that you wish to include      ctraceback  most recent call last      file   usr bin spotirec   line    in        parse      file   usr bin spotirec   line    in parse      print choices data get user top genres    sort true     file   usr bin spotirec   line    in print choices      input string   input  enter integer identifiers for     whitespace separated selections that you wish to    keyboardinterrupt         catching this exception and simply exiting with a non zero should suffice ,0
9921,3337752428.0,IssuesEvent,2015-11-13 01:09:19,golang/go,https://api.github.com/repos/golang/go,closed,os: mention ErrInvalid for nil receivers,Documentation,"Methods on `*os.File` return `ErrInvalid` when the receiver is nil. This is, however, not documented anywhere. Usually this would be fine, if it weren't for a lot of documentation on methods saying `If there is an error, it will be of type *PathError`. 

Operating on nil `*os.File`s is a programming mistake and shouldn't be a common occurence, so it shouldn't complicate all of the documentation. However, a note in the package-level documentation could be an easy fix for a small inaccuracy in the rest of the documentation.",1.0,"os: mention ErrInvalid for nil receivers - Methods on `*os.File` return `ErrInvalid` when the receiver is nil. This is, however, not documented anywhere. Usually this would be fine, if it weren't for a lot of documentation on methods saying `If there is an error, it will be of type *PathError`. 

Operating on nil `*os.File`s is a programming mistake and shouldn't be a common occurence, so it shouldn't complicate all of the documentation. However, a note in the package-level documentation could be an easy fix for a small inaccuracy in the rest of the documentation.",1,os  mention errinvalid for nil receivers   methods on   os file  return  errinvalid  when the receiver is nil  this is  however  not documented anywhere  usually this would be fine  if it weren t for a lot of documentation on methods saying  if there is an error  it will be of type  patherror       operating on nil   os file s is a programming mistake and shouldn t be a common occurence  so it shouldn t complicate all of the documentation  however  a note in the package level documentation could be an easy fix for a small inaccuracy in the rest of the documentation ,1
548442,16064538451.0,IssuesEvent,2021-04-23 16:57:16,googleapis/google-auth-library-nodejs,https://api.github.com/repos/googleapis/google-auth-library-nodejs,closed,err.code type changes from 'string' to 'number'.,priority: p2 type: bug,"Thanks for stopping by to let us know something could be better!

**PLEASE READ**: If you have a support contract with Google, please create an issue in the [support console](https://cloud.google.com/support/) instead of filing on GitHub. This will ensure a timely response.

1) Is this a client library issue or a product issue?
This is the client library for . We will only be able to assist with issues that pertain to the behaviors of this library. If the issue you're experiencing is due to the behavior of the product itself, please visit the [ Support page]() to reach the most relevant engineers.

2) Did someone already solve this?
  - Search the issues already opened: https://github.com/googleapis/google-auth-library-nodejs/issues
  - Search the issues on our ""catch-all"" repository: https://github.com/googleapis/google-cloud-node
  - Search or ask on StackOverflow (engineers monitor these tags): http://stackoverflow.com/questions/tagged/google-cloud-platform+node.js

3) Do you have a support contract?
Please create an issue in the [support console](https://cloud.google.com/support/) to ensure a timely response.

If the support paths suggested above still do not result in a resolution, please provide the following details.

#### Environment details

  - OS: Windows 10.0.18362
  - Node.js version: 12.13.0
  - npm version: 6.12.0
  - `google-auth-library` version: 6.1.1.

#### Steps to reproduce

  1. Call google.classroom(""v1"").courses.list(), or any related API (courses.teacher, courses.student, etc.)
  2. Keep calling until a quota threshold is reached (should get a 429 error code).
  3. Look at the typeof the error.code returned.  It will be a 'number', but should be a 'string'.

Looks like 
   err.code = body.error.code; 
around line 95 in processError() in transporters.js needs to ensure the assigned value is a string.

Line 112 handles this by calling toString().  Might be other lines that need to ensure the code field is a string type.

Making sure to follow these steps will guarantee the quickest resolution possible.

Thanks!
",1.0,"err.code type changes from 'string' to 'number'. - Thanks for stopping by to let us know something could be better!

**PLEASE READ**: If you have a support contract with Google, please create an issue in the [support console](https://cloud.google.com/support/) instead of filing on GitHub. This will ensure a timely response.

1) Is this a client library issue or a product issue?
This is the client library for . We will only be able to assist with issues that pertain to the behaviors of this library. If the issue you're experiencing is due to the behavior of the product itself, please visit the [ Support page]() to reach the most relevant engineers.

2) Did someone already solve this?
  - Search the issues already opened: https://github.com/googleapis/google-auth-library-nodejs/issues
  - Search the issues on our ""catch-all"" repository: https://github.com/googleapis/google-cloud-node
  - Search or ask on StackOverflow (engineers monitor these tags): http://stackoverflow.com/questions/tagged/google-cloud-platform+node.js

3) Do you have a support contract?
Please create an issue in the [support console](https://cloud.google.com/support/) to ensure a timely response.

If the support paths suggested above still do not result in a resolution, please provide the following details.

#### Environment details

  - OS: Windows 10.0.18362
  - Node.js version: 12.13.0
  - npm version: 6.12.0
  - `google-auth-library` version: 6.1.1.

#### Steps to reproduce

  1. Call google.classroom(""v1"").courses.list(), or any related API (courses.teacher, courses.student, etc.)
  2. Keep calling until a quota threshold is reached (should get a 429 error code).
  3. Look at the typeof the error.code returned.  It will be a 'number', but should be a 'string'.

Looks like 
   err.code = body.error.code; 
around line 95 in processError() in transporters.js needs to ensure the assigned value is a string.

Line 112 handles this by calling toString().  Might be other lines that need to ensure the code field is a string type.

Making sure to follow these steps will guarantee the quickest resolution possible.

Thanks!
",0,err code type changes from  string  to  number     thanks for stopping by to let us know something could be better       please read    if you have a support contract with google  please create an issue in the     instead of filing on github  this will ensure a timely response        is this a client library issue or a product issue   this is the client library for   we will only be able to assist with issues that pertain to the behaviors of this library  if the issue you re experiencing is due to the behavior of the product itself  please visit the     to reach the most relevant engineers        did someone already solve this       search the issues already opened         search the issues on our  catch all  repository         search or ask on stackoverflow  engineers monitor these tags           do you have a support contract   please create an issue in the     to ensure a timely response     if the support paths suggested above still do not result in a resolution  please provide the following details          environment details        os  windows            node js version             npm version              google auth library  version                 steps to reproduce         call google classroom      courses list    or any related api  courses teacher  courses student  etc         keep calling until a quota threshold is reached  should get a   error code         look at the typeof the error code returned   it will be a  number   but should be a  string      looks like      err code   body error code    around line   in processerror   in transporters js needs to ensure the assigned value is a string     line   handles this by calling tostring     might be other lines that need to ensure the code field is a string type     making sure to follow these steps will guarantee the quickest resolution possible     thanks   ,0
96154,12100601521.0,IssuesEvent,2020-04-20 14:02:19,carbon-design-system/ibm-dotcom-library-website,https://api.github.com/repos/carbon-design-system/ibm-dotcom-library-website,closed,Cupcake website footer content needs updates,Airtable Done content design website: cupcake,"@wonilsuhibm commented on [Mon Apr 06 2020](https://github.com/carbon-design-system/ibm-dotcom-library/issues/1974)

### User story
As a maker of IBM.com, I need to understand when to use the short version so that I don't misuse it.

### notes
- Currently the footer page states that the short version is available when the screen real estate is limited. This is incorrect. The language should be that the short version is only available to pre-approved transactional pages such as check-out and registration. All other pages should use the default version.

### Acceptance criteria
- [ ] The language on the page has been updated.

---

@wonilsuhibm commented on [Mon Apr 06 2020](https://github.com/carbon-design-system/ibm-dotcom-library/issues/1974#issuecomment-609942329)

There seem to be two Box notes, neither of which reflect the desired guidelines. As a part of this exercise, please archive as needed, and leave one master doc in [this folder](https://ibm.box.com/s/ks8juuduyzxf67nqrpxmpqy81fi0nsqp)

---

@wonilsuhibm commented on [Mon Apr 06 2020](https://github.com/carbon-design-system/ibm-dotcom-library/issues/1974#issuecomment-609953557)

Here is a content update proposal from a while ago—this seems to have some of the correct information. Let's take this into consideration in the final update.

https://github.com/carbon-design-system/ibm-dotcom-library-website/issues/108#issuecomment-565157179

",1.0,"Cupcake website footer content needs updates - @wonilsuhibm commented on [Mon Apr 06 2020](https://github.com/carbon-design-system/ibm-dotcom-library/issues/1974)

### User story
As a maker of IBM.com, I need to understand when to use the short version so that I don't misuse it.

### notes
- Currently the footer page states that the short version is available when the screen real estate is limited. This is incorrect. The language should be that the short version is only available to pre-approved transactional pages such as check-out and registration. All other pages should use the default version.

### Acceptance criteria
- [ ] The language on the page has been updated.

---

@wonilsuhibm commented on [Mon Apr 06 2020](https://github.com/carbon-design-system/ibm-dotcom-library/issues/1974#issuecomment-609942329)

There seem to be two Box notes, neither of which reflect the desired guidelines. As a part of this exercise, please archive as needed, and leave one master doc in [this folder](https://ibm.box.com/s/ks8juuduyzxf67nqrpxmpqy81fi0nsqp)

---

@wonilsuhibm commented on [Mon Apr 06 2020](https://github.com/carbon-design-system/ibm-dotcom-library/issues/1974#issuecomment-609953557)

Here is a content update proposal from a while ago—this seems to have some of the correct information. Let's take this into consideration in the final update.

https://github.com/carbon-design-system/ibm-dotcom-library-website/issues/108#issuecomment-565157179

",0,cupcake website footer content needs updates    wonilsuhibm commented on          user story as a maker of ibm com  i need to understand when to use the short version so that i don t misuse it       notes   currently the footer page states that the short version is available when the screen real estate is limited  this is incorrect  the language should be that the short version is only available to pre approved transactional pages such as check out and registration  all other pages should use the default version       acceptance criteria     the language on the page has been updated         wonilsuhibm commented on      there seem to be two box notes  neither of which reflect the desired guidelines  as a part of this exercise  please archive as needed  and leave one master doc in            wonilsuhibm commented on      here is a content update proposal from a while ago—this seems to have some of the correct information  let s take this into consideration in the final update        ,0
312924,23448034054.0,IssuesEvent,2022-08-15 21:55:16,golang/go,https://api.github.com/repos/golang/go,closed,net/http: clarify use-cases of WithContext vs Clone on requests,Documentation NeedsInvestigation,"The `http.Request` struct had a `Clone` method added in go 1.13, prompted by this issue: https://github.com/golang/go/issues/23544. At that time, I believe the documentation for `WithContext` was updated to suggest that most uses of that method could be replaced with `Clone`.

However, that issue also had this follow-up exchange: https://github.com/golang/go/issues/23544#issuecomment-564336662

> @bradfitz I just came across Clone as a first time user of contexts within net/http. I had a question about this bit of documentation on WithContext:
>
> > ...To change the context of a request (such as an incoming) you then also want to modify to send back out, use Request.Clone. Between those two uses, it's rare to need WithContext.
>
> I wanted to ask if Clone should be preferred over WithContext in all situations. Specifically I'm writing a server middleware and only need to annotate a request (adding a logged in user) so it can be used by other handlers.
>
> Is WithContext not appropriate for this situation?

And @bradfitz responded:

> WithContext works there.

And this has come up occasionally in Slack as well, with people writing very simple middleware that wrap `http.Handler` and just stick a value into the context on the request using `WithContext`. An extremely simple version, for which `Clone` seems like overkill, might be:

```
func WithRequestId(base http.Handler) http.Handler {
   return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
      ctx := context.WithValue(r.Context(), ""request_id"", uuid.NewString())
      base.ServeHTTP(w, r.WithContext(ctx))
   })
}
```

So this issue is mostly asking: is this usage of `WithContext` in this sort of middleware context _correct_, and furthermore can we augment the `WithContext` documentation block to be less prescriptive that `Clone` is the obvious way to go, and that there are plenty of value use-cases for `WithContext`, especially when you're not looking to ""reuse"" the request to make a subsequent request?",1.0,"net/http: clarify use-cases of WithContext vs Clone on requests - The `http.Request` struct had a `Clone` method added in go 1.13, prompted by this issue: https://github.com/golang/go/issues/23544. At that time, I believe the documentation for `WithContext` was updated to suggest that most uses of that method could be replaced with `Clone`.

However, that issue also had this follow-up exchange: https://github.com/golang/go/issues/23544#issuecomment-564336662

> @bradfitz I just came across Clone as a first time user of contexts within net/http. I had a question about this bit of documentation on WithContext:
>
> > ...To change the context of a request (such as an incoming) you then also want to modify to send back out, use Request.Clone. Between those two uses, it's rare to need WithContext.
>
> I wanted to ask if Clone should be preferred over WithContext in all situations. Specifically I'm writing a server middleware and only need to annotate a request (adding a logged in user) so it can be used by other handlers.
>
> Is WithContext not appropriate for this situation?

And @bradfitz responded:

> WithContext works there.

And this has come up occasionally in Slack as well, with people writing very simple middleware that wrap `http.Handler` and just stick a value into the context on the request using `WithContext`. An extremely simple version, for which `Clone` seems like overkill, might be:

```
func WithRequestId(base http.Handler) http.Handler {
   return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
      ctx := context.WithValue(r.Context(), ""request_id"", uuid.NewString())
      base.ServeHTTP(w, r.WithContext(ctx))
   })
}
```

So this issue is mostly asking: is this usage of `WithContext` in this sort of middleware context _correct_, and furthermore can we augment the `WithContext` documentation block to be less prescriptive that `Clone` is the obvious way to go, and that there are plenty of value use-cases for `WithContext`, especially when you're not looking to ""reuse"" the request to make a subsequent request?",1,net http  clarify use cases of withcontext vs clone on requests   the  http request  struct had a  clone  method added in go      prompted by this issue    at that time  i believe the documentation for  withcontext  was updated to suggest that most uses of that method could be replaced with  clone      however  that issue also had this follow up exchange          bradfitz i just came across clone as a first time user of contexts within net http  i had a question about this bit of documentation on withcontext             to change the context of a request  such as an incoming  you then also want to modify to send back out  use request clone  between those two uses  it s rare to need withcontext        i wanted to ask if clone should be preferred over withcontext in all situations  specifically i m writing a server middleware and only need to annotate a request  adding a logged in user  so it can be used by other handlers        is withcontext not appropriate for this situation     and  bradfitz responded       withcontext works there     and this has come up occasionally in slack as well  with people writing very simple middleware that wrap  http handler  and just stick a value into the context on the request using  withcontext   an extremely simple version  for which  clone  seems like overkill  might be          func withrequestid base http handler  http handler       return http handlerfunc func w http responsewriter  r  http request           ctx    context withvalue r context     request id   uuid newstring           base servehttp w  r withcontext ctx                     so this issue is mostly asking  is this usage of  withcontext  in this sort of middleware context  correct   and furthermore can we augment the  withcontext  documentation block to be less prescriptive that  clone  is the obvious way to go  and that there are plenty of value use cases for  withcontext   especially when you re not looking to  reuse  the request to make a subsequent request ,1
221500,17019404340.0,IssuesEvent,2021-07-02 16:26:06,golang/go,https://api.github.com/repos/golang/go,closed,cmd/dist: typo in comment,Documentation NeedsFix,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.16 linux/amd64
</pre>

### Does this issue reproduce with the latest release?



### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""/home/vagrant/go/bin""
GOCACHE=""/home/vagrant/.cache/go-build""
GOENV=""/home/vagrant/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/vagrant/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/vagrant/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""go1.16""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2823638017=/tmp/go-build -gno-record-gcc-switches""

</pre></details>

### What did you do?
Read the source code at https://github.com/golang/go/blob/master/src/cmd/dist/test.go#L784

I think `syscall.SysProcAttr`, not `syscall.SysProcAttri`.
Sorry if I'm wrong.


<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->



### What did you expect to see?
```
// because syscall.SysProcAttri struct used in misc/cgo/testsanitizers is only built on linux.
```


### What did you see instead?
```
// because syscall.SysProcAttr struct used in misc/cgo/testsanitizers is only built on linux.
```
",1.0,"cmd/dist: typo in comment - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.16 linux/amd64
</pre>

### Does this issue reproduce with the latest release?



### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""/home/vagrant/go/bin""
GOCACHE=""/home/vagrant/.cache/go-build""
GOENV=""/home/vagrant/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/vagrant/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/vagrant/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""go1.16""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2823638017=/tmp/go-build -gno-record-gcc-switches""

</pre></details>

### What did you do?
Read the source code at https://github.com/golang/go/blob/master/src/cmd/dist/test.go#L784

I think `syscall.SysProcAttr`, not `syscall.SysProcAttri`.
Sorry if I'm wrong.


<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->



### What did you expect to see?
```
// because syscall.SysProcAttri struct used in misc/cgo/testsanitizers is only built on linux.
```


### What did you see instead?
```
// because syscall.SysProcAttr struct used in misc/cgo/testsanitizers is only built on linux.
```
",1,cmd dist  typo in comment         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version            go version  go version     linux             does this issue reproduce with the latest release             what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin   home vagrant go bin   gocache   home vagrant  cache go build   goenv   home vagrant  config go env   goexe     goflags     gohostarch      gohostos  linux   goinsecure     gomodcache   home vagrant go pkg mod   gonoproxy     gonosumdb     goos  linux   gopath   home vagrant go   goprivate     goproxy     goroot   usr local go   gosumdb  sum golang org   gotmpdir     gotooldir   usr local go pkg tool linux     govcs     goversion        gccgo  gccgo   ar  ar   cc  gcc   cxx  g     cgo enabled      gomod   dev null   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches               what did you do   read the source code at      i think  syscall sysprocattr   not  syscall sysprocattri    sorry if i m wrong             if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best                  what did you expect to see           because syscall sysprocattri struct used in misc cgo testsanitizers is only built on linux                what did you see instead           because syscall sysprocattr struct used in misc cgo testsanitizers is only built on linux        ,1
129835,12419529005.0,IssuesEvent,2020-05-23 06:47:41,golang/go,https://api.github.com/repos/golang/go,closed,encoding/asn1: extra elements at the end of a sequence are completely ignored,Documentation NeedsInvestigation,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### Does this issue reproduce with the latest release?
Yes

### What did you do?

Appended garbage data (such as zeros, null, etc) to a hex encoded asn1 SEQUENCE type.

For example, rather than:
`302d021500aa6a258fbf7d90e15614676d377df8b10e38db4a0214496d5220b5f67d3532d1f991203bc3523b964c3b`

I provided:

`302f021500aa6a258fbf7d90e15614676d377df8b10e38db4a0214496d5220b5f67d3532d1f991203bc3523b964c3b0000`

which has a slightly larger length, and some trailing zeros.

https://play.golang.org/p/TrwfRC31i1m

### What did you expect to see?

The dropped/ignored data should be provided in `rest`, or documented otherwise, so users know that some of the data provided to `asn1.Unmarshal` was not included in the resulting struct.

Since this is often used alongside `ecdsa.Verify`, the best long term solution would be implement an API similar to the one described in https://github.com/golang/go/issues/20544 that can except an asn1 encoded string and verify it directly, returning 'false' if there is either a parsing issue (ie. some trailing garbage) or if the verification failed.

### What did you see instead?

The garbage at the end is simply dropped off and ignored, but not provided in `rest` when returned from `asn1.Unmarshal`. Both of the encoded strings above produce the same struct value without an error or anything in `rest`.

This is surprising, as I would expect DER encoding to have a 1:1 relationship between input and output, but also that data is dropped off without being included in rest (as many users likely expect)",1.0,"encoding/asn1: extra elements at the end of a sequence are completely ignored - <!-- Please answer these questions before submitting your issue. Thanks! -->

### Does this issue reproduce with the latest release?
Yes

### What did you do?

Appended garbage data (such as zeros, null, etc) to a hex encoded asn1 SEQUENCE type.

For example, rather than:
`302d021500aa6a258fbf7d90e15614676d377df8b10e38db4a0214496d5220b5f67d3532d1f991203bc3523b964c3b`

I provided:

`302f021500aa6a258fbf7d90e15614676d377df8b10e38db4a0214496d5220b5f67d3532d1f991203bc3523b964c3b0000`

which has a slightly larger length, and some trailing zeros.

https://play.golang.org/p/TrwfRC31i1m

### What did you expect to see?

The dropped/ignored data should be provided in `rest`, or documented otherwise, so users know that some of the data provided to `asn1.Unmarshal` was not included in the resulting struct.

Since this is often used alongside `ecdsa.Verify`, the best long term solution would be implement an API similar to the one described in https://github.com/golang/go/issues/20544 that can except an asn1 encoded string and verify it directly, returning 'false' if there is either a parsing issue (ie. some trailing garbage) or if the verification failed.

### What did you see instead?

The garbage at the end is simply dropped off and ignored, but not provided in `rest` when returned from `asn1.Unmarshal`. Both of the encoded strings above produce the same struct value without an error or anything in `rest`.

This is surprising, as I would expect DER encoding to have a 1:1 relationship between input and output, but also that data is dropped off without being included in rest (as many users likely expect)",1,encoding    extra elements at the end of a sequence are completely ignored            does this issue reproduce with the latest release   yes        what did you do     appended garbage data  such as zeros  null  etc  to a hex encoded   sequence type     for example  rather than          i provided            which has a slightly larger length  and some trailing zeros              what did you expect to see     the dropped ignored data should be provided in  rest   or documented otherwise  so users know that some of the data provided to    unmarshal  was not included in the resulting struct     since this is often used alongside  ecdsa verify   the best long term solution would be implement an api similar to the one described in   that can except an   encoded string and verify it directly  returning  false  if there is either a parsing issue  ie  some trailing garbage  or if the verification failed         what did you see instead     the garbage at the end is simply dropped off and ignored  but not provided in  rest  when returned from    unmarshal   both of the encoded strings above produce the same struct value without an error or anything in  rest      this is surprising  as i would expect der encoding to have a     relationship between input and output  but also that data is dropped off without being included in rest  as many users likely expect ,1
214391,16563198123.0,IssuesEvent,2021-05-29 00:16:57,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.17: document text/template/parse changes for Go 1.17,Documentation NeedsInvestigation help wanted release-blocker,"As of filing this issue, the [Go 1.17 draft release notes](https://tip.golang.org/doc/go1.17) contained the following HTML:

<dl id=""text/template/parse""><dt><a href=""/pkg/text/template/parse/"">text/template/parse</a></dt>
  <dd>
    <p><!-- CL 301493 -->
      TODO: <a href=""https://golang.org/cl/301493"">https://golang.org/cl/301493</a>: add a mode to skip func-check on parsing
    </p>
  </dd>
</dl>

---

This TODO needs to be resolved by July 1 so that we can have complete release notes for [Beta 1](https://golang.org/s/release#june-1--december-1-beta-1-issued).

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.17:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.17) and include ""For #44513. Fixes #46025."" in the body.",1.0,"doc/go1.17: document text/template/parse changes for Go 1.17 - As of filing this issue, the [Go 1.17 draft release notes](https://tip.golang.org/doc/go1.17) contained the following HTML:

<dl id=""text/template/parse""><dt><a href=""/pkg/text/template/parse/"">text/template/parse</a></dt>
  <dd>
    <p><!-- CL 301493 -->
      TODO: <a href=""https://golang.org/cl/301493"">https://golang.org/cl/301493</a>: add a mode to skip func-check on parsing
    </p>
  </dd>
</dl>

---

This TODO needs to be resolved by July 1 so that we can have complete release notes for [Beta 1](https://golang.org/s/release#june-1--december-1-beta-1-issued).

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.17:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.17) and include ""For #44513. Fixes #46025."" in the body.",1,doc      document text template parse changes for go       as of filing this issue  the     contained the following html      text template parse                    todo   a href    add a mode to skip func check on parsing                   this todo needs to be resolved by july   so that we can have complete release notes for      a sequence of steps to resolve this issue may be      come up with a draft release note entry in this issue  then move the issue to needsfix state     send a cl with  doc           and include  for     fixes      in the body ,1
6197,3005376773.0,IssuesEvent,2015-07-26 21:04:59,golang/go,https://api.github.com/repos/golang/go,closed,doc: clarify usage of CGO_ENABLED,Documentation,"I was trying to repro issue #9510.  I'm on a linux/amd64 system, and I used ""GOARCH=386 ./make.bash --no-clean"" to setup a cross-compiler toolchain.  However, subsequently running ""GOARCH=386 go build issue"" per iant@'s instructions yielded an unhelpful ""no buildable Go source files in .../issue/a"" error.

Poking into the package go/build source code, I discovered mention of ""CGO_ENABLED"" so I tried ""GOARCH=386 CGO_ENABLED=1 go build issue"".  This worked to reproduce the issue.

However, trying to learn more about this setting, I found this in cmd/cgo/doc.go:

    To enable cgo during cross compiling builds, set the CGO_ENABLED
    environment variable to 1 when building the Go tools with make.bash.

So I inferred I was misusing it and decided to startover with ""GOARCH=386 CGO_ENABLED=1 ./make.bash --no-clean"" instead, but then running just ""GOARCH=386 go build issue"" again produced the same ""no buildable Go source files"" error.

Confusingly, src/make.bash also seems to mention CGO_ENABLED having some significance, but at the moment (even having poked through run.bash and grep'd the source code), I'm still not sure I entirely understand the significance.",1.0,"doc: clarify usage of CGO_ENABLED - I was trying to repro issue #9510.  I'm on a linux/amd64 system, and I used ""GOARCH=386 ./make.bash --no-clean"" to setup a cross-compiler toolchain.  However, subsequently running ""GOARCH=386 go build issue"" per iant@'s instructions yielded an unhelpful ""no buildable Go source files in .../issue/a"" error.

Poking into the package go/build source code, I discovered mention of ""CGO_ENABLED"" so I tried ""GOARCH=386 CGO_ENABLED=1 go build issue"".  This worked to reproduce the issue.

However, trying to learn more about this setting, I found this in cmd/cgo/doc.go:

    To enable cgo during cross compiling builds, set the CGO_ENABLED
    environment variable to 1 when building the Go tools with make.bash.

So I inferred I was misusing it and decided to startover with ""GOARCH=386 CGO_ENABLED=1 ./make.bash --no-clean"" instead, but then running just ""GOARCH=386 go build issue"" again produced the same ""no buildable Go source files"" error.

Confusingly, src/make.bash also seems to mention CGO_ENABLED having some significance, but at the moment (even having poked through run.bash and grep'd the source code), I'm still not sure I entirely understand the significance.",1,doc  clarify usage of cgo enabled   i was trying to repro issue      i m on a linux   system  and i used  goarch     make bash   no clean  to setup a cross compiler toolchain   however  subsequently running  goarch   go build issue  per iant  s instructions yielded an unhelpful  no buildable go source files in     issue a  error     poking into the package go build source code  i discovered mention of  cgo enabled  so i tried  goarch   cgo enabled   go build issue    this worked to reproduce the issue     however  trying to learn more about this setting  i found this in cmd cgo doc go         to enable cgo during cross compiling builds  set the cgo enabled      environment variable to   when building the go tools with make bash     so i inferred i was misusing it and decided to startover with  goarch   cgo enabled     make bash   no clean  instead  but then running just  goarch   go build issue  again produced the same  no buildable go source files  error     confusingly  src make bash also seems to mention cgo enabled having some significance  but at the moment  even having poked through run bash and grep d the source code   i m still not sure i entirely understand the significance ,1
349717,10472318112.0,IssuesEvent,2019-09-23 09:54:32,bradyrx/climpred,https://api.github.com/repos/bradyrx/climpred,closed,Add vectorized deterministic and probabilistic metrics,high priority,"Take advantage of existing: don't reinvent the wheel

- murcss: 
  - https://rawgit.com/illing2005/murcss/master/doc/build/html/tutorial.html
  - all calculations based on CDOs
  - built primarily for MPI-ESM Decadal Prediction Project MiKlip
  - can handle Murphy-Eppstein decomposition, bias (really useful for hindcasts)
  - can probabilty be used to create lead year timeseries easily
  - contains:
    - MSESS (Mean Squared Error Skill Score)
    - CRPSS (Continous Ranked Probabillity Skill Score)

- properscoring
  - https://github.com/TheClimateCorporation/properscoring
  - contains:
   - Continuous Ranked Probability Score (CRPS) 
   - Brier Score

- https://github.com/PeterRochford/SkillMetrics
  - not applicable to maps?

New metrics should be able to be applied to mapped data (input data dimensions lon, lat, time, ensemble, member) and run fast. Otherwise bootstrapping will not work.

Lets post in this thread metrics we want to see in this package:",1.0,"Add vectorized deterministic and probabilistic metrics - Take advantage of existing: don't reinvent the wheel

- murcss: 
  - https://rawgit.com/illing2005/murcss/master/doc/build/html/tutorial.html
  - all calculations based on CDOs
  - built primarily for MPI-ESM Decadal Prediction Project MiKlip
  - can handle Murphy-Eppstein decomposition, bias (really useful for hindcasts)
  - can probabilty be used to create lead year timeseries easily
  - contains:
    - MSESS (Mean Squared Error Skill Score)
    - CRPSS (Continous Ranked Probabillity Skill Score)

- properscoring
  - https://github.com/TheClimateCorporation/properscoring
  - contains:
   - Continuous Ranked Probability Score (CRPS) 
   - Brier Score

- https://github.com/PeterRochford/SkillMetrics
  - not applicable to maps?

New metrics should be able to be applied to mapped data (input data dimensions lon, lat, time, ensemble, member) and run fast. Otherwise bootstrapping will not work.

Lets post in this thread metrics we want to see in this package:",0,add vectorized deterministic and probabilistic metrics   take advantage of existing  don t reinvent the wheel      murcss               all calculations based on cdos      built primarily for mpi esm decadal prediction project miklip      can handle murphy eppstein decomposition  bias  really useful for hindcasts       can probabilty be used to create lead year timeseries easily      contains         msess  mean squared error skill score         crpss  continous ranked probabillity skill score       properscoring             contains        continuous ranked probability score  crps         brier score             not applicable to maps     new metrics should be able to be applied to mapped data  input data dimensions lon  lat  time  ensemble  member  and run fast  otherwise bootstrapping will not work     lets post in this thread metrics we want to see in this package ,0
53631,7846878716.0,IssuesEvent,2018-06-19 16:40:43,golang/go,https://api.github.com/repos/golang/go,closed,all: remove support for OS X 10.8 and 10.9,Documentation NeedsFix release-blocker,"Per discussion on #23011, Go 1.11 will remove support for OS X 10.8 Mountain Lion and OS X 10.9 Mavericks. This issue is to remember to do that, and to document it in the Go 1.11 release notes.
",1.0,"all: remove support for OS X 10.8 and 10.9 - Per discussion on #23011, Go 1.11 will remove support for OS X 10.8 Mountain Lion and OS X 10.9 Mavericks. This issue is to remember to do that, and to document it in the Go 1.11 release notes.
",1,all  remove support for os x     and       per discussion on     go     will remove support for os x     mountain lion and os x     mavericks  this issue is to remember to do that  and to document it in the go     release notes   ,1
239467,26231680632.0,IssuesEvent,2023-01-05 01:09:21,ChoeMinji/rails-7.0.0.alpha2,https://api.github.com/repos/ChoeMinji/rails-7.0.0.alpha2,opened,CVE-2021-44906 (High) detected in minimist-1.2.5.tgz,security vulnerability,"## CVE-2021-44906 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>minimist-1.2.5.tgz</b></p></summary>

<p>parse argument options</p>
<p>Library home page: <a href=""https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz"">https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/minimist/package.json</p>
<p>

Dependency Hierarchy:
  - activestorage-7.0.0-alpha2.tgz (Root Library)
    - eslint-plugin-import-2.23.4.tgz
      - tsconfig-paths-3.10.1.tgz
        - json5-2.2.0.tgz
          - :x: **minimist-1.2.5.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/ChoeMinji/rails-7.0.0.alpha2/commit/3a3902efe3788aa4f5410d439175653e42f854e6"">3a3902efe3788aa4f5410d439175653e42f854e6</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>  
  
Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).

<p>Publish Date: 2022-03-17
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-44906>CVE-2021-44906</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>Release Date: 2022-03-17</p>
<p>Fix Resolution (minimist): 1.2.6</p>
<p>Direct dependency fix Resolution (@rails/activestorage): 7.0.0</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2021-44906 (High) detected in minimist-1.2.5.tgz - ## CVE-2021-44906 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>minimist-1.2.5.tgz</b></p></summary>

<p>parse argument options</p>
<p>Library home page: <a href=""https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz"">https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/minimist/package.json</p>
<p>

Dependency Hierarchy:
  - activestorage-7.0.0-alpha2.tgz (Root Library)
    - eslint-plugin-import-2.23.4.tgz
      - tsconfig-paths-3.10.1.tgz
        - json5-2.2.0.tgz
          - :x: **minimist-1.2.5.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/ChoeMinji/rails-7.0.0.alpha2/commit/3a3902efe3788aa4f5410d439175653e42f854e6"">3a3902efe3788aa4f5410d439175653e42f854e6</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>  
  
Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).

<p>Publish Date: 2022-03-17
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-44906>CVE-2021-44906</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>Release Date: 2022-03-17</p>
<p>Fix Resolution (minimist): 1.2.6</p>
<p>Direct dependency fix Resolution (@rails/activestorage): 7.0.0</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,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   package json   path to vulnerable library   node modules minimist package json     dependency hierarchy      activestorage         tgz  root library        eslint plugin import       tgz         tsconfig paths       tgz                   tgz              x    minimist       tgz    vulnerable library   found in head commit   a href     found in base branch   main              vulnerability details         minimist         is vulnerable to prototype pollution via file index js  function setkey    lines         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   release date          fix resolution  minimist           direct dependency fix resolution   rails activestorage                       step up your open source security game with mend    ,0
7596,6966963897.0,IssuesEvent,2017-12-10 01:12:16,marcelb98/piTemp,https://api.github.com/repos/marcelb98/piTemp,opened,Possible JS-injection,security bug,"On the detail-page of a sensor is a possible JS-injection when sensor (the id) is being included.
Same applies to the datetimes.

https://github.com/marcelb98/piTemp/blob/be82678f54e7522c699fbbfe92da55e0a1d8a79e/templates/detail.html#L62
https://github.com/marcelb98/piTemp/blob/be82678f54e7522c699fbbfe92da55e0a1d8a79e/app.py#L87",True,"Possible JS-injection - On the detail-page of a sensor is a possible JS-injection when sensor (the id) is being included.
Same applies to the datetimes.

https://github.com/marcelb98/piTemp/blob/be82678f54e7522c699fbbfe92da55e0a1d8a79e/templates/detail.html#L62
https://github.com/marcelb98/piTemp/blob/be82678f54e7522c699fbbfe92da55e0a1d8a79e/app.py#L87",0,possible js injection   on the detail page of a sensor is a possible js injection when sensor  the id  is being included   same applies to the datetimes         ,0
30542,24905537049.0,IssuesEvent,2022-10-29 07:27:20,StefanSchubert/sabi,https://api.github.com/repos/StefanSchubert/sabi,closed,How to activate spring milestone repository in github action?,bug help wanted maven infrastructure,"SABIs github action (CI pipeline) is currently broken due to the use of spring milestone repository.
How can we activate this repo for githubs CI?",1.0,"How to activate spring milestone repository in github action? - SABIs github action (CI pipeline) is currently broken due to the use of spring milestone repository.
How can we activate this repo for githubs CI?",0,how to activate spring milestone repository in github action    sabis github action  ci pipeline  is currently broken due to the use of spring milestone repository   how can we activate this repo for githubs ci ,0
274899,20883189394.0,IssuesEvent,2022-03-23 00:07:39,golang/go,https://api.github.com/repos/golang/go,closed,doc: GOAMD64 not mentionned on https://go.dev/doc/install/source,Documentation NeedsFix,"Go 1.18 introduces [GOAMD64](https://go.dev/doc/go1.18#amd64) compile setting.

The GOAMD64 environment variable is not mentionned on https://go.dev/doc/install/source contrary to other environment variables that affect the build. ",1.0,"doc: GOAMD64 not mentionned on https://go.dev/doc/install/source - Go 1.18 introduces [GOAMD64](https://go.dev/doc/go1.18#amd64) compile setting.

The GOAMD64 environment variable is not mentionned on https://go.dev/doc/install/source contrary to other environment variables that affect the build. ",1,doc    not mentionned on     go     introduces     compile setting     the   environment variable is not mentionned on   contrary to other environment variables that affect the build  ,1
81733,10255495303.0,IssuesEvent,2019-08-21 15:31:54,golang/go,https://api.github.com/repos/golang/go,closed,x/website: documents link is not aligned on tip.golang.org/doc/go1.6+,Documentation NeedsFix help wanted,"### What did you do?
visit one of:
https://tip.golang.org/doc/go1.6
...
https://tip.golang.org/doc/go1.13

### What did you expect to see?
see behavior on everything pre go1.6 docs

### What did you see instead?
![documents_not_aligned](https://user-images.githubusercontent.com/19241481/63279822-fc51ed80-c2a9-11e9-8daa-00033fc2e2f5.png)

",1.0,"x/website: documents link is not aligned on tip.golang.org/doc/go1.6+ - ### What did you do?
visit one of:
https://tip.golang.org/doc/go1.6
...
https://tip.golang.org/doc/go1.13

### What did you expect to see?
see behavior on everything pre go1.6 docs

### What did you see instead?
![documents_not_aligned](https://user-images.githubusercontent.com/19241481/63279822-fc51ed80-c2a9-11e9-8daa-00033fc2e2f5.png)

",1,x website  documents link is not aligned on tip golang org doc            what did you do   visit one of                    what did you expect to see   see behavior on everything pre     docs        what did you see instead           ,1
169824,26865214765.0,IssuesEvent,2023-02-03 22:40:32,regen-network/regen-registry,https://api.github.com/repos/regen-network/regen-registry,closed,Regional Overview page or popup,design,"Design a page for showing info about the region

See this video from Amazon working group: https://drive.google.com/drive/u/1/folders/1kZAAwb2Qp-UYd7LnHcFtl9bveapi4NuX",1.0,"Regional Overview page or popup - Design a page for showing info about the region

See this video from Amazon working group: https://drive.google.com/drive/u/1/folders/1kZAAwb2Qp-UYd7LnHcFtl9bveapi4NuX",0,regional overview page or popup   design a page for showing info about the region  see this video from amazon working group   ,0
50632,7614181443.0,IssuesEvent,2018-05-02 01:11:16,golang/go,https://api.github.com/repos/golang/go,closed,doc: clearer plain git contributing guidelines,Documentation,"### What:
Change the contributing guidelines document to make the recommended process more familiar and obvious to users of plain git.

### What it is not:
This issue is not a request or proposal to replace Gerrit or the review process. This issue is not a request or proposal to remove the `git-codereview` tool or to make drastic changes to how anyone on the Go team or existing contributors go about contributing. 

### Why:
There are other open issues proposing a switch to GitHub (#21956), or adding the ability to support pushing via GitHub (#18517). Based on my own experience I think much of the friction that GitHub users are experiencing is caused by the contributing guidelines centering around `git-codereview`, which abstracts git away from the developer. Abstracting git away from developers is jarring when developers know how to use that tool already. It gives them the experience that they are using something that is entirely different to what they use today, even though it is not.

### Context:
I recently submitted my [first](https://go-review.googlesource.com/c/go/+/73890) [contribution](https://go-review.googlesource.com/c/go/+/73891) to Go and was surprised at how straight forward and refreshing Gerrit was in comparison to GitHub. I had delayed contributing because the process described at https://golang.org/doc/contribute.html appeared so different to what I was use to. In practice it wasn't. It only appeared that way because there was a layer of abstraction.

Before contributing the main point of friction for me wasn't the use of Gerrit vs GitHub, but the fact that all of the examples centered around the use of `git-codereview`, a custom tool for interacting with the Go Gerrit instance. I realize this tool is optional, but it took time to read all of the text and note down which git commands each `git-codereview` command actually used.

At the end it came down to:
1. Install two hooks
2. `git clone`
3. `git pull -r`
4. `git checkout -b <branch>`
5. `git commit`
6. `git push -u origin HEAD:refs/for/master` (patch set 1)
7. `git commit --amend`
8. `git push -u origin HEAD:refs/for/master` (patch set 2)

The above is almost identical to the workflows I use at work and on open source on GitHub, and it is instantly familiar to me as a git user.

The contribution guidelines tell a different story:
1. `git codereview hooks`
2. `git clone`
3. `git sync`
4. `git change`
5. `git mail` (patch set 1)
6. `git change` (to amend)
7. `git mail` (patch set 2)

While the above is technically less commands, it's four new commands that I had never seen before and had to learn about. These commands abstract git away from plain git users, unnecessarily.

### How:
Some ideas for how the contributing guidelines document could be made more familiar to plain git users:

* Replace examples using `git-codereview` with plain git commands where the corresponding git commands are simple and straight forward. e.g. `git sync` vs `git pull -r`, `git push` vs `git mail`, etc.
* Display plain git commands side-by-side (not one after the other) in the same size, font, weight, etc.
* Make `git-codereview` the recommended path for those not familiar with git, or power users.
* Make plain git the recommended path for those familiar with git, with a suggestion to check out `git-codereview`.
* Offer the pre-commit hook at a URL that can be curl'd like how the [commit-msg hook is available](http://go-review.googlesource.com/tools/hooks/commit-msg) so that it's simple for developers to install the commit hooks how they would any others for other projects.

I've got a branch with changes to the contributing doc that I made to experiment with these ideas and to confirm if focusing on plain git commands would make it appear more familiar and approachable. I'd love to be involved with improving the guidelines in this way if this is something that the community agrees with.",1.0,"doc: clearer plain git contributing guidelines - ### What:
Change the contributing guidelines document to make the recommended process more familiar and obvious to users of plain git.

### What it is not:
This issue is not a request or proposal to replace Gerrit or the review process. This issue is not a request or proposal to remove the `git-codereview` tool or to make drastic changes to how anyone on the Go team or existing contributors go about contributing. 

### Why:
There are other open issues proposing a switch to GitHub (#21956), or adding the ability to support pushing via GitHub (#18517). Based on my own experience I think much of the friction that GitHub users are experiencing is caused by the contributing guidelines centering around `git-codereview`, which abstracts git away from the developer. Abstracting git away from developers is jarring when developers know how to use that tool already. It gives them the experience that they are using something that is entirely different to what they use today, even though it is not.

### Context:
I recently submitted my [first](https://go-review.googlesource.com/c/go/+/73890) [contribution](https://go-review.googlesource.com/c/go/+/73891) to Go and was surprised at how straight forward and refreshing Gerrit was in comparison to GitHub. I had delayed contributing because the process described at https://golang.org/doc/contribute.html appeared so different to what I was use to. In practice it wasn't. It only appeared that way because there was a layer of abstraction.

Before contributing the main point of friction for me wasn't the use of Gerrit vs GitHub, but the fact that all of the examples centered around the use of `git-codereview`, a custom tool for interacting with the Go Gerrit instance. I realize this tool is optional, but it took time to read all of the text and note down which git commands each `git-codereview` command actually used.

At the end it came down to:
1. Install two hooks
2. `git clone`
3. `git pull -r`
4. `git checkout -b <branch>`
5. `git commit`
6. `git push -u origin HEAD:refs/for/master` (patch set 1)
7. `git commit --amend`
8. `git push -u origin HEAD:refs/for/master` (patch set 2)

The above is almost identical to the workflows I use at work and on open source on GitHub, and it is instantly familiar to me as a git user.

The contribution guidelines tell a different story:
1. `git codereview hooks`
2. `git clone`
3. `git sync`
4. `git change`
5. `git mail` (patch set 1)
6. `git change` (to amend)
7. `git mail` (patch set 2)

While the above is technically less commands, it's four new commands that I had never seen before and had to learn about. These commands abstract git away from plain git users, unnecessarily.

### How:
Some ideas for how the contributing guidelines document could be made more familiar to plain git users:

* Replace examples using `git-codereview` with plain git commands where the corresponding git commands are simple and straight forward. e.g. `git sync` vs `git pull -r`, `git push` vs `git mail`, etc.
* Display plain git commands side-by-side (not one after the other) in the same size, font, weight, etc.
* Make `git-codereview` the recommended path for those not familiar with git, or power users.
* Make plain git the recommended path for those familiar with git, with a suggestion to check out `git-codereview`.
* Offer the pre-commit hook at a URL that can be curl'd like how the [commit-msg hook is available](http://go-review.googlesource.com/tools/hooks/commit-msg) so that it's simple for developers to install the commit hooks how they would any others for other projects.

I've got a branch with changes to the contributing doc that I made to experiment with these ideas and to confirm if focusing on plain git commands would make it appear more familiar and approachable. I'd love to be involved with improving the guidelines in this way if this is something that the community agrees with.",1,doc  clearer plain git contributing guidelines       what   change the contributing guidelines document to make the recommended process more familiar and obvious to users of plain git         what it is not   this issue is not a request or proposal to replace gerrit or the review process  this issue is not a request or proposal to remove the  git codereview  tool or to make drastic changes to how anyone on the go team or existing contributors go about contributing          why   there are other open issues proposing a switch to github       or adding the ability to support pushing via github       based on my own experience i think much of the friction that github users are experiencing is caused by the contributing guidelines centering around  git codereview   which abstracts git away from the developer  abstracting git away from developers is jarring when developers know how to use that tool already  it gives them the experience that they are using something that is entirely different to what they use today  even though it is not         context   i recently submitted my         to go and was surprised at how straight forward and refreshing gerrit was in comparison to github  i had delayed contributing because the process described at   appeared so different to what i was use to  in practice it wasn t  it only appeared that way because there was a layer of abstraction     before contributing the main point of friction for me wasn t the use of gerrit vs github  but the fact that all of the examples centered around the use of  git codereview   a custom tool for interacting with the go gerrit instance  i realize this tool is optional  but it took time to read all of the text and note down which git commands each  git codereview  command actually used     at the end it came down to      install two hooks      git clone       git pull  r       git checkout  b         git commit       git push  u origin head refs for master   patch set         git commit   amend       git push  u origin head refs for master   patch set       the above is almost identical to the workflows i use at work and on open source on github  and it is instantly familiar to me as a git user     the contribution guidelines tell a different story       git codereview hooks       git clone       git sync       git change       git mail   patch set         git change   to amend       git mail   patch set       while the above is technically less commands  it s four new commands that i had never seen before and had to learn about  these commands abstract git away from plain git users  unnecessarily         how   some ideas for how the contributing guidelines document could be made more familiar to plain git users       replace examples using  git codereview  with plain git commands where the corresponding git commands are simple and straight forward  e g   git sync  vs  git pull  r    git push  vs  git mail   etc     display plain git commands side by side  not one after the other  in the same size  font  weight  etc     make  git codereview  the recommended path for those not familiar with git  or power users     make plain git the recommended path for those familiar with git  with a suggestion to check out  git codereview      offer the pre commit hook at a url that can be curl d like how the     so that it s simple for developers to install the commit hooks how they would any others for other projects     i ve got a branch with changes to the contributing doc that i made to experiment with these ideas and to confirm if focusing on plain git commands would make it appear more familiar and approachable  i d love to be involved with improving the guidelines in this way if this is something that the community agrees with ,1
18259,4241769452.0,IssuesEvent,2016-07-06 17:20:43,golang/go,https://api.github.com/repos/golang/go,closed,encoding/xml: needless package qualifier in godoc output,Documentation,"<pre>$ godoc encoding/xml | grep 'xml\.'
	- the value of the XMLName field of type xml.Name
	* If the struct has a field named XMLName of type xml.Name,
    Unmarshal maps an XML element to an xml.Name by recording the element
    Decode works like xml.Unmarshal, except it reads the decoder stream to
    DecodeElement works like xml.Unmarshal except that it takes a pointer to
$

It appears to be breaking the convention for no good reason. It needs s/xml\.//</pre>",1.0,"encoding/xml: needless package qualifier in godoc output - <pre>$ godoc encoding/xml | grep 'xml\.'
	- the value of the XMLName field of type xml.Name
	* If the struct has a field named XMLName of type xml.Name,
    Unmarshal maps an XML element to an xml.Name by recording the element
    Decode works like xml.Unmarshal, except it reads the decoder stream to
    DecodeElement works like xml.Unmarshal except that it takes a pointer to
$

It appears to be breaking the convention for no good reason. It needs s/xml\.//</pre>",1,encoding xml  needless package qualifier in godoc output      godoc encoding xml   grep  xml    	  the value of the xmlname field of type xml name 	  if the struct has a field named xmlname of type xml name      unmarshal maps an xml element to an xml name by recording the element     decode works like xml unmarshal  except it reads the decoder stream to     decodeelement works like xml unmarshal except that it takes a pointer to    it appears to be breaking the convention for no good reason  it needs s xml     ,1
261361,19707991102.0,IssuesEvent,2022-01-13 00:54:52,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.18: clarify when/why to set GOAMD64 architecture values,Documentation NeedsDecision,"Reading the Go 1.18 release notes, there are sort of two naive models that you could have about this:

> Go 1.18 introduces the new GOAMD64 environment variable, which selects a mininum target version of the AMD64 architecture. Allowed values are v1, v2, v3, or v4. Each higher level requires, and takes advantage of, additional processor features. A detailed description can be found here.
>
> The GOAMD64 environment variable defaults to v1.

Model 1: Setting these variables at compile time means Go will replace the worse CPU instructions with the better CPU instructions in the generated binary.

Model 2: Both instructions are compiled into the binary, and at runtime Go will read the GOAMD64 environment variable and use the better CPU instructions instead of the worse CPU instructions, if they are available.

I would guess that Model 1 is what you are going for. But that's also a little confusing to me because I believe that the compiler does CPU feature detection already to determine which instructions are supported, at least I think I've seen commits to that effect. So reading the documentation, I am confused why we now need an environment variable. My colleague also tried to read through the code to figure out where Go was using any of the new CPU instructions and couldn't find anything.

I think the doc could benefit from another sentence or two explaining a bit more context about why this is necessary now, or linking to more information.",1.0,"doc/go1.18: clarify when/why to set GOAMD64 architecture values - Reading the Go 1.18 release notes, there are sort of two naive models that you could have about this:

> Go 1.18 introduces the new GOAMD64 environment variable, which selects a mininum target version of the AMD64 architecture. Allowed values are v1, v2, v3, or v4. Each higher level requires, and takes advantage of, additional processor features. A detailed description can be found here.
>
> The GOAMD64 environment variable defaults to v1.

Model 1: Setting these variables at compile time means Go will replace the worse CPU instructions with the better CPU instructions in the generated binary.

Model 2: Both instructions are compiled into the binary, and at runtime Go will read the GOAMD64 environment variable and use the better CPU instructions instead of the worse CPU instructions, if they are available.

I would guess that Model 1 is what you are going for. But that's also a little confusing to me because I believe that the compiler does CPU feature detection already to determine which instructions are supported, at least I think I've seen commits to that effect. So reading the documentation, I am confused why we now need an environment variable. My colleague also tried to read through the code to figure out where Go was using any of the new CPU instructions and couldn't find anything.

I think the doc could benefit from another sentence or two explaining a bit more context about why this is necessary now, or linking to more information.",1,doc      clarify when why to set   architecture values   reading the go     release notes  there are sort of two naive models that you could have about this       go     introduces the new   environment variable  which selects a mininum target version of the   architecture  allowed values are          or    each higher level requires  and takes advantage of  additional processor features  a detailed description can be found here        the   environment variable defaults to       model    setting these variables at compile time means go will replace the worse cpu instructions with the better cpu instructions in the generated binary     model    both instructions are compiled into the binary  and at runtime go will read the   environment variable and use the better cpu instructions instead of the worse cpu instructions  if they are available     i would guess that model   is what you are going for  but that s also a little confusing to me because i believe that the compiler does cpu feature detection already to determine which instructions are supported  at least i think i ve seen commits to that effect  so reading the documentation  i am confused why we now need an environment variable  my colleague also tried to read through the code to figure out where go was using any of the new cpu instructions and couldn t find anything     i think the doc could benefit from another sentence or two explaining a bit more context about why this is necessary now  or linking to more information ,1
386246,11434264656.0,IssuesEvent,2020-02-04 17:03:56,woocommerce/woocommerce,https://api.github.com/repos/woocommerce/woocommerce,closed,[4.0] Prepare onboarding for the new reality,enhancement has pull request priority: high,"- The old onboarding should stop recommending WooCommerce Admin for WC >= 4
- The new onboarding shouldn't include information about the installation of the plugin
",1.0,"[4.0] Prepare onboarding for the new reality - - The old onboarding should stop recommending WooCommerce Admin for WC >= 4
- The new onboarding shouldn't include information about the installation of the plugin
",0,  prepare onboarding for the new reality     the old onboarding should stop recommending woocommerce admin for wc         the new onboarding shouldn t include information about the installation of the plugin  ,0
40039,9809955324.0,IssuesEvent,2019-06-12 19:15:59,idaholab/moose,https://api.github.com/repos/idaholab/moose,closed,SamplerPostprocessorTransfer becomes slow for large number of samples,T: defect,"## Bug Description
<!--A clear and concise description of the problem.-->
For a large number of samples,  SamplerPostprocessorTransfer becomes very slow to collect results from sub app. It is caused by calling initialize() function for every sample to transfer back data. This should be avoided.  

## Steps to Reproduce
<!--Steps to reproduce the behavior (input file, or modifications to an existing input file, etc.)-->
I tried to run 100000 samples with 20 mpi processes and a significant slow-down after all the sub apps finish was observed.  

## Impact
<!--Does this prevent you from getting your work done, or is it more of an annoyance?-->
It will prevent users from running Monte Carlo simulation with large number of samples. ",1.0,"SamplerPostprocessorTransfer becomes slow for large number of samples - ## Bug Description
<!--A clear and concise description of the problem.-->
For a large number of samples,  SamplerPostprocessorTransfer becomes very slow to collect results from sub app. It is caused by calling initialize() function for every sample to transfer back data. This should be avoided.  

## Steps to Reproduce
<!--Steps to reproduce the behavior (input file, or modifications to an existing input file, etc.)-->
I tried to run 100000 samples with 20 mpi processes and a significant slow-down after all the sub apps finish was observed.  

## Impact
<!--Does this prevent you from getting your work done, or is it more of an annoyance?-->
It will prevent users from running Monte Carlo simulation with large number of samples. ",0,samplerpostprocessortransfer becomes slow for large number of samples      bug description     for a large number of samples   samplerpostprocessortransfer becomes very slow to collect results from sub app  it is caused by calling initialize   function for every sample to transfer back data  this should be avoided          steps to reproduce     i tried to run   samples with   mpi processes and a significant slow down after all the sub apps finish was observed          impact     it will prevent users from running monte carlo simulation with large number of samples  ,0
264491,20022723485.0,IssuesEvent,2022-02-01 17:53:50,golang/go,https://api.github.com/repos/golang/go,closed,spec: document/explain which interfaces implement `comparable`,Documentation,"<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.18beta1 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""on""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/bobg/.cache/go-build""
GOENV=""/home/bobg/.config/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/bobg/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/bobg/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/home/bobg/sdk/go1.18beta1""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/home/bobg/sdk/go1.18beta1/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""go1.18beta1""
GCCGO=""gccgo""
GOAMD64=""v1""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/bobg/go/src/github.com/bobg/modver/go.mod""
GOWORK=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build3923542930=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

https://go.dev/play/p/S-ijx-XOlu8?v=gotip

```go
var (
	anyType        = types.Universe.Lookup(""any"").Type()
	comparableType = types.Universe.Lookup(""comparable"").Type()
)
fmt.Println(types.AssignableTo(comparableType, anyType))
fmt.Println(types.AssignableTo(anyType, comparableType))
```

### What did you expect to see?

true
false

That is, I (naively?) expected the same check that prevents me using non-comparable types as map keys to tell me that I cannot assign a value of an unconstrained type to a variable of a comparable type.

### What did you see instead?

true
true
",1.0,"spec: document/explain which interfaces implement `comparable` - <!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.18beta1 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""on""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/bobg/.cache/go-build""
GOENV=""/home/bobg/.config/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/bobg/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/bobg/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/home/bobg/sdk/go1.18beta1""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/home/bobg/sdk/go1.18beta1/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""go1.18beta1""
GCCGO=""gccgo""
GOAMD64=""v1""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/bobg/go/src/github.com/bobg/modver/go.mod""
GOWORK=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build3923542930=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

https://go.dev/play/p/S-ijx-XOlu8?v=gotip

```go
var (
	anyType        = types.Universe.Lookup(""any"").Type()
	comparableType = types.Universe.Lookup(""comparable"").Type()
)
fmt.Println(types.AssignableTo(comparableType, anyType))
fmt.Println(types.AssignableTo(anyType, comparableType))
```

### What did you expect to see?

true
false

That is, I (naively?) expected the same check that prevents me using non-comparable types as map keys to tell me that I cannot assign a value of an unconstrained type to a variable of a comparable type.

### What did you see instead?

true
true
",1,spec  document explain which interfaces implement  comparable          please answer these questions before submitting your issue  thanks              what version of go are you using   go version            go version  go version     linux             does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env          go env  output       go env     on   goarch      gobin     gocache   home bobg  cache go build   goenv   home bobg  config go env   goexe     goexperiment     goflags     gohostarch      gohostos  linux   goinsecure     gomodcache   home bobg go pkg mod   gonoproxy     gonosumdb     goos  linux   gopath   home bobg go   goprivate     goproxy     goroot   home bobg sdk       gosumdb  sum golang org   gotmpdir     gotooldir   home bobg sdk     pkg tool linux     govcs     goversion        gccgo  gccgo          ar  ar   cc  gcc   cxx  g     cgo enabled      gomod   home bobg go src github com bobg modver go mod   gowork     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches             what did you do             go  var    	anytype          types universe lookup  any   type    	comparabletype   types universe lookup  comparable   type       fmt println types assignableto comparabletype  anytype    fmt println types assignableto anytype  comparabletype               what did you expect to see     true  false    that is  i  naively   expected the same check that prevents me using non comparable types as map keys to tell me that i cannot assign a value of an unconstrained type to a variable of a comparable type         what did you see instead     true  true  ,1
170437,20871373127.0,IssuesEvent,2022-03-22 12:17:48,scm-automation-project/npm-7-with-workspaces-without-lock-file-project,https://api.github.com/repos/scm-automation-project/npm-7-with-workspaces-without-lock-file-project,opened,package-b-1.0.0.tgz: 1 vulnerabilities (highest severity is: 7.5),security vulnerability,"<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>package-b-1.0.0.tgz</b></p></summary>

<p></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/serve-static/node_modules/mime/package.json,/node_modules/express/node_modules/mime/package.json</p>
<p>


<p>Found in HEAD commit: <a href=""https://github.com/scm-automation-project/npm-7-with-workspaces-without-lock-file-project/commit/4c88ce4c4292cb0888aa62df5347d70314dde738"">4c88ce4c4292cb0888aa62df5347d70314dde738</a></p></details>

## Vulnerabilities

| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2017-16138](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16138) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | mime-1.3.4.tgz | Transitive | N/A | &#10060; |


## Details

<details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2017-16138</summary>


###  Vulnerable Library - <b>mime-1.3.4.tgz</b></p>

<p>A comprehensive library for mime-type mapping</p>
<p>Library home page: <a href=""https://registry.npmjs.org/mime/-/mime-1.3.4.tgz"">https://registry.npmjs.org/mime/-/mime-1.3.4.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/serve-static/node_modules/mime/package.json,/node_modules/express/node_modules/mime/package.json</p>
<p>

Dependency Hierarchy:
  - package-b-1.0.0.tgz (Root Library)
    - express-4.15.5.tgz
      - serve-static-1.12.6.tgz
        - send-0.15.6.tgz
          - :x: **mime-1.3.4.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/scm-automation-project/npm-7-with-workspaces-without-lock-file-project/commit/4c88ce4c4292cb0888aa62df5347d70314dde738"">4c88ce4c4292cb0888aa62df5347d70314dde738</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
The mime module < 1.4.1, 2.0.1, 2.0.2 is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input.

<p>Publish Date: 2018-06-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16138>CVE-2017-16138</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138</a></p>
<p>Release Date: 2018-06-07</p>
<p>Fix Resolution: 1.4.1,2.0.3</p>

</p>

<p></p>

</details>
<!-- <REMEDIATE>[{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""mime"",""packageVersion"":""1.3.4"",""packageFilePaths"":[""/package.json""],""isTransitiveDependency"":true,""dependencyTree"":""package-b:1.0.0;express:4.15.5;serve-static:1.12.6;send:0.15.6;mime:1.3.4"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""1.4.1,2.0.3"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2017-16138"",""vulnerabilityDetails"":""The mime module \u003c 1.4.1, 2.0.1, 2.0.2 is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16138"",""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,"package-b-1.0.0.tgz: 1 vulnerabilities (highest severity is: 7.5) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>package-b-1.0.0.tgz</b></p></summary>

<p></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/serve-static/node_modules/mime/package.json,/node_modules/express/node_modules/mime/package.json</p>
<p>


<p>Found in HEAD commit: <a href=""https://github.com/scm-automation-project/npm-7-with-workspaces-without-lock-file-project/commit/4c88ce4c4292cb0888aa62df5347d70314dde738"">4c88ce4c4292cb0888aa62df5347d70314dde738</a></p></details>

## Vulnerabilities

| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2017-16138](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16138) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | mime-1.3.4.tgz | Transitive | N/A | &#10060; |


## Details

<details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2017-16138</summary>


###  Vulnerable Library - <b>mime-1.3.4.tgz</b></p>

<p>A comprehensive library for mime-type mapping</p>
<p>Library home page: <a href=""https://registry.npmjs.org/mime/-/mime-1.3.4.tgz"">https://registry.npmjs.org/mime/-/mime-1.3.4.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/serve-static/node_modules/mime/package.json,/node_modules/express/node_modules/mime/package.json</p>
<p>

Dependency Hierarchy:
  - package-b-1.0.0.tgz (Root Library)
    - express-4.15.5.tgz
      - serve-static-1.12.6.tgz
        - send-0.15.6.tgz
          - :x: **mime-1.3.4.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/scm-automation-project/npm-7-with-workspaces-without-lock-file-project/commit/4c88ce4c4292cb0888aa62df5347d70314dde738"">4c88ce4c4292cb0888aa62df5347d70314dde738</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
The mime module < 1.4.1, 2.0.1, 2.0.2 is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input.

<p>Publish Date: 2018-06-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16138>CVE-2017-16138</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138</a></p>
<p>Release Date: 2018-06-07</p>
<p>Fix Resolution: 1.4.1,2.0.3</p>

</p>

<p></p>

</details>
<!-- <REMEDIATE>[{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""mime"",""packageVersion"":""1.3.4"",""packageFilePaths"":[""/package.json""],""isTransitiveDependency"":true,""dependencyTree"":""package-b:1.0.0;express:4.15.5;serve-static:1.12.6;send:0.15.6;mime:1.3.4"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""1.4.1,2.0.3"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2017-16138"",""vulnerabilityDetails"":""The mime module \u003c 1.4.1, 2.0.1, 2.0.2 is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16138"",""cvss3Severity"":""high"",""cvss3Score"":""7.5"",""cvss3Metrics"":{""A"":""High"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""None"",""AV"":""Network"",""I"":""None""},""extraData"":{}}]</REMEDIATE> -->",0,package b       tgz    vulnerabilities  highest severity is             vulnerable library    package b       tgz         path to dependency file   package json   path to vulnerable library   node modules serve static node modules mime package json  node modules express node modules mime package json       found in head commit   a href        vulnerabilities    cve   severity     cvss   dependency   type   fixed in   remediation available                                                                                   high         mime       tgz   transitive   n a               details        cve             vulnerable library    mime       tgz     a comprehensive library for mime type mapping   library home page   a href     path to dependency file   package json   path to vulnerable library   node modules serve static node modules mime package json  node modules express node modules mime package json     dependency hierarchy      package b       tgz  root library        express       tgz         serve static       tgz           send       tgz              x    mime       tgz    vulnerable library   found in head commit   a href     found in base branch   main               vulnerability details        the mime module                       is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input    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                             istransitivedependency  true  dependencytree   package b       express       serve static       send       mime         isminimumfixversionavailable  true  minimumfixversion                 isbinary  false    basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   the mime module                        is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input    vulnerabilityurl        ,0
21710,4733964745.0,IssuesEvent,2016-10-19 12:57:53,golang/go,https://api.github.com/repos/golang/go,closed,text/template: document redefinition of templates,Documentation NeedsFix,"Go home page, Go 1.7.1.

Package `text/template` and `html/template` provide the same interface. But the documentation of `text/template.Parse()` and `html/template.Parse()` are different.

`text/template.Parse()` leaves out an important fact that it is an error to redefine a non-empty template. `html/template.Parse()` contains this important fact. But they work the same way.

I believe when `{{block}}` action was added in Go 1.6 and redefining of templates got allowed, only the doc of `html/template.Parse()` was updated but not `text/template.Parse()`.

Example code that triggers this error:

    template.Must(template.New("""").Parse(`{{block ""A"" ""a""}}a{{end}}{{define ""A""}}b{{end}}`))

Playground link with `text/template`: https://play.golang.org/p/PY3zLcCFiu

Playground link with `html/template`: https://play.golang.org/p/UeQk4D3tcB",1.0,"text/template: document redefinition of templates - Go home page, Go 1.7.1.

Package `text/template` and `html/template` provide the same interface. But the documentation of `text/template.Parse()` and `html/template.Parse()` are different.

`text/template.Parse()` leaves out an important fact that it is an error to redefine a non-empty template. `html/template.Parse()` contains this important fact. But they work the same way.

I believe when `{{block}}` action was added in Go 1.6 and redefining of templates got allowed, only the doc of `html/template.Parse()` was updated but not `text/template.Parse()`.

Example code that triggers this error:

    template.Must(template.New("""").Parse(`{{block ""A"" ""a""}}a{{end}}{{define ""A""}}b{{end}}`))

Playground link with `text/template`: https://play.golang.org/p/PY3zLcCFiu

Playground link with `html/template`: https://play.golang.org/p/UeQk4D3tcB",1,text template  document redefinition of templates   go home page  go           package  text template  and  html template  provide the same interface  but the documentation of  text template parse    and  html template parse    are different      text template parse    leaves out an important fact that it is an error to redefine a non empty template   html template parse    contains this important fact  but they work the same way     i believe when    block    action was added in go     and redefining of templates got allowed  only the doc of  html template parse    was updated but not  text template parse        example code that triggers this error         template must template new     parse    block  a   a   a  end    define  a   b  end         playground link with  text template        playground link with  html template    ,1
172034,21031059498.0,IssuesEvent,2022-03-31 01:04:01,brogers588/Maven-Prioritize,https://api.github.com/repos/brogers588/Maven-Prioritize,opened,CVE-2022-22950 (Medium) detected in spring-expression-4.2.4.RELEASE.jar,security vulnerability,"## CVE-2022-22950 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-expression-4.2.4.RELEASE.jar</b></p></summary>

<p>Spring Expression Language (SpEL)</p>
<p>Library home page: <a href=""https://github.com/spring-projects/spring-framework"">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-expression/4.2.4.RELEASE/spring-expression-4.2.4.RELEASE.jar</p>
<p>

Dependency Hierarchy:
  - nifi-web-security-1.1.1.jar (Root Library)
    - nifi-administration-1.1.1.jar
      - spring-context-4.2.4.RELEASE.jar
        - :x: **spring-expression-4.2.4.RELEASE.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
In Spring Framework versions 5.3.0 - 5.3.16 and older unsupported versions, it is possible for a user to provide a specially crafted SpEL expression that may cause a denial of service condition

<p>Publish Date: 2022-01-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22950>CVE-2022-22950</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.4</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: Low
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://tanzu.vmware.com/security/cve-2022-22950"">https://tanzu.vmware.com/security/cve-2022-22950</a></p>
<p>Release Date: 2022-01-11</p>
<p>Fix Resolution: org.springframework:spring-expression:5.3.17</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""org.springframework"",""packageName"":""spring-expression"",""packageVersion"":""4.2.4.RELEASE"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.apache.nifi:nifi-web-security:1.1.1;org.apache.nifi:nifi-administration:1.1.1;org.springframework:spring-context:4.2.4.RELEASE;org.springframework:spring-expression:4.2.4.RELEASE"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""org.springframework:spring-expression:5.3.17"",""isBinary"":false}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""CVE-2022-22950"",""vulnerabilityDetails"":""In Spring Framework versions 5.3.0 - 5.3.16 and older unsupported versions, it is possible for a user to provide a specially crafted SpEL expression that may cause a denial of service condition"",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22950"",""cvss3Severity"":""medium"",""cvss3Score"":""5.4"",""cvss3Metrics"":{""A"":""Low"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""Required"",""AV"":""Network"",""I"":""Low""},""extraData"":{}}</REMEDIATE> -->",True,"CVE-2022-22950 (Medium) detected in spring-expression-4.2.4.RELEASE.jar - ## CVE-2022-22950 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-expression-4.2.4.RELEASE.jar</b></p></summary>

<p>Spring Expression Language (SpEL)</p>
<p>Library home page: <a href=""https://github.com/spring-projects/spring-framework"">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-expression/4.2.4.RELEASE/spring-expression-4.2.4.RELEASE.jar</p>
<p>

Dependency Hierarchy:
  - nifi-web-security-1.1.1.jar (Root Library)
    - nifi-administration-1.1.1.jar
      - spring-context-4.2.4.RELEASE.jar
        - :x: **spring-expression-4.2.4.RELEASE.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
In Spring Framework versions 5.3.0 - 5.3.16 and older unsupported versions, it is possible for a user to provide a specially crafted SpEL expression that may cause a denial of service condition

<p>Publish Date: 2022-01-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22950>CVE-2022-22950</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.4</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: Low
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://tanzu.vmware.com/security/cve-2022-22950"">https://tanzu.vmware.com/security/cve-2022-22950</a></p>
<p>Release Date: 2022-01-11</p>
<p>Fix Resolution: org.springframework:spring-expression:5.3.17</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""org.springframework"",""packageName"":""spring-expression"",""packageVersion"":""4.2.4.RELEASE"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.apache.nifi:nifi-web-security:1.1.1;org.apache.nifi:nifi-administration:1.1.1;org.springframework:spring-context:4.2.4.RELEASE;org.springframework:spring-expression:4.2.4.RELEASE"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""org.springframework:spring-expression:5.3.17"",""isBinary"":false}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""CVE-2022-22950"",""vulnerabilityDetails"":""In Spring Framework versions 5.3.0 - 5.3.16 and older unsupported versions, it is possible for a user to provide a specially crafted SpEL expression that may cause a denial of service condition"",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22950"",""cvss3Severity"":""medium"",""cvss3Score"":""5.4"",""cvss3Metrics"":{""A"":""Low"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""Required"",""AV"":""Network"",""I"":""Low""},""extraData"":{}}</REMEDIATE> -->",0,cve      medium  detected in spring expression       release jar      cve       medium severity vulnerability     vulnerable library    spring expression       release jar      spring expression language  spel    library home page   a href     path to dependency file   pom xml   path to vulnerable library   home wss scanner    repository org springframework spring expression       release spring expression       release jar     dependency hierarchy      nifi web security       jar  root library        nifi administration       jar         spring context       release jar            x    spring expression       release jar    vulnerable library   found in base branch   master              vulnerability details         in spring framework versions               and older unsupported versions  it is possible for a user to provide a specially crafted spel expression that may cause a denial of service condition   publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  required     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  low     availability impact  low   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  org springframework spring expression                    isopenpronvulnerability  true  ispackagebased  true  isdefaultbranch  true  packages     istransitivedependency  true  dependencytree   org apache nifi nifi web security       org apache nifi nifi administration       org springframework spring context       release org springframework spring expression       release   isminimumfixversionavailable  true  minimumfixversion   org springframework spring expression         isbinary  false    basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   in spring framework versions               and older unsupported versions  it is possible for a user to provide a specially crafted spel expression that may cause a denial of service condition   vulnerabilityurl        ,0
77999,27271605898.0,IssuesEvent,2023-02-22 22:58:13,idaholab/HERON,https://api.github.com/repos/idaholab/HERON,closed,[DEFECT] Taxes & Inflation flags on recurring cashflows don't do anything,defect priority-critical,"--------
Defect Description
--------

**Describe the defect**

Currently, a user cannot prevent taxes from being applied to a recurring cash flow. According to [`TEAL/src/Cashflows.py#L1127`](https://github.com/idaholab/TEAL/blob/devel/src/CashFlows.py#L1127), any recurring cash flow is automatically taxed by default. 

If a user specifies `taxable=False` on a `<Cashflow>` that is recurring, it will apply the tax rate anyway. 

In HERON, users have the ability to specify if a cash flow is taxed or not, but in the code, we do not actually pass this information on to TEAL. See [`HERON/src/DispatchManager.py#L335-L340`](https://github.com/idaholab/HERON/blob/devel/src/DispatchManager.py#L335)

This becomes an issue, for example, if a user wants to implement a Production Tax Credit (PTC) for a specific resource on a specific component. This is a recurring cash flow that should not be taxed. 

##### What did you expect to see happen?


##### What did you see instead?


##### Do you have a suggested fix for the development team?


**Describe how to Reproduce**
Steps to reproduce the behavior:
1. 
2. 
3. 
4. 

**Screenshots and Input Files**
Please attach the input file(s) that generate this error.  The simpler the input, the faster we can find the issue.

**Platform (please complete the following information):**
 - OS: [e.g. iOS]
 - Version: [e.g. 22]
 - Dependencies Installation: [CONDA or PIP]

----------------
For Change Control Board: Issue Review
----------------
This review should occur before any development is performed as a response to this issue.
- [x] 1. Is it tagged with a type: defect or task?
- [x] 2. Is it tagged with a priority: critical, normal or minor?
- [x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
- [x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
- [x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

-------
For Change Control Board: Issue Closure
-------
This review should occur when the issue is imminently going to be closed.
- [x] 1. If the issue is a defect, is the defect fixed?
- [x] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
- [x] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
- [x] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
- [x] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?
",1.0,"[DEFECT] Taxes & Inflation flags on recurring cashflows don't do anything - --------
Defect Description
--------

**Describe the defect**

Currently, a user cannot prevent taxes from being applied to a recurring cash flow. According to [`TEAL/src/Cashflows.py#L1127`](https://github.com/idaholab/TEAL/blob/devel/src/CashFlows.py#L1127), any recurring cash flow is automatically taxed by default. 

If a user specifies `taxable=False` on a `<Cashflow>` that is recurring, it will apply the tax rate anyway. 

In HERON, users have the ability to specify if a cash flow is taxed or not, but in the code, we do not actually pass this information on to TEAL. See [`HERON/src/DispatchManager.py#L335-L340`](https://github.com/idaholab/HERON/blob/devel/src/DispatchManager.py#L335)

This becomes an issue, for example, if a user wants to implement a Production Tax Credit (PTC) for a specific resource on a specific component. This is a recurring cash flow that should not be taxed. 

##### What did you expect to see happen?


##### What did you see instead?


##### Do you have a suggested fix for the development team?


**Describe how to Reproduce**
Steps to reproduce the behavior:
1. 
2. 
3. 
4. 

**Screenshots and Input Files**
Please attach the input file(s) that generate this error.  The simpler the input, the faster we can find the issue.

**Platform (please complete the following information):**
 - OS: [e.g. iOS]
 - Version: [e.g. 22]
 - Dependencies Installation: [CONDA or PIP]

----------------
For Change Control Board: Issue Review
----------------
This review should occur before any development is performed as a response to this issue.
- [x] 1. Is it tagged with a type: defect or task?
- [x] 2. Is it tagged with a priority: critical, normal or minor?
- [x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
- [x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
- [x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

-------
For Change Control Board: Issue Closure
-------
This review should occur when the issue is imminently going to be closed.
- [x] 1. If the issue is a defect, is the defect fixed?
- [x] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
- [x] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
- [x] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
- [x] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?
",0,  taxes   inflation flags on recurring cashflows don t do anything             defect description                describe the defect      currently  a user cannot prevent taxes from being applied to a recurring cash flow  according to     any recurring cash flow is automatically taxed by default      if a user specifies  taxable false  on a     that is recurring  it will apply the tax rate anyway      in heron  users have the ability to specify if a cash flow is taxed or not  but in the code  we do not actually pass this information on to teal  see        this becomes an issue  for example  if a user wants to implement a production tax credit  ptc  for a specific resource on a specific component  this is a recurring cash flow that should not be taxed            what did you expect to see happen             what did you see instead             do you have a suggested fix for the development team         describe how to reproduce    steps to reproduce the behavior                           screenshots and input files    please attach the input file s  that generate this error   the simpler the input  the faster we can find the issue       platform  please complete the following information         os        version        dependencies installation                         for change control board  issue review                    this review should occur before any development is performed as a response to this issue          is it tagged with a type  defect or task          is it tagged with a priority  critical  normal or minor          if it will impact requirements or requirements tests  is it tagged with requirements          if it is a defect  can it cause wrong results for users  if so an email needs to be sent to the users          is a rationale provided   such as explaining why the improvement is needed or why current code is wrong               for change control board  issue closure           this review should occur when the issue is imminently going to be closed          if the issue is a defect  is the defect fixed          if the issue is a defect  is the defect tested for in the regression test system    if not explain why not           if the issue can impact users  has an email to the users group been written  the email should specify if the defect impacts stable or master           if the issue is a defect  does it impact the latest release branch  if yes  is there any issue tagged with release  create if needed           if the issue is being closed without a pull request  has an explanation of why it is being closed been provided   ,0
10693,3418612338.0,IssuesEvent,2015-12-08 03:22:54,golang/go,https://api.github.com/repos/golang/go,opened,tour: better explanation about type declarations?,Documentation,"Context: https://tour.golang.org/moretypes/2

I just decided to look through the Go tour to see how it explains named types and assignability.  As far as I can tell, the only explanation is the parenthetical sentence ""And a `type` declaration does what you'd expect.""

Based on user questions like issue #13529, I suspect that `type` declarations do *not* necessarily do what users expect, and perhaps it's worth elaborating on this point somehow.",1.0,"tour: better explanation about type declarations? - Context: https://tour.golang.org/moretypes/2

I just decided to look through the Go tour to see how it explains named types and assignability.  As far as I can tell, the only explanation is the parenthetical sentence ""And a `type` declaration does what you'd expect.""

Based on user questions like issue #13529, I suspect that `type` declarations do *not* necessarily do what users expect, and perhaps it's worth elaborating on this point somehow.",1,tour  better explanation about type declarations    context       i just decided to look through the go tour to see how it explains named types and assignability   as far as i can tell  the only explanation is the parenthetical sentence  and a  type  declaration does what you d expect      based on user questions like issue     i suspect that  type  declarations do  not  necessarily do what users expect  and perhaps it s worth elaborating on this point somehow ,1
287182,24815202198.0,IssuesEvent,2022-10-25 12:39:51,hazelcast/hazelcast,https://api.github.com/repos/hazelcast/hazelcast,closed,com.hazelcast.jet.sql_slow.MapIndexScanPMigrationStressTest.stressTest_sorted [HZ-1375],Type: Test-Failure Priority: High Source: Internal Team: SQL Module: Jet to-jira,"_5.0.z_ (commit dce2abb3485d5ccd7658b69d0b5a952031f741bf)

Failed on Sonar build (Oracle JDK 11): https://jenkins.hazelcast.com/view/Official%20Builds/job/Hazelcast-5.maintenance-sonar/40/testReport/com.hazelcast.jet.sql_slow/MapIndexScanPMigrationStressTest/stressTest_sorted/

<details><summary>Stacktrace:</summary>

```
org.junit.runners.model.TestTimedOutException: test timed out after 600000 milliseconds
	at app//org.assertj.core.internal.IterableDiff.iterablesRemoveFirst(IterableDiff.java:73)
	at app//org.assertj.core.internal.IterableDiff.subtract(IterableDiff.java:60)
	at app//org.assertj.core.internal.IterableDiff.<init>(IterableDiff.java:32)
	at app//org.assertj.core.internal.IterableDiff.diff(IterableDiff.java:38)
	at app//org.assertj.core.internal.Iterables.assertContainsExactly(Iterables.java:1082)
	at app//org.assertj.core.api.AbstractIterableAssert.containsExactly(AbstractIterableAssert.java:383)
	at app//org.assertj.core.api.ListAssert.containsExactly(ListAssert.java:270)
	at app//org.assertj.core.api.ListAssert.containsExactly(ListAssert.java:48)
	at app//org.assertj.core.api.AbstractIterableAssert.containsExactlyElementsOf(AbstractIterableAssert.java:1642)
	at app//com.hazelcast.jet.sql_slow.MapIndexScanPMigrationStressTest.assertRowsOrdered(MapIndexScanPMigrationStressTest.java:153)
	at app//com.hazelcast.jet.sql_slow.MapIndexScanPMigrationStressTest.stressTest_sorted(MapIndexScanPMigrationStressTest.java:105)
	at java.base@11.0.13/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base@11.0.13/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base@11.0.13/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base@11.0.13/java.lang.reflect.Method.invoke(Method.java:566)
	at app//org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
	at app//org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at app//org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
	at app//org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at app//com.hazelcast.test.FailOnTimeoutStatement$CallableStatement.call(FailOnTimeoutStatement.java:115)
	at app//com.hazelcast.test.FailOnTimeoutStatement$CallableStatement.call(FailOnTimeoutStatement.java:107)
	at java.base@11.0.13/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base@11.0.13/java.lang.Thread.run(Thread.java:834)
```

</details>

<details><summary>Standard output:</summary>

```
Finished Running Test: stressTest_hash in 174.447 seconds.
Started Running Test: stressTest_sorted
02:12:40,881  INFO |stressTest_sorted| - [MetricsConfigHelper] Time-limited test - [LOCAL] [dev] [5.0.1-SNAPSHOT] Overridden metrics configuration with system property 'hazelcast.metrics.collection.frequency'='1' -> 'MetricsConfig.collectionFrequencySeconds'='1'
02:12:40,882  INFO |stressTest_sorted| - [logo] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] 
	+       +  o    o     o     o---o o----o o      o---o     o     o----o o--o--o
	+ +   + +  |    |    / \       /  |      |     /         / \    |         |   
	+ + + + +  o----o   o   o     o   o----o |    o         o   o   o----o    |   
	+ +   + +  |    |  /     \   /    |      |     \       /     \       |    |   
	+       +  o    o o       o o---o o----o o----o o---o o       o o----o    o   
02:12:40,882  INFO |stressTest_sorted| - [system] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Copyright (c) 2008-2021, Hazelcast, Inc. All Rights Reserved.
02:12:40,882  INFO |stressTest_sorted| - [system] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Hazelcast Platform 5.0.1-SNAPSHOT (20211102 - dce2abb) starting at [127.0.0.1]:5701
02:12:40,882  INFO |stressTest_sorted| - [system] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Cluster name: dev
02:12:40,885  INFO |stressTest_sorted| - [MetricsConfigHelper] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Collecting debug metrics and sending to diagnostics is enabled
02:12:40,888  WARN |stressTest_sorted| - [CPSubsystem] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] CP Subsystem is not enabled. CP data structures will operate in UNSAFE mode! Please note that UNSAFE mode will not provide strong consistency guarantees.
02:12:40,891  INFO |stressTest_sorted| - [JetServiceBackend] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Setting number of cooperative threads and default parallelism to 2
02:12:40,892  INFO |stressTest_sorted| - [Diagnostics] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments.
02:12:40,892  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5701 is STARTING
02:12:40,892  INFO |stressTest_sorted| - [JetExtension] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Jet is enabled
02:12:40,892  INFO |stressTest_sorted| - [ClusterService] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] 

Members {size:1, ver:1} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82 this
]

02:12:40,892 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-1 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:12:40,892  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5701 is STARTED
02:12:40,893  INFO |stressTest_sorted| - [MetricsConfigHelper] Time-limited test - [LOCAL] [dev] [5.0.1-SNAPSHOT] Overridden metrics configuration with system property 'hazelcast.metrics.collection.frequency'='1' -> 'MetricsConfig.collectionFrequencySeconds'='1'
02:12:40,893  INFO |stressTest_sorted| - [logo] Time-limited test - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] 
	+       +  o    o     o     o---o o----o o      o---o     o     o----o o--o--o
	+ +   + +  |    |    / \       /  |      |     /         / \    |         |   
	+ + + + +  o----o   o   o     o   o----o |    o         o   o   o----o    |   
	+ +   + +  |    |  /     \   /    |      |     \       /     \       |    |   
	+       +  o    o o       o o---o o----o o----o o---o o       o o----o    o   
02:12:40,893  INFO |stressTest_sorted| - [system] Time-limited test - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Copyright (c) 2008-2021, Hazelcast, Inc. All Rights Reserved.
02:12:40,893  INFO |stressTest_sorted| - [system] Time-limited test - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Hazelcast Platform 5.0.1-SNAPSHOT (20211102 - dce2abb) starting at [127.0.0.1]:5702
02:12:40,893  INFO |stressTest_sorted| - [system] Time-limited test - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Cluster name: dev
02:12:40,894  INFO |stressTest_sorted| - [HealthMonitor] hz.vibrant_snyder.HealthMonitor - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] processors=8, physical.memory.total=377.6G, physical.memory.free=154.1G, swap.space.total=4.0G, swap.space.free=4.0G, heap.memory.used=306.6M, heap.memory.free=350.4M, heap.memory.total=657.0M, heap.memory.max=2.0G, heap.memory.used/total=46.59%, heap.memory.used/max=14.95%, minor.gc.count=1393, minor.gc.time=10624ms, major.gc.count=0, major.gc.time=0ms, load.process=0.00%, load.system=100.00%, load.systemAverage=12.38, thread.count=45, thread.peakCount=205, cluster.timeDiff=0, event.q.size=0, executor.q.async.size=0, executor.q.client.size=0, executor.q.client.query.size=0, executor.q.client.blocking.size=0, executor.q.query.size=0, executor.q.scheduled.size=0, executor.q.io.size=0, executor.q.system.size=0, executor.q.operations.size=0, executor.q.priorityOperation.size=0, operations.completed.count=0, executor.q.mapLoad.size=0, executor.q.mapLoadAllKeys.size=0, executor.q.cluster.size=0, executor.q.response.size=0, operations.running.count=0, operations.pending.invocations.percentage=0.00%, operations.pending.invocations.count=0, proxy.count=1, clientEndpoint.count=0, connection.active.count=0, client.connection.count=0, connection.count=0
02:12:40,896  INFO |stressTest_sorted| - [MetricsConfigHelper] Time-limited test - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Collecting debug metrics and sending to diagnostics is enabled
02:12:40,899  WARN |stressTest_sorted| - [CPSubsystem] Time-limited test - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] CP Subsystem is not enabled. CP data structures will operate in UNSAFE mode! Please note that UNSAFE mode will not provide strong consistency guarantees.
02:12:40,901  INFO |stressTest_sorted| - [JetServiceBackend] Time-limited test - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Setting number of cooperative threads and default parallelism to 2
02:12:40,903  INFO |stressTest_sorted| - [Diagnostics] Time-limited test - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments.
02:12:40,903  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5702 is STARTING
02:12:40,904  INFO |stressTest_sorted| - [MockServer] Time-limited test - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5701, connection: MockConnection{localEndpoint=[127.0.0.1]:5702, remoteEndpoint=[127.0.0.1]:5701, alive=true}
02:12:40,904  INFO |stressTest_sorted| - [MockServer] hz.vibrant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5702, connection: MockConnection{localEndpoint=[127.0.0.1]:5701, remoteEndpoint=[127.0.0.1]:5702, alive=true}
02:12:40,904  INFO |stressTest_sorted| - [ClusterService] hz.vibrant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] 

Members {size:2, ver:2} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82 this
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd
]

02:12:40,993 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-2 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:12:41,004  INFO |stressTest_sorted| - [JetExtension] hz.flamboyant_snyder.generic-operation.thread-0 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Jet is enabled
02:12:41,005  INFO |stressTest_sorted| - [ClusterService] hz.flamboyant_snyder.generic-operation.thread-0 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] 

Members {size:2, ver:2} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd this
]

02:12:41,093 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-2 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:12:41,193 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-2 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:12:41,293 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-2 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:12:41,393 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-4 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:12:41,404  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5702 is STARTED
02:12:41,406  INFO |stressTest_sorted| - [MetricsConfigHelper] Time-limited test - [LOCAL] [dev] [5.0.1-SNAPSHOT] Overridden metrics configuration with system property 'hazelcast.metrics.collection.frequency'='1' -> 'MetricsConfig.collectionFrequencySeconds'='1'
02:12:41,406  INFO |stressTest_sorted| - [HealthMonitor] hz.flamboyant_snyder.HealthMonitor - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] processors=8, physical.memory.total=377.6G, physical.memory.free=154.1G, swap.space.total=4.0G, swap.space.free=4.0G, heap.memory.used=311.7M, heap.memory.free=345.3M, heap.memory.total=657.0M, heap.memory.max=2.0G, heap.memory.used/total=47.37%, heap.memory.used/max=15.20%, minor.gc.count=1393, minor.gc.time=10624ms, major.gc.count=0, major.gc.time=0ms, load.process=0.00%, load.system=100.00%, load.systemAverage=12.38, thread.count=71, thread.peakCount=205, cluster.timeDiff=0, event.q.size=0, executor.q.async.size=0, executor.q.client.size=0, executor.q.client.query.size=0, executor.q.client.blocking.size=0, executor.q.query.size=0, executor.q.scheduled.size=0, executor.q.io.size=0, executor.q.system.size=0, executor.q.operations.size=0, executor.q.priorityOperation.size=0, operations.completed.count=15, executor.q.mapLoad.size=0, executor.q.mapLoadAllKeys.size=0, executor.q.cluster.size=0, executor.q.response.size=0, operations.running.count=0, operations.pending.invocations.percentage=0.00%, operations.pending.invocations.count=0, proxy.count=1, clientEndpoint.count=0, connection.active.count=0, client.connection.count=0, connection.count=0
02:12:41,406  INFO |stressTest_sorted| - [logo] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] 
	+       +  o    o     o     o---o o----o o      o---o     o     o----o o--o--o
	+ +   + +  |    |    / \       /  |      |     /         / \    |         |   
	+ + + + +  o----o   o   o     o   o----o |    o         o   o   o----o    |   
	+ +   + +  |    |  /     \   /    |      |     \       /     \       |    |   
	+       +  o    o o       o o---o o----o o----o o---o o       o o----o    o   
02:12:41,406  INFO |stressTest_sorted| - [system] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Copyright (c) 2008-2021, Hazelcast, Inc. All Rights Reserved.
02:12:41,406  INFO |stressTest_sorted| - [system] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Hazelcast Platform 5.0.1-SNAPSHOT (20211102 - dce2abb) starting at [127.0.0.1]:5703
02:12:41,406  INFO |stressTest_sorted| - [system] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Cluster name: dev
02:12:41,410  INFO |stressTest_sorted| - [MetricsConfigHelper] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Collecting debug metrics and sending to diagnostics is enabled
02:12:41,414  WARN |stressTest_sorted| - [CPSubsystem] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] CP Subsystem is not enabled. CP data structures will operate in UNSAFE mode! Please note that UNSAFE mode will not provide strong consistency guarantees.
02:12:41,417  INFO |stressTest_sorted| - [JetServiceBackend] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Setting number of cooperative threads and default parallelism to 2
02:12:41,418  INFO |stressTest_sorted| - [Diagnostics] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments.
02:12:41,418  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5703 is STARTING
02:12:41,419  INFO |stressTest_sorted| - [MockServer] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5701, connection: MockConnection{localEndpoint=[127.0.0.1]:5703, remoteEndpoint=[127.0.0.1]:5701, alive=true}
02:12:41,419  INFO |stressTest_sorted| - [MockServer] hz.vibrant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5703, connection: MockConnection{localEndpoint=[127.0.0.1]:5701, remoteEndpoint=[127.0.0.1]:5703, alive=true}
02:12:41,419  INFO |stressTest_sorted| - [ClusterService] hz.vibrant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] 

Members {size:3, ver:3} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82 this
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac
]

02:12:41,420  INFO |stressTest_sorted| - [MockServer] hz.flamboyant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5703, connection: MockConnection{localEndpoint=[127.0.0.1]:5702, remoteEndpoint=[127.0.0.1]:5703, alive=true}
02:12:41,421  INFO |stressTest_sorted| - [ClusterService] hz.flamboyant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] 

Members {size:3, ver:3} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd this
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac
]

02:12:41,493 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-1 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:12:41,519  INFO |stressTest_sorted| - [JetExtension] hz.blissful_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Jet is enabled
02:12:41,520  INFO |stressTest_sorted| - [ClusterService] hz.blissful_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] 

Members {size:3, ver:3} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac this
]

02:12:41,593 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-1 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:12:41,694 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-1 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:12:41,794 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-1 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:12:41,894 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-9 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:12:41,919  INFO |stressTest_sorted| - [MockServer] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5702, connection: MockConnection{localEndpoint=[127.0.0.1]:5703, remoteEndpoint=[127.0.0.1]:5702, alive=true}
02:12:41,919  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5703 is STARTED
02:12:41,921  INFO |stressTest_sorted| - [PartitionStateManager] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Initializing cluster partition table arrangement...
02:12:41,921  INFO |stressTest_sorted| - [HealthMonitor] hz.blissful_snyder.HealthMonitor - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] processors=8, physical.memory.total=377.6G, physical.memory.free=154.1G, swap.space.total=4.0G, swap.space.free=4.0G, heap.memory.used=321.0M, heap.memory.free=336.0M, heap.memory.total=657.0M, heap.memory.max=2.0G, heap.memory.used/total=48.79%, heap.memory.used/max=15.65%, minor.gc.count=1393, minor.gc.time=10624ms, major.gc.count=0, major.gc.time=0ms, load.process=0.00%, load.system=100.00%, load.systemAverage=12.38, thread.count=108, thread.peakCount=205, cluster.timeDiff=0, event.q.size=0, executor.q.async.size=0, executor.q.client.size=0, executor.q.client.query.size=0, executor.q.client.blocking.size=0, executor.q.query.size=0, executor.q.scheduled.size=0, executor.q.io.size=0, executor.q.system.size=0, executor.q.operations.size=0, executor.q.priorityOperation.size=0, operations.completed.count=17, executor.q.mapLoad.size=0, executor.q.mapLoadAllKeys.size=0, executor.q.cluster.size=0, executor.q.response.size=0, operations.running.count=1, operations.pending.invocations.percentage=0.00%, operations.pending.invocations.count=0, proxy.count=1, clientEndpoint.count=0, connection.active.count=0, client.connection.count=0, connection.count=0
02:12:41,995 DEBUG |stressTest_sorted| - [JobRepository] hz.vibrant_snyder.cached.thread-4 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Job cleanup took 0ms
02:12:46,995 DEBUG |stressTest_sorted| - [JobRepository] hz.vibrant_snyder.cached.thread-8 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Job cleanup took 0ms
02:12:51,996 DEBUG |stressTest_sorted| - [JobRepository] hz.vibrant_snyder.cached.thread-2 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Job cleanup took 0ms
02:12:56,997 DEBUG |stressTest_sorted| - [JobRepository] hz.vibrant_snyder.cached.thread-8 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Job cleanup took 0ms
02:13:00,896  INFO |stressTest_sorted| - [HealthMonitor] hz.vibrant_snyder.HealthMonitor - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] processors=8, physical.memory.total=377.6G, physical.memory.free=154.0G, swap.space.total=4.0G, swap.space.free=4.0G, heap.memory.used=303.2M, heap.memory.free=353.8M, heap.memory.total=657.0M, heap.memory.max=2.0G, heap.memory.used/total=45.96%, heap.memory.used/max=14.74%, minor.gc.count=1412, minor.gc.time=10866ms, major.gc.count=0, major.gc.time=0ms, load.process=10.00%, load.system=100.00%, load.systemAverage=12.72, thread.count=117, thread.peakCount=205, cluster.timeDiff=0, event.q.size=0, executor.q.async.size=0, executor.q.client.size=0, executor.q.client.query.size=0, executor.q.client.blocking.size=0, executor.q.query.size=0, executor.q.scheduled.size=0, executor.q.io.size=0, executor.q.system.size=0, executor.q.operations.size=0, executor.q.priorityOperation.size=0, operations.completed.count=218449, executor.q.mapLoad.size=0, executor.q.mapLoadAllKeys.size=0, executor.q.cluster.size=0, executor.q.response.size=0, operations.running.count=0, operations.pending.invocations.percentage=0.00%, operations.pending.invocations.count=0, proxy.count=2, clientEndpoint.count=0, connection.active.count=0, client.connection.count=0, connection.count=0
02:13:01,408  INFO |stressTest_sorted| - [HealthMonitor] hz.flamboyant_snyder.HealthMonitor - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] processors=8, physical.memory.total=377.6G, physical.memory.free=154.0G, swap.space.total=4.0G, swap.space.free=4.0G, heap.memory.used=404.6M, heap.memory.free=252.4M, heap.memory.total=657.0M, heap.memory.max=2.0G, heap.memory.used/total=61.53%, heap.memory.used/max=19.74%, minor.gc.count=1412, minor.gc.time=10866ms, major.gc.count=0, major.gc.time=0ms, load.process=10.00%, load.system=100.00%, load.systemAverage=12.72, thread.count=117, thread.peakCount=205, cluster.timeDiff=-1, event.q.size=0, executor.q.async.size=0, executor.q.client.size=0, executor.q.client.query.size=0, executor.q.client.blocking.size=0, executor.q.query.size=0, executor.q.scheduled.size=0, executor.q.io.size=0, executor.q.system.size=0, executor.q.operations.size=0, executor.q.priorityOperation.size=0, operations.completed.count=167368, executor.q.mapLoad.size=0, executor.q.mapLoadAllKeys.size=0, executor.q.cluster.size=0, executor.q.response.size=0, operations.running.count=0, operations.pending.invocations.percentage=0.00%, operations.pending.invocations.count=0, proxy.count=2, clientEndpoint.count=0, connection.active.count=0, client.connection.count=0, connection.count=0
02:13:01,923  INFO |stressTest_sorted| - [HealthMonitor] hz.blissful_snyder.HealthMonitor - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] processors=8, physical.memory.total=377.6G, physical.memory.free=154.0G, swap.space.total=4.0G, swap.space.free=4.0G, heap.memory.used=527.6M, heap.memory.free=129.4M, heap.memory.total=657.0M, heap.memory.max=2.0G, heap.memory.used/total=80.25%, heap.memory.used/max=25.74%, minor.gc.count=1412, minor.gc.time=10866ms, major.gc.count=0, major.gc.time=0ms, load.process=0.00%, load.system=100.00%, load.systemAverage=12.72, thread.count=117, thread.peakCount=205, cluster.timeDiff=-1, event.q.size=0, executor.q.async.size=0, executor.q.client.size=0, executor.q.client.query.size=0, executor.q.client.blocking.size=0, executor.q.query.size=0, executor.q.scheduled.size=0, executor.q.io.size=0, executor.q.system.size=0, executor.q.operations.size=0, executor.q.priorityOperation.size=0, operations.completed.count=229041, executor.q.mapLoad.size=0, executor.q.mapLoadAllKeys.size=0, executor.q.cluster.size=0, executor.q.response.size=0, operations.running.count=1, operations.pending.invocations.percentage=0.00%, operations.pending.invocations.count=0, proxy.count=2, clientEndpoint.count=0, connection.active.count=0, client.connection.count=0, connection.count=0
02:13:01,997 DEBUG |stressTest_sorted| - [JobRepository] hz.vibrant_snyder.cached.thread-3 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Job cleanup took 0ms
02:13:06,998 DEBUG |stressTest_sorted| - [JobRepository] hz.vibrant_snyder.cached.thread-7 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Job cleanup took 0ms
02:13:11,998 DEBUG |stressTest_sorted| - [JobRepository] hz.vibrant_snyder.cached.thread-14 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Job cleanup took 0ms
02:13:14,848 DEBUG |stressTest_sorted| - [CalciteSqlOptimizer] stressTest_sorted - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Before logical opt:
LogicalSort(sort0=[$1], dir0=[DESC])
  LogicalProject(__key=[$0], this=[$1])
    LogicalTableScan(table=[[hazelcast, public, map[projects=[0, 1]]]])

02:13:14,849 DEBUG |stressTest_sorted| - [CalciteSqlOptimizer] stressTest_sorted - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] After logical opt:
SortLogicalRel(sort0=[$1], dir0=[DESC])
  FullScanLogicalRel(table=[[hazelcast, public, map[projects=[0, 1]]]])

02:13:14,850 DEBUG |stressTest_sorted| - [CalciteSqlOptimizer] stressTest_sorted - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] After physical opt:
IndexScanMapPhysicalRel(table=[[hazelcast, public, map[projects=[0, 1]]]], index=[165c33e1-a26f-4ab6-8286-1f0d1e06f36d], indexExp=[null], remainderExp=[null])

02:13:14,851 DEBUG |stressTest_sorted| - [LightMasterContext] stressTest_sorted - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Start executing light job 070d-2375-7880-0001, execution graph in DOT format:
digraph DAG {
	""Index(IMap[public.map])"" [localParallelism=1];
	""SortCombine"" [localParallelism=1];
	""ClientSink"" [localParallelism=1];
	""Index(IMap[public.map])"" -> ""SortCombine"" [label=""distributed to [127.0.0.1]:5701-partitioned-ordered"", queueSize=1024];
	""SortCombine"" -> ""ClientSink"" [label=""distributed to [127.0.0.1]:5701-partitioned"", queueSize=1024];
}
HINT: You can use graphviz or http://viz-js.com to visualize the printed graph.
02:13:14,851 DEBUG |stressTest_sorted| - [LightMasterContext] stressTest_sorted - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Building execution plan for 070d-2375-7880-0001
02:13:14,851 DEBUG |stressTest_sorted| - [LightMasterContext] stressTest_sorted - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Built execution plans for 070d-2375-7880-0001
02:13:14,852 DEBUG |stressTest_sorted| - [InitExecutionOperation] stressTest_sorted - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Initializing execution plan for job 070d-2375-7880-0001, execution 070d-2375-7880-0001 from [127.0.0.1]:5701
02:13:14,852 DEBUG |stressTest_sorted| - [JobExecutionService] stressTest_sorted - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Execution plan for light job ID=070d-2375-7880-0001, jobName='070d-2375-7880-0001', executionId=070d-2375-7880-0001 initialized, will start the execution
02:13:14,853 DEBUG |stressTest_sorted| - [InitExecutionOperation] hz.blissful_snyder.generic-operation.thread-0 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Initializing execution plan for job 070d-2375-7880-0001, execution 070d-2375-7880-0001 from [127.0.0.1]:5701
02:13:14,853 DEBUG |stressTest_sorted| - [InitExecutionOperation] hz.flamboyant_snyder.generic-operation.thread-0 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Initializing execution plan for job 070d-2375-7880-0001, execution 070d-2375-7880-0001 from [127.0.0.1]:5701
02:13:14,853 DEBUG |stressTest_sorted| - [JobExecutionService] hz.blissful_snyder.generic-operation.thread-0 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Execution plan for light job ID=070d-2375-7880-0001, jobName='070d-2375-7880-0001', executionId=070d-2375-7880-0001 initialized, will start the execution
02:13:14,854 DEBUG |stressTest_sorted| - [JobExecutionService] hz.flamboyant_snyder.generic-operation.thread-0 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Execution plan for light job ID=070d-2375-7880-0001, jobName='070d-2375-7880-0001', executionId=070d-2375-7880-0001 initialized, will start the execution
02:13:14,874  INFO |stressTest_sorted| - [MetricsConfigHelper] Thread-1422 - [LOCAL] [dev] [5.0.1-SNAPSHOT] Overridden metrics configuration with system property 'hazelcast.metrics.collection.frequency'='1' -> 'MetricsConfig.collectionFrequencySeconds'='1'
02:13:14,875  INFO |stressTest_sorted| - [logo] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] 
	+       +  o    o     o     o---o o----o o      o---o     o     o----o o--o--o
	+ +   + +  |    |    / \       /  |      |     /         / \    |         |   
	+ + + + +  o----o   o   o     o   o----o |    o         o   o   o----o    |   
	+ +   + +  |    |  /     \   /    |      |     \       /     \       |    |   
	+       +  o    o o       o o---o o----o o----o o---o o       o o----o    o   
02:13:14,875  INFO |stressTest_sorted| - [system] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Copyright (c) 2008-2021, Hazelcast, Inc. All Rights Reserved.
02:13:14,875  INFO |stressTest_sorted| - [system] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Hazelcast Platform 5.0.1-SNAPSHOT (20211102 - dce2abb) starting at [127.0.0.1]:5704
02:13:14,875  INFO |stressTest_sorted| - [system] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Cluster name: dev
02:13:14,879  INFO |stressTest_sorted| - [MetricsConfigHelper] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Collecting debug metrics and sending to diagnostics is enabled
02:13:14,884  WARN |stressTest_sorted| - [CPSubsystem] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] CP Subsystem is not enabled. CP data structures will operate in UNSAFE mode! Please note that UNSAFE mode will not provide strong consistency guarantees.
02:13:14,888  INFO |stressTest_sorted| - [JetServiceBackend] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Setting number of cooperative threads and default parallelism to 2
02:13:14,890  INFO |stressTest_sorted| - [Diagnostics] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments.
02:13:14,890  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5704 is STARTING
02:13:14,890  INFO |stressTest_sorted| - [MockServer] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5701, connection: MockConnection{localEndpoint=[127.0.0.1]:5704, remoteEndpoint=[127.0.0.1]:5701, alive=true}
02:13:14,891  INFO |stressTest_sorted| - [MockServer] hz.vibrant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5704, connection: MockConnection{localEndpoint=[127.0.0.1]:5701, remoteEndpoint=[127.0.0.1]:5704, alive=true}
02:13:14,891  INFO |stressTest_sorted| - [ClusterService] hz.vibrant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] 

Members {size:4, ver:4} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82 this
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac
	Member [127.0.0.1]:5704 - 6f2e210e-8d29-4e25-a94b-a5324b666501
]

02:13:14,894  INFO |stressTest_sorted| - [MockServer] hz.flamboyant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5704, connection: MockConnection{localEndpoint=[127.0.0.1]:5702, remoteEndpoint=[127.0.0.1]:5704, alive=true}
02:13:14,894  INFO |stressTest_sorted| - [ClusterService] hz.flamboyant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] 

Members {size:4, ver:4} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd this
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac
	Member [127.0.0.1]:5704 - 6f2e210e-8d29-4e25-a94b-a5324b666501
]

02:13:14,894  INFO |stressTest_sorted| - [MockServer] hz.blissful_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5704, connection: MockConnection{localEndpoint=[127.0.0.1]:5703, remoteEndpoint=[127.0.0.1]:5704, alive=true}
02:13:14,894  INFO |stressTest_sorted| - [ClusterService] hz.blissful_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] 

Members {size:4, ver:4} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac this
	Member [127.0.0.1]:5704 - 6f2e210e-8d29-4e25-a94b-a5324b666501
]

02:13:14,993  INFO |stressTest_sorted| - [JetExtension] hz.elastic_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Jet is enabled
02:13:14,994  INFO |stressTest_sorted| - [ClusterService] hz.elastic_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] 

Members {size:4, ver:4} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac
	Member [127.0.0.1]:5704 - 6f2e210e-8d29-4e25-a94b-a5324b666501 this
]

02:13:15,143  INFO |stressTest_sorted| - [MigrationManager] hz.vibrant_snyder.migration - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Repartitioning cluster data. Migration tasks count: 11
02:13:15,144  INFO |stressTest_sorted| - [MockServer] hz.elastic_snyder.partition-operation.thread-1 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5703, connection: MockConnection{localEndpoint=[127.0.0.1]:5704, remoteEndpoint=[127.0.0.1]:5703, alive=true}
02:13:15,144  INFO |stressTest_sorted| - [MockServer] hz.elastic_snyder.partition-operation.thread-0 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5703, connection: MockConnection{localEndpoint=[127.0.0.1]:5704, remoteEndpoint=[127.0.0.1]:5703, alive=true}
02:13:15,144  INFO |stressTest_sorted| - [MockServer] hz.elastic_snyder.partition-operation.thread-0 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5702, connection: MockConnection{localEndpoint=[127.0.0.1]:5704, remoteEndpoint=[127.0.0.1]:5702, alive=true}
02:13:15,403  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5704 is STARTED
02:13:15,405  INFO |stressTest_sorted| - [HealthMonitor] hz.elastic_snyder.HealthMonitor - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] processors=8, physical.memory.total=377.6G, physical.memory.free=154.0G, swap.space.total=4.0G, swap.space.free=4.0G, heap.memory.used=521.0M, heap.memory.free=184.0M, heap.memory.total=705.0M, heap.memory.max=2.0G, heap.memory.used/total=73.81%, heap.memory.used/max=25.41%, minor.gc.count=1428, minor.gc.time=11096ms, major.gc.count=0, major.gc.time=0ms, load.process=6.67%, load.system=100.00%, load.systemAverage=12.26, thread.count=182, thread.peakCount=205, cluster.timeDiff=-2, event.q.size=0, executor.q.async.size=0, executor.q.client.size=0, executor.q.client.query.size=0, executor.q.client.blocking.size=0, executor.q.query.size=0, executor.q.scheduled.size=0, executor.q.io.size=0, executor.q.system.size=0, executor.q.operations.size=0, executor.q.priorityOperation.size=0, operations.completed.count=49, executor.q.mapLoad.size=0, executor.q.mapLoadAllKeys.size=0, executor.q.cluster.size=0, executor.q.response.size=0, operations.running.count=0, operations.pending.invocations.percentage=0.00%, operations.pending.invocations.count=0, proxy.count=3, clientEndpoint.count=0, connection.active.count=0, client.connection.count=0, connection.count=0
02:13:16,407  INFO |stressTest_sorted| - [MigrationManager] hz.vibrant_snyder.migration - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] All migration tasks have been completed. (repartitionTime=Wed Nov 03 02:13:15 UTC 2021, plannedMigrations=11, completedMigrations=11, remainingMigrations=0, totalCompletedMigrations=11, elapsedMigrationOperationTime=6744ms, totalElapsedMigrationOperationTime=6744ms, elapsedDestinationCommitTime=4ms, totalElapsedDestinationCommitTime=4ms, elapsedMigrationTime=6752ms, totalElapsedMigrationTime=6752ms)
02:13:17,403  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5704 is SHUTTING_DOWN
02:13:17,404 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Added a shutting-down member: 6f2e210e-8d29-4e25-a94b-a5324b666501
02:13:17,404  INFO |stressTest_sorted| - [MigrationManager] hz.vibrant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Shutdown request of Member [127.0.0.1]:5704 - 6f2e210e-8d29-4e25-a94b-a5324b666501 is handled
02:13:17,406  INFO |stressTest_sorted| - [MigrationManager] hz.vibrant_snyder.migration - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Repartitioning cluster data. Migration tasks count: 6
02:13:17,724 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-2 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partition replication is not in safe state, but in REPLICA_NOT_SYNC
02:13:17,824 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-2 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because members are shutting down: [6f2e210e-8d29-4e25-a94b-a5324b666501]
02:13:17,924 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-2 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because members are shutting down: [6f2e210e-8d29-4e25-a94b-a5324b666501]
02:13:17,990  INFO |stressTest_sorted| - [MigrationManager] hz.vibrant_snyder.migration - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] All migration tasks have been completed. (repartitionTime=Wed Nov 03 02:13:17 UTC 2021, plannedMigrations=6, completedMigrations=6, remainingMigrations=0, totalCompletedMigrations=17, elapsedMigrationOperationTime=2297ms, totalElapsedMigrationOperationTime=9041ms, elapsedDestinationCommitTime=2ms, totalElapsedDestinationCommitTime=6ms, elapsedMigrationTime=2299ms, totalElapsedMigrationTime=9052ms)
02:13:18,005  INFO |stressTest_sorted| - [Node] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Shutting down connection manager...
02:13:18,005  INFO |stressTest_sorted| - [MockServer] Thread-1422 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Removed connection to endpoint: [127.0.0.1]:5704, connection: MockConnection{localEndpoint=[127.0.0.1]:5703, remoteEndpoint=[127.0.0.1]:5704, alive=false}
02:13:18,005  INFO |stressTest_sorted| - [MockServer] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Removed connection to endpoint: [127.0.0.1]:5703, connection: MockConnection{localEndpoint=[127.0.0.1]:5704, remoteEndpoint=[127.0.0.1]:5703, alive=false}
02:13:18,005  INFO |stressTest_sorted| - [MockServer] Thread-1422 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Removed connection to endpoint: [127.0.0.1]:5704, connection: MockConnection{localEndpoint=[127.0.0.1]:5702, remoteEndpoint=[127.0.0.1]:5704, alive=false}
02:13:18,005  INFO |stressTest_sorted| - [MockServer] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Removed connection to endpoint: [127.0.0.1]:5702, connection: MockConnection{localEndpoint=[127.0.0.1]:5704, remoteEndpoint=[127.0.0.1]:5702, alive=false}
02:13:18,005  INFO |stressTest_sorted| - [MockServer] Thread-1422 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Removed connection to endpoint: [127.0.0.1]:5704, connection: MockConnection{localEndpoint=[127.0.0.1]:5701, remoteEndpoint=[127.0.0.1]:5704, alive=false}
02:13:18,005  INFO |stressTest_sorted| - [MockServer] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Removed connection to endpoint: [127.0.0.1]:5701, connection: MockConnection{localEndpoint=[127.0.0.1]:5704, remoteEndpoint=[127.0.0.1]:5701, alive=false}
02:13:18,005  WARN |stressTest_sorted| - [MembershipManager] Thread-1422 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Member [127.0.0.1]:5704 - 6f2e210e-8d29-4e25-a94b-a5324b666501 is suspected to be dead for reason: Connection manager is stopped on Member [127.0.0.1]:5704 - 6f2e210e-8d29-4e25-a94b-a5324b666501 this
02:13:18,005  WARN |stressTest_sorted| - [MembershipManager] Thread-1422 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Member [127.0.0.1]:5704 - 6f2e210e-8d29-4e25-a94b-a5324b666501 is suspected to be dead for reason: Connection manager is stopped on Member [127.0.0.1]:5704 - 6f2e210e-8d29-4e25-a94b-a5324b666501 this
02:13:18,005  INFO |stressTest_sorted| - [MembershipManager] Thread-1422 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Removing Member [127.0.0.1]:5704 - 6f2e210e-8d29-4e25-a94b-a5324b666501
02:13:18,006  INFO |stressTest_sorted| - [ClusterService] Thread-1422 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] 

Members {size:3, ver:5} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82 this
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac
]

02:13:18,006  INFO |stressTest_sorted| - [TransactionManagerService] hz.vibrant_snyder.cached.thread-2 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Committing/rolling-back live transactions of [127.0.0.1]:5704, UUID: 6f2e210e-8d29-4e25-a94b-a5324b666501
02:13:18,006  INFO |stressTest_sorted| - [TransactionManagerService] hz.blissful_snyder.cached.thread-7 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Committing/rolling-back live transactions of [127.0.0.1]:5704, UUID: 6f2e210e-8d29-4e25-a94b-a5324b666501
02:13:18,006  INFO |stressTest_sorted| - [Node] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Shutting down node engine...
02:13:18,006  INFO |stressTest_sorted| - [ClusterService] hz.flamboyant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] 

Members {size:3, ver:5} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd this
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac
]

02:13:18,006  INFO |stressTest_sorted| - [TransactionManagerService] hz.flamboyant_snyder.cached.thread-8 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Committing/rolling-back live transactions of [127.0.0.1]:5704, UUID: 6f2e210e-8d29-4e25-a94b-a5324b666501
02:13:18,006 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-2 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Removed a shutting-down member: 6f2e210e-8d29-4e25-a94b-a5324b666501, now shuttingDownMembers=[]
02:13:18,006  INFO |stressTest_sorted| - [ClusterService] hz.blissful_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] 

Members {size:3, ver:5} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac this
]

02:13:18,019  INFO |stressTest_sorted| - [MigrationManager] hz.vibrant_snyder.migration - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Partition balance is ok, no need to repartition.
02:13:18,030 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-14 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partition replication is not in safe state, but in MIGRATION_LOCAL
02:13:18,038  INFO |stressTest_sorted| - [NodeExtension] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Destroying node NodeExtension.
02:13:18,039  INFO |stressTest_sorted| - [Node] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Hazelcast Shutdown is completed in 635 ms.
02:13:18,042  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5704 is SHUTDOWN
02:13:18,043  INFO |stressTest_sorted| - [MetricsConfigHelper] Thread-1422 - [LOCAL] [dev] [5.0.1-SNAPSHOT] Overridden metrics configuration with system property 'hazelcast.metrics.collection.frequency'='1' -> 'MetricsConfig.collectionFrequencySeconds'='1'
02:13:18,044  INFO |stressTest_sorted| - [logo] Thread-1422 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] 
	+       +  o    o     o     o---o o----o o      o---o     o     o----o o--o--o
	+ +   + +  |    |    / \       /  |      |     /         / \    |         |   
	+ + + + +  o----o   o   o     o   o----o |    o         o   o   o----o    |   
	+ +   + +  |    |  /     \   /    |      |     \       /     \       |    |   
	+       +  o    o o       o o---o o----o o----o o---o o       o o----o    o   
02:13:18,044  INFO |stressTest_sorted| - [system] Thread-1422 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] Copyright (c) 2008-2021, Hazelcast, Inc. All Rights Reserved.
02:13:18,044  INFO |stressTest_sorted| - [system] Thread-1422 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] Hazelcast Platform 5.0.1-SNAPSHOT (20211102 - dce2abb) starting at [127.0.0.1]:5705
02:13:18,044  INFO |stressTest_sorted| - [system] Thread-1422 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] Cluster name: dev
02:13:18,049  INFO |stressTest_sorted| - [MetricsConfigHelper] Thread-1422 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] Collecting debug metrics and sending to diagnostics is enabled
02:13:18,055  WARN |stressTest_sorted| - [CPSubsystem] Thread-1422 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] CP Subsystem is not enabled. CP data structures will operate in UNSAFE mode! Please note that UNSAFE mode will not provide strong consistency guarantees.
02:13:18,059  INFO |stressTest_sorted| - [JetServiceBackend] Thread-1422 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] Setting number of cooperative threads and default parallelism to 2
02:13:18,061  INFO |stressTest_sorted| - [Diagnostics] Thread-1422 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments.
02:13:18,061  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5705 is STARTING
02:13:18,062  INFO |stressTest_sorted| - [MockServer] Thread-1422 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5701, connection: MockConnection{localEndpoint=[127.0.0.1]:5705, remoteEndpoint=[127.0.0.1]:5701, alive=true}
02:13:18,062  INFO |stressTest_sorted| - [MockServer] hz.vibrant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5705, connection: MockConnection{localEndpoint=[127.0.0.1]:5701, remoteEndpoint=[127.0.0.1]:5705, alive=true}
02:13:18,063  INFO |stressTest_sorted| - [ClusterService] hz.vibrant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] 

Members {size:4, ver:6} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82 this
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac
	Member [127.0.0.1]:5705 - ee18c640-63b5-4090-92dd-7bcff7859d14
]

02:13:18,064  INFO |stressTest_sorted| - [MockServer] hz.flamboyant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5705, connection: MockConnection{localEndpoint=[127.0.0.1]:5702, remoteEndpoint=[127.0.0.1]:5705, alive=true}
02:13:18,064  INFO |stressTest_sorted| - [MockServer] hz.blissful_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5705, connection: MockConnection{localEndpoint=[127.0.0.1]:5703, remoteEndpoint=[127.0.0.1]:5705, alive=true}
02:13:18,064  INFO |stressTest_sorted| - [ClusterService] hz.flamboyant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] 

Members {size:4, ver:6} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd this
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac
	Member [127.0.0.1]:5705 - ee18c640-63b5-4090-92dd-7bcff7859d14
]

02:13:18,064  INFO |stressTest_sorted| - [ClusterService] hz.blissful_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] 

Members {size:4, ver:6} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac this
	Member [127.0.0.1]:5705 - ee18c640-63b5-4090-92dd-7bcff7859d14
]

02:13:18,131 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-5 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partition replication is not in safe state, but in REPLICA_NOT_OWNED
02:13:18,163  INFO |stressTest_sorted| - [JetExtension] hz.stupefied_snyder.generic-operation.thread-0 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] Jet is enabled
02:13:18,163  INFO |stressTest_sorted| - [ClusterService] hz.stupefied_snyder.generic-operation.thread-0 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] 

Members {size:4, ver:6} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac
	Member [127.0.0.1]:5705 - ee18c640-63b5-4090-92dd-7bcff7859d14 this
]

02:13:18,250 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-5 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partition replication is not in safe state, but in REPLICA_NOT_OWNED
02:13:18,314  INFO |stressTest_sorted| - [MigrationManager] hz.vibrant_snyder.migration - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Repartitioning cluster data. Migration tasks count: 11
02:13:18,314  INFO |stressTest_sorted| - [MockServer] hz.stupefied_snyder.partition-operation.thread-1 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5703, connection: MockConnection{localEndpoint=[127.0.0.1]:5705, remoteEndpoint=[127.0.0.1]:5703, alive=true}
02:13:18,314  INFO |stressTest_sorted| - [MockServer] hz.stupefied_snyder.partition-operation.thread-0 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5703, connection: MockConnection{localEndpoint=[127.0.0.1]:5705, remoteEndpoint=[127.0.0.1]:5703, alive=true}
02:13:18,315  INFO |stressTest_sorted| - [MockServer] hz.stupefied_snyder.partition-operation.thread-1 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5702, connection: MockConnection{localEndpoint=[127.0.0.1]:5705, remoteEndpoint=[127.0.0.1]:5702, alive=true}
02:13:18,350 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-5 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partition replication is not in safe state, but in REPLICA_NOT_OWNED
02:13:18,450 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-2 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partition replication is not in safe state, but in REPLICA_NOT_OWNED
02:13:18,550 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-2 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partition replication is not in safe state, but in REPLICA_NOT_OWNED
02:13:18,562  WARN |stressTest_sorted| - [Node] Thread-1422 - [127.
...[truncated 3223507 chars]...
0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:04,191 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-2 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:04,292 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-2 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:04,392 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-2 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:04,492 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-4 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:04,592 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-4 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:04,692 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-4 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:04,793 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-4 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:04,893 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-4 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:04,993 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-9 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:05,093 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-9 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:05,193 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-9 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:05,294 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-9 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:05,395 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-9 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:05,495 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-2 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:05,596 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-2 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:05,697 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-2 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:05,799 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-2 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:05,899 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-2 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:05,992  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5891 is SHUTTING_DOWN
02:23:05,992 DEBUG |stressTest_sorted| - [JobCoordinationService] Thread-1422 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Added a shutting-down member: 3b29e727-e997-4f14-ab7a-75fc5ac6bddb
02:23:06,000  INFO |stressTest_sorted| - [Node] Thread-1422 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Shutting down connection manager...
02:23:06,000  INFO |stressTest_sorted| - [Node] Thread-1422 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Shutting down node engine...
02:23:06,014  INFO |stressTest_sorted| - [NodeExtension] Thread-1422 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Destroying node NodeExtension.
02:23:06,016  INFO |stressTest_sorted| - [Node] Thread-1422 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Hazelcast Shutdown is completed in 24 ms.
02:23:06,016  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5891 is SHUTDOWN
02:23:06,017  INFO |stressTest_sorted| - [MetricsConfigHelper] Thread-1422 - [LOCAL] [dev] [5.0.1-SNAPSHOT] Overridden metrics configuration with system property 'hazelcast.metrics.collection.frequency'='1' -> 'MetricsConfig.collectionFrequencySeconds'='1'
02:23:06,026  INFO |stressTest_sorted| - [logo] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] 
	+       +  o    o     o     o---o o----o o      o---o     o     o----o o--o--o
	+ +   + +  |    |    / \       /  |      |     /         / \    |         |   
	+ + + + +  o----o   o   o     o   o----o |    o         o   o   o----o    |   
	+ +   + +  |    |  /     \   /    |      |     \       /     \       |    |   
	+       +  o    o o       o o---o o----o o----o o---o o       o o----o    o   
02:23:06,026  INFO |stressTest_sorted| - [system] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Copyright (c) 2008-2021, Hazelcast, Inc. All Rights Reserved.
02:23:06,026  INFO |stressTest_sorted| - [system] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Hazelcast Platform 5.0.1-SNAPSHOT (20211102 - dce2abb) starting at [127.0.0.1]:5892
02:23:06,026  INFO |stressTest_sorted| - [system] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Cluster name: dev
02:23:06,032  INFO |stressTest_sorted| - [MetricsConfigHelper] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Collecting debug metrics and sending to diagnostics is enabled
02:23:06,043  WARN |stressTest_sorted| - [CPSubsystem] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] CP Subsystem is not enabled. CP data structures will operate in UNSAFE mode! Please note that UNSAFE mode will not provide strong consistency guarantees.
02:23:06,045  INFO |stressTest_sorted| - [JetServiceBackend] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Setting number of cooperative threads and default parallelism to 2
02:23:06,047  INFO |stressTest_sorted| - [Diagnostics] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments.
02:23:06,047  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5892 is STARTING
02:23:06,047  INFO |stressTest_sorted| - [JetExtension] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Jet is enabled
02:23:06,047  INFO |stressTest_sorted| - [ClusterService] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] 

Members {size:1, ver:1} [
	Member [127.0.0.1]:5892 - a66a08dc-95e2-4089-9f9c-f6df2a9ddb0d this
]

02:23:06,047 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-1 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:06,047  WARN |stressTest_sorted| - [Node] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Config seed port is 5701 and cluster size is 1. Some of the ports seem occupied!
02:23:06,047  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5892 is STARTED
02:23:06,049  INFO |stressTest_sorted| - [HealthMonitor] hz.keen_almeida.HealthMonitor - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] processors=8, physical.memory.total=377.6G, physical.memory.free=157.9G, swap.space.total=4.0G, swap.space.free=4.0G, heap.memory.used=1006.3M, heap.memory.free=506.7M, heap.memory.total=1.5G, heap.memory.max=2.0G, heap.memory.used/total=66.48%, heap.memory.used/max=49.12%, minor.gc.count=2051, minor.gc.time=41249ms, major.gc.count=0, major.gc.time=0ms, load.process=0.00%, load.system=100.00%, load.systemAverage=54.69, thread.count=93, thread.peakCount=207, cluster.timeDiff=0, event.q.size=0, executor.q.async.size=0, executor.q.client.size=0, executor.q.client.query.size=0, executor.q.client.blocking.size=0, executor.q.query.size=0, executor.q.scheduled.size=0, executor.q.io.size=0, executor.q.system.size=0, executor.q.operations.size=0, executor.q.priorityOperation.size=0, operations.completed.count=0, executor.q.mapLoad.size=0, executor.q.mapLoadAllKeys.size=0, executor.q.cluster.size=0, executor.q.response.size=0, operations.running.count=0, operations.pending.invocations.percentage=0.00%, operations.pending.invocations.count=0, proxy.count=1, clientEndpoint.count=0, connection.active.count=0, client.connection.count=0, connection.count=0
02:23:06,147 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-1 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:06,247 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-1 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:06,349 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-2 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:06,449 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-2 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:06,550 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-2 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:06,651 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-2 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:06,751 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-2 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:06,851 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-2 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:06,951 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-2 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:07,224 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-6 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:07,324 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-2 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:07,424 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-2 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:07,524 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-2 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:07,625 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-7 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:07,726 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-7 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:07,826 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-7 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:07,928 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-7 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:08,029 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-7 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:08,048  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5892 is SHUTTING_DOWN
02:23:08,048 DEBUG |stressTest_sorted| - [JobCoordinationService] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Added a shutting-down member: a66a08dc-95e2-4089-9f9c-f6df2a9ddb0d
02:23:08,048  INFO |stressTest_sorted| - [Node] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Shutting down connection manager...
02:23:08,048  INFO |stressTest_sorted| - [Node] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Shutting down node engine...
02:23:08,054  INFO |stressTest_sorted| - [NodeExtension] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Destroying node NodeExtension.
02:23:08,054  INFO |stressTest_sorted| - [Node] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Hazelcast Shutdown is completed in 6 ms.
02:23:08,054  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5892 is SHUTDOWN
02:23:08,055  INFO |stressTest_sorted| - [MetricsConfigHelper] Thread-1422 - [LOCAL] [dev] [5.0.1-SNAPSHOT] Overridden metrics configuration with system property 'hazelcast.metrics.collection.frequency'='1' -> 'MetricsConfig.collectionFrequencySeconds'='1'
02:23:08,056  INFO |stressTest_sorted| - [logo] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] 
	+       +  o    o     o     o---o o----o o      o---o     o     o----o o--o--o
	+ +   + +  |    |    / \       /  |      |     /         / \    |         |   
	+ + + + +  o----o   o   o     o   o----o |    o         o   o   o----o    |   
	+ +   + +  |    |  /     \   /    |      |     \       /     \       |    |   
	+       +  o    o o       o o---o o----o o----o o---o o       o o----o    o   
02:23:08,056  INFO |stressTest_sorted| - [system] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Copyright (c) 2008-2021, Hazelcast, Inc. All Rights Reserved.
02:23:08,056  INFO |stressTest_sorted| - [system] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Hazelcast Platform 5.0.1-SNAPSHOT (20211102 - dce2abb) starting at [127.0.0.1]:5893
02:23:08,056  INFO |stressTest_sorted| - [system] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Cluster name: dev
02:23:08,059  INFO |stressTest_sorted| - [MetricsConfigHelper] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Collecting debug metrics and sending to diagnostics is enabled
02:23:08,063  WARN |stressTest_sorted| - [CPSubsystem] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] CP Subsystem is not enabled. CP data structures will operate in UNSAFE mode! Please note that UNSAFE mode will not provide strong consistency guarantees.
02:23:08,066  INFO |stressTest_sorted| - [JetServiceBackend] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Setting number of cooperative threads and default parallelism to 2
02:23:08,067  INFO |stressTest_sorted| - [Diagnostics] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments.
02:23:08,067  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5893 is STARTING
02:23:08,068  INFO |stressTest_sorted| - [JetExtension] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Jet is enabled
02:23:08,068 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.friendly_almeida.cached.thread-1 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:08,068  INFO |stressTest_sorted| - [ClusterService] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] 

Members {size:1, ver:1} [
	Member [127.0.0.1]:5893 - f228efe1-04ed-4174-a74e-c0c29fca1d16 this
]

02:23:08,068  WARN |stressTest_sorted| - [Node] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Config seed port is 5701 and cluster size is 1. Some of the ports seem occupied!
02:23:08,068  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5893 is STARTED
02:23:08,070  INFO |stressTest_sorted| - [HealthMonitor] hz.friendly_almeida.HealthMonitor - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] processors=8, physical.memory.total=377.6G, physical.memory.free=157.9G, swap.space.total=4.0G, swap.space.free=4.0G, heap.memory.used=937.4M, heap.memory.free=575.6M, heap.memory.total=1.5G, heap.memory.max=2.0G, heap.memory.used/total=61.93%, heap.memory.used/max=45.75%, minor.gc.count=2052, minor.gc.time=41426ms, major.gc.count=0, major.gc.time=0ms, load.process=14.29%, load.system=100.00%, load.systemAverage=54.69, thread.count=93, thread.peakCount=207, cluster.timeDiff=0, event.q.size=0, executor.q.async.size=0, executor.q.client.size=0, executor.q.client.query.size=0, executor.q.client.blocking.size=0, executor.q.query.size=0, executor.q.scheduled.size=0, executor.q.io.size=0, executor.q.system.size=0, executor.q.operations.size=0, executor.q.priorityOperation.size=0, operations.completed.count=0, executor.q.mapLoad.size=0, executor.q.mapLoadAllKeys.size=0, executor.q.cluster.size=0, executor.q.response.size=0, operations.running.count=0, operations.pending.invocations.percentage=0.00%, operations.pending.invocations.count=0, proxy.count=1, clientEndpoint.count=0, connection.active.count=0, client.connection.count=0, connection.count=0
02:23:08,170 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.friendly_almeida.cached.thread-2 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:08,270 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.friendly_almeida.cached.thread-2 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:08,370 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.friendly_almeida.cached.thread-2 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:08,470 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.friendly_almeida.cached.thread-2 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:08,570 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.friendly_almeida.cached.thread-4 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:08,671 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.friendly_almeida.cached.thread-4 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:08,751  INFO |stressTest_sorted| - [ClusterService] hz.blissful_snyder.cached.thread-6 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] 

Members {size:1, ver:378} [
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac this
]

02:23:08,751  INFO |stressTest_sorted| - [MembershipManager] hz.blissful_snyder.cached.thread-6 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Mastership is claimed with: MembersView{version=378, members=[MemberInfo{address=[127.0.0.1]:5703, uuid=6362a347-195b-47ae-9e4c-9419a6abfeac, liteMember=false, memberListJoinVersion=3}]}
02:23:08,771 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.friendly_almeida.cached.thread-4 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:08,871 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.friendly_almeida.cached.thread-4 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:08,971 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.friendly_almeida.cached.thread-4 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:08,978  INFO |stressTest_sorted| - [InternalPartitionService] hz.blissful_snyder.migration - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Fetching partition tables from cluster to determine the most recent one... Local stamp: 507970631642232217
02:23:08,978  INFO |stressTest_sorted| - [InternalPartitionService] hz.blissful_snyder.migration - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Most recent partition table is determined.
02:23:08,978  INFO |stressTest_sorted| - [InternalPartitionService] hz.blissful_snyder.migration - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Applying the most recent of partition state...
02:23:08,978  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Shutting down connection manager...
02:23:08,979  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Shutting down node engine...
02:23:08,981  INFO |stressTest_sorted| - [NodeExtension] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Destroying node NodeExtension.
02:23:08,981  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Hazelcast Shutdown is completed in 5009 ms.
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5703 is SHUTDOWN
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5769 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5769 is SHUTTING_DOWN
02:23:08,981  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5769 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5769 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5769 is SHUTDOWN
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5736 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5736 is SHUTTING_DOWN
02:23:08,981  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5736 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5736 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5736 is SHUTDOWN
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5835 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5835 is SHUTTING_DOWN
02:23:08,981  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5835 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5835 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5835 is SHUTDOWN
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5802 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5802 is SHUTTING_DOWN
02:23:08,981  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5802 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5802 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5802 is SHUTDOWN
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5868 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5868 is SHUTTING_DOWN
02:23:08,981  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5868 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5868 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5868 is SHUTDOWN
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5761 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5761 is SHUTTING_DOWN
02:23:08,981  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5761 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5761 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5761 is SHUTDOWN
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5728 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5728 is SHUTTING_DOWN
02:23:08,981  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5728 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5728 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5728 is SHUTDOWN
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5827 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5827 is SHUTTING_DOWN
02:23:08,981  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5827 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5827 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5827 is SHUTDOWN
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5794 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5794 is SHUTTING_DOWN
02:23:08,981  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5794 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5794 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5794 is SHUTDOWN
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5893 is SHUTTING_DOWN
02:23:08,981 DEBUG |stressTest_sorted| - [JobCoordinationService] Time-limited test - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Added a shutting-down member: f228efe1-04ed-4174-a74e-c0c29fca1d16
02:23:08,981  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Shutting down connection manager...
02:23:08,981  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Shutting down node engine...
02:23:08,983  INFO |stressTest_sorted| - [NodeExtension] Time-limited test - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Destroying node NodeExtension.
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Hazelcast Shutdown is completed in 2 ms.
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5893 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5860 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5860 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5860 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5860 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5860 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5753 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5753 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5753 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5753 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5753 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5720 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5720 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5720 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5720 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5720 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5819 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5819 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5819 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5819 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5819 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5786 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5786 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5786 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5786 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5786 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5885 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5885 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5885 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5885 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5885 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5852 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5852 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5852 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5852 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5852 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5745 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5745 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5745 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5745 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5745 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5712 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5712 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5712 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5712 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5712 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5811 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5811 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5811 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5811 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5811 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5778 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5778 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5778 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5778 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5778 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5877 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5877 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5877 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5877 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5877 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5844 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5844 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5844 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5844 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5844 is SHUTDOWN
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5737 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5737 is SHUTTING_DOWN
02:23:08,984  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5737 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5737 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5737 is SHUTDOWN
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5704 is SHUTTING_DOWN
02:23:08,984  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5704 is SHUTDOWN
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5803 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5803 is SHUTTING_DOWN
02:23:08,984  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5803 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5803 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5803 is SHUTDOWN
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5770 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5770 is SHUTTING_DOWN
02:23:08,984  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5770 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5770 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5770 is SHUTDOWN
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5869 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5869 is SHUTTING_DOWN
02:23:08,984  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5869 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5869 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5869 is SHUTDOWN
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5836 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5836 is SHUTTING_DOWN
02:23:08,984  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5836 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5836 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5836 is SHUTDOWN
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5886 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5886 is SHUTTING_DOWN
02:23:08,984  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5886 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5886 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5886 is SHUTDOWN
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5729 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5729 is SHUTTING_DOWN
02:23:08,984  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5729 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5729 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5729 is SHUTDOWN
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5795 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5795 is SHUTTING_DOWN
02:23:08,984  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5795 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5795 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5795 is SHUTDOWN
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5762 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5762 is SHUTTING_DOWN
02:23:08,984  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5762 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5762 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5762 is SHUTDOWN
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5861 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5861 is SHUTTING_DOWN
02:23:08,984  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5861 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5861 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5861 is SHUTDOWN
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5828 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5828 is SHUTTING_DOWN
02:23:08,984  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5828 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5828 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5828 is SHUTDOWN
BuildInfo right after stressTest_sorted(com.hazelcast.jet.sql_slow.MapIndexScanPMigrationStressTest): BuildInfo{version='5.0.1-SNAPSHOT', build='20211102', buildNumber=20211102, revision=dce2abb, enterprise=false, serializationVersion=1}
Hiccups measured while running test 'stressTest_sorted(com.hazelcast.jet.sql_slow.MapIndexScanPMigrationStressTest):'
02:12:40, accumulated pauses: 74 ms, max pause: 17 ms, pauses over 1000 ms: 0
02:12:45, accumulated pauses: 101 ms, max pause: 26 ms, pauses over 1000 ms: 0
02:12:50, accumulated pauses: 90 ms, max pause: 17 ms, pauses over 1000 ms: 0
02:12:55, accumulated pauses: 89 ms, max pause: 21 ms, pauses over 1000 ms: 0
02:13:00, accumulated pauses: 124 ms, max pause: 21 ms, pauses over 1000 ms: 0
02:13:05, accumulated pauses: 93 ms, max pause: 28 ms, pauses over 1000 ms: 0
02:13:10, accumulated pauses: 126 ms, max pause: 19 ms, pauses over 1000 ms: 0
02:13:15, accumulated pauses: 403 ms, max pause: 96 ms, pauses over 1000 ms: 0
02:13:20, accumulated pauses: 325 ms, max pause: 72 ms, pauses over 1000 ms: 0
02:13:25, accumulated pauses: 318 ms, max pause: 75 ms, pauses over 1000 ms: 0
02:13:30, accumulated pauses: 331 ms, max pause: 53 ms, pauses over 1000 ms: 0
02:13:35, accumulated pauses: 224 ms, max pause: 54 ms, pauses over 1000 ms: 0
02:13:40, accumulated pauses: 289 ms, max pause: 52 ms, pauses over 1000 ms: 0
02:13:45, accumulated pauses: 240 ms, max pause: 59 ms, pauses over 1000 ms: 0
02:13:50, accumulated pauses: 310 ms, max pause: 51 ms, pauses over 1000 ms: 0
02:13:55, accumulated pauses: 203 ms, max pause: 58 ms, pauses over 1000 ms: 0
02:14:00, accumulated pauses: 277 ms, max pause: 50 ms, pauses over 1000 ms: 0
02:14:05, accumulated pauses: 275 ms, max pause: 53 ms, pauses over 1000 ms: 0
02:14:10, accumulated pauses: 233 ms, max pause: 50 ms, pauses over 1000 ms: 0
02:14:15, accumulated pauses: 313 ms, max pause: 50 ms, pauses over 1000 ms: 0
02:14:20, accumulated pauses: 228 ms, max pause: 46 ms, pauses over 1000 ms: 0
02:14:25, accumulated pauses: 296 ms, max pause: 44 ms, pauses over 1000 ms: 0
02:14:30, accumulated pauses: 299 ms, max pause: 57 ms, pauses over 1000 ms: 0
02:14:35, accumulated pauses: 252 ms, max pause: 52 ms, pauses over 1000 ms: 0
02:14:40, accumulated pauses: 270 ms, max pause: 52 ms, pauses over 1000 ms: 0
02:14:45, accumulated pauses: 282 ms, max pause: 55 ms, pauses over 1000 ms: 0
02:14:50, accumulated pauses: 295 ms, max pause: 58 ms, pauses over 1000 ms: 0
02:14:55, accumulated pauses: 259 ms, max pause: 64 ms, pauses over 1000 ms: 0
02:15:00, accumulated pauses: 332 ms, max pause: 70 ms, pauses over 1000 ms: 0
02:15:05, accumulated pauses: 255 ms, max pause: 54 ms, pauses over 1000 ms: 0
02:15:10, accumulated pauses: 278 ms, max pause: 53 ms, pauses over 1000 ms: 0
02:15:15, accumulated pauses: 300 ms, max pause: 60 ms, pauses over 1000 ms: 0
02:15:20, accumulated pauses: 259 ms, max pause: 45 ms, pauses over 1000 ms: 0
02:15:25, accumulated pauses: 258 ms, max pause: 46 ms, pauses over 1000 ms: 0
02:15:30, accumulated pauses: 209 ms, max pause: 48 ms, pauses over 1000 ms: 0
02:15:35, accumulated pauses: 286 ms, max pause: 50 ms, pauses over 1000 ms: 0
02:15:40, accumulated pauses: 299 ms, max pause: 52 ms, pauses over 1000 ms: 0
02:15:45, accumulated pauses: 261 ms, max pause: 60 ms, pauses over 1000 ms: 0
02:15:50, accumulated pauses: 198 ms, max pause: 38 ms, pauses over 1000 ms: 0
02:15:55, accumulated pauses: 348 ms, max pause: 52 ms, pauses over 1000 ms: 0
02:16:00, accumulated pauses: 257 ms, max pause: 65 ms, pauses over 1000 ms: 0
02:16:05, accumulated pauses: 233 ms, max pause: 48 ms, pauses over 1000 ms: 0
02:16:10, accumulated pauses: 279 ms, max pause: 61 ms, pauses over 1000 ms: 0
02:16:15, accumulated pauses: 257 ms, max pause: 64 ms, pauses over 1000 ms: 0
02:16:20, accumulated pauses: 292 ms, max pause: 58 ms, pauses over 1000 ms: 0
02:16:25, accumulated pauses: 235 ms, max pause: 60 ms, pauses over 1000 ms: 0
02:16:30, accumulated pauses: 215 ms, max pause: 68 ms, pauses over 1000 ms: 0
02:16:35, accumulated pauses: 354 ms, max pause: 60 ms, pauses over 1000 ms: 0
02:16:40, accumulated pauses: 257 ms, max pause: 55 ms, pauses over 1000 ms: 0
02:16:45, accumulated pauses: 207 ms, max pause: 52 ms, pauses over 1000 ms: 0
02:16:50, accumulated pauses: 313 ms, max pause: 60 ms, pauses over 1000 ms: 0
02:16:55, accumulated pauses: 303 ms, max pause: 59 ms, pauses over 1000 ms: 0
02:17:00, accumulated pauses: 221 ms, max pause: 52 ms, pauses over 1000 ms: 0
02:17:05, accumulated pauses: 288 ms, max pause: 83 ms, pauses over 1000 ms: 0
02:17:10, accumulated pauses: 262 ms, max pause: 67 ms, pauses over 1000 ms: 0
02:17:15, accumulated pauses: 268 ms, max pause: 56 ms, pauses over 1000 ms: 0
02:17:20, accumulated pauses: 252 ms, max pause: 57 ms, pauses over 1000 ms: 0
02:17:25, accumulated pauses: 221 ms, max pause: 59 ms, pauses over 1000 ms: 0
02:17:30, accumulated pauses: 291 ms, max pause: 57 ms, pauses over 1000 ms: 0
02:17:35, accumulated pauses: 283 ms, max pause: 62 ms, pauses over 1000 ms: 0
02:17:40, accumulated pauses: 202 ms, max pause: 52 ms, pauses over 1000 ms: 0
02:17:45, accumulated pauses: 337 ms, max pause: 60 ms, pauses over 1000 ms: 0
02:17:50, accumulated pauses: 232 ms, max pause: 49 ms, pauses over 1000 ms: 0
02:17:55, accumulated pauses: 247 ms, max pause: 57 ms, pauses over 1000 ms: 0
02:18:00, accumulated pauses: 308 ms, max pause: 68 ms, pauses over 1000 ms: 0
02:18:05, accumulated pauses: 234 ms, max pause: 51 ms, pauses over 1000 ms: 0
02:18:10, accumulated pauses: 212 ms, max pause: 55 ms, pauses over 1000 ms: 0
02:18:15, accumulated pauses: 328 ms, max pause: 63 ms, pauses over 1000 ms: 0
02:18:20, accumulated pauses: 287 ms, max pause: 57 ms, pauses over 1000 ms: 0
02:18:25, accumulated pauses: 208 ms, max pause: 57 ms, pauses over 1000 ms: 0
02:18:30, accumulated pauses: 255 ms, max pause: 53 ms, pauses over 1000 ms: 0
02:18:35, accumulated pauses: 259 ms, max pause: 50 ms, pauses over 1000 ms: 0
02:18:40, accumulated pauses: 200 ms, max pause: 45 ms, pauses over 1000 ms: 0
02:18:45, accumulated pauses: 270 ms, max pause: 50 ms, pauses over 1000 ms: 0
02:18:50, accumulated pauses: 289 ms, max pause: 53 ms, pauses over 1000 ms: 0
02:18:55, accumulated pauses: 245 ms, max pause: 39 ms, pauses over 1000 ms: 0
02:19:00, accumulated pauses: 249 ms, max pause: 52 ms, pauses over 1000 ms: 0
02:19:05, accumulated pauses: 317 ms, max pause: 64 ms, pauses over 1000 ms: 0
02:19:10, accumulated pauses: 219 ms, max pause: 50 ms, pauses over 1000 ms: 0
02:19:15, accumulated pauses: 265 ms, max pause: 50 ms, pauses over 1000 ms: 0
02:19:20, accumulated pauses: 371 ms, max pause: 48 ms, pauses over 1000 ms: 0
02:19:25, accumulated pauses: 245 ms, max pause: 58 ms, pauses over 1000 ms: 0
02:19:30, accumulated pauses: 207 ms, max pause: 55 ms, pauses over 1000 ms: 0
02:19:35, accumulated pauses: 318 ms, max pause: 58 ms, pauses over 1000 ms: 0
02:19:40, accumulated pauses: 203 ms, max pause: 51 ms, pauses over 1000 ms: 0
02:19:45, accumulated pauses: 313 ms, max pause: 58 ms, pauses over 1000 ms: 0
02:19:50, accumulated pauses: 269 ms, max pause: 55 ms, pauses over 1000 ms: 0
02:19:55, accumulated pauses: 192 ms, max pause: 53 ms, pauses over 1000 ms: 0
02:20:00, accumulated pauses: 308 ms, max pause: 57 ms, pauses over 1000 ms: 0
02:20:05, accumulated pauses: 272 ms, max pause: 45 ms, pauses over 1000 ms: 0
02:20:10, accumulated pauses: 209 ms, max pause: 51 ms, pauses over 1000 ms: 0
02:20:15, accumulated pauses: 368 ms, max pause: 64 ms, pauses over 1000 ms: 0
02:20:20, accumulated pauses: 286 ms, max pause: 81 ms, pauses over 1000 ms: 0
02:20:25, accumulated pauses: 269 ms, max pause: 53 ms, pauses over 1000 ms: 0
02:20:30, accumulated pauses: 287 ms, max pause: 58 ms, pauses over 1000 ms: 0
02:20:35, accumulated pauses: 214 ms, max pause: 55 ms, pauses over 1000 ms: 0
02:20:40, accumulated pauses: 245 ms, max pause: 60 ms, pauses over 1000 ms: 0
02:20:45, accumulated pauses: 316 ms, max pause: 51 ms, pauses over 1000 ms: 0
02:20:50, accumulated pauses: 194 ms, max pause: 59 ms, pauses over 1000 ms: 0
02:20:55, accumulated pauses: 285 ms, max pause: 68 ms, pauses over 1000 ms: 0
02:21:00, accumulated pauses: 319 ms, max pause: 55 ms, pauses over 1000 ms: 0
02:21:05, accumulated pauses: 251 ms, max pause: 58 ms, pauses over 1000 ms: 0
02:21:10, accumulated pauses: 255 ms, max pause: 61 ms, pauses over 1000 ms: 0
02:21:15, accumulated pauses: 274 ms, max pause: 68 ms, pauses over 1000 ms: 0
02:21:20, accumulated pauses: 217 ms, max pause: 35 ms, pauses over 1000 ms: 0
02:21:25, accumulated pauses: 320 ms, max pause: 56 ms, pauses over 1000 ms: 0
02:21:30, accumulated pauses: 248 ms, max pause: 50 ms, pauses over 1000 ms: 0
02:21:35, accumulated pauses: 382 ms, max pause: 95 ms, pauses over 1000 ms: 0
02:21:40, accumulated pauses: 382 ms, max pause: 55 ms, pauses over 1000 ms: 0
02:21:45, accumulated pauses: 764 ms, max pause: 122 ms, pauses over 1000 ms: 0
02:21:50, accumulated pauses: 659 ms, max pause: 116 ms, pauses over 1000 ms: 0
02:21:55, accumulated pauses: 491 ms, max pause: 93 ms, pauses over 1000 ms: 0
02:22:00, accumulated pauses: 747 ms, max pause: 271 ms, pauses over 1000 ms: 0
02:22:05, accumulated pauses: 346 ms, max pause: 73 ms, pauses over 1000 ms: 0
02:22:10, accumulated pauses: 339 ms, max pause: 63 ms, pauses over 1000 ms: 0
02:22:15, accumulated pauses: 780 ms, max pause: 182 ms, pauses over 1000 ms: 0
02:22:20, accumulated pauses: 793 ms, max pause: 168 ms, pauses over 1000 ms: 0
02:22:25, accumulated pauses: 600 ms, max pause: 124 ms, pauses over 1000 ms: 0
02:22:30, accumulated pauses: 391 ms, max pause: 140 ms, pauses over 1000 ms: 0
02:22:35, accumulated pauses: 381 ms, max pause: 64 ms, pauses over 1000 ms: 0
02:22:40, accumulated pauses: 1295 ms, max pause: 610 ms, pauses over 1000 ms: 0
02:22:45, accumulated pauses: 1272 ms, max pause: 310 ms, pauses over 1000 ms: 0
02:22:50, accumulated pauses: 842 ms, max pause: 327 ms, pauses over 1000 ms: 0
02:22:55, accumulated pauses: 630 ms, max pause: 263 ms, pauses over 1000 ms: 0
02:23:00, accumulated pauses: 268 ms, max pause: 126 ms, pauses over 1000 ms: 0
02:23:05, accumulated pauses: 284 ms, max pause: 175 ms, pauses over 1000 ms: 0
```

</details>
",1.0,"com.hazelcast.jet.sql_slow.MapIndexScanPMigrationStressTest.stressTest_sorted [HZ-1375] - _5.0.z_ (commit dce2abb3485d5ccd7658b69d0b5a952031f741bf)

Failed on Sonar build (Oracle JDK 11): https://jenkins.hazelcast.com/view/Official%20Builds/job/Hazelcast-5.maintenance-sonar/40/testReport/com.hazelcast.jet.sql_slow/MapIndexScanPMigrationStressTest/stressTest_sorted/

<details><summary>Stacktrace:</summary>

```
org.junit.runners.model.TestTimedOutException: test timed out after 600000 milliseconds
	at app//org.assertj.core.internal.IterableDiff.iterablesRemoveFirst(IterableDiff.java:73)
	at app//org.assertj.core.internal.IterableDiff.subtract(IterableDiff.java:60)
	at app//org.assertj.core.internal.IterableDiff.<init>(IterableDiff.java:32)
	at app//org.assertj.core.internal.IterableDiff.diff(IterableDiff.java:38)
	at app//org.assertj.core.internal.Iterables.assertContainsExactly(Iterables.java:1082)
	at app//org.assertj.core.api.AbstractIterableAssert.containsExactly(AbstractIterableAssert.java:383)
	at app//org.assertj.core.api.ListAssert.containsExactly(ListAssert.java:270)
	at app//org.assertj.core.api.ListAssert.containsExactly(ListAssert.java:48)
	at app//org.assertj.core.api.AbstractIterableAssert.containsExactlyElementsOf(AbstractIterableAssert.java:1642)
	at app//com.hazelcast.jet.sql_slow.MapIndexScanPMigrationStressTest.assertRowsOrdered(MapIndexScanPMigrationStressTest.java:153)
	at app//com.hazelcast.jet.sql_slow.MapIndexScanPMigrationStressTest.stressTest_sorted(MapIndexScanPMigrationStressTest.java:105)
	at java.base@11.0.13/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base@11.0.13/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base@11.0.13/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base@11.0.13/java.lang.reflect.Method.invoke(Method.java:566)
	at app//org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
	at app//org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at app//org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
	at app//org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at app//com.hazelcast.test.FailOnTimeoutStatement$CallableStatement.call(FailOnTimeoutStatement.java:115)
	at app//com.hazelcast.test.FailOnTimeoutStatement$CallableStatement.call(FailOnTimeoutStatement.java:107)
	at java.base@11.0.13/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base@11.0.13/java.lang.Thread.run(Thread.java:834)
```

</details>

<details><summary>Standard output:</summary>

```
Finished Running Test: stressTest_hash in 174.447 seconds.
Started Running Test: stressTest_sorted
02:12:40,881  INFO |stressTest_sorted| - [MetricsConfigHelper] Time-limited test - [LOCAL] [dev] [5.0.1-SNAPSHOT] Overridden metrics configuration with system property 'hazelcast.metrics.collection.frequency'='1' -> 'MetricsConfig.collectionFrequencySeconds'='1'
02:12:40,882  INFO |stressTest_sorted| - [logo] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] 
	+       +  o    o     o     o---o o----o o      o---o     o     o----o o--o--o
	+ +   + +  |    |    / \       /  |      |     /         / \    |         |   
	+ + + + +  o----o   o   o     o   o----o |    o         o   o   o----o    |   
	+ +   + +  |    |  /     \   /    |      |     \       /     \       |    |   
	+       +  o    o o       o o---o o----o o----o o---o o       o o----o    o   
02:12:40,882  INFO |stressTest_sorted| - [system] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Copyright (c) 2008-2021, Hazelcast, Inc. All Rights Reserved.
02:12:40,882  INFO |stressTest_sorted| - [system] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Hazelcast Platform 5.0.1-SNAPSHOT (20211102 - dce2abb) starting at [127.0.0.1]:5701
02:12:40,882  INFO |stressTest_sorted| - [system] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Cluster name: dev
02:12:40,885  INFO |stressTest_sorted| - [MetricsConfigHelper] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Collecting debug metrics and sending to diagnostics is enabled
02:12:40,888  WARN |stressTest_sorted| - [CPSubsystem] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] CP Subsystem is not enabled. CP data structures will operate in UNSAFE mode! Please note that UNSAFE mode will not provide strong consistency guarantees.
02:12:40,891  INFO |stressTest_sorted| - [JetServiceBackend] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Setting number of cooperative threads and default parallelism to 2
02:12:40,892  INFO |stressTest_sorted| - [Diagnostics] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments.
02:12:40,892  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5701 is STARTING
02:12:40,892  INFO |stressTest_sorted| - [JetExtension] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Jet is enabled
02:12:40,892  INFO |stressTest_sorted| - [ClusterService] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] 

Members {size:1, ver:1} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82 this
]

02:12:40,892 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-1 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:12:40,892  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5701 is STARTED
02:12:40,893  INFO |stressTest_sorted| - [MetricsConfigHelper] Time-limited test - [LOCAL] [dev] [5.0.1-SNAPSHOT] Overridden metrics configuration with system property 'hazelcast.metrics.collection.frequency'='1' -> 'MetricsConfig.collectionFrequencySeconds'='1'
02:12:40,893  INFO |stressTest_sorted| - [logo] Time-limited test - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] 
	+       +  o    o     o     o---o o----o o      o---o     o     o----o o--o--o
	+ +   + +  |    |    / \       /  |      |     /         / \    |         |   
	+ + + + +  o----o   o   o     o   o----o |    o         o   o   o----o    |   
	+ +   + +  |    |  /     \   /    |      |     \       /     \       |    |   
	+       +  o    o o       o o---o o----o o----o o---o o       o o----o    o   
02:12:40,893  INFO |stressTest_sorted| - [system] Time-limited test - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Copyright (c) 2008-2021, Hazelcast, Inc. All Rights Reserved.
02:12:40,893  INFO |stressTest_sorted| - [system] Time-limited test - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Hazelcast Platform 5.0.1-SNAPSHOT (20211102 - dce2abb) starting at [127.0.0.1]:5702
02:12:40,893  INFO |stressTest_sorted| - [system] Time-limited test - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Cluster name: dev
02:12:40,894  INFO |stressTest_sorted| - [HealthMonitor] hz.vibrant_snyder.HealthMonitor - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] processors=8, physical.memory.total=377.6G, physical.memory.free=154.1G, swap.space.total=4.0G, swap.space.free=4.0G, heap.memory.used=306.6M, heap.memory.free=350.4M, heap.memory.total=657.0M, heap.memory.max=2.0G, heap.memory.used/total=46.59%, heap.memory.used/max=14.95%, minor.gc.count=1393, minor.gc.time=10624ms, major.gc.count=0, major.gc.time=0ms, load.process=0.00%, load.system=100.00%, load.systemAverage=12.38, thread.count=45, thread.peakCount=205, cluster.timeDiff=0, event.q.size=0, executor.q.async.size=0, executor.q.client.size=0, executor.q.client.query.size=0, executor.q.client.blocking.size=0, executor.q.query.size=0, executor.q.scheduled.size=0, executor.q.io.size=0, executor.q.system.size=0, executor.q.operations.size=0, executor.q.priorityOperation.size=0, operations.completed.count=0, executor.q.mapLoad.size=0, executor.q.mapLoadAllKeys.size=0, executor.q.cluster.size=0, executor.q.response.size=0, operations.running.count=0, operations.pending.invocations.percentage=0.00%, operations.pending.invocations.count=0, proxy.count=1, clientEndpoint.count=0, connection.active.count=0, client.connection.count=0, connection.count=0
02:12:40,896  INFO |stressTest_sorted| - [MetricsConfigHelper] Time-limited test - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Collecting debug metrics and sending to diagnostics is enabled
02:12:40,899  WARN |stressTest_sorted| - [CPSubsystem] Time-limited test - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] CP Subsystem is not enabled. CP data structures will operate in UNSAFE mode! Please note that UNSAFE mode will not provide strong consistency guarantees.
02:12:40,901  INFO |stressTest_sorted| - [JetServiceBackend] Time-limited test - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Setting number of cooperative threads and default parallelism to 2
02:12:40,903  INFO |stressTest_sorted| - [Diagnostics] Time-limited test - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments.
02:12:40,903  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5702 is STARTING
02:12:40,904  INFO |stressTest_sorted| - [MockServer] Time-limited test - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5701, connection: MockConnection{localEndpoint=[127.0.0.1]:5702, remoteEndpoint=[127.0.0.1]:5701, alive=true}
02:12:40,904  INFO |stressTest_sorted| - [MockServer] hz.vibrant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5702, connection: MockConnection{localEndpoint=[127.0.0.1]:5701, remoteEndpoint=[127.0.0.1]:5702, alive=true}
02:12:40,904  INFO |stressTest_sorted| - [ClusterService] hz.vibrant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] 

Members {size:2, ver:2} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82 this
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd
]

02:12:40,993 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-2 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:12:41,004  INFO |stressTest_sorted| - [JetExtension] hz.flamboyant_snyder.generic-operation.thread-0 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Jet is enabled
02:12:41,005  INFO |stressTest_sorted| - [ClusterService] hz.flamboyant_snyder.generic-operation.thread-0 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] 

Members {size:2, ver:2} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd this
]

02:12:41,093 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-2 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:12:41,193 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-2 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:12:41,293 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-2 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:12:41,393 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-4 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:12:41,404  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5702 is STARTED
02:12:41,406  INFO |stressTest_sorted| - [MetricsConfigHelper] Time-limited test - [LOCAL] [dev] [5.0.1-SNAPSHOT] Overridden metrics configuration with system property 'hazelcast.metrics.collection.frequency'='1' -> 'MetricsConfig.collectionFrequencySeconds'='1'
02:12:41,406  INFO |stressTest_sorted| - [HealthMonitor] hz.flamboyant_snyder.HealthMonitor - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] processors=8, physical.memory.total=377.6G, physical.memory.free=154.1G, swap.space.total=4.0G, swap.space.free=4.0G, heap.memory.used=311.7M, heap.memory.free=345.3M, heap.memory.total=657.0M, heap.memory.max=2.0G, heap.memory.used/total=47.37%, heap.memory.used/max=15.20%, minor.gc.count=1393, minor.gc.time=10624ms, major.gc.count=0, major.gc.time=0ms, load.process=0.00%, load.system=100.00%, load.systemAverage=12.38, thread.count=71, thread.peakCount=205, cluster.timeDiff=0, event.q.size=0, executor.q.async.size=0, executor.q.client.size=0, executor.q.client.query.size=0, executor.q.client.blocking.size=0, executor.q.query.size=0, executor.q.scheduled.size=0, executor.q.io.size=0, executor.q.system.size=0, executor.q.operations.size=0, executor.q.priorityOperation.size=0, operations.completed.count=15, executor.q.mapLoad.size=0, executor.q.mapLoadAllKeys.size=0, executor.q.cluster.size=0, executor.q.response.size=0, operations.running.count=0, operations.pending.invocations.percentage=0.00%, operations.pending.invocations.count=0, proxy.count=1, clientEndpoint.count=0, connection.active.count=0, client.connection.count=0, connection.count=0
02:12:41,406  INFO |stressTest_sorted| - [logo] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] 
	+       +  o    o     o     o---o o----o o      o---o     o     o----o o--o--o
	+ +   + +  |    |    / \       /  |      |     /         / \    |         |   
	+ + + + +  o----o   o   o     o   o----o |    o         o   o   o----o    |   
	+ +   + +  |    |  /     \   /    |      |     \       /     \       |    |   
	+       +  o    o o       o o---o o----o o----o o---o o       o o----o    o   
02:12:41,406  INFO |stressTest_sorted| - [system] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Copyright (c) 2008-2021, Hazelcast, Inc. All Rights Reserved.
02:12:41,406  INFO |stressTest_sorted| - [system] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Hazelcast Platform 5.0.1-SNAPSHOT (20211102 - dce2abb) starting at [127.0.0.1]:5703
02:12:41,406  INFO |stressTest_sorted| - [system] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Cluster name: dev
02:12:41,410  INFO |stressTest_sorted| - [MetricsConfigHelper] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Collecting debug metrics and sending to diagnostics is enabled
02:12:41,414  WARN |stressTest_sorted| - [CPSubsystem] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] CP Subsystem is not enabled. CP data structures will operate in UNSAFE mode! Please note that UNSAFE mode will not provide strong consistency guarantees.
02:12:41,417  INFO |stressTest_sorted| - [JetServiceBackend] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Setting number of cooperative threads and default parallelism to 2
02:12:41,418  INFO |stressTest_sorted| - [Diagnostics] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments.
02:12:41,418  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5703 is STARTING
02:12:41,419  INFO |stressTest_sorted| - [MockServer] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5701, connection: MockConnection{localEndpoint=[127.0.0.1]:5703, remoteEndpoint=[127.0.0.1]:5701, alive=true}
02:12:41,419  INFO |stressTest_sorted| - [MockServer] hz.vibrant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5703, connection: MockConnection{localEndpoint=[127.0.0.1]:5701, remoteEndpoint=[127.0.0.1]:5703, alive=true}
02:12:41,419  INFO |stressTest_sorted| - [ClusterService] hz.vibrant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] 

Members {size:3, ver:3} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82 this
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac
]

02:12:41,420  INFO |stressTest_sorted| - [MockServer] hz.flamboyant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5703, connection: MockConnection{localEndpoint=[127.0.0.1]:5702, remoteEndpoint=[127.0.0.1]:5703, alive=true}
02:12:41,421  INFO |stressTest_sorted| - [ClusterService] hz.flamboyant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] 

Members {size:3, ver:3} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd this
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac
]

02:12:41,493 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-1 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:12:41,519  INFO |stressTest_sorted| - [JetExtension] hz.blissful_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Jet is enabled
02:12:41,520  INFO |stressTest_sorted| - [ClusterService] hz.blissful_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] 

Members {size:3, ver:3} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac this
]

02:12:41,593 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-1 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:12:41,694 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-1 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:12:41,794 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-1 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:12:41,894 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-9 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:12:41,919  INFO |stressTest_sorted| - [MockServer] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5702, connection: MockConnection{localEndpoint=[127.0.0.1]:5703, remoteEndpoint=[127.0.0.1]:5702, alive=true}
02:12:41,919  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5703 is STARTED
02:12:41,921  INFO |stressTest_sorted| - [PartitionStateManager] Time-limited test - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Initializing cluster partition table arrangement...
02:12:41,921  INFO |stressTest_sorted| - [HealthMonitor] hz.blissful_snyder.HealthMonitor - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] processors=8, physical.memory.total=377.6G, physical.memory.free=154.1G, swap.space.total=4.0G, swap.space.free=4.0G, heap.memory.used=321.0M, heap.memory.free=336.0M, heap.memory.total=657.0M, heap.memory.max=2.0G, heap.memory.used/total=48.79%, heap.memory.used/max=15.65%, minor.gc.count=1393, minor.gc.time=10624ms, major.gc.count=0, major.gc.time=0ms, load.process=0.00%, load.system=100.00%, load.systemAverage=12.38, thread.count=108, thread.peakCount=205, cluster.timeDiff=0, event.q.size=0, executor.q.async.size=0, executor.q.client.size=0, executor.q.client.query.size=0, executor.q.client.blocking.size=0, executor.q.query.size=0, executor.q.scheduled.size=0, executor.q.io.size=0, executor.q.system.size=0, executor.q.operations.size=0, executor.q.priorityOperation.size=0, operations.completed.count=17, executor.q.mapLoad.size=0, executor.q.mapLoadAllKeys.size=0, executor.q.cluster.size=0, executor.q.response.size=0, operations.running.count=1, operations.pending.invocations.percentage=0.00%, operations.pending.invocations.count=0, proxy.count=1, clientEndpoint.count=0, connection.active.count=0, client.connection.count=0, connection.count=0
02:12:41,995 DEBUG |stressTest_sorted| - [JobRepository] hz.vibrant_snyder.cached.thread-4 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Job cleanup took 0ms
02:12:46,995 DEBUG |stressTest_sorted| - [JobRepository] hz.vibrant_snyder.cached.thread-8 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Job cleanup took 0ms
02:12:51,996 DEBUG |stressTest_sorted| - [JobRepository] hz.vibrant_snyder.cached.thread-2 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Job cleanup took 0ms
02:12:56,997 DEBUG |stressTest_sorted| - [JobRepository] hz.vibrant_snyder.cached.thread-8 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Job cleanup took 0ms
02:13:00,896  INFO |stressTest_sorted| - [HealthMonitor] hz.vibrant_snyder.HealthMonitor - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] processors=8, physical.memory.total=377.6G, physical.memory.free=154.0G, swap.space.total=4.0G, swap.space.free=4.0G, heap.memory.used=303.2M, heap.memory.free=353.8M, heap.memory.total=657.0M, heap.memory.max=2.0G, heap.memory.used/total=45.96%, heap.memory.used/max=14.74%, minor.gc.count=1412, minor.gc.time=10866ms, major.gc.count=0, major.gc.time=0ms, load.process=10.00%, load.system=100.00%, load.systemAverage=12.72, thread.count=117, thread.peakCount=205, cluster.timeDiff=0, event.q.size=0, executor.q.async.size=0, executor.q.client.size=0, executor.q.client.query.size=0, executor.q.client.blocking.size=0, executor.q.query.size=0, executor.q.scheduled.size=0, executor.q.io.size=0, executor.q.system.size=0, executor.q.operations.size=0, executor.q.priorityOperation.size=0, operations.completed.count=218449, executor.q.mapLoad.size=0, executor.q.mapLoadAllKeys.size=0, executor.q.cluster.size=0, executor.q.response.size=0, operations.running.count=0, operations.pending.invocations.percentage=0.00%, operations.pending.invocations.count=0, proxy.count=2, clientEndpoint.count=0, connection.active.count=0, client.connection.count=0, connection.count=0
02:13:01,408  INFO |stressTest_sorted| - [HealthMonitor] hz.flamboyant_snyder.HealthMonitor - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] processors=8, physical.memory.total=377.6G, physical.memory.free=154.0G, swap.space.total=4.0G, swap.space.free=4.0G, heap.memory.used=404.6M, heap.memory.free=252.4M, heap.memory.total=657.0M, heap.memory.max=2.0G, heap.memory.used/total=61.53%, heap.memory.used/max=19.74%, minor.gc.count=1412, minor.gc.time=10866ms, major.gc.count=0, major.gc.time=0ms, load.process=10.00%, load.system=100.00%, load.systemAverage=12.72, thread.count=117, thread.peakCount=205, cluster.timeDiff=-1, event.q.size=0, executor.q.async.size=0, executor.q.client.size=0, executor.q.client.query.size=0, executor.q.client.blocking.size=0, executor.q.query.size=0, executor.q.scheduled.size=0, executor.q.io.size=0, executor.q.system.size=0, executor.q.operations.size=0, executor.q.priorityOperation.size=0, operations.completed.count=167368, executor.q.mapLoad.size=0, executor.q.mapLoadAllKeys.size=0, executor.q.cluster.size=0, executor.q.response.size=0, operations.running.count=0, operations.pending.invocations.percentage=0.00%, operations.pending.invocations.count=0, proxy.count=2, clientEndpoint.count=0, connection.active.count=0, client.connection.count=0, connection.count=0
02:13:01,923  INFO |stressTest_sorted| - [HealthMonitor] hz.blissful_snyder.HealthMonitor - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] processors=8, physical.memory.total=377.6G, physical.memory.free=154.0G, swap.space.total=4.0G, swap.space.free=4.0G, heap.memory.used=527.6M, heap.memory.free=129.4M, heap.memory.total=657.0M, heap.memory.max=2.0G, heap.memory.used/total=80.25%, heap.memory.used/max=25.74%, minor.gc.count=1412, minor.gc.time=10866ms, major.gc.count=0, major.gc.time=0ms, load.process=0.00%, load.system=100.00%, load.systemAverage=12.72, thread.count=117, thread.peakCount=205, cluster.timeDiff=-1, event.q.size=0, executor.q.async.size=0, executor.q.client.size=0, executor.q.client.query.size=0, executor.q.client.blocking.size=0, executor.q.query.size=0, executor.q.scheduled.size=0, executor.q.io.size=0, executor.q.system.size=0, executor.q.operations.size=0, executor.q.priorityOperation.size=0, operations.completed.count=229041, executor.q.mapLoad.size=0, executor.q.mapLoadAllKeys.size=0, executor.q.cluster.size=0, executor.q.response.size=0, operations.running.count=1, operations.pending.invocations.percentage=0.00%, operations.pending.invocations.count=0, proxy.count=2, clientEndpoint.count=0, connection.active.count=0, client.connection.count=0, connection.count=0
02:13:01,997 DEBUG |stressTest_sorted| - [JobRepository] hz.vibrant_snyder.cached.thread-3 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Job cleanup took 0ms
02:13:06,998 DEBUG |stressTest_sorted| - [JobRepository] hz.vibrant_snyder.cached.thread-7 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Job cleanup took 0ms
02:13:11,998 DEBUG |stressTest_sorted| - [JobRepository] hz.vibrant_snyder.cached.thread-14 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Job cleanup took 0ms
02:13:14,848 DEBUG |stressTest_sorted| - [CalciteSqlOptimizer] stressTest_sorted - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Before logical opt:
LogicalSort(sort0=[$1], dir0=[DESC])
  LogicalProject(__key=[$0], this=[$1])
    LogicalTableScan(table=[[hazelcast, public, map[projects=[0, 1]]]])

02:13:14,849 DEBUG |stressTest_sorted| - [CalciteSqlOptimizer] stressTest_sorted - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] After logical opt:
SortLogicalRel(sort0=[$1], dir0=[DESC])
  FullScanLogicalRel(table=[[hazelcast, public, map[projects=[0, 1]]]])

02:13:14,850 DEBUG |stressTest_sorted| - [CalciteSqlOptimizer] stressTest_sorted - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] After physical opt:
IndexScanMapPhysicalRel(table=[[hazelcast, public, map[projects=[0, 1]]]], index=[165c33e1-a26f-4ab6-8286-1f0d1e06f36d], indexExp=[null], remainderExp=[null])

02:13:14,851 DEBUG |stressTest_sorted| - [LightMasterContext] stressTest_sorted - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Start executing light job 070d-2375-7880-0001, execution graph in DOT format:
digraph DAG {
	""Index(IMap[public.map])"" [localParallelism=1];
	""SortCombine"" [localParallelism=1];
	""ClientSink"" [localParallelism=1];
	""Index(IMap[public.map])"" -> ""SortCombine"" [label=""distributed to [127.0.0.1]:5701-partitioned-ordered"", queueSize=1024];
	""SortCombine"" -> ""ClientSink"" [label=""distributed to [127.0.0.1]:5701-partitioned"", queueSize=1024];
}
HINT: You can use graphviz or http://viz-js.com to visualize the printed graph.
02:13:14,851 DEBUG |stressTest_sorted| - [LightMasterContext] stressTest_sorted - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Building execution plan for 070d-2375-7880-0001
02:13:14,851 DEBUG |stressTest_sorted| - [LightMasterContext] stressTest_sorted - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Built execution plans for 070d-2375-7880-0001
02:13:14,852 DEBUG |stressTest_sorted| - [InitExecutionOperation] stressTest_sorted - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Initializing execution plan for job 070d-2375-7880-0001, execution 070d-2375-7880-0001 from [127.0.0.1]:5701
02:13:14,852 DEBUG |stressTest_sorted| - [JobExecutionService] stressTest_sorted - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Execution plan for light job ID=070d-2375-7880-0001, jobName='070d-2375-7880-0001', executionId=070d-2375-7880-0001 initialized, will start the execution
02:13:14,853 DEBUG |stressTest_sorted| - [InitExecutionOperation] hz.blissful_snyder.generic-operation.thread-0 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Initializing execution plan for job 070d-2375-7880-0001, execution 070d-2375-7880-0001 from [127.0.0.1]:5701
02:13:14,853 DEBUG |stressTest_sorted| - [InitExecutionOperation] hz.flamboyant_snyder.generic-operation.thread-0 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Initializing execution plan for job 070d-2375-7880-0001, execution 070d-2375-7880-0001 from [127.0.0.1]:5701
02:13:14,853 DEBUG |stressTest_sorted| - [JobExecutionService] hz.blissful_snyder.generic-operation.thread-0 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Execution plan for light job ID=070d-2375-7880-0001, jobName='070d-2375-7880-0001', executionId=070d-2375-7880-0001 initialized, will start the execution
02:13:14,854 DEBUG |stressTest_sorted| - [JobExecutionService] hz.flamboyant_snyder.generic-operation.thread-0 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Execution plan for light job ID=070d-2375-7880-0001, jobName='070d-2375-7880-0001', executionId=070d-2375-7880-0001 initialized, will start the execution
02:13:14,874  INFO |stressTest_sorted| - [MetricsConfigHelper] Thread-1422 - [LOCAL] [dev] [5.0.1-SNAPSHOT] Overridden metrics configuration with system property 'hazelcast.metrics.collection.frequency'='1' -> 'MetricsConfig.collectionFrequencySeconds'='1'
02:13:14,875  INFO |stressTest_sorted| - [logo] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] 
	+       +  o    o     o     o---o o----o o      o---o     o     o----o o--o--o
	+ +   + +  |    |    / \       /  |      |     /         / \    |         |   
	+ + + + +  o----o   o   o     o   o----o |    o         o   o   o----o    |   
	+ +   + +  |    |  /     \   /    |      |     \       /     \       |    |   
	+       +  o    o o       o o---o o----o o----o o---o o       o o----o    o   
02:13:14,875  INFO |stressTest_sorted| - [system] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Copyright (c) 2008-2021, Hazelcast, Inc. All Rights Reserved.
02:13:14,875  INFO |stressTest_sorted| - [system] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Hazelcast Platform 5.0.1-SNAPSHOT (20211102 - dce2abb) starting at [127.0.0.1]:5704
02:13:14,875  INFO |stressTest_sorted| - [system] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Cluster name: dev
02:13:14,879  INFO |stressTest_sorted| - [MetricsConfigHelper] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Collecting debug metrics and sending to diagnostics is enabled
02:13:14,884  WARN |stressTest_sorted| - [CPSubsystem] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] CP Subsystem is not enabled. CP data structures will operate in UNSAFE mode! Please note that UNSAFE mode will not provide strong consistency guarantees.
02:13:14,888  INFO |stressTest_sorted| - [JetServiceBackend] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Setting number of cooperative threads and default parallelism to 2
02:13:14,890  INFO |stressTest_sorted| - [Diagnostics] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments.
02:13:14,890  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5704 is STARTING
02:13:14,890  INFO |stressTest_sorted| - [MockServer] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5701, connection: MockConnection{localEndpoint=[127.0.0.1]:5704, remoteEndpoint=[127.0.0.1]:5701, alive=true}
02:13:14,891  INFO |stressTest_sorted| - [MockServer] hz.vibrant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5704, connection: MockConnection{localEndpoint=[127.0.0.1]:5701, remoteEndpoint=[127.0.0.1]:5704, alive=true}
02:13:14,891  INFO |stressTest_sorted| - [ClusterService] hz.vibrant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] 

Members {size:4, ver:4} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82 this
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac
	Member [127.0.0.1]:5704 - 6f2e210e-8d29-4e25-a94b-a5324b666501
]

02:13:14,894  INFO |stressTest_sorted| - [MockServer] hz.flamboyant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5704, connection: MockConnection{localEndpoint=[127.0.0.1]:5702, remoteEndpoint=[127.0.0.1]:5704, alive=true}
02:13:14,894  INFO |stressTest_sorted| - [ClusterService] hz.flamboyant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] 

Members {size:4, ver:4} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd this
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac
	Member [127.0.0.1]:5704 - 6f2e210e-8d29-4e25-a94b-a5324b666501
]

02:13:14,894  INFO |stressTest_sorted| - [MockServer] hz.blissful_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5704, connection: MockConnection{localEndpoint=[127.0.0.1]:5703, remoteEndpoint=[127.0.0.1]:5704, alive=true}
02:13:14,894  INFO |stressTest_sorted| - [ClusterService] hz.blissful_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] 

Members {size:4, ver:4} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac this
	Member [127.0.0.1]:5704 - 6f2e210e-8d29-4e25-a94b-a5324b666501
]

02:13:14,993  INFO |stressTest_sorted| - [JetExtension] hz.elastic_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Jet is enabled
02:13:14,994  INFO |stressTest_sorted| - [ClusterService] hz.elastic_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] 

Members {size:4, ver:4} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac
	Member [127.0.0.1]:5704 - 6f2e210e-8d29-4e25-a94b-a5324b666501 this
]

02:13:15,143  INFO |stressTest_sorted| - [MigrationManager] hz.vibrant_snyder.migration - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Repartitioning cluster data. Migration tasks count: 11
02:13:15,144  INFO |stressTest_sorted| - [MockServer] hz.elastic_snyder.partition-operation.thread-1 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5703, connection: MockConnection{localEndpoint=[127.0.0.1]:5704, remoteEndpoint=[127.0.0.1]:5703, alive=true}
02:13:15,144  INFO |stressTest_sorted| - [MockServer] hz.elastic_snyder.partition-operation.thread-0 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5703, connection: MockConnection{localEndpoint=[127.0.0.1]:5704, remoteEndpoint=[127.0.0.1]:5703, alive=true}
02:13:15,144  INFO |stressTest_sorted| - [MockServer] hz.elastic_snyder.partition-operation.thread-0 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5702, connection: MockConnection{localEndpoint=[127.0.0.1]:5704, remoteEndpoint=[127.0.0.1]:5702, alive=true}
02:13:15,403  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5704 is STARTED
02:13:15,405  INFO |stressTest_sorted| - [HealthMonitor] hz.elastic_snyder.HealthMonitor - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] processors=8, physical.memory.total=377.6G, physical.memory.free=154.0G, swap.space.total=4.0G, swap.space.free=4.0G, heap.memory.used=521.0M, heap.memory.free=184.0M, heap.memory.total=705.0M, heap.memory.max=2.0G, heap.memory.used/total=73.81%, heap.memory.used/max=25.41%, minor.gc.count=1428, minor.gc.time=11096ms, major.gc.count=0, major.gc.time=0ms, load.process=6.67%, load.system=100.00%, load.systemAverage=12.26, thread.count=182, thread.peakCount=205, cluster.timeDiff=-2, event.q.size=0, executor.q.async.size=0, executor.q.client.size=0, executor.q.client.query.size=0, executor.q.client.blocking.size=0, executor.q.query.size=0, executor.q.scheduled.size=0, executor.q.io.size=0, executor.q.system.size=0, executor.q.operations.size=0, executor.q.priorityOperation.size=0, operations.completed.count=49, executor.q.mapLoad.size=0, executor.q.mapLoadAllKeys.size=0, executor.q.cluster.size=0, executor.q.response.size=0, operations.running.count=0, operations.pending.invocations.percentage=0.00%, operations.pending.invocations.count=0, proxy.count=3, clientEndpoint.count=0, connection.active.count=0, client.connection.count=0, connection.count=0
02:13:16,407  INFO |stressTest_sorted| - [MigrationManager] hz.vibrant_snyder.migration - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] All migration tasks have been completed. (repartitionTime=Wed Nov 03 02:13:15 UTC 2021, plannedMigrations=11, completedMigrations=11, remainingMigrations=0, totalCompletedMigrations=11, elapsedMigrationOperationTime=6744ms, totalElapsedMigrationOperationTime=6744ms, elapsedDestinationCommitTime=4ms, totalElapsedDestinationCommitTime=4ms, elapsedMigrationTime=6752ms, totalElapsedMigrationTime=6752ms)
02:13:17,403  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5704 is SHUTTING_DOWN
02:13:17,404 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Added a shutting-down member: 6f2e210e-8d29-4e25-a94b-a5324b666501
02:13:17,404  INFO |stressTest_sorted| - [MigrationManager] hz.vibrant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Shutdown request of Member [127.0.0.1]:5704 - 6f2e210e-8d29-4e25-a94b-a5324b666501 is handled
02:13:17,406  INFO |stressTest_sorted| - [MigrationManager] hz.vibrant_snyder.migration - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Repartitioning cluster data. Migration tasks count: 6
02:13:17,724 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-2 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partition replication is not in safe state, but in REPLICA_NOT_SYNC
02:13:17,824 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-2 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because members are shutting down: [6f2e210e-8d29-4e25-a94b-a5324b666501]
02:13:17,924 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-2 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because members are shutting down: [6f2e210e-8d29-4e25-a94b-a5324b666501]
02:13:17,990  INFO |stressTest_sorted| - [MigrationManager] hz.vibrant_snyder.migration - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] All migration tasks have been completed. (repartitionTime=Wed Nov 03 02:13:17 UTC 2021, plannedMigrations=6, completedMigrations=6, remainingMigrations=0, totalCompletedMigrations=17, elapsedMigrationOperationTime=2297ms, totalElapsedMigrationOperationTime=9041ms, elapsedDestinationCommitTime=2ms, totalElapsedDestinationCommitTime=6ms, elapsedMigrationTime=2299ms, totalElapsedMigrationTime=9052ms)
02:13:18,005  INFO |stressTest_sorted| - [Node] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Shutting down connection manager...
02:13:18,005  INFO |stressTest_sorted| - [MockServer] Thread-1422 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Removed connection to endpoint: [127.0.0.1]:5704, connection: MockConnection{localEndpoint=[127.0.0.1]:5703, remoteEndpoint=[127.0.0.1]:5704, alive=false}
02:13:18,005  INFO |stressTest_sorted| - [MockServer] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Removed connection to endpoint: [127.0.0.1]:5703, connection: MockConnection{localEndpoint=[127.0.0.1]:5704, remoteEndpoint=[127.0.0.1]:5703, alive=false}
02:13:18,005  INFO |stressTest_sorted| - [MockServer] Thread-1422 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Removed connection to endpoint: [127.0.0.1]:5704, connection: MockConnection{localEndpoint=[127.0.0.1]:5702, remoteEndpoint=[127.0.0.1]:5704, alive=false}
02:13:18,005  INFO |stressTest_sorted| - [MockServer] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Removed connection to endpoint: [127.0.0.1]:5702, connection: MockConnection{localEndpoint=[127.0.0.1]:5704, remoteEndpoint=[127.0.0.1]:5702, alive=false}
02:13:18,005  INFO |stressTest_sorted| - [MockServer] Thread-1422 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Removed connection to endpoint: [127.0.0.1]:5704, connection: MockConnection{localEndpoint=[127.0.0.1]:5701, remoteEndpoint=[127.0.0.1]:5704, alive=false}
02:13:18,005  INFO |stressTest_sorted| - [MockServer] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Removed connection to endpoint: [127.0.0.1]:5701, connection: MockConnection{localEndpoint=[127.0.0.1]:5704, remoteEndpoint=[127.0.0.1]:5701, alive=false}
02:13:18,005  WARN |stressTest_sorted| - [MembershipManager] Thread-1422 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Member [127.0.0.1]:5704 - 6f2e210e-8d29-4e25-a94b-a5324b666501 is suspected to be dead for reason: Connection manager is stopped on Member [127.0.0.1]:5704 - 6f2e210e-8d29-4e25-a94b-a5324b666501 this
02:13:18,005  WARN |stressTest_sorted| - [MembershipManager] Thread-1422 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Member [127.0.0.1]:5704 - 6f2e210e-8d29-4e25-a94b-a5324b666501 is suspected to be dead for reason: Connection manager is stopped on Member [127.0.0.1]:5704 - 6f2e210e-8d29-4e25-a94b-a5324b666501 this
02:13:18,005  INFO |stressTest_sorted| - [MembershipManager] Thread-1422 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Removing Member [127.0.0.1]:5704 - 6f2e210e-8d29-4e25-a94b-a5324b666501
02:13:18,006  INFO |stressTest_sorted| - [ClusterService] Thread-1422 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] 

Members {size:3, ver:5} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82 this
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac
]

02:13:18,006  INFO |stressTest_sorted| - [TransactionManagerService] hz.vibrant_snyder.cached.thread-2 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Committing/rolling-back live transactions of [127.0.0.1]:5704, UUID: 6f2e210e-8d29-4e25-a94b-a5324b666501
02:13:18,006  INFO |stressTest_sorted| - [TransactionManagerService] hz.blissful_snyder.cached.thread-7 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Committing/rolling-back live transactions of [127.0.0.1]:5704, UUID: 6f2e210e-8d29-4e25-a94b-a5324b666501
02:13:18,006  INFO |stressTest_sorted| - [Node] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Shutting down node engine...
02:13:18,006  INFO |stressTest_sorted| - [ClusterService] hz.flamboyant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] 

Members {size:3, ver:5} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd this
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac
]

02:13:18,006  INFO |stressTest_sorted| - [TransactionManagerService] hz.flamboyant_snyder.cached.thread-8 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Committing/rolling-back live transactions of [127.0.0.1]:5704, UUID: 6f2e210e-8d29-4e25-a94b-a5324b666501
02:13:18,006 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-2 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Removed a shutting-down member: 6f2e210e-8d29-4e25-a94b-a5324b666501, now shuttingDownMembers=[]
02:13:18,006  INFO |stressTest_sorted| - [ClusterService] hz.blissful_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] 

Members {size:3, ver:5} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac this
]

02:13:18,019  INFO |stressTest_sorted| - [MigrationManager] hz.vibrant_snyder.migration - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Partition balance is ok, no need to repartition.
02:13:18,030 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-14 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partition replication is not in safe state, but in MIGRATION_LOCAL
02:13:18,038  INFO |stressTest_sorted| - [NodeExtension] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Destroying node NodeExtension.
02:13:18,039  INFO |stressTest_sorted| - [Node] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Hazelcast Shutdown is completed in 635 ms.
02:13:18,042  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5704 is SHUTDOWN
02:13:18,043  INFO |stressTest_sorted| - [MetricsConfigHelper] Thread-1422 - [LOCAL] [dev] [5.0.1-SNAPSHOT] Overridden metrics configuration with system property 'hazelcast.metrics.collection.frequency'='1' -> 'MetricsConfig.collectionFrequencySeconds'='1'
02:13:18,044  INFO |stressTest_sorted| - [logo] Thread-1422 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] 
	+       +  o    o     o     o---o o----o o      o---o     o     o----o o--o--o
	+ +   + +  |    |    / \       /  |      |     /         / \    |         |   
	+ + + + +  o----o   o   o     o   o----o |    o         o   o   o----o    |   
	+ +   + +  |    |  /     \   /    |      |     \       /     \       |    |   
	+       +  o    o o       o o---o o----o o----o o---o o       o o----o    o   
02:13:18,044  INFO |stressTest_sorted| - [system] Thread-1422 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] Copyright (c) 2008-2021, Hazelcast, Inc. All Rights Reserved.
02:13:18,044  INFO |stressTest_sorted| - [system] Thread-1422 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] Hazelcast Platform 5.0.1-SNAPSHOT (20211102 - dce2abb) starting at [127.0.0.1]:5705
02:13:18,044  INFO |stressTest_sorted| - [system] Thread-1422 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] Cluster name: dev
02:13:18,049  INFO |stressTest_sorted| - [MetricsConfigHelper] Thread-1422 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] Collecting debug metrics and sending to diagnostics is enabled
02:13:18,055  WARN |stressTest_sorted| - [CPSubsystem] Thread-1422 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] CP Subsystem is not enabled. CP data structures will operate in UNSAFE mode! Please note that UNSAFE mode will not provide strong consistency guarantees.
02:13:18,059  INFO |stressTest_sorted| - [JetServiceBackend] Thread-1422 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] Setting number of cooperative threads and default parallelism to 2
02:13:18,061  INFO |stressTest_sorted| - [Diagnostics] Thread-1422 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments.
02:13:18,061  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5705 is STARTING
02:13:18,062  INFO |stressTest_sorted| - [MockServer] Thread-1422 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5701, connection: MockConnection{localEndpoint=[127.0.0.1]:5705, remoteEndpoint=[127.0.0.1]:5701, alive=true}
02:13:18,062  INFO |stressTest_sorted| - [MockServer] hz.vibrant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5705, connection: MockConnection{localEndpoint=[127.0.0.1]:5701, remoteEndpoint=[127.0.0.1]:5705, alive=true}
02:13:18,063  INFO |stressTest_sorted| - [ClusterService] hz.vibrant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] 

Members {size:4, ver:6} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82 this
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac
	Member [127.0.0.1]:5705 - ee18c640-63b5-4090-92dd-7bcff7859d14
]

02:13:18,064  INFO |stressTest_sorted| - [MockServer] hz.flamboyant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5705, connection: MockConnection{localEndpoint=[127.0.0.1]:5702, remoteEndpoint=[127.0.0.1]:5705, alive=true}
02:13:18,064  INFO |stressTest_sorted| - [MockServer] hz.blissful_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5705, connection: MockConnection{localEndpoint=[127.0.0.1]:5703, remoteEndpoint=[127.0.0.1]:5705, alive=true}
02:13:18,064  INFO |stressTest_sorted| - [ClusterService] hz.flamboyant_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5702 [dev] [5.0.1-SNAPSHOT] 

Members {size:4, ver:6} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd this
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac
	Member [127.0.0.1]:5705 - ee18c640-63b5-4090-92dd-7bcff7859d14
]

02:13:18,064  INFO |stressTest_sorted| - [ClusterService] hz.blissful_snyder.priority-generic-operation.thread-0 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] 

Members {size:4, ver:6} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac this
	Member [127.0.0.1]:5705 - ee18c640-63b5-4090-92dd-7bcff7859d14
]

02:13:18,131 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-5 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partition replication is not in safe state, but in REPLICA_NOT_OWNED
02:13:18,163  INFO |stressTest_sorted| - [JetExtension] hz.stupefied_snyder.generic-operation.thread-0 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] Jet is enabled
02:13:18,163  INFO |stressTest_sorted| - [ClusterService] hz.stupefied_snyder.generic-operation.thread-0 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] 

Members {size:4, ver:6} [
	Member [127.0.0.1]:5701 - fe3f8bdd-d56f-435b-9b0a-d63a1cc5be82
	Member [127.0.0.1]:5702 - 13cdf9d3-f871-4fdd-965d-3932228a46bd
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac
	Member [127.0.0.1]:5705 - ee18c640-63b5-4090-92dd-7bcff7859d14 this
]

02:13:18,250 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-5 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partition replication is not in safe state, but in REPLICA_NOT_OWNED
02:13:18,314  INFO |stressTest_sorted| - [MigrationManager] hz.vibrant_snyder.migration - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Repartitioning cluster data. Migration tasks count: 11
02:13:18,314  INFO |stressTest_sorted| - [MockServer] hz.stupefied_snyder.partition-operation.thread-1 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5703, connection: MockConnection{localEndpoint=[127.0.0.1]:5705, remoteEndpoint=[127.0.0.1]:5703, alive=true}
02:13:18,314  INFO |stressTest_sorted| - [MockServer] hz.stupefied_snyder.partition-operation.thread-0 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5703, connection: MockConnection{localEndpoint=[127.0.0.1]:5705, remoteEndpoint=[127.0.0.1]:5703, alive=true}
02:13:18,315  INFO |stressTest_sorted| - [MockServer] hz.stupefied_snyder.partition-operation.thread-1 - [127.0.0.1]:5705 [dev] [5.0.1-SNAPSHOT] Created connection to endpoint: [127.0.0.1]:5702, connection: MockConnection{localEndpoint=[127.0.0.1]:5705, remoteEndpoint=[127.0.0.1]:5702, alive=true}
02:13:18,350 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-5 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partition replication is not in safe state, but in REPLICA_NOT_OWNED
02:13:18,450 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-2 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partition replication is not in safe state, but in REPLICA_NOT_OWNED
02:13:18,550 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.vibrant_snyder.cached.thread-2 - [127.0.0.1]:5701 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partition replication is not in safe state, but in REPLICA_NOT_OWNED
02:13:18,562  WARN |stressTest_sorted| - [Node] Thread-1422 - [127.
...[truncated 3223507 chars]...
0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:04,191 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-2 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:04,292 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-2 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:04,392 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-2 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:04,492 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-4 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:04,592 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-4 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:04,692 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-4 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:04,793 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-4 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:04,893 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-4 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:04,993 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-9 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:05,093 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-9 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:05,193 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-9 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:05,294 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-9 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:05,395 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-9 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:05,495 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-2 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:05,596 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-2 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:05,697 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-2 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:05,799 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-2 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:05,899 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.trusting_almeida.cached.thread-2 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:05,992  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5891 is SHUTTING_DOWN
02:23:05,992 DEBUG |stressTest_sorted| - [JobCoordinationService] Thread-1422 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Added a shutting-down member: 3b29e727-e997-4f14-ab7a-75fc5ac6bddb
02:23:06,000  INFO |stressTest_sorted| - [Node] Thread-1422 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Shutting down connection manager...
02:23:06,000  INFO |stressTest_sorted| - [Node] Thread-1422 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Shutting down node engine...
02:23:06,014  INFO |stressTest_sorted| - [NodeExtension] Thread-1422 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Destroying node NodeExtension.
02:23:06,016  INFO |stressTest_sorted| - [Node] Thread-1422 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] Hazelcast Shutdown is completed in 24 ms.
02:23:06,016  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5891 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5891 is SHUTDOWN
02:23:06,017  INFO |stressTest_sorted| - [MetricsConfigHelper] Thread-1422 - [LOCAL] [dev] [5.0.1-SNAPSHOT] Overridden metrics configuration with system property 'hazelcast.metrics.collection.frequency'='1' -> 'MetricsConfig.collectionFrequencySeconds'='1'
02:23:06,026  INFO |stressTest_sorted| - [logo] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] 
	+       +  o    o     o     o---o o----o o      o---o     o     o----o o--o--o
	+ +   + +  |    |    / \       /  |      |     /         / \    |         |   
	+ + + + +  o----o   o   o     o   o----o |    o         o   o   o----o    |   
	+ +   + +  |    |  /     \   /    |      |     \       /     \       |    |   
	+       +  o    o o       o o---o o----o o----o o---o o       o o----o    o   
02:23:06,026  INFO |stressTest_sorted| - [system] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Copyright (c) 2008-2021, Hazelcast, Inc. All Rights Reserved.
02:23:06,026  INFO |stressTest_sorted| - [system] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Hazelcast Platform 5.0.1-SNAPSHOT (20211102 - dce2abb) starting at [127.0.0.1]:5892
02:23:06,026  INFO |stressTest_sorted| - [system] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Cluster name: dev
02:23:06,032  INFO |stressTest_sorted| - [MetricsConfigHelper] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Collecting debug metrics and sending to diagnostics is enabled
02:23:06,043  WARN |stressTest_sorted| - [CPSubsystem] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] CP Subsystem is not enabled. CP data structures will operate in UNSAFE mode! Please note that UNSAFE mode will not provide strong consistency guarantees.
02:23:06,045  INFO |stressTest_sorted| - [JetServiceBackend] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Setting number of cooperative threads and default parallelism to 2
02:23:06,047  INFO |stressTest_sorted| - [Diagnostics] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments.
02:23:06,047  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5892 is STARTING
02:23:06,047  INFO |stressTest_sorted| - [JetExtension] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Jet is enabled
02:23:06,047  INFO |stressTest_sorted| - [ClusterService] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] 

Members {size:1, ver:1} [
	Member [127.0.0.1]:5892 - a66a08dc-95e2-4089-9f9c-f6df2a9ddb0d this
]

02:23:06,047 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-1 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:06,047  WARN |stressTest_sorted| - [Node] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Config seed port is 5701 and cluster size is 1. Some of the ports seem occupied!
02:23:06,047  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5892 is STARTED
02:23:06,049  INFO |stressTest_sorted| - [HealthMonitor] hz.keen_almeida.HealthMonitor - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] processors=8, physical.memory.total=377.6G, physical.memory.free=157.9G, swap.space.total=4.0G, swap.space.free=4.0G, heap.memory.used=1006.3M, heap.memory.free=506.7M, heap.memory.total=1.5G, heap.memory.max=2.0G, heap.memory.used/total=66.48%, heap.memory.used/max=49.12%, minor.gc.count=2051, minor.gc.time=41249ms, major.gc.count=0, major.gc.time=0ms, load.process=0.00%, load.system=100.00%, load.systemAverage=54.69, thread.count=93, thread.peakCount=207, cluster.timeDiff=0, event.q.size=0, executor.q.async.size=0, executor.q.client.size=0, executor.q.client.query.size=0, executor.q.client.blocking.size=0, executor.q.query.size=0, executor.q.scheduled.size=0, executor.q.io.size=0, executor.q.system.size=0, executor.q.operations.size=0, executor.q.priorityOperation.size=0, operations.completed.count=0, executor.q.mapLoad.size=0, executor.q.mapLoadAllKeys.size=0, executor.q.cluster.size=0, executor.q.response.size=0, operations.running.count=0, operations.pending.invocations.percentage=0.00%, operations.pending.invocations.count=0, proxy.count=1, clientEndpoint.count=0, connection.active.count=0, client.connection.count=0, connection.count=0
02:23:06,147 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-1 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:06,247 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-1 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:06,349 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-2 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:06,449 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-2 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:06,550 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-2 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:06,651 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-2 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:06,751 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-2 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:06,851 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-2 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:06,951 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-2 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:07,224 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-6 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:07,324 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-2 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:07,424 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-2 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:07,524 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-2 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:07,625 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-7 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:07,726 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-7 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:07,826 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-7 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:07,928 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-7 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:08,029 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.keen_almeida.cached.thread-7 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:08,048  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5892 is SHUTTING_DOWN
02:23:08,048 DEBUG |stressTest_sorted| - [JobCoordinationService] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Added a shutting-down member: a66a08dc-95e2-4089-9f9c-f6df2a9ddb0d
02:23:08,048  INFO |stressTest_sorted| - [Node] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Shutting down connection manager...
02:23:08,048  INFO |stressTest_sorted| - [Node] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Shutting down node engine...
02:23:08,054  INFO |stressTest_sorted| - [NodeExtension] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Destroying node NodeExtension.
02:23:08,054  INFO |stressTest_sorted| - [Node] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] Hazelcast Shutdown is completed in 6 ms.
02:23:08,054  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5892 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5892 is SHUTDOWN
02:23:08,055  INFO |stressTest_sorted| - [MetricsConfigHelper] Thread-1422 - [LOCAL] [dev] [5.0.1-SNAPSHOT] Overridden metrics configuration with system property 'hazelcast.metrics.collection.frequency'='1' -> 'MetricsConfig.collectionFrequencySeconds'='1'
02:23:08,056  INFO |stressTest_sorted| - [logo] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] 
	+       +  o    o     o     o---o o----o o      o---o     o     o----o o--o--o
	+ +   + +  |    |    / \       /  |      |     /         / \    |         |   
	+ + + + +  o----o   o   o     o   o----o |    o         o   o   o----o    |   
	+ +   + +  |    |  /     \   /    |      |     \       /     \       |    |   
	+       +  o    o o       o o---o o----o o----o o---o o       o o----o    o   
02:23:08,056  INFO |stressTest_sorted| - [system] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Copyright (c) 2008-2021, Hazelcast, Inc. All Rights Reserved.
02:23:08,056  INFO |stressTest_sorted| - [system] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Hazelcast Platform 5.0.1-SNAPSHOT (20211102 - dce2abb) starting at [127.0.0.1]:5893
02:23:08,056  INFO |stressTest_sorted| - [system] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Cluster name: dev
02:23:08,059  INFO |stressTest_sorted| - [MetricsConfigHelper] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Collecting debug metrics and sending to diagnostics is enabled
02:23:08,063  WARN |stressTest_sorted| - [CPSubsystem] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] CP Subsystem is not enabled. CP data structures will operate in UNSAFE mode! Please note that UNSAFE mode will not provide strong consistency guarantees.
02:23:08,066  INFO |stressTest_sorted| - [JetServiceBackend] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Setting number of cooperative threads and default parallelism to 2
02:23:08,067  INFO |stressTest_sorted| - [Diagnostics] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments.
02:23:08,067  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5893 is STARTING
02:23:08,068  INFO |stressTest_sorted| - [JetExtension] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Jet is enabled
02:23:08,068 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.friendly_almeida.cached.thread-1 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:08,068  INFO |stressTest_sorted| - [ClusterService] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] 

Members {size:1, ver:1} [
	Member [127.0.0.1]:5893 - f228efe1-04ed-4174-a74e-c0c29fca1d16 this
]

02:23:08,068  WARN |stressTest_sorted| - [Node] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Config seed port is 5701 and cluster size is 1. Some of the ports seem occupied!
02:23:08,068  INFO |stressTest_sorted| - [LifecycleService] Thread-1422 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5893 is STARTED
02:23:08,070  INFO |stressTest_sorted| - [HealthMonitor] hz.friendly_almeida.HealthMonitor - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] processors=8, physical.memory.total=377.6G, physical.memory.free=157.9G, swap.space.total=4.0G, swap.space.free=4.0G, heap.memory.used=937.4M, heap.memory.free=575.6M, heap.memory.total=1.5G, heap.memory.max=2.0G, heap.memory.used/total=61.93%, heap.memory.used/max=45.75%, minor.gc.count=2052, minor.gc.time=41426ms, major.gc.count=0, major.gc.time=0ms, load.process=14.29%, load.system=100.00%, load.systemAverage=54.69, thread.count=93, thread.peakCount=207, cluster.timeDiff=0, event.q.size=0, executor.q.async.size=0, executor.q.client.size=0, executor.q.client.query.size=0, executor.q.client.blocking.size=0, executor.q.query.size=0, executor.q.scheduled.size=0, executor.q.io.size=0, executor.q.system.size=0, executor.q.operations.size=0, executor.q.priorityOperation.size=0, operations.completed.count=0, executor.q.mapLoad.size=0, executor.q.mapLoadAllKeys.size=0, executor.q.cluster.size=0, executor.q.response.size=0, operations.running.count=0, operations.pending.invocations.percentage=0.00%, operations.pending.invocations.count=0, proxy.count=1, clientEndpoint.count=0, connection.active.count=0, client.connection.count=0, connection.count=0
02:23:08,170 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.friendly_almeida.cached.thread-2 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:08,270 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.friendly_almeida.cached.thread-2 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:08,370 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.friendly_almeida.cached.thread-2 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:08,470 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.friendly_almeida.cached.thread-2 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:08,570 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.friendly_almeida.cached.thread-4 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:08,671 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.friendly_almeida.cached.thread-4 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:08,751  INFO |stressTest_sorted| - [ClusterService] hz.blissful_snyder.cached.thread-6 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] 

Members {size:1, ver:378} [
	Member [127.0.0.1]:5703 - 6362a347-195b-47ae-9e4c-9419a6abfeac this
]

02:23:08,751  INFO |stressTest_sorted| - [MembershipManager] hz.blissful_snyder.cached.thread-6 - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Mastership is claimed with: MembersView{version=378, members=[MemberInfo{address=[127.0.0.1]:5703, uuid=6362a347-195b-47ae-9e4c-9419a6abfeac, liteMember=false, memberListJoinVersion=3}]}
02:23:08,771 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.friendly_almeida.cached.thread-4 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:08,871 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.friendly_almeida.cached.thread-4 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:08,971 DEBUG |stressTest_sorted| - [JobCoordinationService] hz.friendly_almeida.cached.thread-4 - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Not starting jobs because partitions are not yet initialized.
02:23:08,978  INFO |stressTest_sorted| - [InternalPartitionService] hz.blissful_snyder.migration - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Fetching partition tables from cluster to determine the most recent one... Local stamp: 507970631642232217
02:23:08,978  INFO |stressTest_sorted| - [InternalPartitionService] hz.blissful_snyder.migration - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Most recent partition table is determined.
02:23:08,978  INFO |stressTest_sorted| - [InternalPartitionService] hz.blissful_snyder.migration - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Applying the most recent of partition state...
02:23:08,978  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Shutting down connection manager...
02:23:08,979  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Shutting down node engine...
02:23:08,981  INFO |stressTest_sorted| - [NodeExtension] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Destroying node NodeExtension.
02:23:08,981  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] Hazelcast Shutdown is completed in 5009 ms.
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5703 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5703 is SHUTDOWN
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5769 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5769 is SHUTTING_DOWN
02:23:08,981  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5769 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5769 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5769 is SHUTDOWN
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5736 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5736 is SHUTTING_DOWN
02:23:08,981  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5736 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5736 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5736 is SHUTDOWN
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5835 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5835 is SHUTTING_DOWN
02:23:08,981  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5835 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5835 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5835 is SHUTDOWN
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5802 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5802 is SHUTTING_DOWN
02:23:08,981  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5802 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5802 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5802 is SHUTDOWN
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5868 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5868 is SHUTTING_DOWN
02:23:08,981  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5868 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5868 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5868 is SHUTDOWN
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5761 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5761 is SHUTTING_DOWN
02:23:08,981  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5761 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5761 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5761 is SHUTDOWN
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5728 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5728 is SHUTTING_DOWN
02:23:08,981  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5728 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5728 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5728 is SHUTDOWN
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5827 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5827 is SHUTTING_DOWN
02:23:08,981  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5827 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5827 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5827 is SHUTDOWN
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5794 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5794 is SHUTTING_DOWN
02:23:08,981  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5794 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5794 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5794 is SHUTDOWN
02:23:08,981  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5893 is SHUTTING_DOWN
02:23:08,981 DEBUG |stressTest_sorted| - [JobCoordinationService] Time-limited test - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Added a shutting-down member: f228efe1-04ed-4174-a74e-c0c29fca1d16
02:23:08,981  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Shutting down connection manager...
02:23:08,981  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Shutting down node engine...
02:23:08,983  INFO |stressTest_sorted| - [NodeExtension] Time-limited test - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Destroying node NodeExtension.
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] Hazelcast Shutdown is completed in 2 ms.
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5893 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5893 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5860 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5860 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5860 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5860 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5860 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5753 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5753 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5753 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5753 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5753 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5720 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5720 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5720 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5720 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5720 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5819 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5819 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5819 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5819 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5819 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5786 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5786 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5786 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5786 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5786 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5885 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5885 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5885 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5885 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5885 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5852 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5852 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5852 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5852 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5852 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5745 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5745 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5745 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5745 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5745 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5712 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5712 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5712 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5712 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5712 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5811 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5811 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5811 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5811 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5811 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5778 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5778 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5778 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5778 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5778 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5877 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5877 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5877 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5877 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5877 is SHUTDOWN
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5844 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5844 is SHUTTING_DOWN
02:23:08,983  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5844 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,983  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5844 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5844 is SHUTDOWN
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5737 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5737 is SHUTTING_DOWN
02:23:08,984  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5737 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5737 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5737 is SHUTDOWN
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5704 is SHUTTING_DOWN
02:23:08,984  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5704 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5704 is SHUTDOWN
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5803 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5803 is SHUTTING_DOWN
02:23:08,984  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5803 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5803 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5803 is SHUTDOWN
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5770 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5770 is SHUTTING_DOWN
02:23:08,984  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5770 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5770 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5770 is SHUTDOWN
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5869 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5869 is SHUTTING_DOWN
02:23:08,984  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5869 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5869 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5869 is SHUTDOWN
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5836 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5836 is SHUTTING_DOWN
02:23:08,984  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5836 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5836 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5836 is SHUTDOWN
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5886 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5886 is SHUTTING_DOWN
02:23:08,984  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5886 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5886 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5886 is SHUTDOWN
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5729 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5729 is SHUTTING_DOWN
02:23:08,984  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5729 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5729 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5729 is SHUTDOWN
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5795 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5795 is SHUTTING_DOWN
02:23:08,984  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5795 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5795 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5795 is SHUTDOWN
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5762 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5762 is SHUTTING_DOWN
02:23:08,984  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5762 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5762 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5762 is SHUTDOWN
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5861 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5861 is SHUTTING_DOWN
02:23:08,984  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5861 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5861 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5861 is SHUTDOWN
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5828 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5828 is SHUTTING_DOWN
02:23:08,984  INFO |stressTest_sorted| - [Node] Time-limited test - [127.0.0.1]:5828 [dev] [5.0.1-SNAPSHOT] Node is already shutting down... Waiting for shutdown process to complete...
02:23:08,984  INFO |stressTest_sorted| - [LifecycleService] Time-limited test - [127.0.0.1]:5828 [dev] [5.0.1-SNAPSHOT] [127.0.0.1]:5828 is SHUTDOWN
BuildInfo right after stressTest_sorted(com.hazelcast.jet.sql_slow.MapIndexScanPMigrationStressTest): BuildInfo{version='5.0.1-SNAPSHOT', build='20211102', buildNumber=20211102, revision=dce2abb, enterprise=false, serializationVersion=1}
Hiccups measured while running test 'stressTest_sorted(com.hazelcast.jet.sql_slow.MapIndexScanPMigrationStressTest):'
02:12:40, accumulated pauses: 74 ms, max pause: 17 ms, pauses over 1000 ms: 0
02:12:45, accumulated pauses: 101 ms, max pause: 26 ms, pauses over 1000 ms: 0
02:12:50, accumulated pauses: 90 ms, max pause: 17 ms, pauses over 1000 ms: 0
02:12:55, accumulated pauses: 89 ms, max pause: 21 ms, pauses over 1000 ms: 0
02:13:00, accumulated pauses: 124 ms, max pause: 21 ms, pauses over 1000 ms: 0
02:13:05, accumulated pauses: 93 ms, max pause: 28 ms, pauses over 1000 ms: 0
02:13:10, accumulated pauses: 126 ms, max pause: 19 ms, pauses over 1000 ms: 0
02:13:15, accumulated pauses: 403 ms, max pause: 96 ms, pauses over 1000 ms: 0
02:13:20, accumulated pauses: 325 ms, max pause: 72 ms, pauses over 1000 ms: 0
02:13:25, accumulated pauses: 318 ms, max pause: 75 ms, pauses over 1000 ms: 0
02:13:30, accumulated pauses: 331 ms, max pause: 53 ms, pauses over 1000 ms: 0
02:13:35, accumulated pauses: 224 ms, max pause: 54 ms, pauses over 1000 ms: 0
02:13:40, accumulated pauses: 289 ms, max pause: 52 ms, pauses over 1000 ms: 0
02:13:45, accumulated pauses: 240 ms, max pause: 59 ms, pauses over 1000 ms: 0
02:13:50, accumulated pauses: 310 ms, max pause: 51 ms, pauses over 1000 ms: 0
02:13:55, accumulated pauses: 203 ms, max pause: 58 ms, pauses over 1000 ms: 0
02:14:00, accumulated pauses: 277 ms, max pause: 50 ms, pauses over 1000 ms: 0
02:14:05, accumulated pauses: 275 ms, max pause: 53 ms, pauses over 1000 ms: 0
02:14:10, accumulated pauses: 233 ms, max pause: 50 ms, pauses over 1000 ms: 0
02:14:15, accumulated pauses: 313 ms, max pause: 50 ms, pauses over 1000 ms: 0
02:14:20, accumulated pauses: 228 ms, max pause: 46 ms, pauses over 1000 ms: 0
02:14:25, accumulated pauses: 296 ms, max pause: 44 ms, pauses over 1000 ms: 0
02:14:30, accumulated pauses: 299 ms, max pause: 57 ms, pauses over 1000 ms: 0
02:14:35, accumulated pauses: 252 ms, max pause: 52 ms, pauses over 1000 ms: 0
02:14:40, accumulated pauses: 270 ms, max pause: 52 ms, pauses over 1000 ms: 0
02:14:45, accumulated pauses: 282 ms, max pause: 55 ms, pauses over 1000 ms: 0
02:14:50, accumulated pauses: 295 ms, max pause: 58 ms, pauses over 1000 ms: 0
02:14:55, accumulated pauses: 259 ms, max pause: 64 ms, pauses over 1000 ms: 0
02:15:00, accumulated pauses: 332 ms, max pause: 70 ms, pauses over 1000 ms: 0
02:15:05, accumulated pauses: 255 ms, max pause: 54 ms, pauses over 1000 ms: 0
02:15:10, accumulated pauses: 278 ms, max pause: 53 ms, pauses over 1000 ms: 0
02:15:15, accumulated pauses: 300 ms, max pause: 60 ms, pauses over 1000 ms: 0
02:15:20, accumulated pauses: 259 ms, max pause: 45 ms, pauses over 1000 ms: 0
02:15:25, accumulated pauses: 258 ms, max pause: 46 ms, pauses over 1000 ms: 0
02:15:30, accumulated pauses: 209 ms, max pause: 48 ms, pauses over 1000 ms: 0
02:15:35, accumulated pauses: 286 ms, max pause: 50 ms, pauses over 1000 ms: 0
02:15:40, accumulated pauses: 299 ms, max pause: 52 ms, pauses over 1000 ms: 0
02:15:45, accumulated pauses: 261 ms, max pause: 60 ms, pauses over 1000 ms: 0
02:15:50, accumulated pauses: 198 ms, max pause: 38 ms, pauses over 1000 ms: 0
02:15:55, accumulated pauses: 348 ms, max pause: 52 ms, pauses over 1000 ms: 0
02:16:00, accumulated pauses: 257 ms, max pause: 65 ms, pauses over 1000 ms: 0
02:16:05, accumulated pauses: 233 ms, max pause: 48 ms, pauses over 1000 ms: 0
02:16:10, accumulated pauses: 279 ms, max pause: 61 ms, pauses over 1000 ms: 0
02:16:15, accumulated pauses: 257 ms, max pause: 64 ms, pauses over 1000 ms: 0
02:16:20, accumulated pauses: 292 ms, max pause: 58 ms, pauses over 1000 ms: 0
02:16:25, accumulated pauses: 235 ms, max pause: 60 ms, pauses over 1000 ms: 0
02:16:30, accumulated pauses: 215 ms, max pause: 68 ms, pauses over 1000 ms: 0
02:16:35, accumulated pauses: 354 ms, max pause: 60 ms, pauses over 1000 ms: 0
02:16:40, accumulated pauses: 257 ms, max pause: 55 ms, pauses over 1000 ms: 0
02:16:45, accumulated pauses: 207 ms, max pause: 52 ms, pauses over 1000 ms: 0
02:16:50, accumulated pauses: 313 ms, max pause: 60 ms, pauses over 1000 ms: 0
02:16:55, accumulated pauses: 303 ms, max pause: 59 ms, pauses over 1000 ms: 0
02:17:00, accumulated pauses: 221 ms, max pause: 52 ms, pauses over 1000 ms: 0
02:17:05, accumulated pauses: 288 ms, max pause: 83 ms, pauses over 1000 ms: 0
02:17:10, accumulated pauses: 262 ms, max pause: 67 ms, pauses over 1000 ms: 0
02:17:15, accumulated pauses: 268 ms, max pause: 56 ms, pauses over 1000 ms: 0
02:17:20, accumulated pauses: 252 ms, max pause: 57 ms, pauses over 1000 ms: 0
02:17:25, accumulated pauses: 221 ms, max pause: 59 ms, pauses over 1000 ms: 0
02:17:30, accumulated pauses: 291 ms, max pause: 57 ms, pauses over 1000 ms: 0
02:17:35, accumulated pauses: 283 ms, max pause: 62 ms, pauses over 1000 ms: 0
02:17:40, accumulated pauses: 202 ms, max pause: 52 ms, pauses over 1000 ms: 0
02:17:45, accumulated pauses: 337 ms, max pause: 60 ms, pauses over 1000 ms: 0
02:17:50, accumulated pauses: 232 ms, max pause: 49 ms, pauses over 1000 ms: 0
02:17:55, accumulated pauses: 247 ms, max pause: 57 ms, pauses over 1000 ms: 0
02:18:00, accumulated pauses: 308 ms, max pause: 68 ms, pauses over 1000 ms: 0
02:18:05, accumulated pauses: 234 ms, max pause: 51 ms, pauses over 1000 ms: 0
02:18:10, accumulated pauses: 212 ms, max pause: 55 ms, pauses over 1000 ms: 0
02:18:15, accumulated pauses: 328 ms, max pause: 63 ms, pauses over 1000 ms: 0
02:18:20, accumulated pauses: 287 ms, max pause: 57 ms, pauses over 1000 ms: 0
02:18:25, accumulated pauses: 208 ms, max pause: 57 ms, pauses over 1000 ms: 0
02:18:30, accumulated pauses: 255 ms, max pause: 53 ms, pauses over 1000 ms: 0
02:18:35, accumulated pauses: 259 ms, max pause: 50 ms, pauses over 1000 ms: 0
02:18:40, accumulated pauses: 200 ms, max pause: 45 ms, pauses over 1000 ms: 0
02:18:45, accumulated pauses: 270 ms, max pause: 50 ms, pauses over 1000 ms: 0
02:18:50, accumulated pauses: 289 ms, max pause: 53 ms, pauses over 1000 ms: 0
02:18:55, accumulated pauses: 245 ms, max pause: 39 ms, pauses over 1000 ms: 0
02:19:00, accumulated pauses: 249 ms, max pause: 52 ms, pauses over 1000 ms: 0
02:19:05, accumulated pauses: 317 ms, max pause: 64 ms, pauses over 1000 ms: 0
02:19:10, accumulated pauses: 219 ms, max pause: 50 ms, pauses over 1000 ms: 0
02:19:15, accumulated pauses: 265 ms, max pause: 50 ms, pauses over 1000 ms: 0
02:19:20, accumulated pauses: 371 ms, max pause: 48 ms, pauses over 1000 ms: 0
02:19:25, accumulated pauses: 245 ms, max pause: 58 ms, pauses over 1000 ms: 0
02:19:30, accumulated pauses: 207 ms, max pause: 55 ms, pauses over 1000 ms: 0
02:19:35, accumulated pauses: 318 ms, max pause: 58 ms, pauses over 1000 ms: 0
02:19:40, accumulated pauses: 203 ms, max pause: 51 ms, pauses over 1000 ms: 0
02:19:45, accumulated pauses: 313 ms, max pause: 58 ms, pauses over 1000 ms: 0
02:19:50, accumulated pauses: 269 ms, max pause: 55 ms, pauses over 1000 ms: 0
02:19:55, accumulated pauses: 192 ms, max pause: 53 ms, pauses over 1000 ms: 0
02:20:00, accumulated pauses: 308 ms, max pause: 57 ms, pauses over 1000 ms: 0
02:20:05, accumulated pauses: 272 ms, max pause: 45 ms, pauses over 1000 ms: 0
02:20:10, accumulated pauses: 209 ms, max pause: 51 ms, pauses over 1000 ms: 0
02:20:15, accumulated pauses: 368 ms, max pause: 64 ms, pauses over 1000 ms: 0
02:20:20, accumulated pauses: 286 ms, max pause: 81 ms, pauses over 1000 ms: 0
02:20:25, accumulated pauses: 269 ms, max pause: 53 ms, pauses over 1000 ms: 0
02:20:30, accumulated pauses: 287 ms, max pause: 58 ms, pauses over 1000 ms: 0
02:20:35, accumulated pauses: 214 ms, max pause: 55 ms, pauses over 1000 ms: 0
02:20:40, accumulated pauses: 245 ms, max pause: 60 ms, pauses over 1000 ms: 0
02:20:45, accumulated pauses: 316 ms, max pause: 51 ms, pauses over 1000 ms: 0
02:20:50, accumulated pauses: 194 ms, max pause: 59 ms, pauses over 1000 ms: 0
02:20:55, accumulated pauses: 285 ms, max pause: 68 ms, pauses over 1000 ms: 0
02:21:00, accumulated pauses: 319 ms, max pause: 55 ms, pauses over 1000 ms: 0
02:21:05, accumulated pauses: 251 ms, max pause: 58 ms, pauses over 1000 ms: 0
02:21:10, accumulated pauses: 255 ms, max pause: 61 ms, pauses over 1000 ms: 0
02:21:15, accumulated pauses: 274 ms, max pause: 68 ms, pauses over 1000 ms: 0
02:21:20, accumulated pauses: 217 ms, max pause: 35 ms, pauses over 1000 ms: 0
02:21:25, accumulated pauses: 320 ms, max pause: 56 ms, pauses over 1000 ms: 0
02:21:30, accumulated pauses: 248 ms, max pause: 50 ms, pauses over 1000 ms: 0
02:21:35, accumulated pauses: 382 ms, max pause: 95 ms, pauses over 1000 ms: 0
02:21:40, accumulated pauses: 382 ms, max pause: 55 ms, pauses over 1000 ms: 0
02:21:45, accumulated pauses: 764 ms, max pause: 122 ms, pauses over 1000 ms: 0
02:21:50, accumulated pauses: 659 ms, max pause: 116 ms, pauses over 1000 ms: 0
02:21:55, accumulated pauses: 491 ms, max pause: 93 ms, pauses over 1000 ms: 0
02:22:00, accumulated pauses: 747 ms, max pause: 271 ms, pauses over 1000 ms: 0
02:22:05, accumulated pauses: 346 ms, max pause: 73 ms, pauses over 1000 ms: 0
02:22:10, accumulated pauses: 339 ms, max pause: 63 ms, pauses over 1000 ms: 0
02:22:15, accumulated pauses: 780 ms, max pause: 182 ms, pauses over 1000 ms: 0
02:22:20, accumulated pauses: 793 ms, max pause: 168 ms, pauses over 1000 ms: 0
02:22:25, accumulated pauses: 600 ms, max pause: 124 ms, pauses over 1000 ms: 0
02:22:30, accumulated pauses: 391 ms, max pause: 140 ms, pauses over 1000 ms: 0
02:22:35, accumulated pauses: 381 ms, max pause: 64 ms, pauses over 1000 ms: 0
02:22:40, accumulated pauses: 1295 ms, max pause: 610 ms, pauses over 1000 ms: 0
02:22:45, accumulated pauses: 1272 ms, max pause: 310 ms, pauses over 1000 ms: 0
02:22:50, accumulated pauses: 842 ms, max pause: 327 ms, pauses over 1000 ms: 0
02:22:55, accumulated pauses: 630 ms, max pause: 263 ms, pauses over 1000 ms: 0
02:23:00, accumulated pauses: 268 ms, max pause: 126 ms, pauses over 1000 ms: 0
02:23:05, accumulated pauses: 284 ms, max pause: 175 ms, pauses over 1000 ms: 0
```

</details>
",0,com hazelcast jet sql slow mapindexscanpmigrationstresstest stresstest sorted          z   commit       failed on sonar build  oracle jdk            stacktrace           org junit runners model testtimedoutexception  test timed out after   milliseconds  	at app  org assertj core internal iterablediff iterablesremovefirst iterablediff java     	at app  org assertj core internal iterablediff subtract iterablediff java     	at app  org assertj core internal iterablediff   iterablediff java     	at app  org assertj core internal iterablediff diff iterablediff java     	at app  org assertj core internal iterables assertcontainsexactly iterables java     	at app  org assertj core api abstractiterableassert containsexactly abstractiterableassert java     	at app  org assertj core api listassert containsexactly listassert java     	at app  org assertj core api listassert containsexactly listassert java     	at app  org assertj core api abstractiterableassert containsexactlyelementsof abstractiterableassert java     	at app  com hazelcast jet sql slow mapindexscanpmigrationstresstest assertrowsordered mapindexscanpmigrationstresstest java     	at app  com hazelcast jet sql slow mapindexscanpmigrationstresstest stresstest sorted mapindexscanpmigrationstresstest java     	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 app  org junit runners model frameworkmethod   runreflectivecall frameworkmethod java     	at app  org junit internal runners model reflectivecallable run reflectivecallable java     	at app  org junit runners model frameworkmethod invokeexplosively frameworkmethod java     	at app  org junit internal runners statements invokemethod evaluate invokemethod java     	at app  com hazelcast test failontimeoutstatement callablestatement call failontimeoutstatement java     	at app  com hazelcast test failontimeoutstatement callablestatement call failontimeoutstatement java     	at java base       java util concurrent futuretask run futuretask java     	at java base       java lang thread run thread java                   standard output           finished running test  stresstest hash in     seconds   started running test  stresstest sorted           info  stresstest sorted      time limited test         overridden metrics configuration with system property  hazelcast metrics collection frequency          metricsconfig collectionfrequencyseconds                info  stresstest sorted      time limited test             	           o    o     o     o   o o    o o      o   o     o     o    o o  o  o  	                                                                                	           o    o   o   o     o   o    o      o         o   o   o    o          	                                                                                	           o    o o       o o   o o    o o    o o   o o       o o    o    o              info  stresstest sorted      time limited test           copyright  c       hazelcast  inc  all rights reserved            info  stresstest sorted      time limited test           hazelcast platform       snapshot         starting at               info  stresstest sorted      time limited test           cluster name  dev           info  stresstest sorted      time limited test           collecting debug metrics and sending to diagnostics is enabled           warn  stresstest sorted      time limited test           cp subsystem is not enabled  cp data structures will operate in unsafe mode  please note that unsafe mode will not provide strong consistency guarantees            info  stresstest sorted      time limited test           setting number of cooperative threads and default parallelism to             info  stresstest sorted      time limited test           diagnostics disabled  to enable add  dhazelcast diagnostics enabled true to the jvm arguments            info  stresstest sorted      time limited test               is starting           info  stresstest sorted      time limited test           jet is enabled           info  stresstest sorted      time limited test               members  size    ver       	member                 this               debug  stresstest sorted      hz vibrant snyder cached thread             not starting jobs because partitions are not yet initialized            info  stresstest sorted      time limited test               is started           info  stresstest sorted      time limited test         overridden metrics configuration with system property  hazelcast metrics collection frequency          metricsconfig collectionfrequencyseconds                info  stresstest sorted      time limited test             	           o    o     o     o   o o    o o      o   o     o     o    o o  o  o  	                                                                                	           o    o   o   o     o   o    o      o         o   o   o    o          	                                                                                	           o    o o       o o   o o    o o    o o   o o       o o    o    o              info  stresstest sorted      time limited test           copyright  c       hazelcast  inc  all rights reserved            info  stresstest sorted      time limited test           hazelcast platform       snapshot         starting at               info  stresstest sorted      time limited test           cluster name  dev           info  stresstest sorted      hz vibrant snyder healthmonitor           processors    physical memory total      physical memory free      swap space total      swap space free      heap memory used      heap memory free      heap memory total      heap memory max      heap memory used total       heap memory used max       minor gc count    minor gc time    major gc count    major gc time    load process       load system       load systemaverage      thread count    thread peakcount    cluster timediff    event q size    executor q async size    executor q client size    executor q client query size    executor q client blocking size    executor q query size    executor q scheduled size    executor q io size    executor q system size    executor q operations size    executor q priorityoperation size    operations completed count    executor q mapload size    executor q maploadallkeys size    executor q cluster size    executor q response size    operations running count    operations pending invocations percentage       operations pending invocations count    proxy count    clientendpoint count    connection active count    client connection count    connection count             info  stresstest sorted      time limited test           collecting debug metrics and sending to diagnostics is enabled           warn  stresstest sorted      time limited test           cp subsystem is not enabled  cp data structures will operate in unsafe mode  please note that unsafe mode will not provide strong consistency guarantees            info  stresstest sorted      time limited test           setting number of cooperative threads and default parallelism to             info  stresstest sorted      time limited test           diagnostics disabled  to enable add  dhazelcast diagnostics enabled true to the jvm arguments            info  stresstest sorted      time limited test               is starting           info  stresstest sorted      time limited test           created connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive true            info  stresstest sorted      hz vibrant snyder priority generic operation thread             created connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive true            info  stresstest sorted      hz vibrant snyder priority generic operation thread                 members  size    ver       	member                 this  	member                               debug  stresstest sorted      hz vibrant snyder cached thread             not starting jobs because partitions are not yet initialized            info  stresstest sorted      hz flamboyant snyder generic operation thread             jet is enabled           info  stresstest sorted      hz flamboyant snyder generic operation thread                 members  size    ver       	member                  	member                 this               debug  stresstest sorted      hz vibrant snyder cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz vibrant snyder cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz vibrant snyder cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz vibrant snyder cached thread             not starting jobs because partitions are not yet initialized            info  stresstest sorted      time limited test               is started           info  stresstest sorted      time limited test         overridden metrics configuration with system property  hazelcast metrics collection frequency          metricsconfig collectionfrequencyseconds                info  stresstest sorted      hz flamboyant snyder healthmonitor           processors    physical memory total      physical memory free      swap space total      swap space free      heap memory used      heap memory free      heap memory total      heap memory max      heap memory used total       heap memory used max       minor gc count    minor gc time    major gc count    major gc time    load process       load system       load systemaverage      thread count    thread peakcount    cluster timediff    event q size    executor q async size    executor q client size    executor q client query size    executor q client blocking size    executor q query size    executor q scheduled size    executor q io size    executor q system size    executor q operations size    executor q priorityoperation size    operations completed count    executor q mapload size    executor q maploadallkeys size    executor q cluster size    executor q response size    operations running count    operations pending invocations percentage       operations pending invocations count    proxy count    clientendpoint count    connection active count    client connection count    connection count             info  stresstest sorted      time limited test             	           o    o     o     o   o o    o o      o   o     o     o    o o  o  o  	                                                                                	           o    o   o   o     o   o    o      o         o   o   o    o          	                                                                                	           o    o o       o o   o o    o o    o o   o o       o o    o    o              info  stresstest sorted      time limited test           copyright  c       hazelcast  inc  all rights reserved            info  stresstest sorted      time limited test           hazelcast platform       snapshot         starting at               info  stresstest sorted      time limited test           cluster name  dev           info  stresstest sorted      time limited test           collecting debug metrics and sending to diagnostics is enabled           warn  stresstest sorted      time limited test           cp subsystem is not enabled  cp data structures will operate in unsafe mode  please note that unsafe mode will not provide strong consistency guarantees            info  stresstest sorted      time limited test           setting number of cooperative threads and default parallelism to             info  stresstest sorted      time limited test           diagnostics disabled  to enable add  dhazelcast diagnostics enabled true to the jvm arguments            info  stresstest sorted      time limited test               is starting           info  stresstest sorted      time limited test           created connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive true            info  stresstest sorted      hz vibrant snyder priority generic operation thread             created connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive true            info  stresstest sorted      hz vibrant snyder priority generic operation thread                 members  size    ver       	member                 this  	member                  	member                                info  stresstest sorted      hz flamboyant snyder priority generic operation thread             created connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive true            info  stresstest sorted      hz flamboyant snyder priority generic operation thread                 members  size    ver       	member                  	member                 this  	member                               debug  stresstest sorted      hz vibrant snyder cached thread             not starting jobs because partitions are not yet initialized            info  stresstest sorted      hz blissful snyder priority generic operation thread             jet is enabled           info  stresstest sorted      hz blissful snyder priority generic operation thread                 members  size    ver       	member                  	member                  	member                 this               debug  stresstest sorted      hz vibrant snyder cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz vibrant snyder cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz vibrant snyder cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz vibrant snyder cached thread             not starting jobs because partitions are not yet initialized            info  stresstest sorted      time limited test           created connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive true            info  stresstest sorted      time limited test               is started           info  stresstest sorted      time limited test           initializing cluster partition table arrangement              info  stresstest sorted      hz blissful snyder healthmonitor           processors    physical memory total      physical memory free      swap space total      swap space free      heap memory used      heap memory free      heap memory total      heap memory max      heap memory used total       heap memory used max       minor gc count    minor gc time    major gc count    major gc time    load process       load system       load systemaverage      thread count    thread peakcount    cluster timediff    event q size    executor q async size    executor q client size    executor q client query size    executor q client blocking size    executor q query size    executor q scheduled size    executor q io size    executor q system size    executor q operations size    executor q priorityoperation size    operations completed count    executor q mapload size    executor q maploadallkeys size    executor q cluster size    executor q response size    operations running count    operations pending invocations percentage       operations pending invocations count    proxy count    clientendpoint count    connection active count    client connection count    connection count            debug  stresstest sorted      hz vibrant snyder cached thread             job cleanup took            debug  stresstest sorted      hz vibrant snyder cached thread             job cleanup took            debug  stresstest sorted      hz vibrant snyder cached thread             job cleanup took            debug  stresstest sorted      hz vibrant snyder cached thread             job cleanup took             info  stresstest sorted      hz vibrant snyder healthmonitor           processors    physical memory total      physical memory free      swap space total      swap space free      heap memory used      heap memory free      heap memory total      heap memory max      heap memory used total       heap memory used max       minor gc count    minor gc time    major gc count    major gc time    load process       load system       load systemaverage      thread count    thread peakcount    cluster timediff    event q size    executor q async size    executor q client size    executor q client query size    executor q client blocking size    executor q query size    executor q scheduled size    executor q io size    executor q system size    executor q operations size    executor q priorityoperation size    operations completed count    executor q mapload size    executor q maploadallkeys size    executor q cluster size    executor q response size    operations running count    operations pending invocations percentage       operations pending invocations count    proxy count    clientendpoint count    connection active count    client connection count    connection count             info  stresstest sorted      hz flamboyant snyder healthmonitor           processors    physical memory total      physical memory free      swap space total      swap space free      heap memory used      heap memory free      heap memory total      heap memory max      heap memory used total       heap memory used max       minor gc count    minor gc time    major gc count    major gc time    load process       load system       load systemaverage      thread count    thread peakcount    cluster timediff     event q size    executor q async size    executor q client size    executor q client query size    executor q client blocking size    executor q query size    executor q scheduled size    executor q io size    executor q system size    executor q operations size    executor q priorityoperation size    operations completed count    executor q mapload size    executor q maploadallkeys size    executor q cluster size    executor q response size    operations running count    operations pending invocations percentage       operations pending invocations count    proxy count    clientendpoint count    connection active count    client connection count    connection count             info  stresstest sorted      hz blissful snyder healthmonitor           processors    physical memory total      physical memory free      swap space total      swap space free      heap memory used      heap memory free      heap memory total      heap memory max      heap memory used total       heap memory used max       minor gc count    minor gc time    major gc count    major gc time    load process       load system       load systemaverage      thread count    thread peakcount    cluster timediff     event q size    executor q async size    executor q client size    executor q client query size    executor q client blocking size    executor q query size    executor q scheduled size    executor q io size    executor q system size    executor q operations size    executor q priorityoperation size    operations completed count    executor q mapload size    executor q maploadallkeys size    executor q cluster size    executor q response size    operations running count    operations pending invocations percentage       operations pending invocations count    proxy count    clientendpoint count    connection active count    client connection count    connection count            debug  stresstest sorted      hz vibrant snyder cached thread             job cleanup took            debug  stresstest sorted      hz vibrant snyder cached thread             job cleanup took            debug  stresstest sorted      hz vibrant snyder cached thread             job cleanup took            debug  stresstest sorted      stresstest sorted           before logical opt   logicalsort              logicalproject   key    this         logicaltablescan table                  debug  stresstest sorted      stresstest sorted           after logical opt   sortlogicalrel              fullscanlogicalrel table                  debug  stresstest sorted      stresstest sorted           after physical opt   indexscanmapphysicalrel table       index    indexexp    remainderexp               debug  stresstest sorted      stresstest sorted           start executing light job          execution graph in dot format   digraph dag    	 index imap        	 sortcombine      	 clientsink      	 index imap        sortcombine      partitioned ordered   queuesize      	 sortcombine      clientsink      partitioned   queuesize         hint  you can use graphviz or   to visualize the printed graph           debug  stresstest sorted      stresstest sorted           building execution plan for                  debug  stresstest sorted      stresstest sorted           built execution plans for                  debug  stresstest sorted      stresstest sorted           initializing execution plan for job          execution         from              debug  stresstest sorted      stresstest sorted           execution plan for light job id          jobname            executionid         initialized  will start the execution          debug  stresstest sorted      hz blissful snyder generic operation thread             initializing execution plan for job          execution         from              debug  stresstest sorted      hz flamboyant snyder generic operation thread             initializing execution plan for job          execution         from              debug  stresstest sorted      hz blissful snyder generic operation thread             execution plan for light job id          jobname            executionid         initialized  will start the execution          debug  stresstest sorted      hz flamboyant snyder generic operation thread             execution plan for light job id          jobname            executionid         initialized  will start the execution           info  stresstest sorted      thread           overridden metrics configuration with system property  hazelcast metrics collection frequency          metricsconfig collectionfrequencyseconds                info  stresstest sorted      thread               	           o    o     o     o   o o    o o      o   o     o     o    o o  o  o  	                                                                                	           o    o   o   o     o   o    o      o         o   o   o    o          	                                                                                	           o    o o       o o   o o    o o    o o   o o       o o    o    o              info  stresstest sorted      thread             copyright  c       hazelcast  inc  all rights reserved            info  stresstest sorted      thread             hazelcast platform       snapshot         starting at               info  stresstest sorted      thread             cluster name  dev           info  stresstest sorted      thread             collecting debug metrics and sending to diagnostics is enabled           warn  stresstest sorted      thread             cp subsystem is not enabled  cp data structures will operate in unsafe mode  please note that unsafe mode will not provide strong consistency guarantees            info  stresstest sorted      thread             setting number of cooperative threads and default parallelism to             info  stresstest sorted      thread             diagnostics disabled  to enable add  dhazelcast diagnostics enabled true to the jvm arguments            info  stresstest sorted      thread                 is starting           info  stresstest sorted      thread             created connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive true            info  stresstest sorted      hz vibrant snyder priority generic operation thread             created connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive true            info  stresstest sorted      hz vibrant snyder priority generic operation thread                 members  size    ver       	member                 this  	member                  	member                  	member                                info  stresstest sorted      hz flamboyant snyder priority generic operation thread             created connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive true            info  stresstest sorted      hz flamboyant snyder priority generic operation thread                 members  size    ver       	member                  	member                 this  	member                  	member                                info  stresstest sorted      hz blissful snyder priority generic operation thread             created connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive true            info  stresstest sorted      hz blissful snyder priority generic operation thread                 members  size    ver       	member                  	member                  	member                 this  	member                                info  stresstest sorted      hz elastic snyder priority generic operation thread             jet is enabled           info  stresstest sorted      hz elastic snyder priority generic operation thread                 members  size    ver       	member                  	member                  	member                  	member                 this                info  stresstest sorted      hz vibrant snyder migration           repartitioning cluster data  migration tasks count              info  stresstest sorted      hz elastic snyder partition operation thread             created connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive true            info  stresstest sorted      hz elastic snyder partition operation thread             created connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive true            info  stresstest sorted      hz elastic snyder partition operation thread             created connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive true            info  stresstest sorted      thread                 is started           info  stresstest sorted      hz elastic snyder healthmonitor           processors    physical memory total      physical memory free      swap space total      swap space free      heap memory used      heap memory free      heap memory total      heap memory max      heap memory used total       heap memory used max       minor gc count    minor gc time    major gc count    major gc time    load process       load system       load systemaverage      thread count    thread peakcount    cluster timediff     event q size    executor q async size    executor q client size    executor q client query size    executor q client blocking size    executor q query size    executor q scheduled size    executor q io size    executor q system size    executor q operations size    executor q priorityoperation size    operations completed count    executor q mapload size    executor q maploadallkeys size    executor q cluster size    executor q response size    operations running count    operations pending invocations percentage       operations pending invocations count    proxy count    clientendpoint count    connection active count    client connection count    connection count             info  stresstest sorted      hz vibrant snyder migration           all migration tasks have been completed   repartitiontime wed nov         utc    plannedmigrations    completedmigrations    remainingmigrations    totalcompletedmigrations    elapsedmigrationoperationtime    totalelapsedmigrationoperationtime    elapseddestinationcommittime    totalelapseddestinationcommittime    elapsedmigrationtime    totalelapsedmigrationtime              info  stresstest sorted      thread                 is shutting down          debug  stresstest sorted      hz vibrant snyder priority generic operation thread             added a shutting down member                      info  stresstest sorted      hz vibrant snyder priority generic operation thread             shutdown request of member                 is handled           info  stresstest sorted      hz vibrant snyder migration           repartitioning cluster data  migration tasks count             debug  stresstest sorted      hz vibrant snyder cached thread             not starting jobs because partition replication is not in safe state  but in replica not sync          debug  stresstest sorted      hz vibrant snyder cached thread             not starting jobs because members are shutting down             debug  stresstest sorted      hz vibrant snyder cached thread             not starting jobs because members are shutting down              info  stresstest sorted      hz vibrant snyder migration           all migration tasks have been completed   repartitiontime wed nov         utc    plannedmigrations    completedmigrations    remainingmigrations    totalcompletedmigrations    elapsedmigrationoperationtime    totalelapsedmigrationoperationtime    elapseddestinationcommittime    totalelapseddestinationcommittime    elapsedmigrationtime    totalelapsedmigrationtime              info  stresstest sorted      thread             shutting down connection manager              info  stresstest sorted      thread             removed connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive false            info  stresstest sorted      thread             removed connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive false            info  stresstest sorted      thread             removed connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive false            info  stresstest sorted      thread             removed connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive false            info  stresstest sorted      thread             removed connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive false            info  stresstest sorted      thread             removed connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive false            warn  stresstest sorted      thread             member                 is suspected to be dead for reason  connection manager is stopped on member                 this           warn  stresstest sorted      thread             member                 is suspected to be dead for reason  connection manager is stopped on member                 this           info  stresstest sorted      thread             removing member                           info  stresstest sorted      thread                 members  size    ver       	member                 this  	member                  	member                                info  stresstest sorted      hz vibrant snyder cached thread             committing rolling back live transactions of      uuid                      info  stresstest sorted      hz blissful snyder cached thread             committing rolling back live transactions of      uuid                      info  stresstest sorted      thread             shutting down node engine              info  stresstest sorted      hz flamboyant snyder priority generic operation thread                 members  size    ver       	member                  	member                 this  	member                                info  stresstest sorted      hz flamboyant snyder cached thread             committing rolling back live transactions of      uuid                     debug  stresstest sorted      hz vibrant snyder cached thread             removed a shutting down member             now shuttingdownmembers             info  stresstest sorted      hz blissful snyder priority generic operation thread                 members  size    ver       	member                  	member                  	member                 this                info  stresstest sorted      hz vibrant snyder migration           partition balance is ok  no need to repartition           debug  stresstest sorted      hz vibrant snyder cached thread             not starting jobs because partition replication is not in safe state  but in migration local           info  stresstest sorted      thread             destroying node nodeextension            info  stresstest sorted      thread             hazelcast shutdown is completed in   ms            info  stresstest sorted      thread                 is shutdown           info  stresstest sorted      thread           overridden metrics configuration with system property  hazelcast metrics collection frequency          metricsconfig collectionfrequencyseconds                info  stresstest sorted      thread               	           o    o     o     o   o o    o o      o   o     o     o    o o  o  o  	                                                                                	           o    o   o   o     o   o    o      o         o   o   o    o          	                                                                                	           o    o o       o o   o o    o o    o o   o o       o o    o    o              info  stresstest sorted      thread             copyright  c       hazelcast  inc  all rights reserved            info  stresstest sorted      thread             hazelcast platform       snapshot         starting at               info  stresstest sorted      thread             cluster name  dev           info  stresstest sorted      thread             collecting debug metrics and sending to diagnostics is enabled           warn  stresstest sorted      thread             cp subsystem is not enabled  cp data structures will operate in unsafe mode  please note that unsafe mode will not provide strong consistency guarantees            info  stresstest sorted      thread             setting number of cooperative threads and default parallelism to             info  stresstest sorted      thread             diagnostics disabled  to enable add  dhazelcast diagnostics enabled true to the jvm arguments            info  stresstest sorted      thread                 is starting           info  stresstest sorted      thread             created connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive true            info  stresstest sorted      hz vibrant snyder priority generic operation thread             created connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive true            info  stresstest sorted      hz vibrant snyder priority generic operation thread                 members  size    ver       	member                 this  	member                  	member                  	member                                info  stresstest sorted      hz flamboyant snyder priority generic operation thread             created connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive true            info  stresstest sorted      hz blissful snyder priority generic operation thread             created connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive true            info  stresstest sorted      hz flamboyant snyder priority generic operation thread                 members  size    ver       	member                  	member                 this  	member                  	member                                info  stresstest sorted      hz blissful snyder priority generic operation thread                 members  size    ver       	member                  	member                  	member                 this  	member                               debug  stresstest sorted      hz vibrant snyder cached thread             not starting jobs because partition replication is not in safe state  but in replica not owned           info  stresstest sorted      hz stupefied snyder generic operation thread             jet is enabled           info  stresstest sorted      hz stupefied snyder generic operation thread                 members  size    ver       	member                  	member                  	member                  	member                 this               debug  stresstest sorted      hz vibrant snyder cached thread             not starting jobs because partition replication is not in safe state  but in replica not owned           info  stresstest sorted      hz vibrant snyder migration           repartitioning cluster data  migration tasks count              info  stresstest sorted      hz stupefied snyder partition operation thread             created connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive true            info  stresstest sorted      hz stupefied snyder partition operation thread             created connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive true            info  stresstest sorted      hz stupefied snyder partition operation thread             created connection to endpoint       connection  mockconnection localendpoint      remoteendpoint      alive true           debug  stresstest sorted      hz vibrant snyder cached thread             not starting jobs because partition replication is not in safe state  but in replica not owned          debug  stresstest sorted      hz vibrant snyder cached thread             not starting jobs because partition replication is not in safe state  but in replica not owned          debug  stresstest sorted      hz vibrant snyder cached thread             not starting jobs because partition replication is not in safe state  but in replica not owned           warn  stresstest sorted      thread                       snapshot  not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz trusting almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz trusting almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz trusting almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz trusting almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz trusting almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz trusting almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz trusting almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz trusting almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz trusting almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz trusting almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz trusting almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz trusting almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz trusting almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz trusting almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz trusting almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz trusting almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz trusting almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz trusting almeida cached thread             not starting jobs because partitions are not yet initialized            info  stresstest sorted      thread                 is shutting down          debug  stresstest sorted      thread             added a shutting down member                      info  stresstest sorted      thread             shutting down connection manager              info  stresstest sorted      thread             shutting down node engine              info  stresstest sorted      thread             destroying node nodeextension            info  stresstest sorted      thread             hazelcast shutdown is completed in   ms            info  stresstest sorted      thread                 is shutdown           info  stresstest sorted      thread           overridden metrics configuration with system property  hazelcast metrics collection frequency          metricsconfig collectionfrequencyseconds                info  stresstest sorted      thread               	           o    o     o     o   o o    o o      o   o     o     o    o o  o  o  	                                                                                	           o    o   o   o     o   o    o      o         o   o   o    o          	                                                                                	           o    o o       o o   o o    o o    o o   o o       o o    o    o              info  stresstest sorted      thread             copyright  c       hazelcast  inc  all rights reserved            info  stresstest sorted      thread             hazelcast platform       snapshot         starting at               info  stresstest sorted      thread             cluster name  dev           info  stresstest sorted      thread             collecting debug metrics and sending to diagnostics is enabled           warn  stresstest sorted      thread             cp subsystem is not enabled  cp data structures will operate in unsafe mode  please note that unsafe mode will not provide strong consistency guarantees            info  stresstest sorted      thread             setting number of cooperative threads and default parallelism to             info  stresstest sorted      thread             diagnostics disabled  to enable add  dhazelcast diagnostics enabled true to the jvm arguments            info  stresstest sorted      thread                 is starting           info  stresstest sorted      thread             jet is enabled           info  stresstest sorted      thread                 members  size    ver       	member                 this               debug  stresstest sorted      hz keen almeida cached thread             not starting jobs because partitions are not yet initialized            warn  stresstest sorted      thread             config seed port is   and cluster size is    some of the ports seem occupied            info  stresstest sorted      thread                 is started           info  stresstest sorted      hz keen almeida healthmonitor           processors    physical memory total      physical memory free      swap space total      swap space free      heap memory used      heap memory free      heap memory total      heap memory max      heap memory used total       heap memory used max       minor gc count    minor gc time    major gc count    major gc time    load process       load system       load systemaverage      thread count    thread peakcount    cluster timediff    event q size    executor q async size    executor q client size    executor q client query size    executor q client blocking size    executor q query size    executor q scheduled size    executor q io size    executor q system size    executor q operations size    executor q priorityoperation size    operations completed count    executor q mapload size    executor q maploadallkeys size    executor q cluster size    executor q response size    operations running count    operations pending invocations percentage       operations pending invocations count    proxy count    clientendpoint count    connection active count    client connection count    connection count            debug  stresstest sorted      hz keen almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz keen almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz keen almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz keen almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz keen almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz keen almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz keen almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz keen almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz keen almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz keen almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz keen almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz keen almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz keen almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz keen almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz keen almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz keen almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz keen almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz keen almeida cached thread             not starting jobs because partitions are not yet initialized            info  stresstest sorted      thread                 is shutting down          debug  stresstest sorted      thread             added a shutting down member                      info  stresstest sorted      thread             shutting down connection manager              info  stresstest sorted      thread             shutting down node engine              info  stresstest sorted      thread             destroying node nodeextension            info  stresstest sorted      thread             hazelcast shutdown is completed in   ms            info  stresstest sorted      thread                 is shutdown           info  stresstest sorted      thread           overridden metrics configuration with system property  hazelcast metrics collection frequency          metricsconfig collectionfrequencyseconds                info  stresstest sorted      thread               	           o    o     o     o   o o    o o      o   o     o     o    o o  o  o  	                                                                                	           o    o   o   o     o   o    o      o         o   o   o    o          	                                                                                	           o    o o       o o   o o    o o    o o   o o       o o    o    o              info  stresstest sorted      thread             copyright  c       hazelcast  inc  all rights reserved            info  stresstest sorted      thread             hazelcast platform       snapshot         starting at               info  stresstest sorted      thread             cluster name  dev           info  stresstest sorted      thread             collecting debug metrics and sending to diagnostics is enabled           warn  stresstest sorted      thread             cp subsystem is not enabled  cp data structures will operate in unsafe mode  please note that unsafe mode will not provide strong consistency guarantees            info  stresstest sorted      thread             setting number of cooperative threads and default parallelism to             info  stresstest sorted      thread             diagnostics disabled  to enable add  dhazelcast diagnostics enabled true to the jvm arguments            info  stresstest sorted      thread                 is starting           info  stresstest sorted      thread             jet is enabled          debug  stresstest sorted      hz friendly almeida cached thread             not starting jobs because partitions are not yet initialized            info  stresstest sorted      thread                 members  size    ver       	member                 this                warn  stresstest sorted      thread             config seed port is   and cluster size is    some of the ports seem occupied            info  stresstest sorted      thread                 is started           info  stresstest sorted      hz friendly almeida healthmonitor           processors    physical memory total      physical memory free      swap space total      swap space free      heap memory used      heap memory free      heap memory total      heap memory max      heap memory used total       heap memory used max       minor gc count    minor gc time    major gc count    major gc time    load process       load system       load systemaverage      thread count    thread peakcount    cluster timediff    event q size    executor q async size    executor q client size    executor q client query size    executor q client blocking size    executor q query size    executor q scheduled size    executor q io size    executor q system size    executor q operations size    executor q priorityoperation size    operations completed count    executor q mapload size    executor q maploadallkeys size    executor q cluster size    executor q response size    operations running count    operations pending invocations percentage       operations pending invocations count    proxy count    clientendpoint count    connection active count    client connection count    connection count            debug  stresstest sorted      hz friendly almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz friendly almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz friendly almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz friendly almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz friendly almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz friendly almeida cached thread             not starting jobs because partitions are not yet initialized            info  stresstest sorted      hz blissful snyder cached thread                 members  size    ver       	member                 this                info  stresstest sorted      hz blissful snyder cached thread             mastership is claimed with  membersview version    members      uuid            litemember false  memberlistjoinversion               debug  stresstest sorted      hz friendly almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz friendly almeida cached thread             not starting jobs because partitions are not yet initialized           debug  stresstest sorted      hz friendly almeida cached thread             not starting jobs because partitions are not yet initialized            info  stresstest sorted      hz blissful snyder migration           fetching partition tables from cluster to determine the most recent one    local stamp              info  stresstest sorted      hz blissful snyder migration           most recent partition table is determined            info  stresstest sorted      hz blissful snyder migration           applying the most recent of partition state              info  stresstest sorted      time limited test           shutting down connection manager              info  stresstest sorted      time limited test           shutting down node engine              info  stresstest sorted      time limited test           destroying node nodeextension            info  stresstest sorted      time limited test           hazelcast shutdown is completed in   ms            info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down          debug  stresstest sorted      time limited test           added a shutting down member                      info  stresstest sorted      time limited test           shutting down connection manager              info  stresstest sorted      time limited test           shutting down node engine              info  stresstest sorted      time limited test           destroying node nodeextension            info  stresstest sorted      time limited test           hazelcast shutdown is completed in   ms            info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown           info  stresstest sorted      time limited test               is shutting down           info  stresstest sorted      time limited test           node is already shutting down    waiting for shutdown process to complete              info  stresstest sorted      time limited test               is shutdown  buildinfo right after stresstest sorted com hazelcast jet sql slow mapindexscanpmigrationstresstest   buildinfo version        snapshot   build      buildnumber    revision    enterprise false  serializationversion     hiccups measured while running test  stresstest sorted com hazelcast jet sql slow mapindexscanpmigrationstresstest            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms            accumulated pauses    ms  max pause    ms  pauses over   ms               ,0
30085,5725524164.0,IssuesEvent,2017-04-20 16:45:41,golang/go,https://api.github.com/repos/golang/go,closed,cmd/trace: traceviewer tool doesn't work in non-chrome browsers,Documentation NeedsFix,"### What version of Go are you using (`go version`)?
go version go1.8

### What operating system and processor architecture are you using (`go env`)?
darwin/amd64

### What did you do?
Call `go tool trace trace.file` as described in https://godoc.org/cmd/trace and open the ""View trace"" link using Safari (or other non-Chrome) web browser.

### What did you expect to see?
Expected to see the Trace viewer.

### What did you see instead?
There is a JavaScript error, saying ""ReferenceError: Can't find variable: tr"" in the console of the browser.

I know that the trace-viewer itself comes from [the catapult project](https://github.com/catapult-project/catapult), as well as that the project was built specifically for Chrome and/or Android, but I think it would be worth to add a notice to `cmd/trace` documentation about this fact.
",1.0,"cmd/trace: traceviewer tool doesn't work in non-chrome browsers - ### What version of Go are you using (`go version`)?
go version go1.8

### What operating system and processor architecture are you using (`go env`)?
darwin/amd64

### What did you do?
Call `go tool trace trace.file` as described in https://godoc.org/cmd/trace and open the ""View trace"" link using Safari (or other non-Chrome) web browser.

### What did you expect to see?
Expected to see the Trace viewer.

### What did you see instead?
There is a JavaScript error, saying ""ReferenceError: Can't find variable: tr"" in the console of the browser.

I know that the trace-viewer itself comes from [the catapult project](https://github.com/catapult-project/catapult), as well as that the project was built specifically for Chrome and/or Android, but I think it would be worth to add a notice to `cmd/trace` documentation about this fact.
",1,cmd trace  traceviewer tool doesn t work in non chrome browsers       what version of go are you using   go version     go version            what operating system and processor architecture are you using   go env     darwin          what did you do   call  go tool trace trace file  as described in   and open the  view trace  link using safari  or other non chrome  web browser         what did you expect to see   expected to see the trace viewer         what did you see instead   there is a javascript error  saying  referenceerror  can t find variable  tr  in the console of the browser     i know that the trace viewer itself comes from     as well as that the project was built specifically for chrome and or android  but i think it would be worth to add a notice to  cmd trace  documentation about this fact   ,1
3198,2743660174.0,IssuesEvent,2015-04-21 23:15:17,golang/go,https://api.github.com/repos/golang/go,closed,math/big: clarify addVW and subVW preconditions,Documentation,"I'm working on an arm64 math/big implementation.

The docs for addVW (arith.go) say:

```go
// Argument y must be either 0 or 1.
func addVW_g(z, x []Word, y Word) (c Word)
```

But e.g. running `TestFloatSetPrec` sends in many values for y. The existing implementations handle them correctly. I care because my initial arm64 implementation transfers y directly to the carry flag at the start, which only works if y is 0 or 1.

subVW does not say that y must be either 0 or 1, but in practice it appears to be, and the semantics are less clear if it is not. However, TestFunVW appears to intentionally send in y=2 to confirm that there's no bad behavior when z and x are nil.

What preconditions do addVW and subVW actually have?

@griesemer feel free to clarify here or just send a CL.

(Additional docs in general in arith.go would be awesome. Right now I'm inferring shlVU and friends from the existing code.)

",1.0,"math/big: clarify addVW and subVW preconditions - I'm working on an arm64 math/big implementation.

The docs for addVW (arith.go) say:

```go
// Argument y must be either 0 or 1.
func addVW_g(z, x []Word, y Word) (c Word)
```

But e.g. running `TestFloatSetPrec` sends in many values for y. The existing implementations handle them correctly. I care because my initial arm64 implementation transfers y directly to the carry flag at the start, which only works if y is 0 or 1.

subVW does not say that y must be either 0 or 1, but in practice it appears to be, and the semantics are less clear if it is not. However, TestFunVW appears to intentionally send in y=2 to confirm that there's no bad behavior when z and x are nil.

What preconditions do addVW and subVW actually have?

@griesemer feel free to clarify here or just send a CL.

(Additional docs in general in arith.go would be awesome. Right now I'm inferring shlVU and friends from the existing code.)

",1,math big  clarify addvw and subvw preconditions   i m working on an   math big implementation     the docs for addvw  arith go  say        go     argument y must be either   or     func addvw g z  x  word  y word   c word          but e g  running  testfloatsetprec  sends in many values for y  the existing implementations handle them correctly  i care because my initial   implementation transfers y directly to the carry flag at the start  which only works if y is   or       subvw does not say that y must be either   or    but in practice it appears to be  and the semantics are less clear if it is not  however  testfunvw appears to intentionally send in y   to confirm that there s no bad behavior when z and x are nil     what preconditions do addvw and subvw actually have      griesemer feel free to clarify here or just send a cl      additional docs in general in arith go would be awesome  right now i m inferring shlvu and friends from the existing code      ,1
195127,15501387696.0,IssuesEvent,2021-03-11 10:28:29,golang/go,https://api.github.com/repos/golang/go,closed,request the chinese document page got the error,Documentation,"#### [document links](https://go-zh.org/doc/)
##### step
1. click this button
![1615457102(1)](https://user-images.githubusercontent.com/24775116/110771085-13459f80-8295-11eb-98f7-f6ab9efc618c.png)


2. got error
![1615457552(1)](https://user-images.githubusercontent.com/24775116/110771385-661f5700-8295-11eb-970d-ef501c16856f.jpg)",1.0,"request the chinese document page got the error - #### [document links](https://go-zh.org/doc/)
##### step
1. click this button
![1615457102(1)](https://user-images.githubusercontent.com/24775116/110771085-13459f80-8295-11eb-98f7-f6ab9efc618c.png)


2. got error
![1615457552(1)](https://user-images.githubusercontent.com/24775116/110771385-661f5700-8295-11eb-970d-ef501c16856f.jpg)",1,request the chinese document page got the error                   step     click this button               got error      ,1
29887,8439404065.0,IssuesEvent,2018-10-18 01:40:09,mayn/packerlicious,https://api.github.com/repos/mayn/packerlicious,closed,AmazonSourceAmiFilter#owners should be required,Hacktoberfest builder help wanted,"packer has made source_ami_filter ""owners"" required for security purposes.

update  packerlicious to make it required also


see: https://www.packer.io/docs/builders/amazon-chroot.html#source_ami_filter",1.0,"AmazonSourceAmiFilter#owners should be required - packer has made source_ami_filter ""owners"" required for security purposes.

update  packerlicious to make it required also


see: https://www.packer.io/docs/builders/amazon-chroot.html#source_ami_filter",0,amazonsourceamifilter owners should be required   packer has made source ami filter  owners  required for security purposes     update  packerlicious to make it required also      see   ,0
304843,9336443417.0,IssuesEvent,2019-03-28 21:15:09,linkerd/linkerd2,https://api.github.com/repos/linkerd/linkerd2,closed,Support Configs Override On Meshed Workloads,area/inject priority/P0,"Following discussion in [2471](https://github.com/linkerd/linkerd2/pull/2471#discussion_r265355427), we have agreed to re-visit the design around ways to support configs override during resource update. In general, we want the `inject` library to honor the config overrides annotations, even though the proxy injection process is [skipped](https://github.com/linkerd/linkerd2/blob/e862e98d1a3c533b5eefafd72afe8925dfb49ea7/pkg/inject/inject.go#L592-L623) (most relevant to existing meshed workloads). 

The approach currently used in #2471 causes the proxy configs to always be overridden, whether (auto or manual) proxy injection happens or not. It is uncertain if this will have unintended consequences on workloads that skipped the injection process. In addition, it also leads to different code path for supporting meshed and non-meshed workloads.

This task should commence immediately, after #2471 is merged.",1.0,"Support Configs Override On Meshed Workloads - Following discussion in [2471](https://github.com/linkerd/linkerd2/pull/2471#discussion_r265355427), we have agreed to re-visit the design around ways to support configs override during resource update. In general, we want the `inject` library to honor the config overrides annotations, even though the proxy injection process is [skipped](https://github.com/linkerd/linkerd2/blob/e862e98d1a3c533b5eefafd72afe8925dfb49ea7/pkg/inject/inject.go#L592-L623) (most relevant to existing meshed workloads). 

The approach currently used in #2471 causes the proxy configs to always be overridden, whether (auto or manual) proxy injection happens or not. It is uncertain if this will have unintended consequences on workloads that skipped the injection process. In addition, it also leads to different code path for supporting meshed and non-meshed workloads.

This task should commence immediately, after #2471 is merged.",0,support configs override on meshed workloads   following discussion in     we have agreed to re visit the design around ways to support configs override during resource update  in general  we want the  inject  library to honor the config overrides annotations  even though the proxy injection process is      most relevant to existing meshed workloads       the approach currently used in    causes the proxy configs to always be overridden  whether  auto or manual  proxy injection happens or not  it is uncertain if this will have unintended consequences on workloads that skipped the injection process  in addition  it also leads to different code path for supporting meshed and non meshed workloads     this task should commence immediately  after    is merged ,0
4006,6934970473.0,IssuesEvent,2017-12-03 01:36:35,bartop/tpl,https://api.github.com/repos/bartop/tpl,opened,Add gcc 4.9 in Travis CI,new feature process upgrade,gcc4.9 has theoretically all the features this library needs to work. We should try to add it to the matrix.,1.0,Add gcc 4.9 in Travis CI - gcc4.9 has theoretically all the features this library needs to work. We should try to add it to the matrix.,0,add gcc     in travis ci       has theoretically all the features this library needs to work  we should try to add it to the matrix ,0
157124,24628540212.0,IssuesEvent,2022-10-16 20:30:31,dotnet/efcore,https://api.github.com/repos/dotnet/efcore,closed,Change Detection: Exception when adding child to parent entity,closed-by-design customer-reported,"When updating an existing entity by adding children to a collection property, db context throws on SaveChanges.

'Microsoft.EntityFrameworkCore.DbUpdateConcurrencyException' occurred in System.Private.CoreLib.dll but was not handled in user code: 'Attempted to update or delete an entity that does not exist in the store.'

The same process works when creating the entity.

Update code (throws an exception):
```C#
    public async Task AddChild(Guid parentId)
    {
        var parent1 = _ctx.Parents
                .Include(item => item.Children)
                .SingleOrDefault(item => item.Id == parentId);            
        if(parent1 != null)
        {
            var child = new Child() {
                Id = Guid.NewGuid(),
                Name = ""this is a test"",
                ParentId = parentId
            };
            parent1.Children.Add(child);
    
            // _ctx.ChangeTracker.DetectChanges();
            // Console.WriteLine(_ctx.ChangeTracker.DebugView.LongView);

            await _ctx.SaveChangesAsync(); // throws exception here...
        }
    }
```
Create code (this code works):
```C#
    public async Task<Guid> CreateParent()
    {
        Guid result = Guid.Empty;
        var parent1 = new Parent() {
            Id = Guid.NewGuid(),
            Name = ""Parent1""
        };
        _ctx.Parents.Add(parent1);

        var child = new Child() {
            Id = Guid.NewGuid(),
            Name = ""Child1"",
            ParentId = parent1.Id
        };
        parent1.Children.Add(child);

        await _ctx.SaveChangesAsync();
        result = parent1.Id;
        return result;
    }
```
NOTE: The change detection does detect the new child, but the new child Status is Modified. The Status should be Added. If the status is manually set to Added, the save works as expected.

This is the output for ChangeTracker.DebugView.LongView:

```pre
Child {Id: 989eff64-6c80-4ecb-8793-ad2a057ae371} Modified
  Id: '989eff64-6c80-4ecb-8793-ad2a057ae371' PK
  Name: 'this is a test' Modified
  ParentId: '1dafab94-8334-4004-8d2d-180a65ad66ab' FK Modified
Child {Id: b934403e-949b-414d-976f-f9b971c2af1c} Unchanged
  Id: 'b934403e-949b-414d-976f-f9b971c2af1c' PK
  Name: 'Child1'
  ParentId: '1dafab94-8334-4004-8d2d-180a65ad66ab' FK
Parent {Id: 1dafab94-8334-4004-8d2d-180a65ad66ab} Unchanged
  Id: '1dafab94-8334-4004-8d2d-180a65ad66ab' PK
  Name: 'Parent1'
  Children: [{Id: b934403e-949b-414d-976f-f9b971c2af1c}, {Id: 989eff64-6c80-4ecb-8793-ad2a057ae371}]
```

This is problematic for us because we add children in a location where the DbContext is not available.

Target framework: .NET 6.0
EF Core version: 6.0.3 (latest)
Database provider: Any 
(tried: Npgsql.EntityFrameworkCore.PostgreSQL and Microsoft.EntityFrameworkCore.InMemory)
Operating system: Linux
[TestChildren.zip](https://github.com/dotnet/efcore/files/8391899/TestChildren.zip)
",1.0,"Change Detection: Exception when adding child to parent entity - When updating an existing entity by adding children to a collection property, db context throws on SaveChanges.

'Microsoft.EntityFrameworkCore.DbUpdateConcurrencyException' occurred in System.Private.CoreLib.dll but was not handled in user code: 'Attempted to update or delete an entity that does not exist in the store.'

The same process works when creating the entity.

Update code (throws an exception):
```C#
    public async Task AddChild(Guid parentId)
    {
        var parent1 = _ctx.Parents
                .Include(item => item.Children)
                .SingleOrDefault(item => item.Id == parentId);            
        if(parent1 != null)
        {
            var child = new Child() {
                Id = Guid.NewGuid(),
                Name = ""this is a test"",
                ParentId = parentId
            };
            parent1.Children.Add(child);
    
            // _ctx.ChangeTracker.DetectChanges();
            // Console.WriteLine(_ctx.ChangeTracker.DebugView.LongView);

            await _ctx.SaveChangesAsync(); // throws exception here...
        }
    }
```
Create code (this code works):
```C#
    public async Task<Guid> CreateParent()
    {
        Guid result = Guid.Empty;
        var parent1 = new Parent() {
            Id = Guid.NewGuid(),
            Name = ""Parent1""
        };
        _ctx.Parents.Add(parent1);

        var child = new Child() {
            Id = Guid.NewGuid(),
            Name = ""Child1"",
            ParentId = parent1.Id
        };
        parent1.Children.Add(child);

        await _ctx.SaveChangesAsync();
        result = parent1.Id;
        return result;
    }
```
NOTE: The change detection does detect the new child, but the new child Status is Modified. The Status should be Added. If the status is manually set to Added, the save works as expected.

This is the output for ChangeTracker.DebugView.LongView:

```pre
Child {Id: 989eff64-6c80-4ecb-8793-ad2a057ae371} Modified
  Id: '989eff64-6c80-4ecb-8793-ad2a057ae371' PK
  Name: 'this is a test' Modified
  ParentId: '1dafab94-8334-4004-8d2d-180a65ad66ab' FK Modified
Child {Id: b934403e-949b-414d-976f-f9b971c2af1c} Unchanged
  Id: 'b934403e-949b-414d-976f-f9b971c2af1c' PK
  Name: 'Child1'
  ParentId: '1dafab94-8334-4004-8d2d-180a65ad66ab' FK
Parent {Id: 1dafab94-8334-4004-8d2d-180a65ad66ab} Unchanged
  Id: '1dafab94-8334-4004-8d2d-180a65ad66ab' PK
  Name: 'Parent1'
  Children: [{Id: b934403e-949b-414d-976f-f9b971c2af1c}, {Id: 989eff64-6c80-4ecb-8793-ad2a057ae371}]
```

This is problematic for us because we add children in a location where the DbContext is not available.

Target framework: .NET 6.0
EF Core version: 6.0.3 (latest)
Database provider: Any 
(tried: Npgsql.EntityFrameworkCore.PostgreSQL and Microsoft.EntityFrameworkCore.InMemory)
Operating system: Linux
[TestChildren.zip](https://github.com/dotnet/efcore/files/8391899/TestChildren.zip)
",0,change detection  exception when adding child to parent entity   when updating an existing entity by adding children to a collection property  db context throws on savechanges      microsoft entityframeworkcore dbupdateconcurrencyexception  occurred in system private corelib dll but was not handled in user code   attempted to update or delete an entity that does not exist in the store      the same process works when creating the entity     update code  throws an exception       c       public async task addchild guid parentid                  var      ctx parents                   include item    item children                    singleordefault item    item id    parentid                        if      null                          var child   new child                      id   guid newguid                     name    this is a test                    parentid   parentid                                children add child                          ctx changetracker detectchanges                    console writeline  ctx changetracker debugview longview                  await  ctx savechangesasync       throws exception here                            create code  this code works       c       public async task  createparent                   guid result   guid empty           var     new parent                  id   guid newguid                 name                             ctx parents add                var child   new child                  id   guid newguid                 name                     parentid     id                        children add child              await  ctx savechangesasync             result     id           return result               note  the change detection does detect the new child  but the new child status is modified  the status should be added  if the status is manually set to added  the save works as expected     this is the output for changetracker debugview longview        pre  child  id             modified    id              pk    name   this is a test  modified    parentid              fk modified  child  id             unchanged    id              pk    name         parentid              fk  parent  id             unchanged    id              pk    name         children            this is problematic for us because we add children in a location where the dbcontext is not available     target framework   net      ef core version         latest   database provider  any    tried  npgsql entityframeworkcore postgresql and microsoft entityframeworkcore inmemory   operating system  linux       ,0
576602,17090621336.0,IssuesEvent,2021-07-08 16:56:24,reichlab/forecast-repository,https://api.github.com/repos/reichlab/forecast-repository,closed,"support truth ""diff"" uploads",High Priority,"Change truth uploads (and maybe be an option for non-truth forecast uploads?) to support uploading only ""diffs,"" i.e., only the retracted/updated/new prediction elements. This involves relaxing this [forecast version rule](https://docs.zoltardata.com/forecastversions/#forecast-version-rules):

> 3. New forecast versions cannot imply any retracted prediction elements in existing versions, i.e., you cannot load data that's a subset of the previous forecast's data.


This issue is based on @nickreich 's [comment](https://app.slack.com/client/T089JRGMA/C01AN0JE46R):

> re: truth upload jobs being large. I just wanted to throw out one small idea here. These jobs are big because the truth data is massive. And due to current ""duplicate forecast"" rules that require any updated forecast to also upload all original data, we need to upload all duplicate data, which makes these jobs MASSIVE. This makes sense for individual forecasts, but I wonder if maybe it is in the way for truth forecast uploads. E.g. if we relaxed the duplicate forecast upload requirement for truth data (maybe this is too big an ask to forecast updating logic?!), then we could have a lighter-weight (at least on the server) workflow that could go like this:
> 
> - input to a local function a large new truth file that is ready to be uploaded
> - download current truth
> - compare current truth with the large new truth file, extract only the ""diff"" (i.e. retracted, updated and new observations)
> - upload only the retracted/updated/new forecasts, with implicitly all the rest of the observations staying the same.
",1.0,"support truth ""diff"" uploads - Change truth uploads (and maybe be an option for non-truth forecast uploads?) to support uploading only ""diffs,"" i.e., only the retracted/updated/new prediction elements. This involves relaxing this [forecast version rule](https://docs.zoltardata.com/forecastversions/#forecast-version-rules):

> 3. New forecast versions cannot imply any retracted prediction elements in existing versions, i.e., you cannot load data that's a subset of the previous forecast's data.


This issue is based on @nickreich 's [comment](https://app.slack.com/client/T089JRGMA/C01AN0JE46R):

> re: truth upload jobs being large. I just wanted to throw out one small idea here. These jobs are big because the truth data is massive. And due to current ""duplicate forecast"" rules that require any updated forecast to also upload all original data, we need to upload all duplicate data, which makes these jobs MASSIVE. This makes sense for individual forecasts, but I wonder if maybe it is in the way for truth forecast uploads. E.g. if we relaxed the duplicate forecast upload requirement for truth data (maybe this is too big an ask to forecast updating logic?!), then we could have a lighter-weight (at least on the server) workflow that could go like this:
> 
> - input to a local function a large new truth file that is ready to be uploaded
> - download current truth
> - compare current truth with the large new truth file, extract only the ""diff"" (i.e. retracted, updated and new observations)
> - upload only the retracted/updated/new forecasts, with implicitly all the rest of the observations staying the same.
",0,support truth  diff  uploads   change truth uploads  and maybe be an option for non truth forecast uploads   to support uploading only  diffs   i e   only the retracted updated new prediction elements  this involves relaxing this             new forecast versions cannot imply any retracted prediction elements in existing versions  i e   you cannot load data that s a subset of the previous forecast s data       this issue is based on  nickreich  s          re  truth upload jobs being large  i just wanted to throw out one small idea here  these jobs are big because the truth data is massive  and due to current  duplicate forecast  rules that require any updated forecast to also upload all original data  we need to upload all duplicate data  which makes these jobs massive  this makes sense for individual forecasts  but i wonder if maybe it is in the way for truth forecast uploads  e g  if we relaxed the duplicate forecast upload requirement for truth data  maybe this is too big an ask to forecast updating logic     then we could have a lighter weight  at least on the server  workflow that could go like this           input to a local function a large new truth file that is ready to be uploaded      download current truth      compare current truth with the large new truth file  extract only the  diff   i e  retracted  updated and new observations       upload only the retracted updated new forecasts  with implicitly all the rest of the observations staying the same   ,0
182564,14917832723.0,IssuesEvent,2021-01-22 20:33:34,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/gopls: include a link to useful docs in the workspace load error notification,Documentation Tools gopls,"<img width=""653"" alt=""Screen Shot 2021-01-08 at 1 55 22 PM"" src=""https://user-images.githubusercontent.com/4999471/104053574-81001d00-51b9-11eb-9776-5068e1a4466c.png"">
This notification is pretty nice!
But for users who are not familiar with modules and nested modules (is it official terminology?), this message may still sound cryptic. Link to any useful documentation would be helpful.",1.0,"x/tools/gopls: include a link to useful docs in the workspace load error notification - <img width=""653"" alt=""Screen Shot 2021-01-08 at 1 55 22 PM"" src=""https://user-images.githubusercontent.com/4999471/104053574-81001d00-51b9-11eb-9776-5068e1a4466c.png"">
This notification is pretty nice!
But for users who are not familiar with modules and nested modules (is it official terminology?), this message may still sound cryptic. Link to any useful documentation would be helpful.",1,x tools gopls  include a link to useful docs in the workspace load error notification    img width     alt  screen shot       at       pm  src     this notification is pretty nice   but for users who are not familiar with modules and nested modules  is it official terminology    this message may still sound cryptic  link to any useful documentation would be helpful ,1
172865,14394512144.0,IssuesEvent,2020-12-03 01:27:56,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.16: document encoding/json changes for Go 1.16,Documentation NeedsInvestigation release-blocker,"As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

<dl id=""encoding/json""><dt><a href=""/pkg/encoding/json/"">encoding/json</a></dt>
  <dd>
    <p><!-- CL 263619 -->
      The error message for
      <a href=""/pkg/encoding/json/#SyntaxError"">SyntaxError</a>
      now begins with ""json: "", matching the other errors in the package.
    </p>
    <p><!-- CL 234818 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/234818"">https://golang.org/cl/234818</a>: allow semicolon in field key / struct tag
    </p>
  </dd>
</dl><!-- encoding/json -->

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.",1.0,"doc/go1.16: document encoding/json changes for Go 1.16 - As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

<dl id=""encoding/json""><dt><a href=""/pkg/encoding/json/"">encoding/json</a></dt>
  <dd>
    <p><!-- CL 263619 -->
      The error message for
      <a href=""/pkg/encoding/json/#SyntaxError"">SyntaxError</a>
      now begins with ""json: "", matching the other errors in the package.
    </p>
    <p><!-- CL 234818 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/234818"">https://golang.org/cl/234818</a>: allow semicolon in field key / struct tag
    </p>
  </dd>
</dl><!-- encoding/json -->

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.",1,doc      document encoding json changes for go       as of filing this issue  the     contained the following html        encoding json                       the error message for         syntaxerror         now begins with  json     matching the other errors in the package                         todo    a href    allow semicolon in field key   struct tag                           per     it s a release blocker for go     beta   to have a complete draft of the eventual release notes  and so the todo needs to be resolved     a sequence of steps to resolve this issue may be        come up with a draft release note entry in this issue  then move the issue to needsfix state      send a cl with  doc           and include  for     fixes   this issue    in the body ,1
53299,7822327655.0,IssuesEvent,2018-06-14 01:48:49,golang/go,https://api.github.com/repos/golang/go,closed,docs: document standard way to recognize machine generated files,Documentation help wanted,"in https://github.com/golang/go/issues/13560#issuecomment-288494154 bradfitz said the wiki would be edited but I can't seem to find anything on the wiki or even googling `golang standard comment on machine generated files`. Only the original issue comes up. We should document it somewhere appropriate.

Maybe https://blog.golang.org/generate could be updated to mention it?",1.0,"docs: document standard way to recognize machine generated files - in https://github.com/golang/go/issues/13560#issuecomment-288494154 bradfitz said the wiki would be edited but I can't seem to find anything on the wiki or even googling `golang standard comment on machine generated files`. Only the original issue comes up. We should document it somewhere appropriate.

Maybe https://blog.golang.org/generate could be updated to mention it?",1,docs  document standard way to recognize machine generated files   in   bradfitz said the wiki would be edited but i can t seem to find anything on the wiki or even googling  golang standard comment on machine generated files   only the original issue comes up  we should document it somewhere appropriate     maybe   could be updated to mention it ,1
130647,18103121087.0,IssuesEvent,2021-09-22 16:07:07,betagouv/mon-entreprise,https://api.github.com/repos/betagouv/mon-entreprise,closed,UI : afficher les options de partage et d'impression sur une seule ligne,🎨 design,"Je trouve que les options de partage et d'impression prennent trop d'espace vertical :

![image](https://user-images.githubusercontent.com/1730702/134036104-f9cfa792-f41e-41e4-9a30-4c135e0580f5.png)

On pourrait regrouper ces deux lignes en une seule.",1.0,"UI : afficher les options de partage et d'impression sur une seule ligne - Je trouve que les options de partage et d'impression prennent trop d'espace vertical :

![image](https://user-images.githubusercontent.com/1730702/134036104-f9cfa792-f41e-41e4-9a30-4c135e0580f5.png)

On pourrait regrouper ces deux lignes en une seule.",0,ui   afficher les options de partage et d impression sur une seule ligne   je trouve que les options de partage et d impression prennent trop d espace vertical              on pourrait regrouper ces deux lignes en une seule ,0
98114,11045494462.0,IssuesEvent,2019-12-09 15:12:54,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: confusing docs for -dropreplace,Documentation NeedsInvestigation modules,"I wanted to programmatically drop all replace directives for a particular module.

Based on the docs, I initially thought just using `-dropreplace=old`, with no `@v`, would drop all replace directives for that module path:

```
The -replace=old[@v]=new[@v] and -dropreplace=old[@v] flags
add and drop a replacement of the given module path and version pair.
If the @v in old@v is omitted, the replacement applies to all versions
with the old module path.
```

It sounds from this like omitting the `@v` from a `-dropreplace` flag will make it apply to (drop) all versions with the old module path. What it actually does is drop any replace directives for that module path that do not specify a version.

It might be worth clarifying the docs a little.
",1.0,"cmd/go: confusing docs for -dropreplace - I wanted to programmatically drop all replace directives for a particular module.

Based on the docs, I initially thought just using `-dropreplace=old`, with no `@v`, would drop all replace directives for that module path:

```
The -replace=old[@v]=new[@v] and -dropreplace=old[@v] flags
add and drop a replacement of the given module path and version pair.
If the @v in old@v is omitted, the replacement applies to all versions
with the old module path.
```

It sounds from this like omitting the `@v` from a `-dropreplace` flag will make it apply to (drop) all versions with the old module path. What it actually does is drop any replace directives for that module path that do not specify a version.

It might be worth clarifying the docs a little.
",1,cmd go  confusing docs for  dropreplace   i wanted to programmatically drop all replace directives for a particular module     based on the docs  i initially thought just using   dropreplace old   with no   v   would drop all replace directives for that module path          the  replace old  new  and  dropreplace old  flags  add and drop a replacement of the given module path and version pair   if the  v in old v is omitted  the replacement applies to all versions  with the old module path          it sounds from this like omitting the   v  from a   dropreplace  flag will make it apply to  drop  all versions with the old module path  what it actually does is drop any replace directives for that module path that do not specify a version     it might be worth clarifying the docs a little   ,1
24809,17791839117.0,IssuesEvent,2021-08-31 17:06:09,qoollo/bob,https://api.github.com/repos/qoollo/bob,opened,Write a description on Docker Hub,infrastructure,"Required parts:
1. Bob description (can be taken from Readme)
2. Link to GitHub repository
3. Link to Wiki on GitHub
4. Versions description (8 bytes key vs 16 bytes key, alpine vs ubuntu)
5. How to use the image. Command to run it, exposed ports and directories, ulimit
6. Configuration details. List of configuration files, their purpose, links to examples in this repository and to description in Wiki 

Source of inspiration: https://hub.docker.com/r/yandex/clickhouse-server",1.0,"Write a description on Docker Hub - Required parts:
1. Bob description (can be taken from Readme)
2. Link to GitHub repository
3. Link to Wiki on GitHub
4. Versions description (8 bytes key vs 16 bytes key, alpine vs ubuntu)
5. How to use the image. Command to run it, exposed ports and directories, ulimit
6. Configuration details. List of configuration files, their purpose, links to examples in this repository and to description in Wiki 

Source of inspiration: https://hub.docker.com/r/yandex/clickhouse-server",0,write a description on docker hub   required parts      bob description  can be taken from readme      link to github repository     link to wiki on github     versions description    bytes key vs   bytes key  alpine vs ubuntu      how to use the image  command to run it  exposed ports and directories  ulimit     configuration details  list of configuration files  their purpose  links to examples in this repository and to description in wiki     source of inspiration   ,0
71105,15180723282.0,IssuesEvent,2021-02-15 01:01:08,LevyForchh/octobot,https://api.github.com/repos/LevyForchh/octobot,closed,CVE-2020-35912 (Low) detected in lock_api-0.1.5.crate - autoclosed,security vulnerability,"## CVE-2020-35912 - Low Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lock_api-0.1.5.crate</b></p></summary>

<p>Wrappers to create fully-featured Mutex and RwLock types. Compatible with no_std.</p>
<p>Library home page: <a href=""https://crates.io/api/v1/crates/lock_api/0.1.5/download"">https://crates.io/api/v1/crates/lock_api/0.1.5/download</a></p>
<p>

Dependency Hierarchy:
  - hyper-rustls-0.16.1.crate (Root Library)
    - hyper-0.12.25.crate
      - tokio-tcp-0.1.3.crate
        - tokio-reactor-0.1.9.crate
          - parking_lot-0.7.1.crate
            - :x: **lock_api-0.1.5.crate** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockWriteGuard unsoundness.

<p>Publish Date: 2020-12-31
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-35912>CVE-2020-35912</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>1.9</b>)</summary>
<p>

Base Score Metrics not available</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":false,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Crate"",""packageName"":""lock_api"",""packageVersion"":""0.1.5"",""packageFilePaths"":[],""isTransitiveDependency"":true,""dependencyTree"":""hyper-rustls:0.16.1;hyper:0.12.25;tokio-tcp:0.1.3;tokio-reactor:0.1.9;parking_lot:0.7.1;lock_api:0.1.5"",""isMinimumFixVersionAvailable"":false}],""baseBranches"":[],""vulnerabilityIdentifier"":""CVE-2020-35912"",""vulnerabilityDetails"":""An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockWriteGuard unsoundness."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-35912"",""cvss2Severity"":""low"",""cvss2Score"":""1.9"",""extraData"":{}}</REMEDIATE> -->",True,"CVE-2020-35912 (Low) detected in lock_api-0.1.5.crate - autoclosed - ## CVE-2020-35912 - Low Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lock_api-0.1.5.crate</b></p></summary>

<p>Wrappers to create fully-featured Mutex and RwLock types. Compatible with no_std.</p>
<p>Library home page: <a href=""https://crates.io/api/v1/crates/lock_api/0.1.5/download"">https://crates.io/api/v1/crates/lock_api/0.1.5/download</a></p>
<p>

Dependency Hierarchy:
  - hyper-rustls-0.16.1.crate (Root Library)
    - hyper-0.12.25.crate
      - tokio-tcp-0.1.3.crate
        - tokio-reactor-0.1.9.crate
          - parking_lot-0.7.1.crate
            - :x: **lock_api-0.1.5.crate** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockWriteGuard unsoundness.

<p>Publish Date: 2020-12-31
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-35912>CVE-2020-35912</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>1.9</b>)</summary>
<p>

Base Score Metrics not available</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":false,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Crate"",""packageName"":""lock_api"",""packageVersion"":""0.1.5"",""packageFilePaths"":[],""isTransitiveDependency"":true,""dependencyTree"":""hyper-rustls:0.16.1;hyper:0.12.25;tokio-tcp:0.1.3;tokio-reactor:0.1.9;parking_lot:0.7.1;lock_api:0.1.5"",""isMinimumFixVersionAvailable"":false}],""baseBranches"":[],""vulnerabilityIdentifier"":""CVE-2020-35912"",""vulnerabilityDetails"":""An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockWriteGuard unsoundness."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-35912"",""cvss2Severity"":""low"",""cvss2Score"":""1.9"",""extraData"":{}}</REMEDIATE> -->",0,cve      low  detected in lock api       crate   autoclosed      cve       low severity vulnerability     vulnerable library    lock api       crate      wrappers to create fully featured mutex and rwlock types  compatible with no std    library home page   a href       dependency hierarchy      hyper rustls       crate  root library        hyper       crate         tokio tcp       crate           tokio reactor       crate             parking lot       crate                x    lock api       crate    vulnerable library             vulnerability details         an issue was discovered in the lock api crate before       for rust  a data race can occur because of mappedrwlockwriteguard unsoundness    publish date         url   a href              cvss   score details             base score metrics not available              isopenpronvulnerability  false  ispackagebased  true  isdefaultbranch  true  packages     istransitivedependency  true  dependencytree   hyper rustls       hyper       tokio tcp       tokio reactor       parking lot       lock api         isminimumfixversionavailable  false    basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   an issue was discovered in the lock api crate before       for rust  a data race can occur because of mappedrwlockwriteguard unsoundness    vulnerabilityurl        ,0
114610,11852049517.0,IssuesEvent,2020-03-24 19:11:54,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: document using 'go list' to download modules needed to build packages,Documentation NeedsFix modules,"`go list -test ./...` can be used to download the modules needed to build tests of the packages matched by `./...`. This is usually a smaller set of modules than `go mod download all` (or equivalent `go mod download`) would select, so it's a useful command when building small Docker images.

This should be documented as a FAQ on https://github.com/golang/go/wiki/Modules.

Related #36460: fewer modules will be downloaded by `go mod download all` when lazy module loading is implemented.",1.0,"cmd/go: document using 'go list' to download modules needed to build packages - `go list -test ./...` can be used to download the modules needed to build tests of the packages matched by `./...`. This is usually a smaller set of modules than `go mod download all` (or equivalent `go mod download`) would select, so it's a useful command when building small Docker images.

This should be documented as a FAQ on https://github.com/golang/go/wiki/Modules.

Related #36460: fewer modules will be downloaded by `go mod download all` when lazy module loading is implemented.",1,cmd go  document using  go list  to download modules needed to build packages    go list  test        can be used to download the modules needed to build tests of the packages matched by          this is usually a smaller set of modules than  go mod download all   or equivalent  go mod download   would select  so it s a useful command when building small docker images     this should be documented as a faq on      related     fewer modules will be downloaded by  go mod download all  when lazy module loading is implemented ,1
79572,15223190868.0,IssuesEvent,2021-02-18 02:04:20,sourcegraph/sourcegraph,https://api.github.com/repos/sourcegraph/sourcegraph,opened,RFC 311: Independently configure,RFC-311 code-intelligence-performance team/code-intelligence,"Part of [RFC 311: Out of band migrations](https://docs.google.com/document/d/1q59lyj-tLEmEQBe3k9bTQj85NR4abfk2SLNS6UkmcdM).

https://github.com/sourcegraph/sourcegraph/issues/18407 isolated each migrator run. The tick and recheck times for each migration should be independently configurable (e.g., one migrator should be called once a minute; another once every 10 seconds while active).",2.0,"RFC 311: Independently configure - Part of [RFC 311: Out of band migrations](https://docs.google.com/document/d/1q59lyj-tLEmEQBe3k9bTQj85NR4abfk2SLNS6UkmcdM).

https://github.com/sourcegraph/sourcegraph/issues/18407 isolated each migrator run. The tick and recheck times for each migration should be independently configurable (e.g., one migrator should be called once a minute; another once every 10 seconds while active).",0,rfc    independently configure   part of          isolated each migrator run  the tick and recheck times for each migration should be independently configurable  e g   one migrator should be called once a minute  another once every   seconds while active  ,0
45678,7195418698.0,IssuesEvent,2018-02-04 16:58:10,golang/go,https://api.github.com/repos/golang/go,opened,strconv: Unquote example looks like a unit test instead of an example,Documentation NeedsFix help wanted,"The Unquote example (https://golang.org/pkg/strconv/#Unquote) looks like a unit test instead of an example.

That is a sea of backslashes and quotes. I think we could make a more readable example.
",1.0,"strconv: Unquote example looks like a unit test instead of an example - The Unquote example (https://golang.org/pkg/strconv/#Unquote) looks like a unit test instead of an example.

That is a sea of backslashes and quotes. I think we could make a more readable example.
",1,strconv  unquote example looks like a unit test instead of an example   the unquote example    looks like a unit test instead of an example     that is a sea of backslashes and quotes  i think we could make a more readable example   ,1
136521,12717504131.0,IssuesEvent,2020-06-24 05:21:54,golang/go,https://api.github.com/repos/golang/go,closed,"x/tools/internal/gocommand: documentation doesn't state what Run{,Piped,Raw} do and what they returns",Documentation NeedsInvestigation Tools,"There are 3 exported identifiers with the word ""Run"" in package [`golang.org/x/tools/internal/gocommand`](https://pkg.go.dev/golang.org/x/tools/internal/gocommand). None of them say what the identifiers do and what they return. Each one says ""it's like this other Run variant"". This makes it hard to know how to use the API of `gocommand` package.

```Go
// RunPiped is like Run, but relies on the given stdout/stderr
func (i *Invocation) RunPiped(ctx context.Context, stdout, stderr io.Writer) error

// Run calls Runner.RunRaw, serializing requests if they fight over go.mod changes.
func (runner *Runner) Run(ctx context.Context, inv Invocation) (*bytes.Buffer, error)

// RunRaw calls Invocation.runRaw, serializing requests if they fight over go.mod changes.
func (runner *Runner) RunRaw(ctx context.Context, inv Invocation) (*bytes.Buffer, *bytes.Buffer, error, error)
```

Documentation for `Invocation.runRaw` isn't readily visible because it's an unexported identifier:

```Go
// RunRaw is like RunPiped, but also returns the raw stderr and error for callers
// that want to do low-level error handling/recovery.
func (i *Invocation) runRaw(ctx context.Context) (stdout *bytes.Buffer, stderr *bytes.Buffer, friendlyError error, rawError error)
```

It has named return values that help.

The `Runner` type is documented as follows:

```
// An Runner will run go command invocations and serialize them if it sees a concurrency error.
```

Perhaps that should be made more visible on the methods, and their `*bytes.Buffer` and `error` results can be given names like `stdout`, `stderr` to help clarify what's what.

/cc @heschik",1.0,"x/tools/internal/gocommand: documentation doesn't state what Run{,Piped,Raw} do and what they returns - There are 3 exported identifiers with the word ""Run"" in package [`golang.org/x/tools/internal/gocommand`](https://pkg.go.dev/golang.org/x/tools/internal/gocommand). None of them say what the identifiers do and what they return. Each one says ""it's like this other Run variant"". This makes it hard to know how to use the API of `gocommand` package.

```Go
// RunPiped is like Run, but relies on the given stdout/stderr
func (i *Invocation) RunPiped(ctx context.Context, stdout, stderr io.Writer) error

// Run calls Runner.RunRaw, serializing requests if they fight over go.mod changes.
func (runner *Runner) Run(ctx context.Context, inv Invocation) (*bytes.Buffer, error)

// RunRaw calls Invocation.runRaw, serializing requests if they fight over go.mod changes.
func (runner *Runner) RunRaw(ctx context.Context, inv Invocation) (*bytes.Buffer, *bytes.Buffer, error, error)
```

Documentation for `Invocation.runRaw` isn't readily visible because it's an unexported identifier:

```Go
// RunRaw is like RunPiped, but also returns the raw stderr and error for callers
// that want to do low-level error handling/recovery.
func (i *Invocation) runRaw(ctx context.Context) (stdout *bytes.Buffer, stderr *bytes.Buffer, friendlyError error, rawError error)
```

It has named return values that help.

The `Runner` type is documented as follows:

```
// An Runner will run go command invocations and serialize them if it sees a concurrency error.
```

Perhaps that should be made more visible on the methods, and their `*bytes.Buffer` and `error` results can be given names like `stdout`, `stderr` to help clarify what's what.

/cc @heschik",1,x tools internal gocommand  documentation doesn t state what run  piped raw  do and what they returns   there are   exported identifiers with the word  run  in package     none of them say what the identifiers do and what they return  each one says  it s like this other run variant   this makes it hard to know how to use the api of  gocommand  package        go     runpiped is like run  but relies on the given stdout stderr  func  i  invocation  runpiped ctx context context  stdout  stderr io writer  error       run calls runner runraw  serializing requests if they fight over go mod changes   func  runner  runner  run ctx context context  inv invocation    bytes buffer  error        runraw calls invocation runraw  serializing requests if they fight over go mod changes   func  runner  runner  runraw ctx context context  inv invocation    bytes buffer   bytes buffer  error  error          documentation for  invocation runraw  isn t readily visible because it s an unexported identifier        go     runraw is like runpiped  but also returns the raw stderr and error for callers     that want to do low level error handling recovery   func  i  invocation  runraw ctx context context   stdout  bytes buffer  stderr  bytes buffer  friendlyerror error  rawerror error          it has named return values that help     the  runner  type is documented as follows             an runner will run go command invocations and serialize them if it sees a concurrency error          perhaps that should be made more visible on the methods  and their   bytes buffer  and  error  results can be given names like  stdout    stderr  to help clarify what s what      cc  heschik,1
230529,7611204373.0,IssuesEvent,2018-05-01 12:53:03,ropensci/drake,https://api.github.com/repos/ropensci/drake,opened,A quicker end to staged parallelism,priority: high topic: efficiency,"## The problem

With the exception of `make(parallelism = ""future"")` and `make(parallelism = ""Makefile"")`, `drake` has an embarrassing approach to parallelism, both literally and figuratively. It divides the dependency graph into conditionally independent stages and then runs those stages sequentially. Targets only run in parallel within those stages. In other words, `drake` waits for the slowest target to finish before moving to the next stage.

![capture](https://user-images.githubusercontent.com/1580860/39472822-a6d211b6-4d19-11e8-820c-1e4c05f637cf.PNG)

At the time, I could not find an R package to traverse an arbitrary network of jobs in parallel. (**Stop me right here if such a tool actually exists!**) Parallel computing options like `foreach`, `parLapply`, `mclapply`, and `future_lapply` all assume the workers can act independently. So I thought staged parallelism was natural. However, I was thinking within the constraints of the available technology, and parallel efficiency suffered.

## Long-term work

In late February, I started the [`workers`](https://github.com/wlandau/workers) package. If you give it a job network and a parallel computing technology, the goal is to traverse the graph using a state-of-the-art algorithm. It has a proof-of-concept implementation and an initial [design specification](https://github.com/wlandau/workers/tree/master/specification), but it has a long way to go. At this stage, it really needs an R-focused [message queue](http://queues.io/). I was hoping [`liteq`](https://github.com/r-lib/liteq) would work, but due to an [apparent race condition](https://github.com/r-lib/liteq/issues/17) and some speed/overhead issues on my end, I am stuck for the time being.

## Now

I say we rework the `make(parallelism = ""mclapply"")` and `make(parallelism = ""parLapply"")` backends natively. As I see it, `make(parallelism = ""mclapply"", jobs = 2)` should fork 3 processes: 2 workers and 1 master. The master sends jobs to the workers in the correct order at the correct time, and the workers keep coming back for more. The goal is to drive overhead down as much as possible, so the workers are persistent.

The implementation will be similar to `make(parallelism = ""future"", caching = ""worker"")` (see [`future.R`](https://github.com/ropensci/drake/blob/master/R/future.R)). I think the implementation should go into `drake` itself because 

1. The code should be relatively short, and
2. I do not want to lock in the design of [`workers`](https://github.com/wlandau/workers) until I get the chance to do an extensive lit review of parallel graph algorithms.

",1.0,"A quicker end to staged parallelism - ## The problem

With the exception of `make(parallelism = ""future"")` and `make(parallelism = ""Makefile"")`, `drake` has an embarrassing approach to parallelism, both literally and figuratively. It divides the dependency graph into conditionally independent stages and then runs those stages sequentially. Targets only run in parallel within those stages. In other words, `drake` waits for the slowest target to finish before moving to the next stage.

![capture](https://user-images.githubusercontent.com/1580860/39472822-a6d211b6-4d19-11e8-820c-1e4c05f637cf.PNG)

At the time, I could not find an R package to traverse an arbitrary network of jobs in parallel. (**Stop me right here if such a tool actually exists!**) Parallel computing options like `foreach`, `parLapply`, `mclapply`, and `future_lapply` all assume the workers can act independently. So I thought staged parallelism was natural. However, I was thinking within the constraints of the available technology, and parallel efficiency suffered.

## Long-term work

In late February, I started the [`workers`](https://github.com/wlandau/workers) package. If you give it a job network and a parallel computing technology, the goal is to traverse the graph using a state-of-the-art algorithm. It has a proof-of-concept implementation and an initial [design specification](https://github.com/wlandau/workers/tree/master/specification), but it has a long way to go. At this stage, it really needs an R-focused [message queue](http://queues.io/). I was hoping [`liteq`](https://github.com/r-lib/liteq) would work, but due to an [apparent race condition](https://github.com/r-lib/liteq/issues/17) and some speed/overhead issues on my end, I am stuck for the time being.

## Now

I say we rework the `make(parallelism = ""mclapply"")` and `make(parallelism = ""parLapply"")` backends natively. As I see it, `make(parallelism = ""mclapply"", jobs = 2)` should fork 3 processes: 2 workers and 1 master. The master sends jobs to the workers in the correct order at the correct time, and the workers keep coming back for more. The goal is to drive overhead down as much as possible, so the workers are persistent.

The implementation will be similar to `make(parallelism = ""future"", caching = ""worker"")` (see [`future.R`](https://github.com/ropensci/drake/blob/master/R/future.R)). I think the implementation should go into `drake` itself because 

1. The code should be relatively short, and
2. I do not want to lock in the design of [`workers`](https://github.com/wlandau/workers) until I get the chance to do an extensive lit review of parallel graph algorithms.

",0,a quicker end to staged parallelism      the problem    with the exception of  make parallelism    future    and  make parallelism    makefile      drake  has an embarrassing approach to parallelism  both literally and figuratively  it divides the dependency graph into conditionally independent stages and then runs those stages sequentially  targets only run in parallel within those stages  in other words   drake  waits for the slowest target to finish before moving to the next stage             at the time  i could not find an r package to traverse an arbitrary network of jobs in parallel     stop me right here if such a tool actually exists     parallel computing options like  foreach    parlapply    mclapply   and  future lapply  all assume the workers can act independently  so i thought staged parallelism was natural  however  i was thinking within the constraints of the available technology  and parallel efficiency suffered        long term work    in late february  i started the     package  if you give it a job network and a parallel computing technology  the goal is to traverse the graph using a state of the art algorithm  it has a proof of concept implementation and an initial     but it has a long way to go  at this stage  it really needs an r focused     i was hoping     would work  but due to an     and some speed overhead issues on my end  i am stuck for the time being        now    i say we rework the  make parallelism    mclapply    and  make parallelism    parlapply    backends natively  as i see it   make parallelism    mclapply   jobs       should fork   processes    workers and   master  the master sends jobs to the workers in the correct order at the correct time  and the workers keep coming back for more  the goal is to drive overhead down as much as possible  so the workers are persistent     the implementation will be similar to  make parallelism    future   caching    worker     see     i think the implementation should go into  drake  itself because        the code should be relatively short  and     i do not want to lock in the design of     until i get the chance to do an extensive lit review of parallel graph algorithms     ,0
276822,8609827927.0,IssuesEvent,2018-11-19 01:04:36,webcompat/web-bugs,https://api.github.com/repos/webcompat/web-bugs,closed,firefox.webex.com - “Chat” icon is displayed truncated,browser-firefox priority-important severity-minor type-enterprise-survey,"<!-- @browser: Firefox ESR  60.3.0esr -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0 -->
<!-- @reported_with: web -->

**URL**: https://firefox.webex.com/webappng/sites/firefox/dashboard?siteurl=firefox

**Browser / Version**: Firefox ESR  60.3.0esr
**Operating System**: Windows 10 Pro
**Tested Another Browser**: Yes

**Problem type**: Design is broken
**Description**: “Chat” icon is displayed truncated
**Steps to Reproduce**:
**Prerequisites:**
    1. WebEx account available and signed in.
    2. Meetings available. 
**Steps to Reproduce:**
    1. Navigate to https://firefox.webex.com/webappng/sites/firefox/dashboard?siteurl=firefox 
    2. Start/Join a meeting.
    3. After the meeting starts, click the “Chat” icon.
    4. Observe the “Chat” window.
        
**Expected Behavior:**
“Chat” icon is fully visible.

**Actual Behavior:**
“Chat” icon is displayed truncated on the left side.
 
**Note:**
    1. Also reproducible on Firefox Nightly 65.0a1 (2018-11-06).
    2. Not reproducible on Chrome 70.0.3538.77 and Microsoft Edge 41.16299.726.0.
    3. Screenshot attached.
Affected area:
```html
<span class=""chat-avatar-toall icon-avatar-toall"">
	<svg class=""svg-icon"" width=""20"" height=""20"">
		<use class=""symbol symbol-vi-chat-group-20"" xlink:href=""#vi_chat_group_20""></use>
	</svg>
</span>
```

**Watchers:**
@softvision-sergiulogigan
@softvision-oana-arbuzov

sv; type: enterprise-survey
[![Screenshot Description](https://webcompat.com/uploads/2018/11/2a397958-86c3-4a0b-9805-be35e561d890-thumb.jpeg)](https://webcompat.com/uploads/2018/11/2a397958-86c3-4a0b-9805-be35e561d890.jpeg)

<details>
<summary>Browser Configuration</summary>
<ul>
  <li>None</li>
</ul>

</details>

_From [webcompat.com](https://webcompat.com/) with ❤️_",1.0,"firefox.webex.com - “Chat” icon is displayed truncated - <!-- @browser: Firefox ESR  60.3.0esr -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0 -->
<!-- @reported_with: web -->

**URL**: https://firefox.webex.com/webappng/sites/firefox/dashboard?siteurl=firefox

**Browser / Version**: Firefox ESR  60.3.0esr
**Operating System**: Windows 10 Pro
**Tested Another Browser**: Yes

**Problem type**: Design is broken
**Description**: “Chat” icon is displayed truncated
**Steps to Reproduce**:
**Prerequisites:**
    1. WebEx account available and signed in.
    2. Meetings available. 
**Steps to Reproduce:**
    1. Navigate to https://firefox.webex.com/webappng/sites/firefox/dashboard?siteurl=firefox 
    2. Start/Join a meeting.
    3. After the meeting starts, click the “Chat” icon.
    4. Observe the “Chat” window.
        
**Expected Behavior:**
“Chat” icon is fully visible.

**Actual Behavior:**
“Chat” icon is displayed truncated on the left side.
 
**Note:**
    1. Also reproducible on Firefox Nightly 65.0a1 (2018-11-06).
    2. Not reproducible on Chrome 70.0.3538.77 and Microsoft Edge 41.16299.726.0.
    3. Screenshot attached.
Affected area:
```html
<span class=""chat-avatar-toall icon-avatar-toall"">
	<svg class=""svg-icon"" width=""20"" height=""20"">
		<use class=""symbol symbol-vi-chat-group-20"" xlink:href=""#vi_chat_group_20""></use>
	</svg>
</span>
```

**Watchers:**
@softvision-sergiulogigan
@softvision-oana-arbuzov

sv; type: enterprise-survey
[![Screenshot Description](https://webcompat.com/uploads/2018/11/2a397958-86c3-4a0b-9805-be35e561d890-thumb.jpeg)](https://webcompat.com/uploads/2018/11/2a397958-86c3-4a0b-9805-be35e561d890.jpeg)

<details>
<summary>Browser Configuration</summary>
<ul>
  <li>None</li>
</ul>

</details>

_From [webcompat.com](https://webcompat.com/) with ❤️_",0,firefox webex com   “chat” icon is displayed truncated            url         browser   version    firefox esr          operating system    windows   pro   tested another browser    yes    problem type    design is broken   description    “chat” icon is displayed truncated   steps to reproduce      prerequisites            webex account available and signed in          meetings available      steps to reproduce            navigate to            start join a meeting          after the meeting starts  click the “chat” icon          observe the “chat” window               expected behavior     “chat” icon is fully visible       actual behavior     “chat” icon is displayed truncated on the left side        note            also reproducible on firefox nightly                      not reproducible on chrome         and microsoft edge                  screenshot attached   affected area      html     	   		    	               watchers      softvision sergiulogigan   softvision oana arbuzov    sv  type  enterprise survey          browser configuration       none         from     with ❤️ ,0
164597,6229607460.0,IssuesEvent,2017-07-11 04:48:23,TheParrotsAreComing/PAS,https://api.github.com/repos/TheParrotsAreComing/PAS,closed,"Users/View on mobile: Click Paw button, Delete, cancel. Then it takes two clicks to bring paw menu back up.",bug HIGH PRIORITY,"Due to making the delete modal add-adopter-floating-overlay instead of the default data-ix stuff, most likely. It's a temporary fix.",1.0,"Users/View on mobile: Click Paw button, Delete, cancel. Then it takes two clicks to bring paw menu back up. - Due to making the delete modal add-adopter-floating-overlay instead of the default data-ix stuff, most likely. It's a temporary fix.",0,users view on mobile  click paw button  delete  cancel  then it takes two clicks to bring paw menu back up    due to making the delete modal add adopter floating overlay instead of the default data ix stuff  most likely  it s a temporary fix ,0
67570,20997493396.0,IssuesEvent,2022-03-29 14:36:17,SeleniumHQ/selenium,https://api.github.com/repos/SeleniumHQ/selenium,closed,[🐛 Bug]: SessionNotCreatedException for Edge in IE Mode,D-IE I-defect D-edge,"### What happened?

I am facing issue while automating the application using Selenium 4 in IE mode in Microsoft Edge with Internet Explorer Driver. 
I have followed the steps given in the [Microsoft Blog](https://blogs.windows.com/msedgedev/2022/02/01/test-ie-mode-in-microsoft-edge-internet-explorer-driver/)  but still not able to get the results.
Language Used- JAVA
Browser- IE Compatibility Mode 

Code Snippet- 
 public static void main(String[] args) {        
        InternetExplorerOptions ieOptions = new InternetExplorerOptions();
        ieOptions.attachToEdgeChrome();
        ieOptions.withEdgeExecutablePath(""C:\\Program Files (x86)\\Microsoft\\Edge\\Application\\msedge.exe"");
        
        WebDriver driver = new InternetExplorerDriver(ieOptions);
        driver.get(""http://www.bing.com"");
        WebElement elem = driver.findElement(By.id(""sb_form_q""));
        elem.sendKeys(""IE mode"", Keys.RETURN);
        driver.close();
    }
Issue: I am able to launch the browser in ""Edge compatibility mode"" but not able to move further. The screen is stuck on the page with following error:

 ""This is the initial start page for the WebDriver server"".

![image](https://user-images.githubusercontent.com/63354414/156769485-5c7d2c43-4816-43e6-a0d9-e277f3165e7b.png)


### How can we reproduce the issue?

```shell
import org.openqa.selenium.By;
import org.openqa.selenium.Keys;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
import org.openqa.selenium.ie.InternetExplorerDriver;
import org.openqa.selenium.ie.InternetExplorerOptions;
public class IEDriverSample {
    public static void main(String[] args) {        
        InternetExplorerOptions ieOptions = new InternetExplorerOptions();
        ieOptions.attachToEdgeChrome();
        ieOptions.withEdgeExecutablePath(""C:\\Program Files (x86)\\Microsoft\\Edge\\Application\\msedge.exe"");
        
        WebDriver driver = new InternetExplorerDriver(ieOptions);
        driver.get(""http://www.bing.com"");
        WebElement elem = driver.findElement(By.id(""sb_form_q""));
        elem.sendKeys(""IE mode"", Keys.RETURN);
        driver.close();
    }
}
```


### Relevant log output

```shell
NA
```


### Operating System

Windows 10

### Selenium version

<dependency>             <groupId>org.seleniumhq.selenium</groupId>             <artifactId>selenium-java</artifactId>             <version>4.1.2</version>         </dependency>

### What are the browser(s) and version(s) where you see this issue?

IE Mode in Edge

### What are the browser driver(s) and version(s) where you see this issue?

IE Driver 4.0.0.0 

### Are you using Selenium Grid?

No",1.0,"[🐛 Bug]: SessionNotCreatedException for Edge in IE Mode - ### What happened?

I am facing issue while automating the application using Selenium 4 in IE mode in Microsoft Edge with Internet Explorer Driver. 
I have followed the steps given in the [Microsoft Blog](https://blogs.windows.com/msedgedev/2022/02/01/test-ie-mode-in-microsoft-edge-internet-explorer-driver/)  but still not able to get the results.
Language Used- JAVA
Browser- IE Compatibility Mode 

Code Snippet- 
 public static void main(String[] args) {        
        InternetExplorerOptions ieOptions = new InternetExplorerOptions();
        ieOptions.attachToEdgeChrome();
        ieOptions.withEdgeExecutablePath(""C:\\Program Files (x86)\\Microsoft\\Edge\\Application\\msedge.exe"");
        
        WebDriver driver = new InternetExplorerDriver(ieOptions);
        driver.get(""http://www.bing.com"");
        WebElement elem = driver.findElement(By.id(""sb_form_q""));
        elem.sendKeys(""IE mode"", Keys.RETURN);
        driver.close();
    }
Issue: I am able to launch the browser in ""Edge compatibility mode"" but not able to move further. The screen is stuck on the page with following error:

 ""This is the initial start page for the WebDriver server"".

![image](https://user-images.githubusercontent.com/63354414/156769485-5c7d2c43-4816-43e6-a0d9-e277f3165e7b.png)


### How can we reproduce the issue?

```shell
import org.openqa.selenium.By;
import org.openqa.selenium.Keys;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
import org.openqa.selenium.ie.InternetExplorerDriver;
import org.openqa.selenium.ie.InternetExplorerOptions;
public class IEDriverSample {
    public static void main(String[] args) {        
        InternetExplorerOptions ieOptions = new InternetExplorerOptions();
        ieOptions.attachToEdgeChrome();
        ieOptions.withEdgeExecutablePath(""C:\\Program Files (x86)\\Microsoft\\Edge\\Application\\msedge.exe"");
        
        WebDriver driver = new InternetExplorerDriver(ieOptions);
        driver.get(""http://www.bing.com"");
        WebElement elem = driver.findElement(By.id(""sb_form_q""));
        elem.sendKeys(""IE mode"", Keys.RETURN);
        driver.close();
    }
}
```


### Relevant log output

```shell
NA
```


### Operating System

Windows 10

### Selenium version

<dependency>             <groupId>org.seleniumhq.selenium</groupId>             <artifactId>selenium-java</artifactId>             <version>4.1.2</version>         </dependency>

### What are the browser(s) and version(s) where you see this issue?

IE Mode in Edge

### What are the browser driver(s) and version(s) where you see this issue?

IE Driver 4.0.0.0 

### Are you using Selenium Grid?

No",0,   sessionnotcreatedexception for edge in ie mode       what happened   i am facing issue while automating the application using selenium   in ie mode in microsoft edge with internet explorer driver    i have followed the steps given in the      but still not able to get the results   language used  java  browser  ie compatibility mode     code snippet     public static void main string  args                     internetexploreroptions ieoptions   new internetexploreroptions             ieoptions attachtoedgechrome             ieoptions withedgeexecutablepath  c   program files      microsoft  edge  application  msedge exe                       webdriver driver   new internetexplorerdriver ieoptions            driver get             webelement elem   driver findelement by id  sb form q              elem sendkeys  ie mode   keys return            driver close            issue  i am able to launch the browser in  edge compatibility mode  but not able to move further  the screen is stuck on the page with following error       this is the initial start page for the webdriver server                  how can we reproduce the issue      shell import org openqa selenium by   import org openqa selenium keys   import org openqa selenium webdriver   import org openqa selenium webelement   import org openqa selenium ie internetexplorerdriver   import org openqa selenium ie internetexploreroptions   public class iedriversample        public static void main string  args                     internetexploreroptions ieoptions   new internetexploreroptions             ieoptions attachtoedgechrome             ieoptions withedgeexecutablepath  c   program files      microsoft  edge  application  msedge exe                       webdriver driver   new internetexplorerdriver ieoptions            driver get             webelement elem   driver findelement by id  sb form q              elem sendkeys  ie mode   keys return            driver close                        relevant log output     shell na           operating system  windows        selenium version                 org seleniumhq selenium               selenium java                                     what are the browser s  and version s  where you see this issue   ie mode in edge      what are the browser driver s  and version s  where you see this issue   ie driver               are you using selenium grid   no,0
632550,20200480348.0,IssuesEvent,2022-02-11 14:48:45,oceanprotocol/ocean.js,https://api.github.com/repos/oceanprotocol/ocean.js,opened,Stop using toWei/fromWei from web3,Type: Bug Priority: Low,"We need to use amountToWei, weiToAmount to be compatible to tokens with various decimals",1.0,"Stop using toWei/fromWei from web3 - We need to use amountToWei, weiToAmount to be compatible to tokens with various decimals",0,stop using towei fromwei from     we need to use amounttowei  weitoamount to be compatible to tokens with various decimals,0
357659,10616551913.0,IssuesEvent,2019-10-12 12:38:56,ipfs/ipfs-cluster,https://api.github.com/repos/ipfs/ipfs-cluster,opened,Monitor: make accrual detection useful (or remove),difficulty:hard enhancement/feature help wanted priority:high ready,"**Describe the feature you are proposing**

Accrual failure detection exists in the `monitor` module. However, two metrics coming unusually close (like in a re-start), would skew the interval between metrics and then trigger alerts because the next one would come at a normal interval.

As a quick mitigation, safeguards were added to never alert if the last metric was still valid per it's TTL. But since metrics are valid 2x the interval in which they are produced, this means that accrual detection only kicks in on a full degradation (a metric is not only coming in a bit late, but very late).

In practice, metrics validity should not depend on their hardcoded TTL but rely on accrual detection which effectively handles some degradation. If a peer is re-started it could send metrics with a new epoch or in a way that accrual can detach from previous series.

In short, accrual is a complicated thing and we have it for no value right now, we should take full advantage of it or drop it as useless complexity if it turns out it can't really help: it should reduce the number of false positives when making alert decisions purely based on TTL (and not add more false positives).",1.0,"Monitor: make accrual detection useful (or remove) - **Describe the feature you are proposing**

Accrual failure detection exists in the `monitor` module. However, two metrics coming unusually close (like in a re-start), would skew the interval between metrics and then trigger alerts because the next one would come at a normal interval.

As a quick mitigation, safeguards were added to never alert if the last metric was still valid per it's TTL. But since metrics are valid 2x the interval in which they are produced, this means that accrual detection only kicks in on a full degradation (a metric is not only coming in a bit late, but very late).

In practice, metrics validity should not depend on their hardcoded TTL but rely on accrual detection which effectively handles some degradation. If a peer is re-started it could send metrics with a new epoch or in a way that accrual can detach from previous series.

In short, accrual is a complicated thing and we have it for no value right now, we should take full advantage of it or drop it as useless complexity if it turns out it can't really help: it should reduce the number of false positives when making alert decisions purely based on TTL (and not add more false positives).",0,monitor  make accrual detection useful  or remove      describe the feature you are proposing      accrual failure detection exists in the  monitor  module  however  two metrics coming unusually close  like in a re start   would skew the interval between metrics and then trigger alerts because the next one would come at a normal interval     as a quick mitigation  safeguards were added to never alert if the last metric was still valid per it s ttl  but since metrics are valid   the interval in which they are produced  this means that accrual detection only kicks in on a full degradation  a metric is not only coming in a bit late  but very late      in practice  metrics validity should not depend on their hardcoded ttl but rely on accrual detection which effectively handles some degradation  if a peer is re started it could send metrics with a new epoch or in a way that accrual can detach from previous series     in short  accrual is a complicated thing and we have it for no value right now  we should take full advantage of it or drop it as useless complexity if it turns out it can t really help  it should reduce the number of false positives when making alert decisions purely based on ttl  and not add more false positives  ,0
36444,6534882099.0,IssuesEvent,2017-08-31 12:43:09,golang/go,https://api.github.com/repos/golang/go,opened,strconv: incorrect rounding to nearest even,Documentation NeedsDecision,"The following statements
```
fmt.Printf(""x = %.1f\n"", 0.35)
fmt.Printf(""x = %.1f\n"", 0.45)
fmt.Printf(""x = %.1f\n"", 0.55)
fmt.Printf(""x = %.1f\n"", 0.65)
```
produce
```
x = 0.3
x = 0.5
x = 0.6
x = 0.7
```
(https://play.golang.org/p/kLC7Ap0cpP).

However, assuming rounding to nearest even, one would expect the result to be
```
x = 0.4
x = 0.4
x = 0.6
x = 0.6
```
(The examples use fmt.Printf but the culprit is in the underlying strconv code. The documentation doesn't explicitly state that it rounds to nearest even, but that is definitively the intent of the implementation which contains code and comments to that effect.).

The problem of course is that these numbers cannot be accurately represented in binary form and when it comes to the rounding decision, what should be `.5` is sometimes below or above that value.

That said, the correct result could in fact be obtained if rounding were done on the shortest decimal representation that produces the incoming number, that is if rounding where done on the output of using the ""%g"" format (or `strconv.FormatFloat` with precision -1). Unfortunately, computing that representation is much more expensive that what happens now.

We can probably not fix this. For one, it's been like this forever. Also, a corresponding C program
```
#include <stdio.h>

int main() {
	printf(""x = %.1f\n"", 0.35);
	printf(""x = %.1f\n"", 0.45);
	printf(""x = %.1f\n"", 0.55);
	printf(""x = %.1f\n"", 0.65);
	return 0;
}
```
produces the same (incorrect) result. And so does `math/big.Float` formatting with the same arguments (since the code mirrors the strconv code).

But we should probably document it and perhaps even provide a ""correct"" routine for cases where this truly matters.
",1.0,"strconv: incorrect rounding to nearest even - The following statements
```
fmt.Printf(""x = %.1f\n"", 0.35)
fmt.Printf(""x = %.1f\n"", 0.45)
fmt.Printf(""x = %.1f\n"", 0.55)
fmt.Printf(""x = %.1f\n"", 0.65)
```
produce
```
x = 0.3
x = 0.5
x = 0.6
x = 0.7
```
(https://play.golang.org/p/kLC7Ap0cpP).

However, assuming rounding to nearest even, one would expect the result to be
```
x = 0.4
x = 0.4
x = 0.6
x = 0.6
```
(The examples use fmt.Printf but the culprit is in the underlying strconv code. The documentation doesn't explicitly state that it rounds to nearest even, but that is definitively the intent of the implementation which contains code and comments to that effect.).

The problem of course is that these numbers cannot be accurately represented in binary form and when it comes to the rounding decision, what should be `.5` is sometimes below or above that value.

That said, the correct result could in fact be obtained if rounding were done on the shortest decimal representation that produces the incoming number, that is if rounding where done on the output of using the ""%g"" format (or `strconv.FormatFloat` with precision -1). Unfortunately, computing that representation is much more expensive that what happens now.

We can probably not fix this. For one, it's been like this forever. Also, a corresponding C program
```
#include <stdio.h>

int main() {
	printf(""x = %.1f\n"", 0.35);
	printf(""x = %.1f\n"", 0.45);
	printf(""x = %.1f\n"", 0.55);
	printf(""x = %.1f\n"", 0.65);
	return 0;
}
```
produces the same (incorrect) result. And so does `math/big.Float` formatting with the same arguments (since the code mirrors the strconv code).

But we should probably document it and perhaps even provide a ""correct"" routine for cases where this truly matters.
",1,strconv  incorrect rounding to nearest even   the following statements       fmt printf  x       n         fmt printf  x       n         fmt printf  x       n         fmt printf  x       n              produce       x        x        x        x                   however  assuming rounding to nearest even  one would expect the result to be       x        x        x        x              the examples use fmt printf but the culprit is in the underlying strconv code  the documentation doesn t explicitly state that it rounds to nearest even  but that is definitively the intent of the implementation which contains code and comments to that effect       the problem of course is that these numbers cannot be accurately represented in binary form and when it comes to the rounding decision  what should be      is sometimes below or above that value     that said  the correct result could in fact be obtained if rounding were done on the shortest decimal representation that produces the incoming number  that is if rounding where done on the output of using the   g  format  or  strconv formatfloat  with precision      unfortunately  computing that representation is much more expensive that what happens now     we can probably not fix this  for one  it s been like this forever  also  a corresponding c program        include      int main      	printf  x       n          	printf  x       n          	printf  x       n          	printf  x       n          	return             produces the same  incorrect  result  and so does  math big float  formatting with the same arguments  since the code mirrors the strconv code      but we should probably document it and perhaps even provide a  correct  routine for cases where this truly matters   ,1
33831,6263943490.0,IssuesEvent,2017-07-16 01:44:13,golang/go,https://api.github.com/repos/golang/go,closed,go/ast: CommentMap example does not compile,Documentation,"Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
go version go1.8 darwin/amd64


### What operating system and processor architecture are you using (`go env`)?
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/ritesh/code/go""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.8/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.8/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/5x/m5n_f_wj6fngljvf9g7y3mp4qphpn9/T/go-build111820297=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
PKG_CONFIG=""pkg-config""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""

### What did you do?

Tried to run the example in https://golang.org/pkg/go/ast/#example_CommentMap. A link to the full program, with imports, is here:
https://play.golang.org/p/5DA91qtnm4

### What did you expect to see?
Expected the example to run, without any errors.

### What did you see instead?
tmp/sandbox659516205/main.go:44: undefined: removeFirstVarDecl
",1.0,"go/ast: CommentMap example does not compile - Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
go version go1.8 darwin/amd64


### What operating system and processor architecture are you using (`go env`)?
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/ritesh/code/go""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.8/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.8/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/5x/m5n_f_wj6fngljvf9g7y3mp4qphpn9/T/go-build111820297=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
PKG_CONFIG=""pkg-config""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""

### What did you do?

Tried to run the example in https://golang.org/pkg/go/ast/#example_CommentMap. A link to the full program, with imports, is here:
https://play.golang.org/p/5DA91qtnm4

### What did you expect to see?
Expected the example to run, without any errors.

### What did you see instead?
tmp/sandbox659516205/main.go:44: undefined: removeFirstVarDecl
",1,go ast  commentmap example does not compile   please answer these questions before submitting your issue  thanks         what version of go are you using   go version     go version     darwin            what operating system and processor architecture are you using   go env     goarch      gobin     goexe     gohostarch      gohostos  darwin   goos  darwin   gopath   users ritesh code go   gorace     goroot   usr local cellar go     libexec   gotooldir   usr local cellar go     libexec pkg tool darwin     gccgo  gccgo   cc  clang   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders     f   t go    tmp go build  gno record gcc switches  fno common   cxx  clang     cgo enabled      pkg config  pkg config   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g            what did you do     tried to run the example in   a link to the full program  with imports  is here            what did you expect to see   expected the example to run  without any errors         what did you see instead   tmp   main go    undefined  removefirstvardecl  ,1
522724,15166756094.0,IssuesEvent,2021-02-12 16:48:26,threefoldfoundation/www_threefold_marketplace,https://api.github.com/repos/threefoldfoundation/www_threefold_marketplace,closed,MARKETPLACE - website setup,priority_major,"- [x] setup repo based on examplesite
- [x] update structure per provided mockup
- [x] add content as per mockup",1.0,"MARKETPLACE - website setup - - [x] setup repo based on examplesite
- [x] update structure per provided mockup
- [x] add content as per mockup",0,marketplace   website setup       setup repo based on examplesite      update structure per provided mockup      add content as per mockup,0
33834,6264055948.0,IssuesEvent,2017-07-16 03:10:42,golang/go,https://api.github.com/repos/golang/go,opened,all: add a few READMEs to help new people navigate the source tree,Documentation,"The api directory has a friendly README file in it explaining what's in it. We should add short READMEs to some of the other top-level directories, particularly doc, lib, misc, and test.
",1.0,"all: add a few READMEs to help new people navigate the source tree - The api directory has a friendly README file in it explaining what's in it. We should add short READMEs to some of the other top-level directories, particularly doc, lib, misc, and test.
",1,all  add a few readmes to help new people navigate the source tree   the api directory has a friendly readme file in it explaining what s in it  we should add short readmes to some of the other top level directories  particularly doc  lib  misc  and test   ,1
259909,8201540312.0,IssuesEvent,2018-09-01 18:57:19,fossasia/open-event-webapp,https://api.github.com/repos/fossasia/open-event-webapp,opened,Some speakers are not added into generated file of Jugaadfest,Priority: Urgent bug,"Some speakers are missing in the generated file of Jugaadfest, e.g. at the time this issue was filed the eventyay website shows 21 speakers. Jugaadfest.com only shows 19 speakers.

![screenshot from 2018-09-01 20-56-20](https://user-images.githubusercontent.com/1583873/44949030-83a01a00-ae29-11e8-9fe1-f1e3bb4d781d.png)
",1.0,"Some speakers are not added into generated file of Jugaadfest - Some speakers are missing in the generated file of Jugaadfest, e.g. at the time this issue was filed the eventyay website shows 21 speakers. Jugaadfest.com only shows 19 speakers.

![screenshot from 2018-09-01 20-56-20](https://user-images.githubusercontent.com/1583873/44949030-83a01a00-ae29-11e8-9fe1-f1e3bb4d781d.png)
",0,some speakers are not added into generated file of jugaadfest   some speakers are missing in the generated file of jugaadfest  e g  at the time this issue was filed the eventyay website shows   speakers  jugaadfest com only shows   speakers           ,0
61717,8552941804.0,IssuesEvent,2018-11-07 22:42:07,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: perhaps misleading 'require new/thing v2.3.4' example in documentation,Documentation NeedsFix modules,"Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?

Tip (devel +0e40889796 Wed Oct 24 21:23:54 2018 +0000).

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

N/A.

### What did you do?

Go to: https://tip.golang.org/cmd/go/#hdr-The_go_mod_file

### What did you see?

The documentation section on ""The go.mod file"" includes what I think might be a misleading example `require` directive:

```
require new/thing v2.3.4
```

I suspect that would not be representative of how the 1.11 tooling would write that after resolving any module queries.  In other words, I would expect that example `require` to either include the `/v2`:

```
require new/thing/v2 v2.3.4
```

or include `+incompatible`:

```
require new/thing v2.3.4+incompatible 
```

or perhaps something else.

I've seen people get confused on whether or not the `/vN` is required in a `require` directive for a v2+ dependency that has opted in to modules, so might be worth updating that example. 

For context, here is a slightly larger snippet from the doc:

> Each line holds a single directive, made up of a verb followed by arguments. For example:
> 
> ```
> module my/thing
> require other/thing v1.0.2
> require new/thing v2.3.4
> exclude old/thing v1.2.3
> replace bad/thing v1.4.5 => good/thing v1.4.5
> ```
",1.0,"cmd/go: perhaps misleading 'require new/thing v2.3.4' example in documentation - Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?

Tip (devel +0e40889796 Wed Oct 24 21:23:54 2018 +0000).

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

N/A.

### What did you do?

Go to: https://tip.golang.org/cmd/go/#hdr-The_go_mod_file

### What did you see?

The documentation section on ""The go.mod file"" includes what I think might be a misleading example `require` directive:

```
require new/thing v2.3.4
```

I suspect that would not be representative of how the 1.11 tooling would write that after resolving any module queries.  In other words, I would expect that example `require` to either include the `/v2`:

```
require new/thing/v2 v2.3.4
```

or include `+incompatible`:

```
require new/thing v2.3.4+incompatible 
```

or perhaps something else.

I've seen people get confused on whether or not the `/vN` is required in a `require` directive for a v2+ dependency that has opted in to modules, so might be worth updating that example. 

For context, here is a slightly larger snippet from the doc:

> Each line holds a single directive, made up of a verb followed by arguments. For example:
> 
> ```
> module my/thing
> require other/thing v1.0.2
> require new/thing v2.3.4
> exclude old/thing v1.2.3
> replace bad/thing v1.4.5 => good/thing v1.4.5
> ```
",1,cmd go  perhaps misleading  require new thing        example in documentation   please answer these questions before submitting your issue  thanks           what version of go are you using   go version       tip  devel    wed oct                       does this issue reproduce with the latest release     yes         what operating system and processor architecture are you using   go env       n a         what did you do     go to           what did you see     the documentation section on  the go mod file  includes what i think might be a misleading example  require  directive          require new thing               i suspect that would not be representative of how the     tooling would write that after resolving any module queries   in other words  i would expect that example  require  to either include the               require new thing                 or include   incompatible           require new thing       incompatible          or perhaps something else     i ve seen people get confused on whether or not the   vn  is required in a  require  directive for a    dependency that has opted in to modules  so might be worth updating that example      for context  here is a slightly larger snippet from the doc       each line holds a single directive  made up of a verb followed by arguments  for example                module my thing    require other thing          require new thing          exclude old thing          replace bad thing          good thing               ,1
43713,7059292736.0,IssuesEvent,2018-01-05 00:37:01,golang/go,https://api.github.com/repos/golang/go,closed,net/http: fix docs on Transport connection reuse specifics,Documentation,"### What version of Go are you using (`go version`)?
go version go1.7 darwin/amd64

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?


### What did you do?

```
package main

import (
	""time""
    ""fmt""
    ""io/ioutil""
    ""net/http""
)

func main() {
    resp, err := http.Get(""http://127.0.0.1:8588"")
    
    if err != nil {
        panic(err)
    }
    _, err = ioutil.ReadAll(resp.Body)
    if err != nil {
        panic(err)
    }

    resp2, err := http.Get(""http://127.0.0.1:8588"")
    
    if err != nil {
        panic(err)
    }
    _, err = ioutil.ReadAll(resp2.Body)
    if err != nil {
        panic(err)
    }

    fmt.Println(""before time sleep"")
    time.Sleep(time.Second * 35)
}
```

in GO net/http Response Body annotation says:

> It is the caller's responsibility to close Body. The default HTTP client's Transport does not attempt to reuse HTTP/1.0 or HTTP/1.1 TCP connections (""keep-alive"") unless the Body is read to completion and is closed.

yeah, it say we must read body complete AND close body.
in the above code, after read resp.Body I don't close the resp.Body. so, the http client should't reuse the tcp connection. so there will be two tcp connection handshark in wireshark, but I only see ONE.
so, maybe the net/http's comment has something wrong?
thank you.

",1.0,"net/http: fix docs on Transport connection reuse specifics - ### What version of Go are you using (`go version`)?
go version go1.7 darwin/amd64

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?


### What did you do?

```
package main

import (
	""time""
    ""fmt""
    ""io/ioutil""
    ""net/http""
)

func main() {
    resp, err := http.Get(""http://127.0.0.1:8588"")
    
    if err != nil {
        panic(err)
    }
    _, err = ioutil.ReadAll(resp.Body)
    if err != nil {
        panic(err)
    }

    resp2, err := http.Get(""http://127.0.0.1:8588"")
    
    if err != nil {
        panic(err)
    }
    _, err = ioutil.ReadAll(resp2.Body)
    if err != nil {
        panic(err)
    }

    fmt.Println(""before time sleep"")
    time.Sleep(time.Second * 35)
}
```

in GO net/http Response Body annotation says:

> It is the caller's responsibility to close Body. The default HTTP client's Transport does not attempt to reuse HTTP/1.0 or HTTP/1.1 TCP connections (""keep-alive"") unless the Body is read to completion and is closed.

yeah, it say we must read body complete AND close body.
in the above code, after read resp.Body I don't close the resp.Body. so, the http client should't reuse the tcp connection. so there will be two tcp connection handshark in wireshark, but I only see ONE.
so, maybe the net/http's comment has something wrong?
thank you.

",1,net http  fix docs on transport connection reuse specifics       what version of go are you using   go version     go version     darwin          does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env             what did you do          package main    import    	 time        fmt        io ioutil        net http        func main          resp  err    http get               if err    nil            panic err                 err   ioutil readall resp body       if err    nil            panic err                   err    http get               if err    nil            panic err                 err   ioutil readall   body       if err    nil            panic err                fmt println  before time sleep        time sleep time second                 in go net http response body annotation says       it is the caller s responsibility to close body  the default http client s transport does not attempt to reuse http     or http     tcp connections   keep alive   unless the body is read to completion and is closed     yeah  it say we must read body complete and close body   in the above code  after read resp body i don t close the resp body  so  the http client should t reuse the tcp connection  so there will be two tcp connection handshark in wireshark  but i only see one   so  maybe the net http s comment has something wrong   thank you     ,1
43933,7086733444.0,IssuesEvent,2018-01-11 15:42:19,golang/go,https://api.github.com/repos/golang/go,closed,Typing error in Go spec documentation,Documentation,"First of all, I'm sorry if it's not a typing error, still learning Go.

### What version of Go are you using (`go version`)?
1.9

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
ubuntu amd64

### What did you do?
Reading Go specification. Section: Properties of types and values - Type Identities.
Noticed a typing error (maybe?):

> These types are identical:
> `B0, B0, and C0`

### What did you expect to see?
> These types are identical:
> `A0, B0, and C0`

### What did you see instead?
> These types are identical:
> `B0, B0, and C0`

",1.0,"Typing error in Go spec documentation - First of all, I'm sorry if it's not a typing error, still learning Go.

### What version of Go are you using (`go version`)?
1.9

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
ubuntu amd64

### What did you do?
Reading Go specification. Section: Properties of types and values - Type Identities.
Noticed a typing error (maybe?):

> These types are identical:
> `B0, B0, and C0`

### What did you expect to see?
> These types are identical:
> `A0, B0, and C0`

### What did you see instead?
> These types are identical:
> `B0, B0, and C0`

",1,typing error in go spec documentation   first of all  i m sorry if it s not a typing error  still learning go         what version of go are you using   go version                does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env     ubuntu          what did you do   reading go specification  section  properties of types and values   type identities   noticed a typing error  maybe         these types are identical            and           what did you expect to see     these types are identical            and           what did you see instead     these types are identical            and       ,1
114300,17199586764.0,IssuesEvent,2021-07-17 01:04:02,billmcchesney1/linkerd2,https://api.github.com/repos/billmcchesney1/linkerd2,opened,"CVE-2020-28469 (High) detected in glob-parent-3.1.0.tgz, glob-parent-5.1.1.tgz",security vulnerability,"## CVE-2020-28469 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>glob-parent-3.1.0.tgz</b>, <b>glob-parent-5.1.1.tgz</b></p></summary>
<p>

<details><summary><b>glob-parent-3.1.0.tgz</b></p></summary>

<p>Strips glob magic from a string to provide the parent directory path</p>
<p>Library home page: <a href=""https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz"">https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz</a></p>
<p>Path to dependency file: linkerd2/web/app/package.json</p>
<p>Path to vulnerable library: linkerd2/web/app/node_modules/watchpack-chokidar2/node_modules/glob-parent/package.json,linkerd2/web/app/node_modules/webpack-dev-server/node_modules/glob-parent/package.json</p>
<p>

Dependency Hierarchy:
  - webpack-dev-server-3.11.0.tgz (Root Library)
    - chokidar-2.1.8.tgz
      - :x: **glob-parent-3.1.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>glob-parent-5.1.1.tgz</b></p></summary>

<p>Extract the non-magic parent path from a glob string.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.1.tgz"">https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.1.tgz</a></p>
<p>Path to dependency file: linkerd2/web/app/package.json</p>
<p>Path to vulnerable library: linkerd2/web/app/node_modules/glob-parent/package.json</p>
<p>

Dependency Hierarchy:
  - eslint-6.8.0.tgz (Root Library)
    - :x: **glob-parent-5.1.1.tgz** (Vulnerable Library)
</details>

<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>  
  
This affects the package glob-parent before 5.1.2. The enclosure regex used to check for strings ending in enclosure containing path separator.

<p>Publish Date: 2021-06-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28469>CVE-2020-28469</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28469"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28469</a></p>
<p>Release Date: 2021-06-03</p>
<p>Fix Resolution: glob-parent - 5.1.2</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":false,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""glob-parent"",""packageVersion"":""3.1.0"",""packageFilePaths"":[""/web/app/package.json""],""isTransitiveDependency"":true,""dependencyTree"":""webpack-dev-server:3.11.0;chokidar:2.1.8;glob-parent:3.1.0"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""glob-parent - 5.1.2""},{""packageType"":""javascript/Node.js"",""packageName"":""glob-parent"",""packageVersion"":""5.1.1"",""packageFilePaths"":[""/web/app/package.json""],""isTransitiveDependency"":true,""dependencyTree"":""eslint:6.8.0;glob-parent:5.1.1"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""glob-parent - 5.1.2""}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2020-28469"",""vulnerabilityDetails"":""This affects the package glob-parent before 5.1.2. The enclosure regex used to check for strings ending in enclosure containing path separator."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28469"",""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-2020-28469 (High) detected in glob-parent-3.1.0.tgz, glob-parent-5.1.1.tgz - ## CVE-2020-28469 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>glob-parent-3.1.0.tgz</b>, <b>glob-parent-5.1.1.tgz</b></p></summary>
<p>

<details><summary><b>glob-parent-3.1.0.tgz</b></p></summary>

<p>Strips glob magic from a string to provide the parent directory path</p>
<p>Library home page: <a href=""https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz"">https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz</a></p>
<p>Path to dependency file: linkerd2/web/app/package.json</p>
<p>Path to vulnerable library: linkerd2/web/app/node_modules/watchpack-chokidar2/node_modules/glob-parent/package.json,linkerd2/web/app/node_modules/webpack-dev-server/node_modules/glob-parent/package.json</p>
<p>

Dependency Hierarchy:
  - webpack-dev-server-3.11.0.tgz (Root Library)
    - chokidar-2.1.8.tgz
      - :x: **glob-parent-3.1.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>glob-parent-5.1.1.tgz</b></p></summary>

<p>Extract the non-magic parent path from a glob string.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.1.tgz"">https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.1.tgz</a></p>
<p>Path to dependency file: linkerd2/web/app/package.json</p>
<p>Path to vulnerable library: linkerd2/web/app/node_modules/glob-parent/package.json</p>
<p>

Dependency Hierarchy:
  - eslint-6.8.0.tgz (Root Library)
    - :x: **glob-parent-5.1.1.tgz** (Vulnerable Library)
</details>

<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>  
  
This affects the package glob-parent before 5.1.2. The enclosure regex used to check for strings ending in enclosure containing path separator.

<p>Publish Date: 2021-06-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28469>CVE-2020-28469</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28469"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28469</a></p>
<p>Release Date: 2021-06-03</p>
<p>Fix Resolution: glob-parent - 5.1.2</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":false,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""glob-parent"",""packageVersion"":""3.1.0"",""packageFilePaths"":[""/web/app/package.json""],""isTransitiveDependency"":true,""dependencyTree"":""webpack-dev-server:3.11.0;chokidar:2.1.8;glob-parent:3.1.0"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""glob-parent - 5.1.2""},{""packageType"":""javascript/Node.js"",""packageName"":""glob-parent"",""packageVersion"":""5.1.1"",""packageFilePaths"":[""/web/app/package.json""],""isTransitiveDependency"":true,""dependencyTree"":""eslint:6.8.0;glob-parent:5.1.1"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""glob-parent - 5.1.2""}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2020-28469"",""vulnerabilityDetails"":""This affects the package glob-parent before 5.1.2. The enclosure regex used to check for strings ending in enclosure containing path separator."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28469"",""cvss3Severity"":""high"",""cvss3Score"":""7.5"",""cvss3Metrics"":{""A"":""High"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""None"",""AV"":""Network"",""I"":""None""},""extraData"":{}}</REMEDIATE> -->",0,cve      high  detected in glob parent       tgz  glob parent       tgz      cve       high severity vulnerability     vulnerable libraries    glob parent       tgz    glob parent       tgz          glob parent       tgz      strips glob magic from a string to provide the parent directory path   library home page   a href     path to dependency file    web app package json   path to vulnerable library    web app node modules watchpack   node modules glob parent package json   web app node modules webpack dev server node modules glob parent package json     dependency hierarchy      webpack dev server       tgz  root library        chokidar       tgz          x    glob parent       tgz    vulnerable library       glob parent       tgz      extract the non magic parent path from a glob string    library home page   a href     path to dependency file    web app package json   path to vulnerable library    web app node modules glob parent package json     dependency hierarchy      eslint       tgz  root library         x    glob parent       tgz    vulnerable library      found in base branch   main              vulnerability details         this affects the package glob parent before        the enclosure regex used to check for strings ending in enclosure containing path separator    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  glob parent                      isopenpronvulnerability  false  ispackagebased  true  isdefaultbranch  true  packages     istransitivedependency  true  dependencytree   webpack dev server       chokidar       glob parent         isminimumfixversionavailable  true  minimumfixversion   glob parent             packagetype   javascript node js   packagename   glob parent   packageversion           packagefilepaths     istransitivedependency  true  dependencytree   eslint       glob parent         isminimumfixversionavailable  true  minimumfixversion   glob parent             basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   this affects the package glob parent before        the enclosure regex used to check for strings ending in enclosure containing path separator    vulnerabilityurl        ,0
26948,20948621040.0,IssuesEvent,2022-03-26 08:33:14,pixiebrix/pixiebrix-extension,https://api.github.com/repos/pixiebrix/pixiebrix-extension,closed,Include original error stack trace for Rollbar when throwing error in block pipeline,infrastructure,"Throw block errors reported to Rollbar needs to include original stack trace. Otherwise for application errors we can't pinpoint what line caused the error

![image](https://user-images.githubusercontent.com/1879821/159163772-c04ab624-5e6a-4424-a9c8-7eeac669eb2d.png)

Relevant code:
- http://github.com/pixiebrix/pixiebrix-extension/blob/4cf13fc048c6f3b5eac9248227b324b8b78c3cc3/src/runtime/reducePipeline.ts#L570-L570

Related:
- https://github.com/pixiebrix/pixiebrix-extension/issues/2966",1.0,"Include original error stack trace for Rollbar when throwing error in block pipeline - Throw block errors reported to Rollbar needs to include original stack trace. Otherwise for application errors we can't pinpoint what line caused the error

![image](https://user-images.githubusercontent.com/1879821/159163772-c04ab624-5e6a-4424-a9c8-7eeac669eb2d.png)

Relevant code:
- http://github.com/pixiebrix/pixiebrix-extension/blob/4cf13fc048c6f3b5eac9248227b324b8b78c3cc3/src/runtime/reducePipeline.ts#L570-L570

Related:
- https://github.com/pixiebrix/pixiebrix-extension/issues/2966",0,include original error stack trace for rollbar when throwing error in block pipeline   throw block errors reported to rollbar needs to include original stack trace  otherwise for application errors we can t pinpoint what line caused the error            relevant code          related      ,0
123286,12196303654.0,IssuesEvent,2020-04-29 18:51:02,golang/go,https://api.github.com/repos/golang/go,closed,crypto/x509/pkix: FillFromRDNSequence does not preserve multi-value RDNs,Documentation NeedsFix Unfortunate help wanted,"### What version of Go are you using (`go version`)?
This issue affects Go 1.8 and later as a consequence of https://github.com/golang/go/commit/809a1de1ac1ccc76f7a4faf630017626f2f68231 to fix  [#16836](https://github.com/golang/go/issues/16836) (and #12342).

Prior to Go 1.8 and that change, Go did not process multi-value RDNs -- it always assumed just one attribute and value (the first) per RDN.

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
The OS and architecture should not matter.

### What did you do?
https://play.golang.org/p/7OIuhautCe

### What did you expect to see?
The multi-value nature of any RDN is preserved.  That is, the length of the subject (and issuer) RDNSequence before pkix.FillFromRDNSequence and after pkix.ToRDNSequence should match.

### What did you see instead?
The multi-value nature of any RDN is not preserved by pkix.FillFromRDNSequence.  That is, the length of the subject (and issuer) RDNSequence before pkix.FillFromRDNSequence and after pkix.ToRDNSequence do not match.

As previously noted in comments on https://github.com/golang/go/commit/809a1de1ac1ccc76f7a4faf630017626f2f68231, the [original Gerrit CR](https://go-review.googlesource.com/c/go/+/30810#message-a29d12cfb3550dc2ce212ec60ddf32bf86363f13), and #12342, if this will not be fixed, then the behavior should be documented at a minimum.",1.0,"crypto/x509/pkix: FillFromRDNSequence does not preserve multi-value RDNs - ### What version of Go are you using (`go version`)?
This issue affects Go 1.8 and later as a consequence of https://github.com/golang/go/commit/809a1de1ac1ccc76f7a4faf630017626f2f68231 to fix  [#16836](https://github.com/golang/go/issues/16836) (and #12342).

Prior to Go 1.8 and that change, Go did not process multi-value RDNs -- it always assumed just one attribute and value (the first) per RDN.

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
The OS and architecture should not matter.

### What did you do?
https://play.golang.org/p/7OIuhautCe

### What did you expect to see?
The multi-value nature of any RDN is preserved.  That is, the length of the subject (and issuer) RDNSequence before pkix.FillFromRDNSequence and after pkix.ToRDNSequence should match.

### What did you see instead?
The multi-value nature of any RDN is not preserved by pkix.FillFromRDNSequence.  That is, the length of the subject (and issuer) RDNSequence before pkix.FillFromRDNSequence and after pkix.ToRDNSequence do not match.

As previously noted in comments on https://github.com/golang/go/commit/809a1de1ac1ccc76f7a4faf630017626f2f68231, the [original Gerrit CR](https://go-review.googlesource.com/c/go/+/30810#message-a29d12cfb3550dc2ce212ec60ddf32bf86363f13), and #12342, if this will not be fixed, then the behavior should be documented at a minimum.",1,crypto   pkix  fillfromrdnsequence does not preserve multi value rdns       what version of go are you using   go version     this issue affects go     and later as a consequence of   to fix       and         prior to go     and that change  go did not process multi value rdns    it always assumed just one attribute and value  the first  per rdn         does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env     the os and architecture should not matter         what did you do            what did you expect to see   the multi value nature of any rdn is preserved   that is  the length of the subject  and issuer  rdnsequence before pkix fillfromrdnsequence and after pkix tordnsequence should match         what did you see instead   the multi value nature of any rdn is not preserved by pkix fillfromrdnsequence   that is  the length of the subject  and issuer  rdnsequence before pkix fillfromrdnsequence and after pkix tordnsequence do not match     as previously noted in comments on   the     and     if this will not be fixed  then the behavior should be documented at a minimum ,1
135362,19563826835.0,IssuesEvent,2022-01-03 20:18:40,bounswe/2021SpringGroup7,https://api.github.com/repos/bounswe/2021SpringGroup7,closed,CF-47 Admin Page,Type: Enhancement Status: In Progress Priority: High Type: Design Frontend,"Here is the functionality that admins are able to use:
* View reported users
* View reported posts
* Ban reported users
* Delete reported posts",1.0,"CF-47 Admin Page - Here is the functionality that admins are able to use:
* View reported users
* View reported posts
* Ban reported users
* Delete reported posts",0,cf   admin page   here is the functionality that admins are able to use     view reported users    view reported posts    ban reported users    delete reported posts,0
237997,19689798616.0,IssuesEvent,2022-01-12 04:53:57,zephyrproject-rtos/zephyr,https://api.github.com/repos/zephyrproject-rtos/zephyr,closed,"
tests-ci : portability: posix: fs.tls.newlib test Build failure
",bug priority: low platform: NXP area: Tests,"**Describe the bug**
fs.tls.newlib test is Build failure on v2.7.99-2147-g183328a4fbdb on mimxrt685_evk_cm33

see logs for details

**To Reproduce**
1. 
```
scripts/twister --device-testing --device-serial /dev/ttyACM0 -p mimxrt685_evk_cm33  --sub-test portability.posix
```
2. See error

**Expected behavior**
test pass

**Impact**


**Logs and console output**
```
/home/ubuntu/zephyr_project/zephyr_rt685/zephyr/drivers/disk/usdhc.c: In function 'usdhc_dat3_pull':
/home/ubuntu/zephyr_project/zephyr_rt685/zephyr/drivers/disk/usdhc.c:2618:2: error: implicit declaration of function 'imxrt_usdhc_dat3_pull'; did you mean 'usdhc_dat3_pull'? [-Werror=implicit-function-declaration]
 2618 |  imxrt_usdhc_dat3_pull(pullup);
      |  ^~~~~~~~~~~~~~~~~~~~~
      |  usdhc_dat3_pull
cc1: all warnings being treated as errors
    
```

**Environment (please complete the following information):**
 - OS: (e.g. Linux )
 - Toolchain (e.g Zephyr SDK)
 - Commit SHA or Version used: v2.7.99-2147-g183328a4fbdb
 ",1.0,"
tests-ci : portability: posix: fs.tls.newlib test Build failure
 - **Describe the bug**
fs.tls.newlib test is Build failure on v2.7.99-2147-g183328a4fbdb on mimxrt685_evk_cm33

see logs for details

**To Reproduce**
1. 
```
scripts/twister --device-testing --device-serial /dev/ttyACM0 -p mimxrt685_evk_cm33  --sub-test portability.posix
```
2. See error

**Expected behavior**
test pass

**Impact**


**Logs and console output**
```
/home/ubuntu/zephyr_project/zephyr_rt685/zephyr/drivers/disk/usdhc.c: In function 'usdhc_dat3_pull':
/home/ubuntu/zephyr_project/zephyr_rt685/zephyr/drivers/disk/usdhc.c:2618:2: error: implicit declaration of function 'imxrt_usdhc_dat3_pull'; did you mean 'usdhc_dat3_pull'? [-Werror=implicit-function-declaration]
 2618 |  imxrt_usdhc_dat3_pull(pullup);
      |  ^~~~~~~~~~~~~~~~~~~~~
      |  usdhc_dat3_pull
cc1: all warnings being treated as errors
    
```

**Environment (please complete the following information):**
 - OS: (e.g. Linux )
 - Toolchain (e.g Zephyr SDK)
 - Commit SHA or Version used: v2.7.99-2147-g183328a4fbdb
 ",0, tests ci   portability  posix  fs tls newlib test build failure      describe the bug    fs tls newlib test is build failure on           on   evk      see logs for details      to reproduce              scripts twister   device testing   device serial  dev    p   evk      sub test portability posix          see error      expected behavior    test pass      impact          logs and console output          home ubuntu zephyr project zephyr   zephyr drivers disk usdhc c  in function  usdhc   pull     home ubuntu zephyr project zephyr   zephyr drivers disk usdhc c      error  implicit declaration of function  imxrt usdhc   pull   did you mean  usdhc   pull            imxrt usdhc   pull pullup                                             usdhc   pull     all warnings being treated as errors                 environment  please complete the following information         os   e g  linux       toolchain  e g zephyr sdk      commit sha or version used              ,0
446869,12879252126.0,IssuesEvent,2020-07-11 21:02:46,clinwiki-org/clinwiki,https://api.github.com/repos/clinwiki-org/clinwiki,closed,"siteviews are case sensitive and mis-typed ones give no indication that there is a problem, they just show the default.",Priority 4,Lets make not case sensitive for starters. ,1.0,"siteviews are case sensitive and mis-typed ones give no indication that there is a problem, they just show the default. - Lets make not case sensitive for starters. ",0,siteviews are case sensitive and mis typed ones give no indication that there is a problem  they just show the default    lets make not case sensitive for starters  ,0
75677,9881664688.0,IssuesEvent,2019-06-24 15:08:03,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/cmd/gorename: extra whitespace in help text,Documentation,"Noticed an extra whitespace as I was reading its help text.

```
gorename rejects renamings of concrete methods that would change the
assignability relation between types and interfaces.  If the interface
change was intentional, initiate the renaming at the interface method.
```

It is between `interfaces.` and `If`.

@gopherbot documentation",1.0,"x/tools/cmd/gorename: extra whitespace in help text - Noticed an extra whitespace as I was reading its help text.

```
gorename rejects renamings of concrete methods that would change the
assignability relation between types and interfaces.  If the interface
change was intentional, initiate the renaming at the interface method.
```

It is between `interfaces.` and `If`.

@gopherbot documentation",1,x tools cmd gorename  extra whitespace in help text   noticed an extra whitespace as i was reading its help text          gorename rejects renamings of concrete methods that would change the  assignability relation between types and interfaces   if the interface  change was intentional  initiate the renaming at the interface method          it is between  interfaces   and  if       gopherbot documentation,1
90181,3812598752.0,IssuesEvent,2016-03-27 18:05:55,Bernie-2016/ground-control,https://api.github.com/repos/Bernie-2016/ground-control,opened,Add logging for which user is taking admin actions,priority-medium project-event-admin,"[] - Update Event
[] - Delete Event
[] - Send Event Mail
[] - Approve FastForward Request",1.0,"Add logging for which user is taking admin actions - [] - Update Event
[] - Delete Event
[] - Send Event Mail
[] - Approve FastForward Request",0,add logging for which user is taking admin actions       update event     delete event     send event mail     approve fastforward request,0
108794,23664428850.0,IssuesEvent,2022-08-26 19:07:06,unoplatform/uno,https://api.github.com/repos/unoplatform/uno,opened,Enable XAML Trimming for `net6.0-[ios|android|macos|maccatalyst]` and GTK targets,kind/enhancement area/code-generation,"## What would you like to be added:

Support for [XAML Trimming](https://platform.uno/docs/articles/features/resources-trimming.html?) for `net6.0-[ios|android|macos|maccatalyst]` and GTK targets.

## Why is this needed:

Reduce the size of applications.

## Anything else we need to know?
WPF is explicitly excluded from this list as trimming is forcibly disabled by the SDK.

Work branch: https://github.com/unoplatform/uno/tree/dev/eb/xaml-trimming-net6

## Related issues
- https://github.com/dotnet/sdk/issues/27492
- https://github.com/xamarin/xamarin-android/issues/7301

",1.0,"Enable XAML Trimming for `net6.0-[ios|android|macos|maccatalyst]` and GTK targets - ## What would you like to be added:

Support for [XAML Trimming](https://platform.uno/docs/articles/features/resources-trimming.html?) for `net6.0-[ios|android|macos|maccatalyst]` and GTK targets.

## Why is this needed:

Reduce the size of applications.

## Anything else we need to know?
WPF is explicitly excluded from this list as trimming is forcibly disabled by the SDK.

Work branch: https://github.com/unoplatform/uno/tree/dev/eb/xaml-trimming-net6

## Related issues
- https://github.com/dotnet/sdk/issues/27492
- https://github.com/xamarin/xamarin-android/issues/7301

",0,enable xaml trimming for         and gtk targets      what would you like to be added     support for     for         and gtk targets        why is this needed     reduce the size of applications        anything else we need to know   wpf is explicitly excluded from this list as trimming is forcibly disabled by the sdk     work branch          related issues              ,0
19906,4461572190.0,IssuesEvent,2016-08-24 06:24:49,golang/go,https://api.github.com/repos/golang/go,closed,errors: example_test doesn't use errors package,Documentation,"The example in the errors package doesn't import or use the errors package.

The example illustrates how to implement the error interface but doesn't illustrate any feature of the errors package. If it's agreed the example isn't illustrative I'll attempt to claim the issue.

",1.0,"errors: example_test doesn't use errors package - The example in the errors package doesn't import or use the errors package.

The example illustrates how to implement the error interface but doesn't illustrate any feature of the errors package. If it's agreed the example isn't illustrative I'll attempt to claim the issue.

",1,errors  example test doesn t use errors package   the example in the errors package doesn t import or use the errors package     the example illustrates how to implement the error interface but doesn t illustrate any feature of the errors package  if it s agreed the example isn t illustrative i ll attempt to claim the issue     ,1
236595,18103063521.0,IssuesEvent,2021-09-22 16:03:46,golang/go,https://api.github.com/repos/golang/go,opened,declare a standard for packaging Go for downstream distributions,Documentation,"I have spent the last hour or so very confused, because it seemed like the system's Go 1.17.1 I installed via Arch was very different from the `go version devel go1.18-051df0d722` I installed from source recently. After much digging, I ended up realising that my 1.17.1 was missing all test files and testdata directories, and this seems to be [by design](https://github.com/archlinux/svntogit-community/blob/bd9adbc5205ca199dbe1bf25c6ab077a5bd33113/trunk/PKGBUILD#L81-L82).

I [filed a bug](https://bugs.archlinux.org/task/72209) on the distro in question, and hopefully they'll reconsider. At the very least, they should support some way to install those missing files, because otherwise my install of Go is incomplete; `go test std` gives a weird error and then prints a lot of ""no test files"" warnings. Similarly, `go test all` is (silently) broken for third party modules importing std.

I'm raising this issue because I'm very surprised that downstreams are installing partial GOROOTs and giving the impression that they are full and complete Go installs. As far as I am aware, the only way that Go is supported is when the GOROOT is used from a binary distribution, or from the result of `make.bash` without removing files.

Unfortunately, it seems like different distributions have their own definitions of a Go install, with varying degrees of what files are included.

Some distros which don't install a full GOROOT:

* Arch Linux, as discussed above, removes `*_test.go` and `testdata` files.
* Alpine does the same as Arch; [link](https://git.alpinelinux.org/aports/tree/community/go/APKBUILD?id=1f51a7d64cd9c142f67fec3fd122ab825a5dcc5d#n167)
* Fedora appears to do the same as Arch; cannot find any test files in [link](https://fedora.pkgs.org/34/fedora-x86_64/golang-src-1.16-2.fc34.noarch.rpm.html)
* Homebrew seems to delete a couple of testdata dirs; [link](https://github.com/Homebrew/homebrew-core/blob/4fcd38ceae0b6043289018fd32a9c324511fe6c1/Formula/go.rb#L60-L64)
* Gentoo appears to delete all testdata dirs; [link](https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-lang/go/go-1.17.1.ebuild?id=453fb1ade81143f177daf7465d3620a65d3dce71#n166)
* Nix seems to disable many tests, though it doesn't seem to delete files; [link](https://github.com/NixOS/nixpkgs/blob/a930f7da84786807bb105df40e76b541604c3e72/pkgs/development/compilers/go/1.17.nix#L72-L177)

Distros which appear to install an entire GOROOT:

* Debian appears to include all test files; [link for 1.15 on stable](https://packages.debian.org/bullseye/amd64/golang-1.15-src/filelist)
* Ubuntu seems to do the same as Debian; [link](https://packages.ubuntu.com/hirsute/amd64/golang-1.16-src/filelist)
* FreeBSD seems to also include all files; [link](https://cgit.freebsd.org/ports/tree/lang/go/Makefile?id=c72a8f3160a3d158ee6d095a35f5fed843c5ecb4#n82)
* Winget just uses a full binary install; [link](https://github.com/microsoft/winget-pkgs/blob/8fa1fc3860a989034debc9098e4b129340fd9380/manifests/g/GoLang/Go/1.17.1/GoLang.Go.installer.yaml#L16)

It's also worth noting that some distros split ""bin"", ""src"", and ""doc"" packages. I think I don't have any argument against that, as long as the ""full"" or ""default"" install includes all of them.

I understand that it's normal for downstreams to apply light patches to software while packaging. However, I feel like there's a bit of a disconnect happening here: if I install Go with my system's package manager, right now it appears to be a coin toss whether or not that `GOROOT` will be complete with test files and testdata directories. I imagine there might be other inconsistencies too, such as the `misc` or `doc` directories.

I think it's worthwhile to consider whether we want to be in this situation in the long term. I would say not - it's pretty confusing to the end user.

One way I can imagine we could improve the situation in the long term is for the Go project to define a base set of guidelines for packaging Go. For example, if we declare that it should include `GOROOT/src` without deleting test files, then a common source of variance between distributions would go away. It could also declare whether or not it's OK to omit directories like `misc`, `api`, or `doc`.

If we go the route of defining a ""minimal Go install"" which excludes some files such as `*_test.go` and `testdata`, then I reckon that should be properly tested and supported too. Right now, the experience is somewhat poor, as `go test std` fails with `[amd64] FuncPCTestFn: function FuncPCTestFn missing Go declaration`.

Another route to consider is to reduce the incentive for downstreams to strip files. As far as I have seen, there are two common recurring themes:

* Some files are large. For example, Arch argues that removing test files and data reduces the package size by 100MiB. Perhaps we could try to reduce some of the testdata file sizes.
* Some tests fail or are flaky. For example, Nix seems to disable or patch dozens of tests. Perhaps we should encourage them to file bugs about those.",1.0,"declare a standard for packaging Go for downstream distributions - I have spent the last hour or so very confused, because it seemed like the system's Go 1.17.1 I installed via Arch was very different from the `go version devel go1.18-051df0d722` I installed from source recently. After much digging, I ended up realising that my 1.17.1 was missing all test files and testdata directories, and this seems to be [by design](https://github.com/archlinux/svntogit-community/blob/bd9adbc5205ca199dbe1bf25c6ab077a5bd33113/trunk/PKGBUILD#L81-L82).

I [filed a bug](https://bugs.archlinux.org/task/72209) on the distro in question, and hopefully they'll reconsider. At the very least, they should support some way to install those missing files, because otherwise my install of Go is incomplete; `go test std` gives a weird error and then prints a lot of ""no test files"" warnings. Similarly, `go test all` is (silently) broken for third party modules importing std.

I'm raising this issue because I'm very surprised that downstreams are installing partial GOROOTs and giving the impression that they are full and complete Go installs. As far as I am aware, the only way that Go is supported is when the GOROOT is used from a binary distribution, or from the result of `make.bash` without removing files.

Unfortunately, it seems like different distributions have their own definitions of a Go install, with varying degrees of what files are included.

Some distros which don't install a full GOROOT:

* Arch Linux, as discussed above, removes `*_test.go` and `testdata` files.
* Alpine does the same as Arch; [link](https://git.alpinelinux.org/aports/tree/community/go/APKBUILD?id=1f51a7d64cd9c142f67fec3fd122ab825a5dcc5d#n167)
* Fedora appears to do the same as Arch; cannot find any test files in [link](https://fedora.pkgs.org/34/fedora-x86_64/golang-src-1.16-2.fc34.noarch.rpm.html)
* Homebrew seems to delete a couple of testdata dirs; [link](https://github.com/Homebrew/homebrew-core/blob/4fcd38ceae0b6043289018fd32a9c324511fe6c1/Formula/go.rb#L60-L64)
* Gentoo appears to delete all testdata dirs; [link](https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-lang/go/go-1.17.1.ebuild?id=453fb1ade81143f177daf7465d3620a65d3dce71#n166)
* Nix seems to disable many tests, though it doesn't seem to delete files; [link](https://github.com/NixOS/nixpkgs/blob/a930f7da84786807bb105df40e76b541604c3e72/pkgs/development/compilers/go/1.17.nix#L72-L177)

Distros which appear to install an entire GOROOT:

* Debian appears to include all test files; [link for 1.15 on stable](https://packages.debian.org/bullseye/amd64/golang-1.15-src/filelist)
* Ubuntu seems to do the same as Debian; [link](https://packages.ubuntu.com/hirsute/amd64/golang-1.16-src/filelist)
* FreeBSD seems to also include all files; [link](https://cgit.freebsd.org/ports/tree/lang/go/Makefile?id=c72a8f3160a3d158ee6d095a35f5fed843c5ecb4#n82)
* Winget just uses a full binary install; [link](https://github.com/microsoft/winget-pkgs/blob/8fa1fc3860a989034debc9098e4b129340fd9380/manifests/g/GoLang/Go/1.17.1/GoLang.Go.installer.yaml#L16)

It's also worth noting that some distros split ""bin"", ""src"", and ""doc"" packages. I think I don't have any argument against that, as long as the ""full"" or ""default"" install includes all of them.

I understand that it's normal for downstreams to apply light patches to software while packaging. However, I feel like there's a bit of a disconnect happening here: if I install Go with my system's package manager, right now it appears to be a coin toss whether or not that `GOROOT` will be complete with test files and testdata directories. I imagine there might be other inconsistencies too, such as the `misc` or `doc` directories.

I think it's worthwhile to consider whether we want to be in this situation in the long term. I would say not - it's pretty confusing to the end user.

One way I can imagine we could improve the situation in the long term is for the Go project to define a base set of guidelines for packaging Go. For example, if we declare that it should include `GOROOT/src` without deleting test files, then a common source of variance between distributions would go away. It could also declare whether or not it's OK to omit directories like `misc`, `api`, or `doc`.

If we go the route of defining a ""minimal Go install"" which excludes some files such as `*_test.go` and `testdata`, then I reckon that should be properly tested and supported too. Right now, the experience is somewhat poor, as `go test std` fails with `[amd64] FuncPCTestFn: function FuncPCTestFn missing Go declaration`.

Another route to consider is to reduce the incentive for downstreams to strip files. As far as I have seen, there are two common recurring themes:

* Some files are large. For example, Arch argues that removing test files and data reduces the package size by 100MiB. Perhaps we could try to reduce some of the testdata file sizes.
* Some tests fail or are flaky. For example, Nix seems to disable or patch dozens of tests. Perhaps we should encourage them to file bugs about those.",1,declare a standard for packaging go for downstream distributions   i have spent the last hour or so very confused  because it seemed like the system s go       i installed via arch was very different from the  go version devel        i installed from source recently  after much digging  i ended up realising that my       was missing all test files and testdata directories  and this seems to be        i     on the distro in question  and hopefully they ll reconsider  at the very least  they should support some way to install those missing files  because otherwise my install of go is incomplete   go test std  gives a weird error and then prints a lot of  no test files  warnings  similarly   go test all  is  silently  broken for third party modules importing std     i m raising this issue because i m very surprised that downstreams are installing partial goroots and giving the impression that they are full and complete go installs  as far as i am aware  the only way that go is supported is when the goroot is used from a binary distribution  or from the result of  make bash  without removing files     unfortunately  it seems like different distributions have their own definitions of a go install  with varying degrees of what files are included     some distros which don t install a full goroot       arch linux  as discussed above  removes    test go  and  testdata  files     alpine does the same as arch         fedora appears to do the same as arch  cannot find any test files in        homebrew seems to delete a couple of testdata dirs         gentoo appears to delete all testdata dirs         nix seems to disable many tests  though it doesn t seem to delete files         distros which appear to install an entire goroot       debian appears to include all test files         ubuntu seems to do the same as debian         freebsd seems to also include all files         winget just uses a full binary install         it s also worth noting that some distros split  bin    src   and  doc  packages  i think i don t have any argument against that  as long as the  full  or  default  install includes all of them     i understand that it s normal for downstreams to apply light patches to software while packaging  however  i feel like there s a bit of a disconnect happening here  if i install go with my system s package manager  right now it appears to be a coin toss whether or not that  goroot  will be complete with test files and testdata directories  i imagine there might be other inconsistencies too  such as the  misc  or  doc  directories     i think it s worthwhile to consider whether we want to be in this situation in the long term  i would say not   it s pretty confusing to the end user     one way i can imagine we could improve the situation in the long term is for the go project to define a base set of guidelines for packaging go  for example  if we declare that it should include  goroot src  without deleting test files  then a common source of variance between distributions would go away  it could also declare whether or not it s ok to omit directories like  misc    api   or  doc      if we go the route of defining a  minimal go install  which excludes some files such as    test go  and  testdata   then i reckon that should be properly tested and supported too  right now  the experience is somewhat poor  as  go test std  fails with    funcpctestfn  function funcpctestfn missing go declaration      another route to consider is to reduce the incentive for downstreams to strip files  as far as i have seen  there are two common recurring themes       some files are large  for example  arch argues that removing test files and data reduces the package size by    perhaps we could try to reduce some of the testdata file sizes     some tests fail or are flaky  for example  nix seems to disable or patch dozens of tests  perhaps we should encourage them to file bugs about those ,1
54687,7918267974.0,IssuesEvent,2018-07-04 12:45:37,golang/go,https://api.github.com/repos/golang/go,closed,x/perf: error in README file,Documentation,"Installation instructions say: 
> The easiest way to install is to run `go get -u golang.org/x/perf`.

But running the above command gives:
```
package golang.org/x/perf: no Go files in /Users/gbbr/go/src/golang.org/x/perf
```
I guess correct instruction would be:
> The easiest way to install is to run `go get -u golang.org/x/perf/...`.",1.0,"x/perf: error in README file - Installation instructions say: 
> The easiest way to install is to run `go get -u golang.org/x/perf`.

But running the above command gives:
```
package golang.org/x/perf: no Go files in /Users/gbbr/go/src/golang.org/x/perf
```
I guess correct instruction would be:
> The easiest way to install is to run `go get -u golang.org/x/perf/...`.",1,x perf  error in readme file   installation instructions say      the easiest way to install is to run  go get  u golang org x perf      but running the above command gives        package golang org x perf  no go files in  users gbbr go src golang org x perf       i guess correct instruction would be     the easiest way to install is to run  go get  u golang org x perf      ,1
56758,8123710133.0,IssuesEvent,2018-08-16 15:18:54,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: documentation typo in go help mod download [1.10 backport],CherryPickCandidate Documentation,"@bradfitz requested issue #27030 to be considered for backport to the next 1.10 minor release.

> @gopherbot, please backport to 1.11.
",1.0,"cmd/go: documentation typo in go help mod download [1.10 backport] - @bradfitz requested issue #27030 to be considered for backport to the next 1.10 minor release.

> @gopherbot, please backport to 1.11.
",1,cmd go  documentation typo in go help mod download      bradfitz requested issue    to be considered for backport to the next     minor release      gopherbot  please backport to      ,1
24332,5050089162.0,IssuesEvent,2016-12-20 17:39:15,golang/go,https://api.github.com/repos/golang/go,closed,net: LookupCNAME only works for hostnames with CNAME records,Documentation NeedsFix,"### What version of Go are you using (`go version`)?

`go version go1.7.3 linux/amd64`

### What operating system and processor architecture are you using (`go env`)?

```sh
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""""
GORACE=""""
GOROOT=""/usr/lib/google-golang""
GOTOOLDIR=""/usr/lib/google-golang/pkg/tool/linux_amd64""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build668040631=/tmp/go-build -gno-record-gcc-switches""
CXX=""g++""
CGO_ENABLED=""1""
```

### What did you do?

```go
package main

import (
	""fmt""
	""net""
)

func main() {
	if cname, err := net.LookupCNAME(""www.google.com""); err != nil {
		fmt.Printf(""lookup failed: %q\n"", err)
	} else {
		fmt.Printf(""lookup success: %s\n"", cname)
	}
}
```

### What did you expect to see?

[The documentation](https://golang.org/pkg/net/#LookupCNAME) says ""LookupCNAME returns the canonical DNS host for the given name.""  To me, this means that it returns the canonical name as provided by the [POSIX `getaddrinfo()` function](http://pubs.opengroup.org/onlinepubs/9699919799/functions/getaddrinfo.html) when given the `AI_CANONNAME` flag.  So I expected the following:

`lookup success: www.google.com`

### What did you see instead?

`lookup failed: ""lookup www.google.com on 127.0.1.1:53: no such host""`

It turns out that `LookupCNAME` simply resolves CNAME records, it does NOT return the canonical DNS host for the given name as documented.

### Proposed change

Ideally `LookupCNAME` would return the canonical hostname as provided by the POSIX `getaddrinfo()` function.

If the intention of the `LookupCNAME` function is to only resolve CNAME records, then replace the first sentence of the documentation with:

> LookupCNAME resolves the CNAME DNS record for the given name.  It is an error if the given hostname does not have a CNAME record.",1.0,"net: LookupCNAME only works for hostnames with CNAME records - ### What version of Go are you using (`go version`)?

`go version go1.7.3 linux/amd64`

### What operating system and processor architecture are you using (`go env`)?

```sh
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""""
GORACE=""""
GOROOT=""/usr/lib/google-golang""
GOTOOLDIR=""/usr/lib/google-golang/pkg/tool/linux_amd64""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build668040631=/tmp/go-build -gno-record-gcc-switches""
CXX=""g++""
CGO_ENABLED=""1""
```

### What did you do?

```go
package main

import (
	""fmt""
	""net""
)

func main() {
	if cname, err := net.LookupCNAME(""www.google.com""); err != nil {
		fmt.Printf(""lookup failed: %q\n"", err)
	} else {
		fmt.Printf(""lookup success: %s\n"", cname)
	}
}
```

### What did you expect to see?

[The documentation](https://golang.org/pkg/net/#LookupCNAME) says ""LookupCNAME returns the canonical DNS host for the given name.""  To me, this means that it returns the canonical name as provided by the [POSIX `getaddrinfo()` function](http://pubs.opengroup.org/onlinepubs/9699919799/functions/getaddrinfo.html) when given the `AI_CANONNAME` flag.  So I expected the following:

`lookup success: www.google.com`

### What did you see instead?

`lookup failed: ""lookup www.google.com on 127.0.1.1:53: no such host""`

It turns out that `LookupCNAME` simply resolves CNAME records, it does NOT return the canonical DNS host for the given name as documented.

### Proposed change

Ideally `LookupCNAME` would return the canonical hostname as provided by the POSIX `getaddrinfo()` function.

If the intention of the `LookupCNAME` function is to only resolve CNAME records, then replace the first sentence of the documentation with:

> LookupCNAME resolves the CNAME DNS record for the given name.  It is an error if the given hostname does not have a CNAME record.",1,net  lookupcname only works for hostnames with cname records       what version of go are you using   go version        go version       linux           what operating system and processor architecture are you using   go env          sh  goarch      gobin     goexe     gohostarch      gohostos  linux   goos  linux   gopath     gorace     goroot   usr lib google golang   gotooldir   usr lib google golang pkg tool linux     cc  gcc   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches   cxx  g     cgo enabled                 what did you do        go  package main    import    	 fmt   	 net        func main      	if cname  err    net lookupcname    err    nil    		fmt printf  lookup failed   q n   err   	  else    		fmt printf  lookup success   s n   cname   	                 what did you expect to see         says  lookupcname returns the canonical dns host for the given name    to me  this means that it returns the canonical name as provided by the     when given the  ai canonname  flag   so i expected the following      lookup success           what did you see instead      lookup failed   lookup   on            no such host      it turns out that  lookupcname  simply resolves cname records  it does not return the canonical dns host for the given name as documented         proposed change    ideally  lookupcname  would return the canonical hostname as provided by the posix  getaddrinfo    function     if the intention of the  lookupcname  function is to only resolve cname records  then replace the first sentence of the documentation with       lookupcname resolves the cname dns record for the given name   it is an error if the given hostname does not have a cname record ,1
19691,4440076113.0,IssuesEvent,2016-08-19 01:02:15,golang/go,https://api.github.com/repos/golang/go,closed,log/syslog: Dial function needs examples,Documentation,"Please answer these questions before submitting your issue. Thanks!

1. What version of Go are you using (`go version`)?

 1.7

2. What operating system and processor architecture are you using (`go env`)?

darwin/amd_64

3. What did you do?

Tried to view  the docs for https://golang.org/pkg/log/syslog/#Dial

4. What did you expect to see?

Documentation/examples describing what the 'network' and 'raddr' values should be.

5. What did you see instead?

No mention of what those should be. It appears 'network' refers to 'address family' or 'protocol' (tcp/udp/unix/unixgram), rather than some string representing a network address. 'raddr' seems to be the 'host:port', or file path string for connecting to the socket.  I had to browse the test suite's source code to figure out what these should be. ",1.0,"log/syslog: Dial function needs examples - Please answer these questions before submitting your issue. Thanks!

1. What version of Go are you using (`go version`)?

 1.7

2. What operating system and processor architecture are you using (`go env`)?

darwin/amd_64

3. What did you do?

Tried to view  the docs for https://golang.org/pkg/log/syslog/#Dial

4. What did you expect to see?

Documentation/examples describing what the 'network' and 'raddr' values should be.

5. What did you see instead?

No mention of what those should be. It appears 'network' refers to 'address family' or 'protocol' (tcp/udp/unix/unixgram), rather than some string representing a network address. 'raddr' seems to be the 'host:port', or file path string for connecting to the socket.  I had to browse the test suite's source code to figure out what these should be. ",1,log syslog  dial function needs examples   please answer these questions before submitting your issue  thanks        what version of go are you using   go version                  what operating system and processor architecture are you using   go env       darwin amd         what did you do     tried to view  the docs for         what did you expect to see     documentation examples describing what the  network  and  raddr  values should be        what did you see instead     no mention of what those should be  it appears  network  refers to  address family  or  protocol   tcp udp unix unixgram   rather than some string representing a network address   raddr  seems to be the  host port   or file path string for connecting to the socket   i had to browse the test suite s source code to figure out what these should be  ,1
413107,12060463091.0,IssuesEvent,2020-04-15 21:15:40,webcompat/web-bugs,https://api.github.com/repos/webcompat/web-bugs,closed,glitch.com - Builtin function has different length property in console,browser-chrome priority-normal severity-minor,"<!-- @browser: Chrome 71.0.3578 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 -->
<!-- @reported_with: web -->

**URL**: https://glitch.com/edit/#!/builtin-function-length

**Browser / Version**: Chrome 71.0.3578
**Operating System**: Windows 10
**Tested Another Browser**: Yes

**Problem type**: Something else
**Description**: In Chrome the builtin function console.warn has a length property of one while Firefox and Edge have a length value of zero
**Steps to Reproduce**:


<details>
<summary>Browser Configuration</summary>
<ul>
  <li>None</li>
</ul>

</details>

Reported by @rajsite

_From [webcompat.com](https://webcompat.com/) with ❤️_",1.0,"glitch.com - Builtin function has different length property in console - <!-- @browser: Chrome 71.0.3578 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 -->
<!-- @reported_with: web -->

**URL**: https://glitch.com/edit/#!/builtin-function-length

**Browser / Version**: Chrome 71.0.3578
**Operating System**: Windows 10
**Tested Another Browser**: Yes

**Problem type**: Something else
**Description**: In Chrome the builtin function console.warn has a length property of one while Firefox and Edge have a length value of zero
**Steps to Reproduce**:


<details>
<summary>Browser Configuration</summary>
<ul>
  <li>None</li>
</ul>

</details>

Reported by @rajsite

_From [webcompat.com](https://webcompat.com/) with ❤️_",0,glitch com   builtin function has different length property in console            url         browser   version    chrome         operating system    windows     tested another browser    yes    problem type    something else   description    in chrome the builtin function console warn has a length property of one while firefox and edge have a length value of zero   steps to reproduce         browser configuration       none        reported by  rajsite   from     with ❤️ ,0
294608,22157971082.0,IssuesEvent,2022-06-04 03:57:40,golang/go,https://api.github.com/repos/golang/go,closed,documentation: Go internal abi specification document alignment confusion,Documentation NeedsInvestigation,"Hello everyone!

I hope that this is the right place to raise this issue:

I have read through the ""Go internal ABI specification"" (src/cmd/compile/internal-abi.md) and have studied the excellent, thorough discussion of the definition of the alignment of sequences (of which a `struct` is a special case) and the alignment of built-in types. 

I am curious, however, how that squares with the following statement
> On ARM, 386, and 32-bit MIPS, it is the caller's responsibility to arrange for 64-bit alignment of 64-bit words accessed atomically. The first word in a variable or in an allocated struct, array, or slice can be relied upon to be 64-bit aligned. 

from https://pkg.go.dev/sync/atomic#pkg-note-BUG. 

Nothing in the ""Go internal ABI specification"" seems to indicate that there is a special case for these architectures. I was just wondering if this is is because the representation made by https://pkg.go.dev/sync/atomic#pkg-note-BUG concerns the ""public"" ABI and would supersede the definitions/algorithms in the internal ABI in this case?

Or, is it simply something that is just out of date with a (admittedly internal) piece of documentation. If it is, I would be glad to submit a patch for the ""Go internal ABI specification"" document to bring it up to date.

That document is such a helpful, interesting read for so many reasons and one of the main reasons why I really enjoy working with this language!

Thanks for everything!
Will

cc @danscales ",1.0,"documentation: Go internal abi specification document alignment confusion - Hello everyone!

I hope that this is the right place to raise this issue:

I have read through the ""Go internal ABI specification"" (src/cmd/compile/internal-abi.md) and have studied the excellent, thorough discussion of the definition of the alignment of sequences (of which a `struct` is a special case) and the alignment of built-in types. 

I am curious, however, how that squares with the following statement
> On ARM, 386, and 32-bit MIPS, it is the caller's responsibility to arrange for 64-bit alignment of 64-bit words accessed atomically. The first word in a variable or in an allocated struct, array, or slice can be relied upon to be 64-bit aligned. 

from https://pkg.go.dev/sync/atomic#pkg-note-BUG. 

Nothing in the ""Go internal ABI specification"" seems to indicate that there is a special case for these architectures. I was just wondering if this is is because the representation made by https://pkg.go.dev/sync/atomic#pkg-note-BUG concerns the ""public"" ABI and would supersede the definitions/algorithms in the internal ABI in this case?

Or, is it simply something that is just out of date with a (admittedly internal) piece of documentation. If it is, I would be glad to submit a patch for the ""Go internal ABI specification"" document to bring it up to date.

That document is such a helpful, interesting read for so many reasons and one of the main reasons why I really enjoy working with this language!

Thanks for everything!
Will

cc @danscales ",1,documentation  go internal abi specification document alignment confusion   hello everyone     i hope that this is the right place to raise this issue     i have read through the  go internal abi specification   src cmd compile internal abi md  and have studied the excellent  thorough discussion of the definition of the alignment of sequences  of which a  struct  is a special case  and the alignment of built in types      i am curious  however  how that squares with the following statement    on arm     and   bit mips  it is the caller s responsibility to arrange for   bit alignment of   bit words accessed atomically  the first word in a variable or in an allocated struct  array  or slice can be relied upon to be   bit aligned      from       nothing in the  go internal abi specification  seems to indicate that there is a special case for these architectures  i was just wondering if this is is because the representation made by   concerns the  public  abi and would supersede the definitions algorithms in the internal abi in this case     or  is it simply something that is just out of date with a  admittedly internal  piece of documentation  if it is  i would be glad to submit a patch for the  go internal abi specification  document to bring it up to date     that document is such a helpful  interesting read for so many reasons and one of the main reasons why i really enjoy working with this language     thanks for everything   will    cc  danscales ,1
23115,4877616701.0,IssuesEvent,2016-11-16 16:06:26,golang/go,https://api.github.com/repos/golang/go,closed,database/sql: clarify docs for Tx.Stmt().Close(),Documentation NeedsInvestigation,"`Tx.Stmt()` example (https://github.com/golang/go/blob/733aefd06e5cf708637308a4ad7a048aa97db5cd/src/database/sql/sql.go#L1332) shows the following code:

```
res, err := tx.Stmt(updateMoney).Exec(123.45, 98293203)
```

Looking at that code I assume there is no need to explicitly close the `Stmt` returned from `tx.Stmt(updateMoney)` because example does not even store references to it.

On the other hand, tests (https://github.com/golang/go/blob/733aefd06e5cf708637308a4ad7a048aa97db5cd/src/database/sql/sql_test.go#L577 and https://github.com/golang/go/blob/733aefd06e5cf708637308a4ad7a048aa97db5cd/src/database/sql/sql_test.go#L665) are explicitly closing that `Stmt`.

So I wonder - is there an actual need to `.Close()` the prepared statements returned from `tx.Stmt()` or rollback/commit will close them automatically?

/cc @bradfitz 
",1.0,"database/sql: clarify docs for Tx.Stmt().Close() - `Tx.Stmt()` example (https://github.com/golang/go/blob/733aefd06e5cf708637308a4ad7a048aa97db5cd/src/database/sql/sql.go#L1332) shows the following code:

```
res, err := tx.Stmt(updateMoney).Exec(123.45, 98293203)
```

Looking at that code I assume there is no need to explicitly close the `Stmt` returned from `tx.Stmt(updateMoney)` because example does not even store references to it.

On the other hand, tests (https://github.com/golang/go/blob/733aefd06e5cf708637308a4ad7a048aa97db5cd/src/database/sql/sql_test.go#L577 and https://github.com/golang/go/blob/733aefd06e5cf708637308a4ad7a048aa97db5cd/src/database/sql/sql_test.go#L665) are explicitly closing that `Stmt`.

So I wonder - is there an actual need to `.Close()` the prepared statements returned from `tx.Stmt()` or rollback/commit will close them automatically?

/cc @bradfitz 
",1,database sql  clarify docs for tx stmt   close      tx stmt    example    shows the following code       res  err    tx stmt updatemoney  exec              looking at that code i assume there is no need to explicitly close the  stmt  returned from  tx stmt updatemoney   because example does not even store references to it   on the other hand  tests    and   are explicitly closing that  stmt    so i wonder   is there an actual need to   close    the prepared statements returned from  tx stmt    or rollback commit will close them automatically    cc  bradfitz  ,1
35096,6412685159.0,IssuesEvent,2017-08-08 04:31:21,golang/go,https://api.github.com/repos/golang/go,closed,encoding/json: indentation of raw strings in examples looks suboptimal in godoc,Documentation NeedsFix Suggested,"### Motivation

There are two ways a Go [example](https://godoc.org/testing#hdr-Examples) can be read:

1. In the source code of a _test.go file.
2. Via `godoc` command or the web interface it provides.

In most cases, examples look equally good in both interfaces. However, in some cases, there may be two alternative ways to write an example, such that one of them looks better inside source code, and the other looks better in the godoc interface.

My understanding is that it's better to prioritize the godoc interface over the source code, since most people will be reading examples via godoc (be it locally, or via https://godoc.org, or https://golang.org/pkg/). If that is not correct, the rest of this issue is not valid.

## Issue

I found that there are 5 examples in `encoding/json` package that have raw strings with indentation which is suboptimal when seen via the godoc interface.

They are:

- [ ] https://tip.golang.org/pkg/encoding/json/#example_Decoder:

    ![image](https://user-images.githubusercontent.com/1924134/28241824-68a28366-6959-11e7-89d7-2c74dab82d11.png)

- [x] https://tip.golang.org/pkg/encoding/json/#example_Decoder_Decode_stream:
    (Resolved by CL [48910](https://golang.org/cl/48910).)

    ![image](https://user-images.githubusercontent.com/1924134/28241827-75ee5496-6959-11e7-9944-f7ddb66308dd.png)

- [ ] https://tip.golang.org/pkg/encoding/json/#example_Decoder_Token:

    ![image](https://user-images.githubusercontent.com/1924134/28241828-7f1f46ec-6959-11e7-9512-b77c36adfec0.png)

- [ ] https://tip.golang.org/pkg/encoding/json/#example_Unmarshal:

    ![image](https://user-images.githubusercontent.com/1924134/28244990-79478be4-69b8-11e7-931c-8110289ec0ed.png)

- [ ] https://tip.golang.org/pkg/encoding/json/#example_RawMessage_unmarshal:

    ![image](https://user-images.githubusercontent.com/1924134/28245003-b28835f2-69b8-11e7-81e9-14ff04275f5b.png)

Their readability in godoc interface can be improved by dedenting the contents of the raw string by 1 tab.",1.0,"encoding/json: indentation of raw strings in examples looks suboptimal in godoc - ### Motivation

There are two ways a Go [example](https://godoc.org/testing#hdr-Examples) can be read:

1. In the source code of a _test.go file.
2. Via `godoc` command or the web interface it provides.

In most cases, examples look equally good in both interfaces. However, in some cases, there may be two alternative ways to write an example, such that one of them looks better inside source code, and the other looks better in the godoc interface.

My understanding is that it's better to prioritize the godoc interface over the source code, since most people will be reading examples via godoc (be it locally, or via https://godoc.org, or https://golang.org/pkg/). If that is not correct, the rest of this issue is not valid.

## Issue

I found that there are 5 examples in `encoding/json` package that have raw strings with indentation which is suboptimal when seen via the godoc interface.

They are:

- [ ] https://tip.golang.org/pkg/encoding/json/#example_Decoder:

    ![image](https://user-images.githubusercontent.com/1924134/28241824-68a28366-6959-11e7-89d7-2c74dab82d11.png)

- [x] https://tip.golang.org/pkg/encoding/json/#example_Decoder_Decode_stream:
    (Resolved by CL [48910](https://golang.org/cl/48910).)

    ![image](https://user-images.githubusercontent.com/1924134/28241827-75ee5496-6959-11e7-9944-f7ddb66308dd.png)

- [ ] https://tip.golang.org/pkg/encoding/json/#example_Decoder_Token:

    ![image](https://user-images.githubusercontent.com/1924134/28241828-7f1f46ec-6959-11e7-9512-b77c36adfec0.png)

- [ ] https://tip.golang.org/pkg/encoding/json/#example_Unmarshal:

    ![image](https://user-images.githubusercontent.com/1924134/28244990-79478be4-69b8-11e7-931c-8110289ec0ed.png)

- [ ] https://tip.golang.org/pkg/encoding/json/#example_RawMessage_unmarshal:

    ![image](https://user-images.githubusercontent.com/1924134/28245003-b28835f2-69b8-11e7-81e9-14ff04275f5b.png)

Their readability in godoc interface can be improved by dedenting the contents of the raw string by 1 tab.",1,encoding json  indentation of raw strings in examples looks suboptimal in godoc       motivation    there are two ways a go     can be read        in the source code of a  test go file      via  godoc  command or the web interface it provides     in most cases  examples look equally good in both interfaces  however  in some cases  there may be two alternative ways to write an example  such that one of them looks better inside source code  and the other looks better in the godoc interface     my understanding is that it s better to prioritize the godoc interface over the source code  since most people will be reading examples via godoc  be it locally  or via   or   if that is not correct  the rest of this issue is not valid        issue    i found that there are   examples in  encoding json  package that have raw strings with indentation which is suboptimal when seen via the godoc interface     they are                                      resolved by cl                                                                                   their readability in godoc interface can be improved by dedenting the contents of the raw string by   tab ,1
246621,7895435149.0,IssuesEvent,2018-06-29 03:15:40,aowen87/BAR,https://api.github.com/repos/aowen87/BAR,closed,Shift left button no longer constrains to 1:1 rectangles when zooming in 2d zoom mode.,Likelihood: 3 - Occasional OS: All Priority: Normal Severity: 3 - Major Irritation Support Group: Any bug version: 2.6.0,"When you are in zoom mode and you use shift left button press to zoom, the rectangle should be constrained to a 1:1 rectangle. Now it just pans the image like in navigate mode. Furthermore, if you release the shift button before releasing the mouse button, it will be stuck navigating (i.e. if you move the mouse it will pan the image even if you are not pressing the left mouse button). This was broken in visit 2.6.0. 2.5.2 works properly.



-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. The following information
could not be accurately captured in the new ticket:

Original author: Eric Brugger
Original creation: 04/16/2013 02:28 pm
Original update: 06/24/2013 06:26 pm
Ticket number: 1426",1.0,"Shift left button no longer constrains to 1:1 rectangles when zooming in 2d zoom mode. - When you are in zoom mode and you use shift left button press to zoom, the rectangle should be constrained to a 1:1 rectangle. Now it just pans the image like in navigate mode. Furthermore, if you release the shift button before releasing the mouse button, it will be stuck navigating (i.e. if you move the mouse it will pan the image even if you are not pressing the left mouse button). This was broken in visit 2.6.0. 2.5.2 works properly.



-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. The following information
could not be accurately captured in the new ticket:

Original author: Eric Brugger
Original creation: 04/16/2013 02:28 pm
Original update: 06/24/2013 06:26 pm
Ticket number: 1426",0,shift left button no longer constrains to     rectangles when zooming in   zoom mode    when you are in zoom mode and you use shift left button press to zoom  the rectangle should be constrained to a     rectangle  now it just pans the image like in navigate mode  furthermore  if you release the shift button before releasing the mouse button  it will be stuck navigating  i e  if you move the mouse it will pan the image even if you are not pressing the left mouse button   this was broken in visit              works properly                            redmine migration                        this ticket was migrated from redmine  the following information could not be accurately captured in the new ticket   original author  eric brugger original creation            pm original update            pm ticket number   ,0
14591,10980170450.0,IssuesEvent,2019-11-30 12:12:53,eclipse/vorto,https://api.github.com/repos/eclipse/vorto,closed,Notify Github if CLM evaluation has policy issues,Infrastructure,If the CLM scan detects critical issues notify Github with a failure for the compliance check.,1.0,Notify Github if CLM evaluation has policy issues - If the CLM scan detects critical issues notify Github with a failure for the compliance check.,0,notify github if clm evaluation has policy issues   if the clm scan detects critical issues notify github with a failure for the compliance check ,0
183532,14944063121.0,IssuesEvent,2021-01-26 00:30:58,golang/go,https://api.github.com/repos/golang/go,closed,os: document file descriptor ownership semantics for os.NewFile(),Documentation NeedsFix,"### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.15.6 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/vic/.cache/go-build""
GOENV=""/home/vic/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/vic/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/vic/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/lib/go-1.15""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/lib/go-1.15/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/vic/go/src/github.com/optimyze/prodfiler/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build483022862=/tmp/go-build -gno-record-gcc-switches""

</pre></details>

### What did you do?
I am not providing a repro case here, as this is dependent on GC pressure & is intended behavior
What I did: I used `os.NewFile` with a file descriptor owned by a different piece of code. To illustrate:

```go
func func1(fd uintptr) {
    myFile := os.NewFile(fd, """")
    [do some stuff with myFile, like using interfaces that require an io.ReadSeeker]
    [not closing myFile, not closing fd]
}

func func2() {
    fd := getFDFromSomewhere()
    func1(fd)
    // code using fd after this is unedefined behavior
    // Indeed, fd might get closed at any point when `myFile` (in `func1`) gets garbage collected
}
```

This seems to be intended behavior because of: https://github.com/golang/go/blob/master/src/os/file_unix.go#L178
The GC behavior is documented on `os.File.Fd()`: https://github.com/golang/go/blob/master/src/os/file_unix.go#L65

### What did you expect to see?
I expected to see a comment on `os.NewFile` warning me that the naked file descriptor can only be used while the returned `os.File` isn't garbage-collected

### What did you see instead?
Documentation isn't explicit (unless I was looking at the wrong place?), `os.NewFIle` doesn't mention garbage collection at all.
This triggered a difficult-to-reproduce/diagnose bug in my service - I had to go and read the Golang source code to find the root cause.

I'll be happy to open a PR to fix the documentation if this issue seems legit.
Thanks!",1.0,"os: document file descriptor ownership semantics for os.NewFile() - ### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.15.6 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/vic/.cache/go-build""
GOENV=""/home/vic/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/vic/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/vic/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/lib/go-1.15""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/lib/go-1.15/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/vic/go/src/github.com/optimyze/prodfiler/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build483022862=/tmp/go-build -gno-record-gcc-switches""

</pre></details>

### What did you do?
I am not providing a repro case here, as this is dependent on GC pressure & is intended behavior
What I did: I used `os.NewFile` with a file descriptor owned by a different piece of code. To illustrate:

```go
func func1(fd uintptr) {
    myFile := os.NewFile(fd, """")
    [do some stuff with myFile, like using interfaces that require an io.ReadSeeker]
    [not closing myFile, not closing fd]
}

func func2() {
    fd := getFDFromSomewhere()
    func1(fd)
    // code using fd after this is unedefined behavior
    // Indeed, fd might get closed at any point when `myFile` (in `func1`) gets garbage collected
}
```

This seems to be intended behavior because of: https://github.com/golang/go/blob/master/src/os/file_unix.go#L178
The GC behavior is documented on `os.File.Fd()`: https://github.com/golang/go/blob/master/src/os/file_unix.go#L65

### What did you expect to see?
I expected to see a comment on `os.NewFile` warning me that the naked file descriptor can only be used while the returned `os.File` isn't garbage-collected

### What did you see instead?
Documentation isn't explicit (unless I was looking at the wrong place?), `os.NewFIle` doesn't mention garbage collection at all.
This triggered a difficult-to-reproduce/diagnose bug in my service - I had to go and read the Golang source code to find the root cause.

I'll be happy to open a PR to fix the documentation if this issue seems legit.
Thanks!",1,os  document file descriptor ownership semantics for os newfile         what version of go are you using   go version            go version  go version       linux             does this issue reproduce with the latest release   yes          what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   home vic  cache go build   goenv   home vic  config go env   goexe     goflags     gohostarch      gohostos  linux   goinsecure     gomodcache   home vic go pkg mod   gonoproxy     gonosumdb     goos  linux   gopath   home vic go   goprivate     goproxy     goroot   usr lib go       gosumdb  sum golang org   gotmpdir     gotooldir   usr lib go     pkg tool linux     gccgo  gccgo   ar  ar   cc  gcc   cxx  g     cgo enabled      gomod   home vic go src github com optimyze prodfiler go mod   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches               what did you do   i am not providing a repro case here  as this is dependent on gc pressure   is intended behavior  what i did  i used  os newfile  with a file descriptor owned by a different piece of code  to illustrate        go  func   fd uintptr         myfile    os newfile fd                          func            fd    getfdfromsomewhere          fd          code using fd after this is unedefined behavior         indeed  fd might get closed at any point when  myfile   in      gets garbage collected            this seems to be intended behavior because of     the gc behavior is documented on  os file fd              what did you expect to see   i expected to see a comment on  os newfile  warning me that the naked file descriptor can only be used while the returned  os file  isn t garbage collected        what did you see instead   documentation isn t explicit  unless i was looking at the wrong place     os newfile  doesn t mention garbage collection at all   this triggered a difficult to reproduce diagnose bug in my service   i had to go and read the golang source code to find the root cause     i ll be happy to open a pr to fix the documentation if this issue seems legit   thanks ,1
76808,15496203695.0,IssuesEvent,2021-03-11 02:14:59,n-devs/test-ux,https://api.github.com/repos/n-devs/test-ux,opened,CVE-2020-7720 (High) detected in node-forge-0.6.33.tgz,security vulnerability,"## CVE-2020-7720 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-forge-0.6.33.tgz</b></p></summary>

<p>JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/node-forge/-/node-forge-0.6.33.tgz"">https://registry.npmjs.org/node-forge/-/node-forge-0.6.33.tgz</a></p>
<p>Path to dependency file: /test-ux/package.json</p>
<p>Path to vulnerable library: test-ux/node_modules/node-forge/package.json</p>
<p>

Dependency Hierarchy:
  - react-scripts-1.0.17.tgz (Root Library)
    - webpack-dev-server-2.9.4.tgz
      - selfsigned-1.10.1.tgz
        - :x: **node-forge-0.6.33.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>  
  
The package node-forge before 0.10.0 is vulnerable to Prototype Pollution via the util.setPath function. Note: Version 0.10.0 is a breaking change removing the vulnerable functions.

<p>Publish Date: 2020-09-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7720>CVE-2020-7720</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.3</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/digitalbazaar/forge/blob/master/CHANGELOG.md"">https://github.com/digitalbazaar/forge/blob/master/CHANGELOG.md</a></p>
<p>Release Date: 2020-09-13</p>
<p>Fix Resolution: node-forge - 0.10.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-2020-7720 (High) detected in node-forge-0.6.33.tgz - ## CVE-2020-7720 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-forge-0.6.33.tgz</b></p></summary>

<p>JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/node-forge/-/node-forge-0.6.33.tgz"">https://registry.npmjs.org/node-forge/-/node-forge-0.6.33.tgz</a></p>
<p>Path to dependency file: /test-ux/package.json</p>
<p>Path to vulnerable library: test-ux/node_modules/node-forge/package.json</p>
<p>

Dependency Hierarchy:
  - react-scripts-1.0.17.tgz (Root Library)
    - webpack-dev-server-2.9.4.tgz
      - selfsigned-1.10.1.tgz
        - :x: **node-forge-0.6.33.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>  
  
The package node-forge before 0.10.0 is vulnerable to Prototype Pollution via the util.setPath function. Note: Version 0.10.0 is a breaking change removing the vulnerable functions.

<p>Publish Date: 2020-09-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7720>CVE-2020-7720</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.3</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/digitalbazaar/forge/blob/master/CHANGELOG.md"">https://github.com/digitalbazaar/forge/blob/master/CHANGELOG.md</a></p>
<p>Release Date: 2020-09-13</p>
<p>Fix Resolution: node-forge - 0.10.0</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in node forge       tgz      cve       high severity vulnerability     vulnerable library    node forge       tgz      javascript implementations of network transports  cryptography  ciphers  pki  message digests  and various utilities    library home page   a href     path to dependency file   test ux package json   path to vulnerable library  test ux node modules node forge package json     dependency hierarchy      react scripts       tgz  root library        webpack dev server       tgz         selfsigned       tgz            x    node forge       tgz    vulnerable library             vulnerability details         the package node forge before       is vulnerable to prototype pollution via the util setpath function  note  version       is a breaking change removing the vulnerable functions    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  low     integrity impact  low     availability impact  low   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  node forge                       step up your open source security game with whitesource    ,0
459887,13200866474.0,IssuesEvent,2020-08-14 09:03:02,grpc/grpc,https://api.github.com/repos/grpc/grpc,opened,mysterious deadlock in stop_threads() from timer_manager.cc (explained),kind/bug priority/P2,"We're using the latest available version of PHP GRPC extension - 1.31.0 on Linux servers, GCC is quite new, 8 probably, it doesn't really matter in this case.

We have quite a lot of servers running PHP scripts and some of these scripts are ran from crontab, i.e. a regular cronjob starts a launcher script that forks (yes, FORKS) to process some jobs.

We don't really use GRPC extension (yet), but after enabling the extension in php.ini we've noticed that some of the servers are hanging up - the number of PHP processes builds up and they appear to be stuck somewhere in GRPC internals with the following backtrace:
```
0x00007fdbc929c0f0 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
(gdb) bt
#0 0x00007fdbc929c0f0 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1 0x00007fdbc233912c in gpr_cv_wait (cv=0x7fdbc2947d00 <g_cv_shutdown>, mu=0x7fdbc2947c80 <g_mu>, abs_deadline=...)
   at /build/grpc-1.30.0/src/core/lib/gpr/sync_posix.cc:130
#2 0x00007fdbc236aaa2 in stop_threads () at /build/grpc-1.30.0/src/core/lib/iomgr/timer_manager.cc:326
#3 0x00007fdbc236ab59 in grpc_timer_manager_set_threading (threaded=false) at /build/grpc-1.30.0/src/core/lib/iomgr/timer_manager.cc:349
#4 0x00007fdbc2353b88 in grpc_prefork () at /build/grpc-1.30.0/src/core/lib/iomgr/fork_posix.cc:80
#5 0x00007fdbc979e6bc in fork () from /lib64/libc.so.6
```

If we kill the PHP processes, they start working again and after an hour or two we get the same situation - lots of deadlocked PHP processes.
And if we remove GRPC from the configuration, the problem also disappears, so GRPC somehow causes it for sure.

GDB showed that g_thread_count is 1, while there are no threads except for the waiting one. 
It's waiting on conditional variable which is signaled when all threads exit, but no threads are running.
That looked weird.

We've been trying to find a reproduce case for days running different scripts with fork(), exec() and whatnot, but no luck.

At the same time we noticed a strange issue with cron itself - it appears that cron refused to run additional processes with an obscure error message ""Resource temporarily unavailable"". That was the clue.

So after an extensive debugging and digging all over the system we found the culprit - it was a combination of cgroup pids.max limit in /sys/fs/cgroup/pids/system.slice/cron.service/pids.max and GRPC.

For some reason we had quite low pid.max limit: only 512 (don't ask, it's still being investigated) and this number appears to limit ""tasks"", which include processes and threads ([see here](https://www.kernel.org/doc/Documentation/cgroup-v1/pids.txt)).
Because of that system did not allow cron to run new processes _and threads_ after reaching 512 of them in total.
It was working fine until we've added grpc extension to PHP - it added additional thread ran by GRPC core - the timer_thread, so the number of ""tasks"" doubled and we started to hit the limit.

Here comes the interesting part:
GRPC core implements an abstraction class Thread that is supposed to hide all the implementation details of POSIX and Win32 threads. Unfortunately, it also hides pthread_create() result - [nothing is returned](https://github.com/grpc/grpc/blob/master/src/core/lib/gprpp/thd_posix.cc#L164), there are [no error messages](https://github.com/grpc/grpc/blob/master/src/core/lib/gprpp/thd_posix.cc#L150) or any kind of indication that the thread has failed to start.

So here is what happened:
1) we've come close to the limit of 512 threads + processes
2) a PHP process loaded GRPC extension, which initialized GRPC core, which in turn called [start_timer_thread_and_unlock](https://github.com/grpc/grpc/blob/master/src/core/lib/iomgr/timer_manager.cc#L82)() 
3) start_timer_thread_and_lock() incremented g_thread_count and tried to start new thread
4) we hit the limit and the thread did not start 
5) since it's failed to start, its [cleanup function](https://github.com/grpc/grpc/blob/master/src/core/lib/iomgr/timer_manager.cc#L263) was also never executed
6) because of that g_thread_count was not decremented and remained 1
7) stop_threads() was called as a pre-fork handler, but it wasn't able to finish because g_thread_count is always 1 and there are no threads to decrement the value
8) now we're waiting indefinitely on conditional variable g_cv_shutdown, but it will never change

So first of all, apparently, the issue was caused by the cgroup (mis)configuration, but I do believe it's also wrong that GRPC core does not check the result of pthread_create() and just assumes it always succeeds.

Moving g_thread_count++ into timer_thread() itself looks like an easy quick-fix, but I haven't tried it myself and there might be other problems caused by the inability to spawn threads, so I guess changing the core to return the result of pthread_create() and checking it before incrementing the g_thread_count is the right way to fix it.

In addition, it looks like issues #11711 and #10658 could have been caused by similar misconfiguration + GRPC combinations.",1.0,"mysterious deadlock in stop_threads() from timer_manager.cc (explained) - We're using the latest available version of PHP GRPC extension - 1.31.0 on Linux servers, GCC is quite new, 8 probably, it doesn't really matter in this case.

We have quite a lot of servers running PHP scripts and some of these scripts are ran from crontab, i.e. a regular cronjob starts a launcher script that forks (yes, FORKS) to process some jobs.

We don't really use GRPC extension (yet), but after enabling the extension in php.ini we've noticed that some of the servers are hanging up - the number of PHP processes builds up and they appear to be stuck somewhere in GRPC internals with the following backtrace:
```
0x00007fdbc929c0f0 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
(gdb) bt
#0 0x00007fdbc929c0f0 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1 0x00007fdbc233912c in gpr_cv_wait (cv=0x7fdbc2947d00 <g_cv_shutdown>, mu=0x7fdbc2947c80 <g_mu>, abs_deadline=...)
   at /build/grpc-1.30.0/src/core/lib/gpr/sync_posix.cc:130
#2 0x00007fdbc236aaa2 in stop_threads () at /build/grpc-1.30.0/src/core/lib/iomgr/timer_manager.cc:326
#3 0x00007fdbc236ab59 in grpc_timer_manager_set_threading (threaded=false) at /build/grpc-1.30.0/src/core/lib/iomgr/timer_manager.cc:349
#4 0x00007fdbc2353b88 in grpc_prefork () at /build/grpc-1.30.0/src/core/lib/iomgr/fork_posix.cc:80
#5 0x00007fdbc979e6bc in fork () from /lib64/libc.so.6
```

If we kill the PHP processes, they start working again and after an hour or two we get the same situation - lots of deadlocked PHP processes.
And if we remove GRPC from the configuration, the problem also disappears, so GRPC somehow causes it for sure.

GDB showed that g_thread_count is 1, while there are no threads except for the waiting one. 
It's waiting on conditional variable which is signaled when all threads exit, but no threads are running.
That looked weird.

We've been trying to find a reproduce case for days running different scripts with fork(), exec() and whatnot, but no luck.

At the same time we noticed a strange issue with cron itself - it appears that cron refused to run additional processes with an obscure error message ""Resource temporarily unavailable"". That was the clue.

So after an extensive debugging and digging all over the system we found the culprit - it was a combination of cgroup pids.max limit in /sys/fs/cgroup/pids/system.slice/cron.service/pids.max and GRPC.

For some reason we had quite low pid.max limit: only 512 (don't ask, it's still being investigated) and this number appears to limit ""tasks"", which include processes and threads ([see here](https://www.kernel.org/doc/Documentation/cgroup-v1/pids.txt)).
Because of that system did not allow cron to run new processes _and threads_ after reaching 512 of them in total.
It was working fine until we've added grpc extension to PHP - it added additional thread ran by GRPC core - the timer_thread, so the number of ""tasks"" doubled and we started to hit the limit.

Here comes the interesting part:
GRPC core implements an abstraction class Thread that is supposed to hide all the implementation details of POSIX and Win32 threads. Unfortunately, it also hides pthread_create() result - [nothing is returned](https://github.com/grpc/grpc/blob/master/src/core/lib/gprpp/thd_posix.cc#L164), there are [no error messages](https://github.com/grpc/grpc/blob/master/src/core/lib/gprpp/thd_posix.cc#L150) or any kind of indication that the thread has failed to start.

So here is what happened:
1) we've come close to the limit of 512 threads + processes
2) a PHP process loaded GRPC extension, which initialized GRPC core, which in turn called [start_timer_thread_and_unlock](https://github.com/grpc/grpc/blob/master/src/core/lib/iomgr/timer_manager.cc#L82)() 
3) start_timer_thread_and_lock() incremented g_thread_count and tried to start new thread
4) we hit the limit and the thread did not start 
5) since it's failed to start, its [cleanup function](https://github.com/grpc/grpc/blob/master/src/core/lib/iomgr/timer_manager.cc#L263) was also never executed
6) because of that g_thread_count was not decremented and remained 1
7) stop_threads() was called as a pre-fork handler, but it wasn't able to finish because g_thread_count is always 1 and there are no threads to decrement the value
8) now we're waiting indefinitely on conditional variable g_cv_shutdown, but it will never change

So first of all, apparently, the issue was caused by the cgroup (mis)configuration, but I do believe it's also wrong that GRPC core does not check the result of pthread_create() and just assumes it always succeeds.

Moving g_thread_count++ into timer_thread() itself looks like an easy quick-fix, but I haven't tried it myself and there might be other problems caused by the inability to spawn threads, so I guess changing the core to return the result of pthread_create() and checking it before incrementing the g_thread_count is the right way to fix it.

In addition, it looks like issues #11711 and #10658 could have been caused by similar misconfiguration + GRPC combinations.",0,mysterious deadlock in stop threads   from timer manager cc  explained    we re using the latest available version of php grpc extension         on linux servers  gcc is quite new    probably  it doesn t really matter in this case     we have quite a lot of servers running php scripts and some of these scripts are ran from crontab  i e  a regular cronjob starts a launcher script that forks  yes  forks  to process some jobs     we don t really use grpc extension  yet   but after enabling the extension in php ini we ve noticed that some of the servers are hanging up   the number of php processes builds up and they appear to be stuck somewhere in grpc internals with the following backtrace          in pthread cond wait  glibc          from    libpthread so     gdb  bt       in pthread cond wait  glibc          from    libpthread so         in gpr cv wait  cv      mu      abs deadline          at  build grpc       src core lib gpr sync posix cc         in stop threads    at  build grpc       src core lib iomgr timer manager cc         in grpc timer manager set threading  threaded false  at  build grpc       src core lib iomgr timer manager cc         in grpc prefork    at  build grpc       src core lib iomgr fork posix cc         in fork    from    libc so           if we kill the php processes  they start working again and after an hour or two we get the same situation   lots of deadlocked php processes   and if we remove grpc from the configuration  the problem also disappears  so grpc somehow causes it for sure     gdb showed that g thread count is    while there are no threads except for the waiting one    it s waiting on conditional variable which is signaled when all threads exit  but no threads are running   that looked weird     we ve been trying to find a reproduce case for days running different scripts with fork    exec   and whatnot  but no luck     at the same time we noticed a strange issue with cron itself   it appears that cron refused to run additional processes with an obscure error message  resource temporarily unavailable   that was the clue     so after an extensive debugging and digging all over the system we found the culprit   it was a combination of cgroup pids max limit in  sys fs cgroup pids system slice cron service pids max and grpc     for some reason we had quite low pid max limit  only    don t ask  it s still being investigated  and this number appears to limit  tasks   which include processes and threads       because of that system did not allow cron to run new processes  and threads  after reaching   of them in total   it was working fine until we ve added grpc extension to php   it added additional thread ran by grpc core   the timer thread  so the number of  tasks  doubled and we started to hit the limit     here comes the interesting part   grpc core implements an abstraction class thread that is supposed to hide all the implementation details of posix and   threads  unfortunately  it also hides pthread create   result       there are     or any kind of indication that the thread has failed to start     so here is what happened      we ve come close to the limit of   threads   processes     a php process loaded grpc extension  which initialized grpc core  which in turn called          start timer thread and lock   incremented g thread count and tried to start new thread     we hit the limit and the thread did not start      since it s failed to start  its     was also never executed     because of that g thread count was not decremented and remained       stop threads   was called as a pre fork handler  but it wasn t able to finish because g thread count is always   and there are no threads to decrement the value     now we re waiting indefinitely on conditional variable g cv shutdown  but it will never change    so first of all  apparently  the issue was caused by the cgroup  mis configuration  but i do believe it s also wrong that grpc core does not check the result of pthread create   and just assumes it always succeeds     moving g thread count   into timer thread   itself looks like an easy quick fix  but i haven t tried it myself and there might be other problems caused by the inability to spawn threads  so i guess changing the core to return the result of pthread create   and checking it before incrementing the g thread count is the right way to fix it     in addition  it looks like issues    and    could have been caused by similar misconfiguration   grpc combinations ,0
33114,6156817559.0,IssuesEvent,2017-06-28 17:34:19,golang/go,https://api.github.com/repos/golang/go,closed,spec: grammar mistake,Documentation,"> If map entries are created during iteration, that entry may be produced during the iteration or may be skipped.

`map entries are` should be `a map entry is`.",1.0,"spec: grammar mistake - > If map entries are created during iteration, that entry may be produced during the iteration or may be skipped.

`map entries are` should be `a map entry is`.",1,spec  grammar mistake     if map entries are created during iteration  that entry may be produced during the iteration or may be skipped      map entries are  should be  a map entry is  ,1
59640,24845045432.0,IssuesEvent,2022-10-26 15:16:41,hashicorp/terraform-provider-aws,https://api.github.com/repos/hashicorp/terraform-provider-aws,reopened,ISO partition does not support aws_instance disableApiStop argument,bug service/ec2 partition/aws-iso partition/aws-iso-b,"### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave ""+1"" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

<!--- Thank you for keeping this note for the community --->

Relates #18593

### Terraform CLI and Terraform AWS Provider Version

Terraform CLI 1.2.4
Terraform AWS Provider 4.24.0

### Affected Resource(s)

* aws_instance

### Expected Behavior

No error when running `terraform plan` in the ISO partition.

### Actual Behavior

When running `terraform plan` in a region not supporting the `disableApiStop` argument.
```
Error: reading EC2 Instance (redacted) attribute: InvalidParameterValue: Value (disableApiStop) for parameter attribute is invalid. Unknown attribute
```

### Steps to Reproduce

Run `terraform plan` in an environment with an existing `aws_instance` resource in a region not supporting `disableApiStop` (for example `us-isob-east-1` )

### Important Factoids

It looks like support for the `disableApiStop` argument was added in 4.20.0 for all regions, however not all regions have this new feature implemented. For example the ISO partition does not support this new feature.
Reference PR: https://github.com/hashicorp/terraform-provider-aws/pull/25185
",1.0,"ISO partition does not support aws_instance disableApiStop argument - ### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave ""+1"" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

<!--- Thank you for keeping this note for the community --->

Relates #18593

### Terraform CLI and Terraform AWS Provider Version

Terraform CLI 1.2.4
Terraform AWS Provider 4.24.0

### Affected Resource(s)

* aws_instance

### Expected Behavior

No error when running `terraform plan` in the ISO partition.

### Actual Behavior

When running `terraform plan` in a region not supporting the `disableApiStop` argument.
```
Error: reading EC2 Instance (redacted) attribute: InvalidParameterValue: Value (disableApiStop) for parameter attribute is invalid. Unknown attribute
```

### Steps to Reproduce

Run `terraform plan` in an environment with an existing `aws_instance` resource in a region not supporting `disableApiStop` (for example `us-isob-east-1` )

### Important Factoids

It looks like support for the `disableApiStop` argument was added in 4.20.0 for all regions, however not all regions have this new feature implemented. For example the ISO partition does not support this new feature.
Reference PR: https://github.com/hashicorp/terraform-provider-aws/pull/25185
",0,iso partition does not support aws instance disableapistop argument       community note      please vote on this issue by adding a 👍     to the original issue to help the community and maintainers prioritize this request    please do not leave      or other comments that do not add relevant new information or questions  they generate extra noise for issue followers and do not help prioritize the request    if you are interested in working on this issue or have submitted a pull request  please leave a comment         relates           terraform cli and terraform aws provider version    terraform cli        terraform aws provider              affected resource s       aws instance        expected behavior    no error when running  terraform plan  in the iso partition         actual behavior    when running  terraform plan  in a region not supporting the  disableapistop  argument        error  reading   instance  redacted  attribute  invalidparametervalue  value  disableapistop  for parameter attribute is invalid  unknown attribute             steps to reproduce    run  terraform plan  in an environment with an existing  aws instance  resource in a region not supporting  disableapistop   for example  us isob east             important factoids    it looks like support for the  disableapistop  argument was added in       for all regions  however not all regions have this new feature implemented  for example the iso partition does not support this new feature   reference pr     ,0
32817,6122530265.0,IssuesEvent,2017-06-23 00:10:31,golang/go,https://api.github.com/repos/golang/go,closed,net: Is net.IP.IsUnspecified() not specific enough?,Documentation,"### What version of Go are you using (`go version`)?

go version go1.8 darwin/amd64

But it's been this way for a long time.

### What operating system and processor architecture are you using (`go env`)?

darwin_amd64 but all architectures.

### What did you do?

Called net.IP.IsUnspecified() with an unassigned net.IP struct

If possible, provide a recipe for reproducing the error.

https://play.golang.org/p/GHc6PatP8i

### What did you expect to see?

I expect any net.IP struct that does not contain a valid ipv4 or ipv6 address to be ""unspecified"".

### What did you see instead?

IP structs that are neither ipv4 or ipv6 are accepted as ""specified"".

I think IsUnspecified() should check that the IP is a valid v4 or v6 length before testing against their respective zero values. The playground link show an implementation of IsUnspecified() that I think has more precise semantics.",1.0,"net: Is net.IP.IsUnspecified() not specific enough? - ### What version of Go are you using (`go version`)?

go version go1.8 darwin/amd64

But it's been this way for a long time.

### What operating system and processor architecture are you using (`go env`)?

darwin_amd64 but all architectures.

### What did you do?

Called net.IP.IsUnspecified() with an unassigned net.IP struct

If possible, provide a recipe for reproducing the error.

https://play.golang.org/p/GHc6PatP8i

### What did you expect to see?

I expect any net.IP struct that does not contain a valid ipv4 or ipv6 address to be ""unspecified"".

### What did you see instead?

IP structs that are neither ipv4 or ipv6 are accepted as ""specified"".

I think IsUnspecified() should check that the IP is a valid v4 or v6 length before testing against their respective zero values. The playground link show an implementation of IsUnspecified() that I think has more precise semantics.",1,net  is net ip isunspecified   not specific enough        what version of go are you using   go version       go version     darwin      but it s been this way for a long time         what operating system and processor architecture are you using   go env       darwin   but all architectures         what did you do     called net ip isunspecified   with an unassigned net ip struct    if possible  provide a recipe for reproducing the error              what did you expect to see     i expect any net ip struct that does not contain a valid   or   address to be  unspecified          what did you see instead     ip structs that are neither   or   are accepted as  specified      i think isunspecified   should check that the ip is a valid   or   length before testing against their respective zero values  the playground link show an implementation of isunspecified   that i think has more precise semantics ,1
144999,5556874071.0,IssuesEvent,2017-03-24 10:23:29,RetroWoW/RetroWoW,https://api.github.com/repos/RetroWoW/RetroWoW,closed,Soulfire doesn't appear to ever stun w/Pyroclasm,Class - Warlock Mechanics Priority - High,"**Description**: Several weeks of gameplay has not yielded a single Soulfire stun.  Possibly not working correctly.  Other warlocks have also mentioned that they have never seen a stun with 2/2 talents (25% chance to stun).

**Current behaviour**: The % chance to stun never appears to occur

**Expected behaviour**: Spells like soulfire should infrequently stun their target.

**Steps to reproduce the problem**:
N/A

**Source:**
N/A",1.0,"Soulfire doesn't appear to ever stun w/Pyroclasm - **Description**: Several weeks of gameplay has not yielded a single Soulfire stun.  Possibly not working correctly.  Other warlocks have also mentioned that they have never seen a stun with 2/2 talents (25% chance to stun).

**Current behaviour**: The % chance to stun never appears to occur

**Expected behaviour**: Spells like soulfire should infrequently stun their target.

**Steps to reproduce the problem**:
N/A

**Source:**
N/A",0,soulfire doesn t appear to ever stun w pyroclasm     description    several weeks of gameplay has not yielded a single soulfire stun   possibly not working correctly   other warlocks have also mentioned that they have never seen a stun with     talents     chance to stun        current behaviour    the   chance to stun never appears to occur      expected behaviour    spells like soulfire should infrequently stun their target       steps to reproduce the problem     n a      source     n a,0
385257,26627505520.0,IssuesEvent,2023-01-24 15:30:33,golang/go,https://api.github.com/repos/golang/go,closed,"x/website: Fuzzing documentation image has transparent background, works poorly with dark mode",Documentation NeedsFix website,"The fuzzing page, https://tip.golang.org/security/fuzz/, has an image describing different components involved. It however has a transparent background, and with the page supporting dark mode, the image gets very tricky to read:
![image](https://user-images.githubusercontent.com/214867/189207556-9c10f2e7-894a-4b8c-be87-678fb45a21a9.png)

I'm not sure if having a opaque white background would be problematic, but that seems to be the easiest solution.",1.0,"x/website: Fuzzing documentation image has transparent background, works poorly with dark mode - The fuzzing page, https://tip.golang.org/security/fuzz/, has an image describing different components involved. It however has a transparent background, and with the page supporting dark mode, the image gets very tricky to read:
![image](https://user-images.githubusercontent.com/214867/189207556-9c10f2e7-894a-4b8c-be87-678fb45a21a9.png)

I'm not sure if having a opaque white background would be problematic, but that seems to be the easiest solution.",1,x website  fuzzing documentation image has transparent background  works poorly with dark mode   the fuzzing page    has an image describing different components involved  it however has a transparent background  and with the page supporting dark mode  the image gets very tricky to read           i m not sure if having a opaque white background would be problematic  but that seems to be the easiest solution ,1
21720,6208826359.0,IssuesEvent,2017-07-07 01:24:14,ahmedahamid/test,https://api.github.com/repos/ahmedahamid/test,closed,Need Component for Source Code tab.,bug CodePlexMigrationInitiated impact: Medium Souce Code,"Can't enter issues in Issue Tracker for the Source Code tab because it is not a listed Component.


#### Migrated CodePlex Work Item Details
CodePlex Work Item ID: '454'
Vote count: '0'
",2.0,"Need Component for Source Code tab. - Can't enter issues in Issue Tracker for the Source Code tab because it is not a listed Component.


#### Migrated CodePlex Work Item Details
CodePlex Work Item ID: '454'
Vote count: '0'
",0,need component for source code tab    can t enter issues in issue tracker for the source code tab because it is not a listed component           migrated codeplex work item details  codeplex work item id       vote count       ,0
600973,18362624414.0,IssuesEvent,2021-10-09 13:43:46,GoogleCloudPlatform/python-docs-samples,https://api.github.com/repos/GoogleCloudPlatform/python-docs-samples,reopened,storage.cloud-client.iam_test: test_view_bucket_iam_members failed,priority: p1 type: bug api: storage samples flakybot: issue flakybot: flaky,"Note: #6395 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.

----

commit: 84d7cb58a5b088fb347ff46792c3b949551aed6c
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/4fa3ce12-f910-409e-8a0e-542d60dc928a), [Sponge](http://sponge2/4fa3ce12-f910-409e-8a0e-542d60dc928a)
status: failed
<details><summary>Test output</summary><br><pre>Traceback (most recent call last):
  File ""/workspace/storage/cloud-client/iam_test.py"", line 48, in bucket
    storage_client.create_bucket(bucket)
  File ""/workspace/storage/cloud-client/.nox/py-3-10/lib/python3.10/site-packages/google/cloud/storage/client.py"", line 956, in create_bucket
    api_response = self._post_resource(
  File ""/workspace/storage/cloud-client/.nox/py-3-10/lib/python3.10/site-packages/google/cloud/storage/client.py"", line 588, in _post_resource
    return self._connection.api_request(
  File ""/workspace/storage/cloud-client/.nox/py-3-10/lib/python3.10/site-packages/google/cloud/storage/_http.py"", line 80, in api_request
    return call()
  File ""/workspace/storage/cloud-client/.nox/py-3-10/lib/python3.10/site-packages/google/api_core/retry.py"", line 283, in retry_wrapped_func
    return retry_target(
  File ""/workspace/storage/cloud-client/.nox/py-3-10/lib/python3.10/site-packages/google/api_core/retry.py"", line 190, in retry_target
    return target()
  File ""/workspace/storage/cloud-client/.nox/py-3-10/lib/python3.10/site-packages/google/cloud/_http.py"", line 479, in api_request
    raise exceptions.from_http_response(response)
google.api_core.exceptions.BadRequest: 400 POST https://storage.googleapis.com/storage/v1/b?project=python-docs-samples-tests-py310&prettyPrint=false: Unknown project id: python-docs-samples-tests-py310</pre></details>",1.0,"storage.cloud-client.iam_test: test_view_bucket_iam_members failed - Note: #6395 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.

----

commit: 84d7cb58a5b088fb347ff46792c3b949551aed6c
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/4fa3ce12-f910-409e-8a0e-542d60dc928a), [Sponge](http://sponge2/4fa3ce12-f910-409e-8a0e-542d60dc928a)
status: failed
<details><summary>Test output</summary><br><pre>Traceback (most recent call last):
  File ""/workspace/storage/cloud-client/iam_test.py"", line 48, in bucket
    storage_client.create_bucket(bucket)
  File ""/workspace/storage/cloud-client/.nox/py-3-10/lib/python3.10/site-packages/google/cloud/storage/client.py"", line 956, in create_bucket
    api_response = self._post_resource(
  File ""/workspace/storage/cloud-client/.nox/py-3-10/lib/python3.10/site-packages/google/cloud/storage/client.py"", line 588, in _post_resource
    return self._connection.api_request(
  File ""/workspace/storage/cloud-client/.nox/py-3-10/lib/python3.10/site-packages/google/cloud/storage/_http.py"", line 80, in api_request
    return call()
  File ""/workspace/storage/cloud-client/.nox/py-3-10/lib/python3.10/site-packages/google/api_core/retry.py"", line 283, in retry_wrapped_func
    return retry_target(
  File ""/workspace/storage/cloud-client/.nox/py-3-10/lib/python3.10/site-packages/google/api_core/retry.py"", line 190, in retry_target
    return target()
  File ""/workspace/storage/cloud-client/.nox/py-3-10/lib/python3.10/site-packages/google/cloud/_http.py"", line 479, in api_request
    raise exceptions.from_http_response(response)
google.api_core.exceptions.BadRequest: 400 POST https://storage.googleapis.com/storage/v1/b?project=python-docs-samples-tests-py310&prettyPrint=false: Unknown project id: python-docs-samples-tests-py310</pre></details>",0,storage cloud client iam test  test view bucket iam members 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   traceback  most recent call last     file   workspace storage cloud client iam test py   line    in bucket     storage client create bucket bucket    file   workspace storage cloud client  nox py     lib     site packages google cloud storage client py   line    in create bucket     api response   self  post resource    file   workspace storage cloud client  nox py     lib     site packages google cloud storage client py   line    in  post resource     return self  connection api request    file   workspace storage cloud client  nox py     lib     site packages google cloud storage  http py   line    in api request     return call     file   workspace storage cloud client  nox py     lib     site packages google api core retry py   line    in retry wrapped func     return retry target    file   workspace storage cloud client  nox py     lib     site packages google api core retry py   line    in retry target     return target     file   workspace storage cloud client  nox py     lib     site packages google cloud  http py   line    in api request     raise exceptions from http response response  google api core exceptions badrequest    post   unknown project id  python docs samples tests    ,0
308363,23245230291.0,IssuesEvent,2022-08-03 19:26:36,golang/go,https://api.github.com/repos/golang/go,closed,cmd/asm: document `-p` option in help text,Documentation NeedsInvestigation compiler/runtime,"### What version of Go are you using (`go version`)?

Go v1.19

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

Not relevant since issue is with help text.

### What did you do?

`go doc cmd/asm`

### What did you expect to see?

I expected to see help text for the new `-p` option.

### What did you see instead?

The help text does not include the new `-p` option.
",1.0,"cmd/asm: document `-p` option in help text - ### What version of Go are you using (`go version`)?

Go v1.19

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

Not relevant since issue is with help text.

### What did you do?

`go doc cmd/asm`

### What did you expect to see?

I expected to see help text for the new `-p` option.

### What did you see instead?

The help text does not include the new `-p` option.
",1,cmd asm  document   p  option in help text       what version of go are you using   go version       go            does this issue reproduce with the latest release     yes         what operating system and processor architecture are you using   go env       not relevant since issue is with help text         what did you do      go doc cmd asm         what did you expect to see     i expected to see help text for the new   p  option         what did you see instead     the help text does not include the new   p  option   ,1
11030,7396368695.0,IssuesEvent,2018-03-18 11:36:55,Shougo/deoplete.nvim,https://api.github.com/repos/Shougo/deoplete.nvim,closed,neovim-python asyncio support,enhancement performance,"It is still WIP.
~~I will create the branch later.~~

~~https://gist.github.com/Shougo/b1292a539dcf7058c5e22b253fd46339~~

It fixes #645 and #671.
It may fix other problems.
It improves the completion performance.

Note: neovim-python 0.2.3+ is needed.
It does not work in Windows(due to neovim-python problem).

It also supports Vim8.",True,"neovim-python asyncio support - It is still WIP.
~~I will create the branch later.~~

~~https://gist.github.com/Shougo/b1292a539dcf7058c5e22b253fd46339~~

It fixes #645 and #671.
It may fix other problems.
It improves the completion performance.

Note: neovim-python 0.2.3+ is needed.
It does not work in Windows(due to neovim-python problem).

It also supports Vim8.",0,neovim python asyncio support   it is still wip     i will create the branch later              it fixes    and      it may fix other problems   it improves the completion performance     note  neovim python        is needed   it does not work in windows due to neovim python problem      it also supports   ,0
71019,30788900079.0,IssuesEvent,2023-07-31 14:53:27,Ocelot-Social-Community/Ocelot-Social,https://api.github.com/repos/Ocelot-Social-Community/Ocelot-Social,closed,🔧 [Refactor][Frontend] Filter menu optimisation,service: webapp,"## 🔧 Refactor issue
For the events the most important filter is the content type so we need it at the start of the filters.
The all button of topics should also be a square like the topics
Add headline for ""Users I follow"" / ""My Groups"" EN: Sources / DE: Quellen
![image](https://github.com/Ocelot-Social-Community/Ocelot-Social/assets/33051975/834d87d6-7eea-4fc3-bfe3-9a6f1a878932)

## 🤖 ToDos:
Filter Menu

- [x] Filter menu content type as first
- [x] Filter menu „All“ button for topic shown as square
- [x] Filter menu remove hr line
- [x] Filter menu 2nd headline EN: Sources / DE: Quellen
- [x] Filter menu ""Users I follow"" and ""My groups"" as square
- [x] Filter menu ""Nutzer, denn ich folge"", ""meine Gruppen""
- [x] Filter menu ""Zukünftige"" statt ""nicht beendete""

Filter Buttons

- [x] Filter button remove text EN:""Only"" / DE:""Nur""
- [x] Filter button Text: ""Inhalt filtern"" should be ""Inhalte filtern""",1.0,"🔧 [Refactor][Frontend] Filter menu optimisation - ## 🔧 Refactor issue
For the events the most important filter is the content type so we need it at the start of the filters.
The all button of topics should also be a square like the topics
Add headline for ""Users I follow"" / ""My Groups"" EN: Sources / DE: Quellen
![image](https://github.com/Ocelot-Social-Community/Ocelot-Social/assets/33051975/834d87d6-7eea-4fc3-bfe3-9a6f1a878932)

## 🤖 ToDos:
Filter Menu

- [x] Filter menu content type as first
- [x] Filter menu „All“ button for topic shown as square
- [x] Filter menu remove hr line
- [x] Filter menu 2nd headline EN: Sources / DE: Quellen
- [x] Filter menu ""Users I follow"" and ""My groups"" as square
- [x] Filter menu ""Nutzer, denn ich folge"", ""meine Gruppen""
- [x] Filter menu ""Zukünftige"" statt ""nicht beendete""

Filter Buttons

- [x] Filter button remove text EN:""Only"" / DE:""Nur""
- [x] Filter button Text: ""Inhalt filtern"" should be ""Inhalte filtern""",0,🔧    filter menu optimisation      🔧 refactor issue  for the events the most important filter is the content type so we need it at the start of the filters   the all button of topics should also be a square like the topics  add headline for  users i follow     my groups  en  sources   de  quellen             🤖 todos   filter menu        filter menu content type as first      filter menu „all“ button for topic shown as square      filter menu remove hr line      filter menu   headline en  sources   de  quellen      filter menu  users i follow  and  my groups  as square      filter menu  nutzer  denn ich folge    meine gruppen       filter menu  zukünftige  statt  nicht beendete     filter buttons        filter button remove text en  only    de  nur       filter button text   inhalt filtern  should be  inhalte filtern ,0
174074,6536271682.0,IssuesEvent,2017-08-31 17:29:40,pmem/pmemkv,https://api.github.com/repos/pmem/pmemkv,closed,Document use of poolset file,Priority: 1 showstopper Type: Validation,"Passing a xxx.set file to pmemkv appears to work ok, add to README",1.0,"Document use of poolset file - Passing a xxx.set file to pmemkv appears to work ok, add to README",0,document use of poolset file   passing a xxx set file to pmemkv appears to work ok  add to readme,0
26167,5229247730.0,IssuesEvent,2017-01-29 00:50:14,golang/go,https://api.github.com/repos/golang/go,closed,database/sql: update 1.8 release notes,Documentation,"### What version of Go are you using (`go version`)?
1.8rc3

### What operating system and processor architecture are you using (`go env`)?
N/A

### What did you do?
https://beta.golang.org/doc/go1.8#database_sql

### What did you expect to see?
Documentation mentioning `DB.BeginTx()`.

### What did you see instead?
Documentation mentioning non-existant `DB.BeginContext()`. Probably forgot to update documentation as part of #18284.

",1.0,"database/sql: update 1.8 release notes - ### What version of Go are you using (`go version`)?
1.8rc3

### What operating system and processor architecture are you using (`go env`)?
N/A

### What did you do?
https://beta.golang.org/doc/go1.8#database_sql

### What did you expect to see?
Documentation mentioning `DB.BeginTx()`.

### What did you see instead?
Documentation mentioning non-existant `DB.BeginContext()`. Probably forgot to update documentation as part of #18284.

",1,database sql  update     release notes       what version of go are you using   go version                what operating system and processor architecture are you using   go env     n a        what did you do            what did you expect to see   documentation mentioning  db begintx            what did you see instead   documentation mentioning non existant  db begincontext     probably forgot to update documentation as part of        ,1
11219,2641932983.0,IssuesEvent,2015-03-11 20:36:05,chrsmith/html5rocks,https://api.github.com/repos/chrsmith/html5rocks,closed,Resources to add,Milestone-3 Priority-Medium Tutorial Type-Defect,"Original [issue 129](https://code.google.com/p/html5rocks/issues/detail?id=129) created by chrsmith on 2010-08-03T21:54:42.000Z:

drag n drop debugging: http://feiss.be/tmp/dnd_debug/ - might be better for a tutorial link",1.0,"Resources to add - Original [issue 129](https://code.google.com/p/html5rocks/issues/detail?id=129) created by chrsmith on 2010-08-03T21:54:42.000Z:

drag n drop debugging: http://feiss.be/tmp/dnd_debug/ - might be better for a tutorial link",0,resources to add   original     created by chrsmith on               drag n drop debugging      might be better for a tutorial link,0
29102,8288340599.0,IssuesEvent,2018-09-19 11:41:45,hashicorp/packer,https://api.github.com/repos/hashicorp/packer,closed,Amazon EBS Builder's Temporary Security Group is open to 0.0.0.0/0,builder/amazon wontfix,"Packer Version: 1.2.0
Host Platform: Ubuntu
Builder: Amazon AWS

I realize it's a temporary instance; but still - Would be much better to just tie this to the public IP of whatever instance the host is; rather than opening it to 0.0.0.0/0

I just had my automated security rule go off from Cloud Custodian stating that an open security group was created. Would actually be a nuisance once we setup automation to delete these security groups immediately when created.

  
",1.0,"Amazon EBS Builder's Temporary Security Group is open to 0.0.0.0/0 - Packer Version: 1.2.0
Host Platform: Ubuntu
Builder: Amazon AWS

I realize it's a temporary instance; but still - Would be much better to just tie this to the public IP of whatever instance the host is; rather than opening it to 0.0.0.0/0

I just had my automated security rule go off from Cloud Custodian stating that an open security group was created. Would actually be a nuisance once we setup automation to delete these security groups immediately when created.

  
",0,amazon ebs builder s temporary security group is open to             packer version         host platform  ubuntu  builder  amazon aws    i realize it s a temporary instance  but still   would be much better to just tie this to the public ip of whatever instance the host is  rather than opening it to              i just had my automated security rule go off from cloud custodian stating that an open security group was created  would actually be a nuisance once we setup automation to delete these security groups immediately when created         ,0
11952,3551159551.0,IssuesEvent,2016-01-21 01:35:29,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: go list documentation of the struct passed to template is incomplete,Documentation,"The go list --help command documents the struct passed to the template.
However the Package struct Error and DepsError fields have type PackageError, and this type is not documented.",1.0,"cmd/go: go list documentation of the struct passed to template is incomplete - The go list --help command documents the struct passed to the template.
However the Package struct Error and DepsError fields have type PackageError, and this type is not documented.",1,cmd go  go list documentation of the struct passed to template is incomplete   the go list   help command documents the struct passed to the template   however the package struct error and depserror fields have type packageerror  and this type is not documented ,1
32465,6065821522.0,IssuesEvent,2017-06-14 17:04:01,golang/go,https://api.github.com/repos/golang/go,closed,doc: contribute.html is long and wordy,Documentation NeedsFix,"Tracking bug for making the contribution process seem less intimidating, forked from #17794.

Observations:

* contribute.html is long and wordy. It might be good for some users, but it scares other users.

Maybe we need a high-level summary at the top showing the brief steps, with links to more info, rather than making users read a book first.

Also, I had an idea to write a go-gettable tool to walk people through the contribution process step-by-step, inspecting their httpcookies (for Gerrit), CLA state, git config, git-codereview, etc, and telling them what to do next. I want the instructions for contributors to just be:

```
$ go get go4.org/tools/gocontribute
$ gocontribute
```

And then the tool would say what needs to be done next.

/cc @quentinmit @robmccoll

",1.0,"doc: contribute.html is long and wordy - Tracking bug for making the contribution process seem less intimidating, forked from #17794.

Observations:

* contribute.html is long and wordy. It might be good for some users, but it scares other users.

Maybe we need a high-level summary at the top showing the brief steps, with links to more info, rather than making users read a book first.

Also, I had an idea to write a go-gettable tool to walk people through the contribution process step-by-step, inspecting their httpcookies (for Gerrit), CLA state, git config, git-codereview, etc, and telling them what to do next. I want the instructions for contributors to just be:

```
$ go get go4.org/tools/gocontribute
$ gocontribute
```

And then the tool would say what needs to be done next.

/cc @quentinmit @robmccoll

",1,doc  contribute html is long and wordy   tracking bug for making the contribution process seem less intimidating  forked from        observations       contribute html is long and wordy  it might be good for some users  but it scares other users     maybe we need a high level summary at the top showing the brief steps  with links to more info  rather than making users read a book first     also  i had an idea to write a go gettable tool to walk people through the contribution process step by step  inspecting their httpcookies  for gerrit   cla state  git config  git codereview  etc  and telling them what to do next  i want the instructions for contributors to just be            go get   org tools gocontribute    gocontribute         and then the tool would say what needs to be done next      cc  quentinmit  robmccoll    ,1
211781,16458122443.0,IssuesEvent,2021-05-21 15:04:47,golang/go,https://api.github.com/repos/golang/go,opened,net/http/pprof: add note about security implications to the docs,Documentation Security,"The net/http/pprof endpoints include stack traces with integer arguments, which can leak sensitive information depending on the settings. We should mention that in the docs.",1.0,"net/http/pprof: add note about security implications to the docs - The net/http/pprof endpoints include stack traces with integer arguments, which can leak sensitive information depending on the settings. We should mention that in the docs.",1,net http pprof  add note about security implications to the docs   the net http pprof endpoints include stack traces with integer arguments  which can leak sensitive information depending on the settings  we should mention that in the docs ,1
120215,12061456437.0,IssuesEvent,2020-04-15 23:51:39,golang/go,https://api.github.com/repos/golang/go,closed,Need for Improvements on Documentation of io.Copy,Documentation WaitingForInfo,"Hey Guys, Recently I've been studying a lot about system calls and I noticed that The standard library uses many of then to increase performance, like on io.Copy when if Reader is a file, Writer a TCPConn and the OS is linux, freebsd or windows, it uses sendfile or splice. Another example is this issue to be implemented https://github.com/golang/go/issues/36817.

But I feel these different paths are not clear enough on documentation. Example:
On io.Copy:
https://github.com/golang/go/blob/34e38ac99f025549599ea7e1ad2e80026ae16174/src/io/io.go#L363-L367
On net.TCPConn.ReadFrom:
https://github.com/golang/go/blob/34e38ac99f025549599ea7e1ad2e80026ae16174/src/net/tcpsock.go#L98-L99

If the programmer doesn't read all the code, he never will realize what the code is doing. Like he will never know that his solution isn't copying the file to userspace but it's just sending from page cache to socket.

I would like to know if we can describe these cases on io.Copy comments or create a wiki about this topic? What is the best approach to spread this knowledge?

Thanks a lot :) and it's my first issue on this project, if I've done something wrong let me know ;)",1.0,"Need for Improvements on Documentation of io.Copy - Hey Guys, Recently I've been studying a lot about system calls and I noticed that The standard library uses many of then to increase performance, like on io.Copy when if Reader is a file, Writer a TCPConn and the OS is linux, freebsd or windows, it uses sendfile or splice. Another example is this issue to be implemented https://github.com/golang/go/issues/36817.

But I feel these different paths are not clear enough on documentation. Example:
On io.Copy:
https://github.com/golang/go/blob/34e38ac99f025549599ea7e1ad2e80026ae16174/src/io/io.go#L363-L367
On net.TCPConn.ReadFrom:
https://github.com/golang/go/blob/34e38ac99f025549599ea7e1ad2e80026ae16174/src/net/tcpsock.go#L98-L99

If the programmer doesn't read all the code, he never will realize what the code is doing. Like he will never know that his solution isn't copying the file to userspace but it's just sending from page cache to socket.

I would like to know if we can describe these cases on io.Copy comments or create a wiki about this topic? What is the best approach to spread this knowledge?

Thanks a lot :) and it's my first issue on this project, if I've done something wrong let me know ;)",1,need for improvements on documentation of io copy   hey guys  recently i ve been studying a lot about system calls and i noticed that the standard library uses many of then to increase performance  like on io copy when if reader is a file  writer a tcpconn and the os is linux  freebsd or windows  it uses sendfile or splice  another example is this issue to be implemented      but i feel these different paths are not clear enough on documentation  example   on io copy      on net tcpconn readfrom        if the programmer doesn t read all the code  he never will realize what the code is doing  like he will never know that his solution isn t copying the file to userspace but it s just sending from page cache to socket     i would like to know if we can describe these cases on io copy comments or create a wiki about this topic  what is the best approach to spread this knowledge     thanks a lot    and it s my first issue on this project  if i ve done something wrong let me know   ,1
86739,10515961460.0,IssuesEvent,2019-09-28 14:04:15,golang/go,https://api.github.com/repos/golang/go,opened,x/tour: welcome/3 slide missing instructions for installing Go,Documentation NeedsFix,"The first slide of the tour welcomes people and explains how to change slides. The second slide mentions the choice of spoken languages. The third slide strongly suggests running the tour offline.

By the [third slide](https://tour.golang.org/welcome/3), the tour assumes users already have Go installed (and/or know how to install Go). This isn't valid for users who are being introduced to Go by being linked to the tour. It can cause unnecessary confusion as demonstrated by the experience reported in [this comment](https://github.com/golang/go/issues/24819#issuecomment-487723046).

That slide used to have instructions for installing Go, but they were lost as part of deployment changes in [CL 141857](https://golang.org/cl/141857). /cc @andybons

To fix this, we should include a link to https://golang.org/doc/install and/or https://golang.org/dl/ before the first mention of `go get` in the tour. It should also be helpful and a good teaching opportunity to point out where the `tour` binary ends up after `go get` runs successfully.

This issue is factored out from #24819, which was about a formatting bug that is resolved by now.",1.0,"x/tour: welcome/3 slide missing instructions for installing Go - The first slide of the tour welcomes people and explains how to change slides. The second slide mentions the choice of spoken languages. The third slide strongly suggests running the tour offline.

By the [third slide](https://tour.golang.org/welcome/3), the tour assumes users already have Go installed (and/or know how to install Go). This isn't valid for users who are being introduced to Go by being linked to the tour. It can cause unnecessary confusion as demonstrated by the experience reported in [this comment](https://github.com/golang/go/issues/24819#issuecomment-487723046).

That slide used to have instructions for installing Go, but they were lost as part of deployment changes in [CL 141857](https://golang.org/cl/141857). /cc @andybons

To fix this, we should include a link to https://golang.org/doc/install and/or https://golang.org/dl/ before the first mention of `go get` in the tour. It should also be helpful and a good teaching opportunity to point out where the `tour` binary ends up after `go get` runs successfully.

This issue is factored out from #24819, which was about a formatting bug that is resolved by now.",1,x tour  welcome   slide missing instructions for installing go   the first slide of the tour welcomes people and explains how to change slides  the second slide mentions the choice of spoken languages  the third slide strongly suggests running the tour offline     by the     the tour assumes users already have go installed  and or know how to install go   this isn t valid for users who are being introduced to go by being linked to the tour  it can cause unnecessary confusion as demonstrated by the experience reported in        that slide used to have instructions for installing go  but they were lost as part of deployment changes in      cc  andybons    to fix this  we should include a link to   and or   before the first mention of  go get  in the tour  it should also be helpful and a good teaching opportunity to point out where the  tour  binary ends up after  go get  runs successfully     this issue is factored out from     which was about a formatting bug that is resolved by now ,1
50832,7634096312.0,IssuesEvent,2018-05-06 13:55:14,golang/go,https://api.github.com/repos/golang/go,closed,"net/http, x/net/http2: update RFC numbers used as normative references",Documentation help wanted,"The documentation in x/net/http and x/net/http2 packages still contains the obsolete RFC 2616 as a normative reference. I think it's better to replace the reference to RFC 2616 with a series of RFCs 7230 through 7235 for avoiding unnecessary confusion.

When we see some inconsistency, for example, RFC 2616 vs. RFC 723x, in the current implementation, that should be addressed as another issue. So this should be a documentation issue.",1.0,"net/http, x/net/http2: update RFC numbers used as normative references - The documentation in x/net/http and x/net/http2 packages still contains the obsolete RFC 2616 as a normative reference. I think it's better to replace the reference to RFC 2616 with a series of RFCs 7230 through 7235 for avoiding unnecessary confusion.

When we see some inconsistency, for example, RFC 2616 vs. RFC 723x, in the current implementation, that should be addressed as another issue. So this should be a documentation issue.",1,net http  x net    update rfc numbers used as normative references   the documentation in x net http and x net   packages still contains the obsolete rfc   as a normative reference  i think it s better to replace the reference to rfc   with a series of rfcs   through   for avoiding unnecessary confusion     when we see some inconsistency  for example  rfc   vs  rfc    in the current implementation  that should be addressed as another issue  so this should be a documentation issue ,1
300179,22644648211.0,IssuesEvent,2022-07-01 07:29:31,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: cover tool help command syntax does not work on Windows ,Documentation WaitingForInfo NeedsFix,"

### What version of Go are you using (`go version`)? 

<pre>
1.17.5
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?
Windows


### What did you do?

Running 'go tool cover -help' issues a help message that includes this command suggestion:

`
go tool cover -func=c.out
`

This works on the Mac and Linux, but not on Windows. On Windows it produces the following error message:

`
too many arguments
For usage information, run ""go tool cover -help""
`

The correct way to call this is:

`
go tool cover -func c.out
`

This works on all platforms.

Note that this bad usage pattern is sprinkled throughout the go ecosystem. For example, this web page: https://pkg.go.dev/cmd/cover, has this line:

`
Cover is a program for analyzing the coverage profiles generated by 'go test -coverprofile=cover.out'.
`

However, running that line in a windows cmd terminal produces:
`
no required module provides package .out; to add it: go get .out
`

Or here: https://pkg.go.dev/cmd/go#hdr-Build_constraints, it uses examples of `-buildmode=mode`, even though the documentation earlier specs it as `-buildmode mode`.

This clearly is a longstanding problem that should be easy to clean up.





",1.0,"cmd/go: cover tool help command syntax does not work on Windows  - 

### What version of Go are you using (`go version`)? 

<pre>
1.17.5
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?
Windows


### What did you do?

Running 'go tool cover -help' issues a help message that includes this command suggestion:

`
go tool cover -func=c.out
`

This works on the Mac and Linux, but not on Windows. On Windows it produces the following error message:

`
too many arguments
For usage information, run ""go tool cover -help""
`

The correct way to call this is:

`
go tool cover -func c.out
`

This works on all platforms.

Note that this bad usage pattern is sprinkled throughout the go ecosystem. For example, this web page: https://pkg.go.dev/cmd/cover, has this line:

`
Cover is a program for analyzing the coverage profiles generated by 'go test -coverprofile=cover.out'.
`

However, running that line in a windows cmd terminal produces:
`
no required module provides package .out; to add it: go get .out
`

Or here: https://pkg.go.dev/cmd/go#hdr-Build_constraints, it uses examples of `-buildmode=mode`, even though the documentation earlier specs it as `-buildmode mode`.

This clearly is a longstanding problem that should be easy to clean up.





",1,cmd go  cover tool help command syntax does not work on windows            what version of go are you using   go version                           does this issue reproduce with the latest release   yes          what operating system and processor architecture are you using   go env     windows          what did you do     running  go tool cover  help  issues a help message that includes this command suggestion        go tool cover  func c out       this works on the mac and linux  but not on windows  on windows it produces the following error message        too many arguments  for usage information  run  go tool cover  help        the correct way to call this is        go tool cover  func c out       this works on all platforms     note that this bad usage pattern is sprinkled throughout the go ecosystem  for example  this web page    has this line        cover is a program for analyzing the coverage profiles generated by  go test  coverprofile cover out         however  running that line in a windows cmd terminal produces      no required module provides package  out  to add it  go get  out       or here    it uses examples of   buildmode mode   even though the documentation earlier specs it as   buildmode mode      this clearly is a longstanding problem that should be easy to clean up             ,1
74610,9793927779.0,IssuesEvent,2019-06-10 21:13:17,golang/go,https://api.github.com/repos/golang/go,closed,"doc: Effective Go contains a use of ""named type"", which is an obsoleted terminology.",Documentation NeedsDecision,"Should it be ""defined type"" instead?

",1.0,"doc: Effective Go contains a use of ""named type"", which is an obsoleted terminology. - Should it be ""defined type"" instead?

",1,doc  effective go contains a use of  named type   which is an obsoleted terminology    should it be  defined type  instead     ,1
763325,26752470104.0,IssuesEvent,2023-01-30 20:48:52,GoogleCloudPlatform/opentelemetry-operations-java,https://api.github.com/repos/GoogleCloudPlatform/opentelemetry-operations-java,closed,Support google.devtools.cloudtrace.v2.MessageEvent,enhancement priority: p2,"I am trying to convert the trace implementation of an application from OpenCensus to OpenTelemetry.  OpenCensus has a span.addMessageEvent method/class [1] that maps directly to the Google Trace MessageEvent [1] class.  

It looks like OpenTelemetry plans to use span.addEvent for this [3].  Are there plans to support this in the exporter?

[1] https://www.javadoc.io/static/io.opencensus/opencensus-api/0.18.0/io/opencensus/trace/Span.html#addMessageEvent-io.opencensus.trace.MessageEvent-
[2] https://cloud.google.com/trace/docs/reference/v2/rpc/google.devtools.cloudtrace.v2#messageevent
[3] https://github.com/open-telemetry/opentelemetry-java/issues/13
",1.0,"Support google.devtools.cloudtrace.v2.MessageEvent - I am trying to convert the trace implementation of an application from OpenCensus to OpenTelemetry.  OpenCensus has a span.addMessageEvent method/class [1] that maps directly to the Google Trace MessageEvent [1] class.  

It looks like OpenTelemetry plans to use span.addEvent for this [3].  Are there plans to support this in the exporter?

[1] https://www.javadoc.io/static/io.opencensus/opencensus-api/0.18.0/io/opencensus/trace/Span.html#addMessageEvent-io.opencensus.trace.MessageEvent-
[2] https://cloud.google.com/trace/docs/reference/v2/rpc/google.devtools.cloudtrace.v2#messageevent
[3] https://github.com/open-telemetry/opentelemetry-java/issues/13
",0,support google devtools cloudtrace   messageevent   i am trying to convert the trace implementation of an application from opencensus to opentelemetry   opencensus has a span addmessageevent method class   that maps directly to the google trace messageevent   class       it looks like opentelemetry plans to use span addevent for this     are there plans to support this in the exporter                    ,0
369550,25856303499.0,IssuesEvent,2022-12-13 14:00:58,golang/go,https://api.github.com/repos/golang/go,closed,x/sys/unix: Undocumented (possibly incorrect?) SendmsgBuffers behavior with empty iovec,Documentation help wanted NeedsInvestigation compiler/runtime,"<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.19.3 linux/amd64
$ cat go.sum
golang.org/x/sys v0.2.0 h1:ljd4t30dBnAvMZaQCevtY0xLLD0A+bRZXbgLMLU1F/A=
golang.org/x/sys v0.2.0/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/dave/.cache/go-build""
GOENV=""/home/dave/.config/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/dave/Source/Go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/dave/Source/Go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/lib/go-1.19""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/lib/go-1.19/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""go1.19.3""
GCCGO=""gccgo""
GOAMD64=""v1""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/dave/Source/keyholder/go.mod""
GOWORK=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build1272319925=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

I'm interfacing with the Linux kernel cryptography API using the AF_ALG interface, across two processes.  One process is responsible for setting up an AF_ALG (SOCK_SEQPACKET) socket, including setting the key and IV, and then the resulting socket file descriptor is passed to another process (using SCM_RIGHTS), which uses it for encryption or decryption.  By design, the first process does not have access to any of the plaintext or ciphertext data, and the second process does not have access to the encryption key.

The bug I was encountering was seemingly an extra '\0' in the decrypted plaintext output and an off-by-one error between plaintext and expected ciphertext length.  I discovered this is because an extra byte is silently added by x/sys/unix.sendmsgN() if passed an empty Iovec but non-empty out-of-band data, on a non-SOCK_DGRAM socket:

https://cs.opensource.google/go/x/sys/+/refs/tags/v0.2.0:unix/syscall_linux.go;l=1538;drc=d684c6f886692f8b63049d3dabe4f1911ae979c3;bpv=1;bpt=1

As far as I can tell, this behavior is undocumented.  I believe some socket types require at least one byte of data with OOB, but AF_ALG sockets do not.  (The Linux kernel documentation references https://www.chronox.de/libkcapi.html as the canonical client implementation, and it follows the pattern of OOB-but-empty-data to set up the socket, and then it uses vmsplice() to send the non-OOB data.)

The following call results in the extra byte being sent to the socket (error handling and populating `var oob []byte` omitted):

```
unix.SendmsgBuffers(fd, nil, oob, nil, unix.MSG_MORE)
```

This code works as expected:

```
msg := &unix.Msghdr{
    Control: &oob[0],
    // Remaining fields, including Iov and Iovlen are zero
}
msg.SetControllen(len(oob))
unix.Syscall(unix.SYS_SENDMSG, uintptr(fd), uintptr(unsafe.Pointer(msg)), unix.MSG_MORE)
```

### What did you expect to see?

An empty [][]byte resulting in no data being sent.

The documentation for SendmsgBuffers states, ""the function returns the number of bytes written to the socket.""

### What did you see instead?

A '\0' byte being sent to the socket unexpectedly.

SendmsgBuffers returns 0, but actually sends 1 byte to the socket.

### Possible solutions/topics for discussion

The implicit extra byte with Sendmsg appears to date back to the very first Go commit, so it probably comes from Plan 9.  SendmsgBuffers is, however, relatively new (https://github.com/golang/go/issues/52885) so maybe its API/behavior is not as set in stone.  Whether or not their behavior in this regard should diverge is probably a topic for debate.

Should SOCK_SEQPACKET be treated the same as SOCK_DGRAM, and excluded from having the extra byte sent?  If so, should the socket types (maybe just SOCK_STREAM) that require special empty-iovec handling be an allowlist instead of a denylist?

Should the SendmsgBuffers return value be updated to reflect the actual number of bytes sent when passed an empty [][]byte?

Instead of silently adding an invisible byte, should an error be returned if SendmsgBuffers is not supposed to be called with an empty [][]byte?

Even if no changes to behavior are warranted, should SendmsgBuffer's documentation be improved?  (Yes, I am volunteering to do so. :))
",1.0,"x/sys/unix: Undocumented (possibly incorrect?) SendmsgBuffers behavior with empty iovec - <!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.19.3 linux/amd64
$ cat go.sum
golang.org/x/sys v0.2.0 h1:ljd4t30dBnAvMZaQCevtY0xLLD0A+bRZXbgLMLU1F/A=
golang.org/x/sys v0.2.0/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/dave/.cache/go-build""
GOENV=""/home/dave/.config/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/dave/Source/Go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/dave/Source/Go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/lib/go-1.19""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/lib/go-1.19/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""go1.19.3""
GCCGO=""gccgo""
GOAMD64=""v1""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/dave/Source/keyholder/go.mod""
GOWORK=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build1272319925=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

I'm interfacing with the Linux kernel cryptography API using the AF_ALG interface, across two processes.  One process is responsible for setting up an AF_ALG (SOCK_SEQPACKET) socket, including setting the key and IV, and then the resulting socket file descriptor is passed to another process (using SCM_RIGHTS), which uses it for encryption or decryption.  By design, the first process does not have access to any of the plaintext or ciphertext data, and the second process does not have access to the encryption key.

The bug I was encountering was seemingly an extra '\0' in the decrypted plaintext output and an off-by-one error between plaintext and expected ciphertext length.  I discovered this is because an extra byte is silently added by x/sys/unix.sendmsgN() if passed an empty Iovec but non-empty out-of-band data, on a non-SOCK_DGRAM socket:

https://cs.opensource.google/go/x/sys/+/refs/tags/v0.2.0:unix/syscall_linux.go;l=1538;drc=d684c6f886692f8b63049d3dabe4f1911ae979c3;bpv=1;bpt=1

As far as I can tell, this behavior is undocumented.  I believe some socket types require at least one byte of data with OOB, but AF_ALG sockets do not.  (The Linux kernel documentation references https://www.chronox.de/libkcapi.html as the canonical client implementation, and it follows the pattern of OOB-but-empty-data to set up the socket, and then it uses vmsplice() to send the non-OOB data.)

The following call results in the extra byte being sent to the socket (error handling and populating `var oob []byte` omitted):

```
unix.SendmsgBuffers(fd, nil, oob, nil, unix.MSG_MORE)
```

This code works as expected:

```
msg := &unix.Msghdr{
    Control: &oob[0],
    // Remaining fields, including Iov and Iovlen are zero
}
msg.SetControllen(len(oob))
unix.Syscall(unix.SYS_SENDMSG, uintptr(fd), uintptr(unsafe.Pointer(msg)), unix.MSG_MORE)
```

### What did you expect to see?

An empty [][]byte resulting in no data being sent.

The documentation for SendmsgBuffers states, ""the function returns the number of bytes written to the socket.""

### What did you see instead?

A '\0' byte being sent to the socket unexpectedly.

SendmsgBuffers returns 0, but actually sends 1 byte to the socket.

### Possible solutions/topics for discussion

The implicit extra byte with Sendmsg appears to date back to the very first Go commit, so it probably comes from Plan 9.  SendmsgBuffers is, however, relatively new (https://github.com/golang/go/issues/52885) so maybe its API/behavior is not as set in stone.  Whether or not their behavior in this regard should diverge is probably a topic for debate.

Should SOCK_SEQPACKET be treated the same as SOCK_DGRAM, and excluded from having the extra byte sent?  If so, should the socket types (maybe just SOCK_STREAM) that require special empty-iovec handling be an allowlist instead of a denylist?

Should the SendmsgBuffers return value be updated to reflect the actual number of bytes sent when passed an empty [][]byte?

Instead of silently adding an invisible byte, should an error be returned if SendmsgBuffers is not supposed to be called with an empty [][]byte?

Even if no changes to behavior are warranted, should SendmsgBuffer's documentation be improved?  (Yes, I am volunteering to do so. :))
",1,x sys unix  undocumented  possibly incorrect   sendmsgbuffers behavior with empty iovec         please answer these questions before submitting your issue  thanks              what version of go are you using   go version            go version  go version       linux      cat go sum  golang org x sys             a   golang org x sys       go mod                  does this issue reproduce with the latest release     yes         what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   home dave  cache go build   goenv   home dave  config go env   goexe     goexperiment     goflags     gohostarch      gohostos  linux   goinsecure     gomodcache   home dave source go pkg mod   gonoproxy     gonosumdb     goos  linux   gopath   home dave source go   goprivate     goproxy     goroot   usr lib go       gosumdb  sum golang org   gotmpdir     gotooldir   usr lib go     pkg tool linux     govcs     goversion          gccgo  gccgo          ar  ar   cc  gcc   cxx  g     cgo enabled      gomod   home dave source keyholder go mod   gowork     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  wl   no gc sections  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches             what did you do     i m interfacing with the linux kernel cryptography api using the af alg interface  across two processes   one process is responsible for setting up an af alg  sock seqpacket  socket  including setting the key and iv  and then the resulting socket file descriptor is passed to another process  using scm rights   which uses it for encryption or decryption   by design  the first process does not have access to any of the plaintext or ciphertext data  and the second process does not have access to the encryption key     the bug i was encountering was seemingly an extra      in the decrypted plaintext output and an off by one error between plaintext and expected ciphertext length   i discovered this is because an extra byte is silently added by x sys unix sendmsgn   if passed an empty iovec but non empty out of band data  on a non sock dgram socket          as far as i can tell  this behavior is undocumented   i believe some socket types require at least one byte of data with oob  but af alg sockets do not    the linux kernel documentation references   as the canonical client implementation  and it follows the pattern of oob but empty data to set up the socket  and then it uses vmsplice   to send the non oob data      the following call results in the extra byte being sent to the socket  error handling and populating  var oob  byte  omitted           unix sendmsgbuffers fd  nil  oob  nil  unix msg more          this code works as expected          msg     unix msghdr       control   oob           remaining fields  including iov and iovlen are zero     msg setcontrollen len oob    unix syscall unix sys sendmsg  uintptr fd   uintptr unsafe pointer msg    unix msg more              what did you expect to see     an empty   byte resulting in no data being sent     the documentation for sendmsgbuffers states   the function returns the number of bytes written to the socket          what did you see instead     a      byte being sent to the socket unexpectedly     sendmsgbuffers returns    but actually sends   byte to the socket         possible solutions topics for discussion    the implicit extra byte with sendmsg appears to date back to the very first go commit  so it probably comes from plan     sendmsgbuffers is  however  relatively new    so maybe its api behavior is not as set in stone   whether or not their behavior in this regard should diverge is probably a topic for debate     should sock seqpacket be treated the same as sock dgram  and excluded from having the extra byte sent   if so  should the socket types  maybe just sock stream  that require special empty iovec handling be an allowlist instead of a denylist     should the sendmsgbuffers return value be updated to reflect the actual number of bytes sent when passed an empty   byte     instead of silently adding an invisible byte  should an error be returned if sendmsgbuffers is not supposed to be called with an empty   byte     even if no changes to behavior are warranted  should sendmsgbuffer s documentation be improved    yes  i am volunteering to do so       ,1
16936,3576339416.0,IssuesEvent,2016-01-27 19:10:05,SpamExperts/pyzor,https://api.github.com/repos/SpamExperts/pyzor,closed,crash while parsing spam message,bug Pyzor Client Testing,"Hi,

i got the following traceback while trying to check a message with pyzor.

$ pyzor -s mbox check < spam.mbox 
Traceback (most recent call last):
  File ""/usr/bin/pyzor"", line 408, in <module>
    main()
  File ""/usr/bin/pyzor"", line 152, in main
    if not dispatch(client, servers, config):
  File ""/usr/bin/pyzor"", line 237, in check
    for digested in get_input_handler(style):
  File ""/usr/bin/pyzor"", line 181, in _get_input_mbox
    tfile.write(sys.stdin.read().encode(""utf8""))
  File ""/usr/lib/python3.4/codecs.py"", line 319, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa3 in position 2649: invalid start byte

I'm using pyzor 1.0.0 with python 3.4.3. I can provide the spam message that caused the crash if needed.

BR
Atanas
",1.0,"crash while parsing spam message - Hi,

i got the following traceback while trying to check a message with pyzor.

$ pyzor -s mbox check < spam.mbox 
Traceback (most recent call last):
  File ""/usr/bin/pyzor"", line 408, in <module>
    main()
  File ""/usr/bin/pyzor"", line 152, in main
    if not dispatch(client, servers, config):
  File ""/usr/bin/pyzor"", line 237, in check
    for digested in get_input_handler(style):
  File ""/usr/bin/pyzor"", line 181, in _get_input_mbox
    tfile.write(sys.stdin.read().encode(""utf8""))
  File ""/usr/lib/python3.4/codecs.py"", line 319, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa3 in position 2649: invalid start byte

I'm using pyzor 1.0.0 with python 3.4.3. I can provide the spam message that caused the crash if needed.

BR
Atanas
",0,crash while parsing spam message   hi     i got the following traceback while trying to check a message with pyzor       pyzor  s mbox check   spam mbox   traceback  most recent call last      file   usr bin pyzor   line    in        main      file   usr bin pyzor   line    in main      if not dispatch client  servers  config      file   usr bin pyzor   line    in check      for digested in get input handler style      file   usr bin pyzor   line    in  get input mbox      tfile write sys stdin read   encode          file   usr lib     codecs py   line    in decode       result  consumed    self  buffer decode data  self errors  final   unicodedecodeerror   utf    codec can t decode byte   in position    invalid start byte    i m using pyzor       with python        i can provide the spam message that caused the crash if needed     br  atanas  ,0
68133,13082718966.0,IssuesEvent,2020-08-01 15:25:35,minetest/minetest,https://api.github.com/repos/minetest/minetest,closed,gcc warning: -Wclass-memaccess in mapblock_mesh.cpp getNodeVertexDirs,Code quality Low priority,"Hello, just found a warning while compiling

## Issue type

- Build issue
- commit: 3ce03d1c2a63d261c83f5962cd13212697f19472
- related to #8292, and #8117 (maybe others)
- Possible already merged fix on another instance of the warning: #8122

## Gcc version
gcc:
```
g++ --version
g++ (Ubuntu 10.1.0-2ubuntu1~18.04) 10.1.0
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
```
## Warning
Here the warning:
```
[ 37%] Building CXX object src/CMakeFiles/minetest.dir/client/mapblock_mesh.cpp.o
minetest/src/client/mapblock_mesh.cpp: In function ‘void getNodeVertexDirs(const v3s16&, v3s16*)’:
minetest/src/client/mapblock_mesh.cpp:422:64: warning: ‘void* memcpy(void*, const void*, size_t)’ writing to an object of type ‘v3s16’ {aka ‘class irr::core::vector3d<short int>’} with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]
  422 |  memcpy(vertex_dirs, &vertex_dirs_table[idx], 4 * sizeof(v3s16));
      |                                                                ^
In file included from minetest/src/irr_v3d.h:24,
                 from minetest/src/irrlichttypes_bloated.h:25,
                 from minetest/src/irrlichttypes_extrabloated.h:22,
                 from minetest/src/client/mapblock_mesh.h:22,
                 from minetest/src/client/mapblock_mesh.cpp:20:
/usr/include/irrlicht/vector3d.h:22:8: note: ‘v3s16’ {aka ‘class irr::core::vector3d<short int>’} declared here
   22 |  class vector3d
      |        ^~~~~~~~
```

## Affected code

 https://github.com/minetest/minetest/blob/5311a275235d2132443643199330953c877b794a/src/client/mapblock_mesh.cpp#L404-L422

If the fix is not to hard, and if it's possible I can be mentored to fix it. :)

Edit: Removed ""personnal"" part of the paths for clarity.",1.0,"gcc warning: -Wclass-memaccess in mapblock_mesh.cpp getNodeVertexDirs - Hello, just found a warning while compiling

## Issue type

- Build issue
- commit: 3ce03d1c2a63d261c83f5962cd13212697f19472
- related to #8292, and #8117 (maybe others)
- Possible already merged fix on another instance of the warning: #8122

## Gcc version
gcc:
```
g++ --version
g++ (Ubuntu 10.1.0-2ubuntu1~18.04) 10.1.0
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
```
## Warning
Here the warning:
```
[ 37%] Building CXX object src/CMakeFiles/minetest.dir/client/mapblock_mesh.cpp.o
minetest/src/client/mapblock_mesh.cpp: In function ‘void getNodeVertexDirs(const v3s16&, v3s16*)’:
minetest/src/client/mapblock_mesh.cpp:422:64: warning: ‘void* memcpy(void*, const void*, size_t)’ writing to an object of type ‘v3s16’ {aka ‘class irr::core::vector3d<short int>’} with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Wclass-memaccess]
  422 |  memcpy(vertex_dirs, &vertex_dirs_table[idx], 4 * sizeof(v3s16));
      |                                                                ^
In file included from minetest/src/irr_v3d.h:24,
                 from minetest/src/irrlichttypes_bloated.h:25,
                 from minetest/src/irrlichttypes_extrabloated.h:22,
                 from minetest/src/client/mapblock_mesh.h:22,
                 from minetest/src/client/mapblock_mesh.cpp:20:
/usr/include/irrlicht/vector3d.h:22:8: note: ‘v3s16’ {aka ‘class irr::core::vector3d<short int>’} declared here
   22 |  class vector3d
      |        ^~~~~~~~
```

## Affected code

 https://github.com/minetest/minetest/blob/5311a275235d2132443643199330953c877b794a/src/client/mapblock_mesh.cpp#L404-L422

If the fix is not to hard, and if it's possible I can be mentored to fix it. :)

Edit: Removed ""personnal"" part of the paths for clarity.",0,gcc warning   wclass memaccess in mapblock mesh cpp getnodevertexdirs   hello  just found a warning while compiling       issue type      build issue    commit       related to     and     maybe others     possible already merged fix on another instance of the warning           gcc version  gcc        g     version  g    ubuntu                     copyright  c    free software foundation  inc   this is free software  see the source for copying conditions   there is no  warranty  not even for merchantability or fitness for a particular purpose           warning  here the warning          building cxx object src cmakefiles minetest dir client mapblock mesh cpp o  minetest src client mapblock mesh cpp  in function ‘void getnodevertexdirs const        ’   minetest src client mapblock mesh cpp      warning  ‘void  memcpy void   const void   size t ’ writing to an object of type ‘ ’  aka ‘class irr  core    ’  with no trivial copy assignment  use copy assignment or copy initialization instead           memcpy vertex dirs   vertex dirs table       sizeof                                                                                 in file included from minetest src irr   h                      from minetest src irrlichttypes bloated h                      from minetest src irrlichttypes extrabloated h                      from minetest src client mapblock mesh h                      from minetest src client mapblock mesh cpp      usr include irrlicht   h      note  ‘ ’  aka ‘class irr  core    ’  declared here          class                                       affected code          if the fix is not to hard  and if it s possible i can be mentored to fix it        edit  removed  personnal  part of the paths for clarity ,0
65560,8819660880.0,IssuesEvent,2018-12-31 22:49:20,golang/go,https://api.github.com/repos/golang/go,closed,strconv: Atoi documentation is slightly misleading,Documentation NeedsFix,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version 1.11.4
</pre>

### Does this issue reproduce with the latest release?
Yes.


### What operating system and processor architecture are you using (`go env`)?
Irrelevant.

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env

</pre></details>

### What did you do?
Look at the documentation here: https://golang.org/src/strconv/atoi.go?s=5013:5045#L192
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->



### What did you expect to see?
An explanation of `strconv.Atoi` that matched what it actually did.


### What did you see instead?
An explanation that is only half true.

`Atoi returns the result of ParseInt(s, 10, 0) converted to type int.`

It appears that `Atoi` doesn't just return the value of `ParseInt(s, 10, 0)`, it only calls `ParseInt` as a last alternative, the ""slow path"". Without checking the code I was under the belief that I could just replace `Atoi` with `ParseInt` and it would basically run the exact same code.

It appears that the documentation was correct up until this commit:
https://github.com/golang/go/commit/46aa9f5437b000fad3696b0cd9fd97995da16411#diff-cbef0f4cdbfb7c355433bb342a5ef463",1.0,"strconv: Atoi documentation is slightly misleading - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version 1.11.4
</pre>

### Does this issue reproduce with the latest release?
Yes.


### What operating system and processor architecture are you using (`go env`)?
Irrelevant.

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env

</pre></details>

### What did you do?
Look at the documentation here: https://golang.org/src/strconv/atoi.go?s=5013:5045#L192
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->



### What did you expect to see?
An explanation of `strconv.Atoi` that matched what it actually did.


### What did you see instead?
An explanation that is only half true.

`Atoi returns the result of ParseInt(s, 10, 0) converted to type int.`

It appears that `Atoi` doesn't just return the value of `ParseInt(s, 10, 0)`, it only calls `ParseInt` as a last alternative, the ""slow path"". Without checking the code I was under the belief that I could just replace `Atoi` with `ParseInt` and it would basically run the exact same code.

It appears that the documentation was correct up until this commit:
https://github.com/golang/go/commit/46aa9f5437b000fad3696b0cd9fd97995da16411#diff-cbef0f4cdbfb7c355433bb342a5ef463",1,strconv  atoi documentation is slightly misleading            what version of go are you using   go version            go version                 does this issue reproduce with the latest release   yes           what operating system and processor architecture are you using   go env     irrelevant        go env  output       go env              what did you do   look at the documentation here           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best                  what did you expect to see   an explanation of  strconv atoi  that matched what it actually did           what did you see instead   an explanation that is only half true      atoi returns the result of parseint s        converted to type int      it appears that  atoi  doesn t just return the value of  parseint s          it only calls  parseint  as a last alternative  the  slow path   without checking the code i was under the belief that i could just replace  atoi  with  parseint  and it would basically run the exact same code     it appears that the documentation was correct up until this commit    ,1
66378,8920200871.0,IssuesEvent,2019-01-21 05:31:22,golang/go,https://api.github.com/repos/golang/go,closed,"flag: PrintDefaults claims configurability, but doesn't say how",Documentation NeedsFix,"https://golang.org/pkg/flag/#PrintDefaults says 

> PrintDefaults prints, to standard error unless configured otherwise, ...

I couldn't see anywhere how to send its output anywhere else.

I dug through the source code and eventually made my way to `(*FlagSet).SetOutput`, but that was not at all obvious.
",1.0,"flag: PrintDefaults claims configurability, but doesn't say how - https://golang.org/pkg/flag/#PrintDefaults says 

> PrintDefaults prints, to standard error unless configured otherwise, ...

I couldn't see anywhere how to send its output anywhere else.

I dug through the source code and eventually made my way to `(*FlagSet).SetOutput`, but that was not at all obvious.
",1,flag  printdefaults claims configurability  but doesn t say how     says     printdefaults prints  to standard error unless configured otherwise       i couldn t see anywhere how to send its output anywhere else   i dug through the source code and eventually made my way to    flagset  setoutput   but that was not at all obvious  ,1
6639,3037854759.0,IssuesEvent,2015-08-06 19:16:00,golang/go,https://api.github.com/repos/golang/go,closed,doc: be more explicit about panic / recover & new goroutines,Documentation,"I had some confusion over in [Google Groups](https://groups.google.com/forum/#!topic/google-appengine-go/ZCZk2T9rKDk) that recover would apply to any ""descendant"" goroutine panics, similar to try / catch statements in other languages. Neither the [Go blog](http://blog.golang.org/defer-panic-and-recover) nor the [spec](http://golang.org/ref/spec#Handling_panics) is very explicit.

@dsymonds explained it very succinctly as *""The recover builtin only applies to the stack frame that it is in, and each goroutine gets its own stack.""*

I've been working professionally in Go all day every day for over a year and am just learning this little tidbit, and otherwise consider myself fairly proficient, despite misunderstanding something so basic. I'd like to propose an addition to the spec explaining the difference between panic / recover and try / catch, or at a minimum adding @dsymonds' clarification.",1.0,"doc: be more explicit about panic / recover & new goroutines - I had some confusion over in [Google Groups](https://groups.google.com/forum/#!topic/google-appengine-go/ZCZk2T9rKDk) that recover would apply to any ""descendant"" goroutine panics, similar to try / catch statements in other languages. Neither the [Go blog](http://blog.golang.org/defer-panic-and-recover) nor the [spec](http://golang.org/ref/spec#Handling_panics) is very explicit.

@dsymonds explained it very succinctly as *""The recover builtin only applies to the stack frame that it is in, and each goroutine gets its own stack.""*

I've been working professionally in Go all day every day for over a year and am just learning this little tidbit, and otherwise consider myself fairly proficient, despite misunderstanding something so basic. I'd like to propose an addition to the spec explaining the difference between panic / recover and try / catch, or at a minimum adding @dsymonds' clarification.",1,doc  be more explicit about panic   recover   new goroutines   i had some confusion over in     that recover would apply to any  descendant  goroutine panics  similar to try   catch statements in other languages  neither the     nor the     is very explicit      dsymonds explained it very succinctly as   the recover builtin only applies to the stack frame that it is in  and each goroutine gets its own stack       i ve been working professionally in go all day every day for over a year and am just learning this little tidbit  and otherwise consider myself fairly proficient  despite misunderstanding something so basic  i d like to propose an addition to the spec explaining the difference between panic   recover and try   catch  or at a minimum adding  dsymonds  clarification ,1
280187,24283129940.0,IssuesEvent,2022-09-28 19:18:13,ethereum/solidity,https://api.github.com/repos/ethereum/solidity,opened,Bytecode compare runs with `--via-ir`,testing :hammer: medium effort medium impact must have,"The IR pipeline is non-experimental now but our [bytecode compare job](https://github.com/ethereum/solidity/blob/v0.8.17/.circleci/config.yml#L1469-L1504) still uses the legacy codegen. We should add extra runs with `--via-ir`.

I think it's enough to do this for CLI. We might also switch the JSON runs to `--via-ir` but I don't think it's necessary to run them for both codegens.

Note that solc-bin has a [bytecode compare PR check](https://github.com/ethereum/solc-bin/blob/gh-pages/.github/workflows/t-bytecode-compare.yml) that's implemented separately. Not sure if we want to update that one. Running it with one codegen already provides most of its value (which is making sure that the binary is not damaged). The binaries submitted to solc-bin are expected to have gone through the full bytecode comparison in the main repo anyway.",1.0,"Bytecode compare runs with `--via-ir` - The IR pipeline is non-experimental now but our [bytecode compare job](https://github.com/ethereum/solidity/blob/v0.8.17/.circleci/config.yml#L1469-L1504) still uses the legacy codegen. We should add extra runs with `--via-ir`.

I think it's enough to do this for CLI. We might also switch the JSON runs to `--via-ir` but I don't think it's necessary to run them for both codegens.

Note that solc-bin has a [bytecode compare PR check](https://github.com/ethereum/solc-bin/blob/gh-pages/.github/workflows/t-bytecode-compare.yml) that's implemented separately. Not sure if we want to update that one. Running it with one codegen already provides most of its value (which is making sure that the binary is not damaged). The binaries submitted to solc-bin are expected to have gone through the full bytecode comparison in the main repo anyway.",0,bytecode compare runs with    via ir    the ir pipeline is non experimental now but our     still uses the legacy codegen  we should add extra runs with    via ir      i think it s enough to do this for cli  we might also switch the json runs to    via ir  but i don t think it s necessary to run them for both codegens     note that solc bin has a     that s implemented separately  not sure if we want to update that one  running it with one codegen already provides most of its value  which is making sure that the binary is not damaged   the binaries submitted to solc bin are expected to have gone through the full bytecode comparison in the main repo anyway ,0
243652,7860334598.0,IssuesEvent,2018-06-21 19:36:05,google/google-api-python-client,https://api.github.com/repos/google/google-api-python-client,closed,Undefined error: 'Module_six_moves_urllib_parse' object has no attribute 'urlencode',:rotating_light: priority: p2+ status: will not fix type: question,"I tried code sample from https://cloud.google.com/bigquery/authorization, with the environment mentioned below and i got the error.

Environment:
python version 2.7.6
google-api-python-client version 1.4.0
six version 1.4.1

However when i downgraded google-api-python-client to 1.3.2 it works
",1.0,"Undefined error: 'Module_six_moves_urllib_parse' object has no attribute 'urlencode' - I tried code sample from https://cloud.google.com/bigquery/authorization, with the environment mentioned below and i got the error.

Environment:
python version 2.7.6
google-api-python-client version 1.4.0
six version 1.4.1

However when i downgraded google-api-python-client to 1.3.2 it works
",0,undefined error   module six moves urllib parse  object has no attribute  urlencode    i tried code sample from   with the environment mentioned below and i got the error   environment  python version       google api python client version       six version        however when i downgraded google api python client to       it works ,0
5226,2915296394.0,IssuesEvent,2015-06-23 11:39:04,golang/go,https://api.github.com/repos/golang/go,closed,runtime: Will the variable pointer in Go side be invalid during calling C function due to garbage collection?,Documentation,"Go garbage collector does not know Go variable(pointer) used in C world. In Go package source code:
https://github.com/golang/go/blob/master/src/net/cgo_unix.go#L47 here is a variable ""hints"" in Go world which is passed into C function getaddrinfo(). Theoretically, is it possible that the address of ""hints"" is invalid due to Go garbage collection?",1.0,"runtime: Will the variable pointer in Go side be invalid during calling C function due to garbage collection? - Go garbage collector does not know Go variable(pointer) used in C world. In Go package source code:
https://github.com/golang/go/blob/master/src/net/cgo_unix.go#L47 here is a variable ""hints"" in Go world which is passed into C function getaddrinfo(). Theoretically, is it possible that the address of ""hints"" is invalid due to Go garbage collection?",1,runtime  will the variable pointer in go side be invalid during calling c function due to garbage collection    go garbage collector does not know go variable pointer  used in c world  in go package source code     here is a variable  hints  in go world which is passed into c function getaddrinfo    theoretically  is it possible that the address of  hints  is invalid due to go garbage collection ,1
36254,17576548230.0,IssuesEvent,2021-08-15 18:18:31,JWCook/aiohttp-client-cache,https://api.github.com/repos/JWCook/aiohttp-client-cache,closed,Performance testing,performance,"Each storage backend should have some simple performance testing done, e.g. with the stdlib [profile](https://docs.python.org/3.8/library/profile.html) module and maybe a memory profiler.

For now, I mostly just want to look for any obvious, stupid mistakes. For example, if an operation contains blocking code when it shouldn't, or performs significantly worse than its `requests-cache` equivalent.",True,"Performance testing - Each storage backend should have some simple performance testing done, e.g. with the stdlib [profile](https://docs.python.org/3.8/library/profile.html) module and maybe a memory profiler.

For now, I mostly just want to look for any obvious, stupid mistakes. For example, if an operation contains blocking code when it shouldn't, or performs significantly worse than its `requests-cache` equivalent.",0,performance testing   each storage backend should have some simple performance testing done  e g  with the stdlib     module and maybe a memory profiler     for now  i mostly just want to look for any obvious  stupid mistakes  for example  if an operation contains blocking code when it shouldn t  or performs significantly worse than its  requests cache  equivalent ,0
194886,14690623769.0,IssuesEvent,2021-01-02 16:09:16,github-vet/rangeloop-pointer-findings,https://api.github.com/repos/github-vet/rangeloop-pointer-findings,closed,presslabs/mysql-operator: pkg/controller/mysqlcluster/internal/cleaner/pvc_test.go; 3 LoC,fresh test tiny,"
Found a possible issue in [presslabs/mysql-operator](https://www.github.com/presslabs/mysql-operator) at [pkg/controller/mysqlcluster/internal/cleaner/pvc_test.go](https://github.com/presslabs/mysql-operator/blob/47436cc5edd3d974239e45c994ccf7e22afa65e0/pkg/controller/mysqlcluster/internal/cleaner/pvc_test.go#L122-L124)

Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.

> 

[Click here to see the code in its original context.](https://github.com/presslabs/mysql-operator/blob/47436cc5edd3d974239e45c994ccf7e22afa65e0/pkg/controller/mysqlcluster/internal/cleaner/pvc_test.go#L122-L124)

<details>
<summary>Click here to show the 3 line(s) of Go which triggered the analyzer.</summary>

```go
			for _, pvc := range pvcs {
				Expect(c.Create(context.TODO(), &pvc)).To(Succeed())
			}

```
</details>


<details>
<summary>Click here to show extra information the analyzer produced.</summary>

```
No path was found through the callgraph that could lead to a function which writes a pointer argument.

No path was found through the callgraph that could lead to a function which passes a pointer to third-party code.

root signature {Create 2} was not found in the callgraph; reference was passed directly to third-party code
```
</details>


Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.

commit ID: 47436cc5edd3d974239e45c994ccf7e22afa65e0
",1.0,"presslabs/mysql-operator: pkg/controller/mysqlcluster/internal/cleaner/pvc_test.go; 3 LoC - 
Found a possible issue in [presslabs/mysql-operator](https://www.github.com/presslabs/mysql-operator) at [pkg/controller/mysqlcluster/internal/cleaner/pvc_test.go](https://github.com/presslabs/mysql-operator/blob/47436cc5edd3d974239e45c994ccf7e22afa65e0/pkg/controller/mysqlcluster/internal/cleaner/pvc_test.go#L122-L124)

Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.

> 

[Click here to see the code in its original context.](https://github.com/presslabs/mysql-operator/blob/47436cc5edd3d974239e45c994ccf7e22afa65e0/pkg/controller/mysqlcluster/internal/cleaner/pvc_test.go#L122-L124)

<details>
<summary>Click here to show the 3 line(s) of Go which triggered the analyzer.</summary>

```go
			for _, pvc := range pvcs {
				Expect(c.Create(context.TODO(), &pvc)).To(Succeed())
			}

```
</details>


<details>
<summary>Click here to show extra information the analyzer produced.</summary>

```
No path was found through the callgraph that could lead to a function which writes a pointer argument.

No path was found through the callgraph that could lead to a function which passes a pointer to third-party code.

root signature {Create 2} was not found in the callgraph; reference was passed directly to third-party code
```
</details>


Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.

commit ID: 47436cc5edd3d974239e45c994ccf7e22afa65e0
",0,presslabs mysql operator  pkg controller mysqlcluster internal cleaner pvc test go    loc    found a possible issue in     at      below is the message reported by the analyzer for this snippet of code  beware that the analyzer only reports the first issue it finds  so please do not limit your consideration to the contents of the below message               click here to show the   line s  of go which triggered the analyzer       go 			for    pvc    range pvcs   				expect c create context todo     pvc   to succeed    			              click here to show extra information the analyzer produced        no path was found through the callgraph that could lead to a function which writes a pointer argument   no path was found through the callgraph that could lead to a function which passes a pointer to third party code   root signature  create    was not found in the callgraph  reference was passed directly to third party code         leave a reaction on this issue to contribute to the project by classifying this instance as a   bug           mitigated         or   desirable behavior    rocket  see the descriptions of the classifications     for more information   commit id    ,0
2650,3561231667.0,IssuesEvent,2016-01-23 17:19:11,tgstation/-tg-station,https://api.github.com/repos/tgstation/-tg-station,closed,Mining rocks on the asteroid creates air,Atmos Bug Performance,"When a rock is mined on the asteroid, air is produced. This is most easily noticed when an explosive goes off, as the wind pushes the materials mined to outside of the blast zone.
",True,"Mining rocks on the asteroid creates air - When a rock is mined on the asteroid, air is produced. This is most easily noticed when an explosive goes off, as the wind pushes the materials mined to outside of the blast zone.
",0,mining rocks on the asteroid creates air   when a rock is mined on the asteroid  air is produced  this is most easily noticed when an explosive goes off  as the wind pushes the materials mined to outside of the blast zone   ,0
794874,28052985156.0,IssuesEvent,2023-03-29 07:28:34,KDT3-Final-6/final-project-FE,https://api.github.com/repos/KDT3-Final-6/final-project-FE,opened,Feat: 홈페이지 - 플로팅 네비게이션 구현,Status: Available Status: Review Needed Priority:  High,"## ✔️ 체크사항
- [ ] 제목은 `개발 페이지 - 개발 목적` 으로 작성해 주세요.

## 💡 개발 목적

- 플로팅 네비게이션 구현

## 🌐 세부 내용

- [ ] 챗봇
- [ ] 상담번호 노출
- [ ] 맨 위로 버튼

## ⚙️ 참조
",1.0,"Feat: 홈페이지 - 플로팅 네비게이션 구현 - ## ✔️ 체크사항
- [ ] 제목은 `개발 페이지 - 개발 목적` 으로 작성해 주세요.

## 💡 개발 목적

- 플로팅 네비게이션 구현

## 🌐 세부 내용

- [ ] 챗봇
- [ ] 상담번호 노출
- [ ] 맨 위로 버튼

## ⚙️ 참조
",0,feat  홈페이지   플로팅 네비게이션 구현      ✔️ 체크사항      제목은  개발 페이지   개발 목적  으로 작성해 주세요        💡 개발 목적      플로팅 네비게이션 구현       🌐 세부 내용        챗봇      상담번호 노출      맨 위로 버튼       ⚙️ 참조  ,0
459222,13188743004.0,IssuesEvent,2020-08-13 07:08:43,webcompat/web-bugs,https://api.github.com/repos/webcompat/web-bugs,closed,www.xvideos2.com - video or audio doesn't play,browser-focus-geckoview engine-gecko ml-needsdiagnosis-false nsfw priority-normal,"<!-- @browser: Firefox Mobile 78.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 10; Mobile; rv:78.0) Gecko/78.0 Firefox/78.0 -->
<!-- @reported_with: unknown -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/56546 -->
<!-- @extra_labels: browser-focus-geckoview -->

**URL**: http://www.xvideos2.com/video57600039/desi_hot_short_flim_skymoviehd.xyz

**Browser / Version**: Firefox Mobile 78.0
**Operating System**: Android
**Tested Another Browser**: No 

**Problem type**: Video or audio doesn't play
**Description**: The video or audio does not play
**Steps to Reproduce**:


<details>
<summary>Browser Configuration</summary>
<ul>
  <li>None</li>
</ul>
</details>

_From [webcompat.com](https://webcompat.com/) with ❤️_",1.0,"www.xvideos2.com - video or audio doesn't play - <!-- @browser: Firefox Mobile 78.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 10; Mobile; rv:78.0) Gecko/78.0 Firefox/78.0 -->
<!-- @reported_with: unknown -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/56546 -->
<!-- @extra_labels: browser-focus-geckoview -->

**URL**: http://www.xvideos2.com/video57600039/desi_hot_short_flim_skymoviehd.xyz

**Browser / Version**: Firefox Mobile 78.0
**Operating System**: Android
**Tested Another Browser**: No 

**Problem type**: Video or audio doesn't play
**Description**: The video or audio does not play
**Steps to Reproduce**:


<details>
<summary>Browser Configuration</summary>
<ul>
  <li>None</li>
</ul>
</details>

_From [webcompat.com](https://webcompat.com/) with ❤️_",0,    video or audio doesn t play                url         browser   version    firefox mobile       operating system    android   tested another browser    no     problem type    video or audio doesn t play   description    the video or audio does not play   steps to reproduce         browser configuration       none        from     with ❤️ ,0
124371,10310202547.0,IssuesEvent,2019-08-29 14:44:03,eclipse/openj9,https://api.github.com/repos/eclipse/openj9,closed,s390x/compressedrefs/libj9jit29.so: undefined symbol: _Z39generateS390CompareAndBranchInstructionIjEPN2TR11InstructionEPNS0,arch:z comp:jit test failure,"Failure link
------------

https://ci.eclipse.org/openj9/job/Test_openjdk8_j9_sanity.functional_s390x_linux_OMR/229/tapResults/

Optional info
-------------


Failure output (captured from console output)
---------------------------------------------

```
===============================================
Running test stringConcatOptTest_0 ...
===============================================
stringConcatOptTest_0 Start Time: Tue Aug 27 15:08:44 2019 Epoch Time (ms): 1566932924668
variation: NoOptions
JVM_OPTIONS: -Xcompressedrefs 
JVMJ9VM011W Unable to load j9jit29: /home/jenkins/jenkins-agent/workspace/Test_openjdk8_j9_sanity.functional_s390x_linux_OMR/openjdkbinary/j2sdk-image/jre/lib/s390x/compressedrefs/libj9jit29.so: undefined symbol: _Z39generateS390CompareAndBranchInstructionIjEPN2TR11InstructionEPNS0_13CodeGeneratorEN3OMR10InstOpCode8MnemonicEPNS0_4NodeEPNS0_8RegisterET_NS5_1Z10InstOpCode19S390BranchConditionEPNS0_11LabelSymbolEbbS2_PNS0_28RegisterDependencyConditionsE
JVMJ9VM004E Cannot load library required by: -Xjit:count=1,disableAsyncCompilation,verbose,vlog=/home/jenkins/jenkins-agent/workspace/Test_openjdk8_j9_sanity.functional_s390x_linux_OMR/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15669328679326/stringConcatOptTest_0/jitv.log
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

stringConcatOptTest_0_FAILED
```",1.0,"s390x/compressedrefs/libj9jit29.so: undefined symbol: _Z39generateS390CompareAndBranchInstructionIjEPN2TR11InstructionEPNS0 - Failure link
------------

https://ci.eclipse.org/openj9/job/Test_openjdk8_j9_sanity.functional_s390x_linux_OMR/229/tapResults/

Optional info
-------------


Failure output (captured from console output)
---------------------------------------------

```
===============================================
Running test stringConcatOptTest_0 ...
===============================================
stringConcatOptTest_0 Start Time: Tue Aug 27 15:08:44 2019 Epoch Time (ms): 1566932924668
variation: NoOptions
JVM_OPTIONS: -Xcompressedrefs 
JVMJ9VM011W Unable to load j9jit29: /home/jenkins/jenkins-agent/workspace/Test_openjdk8_j9_sanity.functional_s390x_linux_OMR/openjdkbinary/j2sdk-image/jre/lib/s390x/compressedrefs/libj9jit29.so: undefined symbol: _Z39generateS390CompareAndBranchInstructionIjEPN2TR11InstructionEPNS0_13CodeGeneratorEN3OMR10InstOpCode8MnemonicEPNS0_4NodeEPNS0_8RegisterET_NS5_1Z10InstOpCode19S390BranchConditionEPNS0_11LabelSymbolEbbS2_PNS0_28RegisterDependencyConditionsE
JVMJ9VM004E Cannot load library required by: -Xjit:count=1,disableAsyncCompilation,verbose,vlog=/home/jenkins/jenkins-agent/workspace/Test_openjdk8_j9_sanity.functional_s390x_linux_OMR/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15669328679326/stringConcatOptTest_0/jitv.log
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

stringConcatOptTest_0_FAILED
```",0,  compressedrefs   so  undefined symbol       failure link                       optional info                     failure output  captured from console output                                                                                                          running test stringconcatopttest                                                         stringconcatopttest   start time  tue aug           epoch time  ms      variation  nooptions  jvm options   xcompressedrefs     unable to load     home jenkins jenkins agent workspace test     sanity functional   linux omr openjdkbinary   image jre lib   compressedrefs   so  undefined symbol                        cannot load library required by   xjit count   disableasynccompilation verbose vlog  home jenkins jenkins agent workspace test     sanity functional   linux omr openjdk tests testconfig scripts testkitgen          testconfig test output   stringconcatopttest   jitv log  error  could not create the java virtual machine   error  a fatal exception has occurred  program will exit     stringconcatopttest   failed     ,0
60997,8482677792.0,IssuesEvent,2018-10-25 19:14:08,golang/go,https://api.github.com/repos/golang/go,opened,text/template: documentation for IsTrue disagrees with its implementation for struct types,Documentation NeedsDecision,"As noted in #28391, the [documentation for `template.IsTrue`](https://tip.golang.org/pkg/text/template/#IsTrue) says:
> IsTrue reports whether the value is 'true', in the sense of not the zero of its type, and whether the value has a meaningful truth value.

The zero `time.Time` *is* the zero of its type, so according to the documentation it should be considered to be true, but the implementation clearly intends otherwise:
https://github.com/golang/go/blob/f6b554fec75ff1a36c6204755db8c1f638255b64/src/text/template/exec.go#L326-L327

Either the documentation should be clarified, or the behavior of `IsTrue` should be fixed to match what is documented. Probably the former.",1.0,"text/template: documentation for IsTrue disagrees with its implementation for struct types - As noted in #28391, the [documentation for `template.IsTrue`](https://tip.golang.org/pkg/text/template/#IsTrue) says:
> IsTrue reports whether the value is 'true', in the sense of not the zero of its type, and whether the value has a meaningful truth value.

The zero `time.Time` *is* the zero of its type, so according to the documentation it should be considered to be true, but the implementation clearly intends otherwise:
https://github.com/golang/go/blob/f6b554fec75ff1a36c6204755db8c1f638255b64/src/text/template/exec.go#L326-L327

Either the documentation should be clarified, or the behavior of `IsTrue` should be fixed to match what is documented. Probably the former.",1,text template  documentation for istrue disagrees with its implementation for struct types   as noted in     the     says     istrue reports whether the value is  true   in the sense of not the zero of its type  and whether the value has a meaningful truth value     the zero  time time   is  the zero of its type  so according to the documentation it should be considered to be true  but the implementation clearly intends otherwise        either the documentation should be clarified  or the behavior of  istrue  should be fixed to match what is documented  probably the former ,1
289998,32023108880.0,IssuesEvent,2023-09-22 06:49:17,Chiencc/asuswrt-gt-ac5300,https://api.github.com/repos/Chiencc/asuswrt-gt-ac5300,closed,ijgjpeg-7: 10 vulnerabilities (highest severity is: 7.5) - autoclosed,Mend: dependency security vulnerability,"<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ijgjpeg-7</b></p></summary>
<p>

<p>Reference repository for The Independent JPEG Group's JPEG software, with the TurboJPEG API bolted on (for benchmarking purposes)</p>
<p>Library home page: <a href=https://github.com/libjpeg-turbo/ijg.git>https://github.com/libjpeg-turbo/ijg.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5"">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>
</p>

</p></p>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (3)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdtarga.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdtarga.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdtarga.c</b>
</p>

<p></p></details>

## Vulnerabilities

| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (ijgjpeg version) | Remediation Possible** |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2018-11813](https://www.mend.io/vulnerability-database/CVE-2018-11813) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | ijgjpeg-7 | Direct | 2.0.0 | &#10060; |
| [CVE-2020-14152](https://www.mend.io/vulnerability-database/CVE-2020-14152) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.1 | ijgjpeg-7 | Direct | jpeg-9d | &#10060; |
| [WS-2021-0185](https://github.com/libjpeg-turbo/libjpeg-turbo/commit/f35fd27ec641c42d6b115bfa595e483ec58188d2) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.5 | ijgjpeg-7 | Direct | 2.1.0 | &#10060; |
| [CVE-2017-15232](https://www.mend.io/vulnerability-database/CVE-2017-15232) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.5 | detected in multiple dependencies | Direct | 1.5.3 | &#10060; |
| [CVE-2018-14498](https://www.mend.io/vulnerability-database/CVE-2018-14498) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.5 | ijgjpeg-7 | Direct | 2.0.0 | &#10060; |
| [CVE-2012-2806](https://www.mend.io/vulnerability-database/CVE-2012-2806) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.6 | ijgjpeg-7 | Direct | All libjpeg-turbo users should upgrade to the latest version >= libjpeg-turbo-1.2.1
 | &#10060; |
| [CVE-2020-35538](https://www.mend.io/vulnerability-database/CVE-2020-35538) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.5 | ijgjpeg-7 | Direct | 2.0.6 | &#10060; |
| [CVE-2021-46822](https://www.mend.io/vulnerability-database/CVE-2021-46822) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.5 | ijgjpeg-7 | Direct | 2.1.0 | &#10060; |
| [CVE-2013-6630](https://www.mend.io/vulnerability-database/CVE-2013-6630) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.3 | ijgjpeg-7 | Direct | 1.3.1 | &#10060; |
| [CVE-2013-6629](https://www.mend.io/vulnerability-database/CVE-2013-6629) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.3 | ijgjpeg-7 | Direct | 1.3.90 | &#10060; |
<p>**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation</p>

## Details

<details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2018-11813</summary>


###  Vulnerable Library - <b>ijgjpeg-7</b></p>
<p>

<p>Reference repository for The Independent JPEG Group's JPEG software, with the TurboJPEG API bolted on (for benchmarking purposes)</p>
<p>Library home page: <a href=https://github.com/libjpeg-turbo/ijg.git>https://github.com/libjpeg-turbo/ijg.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5"">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>

<p>Found in base branch: <b>master</b></p></p>

</p></p>

###  Vulnerable Source Files (3)
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdtarga.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdtarga.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdtarga.c</b>
</p>

<p></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
libjpeg 9c has a large loop because read_pixel in rdtarga.c mishandles EOF.

<p>Publish Date: 2018-06-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-11813>CVE-2018-11813</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Release Date: 2018-06-06</p>
<p>Fix Resolution: 2.0.0</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-14152</summary>


###  Vulnerable Library - <b>ijgjpeg-7</b></p>
<p>

<p>Reference repository for The Independent JPEG Group's JPEG software, with the TurboJPEG API bolted on (for benchmarking purposes)</p>
<p>Library home page: <a href=https://github.com/libjpeg-turbo/ijg.git>https://github.com/libjpeg-turbo/ijg.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5"">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>

<p>Found in base branch: <b>master</b></p></p>

</p></p>

###  Vulnerable Source Files (3)
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jmemnobs.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jmemnobs.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jmemnobs.c</b>
</p>

<p></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
In IJG JPEG (aka libjpeg) before 9d, jpeg_mem_available() in jmemnobs.c in djpeg does not honor the max_memory_to_use setting, possibly causing excessive memory consumption.

<p>Publish Date: 2020-06-15
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-14152>CVE-2020-14152</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14152"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14152</a></p>
<p>Release Date: 2020-06-15</p>
<p>Fix Resolution: jpeg-9d</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> WS-2021-0185</summary>


###  Vulnerable Library - <b>ijgjpeg-7</b></p>
<p>

<p>Reference repository for The Independent JPEG Group's JPEG software, with the TurboJPEG API bolted on (for benchmarking purposes)</p>
<p>Library home page: <a href=https://github.com/libjpeg-turbo/ijg.git>https://github.com/libjpeg-turbo/ijg.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5"">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>

<p>Found in base branch: <b>master</b></p></p>

</p></p>

###  Vulnerable Source Files (3)
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdppm.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdppm.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdppm.c</b>
</p>

<p></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
libjpeg-turbo before 2.1.0 is vulnerable to heap-buffer-overflow in get_word_rgb_row, related to rdppm.c.


<p>Publish Date: 2021-04-06
<p>URL: <a href=https://github.com/libjpeg-turbo/libjpeg-turbo/commit/f35fd27ec641c42d6b115bfa595e483ec58188d2>WS-2021-0185</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>6.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://osv.dev/vulnerability/OSV-2021-609"">https://osv.dev/vulnerability/OSV-2021-609</a></p>
<p>Release Date: 2021-04-06</p>
<p>Fix Resolution: 2.1.0</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2017-15232</summary>


###  Vulnerable Libraries - <b>ijgjpeg-7</b>, <b>ijgjpeg-7</b>, <b>ijgjpeg-7</b>, <b>ijgjpeg-7</b>, <b>ijgjpeg-7</b>, <b>ijgjpeg-7</b>, <b>ijgjpeg-7</b>, <b>ijgjpeg-7</b></p>
<p>


</p>

<p></p>

###  Vulnerability Details
<p>  
  
libjpeg-turbo 1.5.2 has a NULL Pointer Dereference in jdpostct.c and jquant1.c via a crafted JPEG file.

<p>Publish Date: 2017-10-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-15232>CVE-2017-15232</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>6.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15232"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15232</a></p>
<p>Release Date: 2017-10-11</p>
<p>Fix Resolution: 1.5.3</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2018-14498</summary>


###  Vulnerable Library - <b>ijgjpeg-7</b></p>
<p>

<p>Reference repository for The Independent JPEG Group's JPEG software, with the TurboJPEG API bolted on (for benchmarking purposes)</p>
<p>Library home page: <a href=https://github.com/libjpeg-turbo/ijg.git>https://github.com/libjpeg-turbo/ijg.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5"">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>

<p>Found in base branch: <b>master</b></p></p>

</p></p>

###  Vulnerable Source Files (3)
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdbmp.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdbmp.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdbmp.c</b>
</p>

<p></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
get_8bit_row in rdbmp.c in libjpeg-turbo through 1.5.90 and MozJPEG through 3.3.1 allows attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted 8-bit BMP in which one or more of the color indices is out of range for the number of palette entries.

<p>Publish Date: 2019-03-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-14498>CVE-2018-14498</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>6.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14498"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14498</a></p>
<p>Release Date: 2019-03-07</p>
<p>Fix Resolution: 2.0.0</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2012-2806</summary>


###  Vulnerable Library - <b>ijgjpeg-7</b></p>
<p>

<p>Reference repository for The Independent JPEG Group's JPEG software, with the TurboJPEG API bolted on (for benchmarking purposes)</p>
<p>Library home page: <a href=https://github.com/libjpeg-turbo/ijg.git>https://github.com/libjpeg-turbo/ijg.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5"">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>

<p>Found in base branch: <b>master</b></p></p>

</p></p>

###  Vulnerable Source Files (3)
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jdmarker.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jdmarker.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jdmarker.c</b>
</p>

<p></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
Heap-based buffer overflow in the get_sos function in jdmarker.c in libjpeg-turbo 1.2.0 allows remote attackers to cause a denial of service (application crash) and possibly execute arbitrary code via a large component count in the header of a JPEG image.

<p>Publish Date: 2012-08-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2012-2806>CVE-2012-2806</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>5.6</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: Low
</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=""http://security.gentoo.org/glsa/glsa-201209-13.xml"">http://security.gentoo.org/glsa/glsa-201209-13.xml</a></p>
<p>Release Date: 2012-09-26</p>
<p>Fix Resolution: All libjpeg-turbo users should upgrade to the latest version >= libjpeg-turbo-1.2.1
</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2020-35538</summary>


###  Vulnerable Library - <b>ijgjpeg-7</b></p>
<p>

<p>Reference repository for The Independent JPEG Group's JPEG software, with the TurboJPEG API bolted on (for benchmarking purposes)</p>
<p>Library home page: <a href=https://github.com/libjpeg-turbo/ijg.git>https://github.com/libjpeg-turbo/ijg.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5"">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>

<p>Found in base branch: <b>master</b></p></p>

</p></p>

###  Vulnerable Source Files (3)
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jdapistd.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jdapistd.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jdapistd.c</b>
</p>

<p></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
A crafted input file could cause a null pointer dereference in jcopy_sample_rows() when processed by libjpeg-turbo.

<p>Publish Date: 2022-08-31
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-35538>CVE-2020-35538</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>5.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-35538"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-35538</a></p>
<p>Release Date: 2022-08-31</p>
<p>Fix Resolution: 2.0.6</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2021-46822</summary>


###  Vulnerable Library - <b>ijgjpeg-7</b></p>
<p>

<p>Reference repository for The Independent JPEG Group's JPEG software, with the TurboJPEG API bolted on (for benchmarking purposes)</p>
<p>Library home page: <a href=https://github.com/libjpeg-turbo/ijg.git>https://github.com/libjpeg-turbo/ijg.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5"">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>

<p>Found in base branch: <b>master</b></p></p>

</p></p>

###  Vulnerable Source Files (3)
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdppm.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdppm.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdppm.c</b>
</p>

<p></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
The PPM reader in libjpeg-turbo through 2.0.90 mishandles use of tjLoadImage for loading a 16-bit binary PPM file into a grayscale buffer and loading a 16-bit binary PGM file into an RGB buffer. This is related to a heap-based buffer overflow in the get_word_rgb_row function in rdppm.c.

<p>Publish Date: 2022-06-18
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-46822>CVE-2021-46822</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>5.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-46822"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-46822</a></p>
<p>Release Date: 2022-06-18</p>
<p>Fix Resolution: 2.1.0</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2013-6630</summary>


###  Vulnerable Library - <b>ijgjpeg-7</b></p>
<p>

<p>Reference repository for The Independent JPEG Group's JPEG software, with the TurboJPEG API bolted on (for benchmarking purposes)</p>
<p>Library home page: <a href=https://github.com/libjpeg-turbo/ijg.git>https://github.com/libjpeg-turbo/ijg.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5"">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>

<p>Found in base branch: <b>master</b></p></p>

</p></p>

###  Vulnerable Source Files (3)
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jdmarker.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jdmarker.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jdmarker.c</b>
</p>

<p></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
The get_dht function in jdmarker.c in libjpeg-turbo through 1.3.0, as used in Google Chrome before 31.0.1650.48 and other products, does not set all elements of a certain Huffman value array during the reading of segments that follow Define Huffman Table (DHT) JPEG markers, which allows remote attackers to obtain sensitive information from uninitialized memory locations via a crafted JPEG image.

<p>Publish Date: 2013-11-19
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2013-6630>CVE-2013-6630</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>5.3</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: None
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Release Date: 2013-11-19</p>
<p>Fix Resolution: 1.3.1</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2013-6629</summary>


###  Vulnerable Library - <b>ijgjpeg-7</b></p>
<p>

<p>Reference repository for The Independent JPEG Group's JPEG software, with the TurboJPEG API bolted on (for benchmarking purposes)</p>
<p>Library home page: <a href=https://github.com/libjpeg-turbo/ijg.git>https://github.com/libjpeg-turbo/ijg.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5"">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>

<p>Found in base branch: <b>master</b></p></p>

</p></p>

###  Vulnerable Source Files (2)
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jdmarker.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jdmarker.c</b>
</p>

<p></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
The get_sos function in jdmarker.c in (1) libjpeg 6b and (2) libjpeg-turbo through 1.3.0, as used in Google Chrome before 31.0.1650.48, Ghostscript, and other products, does not check for certain duplications of component data during the reading of segments that follow Start Of Scan (SOS) JPEG markers, which allows remote attackers to obtain sensitive information from uninitialized memory locations via a crafted JPEG image.

<p>Publish Date: 2013-11-19
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2013-6629>CVE-2013-6629</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>5.3</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: None
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-6629"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-6629</a></p>
<p>Release Date: 2013-11-19</p>
<p>Fix Resolution: 1.3.90</p>

</p>

<p></p>

</details>",True,"ijgjpeg-7: 10 vulnerabilities (highest severity is: 7.5) - autoclosed - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ijgjpeg-7</b></p></summary>
<p>

<p>Reference repository for The Independent JPEG Group's JPEG software, with the TurboJPEG API bolted on (for benchmarking purposes)</p>
<p>Library home page: <a href=https://github.com/libjpeg-turbo/ijg.git>https://github.com/libjpeg-turbo/ijg.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5"">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>
</p>

</p></p>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (3)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdtarga.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdtarga.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdtarga.c</b>
</p>

<p></p></details>

## Vulnerabilities

| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (ijgjpeg version) | Remediation Possible** |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2018-11813](https://www.mend.io/vulnerability-database/CVE-2018-11813) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | ijgjpeg-7 | Direct | 2.0.0 | &#10060; |
| [CVE-2020-14152](https://www.mend.io/vulnerability-database/CVE-2020-14152) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.1 | ijgjpeg-7 | Direct | jpeg-9d | &#10060; |
| [WS-2021-0185](https://github.com/libjpeg-turbo/libjpeg-turbo/commit/f35fd27ec641c42d6b115bfa595e483ec58188d2) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.5 | ijgjpeg-7 | Direct | 2.1.0 | &#10060; |
| [CVE-2017-15232](https://www.mend.io/vulnerability-database/CVE-2017-15232) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.5 | detected in multiple dependencies | Direct | 1.5.3 | &#10060; |
| [CVE-2018-14498](https://www.mend.io/vulnerability-database/CVE-2018-14498) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.5 | ijgjpeg-7 | Direct | 2.0.0 | &#10060; |
| [CVE-2012-2806](https://www.mend.io/vulnerability-database/CVE-2012-2806) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.6 | ijgjpeg-7 | Direct | All libjpeg-turbo users should upgrade to the latest version >= libjpeg-turbo-1.2.1
 | &#10060; |
| [CVE-2020-35538](https://www.mend.io/vulnerability-database/CVE-2020-35538) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.5 | ijgjpeg-7 | Direct | 2.0.6 | &#10060; |
| [CVE-2021-46822](https://www.mend.io/vulnerability-database/CVE-2021-46822) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.5 | ijgjpeg-7 | Direct | 2.1.0 | &#10060; |
| [CVE-2013-6630](https://www.mend.io/vulnerability-database/CVE-2013-6630) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.3 | ijgjpeg-7 | Direct | 1.3.1 | &#10060; |
| [CVE-2013-6629](https://www.mend.io/vulnerability-database/CVE-2013-6629) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.3 | ijgjpeg-7 | Direct | 1.3.90 | &#10060; |
<p>**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation</p>

## Details

<details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2018-11813</summary>


###  Vulnerable Library - <b>ijgjpeg-7</b></p>
<p>

<p>Reference repository for The Independent JPEG Group's JPEG software, with the TurboJPEG API bolted on (for benchmarking purposes)</p>
<p>Library home page: <a href=https://github.com/libjpeg-turbo/ijg.git>https://github.com/libjpeg-turbo/ijg.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5"">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>

<p>Found in base branch: <b>master</b></p></p>

</p></p>

###  Vulnerable Source Files (3)
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdtarga.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdtarga.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdtarga.c</b>
</p>

<p></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
libjpeg 9c has a large loop because read_pixel in rdtarga.c mishandles EOF.

<p>Publish Date: 2018-06-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-11813>CVE-2018-11813</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Release Date: 2018-06-06</p>
<p>Fix Resolution: 2.0.0</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-14152</summary>


###  Vulnerable Library - <b>ijgjpeg-7</b></p>
<p>

<p>Reference repository for The Independent JPEG Group's JPEG software, with the TurboJPEG API bolted on (for benchmarking purposes)</p>
<p>Library home page: <a href=https://github.com/libjpeg-turbo/ijg.git>https://github.com/libjpeg-turbo/ijg.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5"">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>

<p>Found in base branch: <b>master</b></p></p>

</p></p>

###  Vulnerable Source Files (3)
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jmemnobs.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jmemnobs.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jmemnobs.c</b>
</p>

<p></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
In IJG JPEG (aka libjpeg) before 9d, jpeg_mem_available() in jmemnobs.c in djpeg does not honor the max_memory_to_use setting, possibly causing excessive memory consumption.

<p>Publish Date: 2020-06-15
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-14152>CVE-2020-14152</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14152"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14152</a></p>
<p>Release Date: 2020-06-15</p>
<p>Fix Resolution: jpeg-9d</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> WS-2021-0185</summary>


###  Vulnerable Library - <b>ijgjpeg-7</b></p>
<p>

<p>Reference repository for The Independent JPEG Group's JPEG software, with the TurboJPEG API bolted on (for benchmarking purposes)</p>
<p>Library home page: <a href=https://github.com/libjpeg-turbo/ijg.git>https://github.com/libjpeg-turbo/ijg.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5"">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>

<p>Found in base branch: <b>master</b></p></p>

</p></p>

###  Vulnerable Source Files (3)
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdppm.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdppm.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdppm.c</b>
</p>

<p></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
libjpeg-turbo before 2.1.0 is vulnerable to heap-buffer-overflow in get_word_rgb_row, related to rdppm.c.


<p>Publish Date: 2021-04-06
<p>URL: <a href=https://github.com/libjpeg-turbo/libjpeg-turbo/commit/f35fd27ec641c42d6b115bfa595e483ec58188d2>WS-2021-0185</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>6.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://osv.dev/vulnerability/OSV-2021-609"">https://osv.dev/vulnerability/OSV-2021-609</a></p>
<p>Release Date: 2021-04-06</p>
<p>Fix Resolution: 2.1.0</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2017-15232</summary>


###  Vulnerable Libraries - <b>ijgjpeg-7</b>, <b>ijgjpeg-7</b>, <b>ijgjpeg-7</b>, <b>ijgjpeg-7</b>, <b>ijgjpeg-7</b>, <b>ijgjpeg-7</b>, <b>ijgjpeg-7</b>, <b>ijgjpeg-7</b></p>
<p>


</p>

<p></p>

###  Vulnerability Details
<p>  
  
libjpeg-turbo 1.5.2 has a NULL Pointer Dereference in jdpostct.c and jquant1.c via a crafted JPEG file.

<p>Publish Date: 2017-10-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-15232>CVE-2017-15232</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>6.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15232"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15232</a></p>
<p>Release Date: 2017-10-11</p>
<p>Fix Resolution: 1.5.3</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2018-14498</summary>


###  Vulnerable Library - <b>ijgjpeg-7</b></p>
<p>

<p>Reference repository for The Independent JPEG Group's JPEG software, with the TurboJPEG API bolted on (for benchmarking purposes)</p>
<p>Library home page: <a href=https://github.com/libjpeg-turbo/ijg.git>https://github.com/libjpeg-turbo/ijg.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5"">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>

<p>Found in base branch: <b>master</b></p></p>

</p></p>

###  Vulnerable Source Files (3)
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdbmp.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdbmp.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdbmp.c</b>
</p>

<p></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
get_8bit_row in rdbmp.c in libjpeg-turbo through 1.5.90 and MozJPEG through 3.3.1 allows attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted 8-bit BMP in which one or more of the color indices is out of range for the number of palette entries.

<p>Publish Date: 2019-03-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-14498>CVE-2018-14498</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>6.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14498"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14498</a></p>
<p>Release Date: 2019-03-07</p>
<p>Fix Resolution: 2.0.0</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2012-2806</summary>


###  Vulnerable Library - <b>ijgjpeg-7</b></p>
<p>

<p>Reference repository for The Independent JPEG Group's JPEG software, with the TurboJPEG API bolted on (for benchmarking purposes)</p>
<p>Library home page: <a href=https://github.com/libjpeg-turbo/ijg.git>https://github.com/libjpeg-turbo/ijg.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5"">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>

<p>Found in base branch: <b>master</b></p></p>

</p></p>

###  Vulnerable Source Files (3)
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jdmarker.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jdmarker.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jdmarker.c</b>
</p>

<p></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
Heap-based buffer overflow in the get_sos function in jdmarker.c in libjpeg-turbo 1.2.0 allows remote attackers to cause a denial of service (application crash) and possibly execute arbitrary code via a large component count in the header of a JPEG image.

<p>Publish Date: 2012-08-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2012-2806>CVE-2012-2806</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>5.6</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: Low
</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=""http://security.gentoo.org/glsa/glsa-201209-13.xml"">http://security.gentoo.org/glsa/glsa-201209-13.xml</a></p>
<p>Release Date: 2012-09-26</p>
<p>Fix Resolution: All libjpeg-turbo users should upgrade to the latest version >= libjpeg-turbo-1.2.1
</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2020-35538</summary>


###  Vulnerable Library - <b>ijgjpeg-7</b></p>
<p>

<p>Reference repository for The Independent JPEG Group's JPEG software, with the TurboJPEG API bolted on (for benchmarking purposes)</p>
<p>Library home page: <a href=https://github.com/libjpeg-turbo/ijg.git>https://github.com/libjpeg-turbo/ijg.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5"">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>

<p>Found in base branch: <b>master</b></p></p>

</p></p>

###  Vulnerable Source Files (3)
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jdapistd.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jdapistd.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jdapistd.c</b>
</p>

<p></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
A crafted input file could cause a null pointer dereference in jcopy_sample_rows() when processed by libjpeg-turbo.

<p>Publish Date: 2022-08-31
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-35538>CVE-2020-35538</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>5.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-35538"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-35538</a></p>
<p>Release Date: 2022-08-31</p>
<p>Fix Resolution: 2.0.6</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2021-46822</summary>


###  Vulnerable Library - <b>ijgjpeg-7</b></p>
<p>

<p>Reference repository for The Independent JPEG Group's JPEG software, with the TurboJPEG API bolted on (for benchmarking purposes)</p>
<p>Library home page: <a href=https://github.com/libjpeg-turbo/ijg.git>https://github.com/libjpeg-turbo/ijg.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5"">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>

<p>Found in base branch: <b>master</b></p></p>

</p></p>

###  Vulnerable Source Files (3)
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdppm.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdppm.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/rdppm.c</b>
</p>

<p></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
The PPM reader in libjpeg-turbo through 2.0.90 mishandles use of tjLoadImage for loading a 16-bit binary PPM file into a grayscale buffer and loading a 16-bit binary PGM file into an RGB buffer. This is related to a heap-based buffer overflow in the get_word_rgb_row function in rdppm.c.

<p>Publish Date: 2022-06-18
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-46822>CVE-2021-46822</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>5.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-46822"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-46822</a></p>
<p>Release Date: 2022-06-18</p>
<p>Fix Resolution: 2.1.0</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2013-6630</summary>


###  Vulnerable Library - <b>ijgjpeg-7</b></p>
<p>

<p>Reference repository for The Independent JPEG Group's JPEG software, with the TurboJPEG API bolted on (for benchmarking purposes)</p>
<p>Library home page: <a href=https://github.com/libjpeg-turbo/ijg.git>https://github.com/libjpeg-turbo/ijg.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5"">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>

<p>Found in base branch: <b>master</b></p></p>

</p></p>

###  Vulnerable Source Files (3)
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jdmarker.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jdmarker.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jdmarker.c</b>
</p>

<p></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
The get_dht function in jdmarker.c in libjpeg-turbo through 1.3.0, as used in Google Chrome before 31.0.1650.48 and other products, does not set all elements of a certain Huffman value array during the reading of segments that follow Define Huffman Table (DHT) JPEG markers, which allows remote attackers to obtain sensitive information from uninitialized memory locations via a crafted JPEG image.

<p>Publish Date: 2013-11-19
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2013-6630>CVE-2013-6630</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>5.3</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: None
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Release Date: 2013-11-19</p>
<p>Fix Resolution: 1.3.1</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2013-6629</summary>


###  Vulnerable Library - <b>ijgjpeg-7</b></p>
<p>

<p>Reference repository for The Independent JPEG Group's JPEG software, with the TurboJPEG API bolted on (for benchmarking purposes)</p>
<p>Library home page: <a href=https://github.com/libjpeg-turbo/ijg.git>https://github.com/libjpeg-turbo/ijg.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Chiencc/asuswrt-gt-ac5300/commit/0c45ce909374d16605095db4fce9a89b9b6bafd5"">0c45ce909374d16605095db4fce9a89b9b6bafd5</a></p>

<p>Found in base branch: <b>master</b></p></p>

</p></p>

###  Vulnerable Source Files (2)
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jdmarker.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/release/src/router/jpeg/jdmarker.c</b>
</p>

<p></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
The get_sos function in jdmarker.c in (1) libjpeg 6b and (2) libjpeg-turbo through 1.3.0, as used in Google Chrome before 31.0.1650.48, Ghostscript, and other products, does not check for certain duplications of component data during the reading of segments that follow Start Of Scan (SOS) JPEG markers, which allows remote attackers to obtain sensitive information from uninitialized memory locations via a crafted JPEG image.

<p>Publish Date: 2013-11-19
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2013-6629>CVE-2013-6629</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>5.3</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: None
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-6629"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-6629</a></p>
<p>Release Date: 2013-11-19</p>
<p>Fix Resolution: 1.3.90</p>

</p>

<p></p>

</details>",0,ijgjpeg      vulnerabilities  highest severity is         autoclosed       vulnerable library    ijgjpeg          reference repository for the independent jpeg group s jpeg software  with the turbojpeg api bolted on  for benchmarking purposes    library home page   a href    found in head commit   a href             vulnerable source files                  release src router jpeg rdtarga c        release src router jpeg rdtarga c        release src router jpeg rdtarga c             vulnerabilities    cve   severity     cvss   dependency   type   fixed in  ijgjpeg version    remediation possible                                                                                               high         ijgjpeg     direct                            high         ijgjpeg     direct   jpeg                      medium         ijgjpeg     direct                            medium         detected in multiple dependencies   direct                            medium         ijgjpeg     direct                            medium         ijgjpeg     direct   all libjpeg turbo users should upgrade to the latest version    libjpeg turbo                           medium         ijgjpeg     direct                            medium         ijgjpeg     direct                            medium         ijgjpeg     direct                            medium         ijgjpeg     direct                     in some cases  remediation pr cannot be created automatically for a vulnerability despite the availability of remediation      details        cve             vulnerable library    ijgjpeg         reference repository for the independent jpeg group s jpeg software  with the turbojpeg api bolted on  for benchmarking purposes    library home page   a href    found in head commit   a href      found in base branch   master              vulnerable source files                 release src router jpeg rdtarga c        release src router jpeg rdtarga c        release src router jpeg rdtarga c                    vulnerability details        libjpeg   has a large loop because read pixel in rdtarga c mishandles eof    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  high   for more information on   scores  click  a href                suggested fix     type  upgrade version   release date          fix resolution                        cve             vulnerable library    ijgjpeg         reference repository for the independent jpeg group s jpeg software  with the turbojpeg api bolted on  for benchmarking purposes    library home page   a href    found in head commit   a href      found in base branch   master              vulnerable source files                 release src router jpeg jmemnobs c        release src router jpeg jmemnobs c        release src router jpeg jmemnobs c                    vulnerability details        in ijg jpeg  aka libjpeg  before    jpeg mem available   in jmemnobs c in djpeg does not honor the max memory to use setting  possibly causing excessive memory consumption    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  local     attack complexity  low     privileges required  none     user interaction  required     scope  unchanged   impact metrics      confidentiality impact  high     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  jpeg                   ws             vulnerable library    ijgjpeg         reference repository for the independent jpeg group s jpeg software  with the turbojpeg api bolted on  for benchmarking purposes    library home page   a href    found in head commit   a href      found in base branch   master              vulnerable source files                 release src router jpeg rdppm c        release src router jpeg rdppm c        release src router jpeg rdppm c                    vulnerability details        libjpeg turbo before       is vulnerable to heap buffer overflow in get word rgb row  related to rdppm c     publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  required     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  high   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution                        cve             vulnerable libraries    ijgjpeg      ijgjpeg      ijgjpeg      ijgjpeg      ijgjpeg      ijgjpeg      ijgjpeg      ijgjpeg                     vulnerability details        libjpeg turbo       has a null pointer dereference in jdpostct c and   c via a crafted jpeg file    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  required     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  high   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution                        cve             vulnerable library    ijgjpeg         reference repository for the independent jpeg group s jpeg software  with the turbojpeg api bolted on  for benchmarking purposes    library home page   a href    found in head commit   a href      found in base branch   master              vulnerable source files                 release src router jpeg rdbmp c        release src router jpeg rdbmp c        release src router jpeg rdbmp c                    vulnerability details        get   row in rdbmp c in libjpeg turbo through       and mozjpeg through       allows attackers to cause a denial of service  heap based buffer over read and application crash  via a crafted   bit bmp in which one or more of the color indices is out of range for the number of palette entries    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  required     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  high   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution                        cve             vulnerable library    ijgjpeg         reference repository for the independent jpeg group s jpeg software  with the turbojpeg api bolted on  for benchmarking purposes    library home page   a href    found in head commit   a href      found in base branch   master              vulnerable source files                 release src router jpeg jdmarker c        release src router jpeg jdmarker c        release src router jpeg jdmarker c                    vulnerability details        heap based buffer overflow in the get sos function in jdmarker c in libjpeg turbo       allows remote attackers to cause a denial of service  application crash  and possibly execute arbitrary code via a large component count in the header of a jpeg image    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  low     integrity impact  low     availability impact  low   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution  all libjpeg turbo users should upgrade to the latest version    libjpeg turbo                        cve             vulnerable library    ijgjpeg         reference repository for the independent jpeg group s jpeg software  with the turbojpeg api bolted on  for benchmarking purposes    library home page   a href    found in head commit   a href      found in base branch   master              vulnerable source files                 release src router jpeg jdapistd c        release src router jpeg jdapistd c        release src router jpeg jdapistd c                    vulnerability details        a crafted input file could cause a null pointer dereference in jcopy sample rows   when processed by libjpeg turbo    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  local     attack complexity  low     privileges required  none     user interaction  required     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  high   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution                        cve             vulnerable library    ijgjpeg         reference repository for the independent jpeg group s jpeg software  with the turbojpeg api bolted on  for benchmarking purposes    library home page   a href    found in head commit   a href      found in base branch   master              vulnerable source files                 release src router jpeg rdppm c        release src router jpeg rdppm c        release src router jpeg rdppm c                    vulnerability details        the ppm reader in libjpeg turbo through       mishandles use of tjloadimage for loading a   bit binary ppm file into a grayscale buffer and loading a   bit binary pgm file into an rgb buffer  this is related to a heap based buffer overflow in the get word rgb row function in rdppm c    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  local     attack complexity  low     privileges required  none     user interaction  required     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  high   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution                        cve             vulnerable library    ijgjpeg         reference repository for the independent jpeg group s jpeg software  with the turbojpeg api bolted on  for benchmarking purposes    library home page   a href    found in head commit   a href      found in base branch   master              vulnerable source files                 release src router jpeg jdmarker c        release src router jpeg jdmarker c        release src router jpeg jdmarker c                    vulnerability details        the get dht function in jdmarker c in libjpeg turbo through        as used in google chrome before         and other products  does not set all elements of a certain huffman value array during the reading of segments that follow define huffman table  dht  jpeg markers  which allows remote attackers to obtain sensitive information from uninitialized memory locations via a crafted jpeg image    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  low     integrity impact  none     availability impact  none   for more information on   scores  click  a href                suggested fix     type  upgrade version   release date          fix resolution                        cve             vulnerable library    ijgjpeg         reference repository for the independent jpeg group s jpeg software  with the turbojpeg api bolted on  for benchmarking purposes    library home page   a href    found in head commit   a href      found in base branch   master              vulnerable source files                 release src router jpeg jdmarker c        release src router jpeg jdmarker c                    vulnerability details        the get sos function in jdmarker c in     libjpeg   and     libjpeg turbo through        as used in google chrome before          ghostscript  and other products  does not check for certain duplications of component data during the reading of segments that follow start of scan  sos  jpeg markers  which allows remote attackers to obtain sensitive information from uninitialized memory locations via a crafted jpeg image    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  low     integrity impact  none     availability impact  none   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution                  ,0
1503,2544540080.0,IssuesEvent,2015-01-29 10:43:51,mysociety/yournextmp-popit,https://api.github.com/repos/mysociety/yournextmp-popit,opened,Make it obvious that this data may be incomplete,design,"As more people find the site, I think they aren't realising that the data is in complete in many places.  For example: 

https://twitter.com/eyeedinburgh/status/560517830916177920

Some heading on the newly designed pages (#146) that says something like ""This data is crowd sourced and may not be complete, please help us make it better"" might prevent this confusion.",1.0,"Make it obvious that this data may be incomplete - As more people find the site, I think they aren't realising that the data is in complete in many places.  For example: 

https://twitter.com/eyeedinburgh/status/560517830916177920

Some heading on the newly designed pages (#146) that says something like ""This data is crowd sourced and may not be complete, please help us make it better"" might prevent this confusion.",0,make it obvious that this data may be incomplete   as more people find the site  i think they aren t realising that the data is in complete in many places   for example           some heading on the newly designed pages      that says something like  this data is crowd sourced and may not be complete  please help us make it better  might prevent this confusion ,0
211843,16460193729.0,IssuesEvent,2021-05-21 17:44:28,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.17: document database/sql changes for Go 1.17,Documentation NeedsInvestigation help wanted release-blocker,"As of filing this issue, the [Go 1.17 draft release notes](https://tip.golang.org/doc/go1.17) contained the following HTML:

<dl id=""database/sql""><dt><a href=""/pkg/database/sql/"">database/sql</a></dt>
  <dd>
    <p><!-- CL 258360 -->
      TODO: <a href=""https://golang.org/cl/258360"">https://golang.org/cl/258360</a>: close driver.Connector if it implements io.Closer
    </p>
    <p><!-- CL 311572 -->
      TODO: <a href=""https://golang.org/cl/311572"">https://golang.org/cl/311572</a>: add NullInt16 and NullByte
    </p>
  </dd>
</dl>

---

This TODO needs to be resolved by July 1 so that we can have complete release notes for [Beta 1](https://golang.org/s/release#june-1--december-1-beta-1-issued).

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.17:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.17) and include ""For #44513. Fixes #46008."" in the body.",1.0,"doc/go1.17: document database/sql changes for Go 1.17 - As of filing this issue, the [Go 1.17 draft release notes](https://tip.golang.org/doc/go1.17) contained the following HTML:

<dl id=""database/sql""><dt><a href=""/pkg/database/sql/"">database/sql</a></dt>
  <dd>
    <p><!-- CL 258360 -->
      TODO: <a href=""https://golang.org/cl/258360"">https://golang.org/cl/258360</a>: close driver.Connector if it implements io.Closer
    </p>
    <p><!-- CL 311572 -->
      TODO: <a href=""https://golang.org/cl/311572"">https://golang.org/cl/311572</a>: add NullInt16 and NullByte
    </p>
  </dd>
</dl>

---

This TODO needs to be resolved by July 1 so that we can have complete release notes for [Beta 1](https://golang.org/s/release#june-1--december-1-beta-1-issued).

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.17:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.17) and include ""For #44513. Fixes #46008."" in the body.",1,doc      document database sql changes for go       as of filing this issue  the     contained the following html        database sql                       todo   a href    close driver connector if it implements io closer                       todo   a href    add   and nullbyte                          this todo needs to be resolved by july   so that we can have complete release notes for        a sequence of steps to resolve this issue may be        come up with a draft release note entry in this issue  then move the issue to needsfix state      send a cl with  doc           and include  for     fixes      in the body ,1
359838,25257951421.0,IssuesEvent,2022-11-15 19:51:56,golang/go,https://api.github.com/repos/golang/go,closed,"unsafe: no documentation for unsafe.SliceData, StringData, or String",Documentation NeedsFix release-blocker,"Recent changes added these data types to the unsafe package, but due to the peculiarities of how unsafe is implemented, special work needs to be done to have

```
go doc unsafe.String
```

work. It does not:

```
% go doc unsafe.String
doc: no symbol String in package unsafe
exit status 1
% 
```

Please fix.

",1.0,"unsafe: no documentation for unsafe.SliceData, StringData, or String - Recent changes added these data types to the unsafe package, but due to the peculiarities of how unsafe is implemented, special work needs to be done to have

```
go doc unsafe.String
```

work. It does not:

```
% go doc unsafe.String
doc: no symbol String in package unsafe
exit status 1
% 
```

Please fix.

",1,unsafe  no documentation for unsafe slicedata  stringdata  or string   recent changes added these data types to the unsafe package  but due to the peculiarities of how unsafe is implemented  special work needs to be done to have         go doc unsafe string         work  it does not            go doc unsafe string  doc  no symbol string in package unsafe  exit status               please fix     ,1
141113,12957747957.0,IssuesEvent,2020-07-20 10:12:20,golang/go,https://api.github.com/repos/golang/go,closed,x/xerrors: clarify documentation around stack frames ,Documentation NeedsInvestigation,"The docs for the `x/xerrors` package currently state

```
Most of the functions and types in this package will be incorporated into the standard library's errors package in Go 1.13; the behavior of this package's Errorf function will be incorporated into the standard library's fmt.Errorf. 
```

This is not accurate. `fmt.Errorf` does _not_ provide the stack-trace functionality of `xerrors.Errorf`. Accordingly, I would suggest changing this docstring to

```
Most of the functions and types in this package have been incorporated into the standard library's errors package in Go 1.13. However, if you wish to retain the stack trace functionality of `xerrors.Errorf`, you will need to keep using this package.
```",1.0,"x/xerrors: clarify documentation around stack frames  - The docs for the `x/xerrors` package currently state

```
Most of the functions and types in this package will be incorporated into the standard library's errors package in Go 1.13; the behavior of this package's Errorf function will be incorporated into the standard library's fmt.Errorf. 
```

This is not accurate. `fmt.Errorf` does _not_ provide the stack-trace functionality of `xerrors.Errorf`. Accordingly, I would suggest changing this docstring to

```
Most of the functions and types in this package have been incorporated into the standard library's errors package in Go 1.13. However, if you wish to retain the stack trace functionality of `xerrors.Errorf`, you will need to keep using this package.
```",1,x xerrors  clarify documentation around stack frames    the docs for the  x xerrors  package currently state         most of the functions and types in this package will be incorporated into the standard library s errors package in go      the behavior of this package s errorf function will be incorporated into the standard library s fmt errorf           this is not accurate   fmt errorf  does  not  provide the stack trace functionality of  xerrors errorf   accordingly  i would suggest changing this docstring to         most of the functions and types in this package have been incorporated into the standard library s errors package in go      however  if you wish to retain the stack trace functionality of  xerrors errorf   you will need to keep using this package      ,1
52720,7781498348.0,IssuesEvent,2018-06-06 00:38:02,golang/go,https://api.github.com/repos/golang/go,closed,x/crypto/acme/autocert: Document key generation with a non-nil acme.Client,Documentation,"Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
1.9

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?


### What did you do?
Read documentation at https://godoc.org/golang.org/x/crypto/acme/autocert#Manager.

### What did you expect to see?
Regarding the Client field, I expected the behaviour [here](https://github.com/golang/crypto/blob/847319b7fc94cab682988f93da778204da164588/acme/autocert/autocert.go#L635):
```
client := m.Client
if client == nil {
	client = &acme.Client{DirectoryURL: acme.LetsEncryptURL}
}
if client.Key == nil {
	var err error
	client.Key, err = m.accountKey(ctx)
	if err != nil {
		return nil, err
	}
}
```
To be documented, with something along the lines of:
```
// If Client is nil, a zero-value acme.Client is used with acme.LetsEncryptURL
// directory endpoint.
// Then, if Client.Key is nil, a newly-generated ECDSA P-256 key is used.
```

### What did you see instead?
```
// If Client is nil, a zero-value acme.Client is used with acme.LetsEncryptURL
// directory endpoint and a newly-generated ECDSA P-256 key.
```
Note that the current documentation implies that:
```
m := autocert.Manager{
	Client: &acme.Client{DirectoryURL: ""http://example.com""},
}
```
Is incorrect as the documentation for acme.Client states:
> Client is an ACME client. The only required field is Key.

The autocert package helpfully generates a key for you and fills in the Key field, allowing you to specify an alternative DirectoryURL without having to generate a key yourself.",1.0,"x/crypto/acme/autocert: Document key generation with a non-nil acme.Client - Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
1.9

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?


### What did you do?
Read documentation at https://godoc.org/golang.org/x/crypto/acme/autocert#Manager.

### What did you expect to see?
Regarding the Client field, I expected the behaviour [here](https://github.com/golang/crypto/blob/847319b7fc94cab682988f93da778204da164588/acme/autocert/autocert.go#L635):
```
client := m.Client
if client == nil {
	client = &acme.Client{DirectoryURL: acme.LetsEncryptURL}
}
if client.Key == nil {
	var err error
	client.Key, err = m.accountKey(ctx)
	if err != nil {
		return nil, err
	}
}
```
To be documented, with something along the lines of:
```
// If Client is nil, a zero-value acme.Client is used with acme.LetsEncryptURL
// directory endpoint.
// Then, if Client.Key is nil, a newly-generated ECDSA P-256 key is used.
```

### What did you see instead?
```
// If Client is nil, a zero-value acme.Client is used with acme.LetsEncryptURL
// directory endpoint and a newly-generated ECDSA P-256 key.
```
Note that the current documentation implies that:
```
m := autocert.Manager{
	Client: &acme.Client{DirectoryURL: ""http://example.com""},
}
```
Is incorrect as the documentation for acme.Client states:
> Client is an ACME client. The only required field is Key.

The autocert package helpfully generates a key for you and fills in the Key field, allowing you to specify an alternative DirectoryURL without having to generate a key yourself.",1,x crypto acme autocert  document key generation with a non nil acme client   please answer these questions before submitting your issue  thanks           what version of go are you using   go version                does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env             what did you do   read documentation at          what did you expect to see   regarding the client field  i expected the behaviour           client    m client  if client    nil    	client    acme client directoryurl  acme letsencrypturl      if client key    nil    	var err error  	client key  err   m accountkey ctx   	if err    nil    		return nil  err  	           to be documented  with something along the lines of           if client is nil  a zero value acme client is used with acme letsencrypturl     directory endpoint      then  if client key is nil  a newly generated ecdsa p   key is used              what did you see instead           if client is nil  a zero value acme client is used with acme letsencrypturl     directory endpoint and a newly generated ecdsa p   key        note that the current documentation implies that        m    autocert manager   	client   acme client directoryurl              is incorrect as the documentation for acme client states     client is an acme client  the only required field is key     the autocert package helpfully generates a key for you and fills in the key field  allowing you to specify an alternative directoryurl without having to generate a key yourself ,1
261803,22773947315.0,IssuesEvent,2022-07-08 12:47:51,MPMG-DCC-UFMG/F01,https://api.github.com/repos/MPMG-DCC-UFMG/F01,opened,Teste de generalizacao para a tag Informações institucionais - Link de acesso - Rio Preto,generalization test development,DoD: Realizar o teste de Generalização do validador da tag Informações institucionais - Link de acesso para o Município de Rio Preto.,1.0,Teste de generalizacao para a tag Informações institucionais - Link de acesso - Rio Preto - DoD: Realizar o teste de Generalização do validador da tag Informações institucionais - Link de acesso para o Município de Rio Preto.,0,teste de generalizacao para a tag informações institucionais   link de acesso   rio preto   dod  realizar o teste de generalização do validador da tag informações institucionais   link de acesso para o município de rio preto ,0
22000,30501433116.0,IssuesEvent,2023-07-18 14:11:15,kulturpass-de/kulturpass-app,https://api.github.com/repos/kulturpass-de/kulturpass-app,closed,Identifizierung auch bei Appversion 1.0.1 nicht möglich,In Process,"Der Identifizierungsprozess ist nach dem Appupdate auf Version 1.0.1 auf Android immernoch nicht möglich. Die App kommt zwar nun zwar 2 Bildschirme weiter (Welche Infos werden gelesen?, ...), aber der Ausweis wird mit gleichem Fehler zwar erkannt (Vibration beim dranhalten) aber halt nicht hinzufügt (AA2_TIMEOUT).",1.0,"Identifizierung auch bei Appversion 1.0.1 nicht möglich - Der Identifizierungsprozess ist nach dem Appupdate auf Version 1.0.1 auf Android immernoch nicht möglich. Die App kommt zwar nun zwar 2 Bildschirme weiter (Welche Infos werden gelesen?, ...), aber der Ausweis wird mit gleichem Fehler zwar erkannt (Vibration beim dranhalten) aber halt nicht hinzufügt (AA2_TIMEOUT).",0,identifizierung auch bei appversion       nicht möglich   der identifizierungsprozess ist nach dem appupdate auf version       auf android immernoch nicht möglich  die app kommt zwar nun zwar   bildschirme weiter  welche infos werden gelesen         aber der ausweis wird mit gleichem fehler zwar erkannt  vibration beim dranhalten  aber halt nicht hinzufügt    timeout  ,0
14587,3868544421.0,IssuesEvent,2016-04-10 01:07:41,golang/go,https://api.github.com/repos/golang/go,closed,x/exp/shiny: better examples UX,Documentation,"Please answer these questions before submitting your issue. Thanks!

1. What version of Go are you using (`go version`)?
go-1.6

2. What operating system and processor architecture are you using (`go env`)?
linux/amd64

3. What did you do?
```
$> mkdir /tmp/gopath
$> cd /tmp/gopath
$> export GOPATH=/tmp/gopath
$> go get -u golang.org/x/exp/shiny/screen/...
$> cd $GOPATH/src/golang.org/x/exp/shiny/example/basic
$> go run ./main.go
${GOPATH}/golang.org/x/exp/shiny/driver/internal/x11key/x11key.go:9:2: cannot find package ""golang.org/x/mobile/event/key"" in any of:

${GOPATH}/src/golang.org/x/exp/shiny/vendor/golang.org/x/mobile/event/key (vendor tree)
        /usr/local/go/src/golang.org/x/mobile/event/key (from $GOROOT)

${GOPATH}/src/golang.org/x/mobile/event/key (from $GOPATH)
${GOPATH}/src/golang.org/x/exp/shiny/driver/x11driver/window.go:25:2: cannot find package ""golang.org/x/mobile/event/lifecycle"" in any of:

${GOPATH}/src/golang.org/x/exp/shiny/vendor/golang.org/x/mobile/event/lifecycle (vendor tree)
        /usr/local/go/src/golang.org/x/mobile/event/lifecycle (from $GOROOT)

${GOPATH}/src/golang.org/x/mobile/event/lifecycle (from $GOPATH)
${GOPATH}/src/golang.org/x/exp/shiny/driver/x11driver/screen.go:20:2: cannot find package ""golang.org/x/mobile/event/mouse"" in any of:

[...etc...]
```

4. What did you expect to see?
A nicer way to run the example(s)

I would propose to:

```
$> cd $GOPATH/src/golang.org/x/exp/shiny
$> git mv example _examples
```

and remove all the `// +build ignore` build tags from the examples,
so one could at least do:
```
$> cd _examples/basic
$> go get -d .
```
to download all the dependencies in one go.

(I can send a CL)

-s

",1.0,"x/exp/shiny: better examples UX - Please answer these questions before submitting your issue. Thanks!

1. What version of Go are you using (`go version`)?
go-1.6

2. What operating system and processor architecture are you using (`go env`)?
linux/amd64

3. What did you do?
```
$> mkdir /tmp/gopath
$> cd /tmp/gopath
$> export GOPATH=/tmp/gopath
$> go get -u golang.org/x/exp/shiny/screen/...
$> cd $GOPATH/src/golang.org/x/exp/shiny/example/basic
$> go run ./main.go
${GOPATH}/golang.org/x/exp/shiny/driver/internal/x11key/x11key.go:9:2: cannot find package ""golang.org/x/mobile/event/key"" in any of:

${GOPATH}/src/golang.org/x/exp/shiny/vendor/golang.org/x/mobile/event/key (vendor tree)
        /usr/local/go/src/golang.org/x/mobile/event/key (from $GOROOT)

${GOPATH}/src/golang.org/x/mobile/event/key (from $GOPATH)
${GOPATH}/src/golang.org/x/exp/shiny/driver/x11driver/window.go:25:2: cannot find package ""golang.org/x/mobile/event/lifecycle"" in any of:

${GOPATH}/src/golang.org/x/exp/shiny/vendor/golang.org/x/mobile/event/lifecycle (vendor tree)
        /usr/local/go/src/golang.org/x/mobile/event/lifecycle (from $GOROOT)

${GOPATH}/src/golang.org/x/mobile/event/lifecycle (from $GOPATH)
${GOPATH}/src/golang.org/x/exp/shiny/driver/x11driver/screen.go:20:2: cannot find package ""golang.org/x/mobile/event/mouse"" in any of:

[...etc...]
```

4. What did you expect to see?
A nicer way to run the example(s)

I would propose to:

```
$> cd $GOPATH/src/golang.org/x/exp/shiny
$> git mv example _examples
```

and remove all the `// +build ignore` build tags from the examples,
so one could at least do:
```
$> cd _examples/basic
$> go get -d .
```
to download all the dependencies in one go.

(I can send a CL)

-s

",1,x exp shiny  better examples ux   please answer these questions before submitting your issue  thanks        what version of go are you using   go version     go           what operating system and processor architecture are you using   go env     linux         what did you do           mkdir  tmp gopath     cd  tmp gopath     export gopath  tmp gopath     go get  u golang org x exp shiny screen         cd  gopath src golang org x exp shiny example basic     go run   main go    gopath  golang org x exp shiny driver internal     go      cannot find package  golang org x mobile event key  in any of       gopath  src golang org x exp shiny vendor golang org x mobile event key  vendor tree            usr local go src golang org x mobile event key  from  goroot       gopath  src golang org x mobile event key  from  gopath     gopath  src golang org x exp shiny driver   window go      cannot find package  golang org x mobile event lifecycle  in any of       gopath  src golang org x exp shiny vendor golang org x mobile event lifecycle  vendor tree            usr local go src golang org x mobile event lifecycle  from  goroot       gopath  src golang org x mobile event lifecycle  from  gopath     gopath  src golang org x exp shiny driver   screen go      cannot find package  golang org x mobile event mouse  in any of                  what did you expect to see   a nicer way to run the example s     i would propose to             cd  gopath src golang org x exp shiny     git mv example  examples         and remove all the      build ignore  build tags from the examples   so one could at least do           cd  examples basic     go get  d         to download all the dependencies in one go      i can send a cl      s    ,1
84766,10417820304.0,IssuesEvent,2019-09-15 01:58:47,golang/go,https://api.github.com/repos/golang/go,closed,net/http: Content-Length is not set in outgoing request when using ioutil.NopCloser,Documentation,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.13 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/1041775/Library/Caches/go-build""
GOENV=""/Users/1041775/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/1041775/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/Cellar/go/1.13/libexec""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/1.13/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/1041775/projects/js-scripts/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/d6/809nhvwd23nd_wryrw60j6hdms016p/T/go-build703352534=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->
Start a httpbin server locally.
<pre>
docker run -p 80:80 kennethreitz/httpbin
</pre>

Run the following program
```go
package main

import (
	""bytes""
	""io/ioutil""
	""log""
	""net/http""
)

func main() {
	reqBody := ioutil.NopCloser(bytes.NewBufferString(`{}`))
	req, err := http.NewRequest(""POST"", ""http://localhost:80/post"", reqBody)
	if err != nil {
		log.Fatalf(""Cannot create request: %v"", err)
	}
	res, err := http.DefaultClient.Do(req)
	if err != nil {
		log.Fatalf(""Cannot do: %v"", err)
	}
	defer res.Body.Close()
	resBody, err := ioutil.ReadAll(res.Body)
	if err != nil {
		log.Fatalf(""Cannot read body: %v"", err)
	}
	log.Printf(""Response Body: %s"", resBody)
}
```

### What did you expect to see?
Content-Length header is set when it is received by the server.


### What did you see instead?
Content-Length header is missing when it is received by the server.

<pre>
2019/09/14 12:55:00 Response Body: {
  ""args"": {}, 
  ""data"": ""{}"", 
  ""files"": {}, 
  ""form"": {}, 
  ""headers"": {
    ""Accept-Encoding"": ""gzip"", 
    ""Host"": ""localhost:80"", 
    ""Transfer-Encoding"": ""chunked"", 
    ""User-Agent"": ""Go-http-client/1.1""
  }, 
  ""json"": {}, 
  ""origin"": ""172.17.0.1"", 
  ""url"": ""http://localhost:80/post""
}
</pre>

Versus what I would receive if I use <pre>reqBody := bytes.NewBufferString(`{}`)</pre>.

<pre>
2019/09/14 12:55:22 Response Body: {
  ""args"": {}, 
  ""data"": ""{}"", 
  ""files"": {}, 
  ""form"": {}, 
  ""headers"": {
    ""Accept-Encoding"": ""gzip"", 
    ""Content-Length"": ""2"", 
    ""Host"": ""localhost:80"", 
    ""User-Agent"": ""Go-http-client/1.1""
  }, 
  ""json"": {}, 
  ""origin"": ""172.17.0.1"", 
  ""url"": ""http://localhost:80/post""
}
</pre>
",1.0,"net/http: Content-Length is not set in outgoing request when using ioutil.NopCloser - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.13 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/1041775/Library/Caches/go-build""
GOENV=""/Users/1041775/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/1041775/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/Cellar/go/1.13/libexec""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/1.13/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/1041775/projects/js-scripts/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/d6/809nhvwd23nd_wryrw60j6hdms016p/T/go-build703352534=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->
Start a httpbin server locally.
<pre>
docker run -p 80:80 kennethreitz/httpbin
</pre>

Run the following program
```go
package main

import (
	""bytes""
	""io/ioutil""
	""log""
	""net/http""
)

func main() {
	reqBody := ioutil.NopCloser(bytes.NewBufferString(`{}`))
	req, err := http.NewRequest(""POST"", ""http://localhost:80/post"", reqBody)
	if err != nil {
		log.Fatalf(""Cannot create request: %v"", err)
	}
	res, err := http.DefaultClient.Do(req)
	if err != nil {
		log.Fatalf(""Cannot do: %v"", err)
	}
	defer res.Body.Close()
	resBody, err := ioutil.ReadAll(res.Body)
	if err != nil {
		log.Fatalf(""Cannot read body: %v"", err)
	}
	log.Printf(""Response Body: %s"", resBody)
}
```

### What did you expect to see?
Content-Length header is set when it is received by the server.


### What did you see instead?
Content-Length header is missing when it is received by the server.

<pre>
2019/09/14 12:55:00 Response Body: {
  ""args"": {}, 
  ""data"": ""{}"", 
  ""files"": {}, 
  ""form"": {}, 
  ""headers"": {
    ""Accept-Encoding"": ""gzip"", 
    ""Host"": ""localhost:80"", 
    ""Transfer-Encoding"": ""chunked"", 
    ""User-Agent"": ""Go-http-client/1.1""
  }, 
  ""json"": {}, 
  ""origin"": ""172.17.0.1"", 
  ""url"": ""http://localhost:80/post""
}
</pre>

Versus what I would receive if I use <pre>reqBody := bytes.NewBufferString(`{}`)</pre>.

<pre>
2019/09/14 12:55:22 Response Body: {
  ""args"": {}, 
  ""data"": ""{}"", 
  ""files"": {}, 
  ""form"": {}, 
  ""headers"": {
    ""Accept-Encoding"": ""gzip"", 
    ""Content-Length"": ""2"", 
    ""Host"": ""localhost:80"", 
    ""User-Agent"": ""Go-http-client/1.1""
  }, 
  ""json"": {}, 
  ""origin"": ""172.17.0.1"", 
  ""url"": ""http://localhost:80/post""
}
</pre>
",1,net http  content length is not set in outgoing request when using ioutil nopcloser            what version of go are you using   go version            go version  go version     darwin             does this issue reproduce with the latest release   yes          what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   users   library caches go build   goenv   users   library application support go env   goexe     goflags     gohostarch      gohostos  darwin   gonoproxy     gonosumdb     goos  darwin   gopath   users   go   goprivate     goproxy     goroot   usr local cellar go     libexec   gosumdb  sum golang org   gotmpdir     gotooldir   usr local cellar go     libexec pkg tool darwin     gccgo  gccgo   ar  ar   cc  clang   cxx  clang     cgo enabled      gomod   users   projects js scripts go mod   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders       t go    tmp go build  gno record gcc switches  fno common             what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best        start a httpbin server locally      docker run  p     kennethreitz httpbin       run the following program     go  package main    import    	 bytes   	 io ioutil   	 log   	 net http        func main      	reqbody    ioutil nopcloser bytes newbufferstring         	req  err    http newrequest  post      reqbody   	if err    nil    		log fatalf  cannot create request   v   err   	   	res  err    http defaultclient do req   	if err    nil    		log fatalf  cannot do   v   err   	   	defer res body close    	resbody  err    ioutil readall res body   	if err    nil    		log fatalf  cannot read body   v   err   	   	log printf  response body   s   resbody                 what did you expect to see   content length header is set when it is received by the server           what did you see instead   content length header is missing when it is received by the server                    response body        args            data              files            form            headers           accept encoding    gzip          host    localhost            transfer encoding    chunked          user agent    go http client                 json            origin                   url               versus what i would receive if i use  reqbody    bytes newbufferstring                           response body        args            data              files            form            headers           accept encoding    gzip          content length               host    localhost            user agent    go http client                 json            origin                   url             ,1
16202,4028024656.0,IssuesEvent,2016-05-18 03:08:02,golang/go,https://api.github.com/repos/golang/go,closed,crypto/x509: typo in docs for x509.CreateCertificateRequest,Documentation,"Please answer these questions before submitting your issue. Thanks!

1. What version of Go are you using (`go version`)?
go version go1.6 darwin/amd64

2. What operating system and processor architecture are you using (`go env`)?
GOARCH=""amd64""
GOOS=""darwin""

3. What did you do?
(Use play.golang.org to provide a runnable example, if possible.)
Read https://golang.org/pkg/crypto/x509/#CreateCertificateRequest

4. What did you expect to see?
""CreateCertificateRequest creates a new certificate request based on a template.""

5. What did you see instead?
""CreateCertificateRequest creates a new certificate based on a template.""

This was really confusing for a minute because there is currently no exposed function in x509 that creates a certificate from a request, but that sentence implies that's what CreateCertificateRequest does, even though the name of the function makes it sort of obvious that's not what it does.
",1.0,"crypto/x509: typo in docs for x509.CreateCertificateRequest - Please answer these questions before submitting your issue. Thanks!

1. What version of Go are you using (`go version`)?
go version go1.6 darwin/amd64

2. What operating system and processor architecture are you using (`go env`)?
GOARCH=""amd64""
GOOS=""darwin""

3. What did you do?
(Use play.golang.org to provide a runnable example, if possible.)
Read https://golang.org/pkg/crypto/x509/#CreateCertificateRequest

4. What did you expect to see?
""CreateCertificateRequest creates a new certificate request based on a template.""

5. What did you see instead?
""CreateCertificateRequest creates a new certificate based on a template.""

This was really confusing for a minute because there is currently no exposed function in x509 that creates a certificate from a request, but that sentence implies that's what CreateCertificateRequest does, even though the name of the function makes it sort of obvious that's not what it does.
",1,crypto    typo in docs for   createcertificaterequest   please answer these questions before submitting your issue  thanks        what version of go are you using   go version     go version     darwin         what operating system and processor architecture are you using   go env     goarch      goos  darwin        what did you do    use play golang org to provide a runnable example  if possible    read         what did you expect to see    createcertificaterequest creates a new certificate request based on a template         what did you see instead    createcertificaterequest creates a new certificate based on a template      this was really confusing for a minute because there is currently no exposed function in   that creates a certificate from a request  but that sentence implies that s what createcertificaterequest does  even though the name of the function makes it sort of obvious that s not what it does   ,1
38126,6660478720.0,IssuesEvent,2017-10-02 00:34:49,golang/go,https://api.github.com/repos/golang/go,closed,bytes: docs do not always state that UTF-8 encoding is used,Documentation,"Not all functions in the bytes package that operate on strings and runes specify that UTF-8 encoding is used. From an initial glance, it appears the following functions are missing that information from their documentation:

- ContainsRune
- Count
- Fields
- Runes
- Title
- ToLower
- ToLowerSpecial
- ToTitle
- ToTitleSpecial
- ToUpper
- ToUpperSpecial
- TrimSpace

Does it make sense to include that detail in each of the above functions?",1.0,"bytes: docs do not always state that UTF-8 encoding is used - Not all functions in the bytes package that operate on strings and runes specify that UTF-8 encoding is used. From an initial glance, it appears the following functions are missing that information from their documentation:

- ContainsRune
- Count
- Fields
- Runes
- Title
- ToLower
- ToLowerSpecial
- ToTitle
- ToTitleSpecial
- ToUpper
- ToUpperSpecial
- TrimSpace

Does it make sense to include that detail in each of the above functions?",1,bytes  docs do not always state that utf   encoding is used   not all functions in the bytes package that operate on strings and runes specify that utf   encoding is used  from an initial glance  it appears the following functions are missing that information from their documentation       containsrune    count    fields    runes    title    tolower    tolowerspecial    totitle    totitlespecial    toupper    toupperspecial    trimspace    does it make sense to include that detail in each of the above functions ,1
126070,12281264895.0,IssuesEvent,2020-05-08 15:32:41,golang/go,https://api.github.com/repos/golang/go,reopened,cmd/go: document build constraints in 'go help',Documentation NeedsFix,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
go version devel +a50c3ffbd4 linux/amd64
</pre>

### Does this issue reproduce with the latest release?



### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/usr/local/google/home/pjw/.cache/go-build""
GOENV=""/usr/local/google/home/pjw/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""

</pre></details>

### What did you do?
In x/tools/internal/lsp/span/uri_windows_test.go I removed // +build window, and renamed the test function to TestURIA (to avoid conflicts with uri_test.go)

I then ran go test -run URI .
### What did you expect to see?
I expected to see it run TestURI (from uri_test.go) and TestURIA (from uri_windows_test.go)

### What did you see instead?
It just ran TestURI

[If I rename uri_window_test.go then go test will run TestURIA]",1.0,"cmd/go: document build constraints in 'go help' - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
go version devel +a50c3ffbd4 linux/amd64
</pre>

### Does this issue reproduce with the latest release?



### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/usr/local/google/home/pjw/.cache/go-build""
GOENV=""/usr/local/google/home/pjw/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""

</pre></details>

### What did you do?
In x/tools/internal/lsp/span/uri_windows_test.go I removed // +build window, and renamed the test function to TestURIA (to avoid conflicts with uri_test.go)

I then ran go test -run URI .
### What did you expect to see?
I expected to see it run TestURI (from uri_test.go) and TestURIA (from uri_windows_test.go)

### What did you see instead?
It just ran TestURI

[If I rename uri_window_test.go then go test will run TestURIA]",1,cmd go  document build constraints in  go help          please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version          go version devel    linux             does this issue reproduce with the latest release             what operating system and processor architecture are you using   go env          go env  output     goarch      gobin     gocache   usr local google home pjw  cache go build   goenv   usr local google home pjw  config go env   goexe     goflags     gohostarch      gohostos  linux   goinsecure     gonoproxy     gonosumdb     goos  linux               what did you do   in x tools internal lsp span uri windows test go i removed     build window  and renamed the test function to testuria  to avoid conflicts with uri test go     i then ran go test  run uri        what did you expect to see   i expected to see it run testuri  from uri test go  and testuria  from uri windows test go         what did you see instead   it just ran testuri     ,1
42987,23064298306.0,IssuesEvent,2022-07-25 12:43:00,qbittorrent/qBittorrent,https://api.github.com/repos/qbittorrent/qBittorrent,closed,4.4.2 Not Downloading,Performance Can't reproduce,"### qBittorrent & operating system versions

qBittorrent: 4.4.2 x64
Operating System: Windows 10 Enterprise 21H2 x64
Qt: 5.15.2

### What is the problem?

The torrent is downloading at 15 kbps even after waiting for a while.

As soon as I reinstall version 4.4.1 the torrent immediately starts to download at 5 MB/sec.

I checked the trackers and they appear to be ""working"".

### Steps to reproduce

1. Install version 4.4.2.
2. Observe the torrent being downloaded at extremely low speed.
3. Reinstall version 4.4.1.
4. Observe the torrent being downloaded at fast speed.

### Additional context

_No response_

### Log(s) & preferences file(s)

_No response_",True,"4.4.2 Not Downloading - ### qBittorrent & operating system versions

qBittorrent: 4.4.2 x64
Operating System: Windows 10 Enterprise 21H2 x64
Qt: 5.15.2

### What is the problem?

The torrent is downloading at 15 kbps even after waiting for a while.

As soon as I reinstall version 4.4.1 the torrent immediately starts to download at 5 MB/sec.

I checked the trackers and they appear to be ""working"".

### Steps to reproduce

1. Install version 4.4.2.
2. Observe the torrent being downloaded at extremely low speed.
3. Reinstall version 4.4.1.
4. Observe the torrent being downloaded at fast speed.

### Additional context

_No response_

### Log(s) & preferences file(s)

_No response_",0,      not downloading       qbittorrent   operating system versions  qbittorrent           operating system  windows   enterprise      qt             what is the problem   the torrent is downloading at   kbps even after waiting for a while     as soon as i reinstall version       the torrent immediately starts to download at   mb sec     i checked the trackers and they appear to be  working        steps to reproduce     install version            observe the torrent being downloaded at extremely low speed      reinstall version            observe the torrent being downloaded at fast speed       additional context   no response       log s    preferences file s    no response ,0
197103,14908616384.0,IssuesEvent,2021-01-22 06:18:56,cockroachdb/cockroach,https://api.github.com/repos/cockroachdb/cockroach,opened,sql/opt/exec/execbuilder: TestExecBuild failed,C-test-failure O-robot branch-master,"[(sql/opt/exec/execbuilder).TestExecBuild failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=2604753&tab=buildLog) on [master@baf34b241c9ee27530f0a3a988149bfd7cca3f6d](https://github.com/cockroachdb/cockroach/commits/baf34b241c9ee27530f0a3a988149bfd7cca3f6d):

```
    logic.go:2528: 
        
        testdata/inverted_join_multi_column:30: EXPLAIN SELECT j1.k
        FROM j1 INNER INVERTED JOIN j2
        ON i IN (10, 20) AND j2.j @> j1.j
        expected success, but found
        (XX000) internal error: exec columns do not match opt columns: expected (1,2,5,6,14), got (1,2,5,6)
        relational.go:341: in buildRelational()
        DETAIL: stack trace:
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/execbuilder/relational.go:341: buildRelational()
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/execbuilder/relational.go:1448: buildLookupJoin()
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/execbuilder/relational.go:218: buildRelational()
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/execbuilder/relational.go:683: buildProject()
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/execbuilder/relational.go:199: buildRelational()
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/execbuilder/builder.go:173: build()
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/execbuilder/builder.go:135: Build()
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/execbuilder/statement.go:127: func1()
        github.com/cockroachdb/cockroach/pkg/sql/opt_exec_factory.go:1881: ConstructExplain()
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/explain/explain_factory.og.go:880: ConstructExplain()
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/execbuilder/statement.go:120: buildExplain()
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/execbuilder/relational.go:275: buildRelational()
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/execbuilder/builder.go:173: build()
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/execbuilder/builder.go:135: Build()
        github.com/cockroachdb/cockroach/pkg/sql/plan_opt.go:565: runExecBuilder()
        github.com/cockroachdb/cockroach/pkg/sql/plan_opt.go:261: makeOptimizerPlan()
        github.com/cockroachdb/cockroach/pkg/sql/conn_executor_exec.go:910: makeExecPlan()
        github.com/cockroachdb/cockroach/pkg/sql/conn_executor_exec.go:796: dispatchToExecutionEngine()
        github.com/cockroachdb/cockroach/pkg/sql/conn_executor_exec.go:641: execStmtInOpenState()
        github.com/cockroachdb/cockroach/pkg/sql/conn_executor_exec.go:119: execStmt()
        github.com/cockroachdb/cockroach/pkg/sql/conn_executor.go:1445: func1()
        github.com/cockroachdb/cockroach/pkg/sql/conn_executor.go:1447: execCmd()
        github.com/cockroachdb/cockroach/pkg/sql/conn_executor.go:1372: run()
        github.com/cockroachdb/cockroach/pkg/sql/conn_executor.go:481: ServeConn()
        github.com/cockroachdb/cockroach/pkg/sql/pgwire/conn.go:631: func1()
        runtime/asm_amd64.s:1374: goexit()
        
        NOTE: internal errors may have more details in logs. Use -show-logs.
E210122 06:12:20.610674 102683 sql/logictest/logic.go:3519  
pq: internal error: exec columns do not match opt columns: expected (1,2,5,6,14), got (1,2,5,6)
    logic.go:2261: 
         pq: internal error: exec columns do not match opt columns: expected (1,2,5,6,14), got (1,2,5,6)
--- done: testdata/inverted_join_multi_column with config local: 5 tests, 2 failures
E210122 06:12:20.611785 102683 sql/logictest/logic.go:3544  testdata/inverted_join_multi_column:57: too many errors encountered, skipping the rest of the input
    logic.go:3087: 
        testdata/inverted_join_multi_column:57: error while processing
    logic.go:3087: testdata/inverted_join_multi_column:57: too many errors encountered, skipping the rest of the input
E210122 06:12:20.615009 103175 sql/stats/automatic_stats.go:302  failed to refresh stats: node unavailable; try another peer
        --- FAIL: TestExecBuild/local/inverted_join_multi_column (1.07s)
=== RUN   TestExecBuild/local
    --- FAIL: TestExecBuild/local (239.76s)

```

<details><summary>More</summary><p>


```
make stressrace TESTS=TestExecBuild PKG=./pkg/sql/opt/exec/execbuilder TESTTIMEOUT=5m STRESSFLAGS='-timeout 5m' 2>&1
```


[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2ATestExecBuild.%2A&sort=title&restgroup=false&display=lastcommented+project)
<sub>powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub></p></details>
",1.0,"sql/opt/exec/execbuilder: TestExecBuild failed - [(sql/opt/exec/execbuilder).TestExecBuild failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=2604753&tab=buildLog) on [master@baf34b241c9ee27530f0a3a988149bfd7cca3f6d](https://github.com/cockroachdb/cockroach/commits/baf34b241c9ee27530f0a3a988149bfd7cca3f6d):

```
    logic.go:2528: 
        
        testdata/inverted_join_multi_column:30: EXPLAIN SELECT j1.k
        FROM j1 INNER INVERTED JOIN j2
        ON i IN (10, 20) AND j2.j @> j1.j
        expected success, but found
        (XX000) internal error: exec columns do not match opt columns: expected (1,2,5,6,14), got (1,2,5,6)
        relational.go:341: in buildRelational()
        DETAIL: stack trace:
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/execbuilder/relational.go:341: buildRelational()
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/execbuilder/relational.go:1448: buildLookupJoin()
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/execbuilder/relational.go:218: buildRelational()
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/execbuilder/relational.go:683: buildProject()
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/execbuilder/relational.go:199: buildRelational()
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/execbuilder/builder.go:173: build()
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/execbuilder/builder.go:135: Build()
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/execbuilder/statement.go:127: func1()
        github.com/cockroachdb/cockroach/pkg/sql/opt_exec_factory.go:1881: ConstructExplain()
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/explain/explain_factory.og.go:880: ConstructExplain()
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/execbuilder/statement.go:120: buildExplain()
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/execbuilder/relational.go:275: buildRelational()
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/execbuilder/builder.go:173: build()
        github.com/cockroachdb/cockroach/pkg/sql/opt/exec/execbuilder/builder.go:135: Build()
        github.com/cockroachdb/cockroach/pkg/sql/plan_opt.go:565: runExecBuilder()
        github.com/cockroachdb/cockroach/pkg/sql/plan_opt.go:261: makeOptimizerPlan()
        github.com/cockroachdb/cockroach/pkg/sql/conn_executor_exec.go:910: makeExecPlan()
        github.com/cockroachdb/cockroach/pkg/sql/conn_executor_exec.go:796: dispatchToExecutionEngine()
        github.com/cockroachdb/cockroach/pkg/sql/conn_executor_exec.go:641: execStmtInOpenState()
        github.com/cockroachdb/cockroach/pkg/sql/conn_executor_exec.go:119: execStmt()
        github.com/cockroachdb/cockroach/pkg/sql/conn_executor.go:1445: func1()
        github.com/cockroachdb/cockroach/pkg/sql/conn_executor.go:1447: execCmd()
        github.com/cockroachdb/cockroach/pkg/sql/conn_executor.go:1372: run()
        github.com/cockroachdb/cockroach/pkg/sql/conn_executor.go:481: ServeConn()
        github.com/cockroachdb/cockroach/pkg/sql/pgwire/conn.go:631: func1()
        runtime/asm_amd64.s:1374: goexit()
        
        NOTE: internal errors may have more details in logs. Use -show-logs.
E210122 06:12:20.610674 102683 sql/logictest/logic.go:3519  
pq: internal error: exec columns do not match opt columns: expected (1,2,5,6,14), got (1,2,5,6)
    logic.go:2261: 
         pq: internal error: exec columns do not match opt columns: expected (1,2,5,6,14), got (1,2,5,6)
--- done: testdata/inverted_join_multi_column with config local: 5 tests, 2 failures
E210122 06:12:20.611785 102683 sql/logictest/logic.go:3544  testdata/inverted_join_multi_column:57: too many errors encountered, skipping the rest of the input
    logic.go:3087: 
        testdata/inverted_join_multi_column:57: error while processing
    logic.go:3087: testdata/inverted_join_multi_column:57: too many errors encountered, skipping the rest of the input
E210122 06:12:20.615009 103175 sql/stats/automatic_stats.go:302  failed to refresh stats: node unavailable; try another peer
        --- FAIL: TestExecBuild/local/inverted_join_multi_column (1.07s)
=== RUN   TestExecBuild/local
    --- FAIL: TestExecBuild/local (239.76s)

```

<details><summary>More</summary><p>


```
make stressrace TESTS=TestExecBuild PKG=./pkg/sql/opt/exec/execbuilder TESTTIMEOUT=5m STRESSFLAGS='-timeout 5m' 2>&1
```


[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2ATestExecBuild.%2A&sort=title&restgroup=false&display=lastcommented+project)
<sub>powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub></p></details>
",0,sql opt exec execbuilder  testexecbuild failed       on              logic go                      testdata inverted join multi column    explain select   k         from   inner inverted join           on i in        and   j      j         expected success  but found             internal error  exec columns do not match opt columns  expected              got                   relational go    in buildrelational           detail  stack trace          github com cockroachdb cockroach pkg sql opt exec execbuilder relational go    buildrelational           github com cockroachdb cockroach pkg sql opt exec execbuilder relational go    buildlookupjoin           github com cockroachdb cockroach pkg sql opt exec execbuilder relational go    buildrelational           github com cockroachdb cockroach pkg sql opt exec execbuilder relational go    buildproject           github com cockroachdb cockroach pkg sql opt exec execbuilder relational go    buildrelational           github com cockroachdb cockroach pkg sql opt exec execbuilder builder go    build           github com cockroachdb cockroach pkg sql opt exec execbuilder builder go    build           github com cockroachdb cockroach pkg sql opt exec execbuilder statement go                github com cockroachdb cockroach pkg sql opt exec factory go    constructexplain           github com cockroachdb cockroach pkg sql opt exec explain explain factory og go    constructexplain           github com cockroachdb cockroach pkg sql opt exec execbuilder statement go    buildexplain           github com cockroachdb cockroach pkg sql opt exec execbuilder relational go    buildrelational           github com cockroachdb cockroach pkg sql opt exec execbuilder builder go    build           github com cockroachdb cockroach pkg sql opt exec execbuilder builder go    build           github com cockroachdb cockroach pkg sql plan opt go    runexecbuilder           github com cockroachdb cockroach pkg sql plan opt go    makeoptimizerplan           github com cockroachdb cockroach pkg sql conn executor exec go    makeexecplan           github com cockroachdb cockroach pkg sql conn executor exec go    dispatchtoexecutionengine           github com cockroachdb cockroach pkg sql conn executor exec go    execstmtinopenstate           github com cockroachdb cockroach pkg sql conn executor exec go    execstmt           github com cockroachdb cockroach pkg sql conn executor go                github com cockroachdb cockroach pkg sql conn executor go    execcmd           github com cockroachdb cockroach pkg sql conn executor go    run           github com cockroachdb cockroach pkg sql conn executor go    serveconn           github com cockroachdb cockroach pkg sql pgwire conn go                runtime asm   s    goexit                    note  internal errors may have more details in logs  use  show logs              sql logictest logic go     pq  internal error  exec columns do not match opt columns  expected              got               logic go              pq  internal error  exec columns do not match opt columns  expected              got               done  testdata inverted join multi column with config local    tests    failures             sql logictest logic go    testdata inverted join multi column    too many errors encountered  skipping the rest of the input     logic go             testdata inverted join multi column    error while processing     logic go    testdata inverted join multi column    too many errors encountered  skipping the rest of the input             sql stats automatic stats go    failed to refresh stats  node unavailable  try another peer             fail  testexecbuild local inverted join multi column           run   testexecbuild local         fail  testexecbuild local               more         make stressrace tests testexecbuild pkg   pkg sql opt exec execbuilder testtimeout   stressflags   timeout                    powered by     ,0
43907,2894004777.0,IssuesEvent,2015-06-15 20:57:13,pirminrehm/neddit,https://api.github.com/repos/pirminrehm/neddit,opened,Undo/Logging,priority todo,"Logging 2 display at client:

```
> db.loggings.find().pretty()
{
	""_id"" : ObjectId(""557f34e21e3f37564d6ef114""),
	""operatorName"" : ""Neddit Test 1"",
	""modifiedAction"" : ""Update"",
	""modifiedType"" : ""Config"",
	""modifiedIdent"" : ""MainConfig"",
	""modifiedOld"" : {
		""hostTypes"" : [
			""printer"",
			""client"",
			""server""
		],
		""users"" : [
			{
				""_id"" : ""557f34e11e3f37564d6ef113"",
				""superAdmin"" : true,
				""validated"" : true,
				""token"" : ""neddit-test1"",
				""email"" : ""neddit-test1@7kw.de"",
				""name"" : ""Neddit Test 1""
			},
			{
				""_id"" : ""557f34e11e3f37564d6ef112"",
				""superAdmin"" : false,
				""validated"" : true,
				""token"" : ""neddit-test2"",
				""email"" : ""neddit-test2@7kw.de"",
				""name"" : ""Neddit Test 2""
			}
		],
		""__v"" : 0,
		""poolNetwork"" : ""876b9f348270a76445a02c21"",
		""examNetwork"" : ""786b9f348270a76445a02c12"",
		""_id"" : ""557f34e11e3f37564d6ef111""
	},
	""modifiedNew"" : {
		""hostTypes"" : [
			""printer"",
			""client"",
			""server""
		],
		""users"" : [
			{
				""_id"" : ""557f34e11e3f37564d6ef113"",
				""superAdmin"" : true,
				""validated"" : true,
				""token"" : ""neddit-test1"",
				""email"" : ""neddit-test1@7kw.de"",
				""name"" : ""Neddit Test 1""
			},
			{
				""_id"" : ""557f34e11e3f37564d6ef112"",
				""superAdmin"" : false,
				""validated"" : true,
				""token"" : ""neddit-test2"",
				""email"" : ""neddit-test2@7kw.de"",
				""name"" : ""Neddit Test 2""
			}
		],
		""__v"" : 0,
		""poolNetwork"" : ""356b9f348270a76445a02ca9"",
		""examNetwork"" : ""256b9f348270a76445a02cab"",
		""_id"" : ""557f34e11e3f37564d6ef111""
	},
	""__v"" : 0
}


{
	""_id"" : ObjectId(""557f377e342f214150d32d75""),
	""operatorName"" : ""Neddit Test 1"",
	""modifiedAction"" : ""Update"",
	""modifiedType"" : ""Network"",
	""modifiedIdent"" : ""testing.mi.hdm-stuttgart.de"",
	""modifiedOld"" : {
		""nameservers"" : [ ],
		""__v"" : 0,
		""domain"" : ""testing.mi.hdm-stuttgart.de"",
		""gatewayIp3"" : 15,
		""netIdIp3"" : 14,
		""mask"" : 13,
		""ip2"" : 12,
		""ip1"" : 11,
		""ip0"" : 10,
		""_id"" : ""557f377e342f214150d32d63""
	},
	""modifiedNew"" : {
		""nameservers"" : [ ],
		""__v"" : 0,
		""domain"" : ""testing.mi.hdm-stuttgart.de"",
		""gatewayIp3"" : 15,
		""netIdIp3"" : 14,
		""mask"" : 13,
		""ip2"" : 12,
		""ip1"" : 11,
		""ip0"" : 255,
		""_id"" : ""557f377e342f214150d32d63""
	},
	""__v"" : 0
}



{
	""_id"" : ObjectId(""557f38e85c74ce71517a1214""),
	""operatorName"" : ""Neddit Test 1"",
	""modifiedAction"" : ""Insert"",
	""modifiedType"" : ""Network"",
	""modifiedIdent"" : ""stud.mi.hdm-stuttgart.de"",
	""modifiedOld"" : """",
	""modifiedNew"" : {
		""nameservers"" : [ ],
		""_id"" : ""557f38e85c74ce71517a1213"",
		""comment"" : ""test"",
		""pxeFilename"" : """",
		""pxeNextServer"" : """",
		""dhcpMax"" : 0,
		""dhcpMin"" : 0,
		""domain"" : ""stud.mi.hdm-stuttgart.de"",
		""gatewayIp3"" : 30,
		""netIdIp3"" : 0,
		""mask"" : 27,
		""ip2"" : 73,
		""ip1"" : 52,
		""ip0"" : 141,
		""__v"" : 0
	},
	""__v"" : 0
}
> 
```",1.0,"Undo/Logging - Logging 2 display at client:

```
> db.loggings.find().pretty()
{
	""_id"" : ObjectId(""557f34e21e3f37564d6ef114""),
	""operatorName"" : ""Neddit Test 1"",
	""modifiedAction"" : ""Update"",
	""modifiedType"" : ""Config"",
	""modifiedIdent"" : ""MainConfig"",
	""modifiedOld"" : {
		""hostTypes"" : [
			""printer"",
			""client"",
			""server""
		],
		""users"" : [
			{
				""_id"" : ""557f34e11e3f37564d6ef113"",
				""superAdmin"" : true,
				""validated"" : true,
				""token"" : ""neddit-test1"",
				""email"" : ""neddit-test1@7kw.de"",
				""name"" : ""Neddit Test 1""
			},
			{
				""_id"" : ""557f34e11e3f37564d6ef112"",
				""superAdmin"" : false,
				""validated"" : true,
				""token"" : ""neddit-test2"",
				""email"" : ""neddit-test2@7kw.de"",
				""name"" : ""Neddit Test 2""
			}
		],
		""__v"" : 0,
		""poolNetwork"" : ""876b9f348270a76445a02c21"",
		""examNetwork"" : ""786b9f348270a76445a02c12"",
		""_id"" : ""557f34e11e3f37564d6ef111""
	},
	""modifiedNew"" : {
		""hostTypes"" : [
			""printer"",
			""client"",
			""server""
		],
		""users"" : [
			{
				""_id"" : ""557f34e11e3f37564d6ef113"",
				""superAdmin"" : true,
				""validated"" : true,
				""token"" : ""neddit-test1"",
				""email"" : ""neddit-test1@7kw.de"",
				""name"" : ""Neddit Test 1""
			},
			{
				""_id"" : ""557f34e11e3f37564d6ef112"",
				""superAdmin"" : false,
				""validated"" : true,
				""token"" : ""neddit-test2"",
				""email"" : ""neddit-test2@7kw.de"",
				""name"" : ""Neddit Test 2""
			}
		],
		""__v"" : 0,
		""poolNetwork"" : ""356b9f348270a76445a02ca9"",
		""examNetwork"" : ""256b9f348270a76445a02cab"",
		""_id"" : ""557f34e11e3f37564d6ef111""
	},
	""__v"" : 0
}


{
	""_id"" : ObjectId(""557f377e342f214150d32d75""),
	""operatorName"" : ""Neddit Test 1"",
	""modifiedAction"" : ""Update"",
	""modifiedType"" : ""Network"",
	""modifiedIdent"" : ""testing.mi.hdm-stuttgart.de"",
	""modifiedOld"" : {
		""nameservers"" : [ ],
		""__v"" : 0,
		""domain"" : ""testing.mi.hdm-stuttgart.de"",
		""gatewayIp3"" : 15,
		""netIdIp3"" : 14,
		""mask"" : 13,
		""ip2"" : 12,
		""ip1"" : 11,
		""ip0"" : 10,
		""_id"" : ""557f377e342f214150d32d63""
	},
	""modifiedNew"" : {
		""nameservers"" : [ ],
		""__v"" : 0,
		""domain"" : ""testing.mi.hdm-stuttgart.de"",
		""gatewayIp3"" : 15,
		""netIdIp3"" : 14,
		""mask"" : 13,
		""ip2"" : 12,
		""ip1"" : 11,
		""ip0"" : 255,
		""_id"" : ""557f377e342f214150d32d63""
	},
	""__v"" : 0
}



{
	""_id"" : ObjectId(""557f38e85c74ce71517a1214""),
	""operatorName"" : ""Neddit Test 1"",
	""modifiedAction"" : ""Insert"",
	""modifiedType"" : ""Network"",
	""modifiedIdent"" : ""stud.mi.hdm-stuttgart.de"",
	""modifiedOld"" : """",
	""modifiedNew"" : {
		""nameservers"" : [ ],
		""_id"" : ""557f38e85c74ce71517a1213"",
		""comment"" : ""test"",
		""pxeFilename"" : """",
		""pxeNextServer"" : """",
		""dhcpMax"" : 0,
		""dhcpMin"" : 0,
		""domain"" : ""stud.mi.hdm-stuttgart.de"",
		""gatewayIp3"" : 30,
		""netIdIp3"" : 0,
		""mask"" : 27,
		""ip2"" : 73,
		""ip1"" : 52,
		""ip0"" : 141,
		""__v"" : 0
	},
	""__v"" : 0
}
> 
```",0,undo logging   logging   display at client            db loggings find   pretty       	  id    objectid        	 operatorname     neddit test      	 modifiedaction     update    	 modifiedtype     config    	 modifiedident     mainconfig    	 modifiedold       		 hosttypes       			 printer    			 client    			 server   		    		 users       			   				  id          				 superadmin    true   				 validated    true   				 token     neddit      				 email     neddit     de    				 name     neddit test     			    			   				  id          				 superadmin    false   				 validated    true   				 token     neddit      				 email     neddit     de    				 name     neddit test     			   		    		   v        		 poolnetwork          		 examnetwork          		  id         	    	 modifiednew       		 hosttypes       			 printer    			 client    			 server   		    		 users       			   				  id          				 superadmin    true   				 validated    true   				 token     neddit      				 email     neddit     de    				 name     neddit test     			    			   				  id          				 superadmin    false   				 validated    true   				 token     neddit      				 email     neddit     de    				 name     neddit test     			   		    		   v        		 poolnetwork          		 examnetwork          		  id         	    	   v                 	  id    objectid        	 operatorname     neddit test      	 modifiedaction     update    	 modifiedtype     network    	 modifiedident     testing mi hdm stuttgart de    	 modifiedold       		 nameservers        		   v        		 domain     testing mi hdm stuttgart de    		          		          		 mask        		          		          		          		  id         	    	 modifiednew       		 nameservers        		   v        		 domain     testing mi hdm stuttgart de    		          		          		 mask        		          		          		          		  id         	    	   v                   	  id    objectid        	 operatorname     neddit test      	 modifiedaction     insert    	 modifiedtype     network    	 modifiedident     stud mi hdm stuttgart de    	 modifiedold         	 modifiednew       		 nameservers        		  id          		 comment     test    		 pxefilename         		 pxenextserver         		 dhcpmax        		 dhcpmin        		 domain     stud mi hdm stuttgart de    		          		          		 mask        		          		          		          		   v       	    	   v                 ,0
49016,7469648806.0,IssuesEvent,2018-04-03 00:03:10,golang/go,https://api.github.com/repos/golang/go,closed,install: Windows: set GOPATH from installer and optionally add GOPATH\bin to PATH,Documentation NeedsFix OS-Windows help wanted,"I ran the Go 1.9.2 Windows installers 32 bit on Windows XP and 64 bit on Windows 7.

The default `GOPATH` on Windows is now (starting with Go 1.8 I think) `%USERPROFILE%\go` but this is not set as an environment variable. It seems to just be assumed by the tools if the environment variable is not set.
The problem with that is that I cannot open `cmd` and type `cd %GOPATH%\bin` for example. This is very inconvenient and confusing to new Go users who read about `GOPATH` everywhere in the docs.

Similarly it would be a very user-friendly feature if the Windows installer asked you, after setting `GOPATH`, if it should add `%GOPATH%\bin` to your `PATH` to be able to run Go programs that they got with `go get` from `cmd` directly. This option and the explanation would be way better right there in the installer instead of having it appear on the download page as mentioned in #18583. New users might not notice the redirect (or have it disabled in the browser) or care to read it. Honestly, who reads the manual before trying things out?

Having a Windows installer is all about convenience so I think we should provide the most common tasks right in it.

This is not only for new users either. I have been using Go for years and installed it on a couple of Windows systems. After the second time I knew what I had to do but it is still tedious. Yesterday I wanted to try compiling my game on a fresh Windows, ideally I would just install Git, install Go (which would set `GOPATH` and add `%GOPATH%\bin` to `PATH`) and `go get` it. Instead I had to go through the arcane Windows menus to get through to the environment variables. (Linux is not better, every dekstop has a different hidden file and syntax to set this, but I expect Linux users to know this stuff better).

In summary my proposal is to add

- one page for setting `GOPATH`, along with a short explanation
- one page for adding `%GOPATH%\bin` to `PATH`, again with a short explanation

to the Windows installer.",1.0,"install: Windows: set GOPATH from installer and optionally add GOPATH\bin to PATH - I ran the Go 1.9.2 Windows installers 32 bit on Windows XP and 64 bit on Windows 7.

The default `GOPATH` on Windows is now (starting with Go 1.8 I think) `%USERPROFILE%\go` but this is not set as an environment variable. It seems to just be assumed by the tools if the environment variable is not set.
The problem with that is that I cannot open `cmd` and type `cd %GOPATH%\bin` for example. This is very inconvenient and confusing to new Go users who read about `GOPATH` everywhere in the docs.

Similarly it would be a very user-friendly feature if the Windows installer asked you, after setting `GOPATH`, if it should add `%GOPATH%\bin` to your `PATH` to be able to run Go programs that they got with `go get` from `cmd` directly. This option and the explanation would be way better right there in the installer instead of having it appear on the download page as mentioned in #18583. New users might not notice the redirect (or have it disabled in the browser) or care to read it. Honestly, who reads the manual before trying things out?

Having a Windows installer is all about convenience so I think we should provide the most common tasks right in it.

This is not only for new users either. I have been using Go for years and installed it on a couple of Windows systems. After the second time I knew what I had to do but it is still tedious. Yesterday I wanted to try compiling my game on a fresh Windows, ideally I would just install Git, install Go (which would set `GOPATH` and add `%GOPATH%\bin` to `PATH`) and `go get` it. Instead I had to go through the arcane Windows menus to get through to the environment variables. (Linux is not better, every dekstop has a different hidden file and syntax to set this, but I expect Linux users to know this stuff better).

In summary my proposal is to add

- one page for setting `GOPATH`, along with a short explanation
- one page for adding `%GOPATH%\bin` to `PATH`, again with a short explanation

to the Windows installer.",1,install  windows  set gopath from installer and optionally add gopath bin to path   i ran the go       windows installers   bit on windows xp and   bit on windows       the default  gopath  on windows is now  starting with go     i think    userprofile  go  but this is not set as an environment variable  it seems to just be assumed by the tools if the environment variable is not set   the problem with that is that i cannot open  cmd  and type  cd  gopath  bin  for example  this is very inconvenient and confusing to new go users who read about  gopath  everywhere in the docs     similarly it would be a very user friendly feature if the windows installer asked you  after setting  gopath   if it should add   gopath  bin  to your  path  to be able to run go programs that they got with  go get  from  cmd  directly  this option and the explanation would be way better right there in the installer instead of having it appear on the download page as mentioned in     new users might not notice the redirect  or have it disabled in the browser  or care to read it  honestly  who reads the manual before trying things out     having a windows installer is all about convenience so i think we should provide the most common tasks right in it     this is not only for new users either  i have been using go for years and installed it on a couple of windows systems  after the second time i knew what i had to do but it is still tedious  yesterday i wanted to try compiling my game on a fresh windows  ideally i would just install git  install go  which would set  gopath  and add   gopath  bin  to  path   and  go get  it  instead i had to go through the arcane windows menus to get through to the environment variables   linux is not better  every dekstop has a different hidden file and syntax to set this  but i expect linux users to know this stuff better      in summary my proposal is to add      one page for setting  gopath   along with a short explanation    one page for adding   gopath  bin  to  path   again with a short explanation    to the windows installer ,1
29931,7135276175.0,IssuesEvent,2018-01-23 00:12:27,nmrih/source-game,https://api.github.com/repos/nmrih/source-game,opened,Achievement: review ARMY_OF_DEAD logic,code reviewed,"Check army of dead logic in the code. It appears to be correct and is likely already shipped. This means if the logic for this achievement is sound, we can just add it in.",1.0,"Achievement: review ARMY_OF_DEAD logic - Check army of dead logic in the code. It appears to be correct and is likely already shipped. This means if the logic for this achievement is sound, we can just add it in.",0,achievement  review army of dead logic   check army of dead logic in the code  it appears to be correct and is likely already shipped  this means if the logic for this achievement is sound  we can just add it in ,0
18766,5706812691.0,IssuesEvent,2017-04-18 12:24:06,chrisblakley/Nebula,https://api.github.com/repos/chrisblakley/Nebula,closed,"Add example for creating, filling, and sorting custom column headers in WP Admin",Backend (Server) WP Admin / Shortcode / Widget,"Here is an example for a post type of `faqs`.

``` php
//Add ID column on post/page listings
add_filter('manage_faqs_posts_columns', 'nebula_faq_columns_head');
function nebula_faq_columns_head($defaults){
    $defaults['faq-category'] = 'Category';
    return $defaults;
}

add_action('manage_posts_custom_column', 'nebula_faq_columns_content', 15, 3);
function nebula_faq_columns_content($column_name, $id){
    if ( $column_name == 'faq-category' ){
        $post = get_post();
        echo $post->custom_fields[""faq_category""][0];
    }
}

//Sortable columns in Product admin
add_filter('manage_edit-faqs_sortable_columns', 'nebula_faq_sortable_columns');
function nebula_faq_sortable_columns($columns) {
    $columns['faq-category'] = 'Category';
    return $columns;
}
add_action('pre_get_posts', 'nebula_faq_columns_orderby');
function nebula_faq_columns_orderby($query) {
    $orderby = $query->get('orderby');

    if ( $orderby == 'faq-category' ) {
        $query->set('meta_key', 'faq_category');
        $query->set('orderby', 'meta_value');
    }
}
```
",1.0,"Add example for creating, filling, and sorting custom column headers in WP Admin - Here is an example for a post type of `faqs`.

``` php
//Add ID column on post/page listings
add_filter('manage_faqs_posts_columns', 'nebula_faq_columns_head');
function nebula_faq_columns_head($defaults){
    $defaults['faq-category'] = 'Category';
    return $defaults;
}

add_action('manage_posts_custom_column', 'nebula_faq_columns_content', 15, 3);
function nebula_faq_columns_content($column_name, $id){
    if ( $column_name == 'faq-category' ){
        $post = get_post();
        echo $post->custom_fields[""faq_category""][0];
    }
}

//Sortable columns in Product admin
add_filter('manage_edit-faqs_sortable_columns', 'nebula_faq_sortable_columns');
function nebula_faq_sortable_columns($columns) {
    $columns['faq-category'] = 'Category';
    return $columns;
}
add_action('pre_get_posts', 'nebula_faq_columns_orderby');
function nebula_faq_columns_orderby($query) {
    $orderby = $query->get('orderby');

    if ( $orderby == 'faq-category' ) {
        $query->set('meta_key', 'faq_category');
        $query->set('orderby', 'meta_value');
    }
}
```
",0,add example for creating  filling  and sorting custom column headers in wp admin   here is an example for a post type of  faqs        php   add id column on post page listings add filter  manage faqs posts columns    nebula faq columns head    function nebula faq columns head  defaults        defaults     category       return  defaults     add action  manage posts custom column    nebula faq columns content          function nebula faq columns content  column name   id       if    column name     faq category              post   get post            echo  post  custom fields               sortable columns in product admin add filter  manage edit faqs sortable columns    nebula faq sortable columns    function nebula faq sortable columns  columns         columns     category       return  columns    add action  pre get posts    nebula faq columns orderby    function nebula faq columns orderby  query         orderby    query  get  orderby         if    orderby     faq category               query  set  meta key    faq category             query  set  orderby    meta value                ,0
3351,4348821036.0,IssuesEvent,2016-07-30 05:20:44,HewlettPackard/POSH-HPOneView,https://api.github.com/repos/HewlettPackard/POSH-HPOneView,closed,Get-HPOVLdapDirectory -- the property 'sessionId' cannot be found on this object,Bug Security (General),"Please fill in as much information as possible to help resolve your issue.

### Actual Behavior
```
Get-HPOVLdapDirectory: The property 'sessionId' cannot be found on this object. Verify that the property exists and can be set.
```

### Steps to reproduce
Connect-HPOVMgmt
Get-HPOVLdapDirectory

### Version Information
HPE OneView PowerShell Library Version (`Get-HPOVVersion`): 2.0.530.1
HPE OneView Appliance Version: 2.00.07
",True,"Get-HPOVLdapDirectory -- the property 'sessionId' cannot be found on this object - Please fill in as much information as possible to help resolve your issue.

### Actual Behavior
```
Get-HPOVLdapDirectory: The property 'sessionId' cannot be found on this object. Verify that the property exists and can be set.
```

### Steps to reproduce
Connect-HPOVMgmt
Get-HPOVLdapDirectory

### Version Information
HPE OneView PowerShell Library Version (`Get-HPOVVersion`): 2.0.530.1
HPE OneView Appliance Version: 2.00.07
",0,get hpovldapdirectory    the property  sessionid  cannot be found on this object   please fill in as much information as possible to help resolve your issue         actual behavior       get hpovldapdirectory  the property  sessionid  cannot be found on this object  verify that the property exists and can be set              steps to reproduce  connect hpovmgmt  get hpovldapdirectory        version information  hpe oneview powershell library version   get hpovversion             hpe oneview appliance version         ,0
318740,23737822697.0,IssuesEvent,2022-08-31 09:39:21,golang/go,https://api.github.com/repos/golang/go,closed,net/http/pprof: documentation doesn't mention some available endpoints,Documentation NeedsFix,"Looking at https://pkg.go.dev/net/http/pprof as of Go 1.18.4, the following endpoints are documented:

* heap
* profile
* block
* mutex
* trace

From looking at https://cs.opensource.google/go/go/+/refs/tags/go1.18.4:src/net/http/pprof/pprof.go;l=344-354, the following are seemingly undocumented:

* allocs
* cmdline
* goroutine
* threadcreate

In particular, I think the `goroutine` endpoint is critically underused; goroutine leaks are a fairly common source of problems in long-lived Go servers, and being able to obtain a goroutine stack dump via `/debug/pprof/goroutine?debug=2` is invaluable. I've met a handful of people over the years who needed this and resorted to heavier alternatives like SIGQUIT because they weren't aware that `net/http/pprof` had it.

cc @cherrymui @rsc per https://dev.golang.org/owners",1.0,"net/http/pprof: documentation doesn't mention some available endpoints - Looking at https://pkg.go.dev/net/http/pprof as of Go 1.18.4, the following endpoints are documented:

* heap
* profile
* block
* mutex
* trace

From looking at https://cs.opensource.google/go/go/+/refs/tags/go1.18.4:src/net/http/pprof/pprof.go;l=344-354, the following are seemingly undocumented:

* allocs
* cmdline
* goroutine
* threadcreate

In particular, I think the `goroutine` endpoint is critically underused; goroutine leaks are a fairly common source of problems in long-lived Go servers, and being able to obtain a goroutine stack dump via `/debug/pprof/goroutine?debug=2` is invaluable. I've met a handful of people over the years who needed this and resorted to heavier alternatives like SIGQUIT because they weren't aware that `net/http/pprof` had it.

cc @cherrymui @rsc per https://dev.golang.org/owners",1,net http pprof  documentation doesn t mention some available endpoints   looking at   as of go        the following endpoints are documented       heap    profile    block    mutex    trace    from looking at   the following are seemingly undocumented       allocs    cmdline    goroutine    threadcreate    in particular  i think the  goroutine  endpoint is critically underused  goroutine leaks are a fairly common source of problems in long lived go servers  and being able to obtain a goroutine stack dump via   debug pprof goroutine debug    is invaluable  i ve met a handful of people over the years who needed this and resorted to heavier alternatives like sigquit because they weren t aware that  net http pprof  had it     cc  cherrymui  rsc per  ,1
41731,6933100544.0,IssuesEvent,2017-12-02 02:11:35,golang/go,https://api.github.com/repos/golang/go,closed,os: SetDeadline doesn't work after an Fd() call,Documentation,"### What version of Go are you using (`go version`)?
go version devel +ed8b7dedd3 Thu Nov 30 01:46:50 2017 +0000 linux/amd64

### What did you do?
```
package main

import (
    ""os""
    ""time""
)

func main() {
    r, w, err := os.Pipe()
    if err != nil { panic(err) }
    println(r.Fd())
    go func() {
        time.Sleep(time.Second*2)
        _, err := w.Write([]byte(""Hello, world!""))
        if err != nil { panic(err) }
    }()
    err = r.SetDeadline(time.Now().Add(time.Second))
    // expect an error at this line
    if err != nil { panic(err) }
    buffer := make([]byte, 16)
    n, err := r.Read(buffer)
    // or this line
    if err != nil { panic(err) }
    println(string(buffer[:n]))
}
```

### What did you expect to see?
A timeout error.
Or an error when `SetDeadline`.

The `Fd()` can also be called after `SetDeadline()`, so a timeout error is better.

### What did you see instead?
A successful Read and ""Hello, world!"".


The method `Fd()` put the file descriptor into blocking mode and the deadline doesn't work after it.
https://github.com/golang/go/blob/8064f82a158e4416e9f32ed7017642ace4280b4f/src/os/file_unix.go#L68

There is a similar issue with package `net`. https://github.com/golang/go/issues/21862",1.0,"os: SetDeadline doesn't work after an Fd() call - ### What version of Go are you using (`go version`)?
go version devel +ed8b7dedd3 Thu Nov 30 01:46:50 2017 +0000 linux/amd64

### What did you do?
```
package main

import (
    ""os""
    ""time""
)

func main() {
    r, w, err := os.Pipe()
    if err != nil { panic(err) }
    println(r.Fd())
    go func() {
        time.Sleep(time.Second*2)
        _, err := w.Write([]byte(""Hello, world!""))
        if err != nil { panic(err) }
    }()
    err = r.SetDeadline(time.Now().Add(time.Second))
    // expect an error at this line
    if err != nil { panic(err) }
    buffer := make([]byte, 16)
    n, err := r.Read(buffer)
    // or this line
    if err != nil { panic(err) }
    println(string(buffer[:n]))
}
```

### What did you expect to see?
A timeout error.
Or an error when `SetDeadline`.

The `Fd()` can also be called after `SetDeadline()`, so a timeout error is better.

### What did you see instead?
A successful Read and ""Hello, world!"".


The method `Fd()` put the file descriptor into blocking mode and the deadline doesn't work after it.
https://github.com/golang/go/blob/8064f82a158e4416e9f32ed7017642ace4280b4f/src/os/file_unix.go#L68

There is a similar issue with package `net`. https://github.com/golang/go/issues/21862",1,os  setdeadline doesn t work after an fd   call       what version of go are you using   go version     go version devel    thu nov              linux          what did you do        package main    import         os        time        func main          r  w  err    os pipe        if err    nil   panic err         println r fd         go func              time sleep time second                err    w write  byte  hello  world              if err    nil   panic err                  err   r setdeadline time now   add time second           expect an error at this line      if err    nil   panic err         buffer    make  byte          n  err    r read buffer          or this line      if err    nil   panic err         println string buffer                   what did you expect to see   a timeout error   or an error when  setdeadline      the  fd    can also be called after  setdeadline     so a timeout error is better         what did you see instead   a successful read and  hello  world         the method  fd    put the file descriptor into blocking mode and the deadline doesn t work after it        there is a similar issue with package  net    ,1
24919,5111745995.0,IssuesEvent,2017-01-06 08:06:48,golang/go,https://api.github.com/repos/golang/go,opened,doc: explain vendoring,Documentation,"[How to Write Go Code](https://golang.org/doc/code.html#remote) should mention vendoring feature under ""Remote packages"" section.

We also need to replace all the mentions of GO15VENDOREXPERIMENT on the wiki with the proper official document.",1.0,"doc: explain vendoring - [How to Write Go Code](https://golang.org/doc/code.html#remote) should mention vendoring feature under ""Remote packages"" section.

We also need to replace all the mentions of GO15VENDOREXPERIMENT on the wiki with the proper official document.",1,doc  explain vendoring       should mention vendoring feature under  remote packages  section     we also need to replace all the mentions of   on the wiki with the proper official document ,1
80005,10149101863.0,IssuesEvent,2019-08-05 14:33:13,golang/go,https://api.github.com/repos/golang/go,opened,doc: add Unicode 11 support to Go 1.13 release notes,Documentation NeedsFix release-blocker,"Tracking issue for Unicode 11 support: #27945
APIs changed:

```
pkg unicode, const Version = ""11.0.0""
pkg unicode, var Dogra *RangeTable
pkg unicode, var Gunjala_Gondi *RangeTable
pkg unicode, var Hanifi_Rohingya *RangeTable
pkg unicode, var Makasar *RangeTable
pkg unicode, var Medefaidrin *RangeTable
pkg unicode, var Old_Sogdian *RangeTable
pkg unicode, var Sogdian *RangeTable
```

/cc @mpvl ",1.0,"doc: add Unicode 11 support to Go 1.13 release notes - Tracking issue for Unicode 11 support: #27945
APIs changed:

```
pkg unicode, const Version = ""11.0.0""
pkg unicode, var Dogra *RangeTable
pkg unicode, var Gunjala_Gondi *RangeTable
pkg unicode, var Hanifi_Rohingya *RangeTable
pkg unicode, var Makasar *RangeTable
pkg unicode, var Medefaidrin *RangeTable
pkg unicode, var Old_Sogdian *RangeTable
pkg unicode, var Sogdian *RangeTable
```

/cc @mpvl ",1,doc  add unicode   support to go     release notes   tracking issue for unicode   support      apis changed          pkg unicode  const version            pkg unicode  var dogra  rangetable  pkg unicode  var gunjala gondi  rangetable  pkg unicode  var hanifi rohingya  rangetable  pkg unicode  var makasar  rangetable  pkg unicode  var medefaidrin  rangetable  pkg unicode  var old sogdian  rangetable  pkg unicode  var sogdian  rangetable          cc  mpvl ,1
302376,22820498182.0,IssuesEvent,2022-07-12 01:27:14,golang/go,https://api.github.com/repos/golang/go,closed,design: add metadata to all design documents ,Documentation help wanted WaitingForInfo,"Today a gopher on Telegram reported a problem when trying to install `staticcheck` with go1.16.
Here is the error:

```sh
go1.16.12 install honnef.co/go/tools/cmd/staticcheck@latest
```

```
.local/lib/go/pkg/mod/honnef.co/go/tools@v0.3.0/go/ir/builder.go:36:2: //go:build comment without // +build comment
```

I remembered that there was a transition period, so I checked the original proposal https://go.dev/design/draft-gobuild.

Here is a list of problems:

  1. The document is **still** marked as a draft
  2. In the transition section, the text uses `Go 1.(N−1)`, `Go 1.N` and so on.
      This is, IMHO, not very easy to follow.

I suggest to add metadata (like Python PEP) to **all** design documents, so that a reader can easily identify

  - If the design has been accepted
  - If the design has been implemented
  - In what Go version the design has been implemented

Thanks.",1.0,"design: add metadata to all design documents  - Today a gopher on Telegram reported a problem when trying to install `staticcheck` with go1.16.
Here is the error:

```sh
go1.16.12 install honnef.co/go/tools/cmd/staticcheck@latest
```

```
.local/lib/go/pkg/mod/honnef.co/go/tools@v0.3.0/go/ir/builder.go:36:2: //go:build comment without // +build comment
```

I remembered that there was a transition period, so I checked the original proposal https://go.dev/design/draft-gobuild.

Here is a list of problems:

  1. The document is **still** marked as a draft
  2. In the transition section, the text uses `Go 1.(N−1)`, `Go 1.N` and so on.
      This is, IMHO, not very easy to follow.

I suggest to add metadata (like Python PEP) to **all** design documents, so that a reader can easily identify

  - If the design has been accepted
  - If the design has been implemented
  - In what Go version the design has been implemented

Thanks.",1,design  add metadata to all design documents    today a gopher on telegram reported a problem when trying to install  staticcheck  with       here is the error        sh        install honnef co go tools cmd staticcheck latest               local lib go pkg mod honnef co go tools       go ir builder go        go build comment without     build comment         i remembered that there was a transition period  so i checked the original proposal      here is a list of problems          the document is   still   marked as a draft       in the transition section  the text uses  go    n−      go   n  and so on         this is  imho  not very easy to follow     i suggest to add metadata  like python pep  to   all   design documents  so that a reader can easily identify        if the design has been accepted      if the design has been implemented      in what go version the design has been implemented    thanks ,1
369206,10889546052.0,IssuesEvent,2019-11-18 18:28:47,department-of-veterans-affairs/caseflow,https://api.github.com/repos/department-of-veterans-affairs/caseflow,closed,Choose correct claimant and payee code for board grant effectuations,BVA Intake enhancement foxtrot priority-medium,"### User or job story
As a user who is processing a board grant effectuation, if the payee code is wrong then I have to manually create a new claim with the correct data, and the prior incorrect claim needs to be canceled.

### Acceptance criteria
- When creating a board grant effectuation EP, the claimant_participant_id should be set to the appeal's claimant's participant_id
- If the claimant has a payee_code set, the end product establishment should use that payee_code
  - Note: this will not be set for existing appeals, but I think we should set it for future appeals (which would be another ticket)
- If the claimant does not have the payee_code set, it should be calculated.  If the claimant is the veteran, it can be set to ""00"". If the claimant is a dependent, it should be set accordingly (see technical notes).

### Out of scope
Backfilling data

### Release notes
Board grant effectuations can support non-veteran claimants and payee codes.

#### Designs
Include screenshots or links to designs if applicable.

#### Background/context
We do not have the payee_code selector for appeals during intake, because what we've heard is that people at the board do not know what payee_codes are and wouldn't be able to choose one.

We may want to re-examine that assumption now that we can ""default"" the payee_code value, and now that we know that we shouldn't just use the veteran as the claimant for board grant effectuations.

Providing that option would only apply to new appeals going forward.  In order for this to apply to appeals that have already been completed, this should be a back-end fix.

#### Technical notes
- The end product establishment for board grant effectuations is created in board_grant_effectuation.rb > build_end_product_establishment
- For board grant effectuations, the end product establishment ""source"" is a decision document. The decision document is connected to an appeal, and the appeal has the claimant.
- There is a method that chooses the default payee code for a specific veteran relationship, located in the relationship.rb > default_payee_code
  - This method is currently used to choose a default payee code for the front-end payee_code selector.

#### Other notes
Example of this is claim_id 73192881, where the appeal had a non-veteran claimant. Claim 74791005 was manually established to fix the issue.

#### Resources/other links
https://dsva.slack.com/archives/CFBLH2LR4/p1571749027058100?thread_ts=1571168692.017200&cid=CFBLH2LR4
",1.0,"Choose correct claimant and payee code for board grant effectuations - ### User or job story
As a user who is processing a board grant effectuation, if the payee code is wrong then I have to manually create a new claim with the correct data, and the prior incorrect claim needs to be canceled.

### Acceptance criteria
- When creating a board grant effectuation EP, the claimant_participant_id should be set to the appeal's claimant's participant_id
- If the claimant has a payee_code set, the end product establishment should use that payee_code
  - Note: this will not be set for existing appeals, but I think we should set it for future appeals (which would be another ticket)
- If the claimant does not have the payee_code set, it should be calculated.  If the claimant is the veteran, it can be set to ""00"". If the claimant is a dependent, it should be set accordingly (see technical notes).

### Out of scope
Backfilling data

### Release notes
Board grant effectuations can support non-veteran claimants and payee codes.

#### Designs
Include screenshots or links to designs if applicable.

#### Background/context
We do not have the payee_code selector for appeals during intake, because what we've heard is that people at the board do not know what payee_codes are and wouldn't be able to choose one.

We may want to re-examine that assumption now that we can ""default"" the payee_code value, and now that we know that we shouldn't just use the veteran as the claimant for board grant effectuations.

Providing that option would only apply to new appeals going forward.  In order for this to apply to appeals that have already been completed, this should be a back-end fix.

#### Technical notes
- The end product establishment for board grant effectuations is created in board_grant_effectuation.rb > build_end_product_establishment
- For board grant effectuations, the end product establishment ""source"" is a decision document. The decision document is connected to an appeal, and the appeal has the claimant.
- There is a method that chooses the default payee code for a specific veteran relationship, located in the relationship.rb > default_payee_code
  - This method is currently used to choose a default payee code for the front-end payee_code selector.

#### Other notes
Example of this is claim_id 73192881, where the appeal had a non-veteran claimant. Claim 74791005 was manually established to fix the issue.

#### Resources/other links
https://dsva.slack.com/archives/CFBLH2LR4/p1571749027058100?thread_ts=1571168692.017200&cid=CFBLH2LR4
",0,choose correct claimant and payee code for board grant effectuations       user or job story as a user who is processing a board grant effectuation  if the payee code is wrong then i have to manually create a new claim with the correct data  and the prior incorrect claim needs to be canceled       acceptance criteria   when creating a board grant effectuation ep  the claimant participant id should be set to the appeal s claimant s participant id   if the claimant has a payee code set  the end product establishment should use that payee code     note  this will not be set for existing appeals  but i think we should set it for future appeals  which would be another ticket    if the claimant does not have the payee code set  it should be calculated   if the claimant is the veteran  it can be set to      if the claimant is a dependent  it should be set accordingly  see technical notes        out of scope backfilling data      release notes board grant effectuations can support non veteran claimants and payee codes        designs include screenshots or links to designs if applicable        background context we do not have the payee code selector for appeals during intake  because what we ve heard is that people at the board do not know what payee codes are and wouldn t be able to choose one   we may want to re examine that assumption now that we can  default  the payee code value  and now that we know that we shouldn t just use the veteran as the claimant for board grant effectuations   providing that option would only apply to new appeals going forward   in order for this to apply to appeals that have already been completed  this should be a back end fix        technical notes   the end product establishment for board grant effectuations is created in board grant effectuation rb   build end product establishment   for board grant effectuations  the end product establishment  source  is a decision document  the decision document is connected to an appeal  and the appeal has the claimant    there is a method that chooses the default payee code for a specific veteran relationship  located in the relationship rb   default payee code     this method is currently used to choose a default payee code for the front end payee code selector        other notes example of this is claim id    where the appeal had a non veteran claimant  claim   was manually established to fix the issue        resources other links   ,0
81922,10264774523.0,IssuesEvent,2019-08-22 17:12:02,golang/go,https://api.github.com/repos/golang/go,closed,net/http: 1.13rc1 docs for TimeoutHandler are incorrect about interfaces,Documentation NeedsFix release-blocker,"As of Go 1.13rc1, net/http's TimeoutHandler does implement the Flusher interface that the docs of TimeoutHandler claims it does not. The fact that it does now implement Flusher is mentioned in the release docs for 1.13rc1, though. 

TimeoutHandler also now implements Pusher which might be worth a mention in its docs.",1.0,"net/http: 1.13rc1 docs for TimeoutHandler are incorrect about interfaces - As of Go 1.13rc1, net/http's TimeoutHandler does implement the Flusher interface that the docs of TimeoutHandler claims it does not. The fact that it does now implement Flusher is mentioned in the release docs for 1.13rc1, though. 

TimeoutHandler also now implements Pusher which might be worth a mention in its docs.",1,net http      docs for timeouthandler are incorrect about interfaces   as of go      net http s timeouthandler does implement the flusher interface that the docs of timeouthandler claims it does not  the fact that it does now implement flusher is mentioned in the release docs for      though      timeouthandler also now implements pusher which might be worth a mention in its docs ,1
302670,22837704247.0,IssuesEvent,2022-07-12 18:20:55,golang/go,https://api.github.com/repos/golang/go,closed,x/website: add a Go GC guide,Documentation NeedsFix release-blocker okay-after-beta1 website,As part of #48409 I proposed adding a new guide for the Go GC. This is an issue to track that work.,1.0,x/website: add a Go GC guide - As part of #48409 I proposed adding a new guide for the Go GC. This is an issue to track that work.,1,x website  add a go gc guide   as part of    i proposed adding a new guide for the go gc  this is an issue to track that work ,1
117177,17439322317.0,IssuesEvent,2021-08-05 01:02:48,kaidisn/focal,https://api.github.com/repos/kaidisn/focal,closed,WS-2020-0218 (High) detected in merge-1.2.0.tgz - autoclosed,security vulnerability,"## WS-2020-0218 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>merge-1.2.0.tgz</b></p></summary>

<p>Merge multiple objects into one, optionally creating a new cloned object. Similar to the jQuery.extend but more flexible. Works in Node.js and the browser.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/merge/-/merge-1.2.0.tgz"">https://registry.npmjs.org/merge/-/merge-1.2.0.tgz</a></p>
<p>Path to dependency file: focal/node_modules/merge/package.json</p>
<p>Path to vulnerable library: focal/node_modules/merge/package.json</p>
<p>

Dependency Hierarchy:
  - focal-0.8.5.tgz (Root Library)
    - jest-24.1.0.tgz
      - jest-cli-24.1.0.tgz
        - jest-runtime-24.1.0.tgz
          - jest-haste-map-24.0.0.tgz
            - sane-3.1.0.tgz
              - exec-sh-0.2.1.tgz
                - :x: **merge-1.2.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/kaidisn/focal/commit/108c475c4b3b40093c1fe5d1b3181f284c8ecd0f"">108c475c4b3b40093c1fe5d1b3181f284c8ecd0f</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>  
  
A Prototype Pollution vulnerability was found in merge before 2.1.0 via the merge.recursive function. It can be tricked into adding or modifying properties of the Object prototype. These properties will be present on all objects.

<p>Publish Date: 2020-10-09
<p>URL: <a href=https://github.com/yeikos/js.merge/pull/38>WS-2020-0218</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/yeikos/js.merge/pull/38"">https://github.com/yeikos/js.merge/pull/38</a></p>
<p>Release Date: 2020-10-09</p>
<p>Fix Resolution: merge - 2.1.0</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""merge"",""packageVersion"":""1.2.0"",""packageFilePaths"":[""/node_modules/merge/package.json""],""isTransitiveDependency"":true,""dependencyTree"":""@grammarly/focal:0.8.5;jest:24.1.0;jest-cli:24.1.0;jest-runtime:24.1.0;jest-haste-map:24.0.0;sane:3.1.0;exec-sh:0.2.1;merge:1.2.0"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""merge - 2.1.0""}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""WS-2020-0218"",""vulnerabilityDetails"":""A Prototype Pollution vulnerability was found in merge before 2.1.0 via the merge.recursive function. It can be tricked into adding or modifying properties of the Object prototype. These properties will be present on all objects."",""vulnerabilityUrl"":""https://github.com/yeikos/js.merge/pull/38"",""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,"WS-2020-0218 (High) detected in merge-1.2.0.tgz - autoclosed - ## WS-2020-0218 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>merge-1.2.0.tgz</b></p></summary>

<p>Merge multiple objects into one, optionally creating a new cloned object. Similar to the jQuery.extend but more flexible. Works in Node.js and the browser.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/merge/-/merge-1.2.0.tgz"">https://registry.npmjs.org/merge/-/merge-1.2.0.tgz</a></p>
<p>Path to dependency file: focal/node_modules/merge/package.json</p>
<p>Path to vulnerable library: focal/node_modules/merge/package.json</p>
<p>

Dependency Hierarchy:
  - focal-0.8.5.tgz (Root Library)
    - jest-24.1.0.tgz
      - jest-cli-24.1.0.tgz
        - jest-runtime-24.1.0.tgz
          - jest-haste-map-24.0.0.tgz
            - sane-3.1.0.tgz
              - exec-sh-0.2.1.tgz
                - :x: **merge-1.2.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/kaidisn/focal/commit/108c475c4b3b40093c1fe5d1b3181f284c8ecd0f"">108c475c4b3b40093c1fe5d1b3181f284c8ecd0f</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>  
  
A Prototype Pollution vulnerability was found in merge before 2.1.0 via the merge.recursive function. It can be tricked into adding or modifying properties of the Object prototype. These properties will be present on all objects.

<p>Publish Date: 2020-10-09
<p>URL: <a href=https://github.com/yeikos/js.merge/pull/38>WS-2020-0218</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/yeikos/js.merge/pull/38"">https://github.com/yeikos/js.merge/pull/38</a></p>
<p>Release Date: 2020-10-09</p>
<p>Fix Resolution: merge - 2.1.0</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""merge"",""packageVersion"":""1.2.0"",""packageFilePaths"":[""/node_modules/merge/package.json""],""isTransitiveDependency"":true,""dependencyTree"":""@grammarly/focal:0.8.5;jest:24.1.0;jest-cli:24.1.0;jest-runtime:24.1.0;jest-haste-map:24.0.0;sane:3.1.0;exec-sh:0.2.1;merge:1.2.0"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""merge - 2.1.0""}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""WS-2020-0218"",""vulnerabilityDetails"":""A Prototype Pollution vulnerability was found in merge before 2.1.0 via the merge.recursive function. It can be tricked into adding or modifying properties of the Object prototype. These properties will be present on all objects."",""vulnerabilityUrl"":""https://github.com/yeikos/js.merge/pull/38"",""cvss3Severity"":""high"",""cvss3Score"":""7.5"",""cvss3Metrics"":{""A"":""High"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""None"",""AV"":""Network"",""I"":""None""},""extraData"":{}}</REMEDIATE> -->",0,ws      high  detected in merge       tgz   autoclosed      ws       high severity vulnerability     vulnerable library    merge       tgz      merge multiple objects into one  optionally creating a new cloned object  similar to the jquery extend but more flexible  works in node js and the browser    library home page   a href     path to dependency file  focal node modules merge package json   path to vulnerable library  focal node modules merge package json     dependency hierarchy      focal       tgz  root library        jest       tgz         jest cli       tgz           jest runtime       tgz             jest haste map       tgz               sane       tgz                 exec sh       tgz                    x    merge       tgz    vulnerable library   found in head commit   a href     found in base branch   master              vulnerability details         a prototype pollution vulnerability was found in merge before       via the merge recursive function  it can be tricked into adding or modifying properties of the object prototype  these properties will be present on all objects    publish date         url   a href              cvss   score details             base score metrics    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  merge                      isopenpronvulnerability  true  ispackagebased  true  isdefaultbranch  true  packages     istransitivedependency  true  dependencytree    grammarly focal       jest       jest cli       jest runtime       jest haste map       sane       exec sh       merge         isminimumfixversionavailable  true  minimumfixversion   merge             basebranches     vulnerabilityidentifier   ws       vulnerabilitydetails   a prototype pollution vulnerability was found in merge before       via the merge recursive function  it can be tricked into adding or modifying properties of the object prototype  these properties will be present on all objects    vulnerabilityurl        ,0
11045,3454722561.0,IssuesEvent,2015-12-17 17:00:59,golang/go,https://api.github.com/repos/golang/go,closed,"cmd/go: document that ""go test"" sets the PWD to the package directory",Documentation,"Using ```go1.5.1```

I have been relying on this behavior for some time and just assumed that it was always true, but when I looked through the documentation for ```go help test``` it doesn't mention this fact at all.

Many benchmarks make this assumption when they load test files from a testdata directory that is relative to the package directory.

Because ```go test``` sets the PWD, stuff like this works from anywhere:
```
rawr@carbonite: /tmp $ go test compress/flate -run none -bench .
PASS
BenchmarkDecodeDigitsSpeed1e4-4   	   10000	    194030 ns/op	  51.54 MB/s	   40301 B/op	       7 allocs/op
...
```

But compiling the test binary does not:
```
rawr@carbonite: /tmp $ go test -c compress/flate
rawr@carbonite: /tmp $ ./flate.test -test.run none -test.bench .
PASS
BenchmarkDecodeDigitsSpeed1e4-4   	--- FAIL: BenchmarkDecodeDigitsSpeed1e4-4
	reader_test.go:45: open ../testdata/e.txt: no such file or directory
...
```

I think the fact that the compiled version fails is WAI, but this behavior should be documented.",1.0,"cmd/go: document that ""go test"" sets the PWD to the package directory - Using ```go1.5.1```

I have been relying on this behavior for some time and just assumed that it was always true, but when I looked through the documentation for ```go help test``` it doesn't mention this fact at all.

Many benchmarks make this assumption when they load test files from a testdata directory that is relative to the package directory.

Because ```go test``` sets the PWD, stuff like this works from anywhere:
```
rawr@carbonite: /tmp $ go test compress/flate -run none -bench .
PASS
BenchmarkDecodeDigitsSpeed1e4-4   	   10000	    194030 ns/op	  51.54 MB/s	   40301 B/op	       7 allocs/op
...
```

But compiling the test binary does not:
```
rawr@carbonite: /tmp $ go test -c compress/flate
rawr@carbonite: /tmp $ ./flate.test -test.run none -test.bench .
PASS
BenchmarkDecodeDigitsSpeed1e4-4   	--- FAIL: BenchmarkDecodeDigitsSpeed1e4-4
	reader_test.go:45: open ../testdata/e.txt: no such file or directory
...
```

I think the fact that the compiled version fails is WAI, but this behavior should be documented.",1,cmd go  document that  go test  sets the pwd to the package directory   using                i have been relying on this behavior for some time and just assumed that it was always true  but when i looked through the documentation for    go help test    it doesn t mention this fact at all     many benchmarks make this assumption when they load test files from a testdata directory that is relative to the package directory     because    go test    sets the pwd  stuff like this works from anywhere        rawr carbonite   tmp   go test compress flate  run none  bench    pass        	    	      ns op	      mb s	     b op	         allocs op              but compiling the test binary does not        rawr carbonite   tmp   go test  c compress flate  rawr carbonite   tmp     flate test  test run none  test bench    pass        	    fail       	reader test go    open    testdata e txt  no such file or directory              i think the fact that the compiled version fails is wai  but this behavior should be documented ,1
302405,22822058608.0,IssuesEvent,2022-07-12 04:04:53,golang/go,https://api.github.com/repos/golang/go,closed,net/http: misleading documentation about the error returned by MaxBytesReader,Documentation NeedsInvestigation,"In Go 1.19, the `MaxBytesReader` method returns an error of type `*MaxBytesError` in case of a `Read` beyond the limit. But the [documentation suggests](https://pkg.go.dev/net/http@go1.19beta1#MaxBytesReader) that the type is `MaxBytesError` instead.

You have to read the implementation code or deduce it from the `Error` method that uses a pointer receiver.",1.0,"net/http: misleading documentation about the error returned by MaxBytesReader - In Go 1.19, the `MaxBytesReader` method returns an error of type `*MaxBytesError` in case of a `Read` beyond the limit. But the [documentation suggests](https://pkg.go.dev/net/http@go1.19beta1#MaxBytesReader) that the type is `MaxBytesError` instead.

You have to read the implementation code or deduce it from the `Error` method that uses a pointer receiver.",1,net http  misleading documentation about the error returned by maxbytesreader   in go      the  maxbytesreader  method returns an error of type   maxbyteserror  in case of a  read  beyond the limit  but the     that the type is  maxbyteserror  instead     you have to read the implementation code or deduce it from the  error  method that uses a pointer receiver ,1
323542,9856268907.0,IssuesEvent,2019-06-19 21:36:33,ChainSafe/lodestar,https://api.github.com/repos/ChainSafe/lodestar,closed,Startup Logic,priority: P3 important type: feature,"<!--NOTE: 
- General questions should go to the gitter room instead of the issue tracker.
-->

**Is your feature request related to a problem? Please describe.**
<!--A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]-->
The executable should have start functionality to a begin processing blocks, shuffling validators etc.

We'll need to accomplish the following:
- [ ] Finish the validator client
- [ ] Define a set of Validator RPC methods
- [ ] Add a new CLI flag (potentially?)
- [ ] Hook up LMDGhost to the epoch, block and state transitions",1.0,"Startup Logic - <!--NOTE: 
- General questions should go to the gitter room instead of the issue tracker.
-->

**Is your feature request related to a problem? Please describe.**
<!--A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]-->
The executable should have start functionality to a begin processing blocks, shuffling validators etc.

We'll need to accomplish the following:
- [ ] Finish the validator client
- [ ] Define a set of Validator RPC methods
- [ ] Add a new CLI flag (potentially?)
- [ ] Hook up LMDGhost to the epoch, block and state transitions",0,startup logic       note      general questions should go to the gitter room instead of the issue tracker            is your feature request related to a problem  please describe        the executable should have start functionality to a begin processing blocks  shuffling validators etc     we ll need to accomplish the following       finish the validator client      define a set of validator rpc methods      add a new cli flag  potentially        hook up lmdghost to the epoch  block and state transitions,0
76887,9967769545.0,IssuesEvent,2019-07-08 14:16:35,golang/go,https://api.github.com/repos/golang/go,closed,"x/blog: the defer, panic and recover entry at the go blog is outdated",Documentation NeedsFix help wanted,"Dear all i was reading [The defer, panic and recover entry](https://blog.golang.org/defer-panic-and-recover) at the go blog until i found this statement:

> For a real-world example of panic and recover, see the json package from the Go standard library. It decodes JSON-encoded data with a set of recursive functions. When malformed JSON is encountered, the parser calls panic to unwind the stack to the top-level function call, which recovers from the panic and returns an appropriate error value (see the 'error' and 'unmarshal' methods of the decodeState type in **decode.go**).

In the [source code of **decode.go**](https://golang.org/src/encoding/json/decode.go) i try to find ""recover"" or ""panic"". Panic is present but recover it isn't! I guess that as time pass, changes to the code occurs and the documention was leave behind outdated. 
I shall notice you with this ticket about the above inconsencty.

More context
-----------------

A gentle person (go.peter.90(at)gmail.com) takes the time to inform me (via gonuts mailing groups) that i will find panic and recovers in [**encode.go**,](https://golang.org/src/encoding/json/encode.go) and i do find those... that show me an example at least! great! but be aware that the example is in the 'marshal' method and not 'unmarshal' as the doc stated.

Well that would be all!

Thanks
V
",1.0,"x/blog: the defer, panic and recover entry at the go blog is outdated - Dear all i was reading [The defer, panic and recover entry](https://blog.golang.org/defer-panic-and-recover) at the go blog until i found this statement:

> For a real-world example of panic and recover, see the json package from the Go standard library. It decodes JSON-encoded data with a set of recursive functions. When malformed JSON is encountered, the parser calls panic to unwind the stack to the top-level function call, which recovers from the panic and returns an appropriate error value (see the 'error' and 'unmarshal' methods of the decodeState type in **decode.go**).

In the [source code of **decode.go**](https://golang.org/src/encoding/json/decode.go) i try to find ""recover"" or ""panic"". Panic is present but recover it isn't! I guess that as time pass, changes to the code occurs and the documention was leave behind outdated. 
I shall notice you with this ticket about the above inconsencty.

More context
-----------------

A gentle person (go.peter.90(at)gmail.com) takes the time to inform me (via gonuts mailing groups) that i will find panic and recovers in [**encode.go**,](https://golang.org/src/encoding/json/encode.go) and i do find those... that show me an example at least! great! but be aware that the example is in the 'marshal' method and not 'unmarshal' as the doc stated.

Well that would be all!

Thanks
V
",1,x blog  the defer  panic and recover entry at the go blog is outdated   dear all i was reading     at the go blog until i found this statement       for a real world example of panic and recover  see the json package from the go standard library  it decodes json encoded data with a set of recursive functions  when malformed json is encountered  the parser calls panic to unwind the stack to the top level function call  which recovers from the panic and returns an appropriate error value  see the  error  and  unmarshal  methods of the decodestate type in   decode go        in the     i try to find  recover  or  panic   panic is present but recover it isn t  i guess that as time pass  changes to the code occurs and the documention was leave behind outdated    i shall notice you with this ticket about the above inconsencty     more context                       a gentle person  go peter   at gmail com  takes the time to inform me  via gonuts mailing groups  that i will find panic and recovers in     and i do find those    that show me an example at least  great  but be aware that the example is in the  marshal  method and not  unmarshal  as the doc stated     well that would be all     thanks  v  ,1
444962,12824146544.0,IssuesEvent,2020-07-06 13:01:26,godaddy-wordpress/coblocks,https://api.github.com/repos/godaddy-wordpress/coblocks,opened,Escape key to close lightbox,[Priority] Low [Type] Enhancement,"The left/right arrow keys are linked to previous/next image, and it'd be lovely to press 'esc' to close the full-screen image version!

Cheers,
Jeremie

Coblocks: Version 2.0.2
WP: Version 5.4.2",1.0,"Escape key to close lightbox - The left/right arrow keys are linked to previous/next image, and it'd be lovely to press 'esc' to close the full-screen image version!

Cheers,
Jeremie

Coblocks: Version 2.0.2
WP: Version 5.4.2",0,escape key to close lightbox   the left right arrow keys are linked to previous next image  and it d be lovely to press  esc  to close the full screen image version     cheers   jeremie    coblocks  version        wp  version      ,0
92581,18893917559.0,IssuesEvent,2021-11-15 15:53:52,creativecommons/cc-licenses,https://api.github.com/repos/creativecommons/cc-licenses,opened,[Feature] Rename repository and improve Django application organization,🟨 priority: medium 🏁 status: ready for work 🚦 status: awaiting triage ✨ goal: improvement 💻 aspect: code 🤖 aspect: dx 🔒 staff only,"## Problem
1. The name ""cc-licenses"" is misleading (as noted at top of README and in the related [[Feature] Rename this repo to “cc-legal-tools-data” · Issue #44 · creativecommons/cc-licenses-data](https://github.com/creativecommons/cc-licenses-data/issues/44))
2. I think the Django namespacing could be better. It currently consists of `cc-licenses`, `licenses`, and `i18n`.
   - why isn't `transifex.py` in `i18n`?
   - there are a lot of transifex management commands. should it be it's own namespace?
   - does having separate `cc-licenses` and `licenses` namespaces pass a cost/benefit analysis? does the locations of templates, settings, etc. make sense / is intuitive?
3. This should be resolved prior to initial launch

## Description
TBD

## Alternatives
Leave as is.

## Additional context
- [Sensemaking: Django for Startup Founders: A better software architecture for SaaS startups and consumer apps](https://alexkrupp.typepad.com/sensemaking/2021/06/django-for-startup-founders-a-better-software-architecture-for-saas-startups-and-consumer-apps.html)
- 🙏🏻 **please comment with additional articles and references**",1.0,"[Feature] Rename repository and improve Django application organization - ## Problem
1. The name ""cc-licenses"" is misleading (as noted at top of README and in the related [[Feature] Rename this repo to “cc-legal-tools-data” · Issue #44 · creativecommons/cc-licenses-data](https://github.com/creativecommons/cc-licenses-data/issues/44))
2. I think the Django namespacing could be better. It currently consists of `cc-licenses`, `licenses`, and `i18n`.
   - why isn't `transifex.py` in `i18n`?
   - there are a lot of transifex management commands. should it be it's own namespace?
   - does having separate `cc-licenses` and `licenses` namespaces pass a cost/benefit analysis? does the locations of templates, settings, etc. make sense / is intuitive?
3. This should be resolved prior to initial launch

## Description
TBD

## Alternatives
Leave as is.

## Additional context
- [Sensemaking: Django for Startup Founders: A better software architecture for SaaS startups and consumer apps](https://alexkrupp.typepad.com/sensemaking/2021/06/django-for-startup-founders-a-better-software-architecture-for-saas-startups-and-consumer-apps.html)
- 🙏🏻 **please comment with additional articles and references**",0,  rename repository and improve django application organization      problem     the name  cc licenses  is misleading  as noted at top of readme and in the related   rename this repo to “cc legal tools data” · issue    · creativecommons cc licenses data        i think the django namespacing could be better  it currently consists of  cc licenses    licenses   and            why isn t  transifex py  in            there are a lot of transifex management commands  should it be it s own namespace        does having separate  cc licenses  and  licenses  namespaces pass a cost benefit analysis  does the locations of templates  settings  etc  make sense   is intuitive      this should be resolved prior to initial launch       description  tbd       alternatives  leave as is        additional context           🙏🏻   please comment with additional articles and references  ,0
164486,12808789703.0,IssuesEvent,2020-07-03 14:17:50,imixs/imixs-marty,https://api.github.com/repos/imixs/imixs-marty,closed,PropertyController - getProperty with default value,feature testing,"Extend the ProertyControler bean with an additional method providing an default value:

    #{propertyController.getProperty('another-property','default value')}",1.0,"PropertyController - getProperty with default value - Extend the ProertyControler bean with an additional method providing an default value:

    #{propertyController.getProperty('another-property','default value')}",0,propertycontroller   getproperty with default value   extend the proertycontroler bean with an additional method providing an default value           propertycontroller getproperty  another property   default value   ,0
24545,17382768087.0,IssuesEvent,2021-08-01 03:09:26,openemr/openemr,https://api.github.com/repos/openemr/openemr,closed,ONC 2015 C-CDA engine Phase 2.,2015 ONC Enhancement Infrastructure,"This continues the C-CDA project with interop(HIE, Import/Export etc) and CCM fixes from issue #4131 .
Phase 3 will be testing and necessary template additions to meet final ONC testing criteria. 
We need phase 2 to support phase 3.
Help is always welcomed...

@vishnuyar and/or @rhausam I could really use the Document resource soon. Even if not finished, I'd help.",1.0,"ONC 2015 C-CDA engine Phase 2. - This continues the C-CDA project with interop(HIE, Import/Export etc) and CCM fixes from issue #4131 .
Phase 3 will be testing and necessary template additions to meet final ONC testing criteria. 
We need phase 2 to support phase 3.
Help is always welcomed...

@vishnuyar and/or @rhausam I could really use the Document resource soon. Even if not finished, I'd help.",0,onc   c cda engine phase      this continues the c cda project with interop hie  import export etc  and ccm fixes from issue       phase   will be testing and necessary template additions to meet final onc testing criteria    we need phase   to support phase     help is always welcomed        vishnuyar and or  rhausam i could really use the document resource soon  even if not finished  i d help ,0
57138,8142258777.0,IssuesEvent,2018-08-21 06:55:09,golang/go,https://api.github.com/repos/golang/go,closed,Undocumented behaviour by map.LoadOrStore,Documentation,"I am not sure if this behaviour is expected, but I could not find any documentation regarding it.

According to the documentation:
```
LoadOrStore returns the existing value for the key if present.
Otherwise, it stores and returns the given value.
The loaded result is true if the value was loaded, false if stored.
```
I naturally expect that if the value is returned by a function, that function is not invoked if the key already exists.

### What version of Go are you using (`go version`)?
go1.10.3


### Does this issue reproduce with the latest release?
N/A

### What operating system and processor architecture are you using (`go env`)?
Darwin / amd64

### What did you do?
I tried to store a value into the `sync.Map` concurrently, by using `LoadOrStore` method, with the same key.

https://play.golang.org/p/PQ3pye-SZGN

### What did you expect to see?
I expected to see that the function `Foo` was only invoked once by the `sMap.LoadOrStore` method.


### What did you see instead?
The `sMap.LoadOrStore` method did only store once, but it invoked the `Foo` function 10 times.

",1.0,"Undocumented behaviour by map.LoadOrStore - I am not sure if this behaviour is expected, but I could not find any documentation regarding it.

According to the documentation:
```
LoadOrStore returns the existing value for the key if present.
Otherwise, it stores and returns the given value.
The loaded result is true if the value was loaded, false if stored.
```
I naturally expect that if the value is returned by a function, that function is not invoked if the key already exists.

### What version of Go are you using (`go version`)?
go1.10.3


### Does this issue reproduce with the latest release?
N/A

### What operating system and processor architecture are you using (`go env`)?
Darwin / amd64

### What did you do?
I tried to store a value into the `sync.Map` concurrently, by using `LoadOrStore` method, with the same key.

https://play.golang.org/p/PQ3pye-SZGN

### What did you expect to see?
I expected to see that the function `Foo` was only invoked once by the `sMap.LoadOrStore` method.


### What did you see instead?
The `sMap.LoadOrStore` method did only store once, but it invoked the `Foo` function 10 times.

",1,undocumented behaviour by map loadorstore   i am not sure if this behaviour is expected  but i could not find any documentation regarding it     according to the documentation        loadorstore returns the existing value for the key if present   otherwise  it stores and returns the given value   the loaded result is true if the value was loaded  false if stored        i naturally expect that if the value is returned by a function  that function is not invoked if the key already exists         what version of go are you using   go version                    does this issue reproduce with the latest release   n a        what operating system and processor architecture are you using   go env     darwin            what did you do   i tried to store a value into the  sync map  concurrently  by using  loadorstore  method  with the same key              what did you expect to see   i expected to see that the function  foo  was only invoked once by the  smap loadorstore  method           what did you see instead   the  smap loadorstore  method did only store once  but it invoked the  foo  function   times     ,1
15156,8787139704.0,IssuesEvent,2018-12-20 17:40:54,rsgalloway/pyseq,https://api.github.com/repos/rsgalloway/pyseq,closed,"pyseq.walk() execute on Python3, Consume huge memory and CPU.",performance,"Hi,
Thank you for great library:)

I found a behavior like a bug that occurred between pyseq 0.5.0 and the latest.
This problem occurs in Python 3.4.4 and Python 3.5.1, but it does not occur in Python 2.7.

Reproduction code and data are here:
https://drive.google.com/open?id=1xPG4x4Uv7RU-nI_IUGL-fO_I4CEyXplb

When executed, it consumes a large amount of memory at the following places.
https://github.com/rsgalloway/pyseq/blob/master/pyseq.py#L635
(and 1 cpu core busy occured)

The program can continue even after the problem has occurred.
However, since memory busy and CPU busy continue, it is impossible to continue the program.

This problem does not occur in pyseq 0.5.0 released on PyPI.
Therefore, I think there is regression bug in the fix from 0.5.0 to the latest pyseq.

My environment:
macOS 10.11.6
Python 3.4.4
Pyseq:latest (2018/11/28)

Regards
",True,"pyseq.walk() execute on Python3, Consume huge memory and CPU. - Hi,
Thank you for great library:)

I found a behavior like a bug that occurred between pyseq 0.5.0 and the latest.
This problem occurs in Python 3.4.4 and Python 3.5.1, but it does not occur in Python 2.7.

Reproduction code and data are here:
https://drive.google.com/open?id=1xPG4x4Uv7RU-nI_IUGL-fO_I4CEyXplb

When executed, it consumes a large amount of memory at the following places.
https://github.com/rsgalloway/pyseq/blob/master/pyseq.py#L635
(and 1 cpu core busy occured)

The program can continue even after the problem has occurred.
However, since memory busy and CPU busy continue, it is impossible to continue the program.

This problem does not occur in pyseq 0.5.0 released on PyPI.
Therefore, I think there is regression bug in the fix from 0.5.0 to the latest pyseq.

My environment:
macOS 10.11.6
Python 3.4.4
Pyseq:latest (2018/11/28)

Regards
",0,pyseq walk   execute on    consume huge memory and cpu    hi   thank you for great library      i found a behavior like a bug that occurred between pyseq       and the latest   this problem occurs in python       and python        but it does not occur in python         reproduction code and data are here        when executed  it consumes a large amount of memory at the following places       and   cpu core busy occured     the program can continue even after the problem has occurred   however  since memory busy and cpu busy continue  it is impossible to continue the program     this problem does not occur in pyseq       released on pypi   therefore  i think there is regression bug in the fix from       to the latest pyseq     my environment   macos        python        pyseq latest            regards  ,0
31849,2740422095.0,IssuesEvent,2015-04-21 01:47:00,x360ce/x360ce,https://api.github.com/repos/x360ce/x360ce,closed,Michał Ogonowski,bug imported invalid Priority-Medium,"_From [michalog...@gmail.com](https://code.google.com/u/113926215535413463016/) on August 01, 2010 11:07:07_

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? What gamepad are you using? On what version of drivers? Please set third label to Core if issue affect emulator (dll file) or App if issue affect x360ce.App application (exe file). Also if you want you can provide any additional information below.

_Original issue: http://code.google.com/p/x360ce/issues/detail?id=48_",1.0,"Michał Ogonowski - _From [michalog...@gmail.com](https://code.google.com/u/113926215535413463016/) on August 01, 2010 11:07:07_

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? What gamepad are you using? On what version of drivers? Please set third label to Core if issue affect emulator (dll file) or App if issue affect x360ce.App application (exe file). Also if you want you can provide any additional information below.

_Original issue: http://code.google.com/p/x360ce/issues/detail?id=48_",0,michał ogonowski    from     on august              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  what gamepad are you using  on what version of drivers  please set third label to core if issue affect emulator  dll file  or app if issue affect   app application  exe file   also if you want you can provide any additional information below    original issue   ,0
507064,14679293552.0,IssuesEvent,2020-12-31 06:34:44,webcompat/web-bugs,https://api.github.com/repos/webcompat/web-bugs,closed,gestyy.com - see bug description,browser-fenix engine-gecko ml-needsdiagnosis-false ml-probability-high priority-normal,"<!-- @browser: Firefox Mobile 84.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 8.1.0; Mobile; rv:84.0) Gecko/84.0 Firefox/84.0 -->
<!-- @reported_with: android-components-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/64644 -->
<!-- @extra_labels: browser-fenix -->

**URL**: http://gestyy.com/e0UmDB

**Browser / Version**: Firefox Mobile 84.0
**Operating System**: Android 8.1.0
**Tested Another Browser**: No 

**Problem type**: Something else
**Description**: keeps giving unsolicited offers/keeps popping up 
**Steps to Reproduce**:

<details>
      <summary>View the screenshot</summary>
      <img alt=""Screenshot"" src=""https://webcompat.com/uploads/2020/12/9227e6b0-84f5-4ed3-a011-a0e5d2a3b544.jpeg"">
      </details>

<details>
<summary>Browser Configuration</summary>
<ul>
  <li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20201119195818</li><li>channel: beta</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>

[View console log messages](https://webcompat.com/console_logs/2020/12/ae292003-26b4-46be-ad0c-232ca21167d3)

_From [webcompat.com](https://webcompat.com/) with ❤️_",1.0,"gestyy.com - see bug description - <!-- @browser: Firefox Mobile 84.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 8.1.0; Mobile; rv:84.0) Gecko/84.0 Firefox/84.0 -->
<!-- @reported_with: android-components-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/64644 -->
<!-- @extra_labels: browser-fenix -->

**URL**: http://gestyy.com/e0UmDB

**Browser / Version**: Firefox Mobile 84.0
**Operating System**: Android 8.1.0
**Tested Another Browser**: No 

**Problem type**: Something else
**Description**: keeps giving unsolicited offers/keeps popping up 
**Steps to Reproduce**:

<details>
      <summary>View the screenshot</summary>
      <img alt=""Screenshot"" src=""https://webcompat.com/uploads/2020/12/9227e6b0-84f5-4ed3-a011-a0e5d2a3b544.jpeg"">
      </details>

<details>
<summary>Browser Configuration</summary>
<ul>
  <li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20201119195818</li><li>channel: beta</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>

[View console log messages](https://webcompat.com/console_logs/2020/12/ae292003-26b4-46be-ad0c-232ca21167d3)

_From [webcompat.com](https://webcompat.com/) with ❤️_",0,gestyy com   see bug description                url         browser   version    firefox mobile       operating system    android         tested another browser    no     problem type    something else   description    keeps giving unsolicited offers keeps popping up    steps to reproduce                view the screenshot          img alt  screenshot  src                 browser configuration       gfx webrender all  false  gfx webrender blob images  true  gfx webrender enabled  false  image mem shared  true  buildid     channel  beta  hastouchscreen  true  mixed active content blocked  false  mixed passive content blocked  false  tracking content blocked  false             from     with ❤️ ,0
446968,31565335668.0,IssuesEvent,2023-09-03 18:58:40,golang/go,https://api.github.com/repos/golang/go,closed,encoding/base64: documentation can show the alphabet used for encoding,Documentation NeedsFix,"The encoding variables make reference to the RFC on how they work, but it's not clear from Go's documentation, nor the RFC, how they differ (note that they are defined in the RFC, but the naming, and link, means it's not an easy lookup for the first time users, I broke some code at work not knowing the difference and it was discovered because a consumer was using the other set) - is there a cleaner way to say
URLEncoding uses the following characterset
```
 Table 2: The ""URL and Filename safe"" Base 64 Alphabet

     Value Encoding  Value Encoding  Value Encoding  Value Encoding
         0 A            17 R            34 i            51 z
         1 B            18 S            35 j            52 0
         2 C            19 T            36 k            53 1
         3 D            20 U            37 l            54 2
         4 E            21 V            38 m            55 3
         5 F            22 W            39 n            56 4
         6 G            23 X            40 o            57 5
         7 H            24 Y            41 p            58 6
         8 I            25 Z            42 q            59 7
         9 J            26 a            43 r            60 8
        10 K            27 b            44 s            61 9
        11 L            28 c            45 t            62 - (minus)
        12 M            29 d            46 u            63 _
        13 N            30 e            47 v           (underline)
        14 O            31 f            48 w
        15 P            32 g            49 x
        16 Q            33 h            50 y         (pad) =
```
and StdEncoding uses the following
```
                      Table 1: The Base 64 Alphabet

     Value Encoding  Value Encoding  Value Encoding  Value Encoding
         0 A            17 R            34 i            51 z
         1 B            18 S            35 j            52 0
         2 C            19 T            36 k            53 1
         3 D            20 U            37 l            54 2
         4 E            21 V            38 m            55 3
         5 F            22 W            39 n            56 4
         6 G            23 X            40 o            57 5
         7 H            24 Y            41 p            58 6
         8 I            25 Z            42 q            59 7
         9 J            26 a            43 r            60 8
        10 K            27 b            44 s            61 9
        11 L            28 c            45 t            62 +
        12 M            29 d            46 u            63 /
        13 N            30 e            47 v
        14 O            31 f            48 w         (pad) =
        15 P            32 g            49 x
        16 Q            33 h            50 y

```
As well as the reasoning that is already present in the docs.",1.0,"encoding/base64: documentation can show the alphabet used for encoding - The encoding variables make reference to the RFC on how they work, but it's not clear from Go's documentation, nor the RFC, how they differ (note that they are defined in the RFC, but the naming, and link, means it's not an easy lookup for the first time users, I broke some code at work not knowing the difference and it was discovered because a consumer was using the other set) - is there a cleaner way to say
URLEncoding uses the following characterset
```
 Table 2: The ""URL and Filename safe"" Base 64 Alphabet

     Value Encoding  Value Encoding  Value Encoding  Value Encoding
         0 A            17 R            34 i            51 z
         1 B            18 S            35 j            52 0
         2 C            19 T            36 k            53 1
         3 D            20 U            37 l            54 2
         4 E            21 V            38 m            55 3
         5 F            22 W            39 n            56 4
         6 G            23 X            40 o            57 5
         7 H            24 Y            41 p            58 6
         8 I            25 Z            42 q            59 7
         9 J            26 a            43 r            60 8
        10 K            27 b            44 s            61 9
        11 L            28 c            45 t            62 - (minus)
        12 M            29 d            46 u            63 _
        13 N            30 e            47 v           (underline)
        14 O            31 f            48 w
        15 P            32 g            49 x
        16 Q            33 h            50 y         (pad) =
```
and StdEncoding uses the following
```
                      Table 1: The Base 64 Alphabet

     Value Encoding  Value Encoding  Value Encoding  Value Encoding
         0 A            17 R            34 i            51 z
         1 B            18 S            35 j            52 0
         2 C            19 T            36 k            53 1
         3 D            20 U            37 l            54 2
         4 E            21 V            38 m            55 3
         5 F            22 W            39 n            56 4
         6 G            23 X            40 o            57 5
         7 H            24 Y            41 p            58 6
         8 I            25 Z            42 q            59 7
         9 J            26 a            43 r            60 8
        10 K            27 b            44 s            61 9
        11 L            28 c            45 t            62 +
        12 M            29 d            46 u            63 /
        13 N            30 e            47 v
        14 O            31 f            48 w         (pad) =
        15 P            32 g            49 x
        16 Q            33 h            50 y

```
As well as the reasoning that is already present in the docs.",1,encoding    documentation can show the alphabet used for encoding   the encoding variables make reference to the rfc on how they work  but it s not clear from go s documentation  nor the rfc  how they differ  note that they are defined in the rfc  but the naming  and link  means it s not an easy lookup for the first time users  i broke some code at work not knowing the difference and it was discovered because a consumer was using the other set    is there a cleaner way to say  urlencoding uses the following characterset        table    the  url and filename safe  base   alphabet         value encoding  value encoding  value encoding  value encoding             a              r              i              z             b              s              j                            c              t              k                            d              u              l                            e              v              m                            f              w              n                            g              x              o                            h              y              p                            i              z              q                            j              a              r                           k              b              s                           l              c              t                 minus             m              d              u                           n              e              v            underline             o              f              w            p              g              x            q              h              y          pad          and stdencoding uses the following                             table    the base   alphabet         value encoding  value encoding  value encoding  value encoding             a              r              i              z             b              s              j                            c              t              k                            d              u              l                            e              v              m                            f              w              n                            g              x              o                            h              y              p                            i              z              q                            j              a              r                           k              b              s                           l              c              t                           m              d              u                           n              e              v            o              f              w          pad               p              g              x            q              h              y         as well as the reasoning that is already present in the docs ,1
28991,5560226550.0,IssuesEvent,2017-03-24 18:52:48,golang/go,https://api.github.com/repos/golang/go,closed,spec: does not cover the case where a map composite literal contains multiple copies of the same key at runtime,Documentation,"Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
[November 18, 2016](https://golang.org/ref/spec)

### What operating system and processor architecture are you using (`go env`)?
N/A

### What did you do?
The Go spec states ""For map literals, all elements must have a key. It is an error to specify multiple elements with the same field name or constant key value."", however, it is silent as to what happens whem multiple elements with the same non-constant key value are present, as in this link: https://play.golang.org/p/53kQ9rF8a2

As you can see, it appears that the later one wins in this example, but I don't know if this always holds.",1.0,"spec: does not cover the case where a map composite literal contains multiple copies of the same key at runtime - Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
[November 18, 2016](https://golang.org/ref/spec)

### What operating system and processor architecture are you using (`go env`)?
N/A

### What did you do?
The Go spec states ""For map literals, all elements must have a key. It is an error to specify multiple elements with the same field name or constant key value."", however, it is silent as to what happens whem multiple elements with the same non-constant key value are present, as in this link: https://play.golang.org/p/53kQ9rF8a2

As you can see, it appears that the later one wins in this example, but I don't know if this always holds.",1,spec  does not cover the case where a map composite literal contains multiple copies of the same key at runtime   please answer these questions before submitting your issue  thanks         what version of go are you using   go version                what operating system and processor architecture are you using   go env     n a        what did you do   the go spec states  for map literals  all elements must have a key  it is an error to specify multiple elements with the same field name or constant key value    however  it is silent as to what happens whem multiple elements with the same non constant key value are present  as in this link       as you can see  it appears that the later one wins in this example  but i don t know if this always holds ,1
13882,10519838163.0,IssuesEvent,2019-09-29 20:45:43,Automattic/newspack-plugin,https://api.github.com/repos/Automattic/newspack-plugin,closed,Local development hampered by plugin configuration dependencies,[Type] Infrastructure,"In a local development environment, Newspack can never be set up because the Jetpack and Site Kit plugins can't be configured using a local URL. While there are ways to expose a local dev environment on a public URL, there are a few problems with that as a solution:

1. It raises the barrier for developers to get set up
2. It exposes the machine to the outside world, which is a security risk
3. Offline development becomes much harder

It is possible, however, to use common markers like the `WP_DEBUG` constant to detect a local development environment and behave differently, allowing testing to proceed without requiring plugins to be setup completely.",1.0,"Local development hampered by plugin configuration dependencies - In a local development environment, Newspack can never be set up because the Jetpack and Site Kit plugins can't be configured using a local URL. While there are ways to expose a local dev environment on a public URL, there are a few problems with that as a solution:

1. It raises the barrier for developers to get set up
2. It exposes the machine to the outside world, which is a security risk
3. Offline development becomes much harder

It is possible, however, to use common markers like the `WP_DEBUG` constant to detect a local development environment and behave differently, allowing testing to proceed without requiring plugins to be setup completely.",0,local development hampered by plugin configuration dependencies   in a local development environment  newspack can never be set up because the jetpack and site kit plugins can t be configured using a local url  while there are ways to expose a local dev environment on a public url  there are a few problems with that as a solution        it raises the barrier for developers to get set up     it exposes the machine to the outside world  which is a security risk     offline development becomes much harder    it is possible  however  to use common markers like the  wp debug  constant to detect a local development environment and behave differently  allowing testing to proceed without requiring plugins to be setup completely ,0
66551,8951939944.0,IssuesEvent,2019-01-25 15:17:34,golang/go,https://api.github.com/repos/golang/go,closed,"go/build: update documentation referring to binary-only packages, to mention 1.12 being the last supported release for BOP",Documentation,"[The Binary-Only Packages section](https://tip.golang.org/pkg/go/build/#hdr-Binary_Only_Packages) discusses binary-only packages, and [the AllowBinary constant](https://tip.golang.org/pkg/go/build/#ImportMode) also mentions them.

Although the 1.12 release notes [mention that ""Go 1.12 is the last release that will support binary-only packages""](https://tip.golang.org/doc/go1.12#binary-only), it seems to me that the Godoc in go/build should make some mention of it as well.

There might be other packages referring to binary-only packages in their documentation; I just happened to stumble across it in go/build today.

footer on tip.golang.org: `Build version devel +9d23975 Wed Jan 23 23:13:03 2019 +0000.`",1.0,"go/build: update documentation referring to binary-only packages, to mention 1.12 being the last supported release for BOP - [The Binary-Only Packages section](https://tip.golang.org/pkg/go/build/#hdr-Binary_Only_Packages) discusses binary-only packages, and [the AllowBinary constant](https://tip.golang.org/pkg/go/build/#ImportMode) also mentions them.

Although the 1.12 release notes [mention that ""Go 1.12 is the last release that will support binary-only packages""](https://tip.golang.org/doc/go1.12#binary-only), it seems to me that the Godoc in go/build should make some mention of it as well.

There might be other packages referring to binary-only packages in their documentation; I just happened to stumble across it in go/build today.

footer on tip.golang.org: `Build version devel +9d23975 Wed Jan 23 23:13:03 2019 +0000.`",1,go build  update documentation referring to binary only packages  to mention     being the last supported release for bop       discusses binary only packages  and     also mentions them     although the     release notes     it seems to me that the godoc in go build should make some mention of it as well     there might be other packages referring to binary only packages in their documentation  i just happened to stumble across it in go build today     footer on tip golang org   build version devel    wed jan               ,1
123386,26249212407.0,IssuesEvent,2023-01-05 17:42:15,joomla/joomla-cms,https://api.github.com/repos/joomla/joomla-cms,closed,Joomla 4 Router URL is case sensitive.,No Code Attached Yet,"### Steps to reproduce the issue

This URL works
https://www.brainforge.co.uk/our-services

This URL fails
https://www.brainforge.co.uk/Our-services

### Expected result

Both should produce the same result.

### Actual result

Upper case character in URL fails.

### System information (as much as possible)



### Additional comments

This was encountered with a 3rd party component with code which looked something like this...

$url = 'myname';
$url = JURI::base() . JText::_($url);
// JText Returns Myname (or a language equivalent)

Link / redirection to that url fails.

I've tried entering uppercase on another Joomla site which has no extension(s) of mine, so I'm sure its not something I have done!",1.0,"Joomla 4 Router URL is case sensitive. - ### Steps to reproduce the issue

This URL works
https://www.brainforge.co.uk/our-services

This URL fails
https://www.brainforge.co.uk/Our-services

### Expected result

Both should produce the same result.

### Actual result

Upper case character in URL fails.

### System information (as much as possible)



### Additional comments

This was encountered with a 3rd party component with code which looked something like this...

$url = 'myname';
$url = JURI::base() . JText::_($url);
// JText Returns Myname (or a language equivalent)

Link / redirection to that url fails.

I've tried entering uppercase on another Joomla site which has no extension(s) of mine, so I'm sure its not something I have done!",0,joomla   router url is case sensitive        steps to reproduce the issue    this url works       this url fails           expected result    both should produce the same result         actual result    upper case character in url fails         system information  as much as possible             additional comments    this was encountered with a   party component with code which looked something like this        url    myname     url   juri  base     jtext     url       jtext returns myname  or a language equivalent     link   redirection to that url fails     i ve tried entering uppercase on another joomla site which has no extension s  of mine  so i m sure its not something i have done ,0
31312,5931393602.0,IssuesEvent,2017-05-24 06:11:39,golang/go,https://api.github.com/repos/golang/go,closed,"time: is documented as safe for concurrent use, but unmarshal methods do not synchronize",Documentation,"time.Time is documented as being safe for concurrent use, however, some methods modify it without synchronization: GobDecode, UnmarshalBinary, UnmarshalJSON, and UnmarshalText.

It seems like we should update the documentation.  What's the right way to document the goroutine-safety guarantee?  Something like:

""A Time value can be used by multiple goroutines simultaneously so long as no goroutine calls an unmarshaler method (t.GobDecode, t.UnmarshalBinary, t.UnmarshalJSON, t.UnmarshalText).""  ?
",1.0,"time: is documented as safe for concurrent use, but unmarshal methods do not synchronize - time.Time is documented as being safe for concurrent use, however, some methods modify it without synchronization: GobDecode, UnmarshalBinary, UnmarshalJSON, and UnmarshalText.

It seems like we should update the documentation.  What's the right way to document the goroutine-safety guarantee?  Something like:

""A Time value can be used by multiple goroutines simultaneously so long as no goroutine calls an unmarshaler method (t.GobDecode, t.UnmarshalBinary, t.UnmarshalJSON, t.UnmarshalText).""  ?
",1,time  is documented as safe for concurrent use  but unmarshal methods do not synchronize   time time is documented as being safe for concurrent use  however  some methods modify it without synchronization  gobdecode  unmarshalbinary  unmarshaljson  and unmarshaltext     it seems like we should update the documentation   what s the right way to document the goroutine safety guarantee   something like      a time value can be used by multiple goroutines simultaneously so long as no goroutine calls an unmarshaler method  t gobdecode  t unmarshalbinary  t unmarshaljson  t unmarshaltext        ,1
445983,12838475113.0,IssuesEvent,2020-07-07 17:32:05,nthopinion/covid19,https://api.github.com/repos/nthopinion/covid19,closed,Update Physicians Questions View,High Priority,"The question view for physicians has been designed and is the same as the public-facing page. Please go to our Figma workspace and take a look at ""Question when clicked"" under Design for Developers.

┆Issue is synchronized with this [Trello card](https://trello.com/c/ElgJh9Bx) by [Unito](https://www.unito.io/learn-more)
",1.0,"Update Physicians Questions View - The question view for physicians has been designed and is the same as the public-facing page. Please go to our Figma workspace and take a look at ""Question when clicked"" under Design for Developers.

┆Issue is synchronized with this [Trello card](https://trello.com/c/ElgJh9Bx) by [Unito](https://www.unito.io/learn-more)
",0,update physicians questions view   the question view for physicians has been designed and is the same as the public facing page  please go to our figma workspace and take a look at  question when clicked  under design for developers   ┆issue is synchronized with this     by     ,0
317315,23671675856.0,IssuesEvent,2022-08-27 13:01:35,golang/go,https://api.github.com/repos/golang/go,closed,"strings, bytes: Title doesn't shield against emoji",Documentation NeedsDecision,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.17.1 darwin/arm64
</pre>

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""on""
GOARCH=""arm64""
GOBIN=""/bin""
GOCACHE=""/Users/wang/Library/Caches/go-build""
GOENV=""/Users/wang/Library/Application Support/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""arm64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/wang/go/pkg/mod""
GONOPROXY=""gitlab.hexcloud.cn""
GONOSUMDB=""gitlab.hexcloud.cn""
GOOS=""darwin""
GOPATH=""/Users/wang/go""
GOPRIVATE=""gitlab.hexcloud.cn""
GOPROXY=""https://goproxy.io,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_arm64""
GOVCS=""""
GOVERSION=""go1.17.1""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/wang/open/source/go/src/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/fc/5_f38pyn6k915kw7_vvfjhrc0000gn/T/go-build1773033347=/tmp/go-build -gno-record-gcc-switches -fno-common""
GOROOT/bin/go version: go version go1.17.1 darwin/arm64
GOROOT/bin/go tool compile -V: compile version go1.17.1
uname -v: Darwin Kernel Version 20.6.0: Wed Jun 23 00:26:27 PDT 2021; root:xnu-7195.141.2~5/RELEASE_ARM64_T8101
ProductName:	macOS
ProductVersion:	11.5.1
BuildVersion:	20G80
lldb --version: lldb-1205.0.28.2
Apple Swift version 5.4.2 (swiftlang-1205.0.28.2 clang-1205.0.19.57)
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

[playground](https://play.golang.org/p/a0CvAAQCRn8)

### What did you expect to see?

☺☻☹Hello

### What did you see instead?

☺☻☹hello
",1.0,"strings, bytes: Title doesn't shield against emoji - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.17.1 darwin/arm64
</pre>

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""on""
GOARCH=""arm64""
GOBIN=""/bin""
GOCACHE=""/Users/wang/Library/Caches/go-build""
GOENV=""/Users/wang/Library/Application Support/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""arm64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/wang/go/pkg/mod""
GONOPROXY=""gitlab.hexcloud.cn""
GONOSUMDB=""gitlab.hexcloud.cn""
GOOS=""darwin""
GOPATH=""/Users/wang/go""
GOPRIVATE=""gitlab.hexcloud.cn""
GOPROXY=""https://goproxy.io,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_arm64""
GOVCS=""""
GOVERSION=""go1.17.1""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/wang/open/source/go/src/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/fc/5_f38pyn6k915kw7_vvfjhrc0000gn/T/go-build1773033347=/tmp/go-build -gno-record-gcc-switches -fno-common""
GOROOT/bin/go version: go version go1.17.1 darwin/arm64
GOROOT/bin/go tool compile -V: compile version go1.17.1
uname -v: Darwin Kernel Version 20.6.0: Wed Jun 23 00:26:27 PDT 2021; root:xnu-7195.141.2~5/RELEASE_ARM64_T8101
ProductName:	macOS
ProductVersion:	11.5.1
BuildVersion:	20G80
lldb --version: lldb-1205.0.28.2
Apple Swift version 5.4.2 (swiftlang-1205.0.28.2 clang-1205.0.19.57)
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

[playground](https://play.golang.org/p/a0CvAAQCRn8)

### What did you expect to see?

☺☻☹Hello

### What did you see instead?

☺☻☹hello
",1,strings  bytes  title doesn t shield against emoji            what version of go are you using   go version            go version  go version       darwin             does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env          go env  output       go env     on   goarch      gobin   bin   gocache   users wang library caches go build   goenv   users wang library application support go env   goexe     goexperiment     goflags     gohostarch      gohostos  darwin   goinsecure     gomodcache   users wang go pkg mod   gonoproxy  gitlab hexcloud cn   gonosumdb  gitlab hexcloud cn   goos  darwin   gopath   users wang go   goprivate  gitlab hexcloud cn   goproxy     goroot   usr local go   gosumdb  sum golang org   gotmpdir     gotooldir   usr local go pkg tool darwin     govcs     goversion          gccgo  gccgo   ar  ar   cc  clang   cxx  clang     cgo enabled      gomod   users wang open source go src go mod   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic  arch    pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders fc       t go    tmp go build  gno record gcc switches  fno common   goroot bin go version  go version       darwin    goroot bin go tool compile  v  compile version        uname  v  darwin kernel version        wed jun         pdt    root xnu         release      productname 	macos  productversion 	       buildversion 	   lldb   version  lldb          apple swift version        swiftlang         clang                     what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best                     what did you expect to see     ☺☻☹hello        what did you see instead     ☺☻☹hello  ,1
100481,8744570717.0,IssuesEvent,2018-12-12 22:43:01,dotnet/corefx,https://api.github.com/repos/dotnet/corefx,closed,[arm32/Windows] System.Runtime.Tests failures on arm32 windows,arch-arm32 area-System.Runtime os-windows-iot test-run-core,"Running the arm32 tests on windows for System.Runtime.Tests produced the following results: passed 31427/31439 tests.

Most of the 12 test failures have to do with DateTime not throwing ARgumentOutOfRange exceptions as well as a TimeZoneInfo issue:
```
Assert.Throws() Failure\r\nExpected: typeof(System.ArgumentOutOfRangeException)\r\nActual:   (No exception was thrown)
   at System.AssertExtensions.Throws[T](String paramName, Func`1 testCode) in F:\git\corefx\src\CoreFx.Private.TestUtilities\src\System\AssertExtensions.cs:line 83
   at System.Tests.DateTimeTests.AddMinutes_NewDateOutOfRange_ThrowsArgumentOutOfRangeException(DateTime date, Double minutes) in F:\git\corefx\src\System.Runtime\tests\System\DateTimeTests.cs:line 523
```

[testResults.zip](https://github.com/dotnet/corefx/files/2673800/testResults.zip)

",1.0,"[arm32/Windows] System.Runtime.Tests failures on arm32 windows - Running the arm32 tests on windows for System.Runtime.Tests produced the following results: passed 31427/31439 tests.

Most of the 12 test failures have to do with DateTime not throwing ARgumentOutOfRange exceptions as well as a TimeZoneInfo issue:
```
Assert.Throws() Failure\r\nExpected: typeof(System.ArgumentOutOfRangeException)\r\nActual:   (No exception was thrown)
   at System.AssertExtensions.Throws[T](String paramName, Func`1 testCode) in F:\git\corefx\src\CoreFx.Private.TestUtilities\src\System\AssertExtensions.cs:line 83
   at System.Tests.DateTimeTests.AddMinutes_NewDateOutOfRange_ThrowsArgumentOutOfRangeException(DateTime date, Double minutes) in F:\git\corefx\src\System.Runtime\tests\System\DateTimeTests.cs:line 523
```

[testResults.zip](https://github.com/dotnet/corefx/files/2673800/testResults.zip)

",0,  system runtime tests failures on   windows   running the   tests on windows for system runtime tests produced the following results  passed     tests     most of the   test failures have to do with datetime not throwing argumentoutofrange exceptions as well as a timezoneinfo issue        assert throws   failure r nexpected  typeof system argumentoutofrangeexception  r nactual     no exception was thrown      at system assertextensions throws  string paramname  func   testcode  in f  git corefx src corefx private testutilities src system assertextensions cs line       at system tests datetimetests addminutes newdateoutofrange throwsargumentoutofrangeexception datetime date  double minutes  in f  git corefx src system runtime tests system datetimetests cs line                  ,0
670092,22669859155.0,IssuesEvent,2022-07-03 12:53:03,Waurum-Studio/waurum-issues,https://api.github.com/repos/Waurum-Studio/waurum-issues,closed,Config Items Crash,addon: bru - Issue priority: 2 platform: gmod realm: sh server: funs,"### Expected Behavior

We shouldn't crash when trying to load configurable items list for admins.
We could implement some kind of lazy loading for models / icons or simply add a pagination w/ 50 items per page.

### Actual Behavior

As of now, loading configurable items will 50% of the time crash your gmod instance which is kind of annoying for devs.

### Reproduction Steps

```markdown
1. Go to Config tab in F4
2. Hit the Config items
3. Pray that it doesn't crash
```


### Concerned Platform(s)

[GMOD]  Pedobear Server

### Version

v4.3

### Console Error

_No response_

### Additional Information

_No response_",1.0,"Config Items Crash - ### Expected Behavior

We shouldn't crash when trying to load configurable items list for admins.
We could implement some kind of lazy loading for models / icons or simply add a pagination w/ 50 items per page.

### Actual Behavior

As of now, loading configurable items will 50% of the time crash your gmod instance which is kind of annoying for devs.

### Reproduction Steps

```markdown
1. Go to Config tab in F4
2. Hit the Config items
3. Pray that it doesn't crash
```


### Concerned Platform(s)

[GMOD]  Pedobear Server

### Version

v4.3

### Console Error

_No response_

### Additional Information

_No response_",0,config items crash       expected behavior  we shouldn t crash when trying to load configurable items list for admins   we could implement some kind of lazy loading for models   icons or simply add a pagination w    items per page       actual behavior  as of now  loading configurable items will    of the time crash your gmod instance which is kind of annoying for devs       reproduction steps     markdown    go to config tab in       hit the config items     pray that it doesn t crash           concerned platform s      pedobear server      version           console error   no response       additional information   no response ,0
74048,14171398207.0,IssuesEvent,2020-11-12 15:40:11,jOOQ/jOOQ,https://api.github.com/repos/jOOQ/jOOQ,closed,"Add <visibilityModifier/> to allow for generating explicit / implicit public visibility, as well as internal in KotlinGenerator",C: Code Generation C: Integration: Kotlin E: All Editions P: Medium R: Fixed T: Enhancement,"### Use case:

Kotlin 1.4 has an explicit api mode https://kotlinlang.org/docs/reference/whatsnew14.html#explicit-api-mode-for-library-authors. When this mode is enabled all declarations must contain a visibility modifier (with some exceptions listed in the docs). Currently kotlin generator generates the classes with implicit `public` modifier so it is impossible to enable this mode.

### Possible solution you'd like to see:

Add an explicit `public` modifier to the declarations. It would be nice if we could specify if `public` or `internal` modifier should be used since we would like to use an `internal` modifier but if it would be hard to implement such a feature `public` modifier would be enough. Public API should also specify the return type explicitly.

### Possible workarounds:

The only workaround that we can think of is to move the generation into a separate module that has explicit api mode turned off.

### Versions:

- jOOQ: 3.14.1
- Java: 8
- Database (include vendor): MySQL 8",1.0,"Add <visibilityModifier/> to allow for generating explicit / implicit public visibility, as well as internal in KotlinGenerator - ### Use case:

Kotlin 1.4 has an explicit api mode https://kotlinlang.org/docs/reference/whatsnew14.html#explicit-api-mode-for-library-authors. When this mode is enabled all declarations must contain a visibility modifier (with some exceptions listed in the docs). Currently kotlin generator generates the classes with implicit `public` modifier so it is impossible to enable this mode.

### Possible solution you'd like to see:

Add an explicit `public` modifier to the declarations. It would be nice if we could specify if `public` or `internal` modifier should be used since we would like to use an `internal` modifier but if it would be hard to implement such a feature `public` modifier would be enough. Public API should also specify the return type explicitly.

### Possible workarounds:

The only workaround that we can think of is to move the generation into a separate module that has explicit api mode turned off.

### Versions:

- jOOQ: 3.14.1
- Java: 8
- Database (include vendor): MySQL 8",0,add   to allow for generating explicit   implicit public visibility  as well as internal in kotlingenerator       use case     kotlin     has an explicit api mode   when this mode is enabled all declarations must contain a visibility modifier  with some exceptions listed in the docs   currently kotlin generator generates the classes with implicit  public  modifier so it is impossible to enable this mode         possible solution you d like to see     add an explicit  public  modifier to the declarations  it would be nice if we could specify if  public  or  internal  modifier should be used since we would like to use an  internal  modifier but if it would be hard to implement such a feature  public  modifier would be enough  public api should also specify the return type explicitly         possible workarounds     the only workaround that we can think of is to move the generation into a separate module that has explicit api mode turned off         versions       jooq           java       database  include vendor   mysql  ,0
87860,8124331349.0,IssuesEvent,2018-08-16 17:12:14,learn-co-curriculum/orm-mapping-db-to-ruby-object-lab,https://api.github.com/repos/learn-co-curriculum/orm-mapping-db-to-ruby-object-lab,closed,Sometimes you don't need to use .map to pass a test,Test,"Looking at the text specs, as long as there's some elements returned without discerning the content, then the tests will pass, even though it's not really the correct answer. 

For example, for the ""First X students in grade 10"" portion, I coded this:

`   def self.first_X_students_in_grade_10(x)
    sql = <<-SQL
    SELECT *
    FROM students
    WHERE students.grade = 10
    LIMIT ?
    SQL
    binding.pry
    DB[:conn].execute(sql, x)
  end
`

Please note that before my ""end"" statement, I did not utilize the ""map"" method, and I still got the right answer.  From what I see, I returned something like this: 
[[1, ""Pat"", ""10""], [2, ""Sam"", ""10""]]

I got a nested array with the **values** instead of the actual student objects. 

By adding the .map to the sql query, I got this instead:

[#<Student:0x000000033bf670 @grade=""10"", @id=1, @name=""Pat"">,
 #<Student:0x000000033bf648 @grade=""10"", @id=2, @name=""Sam"">]


Which would seem to be the point of the test, to return student objects. 

I found that other tests were similar, in that returning nested arrays with only 1 element will satisfy the test, but isn't technically correct.  For example, the count of all the students in grade 9. I think the added restriction in the test specs to return something like ""student.id"" should fix this limitation (just like in the ""find by name"" method). 

Hope this is correct, let me know if this isn't really an issue. 

Thanks, 

Michael 
",1.0,"Sometimes you don't need to use .map to pass a test - Looking at the text specs, as long as there's some elements returned without discerning the content, then the tests will pass, even though it's not really the correct answer. 

For example, for the ""First X students in grade 10"" portion, I coded this:

`   def self.first_X_students_in_grade_10(x)
    sql = <<-SQL
    SELECT *
    FROM students
    WHERE students.grade = 10
    LIMIT ?
    SQL
    binding.pry
    DB[:conn].execute(sql, x)
  end
`

Please note that before my ""end"" statement, I did not utilize the ""map"" method, and I still got the right answer.  From what I see, I returned something like this: 
[[1, ""Pat"", ""10""], [2, ""Sam"", ""10""]]

I got a nested array with the **values** instead of the actual student objects. 

By adding the .map to the sql query, I got this instead:

[#<Student:0x000000033bf670 @grade=""10"", @id=1, @name=""Pat"">,
 #<Student:0x000000033bf648 @grade=""10"", @id=2, @name=""Sam"">]


Which would seem to be the point of the test, to return student objects. 

I found that other tests were similar, in that returning nested arrays with only 1 element will satisfy the test, but isn't technically correct.  For example, the count of all the students in grade 9. I think the added restriction in the test specs to return something like ""student.id"" should fix this limitation (just like in the ""find by name"" method). 

Hope this is correct, let me know if this isn't really an issue. 

Thanks, 

Michael 
",0,sometimes you don t need to use  map to pass a test   looking at the text specs  as long as there s some elements returned without discerning the content  then the tests will pass  even though it s not really the correct answer      for example  for the  first x students in grade    portion  i coded this         def self first x students in grade   x       sql      sql      select        from students      where students grade          limit        sql      binding pry      db  execute sql  x     end       please note that before my  end  statement  i did not utilize the  map  method  and i still got the right answer   from what i see  i returned something like this             i got a nested array with the   values   instead of the actual student objects      by adding the  map to the sql query  i got this instead                     which would seem to be the point of the test  to return student objects      i found that other tests were similar  in that returning nested arrays with only   element will satisfy the test  but isn t technically correct   for example  the count of all the students in grade    i think the added restriction in the test specs to return something like  student id  should fix this limitation  just like in the  find by name  method       hope this is correct  let me know if this isn t really an issue      thanks      michael   ,0
11275,13235368814.0,IssuesEvent,2020-08-18 17:55:42,gudmdharalds-a8c/testing123,https://api.github.com/repos/gudmdharalds-a8c/testing123,closed,PHP Upgrade: Compatibility issues found in /,PHP 7.4 Compatibility PHP Compatibility,"The following issues were found when scanning branch <code>abranch12</code> for compatibility problems:  
* bla-11: <b>Error</b>: Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead https://github.com/gudmdharalds-a8c/testing123/blob/b99a028e21f490f459f7095329fe4933e8643e79/bla-11.php#L3

* <b>Error</b>: Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead https://github.com/gudmdharalds-a8c/testing123/blob/b99a028e21f490f459f7095329fe4933e8643e79/bla-7.php#L3

* <b>Error</b>: Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead https://github.com/gudmdharalds-a8c/testing123/blob/b99a028e21f490f459f7095329fe4933e8643e79/bla-8.php#L5

* <b>Warning</b>: Function ldap_sort() is deprecated since PHP 7.0 https://github.com/gudmdharalds-a8c/testing123/blob/b99a028e21f490f459f7095329fe4933e8643e79/file1.php#L3

* <b>Error</b>: Extension 'mcrypt' is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead https://github.com/gudmdharalds-a8c/testing123/blob/b99a028e21f490f459f7095329fe4933e8643e79/file1.php#L5

* <b>Error</b>: Function mcrypt_cfb() is deprecated since PHP 5.5 and removed since PHP 7.0 https://github.com/gudmdharalds-a8c/testing123/blob/b99a028e21f490f459f7095329fe4933e8643e79/file1.php#L5

* <b>Error</b>: Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead https://github.com/gudmdharalds-a8c/testing123/blob/b99a028e21f490f459f7095329fe4933e8643e79/file1.php#L7



 This is an automated report.
",True,"PHP Upgrade: Compatibility issues found in / - The following issues were found when scanning branch <code>abranch12</code> for compatibility problems:  
* bla-11: <b>Error</b>: Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead https://github.com/gudmdharalds-a8c/testing123/blob/b99a028e21f490f459f7095329fe4933e8643e79/bla-11.php#L3

* <b>Error</b>: Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead https://github.com/gudmdharalds-a8c/testing123/blob/b99a028e21f490f459f7095329fe4933e8643e79/bla-7.php#L3

* <b>Error</b>: Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead https://github.com/gudmdharalds-a8c/testing123/blob/b99a028e21f490f459f7095329fe4933e8643e79/bla-8.php#L5

* <b>Warning</b>: Function ldap_sort() is deprecated since PHP 7.0 https://github.com/gudmdharalds-a8c/testing123/blob/b99a028e21f490f459f7095329fe4933e8643e79/file1.php#L3

* <b>Error</b>: Extension 'mcrypt' is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead https://github.com/gudmdharalds-a8c/testing123/blob/b99a028e21f490f459f7095329fe4933e8643e79/file1.php#L5

* <b>Error</b>: Function mcrypt_cfb() is deprecated since PHP 5.5 and removed since PHP 7.0 https://github.com/gudmdharalds-a8c/testing123/blob/b99a028e21f490f459f7095329fe4933e8643e79/file1.php#L5

* <b>Error</b>: Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead https://github.com/gudmdharalds-a8c/testing123/blob/b99a028e21f490f459f7095329fe4933e8643e79/file1.php#L7



 This is an automated report.
",0,php upgrade  compatibility issues found in     the following issues were found when scanning branch     for compatibility problems       bla     error   extension  mysql   is deprecated since php     and removed since php      use mysqli instead         error   extension  mysql   is deprecated since php     and removed since php      use mysqli instead         error   extension  mysql   is deprecated since php     and removed since php      use mysqli instead         warning   function ldap sort   is deprecated since php             error   extension  mcrypt  is deprecated since php     and removed since php      use openssl  preferred  or pecl mcrypt once available instead         error   function mcrypt cfb   is deprecated since php     and removed since php             error   extension  mysql   is deprecated since php     and removed since php      use mysqli instead           this is an automated report   ,0
5033,2900264605.0,IssuesEvent,2015-06-17 15:36:49,golang/go,https://api.github.com/repos/golang/go,closed,doc: extract examples from tests,Documentation,"I suggest digging tests and extract meaningful examples from them.

If approved, I can produce a set of CLs for that.",1.0,"doc: extract examples from tests - I suggest digging tests and extract meaningful examples from them.

If approved, I can produce a set of CLs for that.",1,doc  extract examples from tests   i suggest digging tests and extract meaningful examples from them     if approved  i can produce a set of cls for that ,1
209701,16054315340.0,IssuesEvent,2021-04-23 00:54:23,Realm667/WolfenDoom,https://api.github.com/repos/Realm667/WolfenDoom,closed,C3M1_A: Missing/blank window textures,mapping playtesting,"Missing window textures near the end, in the room with Dr. Schabbs jr. and the last clue of the level.
![Screenshot_BoA_20210422_201424](https://user-images.githubusercontent.com/20642121/115765942-a64f1a80-a3a7-11eb-9415-8d98c89c2710.png)
",1.0,"C3M1_A: Missing/blank window textures - Missing window textures near the end, in the room with Dr. Schabbs jr. and the last clue of the level.
![Screenshot_BoA_20210422_201424](https://user-images.githubusercontent.com/20642121/115765942-a64f1a80-a3a7-11eb-9415-8d98c89c2710.png)
",0,  a  missing blank window textures   missing window textures near the end  in the room with dr  schabbs jr  and the last clue of the level         ,0
126307,17018052469.0,IssuesEvent,2021-07-02 14:40:16,kubernetes-sigs/kui,https://api.github.com/repos/kubernetes-sigs/kui,closed,Should watchable tables auto-scroll to the bottom?,design :art: lifecycle/rotten,"Potentially complicated w.r.t. user-initiated scrolling; e.g. i scroll up, and then Kui annoying scrolls back down?

Maybe use an Unread Badge to indicate new data?",1.0,"Should watchable tables auto-scroll to the bottom? - Potentially complicated w.r.t. user-initiated scrolling; e.g. i scroll up, and then Kui annoying scrolls back down?

Maybe use an Unread Badge to indicate new data?",0,should watchable tables auto scroll to the bottom    potentially complicated w r t  user initiated scrolling  e g  i scroll up  and then kui annoying scrolls back down     maybe use an unread badge to indicate new data ,0
165206,13994423052.0,IssuesEvent,2020-10-28 00:38:47,golang/go,https://api.github.com/repos/golang/go,opened,testing: document -test.benchmem and ReportAllocs output format,Documentation NeedsFix help wanted,"Filing this bug on behalf of someone who prefers not to do it directly:

The `⁠(*testing.B).ReportAllocs` function's documentation says that its output is the same as setting -test.benchmem. However, there is as far as I can tell no explanation anywhere of what, exactly, -test.benchmem is or what it does. There is also no explanation as to what the output format is. For instance, in an output line like

    BenchmarkF-34         	    9718	    672043 ns/op	   34474 B/op	     508 allocs/op

I can see the lines with four numbers, but one of them is completely dimensionless and the others aren't entirely clear.",1.0,"testing: document -test.benchmem and ReportAllocs output format - Filing this bug on behalf of someone who prefers not to do it directly:

The `⁠(*testing.B).ReportAllocs` function's documentation says that its output is the same as setting -test.benchmem. However, there is as far as I can tell no explanation anywhere of what, exactly, -test.benchmem is or what it does. There is also no explanation as to what the output format is. For instance, in an output line like

    BenchmarkF-34         	    9718	    672043 ns/op	   34474 B/op	     508 allocs/op

I can see the lines with four numbers, but one of them is completely dimensionless and the others aren't entirely clear.",1,testing  document  test benchmem and reportallocs output format   filing this bug on behalf of someone who prefers not to do it directly     the  ⁠  testing b  reportallocs  function s documentation says that its output is the same as setting  test benchmem  however  there is as far as i can tell no explanation anywhere of what  exactly   test benchmem is or what it does  there is also no explanation as to what the output format is  for instance  in an output line like        benchmarkf           	     	      ns op	     b op	       allocs op    i can see the lines with four numbers  but one of them is completely dimensionless and the others aren t entirely clear ,1
158126,20007797335.0,IssuesEvent,2022-02-01 00:21:37,RG4421/openedr,https://api.github.com/repos/RG4421/openedr,reopened,CVE-2020-8285 (High) detected in curlcurl-7_63_0,security vulnerability,"## CVE-2020-8285 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>curlcurl-7_63_0</b></p></summary>
<p>

<p>A command line tool and library for transferring data with URL syntax, supporting HTTP, HTTPS, FTP, FTPS, GOPHER, TFTP, SCP, SFTP, SMB, TELNET, DICT, LDAP, LDAPS, FILE, IMAP, SMTP, POP3, RTSP and RTMP. libcurl offers a myriad of powerful features</p>
<p>Library home page: <a href=https://github.com/curl/curl.git>https://github.com/curl/curl.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/RG4421/openedr/commit/f991dbd97bf34917a1d61c43ef4b41832708779c"">f991dbd97bf34917a1d61c43ef4b41832708779c</a></p>

<p>Found in base branch: <b>main</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/openedr/edrav2/eprj/curl/lib/ftp.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/openedr/edrav2/eprj/curl/lib/ftp.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
curl 7.21.0 to and including 7.73.0 is vulnerable to uncontrolled recursion due to a stack overflow issue in FTP wildcard match parsing.

<p>Publish Date: 2020-12-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8285>CVE-2020-8285</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://curl.se/docs/CVE-2020-8285.html"">https://curl.se/docs/CVE-2020-8285.html</a></p>
<p>Release Date: 2020-07-21</p>
<p>Fix Resolution: 7.74.0</p>

</p>
</details>
<p></p>
",True,"CVE-2020-8285 (High) detected in curlcurl-7_63_0 - ## CVE-2020-8285 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>curlcurl-7_63_0</b></p></summary>
<p>

<p>A command line tool and library for transferring data with URL syntax, supporting HTTP, HTTPS, FTP, FTPS, GOPHER, TFTP, SCP, SFTP, SMB, TELNET, DICT, LDAP, LDAPS, FILE, IMAP, SMTP, POP3, RTSP and RTMP. libcurl offers a myriad of powerful features</p>
<p>Library home page: <a href=https://github.com/curl/curl.git>https://github.com/curl/curl.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/RG4421/openedr/commit/f991dbd97bf34917a1d61c43ef4b41832708779c"">f991dbd97bf34917a1d61c43ef4b41832708779c</a></p>

<p>Found in base branch: <b>main</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/openedr/edrav2/eprj/curl/lib/ftp.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/openedr/edrav2/eprj/curl/lib/ftp.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
curl 7.21.0 to and including 7.73.0 is vulnerable to uncontrolled recursion due to a stack overflow issue in FTP wildcard match parsing.

<p>Publish Date: 2020-12-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8285>CVE-2020-8285</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://curl.se/docs/CVE-2020-8285.html"">https://curl.se/docs/CVE-2020-8285.html</a></p>
<p>Release Date: 2020-07-21</p>
<p>Fix Resolution: 7.74.0</p>

</p>
</details>
<p></p>
",0,cve      high  detected in curlcurl            cve       high severity vulnerability     vulnerable library    curlcurl              a command line tool and library for transferring data with url syntax  supporting http  https  ftp  ftps  gopher  tftp  scp  sftp  smb  telnet  dict  ldap  ldaps  file  imap  smtp     rtsp and rtmp  libcurl offers a myriad of powerful features   library home page   a href    found in head commit   a href      found in base branch   main             vulnerable source files                  openedr   eprj curl lib ftp c        openedr   eprj curl lib ftp c                    vulnerability details         curl       to and including       is vulnerable to uncontrolled recursion due to a stack overflow issue in ftp wildcard match parsing    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                 ,0
132427,18268683454.0,IssuesEvent,2021-10-04 11:30:46,artsking/linux-3.0.35,https://api.github.com/repos/artsking/linux-3.0.35,opened,CVE-2013-6282 (High) detected in linux-stable-rtv3.8.6,security vulnerability,"## CVE-2013-6282 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv3.8.6</b></p></summary>
<p>

<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/artsking/linux-3.0.35/commit/5992fa81c6ac1b4e9db13f5408d914525c5b7875"">5992fa81c6ac1b4e9db13f5408d914525c5b7875</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>

</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addresses, which allows attackers to read or modify the contents of arbitrary kernel memory locations via a crafted application, as exploited in the wild against Android devices in October and November 2013.

<p>Publish Date: 2013-11-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-6282>CVE-2013-6282</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>7.2</b>)</summary>
<p>

Base Score Metrics not available</p>

</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2013-6282"">https://nvd.nist.gov/vuln/detail/CVE-2013-6282</a></p>
<p>Release Date: 2013-11-20</p>
<p>Fix Resolution: 3.5.5</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-2013-6282 (High) detected in linux-stable-rtv3.8.6 - ## CVE-2013-6282 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv3.8.6</b></p></summary>
<p>

<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/artsking/linux-3.0.35/commit/5992fa81c6ac1b4e9db13f5408d914525c5b7875"">5992fa81c6ac1b4e9db13f5408d914525c5b7875</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>

</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addresses, which allows attackers to read or modify the contents of arbitrary kernel memory locations via a crafted application, as exploited in the wild against Android devices in October and November 2013.

<p>Publish Date: 2013-11-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-6282>CVE-2013-6282</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>7.2</b>)</summary>
<p>

Base Score Metrics not available</p>

</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2013-6282"">https://nvd.nist.gov/vuln/detail/CVE-2013-6282</a></p>
<p>Release Date: 2013-11-20</p>
<p>Fix Resolution: 3.5.5</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in linux stable            cve       high severity vulnerability     vulnerable library    linux stable              julia cartwright s fork of linux stable rt git   library home page   a href    found in head commit   a href      found in base branch   master             vulnerable source files                              vulnerability details         the     get user and     put user api functions in the linux kernel before       on the   and   arm platforms do not validate certain addresses  which allows attackers to read or modify the contents of arbitrary kernel memory locations via a crafted application  as exploited in the wild against android devices in october and november      publish date         url   a href              cvss   score details             base score metrics not available              suggested fix      type  upgrade version   origin   a href     release date          fix resolution                      step up your open source security game with whitesource    ,0
23667,4964368251.0,IssuesEvent,2016-12-03 18:48:50,golang/go,https://api.github.com/repos/golang/go,opened,net: can Conn.Close block?,Documentation NeedsDecision,"The documentation for `net.Conn.Close` is:
> Close closes the connection. Any blocked Read or Write operations will be unblocked and return errors.

However, it does not mention anything about whether `Close` itself can block.

Some `net.Conn` implementations have an implicit write buffer. Thus, when `Close` is called, it still needs to flush the buffer before returning. This means that `Close` is effectively an operation that involves IO. Since it involves IO, this means that `Close` may have to wait until the recipient acknowledges the incoming data (which could potentially be forever if the receiver's read buffer is full).

If we extend the documentation for `net.Conn.Close`, would the following be reasonable?
> Close closes the connection. Any blocked Read or Write operations will be unblocked and return errors. Close itself may block while it is flushing any internal write buffers, but must return an error when a previously set deadline has been exceeded.

\cc @bradfitz @mikioh ",1.0,"net: can Conn.Close block? - The documentation for `net.Conn.Close` is:
> Close closes the connection. Any blocked Read or Write operations will be unblocked and return errors.

However, it does not mention anything about whether `Close` itself can block.

Some `net.Conn` implementations have an implicit write buffer. Thus, when `Close` is called, it still needs to flush the buffer before returning. This means that `Close` is effectively an operation that involves IO. Since it involves IO, this means that `Close` may have to wait until the recipient acknowledges the incoming data (which could potentially be forever if the receiver's read buffer is full).

If we extend the documentation for `net.Conn.Close`, would the following be reasonable?
> Close closes the connection. Any blocked Read or Write operations will be unblocked and return errors. Close itself may block while it is flushing any internal write buffers, but must return an error when a previously set deadline has been exceeded.

\cc @bradfitz @mikioh ",1,net  can conn close block    the documentation for  net conn close  is     close closes the connection  any blocked read or write operations will be unblocked and return errors     however  it does not mention anything about whether  close  itself can block     some  net conn  implementations have an implicit write buffer  thus  when  close  is called  it still needs to flush the buffer before returning  this means that  close  is effectively an operation that involves io  since it involves io  this means that  close  may have to wait until the recipient acknowledges the incoming data  which could potentially be forever if the receiver s read buffer is full      if we extend the documentation for  net conn close   would the following be reasonable     close closes the connection  any blocked read or write operations will be unblocked and return errors  close itself may block while it is flushing any internal write buffers  but must return an error when a previously set deadline has been exceeded      cc  bradfitz  mikioh ,1
269213,8433422128.0,IssuesEvent,2018-10-17 07:14:16,webcompat/web-bugs,https://api.github.com/repos/webcompat/web-bugs,closed,www.nextmuni.com - see bug description,browser-firefox priority-normal,"<!-- @browser: Firefox 62.0 -->
<!-- @ua_header: Mozilla/5.0 (X11; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0 -->
<!-- @reported_with: web -->

**URL**: https://www.nextmuni.com/#_home

**Browser / Version**: Firefox 62.0
**Operating System**: Android
**Tested Another Browser**: Yes

**Problem type**: Something else
**Description**: Content sized incorrectly in Firefox compared to Chrome.
**Steps to Reproduce**:
Accessed web site via URL.
[![Screenshot Description](https://webcompat.com/uploads/2018/6/111c3028-214d-430f-ab7f-4e5915648b9a-thumb.jpg)](https://webcompat.com/uploads/2018/6/111c3028-214d-430f-ab7f-4e5915648b9a.jpg)



_From [webcompat.com](https://webcompat.com/) with ❤️_",1.0,"www.nextmuni.com - see bug description - <!-- @browser: Firefox 62.0 -->
<!-- @ua_header: Mozilla/5.0 (X11; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0 -->
<!-- @reported_with: web -->

**URL**: https://www.nextmuni.com/#_home

**Browser / Version**: Firefox 62.0
**Operating System**: Android
**Tested Another Browser**: Yes

**Problem type**: Something else
**Description**: Content sized incorrectly in Firefox compared to Chrome.
**Steps to Reproduce**:
Accessed web site via URL.
[![Screenshot Description](https://webcompat.com/uploads/2018/6/111c3028-214d-430f-ab7f-4e5915648b9a-thumb.jpg)](https://webcompat.com/uploads/2018/6/111c3028-214d-430f-ab7f-4e5915648b9a.jpg)



_From [webcompat.com](https://webcompat.com/) with ❤️_",0,    see bug description                url           browser   version    firefox        operating system    android    tested another browser    yes      problem type    something else    description    content sized incorrectly in firefox compared to chrome     steps to reproduce     accessed web site via url               from     with ❤️ ,0
34965,6397004404.0,IssuesEvent,2017-08-04 16:53:55,golang/go,https://api.github.com/repos/golang/go,closed,doc/editors: mention that Gogland can be distributed as part of Jetbrains paid IDEs,Documentation,"### What version of Go are you using (`go version`)?
n/a

### What operating system and processor architecture are you using (`go env`)?
n/a

### What did you do?
on http://tip.golang.org/doc/editors.html, this sentence is not totally true:
```text
Gogland: Gogland is distributed either as a standalone IDE or as a plugin for the IntelliJ Platform IDEs
``` 
I prefere this one:
```text
Gogland: Gogland is distributed either as a standalone IDE or as a plugin for Intellij IDEA Ultimate and other Jetbrain paid IDEs.
```

### What did you expect to see?
n/a

### What did you see instead?
n/a

",1.0,"doc/editors: mention that Gogland can be distributed as part of Jetbrains paid IDEs - ### What version of Go are you using (`go version`)?
n/a

### What operating system and processor architecture are you using (`go env`)?
n/a

### What did you do?
on http://tip.golang.org/doc/editors.html, this sentence is not totally true:
```text
Gogland: Gogland is distributed either as a standalone IDE or as a plugin for the IntelliJ Platform IDEs
``` 
I prefere this one:
```text
Gogland: Gogland is distributed either as a standalone IDE or as a plugin for Intellij IDEA Ultimate and other Jetbrain paid IDEs.
```

### What did you expect to see?
n/a

### What did you see instead?
n/a

",1,doc editors  mention that gogland can be distributed as part of jetbrains paid ides       what version of go are you using   go version     n a        what operating system and processor architecture are you using   go env     n a        what did you do   on   this sentence is not totally true      text  gogland  gogland is distributed either as a standalone ide or as a plugin for the intellij platform ides        i prefere this one      text  gogland  gogland is distributed either as a standalone ide or as a plugin for intellij idea ultimate and other jetbrain paid ides              what did you expect to see   n a        what did you see instead   n a    ,1
102258,11278105354.0,IssuesEvent,2020-01-15 05:33:39,golang/go,https://api.github.com/repos/golang/go,closed,"doc: go-spec.html missing space before . on line 2416, OperandName = identifier | QualifiedIdent.",Documentation NeedsFix,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
go 1.13.5

(line 2416 is as of current master)

</pre>

### Does this issue reproduce with the latest release?

yes 

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env

GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/user2/Library/Caches/go-build""
GOENV=""/Users/user2/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/user2/A/AL3/code/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/8v/vpckwgfs4_547sb94qr9f4d40000gq/T/go-build564981435=/tmp/go-build -gno-record-gcc-switches -fno-common""

</pre></details>

### What did you do?

<!--
extracted grammar production rules from go-spec.html

to find erroneous line, search for ""OperandName = identifier | QualifiedIdent.""
-->



### What did you expect to see?

""OperandName = identifier | QualifiedIdent .""


### What did you see instead?

""OperandName = identifier | QualifiedIdent.""
",1.0,"doc: go-spec.html missing space before . on line 2416, OperandName = identifier | QualifiedIdent. - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
go 1.13.5

(line 2416 is as of current master)

</pre>

### Does this issue reproduce with the latest release?

yes 

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env

GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/user2/Library/Caches/go-build""
GOENV=""/Users/user2/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/user2/A/AL3/code/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/8v/vpckwgfs4_547sb94qr9f4d40000gq/T/go-build564981435=/tmp/go-build -gno-record-gcc-switches -fno-common""

</pre></details>

### What did you do?

<!--
extracted grammar production rules from go-spec.html

to find erroneous line, search for ""OperandName = identifier | QualifiedIdent.""
-->



### What did you expect to see?

""OperandName = identifier | QualifiedIdent .""


### What did you see instead?

""OperandName = identifier | QualifiedIdent.""
",1,doc  go spec html missing space before   on line    operandname   identifier   qualifiedident          please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version          go           line   is as of current master              does this issue reproduce with the latest release     yes         what operating system and processor architecture are you using   go env          go env  output       go env          goarch      gobin     gocache   users   library caches go build   goenv   users   library application support go env   goexe     goflags     gohostarch      gohostos  darwin   gonoproxy     gonosumdb     goos  darwin   gopath   users   a   code go   goprivate     goproxy     goroot   usr local go   gosumdb  sum golang org   gotmpdir     gotooldir   usr local go pkg tool darwin     gccgo  gccgo   ar  ar   cc  clang   cxx  clang     cgo enabled      gomod     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders       t go    tmp go build  gno record gcc switches  fno common               what did you do           extracted grammar production rules from go spec html    to find erroneous line  search for  operandname   identifier   qualifiedident                   what did you expect to see      operandname   identifier   qualifiedident             what did you see instead      operandname   identifier   qualifiedident    ,1
90389,18145223217.0,IssuesEvent,2021-09-25 09:57:04,edudata-plus/tools,https://api.github.com/repos/edudata-plus/tools,closed,例外対応: 音符記号のリスト,code2broader,"例：


テキスト | コード
-- | --
全音符 | 8280300290100000
付点二分音符 | 8280300290200000
二分音符 | 8280300290300000
付点四分音符 | 8280300290400000
四分音符 | 8280300290500000
付点八分音符 | 8280300290600000
八分音符 | 8280300290700000
十六分音符 | 8280300290800000
付点八分音符と十六分音符 | 8280300290900000
四分休符 | 8280300291000000
八分休符 | 8280300291100000
",1.0,"例外対応: 音符記号のリスト - 例：


テキスト | コード
-- | --
全音符 | 8280300290100000
付点二分音符 | 8280300290200000
二分音符 | 8280300290300000
付点四分音符 | 8280300290400000
四分音符 | 8280300290500000
付点八分音符 | 8280300290600000
八分音符 | 8280300290700000
十六分音符 | 8280300290800000
付点八分音符と十六分音符 | 8280300290900000
四分休符 | 8280300291000000
八分休符 | 8280300291100000
",0,例外対応  音符記号のリスト   例：      テキスト   コード           全音符      付点二分音符      二分音符      付点四分音符      四分音符      付点八分音符      八分音符      十六分音符      付点八分音符と十六分音符      四分休符      八分休符      ,0
25476,5168164356.0,IssuesEvent,2017-01-17 20:50:24,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: go bug help message is outdated,Documentation NeedsFix,"```
$ gotip version
go version devel +39e31d5ec0 Thu Jan 12 04:50:46 2017 +0000 linux/amd64
```

Change 896ac677b5e3e80278cc1ce179d8a077ac3a6d2f modified the `bug` subcommand to make it open the system browser and pre-fill an issue template (instead of just dumping the infos to the screen), but the subcommand help string was not updated accordingly.

It is certainly unexpected that a command that is currently documented like this:

```
$ gotip bug -h
usage: bug

Bug prints information that helps file effective bug reports.

Bugs may be reported at https://golang.org/issue/new.
```

opens my browser and uses it to display a pre-filled github issue.",1.0,"cmd/go: go bug help message is outdated - ```
$ gotip version
go version devel +39e31d5ec0 Thu Jan 12 04:50:46 2017 +0000 linux/amd64
```

Change 896ac677b5e3e80278cc1ce179d8a077ac3a6d2f modified the `bug` subcommand to make it open the system browser and pre-fill an issue template (instead of just dumping the infos to the screen), but the subcommand help string was not updated accordingly.

It is certainly unexpected that a command that is currently documented like this:

```
$ gotip bug -h
usage: bug

Bug prints information that helps file effective bug reports.

Bugs may be reported at https://golang.org/issue/new.
```

opens my browser and uses it to display a pre-filled github issue.",1,cmd go  go bug help message is outdated          gotip version  go version devel    thu jan              linux           change   modified the  bug  subcommand to make it open the system browser and pre fill an issue template  instead of just dumping the infos to the screen   but the subcommand help string was not updated accordingly     it is certainly unexpected that a command that is currently documented like this            gotip bug  h  usage  bug    bug prints information that helps file effective bug reports     bugs may be reported at           opens my browser and uses it to display a pre filled github issue ,1
39218,6730758602.0,IssuesEvent,2017-10-18 03:08:28,golang/go,https://api.github.com/repos/golang/go,closed,database/sql: example usage for Out is incorrect,Documentation,"Hi,
Small thing, but please change example usage code for sql.Out from:
`_, err := db.ExecContext(ctx, ""ProcName"", sql.Named(""Arg1"", Out{Dest: &outArg}))`
to:
`_, err := db.ExecContext(ctx, ""ProcName"", sql.Named(""Arg1"", sql.Out{Dest: &outArg}))`

[Line 288 in database/sql/sql.go](https://golang.org/src/database/sql/sql.go?s=7393:7789#L288)


### What version of Go are you using (`go version`)?
Go 1.9

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
 linux/amd64 (Windows Subsystem for Linux)

### What did you do?
I copied the code in the example usage of the new Out parameter and the compiler complained about unknown type `Out`

### What did you expect to see?
N/A
### What did you see instead?
Compile error



",1.0,"database/sql: example usage for Out is incorrect - Hi,
Small thing, but please change example usage code for sql.Out from:
`_, err := db.ExecContext(ctx, ""ProcName"", sql.Named(""Arg1"", Out{Dest: &outArg}))`
to:
`_, err := db.ExecContext(ctx, ""ProcName"", sql.Named(""Arg1"", sql.Out{Dest: &outArg}))`

[Line 288 in database/sql/sql.go](https://golang.org/src/database/sql/sql.go?s=7393:7789#L288)


### What version of Go are you using (`go version`)?
Go 1.9

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
 linux/amd64 (Windows Subsystem for Linux)

### What did you do?
I copied the code in the example usage of the new Out parameter and the compiler complained about unknown type `Out`

### What did you expect to see?
N/A
### What did you see instead?
Compile error



",1,database sql  example usage for out is incorrect   hi   small thing  but please change example usage code for sql out from       err    db execcontext ctx   procname   sql named      out dest   outarg      to       err    db execcontext ctx   procname   sql named      sql out dest   outarg                     what version of go are you using   go version     go            does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env      linux    windows subsystem for linux         what did you do   i copied the code in the example usage of the new out parameter and the compiler complained about unknown type  out         what did you expect to see   n a      what did you see instead   compile error        ,1
53181,7809936650.0,IssuesEvent,2018-06-12 03:43:24,golang/go,https://api.github.com/repos/golang/go,closed,doc: setting GOROOT is not necessary when installing to custom location ,Documentation NeedsFix help wanted,"### What version of Go are you using (`go version`)?

go version go1.10.1 darwin/amd64

### Does this issue reproduce with the latest release?

Yes.

### What did you do?

1. Visit https://golang.org/dl/ and download a go1.10.1 tarball
2. Install to a custom location:
    ```
    $ cd /tmp
    $ tar -xzf ~/Downloads/go1.10.1.darwin-amd64.tar.gz
    $ go/bin/go env GOROOT
    /tmp/go
    ```

3. Visit https://golang.org/doc/install#tarball_non_standard and see the installation instructions

### What did you expect to see?

No need to set GOROOT, as it is indeed [not necessary in Go 1.10](https://golang.org/doc/go1.10#goroot).

### What did you see instead?

> For example, if you installed Go to your home directory you should add commands like the following to $HOME/.profile:
> 
> ```
> export GOROOT=$HOME/go1.X
> export PATH=$PATH:$GOROOT/bin
> ```
> 
> Note: GOROOT must be set only when installing to a custom location.


---

In https://github.com/golang/go/issues/18678#issue-201154131, @minux proposed to derive GOROOT from `os.Executable`...

> And then we can eliminate all mentions of GOROOT in user facing documents (in fact, we should actively discourage setting GOROOT in user facing documents.)

The change was implemented in [CL 42533](https://go-review.googlesource.com/42533), but the documentation was not updated to remove suggestions to set GOROOT.",1.0,"doc: setting GOROOT is not necessary when installing to custom location  - ### What version of Go are you using (`go version`)?

go version go1.10.1 darwin/amd64

### Does this issue reproduce with the latest release?

Yes.

### What did you do?

1. Visit https://golang.org/dl/ and download a go1.10.1 tarball
2. Install to a custom location:
    ```
    $ cd /tmp
    $ tar -xzf ~/Downloads/go1.10.1.darwin-amd64.tar.gz
    $ go/bin/go env GOROOT
    /tmp/go
    ```

3. Visit https://golang.org/doc/install#tarball_non_standard and see the installation instructions

### What did you expect to see?

No need to set GOROOT, as it is indeed [not necessary in Go 1.10](https://golang.org/doc/go1.10#goroot).

### What did you see instead?

> For example, if you installed Go to your home directory you should add commands like the following to $HOME/.profile:
> 
> ```
> export GOROOT=$HOME/go1.X
> export PATH=$PATH:$GOROOT/bin
> ```
> 
> Note: GOROOT must be set only when installing to a custom location.


---

In https://github.com/golang/go/issues/18678#issue-201154131, @minux proposed to derive GOROOT from `os.Executable`...

> And then we can eliminate all mentions of GOROOT in user facing documents (in fact, we should actively discourage setting GOROOT in user facing documents.)

The change was implemented in [CL 42533](https://go-review.googlesource.com/42533), but the documentation was not updated to remove suggestions to set GOROOT.",1,doc  setting goroot is not necessary when installing to custom location        what version of go are you using   go version       go version       darwin          does this issue reproduce with the latest release     yes         what did you do        visit   and download a       tarball     install to a custom location                  cd  tmp        tar  xzf   downloads       darwin   tar gz        go bin go env goroot       tmp go                visit   and see the installation instructions        what did you expect to see     no need to set goroot  as it is indeed            what did you see instead       for example  if you installed go to your home directory you should add commands like the following to  home  profile                export goroot  home   x    export path  path  goroot bin               note  goroot must be set only when installing to a custom location              in    minux proposed to derive goroot from  os executable          and then we can eliminate all mentions of goroot in user facing documents  in fact  we should actively discourage setting goroot in user facing documents      the change was implemented in     but the documentation was not updated to remove suggestions to set goroot ,1
539268,15786289946.0,IssuesEvent,2021-04-01 17:32:00,LLK/scratch-www,https://api.github.com/repos/LLK/scratch-www,closed,1.4 Download page should say Mac OS version 10.4-10.14,High Severity Low Impact good first issue help wanted mini priority 3,"1.4 Download page should say Mac OS version ""10.4 through 10.14""

Currently it says ""10.4 or later""",1.0,"1.4 Download page should say Mac OS version 10.4-10.14 - 1.4 Download page should say Mac OS version ""10.4 through 10.14""

Currently it says ""10.4 or later""",0,    download page should say mac os version               download page should say mac os version      through         currently it says      or later ,0
686826,23505772782.0,IssuesEvent,2022-08-18 12:30:36,Carbonable/carbonable-starknet,https://api.github.com/repos/Carbonable/carbonable-starknet,opened,Test refactoring,state: inactive priority: soon type: testing effort: 5 work: complicated,"# Proposition

The propopsition is mainly motivated by the growth of new features and SOC.
Since we are adding more and more contracts and features, it could be interesting to refactor tests.

## Integration tests

Integration tests focus on nominal usages by default, this is what aim the test_nominal_cases files of each contract.

We also want to test specific behaviors by chaining actions between contracts, this will be the purpose of the test_specific_cases file of each contract.

Notes:
- I think protostar generate a single instance of what the `__setup__` returns **for each test files** which could slow down tests and increase memory usage
- we need to check how to factorize the `__setup__` cheatcode

## Unit tests

Unit tests focus on the nominal cases and expect revert tests, since several tests are required per new functionnality (according to the number of exception raised by the function), there is an opportunity to spread tests per functionnality.

Note: A new library.cairo file could store shared code (as the one in the integration tests).

## Folder structure diagram

```
tests/
├── integrations/
│   ├── library.cairo
│   ├── minter/
│   │   └── test_nominal_cases.cairo
│   │   └── test_specific_cases.cairo
│   ├── yielder/
│   │   └── test_nominal_cases.cairo
│   │   └── test_specific_cases.cairo
│   ├── .../
├── mocks/
│   └── erc20.cairo
├── units/
│   ├── library.cairo
│   ├── minter/
│   │   ├── test_decrease_reserved_supply_for_mint.cairo
│   │   ├── test_...
│   │   ├── test_airdrop.cairo
│   │   ├── test_whitelist_buy.cairo
│   │   └── test_public_buy.cairo
│   ├── yielder/
│   │   └── test_...
```",1.0,"Test refactoring - # Proposition

The propopsition is mainly motivated by the growth of new features and SOC.
Since we are adding more and more contracts and features, it could be interesting to refactor tests.

## Integration tests

Integration tests focus on nominal usages by default, this is what aim the test_nominal_cases files of each contract.

We also want to test specific behaviors by chaining actions between contracts, this will be the purpose of the test_specific_cases file of each contract.

Notes:
- I think protostar generate a single instance of what the `__setup__` returns **for each test files** which could slow down tests and increase memory usage
- we need to check how to factorize the `__setup__` cheatcode

## Unit tests

Unit tests focus on the nominal cases and expect revert tests, since several tests are required per new functionnality (according to the number of exception raised by the function), there is an opportunity to spread tests per functionnality.

Note: A new library.cairo file could store shared code (as the one in the integration tests).

## Folder structure diagram

```
tests/
├── integrations/
│   ├── library.cairo
│   ├── minter/
│   │   └── test_nominal_cases.cairo
│   │   └── test_specific_cases.cairo
│   ├── yielder/
│   │   └── test_nominal_cases.cairo
│   │   └── test_specific_cases.cairo
│   ├── .../
├── mocks/
│   └── erc20.cairo
├── units/
│   ├── library.cairo
│   ├── minter/
│   │   ├── test_decrease_reserved_supply_for_mint.cairo
│   │   ├── test_...
│   │   ├── test_airdrop.cairo
│   │   ├── test_whitelist_buy.cairo
│   │   └── test_public_buy.cairo
│   ├── yielder/
│   │   └── test_...
```",0,test refactoring     proposition    the propopsition is mainly motivated by the growth of new features and soc   since we are adding more and more contracts and features  it could be interesting to refactor tests        integration tests    integration tests focus on nominal usages by default  this is what aim the test nominal cases files of each contract     we also want to test specific behaviors by chaining actions between contracts  this will be the purpose of the test specific cases file of each contract     notes     i think protostar generate a single instance of what the    setup    returns   for each test files   which could slow down tests and increase memory usage    we need to check how to factorize the    setup    cheatcode       unit tests    unit tests focus on the nominal cases and expect revert tests  since several tests are required per new functionnality  according to the number of exception raised by the function   there is an opportunity to spread tests per functionnality     note  a new library cairo file could store shared code  as the one in the integration tests         folder structure diagram         tests   ├── integrations   │   ├── library cairo  │   ├── minter   │   │   └── test nominal cases cairo  │   │   └── test specific cases cairo  │   ├── yielder   │   │   └── test nominal cases cairo  │   │   └── test specific cases cairo  │   ├──       ├── mocks   │   └──   cairo  ├── units   │   ├── library cairo  │   ├── minter   │   │   ├── test decrease reserved supply for mint cairo  │   │   ├── test      │   │   ├── test airdrop cairo  │   │   ├── test whitelist buy cairo  │   │   └── test public buy cairo  │   ├── yielder   │   │   └── test         ,0
130965,18214360562.0,IssuesEvent,2021-09-30 01:02:17,doc-ai/tensorflow,https://api.github.com/repos/doc-ai/tensorflow,opened,CVE-2021-37678 (High) detected in tensorflow-2.0.0b1-cp36-cp36m-manylinux1_x86_64.whl,security vulnerability,"## CVE-2021-37678 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-2.0.0b1-cp36-cp36m-manylinux1_x86_64.whl</b></p></summary>

<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href=""https://files.pythonhosted.org/packages/29/6c/2c9a5c4d095c63c2fb37d20def0e4f92685f7aee9243d6aae25862694fd1/tensorflow-2.0.0b1-cp36-cp36m-manylinux1_x86_64.whl"">https://files.pythonhosted.org/packages/29/6c/2c9a5c4d095c63c2fb37d20def0e4f92685f7aee9243d6aae25862694fd1/tensorflow-2.0.0b1-cp36-cp36m-manylinux1_x86_64.whl</a></p>
<p>Path to dependency file: tensorflow/tensorflow/lite/micro/examples/magic_wand/train/requirements.txt</p>
<p>Path to vulnerable library: tensorflow/tensorflow/lite/micro/examples/magic_wand/train/requirements.txt</p>
<p>

Dependency Hierarchy:
  - :x: **tensorflow-2.0.0b1-cp36-cp36m-manylinux1_x86_64.whl** (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>  
  
TensorFlow is an end-to-end open source platform for machine learning. In affected versions TensorFlow and Keras can be tricked to perform arbitrary code execution when deserializing a Keras model from YAML format. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/python/keras/saving/model_config.py#L66-L104) uses `yaml.unsafe_load` which can perform arbitrary code execution on the input. Given that YAML format support requires a significant amount of work, we have removed it for now. We have patched the issue in GitHub commit 23d6383eb6c14084a8fc3bdf164043b974818012. 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-37678>CVE-2021-37678</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>8.8</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Changed
- Impact Metrics:
  - Confidentiality Impact: 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/tensorflow/tensorflow/security/advisories/GHSA-r6jx-9g48-2r5r"">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-r6jx-9g48-2r5r</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>

***
<!-- 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"":""Python"",""packageName"":""tensorflow"",""packageVersion"":""2.0.0b1"",""packageFilePaths"":[""/tensorflow/lite/micro/examples/magic_wand/train/requirements.txt""],""isTransitiveDependency"":false,""dependencyTree"":""tensorflow:2.0.0b1"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""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""}],""baseBranches"":[],""vulnerabilityIdentifier"":""CVE-2021-37678"",""vulnerabilityDetails"":""TensorFlow is an end-to-end open source platform for machine learning. In affected versions TensorFlow and Keras can be tricked to perform arbitrary code execution when deserializing a Keras model from YAML format. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/python/keras/saving/model_config.py#L66-L104) uses `yaml.unsafe_load` which can perform arbitrary code execution on the input. Given that YAML format support requires a significant amount of work, we have removed it for now. We have patched the issue in GitHub commit 23d6383eb6c14084a8fc3bdf164043b974818012. 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."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37678"",""cvss3Severity"":""high"",""cvss3Score"":""8.8"",""cvss3Metrics"":{""A"":""High"",""AC"":""Low"",""PR"":""Low"",""S"":""Changed"",""C"":""High"",""UI"":""None"",""AV"":""Local"",""I"":""High""},""extraData"":{}}</REMEDIATE> -->",True,"CVE-2021-37678 (High) detected in tensorflow-2.0.0b1-cp36-cp36m-manylinux1_x86_64.whl - ## CVE-2021-37678 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-2.0.0b1-cp36-cp36m-manylinux1_x86_64.whl</b></p></summary>

<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href=""https://files.pythonhosted.org/packages/29/6c/2c9a5c4d095c63c2fb37d20def0e4f92685f7aee9243d6aae25862694fd1/tensorflow-2.0.0b1-cp36-cp36m-manylinux1_x86_64.whl"">https://files.pythonhosted.org/packages/29/6c/2c9a5c4d095c63c2fb37d20def0e4f92685f7aee9243d6aae25862694fd1/tensorflow-2.0.0b1-cp36-cp36m-manylinux1_x86_64.whl</a></p>
<p>Path to dependency file: tensorflow/tensorflow/lite/micro/examples/magic_wand/train/requirements.txt</p>
<p>Path to vulnerable library: tensorflow/tensorflow/lite/micro/examples/magic_wand/train/requirements.txt</p>
<p>

Dependency Hierarchy:
  - :x: **tensorflow-2.0.0b1-cp36-cp36m-manylinux1_x86_64.whl** (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>  
  
TensorFlow is an end-to-end open source platform for machine learning. In affected versions TensorFlow and Keras can be tricked to perform arbitrary code execution when deserializing a Keras model from YAML format. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/python/keras/saving/model_config.py#L66-L104) uses `yaml.unsafe_load` which can perform arbitrary code execution on the input. Given that YAML format support requires a significant amount of work, we have removed it for now. We have patched the issue in GitHub commit 23d6383eb6c14084a8fc3bdf164043b974818012. 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-37678>CVE-2021-37678</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>8.8</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Changed
- Impact Metrics:
  - Confidentiality Impact: 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/tensorflow/tensorflow/security/advisories/GHSA-r6jx-9g48-2r5r"">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-r6jx-9g48-2r5r</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>

***
<!-- 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"":""Python"",""packageName"":""tensorflow"",""packageVersion"":""2.0.0b1"",""packageFilePaths"":[""/tensorflow/lite/micro/examples/magic_wand/train/requirements.txt""],""isTransitiveDependency"":false,""dependencyTree"":""tensorflow:2.0.0b1"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""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""}],""baseBranches"":[],""vulnerabilityIdentifier"":""CVE-2021-37678"",""vulnerabilityDetails"":""TensorFlow is an end-to-end open source platform for machine learning. In affected versions TensorFlow and Keras can be tricked to perform arbitrary code execution when deserializing a Keras model from YAML format. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/python/keras/saving/model_config.py#L66-L104) uses `yaml.unsafe_load` which can perform arbitrary code execution on the input. Given that YAML format support requires a significant amount of work, we have removed it for now. We have patched the issue in GitHub commit 23d6383eb6c14084a8fc3bdf164043b974818012. 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."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37678"",""cvss3Severity"":""high"",""cvss3Score"":""8.8"",""cvss3Metrics"":{""A"":""High"",""AC"":""Low"",""PR"":""Low"",""S"":""Changed"",""C"":""High"",""UI"":""None"",""AV"":""Local"",""I"":""High""},""extraData"":{}}</REMEDIATE> -->",0,cve      high  detected in tensorflow                 whl      cve       high 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  tensorflow tensorflow lite micro examples magic wand train requirements txt   path to vulnerable library  tensorflow tensorflow lite micro examples magic wand train requirements txt     dependency hierarchy       x    tensorflow                 whl    vulnerable library             vulnerability details         tensorflow is an end to end open source platform for machine learning  in affected versions tensorflow and keras can be tricked to perform arbitrary code execution when deserializing a keras model from yaml format  the     uses  yaml unsafe load  which can perform arbitrary code execution on the input  given that yaml format support requires a significant amount of work  we have removed it for now  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  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  tensorflow                               tensorflow cpu                               tensorflow gpu                                                  check this box to open an automated fix pr        isopenpronvulnerability  false  ispackagebased  true  isdefaultbranch  true  packages     istransitivedependency  false  dependencytree   tensorflow         isminimumfixversionavailable  true  minimumfixversion   tensorflow                               tensorflow cpu                               tensorflow gpu                                  basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   tensorflow is an end to end open source platform for machine learning  in affected versions tensorflow and keras can be tricked to perform arbitrary code execution when deserializing a keras model from yaml format  the     uses  yaml unsafe load  which can perform arbitrary code execution on the input  given that yaml format support requires a significant amount of work  we have removed it for now  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    vulnerabilityurl        ,0
14667,3873105535.0,IssuesEvent,2016-04-11 15:52:08,golang/go,https://api.github.com/repos/golang/go,reopened,net/http: document that Error() does not terminate the current handler,Documentation,"Using `go1.6`

I recently saw code that did the following:
```
func serveHTTP(resp http.ResponseWriter, req *http.Request) {
    ...

    if err := foo(); err != nil {
        http.Error(resp, err.Error(), http.StatusInternalServerError)
    }

    if err := bar(); err != nil {
        http.Error(resp, err.Error(), http.StatusInternalServerError)
    }
}
```

The assumption made was that http.Error() terminates the current handler in some magical way. Instead, Error simply sets the headers and writes the body message, and it is the programmer's responsibility to return. We should document this.
",1.0,"net/http: document that Error() does not terminate the current handler - Using `go1.6`

I recently saw code that did the following:
```
func serveHTTP(resp http.ResponseWriter, req *http.Request) {
    ...

    if err := foo(); err != nil {
        http.Error(resp, err.Error(), http.StatusInternalServerError)
    }

    if err := bar(); err != nil {
        http.Error(resp, err.Error(), http.StatusInternalServerError)
    }
}
```

The assumption made was that http.Error() terminates the current handler in some magical way. Instead, Error simply sets the headers and writes the body message, and it is the programmer's responsibility to return. We should document this.
",1,net http  document that error   does not terminate the current handler   using          i recently saw code that did the following        func servehttp resp http responsewriter  req  http request                    if err    foo    err    nil            http error resp  err error    http statusinternalservererror                if err    bar    err    nil            http error resp  err error    http statusinternalservererror                    the assumption made was that http error   terminates the current handler in some magical way  instead  error simply sets the headers and writes the body message  and it is the programmer s responsibility to return  we should document this   ,1
106232,11473393682.0,IssuesEvent,2020-02-09 22:53:00,golang/go,https://api.github.com/repos/golang/go,closed,wiki: rename FileTreeDocumentation,Documentation NeedsDecision,"I'd like to rename the FileTreeDocumentation page to GoTree.

In alternative the name might simply be shortened to FileTree.
",1.0,"wiki: rename FileTreeDocumentation - I'd like to rename the FileTreeDocumentation page to GoTree.

In alternative the name might simply be shortened to FileTree.
",1,wiki  rename filetreedocumentation   i d like to rename the filetreedocumentation page to gotree     in alternative the name might simply be shortened to filetree   ,1
21587,4726882938.0,IssuesEvent,2016-10-18 11:46:47,golang/go,https://api.github.com/repos/golang/go,closed,net: InterfaceAddrs is not good for multi-homed IP node,Documentation NeedsFix,"I propose adding the missing Zone field to IPNet structure.

A trouble: The lack of IPv6 addressing scope information makes IPNet less usable. For example, when we have an IPNet and it represents an IPv6 link-local address, it's hard for us to distinguish the address belongs to which link/network interface.

A workaround: Rescan IP routing information by using Interfaces function and Addrs method of Interface structure (and play a guessing game when the address comes from foreign packages because it's possible to have the same IPv6 link-local address on all the equipped links.)

Proposal:  From Go 1.6 the network interface and interface address identification feature works correctly for both IPv4 and IPv6 on tier-1 platforms. I think it makes sense to add Zone field to IPNet structure the same as {IP,TCP,UDP}Addr structures like the following:
```
type IPNet struct {
        IP   IP     // network number
        Mask IPMask // network mask
        Zone string // IPv6 scoped addressing zone
}
```
make IPNet.String return ""fe80::1%en0/64"" and ParseCIDR function being able to parse IPv6 address prefix literal including zone identifier such as ""fe80::1%en0/64"". Also network interface and interface address identification feature comprised of Interfaces function and Addrs method of Interface structure behaves the same as IP address resolution and connection setup features; just handles unicast IPv6 link-local addressing scope information only.

An implementation: https://go-review.googlesource.com/#/c/19946/",1.0,"net: InterfaceAddrs is not good for multi-homed IP node - I propose adding the missing Zone field to IPNet structure.

A trouble: The lack of IPv6 addressing scope information makes IPNet less usable. For example, when we have an IPNet and it represents an IPv6 link-local address, it's hard for us to distinguish the address belongs to which link/network interface.

A workaround: Rescan IP routing information by using Interfaces function and Addrs method of Interface structure (and play a guessing game when the address comes from foreign packages because it's possible to have the same IPv6 link-local address on all the equipped links.)

Proposal:  From Go 1.6 the network interface and interface address identification feature works correctly for both IPv4 and IPv6 on tier-1 platforms. I think it makes sense to add Zone field to IPNet structure the same as {IP,TCP,UDP}Addr structures like the following:
```
type IPNet struct {
        IP   IP     // network number
        Mask IPMask // network mask
        Zone string // IPv6 scoped addressing zone
}
```
make IPNet.String return ""fe80::1%en0/64"" and ParseCIDR function being able to parse IPv6 address prefix literal including zone identifier such as ""fe80::1%en0/64"". Also network interface and interface address identification feature comprised of Interfaces function and Addrs method of Interface structure behaves the same as IP address resolution and connection setup features; just handles unicast IPv6 link-local addressing scope information only.

An implementation: https://go-review.googlesource.com/#/c/19946/",1,net  interfaceaddrs is not good for multi homed ip node   i propose adding the missing zone field to ipnet structure     a trouble  the lack of   addressing scope information makes ipnet less usable  for example  when we have an ipnet and it represents an   link local address  it s hard for us to distinguish the address belongs to which link network interface     a workaround  rescan ip routing information by using interfaces function and addrs method of interface structure  and play a guessing game when the address comes from foreign packages because it s possible to have the same   link local address on all the equipped links      proposal   from go     the network interface and interface address identification feature works correctly for both   and   on tier   platforms  i think it makes sense to add zone field to ipnet structure the same as  ip tcp udp addr structures like the following        type ipnet struct            ip   ip        network number          mask ipmask    network mask          zone string      scoped addressing zone          make ipnet string return            and parsecidr function being able to parse   address prefix literal including zone identifier such as             also network interface and interface address identification feature comprised of interfaces function and addrs method of interface structure behaves the same as ip address resolution and connection setup features  just handles unicast   link local addressing scope information only     an implementation   ,1
351207,25017835309.0,IssuesEvent,2022-11-03 20:33:20,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/gopls: design/document new release policy,Documentation gopls Tools,"### Background

Historically, we've endeavored to do a new gopls release ~monthly, in order to stay up-to-date with dependencies and minimize delta. Typically we'd cut a new minor version (e.g. gopls@v0.9.0) whenever there is a significant improvement that we'd like to highlight. At this point we'd create a new release branch (e.g. gopls-release-branch.0.9), and subsequently merge from master to the release branch whenever we cut patch releases (e.g. gopls@v0.9.1).

### Problems

There are some problems with this model that we'd like to solve:
1. **Releasing is tedious**. Releasing involves multiple CLs, smoke testing, writing release notes, etc. We are working on integrating with the release team's new [Relui](https://github.com/golang/build/tree/master/cmd/relui) automation, which should make the _process_ of releasing easier, but it doesn't eliminate the need for manual verification of releases, writing release notes, or promoting the prerelease.
2. **Releasing is risky**. For example, see #54459. While we continue to invest in testing and benchmarking, it is unfortunately true that
  a. gopls has significant technical debt that we're still paying down
  b. gopls interacts heavily with the operating system, and so is subject to differing behavior across platforms ([example](https://go.dev/issue/54007))
  c. gopls interacts with dozens of different editors and LSP clients, many of which have subtly different behavior ([example](https://go.dev/issue/54559))
  d. gopls has no telemetry, and user reports are sparse and sporadic
3. **Historically, releases haven't followed the spirit of semver**. While we try to associate minor versions with ""significant"" changes, we have introduced new features in patch versions. Because we have been merging from master, there is also no reason to expect that patch releases are incrementally more stable: we introduced breakages such as #54459 in patch releases.

### Proposed Change

I propose to address these problems by adopting a release policy more similar to that of the main Go distribution (albeit every 3 months rather than 6):

- **Only merge from master for `*.*.0` patch releases**.  Instead of merging for each patch release, only merge when we initially cut our minor version release branches, corresponding to the `*.*.0` patch release. Subsequent patch releases will contain only cherry-picked CLs, ideally only bug fixes.
- **Target minor releases every ~3 months**. Try to stick to a schedule of releasing new minor versions every 3 months. This will allow a regular pace of new features, and allow us to coordinate with the Go release, but will reduce churn.
- **Let new minor versions soak in prerelease for longer**.  In the past, we've let prereleases soak for a few days, longer if we think they are risky. With this new policy, I think new minor versions should soak in prerelease for at least two weeks.
- **Heavily promote minor version prereleases**. Recently we've tried promoting risky prereleases on gophers Slack, with moderate success. We can do more: a devlog, twitter post, or nightly channel for the main vscode-go extension. We can also encourage non-vscode LSP clients to have a nightly channel.
- **Fully automate patch releases**. If subsequent patch releases consist only of a small number of bug fixes, it should be possible to fully automate them in Relui, including their release notes and publication.
- **Target patch releases every ~month**. Since patch releases should be easy, releasing every month should no longer introduce significant toil.
- **Document this policy**, for reference and to set expectations.

CC @golang/tools-team ",1.0,"x/tools/gopls: design/document new release policy - ### Background

Historically, we've endeavored to do a new gopls release ~monthly, in order to stay up-to-date with dependencies and minimize delta. Typically we'd cut a new minor version (e.g. gopls@v0.9.0) whenever there is a significant improvement that we'd like to highlight. At this point we'd create a new release branch (e.g. gopls-release-branch.0.9), and subsequently merge from master to the release branch whenever we cut patch releases (e.g. gopls@v0.9.1).

### Problems

There are some problems with this model that we'd like to solve:
1. **Releasing is tedious**. Releasing involves multiple CLs, smoke testing, writing release notes, etc. We are working on integrating with the release team's new [Relui](https://github.com/golang/build/tree/master/cmd/relui) automation, which should make the _process_ of releasing easier, but it doesn't eliminate the need for manual verification of releases, writing release notes, or promoting the prerelease.
2. **Releasing is risky**. For example, see #54459. While we continue to invest in testing and benchmarking, it is unfortunately true that
  a. gopls has significant technical debt that we're still paying down
  b. gopls interacts heavily with the operating system, and so is subject to differing behavior across platforms ([example](https://go.dev/issue/54007))
  c. gopls interacts with dozens of different editors and LSP clients, many of which have subtly different behavior ([example](https://go.dev/issue/54559))
  d. gopls has no telemetry, and user reports are sparse and sporadic
3. **Historically, releases haven't followed the spirit of semver**. While we try to associate minor versions with ""significant"" changes, we have introduced new features in patch versions. Because we have been merging from master, there is also no reason to expect that patch releases are incrementally more stable: we introduced breakages such as #54459 in patch releases.

### Proposed Change

I propose to address these problems by adopting a release policy more similar to that of the main Go distribution (albeit every 3 months rather than 6):

- **Only merge from master for `*.*.0` patch releases**.  Instead of merging for each patch release, only merge when we initially cut our minor version release branches, corresponding to the `*.*.0` patch release. Subsequent patch releases will contain only cherry-picked CLs, ideally only bug fixes.
- **Target minor releases every ~3 months**. Try to stick to a schedule of releasing new minor versions every 3 months. This will allow a regular pace of new features, and allow us to coordinate with the Go release, but will reduce churn.
- **Let new minor versions soak in prerelease for longer**.  In the past, we've let prereleases soak for a few days, longer if we think they are risky. With this new policy, I think new minor versions should soak in prerelease for at least two weeks.
- **Heavily promote minor version prereleases**. Recently we've tried promoting risky prereleases on gophers Slack, with moderate success. We can do more: a devlog, twitter post, or nightly channel for the main vscode-go extension. We can also encourage non-vscode LSP clients to have a nightly channel.
- **Fully automate patch releases**. If subsequent patch releases consist only of a small number of bug fixes, it should be possible to fully automate them in Relui, including their release notes and publication.
- **Target patch releases every ~month**. Since patch releases should be easy, releasing every month should no longer introduce significant toil.
- **Document this policy**, for reference and to set expectations.

CC @golang/tools-team ",1,x tools gopls  design document new release policy       background    historically  we ve endeavored to do a new gopls release  monthly  in order to stay up to date with dependencies and minimize delta  typically we d cut a new minor version  e g  gopls        whenever there is a significant improvement that we d like to highlight  at this point we d create a new release branch  e g  gopls release branch       and subsequently merge from master to the release branch whenever we cut patch releases  e g  gopls                problems    there are some problems with this model that we d like to solve        releasing is tedious    releasing involves multiple cls  smoke testing  writing release notes  etc  we are working on integrating with the release team s new     automation  which should make the  process  of releasing easier  but it doesn t eliminate the need for manual verification of releases  writing release notes  or promoting the prerelease        releasing is risky    for example  see     while we continue to invest in testing and benchmarking  it is unfortunately true that    a  gopls has significant technical debt that we re still paying down    b  gopls interacts heavily with the operating system  and so is subject to differing behavior across platforms         c  gopls interacts with dozens of different editors and lsp clients  many of which have subtly different behavior         d  gopls has no telemetry  and user reports are sparse and sporadic       historically  releases haven t followed the spirit of semver    while we try to associate minor versions with  significant  changes  we have introduced new features in patch versions  because we have been merging from master  there is also no reason to expect that patch releases are incrementally more stable  we introduced breakages such as    in patch releases         proposed change    i propose to address these problems by adopting a release policy more similar to that of the main go distribution  albeit every   months rather than            only merge from master for         patch releases     instead of merging for each patch release  only merge when we initially cut our minor version release branches  corresponding to the         patch release  subsequent patch releases will contain only cherry picked cls  ideally only bug fixes       target minor releases every    months    try to stick to a schedule of releasing new minor versions every   months  this will allow a regular pace of new features  and allow us to coordinate with the go release  but will reduce churn       let new minor versions soak in prerelease for longer     in the past  we ve let prereleases soak for a few days  longer if we think they are risky  with this new policy  i think new minor versions should soak in prerelease for at least two weeks       heavily promote minor version prereleases    recently we ve tried promoting risky prereleases on gophers slack  with moderate success  we can do more  a devlog  twitter post  or nightly channel for the main vscode go extension  we can also encourage non vscode lsp clients to have a nightly channel       fully automate patch releases    if subsequent patch releases consist only of a small number of bug fixes  it should be possible to fully automate them in relui  including their release notes and publication       target patch releases every  month    since patch releases should be easy  releasing every month should no longer introduce significant toil       document this policy    for reference and to set expectations     cc  golang tools team ,1
653159,21574070132.0,IssuesEvent,2022-05-02 11:53:29,thoth-station/investigator,https://api.github.com/repos/thoth-station/investigator,closed,Investigator v0.16.0 is not able to consume provenance kafka messages and schedule workload.,priority/critical-urgent kind/bug sig/devsecops,"Investigator v0.16.0 is not able to consume provenance kafka messages and schedule workload.
http://investigator-faust-web-thoth-infra-stage.apps.ocp4.prod.psi.redhat.com/metrics
Tested with: https://stage.thoth-station.ninja/api/v1/provenance/python/provenance-checker-220413103246-afc8d63e2ac31a4f

_Originally posted by @harshad16 in https://github.com/thoth-station/integration-tests/issues/309#issuecomment-1097912199_",1.0,"Investigator v0.16.0 is not able to consume provenance kafka messages and schedule workload. - Investigator v0.16.0 is not able to consume provenance kafka messages and schedule workload.
http://investigator-faust-web-thoth-infra-stage.apps.ocp4.prod.psi.redhat.com/metrics
Tested with: https://stage.thoth-station.ninja/api/v1/provenance/python/provenance-checker-220413103246-afc8d63e2ac31a4f

_Originally posted by @harshad16 in https://github.com/thoth-station/integration-tests/issues/309#issuecomment-1097912199_",0,investigator       is not able to consume provenance kafka messages and schedule workload    investigator       is not able to consume provenance kafka messages and schedule workload      tested with        originally posted by    in  ,0
95120,10866568624.0,IssuesEvent,2019-11-14 21:33:33,golang/go,https://api.github.com/repos/golang/go,closed,doc: doc/articles/wiki test failing when GOROOT is read-only,Documentation NeedsFix,"From https://build.golang.org/log/e704977e8e25fee42871ecc456d8e0045f01db3f (thanks @mengzhuo!):

```
##### ../doc/articles/wiki
go build command-line-arguments: copying /tmp/workdir-host-linux-mipsle-mengzhuo/tmp/go-build204611216/b001/exe/a.out: open get.bin: permission denied
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
2019/11/14 05:35:08 Failed: exit status 2
2019/11/14 05:35:09 FAILED
```

(Part of #28387, the continuing saga.)",1.0,"doc: doc/articles/wiki test failing when GOROOT is read-only - From https://build.golang.org/log/e704977e8e25fee42871ecc456d8e0045f01db3f (thanks @mengzhuo!):

```
##### ../doc/articles/wiki
go build command-line-arguments: copying /tmp/workdir-host-linux-mipsle-mengzhuo/tmp/go-build204611216/b001/exe/a.out: open get.bin: permission denied
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
2019/11/14 05:35:08 Failed: exit status 2
2019/11/14 05:35:09 FAILED
```

(Part of #28387, the continuing saga.)",1,doc  doc articles wiki test failing when goroot is read only   from    thanks  mengzhuo                     doc articles wiki  go build command line arguments  copying  tmp workdir host linux mipsle mengzhuo tmp go     exe a out  open get bin  permission denied  kill  usage  kill   pid   jobspec     or kill  l                failed  exit status                failed          part of     the continuing saga  ,1
55645,6488285947.0,IssuesEvent,2017-08-20 15:46:28,FireFly-WoW/FireFly-IssueTracker,https://api.github.com/repos/FireFly-WoW/FireFly-IssueTracker,closed,Mulgore res locations back to front,Confirmed - to be assigned Priority: Medium Status: Tested / Working,"**Description:**

The resurrection locations depending on where you die are backwards it seems.

**Current behaviour:**

When I died in Brambleblade Ravine I was spawned at the res point to the north and had to walk a long way back along the wall infront of red cloud mesa. When i died north of that res point, to the east of Bloodhoof Village, I spawned next to Red Cloud Mesa.

**Expected behaviour:**

The opposite of this.

**Steps to reproduce the problem:**

1. Die in brambleblade ravine, specifically outside the chieftan's hut
2. Die to the east of bloodhood village around 64, 60

**Screenshots:**
http://i.imgur.com/p5uWRjb.jpg
",1.0,"Mulgore res locations back to front - **Description:**

The resurrection locations depending on where you die are backwards it seems.

**Current behaviour:**

When I died in Brambleblade Ravine I was spawned at the res point to the north and had to walk a long way back along the wall infront of red cloud mesa. When i died north of that res point, to the east of Bloodhoof Village, I spawned next to Red Cloud Mesa.

**Expected behaviour:**

The opposite of this.

**Steps to reproduce the problem:**

1. Die in brambleblade ravine, specifically outside the chieftan's hut
2. Die to the east of bloodhood village around 64, 60

**Screenshots:**
http://i.imgur.com/p5uWRjb.jpg
",0,mulgore res locations back to front     description       the resurrection locations depending on where you die are backwards it seems       current behaviour       when i died in brambleblade ravine i was spawned at the res point to the north and had to walk a long way back along the wall infront of red cloud mesa  when i died north of that res point  to the east of bloodhoof village  i spawned next to red cloud mesa       expected behaviour       the opposite of this       steps to reproduce the problem          die in brambleblade ravine  specifically outside the chieftan s hut     die to the east of bloodhood village around           screenshots        ,0
313243,23464649324.0,IssuesEvent,2022-08-16 15:41:46,golang/go,https://api.github.com/repos/golang/go,closed,go install OR docs inconsistent to install multiple versions,Documentation,"### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.15.15 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/user/.cache/go-build""
GOENV=""/home/user/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/user/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/user/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/opt/go/1.18""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/opt/go/1.18/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build482777503=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

1. cd to a go module.
2. execute install as instructed in https://go.dev/doc/manage-install

```sh
$ go install golang.org/dl/go1.17.0@latest
```

### What did you expect to see?

```
$ go1.17.0 version
> return a value
```

### What did you see instead?

```
> go install golang.org/dl/go1.17.0@latest
> package golang.org/dl/go1.17.0@latest: can only use path@version syntax with 'go get'
$ go1.17.0 version
> 
```
",1.0,"go install OR docs inconsistent to install multiple versions - ### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.15.15 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/user/.cache/go-build""
GOENV=""/home/user/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/user/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/user/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/opt/go/1.18""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/opt/go/1.18/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build482777503=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

1. cd to a go module.
2. execute install as instructed in https://go.dev/doc/manage-install

```sh
$ go install golang.org/dl/go1.17.0@latest
```

### What did you expect to see?

```
$ go1.17.0 version
> return a value
```

### What did you see instead?

```
> go install golang.org/dl/go1.17.0@latest
> package golang.org/dl/go1.17.0@latest: can only use path@version syntax with 'go get'
$ go1.17.0 version
> 
```
",1,go install or docs inconsistent to install multiple versions       what version of go are you using   go version            go version  go version       linux             does this issue reproduce with the latest release     yes         what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   home user  cache go build   goenv   home user  config go env   goexe     goflags     gohostarch      gohostos  linux   goinsecure     gomodcache   home user go pkg mod   gonoproxy     gonosumdb     goos  linux   gopath   home user go   goprivate     goproxy     goroot   opt go       gosumdb  sum golang org   gotmpdir     gotooldir   opt go     pkg tool linux     gccgo  gccgo   ar  ar   cc  gcc   cxx  g     cgo enabled      gomod     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches             what did you do        cd to a go module      execute install as instructed in         sh    go install golang org dl       latest             what did you expect to see                  version    return a value             what did you see instead            go install golang org dl       latest    package golang org dl       latest  can only use path version syntax with  go get           version           ,1
75842,15495618012.0,IssuesEvent,2021-03-11 01:10:56,Hackagroup/BirdsEye,https://api.github.com/repos/Hackagroup/BirdsEye,opened,CVE-2020-28168 (Medium) detected in axios-0.21.0.tgz,security vulnerability,"## CVE-2020-28168 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>axios-0.21.0.tgz</b></p></summary>

<p>Promise based HTTP client for the browser and node.js</p>
<p>Library home page: <a href=""https://registry.npmjs.org/axios/-/axios-0.21.0.tgz"">https://registry.npmjs.org/axios/-/axios-0.21.0.tgz</a></p>
<p>Path to dependency file: BirdsEye/client/package.json</p>
<p>Path to vulnerable library: BirdsEye/client/node_modules/axios/package.json</p>
<p>

Dependency Hierarchy:
  - :x: **axios-0.21.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>main</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>  
  
Axios NPM package 0.21.0 contains a Server-Side Request Forgery (SSRF) vulnerability where an attacker is able to bypass a proxy by providing a URL that responds with a redirect to a restricted host or IP address.

<p>Publish Date: 2020-11-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28168>CVE-2020-28168</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.9</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: None
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/axios/axios/commit/c7329fefc890050edd51e40e469a154d0117fc55"">https://github.com/axios/axios/commit/c7329fefc890050edd51e40e469a154d0117fc55</a></p>
<p>Release Date: 2020-11-06</p>
<p>Fix Resolution: axios - 0.21.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-28168 (Medium) detected in axios-0.21.0.tgz - ## CVE-2020-28168 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>axios-0.21.0.tgz</b></p></summary>

<p>Promise based HTTP client for the browser and node.js</p>
<p>Library home page: <a href=""https://registry.npmjs.org/axios/-/axios-0.21.0.tgz"">https://registry.npmjs.org/axios/-/axios-0.21.0.tgz</a></p>
<p>Path to dependency file: BirdsEye/client/package.json</p>
<p>Path to vulnerable library: BirdsEye/client/node_modules/axios/package.json</p>
<p>

Dependency Hierarchy:
  - :x: **axios-0.21.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>main</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>  
  
Axios NPM package 0.21.0 contains a Server-Side Request Forgery (SSRF) vulnerability where an attacker is able to bypass a proxy by providing a URL that responds with a redirect to a restricted host or IP address.

<p>Publish Date: 2020-11-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28168>CVE-2020-28168</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.9</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: None
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/axios/axios/commit/c7329fefc890050edd51e40e469a154d0117fc55"">https://github.com/axios/axios/commit/c7329fefc890050edd51e40e469a154d0117fc55</a></p>
<p>Release Date: 2020-11-06</p>
<p>Fix Resolution: axios - 0.21.1</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      medium  detected in axios       tgz      cve       medium severity vulnerability     vulnerable library    axios       tgz      promise based http client for the browser and node js   library home page   a href     path to dependency file  birdseye client package json   path to vulnerable library  birdseye client node modules axios package json     dependency hierarchy       x    axios       tgz    vulnerable library   found in base branch   main              vulnerability details         axios npm package       contains a server side request forgery  ssrf  vulnerability where an attacker is able to bypass a proxy by providing a url that responds with a redirect to a restricted host or ip address    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  none     availability impact  none   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  axios                       step up your open source security game with whitesource    ,0
211595,23833166704.0,IssuesEvent,2022-09-06 01:10:19,KDWSS/dd-trace-java,https://api.github.com/repos/KDWSS/dd-trace-java,opened,CVE-2022-38751 (Medium) detected in multiple libraries,security vulnerability,"## CVE-2022-38751 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>snakeyaml-1.23.jar</b>, <b>snakeyaml-1.12.jar</b>, <b>snakeyaml-1.28.jar</b>, <b>snakeyaml-1.26.jar</b>, <b>snakeyaml-1.15.jar</b>, <b>snakeyaml-1.16.jar</b>, <b>snakeyaml-1.19.jar</b>, <b>snakeyaml-1.27.jar</b>, <b>snakeyaml-1.17.jar</b>, <b>snakeyaml-1.21.jar</b>, <b>snakeyaml-1.13.jar</b>, <b>snakeyaml-1.25.jar</b>, <b>snakeyaml-1.6.jar</b></p></summary>
<p>

<details><summary><b>snakeyaml-1.23.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://www.snakeyaml.org"">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dd-java-agent/instrumentation/jax-rs-annotations-2/jax-rs-annotations-2.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.23/ec62d74fe50689c28c0ff5b35d3aebcaa8b5be68/snakeyaml-1.23.jar</p>
<p>

Dependency Hierarchy:
  - dropwizard-testing-1.3.29.jar (Root Library)
    - dropwizard-core-1.3.29.jar
      - dropwizard-configuration-1.3.29.jar
        - jackson-dataformat-yaml-2.9.10.jar
          - :x: **snakeyaml-1.23.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.12.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://www.snakeyaml.org"">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dd-java-agent/instrumentation/elasticsearch/elasticsearch.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.12/ebe66a6b88caab31d7a19571ad23656377523545/snakeyaml-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.12/ebe66a6b88caab31d7a19571ad23656377523545/snakeyaml-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.12/ebe66a6b88caab31d7a19571ad23656377523545/snakeyaml-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.12/ebe66a6b88caab31d7a19571ad23656377523545/snakeyaml-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.12/ebe66a6b88caab31d7a19571ad23656377523545/snakeyaml-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.12/ebe66a6b88caab31d7a19571ad23656377523545/snakeyaml-1.12.jar</p>
<p>

Dependency Hierarchy:
  - dropwizard-testing-0.8.0.jar (Root Library)
    - dropwizard-core-0.8.0.jar
      - dropwizard-configuration-0.8.0.jar
        - jackson-dataformat-yaml-2.5.1.jar
          - :x: **snakeyaml-1.12.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.28.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://www.snakeyaml.org"">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dd-java-agent/instrumentation/spring-rabbit/spring-rabbit.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.28/7cae037c3014350c923776548e71c9feb7a69259/snakeyaml-1.28.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.28/7cae037c3014350c923776548e71c9feb7a69259/snakeyaml-1.28.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.28/7cae037c3014350c923776548e71c9feb7a69259/snakeyaml-1.28.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.28/7cae037c3014350c923776548e71c9feb7a69259/snakeyaml-1.28.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-starter-webflux-2.5.0.jar (Root Library)
    - spring-boot-starter-2.5.0.jar
      - :x: **snakeyaml-1.28.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.26.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://www.snakeyaml.org"">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dd-java-agent/agent-jmxfetch/agent-jmxfetch.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.26/snakeyaml-1.26.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.26/snakeyaml-1.26.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.26/snakeyaml-1.26.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.26/snakeyaml-1.26.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.26/snakeyaml-1.26.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-dependencies-2.3.5.RELEASE.pom (Root Library)
    - :x: **snakeyaml-1.26.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.15.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://www.snakeyaml.org"">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dd-smoke-tests/play-2.4/play-2.4.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.15/3b132bea69e8ee099f416044970997bde80f4ea6/snakeyaml-1.15.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.15/3b132bea69e8ee099f416044970997bde80f4ea6/snakeyaml-1.15.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.15/3b132bea69e8ee099f416044970997bde80f4ea6/snakeyaml-1.15.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.15/3b132bea69e8ee099f416044970997bde80f4ea6/snakeyaml-1.15.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.15/3b132bea69e8ee099f416044970997bde80f4ea6/snakeyaml-1.15.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.15/3b132bea69e8ee099f416044970997bde80f4ea6/snakeyaml-1.15.jar</p>
<p>

Dependency Hierarchy:
  - transport-6.0.0.jar (Root Library)
    - elasticsearch-6.0.0.jar
      - :x: **snakeyaml-1.15.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.16.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://www.snakeyaml.org"">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dd-smoke-tests/play-2.5/play-2.5.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.16/d64fb662c9e42789149f5078a62a22edda786c6a/snakeyaml-1.16.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.16/d64fb662c9e42789149f5078a62a22edda786c6a/snakeyaml-1.16.jar</p>
<p>

Dependency Hierarchy:
  - play-java_2.11-2.5.0.jar (Root Library)
    - :x: **snakeyaml-1.16.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.19.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://www.snakeyaml.org"">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dd-java-agent/instrumentation/spring-webflux-5/spring-webflux-5.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.19/2d998d3d674b172a588e54ab619854d073f555b5/snakeyaml-1.19.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.19/2d998d3d674b172a588e54ab619854d073f555b5/snakeyaml-1.19.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-starter-test-2.0.9.RELEASE.jar (Root Library)
    - spring-boot-starter-2.0.9.RELEASE.jar
      - :x: **snakeyaml-1.19.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.27.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://www.snakeyaml.org"">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dd-java-agent/instrumentation/spring-rabbit/spring-rabbit.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.27/359d62567480b07a679dc643f82fc926b100eed5/snakeyaml-1.27.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.27/359d62567480b07a679dc643f82fc926b100eed5/snakeyaml-1.27.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.27/359d62567480b07a679dc643f82fc926b100eed5/snakeyaml-1.27.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.27/359d62567480b07a679dc643f82fc926b100eed5/snakeyaml-1.27.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.27/359d62567480b07a679dc643f82fc926b100eed5/snakeyaml-1.27.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.27/359d62567480b07a679dc643f82fc926b100eed5/snakeyaml-1.27.jar</p>
<p>

Dependency Hierarchy:
  - ratpack-groovy-test-1.10.0-milestone-4.jar (Root Library)
    - ratpack-test-1.10.0-milestone-4.jar
      - ratpack-core-1.10.0-milestone-4.jar
        - :x: **snakeyaml-1.27.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.17.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://www.snakeyaml.org"">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dd-java-agent/instrumentation/elasticsearch/rest-7/rest-7.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.17/7a27ea250c5130b2922b86dea63cbb1cc10a660c/snakeyaml-1.17.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.17/7a27ea250c5130b2922b86dea63cbb1cc10a660c/snakeyaml-1.17.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.17/7a27ea250c5130b2922b86dea63cbb1cc10a660c/snakeyaml-1.17.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.17/7a27ea250c5130b2922b86dea63cbb1cc10a660c/snakeyaml-1.17.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.17/7a27ea250c5130b2922b86dea63cbb1cc10a660c/snakeyaml-1.17.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.17/7a27ea250c5130b2922b86dea63cbb1cc10a660c/snakeyaml-1.17.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.17/7a27ea250c5130b2922b86dea63cbb1cc10a660c/snakeyaml-1.17.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.17/7a27ea250c5130b2922b86dea63cbb1cc10a660c/snakeyaml-1.17.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.17/7a27ea250c5130b2922b86dea63cbb1cc10a660c/snakeyaml-1.17.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.17/7a27ea250c5130b2922b86dea63cbb1cc10a660c/snakeyaml-1.17.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.17/7a27ea250c5130b2922b86dea63cbb1cc10a660c/snakeyaml-1.17.jar</p>
<p>

Dependency Hierarchy:
  - elasticsearch-6.8.20.jar (Root Library)
    - elasticsearch-x-content-6.8.20.jar
      - :x: **snakeyaml-1.17.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.21.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://www.snakeyaml.org"">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dd-java-agent/instrumentation/mule-4/mule-4.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.21/18775fdda48574784f40b47bf478ab0593f92e4d/snakeyaml-1.21.jar</p>
<p>

Dependency Hierarchy:
  - mule-core-4.2.2.jar (Root Library)
    - :x: **snakeyaml-1.21.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.13.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://www.snakeyaml.org"">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dd-java-agent/instrumentation/play-2.3/play-2.3.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.13/73cbb494a912866c4c831a178c3a2a9169f4eaad/snakeyaml-1.13.jar</p>
<p>

Dependency Hierarchy:
  - play-java_2.11-2.3.9.jar (Root Library)
    - :x: **snakeyaml-1.13.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.25.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://www.snakeyaml.org"">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dd-smoke-tests/springboot-openliberty/application/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.25/snakeyaml-1.25.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-starter-web-2.2.7.RELEASE.jar (Root Library)
    - spring-boot-starter-2.2.7.RELEASE.jar
      - :x: **snakeyaml-1.25.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.6.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://code.google.com/p/snakeyaml/"">http://code.google.com/p/snakeyaml/</a></p>
<p>Path to dependency file: /dd-java-agent/instrumentation/testng-6.4/testng-6.4.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.6/a1e23e31c424d566ee27382e373d73a28fdabd88/snakeyaml-1.6.jar</p>
<p>

Dependency Hierarchy:
  - testng-6.4.jar (Root Library)
    - :x: **snakeyaml-1.6.jar** (Vulnerable Library)
</details>

<p>Found in HEAD commit: <a href=""https://github.com/KDWSS/dd-trace-java/commit/2819174635979a19573ec0ce8e3e2b63a3848079"">2819174635979a19573ec0ce8e3e2b63a3848079</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>  
  
Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.

<p>Publish Date: 2022-09-05
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-38751>CVE-2022-38751</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: 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>
",True,"CVE-2022-38751 (Medium) detected in multiple libraries - ## CVE-2022-38751 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>snakeyaml-1.23.jar</b>, <b>snakeyaml-1.12.jar</b>, <b>snakeyaml-1.28.jar</b>, <b>snakeyaml-1.26.jar</b>, <b>snakeyaml-1.15.jar</b>, <b>snakeyaml-1.16.jar</b>, <b>snakeyaml-1.19.jar</b>, <b>snakeyaml-1.27.jar</b>, <b>snakeyaml-1.17.jar</b>, <b>snakeyaml-1.21.jar</b>, <b>snakeyaml-1.13.jar</b>, <b>snakeyaml-1.25.jar</b>, <b>snakeyaml-1.6.jar</b></p></summary>
<p>

<details><summary><b>snakeyaml-1.23.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://www.snakeyaml.org"">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dd-java-agent/instrumentation/jax-rs-annotations-2/jax-rs-annotations-2.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.23/ec62d74fe50689c28c0ff5b35d3aebcaa8b5be68/snakeyaml-1.23.jar</p>
<p>

Dependency Hierarchy:
  - dropwizard-testing-1.3.29.jar (Root Library)
    - dropwizard-core-1.3.29.jar
      - dropwizard-configuration-1.3.29.jar
        - jackson-dataformat-yaml-2.9.10.jar
          - :x: **snakeyaml-1.23.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.12.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://www.snakeyaml.org"">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dd-java-agent/instrumentation/elasticsearch/elasticsearch.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.12/ebe66a6b88caab31d7a19571ad23656377523545/snakeyaml-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.12/ebe66a6b88caab31d7a19571ad23656377523545/snakeyaml-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.12/ebe66a6b88caab31d7a19571ad23656377523545/snakeyaml-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.12/ebe66a6b88caab31d7a19571ad23656377523545/snakeyaml-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.12/ebe66a6b88caab31d7a19571ad23656377523545/snakeyaml-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.12/ebe66a6b88caab31d7a19571ad23656377523545/snakeyaml-1.12.jar</p>
<p>

Dependency Hierarchy:
  - dropwizard-testing-0.8.0.jar (Root Library)
    - dropwizard-core-0.8.0.jar
      - dropwizard-configuration-0.8.0.jar
        - jackson-dataformat-yaml-2.5.1.jar
          - :x: **snakeyaml-1.12.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.28.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://www.snakeyaml.org"">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dd-java-agent/instrumentation/spring-rabbit/spring-rabbit.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.28/7cae037c3014350c923776548e71c9feb7a69259/snakeyaml-1.28.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.28/7cae037c3014350c923776548e71c9feb7a69259/snakeyaml-1.28.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.28/7cae037c3014350c923776548e71c9feb7a69259/snakeyaml-1.28.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.28/7cae037c3014350c923776548e71c9feb7a69259/snakeyaml-1.28.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-starter-webflux-2.5.0.jar (Root Library)
    - spring-boot-starter-2.5.0.jar
      - :x: **snakeyaml-1.28.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.26.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://www.snakeyaml.org"">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dd-java-agent/agent-jmxfetch/agent-jmxfetch.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.26/snakeyaml-1.26.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.26/snakeyaml-1.26.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.26/snakeyaml-1.26.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.26/snakeyaml-1.26.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.26/snakeyaml-1.26.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-dependencies-2.3.5.RELEASE.pom (Root Library)
    - :x: **snakeyaml-1.26.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.15.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://www.snakeyaml.org"">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dd-smoke-tests/play-2.4/play-2.4.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.15/3b132bea69e8ee099f416044970997bde80f4ea6/snakeyaml-1.15.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.15/3b132bea69e8ee099f416044970997bde80f4ea6/snakeyaml-1.15.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.15/3b132bea69e8ee099f416044970997bde80f4ea6/snakeyaml-1.15.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.15/3b132bea69e8ee099f416044970997bde80f4ea6/snakeyaml-1.15.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.15/3b132bea69e8ee099f416044970997bde80f4ea6/snakeyaml-1.15.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.15/3b132bea69e8ee099f416044970997bde80f4ea6/snakeyaml-1.15.jar</p>
<p>

Dependency Hierarchy:
  - transport-6.0.0.jar (Root Library)
    - elasticsearch-6.0.0.jar
      - :x: **snakeyaml-1.15.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.16.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://www.snakeyaml.org"">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dd-smoke-tests/play-2.5/play-2.5.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.16/d64fb662c9e42789149f5078a62a22edda786c6a/snakeyaml-1.16.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.16/d64fb662c9e42789149f5078a62a22edda786c6a/snakeyaml-1.16.jar</p>
<p>

Dependency Hierarchy:
  - play-java_2.11-2.5.0.jar (Root Library)
    - :x: **snakeyaml-1.16.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.19.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://www.snakeyaml.org"">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dd-java-agent/instrumentation/spring-webflux-5/spring-webflux-5.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.19/2d998d3d674b172a588e54ab619854d073f555b5/snakeyaml-1.19.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.19/2d998d3d674b172a588e54ab619854d073f555b5/snakeyaml-1.19.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-starter-test-2.0.9.RELEASE.jar (Root Library)
    - spring-boot-starter-2.0.9.RELEASE.jar
      - :x: **snakeyaml-1.19.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.27.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://www.snakeyaml.org"">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dd-java-agent/instrumentation/spring-rabbit/spring-rabbit.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.27/359d62567480b07a679dc643f82fc926b100eed5/snakeyaml-1.27.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.27/359d62567480b07a679dc643f82fc926b100eed5/snakeyaml-1.27.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.27/359d62567480b07a679dc643f82fc926b100eed5/snakeyaml-1.27.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.27/359d62567480b07a679dc643f82fc926b100eed5/snakeyaml-1.27.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.27/359d62567480b07a679dc643f82fc926b100eed5/snakeyaml-1.27.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.27/359d62567480b07a679dc643f82fc926b100eed5/snakeyaml-1.27.jar</p>
<p>

Dependency Hierarchy:
  - ratpack-groovy-test-1.10.0-milestone-4.jar (Root Library)
    - ratpack-test-1.10.0-milestone-4.jar
      - ratpack-core-1.10.0-milestone-4.jar
        - :x: **snakeyaml-1.27.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.17.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://www.snakeyaml.org"">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dd-java-agent/instrumentation/elasticsearch/rest-7/rest-7.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.17/7a27ea250c5130b2922b86dea63cbb1cc10a660c/snakeyaml-1.17.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.17/7a27ea250c5130b2922b86dea63cbb1cc10a660c/snakeyaml-1.17.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.17/7a27ea250c5130b2922b86dea63cbb1cc10a660c/snakeyaml-1.17.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.17/7a27ea250c5130b2922b86dea63cbb1cc10a660c/snakeyaml-1.17.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.17/7a27ea250c5130b2922b86dea63cbb1cc10a660c/snakeyaml-1.17.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.17/7a27ea250c5130b2922b86dea63cbb1cc10a660c/snakeyaml-1.17.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.17/7a27ea250c5130b2922b86dea63cbb1cc10a660c/snakeyaml-1.17.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.17/7a27ea250c5130b2922b86dea63cbb1cc10a660c/snakeyaml-1.17.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.17/7a27ea250c5130b2922b86dea63cbb1cc10a660c/snakeyaml-1.17.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.17/7a27ea250c5130b2922b86dea63cbb1cc10a660c/snakeyaml-1.17.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.17/7a27ea250c5130b2922b86dea63cbb1cc10a660c/snakeyaml-1.17.jar</p>
<p>

Dependency Hierarchy:
  - elasticsearch-6.8.20.jar (Root Library)
    - elasticsearch-x-content-6.8.20.jar
      - :x: **snakeyaml-1.17.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.21.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://www.snakeyaml.org"">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dd-java-agent/instrumentation/mule-4/mule-4.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.21/18775fdda48574784f40b47bf478ab0593f92e4d/snakeyaml-1.21.jar</p>
<p>

Dependency Hierarchy:
  - mule-core-4.2.2.jar (Root Library)
    - :x: **snakeyaml-1.21.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.13.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://www.snakeyaml.org"">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dd-java-agent/instrumentation/play-2.3/play-2.3.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.13/73cbb494a912866c4c831a178c3a2a9169f4eaad/snakeyaml-1.13.jar</p>
<p>

Dependency Hierarchy:
  - play-java_2.11-2.3.9.jar (Root Library)
    - :x: **snakeyaml-1.13.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.25.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://www.snakeyaml.org"">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /dd-smoke-tests/springboot-openliberty/application/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.25/snakeyaml-1.25.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-starter-web-2.2.7.RELEASE.jar (Root Library)
    - spring-boot-starter-2.2.7.RELEASE.jar
      - :x: **snakeyaml-1.25.jar** (Vulnerable Library)
</details>
<details><summary><b>snakeyaml-1.6.jar</b></p></summary>

<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href=""http://code.google.com/p/snakeyaml/"">http://code.google.com/p/snakeyaml/</a></p>
<p>Path to dependency file: /dd-java-agent/instrumentation/testng-6.4/testng-6.4.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.6/a1e23e31c424d566ee27382e373d73a28fdabd88/snakeyaml-1.6.jar</p>
<p>

Dependency Hierarchy:
  - testng-6.4.jar (Root Library)
    - :x: **snakeyaml-1.6.jar** (Vulnerable Library)
</details>

<p>Found in HEAD commit: <a href=""https://github.com/KDWSS/dd-trace-java/commit/2819174635979a19573ec0ce8e3e2b63a3848079"">2819174635979a19573ec0ce8e3e2b63a3848079</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>  
  
Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.

<p>Publish Date: 2022-09-05
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-38751>CVE-2022-38751</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: 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>
",0,cve      medium  detected in multiple libraries      cve       medium severity vulnerability     vulnerable libraries    snakeyaml     jar    snakeyaml     jar    snakeyaml     jar    snakeyaml     jar    snakeyaml     jar    snakeyaml     jar    snakeyaml     jar    snakeyaml     jar    snakeyaml     jar    snakeyaml     jar    snakeyaml     jar    snakeyaml     jar    snakeyaml     jar          snakeyaml     jar      yaml     parser and emitter for java   library home page   a href     path to dependency file   dd java agent instrumentation jax rs annotations   jax rs annotations   gradle   path to vulnerable library   home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar     dependency hierarchy      dropwizard testing       jar  root library        dropwizard core       jar         dropwizard configuration       jar           jackson dataformat yaml       jar              x    snakeyaml     jar    vulnerable library       snakeyaml     jar      yaml     parser and emitter for java   library home page   a href     path to dependency file   dd java agent instrumentation elasticsearch elasticsearch gradle   path to vulnerable library   home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar     dependency hierarchy      dropwizard testing       jar  root library        dropwizard core       jar         dropwizard configuration       jar           jackson dataformat yaml       jar              x    snakeyaml     jar    vulnerable library       snakeyaml     jar      yaml     parser and emitter for java   library home page   a href     path to dependency file   dd java agent instrumentation spring rabbit spring rabbit gradle   path to vulnerable library   home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar     dependency hierarchy      spring boot starter webflux       jar  root library        spring boot starter       jar          x    snakeyaml     jar    vulnerable library       snakeyaml     jar      yaml     parser and emitter for java   library home page   a href     path to dependency file   dd java agent agent jmxfetch agent jmxfetch gradle   path to vulnerable library   home wss scanner    repository org yaml snakeyaml     snakeyaml     jar  home wss scanner    repository org yaml snakeyaml     snakeyaml     jar  home wss scanner    repository org yaml snakeyaml     snakeyaml     jar  home wss scanner    repository org yaml snakeyaml     snakeyaml     jar  home wss scanner    repository org yaml snakeyaml     snakeyaml     jar     dependency hierarchy      spring boot dependencies       release pom  root library         x    snakeyaml     jar    vulnerable library       snakeyaml     jar      yaml     parser and emitter for java   library home page   a href     path to dependency file   dd smoke tests play     play     gradle   path to vulnerable library   home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar     dependency hierarchy      transport       jar  root library        elasticsearch       jar          x    snakeyaml     jar    vulnerable library       snakeyaml     jar      yaml     parser and emitter for java   library home page   a href     path to dependency file   dd smoke tests play     play     gradle   path to vulnerable library   home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar     dependency hierarchy      play java           jar  root library         x    snakeyaml     jar    vulnerable library       snakeyaml     jar      yaml     parser and emitter for java   library home page   a href     path to dependency file   dd java agent instrumentation spring webflux   spring webflux   gradle   path to vulnerable library   home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar     dependency hierarchy      spring boot starter test       release jar  root library        spring boot starter       release jar          x    snakeyaml     jar    vulnerable library       snakeyaml     jar      yaml     parser and emitter for java   library home page   a href     path to dependency file   dd java agent instrumentation spring rabbit spring rabbit gradle   path to vulnerable library   home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar     dependency hierarchy      ratpack groovy test       milestone   jar  root library        ratpack test       milestone   jar         ratpack core       milestone   jar            x    snakeyaml     jar    vulnerable library       snakeyaml     jar      yaml     parser and emitter for java   library home page   a href     path to dependency file   dd java agent instrumentation elasticsearch rest   rest   gradle   path to vulnerable library   home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar  home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar     dependency hierarchy      elasticsearch       jar  root library        elasticsearch x content       jar          x    snakeyaml     jar    vulnerable library       snakeyaml     jar      yaml     parser and emitter for java   library home page   a href     path to dependency file   dd java agent instrumentation mule   mule   gradle   path to vulnerable library   home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar     dependency hierarchy      mule core       jar  root library         x    snakeyaml     jar    vulnerable library       snakeyaml     jar      yaml     parser and emitter for java   library home page   a href     path to dependency file   dd java agent instrumentation play     play     gradle   path to vulnerable library   home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar     dependency hierarchy      play java           jar  root library         x    snakeyaml     jar    vulnerable library       snakeyaml     jar      yaml     parser and emitter for java   library home page   a href     path to dependency file   dd smoke tests springboot openliberty application pom xml   path to vulnerable library   home wss scanner    repository org yaml snakeyaml     snakeyaml     jar     dependency hierarchy      spring boot starter web       release jar  root library        spring boot starter       release jar          x    snakeyaml     jar    vulnerable library       snakeyaml     jar      yaml     parser and emitter for java   library home page   a href     path to dependency file   dd java agent instrumentation testng     testng     gradle   path to vulnerable library   home wss scanner  gradle caches modules   files     org yaml snakeyaml       snakeyaml     jar     dependency hierarchy      testng     jar  root library         x    snakeyaml     jar    vulnerable library      found in head commit   a href     found in base branch   master              vulnerability details         using snakeyaml to parse untrusted yaml files may be vulnerable to denial of service attacks  dos   if the parser is running on user supplied input  an attacker may supply content that causes the parser to crash by stackoverflow    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     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           ,0
22061,4770831254.0,IssuesEvent,2016-10-26 16:14:27,golang/go,https://api.github.com/repos/golang/go,closed,doc: rephrase sentence about comments in Effective Go,Documentation,"In Effective Go, [Commentary](https://golang.org/doc/effective_go.html#commentary) section:

> If the name always begins the comment, the output of godoc can usefully be run through grep.

is better phrased as:

> If comments always begin with a name, the output of godoc can usefully be run through grep.
",1.0,"doc: rephrase sentence about comments in Effective Go - In Effective Go, [Commentary](https://golang.org/doc/effective_go.html#commentary) section:

> If the name always begins the comment, the output of godoc can usefully be run through grep.

is better phrased as:

> If comments always begin with a name, the output of godoc can usefully be run through grep.
",1,doc  rephrase sentence about comments in effective go   in effective go      section       if the name always begins the comment  the output of godoc can usefully be run through grep     is better phrased as       if comments always begin with a name  the output of godoc can usefully be run through grep   ,1
16727,9858863083.0,IssuesEvent,2019-06-20 08:13:52,tamirko/ksa2006_v1,https://api.github.com/repos/tamirko/ksa2006_v1,closed,CVE-2012-6708 (Medium) detected in jquery-1.7.2.min.js,security vulnerability,"## CVE-2012-6708 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jquery-1.7.2.min.js</b></p></summary>

<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href=""https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.2/jquery.min.js"">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.2/jquery.min.js</a></p>
<p>Path to vulnerable library: /ksa2006_v1/ksa-web-root/ksa-web/target/ROOT/rs/jquery/jquery-1.7.2.min.js,/ksa2006_v1/ksa-web-root/ksa-web/src/main/webapp/rs/jquery/jquery-1.7.2.min.js</p>
<p>

Dependency Hierarchy:
  - :x: **jquery-1.7.2.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://api.github.com/repos/tamirko/ksa2006_v1/commits/0a7c19bfbfbe5188078ad6638b6c5490525b1695"">0a7c19bfbfbe5188078ad6638b6c5490525b1695</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
jQuery before 1.9.0 is vulnerable to Cross-site Scripting (XSS) attacks. The jQuery(strInput) function does not differentiate selectors from HTML in a reliable fashion. In vulnerable versions, jQuery determined whether the input was HTML by looking for the '<' character anywhere in the string, giving attackers more flexibility when attempting to construct a malicious payload. In fixed versions, jQuery only deems the input to be HTML if it explicitly starts with the '<' character, limiting exploitability only to attackers who can control the beginning of a string, which is far less common.

<p>Publish Date: 2018-01-18
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-6708>CVE-2012-6708</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Changed
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2012-6708"">https://nvd.nist.gov/vuln/detail/CVE-2012-6708</a></p>
<p>Release Date: 2018-01-18</p>
<p>Fix Resolution: 1.9.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-2012-6708 (Medium) detected in jquery-1.7.2.min.js - ## CVE-2012-6708 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jquery-1.7.2.min.js</b></p></summary>

<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href=""https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.2/jquery.min.js"">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.2/jquery.min.js</a></p>
<p>Path to vulnerable library: /ksa2006_v1/ksa-web-root/ksa-web/target/ROOT/rs/jquery/jquery-1.7.2.min.js,/ksa2006_v1/ksa-web-root/ksa-web/src/main/webapp/rs/jquery/jquery-1.7.2.min.js</p>
<p>

Dependency Hierarchy:
  - :x: **jquery-1.7.2.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://api.github.com/repos/tamirko/ksa2006_v1/commits/0a7c19bfbfbe5188078ad6638b6c5490525b1695"">0a7c19bfbfbe5188078ad6638b6c5490525b1695</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
jQuery before 1.9.0 is vulnerable to Cross-site Scripting (XSS) attacks. The jQuery(strInput) function does not differentiate selectors from HTML in a reliable fashion. In vulnerable versions, jQuery determined whether the input was HTML by looking for the '<' character anywhere in the string, giving attackers more flexibility when attempting to construct a malicious payload. In fixed versions, jQuery only deems the input to be HTML if it explicitly starts with the '<' character, limiting exploitability only to attackers who can control the beginning of a string, which is far less common.

<p>Publish Date: 2018-01-18
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-6708>CVE-2012-6708</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Changed
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2012-6708"">https://nvd.nist.gov/vuln/detail/CVE-2012-6708</a></p>
<p>Release Date: 2018-01-18</p>
<p>Fix Resolution: 1.9.0</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      medium  detected in jquery       min js      cve       medium severity vulnerability     vulnerable library    jquery       min js      javascript library for dom operations   library home page   a href     path to vulnerable library       ksa web root ksa web target root rs jquery jquery       min js      ksa web root ksa web src main webapp rs jquery jquery       min js     dependency hierarchy       x    jquery       min js    vulnerable library   found in head commit   a href               vulnerability details         jquery before       is vulnerable to cross site scripting  xss  attacks  the jquery strinput  function does not differentiate selectors from html in a reliable fashion  in vulnerable versions  jquery determined whether the input was html by looking for the     character anywhere in the string  giving attackers more flexibility when attempting to construct a malicious payload  in fixed versions  jquery only deems the input to be html if it explicitly starts with the     character  limiting exploitability only to attackers who can control the beginning of a string  which is far less common    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  required     scope  changed   impact metrics      confidentiality impact  low     integrity impact  low     availability impact  none   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                      step up your open source security game with whitesource    ,0
274208,8558510081.0,IssuesEvent,2018-11-08 18:28:42,CSBiology/BioFSharp,https://api.github.com/repos/CSBiology/BioFSharp,opened,Refactoring and inclusion of our next generation sequencing pipeline,priority-high project-IO,"### Description
Several tools for the analysis of next generation sequencing data have been developed in the workgroup during the last months. These need to be refactored and added to the project. 
This includes:
 - modeling of the GeneOmnibus FTP server structure
 - SOFT reader
 - SRAToolkit wrapper
 - Nora wrapper
 - FastP wrapper
 ",1.0,"Refactoring and inclusion of our next generation sequencing pipeline - ### Description
Several tools for the analysis of next generation sequencing data have been developed in the workgroup during the last months. These need to be refactored and added to the project. 
This includes:
 - modeling of the GeneOmnibus FTP server structure
 - SOFT reader
 - SRAToolkit wrapper
 - Nora wrapper
 - FastP wrapper
 ",0,refactoring and inclusion of our next generation sequencing pipeline       description  several tools for the analysis of next generation sequencing data have been developed in the workgroup during the last months  these need to be refactored and added to the project    this includes      modeling of the geneomnibus ftp server structure     soft reader     sratoolkit wrapper     nora wrapper     fastp wrapper   ,0
337946,24563349809.0,IssuesEvent,2022-10-12 22:56:54,golang/go,https://api.github.com/repos/golang/go,closed,runtime/cgo: incorrectly handle SIGPIPE(and other signals) from non-Go thread,Documentation NeedsFix compiler/runtime,"<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.19.2 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/secret/.cache/go-build""
GOENV=""/home/secret/.config/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/secret/go/pkg/mod""
GOOS=""linux""
GOPATH=""/home/secret/go""
GOPROXY=""https://goproxy.cn|https://proxy.golang.org|direct""
GOROOT=""/data00/home/secret/go1.19""
GOSUMDB=""sum.golang.google.cn""
GOTMPDIR=""""
GOTOOLDIR=""/data00/home/secret/go1.19/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""go1.19.2""
GCCGO=""gccgo""
GOAMD64=""v1""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
GOWORK=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build457638227=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?
Following code is a minimal example. SIGPIPE raised from linux socket write, but can be reproduced by the following form.

According to the [document](https://pkg.go.dev/os/signal#hdr-SIGPIPE), SIGPIPE should be caught by default, without affect program, just like the kill line in `test` function. But in sub-thread created by pthread, the SIGPIPE trigger the runtime.raisebadsignal, and make program exit, like kill line in `subThread` function (uncomment it).


```go
package main

/*
#include <pthread.h>
#include <signal.h>
#include <unistd.h>
#include <sys/syscall.h>
#define gettid() syscall(SYS_gettid)

void *subThread(void *_)
{
    // kill(gettid(), SIGPIPE); // kill by thread id
    return NULL;
}

void test()
{
    pthread_t thread_id;
    pthread_create(&thread_id, NULL, subThread, NULL);
    pthread_join(thread_id, NULL);

    kill(gettid(), SIGPIPE);
}
*/
import ""C""

func main() {
	C.test()

	// should not exit
	select {}
}
```



### What did you expect to see?

Go runtime catch the SIGPIPE from thread created by pthread, and everything works fine.

### What did you see instead?
(uncomment kill function in `subThread`)
kill in `subThread` make program exit, kill in `test` make program continue running.",1.0,"runtime/cgo: incorrectly handle SIGPIPE(and other signals) from non-Go thread - <!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.19.2 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/secret/.cache/go-build""
GOENV=""/home/secret/.config/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/secret/go/pkg/mod""
GOOS=""linux""
GOPATH=""/home/secret/go""
GOPROXY=""https://goproxy.cn|https://proxy.golang.org|direct""
GOROOT=""/data00/home/secret/go1.19""
GOSUMDB=""sum.golang.google.cn""
GOTMPDIR=""""
GOTOOLDIR=""/data00/home/secret/go1.19/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""go1.19.2""
GCCGO=""gccgo""
GOAMD64=""v1""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
GOWORK=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build457638227=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?
Following code is a minimal example. SIGPIPE raised from linux socket write, but can be reproduced by the following form.

According to the [document](https://pkg.go.dev/os/signal#hdr-SIGPIPE), SIGPIPE should be caught by default, without affect program, just like the kill line in `test` function. But in sub-thread created by pthread, the SIGPIPE trigger the runtime.raisebadsignal, and make program exit, like kill line in `subThread` function (uncomment it).


```go
package main

/*
#include <pthread.h>
#include <signal.h>
#include <unistd.h>
#include <sys/syscall.h>
#define gettid() syscall(SYS_gettid)

void *subThread(void *_)
{
    // kill(gettid(), SIGPIPE); // kill by thread id
    return NULL;
}

void test()
{
    pthread_t thread_id;
    pthread_create(&thread_id, NULL, subThread, NULL);
    pthread_join(thread_id, NULL);

    kill(gettid(), SIGPIPE);
}
*/
import ""C""

func main() {
	C.test()

	// should not exit
	select {}
}
```



### What did you expect to see?

Go runtime catch the SIGPIPE from thread created by pthread, and everything works fine.

### What did you see instead?
(uncomment kill function in `subThread`)
kill in `subThread` make program exit, kill in `test` make program continue running.",1,runtime cgo  incorrectly handle sigpipe and other signals  from non go thread         please answer these questions before submitting your issue  thanks              what version of go are you using   go version            go version  go version       linux             does this issue reproduce with the latest release   yes          what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   home secret  cache go build   goenv   home secret  config go env   goexe     goexperiment     goflags     gohostarch      gohostos  linux   goinsecure     gomodcache   home secret go pkg mod   goos  linux   gopath   home secret go   goproxy     goroot     home secret       gosumdb  sum golang google cn   gotmpdir     gotooldir     home secret     pkg tool linux     govcs     goversion          gccgo  gccgo          ar  ar   cc  gcc   cxx  g     cgo enabled      gomod   dev null   gowork     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  wl   no gc sections  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches             what did you do   following code is a minimal example  sigpipe raised from linux socket write  but can be reproduced by the following form     according to the     sigpipe should be caught by default  without affect program  just like the kill line in  test  function  but in sub thread created by pthread  the sigpipe trigger the runtime raisebadsignal  and make program exit  like kill line in  subthread  function  uncomment it           go  package main         include     include     include     include     define gettid   syscall sys gettid     void  subthread void                kill gettid    sigpipe      kill by thread id      return null        void test           pthread t thread id       pthread create  thread id  null  subthread  null        pthread join thread id  null          kill gettid    sigpipe           import  c     func main      	c test      	   should not exit  	select                       what did you expect to see     go runtime catch the sigpipe from thread created by pthread  and everything works fine         what did you see instead    uncomment kill function in  subthread    kill in  subthread  make program exit  kill in  test  make program continue running ,1
49873,7544489717.0,IssuesEvent,2018-04-17 18:35:51,golang/go,https://api.github.com/repos/golang/go,closed,x/crypto/acme/autocert: clarify usage of (*Manager).GetCertificate,Documentation,"Would be nice to have a example of `cert, err := m.GetCertificate(...)` so the certificates can be used in GRPC. I fail to come up with a solution.
```go
    m := &autocert.Manager{
        Cache:      autocert.DirCache(""tls""),
        Prompt:     autocert.AcceptTOS,
        HostPolicy: autocert.HostWhitelist(""example.com""),
    }
    go http.ListenAndServe("":http"", m.HTTPHandler(nil))
    cert, err := m.GetCertificate(...)
    if err != nil {
        t.Fatalf(""Failed to generate certificates %s"", err)
    }
    creds := credentials.NewServerTLSFromCert(cert)
    srv := grpc.NewServer(grpc.Creds(creds))
    reflection.Register(srv)
```
https://godoc.org/golang.org/x/crypto/acme/autocert

https://stackoverflow.com/questions/49874945/acme-certificate-for-grpc",1.0,"x/crypto/acme/autocert: clarify usage of (*Manager).GetCertificate - Would be nice to have a example of `cert, err := m.GetCertificate(...)` so the certificates can be used in GRPC. I fail to come up with a solution.
```go
    m := &autocert.Manager{
        Cache:      autocert.DirCache(""tls""),
        Prompt:     autocert.AcceptTOS,
        HostPolicy: autocert.HostWhitelist(""example.com""),
    }
    go http.ListenAndServe("":http"", m.HTTPHandler(nil))
    cert, err := m.GetCertificate(...)
    if err != nil {
        t.Fatalf(""Failed to generate certificates %s"", err)
    }
    creds := credentials.NewServerTLSFromCert(cert)
    srv := grpc.NewServer(grpc.Creds(creds))
    reflection.Register(srv)
```
https://godoc.org/golang.org/x/crypto/acme/autocert

https://stackoverflow.com/questions/49874945/acme-certificate-for-grpc",1,x crypto acme autocert  clarify usage of   manager  getcertificate   would be nice to have a example of  cert  err    m getcertificate       so the certificates can be used in grpc  i fail to come up with a solution      go      m     autocert manager           cache       autocert dircache  tls             prompt      autocert accepttos           hostpolicy  autocert hostwhitelist  example com                go http listenandserve   http   m httphandler nil        cert  err    m getcertificate           if err    nil            t fatalf  failed to generate certificates  s   err              creds    credentials newservertlsfromcert cert       srv    grpc newserver grpc creds creds        reflection register srv              ,1
77964,15569907115.0,IssuesEvent,2021-03-17 01:16:13,Sam-Marx/anti_nude_bot,https://api.github.com/repos/Sam-Marx/anti_nude_bot,opened,CVE-2020-15202 (High) detected in tensorflow-1.14.0-cp27-cp27mu-manylinux1_x86_64.whl,security vulnerability,"## CVE-2020-15202 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-1.14.0-cp27-cp27mu-manylinux1_x86_64.whl</b></p></summary>

<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href=""https://files.pythonhosted.org/packages/d3/59/d88fe8c58ffb66aca21d03c0e290cd68327cc133591130c674985e98a482/tensorflow-1.14.0-cp27-cp27mu-manylinux1_x86_64.whl"">https://files.pythonhosted.org/packages/d3/59/d88fe8c58ffb66aca21d03c0e290cd68327cc133591130c674985e98a482/tensorflow-1.14.0-cp27-cp27mu-manylinux1_x86_64.whl</a></p>
<p>Path to dependency file: /anti_nude_bot/requirements.txt</p>
<p>Path to vulnerable library: teSource-ArchiveExtractor_0c4fd107-566e-4a98-973e-bda8edd30ae2/20190703163800_95826/20190703163719_depth_0/h5py-2.9.0-cp27-cp27mu-manylinux1_x86_64/h5py/tests/hl</p>
<p>

Dependency Hierarchy:
  - :x: **tensorflow-1.14.0-cp27-cp27mu-manylinux1_x86_64.whl** (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>  
  
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `Shard` API in TensorFlow expects the last argument to be a function taking two `int64` (i.e., `long long`) arguments. However, there are several places in TensorFlow where a lambda taking `int` or `int32` arguments is being used. In these cases, if the amount of work to be parallelized is large enough, integer truncation occurs. Depending on how the two arguments of the lambda are used, this can result in segfaults, read/write outside of heap allocated arrays, stack overflows, or data corruption. The issue is patched in commits 27b417360cbd671ef55915e4bb6bb06af8b8a832 and ca8c013b5e97b1373b3bb1c97ea655e69f31a575, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.

<p>Publish Date: 2020-09-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15202>CVE-2020-15202</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.0</b>)</summary>
<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>
</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-h6fg-mjxg-hqq4"">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6fg-mjxg-hqq4</a></p>
<p>Release Date: 2020-07-21</p>
<p>Fix Resolution: 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.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-15202 (High) detected in tensorflow-1.14.0-cp27-cp27mu-manylinux1_x86_64.whl - ## CVE-2020-15202 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-1.14.0-cp27-cp27mu-manylinux1_x86_64.whl</b></p></summary>

<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href=""https://files.pythonhosted.org/packages/d3/59/d88fe8c58ffb66aca21d03c0e290cd68327cc133591130c674985e98a482/tensorflow-1.14.0-cp27-cp27mu-manylinux1_x86_64.whl"">https://files.pythonhosted.org/packages/d3/59/d88fe8c58ffb66aca21d03c0e290cd68327cc133591130c674985e98a482/tensorflow-1.14.0-cp27-cp27mu-manylinux1_x86_64.whl</a></p>
<p>Path to dependency file: /anti_nude_bot/requirements.txt</p>
<p>Path to vulnerable library: teSource-ArchiveExtractor_0c4fd107-566e-4a98-973e-bda8edd30ae2/20190703163800_95826/20190703163719_depth_0/h5py-2.9.0-cp27-cp27mu-manylinux1_x86_64/h5py/tests/hl</p>
<p>

Dependency Hierarchy:
  - :x: **tensorflow-1.14.0-cp27-cp27mu-manylinux1_x86_64.whl** (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>  
  
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `Shard` API in TensorFlow expects the last argument to be a function taking two `int64` (i.e., `long long`) arguments. However, there are several places in TensorFlow where a lambda taking `int` or `int32` arguments is being used. In these cases, if the amount of work to be parallelized is large enough, integer truncation occurs. Depending on how the two arguments of the lambda are used, this can result in segfaults, read/write outside of heap allocated arrays, stack overflows, or data corruption. The issue is patched in commits 27b417360cbd671ef55915e4bb6bb06af8b8a832 and ca8c013b5e97b1373b3bb1c97ea655e69f31a575, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.

<p>Publish Date: 2020-09-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15202>CVE-2020-15202</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.0</b>)</summary>
<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>
</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-h6fg-mjxg-hqq4"">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6fg-mjxg-hqq4</a></p>
<p>Release Date: 2020-07-21</p>
<p>Fix Resolution: 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.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)",0,cve      high  detected in tensorflow                 whl      cve       high 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   anti nude bot requirements txt   path to vulnerable library  tesource archiveextractor                 depth                       tests hl     dependency hierarchy       x    tensorflow                 whl    vulnerable library             vulnerability details         in tensorflow before versions                            and        the  shard  api in tensorflow expects the last argument to be a function taking two      i e    long long   arguments  however  there are several places in tensorflow where a lambda taking  int  or     arguments is being used  in these cases  if the amount of work to be parallelized is large enough  integer truncation occurs  depending on how the two arguments of the lambda are used  this can result in segfaults  read write outside of heap allocated arrays  stack overflows  or data corruption  the issue is patched in commits   and    and is released in tensorflow versions                             or          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                                                  step up your open source security game with whitesource    ,0
406305,11889830602.0,IssuesEvent,2020-03-28 15:37:05,BlackbirdHQ/ublox-cellular-rs,https://api.github.com/repos/BlackbirdHQ/ublox-cellular-rs,closed,Continuous integration,enhancement 👍 priority: medium,"Add Github Actions CI to:

- [ ] Build using stable toolchain in `#[no_std]`
- [ ] Check Formatting & Clippy
- [ ] Run tests when #6 has landed",1.0,"Continuous integration - Add Github Actions CI to:

- [ ] Build using stable toolchain in `#[no_std]`
- [ ] Check Formatting & Clippy
- [ ] Run tests when #6 has landed",0,continuous integration   add github actions ci to         build using stable toolchain in           check formatting   clippy      run tests when    has landed,0
174562,6541185852.0,IssuesEvent,2017-09-01 18:42:25,zehro/UAH-Theatre,https://api.github.com/repos/zehro/UAH-Theatre,opened,"As a registered user, I want to add an item so that I can track the item within the application.",Feature Priority - High Team - Database Team - Front End,"## Story/Task Details
- [ ] Design Add Item UI Page
- [ ] Code back-end logic

## Acceptance Scenarios
Scenario 1: The item does not exist in the database yet
- Given the user fills out a form to add the item
- When the item information does not match an existing entry in the database
- Then a new item is created in the database and the user is informed that the item has been added successfully

Scenario 2: The item already existed in the database
- Given the user fills out a form to add the item
- When the item information matches an existing entry in the database
- Then  the user is informed that the item already exists and the request failed


## Done Done Criteria
1. The client has approved UI design
2. The user story is tested and validated by at least one other team member
3. The code is reviewed and passed any unit/acceptance tests
4. The code is merged with master branch",1.0,"As a registered user, I want to add an item so that I can track the item within the application. - ## Story/Task Details
- [ ] Design Add Item UI Page
- [ ] Code back-end logic

## Acceptance Scenarios
Scenario 1: The item does not exist in the database yet
- Given the user fills out a form to add the item
- When the item information does not match an existing entry in the database
- Then a new item is created in the database and the user is informed that the item has been added successfully

Scenario 2: The item already existed in the database
- Given the user fills out a form to add the item
- When the item information matches an existing entry in the database
- Then  the user is informed that the item already exists and the request failed


## Done Done Criteria
1. The client has approved UI design
2. The user story is tested and validated by at least one other team member
3. The code is reviewed and passed any unit/acceptance tests
4. The code is merged with master branch",0,as a registered user  i want to add an item so that i can track the item within the application       story task details      design add item ui page      code back end logic       acceptance scenarios  scenario    the item does not exist in the database yet    given the user fills out a form to add the item    when the item information does not match an existing entry in the database    then a new item is created in the database and the user is informed that the item has been added successfully    scenario    the item already existed in the database    given the user fills out a form to add the item    when the item information matches an existing entry in the database    then  the user is informed that the item already exists and the request failed         done done criteria     the client has approved ui design     the user story is tested and validated by at least one other team member     the code is reviewed and passed any unit acceptance tests     the code is merged with master branch,0
13681,10420601660.0,IssuesEvent,2019-09-16 01:36:48,APSIMInitiative/ApsimX,https://api.github.com/repos/APSIMInitiative/ApsimX,opened,Directory names with odd characters cause UI problems,bug interface/infrastructure,"In CSIRO we are moving to Microsoft OneDrive. When someone shares a directory with you, the directory, by default, syncs to your computer like this:

C:\Users\hol353\CSIRO\Moore, Andrew (A&F, Black Mountain) - R-13151 DARPA World Modelers.

The APSIM user interface can open .apsimx files within this directory but when you click Save you get: 
![image](https://user-images.githubusercontent.com/1943827/64930650-1a454a80-d876-11e9-87b4-3731f9920a5a.png)
Note the lack of any text. Also I notice that the file isn't being put on the most recent list on the home page. Everything else seems to be ok.",1.0,"Directory names with odd characters cause UI problems - In CSIRO we are moving to Microsoft OneDrive. When someone shares a directory with you, the directory, by default, syncs to your computer like this:

C:\Users\hol353\CSIRO\Moore, Andrew (A&F, Black Mountain) - R-13151 DARPA World Modelers.

The APSIM user interface can open .apsimx files within this directory but when you click Save you get: 
![image](https://user-images.githubusercontent.com/1943827/64930650-1a454a80-d876-11e9-87b4-3731f9920a5a.png)
Note the lack of any text. Also I notice that the file isn't being put on the most recent list on the home page. Everything else seems to be ok.",0,directory names with odd characters cause ui problems   in csiro we are moving to microsoft onedrive  when someone shares a directory with you  the directory  by default  syncs to your computer like this     c  users   csiro moore  andrew  a f  black mountain    r   darpa world modelers     the apsim user interface can open  apsimx files within this directory but when you click save you get          note the lack of any text  also i notice that the file isn t being put on the most recent list on the home page  everything else seems to be ok ,0
71372,15194340790.0,IssuesEvent,2021-02-16 03:21:41,devikab2b/whites4,https://api.github.com/repos/devikab2b/whites4,closed,CVE-2021-21290 (Medium) detected in netty-all-4.1.51.Final.jar - autoclosed,security vulnerability,"## CVE-2021-21290 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>netty-all-4.1.51.Final.jar</b></p></summary>

<p>Netty is an asynchronous event-driven network application framework for
    rapid development of maintainable high performance protocol servers and
    clients.</p>
<p>Library home page: <a href=""https://netty.io/"">https://netty.io/</a></p>
<p>Path to dependency file: whites4/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/io/netty/netty-all/4.1.51.Final/netty-all-4.1.51.Final.jar</p>
<p>

Dependency Hierarchy:
  - spark-core_2.12-3.1.0.jar (Root Library)
    - :x: **netty-all-4.1.51.Final.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/devikab2b/whites4/commit/2dfd140187b660d885ea5ec7b9eb49e235ca8dac"">2dfd140187b660d885ea5ec7b9eb49e235ca8dac</a></p>
<p>Found in base branch: <b>main</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>  
  
Netty is an open-source, asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. In Netty before version 4.1.59.Final there is a vulnerability on Unix-like systems involving an insecure temp file. When netty's multipart decoders are used local information disclosure can occur via the local system temporary directory if temporary storing uploads on the disk is enabled. On unix-like systems, the temporary directory is shared between all user. As such, writing to this directory using APIs that do not explicitly set the file/directory permissions can lead to information disclosure. Of note, this does not impact modern MacOS Operating Systems. The method ""File.createTempFile"" on unix-like systems creates a random file, but, by default will create this file with the permissions ""-rw-r--r--"". Thus, if sensitive information is written to this file, other local users can read this information. This is the case in netty's ""AbstractDiskHttpData"" is vulnerable. This has been fixed in version 4.1.59.Final. As a workaround, one may specify your own ""java.io.tmpdir"" when you start the JVM or use ""DefaultHttpDataFactory.setBaseDir(...)"" to set the directory to something that is only readable by the current user.

<p>Publish Date: 2021-02-08
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-21290>CVE-2021-21290</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.2</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: None
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/netty/netty/security/advisories/GHSA-5mcr-gq6c-3hq2"">https://github.com/netty/netty/security/advisories/GHSA-5mcr-gq6c-3hq2</a></p>
<p>Release Date: 2021-02-08</p>
<p>Fix Resolution: io.netty:netty-codec-http:4.1.59.Final</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-21290 (Medium) detected in netty-all-4.1.51.Final.jar - autoclosed - ## CVE-2021-21290 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>netty-all-4.1.51.Final.jar</b></p></summary>

<p>Netty is an asynchronous event-driven network application framework for
    rapid development of maintainable high performance protocol servers and
    clients.</p>
<p>Library home page: <a href=""https://netty.io/"">https://netty.io/</a></p>
<p>Path to dependency file: whites4/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/io/netty/netty-all/4.1.51.Final/netty-all-4.1.51.Final.jar</p>
<p>

Dependency Hierarchy:
  - spark-core_2.12-3.1.0.jar (Root Library)
    - :x: **netty-all-4.1.51.Final.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/devikab2b/whites4/commit/2dfd140187b660d885ea5ec7b9eb49e235ca8dac"">2dfd140187b660d885ea5ec7b9eb49e235ca8dac</a></p>
<p>Found in base branch: <b>main</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>  
  
Netty is an open-source, asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. In Netty before version 4.1.59.Final there is a vulnerability on Unix-like systems involving an insecure temp file. When netty's multipart decoders are used local information disclosure can occur via the local system temporary directory if temporary storing uploads on the disk is enabled. On unix-like systems, the temporary directory is shared between all user. As such, writing to this directory using APIs that do not explicitly set the file/directory permissions can lead to information disclosure. Of note, this does not impact modern MacOS Operating Systems. The method ""File.createTempFile"" on unix-like systems creates a random file, but, by default will create this file with the permissions ""-rw-r--r--"". Thus, if sensitive information is written to this file, other local users can read this information. This is the case in netty's ""AbstractDiskHttpData"" is vulnerable. This has been fixed in version 4.1.59.Final. As a workaround, one may specify your own ""java.io.tmpdir"" when you start the JVM or use ""DefaultHttpDataFactory.setBaseDir(...)"" to set the directory to something that is only readable by the current user.

<p>Publish Date: 2021-02-08
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-21290>CVE-2021-21290</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.2</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: None
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/netty/netty/security/advisories/GHSA-5mcr-gq6c-3hq2"">https://github.com/netty/netty/security/advisories/GHSA-5mcr-gq6c-3hq2</a></p>
<p>Release Date: 2021-02-08</p>
<p>Fix Resolution: io.netty:netty-codec-http:4.1.59.Final</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      medium  detected in netty all       final jar   autoclosed      cve       medium severity vulnerability     vulnerable library    netty all       final jar      netty is an asynchronous event driven network application framework for     rapid development of maintainable high performance protocol servers and     clients    library home page   a href     path to dependency file    pom xml   path to vulnerable library   home wss scanner    repository io netty netty all       final netty all       final jar     dependency hierarchy      spark core           jar  root library         x    netty all       final jar    vulnerable library   found in head commit   a href     found in base branch   main              vulnerability details         netty is an open source  asynchronous event driven network application framework for rapid development of maintainable high performance protocol servers   clients  in netty before version       final there is a vulnerability on unix like systems involving an insecure temp file  when netty s multipart decoders are used local information disclosure can occur via the local system temporary directory if temporary storing uploads on the disk is enabled  on unix like systems  the temporary directory is shared between all user  as such  writing to this directory using apis that do not explicitly set the file directory permissions can lead to information disclosure  of note  this does not impact modern macos operating systems  the method  file createtempfile  on unix like systems creates a random file  but  by default will create this file with the permissions   rw r  r     thus  if sensitive information is written to this file  other local users can read this information  this is the case in netty s  abstractdiskhttpdata  is vulnerable  this has been fixed in version       final  as a workaround  one may specify your own  java io tmpdir  when you start the jvm or use  defaulthttpdatafactory setbasedir       to set the directory to something that is only readable by the current user    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  local     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  none     availability impact  none   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  io netty netty codec http       final               step up your open source security game with whitesource    ,0
5313,2921979377.0,IssuesEvent,2015-06-25 07:14:34,golang/go,https://api.github.com/repos/golang/go,closed,"os/exec: Cmd can only be executed once, but that isn't documented",Documentation,"Once an exec.Cmd has been Run (e.g. through .Run, .Output or .CombinedOutput) calling one of these run methods again will result in an error.

1. This fact isn't documented.
2. The resulting error messages don't clearly identify what caused the problem.
3. This behaviour probably isn't necessary; for many commands it makes perfectly good sense to run them more than once.

I'm not talking about parallel execution here, this is running, checking the output, then running again.

Example error message from calling CombinedOutput more than once:
""exec: Stdout already set.""
http://play.golang.org/p/Aaj3Gbva_S",1.0,"os/exec: Cmd can only be executed once, but that isn't documented - Once an exec.Cmd has been Run (e.g. through .Run, .Output or .CombinedOutput) calling one of these run methods again will result in an error.

1. This fact isn't documented.
2. The resulting error messages don't clearly identify what caused the problem.
3. This behaviour probably isn't necessary; for many commands it makes perfectly good sense to run them more than once.

I'm not talking about parallel execution here, this is running, checking the output, then running again.

Example error message from calling CombinedOutput more than once:
""exec: Stdout already set.""
http://play.golang.org/p/Aaj3Gbva_S",1,os exec  cmd can only be executed once  but that isn t documented   once an exec cmd has been run  e g  through  run   output or  combinedoutput  calling one of these run methods again will result in an error        this fact isn t documented      the resulting error messages don t clearly identify what caused the problem      this behaviour probably isn t necessary  for many commands it makes perfectly good sense to run them more than once     i m not talking about parallel execution here  this is running  checking the output  then running again     example error message from calling combinedoutput more than once    exec  stdout already set     ,1
695390,23855037418.0,IssuesEvent,2022-09-06 22:09:07,microsoft/terminal,https://api.github.com/repos/microsoft/terminal,closed,Settings: Add links to documentation in the settings UI ,Help Wanted Product-Terminal Issue-Task Priority-3 Area-Settings UI,"The new Windows Terminal version has a settings UI. Great! But in a regular/typical window size it contains too much blank space, as you can see in the screenshot below.

![image](https://user-images.githubusercontent.com/32982430/114781237-b7c96e80-9d78-11eb-80e3-638ff5c3c8f7.png)

I mostly use my Terminal in a medium size to complete quick tasks. Maximizing or resizing the window just to have a better view of settings is inconvenient. 

- [ ] Add help links or link to documentation at the right side, just like system settings. 
- [ ] Make the footer smaller. 

~~My idea would be to expand the hamburger menu much sooner at smaller window sizes. Like showing it already on the 120x30 size. Because the main content of the settings doesn't fill much area in the width anyways. This is the minimum size to have an always expanded hamburger menu and you can see: there is still room left.~~
![image](https://user-images.githubusercontent.com/32982430/114782148-e431ba80-9d79-11eb-9fbc-7c8f2a3d98e9.png)


My screenresolution is 2736x1824 and I use 200% scaling (device: Surface Pro 7).",1.0,"Settings: Add links to documentation in the settings UI  - The new Windows Terminal version has a settings UI. Great! But in a regular/typical window size it contains too much blank space, as you can see in the screenshot below.

![image](https://user-images.githubusercontent.com/32982430/114781237-b7c96e80-9d78-11eb-80e3-638ff5c3c8f7.png)

I mostly use my Terminal in a medium size to complete quick tasks. Maximizing or resizing the window just to have a better view of settings is inconvenient. 

- [ ] Add help links or link to documentation at the right side, just like system settings. 
- [ ] Make the footer smaller. 

~~My idea would be to expand the hamburger menu much sooner at smaller window sizes. Like showing it already on the 120x30 size. Because the main content of the settings doesn't fill much area in the width anyways. This is the minimum size to have an always expanded hamburger menu and you can see: there is still room left.~~
![image](https://user-images.githubusercontent.com/32982430/114782148-e431ba80-9d79-11eb-9fbc-7c8f2a3d98e9.png)


My screenresolution is 2736x1824 and I use 200% scaling (device: Surface Pro 7).",0,settings  add links to documentation in the settings ui    the new windows terminal version has a settings ui  great  but in a regular typical window size it contains too much blank space  as you can see in the screenshot below             i mostly use my terminal in a medium size to complete quick tasks  maximizing or resizing the window just to have a better view of settings is inconvenient        add help links or link to documentation at the right side  just like system settings       make the footer smaller        my idea would be to expand the hamburger menu much sooner at smaller window sizes  like showing it already on the   size  because the main content of the settings doesn t fill much area in the width anyways  this is the minimum size to have an always expanded hamburger menu and you can see  there is still room left              my screenresolution is   and i use    scaling  device  surface pro    ,0
334803,29985600657.0,IssuesEvent,2023-06-25 07:29:13,cockroachdb/cockroach,https://api.github.com/repos/cockroachdb/cockroach,opened,pkg/ccl/testccl/workload/schemachange/schemachange_test: TestWorkload failed,C-test-failure O-robot T-sql-foundations branch-release-23.1,"pkg/ccl/testccl/workload/schemachange/schemachange_test.TestWorkload [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/10665329?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/10665329?buildTab=artifacts#/) on release-23.1 @ [dbf6ce8438742a73b9d17391c1ef868a4e7a9569](https://github.com/cockroachdb/cockroach/commits/dbf6ce8438742a73b9d17391c1ef868a4e7a9569):


```
1, 29, protected_ts_records, 32
1, 29, rangelog, 13
1, 29, replication_constraint_stats, 25
1, 29, replication_critical_localities, 26
1, 29, replication_stats, 27
1, 29, reports_meta, 28
1, 29, role_id_seq, 48
1, 29, role_members, 23
1, 29, role_options, 33
1, 29, scheduled_jobs, 37
1, 29, settings, 6
1, 29, span_configurations, 47
1, 29, span_stats_buckets, 55
1, 29, span_stats_samples, 56
1, 29, span_stats_tenant_boundaries, 57
1, 29, span_stats_unique_keys, 54
1, 29, sql_instances, 46
1, 29, sqlliveness, 39
1, 29, statement_activity, 60
1, 29, statement_bundle_chunks, 34
1, 29, statement_diagnostics, 36
1, 29, statement_diagnostics_requests, 35
1, 29, statement_statistics, 42
1, 29, table_statistics, 20
1, 29, task_payloads, 58
1, 29, tenant_id_seq, 62
1, 29, tenant_settings, 50
1, 29, tenant_tasks, 59
1, 29, tenant_usage, 45
1, 29, tenants, 8
1, 29, transaction_activity, 61
1, 29, transaction_statistics, 43
1, 29, ui, 14
1, 29, users, 4
1, 29, web_sessions, 19
1, 29, zones, 5
100, 0, public, 101
102, 0, public, 103
104, 0, public, 105
104, 0, schema109, 125
104, 105, _enum14, 112
104, 105, enum14, 111
104, 105, seq36, 110
104, 105, seq85, 123
104, 125, _enum112, 127
104, 125, enum112, 126
    schema_change_external_test.go:80: backup in /artifacts/tmp/_tmp/fcba020ca7cb44bf8385bd0e13bcbe2d/logTestWorkload2476893510
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/fcba020ca7cb44bf8385bd0e13bcbe2d/logTestWorkload2476893510
--- FAIL: TestWorkload (52.17s)
```
<p>Parameters: <code>TAGS=bazel,gss,deadlock</code>
</p>
<details><summary>Help</summary>
<p>

See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
</p>
</details>
<details><summary>Same failure on other branches</summary>
<p>

- #93779 pkg/ccl/testccl/workload/schemachange/schemachange_test: TestWorkload failed [C-test-failure O-robot T-sql-foundations branch-master]
</p>
</details>
/cc @cockroachdb/sql-foundations
<sub>

[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestWorkload.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
",1.0,"pkg/ccl/testccl/workload/schemachange/schemachange_test: TestWorkload failed - pkg/ccl/testccl/workload/schemachange/schemachange_test.TestWorkload [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/10665329?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/10665329?buildTab=artifacts#/) on release-23.1 @ [dbf6ce8438742a73b9d17391c1ef868a4e7a9569](https://github.com/cockroachdb/cockroach/commits/dbf6ce8438742a73b9d17391c1ef868a4e7a9569):


```
1, 29, protected_ts_records, 32
1, 29, rangelog, 13
1, 29, replication_constraint_stats, 25
1, 29, replication_critical_localities, 26
1, 29, replication_stats, 27
1, 29, reports_meta, 28
1, 29, role_id_seq, 48
1, 29, role_members, 23
1, 29, role_options, 33
1, 29, scheduled_jobs, 37
1, 29, settings, 6
1, 29, span_configurations, 47
1, 29, span_stats_buckets, 55
1, 29, span_stats_samples, 56
1, 29, span_stats_tenant_boundaries, 57
1, 29, span_stats_unique_keys, 54
1, 29, sql_instances, 46
1, 29, sqlliveness, 39
1, 29, statement_activity, 60
1, 29, statement_bundle_chunks, 34
1, 29, statement_diagnostics, 36
1, 29, statement_diagnostics_requests, 35
1, 29, statement_statistics, 42
1, 29, table_statistics, 20
1, 29, task_payloads, 58
1, 29, tenant_id_seq, 62
1, 29, tenant_settings, 50
1, 29, tenant_tasks, 59
1, 29, tenant_usage, 45
1, 29, tenants, 8
1, 29, transaction_activity, 61
1, 29, transaction_statistics, 43
1, 29, ui, 14
1, 29, users, 4
1, 29, web_sessions, 19
1, 29, zones, 5
100, 0, public, 101
102, 0, public, 103
104, 0, public, 105
104, 0, schema109, 125
104, 105, _enum14, 112
104, 105, enum14, 111
104, 105, seq36, 110
104, 105, seq85, 123
104, 125, _enum112, 127
104, 125, enum112, 126
    schema_change_external_test.go:80: backup in /artifacts/tmp/_tmp/fcba020ca7cb44bf8385bd0e13bcbe2d/logTestWorkload2476893510
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/fcba020ca7cb44bf8385bd0e13bcbe2d/logTestWorkload2476893510
--- FAIL: TestWorkload (52.17s)
```
<p>Parameters: <code>TAGS=bazel,gss,deadlock</code>
</p>
<details><summary>Help</summary>
<p>

See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
</p>
</details>
<details><summary>Same failure on other branches</summary>
<p>

- #93779 pkg/ccl/testccl/workload/schemachange/schemachange_test: TestWorkload failed [C-test-failure O-robot T-sql-foundations branch-master]
</p>
</details>
/cc @cockroachdb/sql-foundations
<sub>

[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestWorkload.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
",0,pkg ccl testccl workload schemachange schemachange test  testworkload failed   pkg ccl testccl workload schemachange schemachange test testworkload     with     on release                       protected ts records          rangelog          replication constraint stats          replication critical localities          replication stats          reports meta          role id seq          role members          role options          scheduled jobs          settings          span configurations          span stats buckets          span stats samples          span stats tenant boundaries          span stats unique keys          sql instances          sqlliveness          statement activity          statement bundle chunks          statement diagnostics          statement diagnostics requests          statement statistics          table statistics          task payloads          tenant id seq          tenant settings          tenant tasks          tenant usage          tenants          transaction activity          transaction statistics          ui          users          web sessions          zones          public          public          public                                                                                       schema change external test go    backup in  artifacts tmp  tmp         panic go       test log scope end    test logs left over in   artifacts tmp  tmp         fail  testworkload            parameters   tags bazel gss deadlock      help     see also            same failure on other branches          pkg ccl testccl workload schemachange schemachange test  testworkload failed        cc  cockroachdb sql foundations                ,0
10469,2944461493.0,IssuesEvent,2015-07-03 04:22:31,DriveAI/Website,https://api.github.com/repos/DriveAI/Website,closed,Progress page goals/updates user experience,design change,"Each of goals and updates need a place for a brief description of what we mean by goals and updates. We need a place to put an overview of how autonomous vehicles work so the goals seem like an exhaustive list instead of a collection of scattered milestones. The text-based updates should be visible upon reaching the page, either as the default content or side-by-side with the milestones.",1.0,"Progress page goals/updates user experience - Each of goals and updates need a place for a brief description of what we mean by goals and updates. We need a place to put an overview of how autonomous vehicles work so the goals seem like an exhaustive list instead of a collection of scattered milestones. The text-based updates should be visible upon reaching the page, either as the default content or side-by-side with the milestones.",0,progress page goals updates user experience   each of goals and updates need a place for a brief description of what we mean by goals and updates  we need a place to put an overview of how autonomous vehicles work so the goals seem like an exhaustive list instead of a collection of scattered milestones  the text based updates should be visible upon reaching the page  either as the default content or side by side with the milestones ,0
56236,8058588986.0,IssuesEvent,2018-08-02 18:58:19,golang/go,https://api.github.com/repos/golang/go,closed,doc: Contribution guidelines should specify git origin,Documentation,"I'm creating a duplicate of issue #10130, which was IMHO wrongly closed and then frozen. The contributing guide as it stands leaves out a key piece of information about how to contribute. Hunting around for it on the web isn't better than having it in the guide, even if including it makes the guide slightly more verbose.

Here is the text of the original issue, as valid now as when it was originally reported:

""The contribution guidelines don't mention that git origin should be https://go.googlesource.com/go.

git-codereview: git origin must be a Gerrit host, not GitHub: https://github.com/golang/go.git""
",1.0,"doc: Contribution guidelines should specify git origin - I'm creating a duplicate of issue #10130, which was IMHO wrongly closed and then frozen. The contributing guide as it stands leaves out a key piece of information about how to contribute. Hunting around for it on the web isn't better than having it in the guide, even if including it makes the guide slightly more verbose.

Here is the text of the original issue, as valid now as when it was originally reported:

""The contribution guidelines don't mention that git origin should be https://go.googlesource.com/go.

git-codereview: git origin must be a Gerrit host, not GitHub: https://github.com/golang/go.git""
",1,doc  contribution guidelines should specify git origin   i m creating a duplicate of issue     which was imho wrongly closed and then frozen  the contributing guide as it stands leaves out a key piece of information about how to contribute  hunting around for it on the web isn t better than having it in the guide  even if including it makes the guide slightly more verbose     here is the text of the original issue  as valid now as when it was originally reported      the contribution guidelines don t mention that git origin should be      git codereview  git origin must be a gerrit host  not github     ,1
109835,16892166550.0,IssuesEvent,2021-06-23 10:34:10,epam/TimeBase,https://api.github.com/repos/epam/TimeBase,closed,CVE-2018-19360 (High) detected in jackson-databind-2.9.6.jar - autoclosed,security vulnerability,"## CVE-2018-19360 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.6.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: TimeBase/java/installer/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.9.6/cfa4f316351a91bfd95cb0644c6a2c95f52db1fc/jackson-databind-2.9.6.jar</p>
<p>

Dependency Hierarchy:
  - izpack-compiler-5.1.3.jar (Root Library)
    - tika-parsers-1.19.jar
      - :x: **jackson-databind-2.9.6.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/epam/TimeBase/commit/76d75f5eb2971c940ed61bb66cd24661abe01546"">76d75f5eb2971c940ed61bb66cd24661abe01546</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>  
  
FasterXML jackson-databind 2.x before 2.9.8 might allow attackers to have unspecified impact by leveraging failure to block the axis2-transport-jms class from polymorphic deserialization.

<p>Publish Date: 2019-01-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19360>CVE-2018-19360</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19360"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19360</a></p>
<p>Release Date: 2019-01-02</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.7.9.5,2.8.11.3,2.9.8,2.10.0.pr1</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":false,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""com.fasterxml.jackson.core"",""packageName"":""jackson-databind"",""packageVersion"":""2.9.6"",""packageFilePaths"":[""/java/installer/build.gradle""],""isTransitiveDependency"":true,""dependencyTree"":""org.codehaus.izpack:izpack-compiler:5.1.3;org.apache.tika:tika-parsers:1.19;com.fasterxml.jackson.core:jackson-databind:2.9.6"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""com.fasterxml.jackson.core:jackson-databind:2.7.9.5,2.8.11.3,2.9.8,2.10.0.pr1""}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2018-19360"",""vulnerabilityDetails"":""FasterXML jackson-databind 2.x before 2.9.8 might allow attackers to have unspecified impact by leveraging failure to block the axis2-transport-jms class from polymorphic deserialization."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19360"",""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-2018-19360 (High) detected in jackson-databind-2.9.6.jar - autoclosed - ## CVE-2018-19360 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.6.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: TimeBase/java/installer/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.9.6/cfa4f316351a91bfd95cb0644c6a2c95f52db1fc/jackson-databind-2.9.6.jar</p>
<p>

Dependency Hierarchy:
  - izpack-compiler-5.1.3.jar (Root Library)
    - tika-parsers-1.19.jar
      - :x: **jackson-databind-2.9.6.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/epam/TimeBase/commit/76d75f5eb2971c940ed61bb66cd24661abe01546"">76d75f5eb2971c940ed61bb66cd24661abe01546</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>  
  
FasterXML jackson-databind 2.x before 2.9.8 might allow attackers to have unspecified impact by leveraging failure to block the axis2-transport-jms class from polymorphic deserialization.

<p>Publish Date: 2019-01-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19360>CVE-2018-19360</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19360"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19360</a></p>
<p>Release Date: 2019-01-02</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.7.9.5,2.8.11.3,2.9.8,2.10.0.pr1</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":false,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""com.fasterxml.jackson.core"",""packageName"":""jackson-databind"",""packageVersion"":""2.9.6"",""packageFilePaths"":[""/java/installer/build.gradle""],""isTransitiveDependency"":true,""dependencyTree"":""org.codehaus.izpack:izpack-compiler:5.1.3;org.apache.tika:tika-parsers:1.19;com.fasterxml.jackson.core:jackson-databind:2.9.6"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""com.fasterxml.jackson.core:jackson-databind:2.7.9.5,2.8.11.3,2.9.8,2.10.0.pr1""}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2018-19360"",""vulnerabilityDetails"":""FasterXML jackson-databind 2.x before 2.9.8 might allow attackers to have unspecified impact by leveraging failure to block the axis2-transport-jms class from polymorphic deserialization."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19360"",""cvss3Severity"":""high"",""cvss3Score"":""9.8"",""cvss3Metrics"":{""A"":""High"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""High"",""UI"":""None"",""AV"":""Network"",""I"":""High""},""extraData"":{}}</REMEDIATE> -->",0,cve      high  detected in jackson databind       jar   autoclosed      cve       high severity vulnerability     vulnerable library    jackson databind       jar      general data binding functionality for jackson  works on core streaming api   library home page   a href     path to dependency file  timebase java installer build gradle   path to vulnerable library   home wss scanner  gradle caches modules   files     com fasterxml jackson core jackson databind         jackson databind       jar     dependency hierarchy      izpack compiler       jar  root library        tika parsers     jar          x    jackson databind       jar    vulnerable library   found in head commit   a href     found in base branch   main              vulnerability details         fasterxml jackson databind   x before       might allow attackers to have unspecified impact by leveraging failure to block the   transport jms class from polymorphic deserialization    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  com fasterxml jackson core jackson databind                                            isopenpronvulnerability  false  ispackagebased  true  isdefaultbranch  true  packages     istransitivedependency  true  dependencytree   org codehaus izpack izpack compiler       org apache tika tika parsers     com fasterxml jackson core jackson databind         isminimumfixversionavailable  true  minimumfixversion   com fasterxml jackson core jackson databind                                   basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   fasterxml jackson databind   x before       might allow attackers to have unspecified impact by leveraging failure to block the   transport jms class from polymorphic deserialization    vulnerabilityurl        ,0
55720,23551948703.0,IssuesEvent,2022-08-21 23:44:35,jpmens/mqttwarn,https://api.github.com/repos/jpmens/mqttwarn,closed,[fbchat] Update fbchat service with last version v2.0.0a5,enhancement help wanted service plugin,Please make needed updates for fbchat service to cover changes in last version: https://github.com/fbchat-dev/fbchat - v2.0.0a5,1.0,[fbchat] Update fbchat service with last version v2.0.0a5 - Please make needed updates for fbchat service to cover changes in last version: https://github.com/fbchat-dev/fbchat - v2.0.0a5,0,  update fbchat service with last version         please make needed updates for fbchat service to cover changes in last version           ,0
173131,14403475725.0,IssuesEvent,2020-12-03 16:06:09,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.16: document log changes for Go 1.16,Documentation NeedsInvestigation help wanted release-blocker,"As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

<dl id=""log""><dt><a href=""/pkg/log/"">log</a></dt>
  <dd>
    <p><!-- CL 264460 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/264460"">https://golang.org/cl/264460</a>: expose std via new Default function
    </p>
  </dd>
</dl><!-- log -->

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.",1.0,"doc/go1.16: document log changes for Go 1.16 - As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

<dl id=""log""><dt><a href=""/pkg/log/"">log</a></dt>
  <dd>
    <p><!-- CL 264460 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/264460"">https://golang.org/cl/264460</a>: expose std via new Default function
    </p>
  </dd>
</dl><!-- log -->

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.",1,doc      document log changes for go       as of filing this issue  the     contained the following html        log                        todo    a href    expose std via new default function                           per     it s a release blocker for go     beta   to have a complete draft of the eventual release notes  and so the todo needs to be resolved     a sequence of steps to resolve this issue may be        come up with a draft release note entry in this issue  then move the issue to needsfix state      send a cl with  doc           and include  for     fixes   this issue    in the body ,1
63124,8658612228.0,IssuesEvent,2018-11-28 01:50:22,golang/go,https://api.github.com/repos/golang/go,closed,cmd/vet: restore documentation about vet flags,Documentation release-blocker,"The rearrangement of the vet tool, while a great step forward, seems to have lost the documentation of vet flags.

```
> go vet -help
usage: go vet [-n] [-x] [build flags] [vet flags] [packages]
Run 'go help vet' for details.

> go help vet
usage: go vet [-n] [-x] [build flags] [vet flags] [packages]

Vet runs the Go vet command on the packages named by the import paths.

For more about vet and its flags, see 'go doc cmd/vet'.
For more about specifying packages, see 'go help packages'.

The -n flag prints commands that would be executed.
The -x flag prints commands as they are executed.

The build flags supported by go vet are those that control package resolution
and execution, such as -n, -x, -v, -tags, and -toolexec.
For more about these flags, see 'go help build'.

See also: go fmt, go fix.

> go doc cmd/vet
The vet command is a driver for static checkers conforming to the
golang.org/x/tools/go/analysis API. Run it using 'go vet'.

For a tool capable of running standalone, use a multichecker-based tool such
as golang.org/x/tools/go/analysis/cmd/vet.

> go tool vet -help
vet is a tool for static analysis of Go programs.

Usage of vet:
	vet unit.cfg	# execute analysis specified by config file
	vet help		# general help
	vet help name	# help on specific analyzer and its flags
```

`go tool vet help` does list available flags.  But that didn't work in 1.11.  And I only got there by knowing about `go tool vet`, which is not mentioned by any of the first places to look.

CC @alandonovan ",1.0,"cmd/vet: restore documentation about vet flags - The rearrangement of the vet tool, while a great step forward, seems to have lost the documentation of vet flags.

```
> go vet -help
usage: go vet [-n] [-x] [build flags] [vet flags] [packages]
Run 'go help vet' for details.

> go help vet
usage: go vet [-n] [-x] [build flags] [vet flags] [packages]

Vet runs the Go vet command on the packages named by the import paths.

For more about vet and its flags, see 'go doc cmd/vet'.
For more about specifying packages, see 'go help packages'.

The -n flag prints commands that would be executed.
The -x flag prints commands as they are executed.

The build flags supported by go vet are those that control package resolution
and execution, such as -n, -x, -v, -tags, and -toolexec.
For more about these flags, see 'go help build'.

See also: go fmt, go fix.

> go doc cmd/vet
The vet command is a driver for static checkers conforming to the
golang.org/x/tools/go/analysis API. Run it using 'go vet'.

For a tool capable of running standalone, use a multichecker-based tool such
as golang.org/x/tools/go/analysis/cmd/vet.

> go tool vet -help
vet is a tool for static analysis of Go programs.

Usage of vet:
	vet unit.cfg	# execute analysis specified by config file
	vet help		# general help
	vet help name	# help on specific analyzer and its flags
```

`go tool vet help` does list available flags.  But that didn't work in 1.11.  And I only got there by knowing about `go tool vet`, which is not mentioned by any of the first places to look.

CC @alandonovan ",1,cmd vet  restore documentation about vet flags   the rearrangement of the vet tool  while a great step forward  seems to have lost the documentation of vet flags            go vet  help  usage  go vet            run  go help vet  for details       go help vet  usage  go vet              vet runs the go vet command on the packages named by the import paths     for more about vet and its flags  see  go doc cmd vet    for more about specifying packages  see  go help packages      the  n flag prints commands that would be executed   the  x flag prints commands as they are executed     the build flags supported by go vet are those that control package resolution  and execution  such as  n   x   v   tags  and  toolexec   for more about these flags  see  go help build      see also  go fmt  go fix       go doc cmd vet  the vet command is a driver for static checkers conforming to the  golang org x tools go analysis api  run it using  go vet      for a tool capable of running standalone  use a multichecker based tool such  as golang org x tools go analysis cmd vet       go tool vet  help  vet is a tool for static analysis of go programs     usage of vet   	vet unit cfg	  execute analysis specified by config file  	vet help		  general help  	vet help name	  help on specific analyzer and its flags          go tool vet help  does list available flags   but that didn t work in       and i only got there by knowing about  go tool vet   which is not mentioned by any of the first places to look     cc  alandonovan ,1
205912,7107221017.0,IssuesEvent,2018-01-16 19:12:36,broadinstitute/gatk,https://api.github.com/repos/broadinstitute/gatk,closed,Add a file-based configuration mechanism to GATK (with ability to override),Engine Epic PRIORITY_HIGH,Ideally using a standard mechanism like Apache `Configuration`,1.0,Add a file-based configuration mechanism to GATK (with ability to override) - Ideally using a standard mechanism like Apache `Configuration`,0,add a file based configuration mechanism to gatk  with ability to override    ideally using a standard mechanism like apache  configuration ,0
340451,10272498490.0,IssuesEvent,2019-08-23 16:36:10,SparkDevNetwork/Rock,https://api.github.com/repos/SparkDevNetwork/Rock,closed,Add support for inherited fundraising group types to Fundraising blocks,Priority: Low Status: Confirmed Topic: Rock Internals Type: Enhancement,"# Feature Request
**Describe the Feature Request**

Currently if you want to create inherited Fundraising Group Types, for example to have different groups have different attributes defined, you cannot really use them with the fundraising system as they do explicit checks for the fundraising group type id.

Requesting enhancement to allow for those inherited group types to work with the existing fundraising blocks:

* Fundraising List
* Fundraising Progress
* Fundraising Donation List
* Group Detail (currently has partial support for only 1 level deep)

**Describe Preferred Solution**

The majority of the solution would be to add a new method to `Group` entity called `IsGroupOfType` that checks the (cached) group type inheritance tree to see if the indicated group type id is in the inheritance tree of the group.

The individual blocks would then use a check of: `if ( group.IsGroupOfType( fundraisingOpportunityTypeId ) )` to see if the group is ""of fundraising group type"".

**Describe Alternatives**

No alternatives really considered. Other options would be to put explicit inheritance check code in each block, which seems silly.

**Providing Code**
I will provide code if feature request is approved: **YES**

",1.0,"Add support for inherited fundraising group types to Fundraising blocks - # Feature Request
**Describe the Feature Request**

Currently if you want to create inherited Fundraising Group Types, for example to have different groups have different attributes defined, you cannot really use them with the fundraising system as they do explicit checks for the fundraising group type id.

Requesting enhancement to allow for those inherited group types to work with the existing fundraising blocks:

* Fundraising List
* Fundraising Progress
* Fundraising Donation List
* Group Detail (currently has partial support for only 1 level deep)

**Describe Preferred Solution**

The majority of the solution would be to add a new method to `Group` entity called `IsGroupOfType` that checks the (cached) group type inheritance tree to see if the indicated group type id is in the inheritance tree of the group.

The individual blocks would then use a check of: `if ( group.IsGroupOfType( fundraisingOpportunityTypeId ) )` to see if the group is ""of fundraising group type"".

**Describe Alternatives**

No alternatives really considered. Other options would be to put explicit inheritance check code in each block, which seems silly.

**Providing Code**
I will provide code if feature request is approved: **YES**

",0,add support for inherited fundraising group types to fundraising blocks     feature request   describe the feature request    currently if you want to create inherited fundraising group types  for example to have different groups have different attributes defined  you cannot really use them with the fundraising system as they do explicit checks for the fundraising group type id   requesting enhancement to allow for those inherited group types to work with the existing fundraising blocks     fundraising list   fundraising progress   fundraising donation list   group detail  currently has partial support for only   level deep     describe preferred solution    the majority of the solution would be to add a new method to  group  entity called  isgroupoftype  that checks the  cached  group type inheritance tree to see if the indicated group type id is in the inheritance tree of the group   the individual blocks would then use a check of   if   group isgroupoftype  fundraisingopportunitytypeid      to see if the group is  of fundraising group type      describe alternatives    no alternatives really considered  other options would be to put explicit inheritance check code in each block  which seems silly     providing code   i will provide code if feature request is approved    yes    ,0
130845,12463776118.0,IssuesEvent,2020-05-28 11:14:51,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/cmd/godoc: support exporting HTML documentation,Documentation Tools WaitingForInfo,"Is there a way to generate a godoc for a module/package or export the generated documentation in a static file format? 

Currently way of generating docs:
`godoc -http=:PORT` 

Can we add an export button mechanism to the page? That can export the document for the entire project. ",1.0,"x/tools/cmd/godoc: support exporting HTML documentation - Is there a way to generate a godoc for a module/package or export the generated documentation in a static file format? 

Currently way of generating docs:
`godoc -http=:PORT` 

Can we add an export button mechanism to the page? That can export the document for the entire project. ",1,x tools cmd godoc  support exporting html documentation   is there a way to generate a godoc for a module package or export the generated documentation in a static file format      currently way of generating docs    godoc  http  port      can we add an export button mechanism to the page  that can export the document for the entire project  ,1
319205,27355909442.0,IssuesEvent,2023-02-27 12:51:54,QubesOS/updates-status,https://api.github.com/repos/QubesOS/updates-status,closed,linux-kernel-latest v6.1.11-1-latest (r4.1),r4.1-dom0-cur-test,"Update of linux-kernel-latest to v6.1.11-1-latest for Qubes r4.1, see comments below for details.

Built from: https://github.com/QubesOS/qubes-linux-kernel/commit/49782f196f121b85cea910d2314fa3faef9f68a2

[Changes since previous version](https://github.com/QubesOS/qubes-linux-kernel/compare/v6.1.7-1-latest...v6.1.11-1-latest):
QubesOS/qubes-linux-kernel@49782f1 Update to kernel-6.1.11
QubesOS/qubes-linux-kernel@9f935d6 Fix setting VM kernel after rearranging version suffix
QubesOS/qubes-linux-kernel@e9bb8f2 Rearrange version suffix
QubesOS/qubes-linux-kernel@eef8e33 Revert ""Fix suspend""

Referenced issues:


If you're release manager, you can issue GPG-inline signed command:

* `Upload linux-kernel-latest 49782f196f121b85cea910d2314fa3faef9f68a2 r4.1 current repo` (available 7 days from now)
* `Upload linux-kernel-latest 49782f196f121b85cea910d2314fa3faef9f68a2 r4.1 current (dists) repo`, you can choose subset of distributions, like `vm-fc24 vm-fc25` (available 7 days from now)
* `Upload linux-kernel-latest 49782f196f121b85cea910d2314fa3faef9f68a2 r4.1 security-testing repo`

Above commands will work only if packages in current-testing repository were built from given commit (i.e. no new version superseded it).
",1.0,"linux-kernel-latest v6.1.11-1-latest (r4.1) - Update of linux-kernel-latest to v6.1.11-1-latest for Qubes r4.1, see comments below for details.

Built from: https://github.com/QubesOS/qubes-linux-kernel/commit/49782f196f121b85cea910d2314fa3faef9f68a2

[Changes since previous version](https://github.com/QubesOS/qubes-linux-kernel/compare/v6.1.7-1-latest...v6.1.11-1-latest):
QubesOS/qubes-linux-kernel@49782f1 Update to kernel-6.1.11
QubesOS/qubes-linux-kernel@9f935d6 Fix setting VM kernel after rearranging version suffix
QubesOS/qubes-linux-kernel@e9bb8f2 Rearrange version suffix
QubesOS/qubes-linux-kernel@eef8e33 Revert ""Fix suspend""

Referenced issues:


If you're release manager, you can issue GPG-inline signed command:

* `Upload linux-kernel-latest 49782f196f121b85cea910d2314fa3faef9f68a2 r4.1 current repo` (available 7 days from now)
* `Upload linux-kernel-latest 49782f196f121b85cea910d2314fa3faef9f68a2 r4.1 current (dists) repo`, you can choose subset of distributions, like `vm-fc24 vm-fc25` (available 7 days from now)
* `Upload linux-kernel-latest 49782f196f121b85cea910d2314fa3faef9f68a2 r4.1 security-testing repo`

Above commands will work only if packages in current-testing repository were built from given commit (i.e. no new version superseded it).
",0,linux kernel latest         latest         update of linux kernel latest to         latest for qubes      see comments below for details   built from         qubesos qubes linux kernel   update to kernel       qubesos qubes linux kernel   fix setting vm kernel after rearranging version suffix qubesos qubes linux kernel   rearrange version suffix qubesos qubes linux kernel   revert  fix suspend   referenced issues    if you re release manager  you can issue gpg inline signed command      upload linux kernel latest       current repo   available   days from now     upload linux kernel latest       current  dists  repo   you can choose subset of distributions  like  vm   vm     available   days from now     upload linux kernel latest       security testing repo   above commands will work only if packages in current testing repository were built from given commit  i e  no new version superseded it   ,0
69425,13247227111.0,IssuesEvent,2020-08-19 16:54:21,microsoft/vscode-python,https://api.github.com/repos/microsoft/vscode-python,opened,Language of default cells in native notebooks,data science ds-vscode-notebook type-work item,"Based on the current VSCode notebook design, the default language of cells is always the first item in the `NoteboookDocument.languages` property.
This property contains a list of langauges the notebook supports, we'll be adding csharp, javascript, fsharp, etc (languages of all kernels found on user machine).

However majority of the users might not want this, majority of the users would be creating Python notebooks.

* 1. Should we default all notebooks to be python?
	* This would work.
	* However, if a user has a `csharp` kernel, this is annoying
* 2. Should we instead leave the current behavior
	* Default cell language to the first item in the list of languages
	* Assumption here is, if user has multiple kernels installed, then they are working on other languages (hence its wrong to place `python` first)
* 3. Go with option 2
	* Default cell language of notebook to the language of the last used notebook.
	* This way, if user opens an existing notebook and it is julia, and next time they create a blank notebook, then the default cell is always `julia`
	* Similarly, if user opens an existing notebook with `rust`, then default language for all cells in this notebook is `rust`.

I think **option 3** might be the best way forward.",1.0,"Language of default cells in native notebooks - Based on the current VSCode notebook design, the default language of cells is always the first item in the `NoteboookDocument.languages` property.
This property contains a list of langauges the notebook supports, we'll be adding csharp, javascript, fsharp, etc (languages of all kernels found on user machine).

However majority of the users might not want this, majority of the users would be creating Python notebooks.

* 1. Should we default all notebooks to be python?
	* This would work.
	* However, if a user has a `csharp` kernel, this is annoying
* 2. Should we instead leave the current behavior
	* Default cell language to the first item in the list of languages
	* Assumption here is, if user has multiple kernels installed, then they are working on other languages (hence its wrong to place `python` first)
* 3. Go with option 2
	* Default cell language of notebook to the language of the last used notebook.
	* This way, if user opens an existing notebook and it is julia, and next time they create a blank notebook, then the default cell is always `julia`
	* Similarly, if user opens an existing notebook with `rust`, then default language for all cells in this notebook is `rust`.

I think **option 3** might be the best way forward.",0,language of default cells in native notebooks   based on the current vscode notebook design  the default language of cells is always the first item in the  noteboookdocument languages  property   this property contains a list of langauges the notebook supports  we ll be adding csharp  javascript  fsharp  etc  languages of all kernels found on user machine      however majority of the users might not want this  majority of the users would be creating python notebooks          should we default all notebooks to be python   	  this would work   	  however  if a user has a  csharp  kernel  this is annoying       should we instead leave the current behavior  	  default cell language to the first item in the list of languages  	  assumption here is  if user has multiple kernels installed  then they are working on other languages  hence its wrong to place  python  first        go with option    	  default cell language of notebook to the language of the last used notebook   	  this way  if user opens an existing notebook and it is julia  and next time they create a blank notebook  then the default cell is always  julia   	  similarly  if user opens an existing notebook with  rust   then default language for all cells in this notebook is  rust      i think   option     might be the best way forward ,0
23517,4954485616.0,IssuesEvent,2016-12-01 17:42:42,golang/go,https://api.github.com/repos/golang/go,closed,net/http: document Request.Context's lifetime again,Documentation,"It was originally documented as closing when the peer closed for Go 1.7, but then we removed that part of the docs when the implementation wasn't complete.

The implementation is complete in Go 1.8, so we need to add the docs back.
",1.0,"net/http: document Request.Context's lifetime again - It was originally documented as closing when the peer closed for Go 1.7, but then we removed that part of the docs when the implementation wasn't complete.

The implementation is complete in Go 1.8, so we need to add the docs back.
",1,net http  document request context s lifetime again   it was originally documented as closing when the peer closed for go      but then we removed that part of the docs when the implementation wasn t complete     the implementation is complete in go      so we need to add the docs back   ,1
42965,2878492574.0,IssuesEvent,2015-06-10 01:30:37,besasm/EMGAATS,https://api.github.com/repos/besasm/EMGAATS,opened,Add frac2sewbeg property to building,#1 Priority data question,"Our current modeling practice requires us to calculate the peak HGL at the location where a building's  sewer lateral connects to the pipe.  Basement flooding risk is a determined based on a comparison of peak HGL and basement floor.

fract2sewbeg describes where the lateral connects to the pipe.
frac2sewbeg is fraction calculated as the lateral connection distance from the upstream manhole divided by the total pipe length.

*fract2sewbeg only applies to buildings.*

**Implications of adding this property to a building:**
A building only has one sanitary connection.  
If we wish to create a second sanitary connection we would have to split the building.",1.0,"Add frac2sewbeg property to building - Our current modeling practice requires us to calculate the peak HGL at the location where a building's  sewer lateral connects to the pipe.  Basement flooding risk is a determined based on a comparison of peak HGL and basement floor.

fract2sewbeg describes where the lateral connects to the pipe.
frac2sewbeg is fraction calculated as the lateral connection distance from the upstream manhole divided by the total pipe length.

*fract2sewbeg only applies to buildings.*

**Implications of adding this property to a building:**
A building only has one sanitary connection.  
If we wish to create a second sanitary connection we would have to split the building.",0,add   property to building   our current modeling practice requires us to calculate the peak hgl at the location where a building s  sewer lateral connects to the pipe   basement flooding risk is a determined based on a comparison of peak hgl and basement floor       describes where the lateral connects to the pipe     is fraction calculated as the lateral connection distance from the upstream manhole divided by the total pipe length        only applies to buildings        implications of adding this property to a building     a building only has one sanitary connection     if we wish to create a second sanitary connection we would have to split the building ,0
82086,10269668022.0,IssuesEvent,2019-08-23 09:35:28,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/cmd/stringer: document -linecomment in 'go doc stringer',Documentation NeedsFix help wanted,"This proposal is for that the 'stringer' tool gets flexibility at return strings, because the names that it returns are cased as they are in the values defined.

### Problem
```
type systemKind int

const (
	Windows systemKind = iota
	MacOS
	Linux
	Android
	Ios
)
```
```
$ stringer -type systemKind ./test_data/
```
The names that it generates are `WindowsMacOSLinuxAndroidIos`.
But sometimes you want show the name of other way, e.g.
""macOS"" for ""MacOS"" or ""iOS"" for ""Ios""

So, the name given to define a constant has not to be the name wanted to be showed into a string.

Also, I would want to get other funcion name to get the string given into a tag string.

### Proposal

Using a tag string like `str` to generate an alternative name, and with an optional tag name (e.g. `long`) to generate a funcion where return the string.

```
const (
	Windows systemKind = iota
	MacOS // `str:""macOS""`
	Linux     // `long:""the best system""`
	Android
	Ios // `str:""iOS""`
)
```
So the method `(i systemKind) String()` would get `WindowsmacOSLinuxAndroidiOS`.

And it would add a second method, e.g. `(systemKind) LongString()`
where it would return ""the best system"" for the value `Linux`.",1.0,"x/tools/cmd/stringer: document -linecomment in 'go doc stringer' - This proposal is for that the 'stringer' tool gets flexibility at return strings, because the names that it returns are cased as they are in the values defined.

### Problem
```
type systemKind int

const (
	Windows systemKind = iota
	MacOS
	Linux
	Android
	Ios
)
```
```
$ stringer -type systemKind ./test_data/
```
The names that it generates are `WindowsMacOSLinuxAndroidIos`.
But sometimes you want show the name of other way, e.g.
""macOS"" for ""MacOS"" or ""iOS"" for ""Ios""

So, the name given to define a constant has not to be the name wanted to be showed into a string.

Also, I would want to get other funcion name to get the string given into a tag string.

### Proposal

Using a tag string like `str` to generate an alternative name, and with an optional tag name (e.g. `long`) to generate a funcion where return the string.

```
const (
	Windows systemKind = iota
	MacOS // `str:""macOS""`
	Linux     // `long:""the best system""`
	Android
	Ios // `str:""iOS""`
)
```
So the method `(i systemKind) String()` would get `WindowsmacOSLinuxAndroidiOS`.

And it would add a second method, e.g. `(systemKind) LongString()`
where it would return ""the best system"" for the value `Linux`.",1,x tools cmd stringer  document  linecomment in  go doc stringer    this proposal is for that the  stringer  tool gets flexibility at return strings  because the names that it returns are cased as they are in the values defined         problem       type systemkind int    const    	windows systemkind   iota  	macos  	linux  	android  	ios                 stringer  type systemkind   test data        the names that it generates are  windowsmacoslinuxandroidios    but sometimes you want show the name of other way  e g    macos  for  macos  or  ios  for  ios     so  the name given to define a constant has not to be the name wanted to be showed into a string     also  i would want to get other funcion name to get the string given into a tag string         proposal    using a tag string like  str  to generate an alternative name  and with an optional tag name  e g   long   to generate a funcion where return the string          const    	windows systemkind   iota  	macos     str  macos    	linux         long  the best system    	android  	ios     str  ios            so the method   i systemkind  string    would get  windowsmacoslinuxandroidios      and it would add a second method  e g    systemkind  longstring     where it would return  the best system  for the value  linux  ,1
57036,8137873918.0,IssuesEvent,2018-08-20 13:14:43,golang/go,https://api.github.com/repos/golang/go,closed,net/http: imprecise description of the return values of HTTP serve functions,Documentation,"### What version of Go are you using (`go version`)?

go version go1.10.3 darwin/amd64

In `net.http` package, there are following fucntions/methods related to serve HTTP:

1. [http.Serve](https://golang.org/pkg/net/http/#Serve)
1. [http.ListenAndServe](https://golang.org/pkg/net/http/#ListenAndServe)
1. [http.ListenAndServeTLS](https://golang.org/pkg/net/http/#ListenAndServeTLS)
1. [http.Server.Serve](https://golang.org/pkg/net/http/#Server.Serve)
1. [http.Server.ListenAndServe](https://golang.org/pkg/net/http/#Server.ListenAndServe)
1. [http.Server.ListenAndServeTLS](https://golang.org/pkg/net/http/#Server.ListenAndServeTLS)

Except the first one, all docs for those functiosn/methods say something like `always returns a non-nil error`. But if such a function/method is terminated by a signal which is a common way to terminate a HTTP server, it will not return. For example, consider the following go code `http.go`:

```go
package main

import (
	""log""
	""net/http""
)

func main() {
	var srv http.Server
	srv.Addr = "":12345""

	if err := srv.ListenAndServe(); err != http.ErrServerClosed {
		log.Printf(""http error: %s"", err)
	}
}
```

A `SIGINT` signal will terminate the program and `http.ListenAndServe` will not return.
```
➜  local go run http.go
^Csignal: interrupt
```
Only if `srv` is teriminated by [Server.Shutdown](https://golang.org/pkg/net/http/#Server.Shutdown), ` srv.ListenAndServe` will return.

I think that the descripion `always returns a non-nil error` should mention this behaviour. Otherwise, people will tend to write [the following code](https://github.com/coreos/etcd/blob/master/contrib/raftexample/raft.go#L467):

```go
	err = (&http.Server{Handler: rc.transport.Handler()}).Serve(ln)
	select {
	case <-rc.httpstopc:
	default:
		log.Fatalf(""raftexample: Failed to serve rafthttp (%v)"", err)
	}
```
They are hoping that `Serve` will return. But it will not since `Shutdown` is not used in a way descripted in `Shutdown`'s example code.


",1.0,"net/http: imprecise description of the return values of HTTP serve functions - ### What version of Go are you using (`go version`)?

go version go1.10.3 darwin/amd64

In `net.http` package, there are following fucntions/methods related to serve HTTP:

1. [http.Serve](https://golang.org/pkg/net/http/#Serve)
1. [http.ListenAndServe](https://golang.org/pkg/net/http/#ListenAndServe)
1. [http.ListenAndServeTLS](https://golang.org/pkg/net/http/#ListenAndServeTLS)
1. [http.Server.Serve](https://golang.org/pkg/net/http/#Server.Serve)
1. [http.Server.ListenAndServe](https://golang.org/pkg/net/http/#Server.ListenAndServe)
1. [http.Server.ListenAndServeTLS](https://golang.org/pkg/net/http/#Server.ListenAndServeTLS)

Except the first one, all docs for those functiosn/methods say something like `always returns a non-nil error`. But if such a function/method is terminated by a signal which is a common way to terminate a HTTP server, it will not return. For example, consider the following go code `http.go`:

```go
package main

import (
	""log""
	""net/http""
)

func main() {
	var srv http.Server
	srv.Addr = "":12345""

	if err := srv.ListenAndServe(); err != http.ErrServerClosed {
		log.Printf(""http error: %s"", err)
	}
}
```

A `SIGINT` signal will terminate the program and `http.ListenAndServe` will not return.
```
➜  local go run http.go
^Csignal: interrupt
```
Only if `srv` is teriminated by [Server.Shutdown](https://golang.org/pkg/net/http/#Server.Shutdown), ` srv.ListenAndServe` will return.

I think that the descripion `always returns a non-nil error` should mention this behaviour. Otherwise, people will tend to write [the following code](https://github.com/coreos/etcd/blob/master/contrib/raftexample/raft.go#L467):

```go
	err = (&http.Server{Handler: rc.transport.Handler()}).Serve(ln)
	select {
	case <-rc.httpstopc:
	default:
		log.Fatalf(""raftexample: Failed to serve rafthttp (%v)"", err)
	}
```
They are hoping that `Serve` will return. But it will not since `Shutdown` is not used in a way descripted in `Shutdown`'s example code.


",1,net http  imprecise description of the return values of http serve functions       what version of go are you using   go version       go version       darwin      in  net http  package  there are following fucntions methods related to serve http                                                       except the first one  all docs for those functiosn methods say something like  always returns a non nil error   but if such a function method is terminated by a signal which is a common way to terminate a http server  it will not return  for example  consider the following go code  http go         go  package main    import    	 log   	 net http        func main      	var srv http server  	srv addr           	if err    srv listenandserve    err    http errserverclosed    		log printf  http error   s   err   	             a  sigint  signal will terminate the program and  http listenandserve  will not return        ➜  local go run http go   csignal  interrupt       only if  srv  is teriminated by       srv listenandserve  will return     i think that the descripion  always returns a non nil error  should mention this behaviour  otherwise  people will tend to write           go  	err     http server handler  rc transport handler     serve ln   	select    	case   rc httpstopc   	default   		log fatalf  raftexample  failed to serve rafthttp   v    err   	        they are hoping that  serve  will return  but it will not since  shutdown  is not used in a way descripted in  shutdown  s example code       ,1
114049,24536181319.0,IssuesEvent,2022-10-11 20:58:59,KeyWorksRW/wxUiEditor,https://api.github.com/repos/KeyWorksRW/wxUiEditor,closed,"Refactor all preferences, flags and settings",code review/refactor,"### Description:
<!-- Provide a description of of what you want to happen here -->
Preferences, flags and settings are read/set in multiple locations using multiple methods. For example, there is a `AppOptions` class which reads, but never writes. There are settings read in the `App` class, but saved in `MainFrame` -- at least those that are actually saved. Some settings are read but never saved.

The entire config settings needs to be refactored to bring everything into a single location. The `AppOptions` class would be the logical choice, but it needs to be specifically read _and_ written (currently it's only read).
",1.0,"Refactor all preferences, flags and settings - ### Description:
<!-- Provide a description of of what you want to happen here -->
Preferences, flags and settings are read/set in multiple locations using multiple methods. For example, there is a `AppOptions` class which reads, but never writes. There are settings read in the `App` class, but saved in `MainFrame` -- at least those that are actually saved. Some settings are read but never saved.

The entire config settings needs to be refactored to bring everything into a single location. The `AppOptions` class would be the logical choice, but it needs to be specifically read _and_ written (currently it's only read).
",0,refactor all preferences  flags and settings       description      preferences  flags and settings are read set in multiple locations using multiple methods  for example  there is a  appoptions  class which reads  but never writes  there are settings read in the  app  class  but saved in  mainframe     at least those that are actually saved  some settings are read but never saved     the entire config settings needs to be refactored to bring everything into a single location  the  appoptions  class would be the logical choice  but it needs to be specifically read  and  written  currently it s only read    ,0
18521,2615172759.0,IssuesEvent,2015-03-01 06:54:50,chrsmith/html5rocks,https://api.github.com/repos/chrsmith/html5rocks,closed,Change the way that using hash to mention tags into using search params.,auto-migrated Milestone-Q12012 Priority-P1 Type-Bug,"```
Related to issue 793(http://code.google.com/p/html5rocks/issues/detail?id=793).

The method we're currently using to indicate tags are putting all of them in 
hash of URL which is not good. An side effect might be issue 793, even it got 
fixed, but the behavior is really bad. You see, that if we input things like 
http://master.html5rocks.appspot.com/en/tutorials#gaming, the page will scroll 
down to the the bottom, and then, scroll to top. It doesn't look like a good 
experience.

The thing that causes the page to scroll down is there're several invisible 
<div class=""page"">s at the bottom of the page and, some of them own the id 
strings as same as some of tags, like ""gaming"", ""mobile"".

So when the browser sees the #gaming hash tag, it will scroll down to the <div 
class=""page"" id=""gaming""> part. That's so bad.

We can fix that by changing all ids that have same strings as tags, or change 
the hash to be more specific that will not conflict with any element ids. But I 
don't think either of them are good enough.

I think we could get rid of using hash to indicates tags, especially we have 
already some mess code there do deal with hashchange event(look, the line 205 
and 310 inside tutsapp.js are somehow against each other.)

Using search params may be neater, the url will be look like:
http://master.html5rocks.appspot.com/en/tutorials?audience:business,gaming&tags=
canvas,webgl
Which is shorter and easier to read than our current implementation for same 
purpose:
http://master.html5rocks.appspot.com/en/tutorials#audience:business,audience:gam
ing,canvas,webgl
```

Original issue reported on code.google.com by `han...@google.com` on 9 Feb 2012 at 3:30",1.0,"Change the way that using hash to mention tags into using search params. - ```
Related to issue 793(http://code.google.com/p/html5rocks/issues/detail?id=793).

The method we're currently using to indicate tags are putting all of them in 
hash of URL which is not good. An side effect might be issue 793, even it got 
fixed, but the behavior is really bad. You see, that if we input things like 
http://master.html5rocks.appspot.com/en/tutorials#gaming, the page will scroll 
down to the the bottom, and then, scroll to top. It doesn't look like a good 
experience.

The thing that causes the page to scroll down is there're several invisible 
<div class=""page"">s at the bottom of the page and, some of them own the id 
strings as same as some of tags, like ""gaming"", ""mobile"".

So when the browser sees the #gaming hash tag, it will scroll down to the <div 
class=""page"" id=""gaming""> part. That's so bad.

We can fix that by changing all ids that have same strings as tags, or change 
the hash to be more specific that will not conflict with any element ids. But I 
don't think either of them are good enough.

I think we could get rid of using hash to indicates tags, especially we have 
already some mess code there do deal with hashchange event(look, the line 205 
and 310 inside tutsapp.js are somehow against each other.)

Using search params may be neater, the url will be look like:
http://master.html5rocks.appspot.com/en/tutorials?audience:business,gaming&tags=
canvas,webgl
Which is shorter and easier to read than our current implementation for same 
purpose:
http://master.html5rocks.appspot.com/en/tutorials#audience:business,audience:gam
ing,canvas,webgl
```

Original issue reported on code.google.com by `han...@google.com` on 9 Feb 2012 at 3:30",0,change the way that using hash to mention tags into using search params        related to issue      the method we re currently using to indicate tags are putting all of them in  hash of url which is not good  an side effect might be issue    even it got  fixed  but the behavior is really bad  you see  that if we input things like    the page will scroll  down to the the bottom  and then  scroll to top  it doesn t look like a good  experience   the thing that causes the page to scroll down is there re several invisible   s at the bottom of the page and  some of them own the id  strings as same as some of tags  like  gaming    mobile    so when the browser sees the  gaming hash tag  it will scroll down to the  div  class  page  id  gaming   part  that s so bad   we can fix that by changing all ids that have same strings as tags  or change  the hash to be more specific that will not conflict with any element ids  but i  don t think either of them are good enough   i think we could get rid of using hash to indicates tags  especially we have  already some mess code there do deal with hashchange event look  the line    and   inside tutsapp js are somehow against each other    using search params may be neater  the url will be look like    canvas webgl which is shorter and easier to read than our current implementation for same  purpose    ing canvas webgl      original issue reported on code google com by  han    google com  on   feb   at    ,0
250667,7979670230.0,IssuesEvent,2018-07-17 22:48:58,RoboJackets/robocup-software,https://api.github.com/repos/RoboJackets/robocup-software,opened,Fix comments in miscellaneous files,area / soccer area / support exp / novice (1) priority / low status / new type / enhancement,"* Delete comment in defensive_positioning.py Line 23-24
* Delete comment in basic_122.py Line 65-67
* Delete comment in RRTPlanner.cpp Line 303, 312
* Fix shoSot to shoot in forward_pass.py Line 35",1.0,"Fix comments in miscellaneous files - * Delete comment in defensive_positioning.py Line 23-24
* Delete comment in basic_122.py Line 65-67
* Delete comment in RRTPlanner.cpp Line 303, 312
* Fix shoSot to shoot in forward_pass.py Line 35",0,fix comments in miscellaneous files     delete comment in defensive positioning py line        delete comment in basic   py line        delete comment in rrtplanner cpp line         fix shosot to shoot in forward pass py line  ,0
172882,13350754216.0,IssuesEvent,2020-08-30 09:51:39,yugabyte/yugabyte-db,https://api.github.com/repos/yugabyte/yugabyte-db,closed,[test] TSAN data race in C++ driver: in CassandraFuture destructor,area/tools kind/failing-test,"Test: `cassandra_cpp_driver-test`
TSAN log:
```
WARNING: ThreadSanitizer: data race (pid=31789)
  Write of size 8 at 0x7b2400001448 by main thread:
    #0 operator delete(void*) /home/oleg/code/yugabyte-db/thirdparty/src/llvm-7.1.0.src/projects/compiler-rt/lib/tsan/rtl/tsan_new_delete.cc:127 (discriminator 3) (cassandra_cpp_driver-test+0x4dfbe4)
    #1 ~SessionFuture /home/oleg/code/yugabyte-db/thirdparty/src/cassandra-cpp-driver-2.9.0-yb-6/src/session.hpp:252 (libcassandra.so.2+0x16e0f1)
    #2 cass_future_free /home/oleg/code/yugabyte-db/thirdparty/src/cassandra-cpp-driver-2.9.0-yb-6/src/ref_counted.hpp:50 (libcassandra.so.2+0xdee41)
    #3 cass_future_free /home/oleg/code/yugabyte-db/thirdparty/src/cassandra-cpp-driver-2.9.0-yb-6/src/future.cpp:30 (libcassandra.so.2+0xdee41)
    #4 yb::FuncDeleter<CassFuture_, &cass_future_free>::operator()(CassFuture_*) const /home/oleg/code/yugabyte-db/build/tsan-clang-dynamic-ninja/../../src/yb/integration-tests/cql_test_util.h:35 (cassandra_cpp_driver-test+0x5142be)
    #5 yb::CassandraFuture::~CassandraFuture() /home/oleg/code/yugabyte-db/build/tsan-clang-dynamic-ninja/../../thirdparty/installed/tsan/libcxx/include/c++/v1/memory:2634 (cassandra_cpp_driver-test+0x507e6c)
    #6 std::__1::unique_ptr<CassFuture_, yb::FuncDeleter<CassFuture_, &cass_future_free> >::~unique_ptr() /home/oleg/code/yugabyte-db/build/tsan-clang-dynamic-ninja/../../thirdparty/installed/tsan/libcxx/include/c++/v1/memory:2588 (cassandra_cpp_driver-test+0x507e6c)
    #7 ~CassandraFuture /home/oleg/code/yugabyte-db/build/tsan-clang-dynamic-ninja/../../src/yb/integration-tests/cql_test_util.h:150 (cassandra_cpp_driver-test+0x507e6c)
    #8 yb::CassandraSession::Connect(CassCluster_*) /home/oleg/code/yugabyte-db/build/tsan-clang-dynamic-ninja/../../src/yb/integration-tests/cql_test_util.cc:258 (libcql_test_util.so+0xae5e)
    #9 yb::CassandraSession::Create(CassCluster_*) /home/oleg/code/yugabyte-db/build/tsan-clang-dynamic-ninja/../../src/yb/integration-tests/cql_test_util.cc:264 (libcql_test_util.so+0xaf0c)
    #10 yb::CppCassandraDriver::CreateSession() /home/oleg/code/yugabyte-db/build/tsan-clang-dynamic-ninja/../../src/yb/integration-tests/cql_test_util.cc:371 (libcql_test_util.so+0xbd68)
    #11 yb::CppCassandraDriverTest::SetUp() /home/oleg/code/yugabyte-db/build/tsan-clang-dynamic-ninja/../../src/yb/integration-tests/cassandra_cpp_driver-test.cc:112 (cassandra_cpp_driver-test+0x50ecfb)
    #12 void testing::internal::HandleSehExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) /home/oleg/code/yugabyte-db/thirdparty/src/gmock-1.8.0/googletest/src/gtest.cc:2402 (libgmock.so+0x55bbf)
    #13 void testing::internal::HandleExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) /home/oleg/code/yugabyte-db/thirdparty/src/gmock-1.8.0/googletest/src/gtest.cc:2438 (libgmock.so+0x55bbf)
    #14 testing::Test::Run() /home/oleg/code/yugabyte-db/thirdparty/src/gmock-1.8.0/googletest/src/gtest.cc:2470 (libgmock.so+0x34e71)
    #15 testing::TestInfo::Run() /home/oleg/code/yugabyte-db/thirdparty/src/gmock-1.8.0/googletest/src/gtest.cc:2656 (libgmock.so+0x361fc)
    #16 testing::TestCase::Run() /home/oleg/code/yugabyte-db/thirdparty/src/gmock-1.8.0/googletest/src/gtest.cc:2774 (libgmock.so+0x36cd6)
    #17 testing::internal::UnitTestImpl::RunAllTests() /home/oleg/code/yugabyte-db/thirdparty/src/gmock-1.8.0/googletest/src/gtest.cc:4649 (libgmock.so+0x43026)
    #18 bool testing::internal::HandleSehExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool>(testing::internal::UnitTestImpl*, bool (testing::internal::UnitTestImpl::*)(), char const*) /home/oleg/code/yugabyte-db/thirdparty/src/gmock-1.8.0/googletest/src/gtest.cc:2402 (libgmock.so+0x56b2f)
    #19 bool testing::internal::HandleExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool>(testing::internal::UnitTestImpl*, bool (testing::internal::UnitTestImpl::*)(), char const*) /home/oleg/code/yugabyte-db/thirdparty/src/gmock-1.8.0/googletest/src/gtest.cc:2438 (libgmock.so+0x56b2f)
    #20 testing::UnitTest::Run() /home/oleg/code/yugabyte-db/thirdparty/src/gmock-1.8.0/googletest/src/gtest.cc:4257 (libgmock.so+0x428d1)
    #21 RUN_ALL_TESTS() /home/oleg/code/yugabyte-db/build/tsan-clang-dynamic-ninja/../../thirdparty/installed/tsan/include/gtest/gtest.h:2233 (libyb_test_main.so+0x507b)
    #22 main /home/oleg/code/yugabyte-db/build/tsan-clang-dynamic-ninja/../../src/yb/util/test_main.cc:104 (libyb_test_main.so+0x4c5d)

  Previous atomic write of size 4 at 0x7b2400001448 by thread T36 (mutexes: write M139184393822115840):
    #0 __tsan_atomic32_fetch_sub /home/oleg/code/yugabyte-db/thirdparty/src/llvm-7.1.0.src/projects/compiler-rt/lib/tsan/rtl/tsan_interface_atomic.cc:643 (discriminator 4) (cassandra_cpp_driver-test+0x4b652c)
    #1 cass::Session::notify_connected() /home/oleg/code/yugabyte-db/thirdparty/installed/tsan/libcxx/include/c++/v1/atomic:1026 (libcassandra.so.2+0x168a13)
    #2 <null> /home/oleg/code/yugabyte-db/thirdparty/src/cassandra-cpp-driver-2.9.0-yb-6/src/atomic/atomic_std.hpp:52 (libcassandra.so.2+0x168a13)
    #3 <null> /home/oleg/code/yugabyte-db/thirdparty/src/cassandra-cpp-driver-2.9.0-yb-6/src/ref_counted.hpp:46 (libcassandra.so.2+0x168a13)
    #4 <null> /home/oleg/code/yugabyte-db/thirdparty/src/cassandra-cpp-driver-2.9.0-yb-6/src/ref_counted.hpp:126 (libcassandra.so.2+0x168a13)
    #5 <null> /home/oleg/code/yugabyte-db/thirdparty/src/cassandra-cpp-driver-2.9.0-yb-6/src/ref_counted.hpp:106 (libcassandra.so.2+0x168a13)
    #6 cass::Session::notify_connected() /home/oleg/code/yugabyte-db/thirdparty/src/cassandra-cpp-driver-2.9.0-yb-6/src/session.cpp:417 (libcassandra.so.2+0x168a13)
    #7 cass::Session::on_event(cass::SessionEvent const&) /home/oleg/code/yugabyte-db/thirdparty/src/cassandra-cpp-driver-2.9.0-yb-6/src/session.cpp:520 (libcassandra.so.2+0x169459)
    #8 cass::EventThread<cass::SessionEvent>::on_event_internal(uv_async_s*) /home/oleg/code/yugabyte-db/thirdparty/src/cassandra-cpp-driver-2.9.0-yb-6/src/event_thread.hpp:57 (libcassandra.so.2+0x1733ff)
    #9 uv__async_io /home/oleg/code/yugabyte-db/thirdparty/src/libuv-1.23.0/src/unix/async.c:118 (libuv.so+0x1026b)
    #10 uv__io_poll /home/oleg/code/yugabyte-db/thirdparty/src/libuv-1.23.0/src/unix/linux-core.c:401 (libuv.so+0x284d3)
    #11 uv_run /home/oleg/code/yugabyte-db/thirdparty/src/libuv-1.23.0/src/unix/core.c:370 (libuv.so+0x10af6)
    #12 cass::LoopThread::on_run_internal(void*) /home/oleg/code/yugabyte-db/thirdparty/src/cassandra-cpp-driver-2.9.0-yb-6/src/loop_thread.hpp:128 (libcassandra.so.2+0x17037d)

  Mutex M139184393822115840 is already destroyed.
```
",1.0,"[test] TSAN data race in C++ driver: in CassandraFuture destructor - Test: `cassandra_cpp_driver-test`
TSAN log:
```
WARNING: ThreadSanitizer: data race (pid=31789)
  Write of size 8 at 0x7b2400001448 by main thread:
    #0 operator delete(void*) /home/oleg/code/yugabyte-db/thirdparty/src/llvm-7.1.0.src/projects/compiler-rt/lib/tsan/rtl/tsan_new_delete.cc:127 (discriminator 3) (cassandra_cpp_driver-test+0x4dfbe4)
    #1 ~SessionFuture /home/oleg/code/yugabyte-db/thirdparty/src/cassandra-cpp-driver-2.9.0-yb-6/src/session.hpp:252 (libcassandra.so.2+0x16e0f1)
    #2 cass_future_free /home/oleg/code/yugabyte-db/thirdparty/src/cassandra-cpp-driver-2.9.0-yb-6/src/ref_counted.hpp:50 (libcassandra.so.2+0xdee41)
    #3 cass_future_free /home/oleg/code/yugabyte-db/thirdparty/src/cassandra-cpp-driver-2.9.0-yb-6/src/future.cpp:30 (libcassandra.so.2+0xdee41)
    #4 yb::FuncDeleter<CassFuture_, &cass_future_free>::operator()(CassFuture_*) const /home/oleg/code/yugabyte-db/build/tsan-clang-dynamic-ninja/../../src/yb/integration-tests/cql_test_util.h:35 (cassandra_cpp_driver-test+0x5142be)
    #5 yb::CassandraFuture::~CassandraFuture() /home/oleg/code/yugabyte-db/build/tsan-clang-dynamic-ninja/../../thirdparty/installed/tsan/libcxx/include/c++/v1/memory:2634 (cassandra_cpp_driver-test+0x507e6c)
    #6 std::__1::unique_ptr<CassFuture_, yb::FuncDeleter<CassFuture_, &cass_future_free> >::~unique_ptr() /home/oleg/code/yugabyte-db/build/tsan-clang-dynamic-ninja/../../thirdparty/installed/tsan/libcxx/include/c++/v1/memory:2588 (cassandra_cpp_driver-test+0x507e6c)
    #7 ~CassandraFuture /home/oleg/code/yugabyte-db/build/tsan-clang-dynamic-ninja/../../src/yb/integration-tests/cql_test_util.h:150 (cassandra_cpp_driver-test+0x507e6c)
    #8 yb::CassandraSession::Connect(CassCluster_*) /home/oleg/code/yugabyte-db/build/tsan-clang-dynamic-ninja/../../src/yb/integration-tests/cql_test_util.cc:258 (libcql_test_util.so+0xae5e)
    #9 yb::CassandraSession::Create(CassCluster_*) /home/oleg/code/yugabyte-db/build/tsan-clang-dynamic-ninja/../../src/yb/integration-tests/cql_test_util.cc:264 (libcql_test_util.so+0xaf0c)
    #10 yb::CppCassandraDriver::CreateSession() /home/oleg/code/yugabyte-db/build/tsan-clang-dynamic-ninja/../../src/yb/integration-tests/cql_test_util.cc:371 (libcql_test_util.so+0xbd68)
    #11 yb::CppCassandraDriverTest::SetUp() /home/oleg/code/yugabyte-db/build/tsan-clang-dynamic-ninja/../../src/yb/integration-tests/cassandra_cpp_driver-test.cc:112 (cassandra_cpp_driver-test+0x50ecfb)
    #12 void testing::internal::HandleSehExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) /home/oleg/code/yugabyte-db/thirdparty/src/gmock-1.8.0/googletest/src/gtest.cc:2402 (libgmock.so+0x55bbf)
    #13 void testing::internal::HandleExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) /home/oleg/code/yugabyte-db/thirdparty/src/gmock-1.8.0/googletest/src/gtest.cc:2438 (libgmock.so+0x55bbf)
    #14 testing::Test::Run() /home/oleg/code/yugabyte-db/thirdparty/src/gmock-1.8.0/googletest/src/gtest.cc:2470 (libgmock.so+0x34e71)
    #15 testing::TestInfo::Run() /home/oleg/code/yugabyte-db/thirdparty/src/gmock-1.8.0/googletest/src/gtest.cc:2656 (libgmock.so+0x361fc)
    #16 testing::TestCase::Run() /home/oleg/code/yugabyte-db/thirdparty/src/gmock-1.8.0/googletest/src/gtest.cc:2774 (libgmock.so+0x36cd6)
    #17 testing::internal::UnitTestImpl::RunAllTests() /home/oleg/code/yugabyte-db/thirdparty/src/gmock-1.8.0/googletest/src/gtest.cc:4649 (libgmock.so+0x43026)
    #18 bool testing::internal::HandleSehExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool>(testing::internal::UnitTestImpl*, bool (testing::internal::UnitTestImpl::*)(), char const*) /home/oleg/code/yugabyte-db/thirdparty/src/gmock-1.8.0/googletest/src/gtest.cc:2402 (libgmock.so+0x56b2f)
    #19 bool testing::internal::HandleExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool>(testing::internal::UnitTestImpl*, bool (testing::internal::UnitTestImpl::*)(), char const*) /home/oleg/code/yugabyte-db/thirdparty/src/gmock-1.8.0/googletest/src/gtest.cc:2438 (libgmock.so+0x56b2f)
    #20 testing::UnitTest::Run() /home/oleg/code/yugabyte-db/thirdparty/src/gmock-1.8.0/googletest/src/gtest.cc:4257 (libgmock.so+0x428d1)
    #21 RUN_ALL_TESTS() /home/oleg/code/yugabyte-db/build/tsan-clang-dynamic-ninja/../../thirdparty/installed/tsan/include/gtest/gtest.h:2233 (libyb_test_main.so+0x507b)
    #22 main /home/oleg/code/yugabyte-db/build/tsan-clang-dynamic-ninja/../../src/yb/util/test_main.cc:104 (libyb_test_main.so+0x4c5d)

  Previous atomic write of size 4 at 0x7b2400001448 by thread T36 (mutexes: write M139184393822115840):
    #0 __tsan_atomic32_fetch_sub /home/oleg/code/yugabyte-db/thirdparty/src/llvm-7.1.0.src/projects/compiler-rt/lib/tsan/rtl/tsan_interface_atomic.cc:643 (discriminator 4) (cassandra_cpp_driver-test+0x4b652c)
    #1 cass::Session::notify_connected() /home/oleg/code/yugabyte-db/thirdparty/installed/tsan/libcxx/include/c++/v1/atomic:1026 (libcassandra.so.2+0x168a13)
    #2 <null> /home/oleg/code/yugabyte-db/thirdparty/src/cassandra-cpp-driver-2.9.0-yb-6/src/atomic/atomic_std.hpp:52 (libcassandra.so.2+0x168a13)
    #3 <null> /home/oleg/code/yugabyte-db/thirdparty/src/cassandra-cpp-driver-2.9.0-yb-6/src/ref_counted.hpp:46 (libcassandra.so.2+0x168a13)
    #4 <null> /home/oleg/code/yugabyte-db/thirdparty/src/cassandra-cpp-driver-2.9.0-yb-6/src/ref_counted.hpp:126 (libcassandra.so.2+0x168a13)
    #5 <null> /home/oleg/code/yugabyte-db/thirdparty/src/cassandra-cpp-driver-2.9.0-yb-6/src/ref_counted.hpp:106 (libcassandra.so.2+0x168a13)
    #6 cass::Session::notify_connected() /home/oleg/code/yugabyte-db/thirdparty/src/cassandra-cpp-driver-2.9.0-yb-6/src/session.cpp:417 (libcassandra.so.2+0x168a13)
    #7 cass::Session::on_event(cass::SessionEvent const&) /home/oleg/code/yugabyte-db/thirdparty/src/cassandra-cpp-driver-2.9.0-yb-6/src/session.cpp:520 (libcassandra.so.2+0x169459)
    #8 cass::EventThread<cass::SessionEvent>::on_event_internal(uv_async_s*) /home/oleg/code/yugabyte-db/thirdparty/src/cassandra-cpp-driver-2.9.0-yb-6/src/event_thread.hpp:57 (libcassandra.so.2+0x1733ff)
    #9 uv__async_io /home/oleg/code/yugabyte-db/thirdparty/src/libuv-1.23.0/src/unix/async.c:118 (libuv.so+0x1026b)
    #10 uv__io_poll /home/oleg/code/yugabyte-db/thirdparty/src/libuv-1.23.0/src/unix/linux-core.c:401 (libuv.so+0x284d3)
    #11 uv_run /home/oleg/code/yugabyte-db/thirdparty/src/libuv-1.23.0/src/unix/core.c:370 (libuv.so+0x10af6)
    #12 cass::LoopThread::on_run_internal(void*) /home/oleg/code/yugabyte-db/thirdparty/src/cassandra-cpp-driver-2.9.0-yb-6/src/loop_thread.hpp:128 (libcassandra.so.2+0x17037d)

  Mutex M139184393822115840 is already destroyed.
```
",0,  tsan data race in c   driver  in cassandrafuture destructor   test   cassandra cpp driver test   tsan log        warning  threadsanitizer  data race  pid       write of size   at   by main thread          operator delete void    home oleg code yugabyte db thirdparty src llvm       src projects compiler rt lib tsan rtl tsan new delete cc    discriminator     cassandra cpp driver test             sessionfuture  home oleg code yugabyte db thirdparty src cassandra cpp driver       yb   src session hpp    libcassandra so              cass future free  home oleg code yugabyte db thirdparty src cassandra cpp driver       yb   src ref counted hpp    libcassandra so              cass future free  home oleg code yugabyte db thirdparty src cassandra cpp driver       yb   src future cpp    libcassandra so              yb  funcdeleter   operator   cassfuture    const  home oleg code yugabyte db build tsan clang dynamic ninja       src yb integration tests cql test util h    cassandra cpp driver test            yb  cassandrafuture   cassandrafuture    home oleg code yugabyte db build tsan clang dynamic ninja       thirdparty installed tsan libcxx include c     memory    cassandra cpp driver test            std       unique ptr      unique ptr    home oleg code yugabyte db build tsan clang dynamic ninja       thirdparty installed tsan libcxx include c     memory    cassandra cpp driver test             cassandrafuture  home oleg code yugabyte db build tsan clang dynamic ninja       src yb integration tests cql test util h    cassandra cpp driver test            yb  cassandrasession  connect casscluster     home oleg code yugabyte db build tsan clang dynamic ninja       src yb integration tests cql test util cc    libcql test util so            yb  cassandrasession  create casscluster     home oleg code yugabyte db build tsan clang dynamic ninja       src yb integration tests cql test util cc    libcql test util so            yb  cppcassandradriver  createsession    home oleg code yugabyte db build tsan clang dynamic ninja       src yb integration tests cql test util cc    libcql test util so            yb  cppcassandradrivertest  setup    home oleg code yugabyte db build tsan clang dynamic ninja       src yb integration tests cassandra cpp driver test cc    cassandra cpp driver test            void testing  internal  handlesehexceptionsinmethodifsupported  testing  test   void  testing  test        char const    home oleg code yugabyte db thirdparty src gmock       googletest src gtest cc    libgmock so            void testing  internal  handleexceptionsinmethodifsupported  testing  test   void  testing  test        char const    home oleg code yugabyte db thirdparty src gmock       googletest src gtest cc    libgmock so            testing  test  run    home oleg code yugabyte db thirdparty src gmock       googletest src gtest cc    libgmock so            testing  testinfo  run    home oleg code yugabyte db thirdparty src gmock       googletest src gtest cc    libgmock so            testing  testcase  run    home oleg code yugabyte db thirdparty src gmock       googletest src gtest cc    libgmock so            testing  internal  unittestimpl  runalltests    home oleg code yugabyte db thirdparty src gmock       googletest src gtest cc    libgmock so            bool testing  internal  handlesehexceptionsinmethodifsupported  testing  internal  unittestimpl   bool  testing  internal  unittestimpl        char const    home oleg code yugabyte db thirdparty src gmock       googletest src gtest cc    libgmock so            bool testing  internal  handleexceptionsinmethodifsupported  testing  internal  unittestimpl   bool  testing  internal  unittestimpl        char const    home oleg code yugabyte db thirdparty src gmock       googletest src gtest cc    libgmock so            testing  unittest  run    home oleg code yugabyte db thirdparty src gmock       googletest src gtest cc    libgmock so            run all tests    home oleg code yugabyte db build tsan clang dynamic ninja       thirdparty installed tsan include gtest gtest h    libyb test main so            main  home oleg code yugabyte db build tsan clang dynamic ninja       src yb util test main cc    libyb test main so         previous atomic write of size   at   by thread    mutexes  write               tsan   fetch sub  home oleg code yugabyte db thirdparty src llvm       src projects compiler rt lib tsan rtl tsan interface atomic cc    discriminator     cassandra cpp driver test            cass  session  notify connected    home oleg code yugabyte db thirdparty installed tsan libcxx include c     atomic    libcassandra so                 home oleg code yugabyte db thirdparty src cassandra cpp driver       yb   src atomic atomic std hpp    libcassandra so                 home oleg code yugabyte db thirdparty src cassandra cpp driver       yb   src ref counted hpp    libcassandra so                 home oleg code yugabyte db thirdparty src cassandra cpp driver       yb   src ref counted hpp    libcassandra so                 home oleg code yugabyte db thirdparty src cassandra cpp driver       yb   src ref counted hpp    libcassandra so              cass  session  notify connected    home oleg code yugabyte db thirdparty src cassandra cpp driver       yb   src session cpp    libcassandra so              cass  session  on event cass  sessionevent const    home oleg code yugabyte db thirdparty src cassandra cpp driver       yb   src session cpp    libcassandra so              cass  eventthread   on event internal uv async s    home oleg code yugabyte db thirdparty src cassandra cpp driver       yb   src event thread hpp    libcassandra so              uv  async io  home oleg code yugabyte db thirdparty src libuv       src unix async c    libuv so            uv  io poll  home oleg code yugabyte db thirdparty src libuv       src unix linux core c    libuv so            uv run  home oleg code yugabyte db thirdparty src libuv       src unix core c    libuv so            cass  loopthread  on run internal void    home oleg code yugabyte db thirdparty src cassandra cpp driver       yb   src loop thread hpp    libcassandra so           mutex   is already destroyed       ,0
141621,12974005215.0,IssuesEvent,2020-07-21 14:49:53,golang/go,https://api.github.com/repos/golang/go,closed,x/text/language: possible error in the handler example of the package documentation,Documentation NeedsInvestigation,"On line [36](https://github.com/golang/text/blob/master/language/doc.go#L36) of the documentation the cookie value is passed using `lang.String()` to `language.MatchStrings` . I assume it should be `lang.Value` instead.

Current documentation:
```go
lang, _ := r.Cookie(""lang"")
...
tag, _ := language.MatchStrings(matcher, lang.String(), accept)
```
Proposed fix:
```go
lang, _ := r.Cookie(""lang"")
...
tag, _ := language.MatchStrings(matcher, lang.Value, accept)
```

If my proposed solution is right I can provide CL to fix the documentation.",1.0,"x/text/language: possible error in the handler example of the package documentation - On line [36](https://github.com/golang/text/blob/master/language/doc.go#L36) of the documentation the cookie value is passed using `lang.String()` to `language.MatchStrings` . I assume it should be `lang.Value` instead.

Current documentation:
```go
lang, _ := r.Cookie(""lang"")
...
tag, _ := language.MatchStrings(matcher, lang.String(), accept)
```
Proposed fix:
```go
lang, _ := r.Cookie(""lang"")
...
tag, _ := language.MatchStrings(matcher, lang.Value, accept)
```

If my proposed solution is right I can provide CL to fix the documentation.",1,x text language  possible error in the handler example of the package documentation   on line     of the documentation the cookie value is passed using  lang string    to  language matchstrings    i assume it should be  lang value  instead     current documentation      go  lang       r cookie  lang         tag       language matchstrings matcher  lang string    accept        proposed fix      go  lang       r cookie  lang         tag       language matchstrings matcher  lang value  accept          if my proposed solution is right i can provide cl to fix the documentation ,1
88233,10567109628.0,IssuesEvent,2019-10-06 00:34:20,golang/go,https://api.github.com/repos/golang/go,closed,unicode/utf8: document specification,Documentation NeedsFix,"The `utf8` package merely documents that it ""supports text encoded in UTF-8"", but doesn't point to any external sources for what ""UTF-8"" exactly is. I'm not an expert in this area, but my understanding is that UTF-8 is formally defined in [RFC 3629](https://tools.ietf.org/html/rfc3629). Is that true?

Furthermore, does the `Valid` function implement validation for merely the syntax of UTF-8 encoding ([section 4](https://tools.ietf.org/html/rfc3629#section-4)) or a validation of the ""definition"" of UTF-8 ([section 3](https://tools.ietf.org/html/rfc3629#section-3))? The code seems to suggest that it is the later. The godoc does not make this clear to me and probably should  be documented.",1.0,"unicode/utf8: document specification - The `utf8` package merely documents that it ""supports text encoded in UTF-8"", but doesn't point to any external sources for what ""UTF-8"" exactly is. I'm not an expert in this area, but my understanding is that UTF-8 is formally defined in [RFC 3629](https://tools.ietf.org/html/rfc3629). Is that true?

Furthermore, does the `Valid` function implement validation for merely the syntax of UTF-8 encoding ([section 4](https://tools.ietf.org/html/rfc3629#section-4)) or a validation of the ""definition"" of UTF-8 ([section 3](https://tools.ietf.org/html/rfc3629#section-3))? The code seems to suggest that it is the later. The godoc does not make this clear to me and probably should  be documented.",1,unicode    document specification   the     package merely documents that it  supports text encoded in utf     but doesn t point to any external sources for what  utf    exactly is  i m not an expert in this area  but my understanding is that utf   is formally defined in     is that true     furthermore  does the  valid  function implement validation for merely the syntax of utf   encoding      or a validation of the  definition  of utf        the code seems to suggest that it is the later  the godoc does not make this clear to me and probably should  be documented ,1
332301,29210663201.0,IssuesEvent,2023-05-22 00:14:17,QubesOS/updates-status,https://api.github.com/repos/QubesOS/updates-status,closed,gui-agent-linux v4.2.5 (r4.2),r4.2-host-cur-test r4.2-vm-bullseye-cur-test r4.2-vm-bookworm-cur-test r4.2-vm-fc37-cur-test r4.2-vm-fc36-cur-test r4.2-vm-centos-stream8-cur-test r4.2-vm-fc38-cur-test r4.2-vm-archlinux-cur-test r4.2-vm-jammy-cur-test,"Update of gui-agent-linux to v4.2.5 for Qubes OS r4.2, see comments below for details and build status.

From commit: https://github.com/QubesOS/qubes-gui-agent-linux/commit/ad04750f43e82fb2d26530c565ef7a636800355d

[Changes since previous version](https://github.com/QubesOS/qubes-gui-agent-linux/compare/v4.2.4...v4.2.5):
QubesOS/qubes-gui-agent-linux@ad04750 version 4.2.5
QubesOS/qubes-gui-agent-linux@c5e8d77 debian: move piprewire-pulse in Recommends
QubesOS/qubes-gui-agent-linux@aad0b54 debian: update maintainer
QubesOS/qubes-gui-agent-linux@af6700d debian: enable pipewire starting from bookworm
QubesOS/qubes-gui-agent-linux@bdf04d9 pipewire-qubes: add pipewire-pulse dependency
QubesOS/qubes-gui-agent-linux@8a831cb Fix setting pipewire-qubes as recommended under Ubuntu jammy
QubesOS/qubes-gui-agent-linux@b83e4b5 jammy: use pipewire
QubesOS/qubes-gui-agent-linux@155ed61 Merge remote-tracking branch 'qubesos/pr/185' into ubuntu
QubesOS/qubes-gui-agent-linux@948422a pulse: use pulseaudio version from pkg-config
QubesOS/qubes-gui-agent-linux@e404e5e .qubesbuilder: fix sed for ubuntu
QubesOS/qubes-gui-agent-linux@5e8e1d1 Add support for Ubuntu in builderv2

Referenced issues:
QubesOS/qubes-issues#8160

If you're release manager, you can issue GPG-inline signed command:

* `Upload-component r4.2 gui-agent-linux ad04750f43e82fb2d26530c565ef7a636800355d current all` (available 5 days from now)
* `Upload-component r4.2 gui-agent-linux ad04750f43e82fb2d26530c565ef7a636800355d security-testing`

You can choose subset of distributions like:
* `Upload-component r4.2 gui-agent-linux ad04750f43e82fb2d26530c565ef7a636800355d current vm-bookworm,vm-fc37` (available 5 days from now)

Above commands will work only if packages in current-testing repository were built from given commit (i.e. no new version superseded it).

For more information on how to test this update, please take a look at https://www.qubes-os.org/doc/testing/#updates.
",9.0,"gui-agent-linux v4.2.5 (r4.2) - Update of gui-agent-linux to v4.2.5 for Qubes OS r4.2, see comments below for details and build status.

From commit: https://github.com/QubesOS/qubes-gui-agent-linux/commit/ad04750f43e82fb2d26530c565ef7a636800355d

[Changes since previous version](https://github.com/QubesOS/qubes-gui-agent-linux/compare/v4.2.4...v4.2.5):
QubesOS/qubes-gui-agent-linux@ad04750 version 4.2.5
QubesOS/qubes-gui-agent-linux@c5e8d77 debian: move piprewire-pulse in Recommends
QubesOS/qubes-gui-agent-linux@aad0b54 debian: update maintainer
QubesOS/qubes-gui-agent-linux@af6700d debian: enable pipewire starting from bookworm
QubesOS/qubes-gui-agent-linux@bdf04d9 pipewire-qubes: add pipewire-pulse dependency
QubesOS/qubes-gui-agent-linux@8a831cb Fix setting pipewire-qubes as recommended under Ubuntu jammy
QubesOS/qubes-gui-agent-linux@b83e4b5 jammy: use pipewire
QubesOS/qubes-gui-agent-linux@155ed61 Merge remote-tracking branch 'qubesos/pr/185' into ubuntu
QubesOS/qubes-gui-agent-linux@948422a pulse: use pulseaudio version from pkg-config
QubesOS/qubes-gui-agent-linux@e404e5e .qubesbuilder: fix sed for ubuntu
QubesOS/qubes-gui-agent-linux@5e8e1d1 Add support for Ubuntu in builderv2

Referenced issues:
QubesOS/qubes-issues#8160

If you're release manager, you can issue GPG-inline signed command:

* `Upload-component r4.2 gui-agent-linux ad04750f43e82fb2d26530c565ef7a636800355d current all` (available 5 days from now)
* `Upload-component r4.2 gui-agent-linux ad04750f43e82fb2d26530c565ef7a636800355d security-testing`

You can choose subset of distributions like:
* `Upload-component r4.2 gui-agent-linux ad04750f43e82fb2d26530c565ef7a636800355d current vm-bookworm,vm-fc37` (available 5 days from now)

Above commands will work only if packages in current-testing repository were built from given commit (i.e. no new version superseded it).

For more information on how to test this update, please take a look at https://www.qubes-os.org/doc/testing/#updates.
",0,gui agent linux               update of gui agent linux to       for qubes os      see comments below for details and build status   from commit         qubesos qubes gui agent linux   version       qubesos qubes gui agent linux   debian  move piprewire pulse in recommends qubesos qubes gui agent linux   debian  update maintainer qubesos qubes gui agent linux   debian  enable pipewire starting from bookworm qubesos qubes gui agent linux   pipewire qubes  add pipewire pulse dependency qubesos qubes gui agent linux   fix setting pipewire qubes as recommended under ubuntu jammy qubesos qubes gui agent linux   jammy  use pipewire qubesos qubes gui agent linux   merge remote tracking branch  qubesos pr    into ubuntu qubesos qubes gui agent linux   pulse  use pulseaudio version from pkg config qubesos qubes gui agent linux    qubesbuilder  fix sed for ubuntu qubesos qubes gui agent linux   add support for ubuntu in    referenced issues  qubesos qubes issues    if you re release manager  you can issue gpg inline signed command      upload component     gui agent linux   current all   available   days from now     upload component     gui agent linux   security testing   you can choose subset of distributions like     upload component     gui agent linux   current vm bookworm vm     available   days from now   above commands will work only if packages in current testing repository were built from given commit  i e  no new version superseded it    for more information on how to test this update  please take a look at   ,0
89592,3797302155.0,IssuesEvent,2016-03-23 06:58:13,xcat2/xcat-core,https://api.github.com/repos/xcat2/xcat-core,closed,[FVT]Failed to choose correct install disk from multi-disks with WWN on X86(installing sles12.1),component:os_provision priority:high status:pending type:bug,"ENV:
MN:
```
[root@c910f04x21 rh6.7]# rpm -qa  | grep -i xCAT
xCAT-genesis-scripts-x86_64-2.12-snap201603161531.noarch
syslinux-xcat-3.86-2.noarch
xCAT-genesis-base-x86_64-2.9-snap201504212134.noarch
perl-xCAT-2.12-snap201603161530.noarch
xCAT-server-2.12-snap201603161531.noarch
xCAT-buildkit-2.12-snap201603161531.noarch
elilo-xcat-3.14-4.noarch
conserver-xcat-8.1.16-10.x86_64
grub2-xcat-2.02-0.16.el7.snap201506090204.noarch
xCAT-client-2.12-snap201603161530.noarch
xCAT-2.12-snap201603161531.x86_64
ipmitool-xcat-1.8.11-3.x86_64
[root@c910f04x21 rh6.7]# cat /etc/*release
Red Hat Enterprise Linux Server release 6.7 (Santiago)
Red Hat Enterprise Linux Server release 6.7 (Santiago)
```

CN:
```
c910f04x20:/var/log/xcat # udevadm info --query=property --name=sda| grep WWN
ID_WWN=0x500a0751036d9e61
c910f04x20:/var/log/xcat # udevadm info --query=property --name=sdb| grep WWN
ID_WWN=0x500a0751036d9c24
c910f04x20:/var/log/xcat # udevadm info --query=property --name=sdc| grep WWN
ID_WWN=0x500a0751036d9e7a
c910f04x20:/var/log/xcat # udevadm info --query=property --name=sdd| grep WWN
ID_WWN=0x500a0751036d9e83
```

Description:
Set xcatdebugmode=1, then install sles12.1 on CN. 
After installed successfully, logon CN, track /var/log/xcat/xcat.log, then the /dev/sda is chosen as the install disk, but it should be the /dev/sdb

you will see the below logs:
[xcat_log_sles12_x86_1_fresh.txt](https://github.com/xcat2/xcat-core/files/177524/xcat_log_sles12_x86_1_fresh.txt)

",1.0,"[FVT]Failed to choose correct install disk from multi-disks with WWN on X86(installing sles12.1) - ENV:
MN:
```
[root@c910f04x21 rh6.7]# rpm -qa  | grep -i xCAT
xCAT-genesis-scripts-x86_64-2.12-snap201603161531.noarch
syslinux-xcat-3.86-2.noarch
xCAT-genesis-base-x86_64-2.9-snap201504212134.noarch
perl-xCAT-2.12-snap201603161530.noarch
xCAT-server-2.12-snap201603161531.noarch
xCAT-buildkit-2.12-snap201603161531.noarch
elilo-xcat-3.14-4.noarch
conserver-xcat-8.1.16-10.x86_64
grub2-xcat-2.02-0.16.el7.snap201506090204.noarch
xCAT-client-2.12-snap201603161530.noarch
xCAT-2.12-snap201603161531.x86_64
ipmitool-xcat-1.8.11-3.x86_64
[root@c910f04x21 rh6.7]# cat /etc/*release
Red Hat Enterprise Linux Server release 6.7 (Santiago)
Red Hat Enterprise Linux Server release 6.7 (Santiago)
```

CN:
```
c910f04x20:/var/log/xcat # udevadm info --query=property --name=sda| grep WWN
ID_WWN=0x500a0751036d9e61
c910f04x20:/var/log/xcat # udevadm info --query=property --name=sdb| grep WWN
ID_WWN=0x500a0751036d9c24
c910f04x20:/var/log/xcat # udevadm info --query=property --name=sdc| grep WWN
ID_WWN=0x500a0751036d9e7a
c910f04x20:/var/log/xcat # udevadm info --query=property --name=sdd| grep WWN
ID_WWN=0x500a0751036d9e83
```

Description:
Set xcatdebugmode=1, then install sles12.1 on CN. 
After installed successfully, logon CN, track /var/log/xcat/xcat.log, then the /dev/sda is chosen as the install disk, but it should be the /dev/sdb

you will see the below logs:
[xcat_log_sles12_x86_1_fresh.txt](https://github.com/xcat2/xcat-core/files/177524/xcat_log_sles12_x86_1_fresh.txt)

",0, failed to choose correct install disk from multi disks with wwn on   installing        env   mn           rpm  qa    grep  i xcat  xcat genesis scripts           noarch  syslinux xcat       noarch  xcat genesis base           noarch  perl xcat       noarch  xcat server       noarch  xcat buildkit       noarch  elilo xcat       noarch  conserver xcat                xcat             noarch  xcat client       noarch  xcat            ipmitool xcat                 cat  etc  release  red hat enterprise linux server release      santiago   red hat enterprise linux server release      santiago          cn           var log xcat   udevadm info   query property   name sda  grep wwn  id wwn       var log xcat   udevadm info   query property   name sdb  grep wwn  id wwn       var log xcat   udevadm info   query property   name sdc  grep wwn  id wwn       var log xcat   udevadm info   query property   name sdd  grep wwn  id wwn           description   set xcatdebugmode    then install     on cn    after installed successfully  logon cn  track  var log xcat xcat log  then the  dev sda is chosen as the install disk  but it should be the  dev sdb    you will see the below logs          ,0
216505,7308929622.0,IssuesEvent,2018-02-28 10:02:41,SpamExperts/zimbra-addon,https://api.github.com/repos/SpamExperts/zimbra-addon,closed,Error when installing Zimlet,bug priority-normal,"### Version information
N/A

### Steps to replicate

1. Client downloaded zimlet to a Mac
2. Unzipped the file, customized it as described in the KB
3. Added to a zip file and renamed
4. Uploaded the zimlet to one of the mailstore servers
5. Moved it to /opt/zimbra/zimlets/ and ran the deploy command

### Actual result
```
zimbra@mail05 ~]$ /opt/zimbra/bin/zmzimletctl deploy /opt/zimbra/zimlets/com_zimbra_spamexperts.zip

[] INFO: Deploying Zimlet com_zimbra_spamexperts in LDAP.

[] INFO: Installing Zimlet com_zimbra_spamexperts on this host.

[] INFO: Upgrading Zimlet com_zimbra_spamexperts to 1.2

[] INFO: Installing Zimlet config for com_zimbra_spamexperts

[] INFO: Adding Zimlet com_zimbra_spamexperts to COS default

[] INFO: Enabling Zimlet com_zimbra_spamexperts

[] INFO: Deploying on service node mail04.mxof.net

[] INFO: post to server mail04.mxof.net, data size 10718

[] INFO: deploy failed on service node mail04.mxof.net

com.zimbra.common.soap.SoapFaultException: system failure: error deploying Zimlet

ExceptionId:qtp1286783232-37177:1516669373836:ff7335bcdb78a077

Code:service.FAILURE

at com.zimbra.common.soap.Soap12Protocol.soapFault(Soap12Protocol.java:90)

at com.zimbra.common.soap.SoapTransport.extractBodyElement(SoapTransport.java:366)

at com.zimbra.common.soap.SoapTransport.parseSoapResponse(SoapTransport.java:339)

at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:267)

at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:173)

at com.zimbra.common.soap.SoapTransport.invoke(SoapTransport.java:419)

at com.zimbra.common.soap.SoapTransport.invoke(SoapTransport.java:382)

at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.soapDeployZimlet(ZimletUtil.java:1624)

at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.deployZimletOnServiceNode(ZimletUtil.java:1561)

at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.deployZimletRemotely(ZimletUtil.java:1498)

at com.zimbra.cs.zimlet.ZimletUtil.deployZimletRemotely(ZimletUtil.java:1253)

at com.zimbra.cs.zimlet.ZimletUtil.dispatch(ZimletUtil.java:1911)

at com.zimbra.cs.zimlet.ZimletUtil.main(ZimletUtil.java:2007)

com.zimbra.common.soap.SoapFaultException: system failure: error deploying Zimlet

ExceptionId:qtp1286783232-37177:1516669373836:ff7335bcdb78a077

Code:service.FAILURE

at com.zimbra.common.soap.Soap12Protocol.soapFault(Soap12Protocol.java:90)

at com.zimbra.common.soap.SoapTransport.extractBodyElement(SoapTransport.java:366)

at com.zimbra.common.soap.SoapTransport.parseSoapResponse(SoapTransport.java:339)

at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:267)

at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:173)

at com.zimbra.common.soap.SoapTransport.invoke(SoapTransport.java:419)

at com.zimbra.common.soap.SoapTransport.invoke(SoapTransport.java:382)

at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.soapDeployZimlet(ZimletUtil.java:1624)

at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.deployZimletOnServiceNode(ZimletUtil.java:1561)

at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.deployZimletRemotely(ZimletUtil.java:1498)

at com.zimbra.cs.zimlet.ZimletUtil.deployZimletRemotely(ZimletUtil.java:1253)

at com.zimbra.cs.zimlet.ZimletUtil.dispatch(ZimletUtil.java:1911)

at com.zimbra.cs.zimlet.ZimletUtil.main(ZimletUtil.java:2007)

[] ERROR: Error

com.zimbra.common.soap.SoapFaultException: system failure: error deploying Zimlet

ExceptionId:qtp1286783232-37177:1516669373836:ff7335bcdb78a077

Code:service.FAILURE

at com.zimbra.common.soap.Soap12Protocol.soapFault(Soap12Protocol.java:90)

at com.zimbra.common.soap.SoapTransport.extractBodyElement(SoapTransport.java:366)

at com.zimbra.common.soap.SoapTransport.parseSoapResponse(SoapTransport.java:339)

at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:267)

at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:173)

at com.zimbra.common.soap.SoapTransport.invoke(SoapTransport.java:419)

at com.zimbra.common.soap.SoapTransport.invoke(SoapTransport.java:382)

at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.soapDeployZimlet(ZimletUtil.java:1624)

at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.deployZimletOnServiceNode(ZimletUtil.java:1561)

at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.deployZimletRemotely(ZimletUtil.java:1498)

at com.zimbra.cs.zimlet.ZimletUtil.deployZimletRemotely(ZimletUtil.java:1253)

at com.zimbra.cs.zimlet.ZimletUtil.dispatch(ZimletUtil.java:1911)

at com.zimbra.cs.zimlet.ZimletUtil.main(ZimletUtil.java:2007)

[zimbra@mail05 ~]$
```


### Expected result
The addon should be installed.

### Other notes
Whmcs ticket [690062](https://my.spamexperts.com/admin/supporttickets.php?action=view&id=193994)",1.0,"Error when installing Zimlet - ### Version information
N/A

### Steps to replicate

1. Client downloaded zimlet to a Mac
2. Unzipped the file, customized it as described in the KB
3. Added to a zip file and renamed
4. Uploaded the zimlet to one of the mailstore servers
5. Moved it to /opt/zimbra/zimlets/ and ran the deploy command

### Actual result
```
zimbra@mail05 ~]$ /opt/zimbra/bin/zmzimletctl deploy /opt/zimbra/zimlets/com_zimbra_spamexperts.zip

[] INFO: Deploying Zimlet com_zimbra_spamexperts in LDAP.

[] INFO: Installing Zimlet com_zimbra_spamexperts on this host.

[] INFO: Upgrading Zimlet com_zimbra_spamexperts to 1.2

[] INFO: Installing Zimlet config for com_zimbra_spamexperts

[] INFO: Adding Zimlet com_zimbra_spamexperts to COS default

[] INFO: Enabling Zimlet com_zimbra_spamexperts

[] INFO: Deploying on service node mail04.mxof.net

[] INFO: post to server mail04.mxof.net, data size 10718

[] INFO: deploy failed on service node mail04.mxof.net

com.zimbra.common.soap.SoapFaultException: system failure: error deploying Zimlet

ExceptionId:qtp1286783232-37177:1516669373836:ff7335bcdb78a077

Code:service.FAILURE

at com.zimbra.common.soap.Soap12Protocol.soapFault(Soap12Protocol.java:90)

at com.zimbra.common.soap.SoapTransport.extractBodyElement(SoapTransport.java:366)

at com.zimbra.common.soap.SoapTransport.parseSoapResponse(SoapTransport.java:339)

at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:267)

at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:173)

at com.zimbra.common.soap.SoapTransport.invoke(SoapTransport.java:419)

at com.zimbra.common.soap.SoapTransport.invoke(SoapTransport.java:382)

at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.soapDeployZimlet(ZimletUtil.java:1624)

at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.deployZimletOnServiceNode(ZimletUtil.java:1561)

at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.deployZimletRemotely(ZimletUtil.java:1498)

at com.zimbra.cs.zimlet.ZimletUtil.deployZimletRemotely(ZimletUtil.java:1253)

at com.zimbra.cs.zimlet.ZimletUtil.dispatch(ZimletUtil.java:1911)

at com.zimbra.cs.zimlet.ZimletUtil.main(ZimletUtil.java:2007)

com.zimbra.common.soap.SoapFaultException: system failure: error deploying Zimlet

ExceptionId:qtp1286783232-37177:1516669373836:ff7335bcdb78a077

Code:service.FAILURE

at com.zimbra.common.soap.Soap12Protocol.soapFault(Soap12Protocol.java:90)

at com.zimbra.common.soap.SoapTransport.extractBodyElement(SoapTransport.java:366)

at com.zimbra.common.soap.SoapTransport.parseSoapResponse(SoapTransport.java:339)

at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:267)

at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:173)

at com.zimbra.common.soap.SoapTransport.invoke(SoapTransport.java:419)

at com.zimbra.common.soap.SoapTransport.invoke(SoapTransport.java:382)

at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.soapDeployZimlet(ZimletUtil.java:1624)

at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.deployZimletOnServiceNode(ZimletUtil.java:1561)

at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.deployZimletRemotely(ZimletUtil.java:1498)

at com.zimbra.cs.zimlet.ZimletUtil.deployZimletRemotely(ZimletUtil.java:1253)

at com.zimbra.cs.zimlet.ZimletUtil.dispatch(ZimletUtil.java:1911)

at com.zimbra.cs.zimlet.ZimletUtil.main(ZimletUtil.java:2007)

[] ERROR: Error

com.zimbra.common.soap.SoapFaultException: system failure: error deploying Zimlet

ExceptionId:qtp1286783232-37177:1516669373836:ff7335bcdb78a077

Code:service.FAILURE

at com.zimbra.common.soap.Soap12Protocol.soapFault(Soap12Protocol.java:90)

at com.zimbra.common.soap.SoapTransport.extractBodyElement(SoapTransport.java:366)

at com.zimbra.common.soap.SoapTransport.parseSoapResponse(SoapTransport.java:339)

at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:267)

at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:173)

at com.zimbra.common.soap.SoapTransport.invoke(SoapTransport.java:419)

at com.zimbra.common.soap.SoapTransport.invoke(SoapTransport.java:382)

at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.soapDeployZimlet(ZimletUtil.java:1624)

at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.deployZimletOnServiceNode(ZimletUtil.java:1561)

at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.deployZimletRemotely(ZimletUtil.java:1498)

at com.zimbra.cs.zimlet.ZimletUtil.deployZimletRemotely(ZimletUtil.java:1253)

at com.zimbra.cs.zimlet.ZimletUtil.dispatch(ZimletUtil.java:1911)

at com.zimbra.cs.zimlet.ZimletUtil.main(ZimletUtil.java:2007)

[zimbra@mail05 ~]$
```


### Expected result
The addon should be installed.

### Other notes
Whmcs ticket [690062](https://my.spamexperts.com/admin/supporttickets.php?action=view&id=193994)",0,error when installing zimlet       version information  n a        steps to replicate       client downloaded zimlet to a mac     unzipped the file  customized it as described in the kb     added to a zip file and renamed     uploaded the zimlet to one of the mailstore servers     moved it to  opt zimbra zimlets  and ran the deploy command        actual result       zimbra        opt zimbra bin zmzimletctl deploy  opt zimbra zimlets com zimbra spamexperts zip      info  deploying zimlet com zimbra spamexperts in ldap       info  installing zimlet com zimbra spamexperts on this host       info  upgrading zimlet com zimbra spamexperts to          info  installing zimlet config for com zimbra spamexperts      info  adding zimlet com zimbra spamexperts to cos default      info  enabling zimlet com zimbra spamexperts      info  deploying on service node   mxof net      info  post to server   mxof net  data size        info  deploy failed on service node   mxof net    com zimbra common soap soapfaultexception  system failure  error deploying zimlet    exceptionid            code service failure    at com zimbra common soap   soapfault   java       at com zimbra common soap soaptransport extractbodyelement soaptransport java       at com zimbra common soap soaptransport parsesoapresponse soaptransport java       at com zimbra common soap soaphttptransport invoke soaphttptransport java       at com zimbra common soap soaphttptransport invoke soaphttptransport java       at com zimbra common soap soaptransport invoke soaptransport java       at com zimbra common soap soaptransport invoke soaptransport java       at com zimbra cs zimlet zimletutil zimletsoaputil soapdeployzimlet zimletutil java       at com zimbra cs zimlet zimletutil zimletsoaputil deployzimletonservicenode zimletutil java       at com zimbra cs zimlet zimletutil zimletsoaputil deployzimletremotely zimletutil java       at com zimbra cs zimlet zimletutil deployzimletremotely zimletutil java       at com zimbra cs zimlet zimletutil dispatch zimletutil java       at com zimbra cs zimlet zimletutil main zimletutil java       com zimbra common soap soapfaultexception  system failure  error deploying zimlet    exceptionid            code service failure    at com zimbra common soap   soapfault   java       at com zimbra common soap soaptransport extractbodyelement soaptransport java       at com zimbra common soap soaptransport parsesoapresponse soaptransport java       at com zimbra common soap soaphttptransport invoke soaphttptransport java       at com zimbra common soap soaphttptransport invoke soaphttptransport java       at com zimbra common soap soaptransport invoke soaptransport java       at com zimbra common soap soaptransport invoke soaptransport java       at com zimbra cs zimlet zimletutil zimletsoaputil soapdeployzimlet zimletutil java       at com zimbra cs zimlet zimletutil zimletsoaputil deployzimletonservicenode zimletutil java       at com zimbra cs zimlet zimletutil zimletsoaputil deployzimletremotely zimletutil java       at com zimbra cs zimlet zimletutil deployzimletremotely zimletutil java       at com zimbra cs zimlet zimletutil dispatch zimletutil java       at com zimbra cs zimlet zimletutil main zimletutil java         error  error    com zimbra common soap soapfaultexception  system failure  error deploying zimlet    exceptionid            code service failure    at com zimbra common soap   soapfault   java       at com zimbra common soap soaptransport extractbodyelement soaptransport java       at com zimbra common soap soaptransport parsesoapresponse soaptransport java       at com zimbra common soap soaphttptransport invoke soaphttptransport java       at com zimbra common soap soaphttptransport invoke soaphttptransport java       at com zimbra common soap soaptransport invoke soaptransport java       at com zimbra common soap soaptransport invoke soaptransport java       at com zimbra cs zimlet zimletutil zimletsoaputil soapdeployzimlet zimletutil java       at com zimbra cs zimlet zimletutil zimletsoaputil deployzimletonservicenode zimletutil java       at com zimbra cs zimlet zimletutil zimletsoaputil deployzimletremotely zimletutil java       at com zimbra cs zimlet zimletutil deployzimletremotely zimletutil java       at com zimbra cs zimlet zimletutil dispatch zimletutil java       at com zimbra cs zimlet zimletutil main zimletutil java                        expected result  the addon should be installed         other notes  whmcs ticket    ,0
408008,11940611378.0,IssuesEvent,2020-04-02 17:00:16,zephyrproject-rtos/zephyr,https://api.github.com/repos/zephyrproject-rtos/zephyr,closed,[Coverity CID :209375] Side effect in assertion in tests/kernel/interrupt/src/prevent_irq.c,Coverity bug priority: low,"
Static code scan issues found in file:

https://github.com/zephyrproject-rtos/zephyr/tree/29c0c08fd4abc34aae4e1bf579cc506eaabef428/tests/kernel/interrupt/src/prevent_irq.c#L50

Category: Incorrect expression
Function: `test_prevent_interruption`
Component: Tests
CID: [209375](https://scan9.coverity.com/reports.htm#v29726/p12996/mergedDefectId=209375)


Details:

```
44         /* Start the timer and busy-wait for a bit with IRQs locked. The
45          * timer ought to have fired during this time if interrupts weren't
46          * locked -- but since they are, check_lock_new isn't updated.
47          */
48         k_timer_start(&irqlock_timer, K_MSEC(DURATION), K_NO_WAIT);
49         k_busy_wait(MS_TO_US(1000));
>>>     CID 209375:  Incorrect expression  (ASSERT_SIDE_EFFECT)
>>>     Argument ""handler_result"" of z_zassert() has a side effect because the variable is volatile.  The containing function might work differently in a non-debug build.
50         zassert_not_equal(handler_result, HANDLER_TOKEN,
51             ""timer interrupt was serviced while interrupts are locked"");
52    
53         printk(""unlocking interrupts\n"");
54         irq_unlock(key);
55    
```

Please fix or provide comments in coverity using the link:

https://scan9.coverity.com/reports.htm#v32951/p12996.

Note: This issue was created automatically. Priority was set based on classification
of the file affected and the impact field in coverity. Assignees were set using the CODEOWNERS file.
",1.0,"[Coverity CID :209375] Side effect in assertion in tests/kernel/interrupt/src/prevent_irq.c - 
Static code scan issues found in file:

https://github.com/zephyrproject-rtos/zephyr/tree/29c0c08fd4abc34aae4e1bf579cc506eaabef428/tests/kernel/interrupt/src/prevent_irq.c#L50

Category: Incorrect expression
Function: `test_prevent_interruption`
Component: Tests
CID: [209375](https://scan9.coverity.com/reports.htm#v29726/p12996/mergedDefectId=209375)


Details:

```
44         /* Start the timer and busy-wait for a bit with IRQs locked. The
45          * timer ought to have fired during this time if interrupts weren't
46          * locked -- but since they are, check_lock_new isn't updated.
47          */
48         k_timer_start(&irqlock_timer, K_MSEC(DURATION), K_NO_WAIT);
49         k_busy_wait(MS_TO_US(1000));
>>>     CID 209375:  Incorrect expression  (ASSERT_SIDE_EFFECT)
>>>     Argument ""handler_result"" of z_zassert() has a side effect because the variable is volatile.  The containing function might work differently in a non-debug build.
50         zassert_not_equal(handler_result, HANDLER_TOKEN,
51             ""timer interrupt was serviced while interrupts are locked"");
52    
53         printk(""unlocking interrupts\n"");
54         irq_unlock(key);
55    
```

Please fix or provide comments in coverity using the link:

https://scan9.coverity.com/reports.htm#v32951/p12996.

Note: This issue was created automatically. Priority was set based on classification
of the file affected and the impact field in coverity. Assignees were set using the CODEOWNERS file.
",0,  side effect in assertion in tests kernel interrupt src prevent irq c    static code scan issues found in file      category  incorrect expression function   test prevent interruption  component  tests cid        details                    start the timer and busy wait for a bit with irqs locked  the              timer ought to have fired during this time if interrupts weren t              locked    but since they are  check lock new isn t updated                          k timer start  irqlock timer  k msec duration   k no wait             k busy wait ms to us              cid     incorrect expression   assert side effect          argument  handler result  of z zassert   has a side effect because the variable is volatile   the containing function might work differently in a non debug build            zassert not equal handler result  handler token                 timer interrupt was serviced while interrupts are locked                    printk  unlocking interrupts n              irq unlock key              please fix or provide comments in coverity using the link      note  this issue was created automatically  priority was set based on classification of the file affected and the impact field in coverity  assignees were set using the codeowners file  ,0
32764,26973948935.0,IssuesEvent,2023-02-09 08:05:45,Azure/autorest.python,https://api.github.com/repos/Azure/autorest.python,closed,[cadl] see if we can generate with a url type,Epic: Parity with DPG 1.0 Epic: Create test infrastructure,Want to see if we can have a client with an endpoint of cadl type url. Preferably add a test in cadl ranch,1.0,[cadl] see if we can generate with a url type - Want to see if we can have a client with an endpoint of cadl type url. Preferably add a test in cadl ranch,0,  see if we can generate with a url type   want to see if we can have a client with an endpoint of cadl type url  preferably add a test in cadl ranch,0
197345,14919477928.0,IssuesEvent,2021-01-23 00:16:19,zephyrproject-rtos/zephyr,https://api.github.com/repos/zephyrproject-rtos/zephyr,closed,tests: kernel: kernel.threads.armv8m_mpu_stack_guard fails on nrf9160dk,area: Tests bug platform: nRF priority: medium,"**Describe the bug**
The test from tests/kernel/threads/thread_stack/ fail on nrf9160dk
git bisect: c770cab1a3a6cbfefbe8432939f78b321770d498 is the first bad commit

**To Reproduce**
Steps to reproduce the behavior:
1. have nrf 9160dk connected
2. go to zephyr dir
3. run `./scripts/sanitycheck --device-testing -T tests/kernel/threads/thread_stack/ -p nrf9160dk_nrf9160 --device-serial /dev/ttyACM0 -v -v`
4. See error

**Expected behavior**
Test passes 

**Impact**
Not clear

**Logs and console output**
```
DEBUG   - DEVICE: testing stest_member_stack
DEBUG   - DEVICE: Stack object 0x200000a0[544]
DEBUG   - DEVICE: - Testing supervisor mode
DEBUG   - DEVICE: - Thread reports buffer 0x200000c0 size 512
DEBUG   - DEVICE: - check read/write to stack buffer
DEBUG   - DEVICE: - Carved-out space in buffer: 0
DEBUG   - DEVICE: - Unused objects space: 0
DEBUG   - DEVICE: self-reported unused stack space: 124
DEBUG   - DEVICE: target thread unused stack space: 124
DEBUG   - DEVICE: PASS - test_stack_buffer
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_idle_stack
DEBUG   - DEVICE: hi! bye!
DEBUG   - DEVICE: E: could not allocate kernel object, out of memory
DEBUG   - DEVICE: E: ***** MPU FAULT *****
DEBUG   - DEVICE: E:   Data Access Violation
DEBUG   - DEVICE: E:   MMFAR Address: 0x8
DEBUG   - DEVICE: E: r0/a1:  0x00000000  r1/a2:  0x00000001  r2/a3:  0x00000001
DEBUG   - DEVICE: E: r3/a4:  0x00000000 r12/ip:  0xaaaaaaaa r14/lr:  0x0000074f
DEBUG   - DEVICE: E:  xpsr:  0x61000000
DEBUG   - DEVICE: E: Faulting instruction address (r15/pc): 0x0000cf62
DEBUG   - DEVICE: E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
DEBUG   - DEVICE: E: Current thread: 0x200002e0 (unknown)
DEBUG   - DEVICE: E: Halting system
DEBUG   - Waiting for device nrf9160dk_nrf9160 to become available
DEBUG   - Waiting for device nrf9160dk_nrf9160 to become available
```

**Environment (please complete the following information):**
 - Ubuntu 18.04
 - Toolchain  Zephyr SDK",1.0,"tests: kernel: kernel.threads.armv8m_mpu_stack_guard fails on nrf9160dk - **Describe the bug**
The test from tests/kernel/threads/thread_stack/ fail on nrf9160dk
git bisect: c770cab1a3a6cbfefbe8432939f78b321770d498 is the first bad commit

**To Reproduce**
Steps to reproduce the behavior:
1. have nrf 9160dk connected
2. go to zephyr dir
3. run `./scripts/sanitycheck --device-testing -T tests/kernel/threads/thread_stack/ -p nrf9160dk_nrf9160 --device-serial /dev/ttyACM0 -v -v`
4. See error

**Expected behavior**
Test passes 

**Impact**
Not clear

**Logs and console output**
```
DEBUG   - DEVICE: testing stest_member_stack
DEBUG   - DEVICE: Stack object 0x200000a0[544]
DEBUG   - DEVICE: - Testing supervisor mode
DEBUG   - DEVICE: - Thread reports buffer 0x200000c0 size 512
DEBUG   - DEVICE: - check read/write to stack buffer
DEBUG   - DEVICE: - Carved-out space in buffer: 0
DEBUG   - DEVICE: - Unused objects space: 0
DEBUG   - DEVICE: self-reported unused stack space: 124
DEBUG   - DEVICE: target thread unused stack space: 124
DEBUG   - DEVICE: PASS - test_stack_buffer
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_idle_stack
DEBUG   - DEVICE: hi! bye!
DEBUG   - DEVICE: E: could not allocate kernel object, out of memory
DEBUG   - DEVICE: E: ***** MPU FAULT *****
DEBUG   - DEVICE: E:   Data Access Violation
DEBUG   - DEVICE: E:   MMFAR Address: 0x8
DEBUG   - DEVICE: E: r0/a1:  0x00000000  r1/a2:  0x00000001  r2/a3:  0x00000001
DEBUG   - DEVICE: E: r3/a4:  0x00000000 r12/ip:  0xaaaaaaaa r14/lr:  0x0000074f
DEBUG   - DEVICE: E:  xpsr:  0x61000000
DEBUG   - DEVICE: E: Faulting instruction address (r15/pc): 0x0000cf62
DEBUG   - DEVICE: E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
DEBUG   - DEVICE: E: Current thread: 0x200002e0 (unknown)
DEBUG   - DEVICE: E: Halting system
DEBUG   - Waiting for device nrf9160dk_nrf9160 to become available
DEBUG   - Waiting for device nrf9160dk_nrf9160 to become available
```

**Environment (please complete the following information):**
 - Ubuntu 18.04
 - Toolchain  Zephyr SDK",0,tests  kernel  kernel threads   mpu stack guard fails on       describe the bug    the test from tests kernel threads thread stack  fail on    git bisect    is the first bad commit      to reproduce    steps to reproduce the behavior      have nrf   connected     go to zephyr dir     run    scripts sanitycheck   device testing  t tests kernel threads thread stack   p       device serial  dev    v  v      see error      expected behavior    test passes       impact    not clear      logs and console output         debug     device  testing stest member stack  debug     device  stack object     debug     device    testing supervisor mode  debug     device    thread reports buffer   size    debug     device    check read write to stack buffer  debug     device    carved out space in buffer     debug     device    unused objects space     debug     device  self reported unused stack space     debug     device  target thread unused stack space     debug     device  pass   test stack buffer  debug     device                                                                       debug     device  start   test idle stack  debug     device  hi  bye   debug     device  e  could not allocate kernel object  out of memory  debug     device  e        mpu fault        debug     device  e    data access violation  debug     device  e    mmfar address     debug     device  e                             debug     device  e            ip       lr      debug     device  e   xpsr      debug     device  e  faulting instruction address    pc      debug     device  e      zephyr fatal error    cpu exception on cpu    debug     device  e  current thread     unknown   debug     device  e  halting system  debug     waiting for device     to become available  debug     waiting for device     to become available           environment  please complete the following information         ubuntu         toolchain  zephyr sdk,0
186911,15087644456.0,IssuesEvent,2021-02-05 22:35:56,golang/go,https://api.github.com/repos/golang/go,closed,embed: document that paths must satisfy fs.ValidPath(name),Documentation NeedsInvestigation release-blocker,"The embed documentation does not says that paths must also satisfy `fs.ValidPath(name)`. It only says

> The path separator is a forward slash, even on Windows systems.

and 

> Patterns must not contain ‘.’ or ‘..’ path elements nor begin with a leading slash. 

For example in this case:

`//go:embed data/`

the compiler fails with the error:

`pattern data/: invalid pattern syntax`

but ""data/"" is valid as pattern, it is not valid for the `fs.ValidPath` function.

I think that the sentence

> A //go:embed directive above a variable declaration specifies which files to embed, using one or more path.Match patterns.

should mention `fs.ValidPath` and consequently ""The path separator is a forward slash, even on Windows systems"" and ""Patterns must not contain ‘.’ or ‘..’ path elements nor begin with a leading slash"" can be removed.
",1.0,"embed: document that paths must satisfy fs.ValidPath(name) - The embed documentation does not says that paths must also satisfy `fs.ValidPath(name)`. It only says

> The path separator is a forward slash, even on Windows systems.

and 

> Patterns must not contain ‘.’ or ‘..’ path elements nor begin with a leading slash. 

For example in this case:

`//go:embed data/`

the compiler fails with the error:

`pattern data/: invalid pattern syntax`

but ""data/"" is valid as pattern, it is not valid for the `fs.ValidPath` function.

I think that the sentence

> A //go:embed directive above a variable declaration specifies which files to embed, using one or more path.Match patterns.

should mention `fs.ValidPath` and consequently ""The path separator is a forward slash, even on Windows systems"" and ""Patterns must not contain ‘.’ or ‘..’ path elements nor begin with a leading slash"" can be removed.
",1,embed  document that paths must satisfy fs validpath name    the embed documentation does not says that paths must also satisfy  fs validpath name    it only says      the path separator is a forward slash  even on windows systems     and       patterns must not contain ‘ ’ or ‘  ’ path elements nor begin with a leading slash      for example in this case        go embed data      the compiler fails with the error      pattern data   invalid pattern syntax     but  data   is valid as pattern  it is not valid for the  fs validpath  function     i think that the sentence      a   go embed directive above a variable declaration specifies which files to embed  using one or more path match patterns     should mention  fs validpath  and consequently  the path separator is a forward slash  even on windows systems  and  patterns must not contain ‘ ’ or ‘  ’ path elements nor begin with a leading slash  can be removed   ,1
28559,5515129008.0,IssuesEvent,2017-03-17 16:40:47,golang/go,https://api.github.com/repos/golang/go,opened,"doc: figure out, document amd64 minimum requirements",Documentation NeedsDecision,"In https://golang.org/cl/38320, @khr adds POPCOUNT intrinsics for amd64.

I realize that our https://golang.org/wiki/MinimumRequirements doesn't say anything about GOARCH=amd64. (only 386)

Which version of amd64 do we assume? Decide and document.

/cc @randall77 @ianlancetaylor @rsc @mdempsky @josharian @minux @cherrymui @aclements ",1.0,"doc: figure out, document amd64 minimum requirements - In https://golang.org/cl/38320, @khr adds POPCOUNT intrinsics for amd64.

I realize that our https://golang.org/wiki/MinimumRequirements doesn't say anything about GOARCH=amd64. (only 386)

Which version of amd64 do we assume? Decide and document.

/cc @randall77 @ianlancetaylor @rsc @mdempsky @josharian @minux @cherrymui @aclements ",1,doc  figure out  document   minimum requirements   in    khr adds popcount intrinsics for       i realize that our   doesn t say anything about goarch     only       which version of   do we assume  decide and document      cc     ianlancetaylor  rsc  mdempsky  josharian  minux  cherrymui  aclements ,1
317318,23671736220.0,IssuesEvent,2022-08-27 13:11:59,golang/go,https://api.github.com/repos/golang/go,closed,site: https://golang.org/doc/install incorrectly lists minumum kernel version for linux/arm as 2.6.23,Documentation NeedsInvestigation,"https://golang.org/doc/install states that the minimum kernel version for all linux platform is 2.6.23. This is not correct. The minimum for linux/arm is 2.6.27 (possibly 28), however this contradicts information from the wiki, https://github.com/golang/go/wiki/Linux

See #3897

See also https://codereview.appspot.com/7225047/
",1.0,"site: https://golang.org/doc/install incorrectly lists minumum kernel version for linux/arm as 2.6.23 - https://golang.org/doc/install states that the minimum kernel version for all linux platform is 2.6.23. This is not correct. The minimum for linux/arm is 2.6.27 (possibly 28), however this contradicts information from the wiki, https://github.com/golang/go/wiki/Linux

See #3897

See also https://codereview.appspot.com/7225047/
",1,site    incorrectly lists minumum kernel version for linux arm as           states that the minimum kernel version for all linux platform is        this is not correct  the minimum for linux arm is        possibly     however this contradicts information from the wiki       see       see also    ,1
366626,25594575526.0,IssuesEvent,2022-12-01 15:18:24,golang/go,https://api.github.com/repos/golang/go,closed,docs: go fuzzing docs in go.dev blog,Documentation,"Hey, everyone! 

I read the [article](https://go.dev/security/fuzz/) in DARK mode about go fuzzing. I guess, source code by black font on grey background look awful.

Please, fix it  

",1.0,"docs: go fuzzing docs in go.dev blog - Hey, everyone! 

I read the [article](https://go.dev/security/fuzz/) in DARK mode about go fuzzing. I guess, source code by black font on grey background look awful.

Please, fix it  

",1,docs  go fuzzing docs in go dev blog   hey  everyone      i read the     in dark mode about go fuzzing  i guess  source code by black font on grey background look awful     please  fix it      ,1
35025,6401270271.0,IssuesEvent,2017-08-05 19:16:21,golang/go,https://api.github.com/repos/golang/go,opened,doc: document the lack of support for symlinks under GOPATH,Documentation,"Quick back story:
I've spent much longer than I should publicly admit developing Go with go guru half working. Whenever I tried to jump to a symbol in the current package outside the current file, go guru would fail to find the identifier. This was annoying, but I've become accustomed enough to broken tooling that I didn't think too much of it after a search of the vim-go issue tracker didn't mention anything.

Today I got annoyed enough by the issue that I searched a bit harder and came across #20981 which in turn led me to #15507. Since I had been symlinking my privately hosted repo into my GOPATH, I immediately understood what was wrong. Fixing the issue was as simple as swapping the source and destination of my symlink. Now go guru finds all my symbols, which is great.

Anyway, the main issue here is that a lot of developers use symlinks for perfectly valid reasons, but GOPATH doesn't support them. This causes some elements of the go tooling to break without warning, and should therefore be prominently documented in `go help gopath` and https://golang.org/doc/code.html#GOPATH.

I can go ahead and submit a change, but I wanted to create an issue first to make sure this was fine.",1.0,"doc: document the lack of support for symlinks under GOPATH - Quick back story:
I've spent much longer than I should publicly admit developing Go with go guru half working. Whenever I tried to jump to a symbol in the current package outside the current file, go guru would fail to find the identifier. This was annoying, but I've become accustomed enough to broken tooling that I didn't think too much of it after a search of the vim-go issue tracker didn't mention anything.

Today I got annoyed enough by the issue that I searched a bit harder and came across #20981 which in turn led me to #15507. Since I had been symlinking my privately hosted repo into my GOPATH, I immediately understood what was wrong. Fixing the issue was as simple as swapping the source and destination of my symlink. Now go guru finds all my symbols, which is great.

Anyway, the main issue here is that a lot of developers use symlinks for perfectly valid reasons, but GOPATH doesn't support them. This causes some elements of the go tooling to break without warning, and should therefore be prominently documented in `go help gopath` and https://golang.org/doc/code.html#GOPATH.

I can go ahead and submit a change, but I wanted to create an issue first to make sure this was fine.",1,doc  document the lack of support for symlinks under gopath   quick back story   i ve spent much longer than i should publicly admit developing go with go guru half working  whenever i tried to jump to a symbol in the current package outside the current file  go guru would fail to find the identifier  this was annoying  but i ve become accustomed enough to broken tooling that i didn t think too much of it after a search of the vim go issue tracker didn t mention anything     today i got annoyed enough by the issue that i searched a bit harder and came across    which in turn led me to     since i had been symlinking my privately hosted repo into my gopath  i immediately understood what was wrong  fixing the issue was as simple as swapping the source and destination of my symlink  now go guru finds all my symbols  which is great     anyway  the main issue here is that a lot of developers use symlinks for perfectly valid reasons  but gopath doesn t support them  this causes some elements of the go tooling to break without warning  and should therefore be prominently documented in  go help gopath  and      i can go ahead and submit a change  but i wanted to create an issue first to make sure this was fine ,1
206696,16049986467.0,IssuesEvent,2021-04-22 17:53:28,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/gopls: textDocument/completion suggests internal packages from other modules,Documentation Tools gopls,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.16.3 linux/amd64
</pre>

#### gopls version

<pre>
$ gopls version
golang.org/x/tools/gopls v0.6.10
</pre>

#### vscode-go version

```
Id: golang.go
Version: 0.24.2
```

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""~/.cache/go-build""
GOENV=""~/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""~/.go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""~/.go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/lib/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/lib/go/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""go1.16.3""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build1429872732=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

I'll take `Tag` from `golang.org/x/text/language` as an example.

1. I create variable and start typing `language.Tag`
2. LSP client (vscode-go in my case) tries to make a code completion for package that isn't yet imported in current scope

### What did you expect to see?

I expect to **not** see suggestions for `internal` packages from `golang.org/x` when I'm working inside my own modules since these imports will be restricted and cannot be used.

### What did you see instead?

Sometimes (actually quite a lot of times) first suggestion comes from `x/text/internal/language` instead of `x/text/language`.

<details><summary>gopls trace</summary><pre>[Trace - 19:50:58.056 PM] Received response 'textDocument/completion - (57)' in 47ms.
Result: {""isIncomplete"":true,""items"":[{""label"":""language.Language"",""kind"":7,""detail"":""uint16 (from \""golang.org/x/text/internal/language\"")"",""preselect"":true,""sortText"":""00000"",""filterText"":""language.Language"",""insertTextFormat"":2,""textEdit"":{""range"":{""start"":{""line"":36,""character"":1},""end"":{""line"":36,""character"":9}},""newText"":""language.Language""},""additionalTextEdits"":[{""range"":{""start"":{""line"":3,""character"":2},""end"":{""line"":3,""character"":2}},""newText"":""golang.org/x/text/internal/language\""\n\t\""""}]},{""label"":""language"",""kind"":9,""detail"":""\""golang.org/x/text/language\"""",""sortText"":""00001"",""filterText"":""language"",""insertTextFormat"":2,""textEdit"":{""range"":{""start"":{""line"":36,""character"":1},""end"":{""line"":36,""character"":9}},""newText"":""language""},""additionalTextEdits"":[{""range"":{""start"":{""line"":3,""character"":2},""end"":{""line"":3,""character"":2}},""newText"":""golang.org/x/text/language\""\n\t\""""}]},{""label"":""language"",""kind"":9,""detail"":""\""golang.org/x/text/internal/language\"""",""sortText"":""00002"",""filterText"":""language"",""insertTextFormat"":2,""textEdit"":{""range"":{""start"":{""line"":36,""character"":1},""end"":{""line"":36,""character"":9}},""newText"":""language""},""additionalTextEdits"":[{""range"":{""start"":{""line"":3,""character"":2},""end"":{""line"":3,""character"":2}},""newText"":""golang.org/x/text/internal/language\""\n\t\""""}]},{""label"":""language.BaseLanguages"",""kind"":3,""detail"":""func() []language.Language (from \""golang.org/x/text/internal/language\"")"",""documentation"":""BaseLanguages returns the list of all supported base languages. It generates\nthe list by traversing the internal structures.\n"",""sortText"":""00003"",""filterText"":""language.BaseLanguages"",""insertTextFormat"":2,""textEdit"":{""range"":{""start"":{""line"":36,""character"":1},""end"":{""line"":36,""character"":9}},""newText"":""language.BaseLanguages()""},""additionalTextEdits"":[{""range"":{""start"":{""line"":3,""character"":2},""end"":{""line"":3,""character"":2}},""newText"":""golang.org/x/text/internal/language\""\n\t\""""}]},{""label"":""language.ParseAcceptLanguage"",""kind"":3,""detail"":""func(s string) (tag []language.Tag, q []float32, err error) (from \""golang.org/x/text/language\"")"",""documentation"":""ParseAcceptLanguage parses the contents of an Accept-Language header as\ndefined in http://www.ietf.org/rfc/rfc2616.txt and returns a list of Tags and\na list of corresponding quality weights. It is more permissive than RFC 2616\nand may return non-nil slices even if the input is not valid.\nThe Tags will be sorted by highest weight first and then by first occurrence.\nTags with a weight of zero will be dropped. An error will be returned if the\ninput could not be parsed.\n"",""sortText"":""00004"",""filterText"":""language.ParseAcceptLanguage"",""insertTextFormat"":2,""textEdit"":{""range"":{""start"":{""line"":36,""character"":1},""end"":{""line"":36,""character"":9}},""newText"":""language.ParseAcceptLanguage(${1:})""},""additionalTextEdits"":[{""range"":{""start"":{""line"":3,""character"":2},""end"":{""line"":3,""character"":2}},""newText"":""golang.org/x/text/language\""\n\t\""""}]},{""label"":""language"",""kind"":9,""detail"":""\""google.golang.org/genproto/googleapis/cloud/language/v1\"""",""sortText"":""00007"",""filterText"":""language"",""insertTextFormat"":2,""textEdit"":{""range"":{""start"":{""line"":36,""character"":1},""end"":{""line"":36,""character"":9}},""newText"":""language""},""additionalTextEdits"":[{""range"":{""start"":{""line"":3,""character"":2},""end"":{""line"":3,""character"":2}},""newText"":""google.golang.org/genproto/googleapis/cloud/language/v1\""\n\t\""""}]},{""label"":""language"",""kind"":9,""detail"":""\""google.golang.org/api/language/v1\"""",""sortText"":""00008"",""filterText"":""language"",""insertTextFormat"":2,""textEdit"":{""range"":{""start"":{""line"":36,""character"":1},""end"":{""line"":36,""character"":9}},""newText"":""language""},""additionalTextEdits"":[{""range"":{""start"":{""line"":3,""character"":2},""end"":{""line"":3,""character"":2}},""newText"":""google.golang.org/api/language/v1\""\n\t\""""}]}]}</pre></details>
",1.0,"x/tools/gopls: textDocument/completion suggests internal packages from other modules - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.16.3 linux/amd64
</pre>

#### gopls version

<pre>
$ gopls version
golang.org/x/tools/gopls v0.6.10
</pre>

#### vscode-go version

```
Id: golang.go
Version: 0.24.2
```

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""~/.cache/go-build""
GOENV=""~/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""~/.go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""~/.go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/lib/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/lib/go/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""go1.16.3""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build1429872732=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

I'll take `Tag` from `golang.org/x/text/language` as an example.

1. I create variable and start typing `language.Tag`
2. LSP client (vscode-go in my case) tries to make a code completion for package that isn't yet imported in current scope

### What did you expect to see?

I expect to **not** see suggestions for `internal` packages from `golang.org/x` when I'm working inside my own modules since these imports will be restricted and cannot be used.

### What did you see instead?

Sometimes (actually quite a lot of times) first suggestion comes from `x/text/internal/language` instead of `x/text/language`.

<details><summary>gopls trace</summary><pre>[Trace - 19:50:58.056 PM] Received response 'textDocument/completion - (57)' in 47ms.
Result: {""isIncomplete"":true,""items"":[{""label"":""language.Language"",""kind"":7,""detail"":""uint16 (from \""golang.org/x/text/internal/language\"")"",""preselect"":true,""sortText"":""00000"",""filterText"":""language.Language"",""insertTextFormat"":2,""textEdit"":{""range"":{""start"":{""line"":36,""character"":1},""end"":{""line"":36,""character"":9}},""newText"":""language.Language""},""additionalTextEdits"":[{""range"":{""start"":{""line"":3,""character"":2},""end"":{""line"":3,""character"":2}},""newText"":""golang.org/x/text/internal/language\""\n\t\""""}]},{""label"":""language"",""kind"":9,""detail"":""\""golang.org/x/text/language\"""",""sortText"":""00001"",""filterText"":""language"",""insertTextFormat"":2,""textEdit"":{""range"":{""start"":{""line"":36,""character"":1},""end"":{""line"":36,""character"":9}},""newText"":""language""},""additionalTextEdits"":[{""range"":{""start"":{""line"":3,""character"":2},""end"":{""line"":3,""character"":2}},""newText"":""golang.org/x/text/language\""\n\t\""""}]},{""label"":""language"",""kind"":9,""detail"":""\""golang.org/x/text/internal/language\"""",""sortText"":""00002"",""filterText"":""language"",""insertTextFormat"":2,""textEdit"":{""range"":{""start"":{""line"":36,""character"":1},""end"":{""line"":36,""character"":9}},""newText"":""language""},""additionalTextEdits"":[{""range"":{""start"":{""line"":3,""character"":2},""end"":{""line"":3,""character"":2}},""newText"":""golang.org/x/text/internal/language\""\n\t\""""}]},{""label"":""language.BaseLanguages"",""kind"":3,""detail"":""func() []language.Language (from \""golang.org/x/text/internal/language\"")"",""documentation"":""BaseLanguages returns the list of all supported base languages. It generates\nthe list by traversing the internal structures.\n"",""sortText"":""00003"",""filterText"":""language.BaseLanguages"",""insertTextFormat"":2,""textEdit"":{""range"":{""start"":{""line"":36,""character"":1},""end"":{""line"":36,""character"":9}},""newText"":""language.BaseLanguages()""},""additionalTextEdits"":[{""range"":{""start"":{""line"":3,""character"":2},""end"":{""line"":3,""character"":2}},""newText"":""golang.org/x/text/internal/language\""\n\t\""""}]},{""label"":""language.ParseAcceptLanguage"",""kind"":3,""detail"":""func(s string) (tag []language.Tag, q []float32, err error) (from \""golang.org/x/text/language\"")"",""documentation"":""ParseAcceptLanguage parses the contents of an Accept-Language header as\ndefined in http://www.ietf.org/rfc/rfc2616.txt and returns a list of Tags and\na list of corresponding quality weights. It is more permissive than RFC 2616\nand may return non-nil slices even if the input is not valid.\nThe Tags will be sorted by highest weight first and then by first occurrence.\nTags with a weight of zero will be dropped. An error will be returned if the\ninput could not be parsed.\n"",""sortText"":""00004"",""filterText"":""language.ParseAcceptLanguage"",""insertTextFormat"":2,""textEdit"":{""range"":{""start"":{""line"":36,""character"":1},""end"":{""line"":36,""character"":9}},""newText"":""language.ParseAcceptLanguage(${1:})""},""additionalTextEdits"":[{""range"":{""start"":{""line"":3,""character"":2},""end"":{""line"":3,""character"":2}},""newText"":""golang.org/x/text/language\""\n\t\""""}]},{""label"":""language"",""kind"":9,""detail"":""\""google.golang.org/genproto/googleapis/cloud/language/v1\"""",""sortText"":""00007"",""filterText"":""language"",""insertTextFormat"":2,""textEdit"":{""range"":{""start"":{""line"":36,""character"":1},""end"":{""line"":36,""character"":9}},""newText"":""language""},""additionalTextEdits"":[{""range"":{""start"":{""line"":3,""character"":2},""end"":{""line"":3,""character"":2}},""newText"":""google.golang.org/genproto/googleapis/cloud/language/v1\""\n\t\""""}]},{""label"":""language"",""kind"":9,""detail"":""\""google.golang.org/api/language/v1\"""",""sortText"":""00008"",""filterText"":""language"",""insertTextFormat"":2,""textEdit"":{""range"":{""start"":{""line"":36,""character"":1},""end"":{""line"":36,""character"":9}},""newText"":""language""},""additionalTextEdits"":[{""range"":{""start"":{""line"":3,""character"":2},""end"":{""line"":3,""character"":2}},""newText"":""google.golang.org/api/language/v1\""\n\t\""""}]}]}</pre></details>
",1,x tools gopls  textdocument completion suggests internal packages from other modules         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version            go version  go version       linux              gopls version         gopls version  golang org x tools gopls                  vscode go version         id  golang go  version                    does this issue reproduce with the latest release     yes         what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache     cache go build   goenv     config go env   goexe     goflags     gohostarch      gohostos  linux   goinsecure     gomodcache     go pkg mod   gonoproxy     gonosumdb     goos  linux   gopath     go   goprivate     goproxy     goroot   usr lib go   gosumdb  sum golang org   gotmpdir     gotooldir   usr lib go pkg tool linux     govcs     goversion          gccgo  gccgo   ar  ar   cc  gcc   cxx  g     cgo enabled      gomod   dev null   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches             what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best          i ll take  tag  from  golang org x text language  as an example        i create variable and start typing  language tag      lsp client  vscode go in my case  tries to make a code completion for package that isn t yet imported in current scope        what did you expect to see     i expect to   not   see suggestions for  internal  packages from  golang org x  when i m working inside my own modules since these imports will be restricted and cannot be used         what did you see instead     sometimes  actually quite a lot of times  first suggestion comes from  x text internal language  instead of  x text language        gopls trace    received response  textdocument completion        in     result    isincomplete  true  items       label   language   kind     detail     golang org x text language     sorttext       filtertext   language   inserttextformat     textedit    range    start    line     character      end    line     character       newtext   language    additionaltextedits       label   language   kind     detail     golang org x text internal language     sorttext       filtertext   language   inserttextformat     textedit    range    start    line     character      end    line     character       newtext   language    additionaltextedits       label   language baselanguages   kind     detail   func    language language  from   golang org x text internal language      documentation   baselanguages returns the list of all supported base languages  it generates nthe list by traversing the internal structures  n   sorttext       filtertext   language baselanguages   inserttextformat     textedit    range    start    line     character      end    line     character       newtext   language baselanguages      additionaltextedits       label   language parseacceptlanguage   kind     detail   func s string   tag  language tag  q     err error   from   golang org x text language      documentation   parseacceptlanguage parses the contents of an accept language header as ndefined in   and returns a list of tags and na list of corresponding quality weights  it is more permissive than rfc   nand may return non nil slices even if the input is not valid  nthe tags will be sorted by highest weight first and then by first occurrence  ntags with a weight of zero will be dropped  an error will be returned if the ninput could not be parsed  n   sorttext       filtertext   language parseacceptlanguage   inserttextformat     textedit    range    start    line     character      end    line     character       newtext   language parseacceptlanguage           additionaltextedits       label   language   kind     detail     google golang org genproto googleapis cloud language       sorttext       filtertext   language   inserttextformat     textedit    range    start    line     character      end    line     character       newtext   language    additionaltextedits       label   language   kind     detail     google golang org api language       sorttext       filtertext   language   inserttextformat     textedit    range    start    line     character      end    line     character       newtext   language    additionaltextedits          ,1
50503,7607023924.0,IssuesEvent,2018-04-30 15:10:43,golang/go,https://api.github.com/repos/golang/go,closed,"Brand Book: Instead of the RGB color code for Pantone 669 C, the Fuchsia code is listed",Documentation,"### What did you do?

I took a look at the Go [Brand Book](https://storage.googleapis.com/golang-assets/go-brand-book-v1.0.pdf) and saw an incorrect color code on page 16.

### What did you expect to see?

Under color [Pantone 669 C](https://www.pantone.com/color-finder/669-C) (under the ""More colors"" section on page 16), I expected to see the correct RGB color code, which is `63, 42, 86`.

### What did you see instead?

Instead, I saw the RGB code `200, 50, 98` listed underneath, which is the RGB code for Fuchsia.
",1.0,"Brand Book: Instead of the RGB color code for Pantone 669 C, the Fuchsia code is listed - ### What did you do?

I took a look at the Go [Brand Book](https://storage.googleapis.com/golang-assets/go-brand-book-v1.0.pdf) and saw an incorrect color code on page 16.

### What did you expect to see?

Under color [Pantone 669 C](https://www.pantone.com/color-finder/669-C) (under the ""More colors"" section on page 16), I expected to see the correct RGB color code, which is `63, 42, 86`.

### What did you see instead?

Instead, I saw the RGB code `200, 50, 98` listed underneath, which is the RGB code for Fuchsia.
",1,brand book  instead of the rgb color code for pantone   c  the fuchsia code is listed       what did you do     i took a look at the go     and saw an incorrect color code on page           what did you expect to see     under color      under the  more colors  section on page     i expected to see the correct rgb color code  which is                   what did you see instead     instead  i saw the rgb code           listed underneath  which is the rgb code for fuchsia   ,1
58280,8244678824.0,IssuesEvent,2018-09-11 07:18:07,golang/go,https://api.github.com/repos/golang/go,opened,"doc: FAQ entry explaining Go is spelled Go, not Golang",Documentation,This seems to be a recurring point of confusion. Maybe a FAQ entry on correct usage would help.,1.0,"doc: FAQ entry explaining Go is spelled Go, not Golang - This seems to be a recurring point of confusion. Maybe a FAQ entry on correct usage would help.",1,doc  faq entry explaining go is spelled go  not golang   this seems to be a recurring point of confusion  maybe a faq entry on correct usage would help ,1
21564,4725397131.0,IssuesEvent,2016-10-18 06:20:16,golang/go,https://api.github.com/repos/golang/go,closed,net/url: url.RawQuery = url.Query().Encode() can change the URL,Documentation,"In the following code:

```go
u, _ := url.Parse(""http://www.example.com/path?foo"")
fmt.Println(u)
u.RawQuery = u.Query().Encode()
fmt.Println(u)
```

The third line actually changes the URL. The [output](https://play.golang.org/p/HPRB2NlCq4) is:

```
http://www.example.com/path?foo
http://www.example.com/path?foo=
```

A strict reading of [RFC 3986 Section 6](https://tools.ietf.org/html/rfc3986#section-6) suggests that these are two different URLs even after applying the (optional) syntax-based normalizations described in Section 6.2.2. I know of some servers that consider these URLs different. For example, compare the following links:

[http://www.vcfed.org/forum/forumdisplay.php?23-DEC](http://www.vcfed.org/forum/forumdisplay.php?23-DEC)
[http://www.vcfed.org/forum/forumdisplay.php?23-DEC=](http://www.vcfed.org/forum/forumdisplay.php?23-DEC=)

I consider this a bug, but I doubt we could fix this bug in a backwards-compatible way. At least, I think we should update the documentation to make it clear that url.Query().Encode() can change query param ""foo"" to ""foo="", which may be considered a different URL by some servers.",1.0,"net/url: url.RawQuery = url.Query().Encode() can change the URL - In the following code:

```go
u, _ := url.Parse(""http://www.example.com/path?foo"")
fmt.Println(u)
u.RawQuery = u.Query().Encode()
fmt.Println(u)
```

The third line actually changes the URL. The [output](https://play.golang.org/p/HPRB2NlCq4) is:

```
http://www.example.com/path?foo
http://www.example.com/path?foo=
```

A strict reading of [RFC 3986 Section 6](https://tools.ietf.org/html/rfc3986#section-6) suggests that these are two different URLs even after applying the (optional) syntax-based normalizations described in Section 6.2.2. I know of some servers that consider these URLs different. For example, compare the following links:

[http://www.vcfed.org/forum/forumdisplay.php?23-DEC](http://www.vcfed.org/forum/forumdisplay.php?23-DEC)
[http://www.vcfed.org/forum/forumdisplay.php?23-DEC=](http://www.vcfed.org/forum/forumdisplay.php?23-DEC=)

I consider this a bug, but I doubt we could fix this bug in a backwards-compatible way. At least, I think we should update the documentation to make it clear that url.Query().Encode() can change query param ""foo"" to ""foo="", which may be considered a different URL by some servers.",1,net url  url rawquery   url query   encode   can change the url   in the following code        go  u       url parse     fmt println u   u rawquery   u query   encode    fmt println u          the third line actually changes the url  the     is                       a strict reading of     suggests that these are two different urls even after applying the  optional  syntax based normalizations described in section        i know of some servers that consider these urls different  for example  compare the following links                 i consider this a bug  but i doubt we could fix this bug in a backwards compatible way  at least  i think we should update the documentation to make it clear that url query   encode   can change query param  foo  to  foo    which may be considered a different url by some servers ,1
143412,11563004515.0,IssuesEvent,2020-02-20 04:32:23,ansible/ansible,https://api.github.com/repos/ansible/ansible,closed,ansible-test validate-modules for PS modules not loading Ansible utils when in collection,affects_2.10 bug needs_triage support:core test,"##### SUMMARY
When running `ansible-test sanity --test validate-modules` on a PowerShell module in a collection it will fail to import any module util that is in Ansible itself. This causes issues if it requires access to those utils to build the arg spec as we can see with https://app.shippable.com/github/ansible-collections/ansible.windows/runs/16/5/console.

##### ISSUE TYPE
- Bug Report

##### COMPONENT NAME
ansible-test validate-modules

##### ANSIBLE VERSION
```paste below
devel
```

##### CONFIGURATION
N/A

##### OS / ENVIRONMENT
N/A - ansible-test against a collection",1.0,"ansible-test validate-modules for PS modules not loading Ansible utils when in collection - ##### SUMMARY
When running `ansible-test sanity --test validate-modules` on a PowerShell module in a collection it will fail to import any module util that is in Ansible itself. This causes issues if it requires access to those utils to build the arg spec as we can see with https://app.shippable.com/github/ansible-collections/ansible.windows/runs/16/5/console.

##### ISSUE TYPE
- Bug Report

##### COMPONENT NAME
ansible-test validate-modules

##### ANSIBLE VERSION
```paste below
devel
```

##### CONFIGURATION
N/A

##### OS / ENVIRONMENT
N/A - ansible-test against a collection",0,ansible test validate modules for ps modules not loading ansible utils when in collection         summary  when running  ansible test sanity   test validate modules  on a powershell module in a collection it will fail to import any module util that is in ansible itself  this causes issues if it requires access to those utils to build the arg spec as we can see with            issue type    bug report          component name  ansible test validate modules          ansible version     paste below  devel               configuration  n a          os   environment  n a   ansible test against a collection,0
212783,7242641818.0,IssuesEvent,2018-02-14 08:44:11,webcompat/web-bugs,https://api.github.com/repos/webcompat/web-bugs,closed,url is long with no file extensionabout:blank - site is not usable,browser-yes-firefox-mobile priority-normal status-needsinfo,"<!-- @browser: yes Firefox Mobile 60.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 6.0.1; Mobile; rv:60.0) Gecko/60.0 Firefox/60.0 -->
<!-- @reported_with: mobile-reporter -->

**URL**: http://url is long with no file extensionabout:blank

**Browser / Version**: yes Firefox Mobile 60.0
**Operating System**: Android 6.0.1
**Tested Another Browser**: No

**Problem type**: Site is not usable
**Description**: it does not show and in URL says about blank
**Steps to Reproduce**:
I tried to open it and look at who sent it as well as code dsta



_From [webcompat.com](https://webcompat.com/) with ❤️_",1.0,"url is long with no file extensionabout:blank - site is not usable - <!-- @browser: yes Firefox Mobile 60.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 6.0.1; Mobile; rv:60.0) Gecko/60.0 Firefox/60.0 -->
<!-- @reported_with: mobile-reporter -->

**URL**: http://url is long with no file extensionabout:blank

**Browser / Version**: yes Firefox Mobile 60.0
**Operating System**: Android 6.0.1
**Tested Another Browser**: No

**Problem type**: Site is not usable
**Description**: it does not show and in URL says about blank
**Steps to Reproduce**:
I tried to open it and look at who sent it as well as code dsta



_From [webcompat.com](https://webcompat.com/) with ❤️_",0,url is long with no file extensionabout blank   site is not usable            url      is long with no file extensionabout blank    browser   version    yes firefox mobile       operating system    android         tested another browser    no    problem type    site is not usable   description    it does not show and in url says about blank   steps to reproduce    i tried to open it and look at who sent it as well as code dsta     from     with ❤️ ,0
129244,27430159384.0,IssuesEvent,2023-03-02 00:15:13,dotnet/roslyn,https://api.github.com/repos/dotnet/roslyn,closed,Move method parameter left or right with a key combination,Area-IDE Feature Request IDE-CodeStyle,"**Version Used**: 
Version 16.7.0 Preview 3.0 [30126.178.master]
**Expected Behavior**:
Refactoring command moving method parameter left or right with a key combination (e.g. Ctrl+Shift+Alt + (->, <-)
Before:
```C#
public void Do(string a, int b)
```
After:
```C#
public void Do(int b, string a)
```
**Actual Behavior**:
Not implemented",1.0,"Move method parameter left or right with a key combination - **Version Used**: 
Version 16.7.0 Preview 3.0 [30126.178.master]
**Expected Behavior**:
Refactoring command moving method parameter left or right with a key combination (e.g. Ctrl+Shift+Alt + (->, <-)
Before:
```C#
public void Do(string a, int b)
```
After:
```C#
public void Do(int b, string a)
```
**Actual Behavior**:
Not implemented",0,move method parameter left or right with a key combination     version used      version       preview          expected behavior     refactoring command moving method parameter left or right with a key combination  e g  ctrl shift alt             before      c   public void do string a  int b        after      c   public void do int b  string a          actual behavior     not implemented,0
53297,7822208513.0,IssuesEvent,2018-06-14 01:02:08,golang/go,https://api.github.com/repos/golang/go,closed,cmd/vet: more clearly document go tool vet on a single file,Documentation,"#### What did you do?
After upgrading from 1.9.4 to 1.10, I ran `go vet` against a single test file.
```
$ go vet vetissue_test.go
```

I have simplified the code that gave me the original issue and uploaded it
[here](https://github.com/ooesili/vetissue).

#### What did you expect to see?
No output, and a successful exit code. This command succeeded on Go 1.9.4.

#### What did you see instead?
```
$ go vet vetissue_test.go
# command-line-arguments
./vetissue_test.go:6:6: undefined: value
```

What's happening here is that `go vet` is complaining about not being able to
find the definition of an identifier that was declared in a different file in
the same package.

It looks like this change in behaviour was introduced in an effort to run `go
vet` in parallel with `go test`, specifically in https://golang.org/cl/74355
which causes `go vet` to fail when the type check fails.

I'm not really sure what the best course of action is here. My thought is that
when running go vet against a single file, you can never be guaranteed to have
all of the type information you need, so we could ignore type check failures in
vet against single files.

#### System details

```
go version go1.10 darwin/amd64
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/wmerkel/Library/Caches/go-build""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/wmerkel/go""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.10/libexec""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/1.10/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/52/h8r09kdd5t17prlr9whr4cs4pm06q9/T/go-build420935568=/tmp/go-build -gno-record-gcc-switches -fno-common""
GOROOT/bin/go version: go version go1.10 darwin/amd64
GOROOT/bin/go tool compile -V: compile version go1.10
uname -v: Darwin Kernel Version 17.4.0: Sun Dec 17 09:19:54 PST 2017; root:xnu-4570.41.2~1/RELEASE_X86_64
ProductName:	Mac OS X
ProductVersion:	10.13.3
BuildVersion:	17D47
lldb --version: lldb-900.0.64
  Swift-4.0
```",1.0,"cmd/vet: more clearly document go tool vet on a single file - #### What did you do?
After upgrading from 1.9.4 to 1.10, I ran `go vet` against a single test file.
```
$ go vet vetissue_test.go
```

I have simplified the code that gave me the original issue and uploaded it
[here](https://github.com/ooesili/vetissue).

#### What did you expect to see?
No output, and a successful exit code. This command succeeded on Go 1.9.4.

#### What did you see instead?
```
$ go vet vetissue_test.go
# command-line-arguments
./vetissue_test.go:6:6: undefined: value
```

What's happening here is that `go vet` is complaining about not being able to
find the definition of an identifier that was declared in a different file in
the same package.

It looks like this change in behaviour was introduced in an effort to run `go
vet` in parallel with `go test`, specifically in https://golang.org/cl/74355
which causes `go vet` to fail when the type check fails.

I'm not really sure what the best course of action is here. My thought is that
when running go vet against a single file, you can never be guaranteed to have
all of the type information you need, so we could ignore type check failures in
vet against single files.

#### System details

```
go version go1.10 darwin/amd64
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/wmerkel/Library/Caches/go-build""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/wmerkel/go""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.10/libexec""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/1.10/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/52/h8r09kdd5t17prlr9whr4cs4pm06q9/T/go-build420935568=/tmp/go-build -gno-record-gcc-switches -fno-common""
GOROOT/bin/go version: go version go1.10 darwin/amd64
GOROOT/bin/go tool compile -V: compile version go1.10
uname -v: Darwin Kernel Version 17.4.0: Sun Dec 17 09:19:54 PST 2017; root:xnu-4570.41.2~1/RELEASE_X86_64
ProductName:	Mac OS X
ProductVersion:	10.13.3
BuildVersion:	17D47
lldb --version: lldb-900.0.64
  Swift-4.0
```",1,cmd vet  more clearly document go tool vet on a single file        what did you do   after upgrading from       to      i ran  go vet  against a single test file          go vet vetissue test go         i have simplified the code that gave me the original issue and uploaded it              what did you expect to see   no output  and a successful exit code  this command succeeded on go                what did you see instead          go vet vetissue test go    command line arguments    vetissue test go      undefined  value         what s happening here is that  go vet  is complaining about not being able to  find the definition of an identifier that was declared in a different file in  the same package     it looks like this change in behaviour was introduced in an effort to run  go  vet  in parallel with  go test   specifically in    which causes  go vet  to fail when the type check fails     i m not really sure what the best course of action is here  my thought is that  when running go vet against a single file  you can never be guaranteed to have  all of the type information you need  so we could ignore type check failures in  vet against single files          system details         go version     darwin    goarch      gobin     gocache   users wmerkel library caches go build   goexe     gohostarch      gohostos  darwin   goos  darwin   gopath   users wmerkel go   gorace     goroot   usr local cellar go     libexec   gotmpdir     gotooldir   usr local cellar go     libexec pkg tool darwin     gccgo  gccgo   cc  clang   cxx  clang     cgo enabled      cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders     t go    tmp go build  gno record gcc switches  fno common   goroot bin go version  go version     darwin    goroot bin go tool compile  v  compile version      uname  v  darwin kernel version        sun dec         pst    root xnu         release      productname 	mac os x  productversion 	       buildversion 	   lldb   version  lldb          swift         ,1
240054,20007623595.0,IssuesEvent,2022-02-01 00:05:44,triggermesh/triggermesh,https://api.github.com/repos/triggermesh/triggermesh,closed,Bad assertion in E2E test for Azure Event Hubs target,bug testing,"cc @cab105 

```
  Expected
      <[]uint8 | len:182, cap:192>: {""specversion"":""1.0"",""id"":""0000"",""source"":""e2e.triggermesh"",""type"":""e2e.test"",""datacontenttype"":""text/plain"",""data"":""Hello, World"",""iotriggermeshe2e"":""e2e-azureeventhubstarget-6163""}
  to equal
      <string>: Hello, World
  In [It] at: /home/runner/work/triggermesh/triggermesh/test/e2e/targets/azureeventhubs/main.go:292
```",1.0,"Bad assertion in E2E test for Azure Event Hubs target - cc @cab105 

```
  Expected
      <[]uint8 | len:182, cap:192>: {""specversion"":""1.0"",""id"":""0000"",""source"":""e2e.triggermesh"",""type"":""e2e.test"",""datacontenttype"":""text/plain"",""data"":""Hello, World"",""iotriggermeshe2e"":""e2e-azureeventhubstarget-6163""}
  to equal
      <string>: Hello, World
  In [It] at: /home/runner/work/triggermesh/triggermesh/test/e2e/targets/azureeventhubs/main.go:292
```",0,bad assertion in   test for azure event hubs target   cc               expected             specversion         id       source     triggermesh   type     test   datacontenttype   text plain   data   hello  world         azureeventhubstarget        to equal           hello  world    in   at   home runner work triggermesh triggermesh test   targets azureeventhubs main go       ,0
36672,9856648527.0,IssuesEvent,2019-06-19 22:58:11,ApolloAuto/apollo,https://api.github.com/repos/ApolloAuto/apollo,closed,【紧急】虚拟机安装Apollo开发环境-构建失败-[ERROR] Build failed!,Module: Build Type: Help wanted,"![捕获](https://user-images.githubusercontent.com/46391287/59651795-dcc11a80-91bd-11e9-9b6f-f36ad9555fd5.PNG)


vmware**虚拟机安装apollo3.5** 失败，，拉取Apollo源代码成功，docker安装成功，docker内apollo镜像拉去成功，之后编译失败。安装指导文件参考的是“ https://www.cnblogs.com/iors/p/10862713.html”",1.0,"【紧急】虚拟机安装Apollo开发环境-构建失败-[ERROR] Build failed! - ![捕获](https://user-images.githubusercontent.com/46391287/59651795-dcc11a80-91bd-11e9-9b6f-f36ad9555fd5.PNG)


vmware**虚拟机安装apollo3.5** 失败，，拉取Apollo源代码成功，docker安装成功，docker内apollo镜像拉去成功，之后编译失败。安装指导文件参考的是“ https://www.cnblogs.com/iors/p/10862713.html”",0,【紧急】虚拟机安装apollo开发环境 构建失败   build failed              vmware        失败，，拉取apollo源代码成功，docker安装成功，docker内apollo镜像拉去成功，之后编译失败。安装指导文件参考的是“  ,0
115586,11882665464.0,IssuesEvent,2020-03-27 14:45:32,golang/go,https://api.github.com/repos/golang/go,opened,cmd/asm: update where NOFRAME is valid,Documentation,"The current comment for `NOFRAME` in `runtime/textflag.h` says:
```
// TODO(mwhudson): only implemented for ppc64x at present.
```
It's been implemented for lots (all?) architectures since.
Check our coverage and update (delete) this comment.

@mwhudson @zhangfannie ",1.0,"cmd/asm: update where NOFRAME is valid - The current comment for `NOFRAME` in `runtime/textflag.h` says:
```
// TODO(mwhudson): only implemented for ppc64x at present.
```
It's been implemented for lots (all?) architectures since.
Check our coverage and update (delete) this comment.

@mwhudson @zhangfannie ",1,cmd asm  update where noframe is valid   the current comment for  noframe  in  runtime textflag h  says           todo mwhudson   only implemented for   at present        it s been implemented for lots  all   architectures since   check our coverage and update  delete  this comment      mwhudson  zhangfannie ,1
46150,7238835961.0,IssuesEvent,2018-02-13 15:45:47,golang/go,https://api.github.com/repos/golang/go,closed,spec: type alias identity unclear,Documentation WaitingForInfo,"In the ""Type Alias"" [proposal](https://github.com/golang/proposal/blob/master/design/18130-type-alias.md#proposal) by Russ Cox & Robert Griesemer it is specified that:
> After such a declaration, T1 and T2 are identical types.

Given the above, I think that this should be made more obvious within the spec in either the [_Type Identity_](https://golang.org/ref/spec#Type_identity) section or the [_Type Declarations_](https://golang.org/ref/spec#Type_declarations), _""Alias declarations""_ sub-section.",1.0,"spec: type alias identity unclear - In the ""Type Alias"" [proposal](https://github.com/golang/proposal/blob/master/design/18130-type-alias.md#proposal) by Russ Cox & Robert Griesemer it is specified that:
> After such a declaration, T1 and T2 are identical types.

Given the above, I think that this should be made more obvious within the spec in either the [_Type Identity_](https://golang.org/ref/spec#Type_identity) section or the [_Type Declarations_](https://golang.org/ref/spec#Type_declarations), _""Alias declarations""_ sub-section.",1,spec  type alias identity unclear   in the  type alias      by russ cox   robert griesemer it is specified that     after such a declaration    and   are identical types     given the above  i think that this should be made more obvious within the spec in either the     section or the       alias declarations   sub section ,1
38421,6670599130.0,IssuesEvent,2017-10-04 00:46:56,golang/go,https://api.github.com/repos/golang/go,closed,"plugin: ambiguous/undocumented ldflags=""-pluginpath ... -X ...""",Documentation,"Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?

```
go version go1.8 linux/amd64
```

### What operating system and processor architecture are you using (`go env`)?

```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/fsenart/projects""
GORACE=""""
GOROOT=""/home/fsenart/tools/go1.8""
GOTOOLDIR=""/home/fsenart/tools/go1.8/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build076969156=/tmp/go-build -gno-record-gcc-switches""
CXX=""g++""
CGO_ENABLED=""1""
PKG_CONFIG=""pkg-config""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
```

### What did you do?

`$GOPATH/src/issue_ldflags/host.go`

```go
// +build host

package main

import ""plugin""

var hostDummy string = ""EMPTY""

func main() {
	p, err := plugin.Open(""guest.so"")
	if err != nil {
		panic(err)
	}
	f, err := p.Lookup(""F"")
	if err != nil {
		panic(err)
	}

	println(hostDummy)

	f.(func())()
}
```

`$GOPATH/src/issue_ldflags/guest.go`

```go
// +build guest

package main

var guestDummy string = ""EMPTY""

func F() {
	println(guestDummy)
}
```

`$GOPATH/src/issue_ldflags/Makefile`

```Makefile
scenario_1:
	# INSIDE GOPATH & compile WITHOUT specifying source file
	@echo Host
	@echo ===
	@go build -tags host -ldflags='-X main.hostDummy=dummyHost' -o host
	@nm host | grep hostDummy
	@echo Guest
	@echo =====
	@go build -tags guest -buildmode=plugin -ldflags='-X $(shell basename $(CURDIR)).guestDummy=dummyGuest' -o guest.so
	@nm guest.so | grep guestDummy
	@echo Run
	@echo ===
	@./host
	@echo ===
	# WITH custom plugin path
	# https://github.com/golang/go/blob/master/src/cmd/go/internal/work/build.go#L2412
	@go build -tags guest -buildmode=plugin -ldflags='-pluginpath=custompluginpath -X custompluginpath.guestDummy=dummyGuest' -o guest.so
	@nm guest.so | grep guestDummy
	@echo Run
	@echo ===
	@./host

scenario_2:
	# INSIDE GOPATH & compile WITH specifying source file
	@echo Host
	@echo ===
	@go build -tags host -ldflags='-X main.hostDummy=dummyHost' -o host host.go
	@nm host | grep hostDummy
	@echo Guest
	@echo =====
	# If not seeing 2 lines, change the Makefile with the seen id.
	# https://github.com/golang/go/blob/master/src/cmd/go/internal/work/build.go#L2410
	@go build -tags guest -buildmode=plugin -ldflags='-X plugin/unnamed-1edb35ed362d12b8c6c92ff2cc31ad97e4131d95.guestDummy=dummyGuest' -o guest.so guest.go
	@nm guest.so | grep guestDummy
	@echo Run
	@echo ===
	@./host
	@echo ===
	# WITH custom plugin path
	# https://github.com/golang/go/blob/master/src/cmd/go/internal/work/build.go#L2412
	@go build -tags guest -buildmode=plugin -ldflags='-pluginpath=custompluginpath -X custompluginpath.guestDummy=dummyGuest' -o guest.so guest.go
	@nm guest.so | grep guestDummy
	@echo Run
	@echo ===
	@./host

scenario_3:
	# OUTSIDE GOPATH & compile WITHOUT specifying source file
	@echo Host
	@echo ===
	@GOPATH=/nowhere go build -tags host -ldflags='-X main.hostDummy=dummyHost' -o host
	@nm host | grep hostDummy
	@echo Guest
	@echo =====
	@GOPATH=/nowhere go build -tags guest -buildmode=plugin -ldflags='-X _$(CURDIR).guestDummy=dummyGuest' -o guest.so
	@nm guest.so | grep guestDummy
	@echo Run
	@echo ===
	@./host
	@echo ===
	# WITH custom plugin path
	# https://github.com/golang/go/blob/master/src/cmd/go/internal/work/build.go#L2412
	@GOPATH=/nowhere go build -tags guest -buildmode=plugin -ldflags='-pluginpath=custompluginpath -X custompluginpath.guestDummy=dummyGuest' -o guest.so
	@nm guest.so | grep guestDummy
	@echo Run
	@echo ===
	@./host

scenario_4:
	# OUTSIDE GOPATH & compile WITH specifying source file
	@echo Host
	@echo ===
	@GOPATH=/nowhere go build -tags host -ldflags='-X main.hostDummy=dummyHost' -o host host.go
	@nm host | grep hostDummy
	@echo Guest
	@echo =====
	# https://github.com/golang/go/blob/master/src/cmd/go/internal/work/build.go#L2410
	# If not seeing 2 lines, change the Makefile with the seen id.
	@GOPATH=/nowhere go build -tags guest -buildmode=plugin -ldflags='-X plugin/unnamed-1edb35ed362d12b8c6c92ff2cc31ad97e4131d95.guestDummy=dummyGuest' -o guest.so guest.go
	@nm guest.so | grep guestDummy
	@echo Run
	@echo ===
	@./host
	@echo ===
	# WITH custom plugin path
	# https://github.com/golang/go/blob/master/src/cmd/go/internal/work/build.go#L2412
	@GOPATH=/nowhere go build -tags guest -buildmode=plugin -ldflags='-pluginpath=custompluginpath -X custompluginpath.guestDummy=dummyGuest' -o guest.so guest.go
	@nm guest.so | grep guestDummy
	@echo Run
	@echo ===
	@./host
```

If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.


### What did you expect to see?

I expect to be able to use `-ldflags=""-X importpath.guestDummy""` to set a build time variable when compiling with `-buildmode=plugin` ;  as I can do when compiling regular binaries with `-ldflags=""-X main.hostDummy""`

### What did you see instead?

In the context of plugins `importpath` is variable and depends on the building context. I found that I can have a fixed behavior when using `-pluginpath` ldflags. But this flag is not well documented:
```
  -pluginpath string
    	full path name for plugin
```
 Can I use it confidently is this context? is this the good pattern to set a build time variable in plugins?
",1.0,"plugin: ambiguous/undocumented ldflags=""-pluginpath ... -X ..."" - Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?

```
go version go1.8 linux/amd64
```

### What operating system and processor architecture are you using (`go env`)?

```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/fsenart/projects""
GORACE=""""
GOROOT=""/home/fsenart/tools/go1.8""
GOTOOLDIR=""/home/fsenart/tools/go1.8/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build076969156=/tmp/go-build -gno-record-gcc-switches""
CXX=""g++""
CGO_ENABLED=""1""
PKG_CONFIG=""pkg-config""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
```

### What did you do?

`$GOPATH/src/issue_ldflags/host.go`

```go
// +build host

package main

import ""plugin""

var hostDummy string = ""EMPTY""

func main() {
	p, err := plugin.Open(""guest.so"")
	if err != nil {
		panic(err)
	}
	f, err := p.Lookup(""F"")
	if err != nil {
		panic(err)
	}

	println(hostDummy)

	f.(func())()
}
```

`$GOPATH/src/issue_ldflags/guest.go`

```go
// +build guest

package main

var guestDummy string = ""EMPTY""

func F() {
	println(guestDummy)
}
```

`$GOPATH/src/issue_ldflags/Makefile`

```Makefile
scenario_1:
	# INSIDE GOPATH & compile WITHOUT specifying source file
	@echo Host
	@echo ===
	@go build -tags host -ldflags='-X main.hostDummy=dummyHost' -o host
	@nm host | grep hostDummy
	@echo Guest
	@echo =====
	@go build -tags guest -buildmode=plugin -ldflags='-X $(shell basename $(CURDIR)).guestDummy=dummyGuest' -o guest.so
	@nm guest.so | grep guestDummy
	@echo Run
	@echo ===
	@./host
	@echo ===
	# WITH custom plugin path
	# https://github.com/golang/go/blob/master/src/cmd/go/internal/work/build.go#L2412
	@go build -tags guest -buildmode=plugin -ldflags='-pluginpath=custompluginpath -X custompluginpath.guestDummy=dummyGuest' -o guest.so
	@nm guest.so | grep guestDummy
	@echo Run
	@echo ===
	@./host

scenario_2:
	# INSIDE GOPATH & compile WITH specifying source file
	@echo Host
	@echo ===
	@go build -tags host -ldflags='-X main.hostDummy=dummyHost' -o host host.go
	@nm host | grep hostDummy
	@echo Guest
	@echo =====
	# If not seeing 2 lines, change the Makefile with the seen id.
	# https://github.com/golang/go/blob/master/src/cmd/go/internal/work/build.go#L2410
	@go build -tags guest -buildmode=plugin -ldflags='-X plugin/unnamed-1edb35ed362d12b8c6c92ff2cc31ad97e4131d95.guestDummy=dummyGuest' -o guest.so guest.go
	@nm guest.so | grep guestDummy
	@echo Run
	@echo ===
	@./host
	@echo ===
	# WITH custom plugin path
	# https://github.com/golang/go/blob/master/src/cmd/go/internal/work/build.go#L2412
	@go build -tags guest -buildmode=plugin -ldflags='-pluginpath=custompluginpath -X custompluginpath.guestDummy=dummyGuest' -o guest.so guest.go
	@nm guest.so | grep guestDummy
	@echo Run
	@echo ===
	@./host

scenario_3:
	# OUTSIDE GOPATH & compile WITHOUT specifying source file
	@echo Host
	@echo ===
	@GOPATH=/nowhere go build -tags host -ldflags='-X main.hostDummy=dummyHost' -o host
	@nm host | grep hostDummy
	@echo Guest
	@echo =====
	@GOPATH=/nowhere go build -tags guest -buildmode=plugin -ldflags='-X _$(CURDIR).guestDummy=dummyGuest' -o guest.so
	@nm guest.so | grep guestDummy
	@echo Run
	@echo ===
	@./host
	@echo ===
	# WITH custom plugin path
	# https://github.com/golang/go/blob/master/src/cmd/go/internal/work/build.go#L2412
	@GOPATH=/nowhere go build -tags guest -buildmode=plugin -ldflags='-pluginpath=custompluginpath -X custompluginpath.guestDummy=dummyGuest' -o guest.so
	@nm guest.so | grep guestDummy
	@echo Run
	@echo ===
	@./host

scenario_4:
	# OUTSIDE GOPATH & compile WITH specifying source file
	@echo Host
	@echo ===
	@GOPATH=/nowhere go build -tags host -ldflags='-X main.hostDummy=dummyHost' -o host host.go
	@nm host | grep hostDummy
	@echo Guest
	@echo =====
	# https://github.com/golang/go/blob/master/src/cmd/go/internal/work/build.go#L2410
	# If not seeing 2 lines, change the Makefile with the seen id.
	@GOPATH=/nowhere go build -tags guest -buildmode=plugin -ldflags='-X plugin/unnamed-1edb35ed362d12b8c6c92ff2cc31ad97e4131d95.guestDummy=dummyGuest' -o guest.so guest.go
	@nm guest.so | grep guestDummy
	@echo Run
	@echo ===
	@./host
	@echo ===
	# WITH custom plugin path
	# https://github.com/golang/go/blob/master/src/cmd/go/internal/work/build.go#L2412
	@GOPATH=/nowhere go build -tags guest -buildmode=plugin -ldflags='-pluginpath=custompluginpath -X custompluginpath.guestDummy=dummyGuest' -o guest.so guest.go
	@nm guest.so | grep guestDummy
	@echo Run
	@echo ===
	@./host
```

If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.


### What did you expect to see?

I expect to be able to use `-ldflags=""-X importpath.guestDummy""` to set a build time variable when compiling with `-buildmode=plugin` ;  as I can do when compiling regular binaries with `-ldflags=""-X main.hostDummy""`

### What did you see instead?

In the context of plugins `importpath` is variable and depends on the building context. I found that I can have a fixed behavior when using `-pluginpath` ldflags. But this flag is not well documented:
```
  -pluginpath string
    	full path name for plugin
```
 Can I use it confidently is this context? is this the good pattern to set a build time variable in plugins?
",1,plugin  ambiguous undocumented ldflags   pluginpath      x        please answer these questions before submitting your issue  thanks         what version of go are you using   go version            go version     linux               what operating system and processor architecture are you using   go env            goarch      gobin     goexe     gohostarch      gohostos  linux   goos  linux   gopath   home fsenart projects   gorace     goroot   home fsenart tools       gotooldir   home fsenart tools     pkg tool linux     gccgo  gccgo   cc  gcc   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches   cxx  g     cgo enabled      pkg config  pkg config   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g                 what did you do       gopath src issue ldflags host go        go      build host    package main    import  plugin     var hostdummy string    empty     func main      	p  err    plugin open  guest so    	if err    nil    		panic err   	   	f  err    p lookup  f    	if err    nil    		panic err   	     	println hostdummy     	f  func                   gopath src issue ldflags guest go        go      build guest    package main    var guestdummy string    empty     func f      	println guestdummy               gopath src issue ldflags makefile        makefile  scenario     	  inside gopath   compile without specifying source file  	 echo host  	 echo      	 go build  tags host  ldflags   x main hostdummy dummyhost   o host  	 nm host   grep hostdummy  	 echo guest  	 echo        	 go build  tags guest  buildmode plugin  ldflags   x   shell basename   curdir   guestdummy dummyguest   o guest so  	 nm guest so   grep guestdummy  	 echo run  	 echo      	   host  	 echo      	  with custom plugin path  	     	 go build  tags guest  buildmode plugin  ldflags   pluginpath custompluginpath  x custompluginpath guestdummy dummyguest   o guest so  	 nm guest so   grep guestdummy  	 echo run  	 echo      	   host    scenario     	  inside gopath   compile with specifying source file  	 echo host  	 echo      	 go build  tags host  ldflags   x main hostdummy dummyhost   o host host go  	 nm host   grep hostdummy  	 echo guest  	 echo        	  if not seeing   lines  change the makefile with the seen id   	     	 go build  tags guest  buildmode plugin  ldflags   x plugin unnamed   guestdummy dummyguest   o guest so guest go  	 nm guest so   grep guestdummy  	 echo run  	 echo      	   host  	 echo      	  with custom plugin path  	     	 go build  tags guest  buildmode plugin  ldflags   pluginpath custompluginpath  x custompluginpath guestdummy dummyguest   o guest so guest go  	 nm guest so   grep guestdummy  	 echo run  	 echo      	   host    scenario     	  outside gopath   compile without specifying source file  	 echo host  	 echo      	 gopath  nowhere go build  tags host  ldflags   x main hostdummy dummyhost   o host  	 nm host   grep hostdummy  	 echo guest  	 echo        	 gopath  nowhere go build  tags guest  buildmode plugin  ldflags   x    curdir  guestdummy dummyguest   o guest so  	 nm guest so   grep guestdummy  	 echo run  	 echo      	   host  	 echo      	  with custom plugin path  	     	 gopath  nowhere go build  tags guest  buildmode plugin  ldflags   pluginpath custompluginpath  x custompluginpath guestdummy dummyguest   o guest so  	 nm guest so   grep guestdummy  	 echo run  	 echo      	   host    scenario     	  outside gopath   compile with specifying source file  	 echo host  	 echo      	 gopath  nowhere go build  tags host  ldflags   x main hostdummy dummyhost   o host host go  	 nm host   grep hostdummy  	 echo guest  	 echo        	     	  if not seeing   lines  change the makefile with the seen id   	 gopath  nowhere go build  tags guest  buildmode plugin  ldflags   x plugin unnamed   guestdummy dummyguest   o guest so guest go  	 nm guest so   grep guestdummy  	 echo run  	 echo      	   host  	 echo      	  with custom plugin path  	     	 gopath  nowhere go build  tags guest  buildmode plugin  ldflags   pluginpath custompluginpath  x custompluginpath guestdummy dummyguest   o guest so guest go  	 nm guest so   grep guestdummy  	 echo run  	 echo      	   host         if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best           what did you expect to see     i expect to be able to use   ldflags   x importpath guestdummy   to set a build time variable when compiling with   buildmode plugin     as i can do when compiling regular binaries with   ldflags   x main hostdummy          what did you see instead     in the context of plugins  importpath  is variable and depends on the building context  i found that i can have a fixed behavior when using   pluginpath  ldflags  but this flag is not well documented           pluginpath string      	full path name for plugin        can i use it confidently is this context  is this the good pattern to set a build time variable in plugins   ,1
55356,7977941741.0,IssuesEvent,2018-07-17 16:44:55,golang/go,https://api.github.com/repos/golang/go,closed,doc: vet check included in gc needs to be documented,Documentation NeedsFix,"vet check seems to be included in gc by default but not documented in go1.11 release note yet (sorry, I didn't search enough to find related issue/proposal/change to link yet).

This behavior change resulted in build-failures for codes that don't pass vet currently and could be misunderstood as a regression in go1.11. For example, with go1.11 (or tip), go test on 
github.com/spf13/cobra will fail due to failure to pass vet check.

<pre>
$ go version
go version devel +257d6c48e0 Thu Jun 28 03:12:01 2018 +0000 linux/amd64

$  go test github.com/spf13/cobra
# github.com/spf13/cobra
../github.com/spf13/cobra/command_test.go:1105:3: parentPersPreArgs declared but not used
../github.com/spf13/cobra/command_test.go:1109:3: parentPersPostArgs declared but not used
vet: typecheck failures
FAIL	github.com/spf13/cobra [build failed]
</pre>

BTW, the vet error message is confusing because the parentPersPreArgs and parentPersPostArgs in the test are 'used' (literally). But for the purpose of vet check, the vars are 'not used' because they are never read. ",1.0,"doc: vet check included in gc needs to be documented - vet check seems to be included in gc by default but not documented in go1.11 release note yet (sorry, I didn't search enough to find related issue/proposal/change to link yet).

This behavior change resulted in build-failures for codes that don't pass vet currently and could be misunderstood as a regression in go1.11. For example, with go1.11 (or tip), go test on 
github.com/spf13/cobra will fail due to failure to pass vet check.

<pre>
$ go version
go version devel +257d6c48e0 Thu Jun 28 03:12:01 2018 +0000 linux/amd64

$  go test github.com/spf13/cobra
# github.com/spf13/cobra
../github.com/spf13/cobra/command_test.go:1105:3: parentPersPreArgs declared but not used
../github.com/spf13/cobra/command_test.go:1109:3: parentPersPostArgs declared but not used
vet: typecheck failures
FAIL	github.com/spf13/cobra [build failed]
</pre>

BTW, the vet error message is confusing because the parentPersPreArgs and parentPersPostArgs in the test are 'used' (literally). But for the purpose of vet check, the vars are 'not used' because they are never read. ",1,doc  vet check included in gc needs to be documented   vet check seems to be included in gc by default but not documented in     release note yet  sorry  i didn t search enough to find related issue proposal change to link yet      this behavior change resulted in build failures for codes that don t pass vet currently and could be misunderstood as a regression in      for example  with      or tip   go test on   github com   cobra will fail due to failure to pass vet check          go version  go version devel    thu jun              linux         go test github com   cobra    github com   cobra     github com   cobra command test go      parentperspreargs declared but not used     github com   cobra command test go      parentperspostargs declared but not used  vet  typecheck failures  fail	github com   cobra         btw  the vet error message is confusing because the parentperspreargs and parentperspostargs in the test are  used   literally   but for the purpose of vet check  the vars are  not used  because they are never read  ,1
49808,6040916052.0,IssuesEvent,2017-06-10 18:51:38,kubernetes/kubernetes,https://api.github.com/repos/kubernetes/kubernetes,closed,E2E_PUBLISH_GREEN_VERSION should use same logic as other version uploaders,area/test area/test-infra priority/backlog sig/testing stale,"This is follow-on work to #14959 and #15422.
",3.0,"E2E_PUBLISH_GREEN_VERSION should use same logic as other version uploaders - This is follow-on work to #14959 and #15422.
",0,  publish green version should use same logic as other version uploaders   this is follow on work to    and     ,0
428102,29927642150.0,IssuesEvent,2023-06-22 07:10:16,golang/go,https://api.github.com/repos/golang/go,closed,x/website: Random greeting tutorial docs outdated,Documentation website,"This commit: https://github.com/golang/website/commit/f734127 removes some code from the tutorial, but  fails to remove the explanation for that code: https://github.com/golang/website/blob/cf517d8748f3d07b8a57fbee59d056c25b447bef/_content/doc/tutorial/random-greeting.html#L94-L100",1.0,"x/website: Random greeting tutorial docs outdated - This commit: https://github.com/golang/website/commit/f734127 removes some code from the tutorial, but  fails to remove the explanation for that code: https://github.com/golang/website/blob/cf517d8748f3d07b8a57fbee59d056c25b447bef/_content/doc/tutorial/random-greeting.html#L94-L100",1,x website  random greeting tutorial docs outdated   this commit    removes some code from the tutorial  but  fails to remove the explanation for that code   ,1
433791,30350190944.0,IssuesEvent,2023-07-11 18:20:01,golang/go,https://api.github.com/repos/golang/go,closed,runtime: Race detector causes exit status 0xc0000139 on Windows 11 with 1.21rc2 running gcc 9.2.0,Documentation OS-Windows NeedsDecision release-blocker compiler/runtime,"<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.21rc2 windows/amd64
</pre>

### Does this issue reproduce with the latest release?
Reproducible with 1.21rc2 but not reproducible with 1.20.5. I'm not sure how to download 1.21rc1 to test that.

### What operating system and processor architecture are you using (`go env`)?

Windows 11 Pro Version 10.0.22621 Build 22621

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\james\AppData\Local\go-build
set GOENV=C:\Users\james\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\james\go\pkg\mod
set GONOPROXY=gerrit.levenlabs.com,gitlab.com/levenlabs
set GONOSUMDB=gerrit.levenlabs.com,gitlab.com/levenlabs
set GOOS=windows
set GOPATH=C:\Users\james\go;
set GOPRIVATE=gerrit.levenlabs.com,gitlab.com/levenlabs
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=C:\Program Files\Go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLCHAIN=auto
set GOTOOLDIR=C:\Program Files\Go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.21rc2
set GCCGO=gccgo
set GOAMD64=v1
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=C:\Users\james\Dropbox\aftermath\backend\go-llib\go.mod
set GOWORK=
set CGO_CFLAGS=-O2 -g
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-O2 -g
set CGO_FFLAGS=-O2 -g
set CGO_LDFLAGS=-O2 -g
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=C:\Users\james\AppData\Local\Temp\go-build2611928154=/tmp/go-build -gno-record-gcc-switches
</pre></details>

I had previously installed tdm-gcc 9.2.0 which causes the error:
<details><summary><code>gcc -v</code> Output</summary><br><pre>
> gcc -v
Using built-in specs.
COLLECT_GCC=C:\TDM-GCC-64\bin\gcc.exe
COLLECT_LTO_WRAPPER=C:/TDM-GCC-64/bin/../libexec/gcc/x86_64-w64-mingw32/9.2.0/lto-wrapper.exe
Target: x86_64-w64-mingw32
Configured with: ../../../src/gcc-git-9.2.0/configure --build=x86_64-w64-mingw32 --enable-targets=all --enable-languages=ada,c,c++,fortran,lto,objc,obj-c++ --enable-libgomp --enable-lto --enable-graphite --enable-cxx-flags=-DWINPTHREAD_STATIC --disable-build-with-cxx --disable-build-poststage1-with-cxx --enable-libstdcxx-debug --enable-threads=posix --enable-version-specific-runtime-libs --enable-fully-dynamic-string --enable-libstdcxx-threads --enable-libstdcxx-time --with-gnu-ld --disable-werror --disable-nls --disable-win32-registry --enable-large-address-aware --disable-rpath --disable-symvers --prefix=/mingw64tdm --with-local-prefix=/mingw64tdm --with-pkgversion=tdm64-1 --with-bugurl=http://tdm-gcc.tdragon.net/bugs
Thread model: posix
gcc version 9.2.0 (tdm64-1) 
</pre></details>

But upon upgrading to tdm-gcc 10.3.0 the error no longer occurs:
<details><summary><code>gcc -v</code> Output</summary><br><pre>
> gcc -v
Using built-in specs.
COLLECT_GCC=C:\TDM-GCC-64\bin\gcc.exe
COLLECT_LTO_WRAPPER=C:/TDM-GCC-64/bin/../libexec/gcc/x86_64-w64-mingw32/10.3.0/lto-wrapper.exe
Target: x86_64-w64-mingw32
Configured with: ../../../src/gcc-git-10.3.0/configure --build=x86_64-w64-mingw32 --enable-targets=all --enable-languages=ada,c,c++,fortran,jit,lto,objc,obj-c++ --enable-libgomp --enable-lto --enable-graphite --enable-cxx-flags=-DWINPTHREAD_STATIC --disable-build-with-cxx --disable-build-poststage1-with-cxx --enable-libstdcxx-debug --enable-threads=posix --enable-version-specific-runtime-libs --enable-fully-dynamic-string --enable-libstdcxx-filesystem-ts=yes --disable-libstdcxx-pch --enable-libstdcxx-threads --enable-libstdcxx-time=yes --enable-mingw-wildcard --with-gnu-ld --disable-werror --enable-nls --disable-win32-registry --enable-large-address-aware --disable-rpath --disable-symvers --prefix=/mingw64tdm --with-local-prefix=/mingw64tdm --with-pkgversion=tdm64-1 --with-bugurl=https://github.com/jmeubank/tdm-gcc/issues
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 10.3.0 (tdm64-1)
</pre></details>

### What did you do?
Trying to run any tests with `-race` and gcc 9.2.0 ends up failing with `exit status 0xc0000139`.
https://go.dev/play/p/RFjBrSPywGg

```
> go.exe test ./... -v -race
exit status 0xc0000139
```
```
> go.exe test ./... -v
=== RUN   TestAdd
--- PASS: TestAdd (0.00s)
PASS
```

But upon upgrading to gcc 10.3.0:
```
> go.exe test ./... -v -race
=== RUN   TestAdd
--- PASS: TestAdd (0.00s)
PASS
```

### What did you expect to see?
I expected for the race detector not to break between versions without something in the release notes pointing out an expectation of breakage. All I noticed in the release notes for 1.21 that might be related is:
> On Windows AMD64, the linker (with help from the compiler) now emits SEH unwinding data by default, which improves the integration of Go applications with Windows debuggers and other tools.

But it's not obvious that this would require an upgraded gcc. It wasn't until after several hours of Googling and debugging that I ended up attempting to update gcc.

### What did you see instead?
Instead I saw a bizarre exit status that led me down a deep rabbit hole on Google to try and figure out why my go tests suddenly don't work.

",1.0,"runtime: Race detector causes exit status 0xc0000139 on Windows 11 with 1.21rc2 running gcc 9.2.0 - <!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.21rc2 windows/amd64
</pre>

### Does this issue reproduce with the latest release?
Reproducible with 1.21rc2 but not reproducible with 1.20.5. I'm not sure how to download 1.21rc1 to test that.

### What operating system and processor architecture are you using (`go env`)?

Windows 11 Pro Version 10.0.22621 Build 22621

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\james\AppData\Local\go-build
set GOENV=C:\Users\james\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\james\go\pkg\mod
set GONOPROXY=gerrit.levenlabs.com,gitlab.com/levenlabs
set GONOSUMDB=gerrit.levenlabs.com,gitlab.com/levenlabs
set GOOS=windows
set GOPATH=C:\Users\james\go;
set GOPRIVATE=gerrit.levenlabs.com,gitlab.com/levenlabs
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=C:\Program Files\Go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLCHAIN=auto
set GOTOOLDIR=C:\Program Files\Go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.21rc2
set GCCGO=gccgo
set GOAMD64=v1
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=C:\Users\james\Dropbox\aftermath\backend\go-llib\go.mod
set GOWORK=
set CGO_CFLAGS=-O2 -g
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-O2 -g
set CGO_FFLAGS=-O2 -g
set CGO_LDFLAGS=-O2 -g
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=C:\Users\james\AppData\Local\Temp\go-build2611928154=/tmp/go-build -gno-record-gcc-switches
</pre></details>

I had previously installed tdm-gcc 9.2.0 which causes the error:
<details><summary><code>gcc -v</code> Output</summary><br><pre>
> gcc -v
Using built-in specs.
COLLECT_GCC=C:\TDM-GCC-64\bin\gcc.exe
COLLECT_LTO_WRAPPER=C:/TDM-GCC-64/bin/../libexec/gcc/x86_64-w64-mingw32/9.2.0/lto-wrapper.exe
Target: x86_64-w64-mingw32
Configured with: ../../../src/gcc-git-9.2.0/configure --build=x86_64-w64-mingw32 --enable-targets=all --enable-languages=ada,c,c++,fortran,lto,objc,obj-c++ --enable-libgomp --enable-lto --enable-graphite --enable-cxx-flags=-DWINPTHREAD_STATIC --disable-build-with-cxx --disable-build-poststage1-with-cxx --enable-libstdcxx-debug --enable-threads=posix --enable-version-specific-runtime-libs --enable-fully-dynamic-string --enable-libstdcxx-threads --enable-libstdcxx-time --with-gnu-ld --disable-werror --disable-nls --disable-win32-registry --enable-large-address-aware --disable-rpath --disable-symvers --prefix=/mingw64tdm --with-local-prefix=/mingw64tdm --with-pkgversion=tdm64-1 --with-bugurl=http://tdm-gcc.tdragon.net/bugs
Thread model: posix
gcc version 9.2.0 (tdm64-1) 
</pre></details>

But upon upgrading to tdm-gcc 10.3.0 the error no longer occurs:
<details><summary><code>gcc -v</code> Output</summary><br><pre>
> gcc -v
Using built-in specs.
COLLECT_GCC=C:\TDM-GCC-64\bin\gcc.exe
COLLECT_LTO_WRAPPER=C:/TDM-GCC-64/bin/../libexec/gcc/x86_64-w64-mingw32/10.3.0/lto-wrapper.exe
Target: x86_64-w64-mingw32
Configured with: ../../../src/gcc-git-10.3.0/configure --build=x86_64-w64-mingw32 --enable-targets=all --enable-languages=ada,c,c++,fortran,jit,lto,objc,obj-c++ --enable-libgomp --enable-lto --enable-graphite --enable-cxx-flags=-DWINPTHREAD_STATIC --disable-build-with-cxx --disable-build-poststage1-with-cxx --enable-libstdcxx-debug --enable-threads=posix --enable-version-specific-runtime-libs --enable-fully-dynamic-string --enable-libstdcxx-filesystem-ts=yes --disable-libstdcxx-pch --enable-libstdcxx-threads --enable-libstdcxx-time=yes --enable-mingw-wildcard --with-gnu-ld --disable-werror --enable-nls --disable-win32-registry --enable-large-address-aware --disable-rpath --disable-symvers --prefix=/mingw64tdm --with-local-prefix=/mingw64tdm --with-pkgversion=tdm64-1 --with-bugurl=https://github.com/jmeubank/tdm-gcc/issues
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 10.3.0 (tdm64-1)
</pre></details>

### What did you do?
Trying to run any tests with `-race` and gcc 9.2.0 ends up failing with `exit status 0xc0000139`.
https://go.dev/play/p/RFjBrSPywGg

```
> go.exe test ./... -v -race
exit status 0xc0000139
```
```
> go.exe test ./... -v
=== RUN   TestAdd
--- PASS: TestAdd (0.00s)
PASS
```

But upon upgrading to gcc 10.3.0:
```
> go.exe test ./... -v -race
=== RUN   TestAdd
--- PASS: TestAdd (0.00s)
PASS
```

### What did you expect to see?
I expected for the race detector not to break between versions without something in the release notes pointing out an expectation of breakage. All I noticed in the release notes for 1.21 that might be related is:
> On Windows AMD64, the linker (with help from the compiler) now emits SEH unwinding data by default, which improves the integration of Go applications with Windows debuggers and other tools.

But it's not obvious that this would require an upgraded gcc. It wasn't until after several hours of Googling and debugging that I ended up attempting to update gcc.

### What did you see instead?
Instead I saw a bizarre exit status that led me down a deep rabbit hole on Google to try and figure out why my go tests suddenly don't work.

",1,runtime  race detector causes exit status   on windows   with     running gcc               please answer these questions before submitting your issue  thanks              what version of go are you using   go version            go version  go version     windows             does this issue reproduce with the latest release   reproducible with     but not reproducible with        i m not sure how to download     to test that         what operating system and processor architecture are you using   go env       windows   pro version       build         go env  output       go env  set     set goarch    set gobin   set gocache c  users james appdata local go build  set goenv c  users james appdata roaming go env  set goexe  exe  set goexperiment   set goflags   set gohostarch    set gohostos windows  set goinsecure   set gomodcache c  users james go pkg mod  set gonoproxy gerrit levenlabs com gitlab com levenlabs  set gonosumdb gerrit levenlabs com gitlab com levenlabs  set goos windows  set gopath c  users james go   set goprivate gerrit levenlabs com gitlab com levenlabs  set goproxy    set goroot c  program files go  set gosumdb sum golang org  set gotmpdir   set gotoolchain auto  set gotooldir c  program files go pkg tool windows    set govcs   set goversion      set gccgo gccgo  set      set ar ar  set cc gcc  set cxx g    set cgo enabled    set gomod c  users james dropbox aftermath backend go llib go mod  set gowork   set cgo cflags     g  set cgo cppflags   set cgo cxxflags     g  set cgo fflags     g  set cgo ldflags     g  set pkg config pkg config  set gogccflags     mthreads  wl   no gc sections  fmessage length    ffile prefix map c  users james appdata local temp go    tmp go build  gno record gcc switches        i had previously installed tdm gcc       which causes the error      gcc  v  output       gcc  v  using built in specs   collect gcc c  tdm gcc   bin gcc exe  collect lto wrapper c  tdm gcc   bin    libexec gcc               lto wrapper exe  target           configured with           src gcc git       configure   build           enable targets all   enable languages ada c c   fortran lto objc obj c     enable libgomp   enable lto   enable graphite   enable cxx flags  dwinpthread static   disable build with cxx   disable build   with cxx   enable libstdcxx debug   enable threads posix   enable version specific runtime libs   enable fully dynamic string   enable libstdcxx threads   enable libstdcxx time   with gnu ld   disable werror   disable nls   disable   registry   enable large address aware   disable rpath   disable symvers   prefix      with local prefix      with pkgversion       with bugurl    thread model  posix  gcc version                     but upon upgrading to tdm gcc       the error no longer occurs      gcc  v  output       gcc  v  using built in specs   collect gcc c  tdm gcc   bin gcc exe  collect lto wrapper c  tdm gcc   bin    libexec gcc               lto wrapper exe  target           configured with           src gcc git       configure   build           enable targets all   enable languages ada c c   fortran jit lto objc obj c     enable libgomp   enable lto   enable graphite   enable cxx flags  dwinpthread static   disable build with cxx   disable build   with cxx   enable libstdcxx debug   enable threads posix   enable version specific runtime libs   enable fully dynamic string   enable libstdcxx filesystem ts yes   disable libstdcxx pch   enable libstdcxx threads   enable libstdcxx time yes   enable mingw wildcard   with gnu ld   disable werror   enable nls   disable   registry   enable large address aware   disable rpath   disable symvers   prefix      with local prefix      with pkgversion       with bugurl    thread model  posix  supported lto compression algorithms  zlib zstd  gcc version                        what did you do   trying to run any tests with   race  and gcc       ends up failing with  exit status                  go exe test        v  race  exit status                go exe test        v      run   testadd      pass  testadd        pass         but upon upgrading to gcc                go exe test        v  race      run   testadd      pass  testadd        pass             what did you expect to see   i expected for the race detector not to break between versions without something in the release notes pointing out an expectation of breakage  all i noticed in the release notes for     that might be related is     on windows    the linker  with help from the compiler  now emits seh unwinding data by default  which improves the integration of go applications with windows debuggers and other tools     but it s not obvious that this would require an upgraded gcc  it wasn t until after several hours of googling and debugging that i ended up attempting to update gcc         what did you see instead   instead i saw a bizarre exit status that led me down a deep rabbit hole on google to try and figure out why my go tests suddenly don t work     ,1
408180,27656655398.0,IssuesEvent,2023-03-12 02:27:00,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: mention `go get` in `go help mod`,Documentation help wanted NeedsFix GoCommand,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.16
</pre>

### Does this issue reproduce with the latest release?
Yes

### What did you do?
I were working with a module using command `go mod`; i expected that i can update dependency with commands:
`go mod update -u <dependency>`
`go mod update <dependency>@commit`

### What did you expect to see?
I expected for this to work. 
I expected for this to show in `go help mod`:
````
Usage:

        go mod <command> [arguments]

The commands are:

        download    download modules to local cache
        edit        edit go.mod from tools or scripts
        graph       print module requirement graph
        init        initialize new module in current directory
        tidy        add missing and remove unused modules
        vendor      make vendored copy of dependencies
        verify      verify dependencies have expected content
        why         explain why packages or modules are needed
````
### What did you see instead?
After asking a question regarding this topic on golang slack channel i received help from `Tim Heckman` that stated:
````
yeah, the choice was made to keep it as go get so all the existing Gophers wouldn't need to relearn the command(s).
````
````
yeah, that was kept for historical purposes... that was how dependencies have always been gotten.
````
He nicely explained to me that i have to use:
````
go get <dependency>@commit
go get -u <dependency>
````
Which for me is confusing - i expected that subcommand to be related to `go mod` but - it's not in the help of that command - while it's clearly related to modules.",1.0,"cmd/go: mention `go get` in `go help mod` - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.16
</pre>

### Does this issue reproduce with the latest release?
Yes

### What did you do?
I were working with a module using command `go mod`; i expected that i can update dependency with commands:
`go mod update -u <dependency>`
`go mod update <dependency>@commit`

### What did you expect to see?
I expected for this to work. 
I expected for this to show in `go help mod`:
````
Usage:

        go mod <command> [arguments]

The commands are:

        download    download modules to local cache
        edit        edit go.mod from tools or scripts
        graph       print module requirement graph
        init        initialize new module in current directory
        tidy        add missing and remove unused modules
        vendor      make vendored copy of dependencies
        verify      verify dependencies have expected content
        why         explain why packages or modules are needed
````
### What did you see instead?
After asking a question regarding this topic on golang slack channel i received help from `Tim Heckman` that stated:
````
yeah, the choice was made to keep it as go get so all the existing Gophers wouldn't need to relearn the command(s).
````
````
yeah, that was kept for historical purposes... that was how dependencies have always been gotten.
````
He nicely explained to me that i have to use:
````
go get <dependency>@commit
go get -u <dependency>
````
Which for me is confusing - i expected that subcommand to be related to `go mod` but - it's not in the help of that command - while it's clearly related to modules.",1,cmd go  mention  go get  in  go help mod          please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version            go version  go version               does this issue reproduce with the latest release   yes        what did you do   i were working with a module using command  go mod   i expected that i can update dependency with commands    go mod update  u      go mod update   commit         what did you expect to see   i expected for this to work    i expected for this to show in  go help mod          usage             go mod        the commands are             download    download modules to local cache          edit        edit go mod from tools or scripts          graph       print module requirement graph          init        initialize new module in current directory          tidy        add missing and remove unused modules          vendor      make vendored copy of dependencies          verify      verify dependencies have expected content          why         explain why packages or modules are needed            what did you see instead   after asking a question regarding this topic on golang slack channel i received help from  tim heckman  that stated         yeah  the choice was made to keep it as go get so all the existing gophers wouldn t need to relearn the command s                yeah  that was kept for historical purposes    that was how dependencies have always been gotten         he nicely explained to me that i have to use         go get   commit  go get  u          which for me is confusing   i expected that subcommand to be related to  go mod  but   it s not in the help of that command   while it s clearly related to modules ,1
18289,4243508895.0,IssuesEvent,2016-07-06 23:23:33,golang/go,https://api.github.com/repos/golang/go,closed,"path/filepath: behavior of Clean is not explicitly mentioned in its doc, which is surprising and easy to miss",Documentation,"_(Usually an issue is when a function does something which is not documented, or different than documented. This is not the case here, but I still believe there is an issue that can and should be resolved, i.e., improvement is possible.)_

One of my favorite properties of Go is that many things are explicit and there's little magic. When you want to learn what a func in standard library does, often just reading its doc string will tell you everything you need to know, without having to look at the implementation details. This is very nice and follows Principle of Least Surprise.

I was trying to confirm the behavior of `filepath.Join`, so I began by reading its doc:

```
// Join joins any number of path elements into a single path, adding
// a Separator if necessary. The result is Cleaned, in particular
// all empty strings are ignored.
// On Windows, the result is a UNC path if and only if the first path
// element is a UNC path.
func Join(elem ...string) string
```

It says that the result is Cleaned, so I read the doc for `Clean`:

```
// Clean returns the shortest path name equivalent to path
// by purely lexical processing.  It applies the following rules
// iteratively until no further processing can be done:
//
//	1. Replace multiple Separator elements with a single one.
//	2. Eliminate each . path name element (the current directory).
//	3. Eliminate each inner .. path name element (the parent directory)
//	   along with the non-.. element that precedes it.
//	4. Eliminate .. elements that begin a rooted path:
//	   that is, replace ""/.."" by ""/"" at the beginning of a path,
//	   assuming Separator is '/'.
//
// The returned path ends in a slash only if it represents a root directory,
// such as ""/"" on Unix or `C:\` on Windows.
//
// If the result of this process is an empty string, Clean
// returns the string ""."".
//
// See also Rob Pike, ``Lexical File Names in Plan 9 or
// Getting Dot-Dot Right,''
// http://plan9.bell-labs.com/sys/doc/lexnames.html
func Clean(path string) string
```

With that, I am confident that I understand the behavior of `filepath.Join` because I've read its documentation.

However, as I have learned today (by chance), my understanding of `filepath.Join`, `filepath.Clean` was incorrect because I overlooked a **very important, behavior altering** paragraph in the package documentation (which is used to describe this package). Read the second paragraph:

```
// Package filepath implements utility routines for manipulating filename paths
// in a way compatible with the target operating system-defined file paths.
//
// Functions in this package replace any occurrences of the slash ('/') character
// with os.PathSeparator when returning paths unless otherwise specified.
package filepath
```

It turns out that `Clean` replaces any occurrences of the slash ('/') character with `os.PathSeparator` when returning path. So does `Join` since it calls `Clean`.

I believe this is the first time I have ever encountered a standard library package where a part of the behavior (which is not the expected behavior for this package) is specified/overridden by package docs.

If I'm not mistaken, I believe it'd be better to change documentation to document `Clean`s behavior explicitly, and change the package documentation to summarize behavior rather than be the only place that specifies it.

### Exaggerated, contrived example

If I may provide an exaggerated, contrived example of how this current situation makes me feel, it would be like seeing a function in std lib like this:

```Go
// Add returns sum of two numbers.
func Add(a, b int) int
```

Then I run `Add(1, 2)` and get -3 instead of 3. Instead of a bug, imagine it turns out that:

```Go
// Package math has some utilities for dealing with numbers.
//
// Functions in this package return the negation of the expected result, unless
// otherwise specified.
package math
```

This issue is the same as https://github.com/golang/go/issues/10122. However, that issue was resolved a year ago, and I hadn't noticed that it was resolved because I primarily read the function documentation when determining behavior of a function. I read the package documentation when I want to get a better overview of the purpose of package, but it's not where I expect to find unexpected behaviors specified.

### Proposed improvement

I propose improving `path/filepath` by changing `Clean` documentation to be explicit about its behavior, and changing the package summary to be more descriptive of the package, rather than being the canonical place where behavior of individual functions is altered or specified.

E.g., something like this:

![image](https://cloud.githubusercontent.com/assets/1924134/16174123/88bc2c02-356a-11e6-83f4-369710843395.png)

/cc @hyangah since you originally ran into this issue as well (#10122), and worked on the original fix to the doc.",1.0,"path/filepath: behavior of Clean is not explicitly mentioned in its doc, which is surprising and easy to miss - _(Usually an issue is when a function does something which is not documented, or different than documented. This is not the case here, but I still believe there is an issue that can and should be resolved, i.e., improvement is possible.)_

One of my favorite properties of Go is that many things are explicit and there's little magic. When you want to learn what a func in standard library does, often just reading its doc string will tell you everything you need to know, without having to look at the implementation details. This is very nice and follows Principle of Least Surprise.

I was trying to confirm the behavior of `filepath.Join`, so I began by reading its doc:

```
// Join joins any number of path elements into a single path, adding
// a Separator if necessary. The result is Cleaned, in particular
// all empty strings are ignored.
// On Windows, the result is a UNC path if and only if the first path
// element is a UNC path.
func Join(elem ...string) string
```

It says that the result is Cleaned, so I read the doc for `Clean`:

```
// Clean returns the shortest path name equivalent to path
// by purely lexical processing.  It applies the following rules
// iteratively until no further processing can be done:
//
//	1. Replace multiple Separator elements with a single one.
//	2. Eliminate each . path name element (the current directory).
//	3. Eliminate each inner .. path name element (the parent directory)
//	   along with the non-.. element that precedes it.
//	4. Eliminate .. elements that begin a rooted path:
//	   that is, replace ""/.."" by ""/"" at the beginning of a path,
//	   assuming Separator is '/'.
//
// The returned path ends in a slash only if it represents a root directory,
// such as ""/"" on Unix or `C:\` on Windows.
//
// If the result of this process is an empty string, Clean
// returns the string ""."".
//
// See also Rob Pike, ``Lexical File Names in Plan 9 or
// Getting Dot-Dot Right,''
// http://plan9.bell-labs.com/sys/doc/lexnames.html
func Clean(path string) string
```

With that, I am confident that I understand the behavior of `filepath.Join` because I've read its documentation.

However, as I have learned today (by chance), my understanding of `filepath.Join`, `filepath.Clean` was incorrect because I overlooked a **very important, behavior altering** paragraph in the package documentation (which is used to describe this package). Read the second paragraph:

```
// Package filepath implements utility routines for manipulating filename paths
// in a way compatible with the target operating system-defined file paths.
//
// Functions in this package replace any occurrences of the slash ('/') character
// with os.PathSeparator when returning paths unless otherwise specified.
package filepath
```

It turns out that `Clean` replaces any occurrences of the slash ('/') character with `os.PathSeparator` when returning path. So does `Join` since it calls `Clean`.

I believe this is the first time I have ever encountered a standard library package where a part of the behavior (which is not the expected behavior for this package) is specified/overridden by package docs.

If I'm not mistaken, I believe it'd be better to change documentation to document `Clean`s behavior explicitly, and change the package documentation to summarize behavior rather than be the only place that specifies it.

### Exaggerated, contrived example

If I may provide an exaggerated, contrived example of how this current situation makes me feel, it would be like seeing a function in std lib like this:

```Go
// Add returns sum of two numbers.
func Add(a, b int) int
```

Then I run `Add(1, 2)` and get -3 instead of 3. Instead of a bug, imagine it turns out that:

```Go
// Package math has some utilities for dealing with numbers.
//
// Functions in this package return the negation of the expected result, unless
// otherwise specified.
package math
```

This issue is the same as https://github.com/golang/go/issues/10122. However, that issue was resolved a year ago, and I hadn't noticed that it was resolved because I primarily read the function documentation when determining behavior of a function. I read the package documentation when I want to get a better overview of the purpose of package, but it's not where I expect to find unexpected behaviors specified.

### Proposed improvement

I propose improving `path/filepath` by changing `Clean` documentation to be explicit about its behavior, and changing the package summary to be more descriptive of the package, rather than being the canonical place where behavior of individual functions is altered or specified.

E.g., something like this:

![image](https://cloud.githubusercontent.com/assets/1924134/16174123/88bc2c02-356a-11e6-83f4-369710843395.png)

/cc @hyangah since you originally ran into this issue as well (#10122), and worked on the original fix to the doc.",1,path filepath  behavior of clean is not explicitly mentioned in its doc  which is surprising and easy to miss     usually an issue is when a function does something which is not documented  or different than documented  this is not the case here  but i still believe there is an issue that can and should be resolved  i e   improvement is possible       one of my favorite properties of go is that many things are explicit and there s little magic  when you want to learn what a func in standard library does  often just reading its doc string will tell you everything you need to know  without having to look at the implementation details  this is very nice and follows principle of least surprise     i was trying to confirm the behavior of  filepath join   so i began by reading its doc             join joins any number of path elements into a single path  adding     a separator if necessary  the result is cleaned  in particular     all empty strings are ignored      on windows  the result is a unc path if and only if the first path     element is a unc path   func join elem    string  string         it says that the result is cleaned  so i read the doc for  clean              clean returns the shortest path name equivalent to path     by purely lexical processing   it applies the following rules     iteratively until no further processing can be done         	   replace multiple separator elements with a single one     	   eliminate each   path name element  the current directory      	   eliminate each inner    path name element  the parent directory     	   along with the non    element that precedes it     	   eliminate    elements that begin a rooted path     	   that is  replace       by     at the beginning of a path     	   assuming separator is              the returned path ends in a slash only if it represents a root directory      such as     on unix or  c    on windows          if the result of this process is an empty string  clean     returns the string              see also rob pike    lexical file names in plan   or     getting dot dot right           func clean path string  string         with that  i am confident that i understand the behavior of  filepath join  because i ve read its documentation     however  as i have learned today  by chance   my understanding of  filepath join    filepath clean  was incorrect because i overlooked a   very important  behavior altering   paragraph in the package documentation  which is used to describe this package   read the second paragraph             package filepath implements utility routines for manipulating filename paths     in a way compatible with the target operating system defined file paths          functions in this package replace any occurrences of the slash       character     with os pathseparator when returning paths unless otherwise specified   package filepath         it turns out that  clean  replaces any occurrences of the slash       character with  os pathseparator  when returning path  so does  join  since it calls  clean      i believe this is the first time i have ever encountered a standard library package where a part of the behavior  which is not the expected behavior for this package  is specified overridden by package docs     if i m not mistaken  i believe it d be better to change documentation to document  clean s behavior explicitly  and change the package documentation to summarize behavior rather than be the only place that specifies it         exaggerated  contrived example    if i may provide an exaggerated  contrived example of how this current situation makes me feel  it would be like seeing a function in std lib like this        go     add returns sum of two numbers   func add a  b int  int         then i run  add        and get    instead of    instead of a bug  imagine it turns out that        go     package math has some utilities for dealing with numbers          functions in this package return the negation of the expected result  unless     otherwise specified   package math         this issue is the same as   however  that issue was resolved a year ago  and i hadn t noticed that it was resolved because i primarily read the function documentation when determining behavior of a function  i read the package documentation when i want to get a better overview of the purpose of package  but it s not where i expect to find unexpected behaviors specified         proposed improvement    i propose improving  path filepath  by changing  clean  documentation to be explicit about its behavior  and changing the package summary to be more descriptive of the package  rather than being the canonical place where behavior of individual functions is altered or specified     e g   something like this              cc  hyangah since you originally ran into this issue as well       and worked on the original fix to the doc ,1
3737,2783007638.0,IssuesEvent,2015-05-06 21:00:15,golang/go,https://api.github.com/repos/golang/go,closed,testing: (*testing.Benchmark).Log always logs,Documentation,"With this benchmark:

package main
import ""testing""
func BenchmarkLog(b *testing.B) {
	b.Log(""why?"")
}

I get this output:

$ go test -bench .
testing: warning: no tests to run
PASS
BenchmarkLog	2000000000	         0.00 ns/op
--- BENCH: BenchmarkLog
	issue_test.go:6: why?
	issue_test.go:6: why?
	issue_test.go:6: why?
	issue_test.go:6: why?
	issue_test.go:6: why?
	issue_test.go:6: why?

The docs say, ""The text will be printed only if the test fails or the -test.v flag is set.""

Why is b.Log logging anyway?",1.0,"testing: (*testing.Benchmark).Log always logs - With this benchmark:

package main
import ""testing""
func BenchmarkLog(b *testing.B) {
	b.Log(""why?"")
}

I get this output:

$ go test -bench .
testing: warning: no tests to run
PASS
BenchmarkLog	2000000000	         0.00 ns/op
--- BENCH: BenchmarkLog
	issue_test.go:6: why?
	issue_test.go:6: why?
	issue_test.go:6: why?
	issue_test.go:6: why?
	issue_test.go:6: why?
	issue_test.go:6: why?

The docs say, ""The text will be printed only if the test fails or the -test.v flag is set.""

Why is b.Log logging anyway?",1,testing    testing benchmark  log always logs   with this benchmark     package main  import  testing   func benchmarklog b  testing b     	b log  why          i get this output       go test  bench    testing  warning  no tests to run  pass  benchmarklog	 	             ns op      bench  benchmarklog  	issue test go    why   	issue test go    why   	issue test go    why   	issue test go    why   	issue test go    why   	issue test go    why     the docs say   the text will be printed only if the test fails or the  test v flag is set      why is b log logging anyway ,1
218919,7332795269.0,IssuesEvent,2018-03-05 17:19:35,cloudreach/sceptre,https://api.github.com/repos/cloudreach/sceptre,closed,Estimate Template Cost Functionality ,has pr low priority,"I'd like Sceptre to add the ability to provide estimated costs for a stack/template 

https://docs.aws.amazon.com/cli/latest/reference/cloudformation/estimate-template-cost.html

Step 1: 
Just provide the Simple Monthly Calculator URL that is returned.
Step 2: 
Scrape the value and provide the total cost directly, this could be useful when programmatically making decisions about when to launch a template/stack.

Bonus:
It would also be great to estimate the cost for an environment. ",1.0,"Estimate Template Cost Functionality  - I'd like Sceptre to add the ability to provide estimated costs for a stack/template 

https://docs.aws.amazon.com/cli/latest/reference/cloudformation/estimate-template-cost.html

Step 1: 
Just provide the Simple Monthly Calculator URL that is returned.
Step 2: 
Scrape the value and provide the total cost directly, this could be useful when programmatically making decisions about when to launch a template/stack.

Bonus:
It would also be great to estimate the cost for an environment. ",0,estimate template cost functionality    i d like sceptre to add the ability to provide estimated costs for a stack template          step      just provide the simple monthly calculator url that is returned   step      scrape the value and provide the total cost directly  this could be useful when programmatically making decisions about when to launch a template stack     bonus   it would also be great to estimate the cost for an environment  ,0
477117,13755982366.0,IssuesEvent,2020-10-06 19:12:58,kata-containers/runtime,https://api.github.com/repos/kata-containers/runtime,closed,persist: refactor the HypervisorState struct for better readability,enhancement medium-priority,"The `HypervisorState` struct from `virtcontainers/persist/api/hypervisor.go` can be improved in a few ways for better readability:
* Adjust comments to reflect support of cloud-hypervisor
* Re-arrange the struct members to reflect dependency on different types of hypervisor.
   * We may need to discuss whether we can and should split hypervisor-specific members into different structs.

",1.0,"persist: refactor the HypervisorState struct for better readability - The `HypervisorState` struct from `virtcontainers/persist/api/hypervisor.go` can be improved in a few ways for better readability:
* Adjust comments to reflect support of cloud-hypervisor
* Re-arrange the struct members to reflect dependency on different types of hypervisor.
   * We may need to discuss whether we can and should split hypervisor-specific members into different structs.

",0,persist  refactor the hypervisorstate struct for better readability   the  hypervisorstate  struct from  virtcontainers persist api hypervisor go  can be improved in a few ways for better readability     adjust comments to reflect support of cloud hypervisor    re arrange the struct members to reflect dependency on different types of hypervisor        we may need to discuss whether we can and should split hypervisor specific members into different structs     ,0
27933,5412545052.0,IssuesEvent,2017-03-01 14:48:45,golang/go,https://api.github.com/repos/golang/go,closed,os: document how to open a file for appending,Documentation,"It would be nice if the examples called this out, since it's not trivial to get the flags/modes right.",1.0,"os: document how to open a file for appending - It would be nice if the examples called this out, since it's not trivial to get the flags/modes right.",1,os  document how to open a file for appending   it would be nice if the examples called this out  since it s not trivial to get the flags modes right ,1
11047,3454733006.0,IssuesEvent,2015-12-17 17:03:23,golang/go,https://api.github.com/repos/golang/go,closed,"net/http: ServeMux also eliminates repeating ""/""",Documentation,"Just a documentation issue that - `http.ServeMux` (cleanPath) gets also rid of duplicate `/`-s. `http.ServeMux` already contains:

> ServeMux also takes care of sanitizing the URL request path, redirecting any request containing . or .. elements to an equivalent .- and ..-free URL.

I'm not sure how to reword it nicely to include the case of empty path segments, hence I didn't make a CL. Here's shortest example:
```
package main
import (""fmt""; ""net/http"")
func main() {
	http.HandleFunc(""/"", func(w http.ResponseWriter, r *http.Request) {
		fmt.Fprintf(w, ""%s"", r.URL.Path)
	})
	http.ListenAndServe("":8001"", nil)
}
```

`/hello////world` will redirect to `/hello/world`. From URI standpoint they are different and both valid (https://tools.ietf.org/html/rfc3986#section-3.3).",1.0,"net/http: ServeMux also eliminates repeating ""/"" - Just a documentation issue that - `http.ServeMux` (cleanPath) gets also rid of duplicate `/`-s. `http.ServeMux` already contains:

> ServeMux also takes care of sanitizing the URL request path, redirecting any request containing . or .. elements to an equivalent .- and ..-free URL.

I'm not sure how to reword it nicely to include the case of empty path segments, hence I didn't make a CL. Here's shortest example:
```
package main
import (""fmt""; ""net/http"")
func main() {
	http.HandleFunc(""/"", func(w http.ResponseWriter, r *http.Request) {
		fmt.Fprintf(w, ""%s"", r.URL.Path)
	})
	http.ListenAndServe("":8001"", nil)
}
```

`/hello////world` will redirect to `/hello/world`. From URI standpoint they are different and both valid (https://tools.ietf.org/html/rfc3986#section-3.3).",1,net http  servemux also eliminates repeating       just a documentation issue that    http servemux   cleanpath  gets also rid of duplicate     s   http servemux  already contains       servemux also takes care of sanitizing the url request path  redirecting any request containing   or    elements to an equivalent    and    free url     i m not sure how to reword it nicely to include the case of empty path segments  hence i didn t make a cl  here s shortest example        package main  import   fmt    net http    func main      	http handlefunc      func w http responsewriter  r  http request     		fmt fprintf w    s   r url path   	    	http listenandserve       nil               hello    world  will redirect to   hello world   from uri standpoint they are different and both valid   ,1
52639,7778063040.0,IssuesEvent,2018-06-05 13:13:03,golang/go,https://api.github.com/repos/golang/go,closed,"doc: non-standard ""usage"" in flag package",Documentation NeedsFix help wanted,"flag is the only non-main package in the standard library whose documentation begins with:

> Usage:",1.0,"doc: non-standard ""usage"" in flag package - flag is the only non-main package in the standard library whose documentation begins with:

> Usage:",1,doc  non standard  usage  in flag package   flag is the only non main package in the standard library whose documentation begins with       usage ,1
111662,9537666598.0,IssuesEvent,2019-04-30 13:06:14,sebastianbergmann/phpunit,https://api.github.com/repos/sebastianbergmann/phpunit,closed,.phpunit.result.cache file is all over the place,Test Runner bug,"| Q                   | A
| --------------------| ---------------
| PHPUnit version     | 8,1,0
| PHP version         | 7.2.8
| Installation Method | PHAR

Cache is enabled by default, which is not a bad thing. However, by running unit tests, `.phpunit.result.cache` file is being generated in each folder where the test is run. When running tests from the root of the project - that's not a big issue, since one file is generated in the root directory of the project. However, IDEs have integrations for unit tests where you can run a single test method or a class ""on click"". That translates to having multiple `.phpunit.result.cache` files all over the directory structure - in each directory where a test is run.

The solution is obvious - have a single location where the cache file is placed by default and prevent cache clutter in project's directory structure.

",1.0,".phpunit.result.cache file is all over the place - | Q                   | A
| --------------------| ---------------
| PHPUnit version     | 8,1,0
| PHP version         | 7.2.8
| Installation Method | PHAR

Cache is enabled by default, which is not a bad thing. However, by running unit tests, `.phpunit.result.cache` file is being generated in each folder where the test is run. When running tests from the root of the project - that's not a big issue, since one file is generated in the root directory of the project. However, IDEs have integrations for unit tests where you can run a single test method or a class ""on click"". That translates to having multiple `.phpunit.result.cache` files all over the directory structure - in each directory where a test is run.

The solution is obvious - have a single location where the cache file is placed by default and prevent cache clutter in project's directory structure.

",0, phpunit result cache file is all over the place     q                     a                                             phpunit version                php version                    installation method   phar    cache is enabled by default  which is not a bad thing  however  by running unit tests    phpunit result cache  file is being generated in each folder where the test is run  when running tests from the root of the project   that s not a big issue  since one file is generated in the root directory of the project  however  ides have integrations for unit tests where you can run a single test method or a class  on click   that translates to having multiple   phpunit result cache  files all over the directory structure   in each directory where a test is run     the solution is obvious   have a single location where the cache file is placed by default and prevent cache clutter in project s directory structure     ,0
72506,9595901689.0,IssuesEvent,2019-05-09 17:12:21,golang/go,https://api.github.com/repos/golang/go,closed,vendor: no docs on how to update a module in std,Documentation NeedsFix modules release-blocker,"I've been flailing around all morning fighting the new system of updating modules in std.

I want to update x/net in std because the golang.org/x/net/http/httpproxy we have in std is old and doesn't support `ALL_PROXY`.

Note that all_proxy is present in golang.org/x/net:

```
bradfitz@go:~/src/golang.org/x/net$ git show-ref HEAD
9ce7a6920f093fc0b908c4a5f66ae049110f417e refs/remotes/origin/HEAD
bradfitz@go:~/src/golang.org/x/net$ git grep -i all_proxy
proxy/proxy.go:         names: []string{""ALL_PROXY"", ""all_proxy""},
proxy/proxy_test.go:            fmt.Fprintf(&buf, ""all_proxy=%q"", t.allProxyEnv)
proxy/proxy_test.go:            os.Setenv(""ALL_PROXY"", tt.allProxyEnv)
```

But it's not present in std:

```
bradfitz@go:~$ cd $GOROOT/src/
bradfitz@go:~/go/src$ git grep -i all_proxy
```

So, let's update it...

```
bradfitz@go:~/go/src$ go get -u golang.org/x/net/...@latest
go: finding golang.org/x/net latest
go: finding golang.org/x/sys latest
go: finding golang.org/x/crypto latest
bradfitz@go:~/go/src$ git diff go.mod                                                                                                                                                                       diff --git a/src/go.mod b/src/go.mod
index a527f9a244..047e43f864 100644
--- a/src/go.mod
+++ b/src/go.mod
@@ -3,9 +3,9 @@ module std
 go 1.12
 
 require (
-       golang.org/x/crypto v0.0.0-20190424203555-c05e17bb3b2d
-       golang.org/x/net v0.0.0-20190424112056-4829fb13d2c6
-       golang.org/x/sys v0.0.0-20190425145619-16072639606e // indirect
+       golang.org/x/crypto v0.0.0-20190426145343-a29dc8fdc734
+       golang.org/x/net v0.0.0-20190501004415-9ce7a6920f09
+       golang.org/x/sys v0.0.0-20190502145724-3ef323f4f1fd // indirect
        golang.org/x/text v0.3.2 // indirect
-       golang.org/x/tools v0.0.0-20190425214124-2d660fb8a000 // indirect
+       golang.org/x/tools v0.0.0-20190501045030-23463209683d // indirect
 )
```

And `go mod vendor` perhaps?

```
bradfitz@go:~/go/src$ go mod vendor
bradfitz@go:~/go/src$ git grep -i all_proxy
```

Nope. Still not present.

What changed?

```
bradfitz@go:~/go/src$ git diff --stat
 src/go.mod                                                |   8 ++---
 src/go.sum                                                |   7 ++++
 src/vendor/golang.org/x/sys/unix/mkall.sh                 |  14 +++++---
 src/vendor/golang.org/x/sys/unix/mksysctl_openbsd.pl      | 265 ----------------------------------------------------------------------------------------------------------------------------------------------------
 src/vendor/golang.org/x/sys/unix/sockcmsg_unix.go         |   8 ++---
 src/vendor/golang.org/x/sys/unix/syscall.go               |   1 -
 src/vendor/golang.org/x/sys/unix/zsysctl_openbsd_386.go   |   2 ++
 src/vendor/golang.org/x/sys/unix/zsysctl_openbsd_amd64.go |   2 +-
 src/vendor/golang.org/x/sys/unix/zsysctl_openbsd_arm.go   |   4 ++-
 src/vendor/golang.org/x/sys/unix/zsysctl_openbsd_arm64.go |   2 +-
 src/vendor/modules.txt                                    |  14 ++++----
 11 files changed, 39 insertions(+), 288 deletions(-)
```

... other stuff changed, but not `golang.org/x/net/...`

I tried to get get a specific version rather than ""latest""

```
bradfitz@go:~/go/src$ go get -u golang.org/x/net/http/httpproxy@v0.0.0-20190501004415-9ce7a6920f09
go: finding golang.org/x/net/http/httpproxy v0.0.0-20190501004415-9ce7a6920f09
go: finding golang.org/x/net/http v0.0.0-20190501004415-9ce7a6920f09
bradfitz@go:~/go/src$ go mod vendor
bradfitz@go:~/go/src$ git grep -i all_proxy
bradfitz@go:~/go/src$ git di --stat
 src/go.mod                                                |   8 ++---
 src/go.sum                                                |   7 ++++
 src/vendor/golang.org/x/sys/unix/mkall.sh                 |  14 +++++---
 src/vendor/golang.org/x/sys/unix/mksysctl_openbsd.pl      | 265 ----------------------------------------------------------------------------------------------------------------------------------------------------
 src/vendor/golang.org/x/sys/unix/sockcmsg_unix.go         |   8 ++---
 src/vendor/golang.org/x/sys/unix/syscall.go               |   1 -
 src/vendor/golang.org/x/sys/unix/zsysctl_openbsd_386.go   |   2 ++
 src/vendor/golang.org/x/sys/unix/zsysctl_openbsd_amd64.go |   2 +-
 src/vendor/golang.org/x/sys/unix/zsysctl_openbsd_arm.go   |   4 ++-
 src/vendor/golang.org/x/sys/unix/zsysctl_openbsd_arm64.go |   2 +-
 src/vendor/modules.txt                                    |  14 ++++----
 11 files changed, 39 insertions(+), 288 deletions(-)
```

Still no good.

A README.txt would really help.

Also, what is vendor/modules.txt? What role does it play and is it hand maintained or tool maintained and where is it documented? Does it support comments? Could it have some comments saying what it is?

Please help. (and document)
",1.0,"vendor: no docs on how to update a module in std - I've been flailing around all morning fighting the new system of updating modules in std.

I want to update x/net in std because the golang.org/x/net/http/httpproxy we have in std is old and doesn't support `ALL_PROXY`.

Note that all_proxy is present in golang.org/x/net:

```
bradfitz@go:~/src/golang.org/x/net$ git show-ref HEAD
9ce7a6920f093fc0b908c4a5f66ae049110f417e refs/remotes/origin/HEAD
bradfitz@go:~/src/golang.org/x/net$ git grep -i all_proxy
proxy/proxy.go:         names: []string{""ALL_PROXY"", ""all_proxy""},
proxy/proxy_test.go:            fmt.Fprintf(&buf, ""all_proxy=%q"", t.allProxyEnv)
proxy/proxy_test.go:            os.Setenv(""ALL_PROXY"", tt.allProxyEnv)
```

But it's not present in std:

```
bradfitz@go:~$ cd $GOROOT/src/
bradfitz@go:~/go/src$ git grep -i all_proxy
```

So, let's update it...

```
bradfitz@go:~/go/src$ go get -u golang.org/x/net/...@latest
go: finding golang.org/x/net latest
go: finding golang.org/x/sys latest
go: finding golang.org/x/crypto latest
bradfitz@go:~/go/src$ git diff go.mod                                                                                                                                                                       diff --git a/src/go.mod b/src/go.mod
index a527f9a244..047e43f864 100644
--- a/src/go.mod
+++ b/src/go.mod
@@ -3,9 +3,9 @@ module std
 go 1.12
 
 require (
-       golang.org/x/crypto v0.0.0-20190424203555-c05e17bb3b2d
-       golang.org/x/net v0.0.0-20190424112056-4829fb13d2c6
-       golang.org/x/sys v0.0.0-20190425145619-16072639606e // indirect
+       golang.org/x/crypto v0.0.0-20190426145343-a29dc8fdc734
+       golang.org/x/net v0.0.0-20190501004415-9ce7a6920f09
+       golang.org/x/sys v0.0.0-20190502145724-3ef323f4f1fd // indirect
        golang.org/x/text v0.3.2 // indirect
-       golang.org/x/tools v0.0.0-20190425214124-2d660fb8a000 // indirect
+       golang.org/x/tools v0.0.0-20190501045030-23463209683d // indirect
 )
```

And `go mod vendor` perhaps?

```
bradfitz@go:~/go/src$ go mod vendor
bradfitz@go:~/go/src$ git grep -i all_proxy
```

Nope. Still not present.

What changed?

```
bradfitz@go:~/go/src$ git diff --stat
 src/go.mod                                                |   8 ++---
 src/go.sum                                                |   7 ++++
 src/vendor/golang.org/x/sys/unix/mkall.sh                 |  14 +++++---
 src/vendor/golang.org/x/sys/unix/mksysctl_openbsd.pl      | 265 ----------------------------------------------------------------------------------------------------------------------------------------------------
 src/vendor/golang.org/x/sys/unix/sockcmsg_unix.go         |   8 ++---
 src/vendor/golang.org/x/sys/unix/syscall.go               |   1 -
 src/vendor/golang.org/x/sys/unix/zsysctl_openbsd_386.go   |   2 ++
 src/vendor/golang.org/x/sys/unix/zsysctl_openbsd_amd64.go |   2 +-
 src/vendor/golang.org/x/sys/unix/zsysctl_openbsd_arm.go   |   4 ++-
 src/vendor/golang.org/x/sys/unix/zsysctl_openbsd_arm64.go |   2 +-
 src/vendor/modules.txt                                    |  14 ++++----
 11 files changed, 39 insertions(+), 288 deletions(-)
```

... other stuff changed, but not `golang.org/x/net/...`

I tried to get get a specific version rather than ""latest""

```
bradfitz@go:~/go/src$ go get -u golang.org/x/net/http/httpproxy@v0.0.0-20190501004415-9ce7a6920f09
go: finding golang.org/x/net/http/httpproxy v0.0.0-20190501004415-9ce7a6920f09
go: finding golang.org/x/net/http v0.0.0-20190501004415-9ce7a6920f09
bradfitz@go:~/go/src$ go mod vendor
bradfitz@go:~/go/src$ git grep -i all_proxy
bradfitz@go:~/go/src$ git di --stat
 src/go.mod                                                |   8 ++---
 src/go.sum                                                |   7 ++++
 src/vendor/golang.org/x/sys/unix/mkall.sh                 |  14 +++++---
 src/vendor/golang.org/x/sys/unix/mksysctl_openbsd.pl      | 265 ----------------------------------------------------------------------------------------------------------------------------------------------------
 src/vendor/golang.org/x/sys/unix/sockcmsg_unix.go         |   8 ++---
 src/vendor/golang.org/x/sys/unix/syscall.go               |   1 -
 src/vendor/golang.org/x/sys/unix/zsysctl_openbsd_386.go   |   2 ++
 src/vendor/golang.org/x/sys/unix/zsysctl_openbsd_amd64.go |   2 +-
 src/vendor/golang.org/x/sys/unix/zsysctl_openbsd_arm.go   |   4 ++-
 src/vendor/golang.org/x/sys/unix/zsysctl_openbsd_arm64.go |   2 +-
 src/vendor/modules.txt                                    |  14 ++++----
 11 files changed, 39 insertions(+), 288 deletions(-)
```

Still no good.

A README.txt would really help.

Also, what is vendor/modules.txt? What role does it play and is it hand maintained or tool maintained and where is it documented? Does it support comments? Could it have some comments saying what it is?

Please help. (and document)
",1,vendor  no docs on how to update a module in std   i ve been flailing around all morning fighting the new system of updating modules in std     i want to update x net in std because the golang org x net http httpproxy we have in std is old and doesn t support  all proxy      note that all proxy is present in golang org x net          bradfitz go   src golang org x net  git show ref head    refs remotes origin head  bradfitz go   src golang org x net  git grep  i all proxy  proxy proxy go          names   string  all proxy    all proxy     proxy proxy test go             fmt fprintf  buf   all proxy  q   t allproxyenv   proxy proxy test go             os setenv  all proxy   tt allproxyenv          but it s not present in std          bradfitz go    cd  goroot src   bradfitz go   go src  git grep  i all proxy         so  let s update it            bradfitz go   go src  go get  u golang org x net     latest  go  finding golang org x net latest  go  finding golang org x sys latest  go  finding golang org x crypto latest  bradfitz go   go src  git diff go mod                                                                                                                                                                       diff   git a src go mod b src go mod  index             a src go mod      b src go mod                  module std   go          require            golang org x crypto                    golang org x net                    golang org x sys              indirect          golang org x crypto                    golang org x net                    golang org x sys              indirect          golang org x text          indirect          golang org x tools              indirect          golang org x tools              indirect             and  go mod vendor  perhaps          bradfitz go   go src  go mod vendor  bradfitz go   go src  git grep  i all proxy         nope  still not present     what changed          bradfitz go   go src  git diff   stat   src go mod                                                              src go sum                                                             src vendor golang org x sys unix mkall sh                                 src vendor golang org x sys unix mksysctl openbsd pl                                                                                                                                                                 src vendor golang org x sys unix sockcmsg unix go                       src vendor golang org x sys unix syscall go                         src vendor golang org x sys unix zsysctl openbsd   go              src vendor golang org x sys unix zsysctl openbsd   go            src vendor golang org x sys unix zsysctl openbsd arm go               src vendor golang org x sys unix zsysctl openbsd   go            src vendor modules txt                                                      files changed    insertions       deletions                other stuff changed  but not  golang org x net         i tried to get get a specific version rather than  latest          bradfitz go   go src  go get  u golang org x net http httpproxy            go  finding golang org x net http httpproxy            go  finding golang org x net http            bradfitz go   go src  go mod vendor  bradfitz go   go src  git grep  i all proxy  bradfitz go   go src  git di   stat   src go mod                                                              src go sum                                                             src vendor golang org x sys unix mkall sh                                 src vendor golang org x sys unix mksysctl openbsd pl                                                                                                                                                                 src vendor golang org x sys unix sockcmsg unix go                       src vendor golang org x sys unix syscall go                         src vendor golang org x sys unix zsysctl openbsd   go              src vendor golang org x sys unix zsysctl openbsd   go            src vendor golang org x sys unix zsysctl openbsd arm go               src vendor golang org x sys unix zsysctl openbsd   go            src vendor modules txt                                                      files changed    insertions       deletions            still no good     a readme txt would really help     also  what is vendor modules txt  what role does it play and is it hand maintained or tool maintained and where is it documented  does it support comments  could it have some comments saying what it is     please help   and document   ,1
270091,20573993202.0,IssuesEvent,2022-03-04 01:08:59,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: add proper documentation for workspace mode,Documentation NeedsFix GoCommand,"Add full docs for each of the go work subcommands, a doc for getting started on workspace mode, and a reference-style document.",1.0,"cmd/go: add proper documentation for workspace mode - Add full docs for each of the go work subcommands, a doc for getting started on workspace mode, and a reference-style document.",1,cmd go  add proper documentation for workspace mode   add full docs for each of the go work subcommands  a doc for getting started on workspace mode  and a reference style document ,1
21949,4759722823.0,IssuesEvent,2016-10-24 23:44:23,golang/go,https://api.github.com/repos/golang/go,closed,proposal: freeze more packages,Documentation Proposal,"I'd like to freeze some packages for Go 1.7:

* net/rpc (#16844)
* log/syslog (done in ddc25081d24d62ebf37e737b73b8bad8fd4b50ec)
* testing/quick
* net/smtp (done in 883e128f4571a59842e1156b5ebe25d8420162d9)
* text/tabwriter

I want to place a line at the end of their package docs saying ""This package is frozen. It is retained for compatibility with the Go 1 API promise. See https://golang.org/s/frozen-package for details.""

And then at that URL we can spell out the rules more. (e.g. maybe we'll accept actual bug fixes if they're obviously wrong and don't change buggy behavior that people might depend on)

/cc @adg @rsc @ianlancetaylor ",1.0,"proposal: freeze more packages - I'd like to freeze some packages for Go 1.7:

* net/rpc (#16844)
* log/syslog (done in ddc25081d24d62ebf37e737b73b8bad8fd4b50ec)
* testing/quick
* net/smtp (done in 883e128f4571a59842e1156b5ebe25d8420162d9)
* text/tabwriter

I want to place a line at the end of their package docs saying ""This package is frozen. It is retained for compatibility with the Go 1 API promise. See https://golang.org/s/frozen-package for details.""

And then at that URL we can spell out the rules more. (e.g. maybe we'll accept actual bug fixes if they're obviously wrong and don't change buggy behavior that people might depend on)

/cc @adg @rsc @ianlancetaylor ",1,proposal  freeze more packages   i d like to freeze some packages for go           net rpc         log syslog  done in       testing quick    net smtp  done in       text tabwriter    i want to place a line at the end of their package docs saying  this package is frozen  it is retained for compatibility with the go   api promise  see   for details      and then at that url we can spell out the rules more   e g  maybe we ll accept actual bug fixes if they re obviously wrong and don t change buggy behavior that people might depend on      cc  adg  rsc  ianlancetaylor ,1
539530,15790406856.0,IssuesEvent,2021-04-02 01:22:43,grpc/grpc,https://api.github.com/repos/grpc/grpc,opened,"gRPC Azure hosted service (onfigured to HTTP2). only Grpc.Net.Client.Web can connect, standard client cannot.",kind/question priority/P3,"Azure-hosted Web app with gRPC Service configured to HTTP2.
only Grpc.Net.Client.Web can connect, standard client cannot.

seem Azure is not supporting hosting gRPC? 

the only way around is Service to support gRPC-Web and use gRPC-Web Client. however, that doesn't feel right.",1.0,"gRPC Azure hosted service (onfigured to HTTP2). only Grpc.Net.Client.Web can connect, standard client cannot. - Azure-hosted Web app with gRPC Service configured to HTTP2.
only Grpc.Net.Client.Web can connect, standard client cannot.

seem Azure is not supporting hosting gRPC? 

the only way around is Service to support gRPC-Web and use gRPC-Web Client. however, that doesn't feel right.",0,grpc azure hosted service  onfigured to     only grpc net client web can connect  standard client cannot    azure hosted web app with grpc service configured to     only grpc net client web can connect  standard client cannot     seem azure is not supporting hosting grpc      the only way around is service to support grpc web and use grpc web client  however  that doesn t feel right ,0
6725,5619106894.0,IssuesEvent,2017-04-04 00:05:13,OctopusDeploy/Issues,https://api.github.com/repos/OctopusDeploy/Issues,closed,Reduce delay between steps for deployments with many steps/machines,area/execution area/scale enhancement feature/performance,"We recently removed a significant bottleneck between steps, which was impacting customers with projects containing many steps and/or machines (https://github.com/OctopusDeploy/Issues/issues/2546).

But there is still a significant delay:
http://help.octopusdeploy.com/discussions/problems/44558
http://help.octopusdeploy.com/discussions/problems/45981-slow-deployments

Further investigation is required.
",True,"Reduce delay between steps for deployments with many steps/machines - We recently removed a significant bottleneck between steps, which was impacting customers with projects containing many steps and/or machines (https://github.com/OctopusDeploy/Issues/issues/2546).

But there is still a significant delay:
http://help.octopusdeploy.com/discussions/problems/44558
http://help.octopusdeploy.com/discussions/problems/45981-slow-deployments

Further investigation is required.
",0,reduce delay between steps for deployments with many steps machines   we recently removed a significant bottleneck between steps  which was impacting customers with projects containing many steps and or machines     but there is still a significant delay       further investigation is required  ,0
285190,21486388981.0,IssuesEvent,2022-04-27 00:12:12,golang/go,https://api.github.com/repos/golang/go,closed,time: second precision timezone format not documented,Documentation help wanted NeedsFix,"`go doc time` says:

```
    Numeric time zone offsets format as follows:

        ""-0700""  ±hhmm
        ""-07:00"" ±hh:mm
        ""-07""    ±hh
```

However, timezones with second precision (""-07:00:00"" and ""-070000"") are also supported: https://github.com/golang/go/blob/master/src/time/format.go#L151

Could these be added to the documentation? Took me a while to figure out why my pre-1900 date with LMT timezone parsed correctly.

",1.0,"time: second precision timezone format not documented - `go doc time` says:

```
    Numeric time zone offsets format as follows:

        ""-0700""  ±hhmm
        ""-07:00"" ±hh:mm
        ""-07""    ±hh
```

However, timezones with second precision (""-07:00:00"" and ""-070000"") are also supported: https://github.com/golang/go/blob/master/src/time/format.go#L151

Could these be added to the documentation? Took me a while to figure out why my pre-1900 date with LMT timezone parsed correctly.

",1,time  second precision timezone format not documented    go doc time  says              numeric time zone offsets format as follows                   ±hhmm                 ±hh mm                  ±hh         however  timezones with second precision           and       are also supported       could these be added to the documentation  took me a while to figure out why my pre   date with lmt timezone parsed correctly     ,1
98234,11048750026.0,IssuesEvent,2019-12-09 21:51:31,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: document that go env GOMOD can return /dev/null,Documentation NeedsInvestigation,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version devel +da4d58587e Sat Dec 7 15:57:30 2019 +0000 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/myitcv/.cache/go-build""
GOENV=""/home/myitcv/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/myitcv/gostuff""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/home/myitcv/gos""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/home/myitcv/gos/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build492256999=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

The docs for `GOMOD` state:

```
$ go help environment
...
        GOMOD
                The absolute path to the go.mod of the main module,
                or the empty string if not using modules.
```

For some time I have (incorrectly) been advising people that the way to determine if you are in a module context or not (i.e. modules not off and you are in the context of a `go.mod`) is by testing whether the output from `go env GOMOD` is the empty string or not. 

However this fails when you consider:

```
$ cd $(mktemp -d)
$ GO111MODULE=on go env GOMOD
/dev/null
```

It's also not clear the docs are quite correct when it comes to modules being not off (i.e. auto or on):

```
$ cd $(mktemp -d)
$ go env GOMOD
 
```

(i.e. empty string, but we aren't not using modules, we are in the auto mode. Granted this is a bit less clearly incorrect)

I realise that this way `go env GOMOD` can be used to determine whether modules are off/not off, and whether you are in a module context or not assuming that they are not off. But documenting this a bit more clearly would, I think, help (selfishly me at least).

Because the actual logic for correctly determining that modules are not off _and_ you are in a module context is:

```go
cmd := exec.Command(""go"", ""env"", ""GOMOD"")
out, _ := cmd.CombinedOutput()
gomod := strings.TrimSpace(string(out))
if gomod != """" and gomod != os.DevNull {
   // ....
```

Thoughts?

cc @bcmills @jayconrod 

FYI @mvdan @kortschak ",1.0,"cmd/go: document that go env GOMOD can return /dev/null - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version devel +da4d58587e Sat Dec 7 15:57:30 2019 +0000 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/myitcv/.cache/go-build""
GOENV=""/home/myitcv/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/myitcv/gostuff""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/home/myitcv/gos""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/home/myitcv/gos/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build492256999=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

The docs for `GOMOD` state:

```
$ go help environment
...
        GOMOD
                The absolute path to the go.mod of the main module,
                or the empty string if not using modules.
```

For some time I have (incorrectly) been advising people that the way to determine if you are in a module context or not (i.e. modules not off and you are in the context of a `go.mod`) is by testing whether the output from `go env GOMOD` is the empty string or not. 

However this fails when you consider:

```
$ cd $(mktemp -d)
$ GO111MODULE=on go env GOMOD
/dev/null
```

It's also not clear the docs are quite correct when it comes to modules being not off (i.e. auto or on):

```
$ cd $(mktemp -d)
$ go env GOMOD
 
```

(i.e. empty string, but we aren't not using modules, we are in the auto mode. Granted this is a bit less clearly incorrect)

I realise that this way `go env GOMOD` can be used to determine whether modules are off/not off, and whether you are in a module context or not assuming that they are not off. But documenting this a bit more clearly would, I think, help (selfishly me at least).

Because the actual logic for correctly determining that modules are not off _and_ you are in a module context is:

```go
cmd := exec.Command(""go"", ""env"", ""GOMOD"")
out, _ := cmd.CombinedOutput()
gomod := strings.TrimSpace(string(out))
if gomod != """" and gomod != os.DevNull {
   // ....
```

Thoughts?

cc @bcmills @jayconrod 

FYI @mvdan @kortschak ",1,cmd go  document that go env gomod can return  dev null            what version of go are you using   go version            go version  go version devel    sat dec              linux             does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   home myitcv  cache go build   goenv   home myitcv  config go env   goexe     goflags     gohostarch      gohostos  linux   goinsecure     gonoproxy     gonosumdb     goos  linux   gopath   home myitcv gostuff   goprivate     goproxy     goroot   home myitcv gos   gosumdb  sum golang org   gotmpdir     gotooldir   home myitcv gos pkg tool linux     gccgo  gccgo   ar  ar   cc  gcc   cxx  g     cgo enabled      gomod     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches             what did you do     the docs for  gomod  state            go help environment               gomod                  the absolute path to the go mod of the main module                   or the empty string if not using modules          for some time i have  incorrectly  been advising people that the way to determine if you are in a module context or not  i e  modules not off and you are in the context of a  go mod   is by testing whether the output from  go env gomod  is the empty string or not      however this fails when you consider            cd   mktemp  d       on go env gomod   dev null         it s also not clear the docs are quite correct when it comes to modules being not off  i e  auto or on             cd   mktemp  d     go env gomod             i e  empty string  but we aren t not using modules  we are in the auto mode  granted this is a bit less clearly incorrect     i realise that this way  go env gomod  can be used to determine whether modules are off not off  and whether you are in a module context or not assuming that they are not off  but documenting this a bit more clearly would  i think  help  selfishly me at least      because the actual logic for correctly determining that modules are not off  and  you are in a module context is        go  cmd    exec command  go    env    gomod    out       cmd combinedoutput    gomod    strings trimspace string out    if gomod       and gomod    os devnull                       thoughts     cc  bcmills  jayconrod     fyi  mvdan  kortschak ,1
264940,20049473500.0,IssuesEvent,2022-02-03 03:21:56,golang/go,https://api.github.com/repos/golang/go,closed,"net/netip: ParsePrefix documentation typo ""2001::db8::/32""",Documentation NeedsFix,"<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go1.18beta2
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

Not applicable

### What did you do?

Read docs/code

### What did you expect to see?

Valid CIDR notation

### What did you see instead?

Invalid CIDR notation

""2001::db8::/32"" includes an invalid IPv6 address. The double colon may appear only once. This code panics:

<pre>
package main

import (
	""net/netip""
)

// This playground uses a development build of Go:
// devel go1.18-41f485b9a7 Mon Jan 31 13:43:52 2022 +0000

func main() {
	_ = netip.MustParsePrefix(""2001::db8::/32"")
}
</pre>

https://github.com/golang/go/blob/41f485b9a7d8fd647c415be1d11b612063dff21c/src/net/netip/netip.go#L1291
",1.0,"net/netip: ParsePrefix documentation typo ""2001::db8::/32"" - <!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go1.18beta2
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

Not applicable

### What did you do?

Read docs/code

### What did you expect to see?

Valid CIDR notation

### What did you see instead?

Invalid CIDR notation

""2001::db8::/32"" includes an invalid IPv6 address. The double colon may appear only once. This code panics:

<pre>
package main

import (
	""net/netip""
)

// This playground uses a development build of Go:
// devel go1.18-41f485b9a7 Mon Jan 31 13:43:52 2022 +0000

func main() {
	_ = netip.MustParsePrefix(""2001::db8::/32"")
}
</pre>

https://github.com/golang/go/blob/41f485b9a7d8fd647c415be1d11b612063dff21c/src/net/netip/netip.go#L1291
",1,net netip  parseprefix documentation typo                    please answer these questions before submitting your issue  thanks              what version of go are you using   go version            go version                does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env       not applicable        what did you do     read docs code        what did you expect to see     valid cidr notation        what did you see instead     invalid cidr notation               includes an invalid   address  the double colon may appear only once  this code panics        package main    import    	 net netip           this playground uses a development build of go      devel       mon jan                 func main      	    netip mustparseprefix                         ,1
333940,24397567520.0,IssuesEvent,2022-10-04 20:48:14,golang/go,https://api.github.com/repos/golang/go,opened,os: document concurrency properties for File methods,ExpertNeeded Documentation NeedsInvestigation,"### What version of Go are you using (`go version`)?

https://pkg.go.dev/os@go1.19.1

### Does this issue reproduce with the latest release?

Yes.

### What did you do?

For #50436, I'm attempting to unblock reads on a `*File` returned by `os.Pipe` while it is being read concurrently by a user-controlled goroutine. The user-controlled goroutine may legitimately call the `Close` method, and may expect to be able to access other methods (such as `SetDeadline`) via type-assertion.

### What did you expect to see?

Given #6270, #7970, #9307, #17647 and https://go.dev/cl/65490, I expected the documentation for `*os.File to describe which methods are safe to invoke concurrently and under what conditions.

### What did you see instead?

The only mention of concurrency I could find in https://pkg.go.dev/os@go1.19.1 says this:
> Note: The maximum number of concurrent operations on a File may be limited by the OS or the system. The number should be high, but exceeding it may degrade performance or cause other issues.

That seems to imply that at least some of the `File` methods may be invoked concurrently, but isn't explicit about which ones.

I see unsynchronized writes in the `Close` implementation on both [`unix`](https://cs.opensource.google/go/go/+/master:src/os/file_unix.go;l=259;drc=6d8ec893039a39f495c8139012e47754e4518b70) and [`plan9`](https://cs.opensource.google/go/go/+/master:src/os/file_plan9.go;l=159;drc=81431c7aa7c5d782e72dec342442ea7664ef1783) (but maybe not `windows`?); it's not obvious to me which other methods are or aren't safe.

(CC @rsc @ianlancetaylor @robpike from previous `*File` race issues.)",1.0,"os: document concurrency properties for File methods - ### What version of Go are you using (`go version`)?

https://pkg.go.dev/os@go1.19.1

### Does this issue reproduce with the latest release?

Yes.

### What did you do?

For #50436, I'm attempting to unblock reads on a `*File` returned by `os.Pipe` while it is being read concurrently by a user-controlled goroutine. The user-controlled goroutine may legitimately call the `Close` method, and may expect to be able to access other methods (such as `SetDeadline`) via type-assertion.

### What did you expect to see?

Given #6270, #7970, #9307, #17647 and https://go.dev/cl/65490, I expected the documentation for `*os.File to describe which methods are safe to invoke concurrently and under what conditions.

### What did you see instead?

The only mention of concurrency I could find in https://pkg.go.dev/os@go1.19.1 says this:
> Note: The maximum number of concurrent operations on a File may be limited by the OS or the system. The number should be high, but exceeding it may degrade performance or cause other issues.

That seems to imply that at least some of the `File` methods may be invoked concurrently, but isn't explicit about which ones.

I see unsynchronized writes in the `Close` implementation on both [`unix`](https://cs.opensource.google/go/go/+/master:src/os/file_unix.go;l=259;drc=6d8ec893039a39f495c8139012e47754e4518b70) and [`plan9`](https://cs.opensource.google/go/go/+/master:src/os/file_plan9.go;l=159;drc=81431c7aa7c5d782e72dec342442ea7664ef1783) (but maybe not `windows`?); it's not obvious to me which other methods are or aren't safe.

(CC @rsc @ianlancetaylor @robpike from previous `*File` race issues.)",1,os  document concurrency properties for file methods       what version of go are you using   go version                does this issue reproduce with the latest release     yes         what did you do     for     i m attempting to unblock reads on a   file  returned by  os pipe  while it is being read concurrently by a user controlled goroutine  the user controlled goroutine may legitimately call the  close  method  and may expect to be able to access other methods  such as  setdeadline   via type assertion         what did you expect to see     given                and   i expected the documentation for   os file to describe which methods are safe to invoke concurrently and under what conditions         what did you see instead     the only mention of concurrency i could find in   says this     note  the maximum number of concurrent operations on a file may be limited by the os or the system  the number should be high  but exceeding it may degrade performance or cause other issues     that seems to imply that at least some of the  file  methods may be invoked concurrently  but isn t explicit about which ones     i see unsynchronized writes in the  close  implementation on both     and      but maybe not  windows     it s not obvious to me which other methods are or aren t safe      cc  rsc  ianlancetaylor  robpike from previous   file  race issues  ,1
512,2502304965.0,IssuesEvent,2015-01-09 07:01:07,fossology/fossology,https://api.github.com/repos/fossology/fossology,opened,Missing constraint in license_file,Category: DataBase Component: Rank Component: Tester Priority: High Status: New Tracker: Bug,"---


Author Name: **Bob Gobeille** 
Original Redmine Issue: 6753, http://www.fossology.org/issues/6753
Original Date: 2014/03/18
Original Assignee: Bob Gobeille

---

the license_file table needs a foreign key constraint on rf_fk to insure that any given rf_fk refers to a real license_ref record.


",1.0,"Missing constraint in license_file - ---


Author Name: **Bob Gobeille** 
Original Redmine Issue: 6753, http://www.fossology.org/issues/6753
Original Date: 2014/03/18
Original Assignee: Bob Gobeille

---

the license_file table needs a foreign key constraint on rf_fk to insure that any given rf_fk refers to a real license_ref record.


",0,missing constraint in license file         author name    bob gobeille    original redmine issue       original date        original assignee  bob gobeille       the license file table needs a foreign key constraint on rf fk to insure that any given rf fk refers to a real license ref record    ,0
25814,5200586468.0,IssuesEvent,2017-01-24 00:28:54,golang/go,https://api.github.com/repos/golang/go,closed,testing: document MainStart signature change in release notes,Documentation NeedsFix,"c56cc9b3b5727647c2afb3d57f5793151558a0a7 (https://golang.org/cl/32455) changed the signature of testing.MainStart

from:
https://golang.org/pkg/testing/#MainStart
```
func MainStart(matchString func(pat, str string) (bool, error), tests []InternalTest, benchmarks []InternalBenchmark, examples []InternalExample) *M
```

To:
https://beta.golang.org/pkg/testing/#MainStart
```
func MainStart(deps testDeps, tests []InternalTest, benchmarks []InternalBenchmark, examples []InternalExample) *M
```

This is not in our release notes, and just bit Kubernetes in https://github.com/kubernetes/kubernetes/pull/38926#issuecomment-274627297

For the record, this does say:

> It is not meant to be called directly and is not subject to the Go 1 compatibility document. It may change signature from release to release.

/cc @rsc ",1.0,"testing: document MainStart signature change in release notes - c56cc9b3b5727647c2afb3d57f5793151558a0a7 (https://golang.org/cl/32455) changed the signature of testing.MainStart

from:
https://golang.org/pkg/testing/#MainStart
```
func MainStart(matchString func(pat, str string) (bool, error), tests []InternalTest, benchmarks []InternalBenchmark, examples []InternalExample) *M
```

To:
https://beta.golang.org/pkg/testing/#MainStart
```
func MainStart(deps testDeps, tests []InternalTest, benchmarks []InternalBenchmark, examples []InternalExample) *M
```

This is not in our release notes, and just bit Kubernetes in https://github.com/kubernetes/kubernetes/pull/38926#issuecomment-274627297

For the record, this does say:

> It is not meant to be called directly and is not subject to the Go 1 compatibility document. It may change signature from release to release.

/cc @rsc ",1,testing  document mainstart signature change in release notes        changed the signature of testing mainstart    from           func mainstart matchstring func pat  str string   bool  error   tests  internaltest  benchmarks  internalbenchmark  examples  internalexample   m         to           func mainstart deps testdeps  tests  internaltest  benchmarks  internalbenchmark  examples  internalexample   m         this is not in our release notes  and just bit kubernetes in      for the record  this does say       it is not meant to be called directly and is not subject to the go   compatibility document  it may change signature from release to release      cc  rsc ,1
22098,4772987249.0,IssuesEvent,2016-10-26 22:35:37,golang/go,https://api.github.com/repos/golang/go,closed,context: WithCancel example is not explaining cancel func,Documentation NeedsFix,"As a user, I'd expect WithCancel example at https://tip.golang.org/pkg/context/#example_WithCancel to explain specific cancellation of the context by calling the cancel func. The example doesn't even require a cancellable context, see https://play.golang.org/p/4hMwLTCVaU.


Is this example trying to achieve something similar to what's below?
```
package main

import (
	""context""
	""fmt""
	""time""
)

func main() {
	count := func(ctx context.Context, dst chan<- int) {
		n := 1
		for {
			select {
			case dst <- n:
				n++
			case <-ctx.Done():
				fmt.Println(""not leaking"")
				return
			}
		}
	}

	ctx, cancel := context.WithCancel(context.Background())
	defer cancel()

	ints := make(chan int)
	go count(ctx, ints)
	for n := range ints {
		fmt.Println(n)
		if n == 5 {
			cancel()
			break
		}
	}

	time.Sleep(time.Minute)
}
```

/cc @bradfitz ",1.0,"context: WithCancel example is not explaining cancel func - As a user, I'd expect WithCancel example at https://tip.golang.org/pkg/context/#example_WithCancel to explain specific cancellation of the context by calling the cancel func. The example doesn't even require a cancellable context, see https://play.golang.org/p/4hMwLTCVaU.


Is this example trying to achieve something similar to what's below?
```
package main

import (
	""context""
	""fmt""
	""time""
)

func main() {
	count := func(ctx context.Context, dst chan<- int) {
		n := 1
		for {
			select {
			case dst <- n:
				n++
			case <-ctx.Done():
				fmt.Println(""not leaking"")
				return
			}
		}
	}

	ctx, cancel := context.WithCancel(context.Background())
	defer cancel()

	ints := make(chan int)
	go count(ctx, ints)
	for n := range ints {
		fmt.Println(n)
		if n == 5 {
			cancel()
			break
		}
	}

	time.Sleep(time.Minute)
}
```

/cc @bradfitz ",1,context  withcancel example is not explaining cancel func   as a user  i d expect withcancel example at   to explain specific cancellation of the context by calling the cancel func  the example doesn t even require a cancellable context  see        is this example trying to achieve something similar to what s below        package main    import    	 context   	 fmt   	 time        func main      	count    func ctx context context  dst chan   int     		n       		for    			select    			case dst    n   				n    			case   ctx done     				fmt println  not leaking    				return  			   		   	     	ctx  cancel    context withcancel context background     	defer cancel      	ints    make chan int   	go count ctx  ints   	for n    range ints    		fmt println n   		if n         			cancel    			break  		   	     	time sleep time minute              cc  bradfitz ,1
41021,6887769722.0,IssuesEvent,2017-11-22 01:24:33,golang/go,https://api.github.com/repos/golang/go,closed,"doc: GoLand is misspelled (""Gogland"") at /doc/editors.html",Documentation,"Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
N/A (documentation issue)

### Does this issue reproduce with the latest release?
N/A (documentation issue)

### What operating system and processor architecture are you using (`go env`)?
N/A (documentation issue)

### What did you do?

If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.


### What did you expect to see?
""GoLand""

### What did you see instead?
""Gogland""
",1.0,"doc: GoLand is misspelled (""Gogland"") at /doc/editors.html - Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
N/A (documentation issue)

### Does this issue reproduce with the latest release?
N/A (documentation issue)

### What operating system and processor architecture are you using (`go env`)?
N/A (documentation issue)

### What did you do?

If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.


### What did you expect to see?
""GoLand""

### What did you see instead?
""Gogland""
",1,doc  goland is misspelled   gogland   at  doc editors html   please answer these questions before submitting your issue  thanks           what version of go are you using   go version     n a  documentation issue         does this issue reproduce with the latest release   n a  documentation issue         what operating system and processor architecture are you using   go env     n a  documentation issue         what did you do     if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best           what did you expect to see    goland         what did you see instead    gogland   ,1
10843,12828063327.0,IssuesEvent,2020-07-06 19:46:08,dotnet/roslyn,https://api.github.com/repos/dotnet/roslyn,closed,Warning Waves,Area-Compilers Concept-Diagnostic Clarity Feature Request Tenet-Compatibility,"- [ ] Compiler flag + Csc task + CoreCompile target
- [ ] Project system change to display in IDE (https://github.com/dotnet/project-system/issues/4725)
- [ ] Code fixer to help turn the feature on
- [ ] Select a few issues that we want in the first wave

Over the course of its few years of development, the Roslyn compiler team implemented a handful of valuable new diagnostics for situations in user code that almost certainly indicate errors, and which would be very expensive to implement outside the compiler. One typical example was the comparison of a `struct` value against `null`

``` cs
    void M(..., CancellationToken token)
    {
        if (token == null) { ... }
    }
```

The test `token == null` must always fail (a `struct` value, when boxed into an `object`, is never `null`). This almost certainly indicates an error in the user's program. And indeed, this diagnostic alerted us to dozens of real bugs in the Roslyn code base. Other new warnings similarly alerted us to other problems.

Since compiler warnings are enabled by default, any project that upgrades to the new version of the compiler may be ""broken"" (e.g. if configured to treat warnings as errors) by the presence of newly implemented diagnostics at a time when changing the code or the build infrastructure is inconvenient. Due to this concern previous releases of the compiler have avoided adding diagnostics for existing code scenarios. We wanted to allow Roslyn, it its first release and in subsequent releases, to add value by adding additional warnings for likely code problems that are difficult to detect outside the compiler. But how could we do it without breaking compatibility?

A few years ago we considered adding the concept of ""warning waves"" to the compilers. The compiler would know in which compiler version support for each warning was added. The compiler command-line would specify a version for which warnings to allow; the compiler would then report only warnings that were implemented up until the specified ""warning version"". We held meetings and produced a detailed design.

Two years ago we dropped the idea of adding a specific ""warning waves"" flag to the compiler because we ""realized"" that the new mechanisms to control the diagnostics (such as ruleset files) are fine-grained enough to provide the same value.

Unfortunately we did not complete the work to address the scenario. Consequently all of the new warnings implemented in Roslyn have since been removed from the compilers due to compatibility concerns.

It is time for us to revisit the issue, to design and implement a solution that addresses the original problem. Users should be able to specify a version of the compiler that represents the set of warnings they are willing to have reported.

LDM notes:
- https://github.com/dotnet/csharplang/blob/master/meetings/2018/LDM-2018-09-26.md",True,"Warning Waves - - [ ] Compiler flag + Csc task + CoreCompile target
- [ ] Project system change to display in IDE (https://github.com/dotnet/project-system/issues/4725)
- [ ] Code fixer to help turn the feature on
- [ ] Select a few issues that we want in the first wave

Over the course of its few years of development, the Roslyn compiler team implemented a handful of valuable new diagnostics for situations in user code that almost certainly indicate errors, and which would be very expensive to implement outside the compiler. One typical example was the comparison of a `struct` value against `null`

``` cs
    void M(..., CancellationToken token)
    {
        if (token == null) { ... }
    }
```

The test `token == null` must always fail (a `struct` value, when boxed into an `object`, is never `null`). This almost certainly indicates an error in the user's program. And indeed, this diagnostic alerted us to dozens of real bugs in the Roslyn code base. Other new warnings similarly alerted us to other problems.

Since compiler warnings are enabled by default, any project that upgrades to the new version of the compiler may be ""broken"" (e.g. if configured to treat warnings as errors) by the presence of newly implemented diagnostics at a time when changing the code or the build infrastructure is inconvenient. Due to this concern previous releases of the compiler have avoided adding diagnostics for existing code scenarios. We wanted to allow Roslyn, it its first release and in subsequent releases, to add value by adding additional warnings for likely code problems that are difficult to detect outside the compiler. But how could we do it without breaking compatibility?

A few years ago we considered adding the concept of ""warning waves"" to the compilers. The compiler would know in which compiler version support for each warning was added. The compiler command-line would specify a version for which warnings to allow; the compiler would then report only warnings that were implemented up until the specified ""warning version"". We held meetings and produced a detailed design.

Two years ago we dropped the idea of adding a specific ""warning waves"" flag to the compiler because we ""realized"" that the new mechanisms to control the diagnostics (such as ruleset files) are fine-grained enough to provide the same value.

Unfortunately we did not complete the work to address the scenario. Consequently all of the new warnings implemented in Roslyn have since been removed from the compilers due to compatibility concerns.

It is time for us to revisit the issue, to design and implement a solution that addresses the original problem. Users should be able to specify a version of the compiler that represents the set of warnings they are willing to have reported.

LDM notes:
- https://github.com/dotnet/csharplang/blob/master/meetings/2018/LDM-2018-09-26.md",0,warning waves       compiler flag   csc task   corecompile target      project system change to display in ide         code fixer to help turn the feature on      select a few issues that we want in the first wave    over the course of its few years of development  the roslyn compiler team implemented a handful of valuable new diagnostics for situations in user code that almost certainly indicate errors  and which would be very expensive to implement outside the compiler  one typical example was the comparison of a  struct  value against  null         cs      void m      cancellationtoken token                  if  token    null                         the test  token    null  must always fail  a  struct  value  when boxed into an  object   is never  null    this almost certainly indicates an error in the user s program  and indeed  this diagnostic alerted us to dozens of real bugs in the roslyn code base  other new warnings similarly alerted us to other problems     since compiler warnings are enabled by default  any project that upgrades to the new version of the compiler may be  broken   e g  if configured to treat warnings as errors  by the presence of newly implemented diagnostics at a time when changing the code or the build infrastructure is inconvenient  due to this concern previous releases of the compiler have avoided adding diagnostics for existing code scenarios  we wanted to allow roslyn  it its first release and in subsequent releases  to add value by adding additional warnings for likely code problems that are difficult to detect outside the compiler  but how could we do it without breaking compatibility     a few years ago we considered adding the concept of  warning waves  to the compilers  the compiler would know in which compiler version support for each warning was added  the compiler command line would specify a version for which warnings to allow  the compiler would then report only warnings that were implemented up until the specified  warning version   we held meetings and produced a detailed design     two years ago we dropped the idea of adding a specific  warning waves  flag to the compiler because we  realized  that the new mechanisms to control the diagnostics  such as ruleset files  are fine grained enough to provide the same value     unfortunately we did not complete the work to address the scenario  consequently all of the new warnings implemented in roslyn have since been removed from the compilers due to compatibility concerns     it is time for us to revisit the issue  to design and implement a solution that addresses the original problem  users should be able to specify a version of the compiler that represents the set of warnings they are willing to have reported     ldm notes      ,0
190540,15242613860.0,IssuesEvent,2021-02-19 10:06:33,golang/go,https://api.github.com/repos/golang/go,closed,x/website: merge module doc changes as part of Go 1.16 release,Documentation NeedsFix,"1.16 introduces a `retract` directive. The new directive is not mentioned in the [Go Modules Reference](https://tip.golang.org/ref/mod#go-mod-file-grammar). The [CL adding the doc](https://go-review.googlesource.com/c/website/+/286952) will need to be merged before the 1.16 release (currently has a merge conflict).

In 1.16, go install will accepts arguments with version suffixes (`go install pkg@version`). The [CL adding the relevant doc](https://go-review.googlesource.com/c/website/+/285452) will need to be merged before the 1.16 release (currently has a merge conflict, and unresolved comments).

Filing an issue just to be sure this is on someone's radar.

cc @dmitshur @bcmills ",1.0,"x/website: merge module doc changes as part of Go 1.16 release - 1.16 introduces a `retract` directive. The new directive is not mentioned in the [Go Modules Reference](https://tip.golang.org/ref/mod#go-mod-file-grammar). The [CL adding the doc](https://go-review.googlesource.com/c/website/+/286952) will need to be merged before the 1.16 release (currently has a merge conflict).

In 1.16, go install will accepts arguments with version suffixes (`go install pkg@version`). The [CL adding the relevant doc](https://go-review.googlesource.com/c/website/+/285452) will need to be merged before the 1.16 release (currently has a merge conflict, and unresolved comments).

Filing an issue just to be sure this is on someone's radar.

cc @dmitshur @bcmills ",1,x website  merge module doc changes as part of go     release       introduces a  retract  directive  the new directive is not mentioned in the     the     will need to be merged before the     release  currently has a merge conflict      in      go install will accepts arguments with version suffixes   go install pkg version    the     will need to be merged before the     release  currently has a merge conflict  and unresolved comments      filing an issue just to be sure this is on someone s radar     cc  dmitshur  bcmills ,1
11042,3454718103.0,IssuesEvent,2015-12-17 16:59:58,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: docs are unclear that tests are run in parallel across packages,Documentation,"If you provide `go test` with more than one package, tests across packages are run in parallel by default (assuming you have more than one CPU).  If you have tests across packages that contend for a singular resource (for example, listening on a particular TCP port) you can end up getting unexpected failures.

The docs aren't very clear in this respect and I think some improvements can be made to them.  This has bit me in the past and just came up again in the Gophers Slack community.  In these cases we developers had to go to the `go` command's source code to understand what was happening.

In my view, some of the issues:
* `go test --help` is equivalent to `go help testflag` rather than `go help test`.  I tend to add `--help` by default and so I was seeing the wrong (IMO) help output.
* `go help testflag` mentions parallelism with its `-parallel` flag, but this only affects tests within a single package.  The presence of this flag implies that tests that don't set `t.Parallel` will never be run in parallel, regardless of where they live.  
* `go help testflag` does not mention `go help build` at all, and users might not be aware that all the flags there also apply to `go test`, in particular the `-p` flag.  (`go help test` does mention build flags, however, which is good.)
* `go help build` mentions the `-p` flag, but it only talks about builds.  It does not imply that the tests will also be run in parallel.  I think most people assume that build and test are separate steps.  I think it could also be cleaner that it's talking about packages specifically there.

The core issue is that there are multiple levels of parallelism at play, and only one is mentioned in the test help.",1.0,"cmd/go: docs are unclear that tests are run in parallel across packages - If you provide `go test` with more than one package, tests across packages are run in parallel by default (assuming you have more than one CPU).  If you have tests across packages that contend for a singular resource (for example, listening on a particular TCP port) you can end up getting unexpected failures.

The docs aren't very clear in this respect and I think some improvements can be made to them.  This has bit me in the past and just came up again in the Gophers Slack community.  In these cases we developers had to go to the `go` command's source code to understand what was happening.

In my view, some of the issues:
* `go test --help` is equivalent to `go help testflag` rather than `go help test`.  I tend to add `--help` by default and so I was seeing the wrong (IMO) help output.
* `go help testflag` mentions parallelism with its `-parallel` flag, but this only affects tests within a single package.  The presence of this flag implies that tests that don't set `t.Parallel` will never be run in parallel, regardless of where they live.  
* `go help testflag` does not mention `go help build` at all, and users might not be aware that all the flags there also apply to `go test`, in particular the `-p` flag.  (`go help test` does mention build flags, however, which is good.)
* `go help build` mentions the `-p` flag, but it only talks about builds.  It does not imply that the tests will also be run in parallel.  I think most people assume that build and test are separate steps.  I think it could also be cleaner that it's talking about packages specifically there.

The core issue is that there are multiple levels of parallelism at play, and only one is mentioned in the test help.",1,cmd go  docs are unclear that tests are run in parallel across packages   if you provide  go test  with more than one package  tests across packages are run in parallel by default  assuming you have more than one cpu    if you have tests across packages that contend for a singular resource  for example  listening on a particular tcp port  you can end up getting unexpected failures     the docs aren t very clear in this respect and i think some improvements can be made to them   this has bit me in the past and just came up again in the gophers slack community   in these cases we developers had to go to the  go  command s source code to understand what was happening     in my view  some of the issues      go test   help  is equivalent to  go help testflag  rather than  go help test    i tend to add    help  by default and so i was seeing the wrong  imo  help output      go help testflag  mentions parallelism with its   parallel  flag  but this only affects tests within a single package   the presence of this flag implies that tests that don t set  t parallel  will never be run in parallel  regardless of where they live        go help testflag  does not mention  go help build  at all  and users might not be aware that all the flags there also apply to  go test   in particular the   p  flag     go help test  does mention build flags  however  which is good       go help build  mentions the   p  flag  but it only talks about builds   it does not imply that the tests will also be run in parallel   i think most people assume that build and test are separate steps   i think it could also be cleaner that it s talking about packages specifically there     the core issue is that there are multiple levels of parallelism at play  and only one is mentioned in the test help ,1
91854,10730196170.0,IssuesEvent,2019-10-28 16:57:15,golang/go,https://api.github.com/repos/golang/go,closed,proposal: doc: document that Go 1.14 is last to support darwin/arm (32bit version)?,Documentation Proposal mobile,"iOS 13 (and iPadOS 13) does not support running 32-bit apps. iOS 10 was the last version that supported 32-bit apps (with very visible warnings), and it's 3 years old.

Is it time to remove `darwin/arm` (leaving just `darwin/arm64`)? If so, the first step would be to document that Go 1.14 will be the final release with `darwin/arm` support.

Related to #34749. /cc @bradfitz @hyangah @eliasnaur",1.0,"proposal: doc: document that Go 1.14 is last to support darwin/arm (32bit version)? - iOS 13 (and iPadOS 13) does not support running 32-bit apps. iOS 10 was the last version that supported 32-bit apps (with very visible warnings), and it's 3 years old.

Is it time to remove `darwin/arm` (leaving just `darwin/arm64`)? If so, the first step would be to document that Go 1.14 will be the final release with `darwin/arm` support.

Related to #34749. /cc @bradfitz @hyangah @eliasnaur",1,proposal  doc  document that go     is last to support darwin arm    version     ios    and ipados    does not support running   bit apps  ios   was the last version that supported   bit apps  with very visible warnings   and it s   years old     is it time to remove  darwin arm   leaving just  darwin      if so  the first step would be to document that go     will be the final release with  darwin arm  support     related to      cc  bradfitz  hyangah  eliasnaur,1
21923,4758759430.0,IssuesEvent,2016-10-24 20:27:11,golang/go,https://api.github.com/repos/golang/go,closed,encoding/json: RawMessage should marshal without pointer receiver,Documentation,"<pre>The current json.RawMessage implementation defines MarshalJSON on a pointer receiver. 
This causes unexpected behavior when marshalling with non-pointer-receiver objects.

For example:
<a href=""http://play.golang.org/p/Cf_6zpIKC0"">http://play.golang.org/p/Cf_6zpIKC0</a>

Instead, MarshalJSON should be defined on a non-pointer receiver for json.RawMessage. 
This will continue to work for existing code that uses pointer-receivers, but will
change behavior to work &quot;correctly&quot; on code that accidentally uses
non-pointer-receivers.</pre>",1.0,"encoding/json: RawMessage should marshal without pointer receiver - <pre>The current json.RawMessage implementation defines MarshalJSON on a pointer receiver. 
This causes unexpected behavior when marshalling with non-pointer-receiver objects.

For example:
<a href=""http://play.golang.org/p/Cf_6zpIKC0"">http://play.golang.org/p/Cf_6zpIKC0</a>

Instead, MarshalJSON should be defined on a non-pointer receiver for json.RawMessage. 
This will continue to work for existing code that uses pointer-receivers, but will
change behavior to work &quot;correctly&quot; on code that accidentally uses
non-pointer-receivers.</pre>",1,encoding json  rawmessage should marshal without pointer receiver    the current json rawmessage implementation defines marshaljson on a pointer receiver   this causes unexpected behavior when marshalling with non pointer receiver objects   for example   a href     instead  marshaljson should be defined on a non pointer receiver for json rawmessage   this will continue to work for existing code that uses pointer receivers  but will change behavior to work  quot correctly quot  on code that accidentally uses non pointer receivers  ,1
170884,13207645857.0,IssuesEvent,2020-08-14 23:58:11,Azure/azure-sdk-for-net,https://api.github.com/repos/Azure/azure-sdk-for-net,closed,[Test] Fix FormRecognizer test failures,Client Cognitive - Form Recognizer LiveTestFailure test-reliability,Behavior changes with the new service version have triggered issues in our tests: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=494211&view=results,2.0,[Test] Fix FormRecognizer test failures - Behavior changes with the new service version have triggered issues in our tests: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=494211&view=results,0,  fix formrecognizer test failures   behavior changes with the new service version have triggered issues in our tests   ,0
52335,7759136373.0,IssuesEvent,2018-05-31 22:02:16,golang/go,https://api.github.com/repos/golang/go,closed,net/http: document that Server.Serve expects a hashable net.Listener (as a map key),Documentation,"### What version of Go are you using (`go version`)?
1.10

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/vagrant/.cache/go-build""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/vagrant/workspace-dss""
GORACE=""""
GOROOT=""/usr/local/go-1.10""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go-1.10/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build230598238=/tmp/go-build -gno-record-gcc-switches""
```

### What did you do?

I implemented `net.Listener` with a struct that defined a `func()` field. I passed this struct to `http.Server.Serve`. The code compiled just fine and panicked at run-time because my listener implementation couldn't be used as a hash key (see `trackListener` in the `http` package).

### What did you expect to see?

A working `http.Server`. Or else some documentation that clearly states the constraints for the kinds of listeners usable with `http.Server`.

### What did you see instead?

Panic at run-time.",1.0,"net/http: document that Server.Serve expects a hashable net.Listener (as a map key) - ### What version of Go are you using (`go version`)?
1.10

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/vagrant/.cache/go-build""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/vagrant/workspace-dss""
GORACE=""""
GOROOT=""/usr/local/go-1.10""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go-1.10/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build230598238=/tmp/go-build -gno-record-gcc-switches""
```

### What did you do?

I implemented `net.Listener` with a struct that defined a `func()` field. I passed this struct to `http.Server.Serve`. The code compiled just fine and panicked at run-time because my listener implementation couldn't be used as a hash key (see `trackListener` in the `http` package).

### What did you expect to see?

A working `http.Server`. Or else some documentation that clearly states the constraints for the kinds of listeners usable with `http.Server`.

### What did you see instead?

Panic at run-time.",1,net http  document that server serve expects a hashable net listener  as a map key        what version of go are you using   go version                does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env          goarch      gobin     gocache   home vagrant  cache go build   goexe     gohostarch      gohostos  linux   goos  linux   gopath   home vagrant workspace dss   gorace     goroot   usr local go       gotmpdir     gotooldir   usr local go     pkg tool linux     gccgo  gccgo   cc  gcc   cxx  g     cgo enabled      cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches              what did you do     i implemented  net listener  with a struct that defined a  func    field  i passed this struct to  http server serve   the code compiled just fine and panicked at run time because my listener implementation couldn t be used as a hash key  see  tracklistener  in the  http  package          what did you expect to see     a working  http server   or else some documentation that clearly states the constraints for the kinds of listeners usable with  http server          what did you see instead     panic at run time ,1
20390,4541560957.0,IssuesEvent,2016-09-09 18:13:43,golang/go,https://api.github.com/repos/golang/go,closed,doc: available list of first class ports,Documentation,"(Possibly very minor issue, but might be worth to clarify, because go supports such a wide range of os/arch pairs.)

I use these sources (I could find these easily):
1. https://github.com/golang/go/wiki/PortingPolicy
2. https://golang.org/doc/install
3. https://golang.org/dl/
4. https://build.golang.org

1. defines these easily available requirements for identification:

`-` ""Official binaries are provided"" and

`-` ""Installation is documented at http://golang.org/doc/install""


Looking at https://golang.org/dl/  ∩  http://golang.org/doc/install : 
freebsd/386 is missing from installation documentation (System requirements)

If it's ""easy"", this is probably also worth to clarify:
Looking at https://golang.org/dl/  ∩  http://golang.org/doc/install ∩ https://build.golang.org : 
build.golang.org lists these as first class ports, not mentioned in the canonical source of lists:
darwin/arm
darwin/arm64
darwin/386
freebsd/arm
freebsd/386
linux/mips64le
linux/ppc64
linux/ppc64le
android/arm









",1.0,"doc: available list of first class ports - (Possibly very minor issue, but might be worth to clarify, because go supports such a wide range of os/arch pairs.)

I use these sources (I could find these easily):
1. https://github.com/golang/go/wiki/PortingPolicy
2. https://golang.org/doc/install
3. https://golang.org/dl/
4. https://build.golang.org

1. defines these easily available requirements for identification:

`-` ""Official binaries are provided"" and

`-` ""Installation is documented at http://golang.org/doc/install""


Looking at https://golang.org/dl/  ∩  http://golang.org/doc/install : 
freebsd/386 is missing from installation documentation (System requirements)

If it's ""easy"", this is probably also worth to clarify:
Looking at https://golang.org/dl/  ∩  http://golang.org/doc/install ∩ https://build.golang.org : 
build.golang.org lists these as first class ports, not mentioned in the canonical source of lists:
darwin/arm
darwin/arm64
darwin/386
freebsd/arm
freebsd/386
linux/mips64le
linux/ppc64
linux/ppc64le
android/arm









",1,doc  available list of first class ports    possibly very minor issue  but might be worth to clarify  because go supports such a wide range of os arch pairs      i use these sources  i could find these easily                                 defines these easily available requirements for identification          official binaries are provided  and         installation is documented at        looking at    ∩        freebsd   is missing from installation documentation  system requirements     if it s  easy   this is probably also worth to clarify   looking at    ∩    ∩       build golang org lists these as first class ports  not mentioned in the canonical source of lists   darwin arm  darwin    darwin    freebsd arm  freebsd    linux    linux    linux    android arm                    ,1
132806,10764722883.0,IssuesEvent,2019-11-01 09:07:42,nicolargo/glances,https://api.github.com/repos/nicolargo/glances,closed,KeyError: b'Rss:' in memory_maps,bug needs test,"Before filling this issue, please read the manual (https://glances.readthedocs.io/en/latest/) and search if the bug do not already exists in the database (https://github.com/nicolargo/glances/issues).

#### Description

For a bug: Describe the bug and list the steps you used when the issue occurred.

    > glances -w 
      File ""/usr/local/bin/glances"", line 11, in <module>
        load_entry_point('Glances==3.1.3', 'console_scripts', 'glances')()
      File ""/usr/local/lib/python3.6/dist-packages/glances/__init__.py"", line 143, in main
        start(config=config, args=args)
      File ""/usr/local/lib/python3.6/dist-packages/glances/__init__.py"", line 108, in start
        mode = GlancesMode(config=config, args=args)
      File ""/usr/local/lib/python3.6/dist-packages/glances/webserver.py"", line 41, in __init__
        self.stats.update()
      File ""/usr/local/lib/python3.6/dist-packages/glances/stats.py"", line 234, in update
        self._plugins[p].update()
      File ""/usr/local/lib/python3.6/dist-packages/glances/plugins/glances_processcount.py"", line 73, in update
        glances_processes.update()
      File ""/usr/local/lib/python3.6/dist-packages/glances/processes.py"", line 295, in update
        extended['memory_swap'] = sum([v.swap for v in top_process.memory_maps()])
      File ""/usr/local/lib/python3.6/dist-packages/psutil/__init__.py"", line 1233, in memory_maps
        it = self._proc.memory_maps()
      File ""/usr/local/lib/python3.6/dist-packages/psutil/_pslinux.py"", line 1513, in wrapper
        return fun(self, *args, **kwargs)
      File ""/usr/local/lib/python3.6/dist-packages/psutil/_pslinux.py"", line 1842, in memory_maps
        data[b'Rss:'],
    KeyError: b'Rss:'


For an enhancement or new feature: Describe your needs.

#### Versions

* Glances & psutil (glances -V):
    Glances v3.1.3 with psutil v5.6.3
* Operating System (lsb_release -a):

   No LSB modules are available.
   Distributor ID: Ubuntu
   Description:    Ubuntu 18.04.3 LTS
   Release:        18.04
   Codename:       bionic
   
#### Logs

You can also pastebin the Glances logs file (https://glances.readthedocs.io/en/latest/config.html#logging)
",1.0,"KeyError: b'Rss:' in memory_maps - Before filling this issue, please read the manual (https://glances.readthedocs.io/en/latest/) and search if the bug do not already exists in the database (https://github.com/nicolargo/glances/issues).

#### Description

For a bug: Describe the bug and list the steps you used when the issue occurred.

    > glances -w 
      File ""/usr/local/bin/glances"", line 11, in <module>
        load_entry_point('Glances==3.1.3', 'console_scripts', 'glances')()
      File ""/usr/local/lib/python3.6/dist-packages/glances/__init__.py"", line 143, in main
        start(config=config, args=args)
      File ""/usr/local/lib/python3.6/dist-packages/glances/__init__.py"", line 108, in start
        mode = GlancesMode(config=config, args=args)
      File ""/usr/local/lib/python3.6/dist-packages/glances/webserver.py"", line 41, in __init__
        self.stats.update()
      File ""/usr/local/lib/python3.6/dist-packages/glances/stats.py"", line 234, in update
        self._plugins[p].update()
      File ""/usr/local/lib/python3.6/dist-packages/glances/plugins/glances_processcount.py"", line 73, in update
        glances_processes.update()
      File ""/usr/local/lib/python3.6/dist-packages/glances/processes.py"", line 295, in update
        extended['memory_swap'] = sum([v.swap for v in top_process.memory_maps()])
      File ""/usr/local/lib/python3.6/dist-packages/psutil/__init__.py"", line 1233, in memory_maps
        it = self._proc.memory_maps()
      File ""/usr/local/lib/python3.6/dist-packages/psutil/_pslinux.py"", line 1513, in wrapper
        return fun(self, *args, **kwargs)
      File ""/usr/local/lib/python3.6/dist-packages/psutil/_pslinux.py"", line 1842, in memory_maps
        data[b'Rss:'],
    KeyError: b'Rss:'


For an enhancement or new feature: Describe your needs.

#### Versions

* Glances & psutil (glances -V):
    Glances v3.1.3 with psutil v5.6.3
* Operating System (lsb_release -a):

   No LSB modules are available.
   Distributor ID: Ubuntu
   Description:    Ubuntu 18.04.3 LTS
   Release:        18.04
   Codename:       bionic
   
#### Logs

You can also pastebin the Glances logs file (https://glances.readthedocs.io/en/latest/config.html#logging)
",0,keyerror  b rss   in memory maps   before filling this issue  please read the manual    and search if the bug do not already exists in the database            description    for a bug  describe the bug and list the steps you used when the issue occurred           glances  w         file   usr local bin glances   line    in            load entry point  glances           console scripts    glances            file   usr local lib     dist packages glances   init   py   line    in main          start config config  args args         file   usr local lib     dist packages glances   init   py   line    in start          mode   glancesmode config config  args args         file   usr local lib     dist packages glances webserver py   line    in   init            self stats update          file   usr local lib     dist packages glances stats py   line    in update          self  plugins  update          file   usr local lib     dist packages glances plugins glances processcount py   line    in update          glances processes update          file   usr local lib     dist packages glances processes py   line    in update          extended    sum           file   usr local lib     dist packages psutil   init   py   line    in memory maps          it   self  proc memory maps          file   usr local lib     dist packages psutil  pslinux py   line    in wrapper          return fun self   args    kwargs         file   usr local lib     dist packages psutil  pslinux py   line    in memory maps          data        keyerror  b rss        for an enhancement or new feature  describe your needs          versions      glances   psutil  glances  v        glances       with psutil          operating system  lsb release  a         no lsb modules are available      distributor id  ubuntu     description     ubuntu       lts     release                 codename        bionic            logs    you can also pastebin the glances logs file     ,0
60042,8401708603.0,IssuesEvent,2018-10-11 02:33:11,golang/go,https://api.github.com/repos/golang/go,closed,"unsafe: document that the result of Alignof, Offsetof, and Sizeof are constant",Documentation,"The Go specification documents that these [""builtin"" functions are constants](https://golang.org/ref/spec#Constants). However, it is not clear from the [documentation of the `unsafe` package](https://golang.org/pkg/unsafe/) that these are constants. Perhaps we should document them as such?",1.0,"unsafe: document that the result of Alignof, Offsetof, and Sizeof are constant - The Go specification documents that these [""builtin"" functions are constants](https://golang.org/ref/spec#Constants). However, it is not clear from the [documentation of the `unsafe` package](https://golang.org/pkg/unsafe/) that these are constants. Perhaps we should document them as such?",1,unsafe  document that the result of alignof  offsetof  and sizeof are constant   the go specification documents that these     however  it is not clear from the     that these are constants  perhaps we should document them as such ,1
271221,20625531878.0,IssuesEvent,2022-03-07 22:04:35,golang/go,https://api.github.com/repos/golang/go,opened,x/website: update to latest spec just before release,Documentation release-blocker,"To get the most up-to-date spec into the 1.18 release, rather than cherry-picking possibly multiple CLs until the release, we should create a single CL in the release branch which contains a 1:1 copy of the latest spec at tip.

cc: @dmitshur ",1.0,"x/website: update to latest spec just before release - To get the most up-to-date spec into the 1.18 release, rather than cherry-picking possibly multiple CLs until the release, we should create a single CL in the release branch which contains a 1:1 copy of the latest spec at tip.

cc: @dmitshur ",1,x website  update to latest spec just before release   to get the most up to date spec into the     release  rather than cherry picking possibly multiple cls until the release  we should create a single cl in the release branch which contains a     copy of the latest spec at tip     cc   dmitshur ,1
321453,23855128648.0,IssuesEvent,2022-09-06 22:16:30,golang/go,https://api.github.com/repos/golang/go,closed,net/http: ProxyFromEnvironment documentation is wrong,Documentation NeedsFix,"After the change in #40909 (referenced via #45227), the [documentation for `ProxyFromEnvironment`](https://pkg.go.dev/net/http@go1.19#ProxyFromEnvironment) still incorrectly claims:

> HTTPS_PROXY takes precedence over HTTP_PROXY for https requests.

It seems `HTTP_PROXY` is no longer used at all for `https` requests.  The documentation here should have been fixed when the breaking change was made in Go 1.16.",1.0,"net/http: ProxyFromEnvironment documentation is wrong - After the change in #40909 (referenced via #45227), the [documentation for `ProxyFromEnvironment`](https://pkg.go.dev/net/http@go1.19#ProxyFromEnvironment) still incorrectly claims:

> HTTPS_PROXY takes precedence over HTTP_PROXY for https requests.

It seems `HTTP_PROXY` is no longer used at all for `https` requests.  The documentation here should have been fixed when the breaking change was made in Go 1.16.",1,net http  proxyfromenvironment documentation is wrong   after the change in     referenced via      the     still incorrectly claims       https proxy takes precedence over http proxy for https requests     it seems  http proxy  is no longer used at all for  https  requests   the documentation here should have been fixed when the breaking change was made in go     ,1
39279,6733497169.0,IssuesEvent,2017-10-18 14:59:49,golang/go,https://api.github.com/repos/golang/go,opened,"x/net: Update ""net/context"" documentation to point to context package",Documentation,"I was trying to figure out the difference between the ""golang.org/x/net/context"" and ""context, "" and I couldn't find any, so I was a little bit confused. I had to dig into the release notes until I saw the release notes for [1.7](https://golang.org/doc/go1.7#context) where it says:

> Go 1.7 moves the golang.org/x/net/context package into the standard library as context.

It would be helpful to update the doc in ""x/net/context"" to point to the release note. Also, I notice that go tool fix help you to change imports of golang.org/x/net/context to context. It would be cool to reference that too. 

I would be happy to help with a patch if you think is worth it. 



",1.0,"x/net: Update ""net/context"" documentation to point to context package - I was trying to figure out the difference between the ""golang.org/x/net/context"" and ""context, "" and I couldn't find any, so I was a little bit confused. I had to dig into the release notes until I saw the release notes for [1.7](https://golang.org/doc/go1.7#context) where it says:

> Go 1.7 moves the golang.org/x/net/context package into the standard library as context.

It would be helpful to update the doc in ""x/net/context"" to point to the release note. Also, I notice that go tool fix help you to change imports of golang.org/x/net/context to context. It would be cool to reference that too. 

I would be happy to help with a patch if you think is worth it. 



",1,x net  update  net context  documentation to point to context package   i was trying to figure out the difference between the  golang org x net context  and  context    and i couldn t find any  so i was a little bit confused  i had to dig into the release notes until i saw the release notes for     where it says       go     moves the golang org x net context package into the standard library as context     it would be helpful to update the doc in  x net context  to point to the release note  also  i notice that go tool fix help you to change imports of golang org x net context to context  it would be cool to reference that too      i would be happy to help with a patch if you think is worth it          ,1
94525,10826081538.0,IssuesEvent,2019-11-09 20:08:48,golang/go,https://api.github.com/repos/golang/go,closed,crypto/tls: add an example for using VerifyPeerCertificate to customize verification logic,Documentation NeedsFix,"A number of proposals to add knobs to tls.Config were closed by providing a way to achieve the same result with InsecureSkipVerify and VerifyPeerCertificate. There should be a basic example that replicates the standard verification logic, so users can edit if needed.",1.0,"crypto/tls: add an example for using VerifyPeerCertificate to customize verification logic - A number of proposals to add knobs to tls.Config were closed by providing a way to achieve the same result with InsecureSkipVerify and VerifyPeerCertificate. There should be a basic example that replicates the standard verification logic, so users can edit if needed.",1,crypto tls  add an example for using verifypeercertificate to customize verification logic   a number of proposals to add knobs to tls config were closed by providing a way to achieve the same result with insecureskipverify and verifypeercertificate  there should be a basic example that replicates the standard verification logic  so users can edit if needed ,1
61863,8559865821.0,IssuesEvent,2018-11-08 22:41:30,golang/go,https://api.github.com/repos/golang/go,closed,x/image/draw: Transformer documentation is misformatted,Documentation,"[`draw.Transformer`](https://godoc.org/golang.org/x/image/draw#Transformer) documentation currently looks like this:

![image](https://user-images.githubusercontent.com/1924134/48229705-dd1b4c80-e376-11e8-86ac-9363db916f80.png)

It should look more like this:

![image](https://user-images.githubusercontent.com/1924134/48229732-f4f2d080-e376-11e8-968e-5a63bca0abb8.png)",1.0,"x/image/draw: Transformer documentation is misformatted - [`draw.Transformer`](https://godoc.org/golang.org/x/image/draw#Transformer) documentation currently looks like this:

![image](https://user-images.githubusercontent.com/1924134/48229705-dd1b4c80-e376-11e8-86ac-9363db916f80.png)

It should look more like this:

![image](https://user-images.githubusercontent.com/1924134/48229732-f4f2d080-e376-11e8-968e-5a63bca0abb8.png)",1,x image draw  transformer documentation is misformatted       documentation currently looks like this             it should look more like this         ,1
436680,30564976687.0,IssuesEvent,2023-07-20 17:03:55,golang/go,https://api.github.com/repos/golang/go,closed,net/url: mention net.JoinHostPort for constructing url.URL.Host,Documentation NeedsFix,"In #16142, we add read support for extracting out the hostname and port.

However, that API is lacking the ability to write a host:port pair. Unfortunately, this is not as trivial as concatenating the host and port with a "":"" in-between in the case of IPv6, which requires wrapping the entire host with ""["" and ""]"" characters.

I propose the addition of:
```go
// JoinHostnamePort joins a hostname and a port, separating them with a colon.
// If the hostname is an IPv6 address, then it is wrapped with brackets.
// If the port is empty, then the hostname alone is returned.
func JoinHostnamePort(hostname, port string) string
```

Example outputs:
```go
JoinHostnamePort(""carbonite.digitalstatic.ts.net"", """")              // carbonite.digitalstatic.ts.net
JoinHostnamePort(""carbonite.digitalstatic.ts.net"", ""9200"")          // carbonite.digitalstatic.ts.net:9200
JoinHostnamePort(""100.109.51.95"", """")                               // 100.109.51.95
JoinHostnamePort(""100.109.51.95"", ""9200"")                           // 100.109.51.95:9200
JoinHostnamePort(""fd7a:115c:a1e0:ab12:4843:cd96:626d:335f"", """")     // fd7a:115c:a1e0:ab12:4843:cd96:626d:335f
JoinHostnamePort(""fd7a:115c:a1e0:ab12:4843:cd96:626d:335f"", ""9200"") // [fd7a:115c:a1e0:ab12:4843:cd96:626d:335f]:9200
```

Considerations:
* It's called `JoinHostnamePort` instead of `JoinHostPort` to be consistent with the `url.URL.Hostname` method.
* The port is a `string` to be consistent with `url.URL.Port`
* A standalone function that returns a string is consistent with top-level string-only transformers like `JoinPath`, `PathEscape`, `PathUnescape`, `QueryEscape`, `QueryUnescape`.
* What happens if the hostname contains colons but is not an IPv6 or the port is not a valid integer? We'll just concatenate the host and port with a colon in-between even if the result is ambiguous to parse. Alternatively, we could modify the API of `JoinHostnamePort` to return an error, but I personally like the simplicity of an error-less result.

\cc @bradfitz ",1.0,"net/url: mention net.JoinHostPort for constructing url.URL.Host - In #16142, we add read support for extracting out the hostname and port.

However, that API is lacking the ability to write a host:port pair. Unfortunately, this is not as trivial as concatenating the host and port with a "":"" in-between in the case of IPv6, which requires wrapping the entire host with ""["" and ""]"" characters.

I propose the addition of:
```go
// JoinHostnamePort joins a hostname and a port, separating them with a colon.
// If the hostname is an IPv6 address, then it is wrapped with brackets.
// If the port is empty, then the hostname alone is returned.
func JoinHostnamePort(hostname, port string) string
```

Example outputs:
```go
JoinHostnamePort(""carbonite.digitalstatic.ts.net"", """")              // carbonite.digitalstatic.ts.net
JoinHostnamePort(""carbonite.digitalstatic.ts.net"", ""9200"")          // carbonite.digitalstatic.ts.net:9200
JoinHostnamePort(""100.109.51.95"", """")                               // 100.109.51.95
JoinHostnamePort(""100.109.51.95"", ""9200"")                           // 100.109.51.95:9200
JoinHostnamePort(""fd7a:115c:a1e0:ab12:4843:cd96:626d:335f"", """")     // fd7a:115c:a1e0:ab12:4843:cd96:626d:335f
JoinHostnamePort(""fd7a:115c:a1e0:ab12:4843:cd96:626d:335f"", ""9200"") // [fd7a:115c:a1e0:ab12:4843:cd96:626d:335f]:9200
```

Considerations:
* It's called `JoinHostnamePort` instead of `JoinHostPort` to be consistent with the `url.URL.Hostname` method.
* The port is a `string` to be consistent with `url.URL.Port`
* A standalone function that returns a string is consistent with top-level string-only transformers like `JoinPath`, `PathEscape`, `PathUnescape`, `QueryEscape`, `QueryUnescape`.
* What happens if the hostname contains colons but is not an IPv6 or the port is not a valid integer? We'll just concatenate the host and port with a colon in-between even if the result is ambiguous to parse. Alternatively, we could modify the API of `JoinHostnamePort` to return an error, but I personally like the simplicity of an error-less result.

\cc @bradfitz ",1,net url  mention net joinhostport for constructing url url host   in     we add read support for extracting out the hostname and port     however  that api is lacking the ability to write a host port pair  unfortunately  this is not as trivial as concatenating the host and port with a     in between in the case of    which requires wrapping the entire host with     characters     i propose the addition of      go     joinhostnameport joins a hostname and a port  separating them with a colon      if the hostname is an   address  then it is wrapped with brackets      if the port is empty  then the hostname alone is returned   func joinhostnameport hostname  port string  string         example outputs      go  joinhostnameport  carbonite digitalstatic ts net                       carbonite digitalstatic ts net  joinhostnameport  carbonite digitalstatic ts net                    carbonite digitalstatic ts net    joinhostnameport                                                          joinhostnameport                                                         joinhostnameport                                                joinhostnameport                                        considerations     it s called  joinhostnameport  instead of  joinhostport  to be consistent with the  url url hostname  method     the port is a  string  to be consistent with  url url port     a standalone function that returns a string is consistent with top level string only transformers like  joinpath    pathescape    pathunescape    queryescape    queryunescape      what happens if the hostname contains colons but is not an   or the port is not a valid integer  we ll just concatenate the host and port with a colon in between even if the result is ambiguous to parse  alternatively  we could modify the api of  joinhostnameport  to return an error  but i personally like the simplicity of an error less result      cc  bradfitz ,1
640861,20810819191.0,IssuesEvent,2022-03-18 02:18:28,raccoonrick/SOEN341,https://api.github.com/repos/raccoonrick/SOEN341,closed,Signup and try hosting the website on https://www.000webhost.com/,enhancement Priority: Medium,"A free hosting service for our website will be implemented so that everyone can open the website easily.

- Username: Soenify
- Password: Soenify341",1.0,"Signup and try hosting the website on https://www.000webhost.com/ - A free hosting service for our website will be implemented so that everyone can open the website easily.

- Username: Soenify
- Password: Soenify341",0,signup and try hosting the website on     a free hosting service for our website will be implemented so that everyone can open the website easily       username  soenify    password   ,0
40091,6798220601.0,IssuesEvent,2017-11-02 03:55:15,golang/go,https://api.github.com/repos/golang/go,closed,"cmd/go: list -json outputs concatenated JSON documents, not one single one",Documentation,"Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
```
$ go version
go version go1.7.5 linux/amd64
```

### What operating system and processor architecture are you using (`go env`)?
```
$ go env
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/skuznets/Documents/go""
GORACE=""""
GOROOT=""/home/skuznets/.gvm/gos/go1.7.5""
GOTOOLDIR=""/home/skuznets/.gvm/gos/go1.7.5/pkg/tool/linux_amd64""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build979771774=/tmp/go-build -gno-record-gcc-switches""
CXX=""g++""
CGO_ENABLED=""1""
```

### What did you do?
I ran `go list -json` on a project with multiple packages.


### What did you expect to see?
A JSON list:

```json
{
  ""Packages"": [
    {
      ""Dir"": ""whatever""
    },
    {
      ""Dir"": ""whatever/else""
    }
  ]
}
```

### What did you see instead?
Concatenated JSON documents:

```json
{
  ""Dir"": ""whatever""
}
{
  ""Dir"": ""whatever/else""
}
```

",1.0,"cmd/go: list -json outputs concatenated JSON documents, not one single one - Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
```
$ go version
go version go1.7.5 linux/amd64
```

### What operating system and processor architecture are you using (`go env`)?
```
$ go env
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/skuznets/Documents/go""
GORACE=""""
GOROOT=""/home/skuznets/.gvm/gos/go1.7.5""
GOTOOLDIR=""/home/skuznets/.gvm/gos/go1.7.5/pkg/tool/linux_amd64""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build979771774=/tmp/go-build -gno-record-gcc-switches""
CXX=""g++""
CGO_ENABLED=""1""
```

### What did you do?
I ran `go list -json` on a project with multiple packages.


### What did you expect to see?
A JSON list:

```json
{
  ""Packages"": [
    {
      ""Dir"": ""whatever""
    },
    {
      ""Dir"": ""whatever/else""
    }
  ]
}
```

### What did you see instead?
Concatenated JSON documents:

```json
{
  ""Dir"": ""whatever""
}
{
  ""Dir"": ""whatever/else""
}
```

",1,cmd go  list  json outputs concatenated json documents  not one single one   please answer these questions before submitting your issue  thanks         what version of go are you using   go version            go version  go version       linux               what operating system and processor architecture are you using   go env            go env  goarch      gobin     goexe     gohostarch      gohostos  linux   goos  linux   gopath   home skuznets documents go   gorace     goroot   home skuznets  gvm gos         gotooldir   home skuznets  gvm gos       pkg tool linux     cc  gcc   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches   cxx  g     cgo enabled                 what did you do   i ran  go list  json  on a project with multiple packages           what did you expect to see   a json list        json        packages                    dir    whatever                         dir    whatever else                             what did you see instead   concatenated json documents        json        dir    whatever            dir    whatever else             ,1
51022,7656272034.0,IssuesEvent,2018-05-10 15:45:53,golang/go,https://api.github.com/repos/golang/go,closed,net/http/pprof: URL path /debug/pprof does not list all the available endpoints,Documentation NeedsFix help wanted,"Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?

Whatever is in the Docker image `quay.io/coreos/hyperkube:v1.8.7_coreos.0`.

Here is a possibly informative entry from its `/metrics`:

kubernetes_build_info{buildDate=""2018-01-18T00:17:18Z"",compiler=""gc"",gitCommit=""768e049ab5230010251f30475e0e785e2e999566"",gitTreeState=""clean"",gitVersion=""v1.8.7+coreos.0"",goVersion=""go1.8.3"",major=""1"",minor=""8+"",platform=""linux/amd64""}

### Does this issue reproduce with the latest release?

I think it does.

### What operating system and processor architecture are you using (`go env`)?

That is a Docker container image.  I ran it on Ubuntu 16.04.1, on an Intel processor.

### What did you do?

`kubectl get --raw /debug/pprof --server https://10.233.110.91 --insecure-skip-tls-verify`


### What did you expect to see?

I expected to see the complete list of `<foo>` that makes for a valid path `/debug/pprof/<foo>`.

BTW, I can not find the complete list in any one central place.  Different partial lists can be found: as shown here, in https://golang.org/pkg/net/http/pprof/ , in https://raywangblog.wordpress.com/2017/07/16/golang-profiling/ , and in https://blog.golang.org/profiling-go-programs .  In another issue I finally saw a pointer to https://tip.golang.org/doc/diagnostics.html#profiling .  But the full list should be in the main doc as well as what the runtime reports.

### What did you see instead?

Fetching `/debug/pprof` got me the following list of choices:
```
<tr><td align=right>0<td><a href=""block?debug=1"">block</a>
<tr><td align=right>64<td><a href=""goroutine?debug=1"">goroutine</a>
<tr><td align=right>18<td><a href=""heap?debug=1"">heap</a>
<tr><td align=right>0<td><a href=""mutex?debug=1"">mutex</a>
<tr><td align=right>15<td><a href=""threadcreate?debug=1"">threadcreate</a>
```

Astonishingly, `profile` is missing from that list!  So is `trace` (which _is_ mentioned in https://golang.org/pkg/net/http/pprof/ --- which, distressingly, does not say anything about `?debug=1`).",1.0,"net/http/pprof: URL path /debug/pprof does not list all the available endpoints - Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?

Whatever is in the Docker image `quay.io/coreos/hyperkube:v1.8.7_coreos.0`.

Here is a possibly informative entry from its `/metrics`:

kubernetes_build_info{buildDate=""2018-01-18T00:17:18Z"",compiler=""gc"",gitCommit=""768e049ab5230010251f30475e0e785e2e999566"",gitTreeState=""clean"",gitVersion=""v1.8.7+coreos.0"",goVersion=""go1.8.3"",major=""1"",minor=""8+"",platform=""linux/amd64""}

### Does this issue reproduce with the latest release?

I think it does.

### What operating system and processor architecture are you using (`go env`)?

That is a Docker container image.  I ran it on Ubuntu 16.04.1, on an Intel processor.

### What did you do?

`kubectl get --raw /debug/pprof --server https://10.233.110.91 --insecure-skip-tls-verify`


### What did you expect to see?

I expected to see the complete list of `<foo>` that makes for a valid path `/debug/pprof/<foo>`.

BTW, I can not find the complete list in any one central place.  Different partial lists can be found: as shown here, in https://golang.org/pkg/net/http/pprof/ , in https://raywangblog.wordpress.com/2017/07/16/golang-profiling/ , and in https://blog.golang.org/profiling-go-programs .  In another issue I finally saw a pointer to https://tip.golang.org/doc/diagnostics.html#profiling .  But the full list should be in the main doc as well as what the runtime reports.

### What did you see instead?

Fetching `/debug/pprof` got me the following list of choices:
```
<tr><td align=right>0<td><a href=""block?debug=1"">block</a>
<tr><td align=right>64<td><a href=""goroutine?debug=1"">goroutine</a>
<tr><td align=right>18<td><a href=""heap?debug=1"">heap</a>
<tr><td align=right>0<td><a href=""mutex?debug=1"">mutex</a>
<tr><td align=right>15<td><a href=""threadcreate?debug=1"">threadcreate</a>
```

Astonishingly, `profile` is missing from that list!  So is `trace` (which _is_ mentioned in https://golang.org/pkg/net/http/pprof/ --- which, distressingly, does not say anything about `?debug=1`).",1,net http pprof  url path  debug pprof does not list all the available endpoints   please answer these questions before submitting your issue  thanks           what version of go are you using   go version       whatever is in the docker image  quay io coreos hyperkube       coreos        here is a possibly informative entry from its   metrics      kubernetes build info builddate             compiler  gc  gitcommit     gittreestate  clean  gitversion        coreos    goversion         major     minor      platform  linux            does this issue reproduce with the latest release     i think it does         what operating system and processor architecture are you using   go env       that is a docker container image   i ran it on ubuntu        on an intel processor         what did you do      kubectl get   raw  debug pprof   server     insecure skip tls verify           what did you expect to see     i expected to see the complete list of     that makes for a valid path   debug pprof        btw  i can not find the complete list in any one central place   different partial lists can be found  as shown here  in     in     and in      in another issue i finally saw a pointer to      but the full list should be in the main doc as well as what the runtime reports         what did you see instead     fetching   debug pprof  got me the following list of choices             block        goroutine        heap        mutex        threadcreate          astonishingly   profile  is missing from that list   so is  trace   which  is  mentioned in       which  distressingly  does not say anything about   debug     ,1
122849,16362303294.0,IssuesEvent,2021-05-14 11:26:51,Automattic/wp-calypso,https://api.github.com/repos/Automattic/wp-calypso,opened,Blank Canvas: Hide when the eCommerce plan is selected,Design Picker Signup [Type] Task,"### What

### Why

### A/C
- [ ] ...",1.0,"Blank Canvas: Hide when the eCommerce plan is selected - ### What

### Why

### A/C
- [ ] ...",0,blank canvas  hide when the ecommerce plan is selected       what        why        a c         ,0
71177,8632938778.0,IssuesEvent,2018-11-22 12:21:26,MozillaReality/FirefoxReality,https://api.github.com/repos/MozillaReality/FirefoxReality,closed,UR Finding: Users expect to be able to save bookmarks,Draft Design P0,"UR Finding: Users expect to be able to save bookmarks. Explore implementing Favorite/Bookmark support.
",1.0,"UR Finding: Users expect to be able to save bookmarks - UR Finding: Users expect to be able to save bookmarks. Explore implementing Favorite/Bookmark support.
",0,ur finding  users expect to be able to save bookmarks   ur finding  users expect to be able to save bookmarks  explore implementing favorite bookmark support   ,0
1124,2695101449.0,IssuesEvent,2015-04-02 01:13:47,howardabrams/node-mocks-http,https://api.github.com/repos/howardabrams/node-mocks-http,opened,Replace unit testing framework with mocha/chai/sinon/istanbul,build tools enhancement,"## Mocha, Chai, SinonJS and Instanbul
I believe we can improve our unit testing by implementing a more flexible framework, with more readable assertion library, better isolation of the unit of code being tested, and code coverage reporting. I propose that we use Mocha, Chai, SinonJS and Istanbul.

### Testing Framework: Mocha
I know this may be a matter of choice, but I believe `mocha` to be a much better javascript unit testing framework than `nodeunit`. These as just some of my reasons:

- highly extensibly
- multiple reporter options available out of the box
- multiple syntax options available out of the box
- compatible with many existing assertion libraries (I personally prefer `chai`)

### Assertion Library: Chai
Again, this is probably just a matter of style choice, but I just like the readability of Chai's assertions.

### Spy/Mock/Stub Library: SinonJS
Sinon is a great library for spying/mocking/stubbing. It is my go-to library for isolating my unit tests. I think it will be a great addition to our testing framework.

### Code Coverage: Istanbul
I like istanbul because it tracks statement, branch, and function coverage. It also includes both HTML and LCOV reporting out of the box.

---

I think we should implement these before our move to `2.0`. This will be the last minor release before starting work on `2.0`. ",1.0,"Replace unit testing framework with mocha/chai/sinon/istanbul - ## Mocha, Chai, SinonJS and Instanbul
I believe we can improve our unit testing by implementing a more flexible framework, with more readable assertion library, better isolation of the unit of code being tested, and code coverage reporting. I propose that we use Mocha, Chai, SinonJS and Istanbul.

### Testing Framework: Mocha
I know this may be a matter of choice, but I believe `mocha` to be a much better javascript unit testing framework than `nodeunit`. These as just some of my reasons:

- highly extensibly
- multiple reporter options available out of the box
- multiple syntax options available out of the box
- compatible with many existing assertion libraries (I personally prefer `chai`)

### Assertion Library: Chai
Again, this is probably just a matter of style choice, but I just like the readability of Chai's assertions.

### Spy/Mock/Stub Library: SinonJS
Sinon is a great library for spying/mocking/stubbing. It is my go-to library for isolating my unit tests. I think it will be a great addition to our testing framework.

### Code Coverage: Istanbul
I like istanbul because it tracks statement, branch, and function coverage. It also includes both HTML and LCOV reporting out of the box.

---

I think we should implement these before our move to `2.0`. This will be the last minor release before starting work on `2.0`. ",0,replace unit testing framework with mocha chai sinon istanbul      mocha  chai  sinonjs and instanbul  i believe we can improve our unit testing by implementing a more flexible framework  with more readable assertion library  better isolation of the unit of code being tested  and code coverage reporting  i propose that we use mocha  chai  sinonjs and istanbul         testing framework  mocha  i know this may be a matter of choice  but i believe  mocha  to be a much better javascript unit testing framework than  nodeunit   these as just some of my reasons       highly extensibly    multiple reporter options available out of the box    multiple syntax options available out of the box    compatible with many existing assertion libraries  i personally prefer  chai          assertion library  chai  again  this is probably just a matter of style choice  but i just like the readability of chai s assertions         spy mock stub library  sinonjs  sinon is a great library for spying mocking stubbing  it is my go to library for isolating my unit tests  i think it will be a great addition to our testing framework         code coverage  istanbul  i like istanbul because it tracks statement  branch  and function coverage  it also includes both html and lcov reporting out of the box            i think we should implement these before our move to        this will be the last minor release before starting work on        ,0
64135,14657452459.0,IssuesEvent,2020-12-28 15:37:45,fu1771695yongxie/yarn,https://api.github.com/repos/fu1771695yongxie/yarn,opened,CVE-2018-21270 (High) detected in https://source.codeaurora.org/quic/le/platform/external/node/v0.10.44,security vulnerability,"## CVE-2018-21270 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>https://source.codeaurora.org/quic/le/platform/external/node/v0.10.44</b></p></summary>
<p>

<p>Library home page: <a href=https://source.codeaurora.org/quic/le/platform/external/node/>https://source.codeaurora.org/quic/le/platform/external/node/</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/fu1771695yongxie/yarn/commit/b0308a6bc0041ba9a7c0fefc30be7721760dfd37"">b0308a6bc0041ba9a7c0fefc30be7721760dfd37</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (3)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/stringstream/stringstream.js</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/stringstream/stringstream.js</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/stringstream/stringstream.js</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
Versions less than 0.0.6 of the Node.js stringstream module are vulnerable to an out-of-bounds read because of allocation of uninitialized buffers when a number is passed in the input stream (when using Node.js 4.x).

<p>Publish Date: 2020-12-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-21270>CVE-2018-21270</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.1</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: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-21270"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-21270</a></p>
<p>Release Date: 2020-12-03</p>
<p>Fix Resolution: 0.0.6</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2018-21270 (High) detected in https://source.codeaurora.org/quic/le/platform/external/node/v0.10.44 - ## CVE-2018-21270 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>https://source.codeaurora.org/quic/le/platform/external/node/v0.10.44</b></p></summary>
<p>

<p>Library home page: <a href=https://source.codeaurora.org/quic/le/platform/external/node/>https://source.codeaurora.org/quic/le/platform/external/node/</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/fu1771695yongxie/yarn/commit/b0308a6bc0041ba9a7c0fefc30be7721760dfd37"">b0308a6bc0041ba9a7c0fefc30be7721760dfd37</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (3)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/stringstream/stringstream.js</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/stringstream/stringstream.js</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/stringstream/stringstream.js</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
Versions less than 0.0.6 of the Node.js stringstream module are vulnerable to an out-of-bounds read because of allocation of uninitialized buffers when a number is passed in the input stream (when using Node.js 4.x).

<p>Publish Date: 2020-12-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-21270>CVE-2018-21270</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.1</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: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-21270"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-21270</a></p>
<p>Release Date: 2020-12-03</p>
<p>Fix Resolution: 0.0.6</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in        cve       high severity vulnerability     vulnerable library          library home page   a href    found in head commit   a href      found in base branch   master             vulnerable source files                 yarn   tests   fixtures install install bin links eslint node modules stringstream stringstream js       yarn   tests   fixtures install install bin links eslint node modules stringstream stringstream js       yarn   tests   fixtures install install bin links eslint node modules stringstream stringstream js                    vulnerability details         versions less than       of the node js stringstream module are vulnerable to an out of bounds read because of allocation of uninitialized buffers when a number is passed in the input stream  when using node js   x     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  none     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                      step up your open source security game with whitesource    ,0
613909,19101481840.0,IssuesEvent,2021-11-29 23:16:33,Derec-Mods/derecearthmod,https://api.github.com/repos/Derec-Mods/derecearthmod,closed,Furnace Golem destroying paved roads.,bug planned priority: high,"🐛 **Bug Report**
📝 Description
Furnace golems destroy paved roads by walking on them.

🥟 How to reproduce?
Golem walking on paved roads.

🔢 Which version of the mod are you using?
Minecraft Earth Mod 2.5.6.1

",1.0,"Furnace Golem destroying paved roads. - 🐛 **Bug Report**
📝 Description
Furnace golems destroy paved roads by walking on them.

🥟 How to reproduce?
Golem walking on paved roads.

🔢 Which version of the mod are you using?
Minecraft Earth Mod 2.5.6.1

",0,furnace golem destroying paved roads    🐛   bug report    📝 description  furnace golems destroy paved roads by walking on them     🥟 how to reproduce   golem walking on paved roads     🔢 which version of the mod are you using   minecraft earth mod            ,0
50403,26627637200.0,IssuesEvent,2023-01-24 15:35:30,blockscout/blockscout,https://api.github.com/repos/blockscout/blockscout,closed,Inventory tab bad performance for ERC-1155 token,chain: Gnosis :chains: performance,"https://blockscout.com/xdai/mainnet/token/0x761dFbCBa5A43eAF02dc8B2210D83B2ddf9F2E95/inventory

<img width=""1176"" alt=""Screenshot 2021-10-26 at 23 14 38"" src=""https://user-images.githubusercontent.com/4341812/138954068-9594fff0-5abe-4ab3-9af9-d3867d4f8876.png"">

",True,"Inventory tab bad performance for ERC-1155 token - https://blockscout.com/xdai/mainnet/token/0x761dFbCBa5A43eAF02dc8B2210D83B2ddf9F2E95/inventory

<img width=""1176"" alt=""Screenshot 2021-10-26 at 23 14 38"" src=""https://user-images.githubusercontent.com/4341812/138954068-9594fff0-5abe-4ab3-9af9-d3867d4f8876.png"">

",0,inventory tab bad performance for erc   token         img width     alt  screenshot       at        src       ,0
106344,11484953261.0,IssuesEvent,2020-02-11 05:55:50,golang/go,https://api.github.com/repos/golang/go,closed,hash/maphash: Document whether used hash algorithm is stable across future versions,Documentation NeedsFix release-blocker,"The new hash/maphash package in Go 1.14 doesn't make any statement about whether the hash results can differ in future versions or not. 

At worst people will just assume they won't differ and store those hash values expecting to be able to repeat the hashing given the same values and seeds in the future.

I would sleep better when this was made more explicit in the documentation.

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14beta1 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/me/.cache/go-build""
GOENV=""/home/me/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/me/sources/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/snap/go/4962""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/snap/go/4962/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/user/1000/go-build057059169=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?
Read documentation of new package https://tip.golang.org/pkg/hash/maphash/

### What did you expect to see?
Documentation on whether the hash function will always deliver the same hash across all Go 1 versions in the future given the same seed and bytes to be hashed.

### What did you see instead?
No statement whether I can assume this or not.",1.0,"hash/maphash: Document whether used hash algorithm is stable across future versions - The new hash/maphash package in Go 1.14 doesn't make any statement about whether the hash results can differ in future versions or not. 

At worst people will just assume they won't differ and store those hash values expecting to be able to repeat the hashing given the same values and seeds in the future.

I would sleep better when this was made more explicit in the documentation.

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14beta1 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/me/.cache/go-build""
GOENV=""/home/me/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/me/sources/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/snap/go/4962""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/snap/go/4962/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/user/1000/go-build057059169=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?
Read documentation of new package https://tip.golang.org/pkg/hash/maphash/

### What did you expect to see?
Documentation on whether the hash function will always deliver the same hash across all Go 1 versions in the future given the same seed and bytes to be hashed.

### What did you see instead?
No statement whether I can assume this or not.",1,hash maphash  document whether used hash algorithm is stable across future versions   the new hash maphash package in go     doesn t make any statement about whether the hash results can differ in future versions or not      at worst people will just assume they won t differ and store those hash values expecting to be able to repeat the hashing given the same values and seeds in the future     i would sleep better when this was made more explicit in the documentation         what version of go are you using   go version            go version  go version     linux             does this issue reproduce with the latest release   yes          what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   home me  cache go build   goenv   home me  config go env   goexe     goflags     gohostarch      gohostos  linux   goinsecure     gonoproxy     gonosumdb     goos  linux   gopath   home me sources go   goprivate     goproxy     goroot   snap go     gosumdb  sum golang org   gotmpdir     gotooldir   snap go   pkg tool linux     gccgo  gccgo   ar  ar   cc  gcc   cxx  g     cgo enabled      gomod     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp user   go    tmp go build  gno record gcc switches             what did you do   read documentation of new package          what did you expect to see   documentation on whether the hash function will always deliver the same hash across all go   versions in the future given the same seed and bytes to be hashed         what did you see instead   no statement whether i can assume this or not ,1
276884,8614393438.0,IssuesEvent,2018-11-19 17:21:36,actnforchildren/mental_health_app,https://api.github.com/repos/actnforchildren/mental_health_app,reopened,Copy change for Help page,enhancement priority-1,"Content change for Help page Childline from ""Speak to an adult that you trust, if you would like more advice on how you are feeling."" to ""If you don't have anyone you can talk to right now, and you need immediate support with how you're feeling.""",1.0,"Copy change for Help page - Content change for Help page Childline from ""Speak to an adult that you trust, if you would like more advice on how you are feeling."" to ""If you don't have anyone you can talk to right now, and you need immediate support with how you're feeling.""",0,copy change for help page   content change for help page childline from  speak to an adult that you trust  if you would like more advice on how you are feeling   to  if you don t have anyone you can talk to right now  and you need immediate support with how you re feeling  ,0
174045,14445062248.0,IssuesEvent,2020-12-07 22:17:12,golang/go,https://api.github.com/repos/golang/go,closed,reflect: update StructTag documentation to describe multiple space-separated keys,Documentation NeedsFix okay-after-beta1 release-blocker,"Proposal #40281 was accepted and implemented for Go 1.16 in [CL 248341](https://golang.org/cl/248341). It seems the public documentation of [`reflect.StructTag`](https://tip.golang.org/pkg/reflect/#StructTag) was not updated as part of the implementation. It still says:

> Each key is a non-empty string consisting of non-control characters other than space (U+0020 ' '), quote (U+0022 '""'), and colon (U+003A ':').

That is no longer accurate/complete. It needs to be updated to describe the new behavior.

CC @bynov, @deven96, @rsc, @ianlancetaylor.",1.0,"reflect: update StructTag documentation to describe multiple space-separated keys - Proposal #40281 was accepted and implemented for Go 1.16 in [CL 248341](https://golang.org/cl/248341). It seems the public documentation of [`reflect.StructTag`](https://tip.golang.org/pkg/reflect/#StructTag) was not updated as part of the implementation. It still says:

> Each key is a non-empty string consisting of non-control characters other than space (U+0020 ' '), quote (U+0022 '""'), and colon (U+003A ':').

That is no longer accurate/complete. It needs to be updated to describe the new behavior.

CC @bynov, @deven96, @rsc, @ianlancetaylor.",1,reflect  update structtag documentation to describe multiple space separated keys   proposal    was accepted and implemented for go     in     it seems the public documentation of     was not updated as part of the implementation  it still says       each key is a non empty string consisting of non control characters other than space  u         quote  u         and colon  u            that is no longer accurate complete  it needs to be updated to describe the new behavior     cc  bynov       rsc   ianlancetaylor ,1
218745,24395953764.0,IssuesEvent,2022-10-04 19:16:48,bcgov/bc-wallet-mobile,https://api.github.com/repos/bcgov/bc-wallet-mobile,closed,Biometrics with App PIN fallback,story component:security,"As a user I want to be able to choose to use biometrics or my app PIN to enter my digital wallet so that when I'm met with a situation where I can't use my fingerprint or face (wearing gloves, mask, etc,) I can still enter into my wallet without any issues

[See Biometrics and App PIN fallback flow and behaviour](https://app.mural.co/t/digitalidentityandtrust0399/m/digitalidentityandtrust0399/1661808127835/fad19a32b9a164538e74a1c6c4a9897152a2ec5a?wid=0-1661813415640)

### Acceptance Criteria
Given biometrics is turned on 
And the Holder has opened the app
And they are presented with biometrics authentication
When the Holder selects ""cancel""
Then they are prompted to enter their wallet PIN
And they are prompted with the option to enter using their biometrics

Given the Holder has biometrics enabled to access their wallet
When the Holder has selected to enter using their biometrics
Then biometrics authentication is prompted




",True,"Biometrics with App PIN fallback - As a user I want to be able to choose to use biometrics or my app PIN to enter my digital wallet so that when I'm met with a situation where I can't use my fingerprint or face (wearing gloves, mask, etc,) I can still enter into my wallet without any issues

[See Biometrics and App PIN fallback flow and behaviour](https://app.mural.co/t/digitalidentityandtrust0399/m/digitalidentityandtrust0399/1661808127835/fad19a32b9a164538e74a1c6c4a9897152a2ec5a?wid=0-1661813415640)

### Acceptance Criteria
Given biometrics is turned on 
And the Holder has opened the app
And they are presented with biometrics authentication
When the Holder selects ""cancel""
Then they are prompted to enter their wallet PIN
And they are prompted with the option to enter using their biometrics

Given the Holder has biometrics enabled to access their wallet
When the Holder has selected to enter using their biometrics
Then biometrics authentication is prompted




",0,biometrics with app pin fallback   as a user i want to be able to choose to use biometrics or my app pin to enter my digital wallet so that when i m met with a situation where i can t use my fingerprint or face  wearing gloves  mask  etc   i can still enter into my wallet without any issues           acceptance criteria given biometrics is turned on  and the holder has opened the app and they are presented with biometrics authentication when the holder selects  cancel  then they are prompted to enter their wallet pin and they are prompted with the option to enter using their biometrics  given the holder has biometrics enabled to access their wallet when the holder has selected to enter using their biometrics then biometrics authentication is prompted     ,0
97937,20593193833.0,IssuesEvent,2022-03-05 04:36:27,WordPress/openverse-frontend,https://api.github.com/repos/WordPress/openverse-frontend,closed,Add types to `utils/case.js`,🟩 priority: low ✨ goal: improvement 💻 aspect: code,"## Description
<!-- Describe the feature and how it solves the problem. -->
Add type checking to `case.js`. This module has one external dependency which already publishes types. Make sure to add it to `tsconfig.json`'s `include` list.

## Additional context
<!-- Add any other context about the feature here; or delete the section entirely. -->
Part of an ongoing effort to add type checking to parts of the project that can be type checked.

## Implementation
<!-- Replace the [ ] with [x] to check the box. -->
- [ ] 🙋 I would be interested in implementing this feature.
",1.0,"Add types to `utils/case.js` - ## Description
<!-- Describe the feature and how it solves the problem. -->
Add type checking to `case.js`. This module has one external dependency which already publishes types. Make sure to add it to `tsconfig.json`'s `include` list.

## Additional context
<!-- Add any other context about the feature here; or delete the section entirely. -->
Part of an ongoing effort to add type checking to parts of the project that can be type checked.

## Implementation
<!-- Replace the [ ] with [x] to check the box. -->
- [ ] 🙋 I would be interested in implementing this feature.
",0,add types to  utils case js       description     add type checking to  case js   this module has one external dependency which already publishes types  make sure to add it to  tsconfig json  s  include  list        additional context     part of an ongoing effort to add type checking to parts of the project that can be type checked        implementation         🙋 i would be interested in implementing this feature   ,0
75480,9856121863.0,IssuesEvent,2019-06-19 21:11:16,golang/go,https://api.github.com/repos/golang/go,closed,wiki: CodeReviewComments#NamedResultParameters,Documentation NeedsDecision,"> On the other hand, [...] if the meaning of a result isn't clear from context, adding names may be useful in some contexts. 

In general, this will almost always be true. Humans are extremely bad at assessing how obvious an inference is if they already know the fact to be inferred. This is a special case of the [illusion of transparency](https://en.wikipedia.org/wiki/Illusion_of_transparency). In general, the meaning of a result isn't clear from context even if it feels to the author like it's extremely clear from context.

Because of this, the advice given in this section is harmful in most cases.",1.0,"wiki: CodeReviewComments#NamedResultParameters - > On the other hand, [...] if the meaning of a result isn't clear from context, adding names may be useful in some contexts. 

In general, this will almost always be true. Humans are extremely bad at assessing how obvious an inference is if they already know the fact to be inferred. This is a special case of the [illusion of transparency](https://en.wikipedia.org/wiki/Illusion_of_transparency). In general, the meaning of a result isn't clear from context even if it feels to the author like it's extremely clear from context.

Because of this, the advice given in this section is harmful in most cases.",1,wiki  codereviewcomments namedresultparameters     on the other hand    if the meaning of a result isn t clear from context  adding names may be useful in some contexts      in general  this will almost always be true  humans are extremely bad at assessing how obvious an inference is if they already know the fact to be inferred  this is a special case of the     in general  the meaning of a result isn t clear from context even if it feels to the author like it s extremely clear from context     because of this  the advice given in this section is harmful in most cases ,1
272950,20764837320.0,IssuesEvent,2022-03-15 19:38:09,golang/go,https://api.github.com/repos/golang/go,closed,x/website: FAQ needs to have a preamble re: generics,Documentation NeedsFix early-in-cycle release-blocker,The [FAQ](https://go.dev/doc/faq) need to be updated with a preamble/disclaimer as it was not written with generics in mind.,1.0,x/website: FAQ needs to have a preamble re: generics - The [FAQ](https://go.dev/doc/faq) need to be updated with a preamble/disclaimer as it was not written with generics in mind.,1,x website  faq needs to have a preamble re  generics   the     need to be updated with a preamble disclaimer as it was not written with generics in mind ,1
173136,14403476356.0,IssuesEvent,2020-12-03 16:06:11,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.16: document net/smtp changes for Go 1.16,Documentation NeedsInvestigation help wanted release-blocker,"As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

<dl id=""net/smtp""><dt><a href=""/pkg/net/smtp/"">net/smtp</a></dt>
  <dd>
    <p><!-- CL 247257 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/247257"">https://golang.org/cl/247257</a>: adds support for the SMTPUTF8 extension
    </p>
  </dd>
</dl><!-- net/smtp -->

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.",1.0,"doc/go1.16: document net/smtp changes for Go 1.16 - As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

<dl id=""net/smtp""><dt><a href=""/pkg/net/smtp/"">net/smtp</a></dt>
  <dd>
    <p><!-- CL 247257 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/247257"">https://golang.org/cl/247257</a>: adds support for the SMTPUTF8 extension
    </p>
  </dd>
</dl><!-- net/smtp -->

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.",1,doc      document net smtp changes for go       as of filing this issue  the     contained the following html        net smtp                        todo    a href    adds support for the   extension                           per     it s a release blocker for go     beta   to have a complete draft of the eventual release notes  and so the todo needs to be resolved     a sequence of steps to resolve this issue may be        come up with a draft release note entry in this issue  then move the issue to needsfix state      send a cl with  doc           and include  for     fixes   this issue    in the body ,1
295950,25516951590.0,IssuesEvent,2022-11-28 17:04:13,void-linux/void-packages,https://api.github.com/repos/void-linux/void-packages,opened,elogind system-sleep scripts location documentation issue,bug needs-testing,"### Is this a new report?

Yes

### System Info

Void 6.0.10_1 x86_64 AuthenticAMD uptodate rrmFFFF

### Package(s) Affected

elogind-246.10_2

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

No, it's Void Linux specific.

### Expected behaviour

Void (correctly!) configures /etc/elogind/system-sleep as the location for suspend/hibernate pre/post scripts. However, documentation does not indicate this. Upstream docs reference /lib64/elogind/system-sleep as the location. This leads to confusion with users.

I think /etc/elogind/system-sleep is correct, however Void docs should have a mention about this location.

### Actual behaviour

N/A, issue made by request of @paper42 (paper_ on irc).

### Steps to reproduce

1. install elogind
2. try to place a script in /usr/lib/elogind/system-sleep
3. observe it not working
4. place script in /etc/elogind/system-sleep
5. it works
6. wish for better docs",1.0,"elogind system-sleep scripts location documentation issue - ### Is this a new report?

Yes

### System Info

Void 6.0.10_1 x86_64 AuthenticAMD uptodate rrmFFFF

### Package(s) Affected

elogind-246.10_2

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

No, it's Void Linux specific.

### Expected behaviour

Void (correctly!) configures /etc/elogind/system-sleep as the location for suspend/hibernate pre/post scripts. However, documentation does not indicate this. Upstream docs reference /lib64/elogind/system-sleep as the location. This leads to confusion with users.

I think /etc/elogind/system-sleep is correct, however Void docs should have a mention about this location.

### Actual behaviour

N/A, issue made by request of @paper42 (paper_ on irc).

### Steps to reproduce

1. install elogind
2. try to place a script in /usr/lib/elogind/system-sleep
3. observe it not working
4. place script in /etc/elogind/system-sleep
5. it works
6. wish for better docs",0,elogind system sleep scripts location documentation issue       is this a new report   yes      system info  void             authenticamd uptodate rrmffff      package s  affected  elogind            does a report exist for this bug with the project s home  upstream  and or another distro   no  it s void linux specific       expected behaviour  void  correctly   configures  etc elogind system sleep as the location for suspend hibernate pre post scripts  however  documentation does not indicate this  upstream docs reference    elogind system sleep as the location  this leads to confusion with users     i think  etc elogind system sleep is correct  however void docs should have a mention about this location       actual behaviour  n a  issue made by request of     paper  on irc        steps to reproduce     install elogind     try to place a script in  usr lib elogind system sleep     observe it not working     place script in  etc elogind system sleep     it works     wish for better docs,0
43381,7044306113.0,IssuesEvent,2017-12-31 21:50:37,golang/go,https://api.github.com/repos/golang/go,closed,x/crypto/bn256: document that bn256 is weak,Documentation,"Due to recent improvements in calculating discrete logs [1], the BN-256 curve provides less than 128 bits of security. One estimate is that BN-256 provides closer to 96 bits of security. Trevor wrote a good summary of the situation [2]. The package comment for x/crypto/bn256 should note this weakness.

[1] https://eprint.iacr.org/2015/1027
[2] https://moderncrypto.org/mail-archive/curves/2016/000740.html

cc @agl @trevp",1.0,"x/crypto/bn256: document that bn256 is weak - Due to recent improvements in calculating discrete logs [1], the BN-256 curve provides less than 128 bits of security. One estimate is that BN-256 provides closer to 96 bits of security. Trevor wrote a good summary of the situation [2]. The package comment for x/crypto/bn256 should note this weakness.

[1] https://eprint.iacr.org/2015/1027
[2] https://moderncrypto.org/mail-archive/curves/2016/000740.html

cc @agl @trevp",1,x crypto    document that   is weak   due to recent improvements in calculating discrete logs    the bn   curve provides less than   bits of security  one estimate is that bn   provides closer to   bits of security  trevor wrote a good summary of the situation    the package comment for x crypto   should note this weakness                 cc  agl  trevp,1
158620,12420763281.0,IssuesEvent,2020-05-23 13:40:45,linq2db/linq2db,https://api.github.com/repos/linq2db/linq2db,closed,Association using a query expression throws a cast exception when using an IQueryable property.,status: has-tests type: bug,"I'm attempting to add additional query constraints to an association via a query expression. Additionally, when using this association in a query, I would like to perform a .Any() linq query upon this association.

The following configuration works:
```
Mapping:
builder
	.Entity<Entity>()
	.HasTableName(""Entity"")
	.HasPrimaryKey(x => Sql.Property<long>(x, ""Id""))
	.Association(x => Sql.Property<IQueryable<Relationship>>(x, ""relationship""),
		e => e.Id, r => r.EntityId);
```

```
Query:
var result1 = entity
	.Where(t => Sql.Property<IQueryable<Relationship>>(t, ""relationship"").Any())
	.ToList();

SQL:
SELECT
	[t].[Id],
	[t].[Deleted],
	....
FROM
	[Entity] [t]
WHERE
	EXISTS(
		SELECT
			*
		FROM
			[Relationship] [c_1]
		WHERE
			[t].[Id] = [c_1].[EntityId]
	)
```

The following configuration fails with an exception when using the same query from above:
```
builder
	.Entity<Entity>()
	.HasTableName(""Entity"")
	.HasPrimaryKey(x => Sql.Property<long>(x, ""Id""))
	.Association(x => Sql.Property<IQueryable<Relationship>>(x, ""relationship""),
		(e, db) => db.GetTable<Relationship>()
		    .Where(r => r.Deleted == false && r.EntityId == e.Id));
```

If you are seeing an exception, include the full exceptions details (message and stack trace).

```
System.ArgumentException: 'Expression of type 'Linq2DBTest.Relationship' cannot be used for parameter of type 'System.Linq.IQueryable`1[Linq2DBTest.Relationship]' of method 'Boolean Any[Relationship](System.Linq.IQueryable`1[Linq2DBTest.Relationship])'
Parameter name: arg0'
```

### Environment details
linq2db version: *2.7.0*
Database Server: *E.g. SQL Server 2017*
Database Provider: *E.g. SqlClient*
Operating system: *E.g. Windows 10*
Framework version: *.NET Core 2.2*
",1.0,"Association using a query expression throws a cast exception when using an IQueryable property. - I'm attempting to add additional query constraints to an association via a query expression. Additionally, when using this association in a query, I would like to perform a .Any() linq query upon this association.

The following configuration works:
```
Mapping:
builder
	.Entity<Entity>()
	.HasTableName(""Entity"")
	.HasPrimaryKey(x => Sql.Property<long>(x, ""Id""))
	.Association(x => Sql.Property<IQueryable<Relationship>>(x, ""relationship""),
		e => e.Id, r => r.EntityId);
```

```
Query:
var result1 = entity
	.Where(t => Sql.Property<IQueryable<Relationship>>(t, ""relationship"").Any())
	.ToList();

SQL:
SELECT
	[t].[Id],
	[t].[Deleted],
	....
FROM
	[Entity] [t]
WHERE
	EXISTS(
		SELECT
			*
		FROM
			[Relationship] [c_1]
		WHERE
			[t].[Id] = [c_1].[EntityId]
	)
```

The following configuration fails with an exception when using the same query from above:
```
builder
	.Entity<Entity>()
	.HasTableName(""Entity"")
	.HasPrimaryKey(x => Sql.Property<long>(x, ""Id""))
	.Association(x => Sql.Property<IQueryable<Relationship>>(x, ""relationship""),
		(e, db) => db.GetTable<Relationship>()
		    .Where(r => r.Deleted == false && r.EntityId == e.Id));
```

If you are seeing an exception, include the full exceptions details (message and stack trace).

```
System.ArgumentException: 'Expression of type 'Linq2DBTest.Relationship' cannot be used for parameter of type 'System.Linq.IQueryable`1[Linq2DBTest.Relationship]' of method 'Boolean Any[Relationship](System.Linq.IQueryable`1[Linq2DBTest.Relationship])'
Parameter name: arg0'
```

### Environment details
linq2db version: *2.7.0*
Database Server: *E.g. SQL Server 2017*
Database Provider: *E.g. SqlClient*
Operating system: *E.g. Windows 10*
Framework version: *.NET Core 2.2*
",0,association using a query expression throws a cast exception when using an iqueryable property    i m attempting to add additional query constraints to an association via a query expression  additionally  when using this association in a query  i would like to perform a  any   linq query upon this association     the following configuration works        mapping   builder  	 entity     	 hastablename  entity    	 hasprimarykey x    sql property  x   id     	 association x    sql property  x   relationship     		e    e id  r    r entityid                query   var     entity  	 where t    sql property  t   relationship   any     	 tolist       sql   select  	      	      	      from  	     where  	exists   		select  			   		from  			     		where  			           	          the following configuration fails with an exception when using the same query from above        builder  	 entity     	 hastablename  entity    	 hasprimarykey x    sql property  x   id     	 association x    sql property  x   relationship     		 e  db     db gettable     		     where r    r deleted    false    r entityid    e id            if you are seeing an exception  include the full exceptions details  message and stack trace           system argumentexception   expression of type    relationship  cannot be used for parameter of type  system linq iqueryable     of method  boolean any  system linq iqueryable       parameter name                 environment details    version           database server   e g  sql server     database provider   e g  sqlclient   operating system   e g  windows     framework version    net core       ,0
186264,6734774346.0,IssuesEvent,2017-10-18 19:14:55,openshift/origin-web-catalog,https://api.github.com/repos/openshift/origin-web-catalog,closed,Builder dialog should not request all service classes and plans,kind/bug priority/P1,"Every time we open the create from builder dialog, all service classes and plans are requested again. This is potentially a lot of data that we've already requested to build the services view. We should change this logic to pass the values in, or possibly just disable it for now since pod presets are not enabled.

https://github.com/openshift/origin-web-catalog/blob/be6df500e9c61d5787483e2d67e36bac4f92ac7a/src/components/create-from-builder/create-from-builder.controller.ts#L409-L429

@jeff-phillips-18 @jwforres ",1.0,"Builder dialog should not request all service classes and plans - Every time we open the create from builder dialog, all service classes and plans are requested again. This is potentially a lot of data that we've already requested to build the services view. We should change this logic to pass the values in, or possibly just disable it for now since pod presets are not enabled.

https://github.com/openshift/origin-web-catalog/blob/be6df500e9c61d5787483e2d67e36bac4f92ac7a/src/components/create-from-builder/create-from-builder.controller.ts#L409-L429

@jeff-phillips-18 @jwforres ",0,builder dialog should not request all service classes and plans   every time we open the create from builder dialog  all service classes and plans are requested again  this is potentially a lot of data that we ve already requested to build the services view  we should change this logic to pass the values in  or possibly just disable it for now since pod presets are not enabled           jeff phillips    jwforres ,0
577194,17105065408.0,IssuesEvent,2021-07-09 16:24:39,Earthcomputer/multiconnect,https://api.github.com/repos/Earthcomputer/multiconnect,closed,Multiconnect allows 1.17 clients to leash squids,bug priority: medium,"You can leash squids in older versions in 1.17. Doing so doesn't actually consumes the lead, or move the squid. It just removes a lead and draws a ghost lead that doesn't do anything and can stretch infinite length. The lead is only removed client side and thus updating the stack visually gets the lead back.",1.0,"Multiconnect allows 1.17 clients to leash squids - You can leash squids in older versions in 1.17. Doing so doesn't actually consumes the lead, or move the squid. It just removes a lead and draws a ghost lead that doesn't do anything and can stretch infinite length. The lead is only removed client side and thus updating the stack visually gets the lead back.",0,multiconnect allows     clients to leash squids   you can leash squids in older versions in      doing so doesn t actually consumes the lead  or move the squid  it just removes a lead and draws a ghost lead that doesn t do anything and can stretch infinite length  the lead is only removed client side and thus updating the stack visually gets the lead back ,0
33024,6150475087.0,IssuesEvent,2017-06-27 22:42:12,golang/go,https://api.github.com/repos/golang/go,closed,cmd/compile: intermittent test failure on gonum suite with testing/quick,Documentation NeedsFix,"Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
go1.9beta2  (go version devel +eab99a8 Mon Jun 26 21:12:22 2017 +0000 darwin/amd64)

I confirmed this bug does not exist in go1.8.3

### What operating system and processor architecture are you using (`go env`)?
brendan:~$ go env
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/brendan/Documents/othergo""
GORACE=""""
GOROOT=""/Users/brendan/gover/go""
GOTOOLDIR=""/Users/brendan/gover/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/l6/mhj4qjrj4437b_lgfz9pm1rw0000gn/T/go-build536430216=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""

### What did you do?

````
go get -u -t gonum.org/v1/gonum/blas/gonum
cd $GOPATH/src/gonum.org/v1/gonum/blas/gonum/internal/math32
go test ./...
````

Approximately 1 in every 5 runs, this returns
````
brendan:~/Documents/othergo/src/gonum.org/v1/gonum/blas/gonum/internal/math32$ go test
--- FAIL: TestHypot (0.00s)
	math_test.go:46: #91: failed on input struct { X float32; Y float32 }{X:2.214908e+38, Y:-1.091827e+38}
FAIL
exit status 1
````

I ran this ~20 times with go1.8.3, and never saw this test failure (plus, we've been running travis on all of our commits with go1.8.3 and have not seen this failure).

The function in question, `math32.Hypot` calls `math32.Sqrt`, which is implemented in assembly. This can be disabled with the ""noasm"" tag, and the failure still occurs. 
````
brendan:~/Documents/othergo/src/gonum.org/v1/gonum/blas/gonum/internal/math32$ go test -tags=noasm
--- FAIL: TestHypot (0.00s)
	math_test.go:46: #16: failed on input struct { X float32; Y float32 }{X:-1.917559e+38, Y:-3.838481e+36}
FAIL
exit status 1
````

The release notes say there is a change to the `int64` and `uint64` random number generation, but as best as I can tell the source has not changed for `float32` generation. ",1.0,"cmd/compile: intermittent test failure on gonum suite with testing/quick - Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
go1.9beta2  (go version devel +eab99a8 Mon Jun 26 21:12:22 2017 +0000 darwin/amd64)

I confirmed this bug does not exist in go1.8.3

### What operating system and processor architecture are you using (`go env`)?
brendan:~$ go env
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/brendan/Documents/othergo""
GORACE=""""
GOROOT=""/Users/brendan/gover/go""
GOTOOLDIR=""/Users/brendan/gover/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/l6/mhj4qjrj4437b_lgfz9pm1rw0000gn/T/go-build536430216=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""

### What did you do?

````
go get -u -t gonum.org/v1/gonum/blas/gonum
cd $GOPATH/src/gonum.org/v1/gonum/blas/gonum/internal/math32
go test ./...
````

Approximately 1 in every 5 runs, this returns
````
brendan:~/Documents/othergo/src/gonum.org/v1/gonum/blas/gonum/internal/math32$ go test
--- FAIL: TestHypot (0.00s)
	math_test.go:46: #91: failed on input struct { X float32; Y float32 }{X:2.214908e+38, Y:-1.091827e+38}
FAIL
exit status 1
````

I ran this ~20 times with go1.8.3, and never saw this test failure (plus, we've been running travis on all of our commits with go1.8.3 and have not seen this failure).

The function in question, `math32.Hypot` calls `math32.Sqrt`, which is implemented in assembly. This can be disabled with the ""noasm"" tag, and the failure still occurs. 
````
brendan:~/Documents/othergo/src/gonum.org/v1/gonum/blas/gonum/internal/math32$ go test -tags=noasm
--- FAIL: TestHypot (0.00s)
	math_test.go:46: #16: failed on input struct { X float32; Y float32 }{X:-1.917559e+38, Y:-3.838481e+36}
FAIL
exit status 1
````

The release notes say there is a change to the `int64` and `uint64` random number generation, but as best as I can tell the source has not changed for `float32` generation. ",1,cmd compile  intermittent test failure on gonum suite with testing quick   please answer these questions before submitting your issue  thanks         what version of go are you using   go version           go version devel    mon jun              darwin       i confirmed this bug does not exist in              what operating system and processor architecture are you using   go env     brendan    go env  goarch      gobin     goexe     gohostarch      gohostos  darwin   goos  darwin   gopath   users brendan documents othergo   gorace     goroot   users brendan gover go   gotooldir   users brendan gover go pkg tool darwin     gccgo  gccgo   cc  clang   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders       t go    tmp go build  gno record gcc switches  fno common   cxx  clang     cgo enabled      cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config         what did you do           go get  u  t gonum org   gonum blas gonum  cd  gopath src gonum org   gonum blas gonum internal    go test                approximately   in every   runs  this returns        brendan   documents othergo src gonum org   gonum blas gonum internal    go test      fail  testhypot        	math test go        failed on input struct   x    y     x        y          fail  exit status            i ran this    times with        and never saw this test failure  plus  we ve been running travis on all of our commits with       and have not seen this failure      the function in question     hypot  calls    sqrt   which is implemented in assembly  this can be disabled with the  noasm  tag  and the failure still occurs          brendan   documents othergo src gonum org   gonum blas gonum internal    go test  tags noasm      fail  testhypot        	math test go        failed on input struct   x    y     x         y          fail  exit status            the release notes say there is a change to the     and     random number generation  but as best as i can tell the source has not changed for     generation  ,1
254754,27416975664.0,IssuesEvent,2023-03-01 14:24:05,Vonage-Community/tutorials-client_sdk-ios-android-js,https://api.github.com/repos/Vonage-Community/tutorials-client_sdk-ios-android-js,closed,android-core-0.1.4.pom: 1 vulnerabilities (highest severity is: 7.5),security vulnerability,"<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>android-core-0.1.4.pom</b></p></summary>

<p></p>
<p>Path to dependency file: /phone-to-app-kotlin/phone-to-app/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/io.socket/socket.io-client/1.0.0/28dde99672ed62a85e85a7df096c6bec698785b4/socket.io-client-1.0.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/io.socket/socket.io-client/1.0.0/28dde99672ed62a85e85a7df096c6bec698785b4/socket.io-client-1.0.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/io.socket/socket.io-client/1.0.0/28dde99672ed62a85e85a7df096c6bec698785b4/socket.io-client-1.0.0.jar</p>
<p>


<p>Found in HEAD commit: <a href=""https://github.com/Vonage-Community/tutorials-client_sdk-ios-android-js/commit/28aa2a86075c6cb1200ba29ca5d82d9b9437e33b"">28aa2a86075c6cb1200ba29ca5d82d9b9437e33b</a></p></details>

## Vulnerabilities

| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (android-core version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2022-25867](https://www.mend.io/vulnerability-database/CVE-2022-25867) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | socket.io-client-1.0.0.jar | Transitive | N/A* | &#10060; |
<p>*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the section ""Details"" below to see if there is a version of transitive dependency where vulnerability is fixed.</p>

## Details

<details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-25867</summary>


###  Vulnerable Library - <b>socket.io-client-1.0.0.jar</b></p>

<p>Socket.IO Client Library for Java</p>
<p>Library home page: <a href=""https://github.com/socketio/socket.io-client-java"">https://github.com/socketio/socket.io-client-java</a></p>
<p>Path to dependency file: /phone-to-app-kotlin/phone-to-app/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/io.socket/socket.io-client/1.0.0/28dde99672ed62a85e85a7df096c6bec698785b4/socket.io-client-1.0.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/io.socket/socket.io-client/1.0.0/28dde99672ed62a85e85a7df096c6bec698785b4/socket.io-client-1.0.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/io.socket/socket.io-client/1.0.0/28dde99672ed62a85e85a7df096c6bec698785b4/socket.io-client-1.0.0.jar</p>
<p>

Dependency Hierarchy:
  - android-core-0.1.4.pom (Root Library)
    - :x: **socket.io-client-1.0.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/Vonage-Community/tutorials-client_sdk-ios-android-js/commit/28aa2a86075c6cb1200ba29ca5d82d9b9437e33b"">28aa2a86075c6cb1200ba29ca5d82d9b9437e33b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
The package io.socket:socket.io-client before 2.0.1 are vulnerable to NULL Pointer Dereference when parsing a packet with with invalid payload format.

<p>Publish Date: 2022-08-02
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-25867>CVE-2022-25867</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25867"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25867</a></p>
<p>Release Date: 2022-08-02</p>
<p>Fix Resolution: io.socket:socket.io-client:2.0.1</p>

</p>

<p></p>

</details>",True,"android-core-0.1.4.pom: 1 vulnerabilities (highest severity is: 7.5) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>android-core-0.1.4.pom</b></p></summary>

<p></p>
<p>Path to dependency file: /phone-to-app-kotlin/phone-to-app/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/io.socket/socket.io-client/1.0.0/28dde99672ed62a85e85a7df096c6bec698785b4/socket.io-client-1.0.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/io.socket/socket.io-client/1.0.0/28dde99672ed62a85e85a7df096c6bec698785b4/socket.io-client-1.0.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/io.socket/socket.io-client/1.0.0/28dde99672ed62a85e85a7df096c6bec698785b4/socket.io-client-1.0.0.jar</p>
<p>


<p>Found in HEAD commit: <a href=""https://github.com/Vonage-Community/tutorials-client_sdk-ios-android-js/commit/28aa2a86075c6cb1200ba29ca5d82d9b9437e33b"">28aa2a86075c6cb1200ba29ca5d82d9b9437e33b</a></p></details>

## Vulnerabilities

| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (android-core version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2022-25867](https://www.mend.io/vulnerability-database/CVE-2022-25867) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | socket.io-client-1.0.0.jar | Transitive | N/A* | &#10060; |
<p>*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the section ""Details"" below to see if there is a version of transitive dependency where vulnerability is fixed.</p>

## Details

<details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-25867</summary>


###  Vulnerable Library - <b>socket.io-client-1.0.0.jar</b></p>

<p>Socket.IO Client Library for Java</p>
<p>Library home page: <a href=""https://github.com/socketio/socket.io-client-java"">https://github.com/socketio/socket.io-client-java</a></p>
<p>Path to dependency file: /phone-to-app-kotlin/phone-to-app/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/io.socket/socket.io-client/1.0.0/28dde99672ed62a85e85a7df096c6bec698785b4/socket.io-client-1.0.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/io.socket/socket.io-client/1.0.0/28dde99672ed62a85e85a7df096c6bec698785b4/socket.io-client-1.0.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/io.socket/socket.io-client/1.0.0/28dde99672ed62a85e85a7df096c6bec698785b4/socket.io-client-1.0.0.jar</p>
<p>

Dependency Hierarchy:
  - android-core-0.1.4.pom (Root Library)
    - :x: **socket.io-client-1.0.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/Vonage-Community/tutorials-client_sdk-ios-android-js/commit/28aa2a86075c6cb1200ba29ca5d82d9b9437e33b"">28aa2a86075c6cb1200ba29ca5d82d9b9437e33b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
The package io.socket:socket.io-client before 2.0.1 are vulnerable to NULL Pointer Dereference when parsing a packet with with invalid payload format.

<p>Publish Date: 2022-08-02
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-25867>CVE-2022-25867</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25867"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25867</a></p>
<p>Release Date: 2022-08-02</p>
<p>Fix Resolution: io.socket:socket.io-client:2.0.1</p>

</p>

<p></p>

</details>",0,android core       pom    vulnerabilities  highest severity is             vulnerable library    android core       pom         path to dependency file   phone to app kotlin phone to app app build gradle   path to vulnerable library   home wss scanner  gradle caches modules   files     io socket socket io client         socket io client       jar  home wss scanner  gradle caches modules   files     io socket socket io client         socket io client       jar  home wss scanner  gradle caches modules   files     io socket socket io client         socket io client       jar       found in head commit   a href        vulnerabilities    cve   severity     cvss   dependency   type   fixed in  android core version    remediation available                                                                                             high         socket io client       jar   transitive   n a             for some transitive vulnerabilities  there is no version of direct dependency with a fix  check the section  details  below to see if there is a version of transitive dependency where vulnerability is fixed       details        cve             vulnerable library    socket io client       jar     socket io client library for java   library home page   a href     path to dependency file   phone to app kotlin phone to app app build gradle   path to vulnerable library   home wss scanner  gradle caches modules   files     io socket socket io client         socket io client       jar  home wss scanner  gradle caches modules   files     io socket socket io client         socket io client       jar  home wss scanner  gradle caches modules   files     io socket socket io client         socket io client       jar     dependency hierarchy      android core       pom  root library         x    socket io client       jar    vulnerable library   found in head commit   a href     found in base branch   main               vulnerability details        the package io socket socket io client before       are vulnerable to null pointer dereference when parsing a packet with with invalid payload format    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  io socket socket io client                 ,0
163806,20364175753.0,IssuesEvent,2022-02-21 02:16:07,nycbeardo/react-metronome,https://api.github.com/repos/nycbeardo/react-metronome,opened,CVE-2021-27515 (Medium) detected in url-parse-1.4.7.tgz,security vulnerability,"## CVE-2021-27515 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>url-parse-1.4.7.tgz</b></p></summary>

<p>Small footprint URL parser that works seamlessly across Node.js and browser environments</p>
<p>Library home page: <a href=""https://registry.npmjs.org/url-parse/-/url-parse-1.4.7.tgz"">https://registry.npmjs.org/url-parse/-/url-parse-1.4.7.tgz</a></p>
<p>Path to dependency file: /react-metronome/package.json</p>
<p>Path to vulnerable library: /node_modules/url-parse/package.json</p>
<p>

Dependency Hierarchy:
  - react-scripts-3.0.1.tgz (Root Library)
    - react-dev-utils-9.0.1.tgz
      - sockjs-client-1.3.0.tgz
        - :x: **url-parse-1.4.7.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
url-parse before 1.5.0 mishandles certain uses of backslash such as http:\/ and interprets the URI as a relative path.

<p>Publish Date: 2021-02-22
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-27515>CVE-2021-27515</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-27515"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-27515</a></p>
<p>Release Date: 2021-02-22</p>
<p>Fix Resolution (url-parse): 1.5.0</p>
<p>Direct dependency fix Resolution (react-scripts): 3.1.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-27515 (Medium) detected in url-parse-1.4.7.tgz - ## CVE-2021-27515 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>url-parse-1.4.7.tgz</b></p></summary>

<p>Small footprint URL parser that works seamlessly across Node.js and browser environments</p>
<p>Library home page: <a href=""https://registry.npmjs.org/url-parse/-/url-parse-1.4.7.tgz"">https://registry.npmjs.org/url-parse/-/url-parse-1.4.7.tgz</a></p>
<p>Path to dependency file: /react-metronome/package.json</p>
<p>Path to vulnerable library: /node_modules/url-parse/package.json</p>
<p>

Dependency Hierarchy:
  - react-scripts-3.0.1.tgz (Root Library)
    - react-dev-utils-9.0.1.tgz
      - sockjs-client-1.3.0.tgz
        - :x: **url-parse-1.4.7.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
url-parse before 1.5.0 mishandles certain uses of backslash such as http:\/ and interprets the URI as a relative path.

<p>Publish Date: 2021-02-22
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-27515>CVE-2021-27515</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-27515"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-27515</a></p>
<p>Release Date: 2021-02-22</p>
<p>Fix Resolution (url-parse): 1.5.0</p>
<p>Direct dependency fix Resolution (react-scripts): 3.1.0</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      medium  detected in url parse       tgz      cve       medium severity vulnerability     vulnerable library    url parse       tgz      small footprint url parser that works seamlessly across node js and browser environments   library home page   a href     path to dependency file   react metronome package json   path to vulnerable library   node modules url parse package json     dependency hierarchy      react scripts       tgz  root library        react dev utils       tgz         sockjs client       tgz            x    url parse       tgz    vulnerable library             vulnerability details         url parse before       mishandles certain uses of backslash such as http    and interprets the uri as a relative path    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  low     availability impact  none   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  url parse           direct dependency fix resolution  react scripts                       step up your open source security game with whitesource    ,0
232696,7673987826.0,IssuesEvent,2018-05-15 01:10:27,Discordius/Lesswrong2,https://api.github.com/repos/Discordius/Lesswrong2,closed,“(read more)” for recent comments doesn't look great when it's split up by a line break,3. Low Priority (Easy) 6. Optimization,"Here's an example:
<img width=""993"" alt=""screen shot 2017-11-08 at 20 40 38"" src=""https://user-images.githubusercontent.com/2914269/32633812-df40b0d2-c55d-11e7-997e-de4444a597d7.png"">

Adding a non-breakinp space, `(read&nbsp;more)`, seem like an improvement to me.

<img width=""951"" alt=""screen shot 2017-11-09 at 14 57 59"" src=""https://user-images.githubusercontent.com/2914269/32634003-95ce3d88-c55e-11e7-9375-f731de807f13.png"">
",1.0,"“(read more)” for recent comments doesn't look great when it's split up by a line break - Here's an example:
<img width=""993"" alt=""screen shot 2017-11-08 at 20 40 38"" src=""https://user-images.githubusercontent.com/2914269/32633812-df40b0d2-c55d-11e7-997e-de4444a597d7.png"">

Adding a non-breakinp space, `(read&nbsp;more)`, seem like an improvement to me.

<img width=""951"" alt=""screen shot 2017-11-09 at 14 57 59"" src=""https://user-images.githubusercontent.com/2914269/32634003-95ce3d88-c55e-11e7-9375-f731de807f13.png"">
",0,“ read more ” for recent comments doesn t look great when it s split up by a line break   here s an example    img width     alt  screen shot       at        src       adding a non breakinp space    read nbsp more    seem like an improvement to me      img width     alt  screen shot       at        src     ,0
107927,9249062559.0,IssuesEvent,2019-03-15 08:28:00,openSUSE/open-build-service,https://api.github.com/repos/openSUSE/open-build-service,opened,Flickering test ./spec/bootstrap/features/webui/attributes_spec.rb:52,Flickering :cyclone: Test Suite :syringe:,"As we don't reset attribute names for rspec (due to some of them required as seeds), we run into test data collusion.

I can reproduce the problem by running:

```
while rspec ./spec/bootstrap/features/webui/attributes_spec.rb:52; do echo; done
```

Resulting in:

```
Failures:

  1) Bootstrap_Attributes with an attribute for a project with a package add attribute with values
     Failure/Error: expect(page).to have_content('Attribute was successfully created.')
       expected to find text ""Attribute was successfully created."" in ""AttribType::UnknownAttributeTypeError in Webui::AttributeController#edit\nAttribute Type perferendis:MyImageTemplates does not exist\nExtracted source (around line #49):\n47\n48\n49\n50\n51\n52\n              \n    ats = joins(:attrib_namespace).where('attrib_namespaces.name = ? and attrib_types.name = ?', namespace, name)\n    if or_fail && ats.count != 1\n      raise UnknownAttributeTypeError, \""Attribute Type \#{namespace}:\#{name} does not exist\""\n    end\n    ats.first\n  end\nRails.root: /obs/src/api\nApplication Trace | Framework Trace | Full Trace\napp/models/attrib_type.rb:49:in `find_by_namespace_and_name'\napp/models/attrib_type.rb:36:in `find_by_name'\napp/models/attrib_type.rb:28:in `find_by_name!'\napp/models/attrib.rb:41:in `find_by_container_and_fullname'\napp/controllers/webui/attribute_controller.rb:32:in `edit'\nconfig/initializers/wrap_parameters.rb:38:in `call'\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nRequest\nParameters:\n{\""project\""=>\""home:user_1\"", \""package\""=>\""package_1\"", \""attribute\""=>\""perferendis:MyImageTemplates\""}\nToggle session dump\nToggle env dump\nResponse\nHeaders:\nNone"". (However, it was found 1 time including non-visible text.)
     # ./spec/support/features/features_attribute.rb:8:in `add_attribute_with_values'
     # ./spec/bootstrap/features/webui/attributes_spec.rb:55:in `block (4 levels) in <top (required)>'
```

And as the log file shows that attrib name space was used before:

```
frontend@8b0cb4c29e3d:/obs/src/api> grep perferendis log/test.log
[17368:2.71]   AttribNamespace Create (0.3ms)  INSERT INTO `attrib_namespaces` (`name`) VALUES ('perferendis')
[fe4a4065-60df-4a2c-8a60-aa23c6f58572] [17368:0.04] Redirected to http://frontend:3005/attribs/home:user_1/package_1/perferendis:MyImageTemplates/edit
[80f68eca-8138-4b29-af41-2b1c260a4f21] [17368:0.04] Started GET ""/attribs/home:user_1/package_1/perferendis:MyImageTemplates/edit"" for 172.23.0.6 at 2019-03-15 08:19:46 +0000
[80f68eca-8138-4b29-af41-2b1c260a4f21] [17368:0.04]   Parameters: {""project""=>""home:user_1"", ""package""=>""package_1"", ""attribute""=>""perferendis:MyImageTemplates""}
[80f68eca-8138-4b29-af41-2b1c260a4f21] [17368:0.05]    (0.3ms)  SELECT COUNT(*) FROM `attrib_types` INNER JOIN `attrib_namespaces` ON `attrib_namespaces`.`id` = `attrib_types`.`attrib_namespace_id` WHERE (attrib_namespaces.name = 'perferendis' and attrib_types.name = 'MyImageTemplates')
[80f68eca-8138-4b29-af41-2b1c260a4f21] [17368:0.05]   AttribType Load (0.3ms)  SELECT  `attrib_types`.* FROM `attrib_types` INNER JOIN `attrib_namespaces` ON `attrib_namespaces`.`id` = `attrib_types`.`attrib_namespace_id` WHERE (attrib_namespaces.name = 'perferendis' and attrib_types.name = 'MyImageTemplates') ORDER BY `attrib_types`.`id` ASC LIMIT 1
[5e264197-871f-4de2-a0b1-735ca580c676] [17368:3.93] Redirected to http://frontend:3005/attribs/home:user_1/package_1/perferendis:MyImageTemplates/edit
[ee797f90-baec-488c-9fc9-aa7fe218df10] [17368:3.93] Started GET ""/attribs/home:user_1/package_1/perferendis:MyImageTemplates/edit"" for 172.23.0.6 at 2019-03-15 08:19:47 +0000
[ee797f90-baec-488c-9fc9-aa7fe218df10] [17368:3.94]   Parameters: {""project""=>""home:user_1"", ""package""=>""package_1"", ""attribute""=>""perferendis:MyImageTemplates""}
[ee797f90-baec-488c-9fc9-aa7fe218df10] [17368:3.94]    (0.3ms)  SELECT COUNT(*) FROM `attrib_types` INNER JOIN `attrib_namespaces` ON `attrib_namespaces`.`id` = `attrib_types`.`attrib_namespace_id` WHERE (attrib_namespaces.name = 'perferendis' and attrib_types.name = 'MyImageTemplates')
[ee797f90-baec-488c-9fc9-aa7fe218df10] [17368:3.94]   AttribType Load (0.3ms)  SELECT  `attrib_types`.* FROM `attrib_types` INNER JOIN `attrib_namespaces` ON `attrib_namespaces`.`id` = `attrib_types`.`attrib_namespace_id` WHERE (attrib_namespaces.name = 'perferendis' and attrib_types.name = 'MyImageTemplates') ORDER BY `attrib_types`.`id` ASC LIMIT 1
[17416:2.61]   AttribNamespace Create (16.2ms)  INSERT INTO `attrib_namespaces` (`name`) VALUES ('perferendis')
[ed5f3c4a-20ee-4e34-9785-c7891eeb6560] [17416:0.04] Redirected to http://frontend:3005/attribs/home:user_1/package_1/perferendis:MyImageTemplates/edit
[47d14b1a-27f0-4143-8f85-0da9ada4fd8f] [17416:0.04] Started GET ""/attribs/home:user_1/package_1/perferendis:MyImageTemplates/edit"" for 172.23.0.6 at 2019-03-15 08:20:14 +0000
[47d14b1a-27f0-4143-8f85-0da9ada4fd8f] [17416:0.04]   Parameters: {""project""=>""home:user_1"", ""package""=>""package_1"", ""attribute""=>""perferendis:MyImageTemplates""}
[47d14b1a-27f0-4143-8f85-0da9ada4fd8f] [17416:0.05]    (0.2ms)  SELECT COUNT(*) FROM `attrib_types` INNER JOIN `attrib_namespaces` ON `attrib_namespaces`.`id` = `attrib_types`.`attrib_namespace_id` WHERE (attrib_namespaces.name = 'perferendis' and attrib_types.name = 'MyImageTemplates')
[47d14b1a-27f0-4143-8f85-0da9ada4fd8f] [17416:0.05] AttribType::UnknownAttributeTypeError (Attribute Type perferendis:MyImageTemplates does not exist):
```

Faker words are a finite resource :)

I'm afraid the only cure to this is actually resetting attribute namespaces as well and recreating the seed data in the tests requiring them (or e.g. in all feature tests).
",1.0,"Flickering test ./spec/bootstrap/features/webui/attributes_spec.rb:52 - As we don't reset attribute names for rspec (due to some of them required as seeds), we run into test data collusion.

I can reproduce the problem by running:

```
while rspec ./spec/bootstrap/features/webui/attributes_spec.rb:52; do echo; done
```

Resulting in:

```
Failures:

  1) Bootstrap_Attributes with an attribute for a project with a package add attribute with values
     Failure/Error: expect(page).to have_content('Attribute was successfully created.')
       expected to find text ""Attribute was successfully created."" in ""AttribType::UnknownAttributeTypeError in Webui::AttributeController#edit\nAttribute Type perferendis:MyImageTemplates does not exist\nExtracted source (around line #49):\n47\n48\n49\n50\n51\n52\n              \n    ats = joins(:attrib_namespace).where('attrib_namespaces.name = ? and attrib_types.name = ?', namespace, name)\n    if or_fail && ats.count != 1\n      raise UnknownAttributeTypeError, \""Attribute Type \#{namespace}:\#{name} does not exist\""\n    end\n    ats.first\n  end\nRails.root: /obs/src/api\nApplication Trace | Framework Trace | Full Trace\napp/models/attrib_type.rb:49:in `find_by_namespace_and_name'\napp/models/attrib_type.rb:36:in `find_by_name'\napp/models/attrib_type.rb:28:in `find_by_name!'\napp/models/attrib.rb:41:in `find_by_container_and_fullname'\napp/controllers/webui/attribute_controller.rb:32:in `edit'\nconfig/initializers/wrap_parameters.rb:38:in `call'\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nRequest\nParameters:\n{\""project\""=>\""home:user_1\"", \""package\""=>\""package_1\"", \""attribute\""=>\""perferendis:MyImageTemplates\""}\nToggle session dump\nToggle env dump\nResponse\nHeaders:\nNone"". (However, it was found 1 time including non-visible text.)
     # ./spec/support/features/features_attribute.rb:8:in `add_attribute_with_values'
     # ./spec/bootstrap/features/webui/attributes_spec.rb:55:in `block (4 levels) in <top (required)>'
```

And as the log file shows that attrib name space was used before:

```
frontend@8b0cb4c29e3d:/obs/src/api> grep perferendis log/test.log
[17368:2.71]   AttribNamespace Create (0.3ms)  INSERT INTO `attrib_namespaces` (`name`) VALUES ('perferendis')
[fe4a4065-60df-4a2c-8a60-aa23c6f58572] [17368:0.04] Redirected to http://frontend:3005/attribs/home:user_1/package_1/perferendis:MyImageTemplates/edit
[80f68eca-8138-4b29-af41-2b1c260a4f21] [17368:0.04] Started GET ""/attribs/home:user_1/package_1/perferendis:MyImageTemplates/edit"" for 172.23.0.6 at 2019-03-15 08:19:46 +0000
[80f68eca-8138-4b29-af41-2b1c260a4f21] [17368:0.04]   Parameters: {""project""=>""home:user_1"", ""package""=>""package_1"", ""attribute""=>""perferendis:MyImageTemplates""}
[80f68eca-8138-4b29-af41-2b1c260a4f21] [17368:0.05]    (0.3ms)  SELECT COUNT(*) FROM `attrib_types` INNER JOIN `attrib_namespaces` ON `attrib_namespaces`.`id` = `attrib_types`.`attrib_namespace_id` WHERE (attrib_namespaces.name = 'perferendis' and attrib_types.name = 'MyImageTemplates')
[80f68eca-8138-4b29-af41-2b1c260a4f21] [17368:0.05]   AttribType Load (0.3ms)  SELECT  `attrib_types`.* FROM `attrib_types` INNER JOIN `attrib_namespaces` ON `attrib_namespaces`.`id` = `attrib_types`.`attrib_namespace_id` WHERE (attrib_namespaces.name = 'perferendis' and attrib_types.name = 'MyImageTemplates') ORDER BY `attrib_types`.`id` ASC LIMIT 1
[5e264197-871f-4de2-a0b1-735ca580c676] [17368:3.93] Redirected to http://frontend:3005/attribs/home:user_1/package_1/perferendis:MyImageTemplates/edit
[ee797f90-baec-488c-9fc9-aa7fe218df10] [17368:3.93] Started GET ""/attribs/home:user_1/package_1/perferendis:MyImageTemplates/edit"" for 172.23.0.6 at 2019-03-15 08:19:47 +0000
[ee797f90-baec-488c-9fc9-aa7fe218df10] [17368:3.94]   Parameters: {""project""=>""home:user_1"", ""package""=>""package_1"", ""attribute""=>""perferendis:MyImageTemplates""}
[ee797f90-baec-488c-9fc9-aa7fe218df10] [17368:3.94]    (0.3ms)  SELECT COUNT(*) FROM `attrib_types` INNER JOIN `attrib_namespaces` ON `attrib_namespaces`.`id` = `attrib_types`.`attrib_namespace_id` WHERE (attrib_namespaces.name = 'perferendis' and attrib_types.name = 'MyImageTemplates')
[ee797f90-baec-488c-9fc9-aa7fe218df10] [17368:3.94]   AttribType Load (0.3ms)  SELECT  `attrib_types`.* FROM `attrib_types` INNER JOIN `attrib_namespaces` ON `attrib_namespaces`.`id` = `attrib_types`.`attrib_namespace_id` WHERE (attrib_namespaces.name = 'perferendis' and attrib_types.name = 'MyImageTemplates') ORDER BY `attrib_types`.`id` ASC LIMIT 1
[17416:2.61]   AttribNamespace Create (16.2ms)  INSERT INTO `attrib_namespaces` (`name`) VALUES ('perferendis')
[ed5f3c4a-20ee-4e34-9785-c7891eeb6560] [17416:0.04] Redirected to http://frontend:3005/attribs/home:user_1/package_1/perferendis:MyImageTemplates/edit
[47d14b1a-27f0-4143-8f85-0da9ada4fd8f] [17416:0.04] Started GET ""/attribs/home:user_1/package_1/perferendis:MyImageTemplates/edit"" for 172.23.0.6 at 2019-03-15 08:20:14 +0000
[47d14b1a-27f0-4143-8f85-0da9ada4fd8f] [17416:0.04]   Parameters: {""project""=>""home:user_1"", ""package""=>""package_1"", ""attribute""=>""perferendis:MyImageTemplates""}
[47d14b1a-27f0-4143-8f85-0da9ada4fd8f] [17416:0.05]    (0.2ms)  SELECT COUNT(*) FROM `attrib_types` INNER JOIN `attrib_namespaces` ON `attrib_namespaces`.`id` = `attrib_types`.`attrib_namespace_id` WHERE (attrib_namespaces.name = 'perferendis' and attrib_types.name = 'MyImageTemplates')
[47d14b1a-27f0-4143-8f85-0da9ada4fd8f] [17416:0.05] AttribType::UnknownAttributeTypeError (Attribute Type perferendis:MyImageTemplates does not exist):
```

Faker words are a finite resource :)

I'm afraid the only cure to this is actually resetting attribute namespaces as well and recreating the seed data in the tests requiring them (or e.g. in all feature tests).
",0,flickering test   spec bootstrap features webui attributes spec rb     as we don t reset attribute names for rspec  due to some of them required as seeds   we run into test data collusion     i can reproduce the problem by running          while rspec   spec bootstrap features webui attributes spec rb    do echo  done         resulting in          failures          bootstrap attributes with an attribute for a project with a package add attribute with values       failure error  expect page  to have content  attribute was successfully created            expected to find text  attribute was successfully created   in  attribtype  unknownattributetypeerror in webui  attributecontroller edit nattribute type perferendis myimagetemplates does not exist nextracted source  around line                  n               n    ats   joins  attrib namespace  where  attrib namespaces name     and attrib types name       namespace  name  n    if or fail    ats count      n      raise unknownattributetypeerror    attribute type    namespace     name  does not exist   n    end n    ats first n  end nrails root   obs src api napplication trace   framework trace   full trace napp models attrib type rb   in  find by namespace and name  napp models attrib type rb   in  find by name  napp models attrib type rb   in  find by name   napp models attrib rb   in  find by container and fullname  napp controllers webui attribute controller rb   in  edit  nconfig initializers wrap parameters rb   in  call  n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n nrequest nparameters  n   project      home user        package      package        attribute      perferendis myimagetemplates    ntoggle session dump ntoggle env dump nresponse nheaders  nnone    however  it was found   time including non visible text             spec support features features attribute rb   in  add attribute with values            spec bootstrap features webui attributes spec rb   in  block    levels  in            and as the log file shows that attrib name space was used before          frontend    obs src api  grep perferendis log test log      attribnamespace create        insert into  attrib namespaces    name   values   perferendis        redirected to        started get   attribs home user   package   perferendis myimagetemplates edit  for         at                       parameters    project    home user      package    package      attribute    perferendis myimagetemplates                  select count    from  attrib types  inner join  attrib namespaces  on  attrib namespaces   id     attrib types   attrib namespace id  where  attrib namespaces name    perferendis  and attrib types name    myimagetemplates          attribtype load        select   attrib types    from  attrib types  inner join  attrib namespaces  on  attrib namespaces   id     attrib types   attrib namespace id  where  attrib namespaces name    perferendis  and attrib types name    myimagetemplates   order by  attrib types   id  asc limit        redirected to        started get   attribs home user   package   perferendis myimagetemplates edit  for         at                       parameters    project    home user      package    package      attribute    perferendis myimagetemplates                  select count    from  attrib types  inner join  attrib namespaces  on  attrib namespaces   id     attrib types   attrib namespace id  where  attrib namespaces name    perferendis  and attrib types name    myimagetemplates          attribtype load        select   attrib types    from  attrib types  inner join  attrib namespaces  on  attrib namespaces   id     attrib types   attrib namespace id  where  attrib namespaces name    perferendis  and attrib types name    myimagetemplates   order by  attrib types   id  asc limit        attribnamespace create        insert into  attrib namespaces    name   values   perferendis        redirected to        started get   attribs home user   package   perferendis myimagetemplates edit  for         at                       parameters    project    home user      package    package      attribute    perferendis myimagetemplates                  select count    from  attrib types  inner join  attrib namespaces  on  attrib namespaces   id     attrib types   attrib namespace id  where  attrib namespaces name    perferendis  and attrib types name    myimagetemplates        attribtype  unknownattributetypeerror  attribute type perferendis myimagetemplates does not exist           faker words are a finite resource       i m afraid the only cure to this is actually resetting attribute namespaces as well and recreating the seed data in the tests requiring them  or e g  in all feature tests    ,0
281397,8694741056.0,IssuesEvent,2018-12-04 13:30:57,webcompat/web-bugs,https://api.github.com/repos/webcompat/web-bugs,closed,epay.passport.gov.ph - site is not usable,browser-firefox priority-normal,"<!-- @browser: Firefox 64.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:64.0) Gecko/20100101 Firefox/64.0 -->
<!-- @reported_with: desktop-reporter -->

**URL**: http://epay.passport.gov.ph/pgi/grp/GUFLYMV6SB0K5Z

**Browser / Version**: Firefox 64.0
**Operating System**: Windows 7
**Tested Another Browser**: Yes

**Problem type**: Site is not usable
**Description**: always error
**Steps to Reproduce**:


<details>
<summary>Browser Configuration</summary>
<ul>
  <li>mixed active content blocked: false</li><li>image.mem.shared: true</li><li>buildID: 20181122182000</li><li>tracking content blocked: false</li><li>gfx.webrender.blob-images: true</li><li>hasTouchScreen: false</li><li>mixed passive content blocked: false</li><li>gfx.webrender.enabled: false</li><li>gfx.webrender.all: false</li><li>channel: beta</li>
</ul>

</details>

_From [webcompat.com](https://webcompat.com/) with ❤️_",1.0,"epay.passport.gov.ph - site is not usable - <!-- @browser: Firefox 64.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:64.0) Gecko/20100101 Firefox/64.0 -->
<!-- @reported_with: desktop-reporter -->

**URL**: http://epay.passport.gov.ph/pgi/grp/GUFLYMV6SB0K5Z

**Browser / Version**: Firefox 64.0
**Operating System**: Windows 7
**Tested Another Browser**: Yes

**Problem type**: Site is not usable
**Description**: always error
**Steps to Reproduce**:


<details>
<summary>Browser Configuration</summary>
<ul>
  <li>mixed active content blocked: false</li><li>image.mem.shared: true</li><li>buildID: 20181122182000</li><li>tracking content blocked: false</li><li>gfx.webrender.blob-images: true</li><li>hasTouchScreen: false</li><li>mixed passive content blocked: false</li><li>gfx.webrender.enabled: false</li><li>gfx.webrender.all: false</li><li>channel: beta</li>
</ul>

</details>

_From [webcompat.com](https://webcompat.com/) with ❤️_",0,epay passport gov ph   site is not usable            url         browser   version    firefox       operating system    windows     tested another browser    yes    problem type    site is not usable   description    always error   steps to reproduce         browser configuration       mixed active content blocked  false  image mem shared  true  buildid     tracking content blocked  false  gfx webrender blob images  true  hastouchscreen  false  mixed passive content blocked  false  gfx webrender enabled  false  gfx webrender all  false  channel  beta         from     with ❤️ ,0
238533,18244039867.0,IssuesEvent,2021-10-01 16:01:16,golang/go,https://api.github.com/repos/golang/go,closed,doc/modules/managing-dependencies: describe GOPRIVATE,Documentation NeedsFix,"https://golang.org/doc/modules/managing-dependencies currently describes how to set `GOPROXY` to a private module proxy. However, I expect that it is much more common for users to use the public proxy (proxy.golang.org) in conjunction with a few modules that are not publicly available.

We have the [`GOPRIVATE`](https://golang.org/ref/mod#private-module-privacy) variable for that use-case, but a search of the “Managing dependencies” page doesn't currently turn up any hits for the word “private”. The Go Modules Reference page does describe `GOPRIVATE`, but that's probably presented at a lower level than most users would prefer.

(See https://stackoverflow.com/q/65639718 for an example of a user who could benefit from such documentation.)

CC @jayconrod @matloob @stevetraut ",1.0,"doc/modules/managing-dependencies: describe GOPRIVATE - https://golang.org/doc/modules/managing-dependencies currently describes how to set `GOPROXY` to a private module proxy. However, I expect that it is much more common for users to use the public proxy (proxy.golang.org) in conjunction with a few modules that are not publicly available.

We have the [`GOPRIVATE`](https://golang.org/ref/mod#private-module-privacy) variable for that use-case, but a search of the “Managing dependencies” page doesn't currently turn up any hits for the word “private”. The Go Modules Reference page does describe `GOPRIVATE`, but that's probably presented at a lower level than most users would prefer.

(See https://stackoverflow.com/q/65639718 for an example of a user who could benefit from such documentation.)

CC @jayconrod @matloob @stevetraut ",1,doc modules managing dependencies  describe goprivate     currently describes how to set  goproxy  to a private module proxy  however  i expect that it is much more common for users to use the public proxy  proxy golang org  in conjunction with a few modules that are not publicly available     we have the     variable for that use case  but a search of the “managing dependencies” page doesn t currently turn up any hits for the word “private”  the go modules reference page does describe  goprivate   but that s probably presented at a lower level than most users would prefer      see   for an example of a user who could benefit from such documentation      cc  jayconrod  matloob  stevetraut ,1
8720,3210387942.0,IssuesEvent,2015-10-06 02:21:56,golang/go,https://api.github.com/repos/golang/go,closed,io: ByteReader and ByteWriter documentation,Documentation,"For ByteReader, is it possible that a byte is available **and** an error is also set? I would assume this should not happen, otherwise the user would never be able to tell that a byte was returned in the event of an error.

Also, for ByteWriter, the documentation doesn't really say anything at all about it. I would assume that an error is set **if and only if** the byte was not written.

Can documentation be made more clear on the error conditions?",1.0,"io: ByteReader and ByteWriter documentation - For ByteReader, is it possible that a byte is available **and** an error is also set? I would assume this should not happen, otherwise the user would never be able to tell that a byte was returned in the event of an error.

Also, for ByteWriter, the documentation doesn't really say anything at all about it. I would assume that an error is set **if and only if** the byte was not written.

Can documentation be made more clear on the error conditions?",1,io  bytereader and bytewriter documentation   for bytereader  is it possible that a byte is available   and   an error is also set  i would assume this should not happen  otherwise the user would never be able to tell that a byte was returned in the event of an error     also  for bytewriter  the documentation doesn t really say anything at all about it  i would assume that an error is set   if and only if   the byte was not written     can documentation be made more clear on the error conditions ,1
52724,27745802858.0,IssuesEvent,2023-03-15 16:57:36,learningequality/studio,https://api.github.com/repos/learningequality/studio,closed,Request to retrieve API token can take a long time,P1 - important TAG: ux update DEV: backend DEV: frontend TAG: performance,"<!--

Note that anything written between these symbols will not appear in the actual, published issue. They serve as instructions for filling out this template.  Please use the 'preview' tab above this textbox to verify formatting before submitting.

Instructions:
- Start by replacing the content in ""[Title]"" and give a ""[Brief description]"" of the issue above
- Please remove any unused, optional sections below.

-->

## Observed behavior
<!-- Briefly describe the current behavior, including screenshots or other references when applicable -->
When loading the account settings page, the API token is retrieved as a separate async request. The request seems to also calculate the user's storage usage, meaning the request can take a while and during that time, the API token field appears empty to the user.

## Expected behavior
<!-- Briefly describe the expected behavior that did not occur -->
Separate the request for the API token from any storage usage calculation and add appropriate loading indicators for user feedback on the page's loading state.

## User-facing consequences
<!-- Implications and real-world consequences for learners, coaches, admins, and other users of the application -->
Confusion on why the API token isn't appearing
https://learningequality.slack.com/archives/C0LK8QS9J/p1677751140708559

",True,"Request to retrieve API token can take a long time - <!--

Note that anything written between these symbols will not appear in the actual, published issue. They serve as instructions for filling out this template.  Please use the 'preview' tab above this textbox to verify formatting before submitting.

Instructions:
- Start by replacing the content in ""[Title]"" and give a ""[Brief description]"" of the issue above
- Please remove any unused, optional sections below.

-->

## Observed behavior
<!-- Briefly describe the current behavior, including screenshots or other references when applicable -->
When loading the account settings page, the API token is retrieved as a separate async request. The request seems to also calculate the user's storage usage, meaning the request can take a while and during that time, the API token field appears empty to the user.

## Expected behavior
<!-- Briefly describe the expected behavior that did not occur -->
Separate the request for the API token from any storage usage calculation and add appropriate loading indicators for user feedback on the page's loading state.

## User-facing consequences
<!-- Implications and real-world consequences for learners, coaches, admins, and other users of the application -->
Confusion on why the API token isn't appearing
https://learningequality.slack.com/archives/C0LK8QS9J/p1677751140708559

",0,request to retrieve api token can take a long time           note that anything written between these symbols will not appear in the actual  published issue  they serve as instructions for filling out this template   please use the  preview  tab above this textbox to verify formatting before submitting     instructions     start by replacing the content in     and give a     of the issue above    please remove any unused  optional sections below               observed behavior     when loading the account settings page  the api token is retrieved as a separate async request  the request seems to also calculate the user s storage usage  meaning the request can take a while and during that time  the api token field appears empty to the user        expected behavior     separate the request for the api token from any storage usage calculation and add appropriate loading indicators for user feedback on the page s loading state        user facing consequences     confusion on why the api token isn t appearing       ,0
350441,24985036169.0,IssuesEvent,2022-11-02 14:30:44,golang/go,https://api.github.com/repos/golang/go,closed,doc: add guidelines for comment directives,Documentation NeedsInvestigation Tools,"This issue shares some resemblance with https://github.com/golang/go/issues/13560. It is about properly documenting a pretty widespread convention regarding comment text.

In Go, `//go:` is reserved for the Go toolchain. This is documented at https://golang.org/cmd/compile/.

It is unofficially encouraged that other Go tools use a similar ""namespace"" prefix for their comment directives. For example, `//gccgo:` or `//llgo:` for other compilers, `//lint:` for staticcheck, `//go-sumtype:` for another tool, and so on. See https://groups.google.com/g/golang-dev/c/r4rdPdsH1Fg/m/tNZazPenX5cJ, as well as those two tools or others for examples out in the wild.

I think we should more formally define what this format should look like, so that one can programmatically tell if a comment line is a directive. For example, one could imagine `^[a-z-]+:` as a regular expression.

This would help tools which use directives be more consistent, as well as tools which want to inspect all comments and directives in source code. For example, gofumpt does this now, and it [takes some effort](https://github.com/mvdan/gofumpt/blob/eb0da8cc37e367dd519fd5ce98361f758a8b0508/format/format.go#L213-L225) to tell if a comment is a directive.

I don't really mind where this is documented, as long as it's somewhere relatively authoritative. The wording doesn't have to be strong - after all, a Go comment can contain any plaintext. But it should still encourage tools to follow the format, for the sake of consistency.",1.0,"doc: add guidelines for comment directives - This issue shares some resemblance with https://github.com/golang/go/issues/13560. It is about properly documenting a pretty widespread convention regarding comment text.

In Go, `//go:` is reserved for the Go toolchain. This is documented at https://golang.org/cmd/compile/.

It is unofficially encouraged that other Go tools use a similar ""namespace"" prefix for their comment directives. For example, `//gccgo:` or `//llgo:` for other compilers, `//lint:` for staticcheck, `//go-sumtype:` for another tool, and so on. See https://groups.google.com/g/golang-dev/c/r4rdPdsH1Fg/m/tNZazPenX5cJ, as well as those two tools or others for examples out in the wild.

I think we should more formally define what this format should look like, so that one can programmatically tell if a comment line is a directive. For example, one could imagine `^[a-z-]+:` as a regular expression.

This would help tools which use directives be more consistent, as well as tools which want to inspect all comments and directives in source code. For example, gofumpt does this now, and it [takes some effort](https://github.com/mvdan/gofumpt/blob/eb0da8cc37e367dd519fd5ce98361f758a8b0508/format/format.go#L213-L225) to tell if a comment is a directive.

I don't really mind where this is documented, as long as it's somewhere relatively authoritative. The wording doesn't have to be strong - after all, a Go comment can contain any plaintext. But it should still encourage tools to follow the format, for the sake of consistency.",1,doc  add guidelines for comment directives   this issue shares some resemblance with   it is about properly documenting a pretty widespread convention regarding comment text     in go     go   is reserved for the go toolchain  this is documented at      it is unofficially encouraged that other go tools use a similar  namespace  prefix for their comment directives  for example     gccgo   or    llgo   for other compilers     lint   for staticcheck     go sumtype   for another tool  and so on  see   as well as those two tools or others for examples out in the wild     i think we should more formally define what this format should look like  so that one can programmatically tell if a comment line is a directive  for example  one could imagine        as a regular expression     this would help tools which use directives be more consistent  as well as tools which want to inspect all comments and directives in source code  for example  gofumpt does this now  and it     to tell if a comment is a directive     i don t really mind where this is documented  as long as it s somewhere relatively authoritative  the wording doesn t have to be strong   after all  a go comment can contain any plaintext  but it should still encourage tools to follow the format  for the sake of consistency ,1
38930,6714864270.0,IssuesEvent,2017-10-13 18:39:20,golang/go,https://api.github.com/repos/golang/go,reopened,database/sql: unclear docs for Tx cause races in sql/driver implementations,Documentation NeedsFix,"### What version of Go are you using (`go version`)?

`go version go1.8.3 darwin/amd64`

### What did you do?

Unlike `Conn` or `Stmt` there's no guidance on `Tx` indicating how the stdlib uses implementations. This seems to cause bugs in driver implementations, as a `Tx` is expected to handle concurrent calls from multiple goroutines unlike most of the other interfaces in the package.

This came up as I was debugging [a panic inside of lib/pq](https://github.com/lib/pq/issues/614) and discovered it was a data race due to the authors not assuming that their `Tx` would have to deal with calls from multiple goroutines (the repro is [here](https://gist.github.com/blinsay/044f39176eeab7f3020d1b527df5bdd7). It slowly adjusts timeouts to try and make the Context time out as results are coming back). Out of curiosity, I looked at `go-sql-driver/mysql` and the lack of a race there seems like a happy accident - the Context expiring occasionally causes [an internal error to bubble up](https://github.com/go-sql-driver/mysql/blob/a825be04c652d01442384e9dcdf2cdc3f1eda67f/packets.go#L441-L443), since the authors appear to aggressively check their invariants.

I'm not sure whether this is a documentation problem or if there's something database/sql could do to make life easier for driver implementors.

",1.0,"database/sql: unclear docs for Tx cause races in sql/driver implementations - ### What version of Go are you using (`go version`)?

`go version go1.8.3 darwin/amd64`

### What did you do?

Unlike `Conn` or `Stmt` there's no guidance on `Tx` indicating how the stdlib uses implementations. This seems to cause bugs in driver implementations, as a `Tx` is expected to handle concurrent calls from multiple goroutines unlike most of the other interfaces in the package.

This came up as I was debugging [a panic inside of lib/pq](https://github.com/lib/pq/issues/614) and discovered it was a data race due to the authors not assuming that their `Tx` would have to deal with calls from multiple goroutines (the repro is [here](https://gist.github.com/blinsay/044f39176eeab7f3020d1b527df5bdd7). It slowly adjusts timeouts to try and make the Context time out as results are coming back). Out of curiosity, I looked at `go-sql-driver/mysql` and the lack of a race there seems like a happy accident - the Context expiring occasionally causes [an internal error to bubble up](https://github.com/go-sql-driver/mysql/blob/a825be04c652d01442384e9dcdf2cdc3f1eda67f/packets.go#L441-L443), since the authors appear to aggressively check their invariants.

I'm not sure whether this is a documentation problem or if there's something database/sql could do to make life easier for driver implementors.

",1,database sql  unclear docs for tx cause races in sql driver implementations       what version of go are you using   go version        go version       darwin           what did you do     unlike  conn  or  stmt  there s no guidance on  tx  indicating how the stdlib uses implementations  this seems to cause bugs in driver implementations  as a  tx  is expected to handle concurrent calls from multiple goroutines unlike most of the other interfaces in the package     this came up as i was debugging     and discovered it was a data race due to the authors not assuming that their  tx  would have to deal with calls from multiple goroutines  the repro is     it slowly adjusts timeouts to try and make the context time out as results are coming back   out of curiosity  i looked at  go sql driver mysql  and the lack of a race there seems like a happy accident   the context expiring occasionally causes     since the authors appear to aggressively check their invariants     i m not sure whether this is a documentation problem or if there s something database sql could do to make life easier for driver implementors     ,1
7141,2610328983.0,IssuesEvent,2015-02-26 19:46:01,chrsmith/republic-at-war,https://api.github.com/repos/chrsmith/republic-at-war,closed,Hardpoint Error,auto-migrated Priority-Medium Type-Defect,"```
As the CIS, I noticed on all maps so far that the Droid Carriers 3 engines are 
not actually within the ship. they appear correctly when viewing the battle 
from a high angle, but if in side profile it is clearly visible that the engine 
hard-points are above the actual model.
```

-----
Original issue reported on code.google.com by `jkouzman...@gmail.com` on 13 Jun 2011 at 1:39",1.0,"Hardpoint Error - ```
As the CIS, I noticed on all maps so far that the Droid Carriers 3 engines are 
not actually within the ship. they appear correctly when viewing the battle 
from a high angle, but if in side profile it is clearly visible that the engine 
hard-points are above the actual model.
```

-----
Original issue reported on code.google.com by `jkouzman...@gmail.com` on 13 Jun 2011 at 1:39",0,hardpoint error       as the cis  i noticed on all maps so far that the droid carriers   engines are  not actually within the ship  they appear correctly when viewing the battle  from a high angle  but if in side profile it is clearly visible that the engine  hard points are above the actual model             original issue reported on code google com by  jkouzman    gmail com  on   jun   at    ,0
672260,22797614833.0,IssuesEvent,2022-07-10 23:39:42,pvs-hd-tea/LapsPython,https://api.github.com/repos/pvs-hd-tea/LapsPython,closed,bug: Nested invented primitives are not handled,Bug High Priority,"Can't translate invented primitives that call other invented primitives which have not been translated yet. Should be easy to fix by
- starting their translation before reading it
- implementing a check in the grammar parser whether an invented primitive is to be translated
This solution might break the ordered function hierarchy though - when f1 encounters an untranslated primitive, this will be assigned f2, i.e., f1 calls f2 and not vice versa. Can also be fixed but more complicated, discussion makes sense.",1.0,"bug: Nested invented primitives are not handled - Can't translate invented primitives that call other invented primitives which have not been translated yet. Should be easy to fix by
- starting their translation before reading it
- implementing a check in the grammar parser whether an invented primitive is to be translated
This solution might break the ordered function hierarchy though - when f1 encounters an untranslated primitive, this will be assigned f2, i.e., f1 calls f2 and not vice versa. Can also be fixed but more complicated, discussion makes sense.",0,bug  nested invented primitives are not handled   can t translate invented primitives that call other invented primitives which have not been translated yet  should be easy to fix by    starting their translation before reading it    implementing a check in the grammar parser whether an invented primitive is to be translated  this solution might break the ordered function hierarchy though   when   encounters an untranslated primitive  this will be assigned    i e     calls   and not vice versa  can also be fixed but more complicated  discussion makes sense ,0
41588,6922201468.0,IssuesEvent,2017-11-30 01:47:26,golang/go,https://api.github.com/repos/golang/go,closed,strings: please improve documentation for strings.Builder,Documentation HelpWanted NeedsFix,"I think that the documentation of `strings.Builder` could be improved by adding a few sentences that compare it to `bytes.Buffer`.  More exactly, I'd like to see:

  * a pointer to `bytes.Buffer`;
  * a list of the methods that `strings.Builder` is lacking as compared to `bytes.Buffer`.
",1.0,"strings: please improve documentation for strings.Builder - I think that the documentation of `strings.Builder` could be improved by adding a few sentences that compare it to `bytes.Buffer`.  More exactly, I'd like to see:

  * a pointer to `bytes.Buffer`;
  * a list of the methods that `strings.Builder` is lacking as compared to `bytes.Buffer`.
",1,strings  please improve documentation for strings builder   i think that the documentation of  strings builder  could be improved by adding a few sentences that compare it to  bytes buffer    more exactly  i d like to see         a pointer to  bytes buffer        a list of the methods that  strings builder  is lacking as compared to  bytes buffer    ,1
17728,9884474121.0,IssuesEvent,2019-06-24 22:17:06,keras-team/keras,https://api.github.com/repos/keras-team/keras,closed,tf.keras.Model.evaluate skews score in custom tf.keras.callbacks.Callback,backend:tensorflow type:bug/performance,"**System information**  
- Have I written custom code (as opposed to using example directory): YES
- OS Platform and Distribution (e.g., Linux Ubuntu 16.04):  Ubuntu 18.04.2 LTS
- TensorFlow backend (yes / no):  YES
- TensorFlow version:  2.0.0-dev20190601
- Keras version:  2.2.4-tf
- Python version:  3.6
- CUDA/cuDNN version:  7.3.1
- GPU model and memory:  4 GeForce GTX 1080 w/8119MiB

**Describe the current behavior**  
I am using the TensorFlow Dataset api with the Keras Model.fit function. When `x` is a Dataset (and therefor no `y` is provided), an error is thrown if we provide a `batch_size` argument. However, a `batch_size` is required is we want to use `validation_data` (I would already classify this as an error).

So, I wrote my own custom callback to perform a call to Model.evaluate with the validation dataset I had already prepared after every `n`-th batch and after every single epoch. 

During training, at, say, step 1000 (and before the first epoch), the accuracy reported by Tensorboard (I use the Tensorboard Keras callback for train loss and accuracy), as well as the accuracy reported by the metrics display next to the progress bar, might be at ~19%. 

However, after the CustomCallback runs it's function on_batch_end(self, batch, logs=None) and a call to self.model.evaluate is made, the training accuracy displayed by the progress bar and by Tensorboard picks up where the validation accuracy left off. That is, if val accuracy happened to be ~28% (higher due to no Dropout), then the training metric would also read 28% from then on.

**Describe the expected behavior**  
Calling the model's evaluate function from within a custom callback should not change what is displayed for train accuracy. Also, built-in Dataset validation would be nice.

**Code to reproduce the issue**  

This is the custom callback. Instantiating this callback with a subdirectory for valdiation events and a Dataset instance, and then including this callback in a call to model.fit should reproduce the error. I invite you to provide the data. I am abandoning the Keras Model.fit pipeline for now due to time constraints but I thought I would still log the error. 

For this bug to be noticeable, the training accuracy must be noticeably lower due to dropout than the val acc. (the color is blue but this is train accuracy, I promise. The jump is at step 1000, at which point Model.evaluate was called).

![batch_acc](https://user-images.githubusercontent.com/11124194/59510020-efcca580-8eb2-11e9-8a3f-0261d69e4fdd.png)

`
class Validation(tf.keras.callbacks.Callback):
    
    def __init__(self, log_dir, dataset, *args, **kwargs):
        self.dataset = dataset
        self.writer = tf.summary.create_file_writer(f""{log_dir}/validation"")

    def on_train_begin(self, logs=None):
        self.history = {}
        self.step = 0

    def on_batch_end(self, batch, logs=None):
        self.step += 1
        if self.step % Config.val_log_freq == 0:
            metrics = self.model.evaluate(self.dataset, verbose=0)
            for k, v in zip(self.model.metrics_names, metrics):
                with self.writer.as_default():
                    tf.summary.scalar(f""batch_{k}"", v, step=self.step)
            self.writer.flush()
        
    def on_epoch_end(self, epoch, logs=None):
        metrics = self.model.evaluate(self.dataset, verbose=0)
        for k, v in zip(self.model.metrics_names, metrics):
            self.history.setdefault(k, []).append(v)
            with self.writer.as_default():
                tf.summary.scalar(f""epoch_{k}"", v, step=self.step)
        self.writer.flush()
            
validation_callback = Validation(log_dir, valid_dataset)`

**Other info / logs**  
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.  
",True,"tf.keras.Model.evaluate skews score in custom tf.keras.callbacks.Callback - **System information**  
- Have I written custom code (as opposed to using example directory): YES
- OS Platform and Distribution (e.g., Linux Ubuntu 16.04):  Ubuntu 18.04.2 LTS
- TensorFlow backend (yes / no):  YES
- TensorFlow version:  2.0.0-dev20190601
- Keras version:  2.2.4-tf
- Python version:  3.6
- CUDA/cuDNN version:  7.3.1
- GPU model and memory:  4 GeForce GTX 1080 w/8119MiB

**Describe the current behavior**  
I am using the TensorFlow Dataset api with the Keras Model.fit function. When `x` is a Dataset (and therefor no `y` is provided), an error is thrown if we provide a `batch_size` argument. However, a `batch_size` is required is we want to use `validation_data` (I would already classify this as an error).

So, I wrote my own custom callback to perform a call to Model.evaluate with the validation dataset I had already prepared after every `n`-th batch and after every single epoch. 

During training, at, say, step 1000 (and before the first epoch), the accuracy reported by Tensorboard (I use the Tensorboard Keras callback for train loss and accuracy), as well as the accuracy reported by the metrics display next to the progress bar, might be at ~19%. 

However, after the CustomCallback runs it's function on_batch_end(self, batch, logs=None) and a call to self.model.evaluate is made, the training accuracy displayed by the progress bar and by Tensorboard picks up where the validation accuracy left off. That is, if val accuracy happened to be ~28% (higher due to no Dropout), then the training metric would also read 28% from then on.

**Describe the expected behavior**  
Calling the model's evaluate function from within a custom callback should not change what is displayed for train accuracy. Also, built-in Dataset validation would be nice.

**Code to reproduce the issue**  

This is the custom callback. Instantiating this callback with a subdirectory for valdiation events and a Dataset instance, and then including this callback in a call to model.fit should reproduce the error. I invite you to provide the data. I am abandoning the Keras Model.fit pipeline for now due to time constraints but I thought I would still log the error. 

For this bug to be noticeable, the training accuracy must be noticeably lower due to dropout than the val acc. (the color is blue but this is train accuracy, I promise. The jump is at step 1000, at which point Model.evaluate was called).

![batch_acc](https://user-images.githubusercontent.com/11124194/59510020-efcca580-8eb2-11e9-8a3f-0261d69e4fdd.png)

`
class Validation(tf.keras.callbacks.Callback):
    
    def __init__(self, log_dir, dataset, *args, **kwargs):
        self.dataset = dataset
        self.writer = tf.summary.create_file_writer(f""{log_dir}/validation"")

    def on_train_begin(self, logs=None):
        self.history = {}
        self.step = 0

    def on_batch_end(self, batch, logs=None):
        self.step += 1
        if self.step % Config.val_log_freq == 0:
            metrics = self.model.evaluate(self.dataset, verbose=0)
            for k, v in zip(self.model.metrics_names, metrics):
                with self.writer.as_default():
                    tf.summary.scalar(f""batch_{k}"", v, step=self.step)
            self.writer.flush()
        
    def on_epoch_end(self, epoch, logs=None):
        metrics = self.model.evaluate(self.dataset, verbose=0)
        for k, v in zip(self.model.metrics_names, metrics):
            self.history.setdefault(k, []).append(v)
            with self.writer.as_default():
                tf.summary.scalar(f""epoch_{k}"", v, step=self.step)
        self.writer.flush()
            
validation_callback = Validation(log_dir, valid_dataset)`

**Other info / logs**  
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.  
",0,tf keras model evaluate skews score in custom tf keras callbacks callback     system information        have i written custom code  as opposed to using example directory   yes    os platform and distribution  e g   linux ubuntu        ubuntu       lts    tensorflow backend  yes   no    yes    tensorflow version              keras version         tf    python version          cuda cudnn version            gpu model and memory     geforce gtx   w        describe the current behavior      i am using the tensorflow dataset api with the keras model fit function  when  x  is a dataset  and therefor no  y  is provided   an error is thrown if we provide a  batch size  argument  however  a  batch size  is required is we want to use  validation data   i would already classify this as an error      so  i wrote my own custom callback to perform a call to model evaluate with the validation dataset i had already prepared after every  n  th batch and after every single epoch      during training  at  say  step    and before the first epoch   the accuracy reported by tensorboard  i use the tensorboard keras callback for train loss and accuracy   as well as the accuracy reported by the metrics display next to the progress bar  might be at          however  after the customcallback runs it s function on batch end self  batch  logs none  and a call to self model evaluate is made  the training accuracy displayed by the progress bar and by tensorboard picks up where the validation accuracy left off  that is  if val accuracy happened to be      higher due to no dropout   then the training metric would also read    from then on       describe the expected behavior      calling the model s evaluate function from within a custom callback should not change what is displayed for train accuracy  also  built in dataset validation would be nice       code to reproduce the issue        this is the custom callback  instantiating this callback with a subdirectory for valdiation events and a dataset instance  and then including this callback in a call to model fit should reproduce the error  i invite you to provide the data  i am abandoning the keras model fit pipeline for now due to time constraints but i thought i would still log the error      for this bug to be noticeable  the training accuracy must be noticeably lower due to dropout than the val acc   the color is blue but this is train accuracy  i promise  the jump is at step    at which point model evaluate was called                 class validation tf keras callbacks callback              def   init   self  log dir  dataset   args    kwargs            self dataset   dataset          self writer   tf summary create file writer f  log dir  validation          def on train begin self  logs none            self history               self step            def on batch end self  batch  logs none            self step               if self step   config val log freq                    metrics   self model evaluate self dataset  verbose                 for k  v in zip self model metrics names  metrics                    with self writer as default                         tf summary scalar f batch  k    v  step self step               self writer flush                  def on epoch end self  epoch  logs none            metrics   self model evaluate self dataset  verbose             for k  v in zip self model metrics names  metrics                self history setdefault k     append v               with self writer as default                     tf summary scalar f epoch  k    v  step self step           self writer flush                  validation callback   validation log dir  valid dataset        other info   logs      include any logs or source code that would be helpful to diagnose the problem  if including tracebacks  please include the full traceback  large logs and files should be attached     ,0
129294,18076882130.0,IssuesEvent,2021-09-21 10:52:42,three11/react-template-ts,https://api.github.com/repos/three11/react-template-ts,closed,"CVE-2021-3803 (Medium) detected in nth-check-2.0.0.tgz, nth-check-1.0.2.tgz",security vulnerability,"## CVE-2021-3803 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>nth-check-2.0.0.tgz</b>, <b>nth-check-1.0.2.tgz</b></p></summary>
<p>

<details><summary><b>nth-check-2.0.0.tgz</b></p></summary>

<p>Parses and compiles CSS nth-checks to highly optimized functions.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/nth-check/-/nth-check-2.0.0.tgz"">https://registry.npmjs.org/nth-check/-/nth-check-2.0.0.tgz</a></p>
<p>Path to dependency file: react-template-ts/package.json</p>
<p>Path to vulnerable library: react-template-ts/node_modules/nth-check/package.json</p>
<p>

Dependency Hierarchy:
  - enzyme-3.11.0.tgz (Root Library)
    - cheerio-1.0.0-rc.9.tgz
      - cheerio-select-1.4.0.tgz
        - css-select-4.1.2.tgz
          - :x: **nth-check-2.0.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>nth-check-1.0.2.tgz</b></p></summary>

<p>performant nth-check parser & compiler</p>
<p>Library home page: <a href=""https://registry.npmjs.org/nth-check/-/nth-check-1.0.2.tgz"">https://registry.npmjs.org/nth-check/-/nth-check-1.0.2.tgz</a></p>
<p>Path to dependency file: react-template-ts/package.json</p>
<p>Path to vulnerable library: react-template-ts/node_modules/nth-check/package.json</p>
<p>

Dependency Hierarchy:
  - image-webpack-loader-7.0.1.tgz (Root Library)
    - imagemin-svgo-8.0.0.tgz
      - svgo-1.3.2.tgz
        - css-select-2.1.0.tgz
          - :x: **nth-check-1.0.2.tgz** (Vulnerable Library)
</details>

<p>Found in HEAD commit: <a href=""https://github.com/three11/react-template-ts/commit/d6c73664396028513acbef01dcfc815fcf1853f4"">d6c73664396028513acbef01dcfc815fcf1853f4</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>  
  
nth-check is vulnerable to Inefficient Regular Expression Complexity

<p>Publish Date: 2021-09-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3803>CVE-2021-3803</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: N/A
  - Attack Complexity: N/A
  - Privileges Required: N/A
  - User Interaction: N/A
  - Scope: N/A
- Impact Metrics:
  - Confidentiality Impact: N/A
  - Integrity Impact: N/A
  - Availability Impact: N/A
</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/fb55/nth-check/compare/v2.0.0...v2.0.1"">https://github.com/fb55/nth-check/compare/v2.0.0...v2.0.1</a></p>
<p>Release Date: 2021-09-17</p>
<p>Fix Resolution: nth-check - v2.0.1</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2021-3803 (Medium) detected in nth-check-2.0.0.tgz, nth-check-1.0.2.tgz - ## CVE-2021-3803 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>nth-check-2.0.0.tgz</b>, <b>nth-check-1.0.2.tgz</b></p></summary>
<p>

<details><summary><b>nth-check-2.0.0.tgz</b></p></summary>

<p>Parses and compiles CSS nth-checks to highly optimized functions.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/nth-check/-/nth-check-2.0.0.tgz"">https://registry.npmjs.org/nth-check/-/nth-check-2.0.0.tgz</a></p>
<p>Path to dependency file: react-template-ts/package.json</p>
<p>Path to vulnerable library: react-template-ts/node_modules/nth-check/package.json</p>
<p>

Dependency Hierarchy:
  - enzyme-3.11.0.tgz (Root Library)
    - cheerio-1.0.0-rc.9.tgz
      - cheerio-select-1.4.0.tgz
        - css-select-4.1.2.tgz
          - :x: **nth-check-2.0.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>nth-check-1.0.2.tgz</b></p></summary>

<p>performant nth-check parser & compiler</p>
<p>Library home page: <a href=""https://registry.npmjs.org/nth-check/-/nth-check-1.0.2.tgz"">https://registry.npmjs.org/nth-check/-/nth-check-1.0.2.tgz</a></p>
<p>Path to dependency file: react-template-ts/package.json</p>
<p>Path to vulnerable library: react-template-ts/node_modules/nth-check/package.json</p>
<p>

Dependency Hierarchy:
  - image-webpack-loader-7.0.1.tgz (Root Library)
    - imagemin-svgo-8.0.0.tgz
      - svgo-1.3.2.tgz
        - css-select-2.1.0.tgz
          - :x: **nth-check-1.0.2.tgz** (Vulnerable Library)
</details>

<p>Found in HEAD commit: <a href=""https://github.com/three11/react-template-ts/commit/d6c73664396028513acbef01dcfc815fcf1853f4"">d6c73664396028513acbef01dcfc815fcf1853f4</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>  
  
nth-check is vulnerable to Inefficient Regular Expression Complexity

<p>Publish Date: 2021-09-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3803>CVE-2021-3803</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: N/A
  - Attack Complexity: N/A
  - Privileges Required: N/A
  - User Interaction: N/A
  - Scope: N/A
- Impact Metrics:
  - Confidentiality Impact: N/A
  - Integrity Impact: N/A
  - Availability Impact: N/A
</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/fb55/nth-check/compare/v2.0.0...v2.0.1"">https://github.com/fb55/nth-check/compare/v2.0.0...v2.0.1</a></p>
<p>Release Date: 2021-09-17</p>
<p>Fix Resolution: nth-check - v2.0.1</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      medium  detected in nth check       tgz  nth check       tgz      cve       medium severity vulnerability     vulnerable libraries    nth check       tgz    nth check       tgz          nth check       tgz      parses and compiles css nth checks to highly optimized functions    library home page   a href     path to dependency file  react template ts package json   path to vulnerable library  react template ts node modules nth check package json     dependency hierarchy      enzyme       tgz  root library        cheerio       rc   tgz         cheerio select       tgz           css select       tgz              x    nth check       tgz    vulnerable library       nth check       tgz      performant nth check parser   compiler   library home page   a href     path to dependency file  react template ts package json   path to vulnerable library  react template ts node modules nth check package json     dependency hierarchy      image webpack loader       tgz  root library        imagemin svgo       tgz         svgo       tgz           css select       tgz              x    nth check       tgz    vulnerable library      found in head commit   a href     found in base branch   master              vulnerability details         nth check is vulnerable to inefficient regular expression complexity   publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  n a     attack complexity  n a     privileges required  n a     user interaction  n a     scope  n a   impact metrics      confidentiality impact  n a     integrity impact  n a     availability impact  n a   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  nth check                       step up your open source security game with whitesource    ,0
10849,3438004345.0,IssuesEvent,2015-12-13 17:32:41,golang/go,https://api.github.com/repos/golang/go,closed,text/template: not documented that the $ is root variable.,Documentation,"Inside of {{range (root).A}} loop, I wanted use (root).B. But intead it refers (root).A.B. 

I noticed it's expected behavior, but I couldn't find what is the root variable in the [document of text/template](https://golang.org/pkg/text/template/) but found in [stackoverflow](http://stackoverflow.com/a/22873315).

I think we need explanation of what is root variable in the standard document of text/template.",1.0,"text/template: not documented that the $ is root variable. - Inside of {{range (root).A}} loop, I wanted use (root).B. But intead it refers (root).A.B. 

I noticed it's expected behavior, but I couldn't find what is the root variable in the [document of text/template](https://golang.org/pkg/text/template/) but found in [stackoverflow](http://stackoverflow.com/a/22873315).

I think we need explanation of what is root variable in the standard document of text/template.",1,text template  not documented that the   is root variable    inside of   range  root  a   loop  i wanted use  root  b  but intead it refers  root  a b      i noticed it s expected behavior  but i couldn t find what is the root variable in the     but found in        i think we need explanation of what is root variable in the standard document of text template ,1
66504,8948912694.0,IssuesEvent,2019-01-25 04:58:43,golang/go,https://api.github.com/repos/golang/go,closed,"cmd/compile, cmd/link: doc: docs are incomplete",Documentation NeedsFix help wanted,"The documentation for those commands on the website ([compile](https://tip.golang.org/cmd/compile/), [link](https://tip.golang.org/cmd/link/)) lacks certain flags. For example, compile's page is missing the very useful `-m` flag, and link's page -- `-a`, `-buildid`, and others.

(Ideally, those sections would be generated from `go tool (compile|link) -h` output, but I don't know enough details to propose a full solution.)",1.0,"cmd/compile, cmd/link: doc: docs are incomplete - The documentation for those commands on the website ([compile](https://tip.golang.org/cmd/compile/), [link](https://tip.golang.org/cmd/link/)) lacks certain flags. For example, compile's page is missing the very useful `-m` flag, and link's page -- `-a`, `-buildid`, and others.

(Ideally, those sections would be generated from `go tool (compile|link) -h` output, but I don't know enough details to propose a full solution.)",1,cmd compile  cmd link  doc  docs are incomplete   the documentation for those commands on the website          lacks certain flags  for example  compile s page is missing the very useful   m  flag  and link s page      a     buildid   and others      ideally  those sections would be generated from  go tool  compile link   h  output  but i don t know enough details to propose a full solution  ,1
11556,3505781112.0,IssuesEvent,2016-01-08 00:56:56,golang/go,https://api.github.com/repos/golang/go,closed,runtime: document missing GODEBUG settings,Documentation,"`src/runtime/extern.go` needs docs for some missing `GODEBUG` keys: 

* `h2debug` (from https://go-review.googlesource.com/#/c/17754/1/http2/http2.go@29)

* `h2client=0` (from net/http) and upcoming(?) `h2server=0`?

* `netdns` (documented elsewhere, but not in runtime/extern.go)

/cc @ianlancetaylor ",1.0,"runtime: document missing GODEBUG settings - `src/runtime/extern.go` needs docs for some missing `GODEBUG` keys: 

* `h2debug` (from https://go-review.googlesource.com/#/c/17754/1/http2/http2.go@29)

* `h2client=0` (from net/http) and upcoming(?) `h2server=0`?

* `netdns` (documented elsewhere, but not in runtime/extern.go)

/cc @ianlancetaylor ",1,runtime  document missing godebug settings    src runtime extern go  needs docs for some missing  godebug  keys             from               from net http  and upcoming                 netdns   documented elsewhere  but not in runtime extern go      cc  ianlancetaylor ,1
73397,7333385654.0,IssuesEvent,2018-03-05 19:14:34,dotnet/roslyn,https://api.github.com/repos/dotnet/roslyn,opened,ChangeSignatureDialog integration test failures,Area-IDE Test,"Seen a few failures from different unit tests, all with the same stack:
```
System.Windows.Automation.ElementNotAvailableException: Element not available ---> System.Runtime.InteropServices.COMException: An event was unable to invoke any of the subscribers (Exception from HRESULT: 0x80040201)
   at UIAutomationClient.IUIAutomationElement.GetCurrentPropertyValueEx(Int32 propertyId, Int32 ignoreDefaultValue)
   at System.Windows.Automation.AutomationElement.GetCurrentPropertyValue(AutomationProperty property, Boolean ignoreDefaultValue)
   --- End of inner exception stack trace ---
   at System.Windows.Automation.AutomationElement.GetCurrentPropertyValue(AutomationProperty property, Boolean ignoreDefaultValue).GetType().Name
   at System.Windows.Automation.AutomationElement.GetCurrentPropertyValue(AutomationProperty property, Boolean ignoreDefaultValue)
```
Failed tests that I've seen: CSharpChangeSignatureDialog.VerifyRemoveParameter, BasicChangeSignatureDialog.VerifyReorderParameters
Links:
https://ci.dot.net/job/dotnet_roslyn/view/Official%20Builds/job/master/job/windows_debug_vs-integration/1981/
https://ci.dot.net/job/dotnet_roslyn/view/Official%20Builds/job/master/job/windows_debug_vs-integration/1980/
![image](https://user-images.githubusercontent.com/2371880/36994562-5b1a9336-2066-11e8-9f92-d35438357505.png)
",1.0,"ChangeSignatureDialog integration test failures - Seen a few failures from different unit tests, all with the same stack:
```
System.Windows.Automation.ElementNotAvailableException: Element not available ---> System.Runtime.InteropServices.COMException: An event was unable to invoke any of the subscribers (Exception from HRESULT: 0x80040201)
   at UIAutomationClient.IUIAutomationElement.GetCurrentPropertyValueEx(Int32 propertyId, Int32 ignoreDefaultValue)
   at System.Windows.Automation.AutomationElement.GetCurrentPropertyValue(AutomationProperty property, Boolean ignoreDefaultValue)
   --- End of inner exception stack trace ---
   at System.Windows.Automation.AutomationElement.GetCurrentPropertyValue(AutomationProperty property, Boolean ignoreDefaultValue).GetType().Name
   at System.Windows.Automation.AutomationElement.GetCurrentPropertyValue(AutomationProperty property, Boolean ignoreDefaultValue)
```
Failed tests that I've seen: CSharpChangeSignatureDialog.VerifyRemoveParameter, BasicChangeSignatureDialog.VerifyReorderParameters
Links:
https://ci.dot.net/job/dotnet_roslyn/view/Official%20Builds/job/master/job/windows_debug_vs-integration/1981/
https://ci.dot.net/job/dotnet_roslyn/view/Official%20Builds/job/master/job/windows_debug_vs-integration/1980/
![image](https://user-images.githubusercontent.com/2371880/36994562-5b1a9336-2066-11e8-9f92-d35438357505.png)
",0,changesignaturedialog integration test failures   seen a few failures from different unit tests  all with the same stack        system windows automation elementnotavailableexception  element not available      system runtime interopservices comexception  an event was unable to invoke any of the subscribers  exception from hresult         at uiautomationclient iuiautomationelement getcurrentpropertyvalueex   propertyid    ignoredefaultvalue      at system windows automation automationelement getcurrentpropertyvalue automationproperty property  boolean ignoredefaultvalue          end of inner exception stack trace         at system windows automation automationelement getcurrentpropertyvalue automationproperty property  boolean ignoredefaultvalue  gettype   name     at system windows automation automationelement getcurrentpropertyvalue automationproperty property  boolean ignoredefaultvalue        failed tests that i ve seen  csharpchangesignaturedialog verifyremoveparameter  basicchangesignaturedialog verifyreorderparameters  links               ,0
28668,5530757051.0,IssuesEvent,2017-03-21 04:08:10,golang/go,https://api.github.com/repos/golang/go,closed,encoding/gob: encoding of single values doesn't agree with documentation,Documentation NeedsFix,"Please answer these questions before submitting your issue. Thanks!
### What version of Go are you using (`go version`)?

go version go1.7 linux/amd64
### What operating system and processor architecture are you using (`go env`)?

GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/mero""
GORACE=""""
GOROOT=""/home/mero/go""
GOTOOLDIR=""/home/mero/go/pkg/tool/linux_amd64""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build316359239=/tmp/go-build -gno-record-gcc-switches""
CXX=""g++""
CGO_ENABLED=""1""
### What did you do?

https://play.golang.org/p/tXSmbPjlD2
### What did you expect to see?

Above program printing `[]byte{0x2,0x6,0x1}` (see comment for why)
### What did you see instead?

Above program printing `[]byet{0x3, 0x6, 0x0, 0x1}` with an extra 0-byte.

I tried very hard to find any mention of what this 0-byte means in the [documentation](http://godoc.org/encoding/gob) but couldn't find anything (though I can't conclusively say it isn't there :) ). This only happens for single primitive values (not for structs) and I think it's an artifact of how the state machine works (i.e. it emits an end-of-struct-tag, even though there never was one).

As the 0-byte carries no information, this is probably a bug in the encoder, but as there probably is encoding of this in the wild and gob isn't version, it probably can't be fixed. In that case, the documentation should be updated to include this.
",1.0,"encoding/gob: encoding of single values doesn't agree with documentation - Please answer these questions before submitting your issue. Thanks!
### What version of Go are you using (`go version`)?

go version go1.7 linux/amd64
### What operating system and processor architecture are you using (`go env`)?

GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/mero""
GORACE=""""
GOROOT=""/home/mero/go""
GOTOOLDIR=""/home/mero/go/pkg/tool/linux_amd64""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build316359239=/tmp/go-build -gno-record-gcc-switches""
CXX=""g++""
CGO_ENABLED=""1""
### What did you do?

https://play.golang.org/p/tXSmbPjlD2
### What did you expect to see?

Above program printing `[]byte{0x2,0x6,0x1}` (see comment for why)
### What did you see instead?

Above program printing `[]byet{0x3, 0x6, 0x0, 0x1}` with an extra 0-byte.

I tried very hard to find any mention of what this 0-byte means in the [documentation](http://godoc.org/encoding/gob) but couldn't find anything (though I can't conclusively say it isn't there :) ). This only happens for single primitive values (not for structs) and I think it's an artifact of how the state machine works (i.e. it emits an end-of-struct-tag, even though there never was one).

As the 0-byte carries no information, this is probably a bug in the encoder, but as there probably is encoding of this in the wild and gob isn't version, it probably can't be fixed. In that case, the documentation should be updated to include this.
",1,encoding gob  encoding of single values doesn t agree with documentation   please answer these questions before submitting your issue  thanks      what version of go are you using   go version     go version     linux       what operating system and processor architecture are you using   go env     goarch     gobin    goexe    gohostarch     gohostos  linux  goos  linux  gopath   home mero  gorace    goroot   home mero go  gotooldir   home mero go pkg tool linux    cc  gcc  gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches  cxx  g    cgo enabled         what did you do         what did you expect to see   above program printing   byte          see comment for why      what did you see instead   above program printing   byet              with an extra   byte   i tried very hard to find any mention of what this   byte means in the     but couldn t find anything  though i can t conclusively say it isn t there       this only happens for single primitive values  not for structs  and i think it s an artifact of how the state machine works  i e  it emits an end of struct tag  even though there never was one    as the   byte carries no information  this is probably a bug in the encoder  but as there probably is encoding of this in the wild and gob isn t version  it probably can t be fixed  in that case  the documentation should be updated to include this  ,1
240455,18354360218.0,IssuesEvent,2021-10-08 16:04:40,golang/go,https://api.github.com/repos/golang/go,opened,"ref/mod: vcs-find section should mention the ""mod"" version control system",Documentation NeedsFix modules,"I recently asked a question which boils down to: can I publish a Go module in plain zip archives, without using a standard VCS like git?

@bcmills helpfully pointed me towards https://golang.org/ref/mod#serving-from-proxy, which is basically what I want :)

The reason I had failed to find that section of the reference doc is because I looked in https://golang.org/ref/mod#vcs-find, which does not list ""mod"" in its table. It probably should, and have the mention link to the serving-from-proxy section.",1.0,"ref/mod: vcs-find section should mention the ""mod"" version control system - I recently asked a question which boils down to: can I publish a Go module in plain zip archives, without using a standard VCS like git?

@bcmills helpfully pointed me towards https://golang.org/ref/mod#serving-from-proxy, which is basically what I want :)

The reason I had failed to find that section of the reference doc is because I looked in https://golang.org/ref/mod#vcs-find, which does not list ""mod"" in its table. It probably should, and have the mention link to the serving-from-proxy section.",1,ref mod  vcs find section should mention the  mod  version control system   i recently asked a question which boils down to  can i publish a go module in plain zip archives  without using a standard vcs like git      bcmills helpfully pointed me towards   which is basically what i want       the reason i had failed to find that section of the reference doc is because i looked in   which does not list  mod  in its table  it probably should  and have the mention link to the serving from proxy section ,1
326088,9942624168.0,IssuesEvent,2019-07-03 14:15:36,ahmedkaludi/accelerated-mobile-pages,https://api.github.com/repos/ahmedkaludi/accelerated-mobile-pages,closed,Page title is changing when Rank math plugin active,NEED FAST REVIEW Urgent [Priority: HIGH] bug,"REF:https://secure.helpscout.net/conversation/884374984/71353?folderId=3008055

If select custom front page then it will display diff title.
And if not selected then also it display diff title.",1.0,"Page title is changing when Rank math plugin active - REF:https://secure.helpscout.net/conversation/884374984/71353?folderId=3008055

If select custom front page then it will display diff title.
And if not selected then also it display diff title.",0,page title is changing when rank math plugin active   ref      if select custom front page then it will display diff title   and if not selected then also it display diff title ,0
427447,29813066024.0,IssuesEvent,2023-06-16 16:36:19,golang/go,https://api.github.com/repos/golang/go,closed,runtime: document that MemStats.Lookups is always zero,Documentation NeedsFix compiler/runtime,"package main
import ""fmt""
import ""runtime""
func main () {
    var a = runtime.MemStats{}
    runtime.ReadMemStats(&a)
    fmt.Printf(""%+v\n"", a.Lookups)
}",1.0,"runtime: document that MemStats.Lookups is always zero - package main
import ""fmt""
import ""runtime""
func main () {
    var a = runtime.MemStats{}
    runtime.ReadMemStats(&a)
    fmt.Printf(""%+v\n"", a.Lookups)
}",1,runtime  document that memstats lookups is always zero   package main  import  fmt   import  runtime   func main           var a   runtime memstats        runtime readmemstats  a       fmt printf    v n   a lookups    ,1
179929,30323647440.0,IssuesEvent,2023-07-10 21:23:35,Expensify/App,https://api.github.com/repos/Expensify/App,closed,[HOLD for payment 2023-06-19] [$1000] Add boundary to transparent background images on Share QR code screen,External Daily Design Awaiting Payment Bug,"If you haven’t already, check out our [contributing guidelines](https://github.com/Expensify/ReactNativeChat/blob/main/contributingGuides/CONTRIBUTING.md) for onboarding and email contributors@expensify.com to request to join our Slack channel!
___

## Action Performed:

1. Go to staging dot on web chrome
2. Click on profile
3. Change the profile picture to any image with background
4. Click the back arrow
5. Click on Share code and notice that the image is shown in circular frame between the QR code that looks great
6. But now try to change the profile picture that has transparent background (example: 
![transparent photo](https://github.com/Expensify/App/assets/51066321/e6d6ecb1-f5a9-480a-8045-8dfe97e6ff12))

7. Click on Share code and notice that since the image doesn't have any background, it looks weird in between the QR code. Thus, a circular frame should be provided in all the images irrespective of the background

## Expected Result:
A circular frame should be provided in all the images irrespective of the background in the QR code
## Actual Result:
Transparent background images looks weird in Share QR code unlike images with backgrounds

## Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

## Platforms:
<!---
Check off any platforms that are affected by this issue
--->
Which of our officially supported platforms is this issue occurring on?
- [X] Android / native
- [X] Android / Chrome
- [X] iOS / native
- [X] iOS / Safari
- [x] MacOS / Chrome / Safari
- [X] MacOS / Desktop

**Version Number:** 1.3.18-0
**Reproducible in staging?:** y
**Reproducible in production?:** y
**If this was caught during regression testing, add the test name, ID and link from TestRail:**
**Email or phone of affected tester (no customers):**
**Logs:** https://stackoverflow.com/c/expensify/questions/4856
**Notes/Photos/Videos:** Any additional supporting documentation

https://github.com/Expensify/App/assets/43996225/bf86c919-c734-429c-96d8-21a36962fdb9


https://github.com/Expensify/App/assets/43996225/064e6572-6733-4c3b-b379-ffa991fb631a


**Expensify/Expensify Issue URL:**
**Issue reported by:** @priya-zha
**Slack conversation:** https://expensify.slack.com/archives/C049HHMV9SM/p1684818587259709

[View all open jobs on GitHub](https://github.com/Expensify/App/issues?q=is%3Aopen+is%3Aissue+label%3A%22Help+Wanted%22)

<details><summary>Upwork Automation - Do Not Edit</summary>
    <ul>
        <li>Upwork Job URL: https://www.upwork.com/jobs/~01916a33b50e2bee79</li>
        <li>Upwork Job ID: 1661800609949470720</li>
        <li>Last Price Increase: 2023-05-25</li>
    </ul>
</details>",1.0,"[HOLD for payment 2023-06-19] [$1000] Add boundary to transparent background images on Share QR code screen - If you haven’t already, check out our [contributing guidelines](https://github.com/Expensify/ReactNativeChat/blob/main/contributingGuides/CONTRIBUTING.md) for onboarding and email contributors@expensify.com to request to join our Slack channel!
___

## Action Performed:

1. Go to staging dot on web chrome
2. Click on profile
3. Change the profile picture to any image with background
4. Click the back arrow
5. Click on Share code and notice that the image is shown in circular frame between the QR code that looks great
6. But now try to change the profile picture that has transparent background (example: 
![transparent photo](https://github.com/Expensify/App/assets/51066321/e6d6ecb1-f5a9-480a-8045-8dfe97e6ff12))

7. Click on Share code and notice that since the image doesn't have any background, it looks weird in between the QR code. Thus, a circular frame should be provided in all the images irrespective of the background

## Expected Result:
A circular frame should be provided in all the images irrespective of the background in the QR code
## Actual Result:
Transparent background images looks weird in Share QR code unlike images with backgrounds

## Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

## Platforms:
<!---
Check off any platforms that are affected by this issue
--->
Which of our officially supported platforms is this issue occurring on?
- [X] Android / native
- [X] Android / Chrome
- [X] iOS / native
- [X] iOS / Safari
- [x] MacOS / Chrome / Safari
- [X] MacOS / Desktop

**Version Number:** 1.3.18-0
**Reproducible in staging?:** y
**Reproducible in production?:** y
**If this was caught during regression testing, add the test name, ID and link from TestRail:**
**Email or phone of affected tester (no customers):**
**Logs:** https://stackoverflow.com/c/expensify/questions/4856
**Notes/Photos/Videos:** Any additional supporting documentation

https://github.com/Expensify/App/assets/43996225/bf86c919-c734-429c-96d8-21a36962fdb9


https://github.com/Expensify/App/assets/43996225/064e6572-6733-4c3b-b379-ffa991fb631a


**Expensify/Expensify Issue URL:**
**Issue reported by:** @priya-zha
**Slack conversation:** https://expensify.slack.com/archives/C049HHMV9SM/p1684818587259709

[View all open jobs on GitHub](https://github.com/Expensify/App/issues?q=is%3Aopen+is%3Aissue+label%3A%22Help+Wanted%22)

<details><summary>Upwork Automation - Do Not Edit</summary>
    <ul>
        <li>Upwork Job URL: https://www.upwork.com/jobs/~01916a33b50e2bee79</li>
        <li>Upwork Job ID: 1661800609949470720</li>
        <li>Last Price Increase: 2023-05-25</li>
    </ul>
</details>",0,    add boundary to transparent background images on share qr code screen   if you haven’t already  check out our     for onboarding and email contributors expensify com to request to join our slack channel             action performed        go to staging dot on web chrome     click on profile     change the profile picture to any image with background     click the back arrow     click on share code and notice that the image is shown in circular frame between the qr code that looks great     but now try to change the profile picture that has transparent background  example               click on share code and notice that since the image doesn t have any background  it looks weird in between the qr code  thus  a circular frame should be provided in all the images irrespective of the background       expected result   a circular frame should be provided in all the images irrespective of the background in the qr code     actual result   transparent background images looks weird in share qr code unlike images with backgrounds       workaround   can the user still use expensify without this being fixed  have you informed them of the workaround        platforms          check off any platforms that are affected by this issue        which of our officially supported platforms is this issue occurring on       android   native      android   chrome      ios   native      ios   safari      macos   chrome   safari      macos   desktop      version number               reproducible in staging     y    reproducible in production     y    if this was caught during regression testing  add the test name  id and link from testrail       email or phone of affected tester  no customers        logs         notes photos videos    any additional supporting documentation                    expensify expensify issue url       issue reported by     priya zha    slack conversation                 upwork automation   do not edit                 upwork job url             upwork job id              last price increase                ,0
350550,10492104057.0,IssuesEvent,2019-09-25 12:38:25,threefoldfoundation/www_threefold.io_new,https://api.github.com/repos/threefoldfoundation/www_threefold.io_new,closed,Metadata not showing for Community/Team/Partners,priority_critical state_inprogress,I have put meta descriptions + images and such in both team.hmtl and community.html but it does not show up when running it through https://www.metadata.io,1.0,Metadata not showing for Community/Team/Partners - I have put meta descriptions + images and such in both team.hmtl and community.html but it does not show up when running it through https://www.metadata.io,0,metadata not showing for community team partners   i have put meta descriptions   images and such in both team hmtl and community html but it does not show up when running it through  ,0
52525,13753107585.0,IssuesEvent,2020-10-06 15:15:33,idonthaveafifaaddiction/wp-calypso,https://api.github.com/repos/idonthaveafifaaddiction/wp-calypso,opened,"CVE-2020-15138 (High) detected in prismjs-1.17.1.tgz, prismjs-1.6.0.tgz",security vulnerability,"## CVE-2020-15138 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>prismjs-1.17.1.tgz</b>, <b>prismjs-1.6.0.tgz</b></p></summary>
<p>

<details><summary><b>prismjs-1.17.1.tgz</b></p></summary>

<p>Lightweight, robust, elegant syntax highlighting. A spin-off project from Dabblet.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/prismjs/-/prismjs-1.17.1.tgz"">https://registry.npmjs.org/prismjs/-/prismjs-1.17.1.tgz</a></p>
<p>Path to dependency file: wp-calypso/yarn.lock</p>
<p>Path to vulnerable library: wp-calypso/yarn.lock</p>
<p>

Dependency Hierarchy:
  - :x: **prismjs-1.17.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>prismjs-1.6.0.tgz</b></p></summary>

<p>Lightweight, robust, elegant syntax highlighting. A spin-off project from Dabblet.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/prismjs/-/prismjs-1.6.0.tgz"">https://registry.npmjs.org/prismjs/-/prismjs-1.6.0.tgz</a></p>
<p>Path to dependency file: wp-calypso/yarn.lock</p>
<p>Path to vulnerable library: wp-calypso/yarn.lock</p>
<p>

Dependency Hierarchy:
  - react-live-1.12.0.tgz (Root Library)
    - :x: **prismjs-1.6.0.tgz** (Vulnerable Library)
</details>

<p>Found in HEAD commit: <a href=""https://github.com/idonthaveafifaaddiction/wp-calypso/commit/b131c522ed38b50de14a6e81731f66b365a8cf07"">b131c522ed38b50de14a6e81731f66b365a8cf07</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>  
  
Prism is vulnerable to Cross-Site Scripting. The easing preview of the Previewers plugin has an XSS vulnerability that allows attackers to execute arbitrary code in Safari and Internet Explorer. This impacts all Safari and Internet Explorer users of Prism >=v1.1.0 that use the _Previewers_ plugin (>=v1.10.0) or the _Previewer: Easing_ plugin (v1.1.0 to v1.9.0). This problem is fixed in version 1.21.0. To workaround the issue without upgrading, disable the easing preview on all impacted code blocks. You need Prism v1.10.0 or newer to apply this workaround.

<p>Publish Date: 2020-08-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15138>CVE-2020-15138</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: High
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Changed
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: Low
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/PrismJS/prism/v1.21.0"">https://github.com/PrismJS/prism/v1.21.0</a></p>
<p>Release Date: 2020-07-21</p>
<p>Fix Resolution: v1.21.0</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":false,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""prismjs"",""packageVersion"":""1.17.1"",""isTransitiveDependency"":false,""dependencyTree"":""prismjs:1.17.1"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""v1.21.0""},{""packageType"":""javascript/Node.js"",""packageName"":""prismjs"",""packageVersion"":""1.6.0"",""isTransitiveDependency"":true,""dependencyTree"":""react-live:1.12.0;prismjs:1.6.0"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""v1.21.0""}],""vulnerabilityIdentifier"":""CVE-2020-15138"",""vulnerabilityDetails"":""Prism is vulnerable to Cross-Site Scripting. The easing preview of the Previewers plugin has an XSS vulnerability that allows attackers to execute arbitrary code in Safari and Internet Explorer. This impacts all Safari and Internet Explorer users of Prism \u003e\u003dv1.1.0 that use the _Previewers_ plugin (\u003e\u003dv1.10.0) or the _Previewer: Easing_ plugin (v1.1.0 to v1.9.0). This problem is fixed in version 1.21.0. To workaround the issue without upgrading, disable the easing preview on all impacted code blocks. You need Prism v1.10.0 or newer to apply this workaround."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15138"",""cvss3Severity"":""high"",""cvss3Score"":""7.5"",""cvss3Metrics"":{""A"":""Low"",""AC"":""High"",""PR"":""None"",""S"":""Changed"",""C"":""High"",""UI"":""Required"",""AV"":""Network"",""I"":""Low""},""extraData"":{}}</REMEDIATE> -->",True,"CVE-2020-15138 (High) detected in prismjs-1.17.1.tgz, prismjs-1.6.0.tgz - ## CVE-2020-15138 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>prismjs-1.17.1.tgz</b>, <b>prismjs-1.6.0.tgz</b></p></summary>
<p>

<details><summary><b>prismjs-1.17.1.tgz</b></p></summary>

<p>Lightweight, robust, elegant syntax highlighting. A spin-off project from Dabblet.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/prismjs/-/prismjs-1.17.1.tgz"">https://registry.npmjs.org/prismjs/-/prismjs-1.17.1.tgz</a></p>
<p>Path to dependency file: wp-calypso/yarn.lock</p>
<p>Path to vulnerable library: wp-calypso/yarn.lock</p>
<p>

Dependency Hierarchy:
  - :x: **prismjs-1.17.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>prismjs-1.6.0.tgz</b></p></summary>

<p>Lightweight, robust, elegant syntax highlighting. A spin-off project from Dabblet.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/prismjs/-/prismjs-1.6.0.tgz"">https://registry.npmjs.org/prismjs/-/prismjs-1.6.0.tgz</a></p>
<p>Path to dependency file: wp-calypso/yarn.lock</p>
<p>Path to vulnerable library: wp-calypso/yarn.lock</p>
<p>

Dependency Hierarchy:
  - react-live-1.12.0.tgz (Root Library)
    - :x: **prismjs-1.6.0.tgz** (Vulnerable Library)
</details>

<p>Found in HEAD commit: <a href=""https://github.com/idonthaveafifaaddiction/wp-calypso/commit/b131c522ed38b50de14a6e81731f66b365a8cf07"">b131c522ed38b50de14a6e81731f66b365a8cf07</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>  
  
Prism is vulnerable to Cross-Site Scripting. The easing preview of the Previewers plugin has an XSS vulnerability that allows attackers to execute arbitrary code in Safari and Internet Explorer. This impacts all Safari and Internet Explorer users of Prism >=v1.1.0 that use the _Previewers_ plugin (>=v1.10.0) or the _Previewer: Easing_ plugin (v1.1.0 to v1.9.0). This problem is fixed in version 1.21.0. To workaround the issue without upgrading, disable the easing preview on all impacted code blocks. You need Prism v1.10.0 or newer to apply this workaround.

<p>Publish Date: 2020-08-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15138>CVE-2020-15138</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: High
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Changed
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: Low
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/PrismJS/prism/v1.21.0"">https://github.com/PrismJS/prism/v1.21.0</a></p>
<p>Release Date: 2020-07-21</p>
<p>Fix Resolution: v1.21.0</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":false,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""prismjs"",""packageVersion"":""1.17.1"",""isTransitiveDependency"":false,""dependencyTree"":""prismjs:1.17.1"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""v1.21.0""},{""packageType"":""javascript/Node.js"",""packageName"":""prismjs"",""packageVersion"":""1.6.0"",""isTransitiveDependency"":true,""dependencyTree"":""react-live:1.12.0;prismjs:1.6.0"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""v1.21.0""}],""vulnerabilityIdentifier"":""CVE-2020-15138"",""vulnerabilityDetails"":""Prism is vulnerable to Cross-Site Scripting. The easing preview of the Previewers plugin has an XSS vulnerability that allows attackers to execute arbitrary code in Safari and Internet Explorer. This impacts all Safari and Internet Explorer users of Prism \u003e\u003dv1.1.0 that use the _Previewers_ plugin (\u003e\u003dv1.10.0) or the _Previewer: Easing_ plugin (v1.1.0 to v1.9.0). This problem is fixed in version 1.21.0. To workaround the issue without upgrading, disable the easing preview on all impacted code blocks. You need Prism v1.10.0 or newer to apply this workaround."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15138"",""cvss3Severity"":""high"",""cvss3Score"":""7.5"",""cvss3Metrics"":{""A"":""Low"",""AC"":""High"",""PR"":""None"",""S"":""Changed"",""C"":""High"",""UI"":""Required"",""AV"":""Network"",""I"":""Low""},""extraData"":{}}</REMEDIATE> -->",0,cve      high  detected in prismjs       tgz  prismjs       tgz      cve       high severity vulnerability     vulnerable libraries    prismjs       tgz    prismjs       tgz          prismjs       tgz      lightweight  robust  elegant syntax highlighting  a spin off project from dabblet    library home page   a href     path to dependency file  wp calypso yarn lock   path to vulnerable library  wp calypso yarn lock     dependency hierarchy       x    prismjs       tgz    vulnerable library       prismjs       tgz      lightweight  robust  elegant syntax highlighting  a spin off project from dabblet    library home page   a href     path to dependency file  wp calypso yarn lock   path to vulnerable library  wp calypso yarn lock     dependency hierarchy      react live       tgz  root library         x    prismjs       tgz    vulnerable library      found in head commit   a href     found in base branch   master              vulnerability details         prism is vulnerable to cross site scripting  the easing preview of the previewers plugin has an xss vulnerability that allows attackers to execute arbitrary code in safari and internet explorer  this impacts all safari and internet explorer users of prism         that use the  previewers  plugin           or the  previewer  easing  plugin        to         this problem is fixed in version        to workaround the issue without upgrading  disable the easing preview on all impacted code blocks  you need prism       or newer to apply this workaround    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  required     scope  changed   impact metrics      confidentiality impact  high     integrity impact  low     availability impact  low   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                     isopenpronvulnerability  false  ispackagebased  true  isdefaultbranch  true  packages     vulnerabilityidentifier   cve       vulnerabilitydetails   prism is vulnerable to cross site scripting  the easing preview of the previewers plugin has an xss vulnerability that allows attackers to execute arbitrary code in safari and internet explorer  this impacts all safari and internet explorer users of prism          that use the  previewers  plugin            or the  previewer  easing  plugin        to         this problem is fixed in version        to workaround the issue without upgrading  disable the easing preview on all impacted code blocks  you need prism       or newer to apply this workaround    vulnerabilityurl        ,0
84019,10347358426.0,IssuesEvent,2019-09-04 17:12:26,golang/go,https://api.github.com/repos/golang/go,closed,doc: errors: wrong unwrap example,Documentation,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
go 1.13

</pre>

Documentation provides this example of `Unwrap` call https://github.com/golang/go/blob/master/src/errors/errors.go#L19. But this example wont work because `fmt.Errorf` returned `error` interface https://play.golang.org/p/KaQv-yJl6yy

",1.0,"doc: errors: wrong unwrap example - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
go 1.13

</pre>

Documentation provides this example of `Unwrap` call https://github.com/golang/go/blob/master/src/errors/errors.go#L19. But this example wont work because `fmt.Errorf` returned `error` interface https://play.golang.org/p/KaQv-yJl6yy

",1,doc  errors  wrong unwrap example            what version of go are you using   go version          go             documentation provides this example of  unwrap  call   but this example wont work because  fmt errorf  returned  error  interface      ,1
92691,15863711945.0,IssuesEvent,2021-04-08 13:05:23,yoswein/NodeGoat,https://api.github.com/repos/yoswein/NodeGoat,opened,WS-2017-0247 (Low) detected in ms-0.7.1.tgz,security vulnerability,"## WS-2017-0247 - Low Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ms-0.7.1.tgz</b></p></summary>

<p>Tiny ms conversion utility</p>
<p>Library home page: <a href=""https://registry.npmjs.org/ms/-/ms-0.7.1.tgz"">https://registry.npmjs.org/ms/-/ms-0.7.1.tgz</a></p>
<p>Path to dependency file: NodeGoat/package.json</p>
<p>Path to vulnerable library: NodeGoat/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/debug/node_modules/ms/package.json,NodeGoat/node_modules/mocha/node_modules/ms/package.json,NodeGoat/node_modules/connect/node_modules/ms/package.json,NodeGoat/node_modules/nyc/node_modules/ms/package.json</p>
<p>

Dependency Hierarchy:
  - mocha-2.5.3.tgz (Root Library)
    - debug-2.2.0.tgz
      - :x: **ms-0.7.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/yoswein/NodeGoat/commit/26ef3f51dc7e983c5a5b8c3b9239aca51a91432b"">26ef3f51dc7e983c5a5b8c3b9239aca51a91432b</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS).

<p>Publish Date: 2017-04-12
<p>URL: <a href=https://github.com/zeit/ms/commit/305f2ddcd4eff7cc7c518aca6bb2b2d2daad8fef>WS-2017-0247</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>3.4</b>)</summary>
<p>

Base Score Metrics not available</p>

</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/vercel/ms/pull/89"">https://github.com/vercel/ms/pull/89</a></p>
<p>Release Date: 2017-04-12</p>
<p>Fix Resolution: 2.1.1</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""ms"",""packageVersion"":""0.7.1"",""packageFilePaths"":[""/package.json""],""isTransitiveDependency"":true,""dependencyTree"":""mocha:2.5.3;debug:2.2.0;ms:0.7.1"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""2.1.1""}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""WS-2017-0247"",""vulnerabilityDetails"":""Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS)."",""vulnerabilityUrl"":""https://github.com/zeit/ms/commit/305f2ddcd4eff7cc7c518aca6bb2b2d2daad8fef"",""cvss2Severity"":""low"",""cvss2Score"":""3.4"",""extraData"":{}}</REMEDIATE> -->",True,"WS-2017-0247 (Low) detected in ms-0.7.1.tgz - ## WS-2017-0247 - Low Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ms-0.7.1.tgz</b></p></summary>

<p>Tiny ms conversion utility</p>
<p>Library home page: <a href=""https://registry.npmjs.org/ms/-/ms-0.7.1.tgz"">https://registry.npmjs.org/ms/-/ms-0.7.1.tgz</a></p>
<p>Path to dependency file: NodeGoat/package.json</p>
<p>Path to vulnerable library: NodeGoat/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/debug/node_modules/ms/package.json,NodeGoat/node_modules/mocha/node_modules/ms/package.json,NodeGoat/node_modules/connect/node_modules/ms/package.json,NodeGoat/node_modules/nyc/node_modules/ms/package.json</p>
<p>

Dependency Hierarchy:
  - mocha-2.5.3.tgz (Root Library)
    - debug-2.2.0.tgz
      - :x: **ms-0.7.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/yoswein/NodeGoat/commit/26ef3f51dc7e983c5a5b8c3b9239aca51a91432b"">26ef3f51dc7e983c5a5b8c3b9239aca51a91432b</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS).

<p>Publish Date: 2017-04-12
<p>URL: <a href=https://github.com/zeit/ms/commit/305f2ddcd4eff7cc7c518aca6bb2b2d2daad8fef>WS-2017-0247</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>3.4</b>)</summary>
<p>

Base Score Metrics not available</p>

</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/vercel/ms/pull/89"">https://github.com/vercel/ms/pull/89</a></p>
<p>Release Date: 2017-04-12</p>
<p>Fix Resolution: 2.1.1</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""ms"",""packageVersion"":""0.7.1"",""packageFilePaths"":[""/package.json""],""isTransitiveDependency"":true,""dependencyTree"":""mocha:2.5.3;debug:2.2.0;ms:0.7.1"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""2.1.1""}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""WS-2017-0247"",""vulnerabilityDetails"":""Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS)."",""vulnerabilityUrl"":""https://github.com/zeit/ms/commit/305f2ddcd4eff7cc7c518aca6bb2b2d2daad8fef"",""cvss2Severity"":""low"",""cvss2Score"":""3.4"",""extraData"":{}}</REMEDIATE> -->",0,ws      low  detected in ms       tgz      ws       low severity vulnerability     vulnerable library    ms       tgz      tiny ms conversion utility   library home page   a href     path to dependency file  nodegoat package json   path to vulnerable library  nodegoat node modules npm node modules node gyp node modules path array node modules array index node modules debug node modules ms package json nodegoat node modules mocha node modules ms package json nodegoat node modules connect node modules ms package json nodegoat node modules nyc node modules ms package json     dependency hierarchy      mocha       tgz  root library        debug       tgz          x    ms       tgz    vulnerable library   found in head commit   a href     found in base branch   master              vulnerability details         affected versions of this package are vulnerable to regular expression denial of service  redos     publish date         url   a href              cvss   score details             base score metrics not available              suggested fix      type  upgrade version   origin   a href     release date          fix resolution                     isopenpronvulnerability  true  ispackagebased  true  isdefaultbranch  true  packages     istransitivedependency  true  dependencytree   mocha       debug       ms         isminimumfixversionavailable  true  minimumfixversion             basebranches     vulnerabilityidentifier   ws       vulnerabilitydetails   affected versions of this package are vulnerable to regular expression denial of service  redos     vulnerabilityurl        ,0
110434,11700810250.0,IssuesEvent,2020-03-06 18:17:46,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/gopls: gopls ignores the fact that the client doesn't support hierarchicalDocumentSymbolSupport,Documentation NeedsFix Tools gopls help wanted,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version

go version go1.13.1 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env

GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/edkolev/Library/Caches/go-build""
GOENV=""/Users/edkolev/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/edkolev/gocode""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/Cellar/go/1.13.1/libexec""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/1.13.1/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/v7/fnkk7zpd0hvdsl45hpj92cc40000gn/T/go-build203896190=/tmp/go-build -gno-record-gcc-switches -fno-common""


</pre></details>

### What did you do?

1. Start emacs, install `eglot` LSP client
2. Open a main.go with contents
```
package main

func main() {
	print(""hello"")
}
```
3. Run `M-x eglot`. At this point eglot notifies gopls for its capabilities as a client. Note that it doesn't report `hierarchicalDocumentSymbolSupport` as supported.
```
:capabilities
                      (:workspace
                       (:applyEdit t :executeCommand
                                   (:dynamicRegistration :json-false)
                                   :workspaceEdit
                                   (:documentChanges :json-false)
                                   :didChangeWatchedFiles
                                   (:dynamicRegistration t)
                                   :symbol
                                   (:dynamicRegistration :json-false))
                       :textDocument
                       (:synchronization
                        (:dynamicRegistration :json-false :willSave t :willSaveWaitUntil t :didSave t)
                        :completion
                        (:dynamicRegistration :json-false :completionItem
                                              (:snippetSupport t)
                                              :contextSupport t)
                        :hover
                        (:dynamicRegistration :json-false)
                        :signatureHelp
                        (:dynamicRegistration :json-false :signatureInformation
                                              (:parameterInformation
                                               (:labelOffsetSupport t)))
                        :references
                        (:dynamicRegistration :json-false)
                        :definition
                        (:dynamicRegistration :json-false)
                        :documentSymbol
                        (:dynamicRegistration :json-false :symbolKind
                                              (:valueSet
                                               [1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26]))
                        :documentHighlight
                        (:dynamicRegistration :json-false)
                        :codeAction
                        (:dynamicRegistration :json-false :codeActionLiteralSupport
                                              (:codeActionKind
                                               (:valueSet
                                                [""quickfix"" ""refactor"" ""refactor.extract"" ""refactor.inline"" ""refactor.rewrite"" ""source"" ""source.organizeImports""])))
                        :formatting
                        (:dynamicRegistration :json-false)
                        :rangeFormatting
                        (:dynamicRegistration :json-false)
                        :rename
                        (:dynamicRegistration :json-false)
                        :publishDiagnostics
                        (:relatedInformation :json-false))
                       :experimental nil)
```
4. Run `M-x imenu` which causes the following communication, note that gopls replies with a hierarchical document symbol response.

```
client-request (id:4) Sat Oct 12 11:59:33 2019:
(:jsonrpc ""2.0"" :id 4 :method ""textDocument/documentSymbol"" :params
          (:textDocument
           (:uri ""file:///Users/edkolev/dev/go-play/main.go"")))

server-reply (id:4) Sat Oct 12 11:59:33 2019:
(:jsonrpc ""2.0"" :result
          [(:name ""main"" :detail ""()"" :kind 12 :range
                  (:start
                   (:line 2 :character 0)
                   :end
                   (:line 4 :character 1))
                  :selectionRange
                  (:start
                   (:line 2 :character 5)
                   :end
                   (:line 2 :character 9)))]
          :id 4)
```
5. Emacs shows an error

### What did you expect to see?

The list of symbols in the main.go file, i.e. the `main()` function.

### What did you see instead?

Emacs error.

## Notes

- this issue has been reported in eglot here https://github.com/joaotavora/eglot/issues/317
- there's an open PR in eglot to add support for hierarchical response to `textDocument/documentSymbol` https://github.com/joaotavora/eglot/pull/303
",1.0,"x/tools/gopls: gopls ignores the fact that the client doesn't support hierarchicalDocumentSymbolSupport - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version

go version go1.13.1 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env

GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/edkolev/Library/Caches/go-build""
GOENV=""/Users/edkolev/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/edkolev/gocode""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/Cellar/go/1.13.1/libexec""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/1.13.1/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/v7/fnkk7zpd0hvdsl45hpj92cc40000gn/T/go-build203896190=/tmp/go-build -gno-record-gcc-switches -fno-common""


</pre></details>

### What did you do?

1. Start emacs, install `eglot` LSP client
2. Open a main.go with contents
```
package main

func main() {
	print(""hello"")
}
```
3. Run `M-x eglot`. At this point eglot notifies gopls for its capabilities as a client. Note that it doesn't report `hierarchicalDocumentSymbolSupport` as supported.
```
:capabilities
                      (:workspace
                       (:applyEdit t :executeCommand
                                   (:dynamicRegistration :json-false)
                                   :workspaceEdit
                                   (:documentChanges :json-false)
                                   :didChangeWatchedFiles
                                   (:dynamicRegistration t)
                                   :symbol
                                   (:dynamicRegistration :json-false))
                       :textDocument
                       (:synchronization
                        (:dynamicRegistration :json-false :willSave t :willSaveWaitUntil t :didSave t)
                        :completion
                        (:dynamicRegistration :json-false :completionItem
                                              (:snippetSupport t)
                                              :contextSupport t)
                        :hover
                        (:dynamicRegistration :json-false)
                        :signatureHelp
                        (:dynamicRegistration :json-false :signatureInformation
                                              (:parameterInformation
                                               (:labelOffsetSupport t)))
                        :references
                        (:dynamicRegistration :json-false)
                        :definition
                        (:dynamicRegistration :json-false)
                        :documentSymbol
                        (:dynamicRegistration :json-false :symbolKind
                                              (:valueSet
                                               [1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26]))
                        :documentHighlight
                        (:dynamicRegistration :json-false)
                        :codeAction
                        (:dynamicRegistration :json-false :codeActionLiteralSupport
                                              (:codeActionKind
                                               (:valueSet
                                                [""quickfix"" ""refactor"" ""refactor.extract"" ""refactor.inline"" ""refactor.rewrite"" ""source"" ""source.organizeImports""])))
                        :formatting
                        (:dynamicRegistration :json-false)
                        :rangeFormatting
                        (:dynamicRegistration :json-false)
                        :rename
                        (:dynamicRegistration :json-false)
                        :publishDiagnostics
                        (:relatedInformation :json-false))
                       :experimental nil)
```
4. Run `M-x imenu` which causes the following communication, note that gopls replies with a hierarchical document symbol response.

```
client-request (id:4) Sat Oct 12 11:59:33 2019:
(:jsonrpc ""2.0"" :id 4 :method ""textDocument/documentSymbol"" :params
          (:textDocument
           (:uri ""file:///Users/edkolev/dev/go-play/main.go"")))

server-reply (id:4) Sat Oct 12 11:59:33 2019:
(:jsonrpc ""2.0"" :result
          [(:name ""main"" :detail ""()"" :kind 12 :range
                  (:start
                   (:line 2 :character 0)
                   :end
                   (:line 4 :character 1))
                  :selectionRange
                  (:start
                   (:line 2 :character 5)
                   :end
                   (:line 2 :character 9)))]
          :id 4)
```
5. Emacs shows an error

### What did you expect to see?

The list of symbols in the main.go file, i.e. the `main()` function.

### What did you see instead?

Emacs error.

## Notes

- this issue has been reported in eglot here https://github.com/joaotavora/eglot/issues/317
- there's an open PR in eglot to add support for hierarchical response to `textDocument/documentSymbol` https://github.com/joaotavora/eglot/pull/303
",1,x tools gopls  gopls ignores the fact that the client doesn t support hierarchicaldocumentsymbolsupport            what version of go are you using   go version            go version    go version       darwin             does this issue reproduce with the latest release     yes         what operating system and processor architecture are you using   go env          go env  output       go env          goarch      gobin     gocache   users edkolev library caches go build   goenv   users edkolev library application support go env   goexe     goflags     gohostarch      gohostos  darwin   gonoproxy     gonosumdb     goos  darwin   gopath   users edkolev gocode   goprivate     goproxy     goroot   usr local cellar go       libexec   gosumdb  sum golang org   gotmpdir     gotooldir   usr local cellar go       libexec pkg tool darwin     gccgo  gccgo   ar  ar   cc  clang   cxx  clang     cgo enabled      gomod     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders     t go    tmp go build  gno record gcc switches  fno common                 what did you do        start emacs  install  eglot  lsp client     open a main go with contents       package main    func main      	print  hello               run  m x eglot   at this point eglot notifies gopls for its capabilities as a client  note that it doesn t report  hierarchicaldocumentsymbolsupport  as supported         capabilities                          workspace                           applyedit t  executecommand                                       dynamicregistration  json false                                       workspaceedit                                       documentchanges  json false                                       didchangewatchedfiles                                       dynamicregistration t                                       symbol                                       dynamicregistration  json false                            textdocument                           synchronization                            dynamicregistration  json false  willsave t  willsavewaituntil t  didsave t                            completion                            dynamicregistration  json false  completionitem                                                  snippetsupport t                                                  contextsupport t                            hover                            dynamicregistration  json false                            signaturehelp                            dynamicregistration  json false  signatureinformation                                                  parameterinformation                                                   labeloffsetsupport t                              references                            dynamicregistration  json false                            definition                            dynamicregistration  json false                            documentsymbol                            dynamicregistration  json false  symbolkind                                                  valueset                                                                               documenthighlight                            dynamicregistration  json false                            codeaction                            dynamicregistration  json false  codeactionliteralsupport                                                  codeactionkind                                                   valueset                                                                                 formatting                            dynamicregistration  json false                            rangeformatting                            dynamicregistration  json false                            rename                            dynamicregistration  json false                            publishdiagnostics                            relatedinformation  json false                            experimental nil           run  m x imenu  which causes the following communication  note that gopls replies with a hierarchical document symbol response          client request  id    sat oct               jsonrpc        id    method  textdocument documentsymbol   params              textdocument               uri  file    users edkolev dev go play main go        server reply  id    sat oct               jsonrpc        result               name  main   detail       kind    range                      start                       line    character                         end                       line    character                         selectionrange                      start                       line    character                         end                       line    character                   id             emacs shows an error        what did you expect to see     the list of symbols in the main go file  i e  the  main    function         what did you see instead     emacs error        notes      this issue has been reported in eglot here      there s an open pr in eglot to add support for hierarchical response to  textdocument documentsymbol     ,1
690587,23664781767.0,IssuesEvent,2022-08-26 19:31:36,dojot/dojot,https://api.github.com/repos/dojot/dojot,closed,[GUI NX - v-guinx-19-05-22] When accessing the Dashboard tosts are being displayed on the screen. ,Type:Bug :bug: Priority:Low Team:Frontend,"* **I'm submitting a ...**
  - [x] bug report
  - [ ] feature request
  - [ ] support request

When accessing the Dashboard Toast are being displayed on the screen. 

![2022-06-22_10-08.png](https://images.zenhubusercontent.com/5d138e07f0489e0b0b4be7a3/0b53c1a3-30e9-4286-87e6-c1b358179f57)


* **Please tell us about your environment:**
  
  - Version: v-guinx-19-05-22
  - Environment: [docker-compose]
  - Operating system: [Ubuntu 20.04]
",1.0,"[GUI NX - v-guinx-19-05-22] When accessing the Dashboard tosts are being displayed on the screen.  - * **I'm submitting a ...**
  - [x] bug report
  - [ ] feature request
  - [ ] support request

When accessing the Dashboard Toast are being displayed on the screen. 

![2022-06-22_10-08.png](https://images.zenhubusercontent.com/5d138e07f0489e0b0b4be7a3/0b53c1a3-30e9-4286-87e6-c1b358179f57)


* **Please tell us about your environment:**
  
  - Version: v-guinx-19-05-22
  - Environment: [docker-compose]
  - Operating system: [Ubuntu 20.04]
",0,  when accessing the dashboard tosts are being displayed on the screen         i m submitting a             bug report       feature request       support request  when accessing the dashboard toast are being displayed on the screen               please tell us about your environment           version  v guinx           environment        operating system    ,0
136868,12736737203.0,IssuesEvent,2020-06-25 17:27:13,golang/go,https://api.github.com/repos/golang/go,closed,crypto/x509: documentation about SSL_CERT_FILE and SSL_CERT_DIR is incorrect,Documentation NeedsInvestigation,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""/Users/xxx/gopath/bin""
GOCACHE=""/Users/xxx/Library/Caches/go-build""
GOENV=""/Users/xxx/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/xxx/gopath""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/usr/local/go/src/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/2b/74fz3jhd4wz4vnbf4z7ywzww0000gp/T/go-build191944931=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

I tried to use `SSL_CERT_FILE` to try to override the default system location on macOS.

### What did you expect to see?

`x509.SystemCertPool` use my environment variable.

### What did you see instead?

It did not.

Per `crypto/x509`'s docs:

> On UNIX systems the environment variables SSL_CERT_FILE and SSL_CERT_DIR can be used to override the system default locations...

macOS is very much a UNIX system (afaik it's verified UNIX, or at least was) and at any rate, it's [usually assumed to be included in the `_unix.go` convention](https://github.com/golang/go/issues/20322).

At the very least, the docs should specify which operating systems allow the environment variable override.
",1.0,"crypto/x509: documentation about SSL_CERT_FILE and SSL_CERT_DIR is incorrect - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""/Users/xxx/gopath/bin""
GOCACHE=""/Users/xxx/Library/Caches/go-build""
GOENV=""/Users/xxx/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/xxx/gopath""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/usr/local/go/src/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/2b/74fz3jhd4wz4vnbf4z7ywzww0000gp/T/go-build191944931=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

I tried to use `SSL_CERT_FILE` to try to override the default system location on macOS.

### What did you expect to see?

`x509.SystemCertPool` use my environment variable.

### What did you see instead?

It did not.

Per `crypto/x509`'s docs:

> On UNIX systems the environment variables SSL_CERT_FILE and SSL_CERT_DIR can be used to override the system default locations...

macOS is very much a UNIX system (afaik it's verified UNIX, or at least was) and at any rate, it's [usually assumed to be included in the `_unix.go` convention](https://github.com/golang/go/issues/20322).

At the very least, the docs should specify which operating systems allow the environment variable override.
",1,crypto    documentation about ssl cert file and ssl cert dir is incorrect         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version            go version  go version     darwin             does this issue reproduce with the latest release     yes         what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin   users xxx gopath bin   gocache   users xxx library caches go build   goenv   users xxx library application support go env   goexe     goflags     gohostarch      gohostos  darwin   goinsecure     gonoproxy     gonosumdb     goos  darwin   gopath   users xxx gopath   goprivate     goproxy     goroot   usr local go   gosumdb  sum golang org   gotmpdir     gotooldir   usr local go pkg tool darwin     gccgo  gccgo   ar  ar   cc  clang   cxx  clang     cgo enabled      gomod   usr local go src go mod   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders     t go    tmp go build  gno record gcc switches  fno common             what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best          i tried to use  ssl cert file  to try to override the default system location on macos         what did you expect to see        systemcertpool  use my environment variable         what did you see instead     it did not     per  crypto    s docs       on unix systems the environment variables ssl cert file and ssl cert dir can be used to override the system default locations       macos is very much a unix system  afaik it s verified unix  or at least was  and at any rate  it s        at the very least  the docs should specify which operating systems allow the environment variable override   ,1
5156,2909691363.0,IssuesEvent,2015-06-21 00:25:37,golang/go,https://api.github.com/repos/golang/go,closed,misc/ios: document ideviceinfo,Documentation,detect.go shells out to a command named ideviceinfo. It's not clear how to install this binary and where it comes from. Document the installation steps or give a link to an equivalent doc.,1.0,misc/ios: document ideviceinfo - detect.go shells out to a command named ideviceinfo. It's not clear how to install this binary and where it comes from. Document the installation steps or give a link to an equivalent doc.,1,misc ios  document ideviceinfo   detect go shells out to a command named ideviceinfo  it s not clear how to install this binary and where it comes from  document the installation steps or give a link to an equivalent doc ,1
16341,10797885435.0,IssuesEvent,2019-11-06 08:55:36,frappe/erpnext,https://api.github.com/repos/frappe/erpnext,closed,Feature Request - SubForms as a field type,feature-request framework usability,"**Proposed Feature**
Creation of a subform _Field Type_ where the subform is a _DocType_ within the main _DocType_?

**Current Context**
Currently a table can be accessed in this way. However the customization ability the table gives is limited unless non out of the box solution is used (jquery e.t.c).

**Application**
In my case this can be useful in a situation where I need several users to work on a specific form, the users will have different access rights to the subform and its fields depending on different situations, new subforms can be appended/deleted in what will look like a table with each row representing a subform.

This is better than having a table in the form as it doesnt have form attributes.
Meaning that I can apply form controls or change attributes the same way I could with any other doctype under customization section/through custom script.

Please up vote this feature to be included in future releases...Thanks",True,"Feature Request - SubForms as a field type - **Proposed Feature**
Creation of a subform _Field Type_ where the subform is a _DocType_ within the main _DocType_?

**Current Context**
Currently a table can be accessed in this way. However the customization ability the table gives is limited unless non out of the box solution is used (jquery e.t.c).

**Application**
In my case this can be useful in a situation where I need several users to work on a specific form, the users will have different access rights to the subform and its fields depending on different situations, new subforms can be appended/deleted in what will look like a table with each row representing a subform.

This is better than having a table in the form as it doesnt have form attributes.
Meaning that I can apply form controls or change attributes the same way I could with any other doctype under customization section/through custom script.

Please up vote this feature to be included in future releases...Thanks",0,feature request   subforms as a field type     proposed feature    creation of a subform  field type  where the subform is a  doctype  within the main  doctype        current context    currently a table can be accessed in this way  however the customization ability the table gives is limited unless non out of the box solution is used  jquery e t c        application    in my case this can be useful in a situation where i need several users to work on a specific form  the users will have different access rights to the subform and its fields depending on different situations  new subforms can be appended deleted in what will look like a table with each row representing a subform     this is better than having a table in the form as it doesnt have form attributes   meaning that i can apply form controls or change attributes the same way i could with any other doctype under customization section through custom script     please up vote this feature to be included in future releases   thanks,0
14346,3829564672.0,IssuesEvent,2016-03-31 11:16:00,golang/go,https://api.github.com/repos/golang/go,closed,net/http: docs show insufficient way to cleanup Response Body,Documentation,"<pre>What does 'go version' print?

go version go1.4rc1 darwin/amd64

What steps reproduce the problem?
If possible, include a link to a program on play.golang.org.

1. View the docs at <a href=""http://tip.golang.org/pkg/net/http/"">http://tip.golang.org/pkg/net/http/</a>

What happened?

Docs show the following method for cleaning up response bodies:

resp, err := http.Get(&quot;<a href=""http://example.com/&quot"">http://example.com/&quot</a>;)
if err != nil {
	// handle error
}
defer resp.Body.Close()

What should have happened instead?

The method shown above does not handle the case where both resp and err are non-nil,
which was preserved for compatibility reasons in #3795. If the response was a redirect
and the CheckRedirect func returned an error, the http.Client will return both the
Response and an error. That response's Body would never be closed under the example
shown above, and its connection would leak.

Unfortunately, I suspect this compatibility fix has probably led to lots of potential
leaks in Go code in the wild. Since breaking Go 1 compatibility is not an option, the
docs for Go 1 should show people how to correctly clean up after responses without
leaking conns &amp; file descriptors.

Instead, the following should work and would not leak:

resp, err := http.Get(&quot;<a href=""http://example.com/&quot"">http://example.com/&quot</a>;)
if resp != nil {
	defer resp.Body.Close()
}
if err != nil {
	// handle error
}

Please provide any additional information below.</pre>",1.0,"net/http: docs show insufficient way to cleanup Response Body - <pre>What does 'go version' print?

go version go1.4rc1 darwin/amd64

What steps reproduce the problem?
If possible, include a link to a program on play.golang.org.

1. View the docs at <a href=""http://tip.golang.org/pkg/net/http/"">http://tip.golang.org/pkg/net/http/</a>

What happened?

Docs show the following method for cleaning up response bodies:

resp, err := http.Get(&quot;<a href=""http://example.com/&quot"">http://example.com/&quot</a>;)
if err != nil {
	// handle error
}
defer resp.Body.Close()

What should have happened instead?

The method shown above does not handle the case where both resp and err are non-nil,
which was preserved for compatibility reasons in #3795. If the response was a redirect
and the CheckRedirect func returned an error, the http.Client will return both the
Response and an error. That response's Body would never be closed under the example
shown above, and its connection would leak.

Unfortunately, I suspect this compatibility fix has probably led to lots of potential
leaks in Go code in the wild. Since breaking Go 1 compatibility is not an option, the
docs for Go 1 should show people how to correctly clean up after responses without
leaking conns &amp; file descriptors.

Instead, the following should work and would not leak:

resp, err := http.Get(&quot;<a href=""http://example.com/&quot"">http://example.com/&quot</a>;)
if resp != nil {
	defer resp.Body.Close()
}
if err != nil {
	// handle error
}

Please provide any additional information below.</pre>",1,net http  docs show insufficient way to cleanup response body    what does  go version  print   go version     darwin    what steps reproduce the problem  if possible  include a link to a program on play golang org      view the docs at  a href     what happened   docs show the following method for cleaning up response bodies   resp  err    http get  quot  a href    if err    nil   	   handle error   defer resp body close    what should have happened instead   the method shown above does not handle the case where both resp and err are non nil  which was preserved for compatibility reasons in     if the response was a redirect and the checkredirect func returned an error  the http client will return both the response and an error  that response s body would never be closed under the example shown above  and its connection would leak   unfortunately  i suspect this compatibility fix has probably led to lots of potential leaks in go code in the wild  since breaking go   compatibility is not an option  the docs for go   should show people how to correctly clean up after responses without leaking conns  amp  file descriptors   instead  the following should work and would not leak   resp  err    http get  quot  a href    if resp    nil   	defer resp body close     if err    nil   	   handle error    please provide any additional information below  ,1
253689,19161549963.0,IssuesEvent,2021-12-03 01:10:04,golang/go,https://api.github.com/repos/golang/go,closed,builtin: add documentation for `any` and `comparable` to pseudo-package `builtin`,Documentation release-blocker okay-after-beta1,The new predeclared identifiers `any` and `comparable` in Go 1.18 should have documentation entries in the `builtin` pseudo-package: https://pkg.go.dev/builtin@master,1.0,builtin: add documentation for `any` and `comparable` to pseudo-package `builtin` - The new predeclared identifiers `any` and `comparable` in Go 1.18 should have documentation entries in the `builtin` pseudo-package: https://pkg.go.dev/builtin@master,1,builtin  add documentation for  any  and  comparable  to pseudo package  builtin    the new predeclared identifiers  any  and  comparable  in go     should have documentation entries in the  builtin  pseudo package   ,1
177492,14630308793.0,IssuesEvent,2020-12-23 17:27:34,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: Retract field missing from 'go help mod edit' definition of the GoMod struct,Documentation GoCommand NeedsFix help wanted,"### What version of Go are you using (`go version`)?

<pre>
v1.16 beta1
</pre>

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/tmp/go-cache""
GOENV=""/home/gary/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/tmp/go-mod-cache""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/media/Data/Projects/Go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/opt/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""/tmp""
GOTOOLDIR=""/opt/go/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""go1.16beta1""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/media/Data/Projects/Go/src/github.com/nomad-software/vend/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build3728920539=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?
Issue the following command
<pre>
go help mod edit
</pre>

### What did you expect to see?
Complete information regarding the new retract flag in regard to the json struct types.


### What did you see instead?
<pre>
...
type Module struct {
		Path string
		Version string
	}

	type GoMod struct {
		Module  Module
		Go      string
		Require []Require
		Exclude []Module
		Replace []Replace
	}

	type Require struct {
		Path string
		Version string
		Indirect bool
	}

	type Replace struct {
		Old Module
		New Module
	}

	type Retract struct {
		Low       string
		High      string
		Rationale string
	}
...
</pre>
Notice that the `GoMod` definition is missing the `Retract` field.",1.0,"cmd/go: Retract field missing from 'go help mod edit' definition of the GoMod struct - ### What version of Go are you using (`go version`)?

<pre>
v1.16 beta1
</pre>

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/tmp/go-cache""
GOENV=""/home/gary/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/tmp/go-mod-cache""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/media/Data/Projects/Go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/opt/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""/tmp""
GOTOOLDIR=""/opt/go/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""go1.16beta1""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/media/Data/Projects/Go/src/github.com/nomad-software/vend/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build3728920539=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?
Issue the following command
<pre>
go help mod edit
</pre>

### What did you expect to see?
Complete information regarding the new retract flag in regard to the json struct types.


### What did you see instead?
<pre>
...
type Module struct {
		Path string
		Version string
	}

	type GoMod struct {
		Module  Module
		Go      string
		Require []Require
		Exclude []Module
		Replace []Replace
	}

	type Require struct {
		Path string
		Version string
		Indirect bool
	}

	type Replace struct {
		Old Module
		New Module
	}

	type Retract struct {
		Low       string
		High      string
		Rationale string
	}
...
</pre>
Notice that the `GoMod` definition is missing the `Retract` field.",1,cmd go  retract field missing from  go help mod edit  definition of the gomod struct       what version of go are you using   go version                          does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env          go env  output           goarch      gobin     gocache   tmp go cache   goenv   home gary  config go env   goexe     goflags     gohostarch      gohostos  linux   goinsecure     gomodcache   tmp go mod cache   gonoproxy     gonosumdb     goos  linux   gopath   media data projects go   goprivate     goproxy     goroot   opt go   gosumdb  sum golang org   gotmpdir   tmp   gotooldir   opt go pkg tool linux     govcs     goversion        gccgo  gccgo   ar  ar   cc  gcc   cxx  g     cgo enabled      gomod   media data projects go src github com nomad software vend go mod   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches             what did you do   issue the following command     go help mod edit           what did you expect to see   complete information regarding the new retract flag in regard to the json struct types           what did you see instead           type module struct    		path string  		version string  	     	type gomod struct    		module  module  		go      string  		require  require  		exclude  module  		replace  replace  	     	type require struct    		path string  		version string  		indirect bool  	     	type replace struct    		old module  		new module  	     	type retract struct    		low       string  		high      string  		rationale string  	           notice that the  gomod  definition is missing the  retract  field ,1
297117,22340355028.0,IssuesEvent,2022-06-14 23:45:05,golang/go,https://api.github.com/repos/golang/go,closed,"spec: review/clarify uses of ""slice of bytes""",Documentation,"This is a follow-up issue for #23536: Comb through documentation (spec, builtins) to verify the use of the term ""slice of bytes"". The spec appears to mean by this any type whose underlying type is `[]byte`. But not all implementations agree.
",1.0,"spec: review/clarify uses of ""slice of bytes"" - This is a follow-up issue for #23536: Comb through documentation (spec, builtins) to verify the use of the term ""slice of bytes"". The spec appears to mean by this any type whose underlying type is `[]byte`. But not all implementations agree.
",1,spec  review clarify uses of  slice of bytes    this is a follow up issue for     comb through documentation  spec  builtins  to verify the use of the term  slice of bytes   the spec appears to mean by this any type whose underlying type is   byte   but not all implementations agree   ,1
140435,21097940244.0,IssuesEvent,2022-04-04 12:09:26,Regalis11/Barotrauma,https://api.github.com/repos/Regalis11/Barotrauma,closed,Buff Ethanol & Tobacco psychosis resist,Feature request Design Low prio Balance,"Obviously they should still not be able to compare with antidote Haloperidol, but the amount you get from drinking a whole bottle (2 uses) or the amount gained from smoking 1 bag of pipe tobacco (after you spent so long growing it and crafting it for it to get used up in 5 seconds) is almost completely insubstantial when consumed in 'reasonable' quantities.",1.0,"Buff Ethanol & Tobacco psychosis resist - Obviously they should still not be able to compare with antidote Haloperidol, but the amount you get from drinking a whole bottle (2 uses) or the amount gained from smoking 1 bag of pipe tobacco (after you spent so long growing it and crafting it for it to get used up in 5 seconds) is almost completely insubstantial when consumed in 'reasonable' quantities.",0,buff ethanol   tobacco psychosis resist   obviously they should still not be able to compare with antidote haloperidol  but the amount you get from drinking a whole bottle    uses  or the amount gained from smoking   bag of pipe tobacco  after you spent so long growing it and crafting it for it to get used up in   seconds  is almost completely insubstantial when consumed in  reasonable  quantities ,0
54833,7926717247.0,IssuesEvent,2018-07-06 04:00:40,golang/go,https://api.github.com/repos/golang/go,closed,x/vgo: fix installation instructions on README,Documentation WaitingForInfo,"Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
10.2

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
OSX 17.4.0 Darwin Kernel Version 17.4.0: Sun Dec 17 09:19:54 PST 2017; root:xnu-4570.41.2~1/RELEASE_X86_64 x86_64

### What did you do?

go get -u golang.org/x/vgo .

If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.


### What did you expect to see?
 installation of vgo

### What did you see instead?

It hung

### Solution

change documentation to 

go get -u github.com/golang/vgo",1.0,"x/vgo: fix installation instructions on README - Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
10.2

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
OSX 17.4.0 Darwin Kernel Version 17.4.0: Sun Dec 17 09:19:54 PST 2017; root:xnu-4570.41.2~1/RELEASE_X86_64 x86_64

### What did you do?

go get -u golang.org/x/vgo .

If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.


### What did you expect to see?
 installation of vgo

### What did you see instead?

It hung

### Solution

change documentation to 

go get -u github.com/golang/vgo",1,x vgo  fix installation instructions on readme   please answer these questions before submitting your issue  thanks           what version of go are you using   go version                does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env     osx       darwin kernel version        sun dec         pst    root xnu         release                what did you do     go get  u golang org x vgo      if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best           what did you expect to see    installation of vgo        what did you see instead     it hung        solution    change documentation to     go get  u github com golang vgo,1
370129,25889801032.0,IssuesEvent,2022-12-14 17:02:20,golang/go,https://api.github.com/repos/golang/go,opened,"spec: ""type parameters are interfaces"" is confusing",Documentation,"Per the spec, the underlying type of a type parameter is its constraint interface. Similarly to how we talk about an X type (say, an array type) if the underlying type of a named type is X, we also talk about interface types for type parameters. This is confusing.

Reminder issue to try clearer prose where needed.

See also @findleyr 's comment [here](https://go-review.git.corp.google.com/c/go/+/457095/3/doc/go_spec.html#5137).",1.0,"spec: ""type parameters are interfaces"" is confusing - Per the spec, the underlying type of a type parameter is its constraint interface. Similarly to how we talk about an X type (say, an array type) if the underlying type of a named type is X, we also talk about interface types for type parameters. This is confusing.

Reminder issue to try clearer prose where needed.

See also @findleyr 's comment [here](https://go-review.git.corp.google.com/c/go/+/457095/3/doc/go_spec.html#5137).",1,spec   type parameters are interfaces  is confusing   per the spec  the underlying type of a type parameter is its constraint interface  similarly to how we talk about an x type  say  an array type  if the underlying type of a named type is x  we also talk about interface types for type parameters  this is confusing     reminder issue to try clearer prose where needed     see also  findleyr  s comment    ,1
12057,3573604348.0,IssuesEvent,2016-01-27 07:37:39,golang/go,https://api.github.com/repos/golang/go,closed,database/sql: document allowed Scan conversions,Documentation,"<pre>What does 'go version' print?

go version go1.3.3 darwin/amd64

What steps reproduce the problem?
If possible, include a link to a program on play.golang.org.

<a href=""http://play.golang.org/p/mk7wJKtz4H"">http://play.golang.org/p/mk7wJKtz4H</a>

What happened?

NullString.Scan didn't accept a time.Time value:

error: unsupported driver -&gt; Scan pair: time.Time -&gt; *string

What should have happened instead?

It should have converted the time.Time value into a string, just it does with any other
type that Scan accepts.

Please provide any additional information below.

The contract for Scanner says:

        // Scan assigns a value from a database driver.
        //
        // The src value will be of one of the following restricted
        // set of types:
        //
        //    int64
        //    float64
        //    bool
        //    []byte
        //    string
        //    time.Time
        //    nil - for NULL values
        //
        // An error should be returned if the value can not be stored
        // without loss of information.
        Scan(src interface{}) error

All of the other types work by formatting the values as strings. Given that time.Time
has a String() function, I would assume it would be handled as well.</pre>",1.0,"database/sql: document allowed Scan conversions - <pre>What does 'go version' print?

go version go1.3.3 darwin/amd64

What steps reproduce the problem?
If possible, include a link to a program on play.golang.org.

<a href=""http://play.golang.org/p/mk7wJKtz4H"">http://play.golang.org/p/mk7wJKtz4H</a>

What happened?

NullString.Scan didn't accept a time.Time value:

error: unsupported driver -&gt; Scan pair: time.Time -&gt; *string

What should have happened instead?

It should have converted the time.Time value into a string, just it does with any other
type that Scan accepts.

Please provide any additional information below.

The contract for Scanner says:

        // Scan assigns a value from a database driver.
        //
        // The src value will be of one of the following restricted
        // set of types:
        //
        //    int64
        //    float64
        //    bool
        //    []byte
        //    string
        //    time.Time
        //    nil - for NULL values
        //
        // An error should be returned if the value can not be stored
        // without loss of information.
        Scan(src interface{}) error

All of the other types work by formatting the values as strings. Given that time.Time
has a String() function, I would assume it would be handled as well.</pre>",1,database sql  document allowed scan conversions    what does  go version  print   go version       darwin    what steps reproduce the problem  if possible  include a link to a program on play golang org    a href     what happened   nullstring scan didn t accept a time time value   error  unsupported driver   gt  scan pair  time time   gt   string  what should have happened instead   it should have converted the time time value into a string  just it does with any other type that scan accepts   please provide any additional information below   the contract for scanner says              scan assigns a value from a database driver                        the src value will be of one of the following restricted            set of types                                                           bool                byte               string               time time               nil   for null values                       an error should be returned if the value can not be stored            without loss of information          scan src interface    error  all of the other types work by formatting the values as strings  given that time time has a string   function  i would assume it would be handled as well  ,1
168683,20795273668.0,IssuesEvent,2022-03-17 08:40:18,nvenkatesh1/SCA_test_JS,https://api.github.com/repos/nvenkatesh1/SCA_test_JS,opened,react-ace-5.1.1.tgz: 2 vulnerabilities (highest severity is: 6.1),security vulnerability,"<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>react-ace-5.1.1.tgz</b></p></summary>

<p></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/opencollective/node_modules/node-fetch/package.json</p>
<p>


<p>Found in HEAD commit: <a href=""https://github.com/nvenkatesh1/SCA_test_JS/commit/eb47eeefc02a252a76628fec10a3c26aacb34024"">eb47eeefc02a252a76628fec10a3c26aacb34024</a></p></details>

## Vulnerabilities

| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2022-0235](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0235) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | node-fetch-1.6.3.tgz | Transitive | 5.3.0 | &#9989; |
| [CVE-2020-15168](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15168) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | node-fetch-1.6.3.tgz | Transitive | 5.3.0 | &#9989; |


## Details

<details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-0235</summary>


###  Vulnerable Library - <b>node-fetch-1.6.3.tgz</b></p>

<p>A light-weight module that brings window.fetch to node.js and io.js</p>
<p>Library home page: <a href=""https://registry.npmjs.org/node-fetch/-/node-fetch-1.6.3.tgz"">https://registry.npmjs.org/node-fetch/-/node-fetch-1.6.3.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/opencollective/node_modules/node-fetch/package.json</p>
<p>

Dependency Hierarchy:
  - react-ace-5.1.1.tgz (Root Library)
    - opencollective-1.0.3.tgz
      - :x: **node-fetch-1.6.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/nvenkatesh1/SCA_test_JS/commit/eb47eeefc02a252a76628fec10a3c26aacb34024"">eb47eeefc02a252a76628fec10a3c26aacb34024</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor

<p>Publish Date: 2022-01-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0235>CVE-2022-0235</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>6.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Changed
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/advisories/GHSA-r683-j2x4-v87g"">https://github.com/advisories/GHSA-r683-j2x4-v87g</a></p>
<p>Release Date: 2022-01-16</p>
<p>Fix Resolution (node-fetch): 2.6.7</p>
<p>Direct dependency fix Resolution (react-ace): 5.3.0</p>

</p>

<p></p>


:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2020-15168</summary>


###  Vulnerable Library - <b>node-fetch-1.6.3.tgz</b></p>

<p>A light-weight module that brings window.fetch to node.js and io.js</p>
<p>Library home page: <a href=""https://registry.npmjs.org/node-fetch/-/node-fetch-1.6.3.tgz"">https://registry.npmjs.org/node-fetch/-/node-fetch-1.6.3.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/opencollective/node_modules/node-fetch/package.json</p>
<p>

Dependency Hierarchy:
  - react-ace-5.1.1.tgz (Root Library)
    - opencollective-1.0.3.tgz
      - :x: **node-fetch-1.6.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/nvenkatesh1/SCA_test_JS/commit/eb47eeefc02a252a76628fec10a3c26aacb34024"">eb47eeefc02a252a76628fec10a3c26aacb34024</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
node-fetch before versions 2.6.1 and 3.0.0-beta.9 did not honor the size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure. For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don't double-check the size of the data after fetch() has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.

<p>Publish Date: 2020-09-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15168>CVE-2020-15168</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>5.3</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: Low
</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/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r"">https://github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r</a></p>
<p>Release Date: 2020-09-17</p>
<p>Fix Resolution (node-fetch): 2.6.1</p>
<p>Direct dependency fix Resolution (react-ace): 5.3.0</p>

</p>

<p></p>


:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>

***

<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p>
<!-- <REMEDIATE>[{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""react-ace"",""packageVersion"":""5.1.1"",""packageFilePaths"":[""/package.json""],""isTransitiveDependency"":false,""dependencyTree"":""react-ace:5.1.1"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""5.3.0"",""isBinary"":false}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""CVE-2022-0235"",""vulnerabilityDetails"":""node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor"",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0235"",""cvss3Severity"":""medium"",""cvss3Score"":""6.1"",""cvss3Metrics"":{""A"":""None"",""AC"":""Low"",""PR"":""None"",""S"":""Changed"",""C"":""Low"",""UI"":""Required"",""AV"":""Network"",""I"":""Low""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""react-ace"",""packageVersion"":""5.1.1"",""packageFilePaths"":[""/package.json""],""isTransitiveDependency"":false,""dependencyTree"":""react-ace:5.1.1"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""5.3.0"",""isBinary"":false}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""CVE-2020-15168"",""vulnerabilityDetails"":""node-fetch before versions 2.6.1 and 3.0.0-beta.9 did not honor the size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure. For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don\u0027t double-check the size of the data after fetch() has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15168"",""cvss3Severity"":""medium"",""cvss3Score"":""5.3"",""cvss3Metrics"":{""A"":""Low"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""None"",""AV"":""Network"",""I"":""None""},""extraData"":{}}]</REMEDIATE> -->",True,"react-ace-5.1.1.tgz: 2 vulnerabilities (highest severity is: 6.1) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>react-ace-5.1.1.tgz</b></p></summary>

<p></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/opencollective/node_modules/node-fetch/package.json</p>
<p>


<p>Found in HEAD commit: <a href=""https://github.com/nvenkatesh1/SCA_test_JS/commit/eb47eeefc02a252a76628fec10a3c26aacb34024"">eb47eeefc02a252a76628fec10a3c26aacb34024</a></p></details>

## Vulnerabilities

| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2022-0235](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0235) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | node-fetch-1.6.3.tgz | Transitive | 5.3.0 | &#9989; |
| [CVE-2020-15168](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15168) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | node-fetch-1.6.3.tgz | Transitive | 5.3.0 | &#9989; |


## Details

<details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-0235</summary>


###  Vulnerable Library - <b>node-fetch-1.6.3.tgz</b></p>

<p>A light-weight module that brings window.fetch to node.js and io.js</p>
<p>Library home page: <a href=""https://registry.npmjs.org/node-fetch/-/node-fetch-1.6.3.tgz"">https://registry.npmjs.org/node-fetch/-/node-fetch-1.6.3.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/opencollective/node_modules/node-fetch/package.json</p>
<p>

Dependency Hierarchy:
  - react-ace-5.1.1.tgz (Root Library)
    - opencollective-1.0.3.tgz
      - :x: **node-fetch-1.6.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/nvenkatesh1/SCA_test_JS/commit/eb47eeefc02a252a76628fec10a3c26aacb34024"">eb47eeefc02a252a76628fec10a3c26aacb34024</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor

<p>Publish Date: 2022-01-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0235>CVE-2022-0235</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>6.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Changed
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/advisories/GHSA-r683-j2x4-v87g"">https://github.com/advisories/GHSA-r683-j2x4-v87g</a></p>
<p>Release Date: 2022-01-16</p>
<p>Fix Resolution (node-fetch): 2.6.7</p>
<p>Direct dependency fix Resolution (react-ace): 5.3.0</p>

</p>

<p></p>


:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2020-15168</summary>


###  Vulnerable Library - <b>node-fetch-1.6.3.tgz</b></p>

<p>A light-weight module that brings window.fetch to node.js and io.js</p>
<p>Library home page: <a href=""https://registry.npmjs.org/node-fetch/-/node-fetch-1.6.3.tgz"">https://registry.npmjs.org/node-fetch/-/node-fetch-1.6.3.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/opencollective/node_modules/node-fetch/package.json</p>
<p>

Dependency Hierarchy:
  - react-ace-5.1.1.tgz (Root Library)
    - opencollective-1.0.3.tgz
      - :x: **node-fetch-1.6.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/nvenkatesh1/SCA_test_JS/commit/eb47eeefc02a252a76628fec10a3c26aacb34024"">eb47eeefc02a252a76628fec10a3c26aacb34024</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
node-fetch before versions 2.6.1 and 3.0.0-beta.9 did not honor the size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure. For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don't double-check the size of the data after fetch() has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.

<p>Publish Date: 2020-09-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15168>CVE-2020-15168</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>5.3</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: Low
</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/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r"">https://github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r</a></p>
<p>Release Date: 2020-09-17</p>
<p>Fix Resolution (node-fetch): 2.6.1</p>
<p>Direct dependency fix Resolution (react-ace): 5.3.0</p>

</p>

<p></p>


:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>

***

<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p>
<!-- <REMEDIATE>[{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""react-ace"",""packageVersion"":""5.1.1"",""packageFilePaths"":[""/package.json""],""isTransitiveDependency"":false,""dependencyTree"":""react-ace:5.1.1"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""5.3.0"",""isBinary"":false}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""CVE-2022-0235"",""vulnerabilityDetails"":""node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor"",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0235"",""cvss3Severity"":""medium"",""cvss3Score"":""6.1"",""cvss3Metrics"":{""A"":""None"",""AC"":""Low"",""PR"":""None"",""S"":""Changed"",""C"":""Low"",""UI"":""Required"",""AV"":""Network"",""I"":""Low""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""react-ace"",""packageVersion"":""5.1.1"",""packageFilePaths"":[""/package.json""],""isTransitiveDependency"":false,""dependencyTree"":""react-ace:5.1.1"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""5.3.0"",""isBinary"":false}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""CVE-2020-15168"",""vulnerabilityDetails"":""node-fetch before versions 2.6.1 and 3.0.0-beta.9 did not honor the size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure. For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don\u0027t double-check the size of the data after fetch() has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15168"",""cvss3Severity"":""medium"",""cvss3Score"":""5.3"",""cvss3Metrics"":{""A"":""Low"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""None"",""AV"":""Network"",""I"":""None""},""extraData"":{}}]</REMEDIATE> -->",0,react ace       tgz    vulnerabilities  highest severity is             vulnerable library    react ace       tgz         path to dependency file   package json   path to vulnerable library   node modules opencollective node modules node fetch package json       found in head commit   a href        vulnerabilities    cve   severity     cvss   dependency   type   fixed in   remediation available                                                                                   medium         node fetch       tgz   transitive                            medium         node fetch       tgz   transitive                       details        cve             vulnerable library    node fetch       tgz     a light weight module that brings window fetch to node js and io js   library home page   a href     path to dependency file   package json   path to vulnerable library   node modules opencollective node modules node fetch package json     dependency hierarchy      react ace       tgz  root library        opencollective       tgz          x    node fetch       tgz    vulnerable library   found in head commit   a href     found in base branch   master               vulnerability details        node fetch is vulnerable to exposure of sensitive information to an unauthorized actor   publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  required     scope  changed   impact metrics      confidentiality impact  low     integrity impact  low     availability impact  none   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution  node fetch           direct dependency fix resolution  react ace                    rescue worker helmet  automatic remediation is available for this issue        cve             vulnerable library    node fetch       tgz     a light weight module that brings window fetch to node js and io js   library home page   a href     path to dependency file   package json   path to vulnerable library   node modules opencollective node modules node fetch package json     dependency hierarchy      react ace       tgz  root library        opencollective       tgz          x    node fetch       tgz    vulnerable library   found in head commit   a href     found in base branch   master               vulnerability details        node fetch before versions       and       beta   did not honor the size option after following a redirect  which means that when a content size was over the limit  a fetcherror would never get thrown and the process would end without failure  for most people  this fix will have a little or no impact  however  if you are relying on node fetch to gate files above a size  the impact could be significant  for example  if you don t double check the size of the data after fetch   has completed  your js thread could get tied up doing work on a large file  dos  and or cost you money in computing    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  low   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution  node fetch           direct dependency fix resolution  react ace                    rescue worker helmet  automatic remediation is available for this issue           rescue worker helmet  automatic remediation is available for this issue       istransitivedependency  false  dependencytree   react ace         isminimumfixversionavailable  true  minimumfixversion           isbinary  false    basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   node fetch is vulnerable to exposure of sensitive information to an unauthorized actor   vulnerabilityurl       istransitivedependency  false  dependencytree   react ace         isminimumfixversionavailable  true  minimumfixversion           isbinary  false    basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   node fetch before versions       and       beta   did not honor the size option after following a redirect  which means that when a content size was over the limit  a fetcherror would never get thrown and the process would end without failure  for most people  this fix will have a little or no impact  however  if you are relying on node fetch to gate files above a size  the impact could be significant  for example  if you don   double check the size of the data after fetch   has completed  your js thread could get tied up doing work on a large file  dos  and or cost you money in computing    vulnerabilityurl        ,0
367890,25767454240.0,IssuesEvent,2022-12-09 03:54:49,golang/go,https://api.github.com/repos/golang/go,closed,wiki: CodeReviewComments change - Justify variable name length,Documentation NeedsDecision,"From https://github.com/golang/go/wiki/CodeReviewComments#variable-names:

> Variable names in Go should be short rather than long.  This is especially true for local variables with limited scope.  Prefer `c` to `lineCount`.  Prefer `i` to `sliceIndex`.
> The basic rule: the further from its declaration that a name is used, the more descriptive the name must be. For a method receiver, one or two letters is sufficient. Common variables such as loop indices and readers can be a single letter (`i`, `r`). More unusual things and global variables need more descriptive names.

Similarly to https://github.com/golang/go/issues/38912, I don't understand why this is suggested. The comments there have some explanations I don't agree with, but they also suggest that I'm free to do things my own way if I disagree with the document. Literally this is of course true, but the spirit of it conflicts with the introduction of the page:

> This is a laundry list of common mistakes, not a comprehensive style guide.

It says that violating this would be a *mistake*. That's a pretty strong word, so the section on variable names can easily be (mis?)interpreted as [canonical](https://google.github.io/styleguide/go/#canonical).

I'll assume that the introduction is the better source of truth. Including justification would also suit the described use case of the document:

> so that a single detailed explanation can be referred to by shorthands

If someone's PR gets a comment with a link to this section, I imagine a detailed explanation would mean a less divisive resolution.

Could the variable naming convention section be enhanced to include justification?",1.0,"wiki: CodeReviewComments change - Justify variable name length - From https://github.com/golang/go/wiki/CodeReviewComments#variable-names:

> Variable names in Go should be short rather than long.  This is especially true for local variables with limited scope.  Prefer `c` to `lineCount`.  Prefer `i` to `sliceIndex`.
> The basic rule: the further from its declaration that a name is used, the more descriptive the name must be. For a method receiver, one or two letters is sufficient. Common variables such as loop indices and readers can be a single letter (`i`, `r`). More unusual things and global variables need more descriptive names.

Similarly to https://github.com/golang/go/issues/38912, I don't understand why this is suggested. The comments there have some explanations I don't agree with, but they also suggest that I'm free to do things my own way if I disagree with the document. Literally this is of course true, but the spirit of it conflicts with the introduction of the page:

> This is a laundry list of common mistakes, not a comprehensive style guide.

It says that violating this would be a *mistake*. That's a pretty strong word, so the section on variable names can easily be (mis?)interpreted as [canonical](https://google.github.io/styleguide/go/#canonical).

I'll assume that the introduction is the better source of truth. Including justification would also suit the described use case of the document:

> so that a single detailed explanation can be referred to by shorthands

If someone's PR gets a comment with a link to this section, I imagine a detailed explanation would mean a less divisive resolution.

Could the variable naming convention section be enhanced to include justification?",1,wiki  codereviewcomments change   justify variable name length   from        variable names in go should be short rather than long   this is especially true for local variables with limited scope   prefer  c  to  linecount    prefer  i  to  sliceindex      the basic rule  the further from its declaration that a name is used  the more descriptive the name must be  for a method receiver  one or two letters is sufficient  common variables such as loop indices and readers can be a single letter   i    r    more unusual things and global variables need more descriptive names     similarly to   i don t understand why this is suggested  the comments there have some explanations i don t agree with  but they also suggest that i m free to do things my own way if i disagree with the document  literally this is of course true  but the spirit of it conflicts with the introduction of the page       this is a laundry list of common mistakes  not a comprehensive style guide     it says that violating this would be a  mistake   that s a pretty strong word  so the section on variable names can easily be  mis  interpreted as        i ll assume that the introduction is the better source of truth  including justification would also suit the described use case of the document       so that a single detailed explanation can be referred to by shorthands    if someone s pr gets a comment with a link to this section  i imagine a detailed explanation would mean a less divisive resolution     could the variable naming convention section be enhanced to include justification ,1
65280,12549870672.0,IssuesEvent,2020-06-06 08:52:50,remy/nodemon,https://api.github.com/repos/remy/nodemon,closed,nodemon does not relay env variables loaded from file (env-cmd) [Maybe a config Issue],missing code to replicate stale,"<!-- 
  when raising an issue please include replies to the following questions, 
  and if you're reporting a bug, please include details on how to replicate
  and **assume** I have no knowledge of how your systems work - that includes
  gulp, grunt, webpack, etc. Thank you so much <3
-->

- `nodemon -v`: 2.0.3
- `node -v`: v12.16.3
- Operating system/terminal environment: MacOs
- Using Docker? What image: 
- Command you ran:

From package.json I run `yarn dev:watch:asc` which has the script entry below 

```""dev:watch:asc"": ""env-cmd -e dev-asc concurrently --kill-others \""yarn:dev:client\"" \""yarn:dev:server:watch:asc\""""```

Which uses the dev:server:watch script which is this:
```""dev:server:watch:asc"": ""env-cmd -e dev-asc nodemon ./src/server/index | bunyan --color""```

The package env-cmd is similar to cross-env allowing you to setup variables that are saved in a file. which is useful for me because I run an app with multiple tenants which have a couple of env vars setup differently. i.e. CONFIG_FILE_PATH

### Expected behaviour
Nodemon should honor and relay the env vars set from a previous script if they are performed in the same combined command.

### Actual behaviour
Nodemon runs but it ignores the env variables I set in the first script

### Steps to reproduce
NOTE: I can provide a repro repo if this is not just a configuration issue that a nodemon option maybe able to solve.
I tried adding env-cmd call in the execMap and it works but then I don't have a practical way to specify multiple tenants
---

If applicable, please append the `--dump` flag on your command and include the output here **ensuring to remove any sensitive/personal details or tokens**.
",1.0,"nodemon does not relay env variables loaded from file (env-cmd) [Maybe a config Issue] - <!-- 
  when raising an issue please include replies to the following questions, 
  and if you're reporting a bug, please include details on how to replicate
  and **assume** I have no knowledge of how your systems work - that includes
  gulp, grunt, webpack, etc. Thank you so much <3
-->

- `nodemon -v`: 2.0.3
- `node -v`: v12.16.3
- Operating system/terminal environment: MacOs
- Using Docker? What image: 
- Command you ran:

From package.json I run `yarn dev:watch:asc` which has the script entry below 

```""dev:watch:asc"": ""env-cmd -e dev-asc concurrently --kill-others \""yarn:dev:client\"" \""yarn:dev:server:watch:asc\""""```

Which uses the dev:server:watch script which is this:
```""dev:server:watch:asc"": ""env-cmd -e dev-asc nodemon ./src/server/index | bunyan --color""```

The package env-cmd is similar to cross-env allowing you to setup variables that are saved in a file. which is useful for me because I run an app with multiple tenants which have a couple of env vars setup differently. i.e. CONFIG_FILE_PATH

### Expected behaviour
Nodemon should honor and relay the env vars set from a previous script if they are performed in the same combined command.

### Actual behaviour
Nodemon runs but it ignores the env variables I set in the first script

### Steps to reproduce
NOTE: I can provide a repro repo if this is not just a configuration issue that a nodemon option maybe able to solve.
I tried adding env-cmd call in the execMap and it works but then I don't have a practical way to specify multiple tenants
---

If applicable, please append the `--dump` flag on your command and include the output here **ensuring to remove any sensitive/personal details or tokens**.
",0,nodemon does not relay env variables loaded from file  env cmd               when raising an issue please include replies to the following questions      and if you re reporting a bug  please include details on how to replicate    and   assume   i have no knowledge of how your systems work   that includes    gulp  grunt  webpack  etc  thank you so much               nodemon  v             node  v            operating system terminal environment  macos    using docker  what image      command you ran     from package json i run  yarn dev watch asc  which has the script entry below         dev watch asc    env cmd  e dev asc concurrently   kill others   yarn dev client     yarn dev server watch asc          which uses the dev server watch script which is this       dev server watch asc    env cmd  e dev asc nodemon   src server index   bunyan   color        the package env cmd is similar to cross env allowing you to setup variables that are saved in a file  which is useful for me because i run an app with multiple tenants which have a couple of env vars setup differently  i e  config file path        expected behaviour  nodemon should honor and relay the env vars set from a previous script if they are performed in the same combined command         actual behaviour  nodemon runs but it ignores the env variables i set in the first script        steps to reproduce  note  i can provide a repro repo if this is not just a configuration issue that a nodemon option maybe able to solve   i tried adding env cmd call in the execmap and it works but then i don t have a practical way to specify multiple tenants         if applicable  please append the    dump  flag on your command and include the output here   ensuring to remove any sensitive personal details or tokens     ,0
9082,7805779007.0,IssuesEvent,2018-06-11 12:05:15,coq/coq,https://api.github.com/repos/coq/coq,closed,Automate benchmarking,kind: infrastructure,"We should have a bot that is triggered by the use of the `needs: benchmark` flag. When it sees it, it launches a bench for the corresponding PR. When the bench finishes, it posts the results as a comment and removes the flag.",1.0,"Automate benchmarking - We should have a bot that is triggered by the use of the `needs: benchmark` flag. When it sees it, it launches a bench for the corresponding PR. When the bench finishes, it posts the results as a comment and removes the flag.",0,automate benchmarking   we should have a bot that is triggered by the use of the  needs  benchmark  flag  when it sees it  it launches a bench for the corresponding pr  when the bench finishes  it posts the results as a comment and removes the flag ,0
280253,30814906056.0,IssuesEvent,2023-08-01 12:55:18,momo-tong/jackson-databind-2.6.7.4,https://api.github.com/repos/momo-tong/jackson-databind-2.6.7.4,reopened,jackson-databind-2.6.7.4.jar: 18 vulnerabilities (highest severity is: 8.1),Mend: dependency security vulnerability,"<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.6.7.4.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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>


<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p></details>

## Vulnerabilities

| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (jackson-databind version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2021-20190](https://www.mend.io/vulnerability-database/CVE-2021-20190) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.6.7.5 | &#10060; |
| [CVE-2020-36189](https://www.mend.io/vulnerability-database/CVE-2020-36189) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.6.7.5 | &#10060; |
| [CVE-2020-36188](https://www.mend.io/vulnerability-database/CVE-2020-36188) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.6.7.5 | &#10060; |
| [CVE-2020-36179](https://www.mend.io/vulnerability-database/CVE-2020-36179) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.6.7.5 | &#10060; |
| [CVE-2020-10650](https://www.mend.io/vulnerability-database/CVE-2020-10650) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.9.10.4 | &#10060; |
| [CVE-2020-36181](https://www.mend.io/vulnerability-database/CVE-2020-36181) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.6.7.5 | &#10060; |
| [CVE-2020-36180](https://www.mend.io/vulnerability-database/CVE-2020-36180) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.6.7.5 | &#10060; |
| [CVE-2020-36183](https://www.mend.io/vulnerability-database/CVE-2020-36183) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.6.7.5 | &#10060; |
| [CVE-2020-36182](https://www.mend.io/vulnerability-database/CVE-2020-36182) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.6.7.5 | &#10060; |
| [CVE-2020-36185](https://www.mend.io/vulnerability-database/CVE-2020-36185) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.6.7.5 | &#10060; |
| [CVE-2020-36184](https://www.mend.io/vulnerability-database/CVE-2020-36184) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.6.7.5 | &#10060; |
| [CVE-2020-36187](https://www.mend.io/vulnerability-database/CVE-2020-36187) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.6.7.5 | &#10060; |
| [CVE-2020-36186](https://www.mend.io/vulnerability-database/CVE-2020-36186) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.6.7.5 | &#10060; |
| [CVE-2022-42004](https://www.mend.io/vulnerability-database/CVE-2022-42004) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | jackson-databind-2.6.7.4.jar | Direct | 2.12.7.1 | &#10060; |
| [CVE-2022-42003](https://www.mend.io/vulnerability-database/CVE-2022-42003) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | jackson-databind-2.6.7.4.jar | Direct | 2.12.7.1 | &#10060; |
| [CVE-2020-36518](https://www.mend.io/vulnerability-database/CVE-2020-36518) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | jackson-databind-2.6.7.4.jar | Direct | 2.12.6.1 | &#10060; |
| [WS-2018-0125](https://github.com/FasterXML/jackson-core/issues/315) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.3 | jackson-core-2.6.7.jar | Transitive | 2.7.7 | &#10060; |
| [WS-2018-0124](https://issues.jboss.org/browse/JBEAP-6316) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.3 | jackson-core-2.6.7.jar | Transitive | 2.7.8 | &#10060; |


## Details

<details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2021-20190</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
A flaw was found in jackson-databind before 2.9.10.7. FasterXML mishandles the interaction between serialization gadgets and typing. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

<p>Publish Date: 2021-01-19
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-20190>CVE-2021-20190</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-19</p>
<p>Fix Resolution: 2.6.7.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-36189</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to com.newrelic.agent.deps.ch.qos.logback.core.db.DriverManagerConnectionSource.

<p>Publish Date: 2021-01-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36189>CVE-2020-36189</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-06</p>
<p>Fix Resolution: 2.6.7.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-36188</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to com.newrelic.agent.deps.ch.qos.logback.core.db.JNDIConnectionSource.

<p>Publish Date: 2021-01-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36188>CVE-2020-36188</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-06</p>
<p>Fix Resolution: 2.6.7.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-36179</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to oadd.org.apache.commons.dbcp.cpdsadapter.DriverAdapterCPDS.

<p>Publish Date: 2021-01-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36179>CVE-2020-36179</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-07</p>
<p>Fix Resolution: 2.6.7.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-10650</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
A deserialization flaw was discovered in jackson-databind through 2.9.10.4. It could allow an unauthenticated user to perform code execution via ignite-jta or quartz-core: org.apache.ignite.cache.jta.jndi.CacheJndiTmLookup, org.apache.ignite.cache.jta.jndi.CacheJndiTmFactory, and org.quartz.utils.JNDIConnectionProvider.

<p>Publish Date: 2022-12-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-10650>CVE-2020-10650</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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-rpr3-cw39-3pxh"">https://github.com/advisories/GHSA-rpr3-cw39-3pxh</a></p>
<p>Release Date: 2022-12-26</p>
<p>Fix Resolution: 2.9.10.4</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-36181</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<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.cpdsadapter.DriverAdapterCPDS.

<p>Publish Date: 2021-01-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36181>CVE-2020-36181</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-06</p>
<p>Fix Resolution: 2.6.7.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-36180</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.dbcp2.cpdsadapter.DriverAdapterCPDS.

<p>Publish Date: 2021-01-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36180>CVE-2020-36180</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-07</p>
<p>Fix Resolution: 2.6.7.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-36183</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.docx4j.org.apache.xalan.lib.sql.JNDIConnectionPool.

<p>Publish Date: 2021-01-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36183>CVE-2020-36183</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-07</p>
<p>Fix Resolution: 2.6.7.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-36182</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<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.dbcp2.cpdsadapter.DriverAdapterCPDS.

<p>Publish Date: 2021-01-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36182>CVE-2020-36182</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-07</p>
<p>Fix Resolution: 2.6.7.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-36185</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<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.dbcp2.datasources.SharedPoolDataSource.

<p>Publish Date: 2021-01-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36185>CVE-2020-36185</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-06</p>
<p>Fix Resolution: 2.6.7.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-36184</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<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.dbcp2.datasources.PerUserPoolDataSource.

<p>Publish Date: 2021-01-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36184>CVE-2020-36184</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-06</p>
<p>Fix Resolution: 2.6.7.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-36187</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<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://www.mend.io/vulnerability-database/CVE-2020-36187>CVE-2020-36187</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-06</p>
<p>Fix Resolution: 2.6.7.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-36186</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<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.PerUserPoolDataSource.

<p>Publish Date: 2021-01-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36186>CVE-2020-36186</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-06</p>
<p>Fix Resolution: 2.6.7.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2022-42004</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
In FasterXML jackson-databind before 2.13.4, resource exhaustion can occur because of a lack of a check in BeanDeserializer._deserializeFromArray to prevent use of deeply nested arrays. An application is vulnerable only with certain customized choices for deserialization.

<p>Publish Date: 2022-10-02
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-42004>CVE-2022-42004</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Release Date: 2022-10-02</p>
<p>Fix Resolution: 2.12.7.1</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2022-42003</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
In FasterXML jackson-databind before 2.14.0-rc1, resource exhaustion can occur because of a lack of a check in primitive value deserializers to avoid deep wrapper array nesting, when the UNWRAP_SINGLE_VALUE_ARRAYS feature is enabled. Additional fix version in 2.13.4.1 and 2.12.17.1

<p>Publish Date: 2022-10-02
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-42003>CVE-2022-42003</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Release Date: 2022-10-02</p>
<p>Fix Resolution: 2.12.7.1</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-36518</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
jackson-databind before 2.13.0 allows a Java StackOverflow exception and denial of service via a large depth of nested objects.
 Mend Note: After conducting further research, Mend has determined that all versions of com.fasterxml.jackson.core:jackson-databind up to version 2.13.2 are vulnerable to CVE-2020-36518.

<p>Publish Date: 2022-03-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36518>CVE-2020-36518</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Release Date: 2022-03-11</p>
<p>Fix Resolution: 2.12.6.1</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> WS-2018-0125</summary>


###  Vulnerable Library - <b>jackson-core-2.6.7.jar</b></p>

<p>Core Jackson abstractions, basic JSON streaming API implementation</p>
<p>Library home page: <a href=""https://github.com/FasterXML/jackson-core"">https://github.com/FasterXML/jackson-core</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-core/2.6.7/jackson-core-2.6.7.jar</p>
<p>

Dependency Hierarchy:
  - jackson-databind-2.6.7.4.jar (Root Library)
    - :x: **jackson-core-2.6.7.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
OutOfMemoryError when writing BigDecimal In Jackson Core before version 2.7.7.
When enabled the WRITE_BIGDECIMAL_AS_PLAIN setting, Jackson will attempt to write out the whole number, no matter how large the exponent.

<p>Publish Date: 2016-08-25
<p>URL: <a href=https://github.com/FasterXML/jackson-core/issues/315>WS-2018-0125</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>5.3</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Release Date: 2016-08-25</p>
<p>Fix Resolution (com.fasterxml.jackson.core:jackson-core): 2.7.7</p>
<p>Direct dependency fix Resolution (com.fasterxml.jackson.core:jackson-databind): 2.7.7</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> WS-2018-0124</summary>


###  Vulnerable Library - <b>jackson-core-2.6.7.jar</b></p>

<p>Core Jackson abstractions, basic JSON streaming API implementation</p>
<p>Library home page: <a href=""https://github.com/FasterXML/jackson-core"">https://github.com/FasterXML/jackson-core</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-core/2.6.7/jackson-core-2.6.7.jar</p>
<p>

Dependency Hierarchy:
  - jackson-databind-2.6.7.4.jar (Root Library)
    - :x: **jackson-core-2.6.7.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
In Jackson Core before version 2.8.6 if the REST endpoint consumes POST requests with JSON or XML data and data are invalid, the first unrecognized token is printed to server.log. If the first token is word of length 10MB, the whole word is printed. This is potentially dangerous and can be used to attack the server by filling the disk with logs.

<p>Publish Date: 2018-06-24
<p>URL: <a href=https://issues.jboss.org/browse/JBEAP-6316>WS-2018-0124</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>5.3</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: Low
</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://cve.mitre.org/cgi-bin/cvename.cgi?name=WS-2018-0124"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=WS-2018-0124</a></p>
<p>Release Date: 2018-01-24</p>
<p>Fix Resolution (com.fasterxml.jackson.core:jackson-core): 2.8.6</p>
<p>Direct dependency fix Resolution (com.fasterxml.jackson.core:jackson-databind): 2.7.8</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details>",True,"jackson-databind-2.6.7.4.jar: 18 vulnerabilities (highest severity is: 8.1) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.6.7.4.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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>


<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p></details>

## Vulnerabilities

| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (jackson-databind version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2021-20190](https://www.mend.io/vulnerability-database/CVE-2021-20190) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.6.7.5 | &#10060; |
| [CVE-2020-36189](https://www.mend.io/vulnerability-database/CVE-2020-36189) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.6.7.5 | &#10060; |
| [CVE-2020-36188](https://www.mend.io/vulnerability-database/CVE-2020-36188) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.6.7.5 | &#10060; |
| [CVE-2020-36179](https://www.mend.io/vulnerability-database/CVE-2020-36179) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.6.7.5 | &#10060; |
| [CVE-2020-10650](https://www.mend.io/vulnerability-database/CVE-2020-10650) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.9.10.4 | &#10060; |
| [CVE-2020-36181](https://www.mend.io/vulnerability-database/CVE-2020-36181) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.6.7.5 | &#10060; |
| [CVE-2020-36180](https://www.mend.io/vulnerability-database/CVE-2020-36180) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.6.7.5 | &#10060; |
| [CVE-2020-36183](https://www.mend.io/vulnerability-database/CVE-2020-36183) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.6.7.5 | &#10060; |
| [CVE-2020-36182](https://www.mend.io/vulnerability-database/CVE-2020-36182) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.6.7.5 | &#10060; |
| [CVE-2020-36185](https://www.mend.io/vulnerability-database/CVE-2020-36185) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.6.7.5 | &#10060; |
| [CVE-2020-36184](https://www.mend.io/vulnerability-database/CVE-2020-36184) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.6.7.5 | &#10060; |
| [CVE-2020-36187](https://www.mend.io/vulnerability-database/CVE-2020-36187) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.6.7.5 | &#10060; |
| [CVE-2020-36186](https://www.mend.io/vulnerability-database/CVE-2020-36186) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | jackson-databind-2.6.7.4.jar | Direct | 2.6.7.5 | &#10060; |
| [CVE-2022-42004](https://www.mend.io/vulnerability-database/CVE-2022-42004) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | jackson-databind-2.6.7.4.jar | Direct | 2.12.7.1 | &#10060; |
| [CVE-2022-42003](https://www.mend.io/vulnerability-database/CVE-2022-42003) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | jackson-databind-2.6.7.4.jar | Direct | 2.12.7.1 | &#10060; |
| [CVE-2020-36518](https://www.mend.io/vulnerability-database/CVE-2020-36518) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | jackson-databind-2.6.7.4.jar | Direct | 2.12.6.1 | &#10060; |
| [WS-2018-0125](https://github.com/FasterXML/jackson-core/issues/315) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.3 | jackson-core-2.6.7.jar | Transitive | 2.7.7 | &#10060; |
| [WS-2018-0124](https://issues.jboss.org/browse/JBEAP-6316) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.3 | jackson-core-2.6.7.jar | Transitive | 2.7.8 | &#10060; |


## Details

<details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2021-20190</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
A flaw was found in jackson-databind before 2.9.10.7. FasterXML mishandles the interaction between serialization gadgets and typing. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

<p>Publish Date: 2021-01-19
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-20190>CVE-2021-20190</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-19</p>
<p>Fix Resolution: 2.6.7.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-36189</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to com.newrelic.agent.deps.ch.qos.logback.core.db.DriverManagerConnectionSource.

<p>Publish Date: 2021-01-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36189>CVE-2020-36189</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-06</p>
<p>Fix Resolution: 2.6.7.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-36188</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to com.newrelic.agent.deps.ch.qos.logback.core.db.JNDIConnectionSource.

<p>Publish Date: 2021-01-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36188>CVE-2020-36188</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-06</p>
<p>Fix Resolution: 2.6.7.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-36179</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to oadd.org.apache.commons.dbcp.cpdsadapter.DriverAdapterCPDS.

<p>Publish Date: 2021-01-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36179>CVE-2020-36179</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-07</p>
<p>Fix Resolution: 2.6.7.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-10650</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
A deserialization flaw was discovered in jackson-databind through 2.9.10.4. It could allow an unauthenticated user to perform code execution via ignite-jta or quartz-core: org.apache.ignite.cache.jta.jndi.CacheJndiTmLookup, org.apache.ignite.cache.jta.jndi.CacheJndiTmFactory, and org.quartz.utils.JNDIConnectionProvider.

<p>Publish Date: 2022-12-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-10650>CVE-2020-10650</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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-rpr3-cw39-3pxh"">https://github.com/advisories/GHSA-rpr3-cw39-3pxh</a></p>
<p>Release Date: 2022-12-26</p>
<p>Fix Resolution: 2.9.10.4</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-36181</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<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.cpdsadapter.DriverAdapterCPDS.

<p>Publish Date: 2021-01-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36181>CVE-2020-36181</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-06</p>
<p>Fix Resolution: 2.6.7.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-36180</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.dbcp2.cpdsadapter.DriverAdapterCPDS.

<p>Publish Date: 2021-01-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36180>CVE-2020-36180</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-07</p>
<p>Fix Resolution: 2.6.7.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-36183</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.docx4j.org.apache.xalan.lib.sql.JNDIConnectionPool.

<p>Publish Date: 2021-01-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36183>CVE-2020-36183</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-07</p>
<p>Fix Resolution: 2.6.7.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-36182</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<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.dbcp2.cpdsadapter.DriverAdapterCPDS.

<p>Publish Date: 2021-01-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36182>CVE-2020-36182</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-07</p>
<p>Fix Resolution: 2.6.7.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-36185</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<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.dbcp2.datasources.SharedPoolDataSource.

<p>Publish Date: 2021-01-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36185>CVE-2020-36185</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-06</p>
<p>Fix Resolution: 2.6.7.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-36184</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<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.dbcp2.datasources.PerUserPoolDataSource.

<p>Publish Date: 2021-01-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36184>CVE-2020-36184</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-06</p>
<p>Fix Resolution: 2.6.7.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-36187</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<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://www.mend.io/vulnerability-database/CVE-2020-36187>CVE-2020-36187</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-06</p>
<p>Fix Resolution: 2.6.7.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-36186</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<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.PerUserPoolDataSource.

<p>Publish Date: 2021-01-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36186>CVE-2020-36186</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-06</p>
<p>Fix Resolution: 2.6.7.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2022-42004</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
In FasterXML jackson-databind before 2.13.4, resource exhaustion can occur because of a lack of a check in BeanDeserializer._deserializeFromArray to prevent use of deeply nested arrays. An application is vulnerable only with certain customized choices for deserialization.

<p>Publish Date: 2022-10-02
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-42004>CVE-2022-42004</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Release Date: 2022-10-02</p>
<p>Fix Resolution: 2.12.7.1</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2022-42003</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
In FasterXML jackson-databind before 2.14.0-rc1, resource exhaustion can occur because of a lack of a check in primitive value deserializers to avoid deep wrapper array nesting, when the UNWRAP_SINGLE_VALUE_ARRAYS feature is enabled. Additional fix version in 2.13.4.1 and 2.12.17.1

<p>Publish Date: 2022-10-02
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-42003>CVE-2022-42003</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Release Date: 2022-10-02</p>
<p>Fix Resolution: 2.12.7.1</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2020-36518</summary>


###  Vulnerable Library - <b>jackson-databind-2.6.7.4.jar</b></p>

<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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.7.4/jackson-databind-2.6.7.4.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.6.7.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
jackson-databind before 2.13.0 allows a Java StackOverflow exception and denial of service via a large depth of nested objects.
 Mend Note: After conducting further research, Mend has determined that all versions of com.fasterxml.jackson.core:jackson-databind up to version 2.13.2 are vulnerable to CVE-2020-36518.

<p>Publish Date: 2022-03-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36518>CVE-2020-36518</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Release Date: 2022-03-11</p>
<p>Fix Resolution: 2.12.6.1</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> WS-2018-0125</summary>


###  Vulnerable Library - <b>jackson-core-2.6.7.jar</b></p>

<p>Core Jackson abstractions, basic JSON streaming API implementation</p>
<p>Library home page: <a href=""https://github.com/FasterXML/jackson-core"">https://github.com/FasterXML/jackson-core</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-core/2.6.7/jackson-core-2.6.7.jar</p>
<p>

Dependency Hierarchy:
  - jackson-databind-2.6.7.4.jar (Root Library)
    - :x: **jackson-core-2.6.7.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
OutOfMemoryError when writing BigDecimal In Jackson Core before version 2.7.7.
When enabled the WRITE_BIGDECIMAL_AS_PLAIN setting, Jackson will attempt to write out the whole number, no matter how large the exponent.

<p>Publish Date: 2016-08-25
<p>URL: <a href=https://github.com/FasterXML/jackson-core/issues/315>WS-2018-0125</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>5.3</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Release Date: 2016-08-25</p>
<p>Fix Resolution (com.fasterxml.jackson.core:jackson-core): 2.7.7</p>
<p>Direct dependency fix Resolution (com.fasterxml.jackson.core:jackson-databind): 2.7.7</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> WS-2018-0124</summary>


###  Vulnerable Library - <b>jackson-core-2.6.7.jar</b></p>

<p>Core Jackson abstractions, basic JSON streaming API implementation</p>
<p>Library home page: <a href=""https://github.com/FasterXML/jackson-core"">https://github.com/FasterXML/jackson-core</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-core/2.6.7/jackson-core-2.6.7.jar</p>
<p>

Dependency Hierarchy:
  - jackson-databind-2.6.7.4.jar (Root Library)
    - :x: **jackson-core-2.6.7.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/momo-tong/jackson-databind-2.6.7.4/commit/04d4aaad104a5be2b96c4d63de2193a16e06bae0"">04d4aaad104a5be2b96c4d63de2193a16e06bae0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
In Jackson Core before version 2.8.6 if the REST endpoint consumes POST requests with JSON or XML data and data are invalid, the first unrecognized token is printed to server.log. If the first token is word of length 10MB, the whole word is printed. This is potentially dangerous and can be used to attack the server by filling the disk with logs.

<p>Publish Date: 2018-06-24
<p>URL: <a href=https://issues.jboss.org/browse/JBEAP-6316>WS-2018-0124</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>5.3</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: Low
</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://cve.mitre.org/cgi-bin/cvename.cgi?name=WS-2018-0124"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=WS-2018-0124</a></p>
<p>Release Date: 2018-01-24</p>
<p>Fix Resolution (com.fasterxml.jackson.core:jackson-core): 2.8.6</p>
<p>Direct dependency fix Resolution (com.fasterxml.jackson.core:jackson-databind): 2.7.8</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details>",0,jackson databind         jar    vulnerabilities  highest severity is             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   pom xml   path to vulnerable library   home wss scanner    repository com fasterxml jackson core jackson databind         jackson databind         jar       found in head commit   a href        vulnerabilities    cve   severity     cvss   dependency   type   fixed in  jackson databind version    remediation available                                                                                             high         jackson databind         jar   direct                              high         jackson databind         jar   direct                              high         jackson databind         jar   direct                              high         jackson databind         jar   direct                              high         jackson databind         jar   direct                              high         jackson databind         jar   direct                              high         jackson databind         jar   direct                              high         jackson databind         jar   direct                              high         jackson databind         jar   direct                              high         jackson databind         jar   direct                              high         jackson databind         jar   direct                              high         jackson databind         jar   direct                              high         jackson databind         jar   direct                              high         jackson databind         jar   direct                              high         jackson databind         jar   direct                              high         jackson databind         jar   direct                              medium         jackson core       jar   transitive                            medium         jackson core       jar   transitive                       details        cve             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   pom xml   path to vulnerable library   home wss scanner    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        a flaw was found in jackson databind before          fasterxml mishandles the interaction between serialization gadgets and typing  the highest threat from this vulnerability is to data confidentiality and integrity as well as system availability    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  high   for more information on   scores  click  a href                suggested fix     type  upgrade version   release date          fix resolution                    step up your open source security game with mend            cve             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   pom xml   path to vulnerable library   home wss scanner    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 com newrelic agent deps ch qos logback core db drivermanagerconnectionsource    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  high   for more information on   scores  click  a href                suggested fix     type  upgrade version   release date          fix resolution                    step up your open source security game with mend            cve             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   pom xml   path to vulnerable library   home wss scanner    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 com newrelic agent deps ch qos logback core db jndiconnectionsource    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  high   for more information on   scores  click  a href                suggested fix     type  upgrade version   release date          fix resolution                    step up your open source security game with mend            cve             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   pom xml   path to vulnerable library   home wss scanner    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 oadd org apache commons dbcp cpdsadapter driveradaptercpds    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  high   for more information on   scores  click  a href                suggested fix     type  upgrade version   release date          fix resolution                    step up your open source security game with mend            cve             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   pom xml   path to vulnerable library   home wss scanner    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        a deserialization flaw was discovered in jackson databind through          it could allow an unauthenticated user to perform code execution via ignite jta or quartz core  org apache ignite cache jta jndi cachejnditmlookup  org apache ignite cache jta jndi cachejnditmfactory  and org quartz utils jndiconnectionprovider    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  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 mend            cve             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   pom xml   path to vulnerable library   home wss scanner    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 cpdsadapter driveradaptercpds    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  high   for more information on   scores  click  a href                suggested fix     type  upgrade version   release date          fix resolution                    step up your open source security game with mend            cve             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   pom xml   path to vulnerable library   home wss scanner    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 commons   cpdsadapter driveradaptercpds    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  high   for more information on   scores  click  a href                suggested fix     type  upgrade version   release date          fix resolution                    step up your open source security game with mend            cve             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   pom xml   path to vulnerable library   home wss scanner    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   org apache xalan lib sql jndiconnectionpool    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  high   for more information on   scores  click  a href                suggested fix     type  upgrade version   release date          fix resolution                    step up your open source security game with mend            cve             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   pom xml   path to vulnerable library   home wss scanner    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   cpdsadapter driveradaptercpds    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  high   for more information on   scores  click  a href                suggested fix     type  upgrade version   release date          fix resolution                    step up your open source security game with mend            cve             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   pom xml   path to vulnerable library   home wss scanner    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   datasources sharedpooldatasource    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  high   for more information on   scores  click  a href                suggested fix     type  upgrade version   release date          fix resolution                    step up your open source security game with mend            cve             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   pom xml   path to vulnerable library   home wss scanner    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   datasources peruserpooldatasource    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  high   for more information on   scores  click  a href                suggested fix     type  upgrade version   release date          fix resolution                    step up your open source security game with mend            cve             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   pom xml   path to vulnerable library   home wss scanner    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    exploitability metrics      attack vector  network     attack complexity  high     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   release date          fix resolution                    step up your open source security game with mend            cve             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   pom xml   path to vulnerable library   home wss scanner    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 peruserpooldatasource    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  high   for more information on   scores  click  a href                suggested fix     type  upgrade version   release date          fix resolution                    step up your open source security game with mend            cve             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   pom xml   path to vulnerable library   home wss scanner    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        in fasterxml jackson databind before        resource exhaustion can occur because of a lack of a check in beandeserializer  deserializefromarray to prevent use of deeply nested arrays  an application is vulnerable only with certain customized choices for deserialization    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  high   for more information on   scores  click  a href                suggested fix     type  upgrade version   release date          fix resolution                    step up your open source security game with mend            cve             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   pom xml   path to vulnerable library   home wss scanner    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        in fasterxml jackson databind before          resource exhaustion can occur because of a lack of a check in primitive value deserializers to avoid deep wrapper array nesting  when the unwrap single value arrays feature is enabled  additional fix version in         and           publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  high   for more information on   scores  click  a href                suggested fix     type  upgrade version   release date          fix resolution                    step up your open source security game with mend            cve             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   pom xml   path to vulnerable library   home wss scanner    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        jackson databind before       allows a java stackoverflow exception and denial of service via a large depth of nested objects   mend note  after conducting further research  mend has determined that all versions of com fasterxml jackson core jackson databind up to version       are vulnerable to cve        publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  high   for more information on   scores  click  a href                suggested fix     type  upgrade version   release date          fix resolution                    step up your open source security game with mend            ws             vulnerable library    jackson core       jar     core jackson abstractions  basic json streaming api implementation   library home page   a href     path to dependency file   pom xml   path to vulnerable library   home wss scanner    repository com fasterxml jackson core jackson core       jackson core       jar     dependency hierarchy      jackson databind         jar  root library         x    jackson core       jar    vulnerable library   found in head commit   a href     found in base branch   master               vulnerability details        outofmemoryerror when writing bigdecimal in jackson core before version        when enabled the write bigdecimal as plain setting  jackson will attempt to write out the whole number  no matter how large the exponent    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  low   for more information on   scores  click  a href                suggested fix     type  upgrade version   release date          fix resolution  com fasterxml jackson core jackson core           direct dependency fix resolution  com fasterxml jackson core jackson databind                   step up your open source security game with mend            ws             vulnerable library    jackson core       jar     core jackson abstractions  basic json streaming api implementation   library home page   a href     path to dependency file   pom xml   path to vulnerable library   home wss scanner    repository com fasterxml jackson core jackson core       jackson core       jar     dependency hierarchy      jackson databind         jar  root library         x    jackson core       jar    vulnerable library   found in head commit   a href     found in base branch   master               vulnerability details        in jackson core before version       if the rest endpoint consumes post requests with json or xml data and data are invalid  the first unrecognized token is printed to server log  if the first token is word of length    the whole word is printed  this is potentially dangerous and can be used to attack the server by filling the disk with logs    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  low   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution  com fasterxml jackson core jackson core           direct dependency fix resolution  com fasterxml jackson core jackson databind                   step up your open source security game with mend      ,0
26468,2684556238.0,IssuesEvent,2015-03-29 03:31:33,gtcasl/gpuocelot,https://api.github.com/repos/gtcasl/gpuocelot,closed,BFE ptx instruction is not supported,bug imported Priority-Low,"_From [ashwin.l...@gmail.com](https://code.google.com/u/103829786111946222660/) on January 31, 2012 17:41:19_

What steps will reproduce the problem? 1.Compile bfe.cpp and link with ocelot
2.Run What is the expected output? What do you see instead? terminate called after throwing an instance of 'parser::PTXParser::Exception'
  what():  
Failed to parse file 'bfetest':

Offending line : bfe.u32 u32_4,u32_1,u32_1,8; Please use labels and text to provide additional information.

**Attachment:** [bfe.cpp](http://code.google.com/p/gpuocelot/issues/detail?id=66)

_Original issue: http://code.google.com/p/gpuocelot/issues/detail?id=66_",1.0,"BFE ptx instruction is not supported - _From [ashwin.l...@gmail.com](https://code.google.com/u/103829786111946222660/) on January 31, 2012 17:41:19_

What steps will reproduce the problem? 1.Compile bfe.cpp and link with ocelot
2.Run What is the expected output? What do you see instead? terminate called after throwing an instance of 'parser::PTXParser::Exception'
  what():  
Failed to parse file 'bfetest':

Offending line : bfe.u32 u32_4,u32_1,u32_1,8; Please use labels and text to provide additional information.

**Attachment:** [bfe.cpp](http://code.google.com/p/gpuocelot/issues/detail?id=66)

_Original issue: http://code.google.com/p/gpuocelot/issues/detail?id=66_",0,bfe ptx instruction is not supported    from     on january              what steps will reproduce the problem    compile bfe cpp and link with ocelot    run what is the expected output  what do you see instead  terminate called after throwing an instance of  parser  ptxparser  exception     what       failed to parse file  bfetest      offending line   bfe                  please use labels and text to provide additional information     attachment          original issue   ,0
69698,9321575950.0,IssuesEvent,2019-03-27 04:38:31,golang/go,https://api.github.com/repos/golang/go,closed,os: Document Exit() behavior with code outside 0 - 255,Documentation NeedsInvestigation,"### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.12.1 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/cuonglm/.cache/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/cuonglm/go""
GOPROXY=""""
GORACE=""""
GOROOT=""/usr/local/stow/go""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/stow/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/cuonglm/sources/go/src/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build303772017=/tmp/go-build -gno-record-gcc-switches""

</pre></details>

### What did you do?

```
package main

import ""os""

func main() {
	os.Exit(256)
}
```

Compile program then run:

```
./main || echo ./main should return failure code
```

### What did you expect to see?

`./main should return failure code` is printed in terminal.

### What did you see instead?

No output.

The number `256` is passed as-is to `_exit()`, or in my case `exit_group()` on Linux.

But on Linux, and other systems which use traditional `wait*()` system call, only the lower 8 bits of that number are available to the parent. it means the program above appears as success.

If the parent uses `waitid()`, the number won't be truncated and return as-is to the parent (Though not on Linux, which still truncate the number even `waitid()` was used. The behavior maybe change in the future).

So the behavior of `os.Exit(code)` where code > 255 or code < 0 can not be consistent. I propose one of these changes:

 - Always transform the code like `wait*()` does, mean a value between 0-255 always returns to parent.

 - Limit the code to value between 0 - 255, do something in case the code out of range:
   + warning message that value outside of 0 - 255 can be truncated
   + warning message that value outside of 0 - 255 is bad number (like dash, yash does)
   + panic, so user knows the problem, and get a standard error code from panic. It also does not break any program. (like m4 does)

 - Document that only value between  0 - 255 is consistent and should be used. Value greater than 255 may or may not be truncated, so the exit code is unspecified.",1.0,"os: Document Exit() behavior with code outside 0 - 255 - ### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.12.1 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/cuonglm/.cache/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/cuonglm/go""
GOPROXY=""""
GORACE=""""
GOROOT=""/usr/local/stow/go""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/stow/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/cuonglm/sources/go/src/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build303772017=/tmp/go-build -gno-record-gcc-switches""

</pre></details>

### What did you do?

```
package main

import ""os""

func main() {
	os.Exit(256)
}
```

Compile program then run:

```
./main || echo ./main should return failure code
```

### What did you expect to see?

`./main should return failure code` is printed in terminal.

### What did you see instead?

No output.

The number `256` is passed as-is to `_exit()`, or in my case `exit_group()` on Linux.

But on Linux, and other systems which use traditional `wait*()` system call, only the lower 8 bits of that number are available to the parent. it means the program above appears as success.

If the parent uses `waitid()`, the number won't be truncated and return as-is to the parent (Though not on Linux, which still truncate the number even `waitid()` was used. The behavior maybe change in the future).

So the behavior of `os.Exit(code)` where code > 255 or code < 0 can not be consistent. I propose one of these changes:

 - Always transform the code like `wait*()` does, mean a value between 0-255 always returns to parent.

 - Limit the code to value between 0 - 255, do something in case the code out of range:
   + warning message that value outside of 0 - 255 can be truncated
   + warning message that value outside of 0 - 255 is bad number (like dash, yash does)
   + panic, so user knows the problem, and get a standard error code from panic. It also does not break any program. (like m4 does)

 - Document that only value between  0 - 255 is consistent and should be used. Value greater than 255 may or may not be truncated, so the exit code is unspecified.",1,os  document exit   behavior with code outside             what version of go are you using   go version            go version  go version       linux             does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env          go env  output       go env  goarch      gobin     gocache   home cuonglm  cache go build   goexe     goflags     gohostarch      gohostos  linux   goos  linux   gopath   home cuonglm go   goproxy     gorace     goroot   usr local stow go   gotmpdir     gotooldir   usr local stow go pkg tool linux     gccgo  gccgo   cc  gcc   cxx  g     cgo enabled      gomod   home cuonglm sources go src go mod   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches               what did you do          package main    import  os     func main      	os exit               compile program then run            main    echo   main should return failure code             what did you expect to see        main should return failure code  is printed in terminal         what did you see instead     no output     the number     is passed as is to   exit     or in my case  exit group    on linux     but on linux  and other systems which use traditional  wait     system call  only the lower   bits of that number are available to the parent  it means the program above appears as success     if the parent uses  waitid     the number won t be truncated and return as is to the parent  though not on linux  which still truncate the number even  waitid    was used  the behavior maybe change in the future      so the behavior of  os exit code   where code     or code     can not be consistent  i propose one of these changes        always transform the code like  wait     does  mean a value between     always returns to parent        limit the code to value between        do something in case the code out of range        warning message that value outside of       can be truncated       warning message that value outside of       is bad number  like dash  yash does        panic  so user knows the problem  and get a standard error code from panic  it also does not break any program   like   does        document that only value between        is consistent and should be used  value greater than   may or may not be truncated  so the exit code is unspecified ,1
123510,12199938714.0,IssuesEvent,2020-04-30 03:08:29,golang/go,https://api.github.com/repos/golang/go,closed,debug/gosym: Table.Files doc is stale?,Documentation NeedsInvestigation,"https://golang.org/pkg/debug/gosym/#Table says:

```go
    Files map[string]*Obj // nil for Go 1.2 and later binaries
```

But empirically that is not true. It's populated.

And https://golang.org/pkg/debug/gosym/#Obj.Paths says:

>     // Use the keys of Table.Files to obtain a list of source files.

... which further suggests it's meant to be non-nil.

/cc @randall77 @ianlancetaylor (not sure who owns this)
",1.0,"debug/gosym: Table.Files doc is stale? - https://golang.org/pkg/debug/gosym/#Table says:

```go
    Files map[string]*Obj // nil for Go 1.2 and later binaries
```

But empirically that is not true. It's populated.

And https://golang.org/pkg/debug/gosym/#Obj.Paths says:

>     // Use the keys of Table.Files to obtain a list of source files.

... which further suggests it's meant to be non-nil.

/cc @randall77 @ianlancetaylor (not sure who owns this)
",1,debug gosym  table files doc is stale      says        go      files map  obj    nil for go     and later binaries         but empirically that is not true  it s populated     and   says              use the keys of table files to obtain a list of source files         which further suggests it s meant to be non nil      cc     ianlancetaylor  not sure who owns this   ,1
6158,3004573822.0,IssuesEvent,2015-07-26 02:57:27,golang/go,https://api.github.com/repos/golang/go,closed,crypto/rand: Reader docs say /dev/urandom but really uses getrandom(2) on Linux when available,Documentation,"> On Unix-like systems, Reader reads from /dev/urandom.

It has been improved since, and is better than that. The docs should reflect this.
",1.0,"crypto/rand: Reader docs say /dev/urandom but really uses getrandom(2) on Linux when available - > On Unix-like systems, Reader reads from /dev/urandom.

It has been improved since, and is better than that. The docs should reflect this.
",1,crypto rand  reader docs say  dev urandom but really uses getrandom    on linux when available     on unix like systems  reader reads from  dev urandom     it has been improved since  and is better than that  the docs should reflect this   ,1
106988,11503919930.0,IssuesEvent,2020-02-12 22:05:22,golang/go,https://api.github.com/repos/golang/go,closed,wiki: clarify Assembly Policy for crypto,Documentation,"Current [Assembly Policy](https://github.com/golang/go/wiki/AssemblyPolicy) establish general guidelines for inclusion of assembly implementations. However there is some [confusion](https://groups.google.com/forum/#!topic/golang-dev/_ZwBZJaDw_U) about it application to crypto.
I think we should clarify the following questions:

- Are assembly implementations of new (to go) modes/hashes/block-ciphers allowed at all?
- If they are allowed, we should have a list of deprecated stuff, that is **intended**  to be slow e. g. rc4.
- Are there any additional requirements for testing crypto asm?
- Can I (or anyone without great background in crypto) +2  straightforward cases e. g. https://go-review.googlesource.com/c/go/+/125316  ?
- If we are not going to accept new assembly implemntaions, than we must do something with CLs sent before creation of assembly policy, that are still in review, e. g. https://go-review.googlesource.com/c/go/+/109135 
",1.0,"wiki: clarify Assembly Policy for crypto - Current [Assembly Policy](https://github.com/golang/go/wiki/AssemblyPolicy) establish general guidelines for inclusion of assembly implementations. However there is some [confusion](https://groups.google.com/forum/#!topic/golang-dev/_ZwBZJaDw_U) about it application to crypto.
I think we should clarify the following questions:

- Are assembly implementations of new (to go) modes/hashes/block-ciphers allowed at all?
- If they are allowed, we should have a list of deprecated stuff, that is **intended**  to be slow e. g. rc4.
- Are there any additional requirements for testing crypto asm?
- Can I (or anyone without great background in crypto) +2  straightforward cases e. g. https://go-review.googlesource.com/c/go/+/125316  ?
- If we are not going to accept new assembly implemntaions, than we must do something with CLs sent before creation of assembly policy, that are still in review, e. g. https://go-review.googlesource.com/c/go/+/109135 
",1,wiki  clarify assembly policy for crypto   current     establish general guidelines for inclusion of assembly implementations  however there is some     about it application to crypto   i think we should clarify the following questions       are assembly implementations of new  to go  modes hashes block ciphers allowed at all     if they are allowed  we should have a list of deprecated stuff  that is   intended    to be slow e  g        are there any additional requirements for testing crypto asm     can i  or anyone without great background in crypto      straightforward cases e  g          if we are not going to accept new assembly implemntaions  than we must do something with cls sent before creation of assembly policy  that are still in review  e  g      ,1
33215,6180328708.0,IssuesEvent,2017-07-03 05:06:13,golang/go,https://api.github.com/repos/golang/go,opened,Effective_GO documentation mistake,Documentation,"
[https://golang.org/doc/effective_go.html#functions](url)
on this code

```
func nextInt(b []byte, i int) (int, int) {
    for ; i < len(b) && !isDigit(b[i]); i++ {
    }
    x := 0
    for ; i < len(b) && isDigit(b[i]); i++ {
        x = x*10 + int(b[i]) - '0'
    }
    return x, i
}
```


I think

```
 for ; i < len(b) && !isDigit(b[i]); i++ {
    }
```

is a duplication mistake",1.0,"Effective_GO documentation mistake - 
[https://golang.org/doc/effective_go.html#functions](url)
on this code

```
func nextInt(b []byte, i int) (int, int) {
    for ; i < len(b) && !isDigit(b[i]); i++ {
    }
    x := 0
    for ; i < len(b) && isDigit(b[i]); i++ {
        x = x*10 + int(b[i]) - '0'
    }
    return x, i
}
```


I think

```
 for ; i < len(b) && !isDigit(b[i]); i++ {
    }
```

is a duplication mistake",1,effective go documentation mistake       url   on this code         func nextint b  byte  i int   int  int         for   i   len b      isdigit b    i                 x           for   i   len b     isdigit b    i              x   x     int b                     return x  i              i think          for   i   len b      isdigit b    i                    is a duplication mistake,1
119793,17632317438.0,IssuesEvent,2021-08-19 09:30:24,AlexRogalskiy/github-action-coverage-reporter,https://api.github.com/repos/AlexRogalskiy/github-action-coverage-reporter,opened,WS-2021-0245 (High) detected in git-2.0.6.tgz,security vulnerability,"## WS-2021-0245 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>git-2.0.6.tgz</b></p></summary>

<p>a util for spawning git from npm CLI contexts</p>
<p>Library home page: <a href=""https://registry.npmjs.org/@npmcli/git/-/git-2.0.6.tgz"">https://registry.npmjs.org/@npmcli/git/-/git-2.0.6.tgz</a></p>
<p>Path to dependency file: github-action-coverage-reporter/package.json</p>
<p>Path to vulnerable library: github-action-coverage-reporter/node_modules/npm/node_modules/@npmcli/git/package.json</p>
<p>

Dependency Hierarchy:
  - npm-7.1.1.tgz (Root Library)
    - npm-7.9.0.tgz
      - libnpmversion-1.1.0.tgz
        - :x: **git-2.0.6.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/AlexRogalskiy/github-action-coverage-reporter/commit/b3a90e821dbcf9e676915ffe96862b8f81ec9ca5"">b3a90e821dbcf9e676915ffe96862b8f81ec9ca5</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
A Command Injection vulnerability was found in @npmcli/git before 2.0.8. It may result in arbitrary shell command execution due to improper argument sanitization when ""npmcli/git"" is used to execute Git commands based on user-controlled input. The impact of this issue is possible Arbitrary Command Injection when npmcli/git is run with untrusted (user-controlled) Git command arguments.

<p>Publish Date: 2021-08-05
<p>URL: <a href=https://github.com/npm/git/commit/9fab115eaaa4e0adc0260b17a4feb83d339327eb>WS-2021-0245</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/advisories/GHSA-hxwm-x553-x359"">https://github.com/advisories/GHSA-hxwm-x553-x359</a></p>
<p>Release Date: 2021-08-05</p>
<p>Fix Resolution: @npmcli/git - 2.0.8</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"WS-2021-0245 (High) detected in git-2.0.6.tgz - ## WS-2021-0245 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>git-2.0.6.tgz</b></p></summary>

<p>a util for spawning git from npm CLI contexts</p>
<p>Library home page: <a href=""https://registry.npmjs.org/@npmcli/git/-/git-2.0.6.tgz"">https://registry.npmjs.org/@npmcli/git/-/git-2.0.6.tgz</a></p>
<p>Path to dependency file: github-action-coverage-reporter/package.json</p>
<p>Path to vulnerable library: github-action-coverage-reporter/node_modules/npm/node_modules/@npmcli/git/package.json</p>
<p>

Dependency Hierarchy:
  - npm-7.1.1.tgz (Root Library)
    - npm-7.9.0.tgz
      - libnpmversion-1.1.0.tgz
        - :x: **git-2.0.6.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/AlexRogalskiy/github-action-coverage-reporter/commit/b3a90e821dbcf9e676915ffe96862b8f81ec9ca5"">b3a90e821dbcf9e676915ffe96862b8f81ec9ca5</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
A Command Injection vulnerability was found in @npmcli/git before 2.0.8. It may result in arbitrary shell command execution due to improper argument sanitization when ""npmcli/git"" is used to execute Git commands based on user-controlled input. The impact of this issue is possible Arbitrary Command Injection when npmcli/git is run with untrusted (user-controlled) Git command arguments.

<p>Publish Date: 2021-08-05
<p>URL: <a href=https://github.com/npm/git/commit/9fab115eaaa4e0adc0260b17a4feb83d339327eb>WS-2021-0245</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/advisories/GHSA-hxwm-x553-x359"">https://github.com/advisories/GHSA-hxwm-x553-x359</a></p>
<p>Release Date: 2021-08-05</p>
<p>Fix Resolution: @npmcli/git - 2.0.8</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,ws      high  detected in git       tgz      ws       high severity vulnerability     vulnerable library    git       tgz      a util for spawning git from npm cli contexts   library home page   a href     path to dependency file  github action coverage reporter package json   path to vulnerable library  github action coverage reporter node modules npm node modules  npmcli git package json     dependency hierarchy      npm       tgz  root library        npm       tgz         libnpmversion       tgz            x    git       tgz    vulnerable library   found in head commit   a href               vulnerability details         a command injection vulnerability was found in  npmcli git before        it may result in arbitrary shell command execution due to improper argument sanitization when  npmcli git  is used to execute git commands based on user controlled input  the impact of this issue is possible arbitrary command injection when npmcli git is run with untrusted  user controlled  git command arguments    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   npmcli git                       step up your open source security game with whitesource    ,0
28496,11641533455.0,IssuesEvent,2020-02-29 03:15:26,fecgov/fec-cms,https://api.github.com/repos/fecgov/fec-cms,closed,[Snyk: Medium] Allocation of Resources without limits (Due: 3/15/2020),Security: moderate,"### Summary

**Remediation:** Pin Pillow@5.4.1 to Pillow@6.2.0 to fix
  ✗ Allocation of Resources Without Limits or Throttling [Medium Severity][https://snyk.io/vuln/SNYK-PYTHON-PILLOW-536096] in Pillow@5.4.1
    introduced by wagtail@2.2.1 > Pillow@5.4.1",True,"[Snyk: Medium] Allocation of Resources without limits (Due: 3/15/2020) - ### Summary

**Remediation:** Pin Pillow@5.4.1 to Pillow@6.2.0 to fix
  ✗ Allocation of Resources Without Limits or Throttling [Medium Severity][https://snyk.io/vuln/SNYK-PYTHON-PILLOW-536096] in Pillow@5.4.1
    introduced by wagtail@2.2.1 > Pillow@5.4.1",0,  allocation of resources without limits  due               summary      remediation    pin pillow       to pillow       to fix    ✗ allocation of resources without limits or throttling    in pillow            introduced by wagtail         pillow      ,0
39699,6761881045.0,IssuesEvent,2017-10-25 04:48:22,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: short commands description in 'go help' too vague for some command,Documentation NeedsDecision,"Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
go1.8.1

### What operating system and processor architecture are you using (`go env`)?
GOARCH=""amd64""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""

### What did you do?
```
$ go help
Go is a tool for managing Go source code.
...
The commands are:

	build       compile packages and dependencies
	clean       remove object files
	doc         show documentation for package or symbol
	env         print Go environment information
	bug         start a bug report
	fix         run go tool fix on packages
	fmt         run gofmt on package sources
	generate    generate Go files by processing source
	get         download and install packages and dependencies
	install     compile and install packages and dependencies
	list        list packages
	run         compile and run Go program
	test        test packages
	tool        run specified go tool
	version     print Go version
	vet         run go tool vet on packages
...
```

### What did you expect to see?

The help output for the `fix` and `vet` is not helpful. Is is just `(""run go tool %s on packages"", toolname)`. Also the `fmt` output could be improved.

### What did you see instead?

The help-output should say what the command will effectively do (like for `vet`: check the source code for potential issues).
",1.0,"cmd/go: short commands description in 'go help' too vague for some command - Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
go1.8.1

### What operating system and processor architecture are you using (`go env`)?
GOARCH=""amd64""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""

### What did you do?
```
$ go help
Go is a tool for managing Go source code.
...
The commands are:

	build       compile packages and dependencies
	clean       remove object files
	doc         show documentation for package or symbol
	env         print Go environment information
	bug         start a bug report
	fix         run go tool fix on packages
	fmt         run gofmt on package sources
	generate    generate Go files by processing source
	get         download and install packages and dependencies
	install     compile and install packages and dependencies
	list        list packages
	run         compile and run Go program
	test        test packages
	tool        run specified go tool
	version     print Go version
	vet         run go tool vet on packages
...
```

### What did you expect to see?

The help output for the `fix` and `vet` is not helpful. Is is just `(""run go tool %s on packages"", toolname)`. Also the `fmt` output could be improved.

### What did you see instead?

The help-output should say what the command will effectively do (like for `vet`: check the source code for potential issues).
",1,cmd go  short commands description in  go help  too vague for some command   please answer these questions before submitting your issue  thanks         what version of go are you using   go version                  what operating system and processor architecture are you using   go env     goarch      gohostarch      gohostos  linux   goos  linux         what did you do          go help  go is a tool for managing go source code        the commands are     	build       compile packages and dependencies  	clean       remove object files  	doc         show documentation for package or symbol  	env         print go environment information  	bug         start a bug report  	fix         run go tool fix on packages  	fmt         run gofmt on package sources  	generate    generate go files by processing source  	get         download and install packages and dependencies  	install     compile and install packages and dependencies  	list        list packages  	run         compile and run go program  	test        test packages  	tool        run specified go tool  	version     print go version  	vet         run go tool vet on packages                  what did you expect to see     the help output for the  fix  and  vet  is not helpful  is is just    run go tool  s on packages   toolname    also the  fmt  output could be improved         what did you see instead     the help output should say what the command will effectively do  like for  vet   check the source code for potential issues    ,1
213990,16544109751.0,IssuesEvent,2021-05-27 21:00:18,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.17: document reflect changes for Go 1.17,Documentation NeedsInvestigation help wanted release-blocker,"As of filing this issue, the [Go 1.17 draft release notes](https://tip.golang.org/doc/go1.17) contained the following HTML:

<dl id=""reflect""><dt><a href=""/pkg/reflect/"">reflect</a></dt>
  <dd>
    <p><!-- CL 266197 -->
      TODO: <a href=""https://golang.org/cl/266197"">https://golang.org/cl/266197</a>: add Method.IsExported and StructField.IsExported methods
    </p>
    <p><!-- CL 281233 -->
      TODO: <a href=""https://golang.org/cl/281233"">https://golang.org/cl/281233</a>: add VisibleFields function
    </p>
    <p><!-- CL 284136 -->
      TODO: <a href=""https://golang.org/cl/284136"">https://golang.org/cl/284136</a>: panic if ArrayOf is called with negative length
    </p>
  </dd>
</dl>

---

This TODO needs to be resolved by July 1 so that we can have complete release notes for [Beta 1](https://golang.org/s/release#june-1--december-1-beta-1-issued).

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.17:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.17) and include ""For #44513. Fixes #46019."" in the body.",1.0,"doc/go1.17: document reflect changes for Go 1.17 - As of filing this issue, the [Go 1.17 draft release notes](https://tip.golang.org/doc/go1.17) contained the following HTML:

<dl id=""reflect""><dt><a href=""/pkg/reflect/"">reflect</a></dt>
  <dd>
    <p><!-- CL 266197 -->
      TODO: <a href=""https://golang.org/cl/266197"">https://golang.org/cl/266197</a>: add Method.IsExported and StructField.IsExported methods
    </p>
    <p><!-- CL 281233 -->
      TODO: <a href=""https://golang.org/cl/281233"">https://golang.org/cl/281233</a>: add VisibleFields function
    </p>
    <p><!-- CL 284136 -->
      TODO: <a href=""https://golang.org/cl/284136"">https://golang.org/cl/284136</a>: panic if ArrayOf is called with negative length
    </p>
  </dd>
</dl>

---

This TODO needs to be resolved by July 1 so that we can have complete release notes for [Beta 1](https://golang.org/s/release#june-1--december-1-beta-1-issued).

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.17:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.17) and include ""For #44513. Fixes #46019."" in the body.",1,doc      document reflect changes for go       as of filing this issue  the     contained the following html      reflect                    todo   a href    add method isexported and structfield isexported methods                    todo   a href    add visiblefields function                    todo   a href    panic if arrayof is called with negative length                   this todo needs to be resolved by july   so that we can have complete release notes for      a sequence of steps to resolve this issue may be      come up with a draft release note entry in this issue  then move the issue to needsfix state     send a cl with  doc           and include  for     fixes      in the body ,1
266983,28485811354.0,IssuesEvent,2023-04-18 07:47:43,Satheesh575555/openSSL_1.0.1g,https://api.github.com/repos/Satheesh575555/openSSL_1.0.1g,opened,CVE-2014-3572 (Medium) detected in opensslOpenSSL_1_0_1g,Mend: dependency security vulnerability,"## CVE-2014-3572 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>opensslOpenSSL_1_0_1g</b></p></summary>
<p>

<p>TLS/SSL and crypto library</p>
<p>Library home page: <a href=https://github.com/openssl/openssl.git>https://github.com/openssl/openssl.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Satheesh575555/openSSL_1.0.1g/commit/7a1521d6faa1c1b2bda3237d82c41b77511b2861"">7a1521d6faa1c1b2bda3237d82c41b77511b2861</a></p>

<p>Found in base branch: <b>main</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/ssl/s3_clnt.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/ssl/s3_clnt.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The ssl3_get_key_exchange function in s3_clnt.c in OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before 1.0.1k allows remote SSL servers to conduct ECDHE-to-ECDH downgrade attacks and trigger a loss of forward secrecy by omitting the ServerKeyExchange message.

<p>Publish Date: 2015-01-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2014-3572>CVE-2014-3572</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2014-3572"">https://nvd.nist.gov/vuln/detail/CVE-2014-3572</a></p>
<p>Release Date: 2015-01-09</p>
<p>Fix Resolution: 0.9.8zd,1.0.0p,1.0.1k</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2014-3572 (Medium) detected in opensslOpenSSL_1_0_1g - ## CVE-2014-3572 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>opensslOpenSSL_1_0_1g</b></p></summary>
<p>

<p>TLS/SSL and crypto library</p>
<p>Library home page: <a href=https://github.com/openssl/openssl.git>https://github.com/openssl/openssl.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Satheesh575555/openSSL_1.0.1g/commit/7a1521d6faa1c1b2bda3237d82c41b77511b2861"">7a1521d6faa1c1b2bda3237d82c41b77511b2861</a></p>

<p>Found in base branch: <b>main</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/ssl/s3_clnt.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/ssl/s3_clnt.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The ssl3_get_key_exchange function in s3_clnt.c in OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before 1.0.1k allows remote SSL servers to conduct ECDHE-to-ECDH downgrade attacks and trigger a loss of forward secrecy by omitting the ServerKeyExchange message.

<p>Publish Date: 2015-01-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2014-3572>CVE-2014-3572</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2014-3572"">https://nvd.nist.gov/vuln/detail/CVE-2014-3572</a></p>
<p>Release Date: 2015-01-09</p>
<p>Fix Resolution: 0.9.8zd,1.0.0p,1.0.1k</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      medium  detected in opensslopenssl            cve       medium severity vulnerability     vulnerable library    opensslopenssl              tls ssl and crypto library   library home page   a href    found in head commit   a href      found in base branch   main             vulnerable source files                  ssl   clnt c        ssl   clnt c                    vulnerability details         the   get key exchange function in   clnt c in openssl before              before        and       before       allows remote ssl servers to conduct ecdhe to ecdh downgrade attacks and trigger a loss of forward secrecy by omitting the serverkeyexchange message    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  low     availability impact  none   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                                  step up your open source security game with mend    ,0
100783,21515864398.0,IssuesEvent,2022-04-28 09:48:21,leo-editor/leo-editor,https://api.github.com/repos/leo-editor/leo-editor,closed,Annotate most Leo files,Enhancement AwaitingMerge Code,"See PR #2604. Waiting until after 6.6.1 to merge into devel.  All work is complete.

This issue is a mass update to more than 90 files, so there new bugs could creep in. Here, I think the risks are justified:

- The changes allow Leo to check almost all of Leo's source files.
- mypy found some real bugs.
- We will test the resulting code for about a month before releasing Leo 6.6.2.",1.0,"Annotate most Leo files - See PR #2604. Waiting until after 6.6.1 to merge into devel.  All work is complete.

This issue is a mass update to more than 90 files, so there new bugs could creep in. Here, I think the risks are justified:

- The changes allow Leo to check almost all of Leo's source files.
- mypy found some real bugs.
- We will test the resulting code for about a month before releasing Leo 6.6.2.",0,annotate most leo files   see pr     waiting until after       to merge into devel   all work is complete     this issue is a mass update to more than   files  so there new bugs could creep in  here  i think the risks are justified       the changes allow leo to check almost all of leo s source files     mypy found some real bugs     we will test the resulting code for about a month before releasing leo       ,0
117019,17400953435.0,IssuesEvent,2021-08-02 19:35:01,labstack/echo,https://api.github.com/repos/labstack/echo,closed,jwt-go Access Restriction Bypass Vuln,security,"### Issue Description
For echo's JWT middleware, the version of `jwt-go` being used is vulnerable to an Access Restriction Bypass. I'm not sure if the vulnerable affects echo, it appears it may not, with the way the lib is currently used. The library appears to be unmaintained and so longer-term, it should be considered moving to an alternative or using a patched version of the library in case implementation changes.

See: https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMDGRIJALVAJWTGO-596515

### Checklist

- [x] Dependencies installed
- [x] No typos
- [x] Searched existing issues and docs
",True,"jwt-go Access Restriction Bypass Vuln - ### Issue Description
For echo's JWT middleware, the version of `jwt-go` being used is vulnerable to an Access Restriction Bypass. I'm not sure if the vulnerable affects echo, it appears it may not, with the way the lib is currently used. The library appears to be unmaintained and so longer-term, it should be considered moving to an alternative or using a patched version of the library in case implementation changes.

See: https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMDGRIJALVAJWTGO-596515

### Checklist

- [x] Dependencies installed
- [x] No typos
- [x] Searched existing issues and docs
",0,jwt go access restriction bypass vuln       issue description  for echo s jwt middleware  the version of  jwt go  being used is vulnerable to an access restriction bypass  i m not sure if the vulnerable affects echo  it appears it may not  with the way the lib is currently used  the library appears to be unmaintained and so longer term  it should be considered moving to an alternative or using a patched version of the library in case implementation changes     see           checklist        dependencies installed      no typos      searched existing issues and docs  ,0
60019,3117673907.0,IssuesEvent,2015-09-04 04:01:55,framingeinstein/issues-test,https://api.github.com/repos/framingeinstein/issues-test,opened,SPK-359: Global Nav: About Speakman should link to Company,priority:normal priority:normal priority:normal priority:normal priority:normal priority:normal resolution:fixed,"Hi Toby, 

About Speakman should link to /Company. 

Thanks",6.0,"SPK-359: Global Nav: About Speakman should link to Company - Hi Toby, 

About Speakman should link to /Company. 

Thanks",0,spk    global nav  about speakman should link to company   hi toby    about speakman should link to  company    thanks,0
62150,15170258423.0,IssuesEvent,2021-02-12 22:49:57,dhermes/bezier,https://api.github.com/repos/dhermes/bezier,opened,Re-enable `-Werror=conversion` if possible.,build language: fortran,"This cropped up in debug mode in recent versions of `gcc`. See (TODO, add commit SHA here).",1.0,"Re-enable `-Werror=conversion` if possible. - This cropped up in debug mode in recent versions of `gcc`. See (TODO, add commit SHA here).",0,re enable   werror conversion  if possible    this cropped up in debug mode in recent versions of  gcc   see  todo  add commit sha here  ,0
211619,16451187557.0,IssuesEvent,2021-05-21 06:06:18,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: document restrictions on module zip extraction,Documentation GoCommand NeedsInvestigation modules,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.13rc1 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""/home/leighmcculloch/local/bin""
GOCACHE=""/home/leighmcculloch/.cache/go-build""
GOENV=""/home/leighmcculloch/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/leighmcculloch/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/home/leighmcculloch/local/bin/go/1.13rc1""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/home/leighmcculloch/local/bin/go/1.13rc1/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/leighmcculloch/devel/test/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build749101513=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

Attempted to `go get` a package at a version.

```
go get github.com/gobuffalo/packr@v1.21.4
```

### What did you expect to see?

The packages to be `go get`d without any issue.

### What did you see instead?

`go get` error'd saying that the package in the sum db is `410 Gone`.

```
$ go get github.com/gobuffalo/packr@v1.21.4
go: finding github.com/gobuffalo/packr v1.21.4
go: finding github.com v1.21.4
go: finding github.com/gobuffalo v1.21.4
go: finding github.com/gobuffalo/packr v1.21.4
go: downloading github.com/gobuffalo/packr v1.21.4
verifying github.com/gobuffalo/packr@v1.21.4: github.com/gobuffalo/packr@v1.21.4: reading https://sum.golang.org/lookup/github.com/gobuffalo/packr@v1.21.4: 410 Gone
```

If I visit the `sum.golang.org` URL manually in a browser, I see this error:
```
not found: unzip /tmp/gopath/pkg/mod/cache/download/github.com/gobuffalo/packr/@v/v1.21.4.zip: case-insensitive file name collision: ""SHOULDERS.md"" and ""shoulders.md""
```

The `packr` project did indeed have two files named `SHOULDERS.md` and `shoulders.md` in `v1.21.4`.

Setting `GONOSUMDB` and turning off `GOPROXY` moves past the limitation in sum.golang.org, but then a similar error appears locally:

```
$ GONOSUMDB=github.com/gobuffalo/packr GOPROXY=direct go1.13rc1 get github.com/gobuffalo/packr@v1.21.4
go: finding github.com/gobuffalo/packr v1.21.4
go: downloading github.com/gobuffalo/packr v1.21.4
go: extracting github.com/gobuffalo/packr v1.21.4
-> unzip /home/leighmcculloch/go/pkg/mod/cache/download/github.com/gobuffalo/packr/@v/v1.21.4.zip: case-insensitive file name collision: ""SHOULDERS.md"" and ""shoulders.md""
go get: unzip /home/leighmcculloch/go/pkg/mod/cache/download/github.com/gobuffalo/packr/@v/v1.21.4.zip: case-insensitive file name collision: ""SHOULDERS.md"" and ""shoulders.md""
```

It appears that versions of projects that contain case insensitive collisions are currently not supported in Go Modules. Checking out the package into a GOPATH manually as `go get` used to still works, and `dep` successfully works with it too.

I think for portability there's some value in not allowing files that collide on case insensitive file systems, but existing packages that were published are now inaccessible.

_This issue was encountered while attempting to upgrade a repo from dep to modules stellar/go#1634._",1.0,"cmd/go: document restrictions on module zip extraction - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.13rc1 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""/home/leighmcculloch/local/bin""
GOCACHE=""/home/leighmcculloch/.cache/go-build""
GOENV=""/home/leighmcculloch/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/leighmcculloch/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/home/leighmcculloch/local/bin/go/1.13rc1""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/home/leighmcculloch/local/bin/go/1.13rc1/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/leighmcculloch/devel/test/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build749101513=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

Attempted to `go get` a package at a version.

```
go get github.com/gobuffalo/packr@v1.21.4
```

### What did you expect to see?

The packages to be `go get`d without any issue.

### What did you see instead?

`go get` error'd saying that the package in the sum db is `410 Gone`.

```
$ go get github.com/gobuffalo/packr@v1.21.4
go: finding github.com/gobuffalo/packr v1.21.4
go: finding github.com v1.21.4
go: finding github.com/gobuffalo v1.21.4
go: finding github.com/gobuffalo/packr v1.21.4
go: downloading github.com/gobuffalo/packr v1.21.4
verifying github.com/gobuffalo/packr@v1.21.4: github.com/gobuffalo/packr@v1.21.4: reading https://sum.golang.org/lookup/github.com/gobuffalo/packr@v1.21.4: 410 Gone
```

If I visit the `sum.golang.org` URL manually in a browser, I see this error:
```
not found: unzip /tmp/gopath/pkg/mod/cache/download/github.com/gobuffalo/packr/@v/v1.21.4.zip: case-insensitive file name collision: ""SHOULDERS.md"" and ""shoulders.md""
```

The `packr` project did indeed have two files named `SHOULDERS.md` and `shoulders.md` in `v1.21.4`.

Setting `GONOSUMDB` and turning off `GOPROXY` moves past the limitation in sum.golang.org, but then a similar error appears locally:

```
$ GONOSUMDB=github.com/gobuffalo/packr GOPROXY=direct go1.13rc1 get github.com/gobuffalo/packr@v1.21.4
go: finding github.com/gobuffalo/packr v1.21.4
go: downloading github.com/gobuffalo/packr v1.21.4
go: extracting github.com/gobuffalo/packr v1.21.4
-> unzip /home/leighmcculloch/go/pkg/mod/cache/download/github.com/gobuffalo/packr/@v/v1.21.4.zip: case-insensitive file name collision: ""SHOULDERS.md"" and ""shoulders.md""
go get: unzip /home/leighmcculloch/go/pkg/mod/cache/download/github.com/gobuffalo/packr/@v/v1.21.4.zip: case-insensitive file name collision: ""SHOULDERS.md"" and ""shoulders.md""
```

It appears that versions of projects that contain case insensitive collisions are currently not supported in Go Modules. Checking out the package into a GOPATH manually as `go get` used to still works, and `dep` successfully works with it too.

I think for portability there's some value in not allowing files that collide on case insensitive file systems, but existing packages that were published are now inaccessible.

_This issue was encountered while attempting to upgrade a repo from dep to modules stellar/go#1634._",1,cmd go  document restrictions on module zip extraction            what version of go are you using   go version            go version  go version     linux             does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin   home leighmcculloch local bin   gocache   home leighmcculloch  cache go build   goenv   home leighmcculloch  config go env   goexe     goflags     gohostarch      gohostos  linux   gonoproxy     gonosumdb     goos  linux   gopath   home leighmcculloch go   goprivate     goproxy     goroot   home leighmcculloch local bin go       gosumdb  sum golang org   gotmpdir     gotooldir   home leighmcculloch local bin go     pkg tool linux     gccgo  gccgo   ar  ar   cc  gcc   cxx  g     cgo enabled      gomod   home leighmcculloch devel test go mod   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches             what did you do     attempted to  go get  a package at a version          go get github com gobuffalo packr                   what did you expect to see     the packages to be  go get d without any issue         what did you see instead      go get  error d saying that the package in the sum db is    gone             go get github com gobuffalo packr        go  finding github com gobuffalo packr        go  finding github com        go  finding github com gobuffalo        go  finding github com gobuffalo packr        go  downloading github com gobuffalo packr        verifying github com gobuffalo packr        github com gobuffalo packr        reading     gone         if i visit the  sum golang org  url manually in a browser  i see this error        not found  unzip  tmp gopath pkg mod cache download github com gobuffalo packr  v       zip  case insensitive file name collision   shoulders md  and  shoulders md          the  packr  project did indeed have two files named  shoulders md  and  shoulders md  in             setting  gonosumdb  and turning off  goproxy  moves past the limitation in sum golang org  but then a similar error appears locally            gonosumdb github com gobuffalo packr goproxy direct     get github com gobuffalo packr        go  finding github com gobuffalo packr        go  downloading github com gobuffalo packr        go  extracting github com gobuffalo packr           unzip  home leighmcculloch go pkg mod cache download github com gobuffalo packr  v       zip  case insensitive file name collision   shoulders md  and  shoulders md   go get  unzip  home leighmcculloch go pkg mod cache download github com gobuffalo packr  v       zip  case insensitive file name collision   shoulders md  and  shoulders md          it appears that versions of projects that contain case insensitive collisions are currently not supported in go modules  checking out the package into a gopath manually as  go get  used to still works  and  dep  successfully works with it too     i think for portability there s some value in not allowing files that collide on case insensitive file systems  but existing packages that were published are now inaccessible      this issue was encountered while attempting to upgrade a repo from dep to modules stellar go    ,1
188506,6777013195.0,IssuesEvent,2017-10-27 20:13:47,department-of-veterans-affairs/caseflow-efolder,https://api.github.com/repos/department-of-veterans-affairs/caseflow-efolder,opened,Downloading demo cases with arbitrary numbers fail,bug-low-priority whiskey,"A recent change broke downloading arbitrary numbered demo cases. So downloading only works for:
- DEMO1
- DEMO2
- DEMO3
- DEMO4
- DEMO5

But not for any other numbers.

# AC
- Verify you can download a demo case with an arbitrary file number.",1.0,"Downloading demo cases with arbitrary numbers fail - A recent change broke downloading arbitrary numbered demo cases. So downloading only works for:
- DEMO1
- DEMO2
- DEMO3
- DEMO4
- DEMO5

But not for any other numbers.

# AC
- Verify you can download a demo case with an arbitrary file number.",0,downloading demo cases with arbitrary numbers fail   a recent change broke downloading arbitrary numbered demo cases  so downloading only works for                              but not for any other numbers       ac    verify you can download a demo case with an arbitrary file number ,0
272252,29794998437.0,IssuesEvent,2023-06-16 01:03:03,billmcchesney1/concord,https://api.github.com/repos/billmcchesney1/concord,closed,CVE-2020-13933 (High) detected in shiro-core-1.5.1.jar - autoclosed,Mend: dependency security vulnerability,"## CVE-2020-13933 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>shiro-core-1.5.1.jar</b></p></summary>

<p>Apache Shiro is a powerful and flexible open-source security framework that cleanly handles
        authentication, authorization, enterprise session management, single sign-on and cryptography services.</p>
<p>Library home page: <a href=""https://shiro.apache.org/shiro-core/"">https://shiro.apache.org/shiro-core/</a></p>
<p>Path to dependency file: /server/impl/pom.xml</p>
<p>Path to vulnerable library: /canner/.m2/repository/org/apache/shiro/shiro-core/1.5.1/shiro-core-1.5.1.jar,/canner/.m2/repository/org/apache/shiro/shiro-core/1.5.1/shiro-core-1.5.1.jar,/canner/.m2/repository/org/apache/shiro/shiro-core/1.5.1/shiro-core-1.5.1.jar</p>
<p>

Dependency Hierarchy:
  - :x: **shiro-core-1.5.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://api.github.com/repos/billmcchesney1/concord/commits/5478aeeda738bb625d7a100be550b55df120b611"">5478aeeda738bb625d7a100be550b55df120b611</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>  
  
Apache Shiro before 1.6.0, when using Apache Shiro, a specially crafted HTTP request may cause an authentication bypass.

<p>Publish Date: 2020-08-17
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-13933>CVE-2020-13933</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: High
  - Integrity Impact: None
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2020-13933"">https://nvd.nist.gov/vuln/detail/CVE-2020-13933</a></p>
<p>Release Date: 2020-08-17</p>
<p>Fix Resolution: 1.6.0</p>

</p>
</details>
<p></p>

***
:rescue_worker_helmet: Automatic Remediation is available for this issue",True,"CVE-2020-13933 (High) detected in shiro-core-1.5.1.jar - autoclosed - ## CVE-2020-13933 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>shiro-core-1.5.1.jar</b></p></summary>

<p>Apache Shiro is a powerful and flexible open-source security framework that cleanly handles
        authentication, authorization, enterprise session management, single sign-on and cryptography services.</p>
<p>Library home page: <a href=""https://shiro.apache.org/shiro-core/"">https://shiro.apache.org/shiro-core/</a></p>
<p>Path to dependency file: /server/impl/pom.xml</p>
<p>Path to vulnerable library: /canner/.m2/repository/org/apache/shiro/shiro-core/1.5.1/shiro-core-1.5.1.jar,/canner/.m2/repository/org/apache/shiro/shiro-core/1.5.1/shiro-core-1.5.1.jar,/canner/.m2/repository/org/apache/shiro/shiro-core/1.5.1/shiro-core-1.5.1.jar</p>
<p>

Dependency Hierarchy:
  - :x: **shiro-core-1.5.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://api.github.com/repos/billmcchesney1/concord/commits/5478aeeda738bb625d7a100be550b55df120b611"">5478aeeda738bb625d7a100be550b55df120b611</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>  
  
Apache Shiro before 1.6.0, when using Apache Shiro, a specially crafted HTTP request may cause an authentication bypass.

<p>Publish Date: 2020-08-17
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-13933>CVE-2020-13933</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: High
  - Integrity Impact: None
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2020-13933"">https://nvd.nist.gov/vuln/detail/CVE-2020-13933</a></p>
<p>Release Date: 2020-08-17</p>
<p>Fix Resolution: 1.6.0</p>

</p>
</details>
<p></p>

***
:rescue_worker_helmet: Automatic Remediation is available for this issue",0,cve      high  detected in shiro core       jar   autoclosed      cve       high severity vulnerability     vulnerable library    shiro core       jar      apache shiro is a powerful and flexible open source security framework that cleanly handles         authentication  authorization  enterprise session management  single sign on and cryptography services    library home page   a href     path to dependency file   server impl pom xml   path to vulnerable library   canner    repository org apache shiro shiro core       shiro core       jar  canner    repository org apache shiro shiro core       shiro core       jar  canner    repository org apache shiro shiro core       shiro core       jar     dependency hierarchy       x    shiro core       jar    vulnerable library   found in head commit   a href     found in base branch   master              vulnerability details         apache shiro before        when using apache shiro  a specially crafted http request may cause an authentication bypass    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  none     availability impact  none   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                       rescue worker helmet  automatic remediation is available for this issue,0
65314,12552861012.0,IssuesEvent,2020-06-06 19:42:39,gregoranders/ts-react-playground,https://api.github.com/repos/gregoranders/ts-react-playground,closed,"Fix ""method_complexity"" issue in src/script/loading.tsx",code quality,"Function `Loading` has a Cognitive Complexity of 7 (exceeds 5 allowed). Consider refactoring.

https://codeclimate.com/github/gregoranders/ts-react-playground/src/script/loading.tsx#issue_5edbe623ae49bb000100004a",1.0,"Fix ""method_complexity"" issue in src/script/loading.tsx - Function `Loading` has a Cognitive Complexity of 7 (exceeds 5 allowed). Consider refactoring.

https://codeclimate.com/github/gregoranders/ts-react-playground/src/script/loading.tsx#issue_5edbe623ae49bb000100004a",0,fix  method complexity  issue in src script loading tsx   function  loading  has a cognitive complexity of    exceeds   allowed   consider refactoring    ,0
278393,21076126545.0,IssuesEvent,2022-04-02 06:49:18,golang/go,https://api.github.com/repos/golang/go,closed,strings: Document use of simple case-folding in EqualFold ,Documentation help wanted NeedsFix,"At the moment, the documentation for [`EqualFold`](https://pkg.go.dev/strings#EqualFold) says:

> EqualFold reports whether s and t, interpreted as UTF-8 strings, are equal under Unicode case-folding, which is a more general form of case-insensitivity. 

However, this is under-specified. `EqualFold` uses simple case-folding, not full case-folding, which can be surprising. For example, Python 3 and Swift default to full case folding:

```
$ python3
> ""ß"".casefold()
'ss'
$ swift
> import Foundation
> ""ß"".folding(options: [.caseInsensitive], locale: nil)
$R0: String = ""ss""
```

I think it would be better to explicitly state that simple case-folding is being used. Perhaps something like:

```
EqualFold reports whether s and t, interpreted as UTF-8 strings,
are equal under simple Unicode case-folding, which is a more
general form of case-insensitivity. For more information,
see https://www.unicode.org/Public/UNIDATA/CaseFolding.txt.

In general, EqualFold(s1, s2) == (ToLower(s1) == ToLower(s2)).
```

Perhaps it would be also helpful to have an example like:

```go
func ExampleEqualFold() {
  fmt.Println(strings.EqualFold(""AB"", ""ab"")) // true because comparison uses simple case-folding
  fmt.Println(strings.EqualFold(""ß"", ""ss""))  // false because comparison does not use full case-folding
  // Output: true
  // Output: false
}
```

One can also add a fuzz test if so desired:

```go
func FuzzEqualFold(f *testing.F) {
    f.Fuzz(func(t *testing.T, s1 string, s2 string) {
        lower := strings.ToLower(s1) == strings.ToLower(s2)
        equalFold := strings.EqualFold(s1, s2)
        if lower != equalFold {
            t.Fatalf(""mismatch between ToLower and EqualFold: s1 = %s, s2 = %s, via Lower = %v, via EqualFold = %v"", s1, s2, lower, equalFold)
        }
    )
}
```",1.0,"strings: Document use of simple case-folding in EqualFold  - At the moment, the documentation for [`EqualFold`](https://pkg.go.dev/strings#EqualFold) says:

> EqualFold reports whether s and t, interpreted as UTF-8 strings, are equal under Unicode case-folding, which is a more general form of case-insensitivity. 

However, this is under-specified. `EqualFold` uses simple case-folding, not full case-folding, which can be surprising. For example, Python 3 and Swift default to full case folding:

```
$ python3
> ""ß"".casefold()
'ss'
$ swift
> import Foundation
> ""ß"".folding(options: [.caseInsensitive], locale: nil)
$R0: String = ""ss""
```

I think it would be better to explicitly state that simple case-folding is being used. Perhaps something like:

```
EqualFold reports whether s and t, interpreted as UTF-8 strings,
are equal under simple Unicode case-folding, which is a more
general form of case-insensitivity. For more information,
see https://www.unicode.org/Public/UNIDATA/CaseFolding.txt.

In general, EqualFold(s1, s2) == (ToLower(s1) == ToLower(s2)).
```

Perhaps it would be also helpful to have an example like:

```go
func ExampleEqualFold() {
  fmt.Println(strings.EqualFold(""AB"", ""ab"")) // true because comparison uses simple case-folding
  fmt.Println(strings.EqualFold(""ß"", ""ss""))  // false because comparison does not use full case-folding
  // Output: true
  // Output: false
}
```

One can also add a fuzz test if so desired:

```go
func FuzzEqualFold(f *testing.F) {
    f.Fuzz(func(t *testing.T, s1 string, s2 string) {
        lower := strings.ToLower(s1) == strings.ToLower(s2)
        equalFold := strings.EqualFold(s1, s2)
        if lower != equalFold {
            t.Fatalf(""mismatch between ToLower and EqualFold: s1 = %s, s2 = %s, via Lower = %v, via EqualFold = %v"", s1, s2, lower, equalFold)
        }
    )
}
```",1,strings  document use of simple case folding in equalfold    at the moment  the documentation for     says       equalfold reports whether s and t  interpreted as utf   strings  are equal under unicode case folding  which is a more general form of case insensitivity      however  this is under specified   equalfold  uses simple case folding  not full case folding  which can be surprising  for example  python   and swift default to full case folding                  ß  casefold     ss     swift    import foundation     ß  folding options     locale  nil       string    ss          i think it would be better to explicitly state that simple case folding is being used  perhaps something like          equalfold reports whether s and t  interpreted as utf   strings   are equal under simple unicode case folding  which is a more  general form of case insensitivity  for more information   see      in general  equalfold           tolower       tolower              perhaps it would be also helpful to have an example like        go  func exampleequalfold        fmt println strings equalfold  ab    ab       true because comparison uses simple case folding    fmt println strings equalfold  ß    ss        false because comparison does not use full case folding       output  true       output  false            one can also add a fuzz test if so desired        go  func fuzzequalfold f  testing f         f fuzz func t  testing t    string    string             lower    strings tolower       strings tolower             equalfold    strings equalfold                if lower    equalfold                t fatalf  mismatch between tolower and equalfold       s       s  via lower    v  via equalfold    v         lower  equalfold                           ,1
441622,30792502876.0,IssuesEvent,2023-07-31 17:13:54,golang/go,https://api.github.com/repos/golang/go,closed,spec: update to latest version before releasing Go 1.21,Documentation release-blocker,"Reminder issue to (wholesale) copy the spec (`$GOROOT/doc/go_spec.html`) from tip into the release branch so the released spec is up-to-date. Marking as release blocker so we don't forget.

This needs to be done after [CL 513275](https://go.dev/cl/513275) has been submitted to tip.

(This is easier than finding the two or three cherry-picks, also no potential 1.22 changes have made it into the spec.)",1.0,"spec: update to latest version before releasing Go 1.21 - Reminder issue to (wholesale) copy the spec (`$GOROOT/doc/go_spec.html`) from tip into the release branch so the released spec is up-to-date. Marking as release blocker so we don't forget.

This needs to be done after [CL 513275](https://go.dev/cl/513275) has been submitted to tip.

(This is easier than finding the two or three cherry-picks, also no potential 1.22 changes have made it into the spec.)",1,spec  update to latest version before releasing go       reminder issue to  wholesale  copy the spec    goroot doc go spec html   from tip into the release branch so the released spec is up to date  marking as release blocker so we don t forget     this needs to be done after     has been submitted to tip      this is easier than finding the two or three cherry picks  also no potential     changes have made it into the spec  ,1
41030,6888053494.0,IssuesEvent,2017-11-22 03:11:26,golang/go,https://api.github.com/repos/golang/go,closed,encoding/json: Unmarshal replaces interface{} types instead of acting on the underlying type,Documentation NeedsDecision,"Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
go version go1.8.3 darwin/amd64

### What operating system and processor architecture are you using (`go env`)?
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""

### What did you do?

Unmarshal to existing `map[string]interface{}` that is hidden behind an `interface{}`:
https://play.golang.org/p/kgaRznDOwb
```golang
var test interface{}
if err := json.Unmarshal([]byte(`{""A"": ""B""}`), &test); err != nil {
	panic(err)
}
fmt.Printf(""First:\n %+v\n"", test)

if err := json.Unmarshal([]byte(`{""C"": ""D""}`), &test); err != nil {
	panic(err)
}
fmt.Printf(""Second:\n %+v\n"", test)
```

### What did you expect to see?

First:
 map[A:B]
Second:
 map[A:B C:D]

According to docs: 

> To unmarshal JSON into an interface value, Unmarshal stores one of these in the interface value:
> ...
> map[string]interface{}, for JSON objects

> To unmarshal a JSON object into a map, Unmarshal first establishes a map to use. If the map is nil, Unmarshal allocates a new map. Otherwise Unmarshal reuses the existing map, keeping existing entries. 

I expect unmarshal to reuse the existing map, instead of replacing it.

### What did you see instead?
First:
 map[A:B]
Second:
 map[C:D]

",1.0,"encoding/json: Unmarshal replaces interface{} types instead of acting on the underlying type - Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
go version go1.8.3 darwin/amd64

### What operating system and processor architecture are you using (`go env`)?
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""

### What did you do?

Unmarshal to existing `map[string]interface{}` that is hidden behind an `interface{}`:
https://play.golang.org/p/kgaRznDOwb
```golang
var test interface{}
if err := json.Unmarshal([]byte(`{""A"": ""B""}`), &test); err != nil {
	panic(err)
}
fmt.Printf(""First:\n %+v\n"", test)

if err := json.Unmarshal([]byte(`{""C"": ""D""}`), &test); err != nil {
	panic(err)
}
fmt.Printf(""Second:\n %+v\n"", test)
```

### What did you expect to see?

First:
 map[A:B]
Second:
 map[A:B C:D]

According to docs: 

> To unmarshal JSON into an interface value, Unmarshal stores one of these in the interface value:
> ...
> map[string]interface{}, for JSON objects

> To unmarshal a JSON object into a map, Unmarshal first establishes a map to use. If the map is nil, Unmarshal allocates a new map. Otherwise Unmarshal reuses the existing map, keeping existing entries. 

I expect unmarshal to reuse the existing map, instead of replacing it.

### What did you see instead?
First:
 map[A:B]
Second:
 map[C:D]

",1,encoding json  unmarshal replaces interface   types instead of acting on the underlying type   please answer these questions before submitting your issue  thanks         what version of go are you using   go version     go version       darwin          what operating system and processor architecture are you using   go env     goarch      gobin     goexe     gohostarch      gohostos  darwin   goos  darwin         what did you do     unmarshal to existing  map interface    that is hidden behind an  interface            golang  var test interface    if err    json unmarshal  byte    a    b       test   err    nil    	panic err      fmt printf  first  n   v n   test     if err    json unmarshal  byte    c    d       test   err    nil    	panic err      fmt printf  second  n   v n   test              what did you expect to see     first    map   second    map     according to docs        to unmarshal json into an interface value  unmarshal stores one of these in the interface value            map interface    for json objects      to unmarshal a json object into a map  unmarshal first establishes a map to use  if the map is nil  unmarshal allocates a new map  otherwise unmarshal reuses the existing map  keeping existing entries      i expect unmarshal to reuse the existing map  instead of replacing it         what did you see instead   first    map   second    map     ,1
442657,30849007705.0,IssuesEvent,2023-08-02 15:25:56,golang/go,https://api.github.com/repos/golang/go,closed,reflect: documentation of StructField.Offset is not clear about type embedding,Documentation help wanted NeedsInvestigation compiler/runtime,"When I read the document I think StructField.Offset means the offset of the field of caller struct, not the offset of embeded struct.But it is the offset of embeded struct.
I think the document should be updated to clear it.

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.19.2 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/a/Library/Caches/go-build""
GOENV=""/Users/a/Library/Application Support/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/a/go/pkg/mod""
GOOS=""darwin""
GOPATH=""/Users/a/go""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GOVCS=""""
GOVERSION=""go1.19.2""
GCCGO=""gccgo""
GOAMD64=""v1""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/mw/884f6hx53r56gd7zxsm1h8bm0000gp/T/go-build2286547601=/tmp/go-build -gno-record-gcc-switches -fno-common""

</pre></details>

### What did you do?
https://go.dev/play/p/xae9pAtDcY7

### What did you expect to see?
8 8


### What did you see instead?
8 0


* ps current solution of the origin problem (get correct offset of a field of struct by name with reflect):
```
func mustGetOffsetFormStruct(rs reflect.Type,fieldName string) uintptr{
	f,ok:=rs.FieldByName(fieldName)
	if ok==false{
		panic(`fieldName not in struct`)
	}
	if len(f.Index)==1{
		return f.Offset
	}
	offset:=uintptr(0)
	for _,index:=range f.Index{
		rf:=rs.Field(index)
		offset+=rf.Offset
		rs = rf.Type
	}
	return offset
}
```",1.0,"reflect: documentation of StructField.Offset is not clear about type embedding - When I read the document I think StructField.Offset means the offset of the field of caller struct, not the offset of embeded struct.But it is the offset of embeded struct.
I think the document should be updated to clear it.

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.19.2 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/a/Library/Caches/go-build""
GOENV=""/Users/a/Library/Application Support/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/a/go/pkg/mod""
GOOS=""darwin""
GOPATH=""/Users/a/go""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GOVCS=""""
GOVERSION=""go1.19.2""
GCCGO=""gccgo""
GOAMD64=""v1""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/mw/884f6hx53r56gd7zxsm1h8bm0000gp/T/go-build2286547601=/tmp/go-build -gno-record-gcc-switches -fno-common""

</pre></details>

### What did you do?
https://go.dev/play/p/xae9pAtDcY7

### What did you expect to see?
8 8


### What did you see instead?
8 0


* ps current solution of the origin problem (get correct offset of a field of struct by name with reflect):
```
func mustGetOffsetFormStruct(rs reflect.Type,fieldName string) uintptr{
	f,ok:=rs.FieldByName(fieldName)
	if ok==false{
		panic(`fieldName not in struct`)
	}
	if len(f.Index)==1{
		return f.Offset
	}
	offset:=uintptr(0)
	for _,index:=range f.Index{
		rf:=rs.Field(index)
		offset+=rf.Offset
		rs = rf.Type
	}
	return offset
}
```",1,reflect  documentation of structfield offset is not clear about type embedding   when i read the document i think structfield offset means the offset of the field of caller struct  not the offset of embeded struct but it is the offset of embeded struct   i think the document should be updated to clear it         what version of go are you using   go version            go version  go version       darwin             does this issue reproduce with the latest release   yes          what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   users a library caches go build   goenv   users a library application support go env   goexe     goexperiment     goflags     gohostarch      gohostos  darwin   goinsecure     gomodcache   users a go pkg mod   goos  darwin   gopath   users a go   goproxy     goroot   usr local go   gosumdb  sum golang org   gotmpdir     gotooldir   usr local go pkg tool darwin     govcs     goversion          gccgo  gccgo          ar  ar   cc  clang   cxx  clang     cgo enabled      cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic  arch         pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders mw   t go    tmp go build  gno record gcc switches  fno common               what did you do            what did you expect to see                what did you see instead              ps current solution of the origin problem  get correct offset of a field of struct by name with reflect         func mustgetoffsetformstruct rs reflect type fieldname string  uintptr   	f ok  rs fieldbyname fieldname   	if ok  false   		panic  fieldname not in struct    	   	if len f index       		return f offset  	   	offset  uintptr     	for   index  range f index   		rf  rs field index   		offset  rf offset  		rs   rf type  	   	return offset        ,1
210,2636664195.0,IssuesEvent,2015-03-10 06:42:47,fabric8io/fabric8,https://api.github.com/repos/fabric8io/fabric8,closed,[Process Controller] Create file system IO API for process controller,process manager,It will be nice to have the API (somewhere near the `ProcessController` level) so process controller could read and write files within its sandbox.,1.0,[Process Controller] Create file system IO API for process controller - It will be nice to have the API (somewhere near the `ProcessController` level) so process controller could read and write files within its sandbox.,0,  create file system io api for process controller   it will be nice to have the api  somewhere near the  processcontroller  level  so process controller could read and write files within its sandbox ,0
188130,15128894959.0,IssuesEvent,2021-02-10 00:12:23,golang/go,https://api.github.com/repos/golang/go,closed,wiki: CodeReviewComments change: suggest got/want phrasing instead of actual/expected.,Documentation NeedsDecision,"Google's internal Go style has converged on ""got/want"" phrasing for test failures, with got before want. This is [reflected in the Standard Library tests, but there are exceptions.](https://golang.org/src/io/io_test.go) Even in the linked io_test.go there is one test that is written in the ""expected/got"" style.

I think it would be useful for the external style guide to suggest ""got/want"" as the common convention for test output: ""In test messages, prefer using the terms 'got/want' instead of 'actual/expected.'""

Creating a common convention would make it easier for programmers to read + understand unfamiliar Go tests. It would also mean that we could add a 'got/want' lint rule to Golint.",1.0,"wiki: CodeReviewComments change: suggest got/want phrasing instead of actual/expected. - Google's internal Go style has converged on ""got/want"" phrasing for test failures, with got before want. This is [reflected in the Standard Library tests, but there are exceptions.](https://golang.org/src/io/io_test.go) Even in the linked io_test.go there is one test that is written in the ""expected/got"" style.

I think it would be useful for the external style guide to suggest ""got/want"" as the common convention for test output: ""In test messages, prefer using the terms 'got/want' instead of 'actual/expected.'""

Creating a common convention would make it easier for programmers to read + understand unfamiliar Go tests. It would also mean that we could add a 'got/want' lint rule to Golint.",1,wiki  codereviewcomments change  suggest got want phrasing instead of actual expected    google s internal go style has converged on  got want  phrasing for test failures  with got before want  this is     even in the linked io test go there is one test that is written in the  expected got  style     i think it would be useful for the external style guide to suggest  got want  as the common convention for test output   in test messages  prefer using the terms  got want  instead of  actual expected       creating a common convention would make it easier for programmers to read   understand unfamiliar go tests  it would also mean that we could add a  got want  lint rule to golint ,1
34831,6383514204.0,IssuesEvent,2017-08-03 00:35:36,golang/go,https://api.github.com/repos/golang/go,closed,doc: add note about vendoring,Documentation NeedsFix,"This is a documentation request for [How to Write Go Code](https://golang.org/doc/code.html).

Given that the vendoring experiment is going away in 1.7, would it be possible to discuss vendoring and the vendor directory in the How to Write Go Code doc?
",1.0,"doc: add note about vendoring - This is a documentation request for [How to Write Go Code](https://golang.org/doc/code.html).

Given that the vendoring experiment is going away in 1.7, would it be possible to discuss vendoring and the vendor directory in the How to Write Go Code doc?
",1,doc  add note about vendoring   this is a documentation request for      given that the vendoring experiment is going away in      would it be possible to discuss vendoring and the vendor directory in the how to write go code doc  ,1
215794,16617611379.0,IssuesEvent,2021-06-02 18:53:37,golang/go,https://api.github.com/repos/golang/go,closed,io/fs: documentation of func Sub,Documentation NeedsInvestigation,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.16 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/harald/.cache/go-build""
GOENV=""/home/harald/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/harald/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/harald/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/opt/golang/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/opt/golang/go/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""go1.16""
GCCGO=""/usr/bin/gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2438140086=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

Read the documentation of the func Sub in package io/fs.
https://golang.org/pkg/io/fs/#Sub


### What did you expect to see?

See below

### What did you see instead?

There is a small bug in the description of what func Sub does. In

> Otherwise, Sub returns a new FS implementation sub that, in effect, implements sub.Open(dir) as fsys.Open(path.Join(dir, name)).

I think it should read ""sub.Open(name)"" instead of ""sub.Open(dir)"".",1.0,"io/fs: documentation of func Sub - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.16 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/harald/.cache/go-build""
GOENV=""/home/harald/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/harald/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/harald/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/opt/golang/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/opt/golang/go/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""go1.16""
GCCGO=""/usr/bin/gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2438140086=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

Read the documentation of the func Sub in package io/fs.
https://golang.org/pkg/io/fs/#Sub


### What did you expect to see?

See below

### What did you see instead?

There is a small bug in the description of what func Sub does. In

> Otherwise, Sub returns a new FS implementation sub that, in effect, implements sub.Open(dir) as fsys.Open(path.Join(dir, name)).

I think it should read ""sub.Open(name)"" instead of ""sub.Open(dir)"".",1,io fs  documentation of func sub         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version            go version  go version     linux             does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   home harald  cache go build   goenv   home harald  config go env   goexe     goflags     gohostarch      gohostos  linux   goinsecure     gomodcache   home harald go pkg mod   gonoproxy     gonosumdb     goos  linux   gopath   home harald go   goprivate     goproxy     goroot   opt golang go   gosumdb  sum golang org   gotmpdir     gotooldir   opt golang go pkg tool linux     govcs     goversion        gccgo   usr bin gccgo   ar  ar   cc  gcc   cxx  g     cgo enabled      gomod   dev null   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches             what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best          read the documentation of the func sub in package io fs              what did you expect to see     see below        what did you see instead     there is a small bug in the description of what func sub does  in      otherwise  sub returns a new fs implementation sub that  in effect  implements sub open dir  as fsys open path join dir  name       i think it should read  sub open name   instead of  sub open dir   ,1
40847,6872828676.0,IssuesEvent,2017-11-18 01:49:30,golang/go,https://api.github.com/repos/golang/go,closed,builtin: update documentation on builtin `make`,Documentation,"Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
1.9.2

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
darwin amd64

### What did you do?

If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.

read the documentation on the make builtin (https://golang.org/pkg/builtin/#make)

### What did you expect to see?

An explanation that specifying the capacity for a slice means that go will allocate an array big enough to hold that capacity without any resizing.
(After digging around the source code, I found this to be true)

### What did you see instead?

Ambiguous comment:
```
//	Slice: The size specifies the length. The capacity of the slice is
//	equal to its length. A second integer argument may be provided to
//	specify a different capacity; it must be no smaller than the
//	length, so make([]int, 0, 10) allocates a slice of length 0 and
//	capacity 10.
```

### Proposed Fix
Update this section of the comment to read:
```
//	Slice: The size specifies the length. The capacity of the slice is
//	equal to its length. A second integer argument may be provided to
//	specify a different capacity; it must be no smaller than the
//	length, so make([]int, 0, 10) allocates an underlying array of size 10
//	and returns a slice of length 0 and capacity 10 that is backed by this
//	underlying array.
```",1.0,"builtin: update documentation on builtin `make` - Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
1.9.2

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
darwin amd64

### What did you do?

If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.

read the documentation on the make builtin (https://golang.org/pkg/builtin/#make)

### What did you expect to see?

An explanation that specifying the capacity for a slice means that go will allocate an array big enough to hold that capacity without any resizing.
(After digging around the source code, I found this to be true)

### What did you see instead?

Ambiguous comment:
```
//	Slice: The size specifies the length. The capacity of the slice is
//	equal to its length. A second integer argument may be provided to
//	specify a different capacity; it must be no smaller than the
//	length, so make([]int, 0, 10) allocates a slice of length 0 and
//	capacity 10.
```

### Proposed Fix
Update this section of the comment to read:
```
//	Slice: The size specifies the length. The capacity of the slice is
//	equal to its length. A second integer argument may be provided to
//	specify a different capacity; it must be no smaller than the
//	length, so make([]int, 0, 10) allocates an underlying array of size 10
//	and returns a slice of length 0 and capacity 10 that is backed by this
//	underlying array.
```",1,builtin  update documentation on builtin  make    please answer these questions before submitting your issue  thanks           what version of go are you using   go version                  does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env     darwin          what did you do     if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best     read the documentation on the make builtin           what did you expect to see     an explanation that specifying the capacity for a slice means that go will allocate an array big enough to hold that capacity without any resizing    after digging around the source code  i found this to be true         what did you see instead     ambiguous comment          	slice  the size specifies the length  the capacity of the slice is    	equal to its length  a second integer argument may be provided to    	specify a different capacity  it must be no smaller than the    	length  so make  int        allocates a slice of length   and    	capacity                proposed fix  update this section of the comment to read          	slice  the size specifies the length  the capacity of the slice is    	equal to its length  a second integer argument may be provided to    	specify a different capacity  it must be no smaller than the    	length  so make  int        allocates an underlying array of size      	and returns a slice of length   and capacity   that is backed by this    	underlying array      ,1
347820,24900729297.0,IssuesEvent,2022-10-28 20:34:16,golang/go,https://api.github.com/repos/golang/go,closed,testing: silly typo in documentation,Documentation,"### What version of Go are you using (`go version`)?

<pre>
$ go version
1.19.2
</pre>

### Does this issue reproduce with the latest release?

y

### What operating system and processor architecture are you using (`go env`)?

N/A

### What did you do?

Read the docs.

### What did you expect to see?

Fewer typos.

### What did you see instead?

In the FuzzJSONMarshaling example:
```
t.Error(""Marshal: %v"", err)
```
Either this shouldn't have the ""%v"", or it should be `t.Errorf`.
",1.0,"testing: silly typo in documentation - ### What version of Go are you using (`go version`)?

<pre>
$ go version
1.19.2
</pre>

### Does this issue reproduce with the latest release?

y

### What operating system and processor architecture are you using (`go env`)?

N/A

### What did you do?

Read the docs.

### What did you expect to see?

Fewer typos.

### What did you see instead?

In the FuzzJSONMarshaling example:
```
t.Error(""Marshal: %v"", err)
```
Either this shouldn't have the ""%v"", or it should be `t.Errorf`.
",1,testing  silly typo in documentation       what version of go are you using   go version            go version                  does this issue reproduce with the latest release     y        what operating system and processor architecture are you using   go env       n a        what did you do     read the docs         what did you expect to see     fewer typos         what did you see instead     in the fuzzjsonmarshaling example        t error  marshal   v   err        either this shouldn t have the   v   or it should be  t errorf    ,1
32478,6066472957.0,IssuesEvent,2017-06-14 18:34:04,golang/go,https://api.github.com/repos/golang/go,closed,sync: confusing documentation for RWMutex,Documentation NeedsFix,"[sync#RWMutex](https://golang.org/pkg/sync/#RWMutex)
> An RWMutex is a reader/writer mutual exclusion lock. The lock can be held by an arbitrary number of readers or a single writer. RWMutexes can be created as part of other structures; the zero value for a RWMutex is an unlocked mutex.
>
>An RWMutex must not be copied after first use.
>
>If a goroutine holds a RWMutex for reading, it must not expect this or any other goroutine to be able to also take the read lock until the first read lock is released. In particular, this prohibits recursive read locking. This is to ensure that the lock eventually becomes available; a blocked Lock call excludes new readers from acquiring the lock. 

The third paragraph ""_If a goroutine holds a RWMutex for reading, it must not expect this or any other goroutine to be able to also take the read lock until the first read lock is released._"" appears to contradict the first paragraph ""_The lock can be held by an arbitrary number of readers or a single writer._""

After reading #7576 I think I understand this to mean that subsequent calls to `RWMutex.RLock()` will block if a call to `RWMutex.Lock()` has taken place (even if the write lock is currently not held), however that is not apparent from the rest of the documentation.

If this is the case can the forward for `RWLock` and the documentation for `RWLock.RLock` be updated to match please?",1.0,"sync: confusing documentation for RWMutex - [sync#RWMutex](https://golang.org/pkg/sync/#RWMutex)
> An RWMutex is a reader/writer mutual exclusion lock. The lock can be held by an arbitrary number of readers or a single writer. RWMutexes can be created as part of other structures; the zero value for a RWMutex is an unlocked mutex.
>
>An RWMutex must not be copied after first use.
>
>If a goroutine holds a RWMutex for reading, it must not expect this or any other goroutine to be able to also take the read lock until the first read lock is released. In particular, this prohibits recursive read locking. This is to ensure that the lock eventually becomes available; a blocked Lock call excludes new readers from acquiring the lock. 

The third paragraph ""_If a goroutine holds a RWMutex for reading, it must not expect this or any other goroutine to be able to also take the read lock until the first read lock is released._"" appears to contradict the first paragraph ""_The lock can be held by an arbitrary number of readers or a single writer._""

After reading #7576 I think I understand this to mean that subsequent calls to `RWMutex.RLock()` will block if a call to `RWMutex.Lock()` has taken place (even if the write lock is currently not held), however that is not apparent from the rest of the documentation.

If this is the case can the forward for `RWLock` and the documentation for `RWLock.RLock` be updated to match please?",1,sync  confusing documentation for rwmutex          an rwmutex is a reader writer mutual exclusion lock  the lock can be held by an arbitrary number of readers or a single writer  rwmutexes can be created as part of other structures  the zero value for a rwmutex is an unlocked mutex       an rwmutex must not be copied after first use       if a goroutine holds a rwmutex for reading  it must not expect this or any other goroutine to be able to also take the read lock until the first read lock is released  in particular  this prohibits recursive read locking  this is to ensure that the lock eventually becomes available  a blocked lock call excludes new readers from acquiring the lock      the third paragraph   if a goroutine holds a rwmutex for reading  it must not expect this or any other goroutine to be able to also take the read lock until the first read lock is released    appears to contradict the first paragraph   the lock can be held by an arbitrary number of readers or a single writer       after reading    i think i understand this to mean that subsequent calls to  rwmutex rlock    will block if a call to  rwmutex lock    has taken place  even if the write lock is currently not held   however that is not apparent from the rest of the documentation     if this is the case can the forward for  rwlock  and the documentation for  rwlock rlock  be updated to match please ,1
731104,25202396032.0,IssuesEvent,2022-11-13 09:08:48,CampManagerApp/CampManagerApp,https://api.github.com/repos/CampManagerApp/CampManagerApp,closed,3.0: The admin must be able to see the list of the members of the organisation.,admin priority_high,1- The user going to the members' space.,1.0,3.0: The admin must be able to see the list of the members of the organisation. - 1- The user going to the members' space.,0,     the admin must be able to see the list of the members of the organisation       the user going to the members  space ,0
63260,6835790492.0,IssuesEvent,2017-11-10 03:20:17,mrbigmouth/acgn-stock,https://api.github.com/repos/mrbigmouth/acgn-stock,closed,[voted] 分紅根據當季未上線天數調整,In testing,"根據當季未上線天數，調整非殭屍 (7 天內有登入) 之使用者在季度結算時所能拿到的分紅。

系統內投票網址在此：https://acgn-stock.com/ruleDiscuss/view/6TT48m5oXmR2ey7eM

投票結果的整理如下：
* 同意加入此規則
* 「完整分紅門檻」為 3 天
* 「零分紅門檻」為 5 天
* 「分紅修正曲線」為 100-75-50-25-0，並用 3~5 天區間內插之後為 100-50-0

所以詳細在分紅分配的實作上，需要考慮：
* 未上線天數 < 3 天者，套用「完整分紅門檻」定義，分紅計算時持有股權乘上 100% 後再行計算
* 未上線天數在 3, 4, 5 天者，套用「分紅修正曲線」定義：
  * 為 3 天者，分紅計算時持有股權乘上 100% 後再行計算
  * 為 4 天者，分紅計算時持有股權乘上 50% 後再行計算
  * 為 5 天者，分紅計算時持有股權乘上 0% 後再行計算
* 未上線天數 > 5 天者，套用「零分紅門檻」定義，分紅計算時持有股權乘上 0% 後再行計算 (等同於像殭屍那樣直接完全排除)",1.0,"[voted] 分紅根據當季未上線天數調整 - 根據當季未上線天數，調整非殭屍 (7 天內有登入) 之使用者在季度結算時所能拿到的分紅。

系統內投票網址在此：https://acgn-stock.com/ruleDiscuss/view/6TT48m5oXmR2ey7eM

投票結果的整理如下：
* 同意加入此規則
* 「完整分紅門檻」為 3 天
* 「零分紅門檻」為 5 天
* 「分紅修正曲線」為 100-75-50-25-0，並用 3~5 天區間內插之後為 100-50-0

所以詳細在分紅分配的實作上，需要考慮：
* 未上線天數 < 3 天者，套用「完整分紅門檻」定義，分紅計算時持有股權乘上 100% 後再行計算
* 未上線天數在 3, 4, 5 天者，套用「分紅修正曲線」定義：
  * 為 3 天者，分紅計算時持有股權乘上 100% 後再行計算
  * 為 4 天者，分紅計算時持有股權乘上 50% 後再行計算
  * 為 5 天者，分紅計算時持有股權乘上 0% 後再行計算
* 未上線天數 > 5 天者，套用「零分紅門檻」定義，分紅計算時持有股權乘上 0% 後再行計算 (等同於像殭屍那樣直接完全排除)",0,  分紅根據當季未上線天數調整   根據當季未上線天數，調整非殭屍    天內有登入  之使用者在季度結算時所能拿到的分紅。    系統內投票網址在此：     投票結果的整理如下：    同意加入此規則    「完整分紅門檻」為   天    「零分紅門檻」為   天    「分紅修正曲線」為          ，並用     天區間內插之後為          所以詳細在分紅分配的實作上，需要考慮：    未上線天數     天者，套用「完整分紅門檻」定義，分紅計算時持有股權乘上    後再行計算    未上線天數在         天者，套用「分紅修正曲線」定義：      為   天者，分紅計算時持有股權乘上    後再行計算      為   天者，分紅計算時持有股權乘上    後再行計算      為   天者，分紅計算時持有股權乘上    後再行計算    未上線天數     天者，套用「零分紅門檻」定義，分紅計算時持有股權乘上    後再行計算  等同於像殭屍那樣直接完全排除 ,0
122133,10212698135.0,IssuesEvent,2019-08-14 20:07:42,Kalmalyzer/testrunner-68k,https://api.github.com/repos/Kalmalyzer/testrunner-68k,opened,Print callstack at exception / end-of-test,Test runner feature,"We should analyze the stack contents and look for entries that look like return addresses.

Initially, it would be enough to capture the supervisor stack. Later on, we should probably capture either just the user stack (if the CPU is in user mode) or user + supervisor stacks (if the CPU is in supervisor mode).

The test runner should use the known range of the stack for limiting the stack walk.

The test runner should use the known ranges of code sections for accepting/rejecting return address candidates.

The test runner could inspect the code preceding each return address candidate, check if there's a call operation there, if not, reject the candidate as a false positive. This will however also reject constructs like ""pea return_address / ... / rts"".

The test runner could hook the simulation and track whenever calls are made (effectively implementing a call stack tracker outside of the emulator). This will also reject constructs like ""pea return_address / ... / rts"".",1.0,"Print callstack at exception / end-of-test - We should analyze the stack contents and look for entries that look like return addresses.

Initially, it would be enough to capture the supervisor stack. Later on, we should probably capture either just the user stack (if the CPU is in user mode) or user + supervisor stacks (if the CPU is in supervisor mode).

The test runner should use the known range of the stack for limiting the stack walk.

The test runner should use the known ranges of code sections for accepting/rejecting return address candidates.

The test runner could inspect the code preceding each return address candidate, check if there's a call operation there, if not, reject the candidate as a false positive. This will however also reject constructs like ""pea return_address / ... / rts"".

The test runner could hook the simulation and track whenever calls are made (effectively implementing a call stack tracker outside of the emulator). This will also reject constructs like ""pea return_address / ... / rts"".",0,print callstack at exception   end of test   we should analyze the stack contents and look for entries that look like return addresses     initially  it would be enough to capture the supervisor stack  later on  we should probably capture either just the user stack  if the cpu is in user mode  or user   supervisor stacks  if the cpu is in supervisor mode      the test runner should use the known range of the stack for limiting the stack walk     the test runner should use the known ranges of code sections for accepting rejecting return address candidates     the test runner could inspect the code preceding each return address candidate  check if there s a call operation there  if not  reject the candidate as a false positive  this will however also reject constructs like  pea return address         rts      the test runner could hook the simulation and track whenever calls are made  effectively implementing a call stack tracker outside of the emulator   this will also reject constructs like  pea return address         rts  ,0
41126,6892208147.0,IssuesEvent,2017-11-22 20:01:44,golang/go,https://api.github.com/repos/golang/go,closed,net/rpc: data race on non-net transport,Documentation HelpWanted,"<pre>Here is the reproducer:
<a href=""https://golang.org/cl/10613043/diff/3001/src/pkg/net/rpc/server_test.go"">https://golang.org/cl/10613043/diff/3001/src/pkg/net/rpc/server_test.go</a>

Report is below.

The gist: it's impossible to use net/rpc client/server with any non-thread-safe
transport as pipe or socketpair. It's inevitably produces races between read/write and
close. Such races corrupt arbitrary files and write data to random network connections.

=== RUN TestUnixPipe
==================
WARNING: DATA RACE
Read by goroutine 59:
  os.(*File).read()
      src/pkg/os/file_unix.go:175 +0x5b
  os.(*File).Read()
      src/pkg/os/file.go:95 +0xb9
  bufio.(*Reader).fill()
      src/pkg/bufio/bufio.go:119 +0x272
  bufio.(*Reader).Read()
      src/pkg/bufio/bufio.go:187 +0x3b1
  io.ReadAtLeast()
      src/pkg/io/io.go:284 +0x11a
  io.ReadFull()
      src/pkg/io/io.go:302 +0x7c
  encoding/gob.decodeUintReader()
      src/pkg/encoding/gob/decode.go:65 +0xba
  encoding/gob.(*Decoder).recvMessage()
      src/pkg/encoding/gob/decoder.go:73 +0x81
  encoding/gob.(*Decoder).decodeTypeSequence()
      src/pkg/encoding/gob/decoder.go:159 +0x92
  encoding/gob.(*Decoder).DecodeValue()
      src/pkg/encoding/gob/decoder.go:223 +0x124
  encoding/gob.(*Decoder).Decode()
      src/pkg/encoding/gob/decoder.go:202 +0x227
  net/rpc.(*gobClientCodec).ReadResponseHeader()
      src/pkg/net/rpc/client.go:218 +0x5d
  net/rpc.(*Client).input()
      src/pkg/net/rpc/client.go:106 +0x118

Previous write by goroutine 57:
  os.(*file).close()
      src/pkg/os/file_unix.go:110 +0x164
  os.(*File).Close()
      src/pkg/os/file_unix.go:99 +0x43
  net/rpc.(*gobClientCodec).Close()
      src/pkg/net/rpc/client.go:226 +0x48
  net/rpc.(*Client).Close()
      src/pkg/net/rpc/client.go:280 +0xc6
  net/rpc.TestUnixPipe()
      src/pkg/net/rpc/server_test.go:567 +0x3d5
  testing.tRunner()
      src/pkg/testing/testing.go:361 +0x10c

Goroutine 59 (running) created at:
  net/rpc.NewClientWithCodec()
      src/pkg/net/rpc/client.go:196 +0xd5
  net/rpc.NewClient()
      src/pkg/net/rpc/client.go:186 +0x18d
  net/rpc.TestUnixPipe()
      src/pkg/net/rpc/server_test.go:566 +0x3c7
  testing.tRunner()
      src/pkg/testing/testing.go:361 +0x10c

Goroutine 57 (running) created at:
  testing.RunTests()
      src/pkg/testing/testing.go:441 +0xaef
  testing.Main()
      src/pkg/testing/testing.go:373 +0xab
  main.main()
      net/rpc/_test/_testmain.go:74 +0xda
==================</pre>
",1.0,"net/rpc: data race on non-net transport - <pre>Here is the reproducer:
<a href=""https://golang.org/cl/10613043/diff/3001/src/pkg/net/rpc/server_test.go"">https://golang.org/cl/10613043/diff/3001/src/pkg/net/rpc/server_test.go</a>

Report is below.

The gist: it's impossible to use net/rpc client/server with any non-thread-safe
transport as pipe or socketpair. It's inevitably produces races between read/write and
close. Such races corrupt arbitrary files and write data to random network connections.

=== RUN TestUnixPipe
==================
WARNING: DATA RACE
Read by goroutine 59:
  os.(*File).read()
      src/pkg/os/file_unix.go:175 +0x5b
  os.(*File).Read()
      src/pkg/os/file.go:95 +0xb9
  bufio.(*Reader).fill()
      src/pkg/bufio/bufio.go:119 +0x272
  bufio.(*Reader).Read()
      src/pkg/bufio/bufio.go:187 +0x3b1
  io.ReadAtLeast()
      src/pkg/io/io.go:284 +0x11a
  io.ReadFull()
      src/pkg/io/io.go:302 +0x7c
  encoding/gob.decodeUintReader()
      src/pkg/encoding/gob/decode.go:65 +0xba
  encoding/gob.(*Decoder).recvMessage()
      src/pkg/encoding/gob/decoder.go:73 +0x81
  encoding/gob.(*Decoder).decodeTypeSequence()
      src/pkg/encoding/gob/decoder.go:159 +0x92
  encoding/gob.(*Decoder).DecodeValue()
      src/pkg/encoding/gob/decoder.go:223 +0x124
  encoding/gob.(*Decoder).Decode()
      src/pkg/encoding/gob/decoder.go:202 +0x227
  net/rpc.(*gobClientCodec).ReadResponseHeader()
      src/pkg/net/rpc/client.go:218 +0x5d
  net/rpc.(*Client).input()
      src/pkg/net/rpc/client.go:106 +0x118

Previous write by goroutine 57:
  os.(*file).close()
      src/pkg/os/file_unix.go:110 +0x164
  os.(*File).Close()
      src/pkg/os/file_unix.go:99 +0x43
  net/rpc.(*gobClientCodec).Close()
      src/pkg/net/rpc/client.go:226 +0x48
  net/rpc.(*Client).Close()
      src/pkg/net/rpc/client.go:280 +0xc6
  net/rpc.TestUnixPipe()
      src/pkg/net/rpc/server_test.go:567 +0x3d5
  testing.tRunner()
      src/pkg/testing/testing.go:361 +0x10c

Goroutine 59 (running) created at:
  net/rpc.NewClientWithCodec()
      src/pkg/net/rpc/client.go:196 +0xd5
  net/rpc.NewClient()
      src/pkg/net/rpc/client.go:186 +0x18d
  net/rpc.TestUnixPipe()
      src/pkg/net/rpc/server_test.go:566 +0x3c7
  testing.tRunner()
      src/pkg/testing/testing.go:361 +0x10c

Goroutine 57 (running) created at:
  testing.RunTests()
      src/pkg/testing/testing.go:441 +0xaef
  testing.Main()
      src/pkg/testing/testing.go:373 +0xab
  main.main()
      net/rpc/_test/_testmain.go:74 +0xda
==================</pre>
",1,net rpc  data race on non net transport    here is the reproducer   a href     report is below   the gist  it s impossible to use net rpc client server with any non thread safe transport as pipe or socketpair  it s inevitably produces races between read write and close  such races corrupt arbitrary files and write data to random network connections       run testunixpipe                    warning  data race read by goroutine      os   file  read         src pkg os file unix go        os   file  read         src pkg os file go        bufio   reader  fill         src pkg bufio bufio go        bufio   reader  read         src pkg bufio bufio go        io readatleast         src pkg io io go        io readfull         src pkg io io go        encoding gob decodeuintreader         src pkg encoding gob decode go        encoding gob   decoder  recvmessage         src pkg encoding gob decoder go        encoding gob   decoder  decodetypesequence         src pkg encoding gob decoder go        encoding gob   decoder  decodevalue         src pkg encoding gob decoder go        encoding gob   decoder  decode         src pkg encoding gob decoder go        net rpc   gobclientcodec  readresponseheader         src pkg net rpc client go        net rpc   client  input         src pkg net rpc client go       previous write by goroutine      os   file  close         src pkg os file unix go        os   file  close         src pkg os file unix go        net rpc   gobclientcodec  close         src pkg net rpc client go        net rpc   client  close         src pkg net rpc client go        net rpc testunixpipe         src pkg net rpc server test go        testing trunner         src pkg testing testing go       goroutine    running  created at    net rpc newclientwithcodec         src pkg net rpc client go        net rpc newclient         src pkg net rpc client go        net rpc testunixpipe         src pkg net rpc server test go        testing trunner         src pkg testing testing go       goroutine    running  created at    testing runtests         src pkg testing testing go        testing main         src pkg testing testing go        main main         net rpc  test  testmain go                          ,1
244859,20725289399.0,IssuesEvent,2022-03-14 00:29:30,DnD-Montreal/session-tome,https://api.github.com/repos/DnD-Montreal/session-tome,opened,Campaign Creation and Modification,acceptance test,"## Description
 Acceptance Test for #365
<!-- Provide a general summary of the test in the title above -->

[UAT Environment](https://session-tome.triassi.ca) for executing the acceptance flow

See #443 for automation of this flow

## Acceptance Flow
<!-- Describe the step by step procedure of the acceptance test -->
1. Log in as a regular user
2. Navigate to the campaigns page
3. Attempt to create a campaign
4. Verify that the campaign is created and that you are given a join code
5. Attempt to modify the campaign's details
6. Verify that the changes are saved and that the join code is also updated
",1.0,"Campaign Creation and Modification - ## Description
 Acceptance Test for #365
<!-- Provide a general summary of the test in the title above -->

[UAT Environment](https://session-tome.triassi.ca) for executing the acceptance flow

See #443 for automation of this flow

## Acceptance Flow
<!-- Describe the step by step procedure of the acceptance test -->
1. Log in as a regular user
2. Navigate to the campaigns page
3. Attempt to create a campaign
4. Verify that the campaign is created and that you are given a join code
5. Attempt to modify the campaign's details
6. Verify that the changes are saved and that the join code is also updated
",0,campaign creation and modification      description  acceptance test for           for executing the acceptance flow  see    for automation of this flow     acceptance flow      log in as a regular user    navigate to the campaigns page    attempt to create a campaign    verify that the campaign is created and that you are given a join code    attempt to modify the campaign s details    verify that the changes are saved and that the join code is also updated ,0
18686,13066329602.0,IssuesEvent,2020-07-30 21:28:02,icecube-trac/tix2,https://api.github.com/repos/icecube-trac/tix2,closed,[I3_TESTDATA] Needs an overhaul (Trac #1353),Migrated from Trac cleanup infrastructure,"There's a lot of old cruft in there we should be able to get rid of.

We need to think of a good organizational scheme too, like per-project and common locations for files.

Also, *all* of this should be documented.

Finally, some sort of versioning (it can be really simple) should be implemented, so we can clean periodically while ensuring old releases don't break. 

A good way to start is to maybe make a new location and just move the good stuff (I doubt there's much), while cleaning/fixing/adapting/setting-on-fire old, crufty scripts/tests/examples that depend on old, crufty test data.

Seems like a good winter-break project.

Migrated from https://code.icecube.wisc.edu/ticket/1353
```json
{
    ""status"": ""closed"", 
    ""changetime"": ""2019-07-01T13:30:20"", 
    ""description"": ""There's a lot of old cruft in there we should be able to get rid of.\n\nWe need to think of a good organizational scheme too, like per-project and common locations for files.\n\nAlso, *all* of this should be documented.\n\nFinally, some sort of versioning (it can be really simple) should be implemented, so we can clean periodically while ensuring old releases don't break. \n\nA good way to start is to maybe make a new location and just move the good stuff (I doubt there's much), while cleaning/fixing/adapting/setting-on-fire old, crufty scripts/tests/examples that depend on old, crufty test data.\n\nSeems like a good winter-break project."", 
    ""reporter"": ""olivas"", 
    ""cc"": ""nega"", 
    ""resolution"": ""fixed"", 
    ""_ts"": ""1561987820131392"", 
    ""component"": ""infrastructure"", 
    ""summary"": ""[I3_TESTDATA] Needs an overhaul"", 
    ""priority"": ""critical"", 
    ""keywords"": """", 
    ""time"": ""2015-09-17T15:24:49"", 
    ""milestone"": ""Autumnal Equinox 2019"", 
    ""owner"": ""olivas"", 
    ""type"": ""cleanup""
}
```
",1.0,"[I3_TESTDATA] Needs an overhaul (Trac #1353) - There's a lot of old cruft in there we should be able to get rid of.

We need to think of a good organizational scheme too, like per-project and common locations for files.

Also, *all* of this should be documented.

Finally, some sort of versioning (it can be really simple) should be implemented, so we can clean periodically while ensuring old releases don't break. 

A good way to start is to maybe make a new location and just move the good stuff (I doubt there's much), while cleaning/fixing/adapting/setting-on-fire old, crufty scripts/tests/examples that depend on old, crufty test data.

Seems like a good winter-break project.

Migrated from https://code.icecube.wisc.edu/ticket/1353
```json
{
    ""status"": ""closed"", 
    ""changetime"": ""2019-07-01T13:30:20"", 
    ""description"": ""There's a lot of old cruft in there we should be able to get rid of.\n\nWe need to think of a good organizational scheme too, like per-project and common locations for files.\n\nAlso, *all* of this should be documented.\n\nFinally, some sort of versioning (it can be really simple) should be implemented, so we can clean periodically while ensuring old releases don't break. \n\nA good way to start is to maybe make a new location and just move the good stuff (I doubt there's much), while cleaning/fixing/adapting/setting-on-fire old, crufty scripts/tests/examples that depend on old, crufty test data.\n\nSeems like a good winter-break project."", 
    ""reporter"": ""olivas"", 
    ""cc"": ""nega"", 
    ""resolution"": ""fixed"", 
    ""_ts"": ""1561987820131392"", 
    ""component"": ""infrastructure"", 
    ""summary"": ""[I3_TESTDATA] Needs an overhaul"", 
    ""priority"": ""critical"", 
    ""keywords"": """", 
    ""time"": ""2015-09-17T15:24:49"", 
    ""milestone"": ""Autumnal Equinox 2019"", 
    ""owner"": ""olivas"", 
    ""type"": ""cleanup""
}
```
",0,  needs an overhaul  trac       there s a lot of old cruft in there we should be able to get rid of   we need to think of a good organizational scheme too  like per project and common locations for files   also   all  of this should be documented   finally  some sort of versioning  it can be really simple  should be implemented  so we can clean periodically while ensuring old releases don t break    a good way to start is to maybe make a new location and just move the good stuff  i doubt there s much   while cleaning fixing adapting setting on fire old  crufty scripts tests examples that depend on old  crufty test data   seems like a good winter break project   migrated from      json        status    closed         changetime                      description    there s a lot of old cruft in there we should be able to get rid of  n nwe need to think of a good organizational scheme too  like per project and common locations for files  n nalso   all  of this should be documented  n nfinally  some sort of versioning  it can be really simple  should be implemented  so we can clean periodically while ensuring old releases don t break   n na good way to start is to maybe make a new location and just move the good stuff  i doubt there s much   while cleaning fixing adapting setting on fire old  crufty scripts tests examples that depend on old  crufty test data  n nseems like a good winter break project          reporter    olivas         cc    nega         resolution    fixed          ts              component    infrastructure         summary      needs an overhaul         priority    critical         keywords             time                      milestone    autumnal equinox           owner    olivas         type    cleanup        ,0
648840,21195250640.0,IssuesEvent,2022-04-08 23:15:14,CobeyH/SENG-480A,https://api.github.com/repos/CobeyH/SENG-480A,closed,Supplemental materials,frontend A Priority 2,"* Feature name: Supplemental materials
* Description:
- [x] Make sure all pull request are merged
- [x] Update product page
- [x] Update Wiki
- [x] Update project documentation
- [x] Update description of main use cases
- [x] Update personas
- [x] Update scenarios
- [x] Update architectural overview
- [x] Update main APIs/features
- [x] Update installation and usage instructions
- [x] Update the user study
- [x] Update user feedback
- [x] Update any other relevant information

* Time Estimation: Maybe 6-8 hours all together?
",1.0,"Supplemental materials - * Feature name: Supplemental materials
* Description:
- [x] Make sure all pull request are merged
- [x] Update product page
- [x] Update Wiki
- [x] Update project documentation
- [x] Update description of main use cases
- [x] Update personas
- [x] Update scenarios
- [x] Update architectural overview
- [x] Update main APIs/features
- [x] Update installation and usage instructions
- [x] Update the user study
- [x] Update user feedback
- [x] Update any other relevant information

* Time Estimation: Maybe 6-8 hours all together?
",0,supplemental materials     feature name  supplemental materials    description       make sure all pull request are merged      update product page      update wiki      update project documentation      update description of main use cases      update personas      update scenarios      update architectural overview      update main apis features      update installation and usage instructions      update the user study      update user feedback      update any other relevant information      time estimation  maybe     hours all together   ,0
16886,9917598277.0,IssuesEvent,2019-06-29 02:03:24,HR/Crypter,https://api.github.com/repos/HR/Crypter,opened,Buffer vulnerability,bug security,"Version: 3.1.0

```[DEP0005] DeprecationWarning: The Buffer() and new Buffer() constructors are not recommended for use due to security and usability concerns. Please use the new Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() construction methods instead.
    at showFlaggedDeprecation (buffer.js:127:13)```

Buffer constructor presents a major security threat and has already been deprecated so change its uses to `Buffer.from()`",True,"Buffer vulnerability - Version: 3.1.0

```[DEP0005] DeprecationWarning: The Buffer() and new Buffer() constructors are not recommended for use due to security and usability concerns. Please use the new Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() construction methods instead.
    at showFlaggedDeprecation (buffer.js:127:13)```

Buffer constructor presents a major security threat and has already been deprecated so change its uses to `Buffer.from()`",0,buffer vulnerability   version                deprecationwarning  the buffer   and new buffer   constructors are not recommended for use due to security and usability concerns  please use the new buffer alloc    buffer allocunsafe    or buffer from   construction methods instead       at showflaggeddeprecation  buffer js            buffer constructor presents a major security threat and has already been deprecated so change its uses to  buffer from   ,0
1944,7016285764.0,IssuesEvent,2017-12-21 02:37:53,littlevgl/lvgl,https://api.github.com/repos/littlevgl/lvgl,closed,Suggestion: Move application out of lvgl,architecture,It is a small suggestion to keep library clean and independent. Is it possible to move lv_app/lv_appx out of lvgl source as they are not part of library as such. May it can be moved to a new repo just like hal/misc etc. This way lvgl as a source will have no code that may or may not be usable to others. One can always close the lvapp repo if he/she needs.,1.0,Suggestion: Move application out of lvgl - It is a small suggestion to keep library clean and independent. Is it possible to move lv_app/lv_appx out of lvgl source as they are not part of library as such. May it can be moved to a new repo just like hal/misc etc. This way lvgl as a source will have no code that may or may not be usable to others. One can always close the lvapp repo if he/she needs.,0,suggestion  move application out of lvgl   it is a small suggestion to keep library clean and independent  is it possible to move lv app lv appx out of lvgl source as they are not part of library as such  may it can be moved to a new repo just like hal misc etc  this way lvgl as a source will have no code that may or may not be usable to others  one can always close the lvapp repo if he she needs ,0
307849,23219560099.0,IssuesEvent,2022-08-02 16:50:37,golang/go,https://api.github.com/repos/golang/go,opened,doc: write Go 1.20 release notes,Documentation NeedsFix release-blocker umbrella,"This is the tracking issue for writing the Go 1.20 Release Notes.

When the Go 1.19 Release Notes are complete, this should be closed, and a similar issue should be made for the next release. Previous issues are #51400, #47694, #44513, etc.",1.0,"doc: write Go 1.20 release notes - This is the tracking issue for writing the Go 1.20 Release Notes.

When the Go 1.19 Release Notes are complete, this should be closed, and a similar issue should be made for the next release. Previous issues are #51400, #47694, #44513, etc.",1,doc  write go     release notes   this is the tracking issue for writing the go     release notes     when the go     release notes are complete  this should be closed  and a similar issue should be made for the next release  previous issues are             etc ,1
702391,24120975844.0,IssuesEvent,2022-09-20 18:40:42,googleapis/nodejs-bigquery,https://api.github.com/repos/googleapis/nodejs-bigquery,closed,"BigQuery: ""before all"" hook for ""should get a list of datasets"" failed",type: bug priority: p1 api: bigquery flakybot: issue,"Note: #1012 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.

----

commit: 7933bfe9a1f706f45077e5ea64591aeebd87b27f
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/5a9d1c77-8b6e-4931-923f-14347600c24e), [Sponge](http://sponge2/5a9d1c77-8b6e-4931-923f-14347600c24e)
status: failed
<details><summary>Test output</summary><br><pre>invalid_grant: Invalid JWT Signature.
Error: invalid_grant: Invalid JWT Signature.
    at Gaxios._request (node_modules/gaxios/build/src/gaxios.js:130:23)
        -> /workspace/node_modules/gaxios/src/gaxios.ts:158:15
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async GoogleToken.requestToken (node_modules/gtoken/build/src/index.js:238:23)
    at async GoogleToken.getTokenAsync (node_modules/gtoken/build/src/index.js:145:20)
    at async JWT.refreshTokenNoCache (node_modules/google-auth-library/build/src/auth/jwtclient.js:172:23)
    at async JWT.getRequestMetadataAsync (node_modules/google-auth-library/build/src/auth/oauth2client.js:284:17)
    at async JWT.getRequestHeaders (node_modules/google-auth-library/build/src/auth/oauth2client.js:247:26)
    at async GoogleAuth.authorizeRequest (node_modules/google-auth-library/build/src/auth/googleauth.js:677:25)
    at async Promise.all (index 1)
    at async prepareRequest (node_modules/@google-cloud/storage/build/src/nodejs-common/util.js:447:61)</pre></details>",1.0,"BigQuery: ""before all"" hook for ""should get a list of datasets"" failed - Note: #1012 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.

----

commit: 7933bfe9a1f706f45077e5ea64591aeebd87b27f
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/5a9d1c77-8b6e-4931-923f-14347600c24e), [Sponge](http://sponge2/5a9d1c77-8b6e-4931-923f-14347600c24e)
status: failed
<details><summary>Test output</summary><br><pre>invalid_grant: Invalid JWT Signature.
Error: invalid_grant: Invalid JWT Signature.
    at Gaxios._request (node_modules/gaxios/build/src/gaxios.js:130:23)
        -> /workspace/node_modules/gaxios/src/gaxios.ts:158:15
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async GoogleToken.requestToken (node_modules/gtoken/build/src/index.js:238:23)
    at async GoogleToken.getTokenAsync (node_modules/gtoken/build/src/index.js:145:20)
    at async JWT.refreshTokenNoCache (node_modules/google-auth-library/build/src/auth/jwtclient.js:172:23)
    at async JWT.getRequestMetadataAsync (node_modules/google-auth-library/build/src/auth/oauth2client.js:284:17)
    at async JWT.getRequestHeaders (node_modules/google-auth-library/build/src/auth/oauth2client.js:247:26)
    at async GoogleAuth.authorizeRequest (node_modules/google-auth-library/build/src/auth/googleauth.js:677:25)
    at async Promise.all (index 1)
    at async prepareRequest (node_modules/@google-cloud/storage/build/src/nodejs-common/util.js:447:61)</pre></details>",0,bigquery   before all  hook for  should get a list of datasets  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   invalid grant  invalid jwt signature  error  invalid grant  invalid jwt signature      at gaxios  request  node modules gaxios build src gaxios js                  workspace node modules gaxios src gaxios ts         at processticksandrejections  internal process task queues js          at async googletoken requesttoken  node modules gtoken build src index js          at async googletoken gettokenasync  node modules gtoken build src index js          at async jwt refreshtokennocache  node modules google auth library build src auth jwtclient js          at async jwt getrequestmetadataasync  node modules google auth library build src auth   js          at async jwt getrequestheaders  node modules google auth library build src auth   js          at async googleauth authorizerequest  node modules google auth library build src auth googleauth js          at async promise all  index        at async preparerequest  node modules  google cloud storage build src nodejs common util js       ,0
12611,3632000091.0,IssuesEvent,2016-02-11 06:45:52,golang/go,https://api.github.com/repos/golang/go,opened,blog: typo in matchlang,Documentation,"http://blog.golang.org/matchlang says:

> This post explains why this is a difficult decision and how how Go can help

how how

/cc @mpvl @adg ",1.0,"blog: typo in matchlang - http://blog.golang.org/matchlang says:

> This post explains why this is a difficult decision and how how Go can help

how how

/cc @mpvl @adg ",1,blog  typo in matchlang     says       this post explains why this is a difficult decision and how how go can help    how how     cc  mpvl  adg ,1
3403,2762330881.0,IssuesEvent,2015-04-28 22:00:15,golang/go,https://api.github.com/repos/golang/go,closed,net/http: No easy way to get a server-side Request for testing.,Documentation,"(net/http).Request is populated vastly differently on the client and server sides.
That's probably not fixable, given Go1 compatibility.

But it causes problems when testing http handlers - httptest.ResponseRecorder needs a Request to go with it, and the obvious candidate (http.NewRequest) generates the client-side version, not the server-side version.

You can get the server-side version by setting up an httptest.Server and making a request to it, but that involves a lot of boilerplate and some syscalls.

It would be nice if there were a way (in the http or httptest package) to get a Request in the server-side format without having to go through the whole HTTP stack with a real server.

",1.0,"net/http: No easy way to get a server-side Request for testing. - (net/http).Request is populated vastly differently on the client and server sides.
That's probably not fixable, given Go1 compatibility.

But it causes problems when testing http handlers - httptest.ResponseRecorder needs a Request to go with it, and the obvious candidate (http.NewRequest) generates the client-side version, not the server-side version.

You can get the server-side version by setting up an httptest.Server and making a request to it, but that involves a lot of boilerplate and some syscalls.

It would be nice if there were a way (in the http or httptest package) to get a Request in the server-side format without having to go through the whole HTTP stack with a real server.

",1,net http  no easy way to get a server side request for testing     net http  request is populated vastly differently on the client and server sides   that s probably not fixable  given   compatibility     but it causes problems when testing http handlers   httptest responserecorder needs a request to go with it  and the obvious candidate  http newrequest  generates the client side version  not the server side version     you can get the server side version by setting up an httptest server and making a request to it  but that involves a lot of boilerplate and some syscalls     it would be nice if there were a way  in the http or httptest package  to get a request in the server side format without having to go through the whole http stack with a real server     ,1
275877,23950665083.0,IssuesEvent,2022-09-12 11:12:06,cockroachdb/cockroach,https://api.github.com/repos/cockroachdb/cockroach,opened,roachtest: import/tpcc/warehouses=4000/geo failed,C-test-failure O-robot O-roachtest release-blocker branch-release-22.2,"roachtest.import/tpcc/warehouses=4000/geo [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/6433153?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/6433153?buildTab=artifacts#/import/tpcc/warehouses=4000/geo) on release-22.2 @ [9b62adaceb821a96d325a8ce30f35952ec48e9e5](https://github.com/cockroachdb/cockroach/commits/9b62adaceb821a96d325a8ce30f35952ec48e9e5):


```
		  | golang.org/x/sync/errgroup.(*Group).Go.func1
		  | 	golang.org/x/sync/errgroup/external/org_golang_x_sync/errgroup/errgroup.go:74
		  | runtime.goexit
		  | 	GOROOT/src/runtime/asm_amd64.s:1594
		Wraps: (2) output in run_103452.976750600_n1_cockroach_workload_fixtures_import_tpcc
		Wraps: (3) ./cockroach workload fixtures import tpcc --warehouses=4000 --csv-server='http://localhost:8081' returned
		  | stderr:
		  | I220912 10:34:55.114251 1 ccl/workloadccl/fixture.go:318  [-] 1  starting import of 9 tables
		  | I220912 10:35:02.163833 85 ccl/workloadccl/fixture.go:481  [-] 2  imported 7.9 MiB in item table (100000 rows, 0 index entries, took 5.329441765s, 1.48 MiB/s)
		  | I220912 10:35:02.300062 31 ccl/workloadccl/fixture.go:481  [-] 3  imported 213 KiB in warehouse table (4000 rows, 0 index entries, took 5.465835173s, 0.04 MiB/s)
		  | I220912 10:35:05.158497 32 ccl/workloadccl/fixture.go:481  [-] 4  imported 3.9 MiB in district table (40000 rows, 0 index entries, took 8.324297383s, 0.47 MiB/s)
		  | I220912 10:35:44.504185 84 ccl/workloadccl/fixture.go:481  [-] 5  imported 546 MiB in new_order table (36000000 rows, 0 index entries, took 47.669828412s, 11.46 MiB/s)
		  |
		  | stdout:
		Wraps: (4) secondary error attachment
		  | UNCLASSIFIED_PROBLEM: context canceled
		  | (1) UNCLASSIFIED_PROBLEM
		  | Wraps: (2) Node 1. Command with error:
		  |   | ``````
		  |   | ./cockroach workload fixtures import tpcc --warehouses=4000 --csv-server='http://localhost:8081'
		  |   | ``````
		  | Wraps: (3) context canceled
		  | Error types: (1) errors.Unclassified (2) *hintdetail.withDetail (3) *errors.errorString
		Wraps: (5) context canceled
		Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *cluster.WithCommandDetails (4) *secondary.withSecondaryError (5) *errors.errorString

	monitor.go:127,import.go:154,import.go:181,test_runner.go:908: monitor failure: monitor task failed: read tcp 172.17.0.3:53088 -> 34.89.27.230:26257: read: connection reset by peer
		(1) attached stack trace
		  -- stack trace:
		  | main.(*monitorImpl).WaitE
		  | 	main/pkg/cmd/roachtest/monitor.go:115
		  | main.(*monitorImpl).Wait
		  | 	main/pkg/cmd/roachtest/monitor.go:123
		  | github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerImportTPCC.func1
		  | 	github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/import.go:154
		  | github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerImportTPCC.func3
		  | 	github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/import.go:181
		  | [...repeated from below...]
		Wraps: (2) monitor failure
		Wraps: (3) attached stack trace
		  -- stack trace:
		  | main.(*monitorImpl).wait.func2
		  | 	main/pkg/cmd/roachtest/monitor.go:171
		  | runtime.goexit
		  | 	GOROOT/src/runtime/asm_amd64.s:1594
		Wraps: (4) monitor task failed
		Wraps: (5) read tcp 172.17.0.3:53088 -> 34.89.27.230:26257
		Wraps: (6) read
		Wraps: (7) connection reset by peer
		Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *withstack.withStack (4) *errutil.withPrefix (5) *net.OpError (6) *os.SyscallError (7) syscall.Errno
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=16</code>
, <code>ROACHTEST_ssd=0</code>
</p>
<details><summary>Help</summary>
<p>


See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)



See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)

</p>
</details>
<details><summary>Same failure on other branches</summary>
<p>

- #85310 roachtest: import/tpcc/warehouses=4000/geo failed [raft sideload oom] [A-bulkio A-kv C-test-failure O-roachtest O-robot T-bulkio T-kv-replication branch-master release-blocker]
- #81430 roachtest: import/tpcc/warehouses=4000/geo failed [C-test-failure O-roachtest O-robot T-bulkio branch-release-22.1]
- #76824 roachtest: import/tpcc/warehouses=4000/geo failed [raft sideload oom] [C-test-failure O-roachtest O-robot S-3 T-kv-replication X-nostale branch-release-21.2 no-test-failure-activity]
</p>
</details>
/cc @cockroachdb/bulk-io
<sub>

[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*import/tpcc/warehouses=4000/geo.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
",2.0,"roachtest: import/tpcc/warehouses=4000/geo failed - roachtest.import/tpcc/warehouses=4000/geo [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/6433153?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/6433153?buildTab=artifacts#/import/tpcc/warehouses=4000/geo) on release-22.2 @ [9b62adaceb821a96d325a8ce30f35952ec48e9e5](https://github.com/cockroachdb/cockroach/commits/9b62adaceb821a96d325a8ce30f35952ec48e9e5):


```
		  | golang.org/x/sync/errgroup.(*Group).Go.func1
		  | 	golang.org/x/sync/errgroup/external/org_golang_x_sync/errgroup/errgroup.go:74
		  | runtime.goexit
		  | 	GOROOT/src/runtime/asm_amd64.s:1594
		Wraps: (2) output in run_103452.976750600_n1_cockroach_workload_fixtures_import_tpcc
		Wraps: (3) ./cockroach workload fixtures import tpcc --warehouses=4000 --csv-server='http://localhost:8081' returned
		  | stderr:
		  | I220912 10:34:55.114251 1 ccl/workloadccl/fixture.go:318  [-] 1  starting import of 9 tables
		  | I220912 10:35:02.163833 85 ccl/workloadccl/fixture.go:481  [-] 2  imported 7.9 MiB in item table (100000 rows, 0 index entries, took 5.329441765s, 1.48 MiB/s)
		  | I220912 10:35:02.300062 31 ccl/workloadccl/fixture.go:481  [-] 3  imported 213 KiB in warehouse table (4000 rows, 0 index entries, took 5.465835173s, 0.04 MiB/s)
		  | I220912 10:35:05.158497 32 ccl/workloadccl/fixture.go:481  [-] 4  imported 3.9 MiB in district table (40000 rows, 0 index entries, took 8.324297383s, 0.47 MiB/s)
		  | I220912 10:35:44.504185 84 ccl/workloadccl/fixture.go:481  [-] 5  imported 546 MiB in new_order table (36000000 rows, 0 index entries, took 47.669828412s, 11.46 MiB/s)
		  |
		  | stdout:
		Wraps: (4) secondary error attachment
		  | UNCLASSIFIED_PROBLEM: context canceled
		  | (1) UNCLASSIFIED_PROBLEM
		  | Wraps: (2) Node 1. Command with error:
		  |   | ``````
		  |   | ./cockroach workload fixtures import tpcc --warehouses=4000 --csv-server='http://localhost:8081'
		  |   | ``````
		  | Wraps: (3) context canceled
		  | Error types: (1) errors.Unclassified (2) *hintdetail.withDetail (3) *errors.errorString
		Wraps: (5) context canceled
		Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *cluster.WithCommandDetails (4) *secondary.withSecondaryError (5) *errors.errorString

	monitor.go:127,import.go:154,import.go:181,test_runner.go:908: monitor failure: monitor task failed: read tcp 172.17.0.3:53088 -> 34.89.27.230:26257: read: connection reset by peer
		(1) attached stack trace
		  -- stack trace:
		  | main.(*monitorImpl).WaitE
		  | 	main/pkg/cmd/roachtest/monitor.go:115
		  | main.(*monitorImpl).Wait
		  | 	main/pkg/cmd/roachtest/monitor.go:123
		  | github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerImportTPCC.func1
		  | 	github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/import.go:154
		  | github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerImportTPCC.func3
		  | 	github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/import.go:181
		  | [...repeated from below...]
		Wraps: (2) monitor failure
		Wraps: (3) attached stack trace
		  -- stack trace:
		  | main.(*monitorImpl).wait.func2
		  | 	main/pkg/cmd/roachtest/monitor.go:171
		  | runtime.goexit
		  | 	GOROOT/src/runtime/asm_amd64.s:1594
		Wraps: (4) monitor task failed
		Wraps: (5) read tcp 172.17.0.3:53088 -> 34.89.27.230:26257
		Wraps: (6) read
		Wraps: (7) connection reset by peer
		Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *withstack.withStack (4) *errutil.withPrefix (5) *net.OpError (6) *os.SyscallError (7) syscall.Errno
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=16</code>
, <code>ROACHTEST_ssd=0</code>
</p>
<details><summary>Help</summary>
<p>


See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)



See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)

</p>
</details>
<details><summary>Same failure on other branches</summary>
<p>

- #85310 roachtest: import/tpcc/warehouses=4000/geo failed [raft sideload oom] [A-bulkio A-kv C-test-failure O-roachtest O-robot T-bulkio T-kv-replication branch-master release-blocker]
- #81430 roachtest: import/tpcc/warehouses=4000/geo failed [C-test-failure O-roachtest O-robot T-bulkio branch-release-22.1]
- #76824 roachtest: import/tpcc/warehouses=4000/geo failed [raft sideload oom] [C-test-failure O-roachtest O-robot S-3 T-kv-replication X-nostale branch-release-21.2 no-test-failure-activity]
</p>
</details>
/cc @cockroachdb/bulk-io
<sub>

[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*import/tpcc/warehouses=4000/geo.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
",0,roachtest  import tpcc warehouses   geo failed   roachtest import tpcc warehouses   geo     with     on release                 		    golang org x sync errgroup   group  go   		    	golang org x sync errgroup external org golang x sync errgroup errgroup go   		    runtime goexit 		    	goroot src runtime asm   s   		wraps      output in run       cockroach workload fixtures import tpcc 		wraps        cockroach workload fixtures import tpcc   warehouses     csv server    returned 		    stderr  		                ccl workloadccl fixture go         starting import of   tables 		                ccl workloadccl fixture go         imported     mib in item table    rows    index entries  took          mib s  		                ccl workloadccl fixture go         imported   kib in warehouse table    rows    index entries  took          mib s  		                ccl workloadccl fixture go         imported     mib in district table    rows    index entries  took          mib s  		                ccl workloadccl fixture go         imported   mib in new order table    rows    index entries  took          mib s  		    		    stdout  		wraps      secondary error attachment 		    unclassified problem  context canceled 		        unclassified problem 		    wraps      node    command with error  		               		          cockroach workload fixtures import tpcc   warehouses     csv server    		               		    wraps      context canceled 		    error types      errors unclassified      hintdetail withdetail      errors errorstring 		wraps      context canceled 		error types       withstack withstack      errutil withprefix      cluster withcommanddetails      secondary withsecondaryerror      errors errorstring  	monitor go   import go   import go   test runner go    monitor failure  monitor task failed  read tcp                         read  connection reset by peer 		    attached stack trace 		     stack trace  		    main   monitorimpl  waite 		    	main pkg cmd roachtest monitor go   		    main   monitorimpl  wait 		    	main pkg cmd roachtest monitor go   		    github com cockroachdb cockroach pkg cmd roachtest tests registerimporttpcc   		    	github com cockroachdb cockroach pkg cmd roachtest tests import go   		    github com cockroachdb cockroach pkg cmd roachtest tests registerimporttpcc   		    	github com cockroachdb cockroach pkg cmd roachtest tests import go   		      		wraps      monitor failure 		wraps      attached stack trace 		     stack trace  		    main   monitorimpl  wait   		    	main pkg cmd roachtest monitor go   		    runtime goexit 		    	goroot src runtime asm   s   		wraps      monitor task failed 		wraps      read tcp                        		wraps      read 		wraps      connection reset by peer 		error types       withstack withstack      errutil withprefix      withstack withstack      errutil withprefix      net operror      os syscallerror     syscall errno      parameters   roachtest cloud gce     roachtest cpu       roachtest ssd        help      see         see             same failure on other branches          roachtest  import tpcc warehouses   geo failed          roachtest  import tpcc warehouses   geo failed        roachtest  import tpcc warehouses   geo failed          cc  cockroachdb bulk io                ,0
33469,6206524120.0,IssuesEvent,2017-07-06 18:37:34,golang/go,https://api.github.com/repos/golang/go,closed,runtime/pprof: document predefined profiles under Profiles,Documentation,"It is backwards for pprof.Profile to document the predefined profiles rather than pprof.Profiles or pprof.Lookup. Given the documentation of the predefined is required by multiple APIs under the pprof package, we might consider documenting them under the package doc.
",1.0,"runtime/pprof: document predefined profiles under Profiles - It is backwards for pprof.Profile to document the predefined profiles rather than pprof.Profiles or pprof.Lookup. Given the documentation of the predefined is required by multiple APIs under the pprof package, we might consider documenting them under the package doc.
",1,runtime pprof  document predefined profiles under profiles   it is backwards for pprof profile to document the predefined profiles rather than pprof profiles or pprof lookup  given the documentation of the predefined is required by multiple apis under the pprof package  we might consider documenting them under the package doc   ,1
741454,25796857992.0,IssuesEvent,2022-12-10 16:52:58,GoogleCloudPlatform/cloud-sql-proxy,https://api.github.com/repos/GoogleCloudPlatform/cloud-sql-proxy,closed,tests: TestMysqlSocket failed,priority: p2 type: bug flakybot: issue flakybot: flaky,"This test failed!

To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/main/packages/flakybot).

If I'm commenting on this issue too often, add the `flakybot: quiet` label and
I will stop commenting.

---

commit: 1cc6b364d792a4736d74cb4b03c8083fdf587e5c
buildURL: https://github.com/GoogleCloudPlatform/cloud-sql-proxy/actions/runs/3662209185
status: failed
<details><summary>Test output</summary><br><pre>    connection_test.go:45: unable to verify proxy was serving: proxy start failed: EOF 
         2022/12/10 02:21:44 current FDs rlimit set to 65536, wanted limit is 8500. Nothing to do here.
        2022/12/10 02:21:44 using credential file for authentication; path=""/home/runner/work/cloud-sql-proxy/cloud-sql-proxy/gha-creds-0ca1616630cb9f4a.json""
        2022/12/10 02:21:44 errors parsing config:
        	Get ""https://sqladmin.googleapis.com/sql/v1beta4/projects/cloud-sql-connector-testing/instances/us-central1~mysql-proxy-testing/connectSettings?alt=json&prettyPrint=false"": oauth2/google: unable to generate access token: Post ""https://iamcredentials.googleapis.com/v1/projects/-/serviceAccounts/cloudsql-proxy@gh-13a715-cloudsql-proxy.iam.gserviceaccount.com:generateAccessToken"": oauth2/google: invalid response when retrieving subject token: Get ""https://pipelines.actions.githubusercontent.com/wnFNgWBjsU8cogeeTzb2CiO5AuGdnZuICpyvLHwtISiGZGW9qa/00000000-0000-0000-0000-000000000000/_apis/distributedtask/hubs/Actions/plans/42d5011f-09c5-46cc-a750-1abf6f419794/jobs/077f8b7a-25eb-5f39-ec77-dd037d8f04e1/idtoken?api-version=2.0&audience=https%!A(MISSING)%!F(MISSING)%!F(MISSING)iam.googleapis.com%!F(MISSING)projects%!F(MISSING)174904406655%!F(MISSING)locations%!F(MISSING)global%!F(MISSING)workloadIdentityPools%!F(MISSING)gh-13a715-cloudsql-proxy%!F(MISSING)providers%!F(MISSING)gh-13a715-cloudsql-proxy"": stream error: stream ID 1; CANCEL; received from peer</pre></details>",1.0,"tests: TestMysqlSocket failed - This test failed!

To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/main/packages/flakybot).

If I'm commenting on this issue too often, add the `flakybot: quiet` label and
I will stop commenting.

---

commit: 1cc6b364d792a4736d74cb4b03c8083fdf587e5c
buildURL: https://github.com/GoogleCloudPlatform/cloud-sql-proxy/actions/runs/3662209185
status: failed
<details><summary>Test output</summary><br><pre>    connection_test.go:45: unable to verify proxy was serving: proxy start failed: EOF 
         2022/12/10 02:21:44 current FDs rlimit set to 65536, wanted limit is 8500. Nothing to do here.
        2022/12/10 02:21:44 using credential file for authentication; path=""/home/runner/work/cloud-sql-proxy/cloud-sql-proxy/gha-creds-0ca1616630cb9f4a.json""
        2022/12/10 02:21:44 errors parsing config:
        	Get ""https://sqladmin.googleapis.com/sql/v1beta4/projects/cloud-sql-connector-testing/instances/us-central1~mysql-proxy-testing/connectSettings?alt=json&prettyPrint=false"": oauth2/google: unable to generate access token: Post ""https://iamcredentials.googleapis.com/v1/projects/-/serviceAccounts/cloudsql-proxy@gh-13a715-cloudsql-proxy.iam.gserviceaccount.com:generateAccessToken"": oauth2/google: invalid response when retrieving subject token: Get ""https://pipelines.actions.githubusercontent.com/wnFNgWBjsU8cogeeTzb2CiO5AuGdnZuICpyvLHwtISiGZGW9qa/00000000-0000-0000-0000-000000000000/_apis/distributedtask/hubs/Actions/plans/42d5011f-09c5-46cc-a750-1abf6f419794/jobs/077f8b7a-25eb-5f39-ec77-dd037d8f04e1/idtoken?api-version=2.0&audience=https%!A(MISSING)%!F(MISSING)%!F(MISSING)iam.googleapis.com%!F(MISSING)projects%!F(MISSING)174904406655%!F(MISSING)locations%!F(MISSING)global%!F(MISSING)workloadIdentityPools%!F(MISSING)gh-13a715-cloudsql-proxy%!F(MISSING)providers%!F(MISSING)gh-13a715-cloudsql-proxy"": stream error: stream ID 1; CANCEL; received from peer</pre></details>",0,tests  testmysqlsocket failed   this test failed   to configure my behavior  see      if i m commenting on this issue too often  add the  flakybot  quiet  label and i will stop commenting        commit    buildurl    status  failed   test output       connection test go    unable to verify proxy was serving  proxy start failed  eof                       current fds rlimit set to    wanted limit is    nothing to do here                      using credential file for authentication  path   home runner work cloud sql proxy cloud sql proxy gha creds   json                      errors parsing config          	get      google  unable to generate access token  post      google  invalid response when retrieving subject token  get    stream error  stream id    cancel  received from peer  ,0
244686,18765454547.0,IssuesEvent,2021-11-05 22:57:12,golang/go,https://api.github.com/repos/golang/go,closed,net/netip: zero value of Addr is undocumented,Documentation NeedsFix release-blocker,"The zero value of Addr is not documented (is it 0.0.0.0? is it invalid?) but is referred to in some docs.

> If slice's length is not 4 or 16, AddrFromSlice returns Addr{}, false. ",1.0,"net/netip: zero value of Addr is undocumented - The zero value of Addr is not documented (is it 0.0.0.0? is it invalid?) but is referred to in some docs.

> If slice's length is not 4 or 16, AddrFromSlice returns Addr{}, false. ",1,net netip  zero value of addr is undocumented   the zero value of addr is not documented  is it          is it invalid   but is referred to in some docs       if slice s length is not   or    addrfromslice returns addr    false  ,1
65869,6976945662.0,IssuesEvent,2017-12-12 13:01:04,stebranchi/DarkPovoGang,https://api.github.com/repos/stebranchi/DarkPovoGang,closed,As a developer I want to test almost all functions,in progress test,"How to demo:
We will use Jest testing tool to test almost all functions and get good percentage in branch coverage and statement coverage.",1.0,"As a developer I want to test almost all functions - How to demo:
We will use Jest testing tool to test almost all functions and get good percentage in branch coverage and statement coverage.",0,as a developer i want to test almost all functions   how to demo  we will use jest testing tool to test almost all functions and get good percentage in branch coverage and statement coverage ,0
25181,24851186878.0,IssuesEvent,2022-10-26 20:13:54,bevyengine/bevy,https://api.github.com/repos/bevyengine/bevy,closed,Add support for reflection to remaining input types,A-Input C-Usability A-Reflection,"## What problem does this solve or what need does it fill?

This allows users to access the input types via reflection, which could be useful for scripting, debugging (via `bevy-inspector-egui` for example), etc.

## What solution would you like?

Add `#[derive(Reflect, FromReflect)]` to input types and register their types in the `InputPlugin`. Also add `#[reflect(Traits)]` for relevant traits to the types.

Common:
- `ButtonState`

Keyboard:
- `KeyCode` (`register_type` only, since it doesn't seem to be done in the `InputPlugin`)
- `KeyboardInput`

Mouse:
- `MouseButton`
- `MouseButtonInput`
- `MouseScrollUnit`
- `MouseMotion`
- `MouseWheel`

Gamepads:
- `GamepadButtonType`
- `GamepadAxisType`
- `Gamepad`
- `GamepadButton`
- `GamepadAxis`
- `GamepadEventType`
- `GamepadEvent`

Touch:
- `TouchPhase`
- `ForceTouch`
- `TouchInput`
- `Touch` (maybe?)
- `Touches` (maybe?)

For most (if not all) of these types, it's just a matter of adding `#[derive(Reflect, FromReflect)]` to the type and reflecting the relevant traits.

## What alternative(s) have you considered?

Users can recreate these types (with reflection support) in their own projects and create a system which maps the input types, but this step seems unnecessary. (This is different than mapping raw inputs to actions, it's mapping raw inputs to raw inputs.)

## Additional context

`KeyCode` already implements `Reflect` and `FromReflect`. The only change needed there is to add `.register_type::<KeyCode>()` in the `InputPlugin`.",True,"Add support for reflection to remaining input types - ## What problem does this solve or what need does it fill?

This allows users to access the input types via reflection, which could be useful for scripting, debugging (via `bevy-inspector-egui` for example), etc.

## What solution would you like?

Add `#[derive(Reflect, FromReflect)]` to input types and register their types in the `InputPlugin`. Also add `#[reflect(Traits)]` for relevant traits to the types.

Common:
- `ButtonState`

Keyboard:
- `KeyCode` (`register_type` only, since it doesn't seem to be done in the `InputPlugin`)
- `KeyboardInput`

Mouse:
- `MouseButton`
- `MouseButtonInput`
- `MouseScrollUnit`
- `MouseMotion`
- `MouseWheel`

Gamepads:
- `GamepadButtonType`
- `GamepadAxisType`
- `Gamepad`
- `GamepadButton`
- `GamepadAxis`
- `GamepadEventType`
- `GamepadEvent`

Touch:
- `TouchPhase`
- `ForceTouch`
- `TouchInput`
- `Touch` (maybe?)
- `Touches` (maybe?)

For most (if not all) of these types, it's just a matter of adding `#[derive(Reflect, FromReflect)]` to the type and reflecting the relevant traits.

## What alternative(s) have you considered?

Users can recreate these types (with reflection support) in their own projects and create a system which maps the input types, but this step seems unnecessary. (This is different than mapping raw inputs to actions, it's mapping raw inputs to raw inputs.)

## Additional context

`KeyCode` already implements `Reflect` and `FromReflect`. The only change needed there is to add `.register_type::<KeyCode>()` in the `InputPlugin`.",0,add support for reflection to remaining input types      what problem does this solve or what need does it fill     this allows users to access the input types via reflection  which could be useful for scripting  debugging  via  bevy inspector egui  for example   etc        what solution would you like     add      to input types and register their types in the  inputplugin   also add      for relevant traits to the types     common      buttonstate     keyboard      keycode    register type  only  since it doesn t seem to be done in the  inputplugin       keyboardinput     mouse      mousebutton      mousebuttoninput      mousescrollunit      mousemotion      mousewheel     gamepads      gamepadbuttontype      gamepadaxistype      gamepad      gamepadbutton      gamepadaxis      gamepadeventtype      gamepadevent     touch      touchphase      forcetouch      touchinput      touch   maybe       touches   maybe      for most  if not all  of these types  it s just a matter of adding      to the type and reflecting the relevant traits        what alternative s  have you considered     users can recreate these types  with reflection support  in their own projects and create a system which maps the input types  but this step seems unnecessary   this is different than mapping raw inputs to actions  it s mapping raw inputs to raw inputs         additional context     keycode  already implements  reflect  and  fromreflect   the only change needed there is to add   register type       in the  inputplugin  ,0
174819,14500008787.0,IssuesEvent,2020-12-11 17:27:14,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.16: document go command changes for Go 1.16,Documentation GoCommand NeedsInvestigation okay-after-beta1 release-blocker,"As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

```HTML
<h3 id=""go-command"">Go command</h3>

<p>
  TODO

  <!-- CL 237697: https://golang.org/cl/237697: cmd/go: error when -c or -i are used with unknown flags -->
  <!-- CL 255052: https://golang.org/cl/255052: cmd/go: default to GO111MODULE=on -->
  <!-- CL 266420: https://golang.org/cl/266420: yes (mention go help vcs): cmd/go: add GOVCS setting to control version control usage -->
  <!-- CL 244773: https://golang.org/cl/244773: cmd/go/internal/modload: drop requirements on excluded versions -->
</p>
```

And these TODOs:

```
TODO: write and link to section in golang.org/ref/mod
TODO: write and link to blog post
[...]
TODO: write and link to section in golang.org/ref/mod
TODO: write and link to tutorial or blog post
```

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.
",1.0,"doc/go1.16: document go command changes for Go 1.16 - As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

```HTML
<h3 id=""go-command"">Go command</h3>

<p>
  TODO

  <!-- CL 237697: https://golang.org/cl/237697: cmd/go: error when -c or -i are used with unknown flags -->
  <!-- CL 255052: https://golang.org/cl/255052: cmd/go: default to GO111MODULE=on -->
  <!-- CL 266420: https://golang.org/cl/266420: yes (mention go help vcs): cmd/go: add GOVCS setting to control version control usage -->
  <!-- CL 244773: https://golang.org/cl/244773: cmd/go/internal/modload: drop requirements on excluded versions -->
</p>
```

And these TODOs:

```
TODO: write and link to section in golang.org/ref/mod
TODO: write and link to blog post
[...]
TODO: write and link to section in golang.org/ref/mod
TODO: write and link to tutorial or blog post
```

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.
",1,doc      document go command changes for go       as of filing this issue  the     contained the following html        html   go command          todo                                  and these todos          todo  write and link to section in golang org ref mod  todo  write and link to blog post     todo  write and link to section in golang org ref mod  todo  write and link to tutorial or blog post         per     it s a release blocker for go     beta   to have a complete draft of the eventual release notes  and so the todo needs to be resolved     a sequence of steps to resolve this issue may be        come up with a draft release note entry in this issue  then move the issue to needsfix state      send a cl with  doc           and include  for     fixes   this issue    in the body   ,1
153915,12168497856.0,IssuesEvent,2020-04-27 12:47:22,OpenTechFund/hypha,https://api.github.com/repos/OpenTechFund/hypha,closed,Allow application form makers to set word counts for text fields and then display how many words are left to applicants,:dollar: Funded on Issuehunt UXreport2018 apply enhancement manage priority tested - approved for live ✅,"<!-- Issuehunt Badges -->
[<img alt=""Issuehunt badges"" src=""https://img.shields.io/badge/IssueHunt-%2450%20Funded-%2300A156.svg"" />](https://issuehunt.io/r/OpenTechFund/opentech.fund/issues/577)
<!-- /Issuehunt Badges -->





<!-- Issuehunt content -->

---

<details>
<summary>
<b>IssueHunt Summary</b>
</summary>


### Backers (Total: $50.00)

- [<img src='https://avatars1.githubusercontent.com/u/620336?v=4' alt='danblah' width=24 height=24> danblah](https://issuehunt.io/u/danblah) ($50.00)


#### [Become a backer now!](https://issuehunt.io/r/OpenTechFund/opentech.fund/issues/577)
#### [Or submit a pull request to get the deposits!](https://issuehunt.io/r/OpenTechFund/opentech.fund/issues/577)
### Tips

- Checkout the [Issuehunt explorer](https://issuehunt.io/r/OpenTechFund/opentech.fund/) to discover more funded issues.
- Need some help from other developers? [Add your repositories](https://issuehunt.io/r/new) on IssueHunt to raise funds.
---
IssueHunt has been backed by the following sponsors. [Become a sponsor](https://issuehunt.io/membership/members)
</details>
<!-- /Issuehunt content-->",1.0,"Allow application form makers to set word counts for text fields and then display how many words are left to applicants - <!-- Issuehunt Badges -->
[<img alt=""Issuehunt badges"" src=""https://img.shields.io/badge/IssueHunt-%2450%20Funded-%2300A156.svg"" />](https://issuehunt.io/r/OpenTechFund/opentech.fund/issues/577)
<!-- /Issuehunt Badges -->





<!-- Issuehunt content -->

---

<details>
<summary>
<b>IssueHunt Summary</b>
</summary>


### Backers (Total: $50.00)

- [<img src='https://avatars1.githubusercontent.com/u/620336?v=4' alt='danblah' width=24 height=24> danblah](https://issuehunt.io/u/danblah) ($50.00)


#### [Become a backer now!](https://issuehunt.io/r/OpenTechFund/opentech.fund/issues/577)
#### [Or submit a pull request to get the deposits!](https://issuehunt.io/r/OpenTechFund/opentech.fund/issues/577)
### Tips

- Checkout the [Issuehunt explorer](https://issuehunt.io/r/OpenTechFund/opentech.fund/) to discover more funded issues.
- Need some help from other developers? [Add your repositories](https://issuehunt.io/r/new) on IssueHunt to raise funds.
---
IssueHunt has been backed by the following sponsors. [Become a sponsor](https://issuehunt.io/membership/members)
</details>
<!-- /Issuehunt content-->",0,allow application form makers to set word counts for text fields and then display how many words are left to applicants                             issuehunt summary          backers  total                                              tips    checkout the     to discover more funded issues    need some help from other developers      on issuehunt to raise funds      issuehunt has been backed by the following sponsors         ,0
94282,15962357982.0,IssuesEvent,2021-04-16 01:08:11,RG4421/crayons,https://api.github.com/repos/RG4421/crayons,opened,CVE-2018-20822 (Medium) detected in node-sassv4.13.1,security vulnerability,"## CVE-2018-20822 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-sassv4.13.1</b></p></summary>
<p>

<p>:rainbow: Node.js bindings to libsass</p>
<p>Library home page: <a href=https://github.com/sass/node-sass.git>https://github.com/sass/node-sass.git</a></p>

<p>Found in base branch: <b>next</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>crayons/node_modules/node-sass/src/libsass/src/ast.hpp</b>
</p>
</details>
<p></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>  
  
LibSass 3.5.4 allows attackers to cause a denial-of-service (uncontrolled recursion in Sass::Complex_Selector::perform in ast.hpp and Sass::Inspect::operator in inspect.cpp).

<p>Publish Date: 2019-04-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20822>CVE-2018-20822</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20822"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20822</a></p>
<p>Release Date: 2019-08-06</p>
<p>Fix Resolution: LibSass - 3.6.0;node-sass - 4.13.1</p>

</p>
</details>
<p></p>
",True,"CVE-2018-20822 (Medium) detected in node-sassv4.13.1 - ## CVE-2018-20822 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-sassv4.13.1</b></p></summary>
<p>

<p>:rainbow: Node.js bindings to libsass</p>
<p>Library home page: <a href=https://github.com/sass/node-sass.git>https://github.com/sass/node-sass.git</a></p>

<p>Found in base branch: <b>next</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>crayons/node_modules/node-sass/src/libsass/src/ast.hpp</b>
</p>
</details>
<p></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>  
  
LibSass 3.5.4 allows attackers to cause a denial-of-service (uncontrolled recursion in Sass::Complex_Selector::perform in ast.hpp and Sass::Inspect::operator in inspect.cpp).

<p>Publish Date: 2019-04-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20822>CVE-2018-20822</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20822"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20822</a></p>
<p>Release Date: 2019-08-06</p>
<p>Fix Resolution: LibSass - 3.6.0;node-sass - 4.13.1</p>

</p>
</details>
<p></p>
",0,cve      medium  detected in node            cve       medium severity vulnerability     vulnerable library    node               rainbow  node js bindings to libsass   library home page   a href     found in base branch   next             vulnerable source files                 crayons node modules node sass src libsass src ast hpp                    vulnerability details         libsass       allows attackers to cause a denial of service  uncontrolled recursion in sass  complex selector  perform in ast hpp and sass  inspect  operator in inspect cpp     publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  required     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  libsass         node sass                  ,0
117668,11953125240.0,IssuesEvent,2020-04-03 20:15:06,golang/go,https://api.github.com/repos/golang/go,closed,x/crypto/blake2[b|s]: clarify the difference between the two blake2 packages in the godoc,Documentation NeedsFix,"x/crypto provides two implementations for blake2 hashing: blake2s and blake2b. Looking at the docs, there is no description for why someone should prefer one package over the other.

blake2.net says this: 

> BLAKE2 comes in two flavors:
> - BLAKE2b (or just BLAKE2) is optimized for 64-bit platforms—including NEON-enabled ARMs—and produces digests of any size between 1 and 64 bytes
> - BLAKE2s is optimized for 8- to 32-bit platforms and produces digests of any size between 1 and 32 bytes

The docs for these two packages should say something similar to inform users when making a choice.

/cc @FiloSottile ",1.0,"x/crypto/blake2[b|s]: clarify the difference between the two blake2 packages in the godoc - x/crypto provides two implementations for blake2 hashing: blake2s and blake2b. Looking at the docs, there is no description for why someone should prefer one package over the other.

blake2.net says this: 

> BLAKE2 comes in two flavors:
> - BLAKE2b (or just BLAKE2) is optimized for 64-bit platforms—including NEON-enabled ARMs—and produces digests of any size between 1 and 64 bytes
> - BLAKE2s is optimized for 8- to 32-bit platforms and produces digests of any size between 1 and 32 bytes

The docs for these two packages should say something similar to inform users when making a choice.

/cc @FiloSottile ",1,x crypto     clarify the difference between the two   packages in the godoc   x crypto provides two implementations for   hashing    and    looking at the docs  there is no description for why someone should prefer one package over the other       net says this          comes in two flavors          or just    is optimized for   bit platforms—including neon enabled arms—and produces digests of any size between   and   bytes        is optimized for    to   bit platforms and produces digests of any size between   and   bytes    the docs for these two packages should say something similar to inform users when making a choice      cc  filosottile ,1
5669,2962848810.0,IssuesEvent,2015-07-10 05:23:25,golang/go,https://api.github.com/repos/golang/go,closed,"doc: Release notes 1.5: ""go tool compile"" - is that native only or x-compile too?",Documentation,"http://tip.golang.org/doc/go1.5

Compiler and tools

Independent of but encouraged by the move to Go, the names of the tools have changed. The old names 6g, 8g and so on are gone; instead there is just one binary, accessible as go tool compile, that compiles Go source into binaries suitable for the architecture and operating system specified by $GOARCH and $GOOS. Similarly, there is now one linker (go tool link) and one assembler (go tool asm). The linker was translated automatically from the old C implementation, but the assembler is a new native Go implementation discussed in more detail below.

Similar to the drop of the names 6g, 8g, and so on, the output of the compiler and assembler are now given a plain .o suffix rather than .8, .6, etc.

-> I would find it useful if you can point out: does the compiler only target the native plattform, or will ""go tool compile"" target all plattforms go supports or ... ? As 3 commands gets replaced with one, it is not clear what that one command can exactly do.",1.0,"doc: Release notes 1.5: ""go tool compile"" - is that native only or x-compile too? - http://tip.golang.org/doc/go1.5

Compiler and tools

Independent of but encouraged by the move to Go, the names of the tools have changed. The old names 6g, 8g and so on are gone; instead there is just one binary, accessible as go tool compile, that compiles Go source into binaries suitable for the architecture and operating system specified by $GOARCH and $GOOS. Similarly, there is now one linker (go tool link) and one assembler (go tool asm). The linker was translated automatically from the old C implementation, but the assembler is a new native Go implementation discussed in more detail below.

Similar to the drop of the names 6g, 8g, and so on, the output of the compiler and assembler are now given a plain .o suffix rather than .8, .6, etc.

-> I would find it useful if you can point out: does the compiler only target the native plattform, or will ""go tool compile"" target all plattforms go supports or ... ? As 3 commands gets replaced with one, it is not clear what that one command can exactly do.",1,doc  release notes       go tool compile    is that native only or x compile too         compiler and tools    independent of but encouraged by the move to go  the names of the tools have changed  the old names      and so on are gone  instead there is just one binary  accessible as go tool compile  that compiles go source into binaries suitable for the architecture and operating system specified by  goarch and  goos  similarly  there is now one linker  go tool link  and one assembler  go tool asm   the linker was translated automatically from the old c implementation  but the assembler is a new native go implementation discussed in more detail below     similar to the drop of the names       and so on  the output of the compiler and assembler are now given a plain  o suffix rather than         etc        i would find it useful if you can point out  does the compiler only target the native plattform  or will  go tool compile  target all plattforms go supports or       as   commands gets replaced with one  it is not clear what that one command can exactly do ,1
10113,7918899388.0,IssuesEvent,2018-07-04 14:46:09,BirkbeckCTP/janeway,https://api.github.com/repos/BirkbeckCTP/janeway,closed,Review Manager Permissions,Important security,"- Review permissions on Manager pages to ensure Editors have required access
- Don't display links that Editors cannot use",True,"Review Manager Permissions - - Review permissions on Manager pages to ensure Editors have required access
- Don't display links that Editors cannot use",0,review manager permissions     review permissions on manager pages to ensure editors have required access    don t display links that editors cannot use,0
65360,16242329449.0,IssuesEvent,2021-05-07 11:02:49,flutter/flutter,https://api.github.com/repos/flutter/flutter,closed,Bundling dynamic libraries from external packages issue,a: build passed first triage platform-windows tool,"1. I have a custom .dll file, when I build the app it does bundle this dynamic library with the app, how can I bundle this dynamic library into building an executable app with `flutter build windows`?",1.0,"Bundling dynamic libraries from external packages issue - 1. I have a custom .dll file, when I build the app it does bundle this dynamic library with the app, how can I bundle this dynamic library into building an executable app with `flutter build windows`?",0,bundling dynamic libraries from external packages issue      i have a custom  dll file  when i build the app it does bundle this dynamic library with the app  how can i bundle this dynamic library into building an executable app with  flutter build windows  ,0
43682,7058410021.0,IssuesEvent,2018-01-04 20:16:04,golang/go,https://api.github.com/repos/golang/go,closed,sync: documentation for Map is inadequate,Documentation,"What's there is correct but unhelpful. How does it differ from the map type? When should it be used? When should it not be used? What are its performance characteristics.

I think a newcomer would find what's there inadequate to understand what it's for.",1.0,"sync: documentation for Map is inadequate - What's there is correct but unhelpful. How does it differ from the map type? When should it be used? When should it not be used? What are its performance characteristics.

I think a newcomer would find what's there inadequate to understand what it's for.",1,sync  documentation for map is inadequate   what s there is correct but unhelpful  how does it differ from the map type  when should it be used  when should it not be used  what are its performance characteristics     i think a newcomer would find what s there inadequate to understand what it s for ,1
65725,8837597166.0,IssuesEvent,2019-01-05 07:04:59,golang/go,https://api.github.com/repos/golang/go,opened,debug/gosym: mark LineTable.LineToPC and LineTable.PCToLine as deprecated,Documentation help wanted,"Both methods appear to be deprecated, according to their comments. We have a standard way of marking methods as deprecated; let's apply it here.

This may be a good first issue for someone who wants to try out contributing.

",1.0,"debug/gosym: mark LineTable.LineToPC and LineTable.PCToLine as deprecated - Both methods appear to be deprecated, according to their comments. We have a standard way of marking methods as deprecated; let's apply it here.

This may be a good first issue for someone who wants to try out contributing.

",1,debug gosym  mark linetable linetopc and linetable pctoline as deprecated   both methods appear to be deprecated  according to their comments  we have a standard way of marking methods as deprecated  let s apply it here     this may be a good first issue for someone who wants to try out contributing     ,1
225794,24881448378.0,IssuesEvent,2022-10-28 01:45:10,artsking/linux-4.19.72,https://api.github.com/repos/artsking/linux-4.19.72,closed,CVE-2022-1966 (High) detected in linux-yoctov5.4.51 - autoclosed,security vulnerability,"## CVE-2022-1966 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yoctov5.4.51</b></p></summary>
<p>

<p>Yocto Linux Embedded kernel</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto>https://git.yoctoproject.org/git/linux-yocto</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/artsking/linux-4.19.72/commit/8519fe4185f1a7567a708f01b476f195b0f1046c"">8519fe4185f1a7567a708f01b476f195b0f1046c</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/netfilter/nf_tables_api.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2022-32250. Reason: This candidate is a duplicate of CVE-2022-32250. Notes: All CVE users should reference CVE-2022-32250 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage.

<p>Publish Date: 2022-06-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-1966>CVE-2022-1966</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.8</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<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://www.linuxkernelcves.com/cves/CVE-2022-1966"">https://www.linuxkernelcves.com/cves/CVE-2022-1966</a></p>
<p>Release Date: 2022-06-06</p>
<p>Fix Resolution: v5.10.120,v5.15.45,v5.17.13,v5.19-rc1</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2022-1966 (High) detected in linux-yoctov5.4.51 - autoclosed - ## CVE-2022-1966 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yoctov5.4.51</b></p></summary>
<p>

<p>Yocto Linux Embedded kernel</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto>https://git.yoctoproject.org/git/linux-yocto</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/artsking/linux-4.19.72/commit/8519fe4185f1a7567a708f01b476f195b0f1046c"">8519fe4185f1a7567a708f01b476f195b0f1046c</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/netfilter/nf_tables_api.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2022-32250. Reason: This candidate is a duplicate of CVE-2022-32250. Notes: All CVE users should reference CVE-2022-32250 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage.

<p>Publish Date: 2022-06-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-1966>CVE-2022-1966</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.8</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<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://www.linuxkernelcves.com/cves/CVE-2022-1966"">https://www.linuxkernelcves.com/cves/CVE-2022-1966</a></p>
<p>Release Date: 2022-06-06</p>
<p>Fix Resolution: v5.10.120,v5.15.45,v5.17.13,v5.19-rc1</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in linux         autoclosed      cve       high severity vulnerability     vulnerable library    linux              yocto linux embedded kernel   library home page   a href    found in head commit   a href      found in base branch   master             vulnerable source files                  net netfilter nf tables api c                    vulnerability details            reject    do not use this candidate number  consultids  cve      reason  this candidate is a duplicate of cve      notes  all cve users should reference cve     instead of this candidate  all references and descriptions in this candidate have been removed to prevent accidental usage    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  local     attack complexity  low     privileges required  low     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                                        step up your open source security game with mend    ,0
42015,6961452656.0,IssuesEvent,2017-12-08 09:32:54,golang/go,https://api.github.com/repos/golang/go,closed,doc: editors.html uses Gogland (deprecated),Documentation,"Hi!

JetBrains renamed their Go IDE from [Gogland to Goland](https://blog.jetbrains.com/go/2017/11/02/announcing-goland-former-gogland-eap-18-final-product-name-templates-support-and-more/). It's time to update the page [Editor plugins and IDEs](https://golang.org/doc/editors.html) on main site.

Thanks.",1.0,"doc: editors.html uses Gogland (deprecated) - Hi!

JetBrains renamed their Go IDE from [Gogland to Goland](https://blog.jetbrains.com/go/2017/11/02/announcing-goland-former-gogland-eap-18-final-product-name-templates-support-and-more/). It's time to update the page [Editor plugins and IDEs](https://golang.org/doc/editors.html) on main site.

Thanks.",1,doc  editors html uses gogland  deprecated    hi     jetbrains renamed their go ide from     it s time to update the page     on main site     thanks ,1
40188,12751061127.0,IssuesEvent,2020-06-27 08:40:12,ArchiMageAlex/singularity-core,https://api.github.com/repos/ArchiMageAlex/singularity-core,closed,CVE-2019-12418 (High) detected in tomcat-embed-core-9.0.21.jar,security vulnerability,"## CVE-2019-12418 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tomcat-embed-core-9.0.21.jar</b></p></summary>

<p>Core Tomcat implementation</p>
<p>Library home page: <a href=""https://tomcat.apache.org/"">https://tomcat.apache.org/</a></p>
<p>Path to dependency file: /tmp/ws-scm/singularity-core/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.21/tomcat-embed-core-9.0.21.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-starter-web-2.1.6.RELEASE.jar (Root Library)
    - spring-boot-starter-tomcat-2.1.6.RELEASE.jar
      - :x: **tomcat-embed-core-9.0.21.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/ArchiMageAlex/singularity-core/commit/a3e0863a8b4b39f8a504c7fcb95c9c1e9c84f98d"">a3e0863a8b4b39f8a504c7fcb95c9c1e9c84f98d</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
When Apache Tomcat 9.0.0.M1 to 9.0.28, 8.5.0 to 8.5.47, 7.0.0 and 7.0.97 is configured with the JMX Remote Lifecycle Listener, a local attacker without access to the Tomcat process or configuration files is able to manipulate the RMI registry to perform a man-in-the-middle attack to capture user names and passwords used to access the JMX interface. The attacker can then use these credentials to access the JMX interface and gain complete control over the Tomcat instance.

<p>Publish Date: 2019-12-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-12418>CVE-2019-12418</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.0</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: High
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12418"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12418</a></p>
<p>Release Date: 2019-12-23</p>
<p>Fix Resolution: org.apache.tomcat:tomcat-catalina:7.0.98;org.apache.tomcat:tomcat-catalina:8.5.48;org.apache.tomcat:tomcat-catalina:9.0.29;org.apache.tomcat.embed:tomcat-embed-core:9.0.29</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2019-12418 (High) detected in tomcat-embed-core-9.0.21.jar - ## CVE-2019-12418 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tomcat-embed-core-9.0.21.jar</b></p></summary>

<p>Core Tomcat implementation</p>
<p>Library home page: <a href=""https://tomcat.apache.org/"">https://tomcat.apache.org/</a></p>
<p>Path to dependency file: /tmp/ws-scm/singularity-core/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.21/tomcat-embed-core-9.0.21.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-starter-web-2.1.6.RELEASE.jar (Root Library)
    - spring-boot-starter-tomcat-2.1.6.RELEASE.jar
      - :x: **tomcat-embed-core-9.0.21.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/ArchiMageAlex/singularity-core/commit/a3e0863a8b4b39f8a504c7fcb95c9c1e9c84f98d"">a3e0863a8b4b39f8a504c7fcb95c9c1e9c84f98d</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
When Apache Tomcat 9.0.0.M1 to 9.0.28, 8.5.0 to 8.5.47, 7.0.0 and 7.0.97 is configured with the JMX Remote Lifecycle Listener, a local attacker without access to the Tomcat process or configuration files is able to manipulate the RMI registry to perform a man-in-the-middle attack to capture user names and passwords used to access the JMX interface. The attacker can then use these credentials to access the JMX interface and gain complete control over the Tomcat instance.

<p>Publish Date: 2019-12-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-12418>CVE-2019-12418</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.0</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: High
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12418"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12418</a></p>
<p>Release Date: 2019-12-23</p>
<p>Fix Resolution: org.apache.tomcat:tomcat-catalina:7.0.98;org.apache.tomcat:tomcat-catalina:8.5.48;org.apache.tomcat:tomcat-catalina:9.0.29;org.apache.tomcat.embed:tomcat-embed-core:9.0.29</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in tomcat embed core       jar      cve       high severity vulnerability     vulnerable library    tomcat embed core       jar      core tomcat implementation   library home page   a href     path to dependency file   tmp ws scm singularity core pom xml   path to vulnerable library   root    repository org apache tomcat embed tomcat embed core       tomcat embed core       jar     dependency hierarchy      spring boot starter web       release jar  root library        spring boot starter tomcat       release jar          x    tomcat embed core       jar    vulnerable library   found in head commit   a href               vulnerability details         when apache tomcat         to              to              and       is configured with the jmx remote lifecycle listener  a local attacker without access to the tomcat process or configuration files is able to manipulate the rmi registry to perform a man in the middle attack to capture user names and passwords used to access the jmx interface  the attacker can then use these credentials to access the jmx interface and gain complete control over the tomcat instance    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  local     attack complexity  high     privileges required  low     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  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 tomcat tomcat catalina       org apache tomcat tomcat catalina       org apache tomcat tomcat catalina       org apache tomcat embed tomcat embed core                     step up your open source security game with whitesource    ,0
319073,27345227745.0,IssuesEvent,2023-02-27 03:59:21,emberjs/data,https://api.github.com/repos/emberjs/data,closed,Missing tests for legacy compat with computed `@each` `[]` and `length`,Needs Bug Verification test-contribution,While we don't intend to support these much longer for as long as we do support them we should be testing them. Currently it appears we broke support in 4.7+. Likely these chains still rely on secret handshakes in the prototype extensions that native arrays are given and which ours avoid adding.,1.0,Missing tests for legacy compat with computed `@each` `[]` and `length` - While we don't intend to support these much longer for as long as we do support them we should be testing them. Currently it appears we broke support in 4.7+. Likely these chains still rely on secret handshakes in the prototype extensions that native arrays are given and which ours avoid adding.,0,missing tests for legacy compat with computed   each      and  length    while we don t intend to support these much longer for as long as we do support them we should be testing them  currently it appears we broke support in       likely these chains still rely on secret handshakes in the prototype extensions that native arrays are given and which ours avoid adding ,0
180843,14814879837.0,IssuesEvent,2021-01-14 06:03:17,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/gopls: defining the workspace root,Documentation Tools gopls,"`gopls` supports both module and GOPATH modes. However, we need to define a scope in which language features like references, rename, and implementation should operate. The following is subject to, and will likely, change.

For now, we have the following cases:

### Module mode

#### Supported
- Open workspace at the module root (directory containing the `go.mod` file). The scope is the entire module.
- Open a subdirectory of a module. The scope is the subdirectory that has been opened.

#### Unsupported
- Open a directory that contains a module in a subdirectory. `gopls` will not work in this case.

### GOPATH mode

#### Supported
- Open a directory inside of your GOPATH. The scope is the open directory.

#### At your own risk
- Open your entire GOPATH. The workspace scope will be your entire `GOPATH`. Note that this will cause `gopls` to load your entire GOPATH. If your GOPATH is large, this will take a long time and cause `gopls` to be very slow.

To work around this case, you can create a new GOPATH that contains only the packages you want to work on.

#### Unsupported
- Open a directory containing your GOPATH. Similar to the case above, this will cause `gopls` to treat your entire GOPATH as the workspace scope. It will be very slow to start because it will try to find all of the Go files in the directory you have opened. It will then load all of the files it has found.

---

We are working on addressing all of these cases and improving the behavior of `gopls` in the unsupported cases. All of these cases will be supported once `gopls` reaches `v1.0.0`. 

We understand it may be inconvenient to change your typical workflow to accommodate frequent changes in `gopls`. In this case, it may be easier to stick with a version of `gopls` that works for you (`gopls/v0.2.2`, for instance), or if you are using GOPATH, `gopls` may not be the best tool to use until it reaches `v1.0.0`. 

If you have additional use cases that are not mentioned above, please comment below.
",1.0,"x/tools/gopls: defining the workspace root - `gopls` supports both module and GOPATH modes. However, we need to define a scope in which language features like references, rename, and implementation should operate. The following is subject to, and will likely, change.

For now, we have the following cases:

### Module mode

#### Supported
- Open workspace at the module root (directory containing the `go.mod` file). The scope is the entire module.
- Open a subdirectory of a module. The scope is the subdirectory that has been opened.

#### Unsupported
- Open a directory that contains a module in a subdirectory. `gopls` will not work in this case.

### GOPATH mode

#### Supported
- Open a directory inside of your GOPATH. The scope is the open directory.

#### At your own risk
- Open your entire GOPATH. The workspace scope will be your entire `GOPATH`. Note that this will cause `gopls` to load your entire GOPATH. If your GOPATH is large, this will take a long time and cause `gopls` to be very slow.

To work around this case, you can create a new GOPATH that contains only the packages you want to work on.

#### Unsupported
- Open a directory containing your GOPATH. Similar to the case above, this will cause `gopls` to treat your entire GOPATH as the workspace scope. It will be very slow to start because it will try to find all of the Go files in the directory you have opened. It will then load all of the files it has found.

---

We are working on addressing all of these cases and improving the behavior of `gopls` in the unsupported cases. All of these cases will be supported once `gopls` reaches `v1.0.0`. 

We understand it may be inconvenient to change your typical workflow to accommodate frequent changes in `gopls`. In this case, it may be easier to stick with a version of `gopls` that works for you (`gopls/v0.2.2`, for instance), or if you are using GOPATH, `gopls` may not be the best tool to use until it reaches `v1.0.0`. 

If you have additional use cases that are not mentioned above, please comment below.
",1,x tools gopls  defining the workspace root    gopls  supports both module and gopath modes  however  we need to define a scope in which language features like references  rename  and implementation should operate  the following is subject to  and will likely  change     for now  we have the following cases         module mode         supported    open workspace at the module root  directory containing the  go mod  file   the scope is the entire module     open a subdirectory of a module  the scope is the subdirectory that has been opened          unsupported    open a directory that contains a module in a subdirectory   gopls  will not work in this case         gopath mode         supported    open a directory inside of your gopath  the scope is the open directory          at your own risk    open your entire gopath  the workspace scope will be your entire  gopath   note that this will cause  gopls  to load your entire gopath  if your gopath is large  this will take a long time and cause  gopls  to be very slow     to work around this case  you can create a new gopath that contains only the packages you want to work on          unsupported    open a directory containing your gopath  similar to the case above  this will cause  gopls  to treat your entire gopath as the workspace scope  it will be very slow to start because it will try to find all of the go files in the directory you have opened  it will then load all of the files it has found            we are working on addressing all of these cases and improving the behavior of  gopls  in the unsupported cases  all of these cases will be supported once  gopls  reaches              we understand it may be inconvenient to change your typical workflow to accommodate frequent changes in  gopls   in this case  it may be easier to stick with a version of  gopls  that works for you   gopls         for instance   or if you are using gopath   gopls  may not be the best tool to use until it reaches              if you have additional use cases that are not mentioned above  please comment below   ,1
43714,7059294876.0,IssuesEvent,2018-01-05 00:37:55,golang/go,https://api.github.com/repos/golang/go,closed,net/http: document how to create client CONNECT requests,Documentation NeedsFix,"### What version of Go are you using (`go version`)?
Go1.9

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
windows/amd64

### What did you do?

This error is reproducible at https://play.golang.org/p/9m7rlnqsTm 

I attempted to create a new HTTP request with http.NewRequest() using a URI that starts with a number, with no protocol, that also contains a port:
```_, err = http.NewRequest(http.MethodConnect, ""0.docs.google.com:443"", nil)```

### What did you expect to see?
The request should be created with no error.

### What did you see instead?
I get the error ""parse <URL>: first path segment in URL cannot contain colon""

",1.0,"net/http: document how to create client CONNECT requests - ### What version of Go are you using (`go version`)?
Go1.9

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
windows/amd64

### What did you do?

This error is reproducible at https://play.golang.org/p/9m7rlnqsTm 

I attempted to create a new HTTP request with http.NewRequest() using a URI that starts with a number, with no protocol, that also contains a port:
```_, err = http.NewRequest(http.MethodConnect, ""0.docs.google.com:443"", nil)```

### What did you expect to see?
The request should be created with no error.

### What did you see instead?
I get the error ""parse <URL>: first path segment in URL cannot contain colon""

",1,net http  document how to create client connect requests       what version of go are you using   go version                does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env     windows          what did you do     this error is reproducible at       i attempted to create a new http request with http newrequest   using a uri that starts with a number  with no protocol  that also contains a port         err   http newrequest http methodconnect     docs google com     nil            what did you expect to see   the request should be created with no error         what did you see instead   i get the error  parse    first path segment in url cannot contain colon     ,1
79555,10131824854.0,IssuesEvent,2019-08-01 20:34:19,golang/go,https://api.github.com/repos/golang/go,closed,doc: summarize net/http noteworthy improvements for Go1.13,Documentation,This issue is a placeholder for us to comb through the net/http improvements such as https://github.com/golang/go/issues/30377#issuecomment-469959340 from @vancluever  in which we now use SendFile/ReadFrom for Transport.Body if possible,1.0,doc: summarize net/http noteworthy improvements for Go1.13 - This issue is a placeholder for us to comb through the net/http improvements such as https://github.com/golang/go/issues/30377#issuecomment-469959340 from @vancluever  in which we now use SendFile/ReadFrom for Transport.Body if possible,1,doc  summarize net http noteworthy improvements for       this issue is a placeholder for us to comb through the net http improvements such as   from  vancluever  in which we now use sendfile readfrom for transport body if possible,1
14380,3832979550.0,IssuesEvent,2016-04-01 00:03:31,golang/go,https://api.github.com/repos/golang/go,closed,tour: Math.PI is no longer an export of the Math package,Documentation,"Context: http://127.0.0.1:3999/basics/3

Change the title above to describe your issue and add your feedback here, including code if necessary",1.0,"tour: Math.PI is no longer an export of the Math package - Context: http://127.0.0.1:3999/basics/3

Change the title above to describe your issue and add your feedback here, including code if necessary",1,tour  math pi is no longer an export of the math package   context       change the title above to describe your issue and add your feedback here  including code if necessary,1
86702,10514759996.0,IssuesEvent,2019-09-28 03:23:42,golang/go,https://api.github.com/repos/golang/go,closed,regexp: add examples for all methods on regex.Regexp,Documentation NeedsFix,"Something I've been wanting to do for a while is provide complete example coverage for methods defined on regexp.Regex. There are 36 methods, 11 of which have examples. Unless this isn't desired, I'd like to finish the other 25.


",1.0,"regexp: add examples for all methods on regex.Regexp - Something I've been wanting to do for a while is provide complete example coverage for methods defined on regexp.Regex. There are 36 methods, 11 of which have examples. Unless this isn't desired, I'd like to finish the other 25.


",1,regexp  add examples for all methods on regex regexp   something i ve been wanting to do for a while is provide complete example coverage for methods defined on regexp regex  there are   methods    of which have examples  unless this isn t desired  i d like to finish the other         ,1
627166,19898068137.0,IssuesEvent,2022-01-25 02:56:03,apcountryman/picolibrary-microchip-megaavr0,https://api.github.com/repos/apcountryman/picolibrary-microchip-megaavr0,closed,Add protected register,priority-normal status-awaiting_review type-feature,"Add protected register (`::picolibrary::Microchip::megaAVR0::Protected_Register`).
- [x] The `Protected_Register` class should be defined in the `include/picolibrary/microchip/megaavr0/register.h`/`source/picolibrary/microchip/megaavr0/register.cc` header/source file pair
- [x] The `Protected_Register` class should have the following template arguments:
    - [x] `typename T`: The protected register's underlying integral type (must be `std::uint8_t`)
- [x] The `Protected_Register` class should have the following member type aliases:
    - [x] `using Type = T;`: The protected register's underlying integral type
- [x] The `Protected_Register` class should support the following operations:
    - [x] `operator Type() const noexcept;`: Read the register
    - [x] `auto operator=( Type expression ) noexcept -> Protected_Register &;`
    - [x] `auto operaotr&=( Type expression ) noexcept -> Protected_Register &;`
    - [x] `auto operaotr|=( Type expression ) noexcept -> Protected_Register &;`
    - [x] `auto operaotr^=( Type expression ) noexcept -> Protected_Register &;`",1.0,"Add protected register - Add protected register (`::picolibrary::Microchip::megaAVR0::Protected_Register`).
- [x] The `Protected_Register` class should be defined in the `include/picolibrary/microchip/megaavr0/register.h`/`source/picolibrary/microchip/megaavr0/register.cc` header/source file pair
- [x] The `Protected_Register` class should have the following template arguments:
    - [x] `typename T`: The protected register's underlying integral type (must be `std::uint8_t`)
- [x] The `Protected_Register` class should have the following member type aliases:
    - [x] `using Type = T;`: The protected register's underlying integral type
- [x] The `Protected_Register` class should support the following operations:
    - [x] `operator Type() const noexcept;`: Read the register
    - [x] `auto operator=( Type expression ) noexcept -> Protected_Register &;`
    - [x] `auto operaotr&=( Type expression ) noexcept -> Protected_Register &;`
    - [x] `auto operaotr|=( Type expression ) noexcept -> Protected_Register &;`
    - [x] `auto operaotr^=( Type expression ) noexcept -> Protected_Register &;`",0,add protected register   add protected register     picolibrary  microchip     protected register         the  protected register  class should be defined in the  include picolibrary microchip   register h   source picolibrary microchip   register cc  header source file pair      the  protected register  class should have the following template arguments            typename t   the protected register s underlying integral type  must be  std    t        the  protected register  class should have the following member type aliases            using type   t    the protected register s underlying integral type      the  protected register  class should support the following operations            operator type   const noexcept    read the register           auto operator   type expression   noexcept    protected register               auto operaotr    type expression   noexcept    protected register               auto operaotr    type expression   noexcept    protected register               auto operaotr    type expression   noexcept    protected register    ,0
8792,6655888941.0,IssuesEvent,2017-09-29 18:17:50,SAP/chevrotain,https://api.github.com/repos/SAP/chevrotain,closed,Investigate Faster lookaheads functions using runtime code generation.,Performance,"* Attempt to generate switch case statements instead of using object maps / loops to find the alternatives, basically generate  a DFA.
* Must be possible to disable this as code generation at runtime does not work in some security contexts.
* Disabling this must also be possible indirectly (I.E via some env variable) to support the transitive dependency use case.",True,"Investigate Faster lookaheads functions using runtime code generation. - * Attempt to generate switch case statements instead of using object maps / loops to find the alternatives, basically generate  a DFA.
* Must be possible to disable this as code generation at runtime does not work in some security contexts.
* Disabling this must also be possible indirectly (I.E via some env variable) to support the transitive dependency use case.",0,investigate faster lookaheads functions using runtime code generation      attempt to generate switch case statements instead of using object maps   loops to find the alternatives  basically generate  a dfa     must be possible to disable this as code generation at runtime does not work in some security contexts     disabling this must also be possible indirectly  i e via some env variable  to support the transitive dependency use case ,0
271416,20672534691.0,IssuesEvent,2022-03-10 04:56:26,golang/go,https://api.github.com/repos/golang/go,closed,spec: make(T) compiles even though T has no core type,Documentation NeedsFix,"From a [golang-nuts post](https://groups.google.com/g/golang-nuts/c/JIZuVoUNAlE/m/Ja0SHiS0AgAJ):

```Go
package main

func main() {}

type C interface {
        map[int]int
        M()
}
       
func foo[T C]() {
        var _ = make(T)
}
```
This program compiles without error even though `T` doesn't have a core type (the typeset of `C` is empty).

This may require an update to the definition of core types or perhaps some other accommodation in the spec.",1.0,"spec: make(T) compiles even though T has no core type - From a [golang-nuts post](https://groups.google.com/g/golang-nuts/c/JIZuVoUNAlE/m/Ja0SHiS0AgAJ):

```Go
package main

func main() {}

type C interface {
        map[int]int
        M()
}
       
func foo[T C]() {
        var _ = make(T)
}
```
This program compiles without error even though `T` doesn't have a core type (the typeset of `C` is empty).

This may require an update to the definition of core types or perhaps some other accommodation in the spec.",1,spec  make t  compiles even though t has no core type   from a           go  package main    func main         type c interface            map int          m                func foo               var     make t           this program compiles without error even though  t  doesn t have a core type  the typeset of  c  is empty      this may require an update to the definition of core types or perhaps some other accommodation in the spec ,1
6649,3038836882.0,IssuesEvent,2015-08-07 02:20:41,golang/go,https://api.github.com/repos/golang/go,closed,cmd/compile: document whether c-archive is supported on 386,Documentation,"i use ""GOARCH=386 go build -buildmode=c-archive"",it shows "": no buildable Go source files in""
if use ""GOARCH=386 go build -buildmode=c-shared"", it shows ""-buildmode=c-shared not supported on linux/386""",1.0,"cmd/compile: document whether c-archive is supported on 386 - i use ""GOARCH=386 go build -buildmode=c-archive"",it shows "": no buildable Go source files in""
if use ""GOARCH=386 go build -buildmode=c-shared"", it shows ""-buildmode=c-shared not supported on linux/386""",1,cmd compile  document whether c archive is supported on     i use  goarch   go build  buildmode c archive  it shows    no buildable go source files in   if use  goarch   go build  buildmode c shared   it shows   buildmode c shared not supported on linux   ,1
11245,16724780598.0,IssuesEvent,2021-06-10 11:42:33,renovatebot/renovate,https://api.github.com/repos/renovatebot/renovate,closed,Batched updates for noise reduction,priority-3-normal status:requirements type:feature,"Although Renovate supports schedules, grouping and automerging to reduce ""noise"", the result is still too noisy for many people who watch renovated projects. Of course, most of that annoyance is because of *GitHub Notifications*, which GitHub could improve greatly by letting you mute certain conditions.. but we need to work with what we have.

One idea I have had is to improve the way Renovate does scheduled upgrades.

Today, the way weekly updates might work is either:

1. Keep dependencies mostly separate (e.g. other than predefined monorepos) and then you end up with maybe 10+ PRs all at once at the scheduled time. Then you have the choice of either (a) merging them all independently and hoping none conflicted with each other, or (b) merging, waiting (for rebase), merging, waiting, etc. If you have lock files then you may have no choice but to wait for PR regeneration after each merge.

2. Aggressively group together dependencies for the weekly update. In this case if one update is bad, the PR fails tests and probably nothing will get upgraded. And then what? Work out manually which is bad and manually fix the branch to try to pass? i.e. this is great when it works/passes and ugly when it does not.

I am thinking of a third option:

3a) Renovate creates one branch per upgrade (or group) like in option 1 above, but does not create the PR. For most people, this would be ""silent"" or quiet enough because no GitHub notification as no PR
3b) Once a week (or actually when scheduled..), Renovate bundles together *all* passing updates into one branch/PR.

When this works well, it means you get one PR per week like in (2) above, with hopefully much reduced chance that this combined PR fails.

Two main failure cases to consider:

i) If an upgrade in a branch fails during the week, what to do then? e.g. PR the failed upgrade immediately for someone to look at? Or ignore the failure and wait x days to see if a fix is issued, i.e. only raising a failed PR if the failed upgrade doesn't appear to be getting fixed, or in case it needs a fix in the current repo?

ii) If the combined weekly branch/PR fails testing. i.e. the individual branches had passed, but when combined they have failed - either because of a conflict between them or perhaps a transient CI problem. Right now I'm thinking that the only option is to still raise the PR and let a human intervene.",1.0,"Batched updates for noise reduction - Although Renovate supports schedules, grouping and automerging to reduce ""noise"", the result is still too noisy for many people who watch renovated projects. Of course, most of that annoyance is because of *GitHub Notifications*, which GitHub could improve greatly by letting you mute certain conditions.. but we need to work with what we have.

One idea I have had is to improve the way Renovate does scheduled upgrades.

Today, the way weekly updates might work is either:

1. Keep dependencies mostly separate (e.g. other than predefined monorepos) and then you end up with maybe 10+ PRs all at once at the scheduled time. Then you have the choice of either (a) merging them all independently and hoping none conflicted with each other, or (b) merging, waiting (for rebase), merging, waiting, etc. If you have lock files then you may have no choice but to wait for PR regeneration after each merge.

2. Aggressively group together dependencies for the weekly update. In this case if one update is bad, the PR fails tests and probably nothing will get upgraded. And then what? Work out manually which is bad and manually fix the branch to try to pass? i.e. this is great when it works/passes and ugly when it does not.

I am thinking of a third option:

3a) Renovate creates one branch per upgrade (or group) like in option 1 above, but does not create the PR. For most people, this would be ""silent"" or quiet enough because no GitHub notification as no PR
3b) Once a week (or actually when scheduled..), Renovate bundles together *all* passing updates into one branch/PR.

When this works well, it means you get one PR per week like in (2) above, with hopefully much reduced chance that this combined PR fails.

Two main failure cases to consider:

i) If an upgrade in a branch fails during the week, what to do then? e.g. PR the failed upgrade immediately for someone to look at? Or ignore the failure and wait x days to see if a fix is issued, i.e. only raising a failed PR if the failed upgrade doesn't appear to be getting fixed, or in case it needs a fix in the current repo?

ii) If the combined weekly branch/PR fails testing. i.e. the individual branches had passed, but when combined they have failed - either because of a conflict between them or perhaps a transient CI problem. Right now I'm thinking that the only option is to still raise the PR and let a human intervene.",0,batched updates for noise reduction   although renovate supports schedules  grouping and automerging to reduce  noise   the result is still too noisy for many people who watch renovated projects  of course  most of that annoyance is because of  github notifications   which github could improve greatly by letting you mute certain conditions   but we need to work with what we have     one idea i have had is to improve the way renovate does scheduled upgrades     today  the way weekly updates might work is either        keep dependencies mostly separate  e g  other than predefined monorepos  and then you end up with maybe    prs all at once at the scheduled time  then you have the choice of either  a  merging them all independently and hoping none conflicted with each other  or  b  merging  waiting  for rebase   merging  waiting  etc  if you have lock files then you may have no choice but to wait for pr regeneration after each merge        aggressively group together dependencies for the weekly update  in this case if one update is bad  the pr fails tests and probably nothing will get upgraded  and then what  work out manually which is bad and manually fix the branch to try to pass  i e  this is great when it works passes and ugly when it does not     i am thinking of a third option        renovate creates one branch per upgrade  or group  like in option   above  but does not create the pr  for most people  this would be  silent  or quiet enough because no github notification as no pr     once a week  or actually when scheduled     renovate bundles together  all  passing updates into one branch pr     when this works well  it means you get one pr per week like in     above  with hopefully much reduced chance that this combined pr fails     two main failure cases to consider     i  if an upgrade in a branch fails during the week  what to do then  e g  pr the failed upgrade immediately for someone to look at  or ignore the failure and wait x days to see if a fix is issued  i e  only raising a failed pr if the failed upgrade doesn t appear to be getting fixed  or in case it needs a fix in the current repo     ii  if the combined weekly branch pr fails testing  i e  the individual branches had passed  but when combined they have failed   either because of a conflict between them or perhaps a transient ci problem  right now i m thinking that the only option is to still raise the pr and let a human intervene ,0
64186,12423075997.0,IssuesEvent,2020-05-24 02:52:24,bylapidist/components,https://api.github.com/repos/bylapidist/components,closed,"Fix ""similar-code"" issue in src/components/image/index.tsx",codeclimate,"Similar blocks of code found in 3 locations. Consider refactoring.

https://codeclimate.com/github/bylapidist/components/src/components/image/index.tsx#issue_5ec9b3d0cfdf110001000052",1.0,"Fix ""similar-code"" issue in src/components/image/index.tsx - Similar blocks of code found in 3 locations. Consider refactoring.

https://codeclimate.com/github/bylapidist/components/src/components/image/index.tsx#issue_5ec9b3d0cfdf110001000052",0,fix  similar code  issue in src components image index tsx   similar blocks of code found in   locations  consider refactoring    ,0
40875,10587289645.0,IssuesEvent,2019-10-08 21:43:48,scality/metalk8s,https://api.github.com/repos/scality/metalk8s,closed,Build may fail due to Docker registry being unavailable,bug build ci easy flakiness moonshot,"**Component**:

'ci', 'build'

**What happened**:

When building the ISO in this build https://eve.devsca.com/github/scality/metalk8s/#/builders/1/builds/12383, we faced the following issue:
```
.  PULL IMG     kube-controller-manager:v1.14.6
.  PULL IMG     kube-proxy:v1.14.6
.  PULL IMG     kube-scheduler:v1.14.6
.  PULL IMG     nginx-ingress-defaultbackend-amd64:1.5
.  PULL IMG     grafana:6.3.5
.  PULL IMG     nginx-ingress-controller:0.25.0
.  PULL IMG     calico-node:v3.8.2
time=""2019-10-04T07:29:50Z"" level=fatal msg=""Error initializing source docker://grafana/grafana:6.3.5: Get https://registry-1.docker.io/v2/grafana/grafana/manifests/6.3.5: EOF"" 
TaskFailed - taskid:_image_pull:grafana
Command failed: '['skopeo', '--override-os', 'linux', '--insecure-policy', 'copy', '--format', 'v2s2', 'docker://docker.io/grafana/grafana:6.3.5', 'dir:/home/eve/workspace/kube_pod-prod-metalk8s-backend-0/build/_build/root/images/grafana/6.3.5']' returned 1
```

**What was expected**:

We expect the Docker registry to be available and the ISO being built as expected.

**Steps to reproduce**

Not sure since it's flaky.

**Resolution proposal** (optional):

As discussed with @bertranddemiddelaer we could use the proxy cache from the pod worker by running something like this from the worker to setup the vars and certs for the proxy cache:
```
curl -s http://proxy-cache/setup.sh | sudo sh && . /usr/local/bin/use_scality_proxy_cache
```",1.0,"Build may fail due to Docker registry being unavailable - **Component**:

'ci', 'build'

**What happened**:

When building the ISO in this build https://eve.devsca.com/github/scality/metalk8s/#/builders/1/builds/12383, we faced the following issue:
```
.  PULL IMG     kube-controller-manager:v1.14.6
.  PULL IMG     kube-proxy:v1.14.6
.  PULL IMG     kube-scheduler:v1.14.6
.  PULL IMG     nginx-ingress-defaultbackend-amd64:1.5
.  PULL IMG     grafana:6.3.5
.  PULL IMG     nginx-ingress-controller:0.25.0
.  PULL IMG     calico-node:v3.8.2
time=""2019-10-04T07:29:50Z"" level=fatal msg=""Error initializing source docker://grafana/grafana:6.3.5: Get https://registry-1.docker.io/v2/grafana/grafana/manifests/6.3.5: EOF"" 
TaskFailed - taskid:_image_pull:grafana
Command failed: '['skopeo', '--override-os', 'linux', '--insecure-policy', 'copy', '--format', 'v2s2', 'docker://docker.io/grafana/grafana:6.3.5', 'dir:/home/eve/workspace/kube_pod-prod-metalk8s-backend-0/build/_build/root/images/grafana/6.3.5']' returned 1
```

**What was expected**:

We expect the Docker registry to be available and the ISO being built as expected.

**Steps to reproduce**

Not sure since it's flaky.

**Resolution proposal** (optional):

As discussed with @bertranddemiddelaer we could use the proxy cache from the pod worker by running something like this from the worker to setup the vars and certs for the proxy cache:
```
curl -s http://proxy-cache/setup.sh | sudo sh && . /usr/local/bin/use_scality_proxy_cache
```",0,build may fail due to docker registry being unavailable     component        ci    build       what happened       when building the iso in this build   we faced the following issue           pull img     kube controller manager           pull img     kube proxy           pull img     kube scheduler           pull img     nginx ingress defaultbackend           pull img     grafana           pull img     nginx ingress controller           pull img     calico node        time             level fatal msg  error initializing source docker   grafana grafana        get   eof    taskfailed   taskid  image pull grafana  command failed      returned             what was expected       we expect the docker registry to be available and the iso being built as expected       steps to reproduce      not sure since it s flaky       resolution proposal    optional      as discussed with  bertranddemiddelaer we could use the proxy cache from the pod worker by running something like this from the worker to setup the vars and certs for the proxy cache        curl  s     sudo sh       usr local bin use scality proxy cache     ,0
11914,3548690009.0,IssuesEvent,2016-01-20 15:23:57,golang/go,https://api.github.com/repos/golang/go,closed,"wiki: Minor typo on ""Writing Web Applications""",Documentation,"On https://golang.org/doc/articles/wiki/:

> With this web server running, a visit to `http://localhost:8080/view/test` should show a page titled `""test""` containing the words ""Hello world"".

This should be `http://localhost:8080/view/TestPage` and `""TestPage""` instead of `test`

",1.0,"wiki: Minor typo on ""Writing Web Applications"" - On https://golang.org/doc/articles/wiki/:

> With this web server running, a visit to `http://localhost:8080/view/test` should show a page titled `""test""` containing the words ""Hello world"".

This should be `http://localhost:8080/view/TestPage` and `""TestPage""` instead of `test`

",1,wiki  minor typo on  writing web applications    on        with this web server running  a visit to    should show a page titled   test   containing the words  hello world      this should be    and   testpage   instead of  test     ,1
9538,3292672628.0,IssuesEvent,2015-10-30 15:37:49,golang/go,https://api.github.com/repos/golang/go,opened,testing: document that T and B are safe for concurrent calls,Documentation,"We never documented that t.Errorf and friends are safe to call concurrently from different goroutines.

This came up in review, with unnecessary locking around calling methods on t.
",1.0,"testing: document that T and B are safe for concurrent calls - We never documented that t.Errorf and friends are safe to call concurrently from different goroutines.

This came up in review, with unnecessary locking around calling methods on t.
",1,testing  document that t and b are safe for concurrent calls   we never documented that t errorf and friends are safe to call concurrently from different goroutines     this came up in review  with unnecessary locking around calling methods on t   ,1
127398,27035999993.0,IssuesEvent,2023-02-12 19:38:41,amusecode/amuse,https://api.github.com/repos/amusecode/amuse,closed,Local user artefacts in Makefiles,community_code cosmetic stale,"**Describe the bug**
There are a number of Makefiles which include local paths to binaries, typically in `/home/<username>/` or `/Users/<username>/`. These do not seem to affect anything, but could perhaps be cleaned up.

**Examples**
Two examples in the [simplex Makefiles](https://github.com/amusecode/amuse/blob/10d8d69f2968b6af2ba9c8d0acd73a39a65b808f/src/amuse/community/simplex/Makefile)
https://github.com/amusecode/amuse/blob/10d8d69f2968b6af2ba9c8d0acd73a39a65b808f/src/amuse/community/simplex/Makefile#L26

https://github.com/amusecode/amuse/blob/10d8d69f2968b6af2ba9c8d0acd73a39a65b808f/src/amuse/community/simplex/Makefile#L42

Three other examples match these patterns in [capreole](https://github.com/amusecode/amuse/blob/10d8d69f2968b6af2ba9c8d0acd73a39a65b808f/src/amuse/community/capreole/Makefile) and fi ([makefile](https://github.com/amusecode/amuse/blob/b7fe00fb8cb235ecee3f716fe967c3790a935c22/src/amuse/community/fi/src/Makefile) and [fixedhalo.f90](https://github.com/amusecode/amuse/blob/b7fe00fb8cb235ecee3f716fe967c3790a935c22/src/amuse/community/fi/src/fixedhalo.f90)).",1.0,"Local user artefacts in Makefiles - **Describe the bug**
There are a number of Makefiles which include local paths to binaries, typically in `/home/<username>/` or `/Users/<username>/`. These do not seem to affect anything, but could perhaps be cleaned up.

**Examples**
Two examples in the [simplex Makefiles](https://github.com/amusecode/amuse/blob/10d8d69f2968b6af2ba9c8d0acd73a39a65b808f/src/amuse/community/simplex/Makefile)
https://github.com/amusecode/amuse/blob/10d8d69f2968b6af2ba9c8d0acd73a39a65b808f/src/amuse/community/simplex/Makefile#L26

https://github.com/amusecode/amuse/blob/10d8d69f2968b6af2ba9c8d0acd73a39a65b808f/src/amuse/community/simplex/Makefile#L42

Three other examples match these patterns in [capreole](https://github.com/amusecode/amuse/blob/10d8d69f2968b6af2ba9c8d0acd73a39a65b808f/src/amuse/community/capreole/Makefile) and fi ([makefile](https://github.com/amusecode/amuse/blob/b7fe00fb8cb235ecee3f716fe967c3790a935c22/src/amuse/community/fi/src/Makefile) and [fixedhalo.f90](https://github.com/amusecode/amuse/blob/b7fe00fb8cb235ecee3f716fe967c3790a935c22/src/amuse/community/fi/src/fixedhalo.f90)).",0,local user artefacts in makefiles     describe the bug    there are a number of makefiles which include local paths to binaries  typically in   home     or   users      these do not seem to affect anything  but could perhaps be cleaned up       examples    two examples in the                three other examples match these patterns in     and fi      and    ,0
262461,19804440232.0,IssuesEvent,2022-01-19 04:00:48,golang/go,https://api.github.com/repos/golang/go,closed,spec: shift string(1 << s) should be invalid,Documentation,"```Go
package p
var s uint
var _ = string(1 << s)
```
is not accepted by the compiler:
```
bug.go:3:15: invalid operation: 1 << s (shift of type string)
```
Per the spec (https://golang.org/ref/spec#Constant_expressions):
""If the left operand of a non-constant shift expression is an untyped constant, it is first implicitly converted to the type it would assume if the shift expression were replaced by its left operand alone.""

In this case, the left operand would be converted to `int` (not string). This is different from cases such as, say `float64(1 << s)` where `1` is implicitly converted to `1.0` because it can be done without loss of precision. It seems a bit far-fetched to claim that a `1` can be converted to a string without loss of precision. (That said, the spec is notoriously difficult to decipher with respect to shifts and implicit conversions.)

As an aside, there's still #3939 which is proposing to prohibit `string(int_value)`, and `go vet` is checking for this. So we're not permitting a new category of programs by making `string(1 << s)` valid.

Both `go/types` and `types2` accept this code.

The test `$GOROOT/test/fixedbugs/bug193.go` assumes that this code should fail.
",1.0,"spec: shift string(1 << s) should be invalid - ```Go
package p
var s uint
var _ = string(1 << s)
```
is not accepted by the compiler:
```
bug.go:3:15: invalid operation: 1 << s (shift of type string)
```
Per the spec (https://golang.org/ref/spec#Constant_expressions):
""If the left operand of a non-constant shift expression is an untyped constant, it is first implicitly converted to the type it would assume if the shift expression were replaced by its left operand alone.""

In this case, the left operand would be converted to `int` (not string). This is different from cases such as, say `float64(1 << s)` where `1` is implicitly converted to `1.0` because it can be done without loss of precision. It seems a bit far-fetched to claim that a `1` can be converted to a string without loss of precision. (That said, the spec is notoriously difficult to decipher with respect to shifts and implicit conversions.)

As an aside, there's still #3939 which is proposing to prohibit `string(int_value)`, and `go vet` is checking for this. So we're not permitting a new category of programs by making `string(1 << s)` valid.

Both `go/types` and `types2` accept this code.

The test `$GOROOT/test/fixedbugs/bug193.go` assumes that this code should fail.
",1,spec  shift string      s  should be invalid      go  package p  var s uint  var     string      s        is not accepted by the compiler        bug go      invalid operation       s  shift of type string        per the spec      if the left operand of a non constant shift expression is an untyped constant  it is first implicitly converted to the type it would assume if the shift expression were replaced by its left operand alone      in this case  the left operand would be converted to  int   not string   this is different from cases such as  say         s   where     is implicitly converted to       because it can be done without loss of precision  it seems a bit far fetched to claim that a     can be converted to a string without loss of precision   that said  the spec is notoriously difficult to decipher with respect to shifts and implicit conversions      as an aside  there s still    which is proposing to prohibit  string int value    and  go vet  is checking for this  so we re not permitting a new category of programs by making  string      s   valid     both  go types  and     accept this code     the test   goroot test fixedbugs   go  assumes that this code should fail   ,1
16514,4056590753.0,IssuesEvent,2016-05-24 19:08:18,golang/go,https://api.github.com/repos/golang/go,closed,math/rand: document which bits of seed are used,Documentation,"1. What version of Go are you using (`go version`)?
1.6.2 (1.6.0 has the same issue)

2. What operating system and processor architecture are you using (`go env`)?
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
Ubuntu 14.04.02 Trusty

3. What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
https://play.golang.org/p/JSKCIMotEE

4. What did you expect to see?
A different output string, and a different sequence of integers in the array.

5. What did you see instead?
The exact same output string, and the exact same sequence of integers in the array.

Basically using a different seed (especially one that's numerically quite different) should probably generate a different random sequence. It's very possible that that's just a limitation of the algorithm and that's life but just in case this is actually a bug I wanted to file it so at least someone with more knowledge than me could confirm it either way.",1.0,"math/rand: document which bits of seed are used - 1. What version of Go are you using (`go version`)?
1.6.2 (1.6.0 has the same issue)

2. What operating system and processor architecture are you using (`go env`)?
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
Ubuntu 14.04.02 Trusty

3. What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
https://play.golang.org/p/JSKCIMotEE

4. What did you expect to see?
A different output string, and a different sequence of integers in the array.

5. What did you see instead?
The exact same output string, and the exact same sequence of integers in the array.

Basically using a different seed (especially one that's numerically quite different) should probably generate a different random sequence. It's very possible that that's just a limitation of the algorithm and that's life but just in case this is actually a bug I wanted to file it so at least someone with more knowledge than me could confirm it either way.",1,math rand  document which bits of seed are used      what version of go are you using   go version                  has the same issue        what operating system and processor architecture are you using   go env     gohostarch      gohostos  linux   ubuntu       trusty       what did you do   if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best           what did you expect to see   a different output string  and a different sequence of integers in the array        what did you see instead   the exact same output string  and the exact same sequence of integers in the array     basically using a different seed  especially one that s numerically quite different  should probably generate a different random sequence  it s very possible that that s just a limitation of the algorithm and that s life but just in case this is actually a bug i wanted to file it so at least someone with more knowledge than me could confirm it either way ,1
22169,4777809915.0,IssuesEvent,2016-10-27 17:21:30,golang/go,https://api.github.com/repos/golang/go,closed,net/rpc: method receiver doesn't have to be marshalable by encoding/gob contrary to documentation,Documentation NeedsFix,"Hey!

In the documentation of [net/rpc](https://github.com/golang/go/blob/master/src/net/rpc/server.go#L24), it is said that the method receiver `T` needs to be marshalable with encoding/gob. From my understanding, this is not the case, only the two arguments need to be.",1.0,"net/rpc: method receiver doesn't have to be marshalable by encoding/gob contrary to documentation - Hey!

In the documentation of [net/rpc](https://github.com/golang/go/blob/master/src/net/rpc/server.go#L24), it is said that the method receiver `T` needs to be marshalable with encoding/gob. From my understanding, this is not the case, only the two arguments need to be.",1,net rpc  method receiver doesn t have to be marshalable by encoding gob contrary to documentation   hey     in the documentation of     it is said that the method receiver  t  needs to be marshalable with encoding gob  from my understanding  this is not the case  only the two arguments need to be ,1
14480,8600144002.0,IssuesEvent,2018-11-16 06:12:15,cruzdb/zlog,https://api.github.com/repos/cruzdb/zlog,closed,optimistically extend view for next stripe,feature performance,"we can add a flag to the stripe that is set the first time a position from the stripe is mapped. then when that flag is set the first time for the stripe, we can dispatch an async worker to extend. be careful to carry this flag forward when deserializing views since this isnt't going to be in the serialized version. maybe its not actually necessary since we'll also say ""if this is the first time mapping && the next  stripe isn't present...""

currently a view is extended when a client discovers that no mapping exists for a particular position. the view can be extended optimistically, by creating the next view when the current view is, say, half full.

this is a performance improvement since without it some clients will encounter a big latency hit as the view is created and updated in the fast path.",True,"optimistically extend view for next stripe - we can add a flag to the stripe that is set the first time a position from the stripe is mapped. then when that flag is set the first time for the stripe, we can dispatch an async worker to extend. be careful to carry this flag forward when deserializing views since this isnt't going to be in the serialized version. maybe its not actually necessary since we'll also say ""if this is the first time mapping && the next  stripe isn't present...""

currently a view is extended when a client discovers that no mapping exists for a particular position. the view can be extended optimistically, by creating the next view when the current view is, say, half full.

this is a performance improvement since without it some clients will encounter a big latency hit as the view is created and updated in the fast path.",0,optimistically extend view for next stripe   we can add a flag to the stripe that is set the first time a position from the stripe is mapped  then when that flag is set the first time for the stripe  we can dispatch an async worker to extend  be careful to carry this flag forward when deserializing views since this isnt t going to be in the serialized version  maybe its not actually necessary since we ll also say  if this is the first time mapping    the next  stripe isn t present        currently a view is extended when a client discovers that no mapping exists for a particular position  the view can be extended optimistically  by creating the next view when the current view is  say  half full     this is a performance improvement since without it some clients will encounter a big latency hit as the view is created and updated in the fast path ,0
73590,9672183453.0,IssuesEvent,2019-05-22 02:18:44,golang/go,https://api.github.com/repos/golang/go,closed,errors: documentation for errors.Unwrap mentions non existing interface Wrapper,Documentation NeedsFix release-blocker,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version devel +1ab063ce53 Fri May 17 22:32:30 2019 +0000 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/johan/.cache/go-build""
GOENV=""/home/johan/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/johan/go""
GOPROXY=""direct""
GOROOT=""/home/johan/go/go""
GOSUMDB=""off""
GOTMPDIR=""""
GOTOOLDIR=""/home/johan/go/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/johan/go/go/src/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build709384782=/tmp/go-build -gno-record-gcc-switches""

</pre></details>

### What did you do?

Check documentation for errors package in standard library.

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

### What did you expect to see?

Correct documentation for errors.Unwrap, similar to the Is and As functions.

### What did you see instead?

The documentation for the Unwrap function mentions a non existing interface called Wrapper. This interface has was removed by revert in commit 3e2c522d5c712fa2b1d18a101272abefc7dcb074

Also it's rather unclear how one would go about actually wrap an error. There is the Unwrap function with a short comment (that mentions the non existing Wrapper interface), but nothing much else that provide more context. How are errors chained? Up to 3pp library support?
",1.0,"errors: documentation for errors.Unwrap mentions non existing interface Wrapper - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version devel +1ab063ce53 Fri May 17 22:32:30 2019 +0000 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/johan/.cache/go-build""
GOENV=""/home/johan/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/johan/go""
GOPROXY=""direct""
GOROOT=""/home/johan/go/go""
GOSUMDB=""off""
GOTMPDIR=""""
GOTOOLDIR=""/home/johan/go/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/johan/go/go/src/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build709384782=/tmp/go-build -gno-record-gcc-switches""

</pre></details>

### What did you do?

Check documentation for errors package in standard library.

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

### What did you expect to see?

Correct documentation for errors.Unwrap, similar to the Is and As functions.

### What did you see instead?

The documentation for the Unwrap function mentions a non existing interface called Wrapper. This interface has was removed by revert in commit 3e2c522d5c712fa2b1d18a101272abefc7dcb074

Also it's rather unclear how one would go about actually wrap an error. There is the Unwrap function with a short comment (that mentions the non existing Wrapper interface), but nothing much else that provide more context. How are errors chained? Up to 3pp library support?
",1,errors  documentation for errors unwrap mentions non existing interface wrapper            what version of go are you using   go version            go version  go version devel    fri may              linux             does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env          go env  output       go env  goarch      gobin     gocache   home johan  cache go build   goenv   home johan  config go env   goexe     goflags     gohostarch      gohostos  linux   gonoproxy     gonosumdb     goos  linux   gopath   home johan go   goproxy  direct   goroot   home johan go go   gosumdb  off   gotmpdir     gotooldir   home johan go go pkg tool linux     gccgo  gccgo   ar  ar   cc  gcc   cxx  g     cgo enabled      gomod   home johan go go src go mod   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches               what did you do     check documentation for errors package in standard library           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best              what did you expect to see     correct documentation for errors unwrap  similar to the is and as functions         what did you see instead     the documentation for the unwrap function mentions a non existing interface called wrapper  this interface has was removed by revert in commit      also it s rather unclear how one would go about actually wrap an error  there is the unwrap function with a short comment  that mentions the non existing wrapper interface   but nothing much else that provide more context  how are errors chained  up to   library support   ,1
433754,30348517251.0,IssuesEvent,2023-07-11 17:06:49,golang/go,https://api.github.com/repos/golang/go,closed,log/slog: don't write nil contexts [freeze exception] ,Testing Documentation NeedsFix,"As #61219 points out, we should not pass nil where a context.Context is expected. 
https://go.dev/cl/508437 contains the fix, which includes code as well as documentation.

/cc @golang/release
",1.0,"log/slog: don't write nil contexts [freeze exception]  - As #61219 points out, we should not pass nil where a context.Context is expected. 
https://go.dev/cl/508437 contains the fix, which includes code as well as documentation.

/cc @golang/release
",1,log slog  don t write nil contexts      as    points out  we should not pass nil where a context context is expected      contains the fix  which includes code as well as documentation      cc  golang release  ,1
64942,8780250670.0,IssuesEvent,2018-12-19 16:48:24,golang/go,https://api.github.com/repos/golang/go,reopened,documentation: modules quick start example does not work,Documentation WaitingForInfo modules,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.11.2 linux/amd64

</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/test/.cache/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/test/go""
GOPROXY=""""
GORACE=""""
GOROOT=""/usr/local/go""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/tmp/scratchpad/hello/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build952622232=/tmp/go-build -gno-record-gcc-switches""

</pre></details>

### What did you do?
Followed the quick-start example from the Go 1.11 Wiki page.

Link: [https://github.com/golang/go/wiki/Modules#quick-start-example](https://github.com/golang/go/wiki/Modules#quick-start-example)



### What did you expect to see?
It work


### What did you see instead?
Error after running `go build` the first time.
<pre>
build github.com/you/hello: cannot find module for path rsc.io/quote
</pre>
",1.0,"documentation: modules quick start example does not work - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.11.2 linux/amd64

</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/test/.cache/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/test/go""
GOPROXY=""""
GORACE=""""
GOROOT=""/usr/local/go""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/tmp/scratchpad/hello/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build952622232=/tmp/go-build -gno-record-gcc-switches""

</pre></details>

### What did you do?
Followed the quick-start example from the Go 1.11 Wiki page.

Link: [https://github.com/golang/go/wiki/Modules#quick-start-example](https://github.com/golang/go/wiki/Modules#quick-start-example)



### What did you expect to see?
It work


### What did you see instead?
Error after running `go build` the first time.
<pre>
build github.com/you/hello: cannot find module for path rsc.io/quote
</pre>
",1,documentation  modules quick start example does not work            what version of go are you using   go version            go version  go version       linux               does this issue reproduce with the latest release   yes          what operating system and processor architecture are you using   go env          go env  output       go env  goarch      gobin     gocache   home test  cache go build   goexe     goflags     gohostarch      gohostos  linux   goos  linux   gopath   home test go   goproxy     gorace     goroot   usr local go   gotmpdir     gotooldir   usr local go pkg tool linux     gccgo  gccgo   cc  gcc   cxx  g     cgo enabled      gomod   tmp scratchpad hello go mod   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches               what did you do   followed the quick start example from the go     wiki page     link                 what did you expect to see   it work          what did you see instead   error after running  go build  the first time      build github com you hello  cannot find module for path rsc io quote     ,1
227294,17379693663.0,IssuesEvent,2021-07-31 12:43:14,golang/go,https://api.github.com/repos/golang/go,closed,net/http: document that SetCookie can quote the value,Documentation NeedsInvestigation,"The `SetCookie` function quotes the value if it contains spaces or commas but this behavior is not documented in `SetCookie` documentation:

> SetCookie adds a Set-Cookie header to the provided ResponseWriter's headers. The provided cookie must have a valid Name. Invalid cookies may be silently dropped.
",1.0,"net/http: document that SetCookie can quote the value - The `SetCookie` function quotes the value if it contains spaces or commas but this behavior is not documented in `SetCookie` documentation:

> SetCookie adds a Set-Cookie header to the provided ResponseWriter's headers. The provided cookie must have a valid Name. Invalid cookies may be silently dropped.
",1,net http  document that setcookie can quote the value   the  setcookie  function quotes the value if it contains spaces or commas but this behavior is not documented in  setcookie  documentation       setcookie adds a set cookie header to the provided responsewriter s headers  the provided cookie must have a valid name  invalid cookies may be silently dropped   ,1
21594,4727235745.0,IssuesEvent,2016-10-18 12:56:51,golang/go,https://api.github.com/repos/golang/go,closed,testing: test.memprofilerate documentation is not accurate,Documentation NeedsFix,"The docs for the -test.memprofilerate flag say ""if >= 0"", but the code is simply greater, not greater than or equal:

```
~/go/src/testing$ git grep memProfileRate
testing.go:     memProfileRate   = flag.Int(""test.memprofilerate"", 0, ""if >=0, sets runtime.MemProfileRate"")
testing.go:     if *memProfileRate > 0 {
testing.go:             runtime.MemProfileRate = *memProfileRate
```

And the default is 512KB, not 0: https://golang.org/pkg/runtime/#pkg-variables
",1.0,"testing: test.memprofilerate documentation is not accurate - The docs for the -test.memprofilerate flag say ""if >= 0"", but the code is simply greater, not greater than or equal:

```
~/go/src/testing$ git grep memProfileRate
testing.go:     memProfileRate   = flag.Int(""test.memprofilerate"", 0, ""if >=0, sets runtime.MemProfileRate"")
testing.go:     if *memProfileRate > 0 {
testing.go:             runtime.MemProfileRate = *memProfileRate
```

And the default is 512KB, not 0: https://golang.org/pkg/runtime/#pkg-variables
",1,testing  test memprofilerate documentation is not accurate   the docs for the  test memprofilerate flag say  if        but the code is simply greater  not greater than or equal            go src testing  git grep memprofilerate  testing go      memprofilerate     flag int  test memprofilerate       if      sets runtime memprofilerate    testing go      if  memprofilerate        testing go              runtime memprofilerate    memprofilerate         and the default is    not       ,1
193343,22216137021.0,IssuesEvent,2022-06-08 01:59:46,maddyCode23/linux-4.1.15,https://api.github.com/repos/maddyCode23/linux-4.1.15,reopened,CVE-2016-4581 (Medium) detected in linux-stable-rtv4.1.33,security vulnerability,"## CVE-2016-4581 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>

<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/maddyCode23/linux-4.1.15/commit/f1f3d2b150be669390b32dfea28e773471bdd6e7"">f1f3d2b150be669390b32dfea28e773471bdd6e7</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/pnode.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/pnode.c</b>
</p>
</details>
<p></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>  
  
fs/pnode.c in the Linux kernel before 4.5.4 does not properly traverse a mount propagation tree in a certain case involving a slave mount, which allows local users to cause a denial of service (NULL pointer dereference and OOPS) via a crafted series of mount system calls.

<p>Publish Date: 2016-05-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-4581>CVE-2016-4581</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://nvd.nist.gov/vuln/detail/CVE-2016-4581"">https://nvd.nist.gov/vuln/detail/CVE-2016-4581</a></p>
<p>Release Date: 2016-05-23</p>
<p>Fix Resolution: 4.5.4</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2016-4581 (Medium) detected in linux-stable-rtv4.1.33 - ## CVE-2016-4581 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>

<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/maddyCode23/linux-4.1.15/commit/f1f3d2b150be669390b32dfea28e773471bdd6e7"">f1f3d2b150be669390b32dfea28e773471bdd6e7</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/pnode.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/pnode.c</b>
</p>
</details>
<p></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>  
  
fs/pnode.c in the Linux kernel before 4.5.4 does not properly traverse a mount propagation tree in a certain case involving a slave mount, which allows local users to cause a denial of service (NULL pointer dereference and OOPS) via a crafted series of mount system calls.

<p>Publish Date: 2016-05-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-4581>CVE-2016-4581</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://nvd.nist.gov/vuln/detail/CVE-2016-4581"">https://nvd.nist.gov/vuln/detail/CVE-2016-4581</a></p>
<p>Release Date: 2016-05-23</p>
<p>Fix Resolution: 4.5.4</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      medium  detected in linux stable            cve       medium severity vulnerability     vulnerable library    linux stable              julia cartwright s fork of linux stable rt git   library home page   a href    found in head commit   a href      found in base branch   master             vulnerable source files                  fs pnode c        fs pnode c                    vulnerability details         fs pnode c in the linux kernel before       does not properly traverse a mount propagation tree in a certain case involving a slave mount  which allows local users to cause a denial of service  null pointer dereference and oops  via a crafted series of mount system calls    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                      step up your open source security game with whitesource    ,0
14883,3900391667.0,IssuesEvent,2016-04-18 05:39:06,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: the fact that go build/install ignores _test.go files is not documented,Documentation,"The documentation (both for 1.6 at https://golang.org/cmd/go/ and for tip at https://tip.golang.org/cmd/go/) for `go test` says that

> 'Go test' recompiles each package along with any files with names matching the file pattern ""*_test.go"".

However the documentation for `go build` doesn't say anything about `_test.go` files.

I think the documentation for `go build` and `go install` should be updated to mention that `_test.go` files are ignored.

While most users probably do not read the documentation carefully it is still useful to have something to refer new users to. See the following StackOverflow question for background: http://stackoverflow.com/questions/36638149/undefined-variables-within-a-package-during-build",1.0,"cmd/go: the fact that go build/install ignores _test.go files is not documented - The documentation (both for 1.6 at https://golang.org/cmd/go/ and for tip at https://tip.golang.org/cmd/go/) for `go test` says that

> 'Go test' recompiles each package along with any files with names matching the file pattern ""*_test.go"".

However the documentation for `go build` doesn't say anything about `_test.go` files.

I think the documentation for `go build` and `go install` should be updated to mention that `_test.go` files are ignored.

While most users probably do not read the documentation carefully it is still useful to have something to refer new users to. See the following StackOverflow question for background: http://stackoverflow.com/questions/36638149/undefined-variables-within-a-package-during-build",1,cmd go  the fact that go build install ignores  test go files is not documented   the documentation  both for     at   and for tip at   for  go test  says that       go test  recompiles each package along with any files with names matching the file pattern    test go      however the documentation for  go build  doesn t say anything about   test go  files     i think the documentation for  go build  and  go install  should be updated to mention that   test go  files are ignored     while most users probably do not read the documentation carefully it is still useful to have something to refer new users to  see the following stackoverflow question for background   ,1
344091,10339949674.0,IssuesEvent,2019-09-03 20:37:34,space-wizards/RobustToolbox,https://api.github.com/repos/space-wizards/RobustToolbox,closed,Entity Manager Event Subscriptions Sanity,Area: Entities Priority: 3-low Project: Client Project: Server Type: Bug,"Subscribing delegate event handlers to the entity manager event system doesn't check that the delegate has been initialized yet. This means that if you haven't added a function to your delegate by the time you subscribe the event, then it will cause exceptions when the actual event gets called.

IE
```
eventhandler += onevent;
subscribeevent<eventargs>(eventhandler, this)
```

will make the system work fine, but this

```
subscribeevent<eventargs>(eventhandler, this)
eventhandler += onevent;
```
will not only accept this failed code without exception, it will cause exceptions every single time this event should fire",1.0,"Entity Manager Event Subscriptions Sanity - Subscribing delegate event handlers to the entity manager event system doesn't check that the delegate has been initialized yet. This means that if you haven't added a function to your delegate by the time you subscribe the event, then it will cause exceptions when the actual event gets called.

IE
```
eventhandler += onevent;
subscribeevent<eventargs>(eventhandler, this)
```

will make the system work fine, but this

```
subscribeevent<eventargs>(eventhandler, this)
eventhandler += onevent;
```
will not only accept this failed code without exception, it will cause exceptions every single time this event should fire",0,entity manager event subscriptions sanity   subscribing delegate event handlers to the entity manager event system doesn t check that the delegate has been initialized yet  this means that if you haven t added a function to your delegate by the time you subscribe the event  then it will cause exceptions when the actual event gets called     ie       eventhandler    onevent   subscribeevent  eventhandler  this          will make the system work fine  but this         subscribeevent  eventhandler  this   eventhandler    onevent        will not only accept this failed code without exception  it will cause exceptions every single time this event should fire,0
538246,15765380810.0,IssuesEvent,2021-03-31 14:06:09,webcompat/web-bugs,https://api.github.com/repos/webcompat/web-bugs,closed,www.ndtv.com - see bug description,browser-firefox engine-gecko ml-needsdiagnosis-false ml-probability-high priority-important,"<!-- @browser: Firefox 88.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 6.1; rv:88.0) Gecko/20100101 Firefox/88.0 -->
<!-- @reported_with: desktop-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/69255 -->

**URL**: https://www.ndtv.com/

**Browser / Version**: Firefox 88.0
**Operating System**: Windows 7
**Tested Another Browser**: Yes Chrome

**Problem type**: Something else
**Description**: screen is flikering
**Steps to Reproduce**:
screen flikers while opening sites
<details>
      <summary>View the screenshot</summary>
      <img alt=""Screenshot"" src=""https://webcompat.com/uploads/2021/3/8b912452-d395-4f55-8a78-8172336258fc.jpeg"">
      </details>

<details>
<summary>Browser Configuration</summary>
<ul>
  <li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20210330185720</li><li>channel: beta</li><li>hasTouchScreen: false</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>

[View console log messages](https://webcompat.com/console_logs/2021/3/a05046dd-3b2e-44b5-b168-a7681cf43267)

_From [webcompat.com](https://webcompat.com/) with ❤️_",1.0,"www.ndtv.com - see bug description - <!-- @browser: Firefox 88.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 6.1; rv:88.0) Gecko/20100101 Firefox/88.0 -->
<!-- @reported_with: desktop-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/69255 -->

**URL**: https://www.ndtv.com/

**Browser / Version**: Firefox 88.0
**Operating System**: Windows 7
**Tested Another Browser**: Yes Chrome

**Problem type**: Something else
**Description**: screen is flikering
**Steps to Reproduce**:
screen flikers while opening sites
<details>
      <summary>View the screenshot</summary>
      <img alt=""Screenshot"" src=""https://webcompat.com/uploads/2021/3/8b912452-d395-4f55-8a78-8172336258fc.jpeg"">
      </details>

<details>
<summary>Browser Configuration</summary>
<ul>
  <li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20210330185720</li><li>channel: beta</li><li>hasTouchScreen: false</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>

[View console log messages](https://webcompat.com/console_logs/2021/3/a05046dd-3b2e-44b5-b168-a7681cf43267)

_From [webcompat.com](https://webcompat.com/) with ❤️_",0,    see bug description              url         browser   version    firefox       operating system    windows     tested another browser    yes chrome    problem type    something else   description    screen is flikering   steps to reproduce    screen flikers while opening sites            view the screenshot          img alt  screenshot  src                 browser configuration       gfx webrender all  false  gfx webrender blob images  true  gfx webrender enabled  false  image mem shared  true  buildid     channel  beta  hastouchscreen  false  mixed active content blocked  false  mixed passive content blocked  false  tracking content blocked  false             from     with ❤️ ,0
450756,13018808265.0,IssuesEvent,2020-07-26 19:12:30,ION28/BLUESPAWN,https://api.github.com/repos/ION28/BLUESPAWN,closed,Improve Code Quality,difficulty/hard in progress lang/c++ platform/client priority/high type/enhancement,"This one will take a log of effort. This involves - 

a) Proper commenting / naming
b) Proper usage of const and references
c) Proper C++ style casting
d) Clean up the mess that is wrappers.hpp (and functions using it)
e) Make C-style code more C++-like
f) Spacing and unified formatting

I'll take this one and write up a contribution guidelines as I do this.",1.0,"Improve Code Quality - This one will take a log of effort. This involves - 

a) Proper commenting / naming
b) Proper usage of const and references
c) Proper C++ style casting
d) Clean up the mess that is wrappers.hpp (and functions using it)
e) Make C-style code more C++-like
f) Spacing and unified formatting

I'll take this one and write up a contribution guidelines as I do this.",0,improve code quality   this one will take a log of effort  this involves       a  proper commenting   naming  b  proper usage of const and references  c  proper c   style casting  d  clean up the mess that is wrappers hpp  and functions using it   e  make c style code more c   like  f  spacing and unified formatting    i ll take this one and write up a contribution guidelines as i do this ,0
321237,23847309952.0,IssuesEvent,2022-09-06 14:55:24,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/gopls: The analyzers documentation doesn't mention some analyzers,Documentation gopls Tools,"
### gopls version

<!--

Build info
----------
golang.org/x/tools/gopls master
    golang.org/x/tools/gopls@(devel)
    github.com/BurntSushi/toml@v1.0.0 h1:dtDWrepsVPfW9H/4y7dDgFc2MBUSeJhlaDtK13CxFlU=
    github.com/google/go-cmp@v0.5.7 h1:81/ik6ipDQS2aGcBfIN5dHDB36BwrStyeAQquSYCV4o=
    github.com/sergi/go-diff@v1.1.0 h1:we8PVUC3FE2uYfodKH/nBHMSetSfHDR6scGdBi+erh0=
    golang.org/x/mod@v0.6.0-dev.0.20220106191415-9b9b3d81d5e3 h1:kQgndtyPBW/JIYERgdxfwMYh3AVStj88WQTlNDi2a+o=
    golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c h1:5KslGYwFpkhGh+Q16bwMP3cOontH8FOep7tGV86Y7SQ=
    golang.org/x/sys@v0.0.0-20220209214540-3681064d5158 h1:rm+CHSpPEEW2IsXUib1ThaHIjuBVZjxNgSKmBLFfD4c=
    golang.org/x/text@v0.3.7 h1:olpwvP2KacW1ZWvsR7uQhoyTYvKAupfQrRGBFM352Gk=
    golang.org/x/tools@(devel)
    golang.org/x/xerrors@v0.0.0-20200804184101-5ec99f83aff1 h1:go1bK/D/BFZV2I8cIQd1NKEZ+0owSTG1fDTci4IqFcE=
    honnef.co/go/tools@v0.2.2 h1:MNh1AVMyVX23VUHE2O27jm6lNj3vjO5DexS4A1xvnzk=
    mvdan.cc/gofumpt@v0.3.0 h1:kTojdZo9AcEYbQYhGuLf/zszYthRdhDNDUi2JKTxas4=
    mvdan.cc/xurls/v2@v2.4.0 h1:tzxjVAj+wSBmDcF6zBB7/myTy3gX9xvi8Tyr28AuQgc=
go: go1.18-->


### What did you do?
I read x/tools/gopls/doc/analyzers.md to try to find the setting that would turn off useless messages labelled QF1003. 


### What did you expect to see?

Some mention of QF1003, or a hint about where to find information about it.

### What did you see instead?

nothing.

### Editor and settings
",1.0,"x/tools/gopls: The analyzers documentation doesn't mention some analyzers - 
### gopls version

<!--

Build info
----------
golang.org/x/tools/gopls master
    golang.org/x/tools/gopls@(devel)
    github.com/BurntSushi/toml@v1.0.0 h1:dtDWrepsVPfW9H/4y7dDgFc2MBUSeJhlaDtK13CxFlU=
    github.com/google/go-cmp@v0.5.7 h1:81/ik6ipDQS2aGcBfIN5dHDB36BwrStyeAQquSYCV4o=
    github.com/sergi/go-diff@v1.1.0 h1:we8PVUC3FE2uYfodKH/nBHMSetSfHDR6scGdBi+erh0=
    golang.org/x/mod@v0.6.0-dev.0.20220106191415-9b9b3d81d5e3 h1:kQgndtyPBW/JIYERgdxfwMYh3AVStj88WQTlNDi2a+o=
    golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c h1:5KslGYwFpkhGh+Q16bwMP3cOontH8FOep7tGV86Y7SQ=
    golang.org/x/sys@v0.0.0-20220209214540-3681064d5158 h1:rm+CHSpPEEW2IsXUib1ThaHIjuBVZjxNgSKmBLFfD4c=
    golang.org/x/text@v0.3.7 h1:olpwvP2KacW1ZWvsR7uQhoyTYvKAupfQrRGBFM352Gk=
    golang.org/x/tools@(devel)
    golang.org/x/xerrors@v0.0.0-20200804184101-5ec99f83aff1 h1:go1bK/D/BFZV2I8cIQd1NKEZ+0owSTG1fDTci4IqFcE=
    honnef.co/go/tools@v0.2.2 h1:MNh1AVMyVX23VUHE2O27jm6lNj3vjO5DexS4A1xvnzk=
    mvdan.cc/gofumpt@v0.3.0 h1:kTojdZo9AcEYbQYhGuLf/zszYthRdhDNDUi2JKTxas4=
    mvdan.cc/xurls/v2@v2.4.0 h1:tzxjVAj+wSBmDcF6zBB7/myTy3gX9xvi8Tyr28AuQgc=
go: go1.18-->


### What did you do?
I read x/tools/gopls/doc/analyzers.md to try to find the setting that would turn off useless messages labelled QF1003. 


### What did you expect to see?

Some mention of QF1003, or a hint about where to find information about it.

### What did you see instead?

nothing.

### Editor and settings
",1,x tools gopls  the analyzers documentation doesn t mention some analyzers         gopls version            build info              golang org x tools gopls master      golang org x tools gopls  devel       github com burntsushi toml                   github com google go cmp                   github com sergi go diff                     golang org x mod       dev         kqgndtypbw   o       golang org x sync                       golang org x sys             rm         golang org x text                 golang org x tools  devel       golang org x xerrors               d           honnef co go tools                 mvdan cc gofumpt                   mvdan cc xurls           tzxjvaj       go                  what did you do   i read x tools gopls doc analyzers md to try to find the setting that would turn off useless messages labelled              what did you expect to see     some mention of    or a hint about where to find information about it         what did you see instead     nothing         editor and settings  ,1
11046,3454732978.0,IssuesEvent,2015-12-17 17:03:23,golang/go,https://api.github.com/repos/golang/go,closed,net/http: ServeMux unexpectedly redirecting to add trailing slash,Documentation,"`http.ServeMux` unexpectedly redirects to add a trailing slash if there is a route that matches with a trailing slash.

Given the following `ServeMux`, I expect that a request for `/a` would match the path rooted as `/`.

```go
http.HandleFunc(""/"", ...)
http.HandleFunc(""/a/"", ...)
```
Instead, a 301 redirect is returned redirecting to `/a/` (see http://play.golang.org/p/65Skm2I5hq).

The docs describe redirects as happening in path sanitization cases (ie: requests with `.` or `..` elements), but no mention of transparently adding slashes. The docs also describe the match as a `""rooted subtree""` so it's also unexpected that a pattern for `/a/` would affect requests that don't have that prefix (ie: w/o the trailing slash).

In researching if this situation was reported before, I found a mailing list from 2010 implying this [was expected](https://groups.google.com/d/msg/golang-nuts/P-uq-cN4tjA/Mw9Ns2no35gJ) as well as a [code comment](http://golang.org/src/net/http/server.go#L1566). If that is still the case, then i think the docs should reflect that. (though i personally consider this a bug, i could understand that for some this could be a feature).
",1.0,"net/http: ServeMux unexpectedly redirecting to add trailing slash - `http.ServeMux` unexpectedly redirects to add a trailing slash if there is a route that matches with a trailing slash.

Given the following `ServeMux`, I expect that a request for `/a` would match the path rooted as `/`.

```go
http.HandleFunc(""/"", ...)
http.HandleFunc(""/a/"", ...)
```
Instead, a 301 redirect is returned redirecting to `/a/` (see http://play.golang.org/p/65Skm2I5hq).

The docs describe redirects as happening in path sanitization cases (ie: requests with `.` or `..` elements), but no mention of transparently adding slashes. The docs also describe the match as a `""rooted subtree""` so it's also unexpected that a pattern for `/a/` would affect requests that don't have that prefix (ie: w/o the trailing slash).

In researching if this situation was reported before, I found a mailing list from 2010 implying this [was expected](https://groups.google.com/d/msg/golang-nuts/P-uq-cN4tjA/Mw9Ns2no35gJ) as well as a [code comment](http://golang.org/src/net/http/server.go#L1566). If that is still the case, then i think the docs should reflect that. (though i personally consider this a bug, i could understand that for some this could be a feature).
",1,net http  servemux unexpectedly redirecting to add trailing slash    http servemux  unexpectedly redirects to add a trailing slash if there is a route that matches with a trailing slash     given the following  servemux   i expect that a request for   a  would match the path rooted as            go  http handlefunc            http handlefunc   a               instead  a   redirect is returned redirecting to   a    see      the docs describe redirects as happening in path sanitization cases  ie  requests with     or      elements   but no mention of transparently adding slashes  the docs also describe the match as a   rooted subtree   so it s also unexpected that a pattern for   a   would affect requests that don t have that prefix  ie  w o the trailing slash      in researching if this situation was reported before  i found a mailing list from   implying this     as well as a     if that is still the case  then i think the docs should reflect that   though i personally consider this a bug  i could understand that for some this could be a feature    ,1
314393,23519444721.0,IssuesEvent,2022-08-19 03:09:35,golang/go,https://api.github.com/repos/golang/go,closed,x/sync/errgroup: clarify that Go calls the function regardless of prior errors,Documentation help wanted NeedsFix,"### What version of Go are you using (`go version`)?
```
go version go1.19-pre4 cl/455575533 +12f49fe0ed linux/amd64
```

### Does this issue reproduce with the latest release?
Yes

### What did you do?

```
package test

import (
	""errors""
	""sync/atomic""
	""testing""
	""time""

	""golang.org/x/sync/errgroup""
)

func TestErrGroupDoesNotRunNewFunctionsAfterPreviousError(t *testing.T) {
	group := errgroup.Group{}
	group.SetLimit(1)
	group.Go(func() error {
		return errors.New("""")
	})
	time.Sleep(time.Second)

	var ran atomic.Bool
	group.Go(func() error {
		ran.Store(true)
		return nil
	})
        _ = group.Wait()
	if ran.Load() {
		t.Errorf(""Expected second func not to run, but it did"")
	}
}

```

### What did you expect to see?

The [documentation for errgroup](https://pkg.go.dev/golang.org/x/sync@v0.0.0-20220601150217-0de741cfad7f/errgroup#Group.Go) states:

> Go calls the given function in a new goroutine. It blocks until the new goroutine can be added without the number of active goroutines in the group exceeding the configured limit.
> 
> The first call to return a non-nil error cancels the group; its error will be returned by Wait.

I would assume that if the first call to return a non-nil error cancels the group, future funcs passed to go won't run.

Furthermore calls to `group.Wait()` should return immediately rather than waiting for funcs created after the group was cancelled to complete.

### What did you see instead?

All funcs are called, even those created after the group was cancelled. `group.Wait()` waits for all funcs to complete before returning.


",1.0,"x/sync/errgroup: clarify that Go calls the function regardless of prior errors - ### What version of Go are you using (`go version`)?
```
go version go1.19-pre4 cl/455575533 +12f49fe0ed linux/amd64
```

### Does this issue reproduce with the latest release?
Yes

### What did you do?

```
package test

import (
	""errors""
	""sync/atomic""
	""testing""
	""time""

	""golang.org/x/sync/errgroup""
)

func TestErrGroupDoesNotRunNewFunctionsAfterPreviousError(t *testing.T) {
	group := errgroup.Group{}
	group.SetLimit(1)
	group.Go(func() error {
		return errors.New("""")
	})
	time.Sleep(time.Second)

	var ran atomic.Bool
	group.Go(func() error {
		ran.Store(true)
		return nil
	})
        _ = group.Wait()
	if ran.Load() {
		t.Errorf(""Expected second func not to run, but it did"")
	}
}

```

### What did you expect to see?

The [documentation for errgroup](https://pkg.go.dev/golang.org/x/sync@v0.0.0-20220601150217-0de741cfad7f/errgroup#Group.Go) states:

> Go calls the given function in a new goroutine. It blocks until the new goroutine can be added without the number of active goroutines in the group exceeding the configured limit.
> 
> The first call to return a non-nil error cancels the group; its error will be returned by Wait.

I would assume that if the first call to return a non-nil error cancels the group, future funcs passed to go won't run.

Furthermore calls to `group.Wait()` should return immediately rather than waiting for funcs created after the group was cancelled to complete.

### What did you see instead?

All funcs are called, even those created after the group was cancelled. `group.Wait()` waits for all funcs to complete before returning.


",1,x sync errgroup  clarify that go calls the function regardless of prior errors       what version of go are you using   go version          go version       cl      linux               does this issue reproduce with the latest release   yes        what did you do          package test    import    	 errors   	 sync atomic   	 testing   	 time     	 golang org x sync errgroup        func testerrgroupdoesnotrunnewfunctionsafterpreviouserror t  testing t     	group    errgroup group    	group setlimit     	group go func   error    		return errors new      	    	time sleep time second     	var ran atomic bool  	group go func   error    		ran store true   		return nil  	                group wait    	if ran load      		t errorf  expected second func not to run  but it did    	                   what did you expect to see     the     states       go calls the given function in a new goroutine  it blocks until the new goroutine can be added without the number of active goroutines in the group exceeding the configured limit         the first call to return a non nil error cancels the group  its error will be returned by wait     i would assume that if the first call to return a non nil error cancels the group  future funcs passed to go won t run     furthermore calls to  group wait    should return immediately rather than waiting for funcs created after the group was cancelled to complete         what did you see instead     all funcs are called  even those created after the group was cancelled   group wait    waits for all funcs to complete before returning       ,1
259279,19594062664.0,IssuesEvent,2022-01-05 15:54:51,golang/go,https://api.github.com/repos/golang/go,closed,testing: document file format for fuzz corpus files,Documentation NeedsInvestigation fuzz,"commit 8ac5cbe05d61df0a7a7c9a38ff33305d4dcfea32

The fuzz docs inside the testing package say:

> Seed inputs may be registered by calling F.Add or by storing files in the directory testdata/fuzz/<Name> (where <Name> is the name of the fuzz target) within the package containing the fuzz target.

but the docs don't say what format those files are expected to be in. I was expecting to be able to just copy a load of corpus data from the original fuzz tool (where the format is just exactly the data for the input), but I see errors of the form:

```
 ""testdata/fuzz/FuzzDecoder/27f4f596adb49c6967f41e8f82d3855f5ae9375e"": unmarshal: must include version and at least one value
```

The testing docs should say what format should be used for these files. Ideally there would be a some kind of migration tool to migrate from the old format to the new.
",1.0,"testing: document file format for fuzz corpus files - commit 8ac5cbe05d61df0a7a7c9a38ff33305d4dcfea32

The fuzz docs inside the testing package say:

> Seed inputs may be registered by calling F.Add or by storing files in the directory testdata/fuzz/<Name> (where <Name> is the name of the fuzz target) within the package containing the fuzz target.

but the docs don't say what format those files are expected to be in. I was expecting to be able to just copy a load of corpus data from the original fuzz tool (where the format is just exactly the data for the input), but I see errors of the form:

```
 ""testdata/fuzz/FuzzDecoder/27f4f596adb49c6967f41e8f82d3855f5ae9375e"": unmarshal: must include version and at least one value
```

The testing docs should say what format should be used for these files. Ideally there would be a some kind of migration tool to migrate from the old format to the new.
",1,testing  document file format for fuzz corpus files   commit      the fuzz docs inside the testing package say       seed inputs may be registered by calling f add or by storing files in the directory testdata fuzz    where   is the name of the fuzz target  within the package containing the fuzz target     but the docs don t say what format those files are expected to be in  i was expecting to be able to just copy a load of corpus data from the original fuzz tool  where the format is just exactly the data for the input   but i see errors of the form            testdata fuzz fuzzdecoder     unmarshal  must include version and at least one value         the testing docs should say what format should be used for these files  ideally there would be a some kind of migration tool to migrate from the old format to the new   ,1
23419,4934573006.0,IssuesEvent,2016-11-28 19:28:17,golang/go,https://api.github.com/repos/golang/go,closed,net/http: document that Etags in ServeContent must be RFC 7232 compliant,Documentation,"Change f3862742b67a84edf939f41276360ada4e7197a6 ([CL/32014](http://golang.org/cl/32014)) caused a regression in the behavior of http.ServeContent such that explicitly setting the Etag no longer caused the server to return status 304 when the Etags match.

```go
func Test(t *testing.T) {
	fs := http.FileServer(http.Dir(""/tmp""))
	h := http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
		// Delete if-modified-since header so that ETags can be used instead of the standard cache policy.
		r.Header.Del(""If-Modified-Since"")

		// Set ETag to to uniquely identify the unchanged static asset.
		w.Header().Set(""Etag"", ""6"")

		fs.ServeHTTP(w, r)
	})
	ts := httptest.NewServer(h)

	// Ensure /tmp/test.txt exists.
	if err := ioutil.WriteFile(""/tmp/test.txt"", nil, 0664); err != nil {
		t.Fatal(err)
	}

	var c http.Client
	req, err := http.NewRequest(""GET"", ts.URL+""/test.txt"", nil)
	if err != nil {
		t.Fatal(err)
	}
	req.Header.Add(""If-None-Match"", ""6"") // Same Etag as above
	resp, err := c.Do(req)
	if err != nil {
		t.Fatal(err)
	}
	if resp.StatusCode != 304 {
		t.Error()
	}
}
```

I believe this is a regression because the documentation for `ServeContent` explicitly says:
> If the caller has set w's ETag header, ServeContent uses it to handle requests using If-Range and If-None-Match.

\cc @bradfitz ",1.0,"net/http: document that Etags in ServeContent must be RFC 7232 compliant - Change f3862742b67a84edf939f41276360ada4e7197a6 ([CL/32014](http://golang.org/cl/32014)) caused a regression in the behavior of http.ServeContent such that explicitly setting the Etag no longer caused the server to return status 304 when the Etags match.

```go
func Test(t *testing.T) {
	fs := http.FileServer(http.Dir(""/tmp""))
	h := http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
		// Delete if-modified-since header so that ETags can be used instead of the standard cache policy.
		r.Header.Del(""If-Modified-Since"")

		// Set ETag to to uniquely identify the unchanged static asset.
		w.Header().Set(""Etag"", ""6"")

		fs.ServeHTTP(w, r)
	})
	ts := httptest.NewServer(h)

	// Ensure /tmp/test.txt exists.
	if err := ioutil.WriteFile(""/tmp/test.txt"", nil, 0664); err != nil {
		t.Fatal(err)
	}

	var c http.Client
	req, err := http.NewRequest(""GET"", ts.URL+""/test.txt"", nil)
	if err != nil {
		t.Fatal(err)
	}
	req.Header.Add(""If-None-Match"", ""6"") // Same Etag as above
	resp, err := c.Do(req)
	if err != nil {
		t.Fatal(err)
	}
	if resp.StatusCode != 304 {
		t.Error()
	}
}
```

I believe this is a regression because the documentation for `ServeContent` explicitly says:
> If the caller has set w's ETag header, ServeContent uses it to handle requests using If-Range and If-None-Match.

\cc @bradfitz ",1,net http  document that etags in servecontent must be rfc   compliant   change        caused a regression in the behavior of http servecontent such that explicitly setting the etag no longer caused the server to return status   when the etags match        go  func test t  testing t     	fs    http fileserver http dir   tmp     	h    http handlerfunc func w http responsewriter  r  http request     		   delete if modified since header so that etags can be used instead of the standard cache policy   		r header del  if modified since      		   set etag to to uniquely identify the unchanged static asset   		w header   set  etag           		fs servehttp w  r   	    	ts    httptest newserver h     	   ensure  tmp test txt exists   	if err    ioutil writefile   tmp test txt   nil      err    nil    		t fatal err   	     	var c http client  	req  err    http newrequest  get   ts url   test txt   nil   	if err    nil    		t fatal err   	   	req header add  if none match           same etag as above  	resp  err    c do req   	if err    nil    		t fatal err   	   	if resp statuscode         		t error    	             i believe this is a regression because the documentation for  servecontent  explicitly says     if the caller has set w s etag header  servecontent uses it to handle requests using if range and if none match      cc  bradfitz ,1
58079,8228461086.0,IssuesEvent,2018-09-07 05:27:25,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: go test all is under-documented,Documentation,"### What version of Go are you using (`go version`)?

```
$ go version
go version go1.11 darwin/amd64
```

### Issue

How do I get help for `go test all`? `go help test all` doesn't work, ditto `go test help all`, `go help test` doesn't have documentation for it, and docs [1] [2] dont mention it.

Perhaps I'm missing something - sorry if so. 

1: https://github.com/golang/go/wiki/Modules#installing-and-activating-module-support
2: https://golang.org/pkg/testing/",1.0,"cmd/go: go test all is under-documented - ### What version of Go are you using (`go version`)?

```
$ go version
go version go1.11 darwin/amd64
```

### Issue

How do I get help for `go test all`? `go help test all` doesn't work, ditto `go test help all`, `go help test` doesn't have documentation for it, and docs [1] [2] dont mention it.

Perhaps I'm missing something - sorry if so. 

1: https://github.com/golang/go/wiki/Modules#installing-and-activating-module-support
2: https://golang.org/pkg/testing/",1,cmd go  go test all is under documented       what version of go are you using   go version              go version  go version     darwin               issue    how do i get help for  go test all    go help test all  doesn t work  ditto  go test help all    go help test  doesn t have documentation for it  and docs     dont mention it     perhaps i m missing something   sorry if so                ,1
119675,12036834257.0,IssuesEvent,2020-04-13 20:34:51,golang/go,https://api.github.com/repos/golang/go,closed,errors: example code for errors.As has extraneous code,Documentation NeedsInvestigation,"The example code for `errors.As` (viewed at https://pkg.go.dev/errors?tab=doc#As) is the [entire contents of the `wrap_test.go` file](https://github.com/golang/go/blob/go1.14.1/src/errors/wrap_test.go). It should be just `func ExampleAs() { ... }` I presume.

In talking this over with @FiloSottile, this may be a more systemic issue which can be improved in `godoc`. For example, we have the same issue with the [chacha20poly1305.NewX](https://pkg.go.dev/golang.org/x/crypto/chacha20poly1305?tab=doc#NewX) example code. However, perhaps we should fix the example for the errors package for now either way.

While we're in there, perhaps we should check if there are any improvements to the documentation for errors as tracked in https://github.com/golang/go/issues/31716.

/cc @jba @mpvl ",1.0,"errors: example code for errors.As has extraneous code - The example code for `errors.As` (viewed at https://pkg.go.dev/errors?tab=doc#As) is the [entire contents of the `wrap_test.go` file](https://github.com/golang/go/blob/go1.14.1/src/errors/wrap_test.go). It should be just `func ExampleAs() { ... }` I presume.

In talking this over with @FiloSottile, this may be a more systemic issue which can be improved in `godoc`. For example, we have the same issue with the [chacha20poly1305.NewX](https://pkg.go.dev/golang.org/x/crypto/chacha20poly1305?tab=doc#NewX) example code. However, perhaps we should fix the example for the errors package for now either way.

While we're in there, perhaps we should check if there are any improvements to the documentation for errors as tracked in https://github.com/golang/go/issues/31716.

/cc @jba @mpvl ",1,errors  example code for errors as has extraneous code   the example code for  errors as   viewed at   is the     it should be just  func exampleas            i presume     in talking this over with  filosottile  this may be a more systemic issue which can be improved in  godoc   for example  we have the same issue with the     example code  however  perhaps we should fix the example for the errors package for now either way     while we re in there  perhaps we should check if there are any improvements to the documentation for errors as tracked in       cc  jba  mpvl ,1
7390,24769393249.0,IssuesEvent,2022-10-23 00:07:57,fastapi-mvc/fastapi-mvc,https://api.github.com/repos/fastapi-mvc/fastapi-mvc,closed,Start testing on MacOS,automation,"<!-- Checked checkbox should look like this: [x] -->
- [x] I have searched the [issues](https://github.com/fastapi-mvc/fastapi-mvc/issues) of this repo and believe that this is not a duplicate.

## Feature Request
<!-- Now feel free to write your idea for improvement. Thanks again 🙌 ❤️ -->
Start testing project on MacOS",1.0,"Start testing on MacOS - <!-- Checked checkbox should look like this: [x] -->
- [x] I have searched the [issues](https://github.com/fastapi-mvc/fastapi-mvc/issues) of this repo and believe that this is not a duplicate.

## Feature Request
<!-- Now feel free to write your idea for improvement. Thanks again 🙌 ❤️ -->
Start testing project on MacOS",0,start testing on macos          i have searched the     of this repo and believe that this is not a duplicate        feature request     start testing project on macos,0
19417,4388698633.0,IssuesEvent,2016-08-08 19:44:08,golang/go,https://api.github.com/repos/golang/go,reopened,website: inconsistency in supported OS X versions,Documentation,"https://golang.org/dl/ mentions:

> Apple OS X
> OS X 10.8 or later, Intel 64-bit processor

https://golang.org/doc/install says:

> Official binary distributions are available for ...
> Mac OS X (10.7 and above)
",1.0,"website: inconsistency in supported OS X versions - https://golang.org/dl/ mentions:

> Apple OS X
> OS X 10.8 or later, Intel 64-bit processor

https://golang.org/doc/install says:

> Official binary distributions are available for ...
> Mac OS X (10.7 and above)
",1,website  inconsistency in supported os x versions     mentions       apple os x    os x     or later  intel   bit processor      says       official binary distributions are available for        mac os x      and above   ,1
155219,19767222997.0,IssuesEvent,2022-01-17 05:03:57,kijunb33/test,https://api.github.com/repos/kijunb33/test,opened,CVE-2020-9484 (High) detected in tomcat-embed-core-7.0.90.jar,security vulnerability,"## CVE-2020-9484 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tomcat-embed-core-7.0.90.jar</b></p></summary>

<p>Core Tomcat implementation</p>
<p>Library home page: <a href=""https://tomcat.apache.org/"">https://tomcat.apache.org/</a></p>
<p>Path to vulnerable library: /tomcat-embed-core-7.0.90.jar</p>
<p>

Dependency Hierarchy:
  - :x: **tomcat-embed-core-7.0.90.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/kijunb33/test/commit/6a54250bb688886ee6964a13c249c44d3659de1a"">6a54250bb688886ee6964a13c249c44d3659de1a</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>  
  
When using Apache Tomcat versions 10.0.0-M1 to 10.0.0-M4, 9.0.0.M1 to 9.0.34, 8.5.0 to 8.5.54 and 7.0.0 to 7.0.103 if a) an attacker is able to control the contents and name of a file on the server; and b) the server is configured to use the PersistenceManager with a FileStore; and c) the PersistenceManager is configured with sessionAttributeValueClassNameFilter=""null"" (the default unless a SecurityManager is used) or a sufficiently lax filter to allow the attacker provided object to be deserialized; and d) the attacker knows the relative file path from the storage location used by FileStore to the file the attacker has control over; then, using a specifically crafted request, the attacker will be able to trigger remote code execution via deserialization of the file under their control. Note that all of conditions a) to d) must be true for the attack to succeed.

<p>Publish Date: 2020-05-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9484>CVE-2020-9484</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.0</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: High
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-9484"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-9484</a></p>
<p>Release Date: 2020-05-20</p>
<p>Fix Resolution: org.apache.tomcat.embed:tomcat-embed-core:7.0.104,8.5.55,9.0.35,10.0.0-M5,org.apache.tomcat:tomcat-catalina:7.0.104,8.5.55,9.0.35,10.0.0-M5</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-9484 (High) detected in tomcat-embed-core-7.0.90.jar - ## CVE-2020-9484 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tomcat-embed-core-7.0.90.jar</b></p></summary>

<p>Core Tomcat implementation</p>
<p>Library home page: <a href=""https://tomcat.apache.org/"">https://tomcat.apache.org/</a></p>
<p>Path to vulnerable library: /tomcat-embed-core-7.0.90.jar</p>
<p>

Dependency Hierarchy:
  - :x: **tomcat-embed-core-7.0.90.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/kijunb33/test/commit/6a54250bb688886ee6964a13c249c44d3659de1a"">6a54250bb688886ee6964a13c249c44d3659de1a</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>  
  
When using Apache Tomcat versions 10.0.0-M1 to 10.0.0-M4, 9.0.0.M1 to 9.0.34, 8.5.0 to 8.5.54 and 7.0.0 to 7.0.103 if a) an attacker is able to control the contents and name of a file on the server; and b) the server is configured to use the PersistenceManager with a FileStore; and c) the PersistenceManager is configured with sessionAttributeValueClassNameFilter=""null"" (the default unless a SecurityManager is used) or a sufficiently lax filter to allow the attacker provided object to be deserialized; and d) the attacker knows the relative file path from the storage location used by FileStore to the file the attacker has control over; then, using a specifically crafted request, the attacker will be able to trigger remote code execution via deserialization of the file under their control. Note that all of conditions a) to d) must be true for the attack to succeed.

<p>Publish Date: 2020-05-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9484>CVE-2020-9484</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.0</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: High
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-9484"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-9484</a></p>
<p>Release Date: 2020-05-20</p>
<p>Fix Resolution: org.apache.tomcat.embed:tomcat-embed-core:7.0.104,8.5.55,9.0.35,10.0.0-M5,org.apache.tomcat:tomcat-catalina:7.0.104,8.5.55,9.0.35,10.0.0-M5</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in tomcat embed core       jar      cve       high severity vulnerability     vulnerable library    tomcat embed core       jar      core tomcat implementation   library home page   a href     path to vulnerable library   tomcat embed core       jar     dependency hierarchy       x    tomcat embed core       jar    vulnerable library   found in head commit   a href     found in base branch   master              vulnerability details         when using apache tomcat versions         to                  to              to       and       to       if a  an attacker is able to control the contents and name of a file on the server  and b  the server is configured to use the persistencemanager with a filestore  and c  the persistencemanager is configured with sessionattributevalueclassnamefilter  null   the default unless a securitymanager is used  or a sufficiently lax filter to allow the attacker provided object to be deserialized  and d  the attacker knows the relative file path from the storage location used by filestore to the file the attacker has control over  then  using a specifically crafted request  the attacker will be able to trigger remote code execution via deserialization of the file under their control  note that all of conditions a  to d  must be true for the attack to succeed    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  local     attack complexity  high     privileges required  low     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  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 tomcat embed tomcat embed core                           org apache tomcat tomcat catalina                                         step up your open source security game with whitesource    ,0
335461,24469059360.0,IssuesEvent,2022-10-07 17:50:20,golang/go,https://api.github.com/repos/golang/go,closed,testing: add an example showcasing B.RunParallel with B.ReportMetric,Suggested Documentation NeedsFix,"I had a parallel benchmark in the form of:

```
var totalFoo int64
b.RunParallel(func(pb *testing.PB) {
	for pb.Next() {
		// benchmark...
		totalFoo += someFoo()
	}
})
b.ReportMetric(float64(totalAmount)/float64(b.N), ""foo/op"")
```

I was taking a second look at the benchmark because dividing by `b.N` seemed fishy. This is a parallel benchmark, where I iterate via `pb.Next` and not `b.N`, so can I rely on `b.N` being an accurate detail of how many iterations were run across all goroutines?

The docs seem to imply so:

> RunParallel runs a benchmark in parallel. It creates multiple goroutines and distributes b.N iterations among them.

> ReportMetric adds ""n unit"" to the reported benchmark results. If the metric is per-iteration, the caller should divide by b.N

Still, I had to re-read the docs multiple times to convince myself. I think it would be nice to add an example on ReportMetric for parallel benchmarks, such as `func ExampleB_ReportMetric_parallel`, to help clarify the interaction between the two and how they are meant to be used.

And there's another reason why an example would be good: since `RunParallel` hides the goroutine spawning from the user, it's relatively easy to introduce data races by mistake, like I did above! `totalFoo += someFoo()` would need to be something like `atomic.AddInt64(&totalFoo, someFoo())`. The example could also show that.

Marking as a good candidate for first time contributors. Happy to review it too.

cc @mpvl per https://dev.golang.org/owners",1.0,"testing: add an example showcasing B.RunParallel with B.ReportMetric - I had a parallel benchmark in the form of:

```
var totalFoo int64
b.RunParallel(func(pb *testing.PB) {
	for pb.Next() {
		// benchmark...
		totalFoo += someFoo()
	}
})
b.ReportMetric(float64(totalAmount)/float64(b.N), ""foo/op"")
```

I was taking a second look at the benchmark because dividing by `b.N` seemed fishy. This is a parallel benchmark, where I iterate via `pb.Next` and not `b.N`, so can I rely on `b.N` being an accurate detail of how many iterations were run across all goroutines?

The docs seem to imply so:

> RunParallel runs a benchmark in parallel. It creates multiple goroutines and distributes b.N iterations among them.

> ReportMetric adds ""n unit"" to the reported benchmark results. If the metric is per-iteration, the caller should divide by b.N

Still, I had to re-read the docs multiple times to convince myself. I think it would be nice to add an example on ReportMetric for parallel benchmarks, such as `func ExampleB_ReportMetric_parallel`, to help clarify the interaction between the two and how they are meant to be used.

And there's another reason why an example would be good: since `RunParallel` hides the goroutine spawning from the user, it's relatively easy to introduce data races by mistake, like I did above! `totalFoo += someFoo()` would need to be something like `atomic.AddInt64(&totalFoo, someFoo())`. The example could also show that.

Marking as a good candidate for first time contributors. Happy to review it too.

cc @mpvl per https://dev.golang.org/owners",1,testing  add an example showcasing b runparallel with b reportmetric   i had a parallel benchmark in the form of          var totalfoo    b runparallel func pb  testing pb     	for pb next      		   benchmark     		totalfoo    somefoo    	       b reportmetric   totalamount    b n    foo op           i was taking a second look at the benchmark because dividing by  b n  seemed fishy  this is a parallel benchmark  where i iterate via  pb next  and not  b n   so can i rely on  b n  being an accurate detail of how many iterations were run across all goroutines     the docs seem to imply so       runparallel runs a benchmark in parallel  it creates multiple goroutines and distributes b n iterations among them       reportmetric adds  n unit  to the reported benchmark results  if the metric is per iteration  the caller should divide by b n    still  i had to re read the docs multiple times to convince myself  i think it would be nice to add an example on reportmetric for parallel benchmarks  such as  func exampleb reportmetric parallel   to help clarify the interaction between the two and how they are meant to be used     and there s another reason why an example would be good  since  runparallel  hides the goroutine spawning from the user  it s relatively easy to introduce data races by mistake  like i did above   totalfoo    somefoo    would need to be something like  atomic    totalfoo  somefoo      the example could also show that     marking as a good candidate for first time contributors  happy to review it too     cc  mpvl per  ,1
32656,6101589302.0,IssuesEvent,2017-06-20 14:53:48,golang/go,https://api.github.com/repos/golang/go,closed,Website documentation,Documentation,"If we open exaple on page https://golang.org/pkg/go/parser/ and run in play.
### what you see?

open example_test.go: No such file or directory

### What did you expect to see?

The result of snippet code


",1.0,"Website documentation - If we open exaple on page https://golang.org/pkg/go/parser/ and run in play.
### what you see?

open example_test.go: No such file or directory

### What did you expect to see?

The result of snippet code


",1,website documentation   if we open exaple on page   and run in play       what you see     open example test go  no such file or directory        what did you expect to see     the result of snippet code      ,1
336487,24500986904.0,IssuesEvent,2022-10-10 12:47:33,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/gopls: textDocument/definition is slow in large codebase,Documentation NeedsInvestigation gopls Tools,"<!--
Please answer these questions before submitting your issue. Thanks!
-->

### gopls version
```
golang.org/x/tools/gopls v0.9.4
    golang.org/x/tools/gopls@v0.9.4 h1:YhHOxVi++ILnY+QnH9FGtRKZZrunSaR7OW8/dCp7bBk=
    github.com/BurntSushi/toml@v1.2.0 h1:Rt8g24XnyGTyglgET/PRUNlrUeu9F5L+7FilkXfZgs0=
    github.com/google/go-cmp@v0.5.8 h1:e6P7q2lk1O+qJJb4BtCQXlK8vWEO8V1ZeuEdJNOqZyg=
    github.com/sergi/go-diff@v1.1.0 h1:we8PVUC3FE2uYfodKH/nBHMSetSfHDR6scGdBi+erh0=
    golang.org/x/exp/typeparams@v0.0.0-20220722155223-a9213eeb770e h1:7Xs2YCOpMlNqSQSmrrnhlzBXIE/bpMecZplbLePTJvE=
    golang.org/x/mod@v0.6.0-dev.0.20220419223038-86c51ed26bb4 h1:6zppjxzCulZykYSLyVDYbneBfbaBIQPYMevg0bEwv2s=
    golang.org/x/sync@v0.0.0-20220722155255-886fb9371eb4 h1:uVc8UZUe6tr40fFVnUP5Oj+veunVezqYl9z7DYw9xzw=
    golang.org/x/sys@v0.0.0-20220722155257-8c9f86f7a55f h1:v4INt8xihDGvnrfjMDVXGxw9wrfxYyCjk0KbXjhR55s=
    golang.org/x/text@v0.3.7 h1:olpwvP2KacW1ZWvsR7uQhoyTYvKAupfQrRGBFM352Gk=
    golang.org/x/tools@v0.1.13-0.20220812184215-3f9b119300de h1:b68wxF4nfQjj1XTRHtjVjCximbhAwjztuzDEFGU+n9o=
    honnef.co/go/tools@v0.3.2 h1:ytYb4rOqyp1TSa2EPvNVwtPQJctSELKaMyLfqNP4+34=
    mvdan.cc/gofumpt@v0.3.1 h1:avhhrOmv0IuvQVK7fvwV91oFSGAk5/6Po8GXTzICeu8=
    mvdan.cc/xurls/v2@v2.4.0 h1:tzxjVAj+wSBmDcF6zBB7/myTy3gX9xvi8Tyr28AuQgc=
go: go1.17.6
```


### go env

```
GO111MODULE=""on""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/ubuntu/.cache/go-build""
GOENV=""/home/ubuntu/.config/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""-mod=readonly""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/ubuntu/co/backend/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/ubuntu/co/backend/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/home/ubuntu/co/backend/opt/go1.17.6""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/home/ubuntu/co/backend/opt/go1.17.6/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""go1.17.6""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build457205370=/tmp/go-build -gno-record-gcc-switches""

```



# What Happened
I noticed that `go-to-definition` in vscode on a go file was taking a long time, and consistently saw the following log when navigating within a package (specifically, I was using go to definition to navigate within a package. I'm operating within a large monorepo, with some heavily interlinked packages)

```
[Trace - 23:17:36.892 PM] Received response 'textDocument/definition - (213)' in 11214ms.
```

I pulled up the ""Trace Information"" tab in the debug server, and found a log for `textDocument/Definition` RPC. This log looks to consist of `cache.parseGo` and `cache.TypeCheck` events, but many of these events are replicated, seemly indicating that duplicate work is build done. I see multiple packages being parsed many times (up to ~20, looks to be dependent on imports), with all of its files listed underneath
```
0s textDocument/definition 13.862321388s start=""textDocument/definition"" method=""textDocument/definition"" direction=""in"" id=""#20""

    13.862319081s label= status.code=""OK"" 

    74.474µs queued 27.786µs start=""queued""
    178.05µs source.Identifier 13.861909568s start=""source.Identifier""
...
3.12062168s cache.typeCheck 192.827411ms start=""cache.typeCheck"" package=""foo [bar.test]"" 
    3.120790449s cache.parseGo 196.421µs start=""cache.parseGo"" file=""foo/file_a.go"" 
    .... <package files> ...
...
3.590160298s cache.typeCheck 317.260966ms start=""cache.typeCheck"" package=""foo [baz.test]"" 
    3.590357772s cache.parseGo 274.427µs start=""cache.parseGo"" file=""foo/file_a.go"" 
    .... <package files> ...
...
5.043508487s cache.typeCheck 175.931042ms start=""cache.typeCheck"" package=""foo [foo2.test]"" 
    5.492814972s cache.parseGo 351.925µs start=""cache.parseGo"" file=""foo/file_a.go"" 
    .... <package files> ...
...


```

Appears that there's duplicate work being done - I looked through the codebase for these events and found many todos added in  https://github.com/golang/tools/commit/f79f3aac190554ef62f0257555394b31c29f0320. (eg [a](https://github.com/golang/tools/commit/f79f3aac190554ef62f0257555394b31c29f0320#diff-e230acde030eabf6ec5a1c93adfd0517b7d7eca5f5246f383ea510b752f3b703R475) [b](https://github.com/golang/tools/commit/f79f3aac190554ef62f0257555394b31c29f0320#diff-e230acde030eabf6ec5a1c93adfd0517b7d7eca5f5246f383ea510b752f3b703R577)). Is there any planned work to speed up the `cache.typeCheck` and `cache.parseGo` operations? 

Happy to DM the full trace file to someone if that would help!",1.0,"x/tools/gopls: textDocument/definition is slow in large codebase - <!--
Please answer these questions before submitting your issue. Thanks!
-->

### gopls version
```
golang.org/x/tools/gopls v0.9.4
    golang.org/x/tools/gopls@v0.9.4 h1:YhHOxVi++ILnY+QnH9FGtRKZZrunSaR7OW8/dCp7bBk=
    github.com/BurntSushi/toml@v1.2.0 h1:Rt8g24XnyGTyglgET/PRUNlrUeu9F5L+7FilkXfZgs0=
    github.com/google/go-cmp@v0.5.8 h1:e6P7q2lk1O+qJJb4BtCQXlK8vWEO8V1ZeuEdJNOqZyg=
    github.com/sergi/go-diff@v1.1.0 h1:we8PVUC3FE2uYfodKH/nBHMSetSfHDR6scGdBi+erh0=
    golang.org/x/exp/typeparams@v0.0.0-20220722155223-a9213eeb770e h1:7Xs2YCOpMlNqSQSmrrnhlzBXIE/bpMecZplbLePTJvE=
    golang.org/x/mod@v0.6.0-dev.0.20220419223038-86c51ed26bb4 h1:6zppjxzCulZykYSLyVDYbneBfbaBIQPYMevg0bEwv2s=
    golang.org/x/sync@v0.0.0-20220722155255-886fb9371eb4 h1:uVc8UZUe6tr40fFVnUP5Oj+veunVezqYl9z7DYw9xzw=
    golang.org/x/sys@v0.0.0-20220722155257-8c9f86f7a55f h1:v4INt8xihDGvnrfjMDVXGxw9wrfxYyCjk0KbXjhR55s=
    golang.org/x/text@v0.3.7 h1:olpwvP2KacW1ZWvsR7uQhoyTYvKAupfQrRGBFM352Gk=
    golang.org/x/tools@v0.1.13-0.20220812184215-3f9b119300de h1:b68wxF4nfQjj1XTRHtjVjCximbhAwjztuzDEFGU+n9o=
    honnef.co/go/tools@v0.3.2 h1:ytYb4rOqyp1TSa2EPvNVwtPQJctSELKaMyLfqNP4+34=
    mvdan.cc/gofumpt@v0.3.1 h1:avhhrOmv0IuvQVK7fvwV91oFSGAk5/6Po8GXTzICeu8=
    mvdan.cc/xurls/v2@v2.4.0 h1:tzxjVAj+wSBmDcF6zBB7/myTy3gX9xvi8Tyr28AuQgc=
go: go1.17.6
```


### go env

```
GO111MODULE=""on""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/ubuntu/.cache/go-build""
GOENV=""/home/ubuntu/.config/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""-mod=readonly""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/ubuntu/co/backend/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/ubuntu/co/backend/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/home/ubuntu/co/backend/opt/go1.17.6""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/home/ubuntu/co/backend/opt/go1.17.6/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""go1.17.6""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build457205370=/tmp/go-build -gno-record-gcc-switches""

```



# What Happened
I noticed that `go-to-definition` in vscode on a go file was taking a long time, and consistently saw the following log when navigating within a package (specifically, I was using go to definition to navigate within a package. I'm operating within a large monorepo, with some heavily interlinked packages)

```
[Trace - 23:17:36.892 PM] Received response 'textDocument/definition - (213)' in 11214ms.
```

I pulled up the ""Trace Information"" tab in the debug server, and found a log for `textDocument/Definition` RPC. This log looks to consist of `cache.parseGo` and `cache.TypeCheck` events, but many of these events are replicated, seemly indicating that duplicate work is build done. I see multiple packages being parsed many times (up to ~20, looks to be dependent on imports), with all of its files listed underneath
```
0s textDocument/definition 13.862321388s start=""textDocument/definition"" method=""textDocument/definition"" direction=""in"" id=""#20""

    13.862319081s label= status.code=""OK"" 

    74.474µs queued 27.786µs start=""queued""
    178.05µs source.Identifier 13.861909568s start=""source.Identifier""
...
3.12062168s cache.typeCheck 192.827411ms start=""cache.typeCheck"" package=""foo [bar.test]"" 
    3.120790449s cache.parseGo 196.421µs start=""cache.parseGo"" file=""foo/file_a.go"" 
    .... <package files> ...
...
3.590160298s cache.typeCheck 317.260966ms start=""cache.typeCheck"" package=""foo [baz.test]"" 
    3.590357772s cache.parseGo 274.427µs start=""cache.parseGo"" file=""foo/file_a.go"" 
    .... <package files> ...
...
5.043508487s cache.typeCheck 175.931042ms start=""cache.typeCheck"" package=""foo [foo2.test]"" 
    5.492814972s cache.parseGo 351.925µs start=""cache.parseGo"" file=""foo/file_a.go"" 
    .... <package files> ...
...


```

Appears that there's duplicate work being done - I looked through the codebase for these events and found many todos added in  https://github.com/golang/tools/commit/f79f3aac190554ef62f0257555394b31c29f0320. (eg [a](https://github.com/golang/tools/commit/f79f3aac190554ef62f0257555394b31c29f0320#diff-e230acde030eabf6ec5a1c93adfd0517b7d7eca5f5246f383ea510b752f3b703R475) [b](https://github.com/golang/tools/commit/f79f3aac190554ef62f0257555394b31c29f0320#diff-e230acde030eabf6ec5a1c93adfd0517b7d7eca5f5246f383ea510b752f3b703R577)). Is there any planned work to speed up the `cache.typeCheck` and `cache.parseGo` operations? 

Happy to DM the full trace file to someone if that would help!",1,x tools gopls  textdocument definition is slow in large codebase         please answer these questions before submitting your issue  thanks              gopls version       golang org x tools gopls            golang org x tools gopls         yhhoxvi  ilny           github com burntsushi toml                     github com google go cmp                   github com sergi go diff                     golang org x exp typeparams               bpmeczplbleptjve       golang org x mod       dev                 golang org x sync                       golang org x sys                     golang org x text                 golang org x tools                         honnef co go tools                   mvdan cc gofumpt                   mvdan cc xurls           tzxjvaj       go                      go env            on   goarch      gobin     gocache   home ubuntu  cache go build   goenv   home ubuntu  config go env   goexe     goexperiment     goflags   mod readonly   gohostarch      gohostos  linux   goinsecure     gomodcache   home ubuntu co backend go pkg mod   gonoproxy     gonosumdb     goos  linux   gopath   home ubuntu co backend go   goprivate     goproxy     goroot   home ubuntu co backend opt         gosumdb  sum golang org   gotmpdir     gotooldir   home ubuntu co backend opt       pkg tool linux     govcs     goversion          gccgo  gccgo   ar  ar   cc  gcc   cxx  g     cgo enabled      gomod   dev null   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches                  what happened  i noticed that  go to definition  in vscode on a go file was taking a long time  and consistently saw the following log when navigating within a package  specifically  i was using go to definition to navigate within a package  i m operating within a large monorepo  with some heavily interlinked packages            received response  textdocument definition        in            i pulled up the  trace information  tab in the debug server  and found a log for  textdocument definition  rpc  this log looks to consist of  cache parsego  and  cache typecheck  events  but many of these events are replicated  seemly indicating that duplicate work is build done  i see multiple packages being parsed many times  up to     looks to be dependent on imports   with all of its files listed underneath         textdocument definition     start  textdocument definition  method  textdocument definition  direction  in  id                 label  status code  ok              queued     start  queued           source identifier     start  source identifier            cache typecheck     start  cache typecheck  package  foo              cache parsego     start  cache parsego  file  foo file a go                             cache typecheck     start  cache typecheck  package  foo              cache parsego     start  cache parsego  file  foo file a go                             cache typecheck     start  cache typecheck  package  foo              cache parsego     start  cache parsego  file  foo file a go                                    appears that there s duplicate work being done   i looked through the codebase for these events and found many todos added in     eg         is there any planned work to speed up the  cache typecheck  and  cache parsego  operations      happy to dm the full trace file to someone if that would help ,1
70055,9370499340.0,IssuesEvent,2019-04-03 13:36:06,golang/go,https://api.github.com/repos/golang/go,reopened,"x/tools/cmd/gopls: textDocument/rangeFormatting gives error ""ToUTF16Column: point is missing offset""",Documentation gopls,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.12.1 linux/amd64
$ go list -m golang.org/x/tools
golang.org/x/tools v0.0.0-20190328211700-ab21143f2384
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""/home/myitcv/gostuff/src/github.com/myitcv/govim/.bin""
GOCACHE=""/home/myitcv/.cache/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/myitcv/gostuff""
GOPROXY=""""
GORACE=""""
GOROOT=""/home/myitcv/gos""
GOTMPDIR=""""
GOTOOLDIR=""/home/myitcv/gos/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/myitcv/gostuff/src/github.com/myitcv/govim/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build120717318=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

Considering the following [`govim`](https://github.com/myitcv/govim/tree/master/cmd/govim) [`testscript`](https://godoc.org/github.com/rogpeppe/go-internal/testscript) in which I attempt to range-format line numbers 3-5 (inc) in `main.go`:

```
vim ex 'e main.go'
vim ex '3,5GOVIMGoFmt'
vim ex 'noautocmd w'
cmp main.go main.go.golden

-- go.mod --
module mod

-- main.go --
package main

func main(){
fmt.Println(""Hello, world"")
}
-- main.go.golden --
package main

func main() {
	fmt.Println(""Hello, world"")
}
```

I get the error:

```
ToUTF16Column: point is missing offset
```

The params sent were:

```
&protocol.DocumentRangeFormattingParams{
    TextDocument: protocol.TextDocumentIdentifier{URI:""file://$WORK/main.go""},
    Range:        protocol.Range{
        Start: protocol.Position{Line:2, Character:0},
        End:   protocol.Position{Line:5, Character:0},
    },
    Options: protocol.FormattingOptions{},
}
```

### What did you expect to see?

No error.

### What did you see instead?

The above error.

cc @stamblerre @ianthehat ",1.0,"x/tools/cmd/gopls: textDocument/rangeFormatting gives error ""ToUTF16Column: point is missing offset"" - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.12.1 linux/amd64
$ go list -m golang.org/x/tools
golang.org/x/tools v0.0.0-20190328211700-ab21143f2384
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""/home/myitcv/gostuff/src/github.com/myitcv/govim/.bin""
GOCACHE=""/home/myitcv/.cache/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/myitcv/gostuff""
GOPROXY=""""
GORACE=""""
GOROOT=""/home/myitcv/gos""
GOTMPDIR=""""
GOTOOLDIR=""/home/myitcv/gos/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/myitcv/gostuff/src/github.com/myitcv/govim/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build120717318=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

Considering the following [`govim`](https://github.com/myitcv/govim/tree/master/cmd/govim) [`testscript`](https://godoc.org/github.com/rogpeppe/go-internal/testscript) in which I attempt to range-format line numbers 3-5 (inc) in `main.go`:

```
vim ex 'e main.go'
vim ex '3,5GOVIMGoFmt'
vim ex 'noautocmd w'
cmp main.go main.go.golden

-- go.mod --
module mod

-- main.go --
package main

func main(){
fmt.Println(""Hello, world"")
}
-- main.go.golden --
package main

func main() {
	fmt.Println(""Hello, world"")
}
```

I get the error:

```
ToUTF16Column: point is missing offset
```

The params sent were:

```
&protocol.DocumentRangeFormattingParams{
    TextDocument: protocol.TextDocumentIdentifier{URI:""file://$WORK/main.go""},
    Range:        protocol.Range{
        Start: protocol.Position{Line:2, Character:0},
        End:   protocol.Position{Line:5, Character:0},
    },
    Options: protocol.FormattingOptions{},
}
```

### What did you expect to see?

No error.

### What did you see instead?

The above error.

cc @stamblerre @ianthehat ",1,x tools cmd gopls  textdocument rangeformatting gives error     point is missing offset             what version of go are you using   go version            go version  go version       linux      go list  m golang org x tools  golang org x tools                     does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env          go env  output       go env  goarch      gobin   home myitcv gostuff src github com myitcv govim  bin   gocache   home myitcv  cache go build   goexe     goflags     gohostarch      gohostos  linux   goos  linux   gopath   home myitcv gostuff   goproxy     gorace     goroot   home myitcv gos   gotmpdir     gotooldir   home myitcv gos pkg tool linux     gccgo  gccgo   cc  gcc   cxx  g     cgo enabled      gomod   home myitcv gostuff src github com myitcv govim go mod   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches             what did you do     considering the following         in which i attempt to range format line numbers      inc  in  main go           vim ex  e main go   vim ex        vim ex  noautocmd w   cmp main go main go golden       go mod     module mod       main go     package main    func main     fmt println  hello  world          main go golden     package main    func main      	fmt println  hello  world              i get the error             point is missing offset         the params sent were           protocol documentrangeformattingparams       textdocument  protocol textdocumentidentifier uri  file    work main go         range         protocol range           start  protocol position line    character              end    protocol position line    character                  options  protocol formattingoptions                   what did you expect to see     no error         what did you see instead     the above error     cc  stamblerre  ianthehat ,1
19792,11288671797.0,IssuesEvent,2020-01-16 08:28:47,terraform-providers/terraform-provider-aws,https://api.github.com/repos/terraform-providers/terraform-provider-aws,closed,aws_dynamodb_global_table.TABLE_NAME_HERE: ValidationException: One or more parameter values were invalid: 2 validation errors detected: Value 'us-gov-west-1' at 'replicationGroup.1.member.regionName' failed to satisfy constraint: ,needs-triage service/dynamodb,"Hi,
Trying to deploy a DynamoDB Global Table in AWS Gov Cloud, getting the following error:
```bash
	* module.dynamodb.aws_dynamodb_global_table.TABLE1_NAME_HERE: 1 error occurred:
	* aws_dynamodb_global_table.TABLE1_NAME_HERE: ValidationException: One or more parameter values were invalid: 2 validation errors detected: Value 'us-gov-west-1' at 'replicationGroup.1.member.regionName' failed to satisfy constraint: Member must satisfy enum value set: [us-west-1, us-west-2, ap-northeast-1, ap-northeast-2, us-east-1, eu-west-1, ap-southeast-1, us-east-2, eu-west-2, ap-southeast-2, eu-central-1]; Value 'us-gov-east-1' at 'replicationGroup.2.member.regionName' failed to satisfy constraint: Member must satisfy enum value set: [us-west-1, us-west-2, ap-northeast-1, ap-northeast-2, us-east-1, eu-west-1, ap-southeast-1, us-east-2, eu-west-2, ap-southeast-2, eu-central-1]
	status code: 400, request id: REQUEST_ID


	* module.dynamodb.aws_dynamodb_global_table.TABLE2_NAME_HERE: 1 error occurred:
	* aws_dynamodb_global_table.TABLE2_NAME_HERE: ValidationException: One or more parameter values were invalid: 2 validation errors detected: Value 'us-gov-west-1' at 'replicationGroup.1.member.regionName' failed to satisfy constraint: Member must satisfy enum value set: [us-west-1, us-west-2, ap-northeast-1, ap-northeast-2, us-east-1, eu-west-1, ap-southeast-1, us-east-2, eu-west-2, ap-southeast-2, eu-central-1]; Value 'us-gov-east-1' at 'replicationGroup.2.member.regionName' failed to satisfy constraint: Member must satisfy enum value set: [us-west-1, us-west-2, ap-northeast-1, ap-northeast-2, us-east-1, eu-west-1, ap-southeast-1, us-east-2, eu-west-2, ap-southeast-2, eu-central-1]
	status code: 400, request id: REQUEST_ID
```

Terraform 0.11.14
AWS Provider 2.44.0

Searched other issues, could not find something similar.
The global table support was added here https://github.com/terraform-providers/terraform-provider-aws/issues/2482

## Update - this seems to be a AWS limitation
```bash
AWS_DEFAULT_PROFILE=some_gov_profile_name AWS_DEFAULT_REGION=us-gov-west-1 AWS_PROFILE=some_gov_profile_name aws dynamodb create-global-table --global-table-name GLOBAL_TABLE_NAME --replication-group RegionName
=us-gov-east-1 RegionName=us-gov-west-1

An error occurred (ValidationException) when calling the CreateGlobalTable operation: One or more parameter values were invalid: 2 validation errors detected: Value 'us-gov-east-1' at 'replicationGroup.1.member.regionName' failed to satisfy constraint: Member must satisfy enum value set: [us-west-1, us-west-2, ap-northeast-1, ap-northeast-2, us-east-1, eu-west-1, ap-southeast-1, us-east-2, eu-west-2, ap-southeast-2, eu-central-1]; Value 'us-gov-west-1' at 'replicationGroup.2.member.regionName' failed to satisfy constraint: Member must satisfy enum value set: [us-west-1, us-west-2, ap-northeast-1, ap-northeast-2, us-east-1, eu-west-1, ap-southeast-1, us-east-2, eu-west-2, ap-southeast-2, eu-central-1]
```

## Update#2 - AWS are saying that its the AWS API version issue
The `create-global-table` CLI call (and probably the TF provider) are using API version `2017.11.29`, which is not supported in GovCloud (where I'm trying to deploy my app).

## Update#3 - AWS Go SDK does not specify the GovCloud issue
https://docs.aws.amazon.com/sdk-for-go/api/service/dynamodb/#DynamoDB.CreateGlobalTable

Best,
Yarden",1.0,"aws_dynamodb_global_table.TABLE_NAME_HERE: ValidationException: One or more parameter values were invalid: 2 validation errors detected: Value 'us-gov-west-1' at 'replicationGroup.1.member.regionName' failed to satisfy constraint:  - Hi,
Trying to deploy a DynamoDB Global Table in AWS Gov Cloud, getting the following error:
```bash
	* module.dynamodb.aws_dynamodb_global_table.TABLE1_NAME_HERE: 1 error occurred:
	* aws_dynamodb_global_table.TABLE1_NAME_HERE: ValidationException: One or more parameter values were invalid: 2 validation errors detected: Value 'us-gov-west-1' at 'replicationGroup.1.member.regionName' failed to satisfy constraint: Member must satisfy enum value set: [us-west-1, us-west-2, ap-northeast-1, ap-northeast-2, us-east-1, eu-west-1, ap-southeast-1, us-east-2, eu-west-2, ap-southeast-2, eu-central-1]; Value 'us-gov-east-1' at 'replicationGroup.2.member.regionName' failed to satisfy constraint: Member must satisfy enum value set: [us-west-1, us-west-2, ap-northeast-1, ap-northeast-2, us-east-1, eu-west-1, ap-southeast-1, us-east-2, eu-west-2, ap-southeast-2, eu-central-1]
	status code: 400, request id: REQUEST_ID


	* module.dynamodb.aws_dynamodb_global_table.TABLE2_NAME_HERE: 1 error occurred:
	* aws_dynamodb_global_table.TABLE2_NAME_HERE: ValidationException: One or more parameter values were invalid: 2 validation errors detected: Value 'us-gov-west-1' at 'replicationGroup.1.member.regionName' failed to satisfy constraint: Member must satisfy enum value set: [us-west-1, us-west-2, ap-northeast-1, ap-northeast-2, us-east-1, eu-west-1, ap-southeast-1, us-east-2, eu-west-2, ap-southeast-2, eu-central-1]; Value 'us-gov-east-1' at 'replicationGroup.2.member.regionName' failed to satisfy constraint: Member must satisfy enum value set: [us-west-1, us-west-2, ap-northeast-1, ap-northeast-2, us-east-1, eu-west-1, ap-southeast-1, us-east-2, eu-west-2, ap-southeast-2, eu-central-1]
	status code: 400, request id: REQUEST_ID
```

Terraform 0.11.14
AWS Provider 2.44.0

Searched other issues, could not find something similar.
The global table support was added here https://github.com/terraform-providers/terraform-provider-aws/issues/2482

## Update - this seems to be a AWS limitation
```bash
AWS_DEFAULT_PROFILE=some_gov_profile_name AWS_DEFAULT_REGION=us-gov-west-1 AWS_PROFILE=some_gov_profile_name aws dynamodb create-global-table --global-table-name GLOBAL_TABLE_NAME --replication-group RegionName
=us-gov-east-1 RegionName=us-gov-west-1

An error occurred (ValidationException) when calling the CreateGlobalTable operation: One or more parameter values were invalid: 2 validation errors detected: Value 'us-gov-east-1' at 'replicationGroup.1.member.regionName' failed to satisfy constraint: Member must satisfy enum value set: [us-west-1, us-west-2, ap-northeast-1, ap-northeast-2, us-east-1, eu-west-1, ap-southeast-1, us-east-2, eu-west-2, ap-southeast-2, eu-central-1]; Value 'us-gov-west-1' at 'replicationGroup.2.member.regionName' failed to satisfy constraint: Member must satisfy enum value set: [us-west-1, us-west-2, ap-northeast-1, ap-northeast-2, us-east-1, eu-west-1, ap-southeast-1, us-east-2, eu-west-2, ap-southeast-2, eu-central-1]
```

## Update#2 - AWS are saying that its the AWS API version issue
The `create-global-table` CLI call (and probably the TF provider) are using API version `2017.11.29`, which is not supported in GovCloud (where I'm trying to deploy my app).

## Update#3 - AWS Go SDK does not specify the GovCloud issue
https://docs.aws.amazon.com/sdk-for-go/api/service/dynamodb/#DynamoDB.CreateGlobalTable

Best,
Yarden",0,aws dynamodb global table table name here  validationexception  one or more parameter values were invalid    validation errors detected  value  us gov west    at  replicationgroup   member regionname  failed to satisfy constraint     hi   trying to deploy a dynamodb global table in aws gov cloud  getting the following error      bash  	  module dynamodb aws dynamodb global table   name here    error occurred   	  aws dynamodb global table   name here  validationexception  one or more parameter values were invalid    validation errors detected  value  us gov west    at  replicationgroup   member regionname  failed to satisfy constraint  member must satisfy enum value set     value  us gov east    at  replicationgroup   member regionname  failed to satisfy constraint  member must satisfy enum value set     	status code     request id  request id      	  module dynamodb aws dynamodb global table   name here    error occurred   	  aws dynamodb global table   name here  validationexception  one or more parameter values were invalid    validation errors detected  value  us gov west    at  replicationgroup   member regionname  failed to satisfy constraint  member must satisfy enum value set     value  us gov east    at  replicationgroup   member regionname  failed to satisfy constraint  member must satisfy enum value set     	status code     request id  request id         terraform        aws provider          searched other issues  could not find something similar   the global table support was added here         update   this seems to be a aws limitation     bash  aws default profile some gov profile name aws default region us gov west   aws profile some gov profile name aws dynamodb create global table   global table name global table name   replication group regionname   us gov east   regionname us gov west      an error occurred  validationexception  when calling the createglobaltable operation  one or more parameter values were invalid    validation errors detected  value  us gov east    at  replicationgroup   member regionname  failed to satisfy constraint  member must satisfy enum value set     value  us gov west    at  replicationgroup   member regionname  failed to satisfy constraint  member must satisfy enum value set               update     aws are saying that its the aws api version issue  the  create global table  cli call  and probably the tf provider  are using api version          which is not supported in govcloud  where i m trying to deploy my app         update     aws go sdk does not specify the govcloud issue       best   yarden,0
103377,11355142859.0,IssuesEvent,2020-01-24 19:19:29,golang/go,https://api.github.com/repos/golang/go,opened,doc/go1.14: GOINSECURE needs a release note,Documentation release-blocker,"I was reading through https://nullprogram.com/blog/2020/01/21l (via Golang Weekly) and realized that we forgot to add a release note for #32966.

`GOINSECURE` is a nice feature for local development, so we should make sure it is mentioned in the release notes.",1.0,"doc/go1.14: GOINSECURE needs a release note - I was reading through https://nullprogram.com/blog/2020/01/21l (via Golang Weekly) and realized that we forgot to add a release note for #32966.

`GOINSECURE` is a nice feature for local development, so we should make sure it is mentioned in the release notes.",1,doc      goinsecure needs a release note   i was reading through    via golang weekly  and realized that we forgot to add a release note for         goinsecure  is a nice feature for local development  so we should make sure it is mentioned in the release notes ,1
207962,15863590253.0,IssuesEvent,2021-04-08 12:57:34,nens/lizard-management-client,https://api.github.com/repos/nens/lizard-management-client,closed,Alarm forms - Change field names,Test result,"I think the current field titles for ""relative time"" and snoozing are unclear/not ""covering the load"". Of course we want to give them extensive explanation in the sidebar, but the titles should be clearer.

I propose:
- Change ""Use relative data"" to ""Limit to relative period""
- Snoozing: Change ""After breaking threshold"" to ""Trigger after N times"" and ""After no further impact"" to ""Withdraw after N times""

@LirryPinter Do you agree?",1.0,"Alarm forms - Change field names - I think the current field titles for ""relative time"" and snoozing are unclear/not ""covering the load"". Of course we want to give them extensive explanation in the sidebar, but the titles should be clearer.

I propose:
- Change ""Use relative data"" to ""Limit to relative period""
- Snoozing: Change ""After breaking threshold"" to ""Trigger after N times"" and ""After no further impact"" to ""Withdraw after N times""

@LirryPinter Do you agree?",0,alarm forms   change field names   i think the current field titles for  relative time  and snoozing are unclear not  covering the load   of course we want to give them extensive explanation in the sidebar  but the titles should be clearer   i propose    change  use relative data  to  limit to relative period    snoozing  change  after breaking threshold  to  trigger after n times  and  after no further impact  to  withdraw after n times    lirrypinter do you agree ,0
344173,24800577453.0,IssuesEvent,2022-10-24 21:18:10,golang/go,https://api.github.com/repos/golang/go,closed,x/pkgsite: too many users are filing package removal requests,Documentation pkgsite,"Say I mistakenly pushed a git tag on a Go module of mine, and now I can see it on pkg.go.dev. I only know the basics about Go modules, so I am not yet familiar with retractions. From the home page of pkg.go.dev, I find https://pkg.go.dev/about#removing-a-package:

> If you would like to hide versions of a module on pkg.go.dev, as well as from the go command, you should retract them. Retracting a module version involves adding a retract directive to your go.mod file and publishing a new version. See the Go blog post [New module changes in Go 1.16](https://go.dev/blog/go116-module-changes#TOC_5.) and the [modules reference](https://go.dev/ref/mod#go-mod-file-retract) for details.
> 
> If you cannot retract your module, you can [file a request](https://go.dev/s/pkgsite-package-removal) for the pkgsite team to remove your package.

Presumably, this should lead me to publish a module retraction, not to file a request. However, [plenty of requests are filed regularly](https://github.com/golang/go/issues?q=is%3Aissue+pkgsite+removal+request+in%3Atitle). I've always had the suspicion that the majority of those should be fixed with retractions instead, so I engaged with [one of them](https://github.com/golang/go/issues/55342). And indeed I think this particular user wants to use a retraction; they want to entirely take back a v1.0.0 tag from their users, not simply hide the documentation.

Assuming that all of these users are filing issues by following the pkg.go.dev docs as shown above, I think the docs are confusing. They should better clarify that:

1) A retraction is almost always what the user should do. In fact, I struggle to imagine what the site means by ""If you cannot retract your module"". If we have an edge case in mind, I would call it out explicitly. If not, I would remove the alternative entirely.

2) Removing a package from pkg.go.dev only _hides_ the documentation. The Go module and version will still work for `go get pkg@latest` requests, which I think is a pretty common concern amongst users. For example, the particular issue above is about having pushed a v1.0.0 tag when the module is meant to be a v0. The wording should be clearer.

   It's true that the link points to an issue template which explains this in an HTML comment, but by that point the user has already made the choice to not retract. Plus, can we trust the user to read the entire template carefully before filling the form? :)

3) How to retract the latest version in a clean way. https://go.dev/ref/mod does say:

   > To retract a version, a module author should add a retract directive to go.mod, then publish a new version containing that directive.
   > A version containing retractions may retract itself.

   That is, to retract a v1.0.0, it is possible to publish a v1.0.1 which retracts both versions. The user can follow the links to the blog post or docs, but they have to do quite a lot of reading to find the few important sentences.

   In fact, I would remove the link to the blog post, because the link to the modules reference already overlaps with its information. Plus, the example shown in the blog post is rather simple - it does not cover how to retract the latest version, for example.

--

I propose new wording. Lengthier, but hopefully clearer.

> If you would like to hide versions of a module on pkg.go.dev, as well as from the go command, you should retract them. Retracting a module version involves adding a retract directive to your go.mod file and publishing a new version. See the [modules reference](https://go.dev/ref/mod#go-mod-file-retract) for details.
>
> Note that it is possible to retract the latest version of a module; the link above includes an example. Also note that published versions cannot be reused or modified, and this includes retracted versions.
>
> If you cannot retract your module (TODO: why?), you can [file a request](https://go.dev/s/pkgsite-package-removal) for the pkgsite team to hide your package documentation. Note that the package will continue to be available via go get or go install unless its module is retracted.

Note the TODO per the point 1 above.

Also note that I explicitly call out that retracted versions cannot be used again. I think this is a common misunderstanding: inexperienced Go users think that they can remove or retract a Go module or version, to then ""start fresh"" as if that package or version was never published. That is usually not true. Perhaps this should also be called out in https://go.dev/ref/mod#go-mod-file-retract.

cc @bcmills @seankhliao @julieqiu ",1.0,"x/pkgsite: too many users are filing package removal requests - Say I mistakenly pushed a git tag on a Go module of mine, and now I can see it on pkg.go.dev. I only know the basics about Go modules, so I am not yet familiar with retractions. From the home page of pkg.go.dev, I find https://pkg.go.dev/about#removing-a-package:

> If you would like to hide versions of a module on pkg.go.dev, as well as from the go command, you should retract them. Retracting a module version involves adding a retract directive to your go.mod file and publishing a new version. See the Go blog post [New module changes in Go 1.16](https://go.dev/blog/go116-module-changes#TOC_5.) and the [modules reference](https://go.dev/ref/mod#go-mod-file-retract) for details.
> 
> If you cannot retract your module, you can [file a request](https://go.dev/s/pkgsite-package-removal) for the pkgsite team to remove your package.

Presumably, this should lead me to publish a module retraction, not to file a request. However, [plenty of requests are filed regularly](https://github.com/golang/go/issues?q=is%3Aissue+pkgsite+removal+request+in%3Atitle). I've always had the suspicion that the majority of those should be fixed with retractions instead, so I engaged with [one of them](https://github.com/golang/go/issues/55342). And indeed I think this particular user wants to use a retraction; they want to entirely take back a v1.0.0 tag from their users, not simply hide the documentation.

Assuming that all of these users are filing issues by following the pkg.go.dev docs as shown above, I think the docs are confusing. They should better clarify that:

1) A retraction is almost always what the user should do. In fact, I struggle to imagine what the site means by ""If you cannot retract your module"". If we have an edge case in mind, I would call it out explicitly. If not, I would remove the alternative entirely.

2) Removing a package from pkg.go.dev only _hides_ the documentation. The Go module and version will still work for `go get pkg@latest` requests, which I think is a pretty common concern amongst users. For example, the particular issue above is about having pushed a v1.0.0 tag when the module is meant to be a v0. The wording should be clearer.

   It's true that the link points to an issue template which explains this in an HTML comment, but by that point the user has already made the choice to not retract. Plus, can we trust the user to read the entire template carefully before filling the form? :)

3) How to retract the latest version in a clean way. https://go.dev/ref/mod does say:

   > To retract a version, a module author should add a retract directive to go.mod, then publish a new version containing that directive.
   > A version containing retractions may retract itself.

   That is, to retract a v1.0.0, it is possible to publish a v1.0.1 which retracts both versions. The user can follow the links to the blog post or docs, but they have to do quite a lot of reading to find the few important sentences.

   In fact, I would remove the link to the blog post, because the link to the modules reference already overlaps with its information. Plus, the example shown in the blog post is rather simple - it does not cover how to retract the latest version, for example.

--

I propose new wording. Lengthier, but hopefully clearer.

> If you would like to hide versions of a module on pkg.go.dev, as well as from the go command, you should retract them. Retracting a module version involves adding a retract directive to your go.mod file and publishing a new version. See the [modules reference](https://go.dev/ref/mod#go-mod-file-retract) for details.
>
> Note that it is possible to retract the latest version of a module; the link above includes an example. Also note that published versions cannot be reused or modified, and this includes retracted versions.
>
> If you cannot retract your module (TODO: why?), you can [file a request](https://go.dev/s/pkgsite-package-removal) for the pkgsite team to hide your package documentation. Note that the package will continue to be available via go get or go install unless its module is retracted.

Note the TODO per the point 1 above.

Also note that I explicitly call out that retracted versions cannot be used again. I think this is a common misunderstanding: inexperienced Go users think that they can remove or retract a Go module or version, to then ""start fresh"" as if that package or version was never published. That is usually not true. Perhaps this should also be called out in https://go.dev/ref/mod#go-mod-file-retract.

cc @bcmills @seankhliao @julieqiu ",1,x pkgsite  too many users are filing package removal requests   say i mistakenly pushed a git tag on a go module of mine  and now i can see it on pkg go dev  i only know the basics about go modules  so i am not yet familiar with retractions  from the home page of pkg go dev  i find        if you would like to hide versions of a module on pkg go dev  as well as from the go command  you should retract them  retracting a module version involves adding a retract directive to your go mod file and publishing a new version  see the go blog post     and the     for details         if you cannot retract your module  you can     for the pkgsite team to remove your package     presumably  this should lead me to publish a module retraction  not to file a request  however      i ve always had the suspicion that the majority of those should be fixed with retractions instead  so i engaged with     and indeed i think this particular user wants to use a retraction  they want to entirely take back a       tag from their users  not simply hide the documentation     assuming that all of these users are filing issues by following the pkg go dev docs as shown above  i think the docs are confusing  they should better clarify that        a retraction is almost always what the user should do  in fact  i struggle to imagine what the site means by  if you cannot retract your module   if we have an edge case in mind  i would call it out explicitly  if not  i would remove the alternative entirely        removing a package from pkg go dev only  hides  the documentation  the go module and version will still work for  go get pkg latest  requests  which i think is a pretty common concern amongst users  for example  the particular issue above is about having pushed a       tag when the module is meant to be a    the wording should be clearer        it s true that the link points to an issue template which explains this in an html comment  but by that point the user has already made the choice to not retract  plus  can we trust the user to read the entire template carefully before filling the form           how to retract the latest version in a clean way    does say          to retract a version  a module author should add a retract directive to go mod  then publish a new version containing that directive        a version containing retractions may retract itself        that is  to retract a        it is possible to publish a       which retracts both versions  the user can follow the links to the blog post or docs  but they have to do quite a lot of reading to find the few important sentences        in fact  i would remove the link to the blog post  because the link to the modules reference already overlaps with its information  plus  the example shown in the blog post is rather simple   it does not cover how to retract the latest version  for example           i propose new wording  lengthier  but hopefully clearer       if you would like to hide versions of a module on pkg go dev  as well as from the go command  you should retract them  retracting a module version involves adding a retract directive to your go mod file and publishing a new version  see the     for details        note that it is possible to retract the latest version of a module  the link above includes an example  also note that published versions cannot be reused or modified  and this includes retracted versions        if you cannot retract your module  todo  why    you can     for the pkgsite team to hide your package documentation  note that the package will continue to be available via go get or go install unless its module is retracted     note the todo per the point   above     also note that i explicitly call out that retracted versions cannot be used again  i think this is a common misunderstanding  inexperienced go users think that they can remove or retract a go module or version  to then  start fresh  as if that package or version was never published  that is usually not true  perhaps this should also be called out in      cc  bcmills  seankhliao  julieqiu ,1
48764,7456895635.0,IssuesEvent,2018-03-30 00:20:06,golang/go,https://api.github.com/repos/golang/go,closed,fmt: document the behaviour of %p on slices,Documentation,"I was surprised by the following program's output:

```go
package main

import (
	""fmt""
)

func main() {
	foo := make([]int, 0, 1)
	fmt.Printf(""same: %p\n"", foo)

	foo = append(foo, 0)
	fmt.Printf(""same: %p\n"", foo)

	foo = append(foo, 0)
	fmt.Printf(""different: %p\n"", foo)
}
```

Example output:

```
same: 0xc420018060
same: 0xc420018060
different: 0xc420018070
```

I was expecting an error because there is no documentation regarding `%p` with slices in https://golang.org/pkg/fmt/ but it works fine.

I was surprised by the output as the printed address changed when the underlying array of the slice was modified. This is the expected behaviour because fmt is using the reflect package's Pointer() method on the slice, which will return the address of the first element of the slice. See https://github.com/golang/go/blob/38c561cb2caa8019e44059e2be71c909ceef30a6/src/reflect/value.go#L1267-L1269

There should be some documentation regarding this behaviour because it is unexpected imo.",1.0,"fmt: document the behaviour of %p on slices - I was surprised by the following program's output:

```go
package main

import (
	""fmt""
)

func main() {
	foo := make([]int, 0, 1)
	fmt.Printf(""same: %p\n"", foo)

	foo = append(foo, 0)
	fmt.Printf(""same: %p\n"", foo)

	foo = append(foo, 0)
	fmt.Printf(""different: %p\n"", foo)
}
```

Example output:

```
same: 0xc420018060
same: 0xc420018060
different: 0xc420018070
```

I was expecting an error because there is no documentation regarding `%p` with slices in https://golang.org/pkg/fmt/ but it works fine.

I was surprised by the output as the printed address changed when the underlying array of the slice was modified. This is the expected behaviour because fmt is using the reflect package's Pointer() method on the slice, which will return the address of the first element of the slice. See https://github.com/golang/go/blob/38c561cb2caa8019e44059e2be71c909ceef30a6/src/reflect/value.go#L1267-L1269

There should be some documentation regarding this behaviour because it is unexpected imo.",1,fmt  document the behaviour of  p on slices   i was surprised by the following program s output        go  package main    import    	 fmt        func main      	foo    make  int         	fmt printf  same   p n   foo     	foo   append foo      	fmt printf  same   p n   foo     	foo   append foo      	fmt printf  different   p n   foo             example output          same     same     different            i was expecting an error because there is no documentation regarding   p  with slices in   but it works fine     i was surprised by the output as the printed address changed when the underlying array of the slice was modified  this is the expected behaviour because fmt is using the reflect package s pointer   method on the slice  which will return the address of the first element of the slice  see      there should be some documentation regarding this behaviour because it is unexpected imo ,1
654341,21648431154.0,IssuesEvent,2022-05-06 06:34:03,AbsaOSS/enceladus,https://api.github.com/repos/AbsaOSS/enceladus,closed,Menas fine-tuning for cloud,Epic priority: undecided,"## Background
POC behind, make it final

## Goal
After making Menas running in cloud, some fine-tuning will be required

",1.0,"Menas fine-tuning for cloud - ## Background
POC behind, make it final

## Goal
After making Menas running in cloud, some fine-tuning will be required

",0,menas fine tuning for cloud      background poc behind  make it final     goal after making menas running in cloud  some fine tuning will be required  ,0
7321,3535728771.0,IssuesEvent,2016-01-16 18:56:13,marthjod/jeux,https://api.github.com/repos/marthjod/jeux,opened,Remove `previousRoundId` from code and DB schema,code enhancement,"Only roundId remains somewhat necessary (for sorting purposes). Since a round switch is no longer a round switch but carried out on a per-group basis, previous round info is no longer needed.",1.0,"Remove `previousRoundId` from code and DB schema - Only roundId remains somewhat necessary (for sorting purposes). Since a round switch is no longer a round switch but carried out on a per-group basis, previous round info is no longer needed.",0,remove  previousroundid  from code and db schema   only roundid remains somewhat necessary  for sorting purposes   since a round switch is no longer a round switch but carried out on a per group basis  previous round info is no longer needed ,0
85338,10436715485.0,IssuesEvent,2019-09-17 20:12:28,golang/go,https://api.github.com/repos/golang/go,closed,time: add examples for microseconds and milliseconds methods,Documentation NeedsFix,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.13 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/ps/.cache/go-build""
GOENV=""/home/ps/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/ps/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/ps/Downloads/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build046123357=/tmp/go-build -gno-record-gcc-switches""

</pre></details>

### What did you do?
Visited https://tip.golang.org/pkg/time/
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->



### What did you expect to see?

Testable examples for Microseconds() and Milliseconds() methods.

### What did you see instead?

There were not testable example for these 2 methods.
",1.0,"time: add examples for microseconds and milliseconds methods - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.13 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/ps/.cache/go-build""
GOENV=""/home/ps/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/ps/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/ps/Downloads/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build046123357=/tmp/go-build -gno-record-gcc-switches""

</pre></details>

### What did you do?
Visited https://tip.golang.org/pkg/time/
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->



### What did you expect to see?

Testable examples for Microseconds() and Milliseconds() methods.

### What did you see instead?

There were not testable example for these 2 methods.
",1,time  add examples for microseconds and milliseconds methods            what version of go are you using   go version            go version  go version     linux             does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   home ps  cache go build   goenv   home ps  config go env   goexe     goflags     gohostarch      gohostos  linux   gonoproxy     gonosumdb     goos  linux   gopath   home ps go   goprivate     goproxy     goroot   usr local go   gosumdb  sum golang org   gotmpdir     gotooldir   usr local go pkg tool linux     gccgo  gccgo   ar  ar   cc  gcc   cxx  g     cgo enabled      gomod   home ps downloads go mod   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches               what did you do   visited          if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best                  what did you expect to see     testable examples for microseconds   and milliseconds   methods         what did you see instead     there were not testable example for these   methods   ,1
123285,12196303518.0,IssuesEvent,2020-04-29 18:51:02,golang/go,https://api.github.com/repos/golang/go,closed,crypto/x509/pkix: clarify docs for ExtraNames field in pkix.Name,Documentation NeedsFix,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.12.6 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes.


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/jrittner/.cache/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/jrittner/go-workspace""
GOPROXY=""""
GORACE=""""
GOROOT=""/home/jrittner/go""
GOTMPDIR=""""
GOTOOLDIR=""/home/jrittner/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build691331496=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

I unmarshaled a pkix.Name containing a custom ExtraName, and printed it out.

https://play.golang.org/p/BUS-NDgjPLI

### What did you expect to see?

1.2.3.4=#130673616d706c65,CN=foobar

### What did you see instead?

CN=foobar",1.0,"crypto/x509/pkix: clarify docs for ExtraNames field in pkix.Name - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.12.6 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes.


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/jrittner/.cache/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/jrittner/go-workspace""
GOPROXY=""""
GORACE=""""
GOROOT=""/home/jrittner/go""
GOTMPDIR=""""
GOTOOLDIR=""/home/jrittner/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build691331496=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

I unmarshaled a pkix.Name containing a custom ExtraName, and printed it out.

https://play.golang.org/p/BUS-NDgjPLI

### What did you expect to see?

1.2.3.4=#130673616d706c65,CN=foobar

### What did you see instead?

CN=foobar",1,crypto   pkix  clarify docs for extranames field in pkix name            what version of go are you using   go version            go version  go version       linux             does this issue reproduce with the latest release   yes           what operating system and processor architecture are you using   go env          go env  output       go env  goarch      gobin     gocache   home jrittner  cache go build   goexe     goflags     gohostarch      gohostos  linux   goos  linux   gopath   home jrittner go workspace   goproxy     gorace     goroot   home jrittner go   gotmpdir     gotooldir   home jrittner go pkg tool linux     gccgo  gccgo   cc  gcc   cxx  g     cgo enabled      gomod     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches             what did you do     i unmarshaled a pkix name containing a custom extraname  and printed it out              what did you expect to see                cn foobar        what did you see instead     cn foobar,1
567406,16857865739.0,IssuesEvent,2021-06-21 09:09:45,threefoldfoundation/home,https://api.github.com/repos/threefoldfoundation/home,closed,Speed of our websites,priority_minor,"We are getting feedback that our websites are loading very slowly, especially where internet is rather slow.

Can we please take a look and see what can be done to improve the speed?",1.0,"Speed of our websites - We are getting feedback that our websites are loading very slowly, especially where internet is rather slow.

Can we please take a look and see what can be done to improve the speed?",0,speed of our websites   we are getting feedback that our websites are loading very slowly  especially where internet is rather slow     can we please take a look and see what can be done to improve the speed ,0
104993,22796254450.0,IssuesEvent,2022-07-10 19:11:07,octomation/maintainer,https://api.github.com/repos/octomation/maintainer,closed,github: contribution: suggest doesn't work on last week with Sunday,kind: bug difficulty: medium level: normal scope: code,"```bash
maintainer github contribution suggest --delta 2022-07-10
 Day / Week    #51    #52    #1    #2    #3
------------- ------ ------ ----- ----- ----
 Sunday         -      -      -     -    -
 Monday         -      -      -     -    -
 Tuesday        -      -      -     -    -
 Wednesday      -      -      -     -    -
 Thursday       -      -      -     -    -
 Friday         -      -      -     -    -
 Saturday       -      -      -     -    -
------------- ------ ------ ----- ----- ----
 Suggestion is 0001-01-01: -106751d, 0 -> 0
```

There is no 2022-07-10.",1.0,"github: contribution: suggest doesn't work on last week with Sunday - ```bash
maintainer github contribution suggest --delta 2022-07-10
 Day / Week    #51    #52    #1    #2    #3
------------- ------ ------ ----- ----- ----
 Sunday         -      -      -     -    -
 Monday         -      -      -     -    -
 Tuesday        -      -      -     -    -
 Wednesday      -      -      -     -    -
 Thursday       -      -      -     -    -
 Friday         -      -      -     -    -
 Saturday       -      -      -     -    -
------------- ------ ------ ----- ----- ----
 Suggestion is 0001-01-01: -106751d, 0 -> 0
```

There is no 2022-07-10.",0,github  contribution  suggest doesn t work on last week with sunday      bash  maintainer github contribution suggest   delta         day   week                                                                               sunday                                      monday                                      tuesday                                     wednesday                                   thursday                                    friday                                      saturday                                                                                  suggestion is                           there is no       ,0
21444,6151267148.0,IssuesEvent,2017-06-28 01:46:55,IQSS/dataverse,https://api.github.com/repos/IQSS/dataverse,closed,Shibboleth Groups: arbitrary attributes and regex support,Component: Account & User Info Component: API Help Wanted: Code Mentor: pdurbin Type: Feature,"In #1401 I implemented institution-wide Shibboleth groups (i.e. ""you logged in with your Harvard account"") which is a decent start (though we want the creation to be automated in #1403) but what we **really** want is for people installing Dataverse to be able create a group based on **any arbitrary Shibboleth attribute** (""[eduPersonScopedAffiliation](https://docs.google.com/a/harvard.edu/document/d/1Rk1MqclTz4LpVxfzZJc2dWRaCRVNbO6n_HuAhgwyEII/edit?usp=sharing)"", ""[Organization](https://github.com/IQSS/dataverse/issues/1401#issuecomment-73018520)"", whatever). Also, rather than an exact string match, we want to support **regular expressions**.
",1.0,"Shibboleth Groups: arbitrary attributes and regex support - In #1401 I implemented institution-wide Shibboleth groups (i.e. ""you logged in with your Harvard account"") which is a decent start (though we want the creation to be automated in #1403) but what we **really** want is for people installing Dataverse to be able create a group based on **any arbitrary Shibboleth attribute** (""[eduPersonScopedAffiliation](https://docs.google.com/a/harvard.edu/document/d/1Rk1MqclTz4LpVxfzZJc2dWRaCRVNbO6n_HuAhgwyEII/edit?usp=sharing)"", ""[Organization](https://github.com/IQSS/dataverse/issues/1401#issuecomment-73018520)"", whatever). Also, rather than an exact string match, we want to support **regular expressions**.
",0,shibboleth groups  arbitrary attributes and regex support   in    i implemented institution wide shibboleth groups  i e   you logged in with your harvard account   which is a decent start  though we want the creation to be automated in     but what we   really   want is for people installing dataverse to be able create a group based on   any arbitrary shibboleth attribute              whatever   also  rather than an exact string match  we want to support   regular expressions    ,0
25480,5168404704.0,IssuesEvent,2017-01-17 21:29:48,golang/go,https://api.github.com/repos/golang/go,closed,"README.md: outdated install instructions, GOROOT setting is too prominent",Documentation NeedsFix,"CL c497c9ea4bbe90833ee0bb8660fe91b8f17adee7 updated the installation instructions in `doc/install.html` to clarify that GOROOT should only be set when using a custom install path. This fixed #6613 (doc: clarify that GOROOT is only necessary for non-standard install locations), but the `README.md` file (the one you see when you visit github.com/golang/go) was not updated, and the **Binary distribution** section still starts like this:

> If you have just untarred a binary Go distribution, you need to set the environment variable $GOROOT

which is not ideal.",1.0,"README.md: outdated install instructions, GOROOT setting is too prominent - CL c497c9ea4bbe90833ee0bb8660fe91b8f17adee7 updated the installation instructions in `doc/install.html` to clarify that GOROOT should only be set when using a custom install path. This fixed #6613 (doc: clarify that GOROOT is only necessary for non-standard install locations), but the `README.md` file (the one you see when you visit github.com/golang/go) was not updated, and the **Binary distribution** section still starts like this:

> If you have just untarred a binary Go distribution, you need to set the environment variable $GOROOT

which is not ideal.",1,readme md  outdated install instructions  goroot setting is too prominent   cl   updated the installation instructions in  doc install html  to clarify that goroot should only be set when using a custom install path  this fixed     doc  clarify that goroot is only necessary for non standard install locations   but the  readme md  file  the one you see when you visit github com golang go  was not updated  and the   binary distribution   section still starts like this       if you have just untarred a binary go distribution  you need to set the environment variable  goroot    which is not ideal ,1
73559,9670579630.0,IssuesEvent,2019-05-21 20:16:47,golang/go,https://api.github.com/repos/golang/go,closed,"math/bits: guarantee Add, Sub, Mul, RotateLeft, ReverseBytes to be constant-time operations",Documentation NeedsFix Proposal Proposal-Accepted,"I'm a heavy non-crypto user of `bits.*` and I'm afraid changes like #31229 will effect my performance. One way of keeping crypto people happy and users like me would be to have separate functions for both non-constant time and constant time addition, multiplication, ...

In the issue above I was reminded that the change affects only the fallbacks. I'm afraid promising that the fallbacks are constant time will later lead to constant time native implementations which could very well be slower than their non-constant time alternatives. For example, platforms which don't support carry flag are RISC-V and WebAssembly and it could happened that ""a branch works out better"" [1].

[1] https://gmplib.org/manual/Assembly-Carry-Propagation.html",1.0,"math/bits: guarantee Add, Sub, Mul, RotateLeft, ReverseBytes to be constant-time operations - I'm a heavy non-crypto user of `bits.*` and I'm afraid changes like #31229 will effect my performance. One way of keeping crypto people happy and users like me would be to have separate functions for both non-constant time and constant time addition, multiplication, ...

In the issue above I was reminded that the change affects only the fallbacks. I'm afraid promising that the fallbacks are constant time will later lead to constant time native implementations which could very well be slower than their non-constant time alternatives. For example, platforms which don't support carry flag are RISC-V and WebAssembly and it could happened that ""a branch works out better"" [1].

[1] https://gmplib.org/manual/Assembly-Carry-Propagation.html",1,math bits  guarantee add  sub  mul  rotateleft  reversebytes to be constant time operations   i m a heavy non crypto user of  bits    and i m afraid changes like    will effect my performance  one way of keeping crypto people happy and users like me would be to have separate functions for both non constant time and constant time addition  multiplication         in the issue above i was reminded that the change affects only the fallbacks  i m afraid promising that the fallbacks are constant time will later lead to constant time native implementations which could very well be slower than their non constant time alternatives  for example  platforms which don t support carry flag are risc v and webassembly and it could happened that  a branch works out better           ,1
140502,11348986311.0,IssuesEvent,2020-01-24 02:40:32,kubernetes-sigs/azuredisk-csi-driver,https://api.github.com/repos/kubernetes-sigs/azuredisk-csi-driver,opened,Add an AAD enabled e2e test config,help wanted kind/test,"**Is your feature request related to a problem? Please describe.**
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->

**Describe the solution you'd like in detail**
<!-- A clear and concise description of what you want to happen. -->

**Describe alternatives you've considered**
<!-- A clear and concise description of any alternative solutions or features you've considered. -->

**Additional context**
<!-- Add any other context or screenshots about the feature request here. -->

cc @weinong",1.0,"Add an AAD enabled e2e test config - **Is your feature request related to a problem? Please describe.**
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->

**Describe the solution you'd like in detail**
<!-- A clear and concise description of what you want to happen. -->

**Describe alternatives you've considered**
<!-- A clear and concise description of any alternative solutions or features you've considered. -->

**Additional context**
<!-- Add any other context or screenshots about the feature request here. -->

cc @weinong",0,add an aad enabled   test config     is your feature request related to a problem  please describe            describe the solution you d like in detail           describe alternatives you ve considered           additional context         cc  weinong,0
162669,13894720421.0,IssuesEvent,2020-10-19 15:00:31,golang/go,https://api.github.com/repos/golang/go,closed,crypto/hmac: detect reuse of hash.Hash value,Documentation NeedsFix,"Good time of the day, 

with go 1.15 release it seems there is some regression issue introduced with respect to `crypto/hmac` package. 

Was troubleshooting https://github.com/dvsekhvalnov/jose2go/issues/26 and found that `hmac.Reset()` is no longer behave same way as it was before (at least when called first), crafted minimal test case:

```go
package main

import (
	""crypto/hmac""
	""crypto/sha256""
	""fmt""
	""hash""
)

func main() {
	sha := sha256.New()
	hmac := hmac.New(func() hash.Hash { return sha }, []byte(""anything""))

	hmac.Reset()        // if you try to comment / uncomment that line, go 1.15 will produce different results
	hmac.Write([]byte(""salt""))

	test := hmac.Sum(nil)

	fmt.Printf(""test = %v\n"", test)
}
```
Is it producing output:

1. `[169 238 50 31 23 163 57 12 228 112 77 219 51 95 12 6 185 17 156 244 116 243 186 227 89 79 64 19 227 242 86 186]` on go v1.15
2. `[213 21 105 177 57 151 62 247 23 137 16 75 59 26 241 187 229 148 88 219 30 222 223 77 186 120 81 74 247 237 232 66]` on go v.14 and below

, more over toggling leading `hmac.Reset()` will produce different results with 1.15 vs. previous versions.

It seems change was introduced by https://github.com/golang/go/commit/97240d546c3ae54871c7c196e504e4a0a06faf87
So will tag @magical  and @FiloSottile here.

Honestly i don't know may be calling `hmac.Reset` before everything else is not sane idea, but it's not documented anywhere and clearly was behaving differently before.

Thank you.",1.0,"crypto/hmac: detect reuse of hash.Hash value - Good time of the day, 

with go 1.15 release it seems there is some regression issue introduced with respect to `crypto/hmac` package. 

Was troubleshooting https://github.com/dvsekhvalnov/jose2go/issues/26 and found that `hmac.Reset()` is no longer behave same way as it was before (at least when called first), crafted minimal test case:

```go
package main

import (
	""crypto/hmac""
	""crypto/sha256""
	""fmt""
	""hash""
)

func main() {
	sha := sha256.New()
	hmac := hmac.New(func() hash.Hash { return sha }, []byte(""anything""))

	hmac.Reset()        // if you try to comment / uncomment that line, go 1.15 will produce different results
	hmac.Write([]byte(""salt""))

	test := hmac.Sum(nil)

	fmt.Printf(""test = %v\n"", test)
}
```
Is it producing output:

1. `[169 238 50 31 23 163 57 12 228 112 77 219 51 95 12 6 185 17 156 244 116 243 186 227 89 79 64 19 227 242 86 186]` on go v1.15
2. `[213 21 105 177 57 151 62 247 23 137 16 75 59 26 241 187 229 148 88 219 30 222 223 77 186 120 81 74 247 237 232 66]` on go v.14 and below

, more over toggling leading `hmac.Reset()` will produce different results with 1.15 vs. previous versions.

It seems change was introduced by https://github.com/golang/go/commit/97240d546c3ae54871c7c196e504e4a0a06faf87
So will tag @magical  and @FiloSottile here.

Honestly i don't know may be calling `hmac.Reset` before everything else is not sane idea, but it's not documented anywhere and clearly was behaving differently before.

Thank you.",1,crypto hmac  detect reuse of hash hash value   good time of the day      with go     release it seems there is some regression issue introduced with respect to  crypto hmac  package      was troubleshooting   and found that  hmac reset    is no longer behave same way as it was before  at least when called first   crafted minimal test case        go  package main    import    	 crypto hmac   	 crypto     	 fmt   	 hash        func main      	sha      new    	hmac    hmac new func   hash hash   return sha     byte  anything       	hmac reset             if you try to comment   uncomment that line  go     will produce different results  	hmac write  byte  salt       	test    hmac sum nil     	fmt printf  test    v n   test           is it producing output            on go             on go v   and below      more over toggling leading  hmac reset    will produce different results with     vs  previous versions     it seems change was introduced by    so will tag  magical  and  filosottile here     honestly i don t know may be calling  hmac reset  before everything else is not sane idea  but it s not documented anywhere and clearly was behaving differently before     thank you ,1
123335,12196996575.0,IssuesEvent,2020-04-29 19:59:24,golang/go,https://api.github.com/repos/golang/go,closed,"strings, bytes: divergent documentation for FieldsFunc functions",Documentation NeedsFix,"### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14.2 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What did you do?

Read the documentation for [`strings.FieldsFunc`](https://golang.org/pkg/strings/#FieldsFunc)

### What did you see?

I see that the documentation is out of date with respect to the following note.

> FieldsFunc makes no guarantees about the order in which it calls f(c). If f does
not return consistent results for a given c, FieldsFunc may crash.

This was appropriate when `FieldsForFunc` was using a two-pass logic. However, when the function was optimized to address #19789, this note is not correct anymore. The new implementation does only one-pass over the input. Hence, we can safely remove this note.
",1.0,"strings, bytes: divergent documentation for FieldsFunc functions - ### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14.2 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What did you do?

Read the documentation for [`strings.FieldsFunc`](https://golang.org/pkg/strings/#FieldsFunc)

### What did you see?

I see that the documentation is out of date with respect to the following note.

> FieldsFunc makes no guarantees about the order in which it calls f(c). If f does
not return consistent results for a given c, FieldsFunc may crash.

This was appropriate when `FieldsForFunc` was using a two-pass logic. However, when the function was optimized to address #19789, this note is not correct anymore. The new implementation does only one-pass over the input. Hence, we can safely remove this note.
",1,strings  bytes  divergent documentation for fieldsfunc functions       what version of go are you using   go version            go version  go version       linux             does this issue reproduce with the latest release     yes        what did you do     read the documentation for            what did you see     i see that the documentation is out of date with respect to the following note       fieldsfunc makes no guarantees about the order in which it calls f c   if f does  not return consistent results for a given c  fieldsfunc may crash     this was appropriate when  fieldsforfunc  was using a two pass logic  however  when the function was optimized to address     this note is not correct anymore  the new implementation does only one pass over the input  hence  we can safely remove this note   ,1
39167,10311076581.0,IssuesEvent,2019-08-29 16:29:01,dotnet/docs,https://api.github.com/repos/dotnet/docs,closed,Abridged Reference: Operators / other operators and tokens,:books: Area - C# Guide :building_construction: content model P1,"These don't fit any group, and should have a single page for each operator.

- `?` `:` (conditional operator). Somehow, it feels out of tune with the logical operators.
- `??` (null coalescing). It also feels not in the logical operations group. Most probably, it's because I limit logical operations to those on `bool` operands.
- `+`, `+=` (string concatenation and delegate combination)
- `-`, `-=` (delegate removal)
- `::` (namespace alias qualifier)
- `nameof`
- `sizeof`
- `await`
- `new` operator
- `stackalloc` operator
- `=>` (lambda declaration)

Sub-tasks are:

- [ ] Create the new articles
- [ ] Search for existing issues on content being migrated and consolidated. This is a good opportunity to fix those.
- [ ] Redirect existing content to the new articles.
- [ ] Remove old articles.
- [ ] Update all links in the .NET Content
",1.0,"Abridged Reference: Operators / other operators and tokens - These don't fit any group, and should have a single page for each operator.

- `?` `:` (conditional operator). Somehow, it feels out of tune with the logical operators.
- `??` (null coalescing). It also feels not in the logical operations group. Most probably, it's because I limit logical operations to those on `bool` operands.
- `+`, `+=` (string concatenation and delegate combination)
- `-`, `-=` (delegate removal)
- `::` (namespace alias qualifier)
- `nameof`
- `sizeof`
- `await`
- `new` operator
- `stackalloc` operator
- `=>` (lambda declaration)

Sub-tasks are:

- [ ] Create the new articles
- [ ] Search for existing issues on content being migrated and consolidated. This is a good opportunity to fix those.
- [ ] Redirect existing content to the new articles.
- [ ] Remove old articles.
- [ ] Update all links in the .NET Content
",0,abridged reference  operators   other operators and tokens   these don t fit any group  and should have a single page for each operator                conditional operator   somehow  it feels out of tune with the logical operators           null coalescing   it also feels not in the logical operations group  most probably  it s because i limit logical operations to those on  bool  operands                string concatenation and delegate combination                delegate removal           namespace alias qualifier      nameof      sizeof      await      new  operator     stackalloc  operator          lambda declaration     sub tasks are         create the new articles      search for existing issues on content being migrated and consolidated  this is a good opportunity to fix those       redirect existing content to the new articles       remove old articles       update all links in the  net content  ,0
40196,6803271050.0,IssuesEvent,2017-11-02 23:51:53,golang/go,https://api.github.com/repos/golang/go,closed,net/http: clarify whether Requests can be reused,Documentation,"Re-using requests is currently unreliable.

If that's intended, then I think it should be documented. If not intended, then I can provide steps to reproduce.",1.0,"net/http: clarify whether Requests can be reused - Re-using requests is currently unreliable.

If that's intended, then I think it should be documented. If not intended, then I can provide steps to reproduce.",1,net http  clarify whether requests can be reused   re using requests is currently unreliable     if that s intended  then i think it should be documented  if not intended  then i can provide steps to reproduce ,1
14630,3870275812.0,IssuesEvent,2016-04-11 02:06:33,golang/go,https://api.github.com/repos/golang/go,opened,net: use IPv4/IPv6 reserved address blocks for documentation,Documentation,"There are reserved address blocks for documentation; https://tools.ietf.org/html/rfc5737 and https://tools.ietf.org/html/rfc3849. It'd be better to use them for documentation updates.

- IPv4 address block for doc: 192.0.2.0/24
- IPv6 address block for doc: 2001:db8::/32 (also see https://tools.ietf.org/html/rfc5952)",1.0,"net: use IPv4/IPv6 reserved address blocks for documentation - There are reserved address blocks for documentation; https://tools.ietf.org/html/rfc5737 and https://tools.ietf.org/html/rfc3849. It'd be better to use them for documentation updates.

- IPv4 address block for doc: 192.0.2.0/24
- IPv6 address block for doc: 2001:db8::/32 (also see https://tools.ietf.org/html/rfc5952)",1,net  use     reserved address blocks for documentation   there are reserved address blocks for documentation    and   it d be better to use them for documentation updates         address block for doc                 address block for doc           also see  ,1
3404,2762330882.0,IssuesEvent,2015-04-28 22:00:15,golang/go,https://api.github.com/repos/golang/go,closed,net/http: PostForm docs should mention PATCH method,Documentation,"The `net/http` parses the request body for the PATCH HTTP method [for quite some time now](https://codereview.appspot.com/70990044).
I think the docs should mention that `PostForm` is available not only for POST and PUT but also for PATCH, that users don't need to dig into the code to discover that.
gov1.4.1
",1.0,"net/http: PostForm docs should mention PATCH method - The `net/http` parses the request body for the PATCH HTTP method [for quite some time now](https://codereview.appspot.com/70990044).
I think the docs should mention that `PostForm` is available not only for POST and PUT but also for PATCH, that users don't need to dig into the code to discover that.
gov1.4.1
",1,net http  postform docs should mention patch method   the  net http  parses the request body for the patch http method      i think the docs should mention that  postform  is available not only for post and put but also for patch  that users don t need to dig into the code to discover that          ,1
567190,16850008446.0,IssuesEvent,2021-06-20 10:04:13,nirgreshler/natnet-motionclient,https://api.github.com/repos/nirgreshler/natnet-motionclient,closed,Add tolerance adjustability for how strictly a robot should adhere to its cell,low priority,"ledaati: 
majority =  if more than half of markers fall in one cell
all-but-one = if all but one markers (this is not so relevant because they're circular creatures)
all or nothing = only if all markers fall in that one cell 

Honestly imo i dont' think it even needs to be adjustable. we should test it a bit and settle on one settting. anyway it can be changed in the add_body f(x)",1.0,"Add tolerance adjustability for how strictly a robot should adhere to its cell - ledaati: 
majority =  if more than half of markers fall in one cell
all-but-one = if all but one markers (this is not so relevant because they're circular creatures)
all or nothing = only if all markers fall in that one cell 

Honestly imo i dont' think it even needs to be adjustable. we should test it a bit and settle on one settting. anyway it can be changed in the add_body f(x)",0,add tolerance adjustability for how strictly a robot should adhere to its cell   ledaati    majority    if more than half of markers fall in one cell  all but one   if all but one markers  this is not so relevant because they re circular creatures   all or nothing   only if all markers fall in that one cell     honestly imo i dont  think it even needs to be adjustable  we should test it a bit and settle on one settting  anyway it can be changed in the add body f x ,0
34264,6307134167.0,IssuesEvent,2017-07-21 23:26:50,golang/go,https://api.github.com/repos/golang/go,closed,doc: add VS Code editor guide,DevExp Documentation,"This is a tracking bug for https://github.com/golang/go/issues/20398 VSCode Go.

The brief info card for VSCode Go:

```
VSCode Go
https://github.com/Microsoft/vscode-go 

An extension for VS Code which provides support for the Go language.

Editing
Formatting on save (gofmt), automatic imports, identifier completion, vetting on save, linting on save.

Navigation
Godoc lookup, jumping to definition and referrers, looking up for interface implementations, searching for callers and callees.

Testing and Debugging
Running package tests, running single test case, generating test cases from package/file/function, Delve debugger integration.
```

The screencasts to be done:
- Linting on save
- Searching for callers and callees
- Running package tests
- Generating test cases",1.0,"doc: add VS Code editor guide - This is a tracking bug for https://github.com/golang/go/issues/20398 VSCode Go.

The brief info card for VSCode Go:

```
VSCode Go
https://github.com/Microsoft/vscode-go 

An extension for VS Code which provides support for the Go language.

Editing
Formatting on save (gofmt), automatic imports, identifier completion, vetting on save, linting on save.

Navigation
Godoc lookup, jumping to definition and referrers, looking up for interface implementations, searching for callers and callees.

Testing and Debugging
Running package tests, running single test case, generating test cases from package/file/function, Delve debugger integration.
```

The screencasts to be done:
- Linting on save
- Searching for callers and callees
- Running package tests
- Generating test cases",1,doc  add vs code editor guide   this is a tracking bug for   vscode go     the brief info card for vscode go          vscode go        an extension for vs code which provides support for the go language     editing  formatting on save  gofmt   automatic imports  identifier completion  vetting on save  linting on save     navigation  godoc lookup  jumping to definition and referrers  looking up for interface implementations  searching for callers and callees     testing and debugging  running package tests  running single test case  generating test cases from package file function  delve debugger integration          the screencasts to be done     linting on save    searching for callers and callees    running package tests    generating test cases,1
238993,19803514533.0,IssuesEvent,2022-01-19 02:14:44,itzg/docker-minecraft-server,https://api.github.com/repos/itzg/docker-minecraft-server,closed,Can't get fabric to use the main version,bug status/ready to test status/stale,"### Describe the problem

I did not configure the `VERSION` variable, so the server started with version 1.18
then I restarted the server, meanwhile 1.18.1 was released so the server automatically uses 1.18.1, sadly some fabric mods are not yet compatible. So I changed the `VERSION` to `1.18`

The server log correctly says

```
[init] Resolved version given 1.18 into 1.18
```

but it then continues to use the subversion
```
[INFO] [FabricLoader/GameProvider]: Loading for game Minecraft 1.18.1
[main/INFO]: Loading for game Minecraft 1.18.1
```

1.18.0 does not work


### Container definition

```
minecraft:
    image: itzg/minecraft-server
    restart: unless-stopped
    ports:
      - ""25565:25565""
      - ""24454:24454/udp""  
    volumes:
      - /etc/minecraft/cavesandcliffs:/data
    environment:
      TYPE: ""FABRIC""
      EULA: ""TRUE""
      CONSOLE: ""FALSE""
      MAX_MEMORY: ""5G""
      JVM_OPTS: ""-Dlog4j2.formatMsgNoLookups=true""
      VERSION: ""1.18""
```


### Container logs

```
minecraft_1         | [init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 10 1000 1000 4096 Dec 12 17:56 /data'
minecraft_1         | [init] Resolved version given 1.18 into 1.18
minecraft_1         | [init] Resolving type given FABRIC
minecraft_1         | [init] server.properties already created, skipping
minecraft_1         | [init] Checking for JSON files.
minecraft_1         | [init] Setting initial memory to 1G and max to 5G
minecraft_1         | [init] Starting the Minecraft server...
minecraft_1         | Starting net.fabricmc.loader.impl.game.minecraft.BundlerClassPathCapture
minecraft_1         | [19:03:07] [INFO] [FabricLoader/GameProvider]: Loading for game Minecraft 1.18.1
minecraft_1         | [19:03:08] [main/INFO]: Loading for game Minecraft 1.18.1
minecraft_1         | [19:03:08] [main/WARN]: Mod resolution failed
minecraft_1         | [19:03:08] [main/INFO]: Immediate reason: [HARD_DEP_INCOMPATIBLE_PRESELECTED voicechat 1.18-2.1.17 {depends minecraft @ [1.18]}, ROOT_FORCELOAD_SINGLE voicechat 1.18-2.1.17]
minecraft_1         | [19:03:08] [main/INFO]: Reason: [HARD_DEP voicechat 1.18-2.1.17 {depends minecraft @ [1.18]}]
minecraft_1         | [19:03:08] [main/INFO]: SERVER environment disabled: [fabric-renderer-api-v1, fabric-keybindings-v0, fabric-renderer-registries-v1, fabric-textures-v0, fabric-models-v0, fabric-screen-api-v1, fabric-rendering-v0, fabric-rendering-v1, fabric-key-binding-api-v1, fabric-renderer-indigo, fabric-blockrenderlayer-v1]
minecraft_1         | [19:03:08] [main/INFO]: Fix: add [], remove [], replace [[minecraft 1.18.1] -> add:minecraft 1.18 ([[1.18,1.18]])]
minecraft_1         | [19:03:08] [main/ERROR]: Incompatible mod set!
minecraft_1         | net.fabricmc.loader.impl.FormattedException: net.fabricmc.loader.impl.discovery.ModResolutionException: Mod resolution encountered an incompatible mod set!
minecraft_1         | A potential solution has been determined:
minecraft_1         |    - Replace 'Minecraft' (minecraft) 1.18.1 with version 1.18.
minecraft_1         | Unmet dependency listing:
minecraft_1         |    - Mod 'Simple Voice Chat' (voicechat) 1.18-2.1.17 requires version 1.18 of 'Minecraft' (minecraft), but only the wrong version is present: 1.18.1!
minecraft_1         |            - 'Minecraft' (minecraft) 1.18.1 is an environment reference and usually requires installation or launcher changes to adjust
minecraft_1         | Inactive mods:
minecraft_1         |    - 'Minecraft' (minecraft) 1.18.1, reason: to replace
minecraft_1         |    - mod 'Fabric BlockRenderLayer Registration (v1)' (fabric-blockrenderlayer-v1) 1.1.9+3ac43d95c8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Key Binding API (v1)' (fabric-key-binding-api-v1) 1.0.8+c8aba2f3c8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Key Bindings (v0)' (fabric-keybindings-v0) 0.2.6+b4f4f6cdc8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Models (v0)' (fabric-models-v0) 0.3.3+3ac43d95c8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Renderer API (v1)' (fabric-renderer-api-v1) 0.4.9+3ac43d95c8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Renderer - Indigo' (fabric-renderer-indigo) 0.4.12+3ac43d95c8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Renderer Registries (v1)' (fabric-renderer-registries-v1) 3.2.7+b4f4f6cdc8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Rendering (v0)' (fabric-rendering-v0) 1.1.9+b4f4f6cdc8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Rendering (v1)' (fabric-rendering-v1) 1.10.3+6b21378ac8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Screen API (v1)' (fabric-screen-api-v1) 1.0.7+3ac43d95c8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Textures (v0)' (fabric-textures-v0) 1.0.9+3ac43d95c8, reason: wrong environment (client/server only)
minecraft_1         |   at net.fabricmc.loader.impl.FabricLoaderImpl.load(FabricLoaderImpl.java:188) ~[fabric-loader-0.12.8.jar:?]
minecraft_1         |   at net.fabricmc.loader.impl.launch.knot.Knot.init(Knot.java:142) ~[fabric-loader-0.12.8.jar:?]
minecraft_1         |   at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:71) [fabric-loader-0.12.8.jar:?]
minecraft_1         |   at net.fabricmc.loader.impl.launch.knot.KnotServer.main(KnotServer.java:23) [fabric-loader-0.12.8.jar:?]
minecraft_1         |   at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
minecraft_1         |   at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) ~[?:?]
minecraft_1         |   at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
minecraft_1         |   at java.lang.reflect.Method.invoke(Method.java:568) ~[?:?]
minecraft_1         |   at net.fabricmc.loader.impl.launch.server.FabricServerLauncher.main(FabricServerLauncher.java:66) [fabric-loader-0.12.8.jar:?]
minecraft_1         | Caused by: net.fabricmc.loader.impl.discovery.ModResolutionException: Mod resolution encountered an incompatible mod set!
minecraft_1         | A potential solution has been determined:
minecraft_1         |    - Replace 'Minecraft' (minecraft) 1.18.1 with version 1.18.
minecraft_1         | Unmet dependency listing:
minecraft_1         |    - Mod 'Simple Voice Chat' (voicechat) 1.18-2.1.17 requires version 1.18 of 'Minecraft' (minecraft), but only the wrong version is present: 1.18.1!
minecraft_1         |            - 'Minecraft' (minecraft) 1.18.1 is an environment reference and usually requires installation or launcher changes to adjust
minecraft_1         | Inactive mods:
minecraft_1         |    - 'Minecraft' (minecraft) 1.18.1, reason: to replace
minecraft_1         |    - mod 'Fabric BlockRenderLayer Registration (v1)' (fabric-blockrenderlayer-v1) 1.1.9+3ac43d95c8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Key Binding API (v1)' (fabric-key-binding-api-v1) 1.0.8+c8aba2f3c8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Key Bindings (v0)' (fabric-keybindings-v0) 0.2.6+b4f4f6cdc8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Models (v0)' (fabric-models-v0) 0.3.3+3ac43d95c8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Renderer API (v1)' (fabric-renderer-api-v1) 0.4.9+3ac43d95c8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Renderer - Indigo' (fabric-renderer-indigo) 0.4.12+3ac43d95c8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Renderer Registries (v1)' (fabric-renderer-registries-v1) 3.2.7+b4f4f6cdc8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Rendering (v0)' (fabric-rendering-v0) 1.1.9+b4f4f6cdc8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Rendering (v1)' (fabric-rendering-v1) 1.10.3+6b21378ac8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Screen API (v1)' (fabric-screen-api-v1) 1.0.7+3ac43d95c8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Textures (v0)' (fabric-textures-v0) 1.0.9+3ac43d95c8, reason: wrong environment (client/server only)
minecraft_1         |   at net.fabricmc.loader.impl.discovery.ModResolver.findCompatibleSet(ModResolver.java:183) ~[fabric-loader-0.12.8.jar:?]
minecraft_1         |   at net.fabricmc.loader.impl.discovery.ModResolver.resolve(ModResolver.java:48) ~[fabric-loader-0.12.8.jar:?]
minecraft_1         |   at net.fabricmc.loader.impl.FabricLoaderImpl.setup(FabricLoaderImpl.java:222) ~[fabric-loader-0.12.8.jar:?]
minecraft_1         |   at net.fabricmc.loader.impl.FabricLoaderImpl.load(FabricLoaderImpl.java:186) ~[fabric-loader-0.12.8.jar:?]
minecraft_1         |   ... 8 more
minecraft_1         | 2021-12-12T19:03:08.764Z  WARN    mc-server-runner        sub-process failed      {""exitCode"": 1}
minecraft_1         | 2021-12-12T19:03:08.764Z  INFO    mc-server-runner        Done
```",1.0,"Can't get fabric to use the main version - ### Describe the problem

I did not configure the `VERSION` variable, so the server started with version 1.18
then I restarted the server, meanwhile 1.18.1 was released so the server automatically uses 1.18.1, sadly some fabric mods are not yet compatible. So I changed the `VERSION` to `1.18`

The server log correctly says

```
[init] Resolved version given 1.18 into 1.18
```

but it then continues to use the subversion
```
[INFO] [FabricLoader/GameProvider]: Loading for game Minecraft 1.18.1
[main/INFO]: Loading for game Minecraft 1.18.1
```

1.18.0 does not work


### Container definition

```
minecraft:
    image: itzg/minecraft-server
    restart: unless-stopped
    ports:
      - ""25565:25565""
      - ""24454:24454/udp""  
    volumes:
      - /etc/minecraft/cavesandcliffs:/data
    environment:
      TYPE: ""FABRIC""
      EULA: ""TRUE""
      CONSOLE: ""FALSE""
      MAX_MEMORY: ""5G""
      JVM_OPTS: ""-Dlog4j2.formatMsgNoLookups=true""
      VERSION: ""1.18""
```


### Container logs

```
minecraft_1         | [init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 10 1000 1000 4096 Dec 12 17:56 /data'
minecraft_1         | [init] Resolved version given 1.18 into 1.18
minecraft_1         | [init] Resolving type given FABRIC
minecraft_1         | [init] server.properties already created, skipping
minecraft_1         | [init] Checking for JSON files.
minecraft_1         | [init] Setting initial memory to 1G and max to 5G
minecraft_1         | [init] Starting the Minecraft server...
minecraft_1         | Starting net.fabricmc.loader.impl.game.minecraft.BundlerClassPathCapture
minecraft_1         | [19:03:07] [INFO] [FabricLoader/GameProvider]: Loading for game Minecraft 1.18.1
minecraft_1         | [19:03:08] [main/INFO]: Loading for game Minecraft 1.18.1
minecraft_1         | [19:03:08] [main/WARN]: Mod resolution failed
minecraft_1         | [19:03:08] [main/INFO]: Immediate reason: [HARD_DEP_INCOMPATIBLE_PRESELECTED voicechat 1.18-2.1.17 {depends minecraft @ [1.18]}, ROOT_FORCELOAD_SINGLE voicechat 1.18-2.1.17]
minecraft_1         | [19:03:08] [main/INFO]: Reason: [HARD_DEP voicechat 1.18-2.1.17 {depends minecraft @ [1.18]}]
minecraft_1         | [19:03:08] [main/INFO]: SERVER environment disabled: [fabric-renderer-api-v1, fabric-keybindings-v0, fabric-renderer-registries-v1, fabric-textures-v0, fabric-models-v0, fabric-screen-api-v1, fabric-rendering-v0, fabric-rendering-v1, fabric-key-binding-api-v1, fabric-renderer-indigo, fabric-blockrenderlayer-v1]
minecraft_1         | [19:03:08] [main/INFO]: Fix: add [], remove [], replace [[minecraft 1.18.1] -> add:minecraft 1.18 ([[1.18,1.18]])]
minecraft_1         | [19:03:08] [main/ERROR]: Incompatible mod set!
minecraft_1         | net.fabricmc.loader.impl.FormattedException: net.fabricmc.loader.impl.discovery.ModResolutionException: Mod resolution encountered an incompatible mod set!
minecraft_1         | A potential solution has been determined:
minecraft_1         |    - Replace 'Minecraft' (minecraft) 1.18.1 with version 1.18.
minecraft_1         | Unmet dependency listing:
minecraft_1         |    - Mod 'Simple Voice Chat' (voicechat) 1.18-2.1.17 requires version 1.18 of 'Minecraft' (minecraft), but only the wrong version is present: 1.18.1!
minecraft_1         |            - 'Minecraft' (minecraft) 1.18.1 is an environment reference and usually requires installation or launcher changes to adjust
minecraft_1         | Inactive mods:
minecraft_1         |    - 'Minecraft' (minecraft) 1.18.1, reason: to replace
minecraft_1         |    - mod 'Fabric BlockRenderLayer Registration (v1)' (fabric-blockrenderlayer-v1) 1.1.9+3ac43d95c8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Key Binding API (v1)' (fabric-key-binding-api-v1) 1.0.8+c8aba2f3c8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Key Bindings (v0)' (fabric-keybindings-v0) 0.2.6+b4f4f6cdc8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Models (v0)' (fabric-models-v0) 0.3.3+3ac43d95c8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Renderer API (v1)' (fabric-renderer-api-v1) 0.4.9+3ac43d95c8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Renderer - Indigo' (fabric-renderer-indigo) 0.4.12+3ac43d95c8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Renderer Registries (v1)' (fabric-renderer-registries-v1) 3.2.7+b4f4f6cdc8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Rendering (v0)' (fabric-rendering-v0) 1.1.9+b4f4f6cdc8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Rendering (v1)' (fabric-rendering-v1) 1.10.3+6b21378ac8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Screen API (v1)' (fabric-screen-api-v1) 1.0.7+3ac43d95c8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Textures (v0)' (fabric-textures-v0) 1.0.9+3ac43d95c8, reason: wrong environment (client/server only)
minecraft_1         |   at net.fabricmc.loader.impl.FabricLoaderImpl.load(FabricLoaderImpl.java:188) ~[fabric-loader-0.12.8.jar:?]
minecraft_1         |   at net.fabricmc.loader.impl.launch.knot.Knot.init(Knot.java:142) ~[fabric-loader-0.12.8.jar:?]
minecraft_1         |   at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:71) [fabric-loader-0.12.8.jar:?]
minecraft_1         |   at net.fabricmc.loader.impl.launch.knot.KnotServer.main(KnotServer.java:23) [fabric-loader-0.12.8.jar:?]
minecraft_1         |   at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
minecraft_1         |   at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) ~[?:?]
minecraft_1         |   at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
minecraft_1         |   at java.lang.reflect.Method.invoke(Method.java:568) ~[?:?]
minecraft_1         |   at net.fabricmc.loader.impl.launch.server.FabricServerLauncher.main(FabricServerLauncher.java:66) [fabric-loader-0.12.8.jar:?]
minecraft_1         | Caused by: net.fabricmc.loader.impl.discovery.ModResolutionException: Mod resolution encountered an incompatible mod set!
minecraft_1         | A potential solution has been determined:
minecraft_1         |    - Replace 'Minecraft' (minecraft) 1.18.1 with version 1.18.
minecraft_1         | Unmet dependency listing:
minecraft_1         |    - Mod 'Simple Voice Chat' (voicechat) 1.18-2.1.17 requires version 1.18 of 'Minecraft' (minecraft), but only the wrong version is present: 1.18.1!
minecraft_1         |            - 'Minecraft' (minecraft) 1.18.1 is an environment reference and usually requires installation or launcher changes to adjust
minecraft_1         | Inactive mods:
minecraft_1         |    - 'Minecraft' (minecraft) 1.18.1, reason: to replace
minecraft_1         |    - mod 'Fabric BlockRenderLayer Registration (v1)' (fabric-blockrenderlayer-v1) 1.1.9+3ac43d95c8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Key Binding API (v1)' (fabric-key-binding-api-v1) 1.0.8+c8aba2f3c8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Key Bindings (v0)' (fabric-keybindings-v0) 0.2.6+b4f4f6cdc8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Models (v0)' (fabric-models-v0) 0.3.3+3ac43d95c8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Renderer API (v1)' (fabric-renderer-api-v1) 0.4.9+3ac43d95c8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Renderer - Indigo' (fabric-renderer-indigo) 0.4.12+3ac43d95c8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Renderer Registries (v1)' (fabric-renderer-registries-v1) 3.2.7+b4f4f6cdc8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Rendering (v0)' (fabric-rendering-v0) 1.1.9+b4f4f6cdc8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Rendering (v1)' (fabric-rendering-v1) 1.10.3+6b21378ac8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Screen API (v1)' (fabric-screen-api-v1) 1.0.7+3ac43d95c8, reason: wrong environment (client/server only)
minecraft_1         |    - mod 'Fabric Textures (v0)' (fabric-textures-v0) 1.0.9+3ac43d95c8, reason: wrong environment (client/server only)
minecraft_1         |   at net.fabricmc.loader.impl.discovery.ModResolver.findCompatibleSet(ModResolver.java:183) ~[fabric-loader-0.12.8.jar:?]
minecraft_1         |   at net.fabricmc.loader.impl.discovery.ModResolver.resolve(ModResolver.java:48) ~[fabric-loader-0.12.8.jar:?]
minecraft_1         |   at net.fabricmc.loader.impl.FabricLoaderImpl.setup(FabricLoaderImpl.java:222) ~[fabric-loader-0.12.8.jar:?]
minecraft_1         |   at net.fabricmc.loader.impl.FabricLoaderImpl.load(FabricLoaderImpl.java:186) ~[fabric-loader-0.12.8.jar:?]
minecraft_1         |   ... 8 more
minecraft_1         | 2021-12-12T19:03:08.764Z  WARN    mc-server-runner        sub-process failed      {""exitCode"": 1}
minecraft_1         | 2021-12-12T19:03:08.764Z  INFO    mc-server-runner        Done
```",0,can t get fabric to use the main version       describe the problem  i did not configure the  version  variable  so the server started with version      then i restarted the server  meanwhile       was released so the server automatically uses        sadly some fabric mods are not yet compatible  so i changed the  version  to          the server log correctly says           resolved version given     into             but it then continues to use the subversion            loading for game minecraft           loading for game minecraft                     does not work        container definition       minecraft       image  itzg minecraft server      restart  unless stopped      ports                               udp         volumes            etc minecraft cavesandcliffs  data      environment         type   fabric         eula   true         console   false         max memory             jvm opts      formatmsgnolookups true         version                    container logs       minecraft               running as uid   gid   with  data as  drwxrwxr x         dec        data   minecraft               resolved version given     into      minecraft               resolving type given fabric  minecraft               server properties already created  skipping  minecraft               checking for json files   minecraft               setting initial memory to   and max to    minecraft               starting the minecraft server     minecraft             starting net fabricmc loader impl game minecraft bundlerclasspathcapture  minecraft                    loading for game minecraft        minecraft                  loading for game minecraft        minecraft                  mod resolution failed  minecraft                  immediate reason      root forceload single voicechat             minecraft                  reason       minecraft                  server environment disabled     minecraft                  fix  add    remove    replace      add minecraft            minecraft                  incompatible mod set   minecraft             net fabricmc loader impl formattedexception  net fabricmc loader impl discovery modresolutionexception  mod resolution encountered an incompatible mod set   minecraft             a potential solution has been determined   minecraft                  replace  minecraft   minecraft        with version       minecraft             unmet dependency listing   minecraft                  mod  simple voice chat   voicechat            requires version     of  minecraft   minecraft   but only the wrong version is present          minecraft                           minecraft   minecraft        is an environment reference and usually requires installation or launcher changes to adjust  minecraft             inactive mods   minecraft                   minecraft   minecraft         reason  to replace  minecraft                  mod  fabric blockrenderlayer registration       fabric blockrenderlayer             reason  wrong environment  client server only   minecraft                  mod  fabric key binding api       fabric key binding api             reason  wrong environment  client server only   minecraft                  mod  fabric key bindings       fabric keybindings             reason  wrong environment  client server only   minecraft                  mod  fabric models       fabric models             reason  wrong environment  client server only   minecraft                  mod  fabric renderer api       fabric renderer api             reason  wrong environment  client server only   minecraft                  mod  fabric renderer   indigo   fabric renderer indigo           reason  wrong environment  client server only   minecraft                  mod  fabric renderer registries       fabric renderer registries             reason  wrong environment  client server only   minecraft                  mod  fabric rendering       fabric rendering             reason  wrong environment  client server only   minecraft                  mod  fabric rendering       fabric rendering             reason  wrong environment  client server only   minecraft                  mod  fabric screen api       fabric screen api             reason  wrong environment  client server only   minecraft                  mod  fabric textures       fabric textures             reason  wrong environment  client server only   minecraft               at net fabricmc loader impl fabricloaderimpl load fabricloaderimpl java        minecraft               at net fabricmc loader impl launch knot knot init knot java        minecraft               at net fabricmc loader impl launch knot knot launch knot java       minecraft               at net fabricmc loader impl launch knot knotserver main knotserver java       minecraft               at jdk internal reflect nativemethodaccessorimpl   native method      minecraft               at jdk internal reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java        minecraft               at jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java        minecraft               at java lang reflect method invoke method java        minecraft               at net fabricmc loader impl launch server fabricserverlauncher main fabricserverlauncher java       minecraft             caused by  net fabricmc loader impl discovery modresolutionexception  mod resolution encountered an incompatible mod set   minecraft             a potential solution has been determined   minecraft                  replace  minecraft   minecraft        with version       minecraft             unmet dependency listing   minecraft                  mod  simple voice chat   voicechat            requires version     of  minecraft   minecraft   but only the wrong version is present          minecraft                           minecraft   minecraft        is an environment reference and usually requires installation or launcher changes to adjust  minecraft             inactive mods   minecraft                   minecraft   minecraft         reason  to replace  minecraft                  mod  fabric blockrenderlayer registration       fabric blockrenderlayer             reason  wrong environment  client server only   minecraft                  mod  fabric key binding api       fabric key binding api             reason  wrong environment  client server only   minecraft                  mod  fabric key bindings       fabric keybindings             reason  wrong environment  client server only   minecraft                  mod  fabric models       fabric models             reason  wrong environment  client server only   minecraft                  mod  fabric renderer api       fabric renderer api             reason  wrong environment  client server only   minecraft                  mod  fabric renderer   indigo   fabric renderer indigo           reason  wrong environment  client server only   minecraft                  mod  fabric renderer registries       fabric renderer registries             reason  wrong environment  client server only   minecraft                  mod  fabric rendering       fabric rendering             reason  wrong environment  client server only   minecraft                  mod  fabric rendering       fabric rendering             reason  wrong environment  client server only   minecraft                  mod  fabric screen api       fabric screen api             reason  wrong environment  client server only   minecraft                  mod  fabric textures       fabric textures             reason  wrong environment  client server only   minecraft               at net fabricmc loader impl discovery modresolver findcompatibleset modresolver java        minecraft               at net fabricmc loader impl discovery modresolver resolve modresolver java        minecraft               at net fabricmc loader impl fabricloaderimpl setup fabricloaderimpl java        minecraft               at net fabricmc loader impl fabricloaderimpl load fabricloaderimpl java        minecraft                     more  minecraft                          warn    mc server runner        sub process failed        exitcode       minecraft                          info    mc server runner        done     ,0
606138,18755719300.0,IssuesEvent,2021-11-05 10:28:21,AY2122S1-CS2103-F09-4/tp,https://api.github.com/repos/AY2122S1-CS2103-F09-4/tp,closed,"[PE-D] add command doesn't check for ""."" in email addresses",priority.Low,"Although the add command checks for the existence of ""@"", it doesn't make sure that after the ""@"" there is also an ""."" in the domain.

To recreate this, use an email such as ""example@mail"" and the command will work.

The person card of the created person can be seen below:

![image.png](https://raw.githubusercontent.com/MGRL2201/ped/main/files/40f2e85c-7ab9-4c6b-9129-59b64ae16020.png)



<!--session: 1635494373600-8b3b9cd6-9ebb-4fab-b126-e6b8cd676862-->
<!--Version: Web v3.4.1-->

-------------
Labels: `severity.Low` `type.FunctionalityBug`
original: MGRL2201/ped#10",1.0,"[PE-D] add command doesn't check for ""."" in email addresses - Although the add command checks for the existence of ""@"", it doesn't make sure that after the ""@"" there is also an ""."" in the domain.

To recreate this, use an email such as ""example@mail"" and the command will work.

The person card of the created person can be seen below:

![image.png](https://raw.githubusercontent.com/MGRL2201/ped/main/files/40f2e85c-7ab9-4c6b-9129-59b64ae16020.png)



<!--session: 1635494373600-8b3b9cd6-9ebb-4fab-b126-e6b8cd676862-->
<!--Version: Web v3.4.1-->

-------------
Labels: `severity.Low` `type.FunctionalityBug`
original: MGRL2201/ped#10",0,  add command doesn t check for     in email addresses   although the add command checks for the existence of      it doesn t make sure that after the     there is also an     in the domain   to recreate this  use an email such as  example mail  and the command will work   the person card of the created person can be seen below                              labels   severity low   type functionalitybug  original    ped  ,0
292872,25246388322.0,IssuesEvent,2022-11-15 11:24:11,wazuh/wazuh,https://api.github.com/repos/wazuh/wazuh,closed,Release 4.3.10 - Release Candidate 1 - SELinux,team/cicd type/release release test/4.3.10,"### Packages tests metrics information
|||
| :--                              | :--:                                                            |
| **Main release candidate issue** |#15372                                    |
| **Main packages metrics issue**  | #15340                                                   |
| **Version**                      | 4.3.10                                                   |
| **Release candidate**            | RC1                                                    |
| **Tag**                          | https://github.com/wazuh/wazuh/tree/v4.3.10-rc1 |

---

### Packages used
- Repository: `packages-dev.wazuh.com`
- Package path: `pre-release`
- Package revision: `1`

Status | System | Build |
| :--: | -- | -- |
| 🟢 | CentOS 7 | https://ci.wazuh.info/view/Tests/job/Test_selinux/5219/ |
| 🟢 | Ubuntu Bionic | https://ci.wazuh.info/view/Tests/job/Test_selinux/5220/ |

Status legend:
⚫ - Pending/In progress
⚪ - Skipped
🔴 - Rejected
🟢 - Approved
",1.0,"Release 4.3.10 - Release Candidate 1 - SELinux - ### Packages tests metrics information
|||
| :--                              | :--:                                                            |
| **Main release candidate issue** |#15372                                    |
| **Main packages metrics issue**  | #15340                                                   |
| **Version**                      | 4.3.10                                                   |
| **Release candidate**            | RC1                                                    |
| **Tag**                          | https://github.com/wazuh/wazuh/tree/v4.3.10-rc1 |

---

### Packages used
- Repository: `packages-dev.wazuh.com`
- Package path: `pre-release`
- Package revision: `1`

Status | System | Build |
| :--: | -- | -- |
| 🟢 | CentOS 7 | https://ci.wazuh.info/view/Tests/job/Test_selinux/5219/ |
| 🟢 | Ubuntu Bionic | https://ci.wazuh.info/view/Tests/job/Test_selinux/5220/ |

Status legend:
⚫ - Pending/In progress
⚪ - Skipped
🔴 - Rejected
🟢 - Approved
",0,release         release candidate     selinux       packages tests metrics information                                                                                                                   main release candidate issue                                                 main packages metrics issue                                                                  version                                                                                         release candidate                                                                            tag                                                packages used    repository   packages dev wazuh com     package path   pre release     package revision         status   system   build                          🟢   centos            🟢   ubuntu bionic          status legend   ⚫   pending in progress  ⚪   skipped  🔴   rejected  🟢   approved  ,0
263631,19956732239.0,IssuesEvent,2022-01-28 00:45:22,golang/go,https://api.github.com/repos/golang/go,closed,x/website: Effective Go needs to have a preamble re: generics,Documentation NeedsFix release-blocker,"[Effective Go](https://go.dev/doc/effective_go) needs to be updated with a preamble/disclaimer as it was not written with generics in mind.

cc: @robpike ",1.0,"x/website: Effective Go needs to have a preamble re: generics - [Effective Go](https://go.dev/doc/effective_go) needs to be updated with a preamble/disclaimer as it was not written with generics in mind.

cc: @robpike ",1,x website  effective go needs to have a preamble re  generics       needs to be updated with a preamble disclaimer as it was not written with generics in mind     cc   robpike ,1
29850,7126975623.0,IssuesEvent,2018-01-20 16:36:18,NagiosEnterprises/nagioscore,https://api.github.com/repos/NagiosEnterprises/nagioscore,closed,Nagios Core 4.4 alpha - make install-init error,Bug Code Quality,"I tried installing the latest build of 4.4 and I get the following error:

```
[root@core-014 nagioscore]# make install-init
/usr/bin/install -c -m 755 -o root -g root startup/rh-upstart-init /etc/init/nagios.conf
/usr/bin/install: cannot stat `startup/rh-upstart-init': No such file or directory
make: *** [install-daemoninit] Error 1
```

This is on CentOS release 6.8 (Final) x64.

This is a fresh build of the OS, it has not had Nagios installed on it before.

Full log:
```
[root@core-014 ~]# cd /tmp
[root@core-014 tmp]# ls -la
total 35012
drwxrwxrwt.  7 root root     4096 Jan 16 10:08 .
dr-xr-xr-x. 22 root root     4096 Jan 16 10:06 ..
drwxrwxrwt.  2 root root     4096 Jan 16 10:06 .ICE-unix
-rw-r--r--.  1 root root 35819943 Jan 16 10:08 nagioscore-4.4.aplha.tar.gz
drwxr-xr-x.  2 root root     4096 Jun 10  2016 vmware-config0
drwxr-xr-x.  2 root root     4096 Jun 10  2016 vmware-fonts0
drwx------.  2 root root     4096 Jan 16 10:06 vmware-root
drwxr-xr-x.  7 root root     4096 Sep  1  2014 vmware-tools-distrib
-rw-------.  1 root root        0 Jun 10  2016 yum.log
[root@core-014 tmp]# tar xzf nagioscore-4.4.aplha.tar.gz 
[root@core-014 tmp]# cd nagioscore
[root@core-014 nagioscore]# ./configure 
checking for a BSD-compatible install... /usr/bin/install -c
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether make sets $(MAKE)... yes
checking whether ln -s works... yes
checking for strip... /usr/bin/strip
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking whether time.h and sys/time.h may both be included... yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking ctype.h usability... yes
checking ctype.h presence... yes
checking for ctype.h... yes
checking dirent.h usability... yes
checking dirent.h presence... yes
checking for dirent.h... yes
checking errno.h usability... yes
checking errno.h presence... yes
checking for errno.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking getopt.h usability... yes
checking getopt.h presence... yes
checking for getopt.h... yes
checking grp.h usability... yes
checking grp.h presence... yes
checking for grp.h... yes
checking libgen.h usability... yes
checking libgen.h presence... yes
checking for libgen.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking math.h usability... yes
checking math.h presence... yes
checking for math.h... yes
checking netdb.h usability... yes
checking netdb.h presence... yes
checking for netdb.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking pwd.h usability... yes
checking pwd.h presence... yes
checking for pwd.h... yes
checking regex.h usability... yes
checking regex.h presence... yes
checking for regex.h... yes
checking signal.h usability... yes
checking signal.h presence... yes
checking for signal.h... yes
checking socket.h usability... no
checking socket.h presence... no
checking for socket.h... no
checking stdarg.h usability... yes
checking stdarg.h presence... yes
checking for stdarg.h... yes
checking for string.h... (cached) yes
checking for strings.h... (cached) yes
checking sys/loadavg.h usability... no
checking sys/loadavg.h presence... no
checking for sys/loadavg.h... no
checking sys/mman.h usability... yes
checking sys/mman.h presence... yes
checking for sys/mman.h... yes
checking for sys/types.h... (cached) yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking sys/resource.h usability... yes
checking sys/resource.h presence... yes
checking for sys/resource.h... yes
checking for sys/wait.h... (cached) yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking for sys/stat.h... (cached) yes
checking sys/timeb.h usability... yes
checking sys/timeb.h presence... yes
checking for sys/timeb.h... yes
checking sys/un.h usability... yes
checking sys/un.h presence... yes
checking for sys/un.h... yes
checking sys/ipc.h usability... yes
checking sys/ipc.h presence... yes
checking for sys/ipc.h... yes
checking sys/msg.h usability... yes
checking sys/msg.h presence... yes
checking for sys/msg.h... yes
checking sys/poll.h usability... yes
checking sys/poll.h presence... yes
checking for sys/poll.h... yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking uio.h usability... no
checking uio.h presence... no
checking for uio.h... no
checking for unistd.h... (cached) yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking wchar.h usability... yes
checking wchar.h presence... yes
checking for wchar.h... yes
checking sys/prctl.h usability... yes
checking sys/prctl.h presence... yes
checking for sys/prctl.h... yes
checking for an ANSI C-conforming const... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for struct tm.tm_zone... yes
checking for mode_t... yes
checking for pid_t... yes
checking for size_t... yes
checking return type of signal handlers... void
checking for uid_t in sys/types.h... yes
checking type of array argument to getgroups... gid_t
checking what the operating system is ... linux
checking what the distribution type is ... rh
checking what init system is being used ... upstart
checking what inetd is being used ... upstart
checking for which paths to use ... default
checking for which init file to use ... rh-upstart-init
checking for which inetd files to use ... unknown
checking for va_copy... yes
checking for vsnprintf... yes
checking for snprintf... yes
checking for asprintf... yes
checking for vasprintf... yes
checking for sigaction... yes
checking for C99 vsnprintf... yes
checking for library containing getservbyname... none required
checking for library containing connect... none required
checking for initgroups... yes
checking for setenv... yes
checking for strdup... yes
checking for strstr... yes
checking for strtoul... yes
checking for unsetenv... yes
checking for type of socket size... size_t
checking for library containing nanosleep... none required
checking for mail... no
which: no mail in (/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin)
checking for glibc at least version 2.4... yes
checking sys/epoll.h usability... yes
checking sys/epoll.h presence... yes
checking for sys/epoll.h... yes
checking sys/select.h usability... yes
checking sys/select.h presence... yes
checking for sys/select.h... yes
./configure: line 6408: dnls: command not found
checking for main in -liconv... no
checking for gdImagePng in -lgd (order 1)... no
checking for gdImagePng in -lgd (order 2)... yes
GD library was found!
checking for gdImageCreateTrueColor in -lgd... yes
checking ltdl.h usability... no
checking ltdl.h presence... no
checking for ltdl.h... no
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for dlopen in -ldl... yes
checking for extra flags needed to export symbols...  -Wl,-export-dynamic
checking for linker flags for loadable modules... -shared
checking for traceroute... no
checking for type va_list... yes
checking for perl... /usr/bin/perl
checking for unzip... /usr/bin/unzip
configure: creating ./config.status
config.status: creating html/index.php
config.status: creating Makefile
config.status: creating lib/Makefile
config.status: creating base/Makefile
config.status: creating common/Makefile
config.status: creating contrib/Makefile
config.status: creating cgi/Makefile
config.status: creating html/Makefile
config.status: creating module/Makefile
config.status: creating worker/Makefile
config.status: creating worker/ping/Makefile
config.status: creating xdata/Makefile
config.status: creating subst
config.status: creating pkginfo
config.status: creating startup/openrc-init
config.status: creating startup/default-init
config.status: creating startup/default-service
config.status: creating startup/upstart-init
config.status: creating t/Makefile
config.status: creating t-tap/Makefile
config.status: creating include/config.h
config.status: creating lib/snprintf.h
config.status: creating lib/iobroker.h

Creating sample config files in sample-config/ ...


*** Configuration summary for nagios 4.4.0 2018-??-?? ***:

 General Options:
 -------------------------
        Nagios executable:  nagios
        Nagios user/group:  nagios,nagios
       Command user/group:  nagios,nagios
             Event Broker:  yes
        Install ${prefix}:  /usr/local/nagios
    Install ${includedir}:  /usr/local/nagios/include/nagios
                Lock file:  N/A
   Check result directory:  /usr/local/nagios/var/spool/checkresults
           Init directory:  /etc/init
  Apache conf.d directory:  /etc/httpd/conf.d
             Mail program:  /usr/sbin/sendmail
                  Host OS:  linux-gnu
          IOBroker Method:  epoll

 Web Interface Options:
 ------------------------
                 HTML URL:  http://localhost/nagios/
                  CGI URL:  http://localhost/nagios/cgi-bin/
 Traceroute (used by WAP):  


Review the options above for accuracy.  If they look okay,
type 'make all' to compile the main program and CGIs.

[root@core-014 nagioscore]# make all
cd ./base && make
make[1]: Entering directory `/tmp/nagioscore/base'
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o nagios.o nagios.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o broker.o broker.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o nebmods.o nebmods.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o ../common/shared.o ../common/shared.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o query-handler.o query-handler.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o workers.o workers.c
workers.c: In function ‘wproc_run_job’:
workers.c:996: warning: unused variable ‘i’
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o checks.o checks.c
checks.c: In function ‘service_fresh_check’:
checks.c:740: warning: ‘return’ with a value, in function returning void
checks.c: In function ‘host_fresh_check’:
checks.c:759: warning: ‘return’ with a value, in function returning void
checks.c: In function ‘host_state_or_hard_state_type_change’:
checks.c:930: warning: passing argument 1 of ‘delete_service_acknowledgement_comments’ from incompatible pointer type
../include/comments.h:92: note: expected ‘struct service *’ but argument is of type ‘struct host *’
checks.c: In function ‘handle_async_service_check_result’:
checks.c:1123: warning: suggest explicit braces to avoid ambiguous ‘else’
checks.c: In function ‘handle_async_host_check_result’:
checks.c:2732: warning: suggest explicit braces to avoid ambiguous ‘else’
checks.c:2784: warning: suggest parentheses around assignment used as truth value
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o config.o config.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o commands.o commands.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o events.o events.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o flapping.o flapping.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o logging.o logging.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o macros-base.o ../common/macros.c
../common/macros.c: In function ‘process_macros_r’:
../common/macros.c:140: warning: suggest parentheses around assignment used as truth value
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o netutils.o netutils.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o notifications.o notifications.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o sehandlers.o sehandlers.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o utils.o utils.c
utils.c: In function ‘daemon_init’:
utils.c:1940: warning: implicit declaration of function ‘cleanup_performance_data’
utils.c:1941: warning: implicit declaration of function ‘cleanup_downtime_data’
utils.c: In function ‘process_check_result_file’:
utils.c:2346: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘time_t’
utils.c: In function ‘cleanup’:
utils.c:3372: warning: implicit declaration of function ‘xodtemplate_free_memory’
utils.c: In function ‘rlimit_problem_detection’:
utils.c:3697: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘rlim_t’
utils.c:3702: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘rlim_t’
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o retention-base.o sretention.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o xretention-base.o ../xdata/xrddefault.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o comments-base.o ../common/comments.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o xcomments-base.o ../xdata/xcddefault.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o objects-base.o ../common/objects.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o xobjects-base.o ../xdata/xodtemplate.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o statusdata-base.o ../common/statusdata.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o xstatusdata-base.o ../xdata/xsddefault.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o perfdata-base.o perfdata.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o xperfdata-base.o ../xdata/xpddefault.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o downtime-base.o ../common/downtime.c
make -C ../lib
make[2]: Entering directory `/tmp/nagioscore/lib'
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c squeue.c -o squeue.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c kvvec.c -o kvvec.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c iocache.c -o iocache.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c iobroker.c -o iobroker.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c bitmap.c -o bitmap.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c dkhash.c -o dkhash.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c runcmd.c -o runcmd.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c nsutils.c -o nsutils.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c fanout.c -o fanout.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c pqueue.c -o pqueue.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c worker.c -o worker.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c skiplist.c -o skiplist.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c nsock.c -o nsock.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c nspath.c -o nspath.o
ar cr libnagios.a squeue.o kvvec.o iocache.o iobroker.o bitmap.o dkhash.o runcmd.o nsutils.o fanout.o pqueue.o worker.o skiplist.o nsock.o nspath.o
make[2]: Leaving directory `/tmp/nagioscore/lib'
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -o nagios nagios.o broker.o nebmods.o ../common/shared.o  query-handler.o workers.o checks.o config.o commands.o events.o flapping.o logging.o macros-base.o netutils.o notifications.o sehandlers.o utils.o retention-base.o xretention-base.o comments-base.o xcomments-base.o objects-base.o xobjects-base.o statusdata-base.o xstatusdata-base.o perfdata-base.o xperfdata-base.o downtime-base.o  -Wl,-export-dynamic   -lm  -ldl  ../lib/libnagios.a
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -o nagiostats nagiostats.c  -lm  ../lib/libnagios.a
make[1]: Leaving directory `/tmp/nagioscore/base'
cd ./cgi && make
make[1]: Entering directory `/tmp/nagioscore/cgi'
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI   -c -o getcgi.o getcgi.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI   -c -o cgiutils.o cgiutils.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI   -c -o cgiauth.o cgiauth.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI -c -o macros-cgi.o ../common/macros.c
../common/macros.c: In function ‘process_macros_r’:
../common/macros.c:140: warning: suggest parentheses around assignment used as truth value
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI -c -o objects-cgi.o ../common/objects.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI -c -o xobjects-cgi.o ../xdata/xodtemplate.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI -c -o statusdata-cgi.o ../common/statusdata.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI -c -o xstatusdata-cgi.o ../xdata/xsddefault.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI -c -o comments-cgi.o ../common/comments.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI -c -o downtime-cgi.o ../common/downtime.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI -DJSON_NAGIOS_4X -c -o archiveutils.o archiveutils.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI -DJSON_NAGIOS_4X -c -o jsonutils.o jsonutils.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI -DJSON_NAGIOS_4X  -o archivejson.cgi archivejson.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a archiveutils.o jsonutils.o 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o avail.cgi avail.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI   -c -o extcmd_list.o extcmd_list.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o cmd.cgi cmd.c extcmd_list.o ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a   
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o config.cgi config.c  ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o extinfo.cgi extinfo.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a   
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o history.cgi history.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o notifications.cgi notifications.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI -DJSON_NAGIOS_4X  -o objectjson.cgi objectjson.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a jsonutils.o 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o outages.cgi outages.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a  
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o showlog.cgi showlog.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o status.cgi status.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a  
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI -DJSON_NAGIOS_4X  -o statusjson.cgi statusjson.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a jsonutils.o 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o statuswml.cgi statuswml.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o summary.cgi summary.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o tac.cgi tac.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a  
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o statuswrl.cgi statuswrl.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a -lm 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o statusmap.cgi statusmap.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a -lgd  -lpng -ljpeg -lz -lm 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o trends.cgi trends.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a -lgd  -lpng -ljpeg -lz -lm 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o histogram.cgi histogram.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a -lgd  -lpng -ljpeg -lz -lm 
make[1]: Leaving directory `/tmp/nagioscore/cgi'
cd ./html && make
make[1]: Entering directory `/tmp/nagioscore/html'
(cd angularjs && unzip -u angular-1.3.9.zip)
Archive:  angular-1.3.9.zip
   creating: angular-1.3.9/
  inflating: angular-1.3.9/angular-animate.js  
  inflating: angular-1.3.9/angular-animate.min.js  
  inflating: angular-1.3.9/angular-animate.min.js.map  
  inflating: angular-1.3.9/angular-aria.js  
  inflating: angular-1.3.9/angular-aria.min.js  
  inflating: angular-1.3.9/angular-aria.min.js.map  
  inflating: angular-1.3.9/angular-cookies.js  
  inflating: angular-1.3.9/angular-cookies.min.js  
  inflating: angular-1.3.9/angular-cookies.min.js.map  
  inflating: angular-1.3.9/angular-csp.css  
  inflating: angular-1.3.9/angular-loader.js  
  inflating: angular-1.3.9/angular-loader.min.js  
  inflating: angular-1.3.9/angular-loader.min.js.map  
  inflating: angular-1.3.9/angular-messages.js  
  inflating: angular-1.3.9/angular-messages.min.js  
  inflating: angular-1.3.9/angular-messages.min.js.map  
  inflating: angular-1.3.9/angular-mocks.js  
  inflating: angular-1.3.9/angular-resource.js  
  inflating: angular-1.3.9/angular-resource.min.js  
  inflating: angular-1.3.9/angular-resource.min.js.map  
  inflating: angular-1.3.9/angular-route.js  
  inflating: angular-1.3.9/angular-route.min.js  
  inflating: angular-1.3.9/angular-route.min.js.map  
  inflating: angular-1.3.9/angular-sanitize.js  
  inflating: angular-1.3.9/angular-sanitize.min.js  
  inflating: angular-1.3.9/angular-sanitize.min.js.map  
  inflating: angular-1.3.9/angular-scenario.js  
  inflating: angular-1.3.9/angular-touch.js  
  inflating: angular-1.3.9/angular-touch.min.js  
  inflating: angular-1.3.9/angular-touch.min.js.map  
  inflating: angular-1.3.9/angular.js  
  inflating: angular-1.3.9/angular.min.js  
  inflating: angular-1.3.9/angular.min.js.map  
   creating: angular-1.3.9/docs/
  inflating: angular-1.3.9/docs/Error404.html  
   creating: angular-1.3.9/docs/components/
   creating: angular-1.3.9/docs/components/bootstrap-3.1.1/
   creating: angular-1.3.9/docs/components/bootstrap-3.1.1/css/
  inflating: angular-1.3.9/docs/components/bootstrap-3.1.1/css/bootstrap-theme.css  
  inflating: angular-1.3.9/docs/components/bootstrap-3.1.1/css/bootstrap-theme.css.map  
  inflating: angular-1.3.9/docs/components/bootstrap-3.1.1/css/bootstrap-theme.min.css  
  inflating: angular-1.3.9/docs/components/bootstrap-3.1.1/css/bootstrap.css  
  inflating: angular-1.3.9/docs/components/bootstrap-3.1.1/css/bootstrap.css.map  
  inflating: angular-1.3.9/docs/components/bootstrap-3.1.1/css/bootstrap.min.css  
   creating: angular-1.3.9/docs/components/bootstrap-3.1.1/fonts/
  inflating: angular-1.3.9/docs/components/bootstrap-3.1.1/fonts/glyphicons-halflings-regular.eot  
  inflating: angular-1.3.9/docs/components/bootstrap-3.1.1/fonts/glyphicons-halflings-regular.svg  
  inflating: angular-1.3.9/docs/components/bootstrap-3.1.1/fonts/glyphicons-halflings-regular.ttf  
  inflating: angular-1.3.9/docs/components/bootstrap-3.1.1/fonts/glyphicons-halflings-regular.woff  
   creating: angular-1.3.9/docs/components/bootstrap-3.1.1/js/
  inflating: angular-1.3.9/docs/components/bootstrap-3.1.1/js/bootstrap.js  
  inflating: angular-1.3.9/docs/components/bootstrap-3.1.1/js/bootstrap.min.js  
   creating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/CHANGES.html  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/COPYING  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/README-zh-Hans.html  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/README.html  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/README.md  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/bower.json  
   creating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-apollo.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-clj.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-css.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-dart.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-go.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-hs.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-lisp.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-lua.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-ml.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-n.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-proto.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-scala.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-sql.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-tex.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-vb.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-vhdl.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-wiki.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-xq.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-yaml.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/prettify.css  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/prettify.js  
   creating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/styles/
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/styles/demo.html  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/styles/desert.css  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/styles/index.html  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/styles/sons-of-obsidian.css  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/styles/sunburst.css  
   creating: angular-1.3.9/docs/components/jquery-2.1.1/
  inflating: angular-1.3.9/docs/components/jquery-2.1.1/jquery.js  
  inflating: angular-1.3.9/docs/components/jquery-2.1.1/jquery.min.js  
   creating: angular-1.3.9/docs/components/lunr.js-0.4.2/
  inflating: angular-1.3.9/docs/components/lunr.js-0.4.2/lunr.js  
  inflating: angular-1.3.9/docs/components/lunr.js-0.4.2/lunr.min.js  
  inflating: angular-1.3.9/docs/components/lunr.js-0.4.2/server.js  
   creating: angular-1.3.9/docs/components/marked-0.3.2/
  inflating: angular-1.3.9/docs/components/marked-0.3.2/index.js  
   creating: angular-1.3.9/docs/components/marked-0.3.2/lib/
  inflating: angular-1.3.9/docs/components/marked-0.3.2/lib/marked.js  
   creating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/README.md  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/bower.json  
   creating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/
   creating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Bold/
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Bold/OpenSans-Bold.eot  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Bold/OpenSans-Bold.svg  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Bold/OpenSans-Bold.ttf  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Bold/OpenSans-Bold.woff  
   creating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/BoldItalic/
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/BoldItalic/OpenSans-BoldItalic.eot  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/BoldItalic/OpenSans-BoldItalic.svg  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/BoldItalic/OpenSans-BoldItalic.ttf  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/BoldItalic/OpenSans-BoldItalic.woff  
   creating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/ExtraBold/
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/ExtraBold/OpenSans-ExtraBold.eot  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/ExtraBold/OpenSans-ExtraBold.svg  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/ExtraBold/OpenSans-ExtraBold.ttf  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/ExtraBold/OpenSans-ExtraBold.woff  
   creating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/ExtraBoldItalic/
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/ExtraBoldItalic/OpenSans-ExtraBoldItalic.eot  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/ExtraBoldItalic/OpenSans-ExtraBoldItalic.svg  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/ExtraBoldItalic/OpenSans-ExtraBoldItalic.ttf  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/ExtraBoldItalic/OpenSans-ExtraBoldItalic.woff  
   creating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Italic/
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Italic/OpenSans-Italic.eot  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Italic/OpenSans-Italic.svg  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Italic/OpenSans-Italic.ttf  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Italic/OpenSans-Italic.woff  
   creating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Light/
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Light/OpenSans-Light.eot  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Light/OpenSans-Light.svg  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Light/OpenSans-Light.ttf  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Light/OpenSans-Light.woff  
   creating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/LightItalic/
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/LightItalic/OpenSans-LightItalic.eot  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/LightItalic/OpenSans-LightItalic.svg  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/LightItalic/OpenSans-LightItalic.ttf  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/LightItalic/OpenSans-LightItalic.woff  
   creating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Regular/
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Regular/OpenSans-Regular.eot  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Regular/OpenSans-Regular.svg  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Regular/OpenSans-Regular.ttf  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Regular/OpenSans-Regular.woff  
   creating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Semibold/
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Semibold/OpenSans-Semibold.eot  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Semibold/OpenSans-Semibold.svg  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Semibold/OpenSans-Semibold.ttf  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Semibold/OpenSans-Semibold.woff  
   creating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/SemiboldItalic/
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/SemiboldItalic/OpenSans-SemiboldItalic.eot  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/SemiboldItalic/OpenSans-SemiboldItalic.svg  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/SemiboldItalic/OpenSans-SemiboldItalic.ttf  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/SemiboldItalic/OpenSans-SemiboldItalic.woff  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/index.html  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/open-sans.css  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/open-sans.less  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/open-sans.scss  
   creating: angular-1.3.9/docs/css/
  inflating: angular-1.3.9/docs/css/animations.css  
  inflating: angular-1.3.9/docs/css/doc_widgets.css  
  inflating: angular-1.3.9/docs/css/docs.css  
  inflating: angular-1.3.9/docs/css/prettify-theme.css  
  inflating: angular-1.3.9/docs/css/prettify.css  
   creating: angular-1.3.9/docs/examples/
   creating: angular-1.3.9/docs/examples/example-$filter/
  inflating: angular-1.3.9/docs/examples/example-$filter/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-$filter/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-$filter/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-$filter/index.html  
  inflating: angular-1.3.9/docs/examples/example-$filter/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-$filter/script.js  
   creating: angular-1.3.9/docs/examples/example-$route-service/
  inflating: angular-1.3.9/docs/examples/example-$route-service/book.html  
  inflating: angular-1.3.9/docs/examples/example-$route-service/chapter.html  
  inflating: angular-1.3.9/docs/examples/example-$route-service/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-$route-service/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-$route-service/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-$route-service/index.html  
  inflating: angular-1.3.9/docs/examples/example-$route-service/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-$route-service/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-$route-service/script.js  
   creating: angular-1.3.9/docs/examples/example-NgModelController/
  inflating: angular-1.3.9/docs/examples/example-NgModelController/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-NgModelController/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-NgModelController/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-NgModelController/index.html  
  inflating: angular-1.3.9/docs/examples/example-NgModelController/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-NgModelController/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-NgModelController/script.js  
  inflating: angular-1.3.9/docs/examples/example-NgModelController/style.css  
   creating: angular-1.3.9/docs/examples/example-checkbox-input-directive/
  inflating: angular-1.3.9/docs/examples/example-checkbox-input-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-checkbox-input-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-checkbox-input-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-checkbox-input-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-checkbox-input-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-checkbox-input-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-date-input-directive/
  inflating: angular-1.3.9/docs/examples/example-date-input-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-date-input-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-date-input-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-date-input-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-date-input-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-date-input-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-datetimelocal-input-directive/
  inflating: angular-1.3.9/docs/examples/example-datetimelocal-input-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-datetimelocal-input-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-datetimelocal-input-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-datetimelocal-input-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-datetimelocal-input-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-datetimelocal-input-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-email-input-directive/
  inflating: angular-1.3.9/docs/examples/example-email-input-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-email-input-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-email-input-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-email-input-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-email-input-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-email-input-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-error-$rootScope-inprog/
  inflating: angular-1.3.9/docs/examples/example-error-$rootScope-inprog/app.js  
  inflating: angular-1.3.9/docs/examples/example-error-$rootScope-inprog/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-error-$rootScope-inprog/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-error-$rootScope-inprog/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-error-$rootScope-inprog/index.html  
  inflating: angular-1.3.9/docs/examples/example-error-$rootScope-inprog/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example/
   creating: angular-1.3.9/docs/examples/example-example.csp/
  inflating: angular-1.3.9/docs/examples/example-example.csp/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example.csp/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example.csp/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example.csp/index.html  
  inflating: angular-1.3.9/docs/examples/example-example.csp/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example.csp/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example.csp/script.js  
  inflating: angular-1.3.9/docs/examples/example-example/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example/index.html  
  inflating: angular-1.3.9/docs/examples/example-example/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example/script.js  
   creating: angular-1.3.9/docs/examples/example-example1/
  inflating: angular-1.3.9/docs/examples/example-example1/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example1/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example1/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example1/index.html  
  inflating: angular-1.3.9/docs/examples/example-example1/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example10/
  inflating: angular-1.3.9/docs/examples/example-example10/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example10/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example10/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example10/index.html  
  inflating: angular-1.3.9/docs/examples/example-example10/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example10/script.js  
   creating: angular-1.3.9/docs/examples/example-example100/
  inflating: angular-1.3.9/docs/examples/example-example100/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example100/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example100/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example100/index.html  
  inflating: angular-1.3.9/docs/examples/example-example100/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example100/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example101/
  inflating: angular-1.3.9/docs/examples/example-example101/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example101/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example101/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example101/index.html  
  inflating: angular-1.3.9/docs/examples/example-example101/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example101/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example102/
  inflating: angular-1.3.9/docs/examples/example-example102/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example102/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example102/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example102/index.html  
  inflating: angular-1.3.9/docs/examples/example-example102/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example102/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example103/
  inflating: angular-1.3.9/docs/examples/example-example103/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example103/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example103/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example103/index.html  
  inflating: angular-1.3.9/docs/examples/example-example103/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example104/
  inflating: angular-1.3.9/docs/examples/example-example104/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example104/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example104/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example104/index.html  
  inflating: angular-1.3.9/docs/examples/example-example104/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example104/script.js  
   creating: angular-1.3.9/docs/examples/example-example105/
  inflating: angular-1.3.9/docs/examples/example-example105/http-hello.html  
  inflating: angular-1.3.9/docs/examples/example-example105/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example105/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example105/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example105/index.html  
  inflating: angular-1.3.9/docs/examples/example-example105/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example105/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example105/script.js  
   creating: angular-1.3.9/docs/examples/example-example106/
  inflating: angular-1.3.9/docs/examples/example-example106/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example106/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example106/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example106/index.html  
  inflating: angular-1.3.9/docs/examples/example-example106/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example106/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example107/
  inflating: angular-1.3.9/docs/examples/example-example107/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example107/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example107/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example107/index.html  
  inflating: angular-1.3.9/docs/examples/example-example107/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example108/
  inflating: angular-1.3.9/docs/examples/example-example108/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example108/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example108/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example108/index.html  
  inflating: angular-1.3.9/docs/examples/example-example108/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example109/
  inflating: angular-1.3.9/docs/examples/example-example109/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example109/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example109/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example109/index.html  
  inflating: angular-1.3.9/docs/examples/example-example109/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example109/script.js  
   creating: angular-1.3.9/docs/examples/example-example11/
  inflating: angular-1.3.9/docs/examples/example-example11/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example11/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example11/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example11/index.html  
  inflating: angular-1.3.9/docs/examples/example-example11/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example11/my-customer.html  
  inflating: angular-1.3.9/docs/examples/example-example11/script.js  
   creating: angular-1.3.9/docs/examples/example-example110/
  inflating: angular-1.3.9/docs/examples/example-example110/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example110/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example110/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example110/index.html  
  inflating: angular-1.3.9/docs/examples/example-example110/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example110/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example110/script.js  
  inflating: angular-1.3.9/docs/examples/example-example110/test_data.json  
   creating: angular-1.3.9/docs/examples/example-example111/
  inflating: angular-1.3.9/docs/examples/example-example111/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example111/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example111/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example111/index.html  
  inflating: angular-1.3.9/docs/examples/example-example111/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example111/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example112/
  inflating: angular-1.3.9/docs/examples/example-example112/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example112/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example112/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example112/index.html  
  inflating: angular-1.3.9/docs/examples/example-example112/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example112/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example113/
  inflating: angular-1.3.9/docs/examples/example-example113/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example113/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example113/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example113/index.html  
  inflating: angular-1.3.9/docs/examples/example-example113/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example113/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example114/
  inflating: angular-1.3.9/docs/examples/example-example114/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example114/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example114/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example114/index.html  
  inflating: angular-1.3.9/docs/examples/example-example114/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example114/script.js  
   creating: angular-1.3.9/docs/examples/example-example115/
  inflating: angular-1.3.9/docs/examples/example-example115/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example115/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example115/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example115/index.html  
  inflating: angular-1.3.9/docs/examples/example-example115/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example115/script.js  
   creating: angular-1.3.9/docs/examples/example-example116/
  inflating: angular-1.3.9/docs/examples/example-example116/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example116/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example116/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example116/index.html  
  inflating: angular-1.3.9/docs/examples/example-example116/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example116/script.js  
   creating: angular-1.3.9/docs/examples/example-example12/
  inflating: angular-1.3.9/docs/examples/example-example12/customer-address.html  
  inflating: angular-1.3.9/docs/examples/example-example12/customer-name.html  
  inflating: angular-1.3.9/docs/examples/example-example12/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example12/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example12/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example12/index.html  
  inflating: angular-1.3.9/docs/examples/example-example12/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example12/script.js  
   creating: angular-1.3.9/docs/examples/example-example13/
  inflating: angular-1.3.9/docs/examples/example-example13/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example13/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example13/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example13/index.html  
  inflating: angular-1.3.9/docs/examples/example-example13/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example13/my-customer.html  
  inflating: angular-1.3.9/docs/examples/example-example13/script.js  
   creating: angular-1.3.9/docs/examples/example-example14/
  inflating: angular-1.3.9/docs/examples/example-example14/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example14/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example14/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example14/index.html  
  inflating: angular-1.3.9/docs/examples/example-example14/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example14/my-customer.html  
  inflating: angular-1.3.9/docs/examples/example-example14/script.js  
   creating: angular-1.3.9/docs/examples/example-example15/
  inflating: angular-1.3.9/docs/examples/example-example15/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example15/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example15/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example15/index.html  
  inflating: angular-1.3.9/docs/examples/example-example15/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example15/my-customer-iso.html  
  inflating: angular-1.3.9/docs/examples/example-example15/script.js  
   creating: angular-1.3.9/docs/examples/example-example16/
  inflating: angular-1.3.9/docs/examples/example-example16/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example16/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example16/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example16/index.html  
  inflating: angular-1.3.9/docs/examples/example-example16/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example16/my-customer-plus-vojta.html  
  inflating: angular-1.3.9/docs/examples/example-example16/script.js  
   creating: angular-1.3.9/docs/examples/example-example17/
  inflating: angular-1.3.9/docs/examples/example-example17/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example17/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example17/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example17/index.html  
  inflating: angular-1.3.9/docs/examples/example-example17/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example17/script.js  
   creating: angular-1.3.9/docs/examples/example-example18/
  inflating: angular-1.3.9/docs/examples/example-example18/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example18/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example18/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example18/index.html  
  inflating: angular-1.3.9/docs/examples/example-example18/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example18/my-dialog.html  
  inflating: angular-1.3.9/docs/examples/example-example18/script.js  
   creating: angular-1.3.9/docs/examples/example-example19/
  inflating: angular-1.3.9/docs/examples/example-example19/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example19/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example19/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example19/index.html  
  inflating: angular-1.3.9/docs/examples/example-example19/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example19/my-dialog.html  
  inflating: angular-1.3.9/docs/examples/example-example19/script.js  
   creating: angular-1.3.9/docs/examples/example-example2/
  inflating: angular-1.3.9/docs/examples/example-example2/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example2/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example2/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example2/index.html  
  inflating: angular-1.3.9/docs/examples/example-example2/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example20/
  inflating: angular-1.3.9/docs/examples/example-example20/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example20/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example20/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example20/index.html  
  inflating: angular-1.3.9/docs/examples/example-example20/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example20/my-dialog-close.html  
  inflating: angular-1.3.9/docs/examples/example-example20/script.js  
   creating: angular-1.3.9/docs/examples/example-example21/
  inflating: angular-1.3.9/docs/examples/example-example21/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example21/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example21/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example21/index.html  
  inflating: angular-1.3.9/docs/examples/example-example21/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example21/script.js  
   creating: angular-1.3.9/docs/examples/example-example22/
  inflating: angular-1.3.9/docs/examples/example-example22/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example22/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example22/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example22/index.html  
  inflating: angular-1.3.9/docs/examples/example-example22/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example22/my-pane.html  
  inflating: angular-1.3.9/docs/examples/example-example22/my-tabs.html  
  inflating: angular-1.3.9/docs/examples/example-example22/script.js  
   creating: angular-1.3.9/docs/examples/example-example23/
  inflating: angular-1.3.9/docs/examples/example-example23/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example23/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example23/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example23/index.html  
  inflating: angular-1.3.9/docs/examples/example-example23/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example23/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example24/
  inflating: angular-1.3.9/docs/examples/example-example24/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example24/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example24/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example24/index.html  
  inflating: angular-1.3.9/docs/examples/example-example24/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example24/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example24/script.js  
   creating: angular-1.3.9/docs/examples/example-example25/
  inflating: angular-1.3.9/docs/examples/example-example25/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example25/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example25/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example25/index.html  
  inflating: angular-1.3.9/docs/examples/example-example25/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example25/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example25/script.js  
   creating: angular-1.3.9/docs/examples/example-example26/
  inflating: angular-1.3.9/docs/examples/example-example26/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example26/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example26/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example26/index.html  
  inflating: angular-1.3.9/docs/examples/example-example26/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example26/script.js  
   creating: angular-1.3.9/docs/examples/example-example27/
  inflating: angular-1.3.9/docs/examples/example-example27/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example27/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example27/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example27/index.html  
  inflating: angular-1.3.9/docs/examples/example-example27/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example27/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example27/script.js  
   creating: angular-1.3.9/docs/examples/example-example28/
  inflating: angular-1.3.9/docs/examples/example-example28/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example28/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example28/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example28/index.html  
  inflating: angular-1.3.9/docs/examples/example-example28/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example28/script.js  
   creating: angular-1.3.9/docs/examples/example-example29/
  inflating: angular-1.3.9/docs/examples/example-example29/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example29/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example29/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example29/index.html  
  inflating: angular-1.3.9/docs/examples/example-example29/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example29/script.js  
   creating: angular-1.3.9/docs/examples/example-example3/
  inflating: angular-1.3.9/docs/examples/example-example3/animations.css  
  inflating: angular-1.3.9/docs/examples/example-example3/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example3/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example3/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example3/index.html  
  inflating: angular-1.3.9/docs/examples/example-example3/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example30/
  inflating: angular-1.3.9/docs/examples/example-example30/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example30/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example30/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example30/index.html  
  inflating: angular-1.3.9/docs/examples/example-example30/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example30/script.js  
   creating: angular-1.3.9/docs/examples/example-example31/
  inflating: angular-1.3.9/docs/examples/example-example31/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example31/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example31/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example31/index.html  
  inflating: angular-1.3.9/docs/examples/example-example31/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example32/
  inflating: angular-1.3.9/docs/examples/example-example32/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example32/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example32/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example32/index.html  
  inflating: angular-1.3.9/docs/examples/example-example32/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example33/
  inflating: angular-1.3.9/docs/examples/example-example33/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example33/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example33/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example33/index.html  
  inflating: angular-1.3.9/docs/examples/example-example33/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example33/script.js  
   creating: angular-1.3.9/docs/examples/example-example34/
  inflating: angular-1.3.9/docs/examples/example-example34/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example34/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example34/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example34/index.html  
  inflating: angular-1.3.9/docs/examples/example-example34/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example34/script.js  
   creating: angular-1.3.9/docs/examples/example-example35/
  inflating: angular-1.3.9/docs/examples/example-example35/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example35/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example35/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example35/index.html  
  inflating: angular-1.3.9/docs/examples/example-example35/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example35/script.js  
   creating: angular-1.3.9/docs/examples/example-example36/
  inflating: angular-1.3.9/docs/examples/example-example36/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example36/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example36/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example36/index.html  
  inflating: angular-1.3.9/docs/examples/example-example36/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example36/script.js  
   creating: angular-1.3.9/docs/examples/example-example37/
  inflating: angular-1.3.9/docs/examples/example-example37/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example37/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example37/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example37/index.html  
  inflating: angular-1.3.9/docs/examples/example-example37/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example37/script.js  
   creating: angular-1.3.9/docs/examples/example-example38/
  inflating: angular-1.3.9/docs/examples/example-example38/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example38/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example38/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example38/index.html  
  inflating: angular-1.3.9/docs/examples/example-example38/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example38/script.js  
   creating: angular-1.3.9/docs/examples/example-example39/
  inflating: angular-1.3.9/docs/examples/example-example39/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example39/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example39/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example39/index.html  
  inflating: angular-1.3.9/docs/examples/example-example39/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example39/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example39/script.js  
   creating: angular-1.3.9/docs/examples/example-example4/
  inflating: angular-1.3.9/docs/examples/example-example4/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example4/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example4/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example4/index.html  
  inflating: angular-1.3.9/docs/examples/example-example4/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example4/style.css  
   creating: angular-1.3.9/docs/examples/example-example40/
  inflating: angular-1.3.9/docs/examples/example-example40/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example40/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example40/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example40/index.html  
  inflating: angular-1.3.9/docs/examples/example-example40/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example40/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example40/script.js  
   creating: angular-1.3.9/docs/examples/example-example41/
  inflating: angular-1.3.9/docs/examples/example-example41/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example41/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example41/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example41/index.html  
  inflating: angular-1.3.9/docs/examples/example-example41/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example41/script.js  
   creating: angular-1.3.9/docs/examples/example-example42/
  inflating: angular-1.3.9/docs/examples/example-example42/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example42/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example42/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example42/index.html  
  inflating: angular-1.3.9/docs/examples/example-example42/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example42/script.js  
  inflating: angular-1.3.9/docs/examples/example-example42/style.css  
   creating: angular-1.3.9/docs/examples/example-example43/
  inflating: angular-1.3.9/docs/examples/example-example43/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example43/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example43/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example43/index.html  
  inflating: angular-1.3.9/docs/examples/example-example43/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example43/script.js  
   creating: angular-1.3.9/docs/examples/example-example44/
  inflating: angular-1.3.9/docs/examples/example-example44/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example44/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example44/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example44/index.html  
  inflating: angular-1.3.9/docs/examples/example-example44/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example44/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example44/script.js  
   creating: angular-1.3.9/docs/examples/example-example45/
  inflating: angular-1.3.9/docs/examples/example-example45/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example45/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example45/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example45/index.html  
  inflating: angular-1.3.9/docs/examples/example-example45/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example46/
  inflating: angular-1.3.9/docs/examples/example-example46/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example46/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example46/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example46/index.html  
  inflating: angular-1.3.9/docs/examples/example-example46/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example46/script.js  
   creating: angular-1.3.9/docs/examples/example-example47/
  inflating: angular-1.3.9/docs/examples/example-example47/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example47/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example47/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example47/index.html  
  inflating: angular-1.3.9/docs/examples/example-example47/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example47/script.js  
  inflating: angular-1.3.9/docs/examples/example-example47/style.css  
   creating: angular-1.3.9/docs/examples/example-example48/
  inflating: angular-1.3.9/docs/examples/example-example48/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example48/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example48/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example48/index.html  
  inflating: angular-1.3.9/docs/examples/example-example48/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example48/script.js  
  inflating: angular-1.3.9/docs/examples/example-example48/style.css  
   creating: angular-1.3.9/docs/examples/example-example49/
  inflating: angular-1.3.9/docs/examples/example-example49/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example49/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example49/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example49/index.html  
  inflating: angular-1.3.9/docs/examples/example-example49/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example49/script.js  
  inflating: angular-1.3.9/docs/examples/example-example49/style.css  
   creating: angular-1.3.9/docs/examples/example-example5/
  inflating: angular-1.3.9/docs/examples/example-example5/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example5/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example5/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example5/index.html  
  inflating: angular-1.3.9/docs/examples/example-example5/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example5/script.js  
   creating: angular-1.3.9/docs/examples/example-example50/
  inflating: angular-1.3.9/docs/examples/example-example50/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example50/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example50/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example50/index.html  
  inflating: angular-1.3.9/docs/examples/example-example50/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example50/script.js  
  inflating: angular-1.3.9/docs/examples/example-example50/style.css  
   creating: angular-1.3.9/docs/examples/example-example51/
  inflating: angular-1.3.9/docs/examples/example-example51/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example51/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example51/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example51/index.html  
  inflating: angular-1.3.9/docs/examples/example-example51/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example51/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example52/
  inflating: angular-1.3.9/docs/examples/example-example52/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example52/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example52/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example52/index.html  
  inflating: angular-1.3.9/docs/examples/example-example52/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example52/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example53/
  inflating: angular-1.3.9/docs/examples/example-example53/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example53/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example53/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example53/index.html  
  inflating: angular-1.3.9/docs/examples/example-example53/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example53/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example54/
  inflating: angular-1.3.9/docs/examples/example-example54/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example54/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example54/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example54/index.html  
  inflating: angular-1.3.9/docs/examples/example-example54/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example54/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example55/
  inflating: angular-1.3.9/docs/examples/example-example55/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example55/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example55/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example55/index.html  
  inflating: angular-1.3.9/docs/examples/example-example55/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example55/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example56/
  inflating: angular-1.3.9/docs/examples/example-example56/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example56/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example56/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example56/index.html  
  inflating: angular-1.3.9/docs/examples/example-example56/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example56/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example57/
  inflating: angular-1.3.9/docs/examples/example-example57/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example57/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example57/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example57/index.html  
  inflating: angular-1.3.9/docs/examples/example-example57/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example57/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example58/
  inflating: angular-1.3.9/docs/examples/example-example58/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example58/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example58/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example58/index.html  
  inflating: angular-1.3.9/docs/examples/example-example58/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example58/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example59/
  inflating: angular-1.3.9/docs/examples/example-example59/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example59/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example59/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example59/index.html  
  inflating: angular-1.3.9/docs/examples/example-example59/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example59/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example6/
  inflating: angular-1.3.9/docs/examples/example-example6/app.js  
  inflating: angular-1.3.9/docs/examples/example-example6/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example6/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example6/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example6/index.html  
  inflating: angular-1.3.9/docs/examples/example-example6/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example60/
  inflating: angular-1.3.9/docs/examples/example-example60/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example60/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example60/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example60/index.html  
  inflating: angular-1.3.9/docs/examples/example-example60/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example60/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example61/
  inflating: angular-1.3.9/docs/examples/example-example61/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example61/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example61/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example61/index.html  
  inflating: angular-1.3.9/docs/examples/example-example61/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example61/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example61/script.js  
   creating: angular-1.3.9/docs/examples/example-example62/
  inflating: angular-1.3.9/docs/examples/example-example62/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example62/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example62/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example62/index.html  
  inflating: angular-1.3.9/docs/examples/example-example62/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example62/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example62/style.css  
   creating: angular-1.3.9/docs/examples/example-example63/
  inflating: angular-1.3.9/docs/examples/example-example63/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example63/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example63/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example63/index.html  
  inflating: angular-1.3.9/docs/examples/example-example63/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example63/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example63/style.css  
   creating: angular-1.3.9/docs/examples/example-example64/
  inflating: angular-1.3.9/docs/examples/example-example64/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example64/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example64/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example64/index.html  
  inflating: angular-1.3.9/docs/examples/example-example64/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example64/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example64/style.css  
   creating: angular-1.3.9/docs/examples/example-example65/
  inflating: angular-1.3.9/docs/examples/example-example65/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example65/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example65/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example65/index.html  
  inflating: angular-1.3.9/docs/examples/example-example65/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example65/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example65/style.css  
   creating: angular-1.3.9/docs/examples/example-example66/
  inflating: angular-1.3.9/docs/examples/example-example66/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example66/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example66/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example66/index.html  
  inflating: angular-1.3.9/docs/examples/example-example66/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example66/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example67/
  inflating: angular-1.3.9/docs/examples/example-example67/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example67/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example67/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example67/index.html  
  inflating: angular-1.3.9/docs/examples/example-example67/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example67/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example68/
  inflating: angular-1.3.9/docs/examples/example-example68/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example68/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example68/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example68/index.html  
  inflating: angular-1.3.9/docs/examples/example-example68/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example69/
  inflating: angular-1.3.9/docs/examples/example-example69/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example69/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example69/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example69/index.html  
  inflating: angular-1.3.9/docs/examples/example-example69/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example7/
  inflating: angular-1.3.9/docs/examples/example-example7/app.js  
  inflating: angular-1.3.9/docs/examples/example-example7/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example7/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example7/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example7/index.html  
  inflating: angular-1.3.9/docs/examples/example-example7/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example70/
  inflating: angular-1.3.9/docs/examples/example-example70/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example70/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example70/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example70/index.html  
  inflating: angular-1.3.9/docs/examples/example-example70/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example71/
  inflating: angular-1.3.9/docs/examples/example-example71/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example71/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example71/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example71/index.html  
  inflating: angular-1.3.9/docs/examples/example-example71/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example72/
  inflating: angular-1.3.9/docs/examples/example-example72/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example72/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example72/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example72/index.html  
  inflating: angular-1.3.9/docs/examples/example-example72/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example73/
  inflating: angular-1.3.9/docs/examples/example-example73/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example73/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example73/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example73/index.html  
  inflating: angular-1.3.9/docs/examples/example-example73/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example74/
  inflating: angular-1.3.9/docs/examples/example-example74/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example74/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example74/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example74/index.html  
  inflating: angular-1.3.9/docs/examples/example-example74/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example75/
  inflating: angular-1.3.9/docs/examples/example-example75/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example75/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example75/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example75/index.html  
  inflating: angular-1.3.9/docs/examples/example-example75/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example76/
  inflating: angular-1.3.9/docs/examples/example-example76/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example76/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example76/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example76/index.html  
  inflating: angular-1.3.9/docs/examples/example-example76/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example77/
  inflating: angular-1.3.9/docs/examples/example-example77/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example77/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example77/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example77/index.html  
  inflating: angular-1.3.9/docs/examples/example-example77/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example78/
  inflating: angular-1.3.9/docs/examples/example-example78/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example78/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example78/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example78/index.html  
  inflating: angular-1.3.9/docs/examples/example-example78/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example78/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example79/
  inflating: angular-1.3.9/docs/examples/example-example79/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example79/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example79/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example79/index.html  
  inflating: angular-1.3.9/docs/examples/example-example79/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example8/
  inflating: angular-1.3.9/docs/examples/example-example8/app.css  
  inflating: angular-1.3.9/docs/examples/example-example8/app.js  
  inflating: angular-1.3.9/docs/examples/example-example8/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example8/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example8/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example8/index.html  
  inflating: angular-1.3.9/docs/examples/example-example8/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example80/
  inflating: angular-1.3.9/docs/examples/example-example80/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example80/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example80/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example80/index.html  
  inflating: angular-1.3.9/docs/examples/example-example80/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example81/
  inflating: angular-1.3.9/docs/examples/example-example81/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example81/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example81/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example81/index.html  
  inflating: angular-1.3.9/docs/examples/example-example81/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example82/
  inflating: angular-1.3.9/docs/examples/example-example82/animations.css  
  inflating: angular-1.3.9/docs/examples/example-example82/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example82/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example82/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example82/index.html  
  inflating: angular-1.3.9/docs/examples/example-example82/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example83/
  inflating: angular-1.3.9/docs/examples/example-example83/animations.css  
  inflating: angular-1.3.9/docs/examples/example-example83/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example83/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example83/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example83/index.html  
  inflating: angular-1.3.9/docs/examples/example-example83/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example83/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example83/script.js  
  inflating: angular-1.3.9/docs/examples/example-example83/template1.html  
  inflating: angular-1.3.9/docs/examples/example-example83/template2.html  
   creating: angular-1.3.9/docs/examples/example-example84/
  inflating: angular-1.3.9/docs/examples/example-example84/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example84/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example84/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example84/index.html  
  inflating: angular-1.3.9/docs/examples/example-example84/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example84/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example85/
  inflating: angular-1.3.9/docs/examples/example-example85/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example85/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example85/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example85/index.html  
  inflating: angular-1.3.9/docs/examples/example-example85/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example86/
  inflating: angular-1.3.9/docs/examples/example-example86/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example86/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example86/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example86/index.html  
  inflating: angular-1.3.9/docs/examples/example-example86/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example86/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example87/
  inflating: angular-1.3.9/docs/examples/example-example87/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example87/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example87/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example87/index.html  
  inflating: angular-1.3.9/docs/examples/example-example87/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example87/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example88/
  inflating: angular-1.3.9/docs/examples/example-example88/animations.css  
  inflating: angular-1.3.9/docs/examples/example-example88/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example88/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example88/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example88/index.html  
  inflating: angular-1.3.9/docs/examples/example-example88/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example88/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example89/
  inflating: angular-1.3.9/docs/examples/example-example89/animations.css  
  inflating: angular-1.3.9/docs/examples/example-example89/glyphicons.css  
  inflating: angular-1.3.9/docs/examples/example-example89/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example89/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example89/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example89/index.html  
  inflating: angular-1.3.9/docs/examples/example-example89/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example89/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example9/
  inflating: angular-1.3.9/docs/examples/example-example9/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example9/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example9/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example9/index.html  
  inflating: angular-1.3.9/docs/examples/example-example9/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example9/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example9/script.js  
   creating: angular-1.3.9/docs/examples/example-example90/
  inflating: angular-1.3.9/docs/examples/example-example90/animations.css  
  inflating: angular-1.3.9/docs/examples/example-example90/glyphicons.css  
  inflating: angular-1.3.9/docs/examples/example-example90/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example90/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example90/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example90/index.html  
  inflating: angular-1.3.9/docs/examples/example-example90/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example90/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example91/
  inflating: angular-1.3.9/docs/examples/example-example91/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example91/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example91/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example91/index.html  
  inflating: angular-1.3.9/docs/examples/example-example91/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example91/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example91/style.css  
   creating: angular-1.3.9/docs/examples/example-example92/
  inflating: angular-1.3.9/docs/examples/example-example92/animations.css  
  inflating: angular-1.3.9/docs/examples/example-example92/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example92/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example92/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example92/index.html  
  inflating: angular-1.3.9/docs/examples/example-example92/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example92/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example92/script.js  
   creating: angular-1.3.9/docs/examples/example-example93/
  inflating: angular-1.3.9/docs/examples/example-example93/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example93/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example93/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example93/index.html  
  inflating: angular-1.3.9/docs/examples/example-example93/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example93/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example94/
  inflating: angular-1.3.9/docs/examples/example-example94/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example94/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example94/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example94/index.html  
  inflating: angular-1.3.9/docs/examples/example-example94/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example94/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example95/
  inflating: angular-1.3.9/docs/examples/example-example95/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example95/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example95/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example95/index.html  
  inflating: angular-1.3.9/docs/examples/example-example95/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example95/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example96/
  inflating: angular-1.3.9/docs/examples/example-example96/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example96/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example96/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example96/index.html  
  inflating: angular-1.3.9/docs/examples/example-example96/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example96/script.js  
   creating: angular-1.3.9/docs/examples/example-example97/
  inflating: angular-1.3.9/docs/examples/example-example97/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example97/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example97/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example97/index.html  
  inflating: angular-1.3.9/docs/examples/example-example97/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example97/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example98/
  inflating: angular-1.3.9/docs/examples/example-example98/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example98/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example98/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example98/index.html  
  inflating: angular-1.3.9/docs/examples/example-example98/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example98/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example99/
  inflating: angular-1.3.9/docs/examples/example-example99/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example99/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example99/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example99/index.html  
  inflating: angular-1.3.9/docs/examples/example-example99/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example99/protractor.js  
   creating: angular-1.3.9/docs/examples/example-guide-concepts-1/
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-1/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-1/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-1/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-1/index.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-1/manifest.json  
   creating: angular-1.3.9/docs/examples/example-guide-concepts-2/
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-2/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-2/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-2/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-2/index.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-2/invoice1.js  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-2/manifest.json  
   creating: angular-1.3.9/docs/examples/example-guide-concepts-21/
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-21/finance2.js  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-21/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-21/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-21/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-21/index.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-21/invoice2.js  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-21/manifest.json  
   creating: angular-1.3.9/docs/examples/example-guide-concepts-3/
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-3/finance3.js  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-3/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-3/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-3/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-3/index.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-3/invoice3.js  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-3/manifest.json  
   creating: angular-1.3.9/docs/examples/example-input-directive/
  inflating: angular-1.3.9/docs/examples/example-input-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-input-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-input-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-input-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-input-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-input-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-location-hashbang-mode/
  inflating: angular-1.3.9/docs/examples/example-location-hashbang-mode/addressBar.js  
  inflating: angular-1.3.9/docs/examples/example-location-hashbang-mode/app.js  
  inflating: angular-1.3.9/docs/examples/example-location-hashbang-mode/fakeBrowser.js  
  inflating: angular-1.3.9/docs/examples/example-location-hashbang-mode/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-location-hashbang-mode/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-location-hashbang-mode/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-location-hashbang-mode/index.html  
  inflating: angular-1.3.9/docs/examples/example-location-hashbang-mode/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-location-hashbang-mode/protractor.js  
   creating: angular-1.3.9/docs/examples/example-location-html5-mode/
  inflating: angular-1.3.9/docs/examples/example-location-html5-mode/addressBar.js  
  inflating: angular-1.3.9/docs/examples/example-location-html5-mode/app.js  
  inflating: angular-1.3.9/docs/examples/example-location-html5-mode/fakeBrowser.js  
  inflating: angular-1.3.9/docs/examples/example-location-html5-mode/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-location-html5-mode/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-location-html5-mode/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-location-html5-mode/index.html  
  inflating: angular-1.3.9/docs/examples/example-location-html5-mode/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-location-html5-mode/protractor.js  
   creating: angular-1.3.9/docs/examples/example-month-input-directive/
  inflating: angular-1.3.9/docs/examples/example-month-input-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-month-input-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-month-input-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-month-input-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-month-input-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-month-input-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-ng-model-cancel-update/
  inflating: angular-1.3.9/docs/examples/example-ng-model-cancel-update/app.js  
  inflating: angular-1.3.9/docs/examples/example-ng-model-cancel-update/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ng-model-cancel-update/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ng-model-cancel-update/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ng-model-cancel-update/index.html  
  inflating: angular-1.3.9/docs/examples/example-ng-model-cancel-update/manifest.json  
   creating: angular-1.3.9/docs/examples/example-ngChange-directive/
  inflating: angular-1.3.9/docs/examples/example-ngChange-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ngChange-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ngChange-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ngChange-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-ngChange-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-ngChange-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-ngController/
  inflating: angular-1.3.9/docs/examples/example-ngController/app.js  
  inflating: angular-1.3.9/docs/examples/example-ngController/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ngController/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ngController/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ngController/index.html  
  inflating: angular-1.3.9/docs/examples/example-ngController/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-ngController/protractor.js  
   creating: angular-1.3.9/docs/examples/example-ngControllerAs/
  inflating: angular-1.3.9/docs/examples/example-ngControllerAs/app.js  
  inflating: angular-1.3.9/docs/examples/example-ngControllerAs/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ngControllerAs/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ngControllerAs/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ngControllerAs/index.html  
  inflating: angular-1.3.9/docs/examples/example-ngControllerAs/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-ngControllerAs/protractor.js  
   creating: angular-1.3.9/docs/examples/example-ngList-directive/
   creating: angular-1.3.9/docs/examples/example-ngList-directive-newlines/
  inflating: angular-1.3.9/docs/examples/example-ngList-directive-newlines/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ngList-directive-newlines/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ngList-directive-newlines/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ngList-directive-newlines/index.html  
  inflating: angular-1.3.9/docs/examples/example-ngList-directive-newlines/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-ngList-directive-newlines/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-ngList-directive/app.js  
  inflating: angular-1.3.9/docs/examples/example-ngList-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ngList-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ngList-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ngList-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-ngList-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-ngList-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-ngMessages-directive/
  inflating: angular-1.3.9/docs/examples/example-ngMessages-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ngMessages-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ngMessages-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ngMessages-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-ngMessages-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-ngMessages-directive/script.js  
   creating: angular-1.3.9/docs/examples/example-ngModel-getter-setter/
  inflating: angular-1.3.9/docs/examples/example-ngModel-getter-setter/app.js  
  inflating: angular-1.3.9/docs/examples/example-ngModel-getter-setter/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ngModel-getter-setter/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ngModel-getter-setter/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ngModel-getter-setter/index.html  
  inflating: angular-1.3.9/docs/examples/example-ngModel-getter-setter/manifest.json  
   creating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-blur/
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-blur/app.js  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-blur/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-blur/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-blur/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-blur/index.html  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-blur/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-blur/protractor.js  
   creating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-debounce/
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-debounce/app.js  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-debounce/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-debounce/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-debounce/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-debounce/index.html  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-debounce/manifest.json  
   creating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-getter-setter/
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-getter-setter/app.js  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-getter-setter/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-getter-setter/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-getter-setter/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-getter-setter/index.html  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-getter-setter/manifest.json  
   creating: angular-1.3.9/docs/examples/example-ngValue-directive/
  inflating: angular-1.3.9/docs/examples/example-ngValue-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ngValue-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ngValue-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ngValue-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-ngValue-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-ngValue-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-ngView-directive/
  inflating: angular-1.3.9/docs/examples/example-ngView-directive/animations.css  
  inflating: angular-1.3.9/docs/examples/example-ngView-directive/book.html  
  inflating: angular-1.3.9/docs/examples/example-ngView-directive/chapter.html  
  inflating: angular-1.3.9/docs/examples/example-ngView-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ngView-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ngView-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ngView-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-ngView-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-ngView-directive/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-ngView-directive/script.js  
   creating: angular-1.3.9/docs/examples/example-number-input-directive/
  inflating: angular-1.3.9/docs/examples/example-number-input-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-number-input-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-number-input-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-number-input-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-number-input-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-number-input-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-radio-input-directive/
  inflating: angular-1.3.9/docs/examples/example-radio-input-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-radio-input-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-radio-input-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-radio-input-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-radio-input-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-radio-input-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-text-input-directive/
  inflating: angular-1.3.9/docs/examples/example-text-input-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-text-input-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-text-input-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-text-input-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-text-input-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-text-input-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-time-input-directive/
  inflating: angular-1.3.9/docs/examples/example-time-input-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-time-input-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-time-input-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-time-input-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-time-input-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-time-input-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-url-input-directive/
  inflating: angular-1.3.9/docs/examples/example-url-input-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-url-input-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-url-input-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-url-input-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-url-input-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-url-input-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-week-input-directive/
  inflating: angular-1.3.9/docs/examples/example-week-input-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-week-input-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-week-input-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-week-input-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-week-input-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-week-input-directive/protractor.js  
  inflating: angular-1.3.9/docs/favicon.ico  
   creating: angular-1.3.9/docs/img/
  inflating: angular-1.3.9/docs/img/AngularJS-small.png  
  inflating: angular-1.3.9/docs/img/One_Way_Data_Binding.png  
  inflating: angular-1.3.9/docs/img/Two_Way_Data_Binding.png  
  inflating: angular-1.3.9/docs/img/angular_parts.png  
  inflating: angular-1.3.9/docs/img/angularjs-for-header-only.svg  
  inflating: angular-1.3.9/docs/img/bullet.png  
  inflating: angular-1.3.9/docs/img/form_data_flow.png  
  inflating: angular-1.3.9/docs/img/glyphicons-halflings-white.png  
  inflating: angular-1.3.9/docs/img/glyphicons-halflings.png  
   creating: angular-1.3.9/docs/img/guide/
  inflating: angular-1.3.9/docs/img/guide/concepts-databinding1.png  
  inflating: angular-1.3.9/docs/img/guide/concepts-databinding2.png  
  inflating: angular-1.3.9/docs/img/guide/concepts-directive.png  
  inflating: angular-1.3.9/docs/img/guide/concepts-module-injector.png  
  inflating: angular-1.3.9/docs/img/guide/concepts-module-service.png  
  inflating: angular-1.3.9/docs/img/guide/concepts-runtime.png  
  inflating: angular-1.3.9/docs/img/guide/concepts-scope-watch-strategies.png  
  inflating: angular-1.3.9/docs/img/guide/concepts-scope.png  
  inflating: angular-1.3.9/docs/img/guide/concepts-startup.png  
  inflating: angular-1.3.9/docs/img/guide/concepts-view.png  
  inflating: angular-1.3.9/docs/img/guide/di_sequence_final.png  
  inflating: angular-1.3.9/docs/img/guide/dom_scope_final.png  
  inflating: angular-1.3.9/docs/img/guide/forms-debounce.gif  
  inflating: angular-1.3.9/docs/img/guide/forms-update-on-blur.gif  
  inflating: angular-1.3.9/docs/img/guide/hashbang_vs_regular_url.jpg  
  inflating: angular-1.3.9/docs/img/guide/scenario_runner.png  
  inflating: angular-1.3.9/docs/img/guide/simple_scope_final.png  
  inflating: angular-1.3.9/docs/img/helloworld.png  
  inflating: angular-1.3.9/docs/img/helloworld_2way.png  
   creating: angular-1.3.9/docs/img/tutorial/
  inflating: angular-1.3.9/docs/img/tutorial/catalog_screen.png  
  inflating: angular-1.3.9/docs/img/tutorial/tutorial_00.png  
  inflating: angular-1.3.9/docs/img/tutorial/tutorial_00_final.png  
  inflating: angular-1.3.9/docs/img/tutorial/tutorial_02.png  
  inflating: angular-1.3.9/docs/img/tutorial/tutorial_03.png  
  inflating: angular-1.3.9/docs/img/tutorial/tutorial_04.png  
  inflating: angular-1.3.9/docs/img/tutorial/tutorial_05.png  
  inflating: angular-1.3.9/docs/img/tutorial/tutorial_05.pptx  
  inflating: angular-1.3.9/docs/img/tutorial/tutorial_07_final.png  
  inflating: angular-1.3.9/docs/img/tutorial/tutorial_08-09_final.png  
  inflating: angular-1.3.9/docs/img/tutorial/tutorial_10-11_final.png  
  inflating: angular-1.3.9/docs/img/tutorial/xhr_service_final.png  
  inflating: angular-1.3.9/docs/index-debug.html  
  inflating: angular-1.3.9/docs/index-jquery.html  
  inflating: angular-1.3.9/docs/index-production.html  
  inflating: angular-1.3.9/docs/index.html  
   creating: angular-1.3.9/docs/js/
   creating: angular-1.3.9/docs/js/angular-bootstrap/
  inflating: angular-1.3.9/docs/js/angular-bootstrap/bootstrap.js  
  inflating: angular-1.3.9/docs/js/angular-bootstrap/bootstrap.min.js  
  inflating: angular-1.3.9/docs/js/angular-bootstrap/bootstrap.min.js.map  
  inflating: angular-1.3.9/docs/js/angular-bootstrap/dropdown-toggle.js  
  inflating: angular-1.3.9/docs/js/angular-bootstrap/dropdown-toggle.min.js  
  inflating: angular-1.3.9/docs/js/angular-bootstrap/dropdown-toggle.min.js.map  
  inflating: angular-1.3.9/docs/js/docs.js  
  inflating: angular-1.3.9/docs/js/docs.min.js  
  inflating: angular-1.3.9/docs/js/docs.min.js.map  
  inflating: angular-1.3.9/docs/js/nav-data.js  
  inflating: angular-1.3.9/docs/js/pages-data.js  
  inflating: angular-1.3.9/docs/js/search-data.json  
  inflating: angular-1.3.9/docs/js/search-worker.js  
  inflating: angular-1.3.9/docs/js/search-worker.min.js  
  inflating: angular-1.3.9/docs/js/search-worker.min.js.map  
  inflating: angular-1.3.9/docs/js/versions-data.js  
   creating: angular-1.3.9/docs/partials/
   creating: angular-1.3.9/docs/partials/api/
  inflating: angular-1.3.9/docs/partials/api.html  
   creating: angular-1.3.9/docs/partials/api/auto/
  inflating: angular-1.3.9/docs/partials/api/auto.html  
   creating: angular-1.3.9/docs/partials/api/auto/service/
  inflating: angular-1.3.9/docs/partials/api/auto/service.html  
  inflating: angular-1.3.9/docs/partials/api/auto/service/$injector.html  
  inflating: angular-1.3.9/docs/partials/api/auto/service/$provide.html  
   creating: angular-1.3.9/docs/partials/api/ng/
  inflating: angular-1.3.9/docs/partials/api/ng.html  
   creating: angular-1.3.9/docs/partials/api/ng/directive/
  inflating: angular-1.3.9/docs/partials/api/ng/directive.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/a.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/form.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/input.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngApp.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngBind.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngBindHtml.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngBindTemplate.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngBlur.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngChange.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngChecked.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngClass.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngClassEven.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngClassOdd.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngClick.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngCloak.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngController.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngCopy.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngCsp.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngCut.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngDblclick.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngDisabled.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngFocus.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngForm.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngHide.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngHref.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngIf.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngInclude.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngInit.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngKeydown.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngKeypress.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngKeyup.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngList.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngModel.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngModelOptions.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngMousedown.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngMouseenter.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngMouseleave.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngMousemove.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngMouseover.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngMouseup.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngNonBindable.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngOpen.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngPaste.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngPluralize.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngReadonly.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngRepeat.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngSelected.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngShow.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngSrc.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngSrcset.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngStyle.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngSubmit.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngSwitch.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngTransclude.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngValue.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/script.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/select.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/textarea.html  
   creating: angular-1.3.9/docs/partials/api/ng/filter/
  inflating: angular-1.3.9/docs/partials/api/ng/filter.html  
  inflating: angular-1.3.9/docs/partials/api/ng/filter/currency.html  
  inflating: angular-1.3.9/docs/partials/api/ng/filter/date.html  
  inflating: angular-1.3.9/docs/partials/api/ng/filter/filter.html  
  inflating: angular-1.3.9/docs/partials/api/ng/filter/json.html  
  inflating: angular-1.3.9/docs/partials/api/ng/filter/limitTo.html  
  inflating: angular-1.3.9/docs/partials/api/ng/filter/lowercase.html  
  inflating: angular-1.3.9/docs/partials/api/ng/filter/number.html  
  inflating: angular-1.3.9/docs/partials/api/ng/filter/orderBy.html  
  inflating: angular-1.3.9/docs/partials/api/ng/filter/uppercase.html  
   creating: angular-1.3.9/docs/partials/api/ng/function/
  inflating: angular-1.3.9/docs/partials/api/ng/function.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.bind.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.bootstrap.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.copy.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.element.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.equals.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.extend.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.forEach.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.fromJson.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.identity.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.injector.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.isArray.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.isDate.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.isDefined.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.isElement.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.isFunction.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.isNumber.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.isObject.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.isString.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.isUndefined.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.lowercase.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.module.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.noop.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.reloadWithDebugInfo.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.toJson.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.uppercase.html  
   creating: angular-1.3.9/docs/partials/api/ng/input/
  inflating: angular-1.3.9/docs/partials/api/ng/input.html  
  inflating: angular-1.3.9/docs/partials/api/ng/input/input[checkbox].html  
  inflating: angular-1.3.9/docs/partials/api/ng/input/input[date].html  
  inflating: angular-1.3.9/docs/partials/api/ng/input/input[datetime-local].html  
  inflating: angular-1.3.9/docs/partials/api/ng/input/input[email].html  
  inflating: angular-1.3.9/docs/partials/api/ng/input/input[month].html  
  inflating: angular-1.3.9/docs/partials/api/ng/input/input[number].html  
  inflating: angular-1.3.9/docs/partials/api/ng/input/input[radio].html  
  inflating: angular-1.3.9/docs/partials/api/ng/input/input[text].html  
  inflating: angular-1.3.9/docs/partials/api/ng/input/input[time].html  
  inflating: angular-1.3.9/docs/partials/api/ng/input/input[url].html  
  inflating: angular-1.3.9/docs/partials/api/ng/input/input[week].html  
   creating: angular-1.3.9/docs/partials/api/ng/object/
  inflating: angular-1.3.9/docs/partials/api/ng/object.html  
  inflating: angular-1.3.9/docs/partials/api/ng/object/angular.version.html  
   creating: angular-1.3.9/docs/partials/api/ng/provider/
  inflating: angular-1.3.9/docs/partials/api/ng/provider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$anchorScrollProvider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$animateProvider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$compileProvider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$controllerProvider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$filterProvider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$httpProvider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$interpolateProvider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$locationProvider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$logProvider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$parseProvider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$rootScopeProvider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$sceDelegateProvider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$sceProvider.html  
   creating: angular-1.3.9/docs/partials/api/ng/service/
  inflating: angular-1.3.9/docs/partials/api/ng/service.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$anchorScroll.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$animate.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$cacheFactory.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$compile.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$controller.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$document.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$exceptionHandler.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$filter.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$http.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$httpBackend.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$interpolate.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$interval.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$locale.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$location.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$log.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$parse.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$q.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$rootElement.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$rootScope.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$sce.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$sceDelegate.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$templateCache.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$templateRequest.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$timeout.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$window.html  
   creating: angular-1.3.9/docs/partials/api/ng/type/
  inflating: angular-1.3.9/docs/partials/api/ng/type.html  
  inflating: angular-1.3.9/docs/partials/api/ng/type/$cacheFactory.Cache.html  
  inflating: angular-1.3.9/docs/partials/api/ng/type/$compile.directive.Attributes.html  
  inflating: angular-1.3.9/docs/partials/api/ng/type/$rootScope.Scope.html  
  inflating: angular-1.3.9/docs/partials/api/ng/type/angular.Module.html  
  inflating: angular-1.3.9/docs/partials/api/ng/type/form.FormController.html  
  inflating: angular-1.3.9/docs/partials/api/ng/type/ngModel.NgModelController.html  
   creating: angular-1.3.9/docs/partials/api/ngAnimate/
  inflating: angular-1.3.9/docs/partials/api/ngAnimate.html  
   creating: angular-1.3.9/docs/partials/api/ngAnimate/provider/
  inflating: angular-1.3.9/docs/partials/api/ngAnimate/provider.html  
  inflating: angular-1.3.9/docs/partials/api/ngAnimate/provider/$animateProvider.html  
   creating: angular-1.3.9/docs/partials/api/ngAnimate/service/
  inflating: angular-1.3.9/docs/partials/api/ngAnimate/service.html  
  inflating: angular-1.3.9/docs/partials/api/ngAnimate/service/$animate.html  
   creating: angular-1.3.9/docs/partials/api/ngAria/
  inflating: angular-1.3.9/docs/partials/api/ngAria.html  
   creating: angular-1.3.9/docs/partials/api/ngAria/provider/
  inflating: angular-1.3.9/docs/partials/api/ngAria/provider.html  
  inflating: angular-1.3.9/docs/partials/api/ngAria/provider/$ariaProvider.html  
   creating: angular-1.3.9/docs/partials/api/ngAria/service/
  inflating: angular-1.3.9/docs/partials/api/ngAria/service.html  
  inflating: angular-1.3.9/docs/partials/api/ngAria/service/$aria.html  
   creating: angular-1.3.9/docs/partials/api/ngCookies/
  inflating: angular-1.3.9/docs/partials/api/ngCookies.html  
   creating: angular-1.3.9/docs/partials/api/ngCookies/service/
  inflating: angular-1.3.9/docs/partials/api/ngCookies/service.html  
  inflating: angular-1.3.9/docs/partials/api/ngCookies/service/$cookieStore.html  
  inflating: angular-1.3.9/docs/partials/api/ngCookies/service/$cookies.html  
   creating: angular-1.3.9/docs/partials/api/ngMessages/
  inflating: angular-1.3.9/docs/partials/api/ngMessages.html  
   creating: angular-1.3.9/docs/partials/api/ngMessages/directive/
  inflating: angular-1.3.9/docs/partials/api/ngMessages/directive.html  
  inflating: angular-1.3.9/docs/partials/api/ngMessages/directive/ngMessage.html  
  inflating: angular-1.3.9/docs/partials/api/ngMessages/directive/ngMessages.html  
   creating: angular-1.3.9/docs/partials/api/ngMock/
  inflating: angular-1.3.9/docs/partials/api/ngMock.html  
   creating: angular-1.3.9/docs/partials/api/ngMock/function/
  inflating: angular-1.3.9/docs/partials/api/ngMock/function.html  
  inflating: angular-1.3.9/docs/partials/api/ngMock/function/angular.mock.dump.html  
  inflating: angular-1.3.9/docs/partials/api/ngMock/function/angular.mock.inject.html  
  inflating: angular-1.3.9/docs/partials/api/ngMock/function/angular.mock.module.html  
   creating: angular-1.3.9/docs/partials/api/ngMock/object/
  inflating: angular-1.3.9/docs/partials/api/ngMock/object.html  
  inflating: angular-1.3.9/docs/partials/api/ngMock/object/angular.mock.html  
   creating: angular-1.3.9/docs/partials/api/ngMock/provider/
  inflating: angular-1.3.9/docs/partials/api/ngMock/provider.html  
  inflating: angular-1.3.9/docs/partials/api/ngMock/provider/$exceptionHandlerProvider.html  
   creating: angular-1.3.9/docs/partials/api/ngMock/service/
  inflating: angular-1.3.9/docs/partials/api/ngMock/service.html  
  inflating: angular-1.3.9/docs/partials/api/ngMock/service/$exceptionHandler.html  
  inflating: angular-1.3.9/docs/partials/api/ngMock/service/$httpBackend.html  
  inflating: angular-1.3.9/docs/partials/api/ngMock/service/$interval.html  
  inflating: angular-1.3.9/docs/partials/api/ngMock/service/$log.html  
  inflating: angular-1.3.9/docs/partials/api/ngMock/service/$timeout.html  
   creating: angular-1.3.9/docs/partials/api/ngMock/type/
  inflating: angular-1.3.9/docs/partials/api/ngMock/type.html  
  inflating: angular-1.3.9/docs/partials/api/ngMock/type/$rootScope.Scope.html  
  inflating: angular-1.3.9/docs/partials/api/ngMock/type/angular.mock.TzDate.html  
   creating: angular-1.3.9/docs/partials/api/ngMockE2E/
  inflating: angular-1.3.9/docs/partials/api/ngMockE2E.html  
   creating: angular-1.3.9/docs/partials/api/ngMockE2E/service/
  inflating: angular-1.3.9/docs/partials/api/ngMockE2E/service.html  
  inflating: angular-1.3.9/docs/partials/api/ngMockE2E/service/$httpBackend.html  
   creating: angular-1.3.9/docs/partials/api/ngResource/
  inflating: angular-1.3.9/docs/partials/api/ngResource.html  
   creating: angular-1.3.9/docs/partials/api/ngResource/service/
  inflating: angular-1.3.9/docs/partials/api/ngResource/service.html  
  inflating: angular-1.3.9/docs/partials/api/ngResource/service/$resource.html  
   creating: angular-1.3.9/docs/partials/api/ngRoute/
  inflating: angular-1.3.9/docs/partials/api/ngRoute.html  
   creating: angular-1.3.9/docs/partials/api/ngRoute/directive/
  inflating: angular-1.3.9/docs/partials/api/ngRoute/directive.html  
  inflating: angular-1.3.9/docs/partials/api/ngRoute/directive/ngView.html  
   creating: angular-1.3.9/docs/partials/api/ngRoute/provider/
  inflating: angular-1.3.9/docs/partials/api/ngRoute/provider.html  
  inflating: angular-1.3.9/docs/partials/api/ngRoute/provider/$routeProvider.html  
   creating: angular-1.3.9/docs/partials/api/ngRoute/service/
  inflating: angular-1.3.9/docs/partials/api/ngRoute/service.html  
  inflating: angular-1.3.9/docs/partials/api/ngRoute/service/$route.html  
  inflating: angular-1.3.9/docs/partials/api/ngRoute/service/$routeParams.html  
   creating: angular-1.3.9/docs/partials/api/ngSanitize/
  inflating: angular-1.3.9/docs/partials/api/ngSanitize.html  
   creating: angular-1.3.9/docs/partials/api/ngSanitize/filter/
  inflating: angular-1.3.9/docs/partials/api/ngSanitize/filter.html  
  inflating: angular-1.3.9/docs/partials/api/ngSanitize/filter/linky.html  
   creating: angular-1.3.9/docs/partials/api/ngSanitize/service/
  inflating: angular-1.3.9/docs/partials/api/ngSanitize/service.html  
  inflating: angular-1.3.9/docs/partials/api/ngSanitize/service/$sanitize.html  
   creating: angular-1.3.9/docs/partials/api/ngTouch/
  inflating: angular-1.3.9/docs/partials/api/ngTouch.html  
   creating: angular-1.3.9/docs/partials/api/ngTouch/directive/
  inflating: angular-1.3.9/docs/partials/api/ngTouch/directive.html  
  inflating: angular-1.3.9/docs/partials/api/ngTouch/directive/ngClick.html  
  inflating: angular-1.3.9/docs/partials/api/ngTouch/directive/ngSwipeLeft.html  
  inflating: angular-1.3.9/docs/partials/api/ngTouch/directive/ngSwipeRight.html  
   creating: angular-1.3.9/docs/partials/api/ngTouch/service/
  inflating: angular-1.3.9/docs/partials/api/ngTouch/service.html  
  inflating: angular-1.3.9/docs/partials/api/ngTouch/service/$swipe.html  
   creating: angular-1.3.9/docs/partials/error/
  inflating: angular-1.3.9/docs/partials/error.html  
   creating: angular-1.3.9/docs/partials/error/$animate/
  inflating: angular-1.3.9/docs/partials/error/$animate.html  
  inflating: angular-1.3.9/docs/partials/error/$animate/notcsel.html  
   creating: angular-1.3.9/docs/partials/error/$cacheFactory/
  inflating: angular-1.3.9/docs/partials/error/$cacheFactory.html  
  inflating: angular-1.3.9/docs/partials/error/$cacheFactory/iid.html  
   creating: angular-1.3.9/docs/partials/error/$compile/
  inflating: angular-1.3.9/docs/partials/error/$compile.html  
  inflating: angular-1.3.9/docs/partials/error/$compile/ctreq.html  
  inflating: angular-1.3.9/docs/partials/error/$compile/iscp.html  
  inflating: angular-1.3.9/docs/partials/error/$compile/multidir.html  
  inflating: angular-1.3.9/docs/partials/error/$compile/nodomevents.html  
  inflating: angular-1.3.9/docs/partials/error/$compile/nonassign.html  
  inflating: angular-1.3.9/docs/partials/error/$compile/selmulti.html  
  inflating: angular-1.3.9/docs/partials/error/$compile/tpload.html  
  inflating: angular-1.3.9/docs/partials/error/$compile/tplrt.html  
  inflating: angular-1.3.9/docs/partials/error/$compile/uterdir.html  
   creating: angular-1.3.9/docs/partials/error/$controller/
  inflating: angular-1.3.9/docs/partials/error/$controller.html  
  inflating: angular-1.3.9/docs/partials/error/$controller/noscp.html  
   creating: angular-1.3.9/docs/partials/error/$http/
  inflating: angular-1.3.9/docs/partials/error/$http.html  
  inflating: angular-1.3.9/docs/partials/error/$http/badreq.html  
   creating: angular-1.3.9/docs/partials/error/$injector/
  inflating: angular-1.3.9/docs/partials/error/$injector.html  
  inflating: angular-1.3.9/docs/partials/error/$injector/cdep.html  
  inflating: angular-1.3.9/docs/partials/error/$injector/itkn.html  
  inflating: angular-1.3.9/docs/partials/error/$injector/modulerr.html  
  inflating: angular-1.3.9/docs/partials/error/$injector/nomod.html  
  inflating: angular-1.3.9/docs/partials/error/$injector/pget.html  
  inflating: angular-1.3.9/docs/partials/error/$injector/strictdi.html  
  inflating: angular-1.3.9/docs/partials/error/$injector/undef.html  
  inflating: angular-1.3.9/docs/partials/error/$injector/unpr.html  
   creating: angular-1.3.9/docs/partials/error/$interpolate/
  inflating: angular-1.3.9/docs/partials/error/$interpolate.html  
  inflating: angular-1.3.9/docs/partials/error/$interpolate/interr.html  
  inflating: angular-1.3.9/docs/partials/error/$interpolate/noconcat.html  
   creating: angular-1.3.9/docs/partials/error/$location/
  inflating: angular-1.3.9/docs/partials/error/$location.html  
  inflating: angular-1.3.9/docs/partials/error/$location/ipthprfx.html  
  inflating: angular-1.3.9/docs/partials/error/$location/isrcharg.html  
  inflating: angular-1.3.9/docs/partials/error/$location/nobase.html  
  inflating: angular-1.3.9/docs/partials/error/$location/nostate.html  
   creating: angular-1.3.9/docs/partials/error/$parse/
  inflating: angular-1.3.9/docs/partials/error/$parse.html  
  inflating: angular-1.3.9/docs/partials/error/$parse/isecdom.html  
  inflating: angular-1.3.9/docs/partials/error/$parse/isecff.html  
  inflating: angular-1.3.9/docs/partials/error/$parse/isecfld.html  
  inflating: angular-1.3.9/docs/partials/error/$parse/isecfn.html  
  inflating: angular-1.3.9/docs/partials/error/$parse/isecobj.html  
  inflating: angular-1.3.9/docs/partials/error/$parse/isecwindow.html  
  inflating: angular-1.3.9/docs/partials/error/$parse/lexerr.html  
  inflating: angular-1.3.9/docs/partials/error/$parse/syntax.html  
  inflating: angular-1.3.9/docs/partials/error/$parse/ueoe.html  
   creating: angular-1.3.9/docs/partials/error/$q/
  inflating: angular-1.3.9/docs/partials/error/$q.html  
  inflating: angular-1.3.9/docs/partials/error/$q/norslvr.html  
  inflating: angular-1.3.9/docs/partials/error/$q/qcycle.html  
   creating: angular-1.3.9/docs/partials/error/$resource/
  inflating: angular-1.3.9/docs/partials/error/$resource.html  
  inflating: angular-1.3.9/docs/partials/error/$resource/badargs.html  
  inflating: angular-1.3.9/docs/partials/error/$resource/badcfg.html  
  inflating: angular-1.3.9/docs/partials/error/$resource/badmember.html  
  inflating: angular-1.3.9/docs/partials/error/$resource/badname.html  
   creating: angular-1.3.9/docs/partials/error/$rootScope/
  inflating: angular-1.3.9/docs/partials/error/$rootScope.html  
  inflating: angular-1.3.9/docs/partials/error/$rootScope/infdig.html  
  inflating: angular-1.3.9/docs/partials/error/$rootScope/inprog.html  
   creating: angular-1.3.9/docs/partials/error/$sanitize/
  inflating: angular-1.3.9/docs/partials/error/$sanitize.html  
  inflating: angular-1.3.9/docs/partials/error/$sanitize/badparse.html  
   creating: angular-1.3.9/docs/partials/error/$sce/
  inflating: angular-1.3.9/docs/partials/error/$sce.html  
  inflating: angular-1.3.9/docs/partials/error/$sce/icontext.html  
  inflating: angular-1.3.9/docs/partials/error/$sce/iequirks.html  
  inflating: angular-1.3.9/docs/partials/error/$sce/imatcher.html  
  inflating: angular-1.3.9/docs/partials/error/$sce/insecurl.html  
  inflating: angular-1.3.9/docs/partials/error/$sce/itype.html  
  inflating: angular-1.3.9/docs/partials/error/$sce/iwcard.html  
  inflating: angular-1.3.9/docs/partials/error/$sce/unsafe.html  
   creating: angular-1.3.9/docs/partials/error/jqLite/
  inflating: angular-1.3.9/docs/partials/error/jqLite.html  
  inflating: angular-1.3.9/docs/partials/error/jqLite/nosel.html  
  inflating: angular-1.3.9/docs/partials/error/jqLite/offargs.html  
  inflating: angular-1.3.9/docs/partials/error/jqLite/onargs.html  
   creating: angular-1.3.9/docs/partials/error/ng/
  inflating: angular-1.3.9/docs/partials/error/ng.html  
  inflating: angular-1.3.9/docs/partials/error/ng/areq.html  
  inflating: angular-1.3.9/docs/partials/error/ng/badname.html  
  inflating: angular-1.3.9/docs/partials/error/ng/btstrpd.html  
  inflating: angular-1.3.9/docs/partials/error/ng/cpi.html  
  inflating: angular-1.3.9/docs/partials/error/ng/cpws.html  
  inflating: angular-1.3.9/docs/partials/error/ng/test.html  
   creating: angular-1.3.9/docs/partials/error/ngModel/
  inflating: angular-1.3.9/docs/partials/error/ngModel.html  
  inflating: angular-1.3.9/docs/partials/error/ngModel/constexpr.html  
  inflating: angular-1.3.9/docs/partials/error/ngModel/datefmt.html  
  inflating: angular-1.3.9/docs/partials/error/ngModel/nonassign.html  
   creating: angular-1.3.9/docs/partials/error/ngOptions/
  inflating: angular-1.3.9/docs/partials/error/ngOptions.html  
  inflating: angular-1.3.9/docs/partials/error/ngOptions/iexp.html  
  inflating: angular-1.3.9/docs/partials/error/ngOptions/trkslct.html  
   creating: angular-1.3.9/docs/partials/error/ngPattern/
  inflating: angular-1.3.9/docs/partials/error/ngPattern.html  
  inflating: angular-1.3.9/docs/partials/error/ngPattern/noregexp.html  
   creating: angular-1.3.9/docs/partials/error/ngRepeat/
  inflating: angular-1.3.9/docs/partials/error/ngRepeat.html  
  inflating: angular-1.3.9/docs/partials/error/ngRepeat/badident.html  
  inflating: angular-1.3.9/docs/partials/error/ngRepeat/dupes.html  
  inflating: angular-1.3.9/docs/partials/error/ngRepeat/iexp.html  
  inflating: angular-1.3.9/docs/partials/error/ngRepeat/iidexp.html  
   creating: angular-1.3.9/docs/partials/error/ngTransclude/
  inflating: angular-1.3.9/docs/partials/error/ngTransclude.html  
  inflating: angular-1.3.9/docs/partials/error/ngTransclude/orphan.html  
   creating: angular-1.3.9/docs/partials/guide/
  inflating: angular-1.3.9/docs/partials/guide.html  
  inflating: angular-1.3.9/docs/partials/guide/$location.html  
  inflating: angular-1.3.9/docs/partials/guide/accessibility.html  
  inflating: angular-1.3.9/docs/partials/guide/animations.html  
  inflating: angular-1.3.9/docs/partials/guide/bootstrap.html  
  inflating: angular-1.3.9/docs/partials/guide/compiler.html  
  inflating: angular-1.3.9/docs/partials/guide/concepts.html  
  inflating: angular-1.3.9/docs/partials/guide/controller.html  
  inflating: angular-1.3.9/docs/partials/guide/css-styling.html  
  inflating: angular-1.3.9/docs/partials/guide/databinding.html  
  inflating: angular-1.3.9/docs/partials/guide/di.html  
  inflating: angular-1.3.9/docs/partials/guide/directive.html  
  inflating: angular-1.3.9/docs/partials/guide/e2e-testing.html  
  inflating: angular-1.3.9/docs/partials/guide/expression.html  
  inflating: angular-1.3.9/docs/partials/guide/filter.html  
  inflating: angular-1.3.9/docs/partials/guide/forms.html  
  inflating: angular-1.3.9/docs/partials/guide/i18n.html  
  inflating: angular-1.3.9/docs/partials/guide/ie.html  
  inflating: angular-1.3.9/docs/partials/guide/introduction.html  
  inflating: angular-1.3.9/docs/partials/guide/migration.html  
  inflating: angular-1.3.9/docs/partials/guide/module.html  
  inflating: angular-1.3.9/docs/partials/guide/production.html  
  inflating: angular-1.3.9/docs/partials/guide/providers.html  
  inflating: angular-1.3.9/docs/partials/guide/scope.html  
  inflating: angular-1.3.9/docs/partials/guide/security.html  
  inflating: angular-1.3.9/docs/partials/guide/services.html  
  inflating: angular-1.3.9/docs/partials/guide/templates.html  
  inflating: angular-1.3.9/docs/partials/guide/unit-testing.html  
   creating: angular-1.3.9/docs/partials/misc/
  inflating: angular-1.3.9/docs/partials/misc.html  
  inflating: angular-1.3.9/docs/partials/misc/contribute.html  
  inflating: angular-1.3.9/docs/partials/misc/downloading.html  
  inflating: angular-1.3.9/docs/partials/misc/faq.html  
  inflating: angular-1.3.9/docs/partials/misc/started.html  
   creating: angular-1.3.9/docs/partials/tutorial/
  inflating: angular-1.3.9/docs/partials/tutorial.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_00.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_01.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_02.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_03.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_04.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_05.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_06.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_07.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_08.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_09.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_10.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_11.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_12.html  
  inflating: angular-1.3.9/docs/partials/tutorial/the_end.html  
   creating: angular-1.3.9/docs/ptore2e/
   creating: angular-1.3.9/docs/ptore2e/example-$route-service/
  inflating: angular-1.3.9/docs/ptore2e/example-$route-service/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-$route-service/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-NgModelController/
  inflating: angular-1.3.9/docs/ptore2e/example-NgModelController/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-NgModelController/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-checkbox-input-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-checkbox-input-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-checkbox-input-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-date-input-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-date-input-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-date-input-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-datetimelocal-input-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-datetimelocal-input-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-datetimelocal-input-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-email-input-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-email-input-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-email-input-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example.csp/
  inflating: angular-1.3.9/docs/ptore2e/example-example.csp/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example.csp/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example100/
  inflating: angular-1.3.9/docs/ptore2e/example-example100/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example100/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example101/
  inflating: angular-1.3.9/docs/ptore2e/example-example101/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example101/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example102/
  inflating: angular-1.3.9/docs/ptore2e/example-example102/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example102/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example105/
  inflating: angular-1.3.9/docs/ptore2e/example-example105/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example105/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example106/
  inflating: angular-1.3.9/docs/ptore2e/example-example106/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example106/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example110/
  inflating: angular-1.3.9/docs/ptore2e/example-example110/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example110/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example111/
  inflating: angular-1.3.9/docs/ptore2e/example-example111/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example111/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example112/
  inflating: angular-1.3.9/docs/ptore2e/example-example112/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example112/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example113/
  inflating: angular-1.3.9/docs/ptore2e/example-example113/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example113/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example23/
  inflating: angular-1.3.9/docs/ptore2e/example-example23/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example23/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example24/
  inflating: angular-1.3.9/docs/ptore2e/example-example24/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example24/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example25/
  inflating: angular-1.3.9/docs/ptore2e/example-example25/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example25/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example27/
  inflating: angular-1.3.9/docs/ptore2e/example-example27/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example27/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example39/
  inflating: angular-1.3.9/docs/ptore2e/example-example39/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example39/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example40/
  inflating: angular-1.3.9/docs/ptore2e/example-example40/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example40/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example44/
  inflating: angular-1.3.9/docs/ptore2e/example-example44/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example44/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example51/
  inflating: angular-1.3.9/docs/ptore2e/example-example51/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example51/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example52/
  inflating: angular-1.3.9/docs/ptore2e/example-example52/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example52/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example53/
  inflating: angular-1.3.9/docs/ptore2e/example-example53/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example53/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example54/
  inflating: angular-1.3.9/docs/ptore2e/example-example54/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example54/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example55/
  inflating: angular-1.3.9/docs/ptore2e/example-example55/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example55/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example56/
  inflating: angular-1.3.9/docs/ptore2e/example-example56/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example56/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example57/
  inflating: angular-1.3.9/docs/ptore2e/example-example57/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example57/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example58/
  inflating: angular-1.3.9/docs/ptore2e/example-example58/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example58/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example59/
  inflating: angular-1.3.9/docs/ptore2e/example-example59/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example59/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example60/
  inflating: angular-1.3.9/docs/ptore2e/example-example60/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example60/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example61/
  inflating: angular-1.3.9/docs/ptore2e/example-example61/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example61/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example62/
  inflating: angular-1.3.9/docs/ptore2e/example-example62/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example62/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example63/
  inflating: angular-1.3.9/docs/ptore2e/example-example63/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example63/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example64/
  inflating: angular-1.3.9/docs/ptore2e/example-example64/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example64/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example65/
  inflating: angular-1.3.9/docs/ptore2e/example-example65/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example65/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example66/
  inflating: angular-1.3.9/docs/ptore2e/example-example66/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example66/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example67/
  inflating: angular-1.3.9/docs/ptore2e/example-example67/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example67/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example78/
  inflating: angular-1.3.9/docs/ptore2e/example-example78/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example78/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example83/
  inflating: angular-1.3.9/docs/ptore2e/example-example83/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example83/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example84/
  inflating: angular-1.3.9/docs/ptore2e/example-example84/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example84/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example86/
  inflating: angular-1.3.9/docs/ptore2e/example-example86/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example86/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example87/
  inflating: angular-1.3.9/docs/ptore2e/example-example87/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example87/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example88/
  inflating: angular-1.3.9/docs/ptore2e/example-example88/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example88/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example89/
  inflating: angular-1.3.9/docs/ptore2e/example-example89/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example89/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example9/
  inflating: angular-1.3.9/docs/ptore2e/example-example9/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example9/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example90/
  inflating: angular-1.3.9/docs/ptore2e/example-example90/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example90/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example91/
  inflating: angular-1.3.9/docs/ptore2e/example-example91/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example91/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example92/
  inflating: angular-1.3.9/docs/ptore2e/example-example92/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example92/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example93/
  inflating: angular-1.3.9/docs/ptore2e/example-example93/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example93/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example94/
  inflating: angular-1.3.9/docs/ptore2e/example-example94/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example94/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example95/
  inflating: angular-1.3.9/docs/ptore2e/example-example95/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example95/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example97/
  inflating: angular-1.3.9/docs/ptore2e/example-example97/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example97/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example98/
  inflating: angular-1.3.9/docs/ptore2e/example-example98/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example98/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example99/
  inflating: angular-1.3.9/docs/ptore2e/example-example99/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example99/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-input-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-input-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-input-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-location-hashbang-mode/
  inflating: angular-1.3.9/docs/ptore2e/example-location-hashbang-mode/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-location-hashbang-mode/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-location-html5-mode/
  inflating: angular-1.3.9/docs/ptore2e/example-location-html5-mode/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-location-html5-mode/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-month-input-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-month-input-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-month-input-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-ngChange-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-ngChange-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-ngChange-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-ngController/
  inflating: angular-1.3.9/docs/ptore2e/example-ngController/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-ngController/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-ngControllerAs/
  inflating: angular-1.3.9/docs/ptore2e/example-ngControllerAs/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-ngControllerAs/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-ngList-directive/
   creating: angular-1.3.9/docs/ptore2e/example-ngList-directive-newlines/
  inflating: angular-1.3.9/docs/ptore2e/example-ngList-directive-newlines/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-ngList-directive-newlines/jquery_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-ngList-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-ngList-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-ngModelOptions-directive-blur/
  inflating: angular-1.3.9/docs/ptore2e/example-ngModelOptions-directive-blur/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-ngModelOptions-directive-blur/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-ngValue-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-ngValue-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-ngValue-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-ngView-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-ngView-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-ngView-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-number-input-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-number-input-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-number-input-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-radio-input-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-radio-input-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-radio-input-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-text-input-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-text-input-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-text-input-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-time-input-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-time-input-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-time-input-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-url-input-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-url-input-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-url-input-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-week-input-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-week-input-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-week-input-directive/jquery_test.js  
  inflating: angular-1.3.9/errors.json  
   creating: angular-1.3.9/i18n/
  inflating: angular-1.3.9/i18n/angular-locale_aa-dj.js  
  inflating: angular-1.3.9/i18n/angular-locale_aa-er.js  
  inflating: angular-1.3.9/i18n/angular-locale_aa-et.js  
  inflating: angular-1.3.9/i18n/angular-locale_aa.js  
  inflating: angular-1.3.9/i18n/angular-locale_af-na.js  
  inflating: angular-1.3.9/i18n/angular-locale_af-za.js  
  inflating: angular-1.3.9/i18n/angular-locale_af.js  
  inflating: angular-1.3.9/i18n/angular-locale_agq-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_agq.js  
  inflating: angular-1.3.9/i18n/angular-locale_ak-gh.js  
  inflating: angular-1.3.9/i18n/angular-locale_ak.js  
  inflating: angular-1.3.9/i18n/angular-locale_am-et.js  
  inflating: angular-1.3.9/i18n/angular-locale_am.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-001.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-ae.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-bh.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-dj.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-dz.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-eg.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-eh.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-er.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-il.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-iq.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-jo.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-km.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-kw.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-lb.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-ly.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-ma.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-mr.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-om.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-ps.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-qa.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-sa.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-sd.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-so.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-ss.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-sy.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-td.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-tn.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-ye.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar.js  
  inflating: angular-1.3.9/i18n/angular-locale_as-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_as.js  
  inflating: angular-1.3.9/i18n/angular-locale_asa-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_asa.js  
  inflating: angular-1.3.9/i18n/angular-locale_ast-es.js  
  inflating: angular-1.3.9/i18n/angular-locale_ast.js  
  inflating: angular-1.3.9/i18n/angular-locale_az-cyrl-az.js  
  inflating: angular-1.3.9/i18n/angular-locale_az-cyrl.js  
  inflating: angular-1.3.9/i18n/angular-locale_az-latn-az.js  
  inflating: angular-1.3.9/i18n/angular-locale_az-latn.js  
  inflating: angular-1.3.9/i18n/angular-locale_az.js  
  inflating: angular-1.3.9/i18n/angular-locale_bas-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_bas.js  
  inflating: angular-1.3.9/i18n/angular-locale_be-by.js  
  inflating: angular-1.3.9/i18n/angular-locale_be.js  
  inflating: angular-1.3.9/i18n/angular-locale_bem-zm.js  
  inflating: angular-1.3.9/i18n/angular-locale_bem.js  
  inflating: angular-1.3.9/i18n/angular-locale_bez-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_bez.js  
  inflating: angular-1.3.9/i18n/angular-locale_bg-bg.js  
  inflating: angular-1.3.9/i18n/angular-locale_bg.js  
  inflating: angular-1.3.9/i18n/angular-locale_bm-latn-ml.js  
  inflating: angular-1.3.9/i18n/angular-locale_bm-latn.js  
  inflating: angular-1.3.9/i18n/angular-locale_bm-ml.js  
  inflating: angular-1.3.9/i18n/angular-locale_bm.js  
  inflating: angular-1.3.9/i18n/angular-locale_bn-bd.js  
  inflating: angular-1.3.9/i18n/angular-locale_bn-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_bn.js  
  inflating: angular-1.3.9/i18n/angular-locale_bo-cn.js  
  inflating: angular-1.3.9/i18n/angular-locale_bo-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_bo.js  
  inflating: angular-1.3.9/i18n/angular-locale_br-fr.js  
  inflating: angular-1.3.9/i18n/angular-locale_br.js  
  inflating: angular-1.3.9/i18n/angular-locale_brx-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_brx.js  
  inflating: angular-1.3.9/i18n/angular-locale_bs-cyrl-ba.js  
  inflating: angular-1.3.9/i18n/angular-locale_bs-cyrl.js  
  inflating: angular-1.3.9/i18n/angular-locale_bs-latn-ba.js  
  inflating: angular-1.3.9/i18n/angular-locale_bs-latn.js  
  inflating: angular-1.3.9/i18n/angular-locale_bs.js  
  inflating: angular-1.3.9/i18n/angular-locale_byn-er.js  
  inflating: angular-1.3.9/i18n/angular-locale_byn.js  
  inflating: angular-1.3.9/i18n/angular-locale_ca-ad.js  
  inflating: angular-1.3.9/i18n/angular-locale_ca-es-valencia.js  
  inflating: angular-1.3.9/i18n/angular-locale_ca-es.js  
  inflating: angular-1.3.9/i18n/angular-locale_ca-fr.js  
  inflating: angular-1.3.9/i18n/angular-locale_ca-it.js  
  inflating: angular-1.3.9/i18n/angular-locale_ca.js  
  inflating: angular-1.3.9/i18n/angular-locale_cgg-ug.js  
  inflating: angular-1.3.9/i18n/angular-locale_cgg.js  
  inflating: angular-1.3.9/i18n/angular-locale_chr-us.js  
  inflating: angular-1.3.9/i18n/angular-locale_chr.js  
  inflating: angular-1.3.9/i18n/angular-locale_ckb-arab-iq.js  
  inflating: angular-1.3.9/i18n/angular-locale_ckb-arab-ir.js  
  inflating: angular-1.3.9/i18n/angular-locale_ckb-arab.js  
  inflating: angular-1.3.9/i18n/angular-locale_ckb-iq.js  
  inflating: angular-1.3.9/i18n/angular-locale_ckb-ir.js  
  inflating: angular-1.3.9/i18n/angular-locale_ckb-latn-iq.js  
  inflating: angular-1.3.9/i18n/angular-locale_ckb-latn.js  
  inflating: angular-1.3.9/i18n/angular-locale_ckb.js  
  inflating: angular-1.3.9/i18n/angular-locale_cs-cz.js  
  inflating: angular-1.3.9/i18n/angular-locale_cs.js  
  inflating: angular-1.3.9/i18n/angular-locale_cy-gb.js  
  inflating: angular-1.3.9/i18n/angular-locale_cy.js  
  inflating: angular-1.3.9/i18n/angular-locale_da-dk.js  
  inflating: angular-1.3.9/i18n/angular-locale_da-gl.js  
  inflating: angular-1.3.9/i18n/angular-locale_da.js  
  inflating: angular-1.3.9/i18n/angular-locale_dav-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_dav.js  
  inflating: angular-1.3.9/i18n/angular-locale_de-at.js  
  inflating: angular-1.3.9/i18n/angular-locale_de-be.js  
  inflating: angular-1.3.9/i18n/angular-locale_de-ch.js  
  inflating: angular-1.3.9/i18n/angular-locale_de-de.js  
  inflating: angular-1.3.9/i18n/angular-locale_de-li.js  
  inflating: angular-1.3.9/i18n/angular-locale_de-lu.js  
  inflating: angular-1.3.9/i18n/angular-locale_de.js  
  inflating: angular-1.3.9/i18n/angular-locale_dje-ne.js  
  inflating: angular-1.3.9/i18n/angular-locale_dje.js  
  inflating: angular-1.3.9/i18n/angular-locale_dsb-de.js  
  inflating: angular-1.3.9/i18n/angular-locale_dsb.js  
  inflating: angular-1.3.9/i18n/angular-locale_dua-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_dua.js  
  inflating: angular-1.3.9/i18n/angular-locale_dyo-sn.js  
  inflating: angular-1.3.9/i18n/angular-locale_dyo.js  
  inflating: angular-1.3.9/i18n/angular-locale_dz-bt.js  
  inflating: angular-1.3.9/i18n/angular-locale_dz.js  
  inflating: angular-1.3.9/i18n/angular-locale_ebu-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_ebu.js  
  inflating: angular-1.3.9/i18n/angular-locale_ee-gh.js  
  inflating: angular-1.3.9/i18n/angular-locale_ee-tg.js  
  inflating: angular-1.3.9/i18n/angular-locale_ee.js  
  inflating: angular-1.3.9/i18n/angular-locale_el-cy.js  
  inflating: angular-1.3.9/i18n/angular-locale_el-gr.js  
  inflating: angular-1.3.9/i18n/angular-locale_el.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-001.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-150.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ag.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ai.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-as.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-au.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-bb.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-be.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-bm.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-bs.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-bw.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-bz.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ca.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-cc.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ck.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-cx.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-dg.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-dm.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-er.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-fj.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-fk.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-fm.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-gb.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-gd.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-gg.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-gh.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-gi.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-gm.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-gu.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-gy.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-hk.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ie.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-im.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-io.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-iso.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-je.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-jm.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ki.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-kn.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ky.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-lc.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-lr.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ls.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-mg.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-mh.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-mo.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-mp.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ms.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-mt.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-mu.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-mw.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-my.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-na.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-nf.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ng.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-nr.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-nu.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-nz.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-pg.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ph.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-pk.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-pn.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-pr.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-pw.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-rw.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-sb.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-sc.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-sd.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-sg.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-sh.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-sl.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ss.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-sx.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-sz.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-tc.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-tk.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-to.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-tt.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-tv.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ug.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-um.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-us.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-vc.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-vg.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-vi.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-vu.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ws.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-za.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-zm.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-zw.js  
  inflating: angular-1.3.9/i18n/angular-locale_en.js  
  inflating: angular-1.3.9/i18n/angular-locale_eo-001.js  
  inflating: angular-1.3.9/i18n/angular-locale_eo.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-419.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-ar.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-bo.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-cl.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-co.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-cr.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-cu.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-do.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-ea.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-ec.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-es.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-gq.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-gt.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-hn.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-ic.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-mx.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-ni.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-pa.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-pe.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-ph.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-pr.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-py.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-sv.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-us.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-uy.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-ve.js  
  inflating: angular-1.3.9/i18n/angular-locale_es.js  
  inflating: angular-1.3.9/i18n/angular-locale_et-ee.js  
  inflating: angular-1.3.9/i18n/angular-locale_et.js  
  inflating: angular-1.3.9/i18n/angular-locale_eu-es.js  
  inflating: angular-1.3.9/i18n/angular-locale_eu.js  
  inflating: angular-1.3.9/i18n/angular-locale_ewo-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_ewo.js  
  inflating: angular-1.3.9/i18n/angular-locale_fa-af.js  
  inflating: angular-1.3.9/i18n/angular-locale_fa-ir.js  
  inflating: angular-1.3.9/i18n/angular-locale_fa.js  
  inflating: angular-1.3.9/i18n/angular-locale_ff-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_ff-gn.js  
  inflating: angular-1.3.9/i18n/angular-locale_ff-mr.js  
  inflating: angular-1.3.9/i18n/angular-locale_ff-sn.js  
  inflating: angular-1.3.9/i18n/angular-locale_ff.js  
  inflating: angular-1.3.9/i18n/angular-locale_fi-fi.js  
  inflating: angular-1.3.9/i18n/angular-locale_fi.js  
  inflating: angular-1.3.9/i18n/angular-locale_fil-ph.js  
  inflating: angular-1.3.9/i18n/angular-locale_fil.js  
  inflating: angular-1.3.9/i18n/angular-locale_fo-fo.js  
  inflating: angular-1.3.9/i18n/angular-locale_fo.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-be.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-bf.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-bi.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-bj.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-bl.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-ca.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-cd.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-cf.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-cg.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-ch.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-ci.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-dj.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-dz.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-fr.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-ga.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-gf.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-gn.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-gp.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-gq.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-ht.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-km.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-lu.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-ma.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-mc.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-mf.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-mg.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-ml.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-mq.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-mr.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-mu.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-nc.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-ne.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-pf.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-pm.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-re.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-rw.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-sc.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-sn.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-sy.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-td.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-tg.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-tn.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-vu.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-wf.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-yt.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr.js  
  inflating: angular-1.3.9/i18n/angular-locale_fur-it.js  
  inflating: angular-1.3.9/i18n/angular-locale_fur.js  
  inflating: angular-1.3.9/i18n/angular-locale_fy-nl.js  
  inflating: angular-1.3.9/i18n/angular-locale_fy.js  
  inflating: angular-1.3.9/i18n/angular-locale_ga-ie.js  
  inflating: angular-1.3.9/i18n/angular-locale_ga.js  
  inflating: angular-1.3.9/i18n/angular-locale_gd-gb.js  
  inflating: angular-1.3.9/i18n/angular-locale_gd.js  
  inflating: angular-1.3.9/i18n/angular-locale_gl-es.js  
  inflating: angular-1.3.9/i18n/angular-locale_gl.js  
  inflating: angular-1.3.9/i18n/angular-locale_gsw-ch.js  
  inflating: angular-1.3.9/i18n/angular-locale_gsw-fr.js  
  inflating: angular-1.3.9/i18n/angular-locale_gsw-li.js  
  inflating: angular-1.3.9/i18n/angular-locale_gsw.js  
  inflating: angular-1.3.9/i18n/angular-locale_gu-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_gu.js  
  inflating: angular-1.3.9/i18n/angular-locale_guz-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_guz.js  
  inflating: angular-1.3.9/i18n/angular-locale_gv-im.js  
  inflating: angular-1.3.9/i18n/angular-locale_gv.js  
  inflating: angular-1.3.9/i18n/angular-locale_ha-latn-gh.js  
  inflating: angular-1.3.9/i18n/angular-locale_ha-latn-ne.js  
  inflating: angular-1.3.9/i18n/angular-locale_ha-latn-ng.js  
  inflating: angular-1.3.9/i18n/angular-locale_ha-latn.js  
  inflating: angular-1.3.9/i18n/angular-locale_ha.js  
  inflating: angular-1.3.9/i18n/angular-locale_haw-us.js  
  inflating: angular-1.3.9/i18n/angular-locale_haw.js  
  inflating: angular-1.3.9/i18n/angular-locale_he-il.js  
  inflating: angular-1.3.9/i18n/angular-locale_he.js  
  inflating: angular-1.3.9/i18n/angular-locale_hi-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_hi.js  
  inflating: angular-1.3.9/i18n/angular-locale_hr-ba.js  
  inflating: angular-1.3.9/i18n/angular-locale_hr-hr.js  
  inflating: angular-1.3.9/i18n/angular-locale_hr.js  
  inflating: angular-1.3.9/i18n/angular-locale_hsb-de.js  
  inflating: angular-1.3.9/i18n/angular-locale_hsb.js  
  inflating: angular-1.3.9/i18n/angular-locale_hu-hu.js  
  inflating: angular-1.3.9/i18n/angular-locale_hu.js  
  inflating: angular-1.3.9/i18n/angular-locale_hy-am.js  
  inflating: angular-1.3.9/i18n/angular-locale_hy.js  
  inflating: angular-1.3.9/i18n/angular-locale_ia-fr.js  
  inflating: angular-1.3.9/i18n/angular-locale_ia.js  
  inflating: angular-1.3.9/i18n/angular-locale_id-id.js  
  inflating: angular-1.3.9/i18n/angular-locale_id.js  
  inflating: angular-1.3.9/i18n/angular-locale_ig-ng.js  
  inflating: angular-1.3.9/i18n/angular-locale_ig.js  
  inflating: angular-1.3.9/i18n/angular-locale_ii-cn.js  
  inflating: angular-1.3.9/i18n/angular-locale_ii.js  
  inflating: angular-1.3.9/i18n/angular-locale_in.js  
  inflating: angular-1.3.9/i18n/angular-locale_is-is.js  
  inflating: angular-1.3.9/i18n/angular-locale_is.js  
  inflating: angular-1.3.9/i18n/angular-locale_it-ch.js  
  inflating: angular-1.3.9/i18n/angular-locale_it-it.js  
  inflating: angular-1.3.9/i18n/angular-locale_it-sm.js  
  inflating: angular-1.3.9/i18n/angular-locale_it.js  
  inflating: angular-1.3.9/i18n/angular-locale_iw.js  
  inflating: angular-1.3.9/i18n/angular-locale_ja-jp.js  
  inflating: angular-1.3.9/i18n/angular-locale_ja.js  
  inflating: angular-1.3.9/i18n/angular-locale_jgo-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_jgo.js  
  inflating: angular-1.3.9/i18n/angular-locale_jmc-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_jmc.js  
  inflating: angular-1.3.9/i18n/angular-locale_ka-ge.js  
  inflating: angular-1.3.9/i18n/angular-locale_ka.js  
  inflating: angular-1.3.9/i18n/angular-locale_kab-dz.js  
  inflating: angular-1.3.9/i18n/angular-locale_kab.js  
  inflating: angular-1.3.9/i18n/angular-locale_kam-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_kam.js  
  inflating: angular-1.3.9/i18n/angular-locale_kde-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_kde.js  
  inflating: angular-1.3.9/i18n/angular-locale_kea-cv.js  
  inflating: angular-1.3.9/i18n/angular-locale_kea.js  
  inflating: angular-1.3.9/i18n/angular-locale_khq-ml.js  
  inflating: angular-1.3.9/i18n/angular-locale_khq.js  
  inflating: angular-1.3.9/i18n/angular-locale_ki-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_ki.js  
  inflating: angular-1.3.9/i18n/angular-locale_kk-cyrl-kz.js  
  inflating: angular-1.3.9/i18n/angular-locale_kk-cyrl.js  
  inflating: angular-1.3.9/i18n/angular-locale_kk.js  
  inflating: angular-1.3.9/i18n/angular-locale_kkj-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_kkj.js  
  inflating: angular-1.3.9/i18n/angular-locale_kl-gl.js  
  inflating: angular-1.3.9/i18n/angular-locale_kl.js  
  inflating: angular-1.3.9/i18n/angular-locale_kln-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_kln.js  
  inflating: angular-1.3.9/i18n/angular-locale_km-kh.js  
  inflating: angular-1.3.9/i18n/angular-locale_km.js  
  inflating: angular-1.3.9/i18n/angular-locale_kn-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_kn.js  
  inflating: angular-1.3.9/i18n/angular-locale_ko-kp.js  
  inflating: angular-1.3.9/i18n/angular-locale_ko-kr.js  
  inflating: angular-1.3.9/i18n/angular-locale_ko.js  
  inflating: angular-1.3.9/i18n/angular-locale_kok-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_kok.js  
  inflating: angular-1.3.9/i18n/angular-locale_ks-arab-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_ks-arab.js  
  inflating: angular-1.3.9/i18n/angular-locale_ks.js  
  inflating: angular-1.3.9/i18n/angular-locale_ksb-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_ksb.js  
  inflating: angular-1.3.9/i18n/angular-locale_ksf-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_ksf.js  
  inflating: angular-1.3.9/i18n/angular-locale_ksh-de.js  
  inflating: angular-1.3.9/i18n/angular-locale_ksh.js  
  inflating: angular-1.3.9/i18n/angular-locale_kw-gb.js  
  inflating: angular-1.3.9/i18n/angular-locale_kw.js  
  inflating: angular-1.3.9/i18n/angular-locale_ky-cyrl-kg.js  
  inflating: angular-1.3.9/i18n/angular-locale_ky-cyrl.js  
  inflating: angular-1.3.9/i18n/angular-locale_ky.js  
  inflating: angular-1.3.9/i18n/angular-locale_lag-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_lag.js  
  inflating: angular-1.3.9/i18n/angular-locale_lb-lu.js  
  inflating: angular-1.3.9/i18n/angular-locale_lb.js  
  inflating: angular-1.3.9/i18n/angular-locale_lg-ug.js  
  inflating: angular-1.3.9/i18n/angular-locale_lg.js  
  inflating: angular-1.3.9/i18n/angular-locale_lkt-us.js  
  inflating: angular-1.3.9/i18n/angular-locale_lkt.js  
  inflating: angular-1.3.9/i18n/angular-locale_ln-ao.js  
  inflating: angular-1.3.9/i18n/angular-locale_ln-cd.js  
  inflating: angular-1.3.9/i18n/angular-locale_ln-cf.js  
  inflating: angular-1.3.9/i18n/angular-locale_ln-cg.js  
  inflating: angular-1.3.9/i18n/angular-locale_ln.js  
  inflating: angular-1.3.9/i18n/angular-locale_lo-la.js  
  inflating: angular-1.3.9/i18n/angular-locale_lo.js  
  inflating: angular-1.3.9/i18n/angular-locale_lt-lt.js  
  inflating: angular-1.3.9/i18n/angular-locale_lt.js  
  inflating: angular-1.3.9/i18n/angular-locale_lu-cd.js  
  inflating: angular-1.3.9/i18n/angular-locale_lu.js  
  inflating: angular-1.3.9/i18n/angular-locale_luo-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_luo.js  
  inflating: angular-1.3.9/i18n/angular-locale_luy-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_luy.js  
  inflating: angular-1.3.9/i18n/angular-locale_lv-lv.js  
  inflating: angular-1.3.9/i18n/angular-locale_lv.js  
  inflating: angular-1.3.9/i18n/angular-locale_mas-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_mas-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_mas.js  
  inflating: angular-1.3.9/i18n/angular-locale_mer-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_mer.js  
  inflating: angular-1.3.9/i18n/angular-locale_mfe-mu.js  
  inflating: angular-1.3.9/i18n/angular-locale_mfe.js  
  inflating: angular-1.3.9/i18n/angular-locale_mg-mg.js  
  inflating: angular-1.3.9/i18n/angular-locale_mg.js  
  inflating: angular-1.3.9/i18n/angular-locale_mgh-mz.js  
  inflating: angular-1.3.9/i18n/angular-locale_mgh.js  
  inflating: angular-1.3.9/i18n/angular-locale_mgo-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_mgo.js  
  inflating: angular-1.3.9/i18n/angular-locale_mk-mk.js  
  inflating: angular-1.3.9/i18n/angular-locale_mk.js  
  inflating: angular-1.3.9/i18n/angular-locale_ml-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_ml.js  
  inflating: angular-1.3.9/i18n/angular-locale_mn-cyrl-mn.js  
  inflating: angular-1.3.9/i18n/angular-locale_mn-cyrl.js  
  inflating: angular-1.3.9/i18n/angular-locale_mn.js  
  inflating: angular-1.3.9/i18n/angular-locale_mr-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_mr.js  
  inflating: angular-1.3.9/i18n/angular-locale_ms-latn-bn.js  
  inflating: angular-1.3.9/i18n/angular-locale_ms-latn-my.js  
  inflating: angular-1.3.9/i18n/angular-locale_ms-latn-sg.js  
  inflating: angular-1.3.9/i18n/angular-locale_ms-latn.js  
  inflating: angular-1.3.9/i18n/angular-locale_ms.js  
  inflating: angular-1.3.9/i18n/angular-locale_mt-mt.js  
  inflating: angular-1.3.9/i18n/angular-locale_mt.js  
  inflating: angular-1.3.9/i18n/angular-locale_mua-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_mua.js  
  inflating: angular-1.3.9/i18n/angular-locale_my-mm.js  
  inflating: angular-1.3.9/i18n/angular-locale_my.js  
  inflating: angular-1.3.9/i18n/angular-locale_naq-na.js  
  inflating: angular-1.3.9/i18n/angular-locale_naq.js  
  inflating: angular-1.3.9/i18n/angular-locale_nb-no.js  
  inflating: angular-1.3.9/i18n/angular-locale_nb-sj.js  
  inflating: angular-1.3.9/i18n/angular-locale_nb.js  
  inflating: angular-1.3.9/i18n/angular-locale_nd-zw.js  
  inflating: angular-1.3.9/i18n/angular-locale_nd.js  
  inflating: angular-1.3.9/i18n/angular-locale_ne-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_ne-np.js  
  inflating: angular-1.3.9/i18n/angular-locale_ne.js  
  inflating: angular-1.3.9/i18n/angular-locale_nl-aw.js  
  inflating: angular-1.3.9/i18n/angular-locale_nl-be.js  
  inflating: angular-1.3.9/i18n/angular-locale_nl-bq.js  
  inflating: angular-1.3.9/i18n/angular-locale_nl-cw.js  
  inflating: angular-1.3.9/i18n/angular-locale_nl-nl.js  
  inflating: angular-1.3.9/i18n/angular-locale_nl-sr.js  
  inflating: angular-1.3.9/i18n/angular-locale_nl-sx.js  
  inflating: angular-1.3.9/i18n/angular-locale_nl.js  
  inflating: angular-1.3.9/i18n/angular-locale_nmg-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_nmg.js  
  inflating: angular-1.3.9/i18n/angular-locale_nn-no.js  
  inflating: angular-1.3.9/i18n/angular-locale_nn.js  
  inflating: angular-1.3.9/i18n/angular-locale_nnh-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_nnh.js  
  inflating: angular-1.3.9/i18n/angular-locale_no-no.js  
  inflating: angular-1.3.9/i18n/angular-locale_no.js  
  inflating: angular-1.3.9/i18n/angular-locale_nr-za.js  
  inflating: angular-1.3.9/i18n/angular-locale_nr.js  
  inflating: angular-1.3.9/i18n/angular-locale_nso-za.js  
  inflating: angular-1.3.9/i18n/angular-locale_nso.js  
  inflating: angular-1.3.9/i18n/angular-locale_nus-sd.js  
  inflating: angular-1.3.9/i18n/angular-locale_nus.js  
  inflating: angular-1.3.9/i18n/angular-locale_nyn-ug.js  
  inflating: angular-1.3.9/i18n/angular-locale_nyn.js  
  inflating: angular-1.3.9/i18n/angular-locale_om-et.js  
  inflating: angular-1.3.9/i18n/angular-locale_om-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_om.js  
  inflating: angular-1.3.9/i18n/angular-locale_or-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_or.js  
  inflating: angular-1.3.9/i18n/angular-locale_os-ge.js  
  inflating: angular-1.3.9/i18n/angular-locale_os-ru.js  
  inflating: angular-1.3.9/i18n/angular-locale_os.js  
  inflating: angular-1.3.9/i18n/angular-locale_pa-arab-pk.js  
  inflating: angular-1.3.9/i18n/angular-locale_pa-arab.js  
  inflating: angular-1.3.9/i18n/angular-locale_pa-guru-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_pa-guru.js  
  inflating: angular-1.3.9/i18n/angular-locale_pa.js  
  inflating: angular-1.3.9/i18n/angular-locale_pl-pl.js  
  inflating: angular-1.3.9/i18n/angular-locale_pl.js  
  inflating: angular-1.3.9/i18n/angular-locale_ps-af.js  
  inflating: angular-1.3.9/i18n/angular-locale_ps.js  
  inflating: angular-1.3.9/i18n/angular-locale_pt-ao.js  
  inflating: angular-1.3.9/i18n/angular-locale_pt-br.js  
  inflating: angular-1.3.9/i18n/angular-locale_pt-cv.js  
  inflating: angular-1.3.9/i18n/angular-locale_pt-gw.js  
  inflating: angular-1.3.9/i18n/angular-locale_pt-mo.js  
  inflating: angular-1.3.9/i18n/angular-locale_pt-mz.js  
  inflating: angular-1.3.9/i18n/angular-locale_pt-pt.js  
  inflating: angular-1.3.9/i18n/angular-locale_pt-st.js  
  inflating: angular-1.3.9/i18n/angular-locale_pt-tl.js  
  inflating: angular-1.3.9/i18n/angular-locale_pt.js  
  inflating: angular-1.3.9/i18n/angular-locale_qu-bo.js  
  inflating: angular-1.3.9/i18n/angular-locale_qu-ec.js  
  inflating: angular-1.3.9/i18n/angular-locale_qu-pe.js  
  inflating: angular-1.3.9/i18n/angular-locale_qu.js  
  inflating: angular-1.3.9/i18n/angular-locale_rm-ch.js  
  inflating: angular-1.3.9/i18n/angular-locale_rm.js  
  inflating: angular-1.3.9/i18n/angular-locale_rn-bi.js  
  inflating: angular-1.3.9/i18n/angular-locale_rn.js  
  inflating: angular-1.3.9/i18n/angular-locale_ro-md.js  
  inflating: angular-1.3.9/i18n/angular-locale_ro-ro.js  
  inflating: angular-1.3.9/i18n/angular-locale_ro.js  
  inflating: angular-1.3.9/i18n/angular-locale_rof-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_rof.js  
  inflating: angular-1.3.9/i18n/angular-locale_ru-by.js  
  inflating: angular-1.3.9/i18n/angular-locale_ru-kg.js  
  inflating: angular-1.3.9/i18n/angular-locale_ru-kz.js  
  inflating: angular-1.3.9/i18n/angular-locale_ru-md.js  
  inflating: angular-1.3.9/i18n/angular-locale_ru-ru.js  
  inflating: angular-1.3.9/i18n/angular-locale_ru-ua.js  
  inflating: angular-1.3.9/i18n/angular-locale_ru.js  
  inflating: angular-1.3.9/i18n/angular-locale_rw-rw.js  
  inflating: angular-1.3.9/i18n/angular-locale_rw.js  
  inflating: angular-1.3.9/i18n/angular-locale_rwk-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_rwk.js  
  inflating: angular-1.3.9/i18n/angular-locale_sah-ru.js  
  inflating: angular-1.3.9/i18n/angular-locale_sah.js  
  inflating: angular-1.3.9/i18n/angular-locale_saq-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_saq.js  
  inflating: angular-1.3.9/i18n/angular-locale_sbp-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_sbp.js  
  inflating: angular-1.3.9/i18n/angular-locale_se-fi.js  
  inflating: angular-1.3.9/i18n/angular-locale_se-no.js  
  inflating: angular-1.3.9/i18n/angular-locale_se-se.js  
  inflating: angular-1.3.9/i18n/angular-locale_se.js  
  inflating: angular-1.3.9/i18n/angular-locale_seh-mz.js  
  inflating: angular-1.3.9/i18n/angular-locale_seh.js  
  inflating: angular-1.3.9/i18n/angular-locale_ses-ml.js  
  inflating: angular-1.3.9/i18n/angular-locale_ses.js  
  inflating: angular-1.3.9/i18n/angular-locale_sg-cf.js  
  inflating: angular-1.3.9/i18n/angular-locale_sg.js  
  inflating: angular-1.3.9/i18n/angular-locale_shi-latn-ma.js  
  inflating: angular-1.3.9/i18n/angular-locale_shi-latn.js  
  inflating: angular-1.3.9/i18n/angular-locale_shi-tfng-ma.js  
  inflating: angular-1.3.9/i18n/angular-locale_shi-tfng.js  
  inflating: angular-1.3.9/i18n/angular-locale_shi.js  
  inflating: angular-1.3.9/i18n/angular-locale_si-lk.js  
  inflating: angular-1.3.9/i18n/angular-locale_si.js  
  inflating: angular-1.3.9/i18n/angular-locale_sk-sk.js  
  inflating: angular-1.3.9/i18n/angular-locale_sk.js  
  inflating: angular-1.3.9/i18n/angular-locale_sl-si.js  
  inflating: angular-1.3.9/i18n/angular-locale_sl.js  
  inflating: angular-1.3.9/i18n/angular-locale_smn-fi.js  
  inflating: angular-1.3.9/i18n/angular-locale_smn.js  
  inflating: angular-1.3.9/i18n/angular-locale_sn-zw.js  
  inflating: angular-1.3.9/i18n/angular-locale_sn.js  
  inflating: angular-1.3.9/i18n/angular-locale_so-dj.js  
  inflating: angular-1.3.9/i18n/angular-locale_so-et.js  
  inflating: angular-1.3.9/i18n/angular-locale_so-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_so-so.js  
  inflating: angular-1.3.9/i18n/angular-locale_so.js  
  inflating: angular-1.3.9/i18n/angular-locale_sq-al.js  
  inflating: angular-1.3.9/i18n/angular-locale_sq-mk.js  
  inflating: angular-1.3.9/i18n/angular-locale_sq-xk.js  
  inflating: angular-1.3.9/i18n/angular-locale_sq.js  
  inflating: angular-1.3.9/i18n/angular-locale_sr-cyrl-ba.js  
  inflating: angular-1.3.9/i18n/angular-locale_sr-cyrl-me.js  
  inflating: angular-1.3.9/i18n/angular-locale_sr-cyrl-rs.js  
  inflating: angular-1.3.9/i18n/angular-locale_sr-cyrl-xk.js  
  inflating: angular-1.3.9/i18n/angular-locale_sr-cyrl.js  
  inflating: angular-1.3.9/i18n/angular-locale_sr-latn-ba.js  
  inflating: angular-1.3.9/i18n/angular-locale_sr-latn-me.js  
  inflating: angular-1.3.9/i18n/angular-locale_sr-latn-rs.js  
  inflating: angular-1.3.9/i18n/angular-locale_sr-latn-xk.js  
  inflating: angular-1.3.9/i18n/angular-locale_sr-latn.js  
  inflating: angular-1.3.9/i18n/angular-locale_sr.js  
  inflating: angular-1.3.9/i18n/angular-locale_ss-sz.js  
  inflating: angular-1.3.9/i18n/angular-locale_ss-za.js  
  inflating: angular-1.3.9/i18n/angular-locale_ss.js  
  inflating: angular-1.3.9/i18n/angular-locale_ssy-er.js  
  inflating: angular-1.3.9/i18n/angular-locale_ssy.js  
  inflating: angular-1.3.9/i18n/angular-locale_st-ls.js  
  inflating: angular-1.3.9/i18n/angular-locale_st-za.js  
  inflating: angular-1.3.9/i18n/angular-locale_st.js  
  inflating: angular-1.3.9/i18n/angular-locale_sv-ax.js  
  inflating: angular-1.3.9/i18n/angular-locale_sv-fi.js  
  inflating: angular-1.3.9/i18n/angular-locale_sv-se.js  
  inflating: angular-1.3.9/i18n/angular-locale_sv.js  
  inflating: angular-1.3.9/i18n/angular-locale_sw-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_sw-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_sw-ug.js  
  inflating: angular-1.3.9/i18n/angular-locale_sw.js  
  inflating: angular-1.3.9/i18n/angular-locale_swc-cd.js  
  inflating: angular-1.3.9/i18n/angular-locale_swc.js  
  inflating: angular-1.3.9/i18n/angular-locale_ta-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_ta-lk.js  
  inflating: angular-1.3.9/i18n/angular-locale_ta-my.js  
  inflating: angular-1.3.9/i18n/angular-locale_ta-sg.js  
  inflating: angular-1.3.9/i18n/angular-locale_ta.js  
  inflating: angular-1.3.9/i18n/angular-locale_te-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_te.js  
  inflating: angular-1.3.9/i18n/angular-locale_teo-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_teo-ug.js  
  inflating: angular-1.3.9/i18n/angular-locale_teo.js  
  inflating: angular-1.3.9/i18n/angular-locale_tg-cyrl-tj.js  
  inflating: angular-1.3.9/i18n/angular-locale_tg-cyrl.js  
  inflating: angular-1.3.9/i18n/angular-locale_tg.js  
  inflating: angular-1.3.9/i18n/angular-locale_th-th.js  
  inflating: angular-1.3.9/i18n/angular-locale_th.js  
  inflating: angular-1.3.9/i18n/angular-locale_ti-er.js  
  inflating: angular-1.3.9/i18n/angular-locale_ti-et.js  
  inflating: angular-1.3.9/i18n/angular-locale_ti.js  
  inflating: angular-1.3.9/i18n/angular-locale_tig-er.js  
  inflating: angular-1.3.9/i18n/angular-locale_tig.js  
  inflating: angular-1.3.9/i18n/angular-locale_tl.js  
  inflating: angular-1.3.9/i18n/angular-locale_tn-bw.js  
  inflating: angular-1.3.9/i18n/angular-locale_tn-za.js  
  inflating: angular-1.3.9/i18n/angular-locale_tn.js  
  inflating: angular-1.3.9/i18n/angular-locale_to-to.js  
  inflating: angular-1.3.9/i18n/angular-locale_to.js  
  inflating: angular-1.3.9/i18n/angular-locale_tr-cy.js  
  inflating: angular-1.3.9/i18n/angular-locale_tr-tr.js  
  inflating: angular-1.3.9/i18n/angular-locale_tr.js  
  inflating: angular-1.3.9/i18n/angular-locale_ts-za.js  
  inflating: angular-1.3.9/i18n/angular-locale_ts.js  
  inflating: angular-1.3.9/i18n/angular-locale_twq-ne.js  
  inflating: angular-1.3.9/i18n/angular-locale_twq.js  
  inflating: angular-1.3.9/i18n/angular-locale_tzm-latn-ma.js  
  inflating: angular-1.3.9/i18n/angular-locale_tzm-latn.js  
  inflating: angular-1.3.9/i18n/angular-locale_tzm.js  
  inflating: angular-1.3.9/i18n/angular-locale_ug-arab-cn.js  
  inflating: angular-1.3.9/i18n/angular-locale_ug-arab.js  
  inflating: angular-1.3.9/i18n/angular-locale_ug.js  
  inflating: angular-1.3.9/i18n/angular-locale_uk-ua.js  
  inflating: angular-1.3.9/i18n/angular-locale_uk.js  
  inflating: angular-1.3.9/i18n/angular-locale_ur-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_ur-pk.js  
  inflating: angular-1.3.9/i18n/angular-locale_ur.js  
  inflating: angular-1.3.9/i18n/angular-locale_uz-arab-af.js  
  inflating: angular-1.3.9/i18n/angular-locale_uz-arab.js  
  inflating: angular-1.3.9/i18n/angular-locale_uz-cyrl-uz.js  
  inflating: angular-1.3.9/i18n/angular-locale_uz-cyrl.js  
  inflating: angular-1.3.9/i18n/angular-locale_uz-latn-uz.js  
  inflating: angular-1.3.9/i18n/angular-locale_uz-latn.js  
  inflating: angular-1.3.9/i18n/angular-locale_uz.js  
  inflating: angular-1.3.9/i18n/angular-locale_vai-latn-lr.js  
  inflating: angular-1.3.9/i18n/angular-locale_vai-latn.js  
  inflating: angular-1.3.9/i18n/angular-locale_vai-vaii-lr.js  
  inflating: angular-1.3.9/i18n/angular-locale_vai-vaii.js  
  inflating: angular-1.3.9/i18n/angular-locale_vai.js  
  inflating: angular-1.3.9/i18n/angular-locale_ve-za.js  
  inflating: angular-1.3.9/i18n/angular-locale_ve.js  
  inflating: angular-1.3.9/i18n/angular-locale_vi-vn.js  
  inflating: angular-1.3.9/i18n/angular-locale_vi.js  
  inflating: angular-1.3.9/i18n/angular-locale_vo-001.js  
  inflating: angular-1.3.9/i18n/angular-locale_vo.js  
  inflating: angular-1.3.9/i18n/angular-locale_vun-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_vun.js  
  inflating: angular-1.3.9/i18n/angular-locale_wae-ch.js  
  inflating: angular-1.3.9/i18n/angular-locale_wae.js  
  inflating: angular-1.3.9/i18n/angular-locale_wal-et.js  
  inflating: angular-1.3.9/i18n/angular-locale_wal.js  
  inflating: angular-1.3.9/i18n/angular-locale_xh-za.js  
  inflating: angular-1.3.9/i18n/angular-locale_xh.js  
  inflating: angular-1.3.9/i18n/angular-locale_xog-ug.js  
  inflating: angular-1.3.9/i18n/angular-locale_xog.js  
  inflating: angular-1.3.9/i18n/angular-locale_yav-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_yav.js  
  inflating: angular-1.3.9/i18n/angular-locale_yi-001.js  
  inflating: angular-1.3.9/i18n/angular-locale_yi.js  
  inflating: angular-1.3.9/i18n/angular-locale_yo-bj.js  
  inflating: angular-1.3.9/i18n/angular-locale_yo-ng.js  
  inflating: angular-1.3.9/i18n/angular-locale_yo.js  
  inflating: angular-1.3.9/i18n/angular-locale_zgh-ma.js  
  inflating: angular-1.3.9/i18n/angular-locale_zgh.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh-cn.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh-hans-cn.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh-hans-hk.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh-hans-mo.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh-hans-sg.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh-hans.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh-hant-hk.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh-hant-mo.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh-hant-tw.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh-hant.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh-hk.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh-tw.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh.js  
  inflating: angular-1.3.9/i18n/angular-locale_zu-za.js  
  inflating: angular-1.3.9/i18n/angular-locale_zu.js  
   creating: angular-1.3.9/i18n/ngLocale/
  inflating: angular-1.3.9/version.json  
  inflating: angular-1.3.9/version.txt  
(cd angularjs && unzip -u ui-utils-0.2.1.zip)
Archive:  ui-utils-0.2.1.zip
8df0fcf665a8f14949e189c8d6e2e0204a858b06
   creating: ui-utils-0.2.1/
  inflating: ui-utils-0.2.1/.travis.yml  
  inflating: ui-utils-0.2.1/CHANGELOG.md  
  inflating: ui-utils-0.2.1/bower.json  
  inflating: ui-utils-0.2.1/ui-utils-ieshiv.js  
  inflating: ui-utils-0.2.1/ui-utils-ieshiv.min.js  
  inflating: ui-utils-0.2.1/ui-utils.js  
  inflating: ui-utils-0.2.1/ui-utils.min.js  
if [ ! -d bootstrap-3.3.0 ] ; then mkdir -p bootstrap-3.3.0 && ( cd bootstrap-3.3.0 && unzip -u ../bootstrap-3.3.0-dist.zip && mv dist/* . && rmdir dist ) ; fi
Archive:  ../bootstrap-3.3.0-dist.zip
   creating: dist/
   creating: dist/css/
  inflating: dist/css/bootstrap-theme.css  
  inflating: dist/css/bootstrap-theme.css.map  
  inflating: dist/css/bootstrap-theme.min.css  
  inflating: dist/css/bootstrap.css  
  inflating: dist/css/bootstrap.css.map  
  inflating: dist/css/bootstrap.min.css  
   creating: dist/fonts/
  inflating: dist/fonts/glyphicons-halflings-regular.eot  
  inflating: dist/fonts/glyphicons-halflings-regular.svg  
  inflating: dist/fonts/glyphicons-halflings-regular.ttf  
  inflating: dist/fonts/glyphicons-halflings-regular.woff  
   creating: dist/js/
  inflating: dist/js/bootstrap.js    
  inflating: dist/js/bootstrap.min.js  
  inflating: dist/js/npm.js          
mkdir -p d3
(cd d3 && unzip -u ../d3-3.5.3.zip)
Archive:  ../d3-3.5.3.zip
  inflating: LICENSE                 
  inflating: d3.js                   
  inflating: d3.min.js               
make[1]: Leaving directory `/tmp/nagioscore/html'
if [ xyes = xyes ]; then \
		cd ./module && make; \
	fi
make[1]: Entering directory `/tmp/nagioscore/module'
gcc -I.. -fPIC -g -O2 -DHAVE_CONFIG_H -o helloworld.o helloworld.c -shared  
make[1]: Leaving directory `/tmp/nagioscore/module'
cd ./worker && make all
make[1]: Entering directory `/tmp/nagioscore/worker'
cd ./ping && make all
make[2]: Entering directory `/tmp/nagioscore/worker/ping'
gcc -I.. -I ../../include -I ../.. -g -O2 -DHAVE_CONFIG_H -o worker-ping worker-ping.c -L ../../lib -l nagios  
make[2]: Leaving directory `/tmp/nagioscore/worker/ping'
make[1]: Leaving directory `/tmp/nagioscore/worker'

*** Compile finished ***

If the main program and CGIs compiled without any errors, you
can continue with installing Nagios as follows (type 'make'
without any arguments for a list of all possible options):

  make install
     - This installs the main program, CGIs, and HTML files

  make install-init
     - This installs the init script in /etc/init

  make install-commandmode
     - This installs and configures permissions on the
       directory for holding the external command file

  make install-config
     - This installs *SAMPLE* config files in /usr/local/nagios/etc
       You'll have to modify these sample files before you can
       use Nagios.  Read the HTML documentation for more info
       on doing this.  Pay particular attention to the docs on
       object configuration files, as they determine what/how
       things get monitored!

  make install-webconf
     - This installs the Apache config file for the Nagios
       web interface

  make install-exfoliation
     - This installs the Exfoliation theme for the Nagios
       web interface

  make install-classicui
     - This installs the classic theme for the Nagios
       web interface


*** Support Notes *******************************************

If you have questions about configuring or running Nagios,
please make sure that you:

     - Look at the sample config files
     - Read the documentation on the Nagios Library at:
           https://library.nagios.com

before you post a question to one of the mailing lists.
Also make sure to include pertinent information that could
help others help you.  This might include:

     - What version of Nagios you are using
     - What version of the plugins you are using
     - Relevant snippets from your config files
     - Relevant error messages from the Nagios log file

For more information on obtaining support for Nagios, visit:

       https://support.nagios.com

*************************************************************

Enjoy.

[root@core-014 nagioscore]# useradd nagios
[root@core-014 nagioscore]# usermod -a -G nagios apache
[root@core-014 nagioscore]# 
[root@core-014 nagioscore]# make install
cd ./base && make install
make[1]: Entering directory `/tmp/nagioscore/base'
make install-basic
make[2]: Entering directory `/tmp/nagioscore/base'
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/bin
/usr/bin/install -c -m 774 -o nagios -g nagios nagios /usr/local/nagios/bin
/usr/bin/install -c -m 774 -o nagios -g nagios nagiostats /usr/local/nagios/bin
make[2]: Leaving directory `/tmp/nagioscore/base'
make strip-post-install
make[2]: Entering directory `/tmp/nagioscore/base'
/usr/bin/strip /usr/local/nagios/bin/nagios
/usr/bin/strip /usr/local/nagios/bin/nagiostats
make[2]: Leaving directory `/tmp/nagioscore/base'
make[1]: Leaving directory `/tmp/nagioscore/base'
cd ./cgi && make install
make[1]: Entering directory `/tmp/nagioscore/cgi'
make install-basic
make[2]: Entering directory `/tmp/nagioscore/cgi'
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/bin
for file in *.cgi; do \
		/usr/bin/install -c -m 775 -o nagios -g nagios $file /usr/local/nagios/bin; \
	done
make[2]: Leaving directory `/tmp/nagioscore/cgi'
make strip-post-install
make[2]: Entering directory `/tmp/nagioscore/cgi'
for file in *.cgi; do \
		/usr/bin/strip /usr/local/nagios/bin/$file; \
	done
make[2]: Leaving directory `/tmp/nagioscore/cgi'
make[1]: Leaving directory `/tmp/nagioscore/cgi'
cd ./html && make install
make[1]: Entering directory `/tmp/nagioscore/html'
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/media
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/stylesheets
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/contexthelp
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/docs
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/docs/images
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/js
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/images
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/images/logos
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/includes
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/ssi
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/angularjs
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/angularjs/angular-1.3.9
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/angularjs/ui-utils-0.2.1
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/bootstrap-3.3.0
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/bootstrap-3.3.0/css
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/d3
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/spin
/usr/bin/install -c -m 664 -o nagios -g nagios robots.txt /usr/local/nagios/share
rm -f /usr/local/nagios/share/index.html
rm -f /usr/local/nagios/share/main.html
rm -f /usr/local/nagios/share/side.html
rm -f /usr/local/nagios/share/map.html
rm -f /usr/local/nagios/share/rss-*
rm -rf /usr/local/nagios/share/include/rss
/usr/bin/install -c -m 664 -o nagios -g nagios jsonquery.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios graph-header.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios histogram.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios histogram-form.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios histogram-graph.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios histogram-links.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios infobox.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios map.php /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios map-directive.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios map-form.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios map-links.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios map-popup.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios trends.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios trends-form.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios trends-graph.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios trends-host-yaxis.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios trends-links.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios trends-service-yaxis.html /usr/local/nagios/share
for file in *.php; \
	do /usr/bin/install -c -m 664 -o nagios -g nagios $file /usr/local/nagios/share; done
for file in stylesheets/*.css; \
	do /usr/bin/install -c -m 664 -o nagios -g nagios $file /usr/local/nagios/share/stylesheets; done
for file in contexthelp/*.html; \
	do /usr/bin/install -c -m 664 -o nagios -g nagios $file /usr/local/nagios/share/contexthelp; done
for file in js/*.js; \
	do /usr/bin/install -c -m 664 -o nagios -g nagios $file /usr/local/nagios/share/js; done
for file in images/*.gif; \
	do /usr/bin/install -c -m 664 -o nagios -g nagios $file /usr/local/nagios/share/images; done
for file in images/*.jpg; \
	do /usr/bin/install -c -m 664 -o nagios -g nagios $file /usr/local/nagios/share/images; done
for file in images/*.png; \
	do /usr/bin/install -c -m 664 -o nagios -g nagios $file /usr/local/nagios/share/images; done
for file in images/*.ico; \
	do /usr/bin/install -c -m 664 -o nagios -g nagios $file /usr/local/nagios/share/images; done
for file in images/logos/*.*; \
	do /usr/bin/install -c -m 664 -o nagios -g nagios $file /usr/local/nagios/share/images/logos; done
for file in includes/*.*; \
	do /usr/bin/install -c -m 664 -o nagios -g nagios $file /usr/local/nagios/share/includes; done
/usr/bin/install -c -m 664 -o nagios -g nagios angularjs/angular-1.3.9/angular.min.js  /usr/local/nagios/share/angularjs/angular-1.3.9
/usr/bin/install -c -m 664 -o nagios -g nagios angularjs/angular-1.3.9/angular.min.js.map  /usr/local/nagios/share/angularjs/angular-1.3.9
/usr/bin/install -c -m 664 -o nagios -g nagios angularjs/ui-bootstrap-tpls-0.12.0.min.js  /usr/local/nagios/share/angularjs
/usr/bin/install -c -m 664 -o nagios -g nagios angularjs/ui-utils-0.2.1/ui-utils.js   /usr/local/nagios/share/angularjs/ui-utils-0.2.1
/usr/bin/install -c -m 664 -o nagios -g nagios bootstrap-3.3.0/css/bootstrap.min.css /usr/local/nagios/share/bootstrap-3.3.0/css
/usr/bin/install -c -m 664 -o nagios -g nagios bootstrap-3.3.0/css/bootstrap-theme.min.css /usr/local/nagios/share/bootstrap-3.3.0/css
/usr/bin/install -c -m 664 -o nagios -g nagios d3/d3.min.js /usr/local/nagios/share/d3
/usr/bin/install -c -m 664 -o nagios -g nagios spin/spin.min.js /usr/local/nagios/share/spin
make[1]: Leaving directory `/tmp/nagioscore/html'
make install-exfoliation
make[1]: Entering directory `/tmp/nagioscore'

*** Exfoliation theme installed ***
NOTE: Use 'make install-classicui' to revert to classic Nagios theme

make[1]: Leaving directory `/tmp/nagioscore'
make install-basic
make[1]: Entering directory `/tmp/nagioscore'
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/libexec
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/var
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/var/archives
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/var/spool/checkresults
chmod g+s /usr/local/nagios/var/spool/checkresults

*** Main program, CGIs and HTML files installed ***

You can continue with installing Nagios as follows (type 'make'
without any arguments for a list of all possible options):

  make install-init
     - This installs the init script in /etc/init

  make install-commandmode
     - This installs and configures permissions on the
       directory for holding the external command file

  make install-config
     - This installs sample config files in /usr/local/nagios/etc

make[1]: Leaving directory `/tmp/nagioscore'
[root@core-014 nagioscore]# make install-init
/usr/bin/install -c -m 755 -o root -g root startup/rh-upstart-init /etc/init/nagios.conf
/usr/bin/install: cannot stat `startup/rh-upstart-init': No such file or directory
make: *** [install-daemoninit] Error 1
```",1.0,"Nagios Core 4.4 alpha - make install-init error - I tried installing the latest build of 4.4 and I get the following error:

```
[root@core-014 nagioscore]# make install-init
/usr/bin/install -c -m 755 -o root -g root startup/rh-upstart-init /etc/init/nagios.conf
/usr/bin/install: cannot stat `startup/rh-upstart-init': No such file or directory
make: *** [install-daemoninit] Error 1
```

This is on CentOS release 6.8 (Final) x64.

This is a fresh build of the OS, it has not had Nagios installed on it before.

Full log:
```
[root@core-014 ~]# cd /tmp
[root@core-014 tmp]# ls -la
total 35012
drwxrwxrwt.  7 root root     4096 Jan 16 10:08 .
dr-xr-xr-x. 22 root root     4096 Jan 16 10:06 ..
drwxrwxrwt.  2 root root     4096 Jan 16 10:06 .ICE-unix
-rw-r--r--.  1 root root 35819943 Jan 16 10:08 nagioscore-4.4.aplha.tar.gz
drwxr-xr-x.  2 root root     4096 Jun 10  2016 vmware-config0
drwxr-xr-x.  2 root root     4096 Jun 10  2016 vmware-fonts0
drwx------.  2 root root     4096 Jan 16 10:06 vmware-root
drwxr-xr-x.  7 root root     4096 Sep  1  2014 vmware-tools-distrib
-rw-------.  1 root root        0 Jun 10  2016 yum.log
[root@core-014 tmp]# tar xzf nagioscore-4.4.aplha.tar.gz 
[root@core-014 tmp]# cd nagioscore
[root@core-014 nagioscore]# ./configure 
checking for a BSD-compatible install... /usr/bin/install -c
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether make sets $(MAKE)... yes
checking whether ln -s works... yes
checking for strip... /usr/bin/strip
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking whether time.h and sys/time.h may both be included... yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking ctype.h usability... yes
checking ctype.h presence... yes
checking for ctype.h... yes
checking dirent.h usability... yes
checking dirent.h presence... yes
checking for dirent.h... yes
checking errno.h usability... yes
checking errno.h presence... yes
checking for errno.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking getopt.h usability... yes
checking getopt.h presence... yes
checking for getopt.h... yes
checking grp.h usability... yes
checking grp.h presence... yes
checking for grp.h... yes
checking libgen.h usability... yes
checking libgen.h presence... yes
checking for libgen.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking math.h usability... yes
checking math.h presence... yes
checking for math.h... yes
checking netdb.h usability... yes
checking netdb.h presence... yes
checking for netdb.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking pwd.h usability... yes
checking pwd.h presence... yes
checking for pwd.h... yes
checking regex.h usability... yes
checking regex.h presence... yes
checking for regex.h... yes
checking signal.h usability... yes
checking signal.h presence... yes
checking for signal.h... yes
checking socket.h usability... no
checking socket.h presence... no
checking for socket.h... no
checking stdarg.h usability... yes
checking stdarg.h presence... yes
checking for stdarg.h... yes
checking for string.h... (cached) yes
checking for strings.h... (cached) yes
checking sys/loadavg.h usability... no
checking sys/loadavg.h presence... no
checking for sys/loadavg.h... no
checking sys/mman.h usability... yes
checking sys/mman.h presence... yes
checking for sys/mman.h... yes
checking for sys/types.h... (cached) yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking sys/resource.h usability... yes
checking sys/resource.h presence... yes
checking for sys/resource.h... yes
checking for sys/wait.h... (cached) yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking for sys/stat.h... (cached) yes
checking sys/timeb.h usability... yes
checking sys/timeb.h presence... yes
checking for sys/timeb.h... yes
checking sys/un.h usability... yes
checking sys/un.h presence... yes
checking for sys/un.h... yes
checking sys/ipc.h usability... yes
checking sys/ipc.h presence... yes
checking for sys/ipc.h... yes
checking sys/msg.h usability... yes
checking sys/msg.h presence... yes
checking for sys/msg.h... yes
checking sys/poll.h usability... yes
checking sys/poll.h presence... yes
checking for sys/poll.h... yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking uio.h usability... no
checking uio.h presence... no
checking for uio.h... no
checking for unistd.h... (cached) yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking wchar.h usability... yes
checking wchar.h presence... yes
checking for wchar.h... yes
checking sys/prctl.h usability... yes
checking sys/prctl.h presence... yes
checking for sys/prctl.h... yes
checking for an ANSI C-conforming const... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for struct tm.tm_zone... yes
checking for mode_t... yes
checking for pid_t... yes
checking for size_t... yes
checking return type of signal handlers... void
checking for uid_t in sys/types.h... yes
checking type of array argument to getgroups... gid_t
checking what the operating system is ... linux
checking what the distribution type is ... rh
checking what init system is being used ... upstart
checking what inetd is being used ... upstart
checking for which paths to use ... default
checking for which init file to use ... rh-upstart-init
checking for which inetd files to use ... unknown
checking for va_copy... yes
checking for vsnprintf... yes
checking for snprintf... yes
checking for asprintf... yes
checking for vasprintf... yes
checking for sigaction... yes
checking for C99 vsnprintf... yes
checking for library containing getservbyname... none required
checking for library containing connect... none required
checking for initgroups... yes
checking for setenv... yes
checking for strdup... yes
checking for strstr... yes
checking for strtoul... yes
checking for unsetenv... yes
checking for type of socket size... size_t
checking for library containing nanosleep... none required
checking for mail... no
which: no mail in (/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin)
checking for glibc at least version 2.4... yes
checking sys/epoll.h usability... yes
checking sys/epoll.h presence... yes
checking for sys/epoll.h... yes
checking sys/select.h usability... yes
checking sys/select.h presence... yes
checking for sys/select.h... yes
./configure: line 6408: dnls: command not found
checking for main in -liconv... no
checking for gdImagePng in -lgd (order 1)... no
checking for gdImagePng in -lgd (order 2)... yes
GD library was found!
checking for gdImageCreateTrueColor in -lgd... yes
checking ltdl.h usability... no
checking ltdl.h presence... no
checking for ltdl.h... no
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for dlopen in -ldl... yes
checking for extra flags needed to export symbols...  -Wl,-export-dynamic
checking for linker flags for loadable modules... -shared
checking for traceroute... no
checking for type va_list... yes
checking for perl... /usr/bin/perl
checking for unzip... /usr/bin/unzip
configure: creating ./config.status
config.status: creating html/index.php
config.status: creating Makefile
config.status: creating lib/Makefile
config.status: creating base/Makefile
config.status: creating common/Makefile
config.status: creating contrib/Makefile
config.status: creating cgi/Makefile
config.status: creating html/Makefile
config.status: creating module/Makefile
config.status: creating worker/Makefile
config.status: creating worker/ping/Makefile
config.status: creating xdata/Makefile
config.status: creating subst
config.status: creating pkginfo
config.status: creating startup/openrc-init
config.status: creating startup/default-init
config.status: creating startup/default-service
config.status: creating startup/upstart-init
config.status: creating t/Makefile
config.status: creating t-tap/Makefile
config.status: creating include/config.h
config.status: creating lib/snprintf.h
config.status: creating lib/iobroker.h

Creating sample config files in sample-config/ ...


*** Configuration summary for nagios 4.4.0 2018-??-?? ***:

 General Options:
 -------------------------
        Nagios executable:  nagios
        Nagios user/group:  nagios,nagios
       Command user/group:  nagios,nagios
             Event Broker:  yes
        Install ${prefix}:  /usr/local/nagios
    Install ${includedir}:  /usr/local/nagios/include/nagios
                Lock file:  N/A
   Check result directory:  /usr/local/nagios/var/spool/checkresults
           Init directory:  /etc/init
  Apache conf.d directory:  /etc/httpd/conf.d
             Mail program:  /usr/sbin/sendmail
                  Host OS:  linux-gnu
          IOBroker Method:  epoll

 Web Interface Options:
 ------------------------
                 HTML URL:  http://localhost/nagios/
                  CGI URL:  http://localhost/nagios/cgi-bin/
 Traceroute (used by WAP):  


Review the options above for accuracy.  If they look okay,
type 'make all' to compile the main program and CGIs.

[root@core-014 nagioscore]# make all
cd ./base && make
make[1]: Entering directory `/tmp/nagioscore/base'
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o nagios.o nagios.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o broker.o broker.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o nebmods.o nebmods.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o ../common/shared.o ../common/shared.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o query-handler.o query-handler.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o workers.o workers.c
workers.c: In function ‘wproc_run_job’:
workers.c:996: warning: unused variable ‘i’
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o checks.o checks.c
checks.c: In function ‘service_fresh_check’:
checks.c:740: warning: ‘return’ with a value, in function returning void
checks.c: In function ‘host_fresh_check’:
checks.c:759: warning: ‘return’ with a value, in function returning void
checks.c: In function ‘host_state_or_hard_state_type_change’:
checks.c:930: warning: passing argument 1 of ‘delete_service_acknowledgement_comments’ from incompatible pointer type
../include/comments.h:92: note: expected ‘struct service *’ but argument is of type ‘struct host *’
checks.c: In function ‘handle_async_service_check_result’:
checks.c:1123: warning: suggest explicit braces to avoid ambiguous ‘else’
checks.c: In function ‘handle_async_host_check_result’:
checks.c:2732: warning: suggest explicit braces to avoid ambiguous ‘else’
checks.c:2784: warning: suggest parentheses around assignment used as truth value
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o config.o config.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o commands.o commands.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o events.o events.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o flapping.o flapping.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o logging.o logging.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o macros-base.o ../common/macros.c
../common/macros.c: In function ‘process_macros_r’:
../common/macros.c:140: warning: suggest parentheses around assignment used as truth value
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o netutils.o netutils.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o notifications.o notifications.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o sehandlers.o sehandlers.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE   -c -o utils.o utils.c
utils.c: In function ‘daemon_init’:
utils.c:1940: warning: implicit declaration of function ‘cleanup_performance_data’
utils.c:1941: warning: implicit declaration of function ‘cleanup_downtime_data’
utils.c: In function ‘process_check_result_file’:
utils.c:2346: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘time_t’
utils.c: In function ‘cleanup’:
utils.c:3372: warning: implicit declaration of function ‘xodtemplate_free_memory’
utils.c: In function ‘rlimit_problem_detection’:
utils.c:3697: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘rlim_t’
utils.c:3702: warning: format ‘%d’ expects type ‘int’, but argument 4 has type ‘rlim_t’
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o retention-base.o sretention.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o xretention-base.o ../xdata/xrddefault.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o comments-base.o ../common/comments.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o xcomments-base.o ../xdata/xcddefault.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o objects-base.o ../common/objects.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o xobjects-base.o ../xdata/xodtemplate.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o statusdata-base.o ../common/statusdata.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o xstatusdata-base.o ../xdata/xsddefault.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o perfdata-base.o perfdata.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o xperfdata-base.o ../xdata/xpddefault.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o downtime-base.o ../common/downtime.c
make -C ../lib
make[2]: Entering directory `/tmp/nagioscore/lib'
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c squeue.c -o squeue.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c kvvec.c -o kvvec.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c iocache.c -o iocache.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c iobroker.c -o iobroker.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c bitmap.c -o bitmap.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c dkhash.c -o dkhash.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c runcmd.c -o runcmd.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c nsutils.c -o nsutils.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c fanout.c -o fanout.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c pqueue.c -o pqueue.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c worker.c -o worker.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c skiplist.c -o skiplist.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c nsock.c -o nsock.o
gcc -Wall -g -O2 -DHAVE_CONFIG_H -c nspath.c -o nspath.o
ar cr libnagios.a squeue.o kvvec.o iocache.o iobroker.o bitmap.o dkhash.o runcmd.o nsutils.o fanout.o pqueue.o worker.o skiplist.o nsock.o nspath.o
make[2]: Leaving directory `/tmp/nagioscore/lib'
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -o nagios nagios.o broker.o nebmods.o ../common/shared.o  query-handler.o workers.o checks.o config.o commands.o events.o flapping.o logging.o macros-base.o netutils.o notifications.o sehandlers.o utils.o retention-base.o xretention-base.o comments-base.o xcomments-base.o objects-base.o xobjects-base.o statusdata-base.o xstatusdata-base.o perfdata-base.o xperfdata-base.o downtime-base.o  -Wl,-export-dynamic   -lm  -ldl  ../lib/libnagios.a
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCORE -o nagiostats nagiostats.c  -lm  ../lib/libnagios.a
make[1]: Leaving directory `/tmp/nagioscore/base'
cd ./cgi && make
make[1]: Entering directory `/tmp/nagioscore/cgi'
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI   -c -o getcgi.o getcgi.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI   -c -o cgiutils.o cgiutils.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI   -c -o cgiauth.o cgiauth.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI -c -o macros-cgi.o ../common/macros.c
../common/macros.c: In function ‘process_macros_r’:
../common/macros.c:140: warning: suggest parentheses around assignment used as truth value
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI -c -o objects-cgi.o ../common/objects.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI -c -o xobjects-cgi.o ../xdata/xodtemplate.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI -c -o statusdata-cgi.o ../common/statusdata.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI -c -o xstatusdata-cgi.o ../xdata/xsddefault.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI -c -o comments-cgi.o ../common/comments.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI -c -o downtime-cgi.o ../common/downtime.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI -DJSON_NAGIOS_4X -c -o archiveutils.o archiveutils.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI -DJSON_NAGIOS_4X -c -o jsonutils.o jsonutils.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI -DJSON_NAGIOS_4X  -o archivejson.cgi archivejson.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a archiveutils.o jsonutils.o 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o avail.cgi avail.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI   -c -o extcmd_list.o extcmd_list.c
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o cmd.cgi cmd.c extcmd_list.o ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a   
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o config.cgi config.c  ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o extinfo.cgi extinfo.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a   
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o history.cgi history.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o notifications.cgi notifications.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI -DJSON_NAGIOS_4X  -o objectjson.cgi objectjson.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a jsonutils.o 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o outages.cgi outages.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a  
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o showlog.cgi showlog.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o status.cgi status.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a  
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI -DJSON_NAGIOS_4X  -o statusjson.cgi statusjson.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a jsonutils.o 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o statuswml.cgi statuswml.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o summary.cgi summary.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o tac.cgi tac.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a  
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o statuswrl.cgi statuswrl.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a -lm 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o statusmap.cgi statusmap.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a -lgd  -lpng -ljpeg -lz -lm 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o trends.cgi trends.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a -lgd  -lpng -ljpeg -lz -lm 
gcc -Wall -I.. -g -O2 -DHAVE_CONFIG_H -DNSCGI  -o histogram.cgi histogram.c ../common/shared.o getcgi.o cgiutils.o cgiauth.o macros-cgi.o  objects-cgi.o xobjects-cgi.o statusdata-cgi.o xstatusdata-cgi.o comments-cgi.o downtime-cgi.o ../lib/libnagios.a -lgd  -lpng -ljpeg -lz -lm 
make[1]: Leaving directory `/tmp/nagioscore/cgi'
cd ./html && make
make[1]: Entering directory `/tmp/nagioscore/html'
(cd angularjs && unzip -u angular-1.3.9.zip)
Archive:  angular-1.3.9.zip
   creating: angular-1.3.9/
  inflating: angular-1.3.9/angular-animate.js  
  inflating: angular-1.3.9/angular-animate.min.js  
  inflating: angular-1.3.9/angular-animate.min.js.map  
  inflating: angular-1.3.9/angular-aria.js  
  inflating: angular-1.3.9/angular-aria.min.js  
  inflating: angular-1.3.9/angular-aria.min.js.map  
  inflating: angular-1.3.9/angular-cookies.js  
  inflating: angular-1.3.9/angular-cookies.min.js  
  inflating: angular-1.3.9/angular-cookies.min.js.map  
  inflating: angular-1.3.9/angular-csp.css  
  inflating: angular-1.3.9/angular-loader.js  
  inflating: angular-1.3.9/angular-loader.min.js  
  inflating: angular-1.3.9/angular-loader.min.js.map  
  inflating: angular-1.3.9/angular-messages.js  
  inflating: angular-1.3.9/angular-messages.min.js  
  inflating: angular-1.3.9/angular-messages.min.js.map  
  inflating: angular-1.3.9/angular-mocks.js  
  inflating: angular-1.3.9/angular-resource.js  
  inflating: angular-1.3.9/angular-resource.min.js  
  inflating: angular-1.3.9/angular-resource.min.js.map  
  inflating: angular-1.3.9/angular-route.js  
  inflating: angular-1.3.9/angular-route.min.js  
  inflating: angular-1.3.9/angular-route.min.js.map  
  inflating: angular-1.3.9/angular-sanitize.js  
  inflating: angular-1.3.9/angular-sanitize.min.js  
  inflating: angular-1.3.9/angular-sanitize.min.js.map  
  inflating: angular-1.3.9/angular-scenario.js  
  inflating: angular-1.3.9/angular-touch.js  
  inflating: angular-1.3.9/angular-touch.min.js  
  inflating: angular-1.3.9/angular-touch.min.js.map  
  inflating: angular-1.3.9/angular.js  
  inflating: angular-1.3.9/angular.min.js  
  inflating: angular-1.3.9/angular.min.js.map  
   creating: angular-1.3.9/docs/
  inflating: angular-1.3.9/docs/Error404.html  
   creating: angular-1.3.9/docs/components/
   creating: angular-1.3.9/docs/components/bootstrap-3.1.1/
   creating: angular-1.3.9/docs/components/bootstrap-3.1.1/css/
  inflating: angular-1.3.9/docs/components/bootstrap-3.1.1/css/bootstrap-theme.css  
  inflating: angular-1.3.9/docs/components/bootstrap-3.1.1/css/bootstrap-theme.css.map  
  inflating: angular-1.3.9/docs/components/bootstrap-3.1.1/css/bootstrap-theme.min.css  
  inflating: angular-1.3.9/docs/components/bootstrap-3.1.1/css/bootstrap.css  
  inflating: angular-1.3.9/docs/components/bootstrap-3.1.1/css/bootstrap.css.map  
  inflating: angular-1.3.9/docs/components/bootstrap-3.1.1/css/bootstrap.min.css  
   creating: angular-1.3.9/docs/components/bootstrap-3.1.1/fonts/
  inflating: angular-1.3.9/docs/components/bootstrap-3.1.1/fonts/glyphicons-halflings-regular.eot  
  inflating: angular-1.3.9/docs/components/bootstrap-3.1.1/fonts/glyphicons-halflings-regular.svg  
  inflating: angular-1.3.9/docs/components/bootstrap-3.1.1/fonts/glyphicons-halflings-regular.ttf  
  inflating: angular-1.3.9/docs/components/bootstrap-3.1.1/fonts/glyphicons-halflings-regular.woff  
   creating: angular-1.3.9/docs/components/bootstrap-3.1.1/js/
  inflating: angular-1.3.9/docs/components/bootstrap-3.1.1/js/bootstrap.js  
  inflating: angular-1.3.9/docs/components/bootstrap-3.1.1/js/bootstrap.min.js  
   creating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/CHANGES.html  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/COPYING  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/README-zh-Hans.html  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/README.html  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/README.md  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/bower.json  
   creating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-apollo.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-clj.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-css.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-dart.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-go.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-hs.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-lisp.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-lua.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-ml.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-n.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-proto.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-scala.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-sql.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-tex.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-vb.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-vhdl.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-wiki.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-xq.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/lang-yaml.js  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/prettify.css  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/src/prettify.js  
   creating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/styles/
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/styles/demo.html  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/styles/desert.css  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/styles/index.html  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/styles/sons-of-obsidian.css  
  inflating: angular-1.3.9/docs/components/google-code-prettify-1.0.1/styles/sunburst.css  
   creating: angular-1.3.9/docs/components/jquery-2.1.1/
  inflating: angular-1.3.9/docs/components/jquery-2.1.1/jquery.js  
  inflating: angular-1.3.9/docs/components/jquery-2.1.1/jquery.min.js  
   creating: angular-1.3.9/docs/components/lunr.js-0.4.2/
  inflating: angular-1.3.9/docs/components/lunr.js-0.4.2/lunr.js  
  inflating: angular-1.3.9/docs/components/lunr.js-0.4.2/lunr.min.js  
  inflating: angular-1.3.9/docs/components/lunr.js-0.4.2/server.js  
   creating: angular-1.3.9/docs/components/marked-0.3.2/
  inflating: angular-1.3.9/docs/components/marked-0.3.2/index.js  
   creating: angular-1.3.9/docs/components/marked-0.3.2/lib/
  inflating: angular-1.3.9/docs/components/marked-0.3.2/lib/marked.js  
   creating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/README.md  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/bower.json  
   creating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/
   creating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Bold/
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Bold/OpenSans-Bold.eot  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Bold/OpenSans-Bold.svg  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Bold/OpenSans-Bold.ttf  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Bold/OpenSans-Bold.woff  
   creating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/BoldItalic/
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/BoldItalic/OpenSans-BoldItalic.eot  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/BoldItalic/OpenSans-BoldItalic.svg  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/BoldItalic/OpenSans-BoldItalic.ttf  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/BoldItalic/OpenSans-BoldItalic.woff  
   creating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/ExtraBold/
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/ExtraBold/OpenSans-ExtraBold.eot  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/ExtraBold/OpenSans-ExtraBold.svg  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/ExtraBold/OpenSans-ExtraBold.ttf  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/ExtraBold/OpenSans-ExtraBold.woff  
   creating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/ExtraBoldItalic/
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/ExtraBoldItalic/OpenSans-ExtraBoldItalic.eot  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/ExtraBoldItalic/OpenSans-ExtraBoldItalic.svg  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/ExtraBoldItalic/OpenSans-ExtraBoldItalic.ttf  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/ExtraBoldItalic/OpenSans-ExtraBoldItalic.woff  
   creating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Italic/
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Italic/OpenSans-Italic.eot  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Italic/OpenSans-Italic.svg  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Italic/OpenSans-Italic.ttf  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Italic/OpenSans-Italic.woff  
   creating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Light/
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Light/OpenSans-Light.eot  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Light/OpenSans-Light.svg  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Light/OpenSans-Light.ttf  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Light/OpenSans-Light.woff  
   creating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/LightItalic/
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/LightItalic/OpenSans-LightItalic.eot  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/LightItalic/OpenSans-LightItalic.svg  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/LightItalic/OpenSans-LightItalic.ttf  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/LightItalic/OpenSans-LightItalic.woff  
   creating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Regular/
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Regular/OpenSans-Regular.eot  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Regular/OpenSans-Regular.svg  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Regular/OpenSans-Regular.ttf  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Regular/OpenSans-Regular.woff  
   creating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Semibold/
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Semibold/OpenSans-Semibold.eot  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Semibold/OpenSans-Semibold.svg  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Semibold/OpenSans-Semibold.ttf  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/Semibold/OpenSans-Semibold.woff  
   creating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/SemiboldItalic/
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/SemiboldItalic/OpenSans-SemiboldItalic.eot  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/SemiboldItalic/OpenSans-SemiboldItalic.svg  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/SemiboldItalic/OpenSans-SemiboldItalic.ttf  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/fonts/SemiboldItalic/OpenSans-SemiboldItalic.woff  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/index.html  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/open-sans.css  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/open-sans.less  
  inflating: angular-1.3.9/docs/components/open-sans-fontface-1.0.4/open-sans.scss  
   creating: angular-1.3.9/docs/css/
  inflating: angular-1.3.9/docs/css/animations.css  
  inflating: angular-1.3.9/docs/css/doc_widgets.css  
  inflating: angular-1.3.9/docs/css/docs.css  
  inflating: angular-1.3.9/docs/css/prettify-theme.css  
  inflating: angular-1.3.9/docs/css/prettify.css  
   creating: angular-1.3.9/docs/examples/
   creating: angular-1.3.9/docs/examples/example-$filter/
  inflating: angular-1.3.9/docs/examples/example-$filter/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-$filter/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-$filter/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-$filter/index.html  
  inflating: angular-1.3.9/docs/examples/example-$filter/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-$filter/script.js  
   creating: angular-1.3.9/docs/examples/example-$route-service/
  inflating: angular-1.3.9/docs/examples/example-$route-service/book.html  
  inflating: angular-1.3.9/docs/examples/example-$route-service/chapter.html  
  inflating: angular-1.3.9/docs/examples/example-$route-service/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-$route-service/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-$route-service/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-$route-service/index.html  
  inflating: angular-1.3.9/docs/examples/example-$route-service/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-$route-service/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-$route-service/script.js  
   creating: angular-1.3.9/docs/examples/example-NgModelController/
  inflating: angular-1.3.9/docs/examples/example-NgModelController/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-NgModelController/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-NgModelController/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-NgModelController/index.html  
  inflating: angular-1.3.9/docs/examples/example-NgModelController/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-NgModelController/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-NgModelController/script.js  
  inflating: angular-1.3.9/docs/examples/example-NgModelController/style.css  
   creating: angular-1.3.9/docs/examples/example-checkbox-input-directive/
  inflating: angular-1.3.9/docs/examples/example-checkbox-input-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-checkbox-input-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-checkbox-input-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-checkbox-input-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-checkbox-input-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-checkbox-input-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-date-input-directive/
  inflating: angular-1.3.9/docs/examples/example-date-input-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-date-input-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-date-input-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-date-input-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-date-input-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-date-input-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-datetimelocal-input-directive/
  inflating: angular-1.3.9/docs/examples/example-datetimelocal-input-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-datetimelocal-input-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-datetimelocal-input-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-datetimelocal-input-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-datetimelocal-input-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-datetimelocal-input-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-email-input-directive/
  inflating: angular-1.3.9/docs/examples/example-email-input-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-email-input-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-email-input-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-email-input-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-email-input-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-email-input-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-error-$rootScope-inprog/
  inflating: angular-1.3.9/docs/examples/example-error-$rootScope-inprog/app.js  
  inflating: angular-1.3.9/docs/examples/example-error-$rootScope-inprog/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-error-$rootScope-inprog/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-error-$rootScope-inprog/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-error-$rootScope-inprog/index.html  
  inflating: angular-1.3.9/docs/examples/example-error-$rootScope-inprog/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example/
   creating: angular-1.3.9/docs/examples/example-example.csp/
  inflating: angular-1.3.9/docs/examples/example-example.csp/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example.csp/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example.csp/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example.csp/index.html  
  inflating: angular-1.3.9/docs/examples/example-example.csp/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example.csp/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example.csp/script.js  
  inflating: angular-1.3.9/docs/examples/example-example/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example/index.html  
  inflating: angular-1.3.9/docs/examples/example-example/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example/script.js  
   creating: angular-1.3.9/docs/examples/example-example1/
  inflating: angular-1.3.9/docs/examples/example-example1/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example1/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example1/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example1/index.html  
  inflating: angular-1.3.9/docs/examples/example-example1/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example10/
  inflating: angular-1.3.9/docs/examples/example-example10/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example10/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example10/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example10/index.html  
  inflating: angular-1.3.9/docs/examples/example-example10/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example10/script.js  
   creating: angular-1.3.9/docs/examples/example-example100/
  inflating: angular-1.3.9/docs/examples/example-example100/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example100/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example100/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example100/index.html  
  inflating: angular-1.3.9/docs/examples/example-example100/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example100/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example101/
  inflating: angular-1.3.9/docs/examples/example-example101/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example101/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example101/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example101/index.html  
  inflating: angular-1.3.9/docs/examples/example-example101/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example101/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example102/
  inflating: angular-1.3.9/docs/examples/example-example102/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example102/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example102/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example102/index.html  
  inflating: angular-1.3.9/docs/examples/example-example102/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example102/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example103/
  inflating: angular-1.3.9/docs/examples/example-example103/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example103/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example103/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example103/index.html  
  inflating: angular-1.3.9/docs/examples/example-example103/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example104/
  inflating: angular-1.3.9/docs/examples/example-example104/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example104/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example104/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example104/index.html  
  inflating: angular-1.3.9/docs/examples/example-example104/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example104/script.js  
   creating: angular-1.3.9/docs/examples/example-example105/
  inflating: angular-1.3.9/docs/examples/example-example105/http-hello.html  
  inflating: angular-1.3.9/docs/examples/example-example105/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example105/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example105/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example105/index.html  
  inflating: angular-1.3.9/docs/examples/example-example105/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example105/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example105/script.js  
   creating: angular-1.3.9/docs/examples/example-example106/
  inflating: angular-1.3.9/docs/examples/example-example106/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example106/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example106/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example106/index.html  
  inflating: angular-1.3.9/docs/examples/example-example106/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example106/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example107/
  inflating: angular-1.3.9/docs/examples/example-example107/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example107/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example107/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example107/index.html  
  inflating: angular-1.3.9/docs/examples/example-example107/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example108/
  inflating: angular-1.3.9/docs/examples/example-example108/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example108/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example108/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example108/index.html  
  inflating: angular-1.3.9/docs/examples/example-example108/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example109/
  inflating: angular-1.3.9/docs/examples/example-example109/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example109/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example109/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example109/index.html  
  inflating: angular-1.3.9/docs/examples/example-example109/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example109/script.js  
   creating: angular-1.3.9/docs/examples/example-example11/
  inflating: angular-1.3.9/docs/examples/example-example11/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example11/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example11/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example11/index.html  
  inflating: angular-1.3.9/docs/examples/example-example11/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example11/my-customer.html  
  inflating: angular-1.3.9/docs/examples/example-example11/script.js  
   creating: angular-1.3.9/docs/examples/example-example110/
  inflating: angular-1.3.9/docs/examples/example-example110/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example110/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example110/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example110/index.html  
  inflating: angular-1.3.9/docs/examples/example-example110/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example110/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example110/script.js  
  inflating: angular-1.3.9/docs/examples/example-example110/test_data.json  
   creating: angular-1.3.9/docs/examples/example-example111/
  inflating: angular-1.3.9/docs/examples/example-example111/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example111/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example111/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example111/index.html  
  inflating: angular-1.3.9/docs/examples/example-example111/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example111/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example112/
  inflating: angular-1.3.9/docs/examples/example-example112/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example112/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example112/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example112/index.html  
  inflating: angular-1.3.9/docs/examples/example-example112/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example112/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example113/
  inflating: angular-1.3.9/docs/examples/example-example113/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example113/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example113/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example113/index.html  
  inflating: angular-1.3.9/docs/examples/example-example113/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example113/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example114/
  inflating: angular-1.3.9/docs/examples/example-example114/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example114/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example114/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example114/index.html  
  inflating: angular-1.3.9/docs/examples/example-example114/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example114/script.js  
   creating: angular-1.3.9/docs/examples/example-example115/
  inflating: angular-1.3.9/docs/examples/example-example115/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example115/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example115/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example115/index.html  
  inflating: angular-1.3.9/docs/examples/example-example115/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example115/script.js  
   creating: angular-1.3.9/docs/examples/example-example116/
  inflating: angular-1.3.9/docs/examples/example-example116/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example116/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example116/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example116/index.html  
  inflating: angular-1.3.9/docs/examples/example-example116/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example116/script.js  
   creating: angular-1.3.9/docs/examples/example-example12/
  inflating: angular-1.3.9/docs/examples/example-example12/customer-address.html  
  inflating: angular-1.3.9/docs/examples/example-example12/customer-name.html  
  inflating: angular-1.3.9/docs/examples/example-example12/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example12/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example12/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example12/index.html  
  inflating: angular-1.3.9/docs/examples/example-example12/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example12/script.js  
   creating: angular-1.3.9/docs/examples/example-example13/
  inflating: angular-1.3.9/docs/examples/example-example13/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example13/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example13/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example13/index.html  
  inflating: angular-1.3.9/docs/examples/example-example13/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example13/my-customer.html  
  inflating: angular-1.3.9/docs/examples/example-example13/script.js  
   creating: angular-1.3.9/docs/examples/example-example14/
  inflating: angular-1.3.9/docs/examples/example-example14/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example14/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example14/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example14/index.html  
  inflating: angular-1.3.9/docs/examples/example-example14/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example14/my-customer.html  
  inflating: angular-1.3.9/docs/examples/example-example14/script.js  
   creating: angular-1.3.9/docs/examples/example-example15/
  inflating: angular-1.3.9/docs/examples/example-example15/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example15/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example15/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example15/index.html  
  inflating: angular-1.3.9/docs/examples/example-example15/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example15/my-customer-iso.html  
  inflating: angular-1.3.9/docs/examples/example-example15/script.js  
   creating: angular-1.3.9/docs/examples/example-example16/
  inflating: angular-1.3.9/docs/examples/example-example16/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example16/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example16/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example16/index.html  
  inflating: angular-1.3.9/docs/examples/example-example16/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example16/my-customer-plus-vojta.html  
  inflating: angular-1.3.9/docs/examples/example-example16/script.js  
   creating: angular-1.3.9/docs/examples/example-example17/
  inflating: angular-1.3.9/docs/examples/example-example17/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example17/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example17/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example17/index.html  
  inflating: angular-1.3.9/docs/examples/example-example17/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example17/script.js  
   creating: angular-1.3.9/docs/examples/example-example18/
  inflating: angular-1.3.9/docs/examples/example-example18/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example18/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example18/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example18/index.html  
  inflating: angular-1.3.9/docs/examples/example-example18/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example18/my-dialog.html  
  inflating: angular-1.3.9/docs/examples/example-example18/script.js  
   creating: angular-1.3.9/docs/examples/example-example19/
  inflating: angular-1.3.9/docs/examples/example-example19/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example19/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example19/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example19/index.html  
  inflating: angular-1.3.9/docs/examples/example-example19/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example19/my-dialog.html  
  inflating: angular-1.3.9/docs/examples/example-example19/script.js  
   creating: angular-1.3.9/docs/examples/example-example2/
  inflating: angular-1.3.9/docs/examples/example-example2/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example2/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example2/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example2/index.html  
  inflating: angular-1.3.9/docs/examples/example-example2/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example20/
  inflating: angular-1.3.9/docs/examples/example-example20/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example20/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example20/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example20/index.html  
  inflating: angular-1.3.9/docs/examples/example-example20/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example20/my-dialog-close.html  
  inflating: angular-1.3.9/docs/examples/example-example20/script.js  
   creating: angular-1.3.9/docs/examples/example-example21/
  inflating: angular-1.3.9/docs/examples/example-example21/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example21/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example21/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example21/index.html  
  inflating: angular-1.3.9/docs/examples/example-example21/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example21/script.js  
   creating: angular-1.3.9/docs/examples/example-example22/
  inflating: angular-1.3.9/docs/examples/example-example22/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example22/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example22/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example22/index.html  
  inflating: angular-1.3.9/docs/examples/example-example22/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example22/my-pane.html  
  inflating: angular-1.3.9/docs/examples/example-example22/my-tabs.html  
  inflating: angular-1.3.9/docs/examples/example-example22/script.js  
   creating: angular-1.3.9/docs/examples/example-example23/
  inflating: angular-1.3.9/docs/examples/example-example23/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example23/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example23/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example23/index.html  
  inflating: angular-1.3.9/docs/examples/example-example23/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example23/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example24/
  inflating: angular-1.3.9/docs/examples/example-example24/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example24/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example24/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example24/index.html  
  inflating: angular-1.3.9/docs/examples/example-example24/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example24/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example24/script.js  
   creating: angular-1.3.9/docs/examples/example-example25/
  inflating: angular-1.3.9/docs/examples/example-example25/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example25/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example25/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example25/index.html  
  inflating: angular-1.3.9/docs/examples/example-example25/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example25/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example25/script.js  
   creating: angular-1.3.9/docs/examples/example-example26/
  inflating: angular-1.3.9/docs/examples/example-example26/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example26/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example26/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example26/index.html  
  inflating: angular-1.3.9/docs/examples/example-example26/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example26/script.js  
   creating: angular-1.3.9/docs/examples/example-example27/
  inflating: angular-1.3.9/docs/examples/example-example27/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example27/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example27/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example27/index.html  
  inflating: angular-1.3.9/docs/examples/example-example27/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example27/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example27/script.js  
   creating: angular-1.3.9/docs/examples/example-example28/
  inflating: angular-1.3.9/docs/examples/example-example28/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example28/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example28/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example28/index.html  
  inflating: angular-1.3.9/docs/examples/example-example28/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example28/script.js  
   creating: angular-1.3.9/docs/examples/example-example29/
  inflating: angular-1.3.9/docs/examples/example-example29/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example29/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example29/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example29/index.html  
  inflating: angular-1.3.9/docs/examples/example-example29/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example29/script.js  
   creating: angular-1.3.9/docs/examples/example-example3/
  inflating: angular-1.3.9/docs/examples/example-example3/animations.css  
  inflating: angular-1.3.9/docs/examples/example-example3/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example3/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example3/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example3/index.html  
  inflating: angular-1.3.9/docs/examples/example-example3/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example30/
  inflating: angular-1.3.9/docs/examples/example-example30/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example30/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example30/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example30/index.html  
  inflating: angular-1.3.9/docs/examples/example-example30/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example30/script.js  
   creating: angular-1.3.9/docs/examples/example-example31/
  inflating: angular-1.3.9/docs/examples/example-example31/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example31/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example31/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example31/index.html  
  inflating: angular-1.3.9/docs/examples/example-example31/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example32/
  inflating: angular-1.3.9/docs/examples/example-example32/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example32/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example32/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example32/index.html  
  inflating: angular-1.3.9/docs/examples/example-example32/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example33/
  inflating: angular-1.3.9/docs/examples/example-example33/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example33/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example33/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example33/index.html  
  inflating: angular-1.3.9/docs/examples/example-example33/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example33/script.js  
   creating: angular-1.3.9/docs/examples/example-example34/
  inflating: angular-1.3.9/docs/examples/example-example34/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example34/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example34/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example34/index.html  
  inflating: angular-1.3.9/docs/examples/example-example34/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example34/script.js  
   creating: angular-1.3.9/docs/examples/example-example35/
  inflating: angular-1.3.9/docs/examples/example-example35/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example35/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example35/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example35/index.html  
  inflating: angular-1.3.9/docs/examples/example-example35/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example35/script.js  
   creating: angular-1.3.9/docs/examples/example-example36/
  inflating: angular-1.3.9/docs/examples/example-example36/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example36/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example36/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example36/index.html  
  inflating: angular-1.3.9/docs/examples/example-example36/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example36/script.js  
   creating: angular-1.3.9/docs/examples/example-example37/
  inflating: angular-1.3.9/docs/examples/example-example37/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example37/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example37/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example37/index.html  
  inflating: angular-1.3.9/docs/examples/example-example37/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example37/script.js  
   creating: angular-1.3.9/docs/examples/example-example38/
  inflating: angular-1.3.9/docs/examples/example-example38/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example38/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example38/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example38/index.html  
  inflating: angular-1.3.9/docs/examples/example-example38/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example38/script.js  
   creating: angular-1.3.9/docs/examples/example-example39/
  inflating: angular-1.3.9/docs/examples/example-example39/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example39/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example39/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example39/index.html  
  inflating: angular-1.3.9/docs/examples/example-example39/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example39/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example39/script.js  
   creating: angular-1.3.9/docs/examples/example-example4/
  inflating: angular-1.3.9/docs/examples/example-example4/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example4/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example4/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example4/index.html  
  inflating: angular-1.3.9/docs/examples/example-example4/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example4/style.css  
   creating: angular-1.3.9/docs/examples/example-example40/
  inflating: angular-1.3.9/docs/examples/example-example40/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example40/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example40/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example40/index.html  
  inflating: angular-1.3.9/docs/examples/example-example40/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example40/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example40/script.js  
   creating: angular-1.3.9/docs/examples/example-example41/
  inflating: angular-1.3.9/docs/examples/example-example41/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example41/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example41/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example41/index.html  
  inflating: angular-1.3.9/docs/examples/example-example41/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example41/script.js  
   creating: angular-1.3.9/docs/examples/example-example42/
  inflating: angular-1.3.9/docs/examples/example-example42/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example42/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example42/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example42/index.html  
  inflating: angular-1.3.9/docs/examples/example-example42/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example42/script.js  
  inflating: angular-1.3.9/docs/examples/example-example42/style.css  
   creating: angular-1.3.9/docs/examples/example-example43/
  inflating: angular-1.3.9/docs/examples/example-example43/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example43/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example43/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example43/index.html  
  inflating: angular-1.3.9/docs/examples/example-example43/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example43/script.js  
   creating: angular-1.3.9/docs/examples/example-example44/
  inflating: angular-1.3.9/docs/examples/example-example44/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example44/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example44/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example44/index.html  
  inflating: angular-1.3.9/docs/examples/example-example44/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example44/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example44/script.js  
   creating: angular-1.3.9/docs/examples/example-example45/
  inflating: angular-1.3.9/docs/examples/example-example45/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example45/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example45/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example45/index.html  
  inflating: angular-1.3.9/docs/examples/example-example45/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example46/
  inflating: angular-1.3.9/docs/examples/example-example46/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example46/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example46/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example46/index.html  
  inflating: angular-1.3.9/docs/examples/example-example46/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example46/script.js  
   creating: angular-1.3.9/docs/examples/example-example47/
  inflating: angular-1.3.9/docs/examples/example-example47/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example47/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example47/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example47/index.html  
  inflating: angular-1.3.9/docs/examples/example-example47/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example47/script.js  
  inflating: angular-1.3.9/docs/examples/example-example47/style.css  
   creating: angular-1.3.9/docs/examples/example-example48/
  inflating: angular-1.3.9/docs/examples/example-example48/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example48/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example48/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example48/index.html  
  inflating: angular-1.3.9/docs/examples/example-example48/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example48/script.js  
  inflating: angular-1.3.9/docs/examples/example-example48/style.css  
   creating: angular-1.3.9/docs/examples/example-example49/
  inflating: angular-1.3.9/docs/examples/example-example49/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example49/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example49/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example49/index.html  
  inflating: angular-1.3.9/docs/examples/example-example49/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example49/script.js  
  inflating: angular-1.3.9/docs/examples/example-example49/style.css  
   creating: angular-1.3.9/docs/examples/example-example5/
  inflating: angular-1.3.9/docs/examples/example-example5/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example5/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example5/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example5/index.html  
  inflating: angular-1.3.9/docs/examples/example-example5/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example5/script.js  
   creating: angular-1.3.9/docs/examples/example-example50/
  inflating: angular-1.3.9/docs/examples/example-example50/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example50/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example50/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example50/index.html  
  inflating: angular-1.3.9/docs/examples/example-example50/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example50/script.js  
  inflating: angular-1.3.9/docs/examples/example-example50/style.css  
   creating: angular-1.3.9/docs/examples/example-example51/
  inflating: angular-1.3.9/docs/examples/example-example51/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example51/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example51/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example51/index.html  
  inflating: angular-1.3.9/docs/examples/example-example51/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example51/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example52/
  inflating: angular-1.3.9/docs/examples/example-example52/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example52/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example52/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example52/index.html  
  inflating: angular-1.3.9/docs/examples/example-example52/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example52/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example53/
  inflating: angular-1.3.9/docs/examples/example-example53/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example53/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example53/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example53/index.html  
  inflating: angular-1.3.9/docs/examples/example-example53/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example53/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example54/
  inflating: angular-1.3.9/docs/examples/example-example54/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example54/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example54/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example54/index.html  
  inflating: angular-1.3.9/docs/examples/example-example54/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example54/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example55/
  inflating: angular-1.3.9/docs/examples/example-example55/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example55/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example55/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example55/index.html  
  inflating: angular-1.3.9/docs/examples/example-example55/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example55/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example56/
  inflating: angular-1.3.9/docs/examples/example-example56/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example56/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example56/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example56/index.html  
  inflating: angular-1.3.9/docs/examples/example-example56/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example56/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example57/
  inflating: angular-1.3.9/docs/examples/example-example57/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example57/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example57/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example57/index.html  
  inflating: angular-1.3.9/docs/examples/example-example57/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example57/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example58/
  inflating: angular-1.3.9/docs/examples/example-example58/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example58/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example58/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example58/index.html  
  inflating: angular-1.3.9/docs/examples/example-example58/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example58/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example59/
  inflating: angular-1.3.9/docs/examples/example-example59/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example59/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example59/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example59/index.html  
  inflating: angular-1.3.9/docs/examples/example-example59/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example59/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example6/
  inflating: angular-1.3.9/docs/examples/example-example6/app.js  
  inflating: angular-1.3.9/docs/examples/example-example6/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example6/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example6/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example6/index.html  
  inflating: angular-1.3.9/docs/examples/example-example6/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example60/
  inflating: angular-1.3.9/docs/examples/example-example60/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example60/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example60/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example60/index.html  
  inflating: angular-1.3.9/docs/examples/example-example60/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example60/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example61/
  inflating: angular-1.3.9/docs/examples/example-example61/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example61/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example61/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example61/index.html  
  inflating: angular-1.3.9/docs/examples/example-example61/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example61/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example61/script.js  
   creating: angular-1.3.9/docs/examples/example-example62/
  inflating: angular-1.3.9/docs/examples/example-example62/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example62/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example62/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example62/index.html  
  inflating: angular-1.3.9/docs/examples/example-example62/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example62/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example62/style.css  
   creating: angular-1.3.9/docs/examples/example-example63/
  inflating: angular-1.3.9/docs/examples/example-example63/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example63/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example63/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example63/index.html  
  inflating: angular-1.3.9/docs/examples/example-example63/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example63/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example63/style.css  
   creating: angular-1.3.9/docs/examples/example-example64/
  inflating: angular-1.3.9/docs/examples/example-example64/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example64/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example64/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example64/index.html  
  inflating: angular-1.3.9/docs/examples/example-example64/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example64/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example64/style.css  
   creating: angular-1.3.9/docs/examples/example-example65/
  inflating: angular-1.3.9/docs/examples/example-example65/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example65/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example65/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example65/index.html  
  inflating: angular-1.3.9/docs/examples/example-example65/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example65/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example65/style.css  
   creating: angular-1.3.9/docs/examples/example-example66/
  inflating: angular-1.3.9/docs/examples/example-example66/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example66/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example66/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example66/index.html  
  inflating: angular-1.3.9/docs/examples/example-example66/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example66/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example67/
  inflating: angular-1.3.9/docs/examples/example-example67/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example67/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example67/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example67/index.html  
  inflating: angular-1.3.9/docs/examples/example-example67/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example67/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example68/
  inflating: angular-1.3.9/docs/examples/example-example68/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example68/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example68/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example68/index.html  
  inflating: angular-1.3.9/docs/examples/example-example68/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example69/
  inflating: angular-1.3.9/docs/examples/example-example69/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example69/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example69/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example69/index.html  
  inflating: angular-1.3.9/docs/examples/example-example69/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example7/
  inflating: angular-1.3.9/docs/examples/example-example7/app.js  
  inflating: angular-1.3.9/docs/examples/example-example7/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example7/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example7/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example7/index.html  
  inflating: angular-1.3.9/docs/examples/example-example7/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example70/
  inflating: angular-1.3.9/docs/examples/example-example70/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example70/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example70/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example70/index.html  
  inflating: angular-1.3.9/docs/examples/example-example70/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example71/
  inflating: angular-1.3.9/docs/examples/example-example71/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example71/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example71/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example71/index.html  
  inflating: angular-1.3.9/docs/examples/example-example71/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example72/
  inflating: angular-1.3.9/docs/examples/example-example72/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example72/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example72/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example72/index.html  
  inflating: angular-1.3.9/docs/examples/example-example72/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example73/
  inflating: angular-1.3.9/docs/examples/example-example73/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example73/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example73/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example73/index.html  
  inflating: angular-1.3.9/docs/examples/example-example73/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example74/
  inflating: angular-1.3.9/docs/examples/example-example74/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example74/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example74/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example74/index.html  
  inflating: angular-1.3.9/docs/examples/example-example74/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example75/
  inflating: angular-1.3.9/docs/examples/example-example75/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example75/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example75/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example75/index.html  
  inflating: angular-1.3.9/docs/examples/example-example75/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example76/
  inflating: angular-1.3.9/docs/examples/example-example76/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example76/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example76/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example76/index.html  
  inflating: angular-1.3.9/docs/examples/example-example76/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example77/
  inflating: angular-1.3.9/docs/examples/example-example77/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example77/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example77/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example77/index.html  
  inflating: angular-1.3.9/docs/examples/example-example77/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example78/
  inflating: angular-1.3.9/docs/examples/example-example78/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example78/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example78/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example78/index.html  
  inflating: angular-1.3.9/docs/examples/example-example78/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example78/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example79/
  inflating: angular-1.3.9/docs/examples/example-example79/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example79/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example79/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example79/index.html  
  inflating: angular-1.3.9/docs/examples/example-example79/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example8/
  inflating: angular-1.3.9/docs/examples/example-example8/app.css  
  inflating: angular-1.3.9/docs/examples/example-example8/app.js  
  inflating: angular-1.3.9/docs/examples/example-example8/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example8/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example8/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example8/index.html  
  inflating: angular-1.3.9/docs/examples/example-example8/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example80/
  inflating: angular-1.3.9/docs/examples/example-example80/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example80/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example80/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example80/index.html  
  inflating: angular-1.3.9/docs/examples/example-example80/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example81/
  inflating: angular-1.3.9/docs/examples/example-example81/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example81/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example81/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example81/index.html  
  inflating: angular-1.3.9/docs/examples/example-example81/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example82/
  inflating: angular-1.3.9/docs/examples/example-example82/animations.css  
  inflating: angular-1.3.9/docs/examples/example-example82/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example82/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example82/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example82/index.html  
  inflating: angular-1.3.9/docs/examples/example-example82/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example83/
  inflating: angular-1.3.9/docs/examples/example-example83/animations.css  
  inflating: angular-1.3.9/docs/examples/example-example83/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example83/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example83/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example83/index.html  
  inflating: angular-1.3.9/docs/examples/example-example83/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example83/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example83/script.js  
  inflating: angular-1.3.9/docs/examples/example-example83/template1.html  
  inflating: angular-1.3.9/docs/examples/example-example83/template2.html  
   creating: angular-1.3.9/docs/examples/example-example84/
  inflating: angular-1.3.9/docs/examples/example-example84/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example84/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example84/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example84/index.html  
  inflating: angular-1.3.9/docs/examples/example-example84/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example84/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example85/
  inflating: angular-1.3.9/docs/examples/example-example85/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example85/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example85/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example85/index.html  
  inflating: angular-1.3.9/docs/examples/example-example85/manifest.json  
   creating: angular-1.3.9/docs/examples/example-example86/
  inflating: angular-1.3.9/docs/examples/example-example86/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example86/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example86/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example86/index.html  
  inflating: angular-1.3.9/docs/examples/example-example86/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example86/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example87/
  inflating: angular-1.3.9/docs/examples/example-example87/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example87/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example87/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example87/index.html  
  inflating: angular-1.3.9/docs/examples/example-example87/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example87/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example88/
  inflating: angular-1.3.9/docs/examples/example-example88/animations.css  
  inflating: angular-1.3.9/docs/examples/example-example88/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example88/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example88/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example88/index.html  
  inflating: angular-1.3.9/docs/examples/example-example88/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example88/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example89/
  inflating: angular-1.3.9/docs/examples/example-example89/animations.css  
  inflating: angular-1.3.9/docs/examples/example-example89/glyphicons.css  
  inflating: angular-1.3.9/docs/examples/example-example89/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example89/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example89/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example89/index.html  
  inflating: angular-1.3.9/docs/examples/example-example89/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example89/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example9/
  inflating: angular-1.3.9/docs/examples/example-example9/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example9/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example9/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example9/index.html  
  inflating: angular-1.3.9/docs/examples/example-example9/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example9/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example9/script.js  
   creating: angular-1.3.9/docs/examples/example-example90/
  inflating: angular-1.3.9/docs/examples/example-example90/animations.css  
  inflating: angular-1.3.9/docs/examples/example-example90/glyphicons.css  
  inflating: angular-1.3.9/docs/examples/example-example90/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example90/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example90/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example90/index.html  
  inflating: angular-1.3.9/docs/examples/example-example90/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example90/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example91/
  inflating: angular-1.3.9/docs/examples/example-example91/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example91/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example91/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example91/index.html  
  inflating: angular-1.3.9/docs/examples/example-example91/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example91/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example91/style.css  
   creating: angular-1.3.9/docs/examples/example-example92/
  inflating: angular-1.3.9/docs/examples/example-example92/animations.css  
  inflating: angular-1.3.9/docs/examples/example-example92/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example92/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example92/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example92/index.html  
  inflating: angular-1.3.9/docs/examples/example-example92/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example92/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-example92/script.js  
   creating: angular-1.3.9/docs/examples/example-example93/
  inflating: angular-1.3.9/docs/examples/example-example93/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example93/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example93/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example93/index.html  
  inflating: angular-1.3.9/docs/examples/example-example93/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example93/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example94/
  inflating: angular-1.3.9/docs/examples/example-example94/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example94/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example94/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example94/index.html  
  inflating: angular-1.3.9/docs/examples/example-example94/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example94/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example95/
  inflating: angular-1.3.9/docs/examples/example-example95/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example95/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example95/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example95/index.html  
  inflating: angular-1.3.9/docs/examples/example-example95/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example95/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example96/
  inflating: angular-1.3.9/docs/examples/example-example96/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example96/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example96/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example96/index.html  
  inflating: angular-1.3.9/docs/examples/example-example96/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example96/script.js  
   creating: angular-1.3.9/docs/examples/example-example97/
  inflating: angular-1.3.9/docs/examples/example-example97/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example97/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example97/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example97/index.html  
  inflating: angular-1.3.9/docs/examples/example-example97/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example97/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example98/
  inflating: angular-1.3.9/docs/examples/example-example98/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example98/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example98/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example98/index.html  
  inflating: angular-1.3.9/docs/examples/example-example98/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example98/protractor.js  
   creating: angular-1.3.9/docs/examples/example-example99/
  inflating: angular-1.3.9/docs/examples/example-example99/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-example99/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-example99/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-example99/index.html  
  inflating: angular-1.3.9/docs/examples/example-example99/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-example99/protractor.js  
   creating: angular-1.3.9/docs/examples/example-guide-concepts-1/
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-1/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-1/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-1/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-1/index.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-1/manifest.json  
   creating: angular-1.3.9/docs/examples/example-guide-concepts-2/
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-2/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-2/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-2/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-2/index.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-2/invoice1.js  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-2/manifest.json  
   creating: angular-1.3.9/docs/examples/example-guide-concepts-21/
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-21/finance2.js  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-21/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-21/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-21/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-21/index.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-21/invoice2.js  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-21/manifest.json  
   creating: angular-1.3.9/docs/examples/example-guide-concepts-3/
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-3/finance3.js  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-3/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-3/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-3/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-3/index.html  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-3/invoice3.js  
  inflating: angular-1.3.9/docs/examples/example-guide-concepts-3/manifest.json  
   creating: angular-1.3.9/docs/examples/example-input-directive/
  inflating: angular-1.3.9/docs/examples/example-input-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-input-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-input-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-input-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-input-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-input-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-location-hashbang-mode/
  inflating: angular-1.3.9/docs/examples/example-location-hashbang-mode/addressBar.js  
  inflating: angular-1.3.9/docs/examples/example-location-hashbang-mode/app.js  
  inflating: angular-1.3.9/docs/examples/example-location-hashbang-mode/fakeBrowser.js  
  inflating: angular-1.3.9/docs/examples/example-location-hashbang-mode/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-location-hashbang-mode/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-location-hashbang-mode/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-location-hashbang-mode/index.html  
  inflating: angular-1.3.9/docs/examples/example-location-hashbang-mode/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-location-hashbang-mode/protractor.js  
   creating: angular-1.3.9/docs/examples/example-location-html5-mode/
  inflating: angular-1.3.9/docs/examples/example-location-html5-mode/addressBar.js  
  inflating: angular-1.3.9/docs/examples/example-location-html5-mode/app.js  
  inflating: angular-1.3.9/docs/examples/example-location-html5-mode/fakeBrowser.js  
  inflating: angular-1.3.9/docs/examples/example-location-html5-mode/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-location-html5-mode/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-location-html5-mode/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-location-html5-mode/index.html  
  inflating: angular-1.3.9/docs/examples/example-location-html5-mode/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-location-html5-mode/protractor.js  
   creating: angular-1.3.9/docs/examples/example-month-input-directive/
  inflating: angular-1.3.9/docs/examples/example-month-input-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-month-input-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-month-input-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-month-input-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-month-input-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-month-input-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-ng-model-cancel-update/
  inflating: angular-1.3.9/docs/examples/example-ng-model-cancel-update/app.js  
  inflating: angular-1.3.9/docs/examples/example-ng-model-cancel-update/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ng-model-cancel-update/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ng-model-cancel-update/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ng-model-cancel-update/index.html  
  inflating: angular-1.3.9/docs/examples/example-ng-model-cancel-update/manifest.json  
   creating: angular-1.3.9/docs/examples/example-ngChange-directive/
  inflating: angular-1.3.9/docs/examples/example-ngChange-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ngChange-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ngChange-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ngChange-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-ngChange-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-ngChange-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-ngController/
  inflating: angular-1.3.9/docs/examples/example-ngController/app.js  
  inflating: angular-1.3.9/docs/examples/example-ngController/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ngController/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ngController/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ngController/index.html  
  inflating: angular-1.3.9/docs/examples/example-ngController/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-ngController/protractor.js  
   creating: angular-1.3.9/docs/examples/example-ngControllerAs/
  inflating: angular-1.3.9/docs/examples/example-ngControllerAs/app.js  
  inflating: angular-1.3.9/docs/examples/example-ngControllerAs/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ngControllerAs/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ngControllerAs/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ngControllerAs/index.html  
  inflating: angular-1.3.9/docs/examples/example-ngControllerAs/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-ngControllerAs/protractor.js  
   creating: angular-1.3.9/docs/examples/example-ngList-directive/
   creating: angular-1.3.9/docs/examples/example-ngList-directive-newlines/
  inflating: angular-1.3.9/docs/examples/example-ngList-directive-newlines/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ngList-directive-newlines/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ngList-directive-newlines/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ngList-directive-newlines/index.html  
  inflating: angular-1.3.9/docs/examples/example-ngList-directive-newlines/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-ngList-directive-newlines/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-ngList-directive/app.js  
  inflating: angular-1.3.9/docs/examples/example-ngList-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ngList-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ngList-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ngList-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-ngList-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-ngList-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-ngMessages-directive/
  inflating: angular-1.3.9/docs/examples/example-ngMessages-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ngMessages-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ngMessages-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ngMessages-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-ngMessages-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-ngMessages-directive/script.js  
   creating: angular-1.3.9/docs/examples/example-ngModel-getter-setter/
  inflating: angular-1.3.9/docs/examples/example-ngModel-getter-setter/app.js  
  inflating: angular-1.3.9/docs/examples/example-ngModel-getter-setter/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ngModel-getter-setter/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ngModel-getter-setter/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ngModel-getter-setter/index.html  
  inflating: angular-1.3.9/docs/examples/example-ngModel-getter-setter/manifest.json  
   creating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-blur/
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-blur/app.js  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-blur/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-blur/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-blur/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-blur/index.html  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-blur/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-blur/protractor.js  
   creating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-debounce/
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-debounce/app.js  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-debounce/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-debounce/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-debounce/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-debounce/index.html  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-debounce/manifest.json  
   creating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-getter-setter/
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-getter-setter/app.js  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-getter-setter/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-getter-setter/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-getter-setter/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-getter-setter/index.html  
  inflating: angular-1.3.9/docs/examples/example-ngModelOptions-directive-getter-setter/manifest.json  
   creating: angular-1.3.9/docs/examples/example-ngValue-directive/
  inflating: angular-1.3.9/docs/examples/example-ngValue-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ngValue-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ngValue-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ngValue-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-ngValue-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-ngValue-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-ngView-directive/
  inflating: angular-1.3.9/docs/examples/example-ngView-directive/animations.css  
  inflating: angular-1.3.9/docs/examples/example-ngView-directive/book.html  
  inflating: angular-1.3.9/docs/examples/example-ngView-directive/chapter.html  
  inflating: angular-1.3.9/docs/examples/example-ngView-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-ngView-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-ngView-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-ngView-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-ngView-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-ngView-directive/protractor.js  
  inflating: angular-1.3.9/docs/examples/example-ngView-directive/script.js  
   creating: angular-1.3.9/docs/examples/example-number-input-directive/
  inflating: angular-1.3.9/docs/examples/example-number-input-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-number-input-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-number-input-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-number-input-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-number-input-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-number-input-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-radio-input-directive/
  inflating: angular-1.3.9/docs/examples/example-radio-input-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-radio-input-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-radio-input-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-radio-input-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-radio-input-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-radio-input-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-text-input-directive/
  inflating: angular-1.3.9/docs/examples/example-text-input-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-text-input-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-text-input-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-text-input-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-text-input-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-text-input-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-time-input-directive/
  inflating: angular-1.3.9/docs/examples/example-time-input-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-time-input-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-time-input-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-time-input-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-time-input-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-time-input-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-url-input-directive/
  inflating: angular-1.3.9/docs/examples/example-url-input-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-url-input-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-url-input-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-url-input-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-url-input-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-url-input-directive/protractor.js  
   creating: angular-1.3.9/docs/examples/example-week-input-directive/
  inflating: angular-1.3.9/docs/examples/example-week-input-directive/index-debug.html  
  inflating: angular-1.3.9/docs/examples/example-week-input-directive/index-jquery.html  
  inflating: angular-1.3.9/docs/examples/example-week-input-directive/index-production.html  
  inflating: angular-1.3.9/docs/examples/example-week-input-directive/index.html  
  inflating: angular-1.3.9/docs/examples/example-week-input-directive/manifest.json  
  inflating: angular-1.3.9/docs/examples/example-week-input-directive/protractor.js  
  inflating: angular-1.3.9/docs/favicon.ico  
   creating: angular-1.3.9/docs/img/
  inflating: angular-1.3.9/docs/img/AngularJS-small.png  
  inflating: angular-1.3.9/docs/img/One_Way_Data_Binding.png  
  inflating: angular-1.3.9/docs/img/Two_Way_Data_Binding.png  
  inflating: angular-1.3.9/docs/img/angular_parts.png  
  inflating: angular-1.3.9/docs/img/angularjs-for-header-only.svg  
  inflating: angular-1.3.9/docs/img/bullet.png  
  inflating: angular-1.3.9/docs/img/form_data_flow.png  
  inflating: angular-1.3.9/docs/img/glyphicons-halflings-white.png  
  inflating: angular-1.3.9/docs/img/glyphicons-halflings.png  
   creating: angular-1.3.9/docs/img/guide/
  inflating: angular-1.3.9/docs/img/guide/concepts-databinding1.png  
  inflating: angular-1.3.9/docs/img/guide/concepts-databinding2.png  
  inflating: angular-1.3.9/docs/img/guide/concepts-directive.png  
  inflating: angular-1.3.9/docs/img/guide/concepts-module-injector.png  
  inflating: angular-1.3.9/docs/img/guide/concepts-module-service.png  
  inflating: angular-1.3.9/docs/img/guide/concepts-runtime.png  
  inflating: angular-1.3.9/docs/img/guide/concepts-scope-watch-strategies.png  
  inflating: angular-1.3.9/docs/img/guide/concepts-scope.png  
  inflating: angular-1.3.9/docs/img/guide/concepts-startup.png  
  inflating: angular-1.3.9/docs/img/guide/concepts-view.png  
  inflating: angular-1.3.9/docs/img/guide/di_sequence_final.png  
  inflating: angular-1.3.9/docs/img/guide/dom_scope_final.png  
  inflating: angular-1.3.9/docs/img/guide/forms-debounce.gif  
  inflating: angular-1.3.9/docs/img/guide/forms-update-on-blur.gif  
  inflating: angular-1.3.9/docs/img/guide/hashbang_vs_regular_url.jpg  
  inflating: angular-1.3.9/docs/img/guide/scenario_runner.png  
  inflating: angular-1.3.9/docs/img/guide/simple_scope_final.png  
  inflating: angular-1.3.9/docs/img/helloworld.png  
  inflating: angular-1.3.9/docs/img/helloworld_2way.png  
   creating: angular-1.3.9/docs/img/tutorial/
  inflating: angular-1.3.9/docs/img/tutorial/catalog_screen.png  
  inflating: angular-1.3.9/docs/img/tutorial/tutorial_00.png  
  inflating: angular-1.3.9/docs/img/tutorial/tutorial_00_final.png  
  inflating: angular-1.3.9/docs/img/tutorial/tutorial_02.png  
  inflating: angular-1.3.9/docs/img/tutorial/tutorial_03.png  
  inflating: angular-1.3.9/docs/img/tutorial/tutorial_04.png  
  inflating: angular-1.3.9/docs/img/tutorial/tutorial_05.png  
  inflating: angular-1.3.9/docs/img/tutorial/tutorial_05.pptx  
  inflating: angular-1.3.9/docs/img/tutorial/tutorial_07_final.png  
  inflating: angular-1.3.9/docs/img/tutorial/tutorial_08-09_final.png  
  inflating: angular-1.3.9/docs/img/tutorial/tutorial_10-11_final.png  
  inflating: angular-1.3.9/docs/img/tutorial/xhr_service_final.png  
  inflating: angular-1.3.9/docs/index-debug.html  
  inflating: angular-1.3.9/docs/index-jquery.html  
  inflating: angular-1.3.9/docs/index-production.html  
  inflating: angular-1.3.9/docs/index.html  
   creating: angular-1.3.9/docs/js/
   creating: angular-1.3.9/docs/js/angular-bootstrap/
  inflating: angular-1.3.9/docs/js/angular-bootstrap/bootstrap.js  
  inflating: angular-1.3.9/docs/js/angular-bootstrap/bootstrap.min.js  
  inflating: angular-1.3.9/docs/js/angular-bootstrap/bootstrap.min.js.map  
  inflating: angular-1.3.9/docs/js/angular-bootstrap/dropdown-toggle.js  
  inflating: angular-1.3.9/docs/js/angular-bootstrap/dropdown-toggle.min.js  
  inflating: angular-1.3.9/docs/js/angular-bootstrap/dropdown-toggle.min.js.map  
  inflating: angular-1.3.9/docs/js/docs.js  
  inflating: angular-1.3.9/docs/js/docs.min.js  
  inflating: angular-1.3.9/docs/js/docs.min.js.map  
  inflating: angular-1.3.9/docs/js/nav-data.js  
  inflating: angular-1.3.9/docs/js/pages-data.js  
  inflating: angular-1.3.9/docs/js/search-data.json  
  inflating: angular-1.3.9/docs/js/search-worker.js  
  inflating: angular-1.3.9/docs/js/search-worker.min.js  
  inflating: angular-1.3.9/docs/js/search-worker.min.js.map  
  inflating: angular-1.3.9/docs/js/versions-data.js  
   creating: angular-1.3.9/docs/partials/
   creating: angular-1.3.9/docs/partials/api/
  inflating: angular-1.3.9/docs/partials/api.html  
   creating: angular-1.3.9/docs/partials/api/auto/
  inflating: angular-1.3.9/docs/partials/api/auto.html  
   creating: angular-1.3.9/docs/partials/api/auto/service/
  inflating: angular-1.3.9/docs/partials/api/auto/service.html  
  inflating: angular-1.3.9/docs/partials/api/auto/service/$injector.html  
  inflating: angular-1.3.9/docs/partials/api/auto/service/$provide.html  
   creating: angular-1.3.9/docs/partials/api/ng/
  inflating: angular-1.3.9/docs/partials/api/ng.html  
   creating: angular-1.3.9/docs/partials/api/ng/directive/
  inflating: angular-1.3.9/docs/partials/api/ng/directive.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/a.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/form.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/input.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngApp.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngBind.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngBindHtml.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngBindTemplate.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngBlur.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngChange.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngChecked.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngClass.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngClassEven.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngClassOdd.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngClick.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngCloak.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngController.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngCopy.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngCsp.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngCut.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngDblclick.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngDisabled.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngFocus.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngForm.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngHide.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngHref.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngIf.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngInclude.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngInit.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngKeydown.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngKeypress.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngKeyup.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngList.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngModel.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngModelOptions.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngMousedown.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngMouseenter.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngMouseleave.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngMousemove.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngMouseover.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngMouseup.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngNonBindable.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngOpen.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngPaste.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngPluralize.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngReadonly.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngRepeat.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngSelected.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngShow.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngSrc.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngSrcset.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngStyle.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngSubmit.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngSwitch.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngTransclude.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/ngValue.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/script.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/select.html  
  inflating: angular-1.3.9/docs/partials/api/ng/directive/textarea.html  
   creating: angular-1.3.9/docs/partials/api/ng/filter/
  inflating: angular-1.3.9/docs/partials/api/ng/filter.html  
  inflating: angular-1.3.9/docs/partials/api/ng/filter/currency.html  
  inflating: angular-1.3.9/docs/partials/api/ng/filter/date.html  
  inflating: angular-1.3.9/docs/partials/api/ng/filter/filter.html  
  inflating: angular-1.3.9/docs/partials/api/ng/filter/json.html  
  inflating: angular-1.3.9/docs/partials/api/ng/filter/limitTo.html  
  inflating: angular-1.3.9/docs/partials/api/ng/filter/lowercase.html  
  inflating: angular-1.3.9/docs/partials/api/ng/filter/number.html  
  inflating: angular-1.3.9/docs/partials/api/ng/filter/orderBy.html  
  inflating: angular-1.3.9/docs/partials/api/ng/filter/uppercase.html  
   creating: angular-1.3.9/docs/partials/api/ng/function/
  inflating: angular-1.3.9/docs/partials/api/ng/function.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.bind.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.bootstrap.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.copy.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.element.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.equals.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.extend.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.forEach.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.fromJson.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.identity.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.injector.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.isArray.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.isDate.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.isDefined.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.isElement.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.isFunction.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.isNumber.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.isObject.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.isString.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.isUndefined.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.lowercase.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.module.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.noop.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.reloadWithDebugInfo.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.toJson.html  
  inflating: angular-1.3.9/docs/partials/api/ng/function/angular.uppercase.html  
   creating: angular-1.3.9/docs/partials/api/ng/input/
  inflating: angular-1.3.9/docs/partials/api/ng/input.html  
  inflating: angular-1.3.9/docs/partials/api/ng/input/input[checkbox].html  
  inflating: angular-1.3.9/docs/partials/api/ng/input/input[date].html  
  inflating: angular-1.3.9/docs/partials/api/ng/input/input[datetime-local].html  
  inflating: angular-1.3.9/docs/partials/api/ng/input/input[email].html  
  inflating: angular-1.3.9/docs/partials/api/ng/input/input[month].html  
  inflating: angular-1.3.9/docs/partials/api/ng/input/input[number].html  
  inflating: angular-1.3.9/docs/partials/api/ng/input/input[radio].html  
  inflating: angular-1.3.9/docs/partials/api/ng/input/input[text].html  
  inflating: angular-1.3.9/docs/partials/api/ng/input/input[time].html  
  inflating: angular-1.3.9/docs/partials/api/ng/input/input[url].html  
  inflating: angular-1.3.9/docs/partials/api/ng/input/input[week].html  
   creating: angular-1.3.9/docs/partials/api/ng/object/
  inflating: angular-1.3.9/docs/partials/api/ng/object.html  
  inflating: angular-1.3.9/docs/partials/api/ng/object/angular.version.html  
   creating: angular-1.3.9/docs/partials/api/ng/provider/
  inflating: angular-1.3.9/docs/partials/api/ng/provider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$anchorScrollProvider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$animateProvider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$compileProvider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$controllerProvider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$filterProvider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$httpProvider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$interpolateProvider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$locationProvider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$logProvider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$parseProvider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$rootScopeProvider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$sceDelegateProvider.html  
  inflating: angular-1.3.9/docs/partials/api/ng/provider/$sceProvider.html  
   creating: angular-1.3.9/docs/partials/api/ng/service/
  inflating: angular-1.3.9/docs/partials/api/ng/service.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$anchorScroll.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$animate.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$cacheFactory.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$compile.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$controller.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$document.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$exceptionHandler.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$filter.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$http.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$httpBackend.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$interpolate.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$interval.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$locale.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$location.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$log.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$parse.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$q.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$rootElement.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$rootScope.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$sce.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$sceDelegate.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$templateCache.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$templateRequest.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$timeout.html  
  inflating: angular-1.3.9/docs/partials/api/ng/service/$window.html  
   creating: angular-1.3.9/docs/partials/api/ng/type/
  inflating: angular-1.3.9/docs/partials/api/ng/type.html  
  inflating: angular-1.3.9/docs/partials/api/ng/type/$cacheFactory.Cache.html  
  inflating: angular-1.3.9/docs/partials/api/ng/type/$compile.directive.Attributes.html  
  inflating: angular-1.3.9/docs/partials/api/ng/type/$rootScope.Scope.html  
  inflating: angular-1.3.9/docs/partials/api/ng/type/angular.Module.html  
  inflating: angular-1.3.9/docs/partials/api/ng/type/form.FormController.html  
  inflating: angular-1.3.9/docs/partials/api/ng/type/ngModel.NgModelController.html  
   creating: angular-1.3.9/docs/partials/api/ngAnimate/
  inflating: angular-1.3.9/docs/partials/api/ngAnimate.html  
   creating: angular-1.3.9/docs/partials/api/ngAnimate/provider/
  inflating: angular-1.3.9/docs/partials/api/ngAnimate/provider.html  
  inflating: angular-1.3.9/docs/partials/api/ngAnimate/provider/$animateProvider.html  
   creating: angular-1.3.9/docs/partials/api/ngAnimate/service/
  inflating: angular-1.3.9/docs/partials/api/ngAnimate/service.html  
  inflating: angular-1.3.9/docs/partials/api/ngAnimate/service/$animate.html  
   creating: angular-1.3.9/docs/partials/api/ngAria/
  inflating: angular-1.3.9/docs/partials/api/ngAria.html  
   creating: angular-1.3.9/docs/partials/api/ngAria/provider/
  inflating: angular-1.3.9/docs/partials/api/ngAria/provider.html  
  inflating: angular-1.3.9/docs/partials/api/ngAria/provider/$ariaProvider.html  
   creating: angular-1.3.9/docs/partials/api/ngAria/service/
  inflating: angular-1.3.9/docs/partials/api/ngAria/service.html  
  inflating: angular-1.3.9/docs/partials/api/ngAria/service/$aria.html  
   creating: angular-1.3.9/docs/partials/api/ngCookies/
  inflating: angular-1.3.9/docs/partials/api/ngCookies.html  
   creating: angular-1.3.9/docs/partials/api/ngCookies/service/
  inflating: angular-1.3.9/docs/partials/api/ngCookies/service.html  
  inflating: angular-1.3.9/docs/partials/api/ngCookies/service/$cookieStore.html  
  inflating: angular-1.3.9/docs/partials/api/ngCookies/service/$cookies.html  
   creating: angular-1.3.9/docs/partials/api/ngMessages/
  inflating: angular-1.3.9/docs/partials/api/ngMessages.html  
   creating: angular-1.3.9/docs/partials/api/ngMessages/directive/
  inflating: angular-1.3.9/docs/partials/api/ngMessages/directive.html  
  inflating: angular-1.3.9/docs/partials/api/ngMessages/directive/ngMessage.html  
  inflating: angular-1.3.9/docs/partials/api/ngMessages/directive/ngMessages.html  
   creating: angular-1.3.9/docs/partials/api/ngMock/
  inflating: angular-1.3.9/docs/partials/api/ngMock.html  
   creating: angular-1.3.9/docs/partials/api/ngMock/function/
  inflating: angular-1.3.9/docs/partials/api/ngMock/function.html  
  inflating: angular-1.3.9/docs/partials/api/ngMock/function/angular.mock.dump.html  
  inflating: angular-1.3.9/docs/partials/api/ngMock/function/angular.mock.inject.html  
  inflating: angular-1.3.9/docs/partials/api/ngMock/function/angular.mock.module.html  
   creating: angular-1.3.9/docs/partials/api/ngMock/object/
  inflating: angular-1.3.9/docs/partials/api/ngMock/object.html  
  inflating: angular-1.3.9/docs/partials/api/ngMock/object/angular.mock.html  
   creating: angular-1.3.9/docs/partials/api/ngMock/provider/
  inflating: angular-1.3.9/docs/partials/api/ngMock/provider.html  
  inflating: angular-1.3.9/docs/partials/api/ngMock/provider/$exceptionHandlerProvider.html  
   creating: angular-1.3.9/docs/partials/api/ngMock/service/
  inflating: angular-1.3.9/docs/partials/api/ngMock/service.html  
  inflating: angular-1.3.9/docs/partials/api/ngMock/service/$exceptionHandler.html  
  inflating: angular-1.3.9/docs/partials/api/ngMock/service/$httpBackend.html  
  inflating: angular-1.3.9/docs/partials/api/ngMock/service/$interval.html  
  inflating: angular-1.3.9/docs/partials/api/ngMock/service/$log.html  
  inflating: angular-1.3.9/docs/partials/api/ngMock/service/$timeout.html  
   creating: angular-1.3.9/docs/partials/api/ngMock/type/
  inflating: angular-1.3.9/docs/partials/api/ngMock/type.html  
  inflating: angular-1.3.9/docs/partials/api/ngMock/type/$rootScope.Scope.html  
  inflating: angular-1.3.9/docs/partials/api/ngMock/type/angular.mock.TzDate.html  
   creating: angular-1.3.9/docs/partials/api/ngMockE2E/
  inflating: angular-1.3.9/docs/partials/api/ngMockE2E.html  
   creating: angular-1.3.9/docs/partials/api/ngMockE2E/service/
  inflating: angular-1.3.9/docs/partials/api/ngMockE2E/service.html  
  inflating: angular-1.3.9/docs/partials/api/ngMockE2E/service/$httpBackend.html  
   creating: angular-1.3.9/docs/partials/api/ngResource/
  inflating: angular-1.3.9/docs/partials/api/ngResource.html  
   creating: angular-1.3.9/docs/partials/api/ngResource/service/
  inflating: angular-1.3.9/docs/partials/api/ngResource/service.html  
  inflating: angular-1.3.9/docs/partials/api/ngResource/service/$resource.html  
   creating: angular-1.3.9/docs/partials/api/ngRoute/
  inflating: angular-1.3.9/docs/partials/api/ngRoute.html  
   creating: angular-1.3.9/docs/partials/api/ngRoute/directive/
  inflating: angular-1.3.9/docs/partials/api/ngRoute/directive.html  
  inflating: angular-1.3.9/docs/partials/api/ngRoute/directive/ngView.html  
   creating: angular-1.3.9/docs/partials/api/ngRoute/provider/
  inflating: angular-1.3.9/docs/partials/api/ngRoute/provider.html  
  inflating: angular-1.3.9/docs/partials/api/ngRoute/provider/$routeProvider.html  
   creating: angular-1.3.9/docs/partials/api/ngRoute/service/
  inflating: angular-1.3.9/docs/partials/api/ngRoute/service.html  
  inflating: angular-1.3.9/docs/partials/api/ngRoute/service/$route.html  
  inflating: angular-1.3.9/docs/partials/api/ngRoute/service/$routeParams.html  
   creating: angular-1.3.9/docs/partials/api/ngSanitize/
  inflating: angular-1.3.9/docs/partials/api/ngSanitize.html  
   creating: angular-1.3.9/docs/partials/api/ngSanitize/filter/
  inflating: angular-1.3.9/docs/partials/api/ngSanitize/filter.html  
  inflating: angular-1.3.9/docs/partials/api/ngSanitize/filter/linky.html  
   creating: angular-1.3.9/docs/partials/api/ngSanitize/service/
  inflating: angular-1.3.9/docs/partials/api/ngSanitize/service.html  
  inflating: angular-1.3.9/docs/partials/api/ngSanitize/service/$sanitize.html  
   creating: angular-1.3.9/docs/partials/api/ngTouch/
  inflating: angular-1.3.9/docs/partials/api/ngTouch.html  
   creating: angular-1.3.9/docs/partials/api/ngTouch/directive/
  inflating: angular-1.3.9/docs/partials/api/ngTouch/directive.html  
  inflating: angular-1.3.9/docs/partials/api/ngTouch/directive/ngClick.html  
  inflating: angular-1.3.9/docs/partials/api/ngTouch/directive/ngSwipeLeft.html  
  inflating: angular-1.3.9/docs/partials/api/ngTouch/directive/ngSwipeRight.html  
   creating: angular-1.3.9/docs/partials/api/ngTouch/service/
  inflating: angular-1.3.9/docs/partials/api/ngTouch/service.html  
  inflating: angular-1.3.9/docs/partials/api/ngTouch/service/$swipe.html  
   creating: angular-1.3.9/docs/partials/error/
  inflating: angular-1.3.9/docs/partials/error.html  
   creating: angular-1.3.9/docs/partials/error/$animate/
  inflating: angular-1.3.9/docs/partials/error/$animate.html  
  inflating: angular-1.3.9/docs/partials/error/$animate/notcsel.html  
   creating: angular-1.3.9/docs/partials/error/$cacheFactory/
  inflating: angular-1.3.9/docs/partials/error/$cacheFactory.html  
  inflating: angular-1.3.9/docs/partials/error/$cacheFactory/iid.html  
   creating: angular-1.3.9/docs/partials/error/$compile/
  inflating: angular-1.3.9/docs/partials/error/$compile.html  
  inflating: angular-1.3.9/docs/partials/error/$compile/ctreq.html  
  inflating: angular-1.3.9/docs/partials/error/$compile/iscp.html  
  inflating: angular-1.3.9/docs/partials/error/$compile/multidir.html  
  inflating: angular-1.3.9/docs/partials/error/$compile/nodomevents.html  
  inflating: angular-1.3.9/docs/partials/error/$compile/nonassign.html  
  inflating: angular-1.3.9/docs/partials/error/$compile/selmulti.html  
  inflating: angular-1.3.9/docs/partials/error/$compile/tpload.html  
  inflating: angular-1.3.9/docs/partials/error/$compile/tplrt.html  
  inflating: angular-1.3.9/docs/partials/error/$compile/uterdir.html  
   creating: angular-1.3.9/docs/partials/error/$controller/
  inflating: angular-1.3.9/docs/partials/error/$controller.html  
  inflating: angular-1.3.9/docs/partials/error/$controller/noscp.html  
   creating: angular-1.3.9/docs/partials/error/$http/
  inflating: angular-1.3.9/docs/partials/error/$http.html  
  inflating: angular-1.3.9/docs/partials/error/$http/badreq.html  
   creating: angular-1.3.9/docs/partials/error/$injector/
  inflating: angular-1.3.9/docs/partials/error/$injector.html  
  inflating: angular-1.3.9/docs/partials/error/$injector/cdep.html  
  inflating: angular-1.3.9/docs/partials/error/$injector/itkn.html  
  inflating: angular-1.3.9/docs/partials/error/$injector/modulerr.html  
  inflating: angular-1.3.9/docs/partials/error/$injector/nomod.html  
  inflating: angular-1.3.9/docs/partials/error/$injector/pget.html  
  inflating: angular-1.3.9/docs/partials/error/$injector/strictdi.html  
  inflating: angular-1.3.9/docs/partials/error/$injector/undef.html  
  inflating: angular-1.3.9/docs/partials/error/$injector/unpr.html  
   creating: angular-1.3.9/docs/partials/error/$interpolate/
  inflating: angular-1.3.9/docs/partials/error/$interpolate.html  
  inflating: angular-1.3.9/docs/partials/error/$interpolate/interr.html  
  inflating: angular-1.3.9/docs/partials/error/$interpolate/noconcat.html  
   creating: angular-1.3.9/docs/partials/error/$location/
  inflating: angular-1.3.9/docs/partials/error/$location.html  
  inflating: angular-1.3.9/docs/partials/error/$location/ipthprfx.html  
  inflating: angular-1.3.9/docs/partials/error/$location/isrcharg.html  
  inflating: angular-1.3.9/docs/partials/error/$location/nobase.html  
  inflating: angular-1.3.9/docs/partials/error/$location/nostate.html  
   creating: angular-1.3.9/docs/partials/error/$parse/
  inflating: angular-1.3.9/docs/partials/error/$parse.html  
  inflating: angular-1.3.9/docs/partials/error/$parse/isecdom.html  
  inflating: angular-1.3.9/docs/partials/error/$parse/isecff.html  
  inflating: angular-1.3.9/docs/partials/error/$parse/isecfld.html  
  inflating: angular-1.3.9/docs/partials/error/$parse/isecfn.html  
  inflating: angular-1.3.9/docs/partials/error/$parse/isecobj.html  
  inflating: angular-1.3.9/docs/partials/error/$parse/isecwindow.html  
  inflating: angular-1.3.9/docs/partials/error/$parse/lexerr.html  
  inflating: angular-1.3.9/docs/partials/error/$parse/syntax.html  
  inflating: angular-1.3.9/docs/partials/error/$parse/ueoe.html  
   creating: angular-1.3.9/docs/partials/error/$q/
  inflating: angular-1.3.9/docs/partials/error/$q.html  
  inflating: angular-1.3.9/docs/partials/error/$q/norslvr.html  
  inflating: angular-1.3.9/docs/partials/error/$q/qcycle.html  
   creating: angular-1.3.9/docs/partials/error/$resource/
  inflating: angular-1.3.9/docs/partials/error/$resource.html  
  inflating: angular-1.3.9/docs/partials/error/$resource/badargs.html  
  inflating: angular-1.3.9/docs/partials/error/$resource/badcfg.html  
  inflating: angular-1.3.9/docs/partials/error/$resource/badmember.html  
  inflating: angular-1.3.9/docs/partials/error/$resource/badname.html  
   creating: angular-1.3.9/docs/partials/error/$rootScope/
  inflating: angular-1.3.9/docs/partials/error/$rootScope.html  
  inflating: angular-1.3.9/docs/partials/error/$rootScope/infdig.html  
  inflating: angular-1.3.9/docs/partials/error/$rootScope/inprog.html  
   creating: angular-1.3.9/docs/partials/error/$sanitize/
  inflating: angular-1.3.9/docs/partials/error/$sanitize.html  
  inflating: angular-1.3.9/docs/partials/error/$sanitize/badparse.html  
   creating: angular-1.3.9/docs/partials/error/$sce/
  inflating: angular-1.3.9/docs/partials/error/$sce.html  
  inflating: angular-1.3.9/docs/partials/error/$sce/icontext.html  
  inflating: angular-1.3.9/docs/partials/error/$sce/iequirks.html  
  inflating: angular-1.3.9/docs/partials/error/$sce/imatcher.html  
  inflating: angular-1.3.9/docs/partials/error/$sce/insecurl.html  
  inflating: angular-1.3.9/docs/partials/error/$sce/itype.html  
  inflating: angular-1.3.9/docs/partials/error/$sce/iwcard.html  
  inflating: angular-1.3.9/docs/partials/error/$sce/unsafe.html  
   creating: angular-1.3.9/docs/partials/error/jqLite/
  inflating: angular-1.3.9/docs/partials/error/jqLite.html  
  inflating: angular-1.3.9/docs/partials/error/jqLite/nosel.html  
  inflating: angular-1.3.9/docs/partials/error/jqLite/offargs.html  
  inflating: angular-1.3.9/docs/partials/error/jqLite/onargs.html  
   creating: angular-1.3.9/docs/partials/error/ng/
  inflating: angular-1.3.9/docs/partials/error/ng.html  
  inflating: angular-1.3.9/docs/partials/error/ng/areq.html  
  inflating: angular-1.3.9/docs/partials/error/ng/badname.html  
  inflating: angular-1.3.9/docs/partials/error/ng/btstrpd.html  
  inflating: angular-1.3.9/docs/partials/error/ng/cpi.html  
  inflating: angular-1.3.9/docs/partials/error/ng/cpws.html  
  inflating: angular-1.3.9/docs/partials/error/ng/test.html  
   creating: angular-1.3.9/docs/partials/error/ngModel/
  inflating: angular-1.3.9/docs/partials/error/ngModel.html  
  inflating: angular-1.3.9/docs/partials/error/ngModel/constexpr.html  
  inflating: angular-1.3.9/docs/partials/error/ngModel/datefmt.html  
  inflating: angular-1.3.9/docs/partials/error/ngModel/nonassign.html  
   creating: angular-1.3.9/docs/partials/error/ngOptions/
  inflating: angular-1.3.9/docs/partials/error/ngOptions.html  
  inflating: angular-1.3.9/docs/partials/error/ngOptions/iexp.html  
  inflating: angular-1.3.9/docs/partials/error/ngOptions/trkslct.html  
   creating: angular-1.3.9/docs/partials/error/ngPattern/
  inflating: angular-1.3.9/docs/partials/error/ngPattern.html  
  inflating: angular-1.3.9/docs/partials/error/ngPattern/noregexp.html  
   creating: angular-1.3.9/docs/partials/error/ngRepeat/
  inflating: angular-1.3.9/docs/partials/error/ngRepeat.html  
  inflating: angular-1.3.9/docs/partials/error/ngRepeat/badident.html  
  inflating: angular-1.3.9/docs/partials/error/ngRepeat/dupes.html  
  inflating: angular-1.3.9/docs/partials/error/ngRepeat/iexp.html  
  inflating: angular-1.3.9/docs/partials/error/ngRepeat/iidexp.html  
   creating: angular-1.3.9/docs/partials/error/ngTransclude/
  inflating: angular-1.3.9/docs/partials/error/ngTransclude.html  
  inflating: angular-1.3.9/docs/partials/error/ngTransclude/orphan.html  
   creating: angular-1.3.9/docs/partials/guide/
  inflating: angular-1.3.9/docs/partials/guide.html  
  inflating: angular-1.3.9/docs/partials/guide/$location.html  
  inflating: angular-1.3.9/docs/partials/guide/accessibility.html  
  inflating: angular-1.3.9/docs/partials/guide/animations.html  
  inflating: angular-1.3.9/docs/partials/guide/bootstrap.html  
  inflating: angular-1.3.9/docs/partials/guide/compiler.html  
  inflating: angular-1.3.9/docs/partials/guide/concepts.html  
  inflating: angular-1.3.9/docs/partials/guide/controller.html  
  inflating: angular-1.3.9/docs/partials/guide/css-styling.html  
  inflating: angular-1.3.9/docs/partials/guide/databinding.html  
  inflating: angular-1.3.9/docs/partials/guide/di.html  
  inflating: angular-1.3.9/docs/partials/guide/directive.html  
  inflating: angular-1.3.9/docs/partials/guide/e2e-testing.html  
  inflating: angular-1.3.9/docs/partials/guide/expression.html  
  inflating: angular-1.3.9/docs/partials/guide/filter.html  
  inflating: angular-1.3.9/docs/partials/guide/forms.html  
  inflating: angular-1.3.9/docs/partials/guide/i18n.html  
  inflating: angular-1.3.9/docs/partials/guide/ie.html  
  inflating: angular-1.3.9/docs/partials/guide/introduction.html  
  inflating: angular-1.3.9/docs/partials/guide/migration.html  
  inflating: angular-1.3.9/docs/partials/guide/module.html  
  inflating: angular-1.3.9/docs/partials/guide/production.html  
  inflating: angular-1.3.9/docs/partials/guide/providers.html  
  inflating: angular-1.3.9/docs/partials/guide/scope.html  
  inflating: angular-1.3.9/docs/partials/guide/security.html  
  inflating: angular-1.3.9/docs/partials/guide/services.html  
  inflating: angular-1.3.9/docs/partials/guide/templates.html  
  inflating: angular-1.3.9/docs/partials/guide/unit-testing.html  
   creating: angular-1.3.9/docs/partials/misc/
  inflating: angular-1.3.9/docs/partials/misc.html  
  inflating: angular-1.3.9/docs/partials/misc/contribute.html  
  inflating: angular-1.3.9/docs/partials/misc/downloading.html  
  inflating: angular-1.3.9/docs/partials/misc/faq.html  
  inflating: angular-1.3.9/docs/partials/misc/started.html  
   creating: angular-1.3.9/docs/partials/tutorial/
  inflating: angular-1.3.9/docs/partials/tutorial.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_00.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_01.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_02.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_03.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_04.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_05.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_06.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_07.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_08.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_09.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_10.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_11.html  
  inflating: angular-1.3.9/docs/partials/tutorial/step_12.html  
  inflating: angular-1.3.9/docs/partials/tutorial/the_end.html  
   creating: angular-1.3.9/docs/ptore2e/
   creating: angular-1.3.9/docs/ptore2e/example-$route-service/
  inflating: angular-1.3.9/docs/ptore2e/example-$route-service/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-$route-service/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-NgModelController/
  inflating: angular-1.3.9/docs/ptore2e/example-NgModelController/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-NgModelController/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-checkbox-input-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-checkbox-input-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-checkbox-input-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-date-input-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-date-input-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-date-input-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-datetimelocal-input-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-datetimelocal-input-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-datetimelocal-input-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-email-input-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-email-input-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-email-input-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example.csp/
  inflating: angular-1.3.9/docs/ptore2e/example-example.csp/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example.csp/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example100/
  inflating: angular-1.3.9/docs/ptore2e/example-example100/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example100/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example101/
  inflating: angular-1.3.9/docs/ptore2e/example-example101/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example101/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example102/
  inflating: angular-1.3.9/docs/ptore2e/example-example102/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example102/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example105/
  inflating: angular-1.3.9/docs/ptore2e/example-example105/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example105/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example106/
  inflating: angular-1.3.9/docs/ptore2e/example-example106/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example106/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example110/
  inflating: angular-1.3.9/docs/ptore2e/example-example110/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example110/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example111/
  inflating: angular-1.3.9/docs/ptore2e/example-example111/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example111/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example112/
  inflating: angular-1.3.9/docs/ptore2e/example-example112/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example112/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example113/
  inflating: angular-1.3.9/docs/ptore2e/example-example113/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example113/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example23/
  inflating: angular-1.3.9/docs/ptore2e/example-example23/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example23/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example24/
  inflating: angular-1.3.9/docs/ptore2e/example-example24/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example24/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example25/
  inflating: angular-1.3.9/docs/ptore2e/example-example25/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example25/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example27/
  inflating: angular-1.3.9/docs/ptore2e/example-example27/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example27/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example39/
  inflating: angular-1.3.9/docs/ptore2e/example-example39/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example39/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example40/
  inflating: angular-1.3.9/docs/ptore2e/example-example40/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example40/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example44/
  inflating: angular-1.3.9/docs/ptore2e/example-example44/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example44/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example51/
  inflating: angular-1.3.9/docs/ptore2e/example-example51/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example51/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example52/
  inflating: angular-1.3.9/docs/ptore2e/example-example52/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example52/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example53/
  inflating: angular-1.3.9/docs/ptore2e/example-example53/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example53/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example54/
  inflating: angular-1.3.9/docs/ptore2e/example-example54/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example54/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example55/
  inflating: angular-1.3.9/docs/ptore2e/example-example55/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example55/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example56/
  inflating: angular-1.3.9/docs/ptore2e/example-example56/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example56/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example57/
  inflating: angular-1.3.9/docs/ptore2e/example-example57/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example57/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example58/
  inflating: angular-1.3.9/docs/ptore2e/example-example58/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example58/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example59/
  inflating: angular-1.3.9/docs/ptore2e/example-example59/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example59/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example60/
  inflating: angular-1.3.9/docs/ptore2e/example-example60/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example60/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example61/
  inflating: angular-1.3.9/docs/ptore2e/example-example61/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example61/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example62/
  inflating: angular-1.3.9/docs/ptore2e/example-example62/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example62/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example63/
  inflating: angular-1.3.9/docs/ptore2e/example-example63/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example63/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example64/
  inflating: angular-1.3.9/docs/ptore2e/example-example64/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example64/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example65/
  inflating: angular-1.3.9/docs/ptore2e/example-example65/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example65/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example66/
  inflating: angular-1.3.9/docs/ptore2e/example-example66/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example66/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example67/
  inflating: angular-1.3.9/docs/ptore2e/example-example67/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example67/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example78/
  inflating: angular-1.3.9/docs/ptore2e/example-example78/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example78/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example83/
  inflating: angular-1.3.9/docs/ptore2e/example-example83/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example83/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example84/
  inflating: angular-1.3.9/docs/ptore2e/example-example84/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example84/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example86/
  inflating: angular-1.3.9/docs/ptore2e/example-example86/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example86/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example87/
  inflating: angular-1.3.9/docs/ptore2e/example-example87/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example87/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example88/
  inflating: angular-1.3.9/docs/ptore2e/example-example88/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example88/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example89/
  inflating: angular-1.3.9/docs/ptore2e/example-example89/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example89/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example9/
  inflating: angular-1.3.9/docs/ptore2e/example-example9/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example9/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example90/
  inflating: angular-1.3.9/docs/ptore2e/example-example90/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example90/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example91/
  inflating: angular-1.3.9/docs/ptore2e/example-example91/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example91/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example92/
  inflating: angular-1.3.9/docs/ptore2e/example-example92/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example92/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example93/
  inflating: angular-1.3.9/docs/ptore2e/example-example93/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example93/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example94/
  inflating: angular-1.3.9/docs/ptore2e/example-example94/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example94/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example95/
  inflating: angular-1.3.9/docs/ptore2e/example-example95/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example95/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example97/
  inflating: angular-1.3.9/docs/ptore2e/example-example97/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example97/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example98/
  inflating: angular-1.3.9/docs/ptore2e/example-example98/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example98/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-example99/
  inflating: angular-1.3.9/docs/ptore2e/example-example99/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-example99/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-input-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-input-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-input-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-location-hashbang-mode/
  inflating: angular-1.3.9/docs/ptore2e/example-location-hashbang-mode/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-location-hashbang-mode/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-location-html5-mode/
  inflating: angular-1.3.9/docs/ptore2e/example-location-html5-mode/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-location-html5-mode/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-month-input-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-month-input-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-month-input-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-ngChange-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-ngChange-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-ngChange-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-ngController/
  inflating: angular-1.3.9/docs/ptore2e/example-ngController/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-ngController/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-ngControllerAs/
  inflating: angular-1.3.9/docs/ptore2e/example-ngControllerAs/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-ngControllerAs/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-ngList-directive/
   creating: angular-1.3.9/docs/ptore2e/example-ngList-directive-newlines/
  inflating: angular-1.3.9/docs/ptore2e/example-ngList-directive-newlines/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-ngList-directive-newlines/jquery_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-ngList-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-ngList-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-ngModelOptions-directive-blur/
  inflating: angular-1.3.9/docs/ptore2e/example-ngModelOptions-directive-blur/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-ngModelOptions-directive-blur/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-ngValue-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-ngValue-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-ngValue-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-ngView-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-ngView-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-ngView-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-number-input-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-number-input-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-number-input-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-radio-input-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-radio-input-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-radio-input-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-text-input-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-text-input-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-text-input-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-time-input-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-time-input-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-time-input-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-url-input-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-url-input-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-url-input-directive/jquery_test.js  
   creating: angular-1.3.9/docs/ptore2e/example-week-input-directive/
  inflating: angular-1.3.9/docs/ptore2e/example-week-input-directive/default_test.js  
  inflating: angular-1.3.9/docs/ptore2e/example-week-input-directive/jquery_test.js  
  inflating: angular-1.3.9/errors.json  
   creating: angular-1.3.9/i18n/
  inflating: angular-1.3.9/i18n/angular-locale_aa-dj.js  
  inflating: angular-1.3.9/i18n/angular-locale_aa-er.js  
  inflating: angular-1.3.9/i18n/angular-locale_aa-et.js  
  inflating: angular-1.3.9/i18n/angular-locale_aa.js  
  inflating: angular-1.3.9/i18n/angular-locale_af-na.js  
  inflating: angular-1.3.9/i18n/angular-locale_af-za.js  
  inflating: angular-1.3.9/i18n/angular-locale_af.js  
  inflating: angular-1.3.9/i18n/angular-locale_agq-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_agq.js  
  inflating: angular-1.3.9/i18n/angular-locale_ak-gh.js  
  inflating: angular-1.3.9/i18n/angular-locale_ak.js  
  inflating: angular-1.3.9/i18n/angular-locale_am-et.js  
  inflating: angular-1.3.9/i18n/angular-locale_am.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-001.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-ae.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-bh.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-dj.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-dz.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-eg.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-eh.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-er.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-il.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-iq.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-jo.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-km.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-kw.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-lb.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-ly.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-ma.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-mr.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-om.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-ps.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-qa.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-sa.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-sd.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-so.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-ss.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-sy.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-td.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-tn.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar-ye.js  
  inflating: angular-1.3.9/i18n/angular-locale_ar.js  
  inflating: angular-1.3.9/i18n/angular-locale_as-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_as.js  
  inflating: angular-1.3.9/i18n/angular-locale_asa-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_asa.js  
  inflating: angular-1.3.9/i18n/angular-locale_ast-es.js  
  inflating: angular-1.3.9/i18n/angular-locale_ast.js  
  inflating: angular-1.3.9/i18n/angular-locale_az-cyrl-az.js  
  inflating: angular-1.3.9/i18n/angular-locale_az-cyrl.js  
  inflating: angular-1.3.9/i18n/angular-locale_az-latn-az.js  
  inflating: angular-1.3.9/i18n/angular-locale_az-latn.js  
  inflating: angular-1.3.9/i18n/angular-locale_az.js  
  inflating: angular-1.3.9/i18n/angular-locale_bas-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_bas.js  
  inflating: angular-1.3.9/i18n/angular-locale_be-by.js  
  inflating: angular-1.3.9/i18n/angular-locale_be.js  
  inflating: angular-1.3.9/i18n/angular-locale_bem-zm.js  
  inflating: angular-1.3.9/i18n/angular-locale_bem.js  
  inflating: angular-1.3.9/i18n/angular-locale_bez-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_bez.js  
  inflating: angular-1.3.9/i18n/angular-locale_bg-bg.js  
  inflating: angular-1.3.9/i18n/angular-locale_bg.js  
  inflating: angular-1.3.9/i18n/angular-locale_bm-latn-ml.js  
  inflating: angular-1.3.9/i18n/angular-locale_bm-latn.js  
  inflating: angular-1.3.9/i18n/angular-locale_bm-ml.js  
  inflating: angular-1.3.9/i18n/angular-locale_bm.js  
  inflating: angular-1.3.9/i18n/angular-locale_bn-bd.js  
  inflating: angular-1.3.9/i18n/angular-locale_bn-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_bn.js  
  inflating: angular-1.3.9/i18n/angular-locale_bo-cn.js  
  inflating: angular-1.3.9/i18n/angular-locale_bo-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_bo.js  
  inflating: angular-1.3.9/i18n/angular-locale_br-fr.js  
  inflating: angular-1.3.9/i18n/angular-locale_br.js  
  inflating: angular-1.3.9/i18n/angular-locale_brx-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_brx.js  
  inflating: angular-1.3.9/i18n/angular-locale_bs-cyrl-ba.js  
  inflating: angular-1.3.9/i18n/angular-locale_bs-cyrl.js  
  inflating: angular-1.3.9/i18n/angular-locale_bs-latn-ba.js  
  inflating: angular-1.3.9/i18n/angular-locale_bs-latn.js  
  inflating: angular-1.3.9/i18n/angular-locale_bs.js  
  inflating: angular-1.3.9/i18n/angular-locale_byn-er.js  
  inflating: angular-1.3.9/i18n/angular-locale_byn.js  
  inflating: angular-1.3.9/i18n/angular-locale_ca-ad.js  
  inflating: angular-1.3.9/i18n/angular-locale_ca-es-valencia.js  
  inflating: angular-1.3.9/i18n/angular-locale_ca-es.js  
  inflating: angular-1.3.9/i18n/angular-locale_ca-fr.js  
  inflating: angular-1.3.9/i18n/angular-locale_ca-it.js  
  inflating: angular-1.3.9/i18n/angular-locale_ca.js  
  inflating: angular-1.3.9/i18n/angular-locale_cgg-ug.js  
  inflating: angular-1.3.9/i18n/angular-locale_cgg.js  
  inflating: angular-1.3.9/i18n/angular-locale_chr-us.js  
  inflating: angular-1.3.9/i18n/angular-locale_chr.js  
  inflating: angular-1.3.9/i18n/angular-locale_ckb-arab-iq.js  
  inflating: angular-1.3.9/i18n/angular-locale_ckb-arab-ir.js  
  inflating: angular-1.3.9/i18n/angular-locale_ckb-arab.js  
  inflating: angular-1.3.9/i18n/angular-locale_ckb-iq.js  
  inflating: angular-1.3.9/i18n/angular-locale_ckb-ir.js  
  inflating: angular-1.3.9/i18n/angular-locale_ckb-latn-iq.js  
  inflating: angular-1.3.9/i18n/angular-locale_ckb-latn.js  
  inflating: angular-1.3.9/i18n/angular-locale_ckb.js  
  inflating: angular-1.3.9/i18n/angular-locale_cs-cz.js  
  inflating: angular-1.3.9/i18n/angular-locale_cs.js  
  inflating: angular-1.3.9/i18n/angular-locale_cy-gb.js  
  inflating: angular-1.3.9/i18n/angular-locale_cy.js  
  inflating: angular-1.3.9/i18n/angular-locale_da-dk.js  
  inflating: angular-1.3.9/i18n/angular-locale_da-gl.js  
  inflating: angular-1.3.9/i18n/angular-locale_da.js  
  inflating: angular-1.3.9/i18n/angular-locale_dav-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_dav.js  
  inflating: angular-1.3.9/i18n/angular-locale_de-at.js  
  inflating: angular-1.3.9/i18n/angular-locale_de-be.js  
  inflating: angular-1.3.9/i18n/angular-locale_de-ch.js  
  inflating: angular-1.3.9/i18n/angular-locale_de-de.js  
  inflating: angular-1.3.9/i18n/angular-locale_de-li.js  
  inflating: angular-1.3.9/i18n/angular-locale_de-lu.js  
  inflating: angular-1.3.9/i18n/angular-locale_de.js  
  inflating: angular-1.3.9/i18n/angular-locale_dje-ne.js  
  inflating: angular-1.3.9/i18n/angular-locale_dje.js  
  inflating: angular-1.3.9/i18n/angular-locale_dsb-de.js  
  inflating: angular-1.3.9/i18n/angular-locale_dsb.js  
  inflating: angular-1.3.9/i18n/angular-locale_dua-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_dua.js  
  inflating: angular-1.3.9/i18n/angular-locale_dyo-sn.js  
  inflating: angular-1.3.9/i18n/angular-locale_dyo.js  
  inflating: angular-1.3.9/i18n/angular-locale_dz-bt.js  
  inflating: angular-1.3.9/i18n/angular-locale_dz.js  
  inflating: angular-1.3.9/i18n/angular-locale_ebu-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_ebu.js  
  inflating: angular-1.3.9/i18n/angular-locale_ee-gh.js  
  inflating: angular-1.3.9/i18n/angular-locale_ee-tg.js  
  inflating: angular-1.3.9/i18n/angular-locale_ee.js  
  inflating: angular-1.3.9/i18n/angular-locale_el-cy.js  
  inflating: angular-1.3.9/i18n/angular-locale_el-gr.js  
  inflating: angular-1.3.9/i18n/angular-locale_el.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-001.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-150.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ag.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ai.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-as.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-au.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-bb.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-be.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-bm.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-bs.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-bw.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-bz.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ca.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-cc.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ck.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-cx.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-dg.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-dm.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-er.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-fj.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-fk.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-fm.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-gb.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-gd.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-gg.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-gh.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-gi.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-gm.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-gu.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-gy.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-hk.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ie.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-im.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-io.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-iso.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-je.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-jm.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ki.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-kn.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ky.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-lc.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-lr.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ls.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-mg.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-mh.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-mo.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-mp.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ms.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-mt.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-mu.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-mw.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-my.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-na.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-nf.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ng.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-nr.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-nu.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-nz.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-pg.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ph.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-pk.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-pn.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-pr.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-pw.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-rw.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-sb.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-sc.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-sd.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-sg.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-sh.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-sl.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ss.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-sx.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-sz.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-tc.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-tk.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-to.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-tt.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-tv.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ug.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-um.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-us.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-vc.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-vg.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-vi.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-vu.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-ws.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-za.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-zm.js  
  inflating: angular-1.3.9/i18n/angular-locale_en-zw.js  
  inflating: angular-1.3.9/i18n/angular-locale_en.js  
  inflating: angular-1.3.9/i18n/angular-locale_eo-001.js  
  inflating: angular-1.3.9/i18n/angular-locale_eo.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-419.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-ar.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-bo.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-cl.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-co.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-cr.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-cu.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-do.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-ea.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-ec.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-es.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-gq.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-gt.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-hn.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-ic.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-mx.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-ni.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-pa.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-pe.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-ph.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-pr.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-py.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-sv.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-us.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-uy.js  
  inflating: angular-1.3.9/i18n/angular-locale_es-ve.js  
  inflating: angular-1.3.9/i18n/angular-locale_es.js  
  inflating: angular-1.3.9/i18n/angular-locale_et-ee.js  
  inflating: angular-1.3.9/i18n/angular-locale_et.js  
  inflating: angular-1.3.9/i18n/angular-locale_eu-es.js  
  inflating: angular-1.3.9/i18n/angular-locale_eu.js  
  inflating: angular-1.3.9/i18n/angular-locale_ewo-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_ewo.js  
  inflating: angular-1.3.9/i18n/angular-locale_fa-af.js  
  inflating: angular-1.3.9/i18n/angular-locale_fa-ir.js  
  inflating: angular-1.3.9/i18n/angular-locale_fa.js  
  inflating: angular-1.3.9/i18n/angular-locale_ff-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_ff-gn.js  
  inflating: angular-1.3.9/i18n/angular-locale_ff-mr.js  
  inflating: angular-1.3.9/i18n/angular-locale_ff-sn.js  
  inflating: angular-1.3.9/i18n/angular-locale_ff.js  
  inflating: angular-1.3.9/i18n/angular-locale_fi-fi.js  
  inflating: angular-1.3.9/i18n/angular-locale_fi.js  
  inflating: angular-1.3.9/i18n/angular-locale_fil-ph.js  
  inflating: angular-1.3.9/i18n/angular-locale_fil.js  
  inflating: angular-1.3.9/i18n/angular-locale_fo-fo.js  
  inflating: angular-1.3.9/i18n/angular-locale_fo.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-be.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-bf.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-bi.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-bj.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-bl.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-ca.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-cd.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-cf.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-cg.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-ch.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-ci.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-dj.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-dz.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-fr.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-ga.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-gf.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-gn.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-gp.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-gq.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-ht.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-km.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-lu.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-ma.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-mc.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-mf.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-mg.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-ml.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-mq.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-mr.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-mu.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-nc.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-ne.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-pf.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-pm.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-re.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-rw.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-sc.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-sn.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-sy.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-td.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-tg.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-tn.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-vu.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-wf.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr-yt.js  
  inflating: angular-1.3.9/i18n/angular-locale_fr.js  
  inflating: angular-1.3.9/i18n/angular-locale_fur-it.js  
  inflating: angular-1.3.9/i18n/angular-locale_fur.js  
  inflating: angular-1.3.9/i18n/angular-locale_fy-nl.js  
  inflating: angular-1.3.9/i18n/angular-locale_fy.js  
  inflating: angular-1.3.9/i18n/angular-locale_ga-ie.js  
  inflating: angular-1.3.9/i18n/angular-locale_ga.js  
  inflating: angular-1.3.9/i18n/angular-locale_gd-gb.js  
  inflating: angular-1.3.9/i18n/angular-locale_gd.js  
  inflating: angular-1.3.9/i18n/angular-locale_gl-es.js  
  inflating: angular-1.3.9/i18n/angular-locale_gl.js  
  inflating: angular-1.3.9/i18n/angular-locale_gsw-ch.js  
  inflating: angular-1.3.9/i18n/angular-locale_gsw-fr.js  
  inflating: angular-1.3.9/i18n/angular-locale_gsw-li.js  
  inflating: angular-1.3.9/i18n/angular-locale_gsw.js  
  inflating: angular-1.3.9/i18n/angular-locale_gu-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_gu.js  
  inflating: angular-1.3.9/i18n/angular-locale_guz-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_guz.js  
  inflating: angular-1.3.9/i18n/angular-locale_gv-im.js  
  inflating: angular-1.3.9/i18n/angular-locale_gv.js  
  inflating: angular-1.3.9/i18n/angular-locale_ha-latn-gh.js  
  inflating: angular-1.3.9/i18n/angular-locale_ha-latn-ne.js  
  inflating: angular-1.3.9/i18n/angular-locale_ha-latn-ng.js  
  inflating: angular-1.3.9/i18n/angular-locale_ha-latn.js  
  inflating: angular-1.3.9/i18n/angular-locale_ha.js  
  inflating: angular-1.3.9/i18n/angular-locale_haw-us.js  
  inflating: angular-1.3.9/i18n/angular-locale_haw.js  
  inflating: angular-1.3.9/i18n/angular-locale_he-il.js  
  inflating: angular-1.3.9/i18n/angular-locale_he.js  
  inflating: angular-1.3.9/i18n/angular-locale_hi-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_hi.js  
  inflating: angular-1.3.9/i18n/angular-locale_hr-ba.js  
  inflating: angular-1.3.9/i18n/angular-locale_hr-hr.js  
  inflating: angular-1.3.9/i18n/angular-locale_hr.js  
  inflating: angular-1.3.9/i18n/angular-locale_hsb-de.js  
  inflating: angular-1.3.9/i18n/angular-locale_hsb.js  
  inflating: angular-1.3.9/i18n/angular-locale_hu-hu.js  
  inflating: angular-1.3.9/i18n/angular-locale_hu.js  
  inflating: angular-1.3.9/i18n/angular-locale_hy-am.js  
  inflating: angular-1.3.9/i18n/angular-locale_hy.js  
  inflating: angular-1.3.9/i18n/angular-locale_ia-fr.js  
  inflating: angular-1.3.9/i18n/angular-locale_ia.js  
  inflating: angular-1.3.9/i18n/angular-locale_id-id.js  
  inflating: angular-1.3.9/i18n/angular-locale_id.js  
  inflating: angular-1.3.9/i18n/angular-locale_ig-ng.js  
  inflating: angular-1.3.9/i18n/angular-locale_ig.js  
  inflating: angular-1.3.9/i18n/angular-locale_ii-cn.js  
  inflating: angular-1.3.9/i18n/angular-locale_ii.js  
  inflating: angular-1.3.9/i18n/angular-locale_in.js  
  inflating: angular-1.3.9/i18n/angular-locale_is-is.js  
  inflating: angular-1.3.9/i18n/angular-locale_is.js  
  inflating: angular-1.3.9/i18n/angular-locale_it-ch.js  
  inflating: angular-1.3.9/i18n/angular-locale_it-it.js  
  inflating: angular-1.3.9/i18n/angular-locale_it-sm.js  
  inflating: angular-1.3.9/i18n/angular-locale_it.js  
  inflating: angular-1.3.9/i18n/angular-locale_iw.js  
  inflating: angular-1.3.9/i18n/angular-locale_ja-jp.js  
  inflating: angular-1.3.9/i18n/angular-locale_ja.js  
  inflating: angular-1.3.9/i18n/angular-locale_jgo-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_jgo.js  
  inflating: angular-1.3.9/i18n/angular-locale_jmc-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_jmc.js  
  inflating: angular-1.3.9/i18n/angular-locale_ka-ge.js  
  inflating: angular-1.3.9/i18n/angular-locale_ka.js  
  inflating: angular-1.3.9/i18n/angular-locale_kab-dz.js  
  inflating: angular-1.3.9/i18n/angular-locale_kab.js  
  inflating: angular-1.3.9/i18n/angular-locale_kam-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_kam.js  
  inflating: angular-1.3.9/i18n/angular-locale_kde-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_kde.js  
  inflating: angular-1.3.9/i18n/angular-locale_kea-cv.js  
  inflating: angular-1.3.9/i18n/angular-locale_kea.js  
  inflating: angular-1.3.9/i18n/angular-locale_khq-ml.js  
  inflating: angular-1.3.9/i18n/angular-locale_khq.js  
  inflating: angular-1.3.9/i18n/angular-locale_ki-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_ki.js  
  inflating: angular-1.3.9/i18n/angular-locale_kk-cyrl-kz.js  
  inflating: angular-1.3.9/i18n/angular-locale_kk-cyrl.js  
  inflating: angular-1.3.9/i18n/angular-locale_kk.js  
  inflating: angular-1.3.9/i18n/angular-locale_kkj-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_kkj.js  
  inflating: angular-1.3.9/i18n/angular-locale_kl-gl.js  
  inflating: angular-1.3.9/i18n/angular-locale_kl.js  
  inflating: angular-1.3.9/i18n/angular-locale_kln-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_kln.js  
  inflating: angular-1.3.9/i18n/angular-locale_km-kh.js  
  inflating: angular-1.3.9/i18n/angular-locale_km.js  
  inflating: angular-1.3.9/i18n/angular-locale_kn-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_kn.js  
  inflating: angular-1.3.9/i18n/angular-locale_ko-kp.js  
  inflating: angular-1.3.9/i18n/angular-locale_ko-kr.js  
  inflating: angular-1.3.9/i18n/angular-locale_ko.js  
  inflating: angular-1.3.9/i18n/angular-locale_kok-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_kok.js  
  inflating: angular-1.3.9/i18n/angular-locale_ks-arab-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_ks-arab.js  
  inflating: angular-1.3.9/i18n/angular-locale_ks.js  
  inflating: angular-1.3.9/i18n/angular-locale_ksb-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_ksb.js  
  inflating: angular-1.3.9/i18n/angular-locale_ksf-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_ksf.js  
  inflating: angular-1.3.9/i18n/angular-locale_ksh-de.js  
  inflating: angular-1.3.9/i18n/angular-locale_ksh.js  
  inflating: angular-1.3.9/i18n/angular-locale_kw-gb.js  
  inflating: angular-1.3.9/i18n/angular-locale_kw.js  
  inflating: angular-1.3.9/i18n/angular-locale_ky-cyrl-kg.js  
  inflating: angular-1.3.9/i18n/angular-locale_ky-cyrl.js  
  inflating: angular-1.3.9/i18n/angular-locale_ky.js  
  inflating: angular-1.3.9/i18n/angular-locale_lag-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_lag.js  
  inflating: angular-1.3.9/i18n/angular-locale_lb-lu.js  
  inflating: angular-1.3.9/i18n/angular-locale_lb.js  
  inflating: angular-1.3.9/i18n/angular-locale_lg-ug.js  
  inflating: angular-1.3.9/i18n/angular-locale_lg.js  
  inflating: angular-1.3.9/i18n/angular-locale_lkt-us.js  
  inflating: angular-1.3.9/i18n/angular-locale_lkt.js  
  inflating: angular-1.3.9/i18n/angular-locale_ln-ao.js  
  inflating: angular-1.3.9/i18n/angular-locale_ln-cd.js  
  inflating: angular-1.3.9/i18n/angular-locale_ln-cf.js  
  inflating: angular-1.3.9/i18n/angular-locale_ln-cg.js  
  inflating: angular-1.3.9/i18n/angular-locale_ln.js  
  inflating: angular-1.3.9/i18n/angular-locale_lo-la.js  
  inflating: angular-1.3.9/i18n/angular-locale_lo.js  
  inflating: angular-1.3.9/i18n/angular-locale_lt-lt.js  
  inflating: angular-1.3.9/i18n/angular-locale_lt.js  
  inflating: angular-1.3.9/i18n/angular-locale_lu-cd.js  
  inflating: angular-1.3.9/i18n/angular-locale_lu.js  
  inflating: angular-1.3.9/i18n/angular-locale_luo-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_luo.js  
  inflating: angular-1.3.9/i18n/angular-locale_luy-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_luy.js  
  inflating: angular-1.3.9/i18n/angular-locale_lv-lv.js  
  inflating: angular-1.3.9/i18n/angular-locale_lv.js  
  inflating: angular-1.3.9/i18n/angular-locale_mas-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_mas-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_mas.js  
  inflating: angular-1.3.9/i18n/angular-locale_mer-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_mer.js  
  inflating: angular-1.3.9/i18n/angular-locale_mfe-mu.js  
  inflating: angular-1.3.9/i18n/angular-locale_mfe.js  
  inflating: angular-1.3.9/i18n/angular-locale_mg-mg.js  
  inflating: angular-1.3.9/i18n/angular-locale_mg.js  
  inflating: angular-1.3.9/i18n/angular-locale_mgh-mz.js  
  inflating: angular-1.3.9/i18n/angular-locale_mgh.js  
  inflating: angular-1.3.9/i18n/angular-locale_mgo-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_mgo.js  
  inflating: angular-1.3.9/i18n/angular-locale_mk-mk.js  
  inflating: angular-1.3.9/i18n/angular-locale_mk.js  
  inflating: angular-1.3.9/i18n/angular-locale_ml-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_ml.js  
  inflating: angular-1.3.9/i18n/angular-locale_mn-cyrl-mn.js  
  inflating: angular-1.3.9/i18n/angular-locale_mn-cyrl.js  
  inflating: angular-1.3.9/i18n/angular-locale_mn.js  
  inflating: angular-1.3.9/i18n/angular-locale_mr-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_mr.js  
  inflating: angular-1.3.9/i18n/angular-locale_ms-latn-bn.js  
  inflating: angular-1.3.9/i18n/angular-locale_ms-latn-my.js  
  inflating: angular-1.3.9/i18n/angular-locale_ms-latn-sg.js  
  inflating: angular-1.3.9/i18n/angular-locale_ms-latn.js  
  inflating: angular-1.3.9/i18n/angular-locale_ms.js  
  inflating: angular-1.3.9/i18n/angular-locale_mt-mt.js  
  inflating: angular-1.3.9/i18n/angular-locale_mt.js  
  inflating: angular-1.3.9/i18n/angular-locale_mua-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_mua.js  
  inflating: angular-1.3.9/i18n/angular-locale_my-mm.js  
  inflating: angular-1.3.9/i18n/angular-locale_my.js  
  inflating: angular-1.3.9/i18n/angular-locale_naq-na.js  
  inflating: angular-1.3.9/i18n/angular-locale_naq.js  
  inflating: angular-1.3.9/i18n/angular-locale_nb-no.js  
  inflating: angular-1.3.9/i18n/angular-locale_nb-sj.js  
  inflating: angular-1.3.9/i18n/angular-locale_nb.js  
  inflating: angular-1.3.9/i18n/angular-locale_nd-zw.js  
  inflating: angular-1.3.9/i18n/angular-locale_nd.js  
  inflating: angular-1.3.9/i18n/angular-locale_ne-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_ne-np.js  
  inflating: angular-1.3.9/i18n/angular-locale_ne.js  
  inflating: angular-1.3.9/i18n/angular-locale_nl-aw.js  
  inflating: angular-1.3.9/i18n/angular-locale_nl-be.js  
  inflating: angular-1.3.9/i18n/angular-locale_nl-bq.js  
  inflating: angular-1.3.9/i18n/angular-locale_nl-cw.js  
  inflating: angular-1.3.9/i18n/angular-locale_nl-nl.js  
  inflating: angular-1.3.9/i18n/angular-locale_nl-sr.js  
  inflating: angular-1.3.9/i18n/angular-locale_nl-sx.js  
  inflating: angular-1.3.9/i18n/angular-locale_nl.js  
  inflating: angular-1.3.9/i18n/angular-locale_nmg-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_nmg.js  
  inflating: angular-1.3.9/i18n/angular-locale_nn-no.js  
  inflating: angular-1.3.9/i18n/angular-locale_nn.js  
  inflating: angular-1.3.9/i18n/angular-locale_nnh-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_nnh.js  
  inflating: angular-1.3.9/i18n/angular-locale_no-no.js  
  inflating: angular-1.3.9/i18n/angular-locale_no.js  
  inflating: angular-1.3.9/i18n/angular-locale_nr-za.js  
  inflating: angular-1.3.9/i18n/angular-locale_nr.js  
  inflating: angular-1.3.9/i18n/angular-locale_nso-za.js  
  inflating: angular-1.3.9/i18n/angular-locale_nso.js  
  inflating: angular-1.3.9/i18n/angular-locale_nus-sd.js  
  inflating: angular-1.3.9/i18n/angular-locale_nus.js  
  inflating: angular-1.3.9/i18n/angular-locale_nyn-ug.js  
  inflating: angular-1.3.9/i18n/angular-locale_nyn.js  
  inflating: angular-1.3.9/i18n/angular-locale_om-et.js  
  inflating: angular-1.3.9/i18n/angular-locale_om-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_om.js  
  inflating: angular-1.3.9/i18n/angular-locale_or-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_or.js  
  inflating: angular-1.3.9/i18n/angular-locale_os-ge.js  
  inflating: angular-1.3.9/i18n/angular-locale_os-ru.js  
  inflating: angular-1.3.9/i18n/angular-locale_os.js  
  inflating: angular-1.3.9/i18n/angular-locale_pa-arab-pk.js  
  inflating: angular-1.3.9/i18n/angular-locale_pa-arab.js  
  inflating: angular-1.3.9/i18n/angular-locale_pa-guru-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_pa-guru.js  
  inflating: angular-1.3.9/i18n/angular-locale_pa.js  
  inflating: angular-1.3.9/i18n/angular-locale_pl-pl.js  
  inflating: angular-1.3.9/i18n/angular-locale_pl.js  
  inflating: angular-1.3.9/i18n/angular-locale_ps-af.js  
  inflating: angular-1.3.9/i18n/angular-locale_ps.js  
  inflating: angular-1.3.9/i18n/angular-locale_pt-ao.js  
  inflating: angular-1.3.9/i18n/angular-locale_pt-br.js  
  inflating: angular-1.3.9/i18n/angular-locale_pt-cv.js  
  inflating: angular-1.3.9/i18n/angular-locale_pt-gw.js  
  inflating: angular-1.3.9/i18n/angular-locale_pt-mo.js  
  inflating: angular-1.3.9/i18n/angular-locale_pt-mz.js  
  inflating: angular-1.3.9/i18n/angular-locale_pt-pt.js  
  inflating: angular-1.3.9/i18n/angular-locale_pt-st.js  
  inflating: angular-1.3.9/i18n/angular-locale_pt-tl.js  
  inflating: angular-1.3.9/i18n/angular-locale_pt.js  
  inflating: angular-1.3.9/i18n/angular-locale_qu-bo.js  
  inflating: angular-1.3.9/i18n/angular-locale_qu-ec.js  
  inflating: angular-1.3.9/i18n/angular-locale_qu-pe.js  
  inflating: angular-1.3.9/i18n/angular-locale_qu.js  
  inflating: angular-1.3.9/i18n/angular-locale_rm-ch.js  
  inflating: angular-1.3.9/i18n/angular-locale_rm.js  
  inflating: angular-1.3.9/i18n/angular-locale_rn-bi.js  
  inflating: angular-1.3.9/i18n/angular-locale_rn.js  
  inflating: angular-1.3.9/i18n/angular-locale_ro-md.js  
  inflating: angular-1.3.9/i18n/angular-locale_ro-ro.js  
  inflating: angular-1.3.9/i18n/angular-locale_ro.js  
  inflating: angular-1.3.9/i18n/angular-locale_rof-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_rof.js  
  inflating: angular-1.3.9/i18n/angular-locale_ru-by.js  
  inflating: angular-1.3.9/i18n/angular-locale_ru-kg.js  
  inflating: angular-1.3.9/i18n/angular-locale_ru-kz.js  
  inflating: angular-1.3.9/i18n/angular-locale_ru-md.js  
  inflating: angular-1.3.9/i18n/angular-locale_ru-ru.js  
  inflating: angular-1.3.9/i18n/angular-locale_ru-ua.js  
  inflating: angular-1.3.9/i18n/angular-locale_ru.js  
  inflating: angular-1.3.9/i18n/angular-locale_rw-rw.js  
  inflating: angular-1.3.9/i18n/angular-locale_rw.js  
  inflating: angular-1.3.9/i18n/angular-locale_rwk-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_rwk.js  
  inflating: angular-1.3.9/i18n/angular-locale_sah-ru.js  
  inflating: angular-1.3.9/i18n/angular-locale_sah.js  
  inflating: angular-1.3.9/i18n/angular-locale_saq-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_saq.js  
  inflating: angular-1.3.9/i18n/angular-locale_sbp-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_sbp.js  
  inflating: angular-1.3.9/i18n/angular-locale_se-fi.js  
  inflating: angular-1.3.9/i18n/angular-locale_se-no.js  
  inflating: angular-1.3.9/i18n/angular-locale_se-se.js  
  inflating: angular-1.3.9/i18n/angular-locale_se.js  
  inflating: angular-1.3.9/i18n/angular-locale_seh-mz.js  
  inflating: angular-1.3.9/i18n/angular-locale_seh.js  
  inflating: angular-1.3.9/i18n/angular-locale_ses-ml.js  
  inflating: angular-1.3.9/i18n/angular-locale_ses.js  
  inflating: angular-1.3.9/i18n/angular-locale_sg-cf.js  
  inflating: angular-1.3.9/i18n/angular-locale_sg.js  
  inflating: angular-1.3.9/i18n/angular-locale_shi-latn-ma.js  
  inflating: angular-1.3.9/i18n/angular-locale_shi-latn.js  
  inflating: angular-1.3.9/i18n/angular-locale_shi-tfng-ma.js  
  inflating: angular-1.3.9/i18n/angular-locale_shi-tfng.js  
  inflating: angular-1.3.9/i18n/angular-locale_shi.js  
  inflating: angular-1.3.9/i18n/angular-locale_si-lk.js  
  inflating: angular-1.3.9/i18n/angular-locale_si.js  
  inflating: angular-1.3.9/i18n/angular-locale_sk-sk.js  
  inflating: angular-1.3.9/i18n/angular-locale_sk.js  
  inflating: angular-1.3.9/i18n/angular-locale_sl-si.js  
  inflating: angular-1.3.9/i18n/angular-locale_sl.js  
  inflating: angular-1.3.9/i18n/angular-locale_smn-fi.js  
  inflating: angular-1.3.9/i18n/angular-locale_smn.js  
  inflating: angular-1.3.9/i18n/angular-locale_sn-zw.js  
  inflating: angular-1.3.9/i18n/angular-locale_sn.js  
  inflating: angular-1.3.9/i18n/angular-locale_so-dj.js  
  inflating: angular-1.3.9/i18n/angular-locale_so-et.js  
  inflating: angular-1.3.9/i18n/angular-locale_so-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_so-so.js  
  inflating: angular-1.3.9/i18n/angular-locale_so.js  
  inflating: angular-1.3.9/i18n/angular-locale_sq-al.js  
  inflating: angular-1.3.9/i18n/angular-locale_sq-mk.js  
  inflating: angular-1.3.9/i18n/angular-locale_sq-xk.js  
  inflating: angular-1.3.9/i18n/angular-locale_sq.js  
  inflating: angular-1.3.9/i18n/angular-locale_sr-cyrl-ba.js  
  inflating: angular-1.3.9/i18n/angular-locale_sr-cyrl-me.js  
  inflating: angular-1.3.9/i18n/angular-locale_sr-cyrl-rs.js  
  inflating: angular-1.3.9/i18n/angular-locale_sr-cyrl-xk.js  
  inflating: angular-1.3.9/i18n/angular-locale_sr-cyrl.js  
  inflating: angular-1.3.9/i18n/angular-locale_sr-latn-ba.js  
  inflating: angular-1.3.9/i18n/angular-locale_sr-latn-me.js  
  inflating: angular-1.3.9/i18n/angular-locale_sr-latn-rs.js  
  inflating: angular-1.3.9/i18n/angular-locale_sr-latn-xk.js  
  inflating: angular-1.3.9/i18n/angular-locale_sr-latn.js  
  inflating: angular-1.3.9/i18n/angular-locale_sr.js  
  inflating: angular-1.3.9/i18n/angular-locale_ss-sz.js  
  inflating: angular-1.3.9/i18n/angular-locale_ss-za.js  
  inflating: angular-1.3.9/i18n/angular-locale_ss.js  
  inflating: angular-1.3.9/i18n/angular-locale_ssy-er.js  
  inflating: angular-1.3.9/i18n/angular-locale_ssy.js  
  inflating: angular-1.3.9/i18n/angular-locale_st-ls.js  
  inflating: angular-1.3.9/i18n/angular-locale_st-za.js  
  inflating: angular-1.3.9/i18n/angular-locale_st.js  
  inflating: angular-1.3.9/i18n/angular-locale_sv-ax.js  
  inflating: angular-1.3.9/i18n/angular-locale_sv-fi.js  
  inflating: angular-1.3.9/i18n/angular-locale_sv-se.js  
  inflating: angular-1.3.9/i18n/angular-locale_sv.js  
  inflating: angular-1.3.9/i18n/angular-locale_sw-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_sw-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_sw-ug.js  
  inflating: angular-1.3.9/i18n/angular-locale_sw.js  
  inflating: angular-1.3.9/i18n/angular-locale_swc-cd.js  
  inflating: angular-1.3.9/i18n/angular-locale_swc.js  
  inflating: angular-1.3.9/i18n/angular-locale_ta-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_ta-lk.js  
  inflating: angular-1.3.9/i18n/angular-locale_ta-my.js  
  inflating: angular-1.3.9/i18n/angular-locale_ta-sg.js  
  inflating: angular-1.3.9/i18n/angular-locale_ta.js  
  inflating: angular-1.3.9/i18n/angular-locale_te-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_te.js  
  inflating: angular-1.3.9/i18n/angular-locale_teo-ke.js  
  inflating: angular-1.3.9/i18n/angular-locale_teo-ug.js  
  inflating: angular-1.3.9/i18n/angular-locale_teo.js  
  inflating: angular-1.3.9/i18n/angular-locale_tg-cyrl-tj.js  
  inflating: angular-1.3.9/i18n/angular-locale_tg-cyrl.js  
  inflating: angular-1.3.9/i18n/angular-locale_tg.js  
  inflating: angular-1.3.9/i18n/angular-locale_th-th.js  
  inflating: angular-1.3.9/i18n/angular-locale_th.js  
  inflating: angular-1.3.9/i18n/angular-locale_ti-er.js  
  inflating: angular-1.3.9/i18n/angular-locale_ti-et.js  
  inflating: angular-1.3.9/i18n/angular-locale_ti.js  
  inflating: angular-1.3.9/i18n/angular-locale_tig-er.js  
  inflating: angular-1.3.9/i18n/angular-locale_tig.js  
  inflating: angular-1.3.9/i18n/angular-locale_tl.js  
  inflating: angular-1.3.9/i18n/angular-locale_tn-bw.js  
  inflating: angular-1.3.9/i18n/angular-locale_tn-za.js  
  inflating: angular-1.3.9/i18n/angular-locale_tn.js  
  inflating: angular-1.3.9/i18n/angular-locale_to-to.js  
  inflating: angular-1.3.9/i18n/angular-locale_to.js  
  inflating: angular-1.3.9/i18n/angular-locale_tr-cy.js  
  inflating: angular-1.3.9/i18n/angular-locale_tr-tr.js  
  inflating: angular-1.3.9/i18n/angular-locale_tr.js  
  inflating: angular-1.3.9/i18n/angular-locale_ts-za.js  
  inflating: angular-1.3.9/i18n/angular-locale_ts.js  
  inflating: angular-1.3.9/i18n/angular-locale_twq-ne.js  
  inflating: angular-1.3.9/i18n/angular-locale_twq.js  
  inflating: angular-1.3.9/i18n/angular-locale_tzm-latn-ma.js  
  inflating: angular-1.3.9/i18n/angular-locale_tzm-latn.js  
  inflating: angular-1.3.9/i18n/angular-locale_tzm.js  
  inflating: angular-1.3.9/i18n/angular-locale_ug-arab-cn.js  
  inflating: angular-1.3.9/i18n/angular-locale_ug-arab.js  
  inflating: angular-1.3.9/i18n/angular-locale_ug.js  
  inflating: angular-1.3.9/i18n/angular-locale_uk-ua.js  
  inflating: angular-1.3.9/i18n/angular-locale_uk.js  
  inflating: angular-1.3.9/i18n/angular-locale_ur-in.js  
  inflating: angular-1.3.9/i18n/angular-locale_ur-pk.js  
  inflating: angular-1.3.9/i18n/angular-locale_ur.js  
  inflating: angular-1.3.9/i18n/angular-locale_uz-arab-af.js  
  inflating: angular-1.3.9/i18n/angular-locale_uz-arab.js  
  inflating: angular-1.3.9/i18n/angular-locale_uz-cyrl-uz.js  
  inflating: angular-1.3.9/i18n/angular-locale_uz-cyrl.js  
  inflating: angular-1.3.9/i18n/angular-locale_uz-latn-uz.js  
  inflating: angular-1.3.9/i18n/angular-locale_uz-latn.js  
  inflating: angular-1.3.9/i18n/angular-locale_uz.js  
  inflating: angular-1.3.9/i18n/angular-locale_vai-latn-lr.js  
  inflating: angular-1.3.9/i18n/angular-locale_vai-latn.js  
  inflating: angular-1.3.9/i18n/angular-locale_vai-vaii-lr.js  
  inflating: angular-1.3.9/i18n/angular-locale_vai-vaii.js  
  inflating: angular-1.3.9/i18n/angular-locale_vai.js  
  inflating: angular-1.3.9/i18n/angular-locale_ve-za.js  
  inflating: angular-1.3.9/i18n/angular-locale_ve.js  
  inflating: angular-1.3.9/i18n/angular-locale_vi-vn.js  
  inflating: angular-1.3.9/i18n/angular-locale_vi.js  
  inflating: angular-1.3.9/i18n/angular-locale_vo-001.js  
  inflating: angular-1.3.9/i18n/angular-locale_vo.js  
  inflating: angular-1.3.9/i18n/angular-locale_vun-tz.js  
  inflating: angular-1.3.9/i18n/angular-locale_vun.js  
  inflating: angular-1.3.9/i18n/angular-locale_wae-ch.js  
  inflating: angular-1.3.9/i18n/angular-locale_wae.js  
  inflating: angular-1.3.9/i18n/angular-locale_wal-et.js  
  inflating: angular-1.3.9/i18n/angular-locale_wal.js  
  inflating: angular-1.3.9/i18n/angular-locale_xh-za.js  
  inflating: angular-1.3.9/i18n/angular-locale_xh.js  
  inflating: angular-1.3.9/i18n/angular-locale_xog-ug.js  
  inflating: angular-1.3.9/i18n/angular-locale_xog.js  
  inflating: angular-1.3.9/i18n/angular-locale_yav-cm.js  
  inflating: angular-1.3.9/i18n/angular-locale_yav.js  
  inflating: angular-1.3.9/i18n/angular-locale_yi-001.js  
  inflating: angular-1.3.9/i18n/angular-locale_yi.js  
  inflating: angular-1.3.9/i18n/angular-locale_yo-bj.js  
  inflating: angular-1.3.9/i18n/angular-locale_yo-ng.js  
  inflating: angular-1.3.9/i18n/angular-locale_yo.js  
  inflating: angular-1.3.9/i18n/angular-locale_zgh-ma.js  
  inflating: angular-1.3.9/i18n/angular-locale_zgh.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh-cn.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh-hans-cn.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh-hans-hk.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh-hans-mo.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh-hans-sg.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh-hans.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh-hant-hk.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh-hant-mo.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh-hant-tw.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh-hant.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh-hk.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh-tw.js  
  inflating: angular-1.3.9/i18n/angular-locale_zh.js  
  inflating: angular-1.3.9/i18n/angular-locale_zu-za.js  
  inflating: angular-1.3.9/i18n/angular-locale_zu.js  
   creating: angular-1.3.9/i18n/ngLocale/
  inflating: angular-1.3.9/version.json  
  inflating: angular-1.3.9/version.txt  
(cd angularjs && unzip -u ui-utils-0.2.1.zip)
Archive:  ui-utils-0.2.1.zip
8df0fcf665a8f14949e189c8d6e2e0204a858b06
   creating: ui-utils-0.2.1/
  inflating: ui-utils-0.2.1/.travis.yml  
  inflating: ui-utils-0.2.1/CHANGELOG.md  
  inflating: ui-utils-0.2.1/bower.json  
  inflating: ui-utils-0.2.1/ui-utils-ieshiv.js  
  inflating: ui-utils-0.2.1/ui-utils-ieshiv.min.js  
  inflating: ui-utils-0.2.1/ui-utils.js  
  inflating: ui-utils-0.2.1/ui-utils.min.js  
if [ ! -d bootstrap-3.3.0 ] ; then mkdir -p bootstrap-3.3.0 && ( cd bootstrap-3.3.0 && unzip -u ../bootstrap-3.3.0-dist.zip && mv dist/* . && rmdir dist ) ; fi
Archive:  ../bootstrap-3.3.0-dist.zip
   creating: dist/
   creating: dist/css/
  inflating: dist/css/bootstrap-theme.css  
  inflating: dist/css/bootstrap-theme.css.map  
  inflating: dist/css/bootstrap-theme.min.css  
  inflating: dist/css/bootstrap.css  
  inflating: dist/css/bootstrap.css.map  
  inflating: dist/css/bootstrap.min.css  
   creating: dist/fonts/
  inflating: dist/fonts/glyphicons-halflings-regular.eot  
  inflating: dist/fonts/glyphicons-halflings-regular.svg  
  inflating: dist/fonts/glyphicons-halflings-regular.ttf  
  inflating: dist/fonts/glyphicons-halflings-regular.woff  
   creating: dist/js/
  inflating: dist/js/bootstrap.js    
  inflating: dist/js/bootstrap.min.js  
  inflating: dist/js/npm.js          
mkdir -p d3
(cd d3 && unzip -u ../d3-3.5.3.zip)
Archive:  ../d3-3.5.3.zip
  inflating: LICENSE                 
  inflating: d3.js                   
  inflating: d3.min.js               
make[1]: Leaving directory `/tmp/nagioscore/html'
if [ xyes = xyes ]; then \
		cd ./module && make; \
	fi
make[1]: Entering directory `/tmp/nagioscore/module'
gcc -I.. -fPIC -g -O2 -DHAVE_CONFIG_H -o helloworld.o helloworld.c -shared  
make[1]: Leaving directory `/tmp/nagioscore/module'
cd ./worker && make all
make[1]: Entering directory `/tmp/nagioscore/worker'
cd ./ping && make all
make[2]: Entering directory `/tmp/nagioscore/worker/ping'
gcc -I.. -I ../../include -I ../.. -g -O2 -DHAVE_CONFIG_H -o worker-ping worker-ping.c -L ../../lib -l nagios  
make[2]: Leaving directory `/tmp/nagioscore/worker/ping'
make[1]: Leaving directory `/tmp/nagioscore/worker'

*** Compile finished ***

If the main program and CGIs compiled without any errors, you
can continue with installing Nagios as follows (type 'make'
without any arguments for a list of all possible options):

  make install
     - This installs the main program, CGIs, and HTML files

  make install-init
     - This installs the init script in /etc/init

  make install-commandmode
     - This installs and configures permissions on the
       directory for holding the external command file

  make install-config
     - This installs *SAMPLE* config files in /usr/local/nagios/etc
       You'll have to modify these sample files before you can
       use Nagios.  Read the HTML documentation for more info
       on doing this.  Pay particular attention to the docs on
       object configuration files, as they determine what/how
       things get monitored!

  make install-webconf
     - This installs the Apache config file for the Nagios
       web interface

  make install-exfoliation
     - This installs the Exfoliation theme for the Nagios
       web interface

  make install-classicui
     - This installs the classic theme for the Nagios
       web interface


*** Support Notes *******************************************

If you have questions about configuring or running Nagios,
please make sure that you:

     - Look at the sample config files
     - Read the documentation on the Nagios Library at:
           https://library.nagios.com

before you post a question to one of the mailing lists.
Also make sure to include pertinent information that could
help others help you.  This might include:

     - What version of Nagios you are using
     - What version of the plugins you are using
     - Relevant snippets from your config files
     - Relevant error messages from the Nagios log file

For more information on obtaining support for Nagios, visit:

       https://support.nagios.com

*************************************************************

Enjoy.

[root@core-014 nagioscore]# useradd nagios
[root@core-014 nagioscore]# usermod -a -G nagios apache
[root@core-014 nagioscore]# 
[root@core-014 nagioscore]# make install
cd ./base && make install
make[1]: Entering directory `/tmp/nagioscore/base'
make install-basic
make[2]: Entering directory `/tmp/nagioscore/base'
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/bin
/usr/bin/install -c -m 774 -o nagios -g nagios nagios /usr/local/nagios/bin
/usr/bin/install -c -m 774 -o nagios -g nagios nagiostats /usr/local/nagios/bin
make[2]: Leaving directory `/tmp/nagioscore/base'
make strip-post-install
make[2]: Entering directory `/tmp/nagioscore/base'
/usr/bin/strip /usr/local/nagios/bin/nagios
/usr/bin/strip /usr/local/nagios/bin/nagiostats
make[2]: Leaving directory `/tmp/nagioscore/base'
make[1]: Leaving directory `/tmp/nagioscore/base'
cd ./cgi && make install
make[1]: Entering directory `/tmp/nagioscore/cgi'
make install-basic
make[2]: Entering directory `/tmp/nagioscore/cgi'
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/bin
for file in *.cgi; do \
		/usr/bin/install -c -m 775 -o nagios -g nagios $file /usr/local/nagios/bin; \
	done
make[2]: Leaving directory `/tmp/nagioscore/cgi'
make strip-post-install
make[2]: Entering directory `/tmp/nagioscore/cgi'
for file in *.cgi; do \
		/usr/bin/strip /usr/local/nagios/bin/$file; \
	done
make[2]: Leaving directory `/tmp/nagioscore/cgi'
make[1]: Leaving directory `/tmp/nagioscore/cgi'
cd ./html && make install
make[1]: Entering directory `/tmp/nagioscore/html'
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/media
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/stylesheets
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/contexthelp
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/docs
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/docs/images
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/js
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/images
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/images/logos
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/includes
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/ssi
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/angularjs
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/angularjs/angular-1.3.9
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/angularjs/ui-utils-0.2.1
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/bootstrap-3.3.0
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/bootstrap-3.3.0/css
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/d3
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/share/spin
/usr/bin/install -c -m 664 -o nagios -g nagios robots.txt /usr/local/nagios/share
rm -f /usr/local/nagios/share/index.html
rm -f /usr/local/nagios/share/main.html
rm -f /usr/local/nagios/share/side.html
rm -f /usr/local/nagios/share/map.html
rm -f /usr/local/nagios/share/rss-*
rm -rf /usr/local/nagios/share/include/rss
/usr/bin/install -c -m 664 -o nagios -g nagios jsonquery.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios graph-header.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios histogram.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios histogram-form.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios histogram-graph.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios histogram-links.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios infobox.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios map.php /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios map-directive.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios map-form.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios map-links.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios map-popup.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios trends.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios trends-form.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios trends-graph.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios trends-host-yaxis.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios trends-links.html /usr/local/nagios/share
/usr/bin/install -c -m 664 -o nagios -g nagios trends-service-yaxis.html /usr/local/nagios/share
for file in *.php; \
	do /usr/bin/install -c -m 664 -o nagios -g nagios $file /usr/local/nagios/share; done
for file in stylesheets/*.css; \
	do /usr/bin/install -c -m 664 -o nagios -g nagios $file /usr/local/nagios/share/stylesheets; done
for file in contexthelp/*.html; \
	do /usr/bin/install -c -m 664 -o nagios -g nagios $file /usr/local/nagios/share/contexthelp; done
for file in js/*.js; \
	do /usr/bin/install -c -m 664 -o nagios -g nagios $file /usr/local/nagios/share/js; done
for file in images/*.gif; \
	do /usr/bin/install -c -m 664 -o nagios -g nagios $file /usr/local/nagios/share/images; done
for file in images/*.jpg; \
	do /usr/bin/install -c -m 664 -o nagios -g nagios $file /usr/local/nagios/share/images; done
for file in images/*.png; \
	do /usr/bin/install -c -m 664 -o nagios -g nagios $file /usr/local/nagios/share/images; done
for file in images/*.ico; \
	do /usr/bin/install -c -m 664 -o nagios -g nagios $file /usr/local/nagios/share/images; done
for file in images/logos/*.*; \
	do /usr/bin/install -c -m 664 -o nagios -g nagios $file /usr/local/nagios/share/images/logos; done
for file in includes/*.*; \
	do /usr/bin/install -c -m 664 -o nagios -g nagios $file /usr/local/nagios/share/includes; done
/usr/bin/install -c -m 664 -o nagios -g nagios angularjs/angular-1.3.9/angular.min.js  /usr/local/nagios/share/angularjs/angular-1.3.9
/usr/bin/install -c -m 664 -o nagios -g nagios angularjs/angular-1.3.9/angular.min.js.map  /usr/local/nagios/share/angularjs/angular-1.3.9
/usr/bin/install -c -m 664 -o nagios -g nagios angularjs/ui-bootstrap-tpls-0.12.0.min.js  /usr/local/nagios/share/angularjs
/usr/bin/install -c -m 664 -o nagios -g nagios angularjs/ui-utils-0.2.1/ui-utils.js   /usr/local/nagios/share/angularjs/ui-utils-0.2.1
/usr/bin/install -c -m 664 -o nagios -g nagios bootstrap-3.3.0/css/bootstrap.min.css /usr/local/nagios/share/bootstrap-3.3.0/css
/usr/bin/install -c -m 664 -o nagios -g nagios bootstrap-3.3.0/css/bootstrap-theme.min.css /usr/local/nagios/share/bootstrap-3.3.0/css
/usr/bin/install -c -m 664 -o nagios -g nagios d3/d3.min.js /usr/local/nagios/share/d3
/usr/bin/install -c -m 664 -o nagios -g nagios spin/spin.min.js /usr/local/nagios/share/spin
make[1]: Leaving directory `/tmp/nagioscore/html'
make install-exfoliation
make[1]: Entering directory `/tmp/nagioscore'

*** Exfoliation theme installed ***
NOTE: Use 'make install-classicui' to revert to classic Nagios theme

make[1]: Leaving directory `/tmp/nagioscore'
make install-basic
make[1]: Entering directory `/tmp/nagioscore'
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/libexec
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/var
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/var/archives
/usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/var/spool/checkresults
chmod g+s /usr/local/nagios/var/spool/checkresults

*** Main program, CGIs and HTML files installed ***

You can continue with installing Nagios as follows (type 'make'
without any arguments for a list of all possible options):

  make install-init
     - This installs the init script in /etc/init

  make install-commandmode
     - This installs and configures permissions on the
       directory for holding the external command file

  make install-config
     - This installs sample config files in /usr/local/nagios/etc

make[1]: Leaving directory `/tmp/nagioscore'
[root@core-014 nagioscore]# make install-init
/usr/bin/install -c -m 755 -o root -g root startup/rh-upstart-init /etc/init/nagios.conf
/usr/bin/install: cannot stat `startup/rh-upstart-init': No such file or directory
make: *** [install-daemoninit] Error 1
```",0,nagios core     alpha   make install init error   i tried installing the latest build of     and i get the following error             make install init   usr bin install  c  m    o root  g root startup rh upstart init  etc init nagios conf   usr bin install  cannot stat  startup rh upstart init   no such file or directory  make        error           this is on centos release      final        this is a fresh build of the os  it has not had nagios installed on it before     full log           cd  tmp     ls  la  total    drwxrwxrwt     root root       jan          dr xr xr x    root root       jan           drwxrwxrwt     root root       jan        ice unix   rw r  r       root root   jan       nagioscore     aplha tar gz  drwxr xr x     root root       jun      vmware    drwxr xr x     root root       jun      vmware    drwx           root root       jan       vmware root  drwxr xr x     root root       sep       vmware tools distrib   rw            root root          jun      yum log     tar xzf nagioscore     aplha tar gz      cd nagioscore       configure   checking for a bsd compatible install     usr bin install  c  checking build system type        pc linux gnu  checking host system type        pc linux gnu  checking for gcc    gcc  checking whether the c compiler works    yes  checking for c compiler default output file name    a out  checking for suffix of executables      checking whether we are cross compiling    no  checking for suffix of object files    o  checking whether we are using the gnu c compiler    yes  checking whether gcc accepts  g    yes  checking for gcc option to accept iso      none needed  checking whether make sets   make     yes  checking whether ln  s works    yes  checking for strip     usr bin strip  checking how to run the c preprocessor    gcc  e  checking for grep that handles long lines and  e     bin grep  checking for egrep     bin grep  e  checking for ansi c header files    yes  checking whether time h and sys time h may both be included    yes  checking for sys wait h that is posix   compatible    yes  checking for sys types h    yes  checking for sys stat h    yes  checking for stdlib h    yes  checking for string h    yes  checking for memory h    yes  checking for strings h    yes  checking for inttypes h    yes  checking for stdint h    yes  checking for unistd h    yes  checking arpa inet h usability    yes  checking arpa inet h presence    yes  checking for arpa inet h    yes  checking ctype h usability    yes  checking ctype h presence    yes  checking for ctype h    yes  checking dirent h usability    yes  checking dirent h presence    yes  checking for dirent h    yes  checking errno h usability    yes  checking errno h presence    yes  checking for errno h    yes  checking fcntl h usability    yes  checking fcntl h presence    yes  checking for fcntl h    yes  checking getopt h usability    yes  checking getopt h presence    yes  checking for getopt h    yes  checking grp h usability    yes  checking grp h presence    yes  checking for grp h    yes  checking libgen h usability    yes  checking libgen h presence    yes  checking for libgen h    yes  checking limits h usability    yes  checking limits h presence    yes  checking for limits h    yes  checking math h usability    yes  checking math h presence    yes  checking for math h    yes  checking netdb h usability    yes  checking netdb h presence    yes  checking for netdb h    yes  checking netinet in h usability    yes  checking netinet in h presence    yes  checking for netinet in h    yes  checking pwd h usability    yes  checking pwd h presence    yes  checking for pwd h    yes  checking regex h usability    yes  checking regex h presence    yes  checking for regex h    yes  checking signal h usability    yes  checking signal h presence    yes  checking for signal h    yes  checking socket h usability    no  checking socket h presence    no  checking for socket h    no  checking stdarg h usability    yes  checking stdarg h presence    yes  checking for stdarg h    yes  checking for string h     cached  yes  checking for strings h     cached  yes  checking sys loadavg h usability    no  checking sys loadavg h presence    no  checking for sys loadavg h    no  checking sys mman h usability    yes  checking sys mman h presence    yes  checking for sys mman h    yes  checking for sys types h     cached  yes  checking sys time h usability    yes  checking sys time h presence    yes  checking for sys time h    yes  checking sys resource h usability    yes  checking sys resource h presence    yes  checking for sys resource h    yes  checking for sys wait h     cached  yes  checking sys socket h usability    yes  checking sys socket h presence    yes  checking for sys socket h    yes  checking for sys stat h     cached  yes  checking sys timeb h usability    yes  checking sys timeb h presence    yes  checking for sys timeb h    yes  checking sys un h usability    yes  checking sys un h presence    yes  checking for sys un h    yes  checking sys ipc h usability    yes  checking sys ipc h presence    yes  checking for sys ipc h    yes  checking sys msg h usability    yes  checking sys msg h presence    yes  checking for sys msg h    yes  checking sys poll h usability    yes  checking sys poll h presence    yes  checking for sys poll h    yes  checking syslog h usability    yes  checking syslog h presence    yes  checking for syslog h    yes  checking uio h usability    no  checking uio h presence    no  checking for uio h    no  checking for unistd h     cached  yes  checking locale h usability    yes  checking locale h presence    yes  checking for locale h    yes  checking wchar h usability    yes  checking wchar h presence    yes  checking for wchar h    yes  checking sys prctl h usability    yes  checking sys prctl h presence    yes  checking for sys prctl h    yes  checking for an ansi c conforming const    yes  checking whether struct tm is in sys time h or time h    time h  checking for struct tm tm zone    yes  checking for mode t    yes  checking for pid t    yes  checking for size t    yes  checking return type of signal handlers    void  checking for uid t in sys types h    yes  checking type of array argument to getgroups    gid t  checking what the operating system is     linux  checking what the distribution type is     rh  checking what init system is being used     upstart  checking what inetd is being used     upstart  checking for which paths to use     default  checking for which init file to use     rh upstart init  checking for which inetd files to use     unknown  checking for va copy    yes  checking for vsnprintf    yes  checking for snprintf    yes  checking for asprintf    yes  checking for vasprintf    yes  checking for sigaction    yes  checking for   vsnprintf    yes  checking for library containing getservbyname    none required  checking for library containing connect    none required  checking for initgroups    yes  checking for setenv    yes  checking for strdup    yes  checking for strstr    yes  checking for strtoul    yes  checking for unsetenv    yes  checking for type of socket size    size t  checking for library containing nanosleep    none required  checking for mail    no  which  no mail in   usr local sbin  usr local bin  sbin  bin  usr sbin  usr bin  root bin   checking for glibc at least version        yes  checking sys epoll h usability    yes  checking sys epoll h presence    yes  checking for sys epoll h    yes  checking sys select h usability    yes  checking sys select h presence    yes  checking for sys select h    yes    configure  line    dnls  command not found  checking for main in  liconv    no  checking for gdimagepng in  lgd  order       no  checking for gdimagepng in  lgd  order       yes  gd library was found   checking for gdimagecreatetruecolor in  lgd    yes  checking ltdl h usability    no  checking ltdl h presence    no  checking for ltdl h    no  checking dlfcn h usability    yes  checking dlfcn h presence    yes  checking for dlfcn h    yes  checking for dlopen in  ldl    yes  checking for extra flags needed to export symbols      wl  export dynamic  checking for linker flags for loadable modules     shared  checking for traceroute    no  checking for type va list    yes  checking for perl     usr bin perl  checking for unzip     usr bin unzip  configure  creating   config status  config status  creating html index php  config status  creating makefile  config status  creating lib makefile  config status  creating base makefile  config status  creating common makefile  config status  creating contrib makefile  config status  creating cgi makefile  config status  creating html makefile  config status  creating module makefile  config status  creating worker makefile  config status  creating worker ping makefile  config status  creating xdata makefile  config status  creating subst  config status  creating pkginfo  config status  creating startup openrc init  config status  creating startup default init  config status  creating startup default service  config status  creating startup upstart init  config status  creating t makefile  config status  creating t tap makefile  config status  creating include config h  config status  creating lib snprintf h  config status  creating lib iobroker h    creating sample config files in sample config               configuration summary for nagios                        general options                                       nagios executable   nagios          nagios user group   nagios nagios         command user group   nagios nagios               event broker   yes          install   prefix     usr local nagios      install   includedir     usr local nagios include nagios                  lock file   n a     check result directory    usr local nagios var spool checkresults             init directory    etc init    apache conf d directory    etc httpd conf d               mail program    usr sbin sendmail                    host os   linux gnu            iobroker method   epoll     web interface options                                               html url                        cgi url       traceroute  used by wap          review the options above for accuracy   if they look okay   type  make all  to compile the main program and cgis        make all  cd   base    make  make   entering directory   tmp nagioscore base   gcc  wall  i    g     dhave config h  dnscore  c  o nagios o nagios c  gcc  wall  i    g     dhave config h  dnscore    c  o broker o broker c  gcc  wall  i    g     dhave config h  dnscore    c  o nebmods o nebmods c  gcc  wall  i    g     dhave config h  dnscore  c  o    common shared o    common shared c  gcc  wall  i    g     dhave config h  dnscore    c  o query handler o query handler c  gcc  wall  i    g     dhave config h  dnscore  c  o workers o workers c  workers c  in function ‘wproc run job’   workers c    warning  unused variable ‘i’  gcc  wall  i    g     dhave config h  dnscore    c  o checks o checks c  checks c  in function ‘service fresh check’   checks c    warning  ‘return’ with a value  in function returning void  checks c  in function ‘host fresh check’   checks c    warning  ‘return’ with a value  in function returning void  checks c  in function ‘host state or hard state type change’   checks c    warning  passing argument   of ‘delete service acknowledgement comments’ from incompatible pointer type     include comments h    note  expected ‘struct service  ’ but argument is of type ‘struct host  ’  checks c  in function ‘handle async service check result’   checks c    warning  suggest explicit braces to avoid ambiguous ‘else’  checks c  in function ‘handle async host check result’   checks c    warning  suggest explicit braces to avoid ambiguous ‘else’  checks c    warning  suggest parentheses around assignment used as truth value  gcc  wall  i    g     dhave config h  dnscore    c  o config o config c  gcc  wall  i    g     dhave config h  dnscore    c  o commands o commands c  gcc  wall  i    g     dhave config h  dnscore    c  o events o events c  gcc  wall  i    g     dhave config h  dnscore    c  o flapping o flapping c  gcc  wall  i    g     dhave config h  dnscore    c  o logging o logging c  gcc  wall  i    g     dhave config h  dnscore  c  o macros base o    common macros c     common macros c  in function ‘process macros r’      common macros c    warning  suggest parentheses around assignment used as truth value  gcc  wall  i    g     dhave config h  dnscore    c  o netutils o netutils c  gcc  wall  i    g     dhave config h  dnscore    c  o notifications o notifications c  gcc  wall  i    g     dhave config h  dnscore    c  o sehandlers o sehandlers c  gcc  wall  i    g     dhave config h  dnscore    c  o utils o utils c  utils c  in function ‘daemon init’   utils c    warning  implicit declaration of function ‘cleanup performance data’  utils c    warning  implicit declaration of function ‘cleanup downtime data’  utils c  in function ‘process check result file’   utils c    warning  format ‘ d’ expects type ‘int’  but argument   has type ‘time t’  utils c  in function ‘cleanup’   utils c    warning  implicit declaration of function ‘xodtemplate free memory’  utils c  in function ‘rlimit problem detection’   utils c    warning  format ‘ d’ expects type ‘int’  but argument   has type ‘rlim t’  utils c    warning  format ‘ d’ expects type ‘int’  but argument   has type ‘rlim t’  gcc  wall  i    g     dhave config h  dnscore  c  o retention base o sretention c  gcc  wall  i    g     dhave config h  dnscore  c  o xretention base o    xdata xrddefault c  gcc  wall  i    g     dhave config h  dnscore  c  o comments base o    common comments c  gcc  wall  i    g     dhave config h  dnscore  c  o xcomments base o    xdata xcddefault c  gcc  wall  i    g     dhave config h  dnscore  c  o objects base o    common objects c  gcc  wall  i    g     dhave config h  dnscore  c  o xobjects base o    xdata xodtemplate c  gcc  wall  i    g     dhave config h  dnscore  c  o statusdata base o    common statusdata c  gcc  wall  i    g     dhave config h  dnscore  c  o xstatusdata base o    xdata xsddefault c  gcc  wall  i    g     dhave config h  dnscore  c  o perfdata base o perfdata c  gcc  wall  i    g     dhave config h  dnscore  c  o xperfdata base o    xdata xpddefault c  gcc  wall  i    g     dhave config h  dnscore  c  o downtime base o    common downtime c  make  c    lib  make   entering directory   tmp nagioscore lib   gcc  wall  g     dhave config h  c squeue c  o squeue o  gcc  wall  g     dhave config h  c kvvec c  o kvvec o  gcc  wall  g     dhave config h  c iocache c  o iocache o  gcc  wall  g     dhave config h  c iobroker c  o iobroker o  gcc  wall  g     dhave config h  c bitmap c  o bitmap o  gcc  wall  g     dhave config h  c dkhash c  o dkhash o  gcc  wall  g     dhave config h  c runcmd c  o runcmd o  gcc  wall  g     dhave config h  c nsutils c  o nsutils o  gcc  wall  g     dhave config h  c fanout c  o fanout o  gcc  wall  g     dhave config h  c pqueue c  o pqueue o  gcc  wall  g     dhave config h  c worker c  o worker o  gcc  wall  g     dhave config h  c skiplist c  o skiplist o  gcc  wall  g     dhave config h  c nsock c  o nsock o  gcc  wall  g     dhave config h  c nspath c  o nspath o  ar cr libnagios a squeue o kvvec o iocache o iobroker o bitmap o dkhash o runcmd o nsutils o fanout o pqueue o worker o skiplist o nsock o nspath o  make   leaving directory   tmp nagioscore lib   gcc  wall  i    g     dhave config h  dnscore  o nagios nagios o broker o nebmods o    common shared o  query handler o workers o checks o config o commands o events o flapping o logging o macros base o netutils o notifications o sehandlers o utils o retention base o xretention base o comments base o xcomments base o objects base o xobjects base o statusdata base o xstatusdata base o perfdata base o xperfdata base o downtime base o   wl  export dynamic    lm   ldl     lib libnagios a  gcc  wall  i    g     dhave config h  dnscore  o nagiostats nagiostats c   lm     lib libnagios a  make   leaving directory   tmp nagioscore base   cd   cgi    make  make   entering directory   tmp nagioscore cgi   gcc  wall  i    g     dhave config h  dnscgi    c  o getcgi o getcgi c  gcc  wall  i    g     dhave config h  dnscgi    c  o cgiutils o cgiutils c  gcc  wall  i    g     dhave config h  dnscgi    c  o cgiauth o cgiauth c  gcc  wall  i    g     dhave config h  dnscgi  c  o macros cgi o    common macros c     common macros c  in function ‘process macros r’      common macros c    warning  suggest parentheses around assignment used as truth value  gcc  wall  i    g     dhave config h  dnscgi  c  o objects cgi o    common objects c  gcc  wall  i    g     dhave config h  dnscgi  c  o xobjects cgi o    xdata xodtemplate c  gcc  wall  i    g     dhave config h  dnscgi  c  o statusdata cgi o    common statusdata c  gcc  wall  i    g     dhave config h  dnscgi  c  o xstatusdata cgi o    xdata xsddefault c  gcc  wall  i    g     dhave config h  dnscgi  c  o comments cgi o    common comments c  gcc  wall  i    g     dhave config h  dnscgi  c  o downtime cgi o    common downtime c  gcc  wall  i    g     dhave config h  dnscgi  djson nagios    c  o archiveutils o archiveutils c  gcc  wall  i    g     dhave config h  dnscgi  djson nagios    c  o jsonutils o jsonutils c  gcc  wall  i    g     dhave config h  dnscgi  djson nagios     o archivejson cgi archivejson c    common shared o getcgi o cgiutils o cgiauth o macros cgi o  objects cgi o xobjects cgi o statusdata cgi o xstatusdata cgi o comments cgi o downtime cgi o    lib libnagios a archiveutils o jsonutils o   gcc  wall  i    g     dhave config h  dnscgi   o avail cgi avail c    common shared o getcgi o cgiutils o cgiauth o macros cgi o  objects cgi o xobjects cgi o statusdata cgi o xstatusdata cgi o comments cgi o downtime cgi o    lib libnagios a   gcc  wall  i    g     dhave config h  dnscgi    c  o extcmd list o extcmd list c  gcc  wall  i    g     dhave config h  dnscgi   o cmd cgi cmd c extcmd list o    common shared o getcgi o cgiutils o cgiauth o macros cgi o  objects cgi o xobjects cgi o statusdata cgi o xstatusdata cgi o comments cgi o downtime cgi o    lib libnagios a     gcc  wall  i    g     dhave config h  dnscgi   o config cgi config c     common shared o getcgi o cgiutils o cgiauth o macros cgi o  objects cgi o xobjects cgi o statusdata cgi o xstatusdata cgi o comments cgi o downtime cgi o    lib libnagios a   gcc  wall  i    g     dhave config h  dnscgi   o extinfo cgi extinfo c    common shared o getcgi o cgiutils o cgiauth o macros cgi o  objects cgi o xobjects cgi o statusdata cgi o xstatusdata cgi o comments cgi o downtime cgi o    lib libnagios a     gcc  wall  i    g     dhave config h  dnscgi   o history cgi history c    common shared o getcgi o cgiutils o cgiauth o macros cgi o  objects cgi o xobjects cgi o statusdata cgi o xstatusdata cgi o comments cgi o downtime cgi o    lib libnagios a   gcc  wall  i    g     dhave config h  dnscgi   o notifications cgi notifications c    common shared o getcgi o cgiutils o cgiauth o macros cgi o  objects cgi o xobjects cgi o statusdata cgi o xstatusdata cgi o comments cgi o downtime cgi o    lib libnagios a   gcc  wall  i    g     dhave config h  dnscgi  djson nagios     o objectjson cgi objectjson c    common shared o getcgi o cgiutils o cgiauth o macros cgi o  objects cgi o xobjects cgi o statusdata cgi o xstatusdata cgi o comments cgi o downtime cgi o    lib libnagios a jsonutils o   gcc  wall  i    g     dhave config h  dnscgi   o outages cgi outages c    common shared o getcgi o cgiutils o cgiauth o macros cgi o  objects cgi o xobjects cgi o statusdata cgi o xstatusdata cgi o comments cgi o downtime cgi o    lib libnagios a    gcc  wall  i    g     dhave config h  dnscgi   o showlog cgi showlog c    common shared o getcgi o cgiutils o cgiauth o macros cgi o  objects cgi o xobjects cgi o statusdata cgi o xstatusdata cgi o comments cgi o downtime cgi o    lib libnagios a   gcc  wall  i    g     dhave config h  dnscgi   o status cgi status c    common shared o getcgi o cgiutils o cgiauth o macros cgi o  objects cgi o xobjects cgi o statusdata cgi o xstatusdata cgi o comments cgi o downtime cgi o    lib libnagios a    gcc  wall  i    g     dhave config h  dnscgi  djson nagios     o statusjson cgi statusjson c    common shared o getcgi o cgiutils o cgiauth o macros cgi o  objects cgi o xobjects cgi o statusdata cgi o xstatusdata cgi o comments cgi o downtime cgi o    lib libnagios a jsonutils o   gcc  wall  i    g     dhave config h  dnscgi   o statuswml cgi statuswml c    common shared o getcgi o cgiutils o cgiauth o macros cgi o  objects cgi o xobjects cgi o statusdata cgi o xstatusdata cgi o comments cgi o downtime cgi o    lib libnagios a   gcc  wall  i    g     dhave config h  dnscgi   o summary cgi summary c    common shared o getcgi o cgiutils o cgiauth o macros cgi o  objects cgi o xobjects cgi o statusdata cgi o xstatusdata cgi o comments cgi o downtime cgi o    lib libnagios a   gcc  wall  i    g     dhave config h  dnscgi   o tac cgi tac c    common shared o getcgi o cgiutils o cgiauth o macros cgi o  objects cgi o xobjects cgi o statusdata cgi o xstatusdata cgi o comments cgi o downtime cgi o    lib libnagios a    gcc  wall  i    g     dhave config h  dnscgi   o statuswrl cgi statuswrl c    common shared o getcgi o cgiutils o cgiauth o macros cgi o  objects cgi o xobjects cgi o statusdata cgi o xstatusdata cgi o comments cgi o downtime cgi o    lib libnagios a  lm   gcc  wall  i    g     dhave config h  dnscgi   o statusmap cgi statusmap c    common shared o getcgi o cgiutils o cgiauth o macros cgi o  objects cgi o xobjects cgi o statusdata cgi o xstatusdata cgi o comments cgi o downtime cgi o    lib libnagios a  lgd   lpng  ljpeg  lz  lm   gcc  wall  i    g     dhave config h  dnscgi   o trends cgi trends c    common shared o getcgi o cgiutils o cgiauth o macros cgi o  objects cgi o xobjects cgi o statusdata cgi o xstatusdata cgi o comments cgi o downtime cgi o    lib libnagios a  lgd   lpng  ljpeg  lz  lm   gcc  wall  i    g     dhave config h  dnscgi   o histogram cgi histogram c    common shared o getcgi o cgiutils o cgiauth o macros cgi o  objects cgi o xobjects cgi o statusdata cgi o xstatusdata cgi o comments cgi o downtime cgi o    lib libnagios a  lgd   lpng  ljpeg  lz  lm   make   leaving directory   tmp nagioscore cgi   cd   html    make  make   entering directory   tmp nagioscore html    cd angularjs    unzip  u angular       zip   archive   angular       zip     creating  angular           inflating  angular       angular animate js      inflating  angular       angular animate min js      inflating  angular       angular animate min js map      inflating  angular       angular aria js      inflating  angular       angular aria min js      inflating  angular       angular aria min js map      inflating  angular       angular cookies js      inflating  angular       angular cookies min js      inflating  angular       angular cookies min js map      inflating  angular       angular csp css      inflating  angular       angular loader js      inflating  angular       angular loader min js      inflating  angular       angular loader min js map      inflating  angular       angular messages js      inflating  angular       angular messages min js      inflating  angular       angular messages min js map      inflating  angular       angular mocks js      inflating  angular       angular resource js      inflating  angular       angular resource min js      inflating  angular       angular resource min js map      inflating  angular       angular route js      inflating  angular       angular route min js      inflating  angular       angular route min js map      inflating  angular       angular sanitize js      inflating  angular       angular sanitize min js      inflating  angular       angular sanitize min js map      inflating  angular       angular scenario js      inflating  angular       angular touch js      inflating  angular       angular touch min js      inflating  angular       angular touch min js map      inflating  angular       angular js      inflating  angular       angular min js      inflating  angular       angular min js map       creating  angular       docs     inflating  angular       docs   html       creating  angular       docs components      creating  angular       docs components bootstrap            creating  angular       docs components bootstrap       css     inflating  angular       docs components bootstrap       css bootstrap theme css      inflating  angular       docs components bootstrap       css bootstrap theme css map      inflating  angular       docs components bootstrap       css bootstrap theme min css      inflating  angular       docs components bootstrap       css bootstrap css      inflating  angular       docs components bootstrap       css bootstrap css map      inflating  angular       docs components bootstrap       css bootstrap min css       creating  angular       docs components bootstrap       fonts     inflating  angular       docs components bootstrap       fonts glyphicons halflings regular eot      inflating  angular       docs components bootstrap       fonts glyphicons halflings regular svg      inflating  angular       docs components bootstrap       fonts glyphicons halflings regular ttf      inflating  angular       docs components bootstrap       fonts glyphicons halflings regular woff       creating  angular       docs components bootstrap       js     inflating  angular       docs components bootstrap       js bootstrap js      inflating  angular       docs components bootstrap       js bootstrap min js       creating  angular       docs components google code prettify           inflating  angular       docs components google code prettify       changes html      inflating  angular       docs components google code prettify       copying      inflating  angular       docs components google code prettify       readme zh hans html      inflating  angular       docs components google code prettify       readme html      inflating  angular       docs components google code prettify       readme md      inflating  angular       docs components google code prettify       bower json       creating  angular       docs components google code prettify       src     inflating  angular       docs components google code prettify       src lang apollo js      inflating  angular       docs components google code prettify       src lang clj js      inflating  angular       docs components google code prettify       src lang css js      inflating  angular       docs components google code prettify       src lang dart js      inflating  angular       docs components google code prettify       src lang go js      inflating  angular       docs components google code prettify       src lang hs js      inflating  angular       docs components google code prettify       src lang lisp js      inflating  angular       docs components google code prettify       src lang lua js      inflating  angular       docs components google code prettify       src lang ml js      inflating  angular       docs components google code prettify       src lang n js      inflating  angular       docs components google code prettify       src lang proto js      inflating  angular       docs components google code prettify       src lang scala js      inflating  angular       docs components google code prettify       src lang sql js      inflating  angular       docs components google code prettify       src lang tex js      inflating  angular       docs components google code prettify       src lang vb js      inflating  angular       docs components google code prettify       src lang vhdl js      inflating  angular       docs components google code prettify       src lang wiki js      inflating  angular       docs components google code prettify       src lang xq js      inflating  angular       docs components google code prettify       src lang yaml js      inflating  angular       docs components google code prettify       src prettify css      inflating  angular       docs components google code prettify       src prettify js       creating  angular       docs components google code prettify       styles     inflating  angular       docs components google code prettify       styles demo html      inflating  angular       docs components google code prettify       styles desert css      inflating  angular       docs components google code prettify       styles index html      inflating  angular       docs components google code prettify       styles sons of obsidian css      inflating  angular       docs components google code prettify       styles sunburst css       creating  angular       docs components jquery           inflating  angular       docs components jquery       jquery js      inflating  angular       docs components jquery       jquery min js       creating  angular       docs components lunr js           inflating  angular       docs components lunr js       lunr js      inflating  angular       docs components lunr js       lunr min js      inflating  angular       docs components lunr js       server js       creating  angular       docs components marked           inflating  angular       docs components marked       index js       creating  angular       docs components marked       lib     inflating  angular       docs components marked       lib marked js       creating  angular       docs components open sans fontface           inflating  angular       docs components open sans fontface       readme md      inflating  angular       docs components open sans fontface       bower json       creating  angular       docs components open sans fontface       fonts      creating  angular       docs components open sans fontface       fonts bold     inflating  angular       docs components open sans fontface       fonts bold opensans bold eot      inflating  angular       docs components open sans fontface       fonts bold opensans bold svg      inflating  angular       docs components open sans fontface       fonts bold opensans bold ttf      inflating  angular       docs components open sans fontface       fonts bold opensans bold woff       creating  angular       docs components open sans fontface       fonts bolditalic     inflating  angular       docs components open sans fontface       fonts bolditalic opensans bolditalic eot      inflating  angular       docs components open sans fontface       fonts bolditalic opensans bolditalic svg      inflating  angular       docs components open sans fontface       fonts bolditalic opensans bolditalic ttf      inflating  angular       docs components open sans fontface       fonts bolditalic opensans bolditalic woff       creating  angular       docs components open sans fontface       fonts extrabold     inflating  angular       docs components open sans fontface       fonts extrabold opensans extrabold eot      inflating  angular       docs components open sans fontface       fonts extrabold opensans extrabold svg      inflating  angular       docs components open sans fontface       fonts extrabold opensans extrabold ttf      inflating  angular       docs components open sans fontface       fonts extrabold opensans extrabold woff       creating  angular       docs components open sans fontface       fonts extrabolditalic     inflating  angular       docs components open sans fontface       fonts extrabolditalic opensans extrabolditalic eot      inflating  angular       docs components open sans fontface       fonts extrabolditalic opensans extrabolditalic svg      inflating  angular       docs components open sans fontface       fonts extrabolditalic opensans extrabolditalic ttf      inflating  angular       docs components open sans fontface       fonts extrabolditalic opensans extrabolditalic woff       creating  angular       docs components open sans fontface       fonts italic     inflating  angular       docs components open sans fontface       fonts italic opensans italic eot      inflating  angular       docs components open sans fontface       fonts italic opensans italic svg      inflating  angular       docs components open sans fontface       fonts italic opensans italic ttf      inflating  angular       docs components open sans fontface       fonts italic opensans italic woff       creating  angular       docs components open sans fontface       fonts light     inflating  angular       docs components open sans fontface       fonts light opensans light eot      inflating  angular       docs components open sans fontface       fonts light opensans light svg      inflating  angular       docs components open sans fontface       fonts light opensans light ttf      inflating  angular       docs components open sans fontface       fonts light opensans light woff       creating  angular       docs components open sans fontface       fonts lightitalic     inflating  angular       docs components open sans fontface       fonts lightitalic opensans lightitalic eot      inflating  angular       docs components open sans fontface       fonts lightitalic opensans lightitalic svg      inflating  angular       docs components open sans fontface       fonts lightitalic opensans lightitalic ttf      inflating  angular       docs components open sans fontface       fonts lightitalic opensans lightitalic woff       creating  angular       docs components open sans fontface       fonts regular     inflating  angular       docs components open sans fontface       fonts regular opensans regular eot      inflating  angular       docs components open sans fontface       fonts regular opensans regular svg      inflating  angular       docs components open sans fontface       fonts regular opensans regular ttf      inflating  angular       docs components open sans fontface       fonts regular opensans regular woff       creating  angular       docs components open sans fontface       fonts semibold     inflating  angular       docs components open sans fontface       fonts semibold opensans semibold eot      inflating  angular       docs components open sans fontface       fonts semibold opensans semibold svg      inflating  angular       docs components open sans fontface       fonts semibold opensans semibold ttf      inflating  angular       docs components open sans fontface       fonts semibold opensans semibold woff       creating  angular       docs components open sans fontface       fonts semibolditalic     inflating  angular       docs components open sans fontface       fonts semibolditalic opensans semibolditalic eot      inflating  angular       docs components open sans fontface       fonts semibolditalic opensans semibolditalic svg      inflating  angular       docs components open sans fontface       fonts semibolditalic opensans semibolditalic ttf      inflating  angular       docs components open sans fontface       fonts semibolditalic opensans semibolditalic woff      inflating  angular       docs components open sans fontface       index html      inflating  angular       docs components open sans fontface       open sans css      inflating  angular       docs components open sans fontface       open sans less      inflating  angular       docs components open sans fontface       open sans scss       creating  angular       docs css     inflating  angular       docs css animations css      inflating  angular       docs css doc widgets css      inflating  angular       docs css docs css      inflating  angular       docs css prettify theme css      inflating  angular       docs css prettify css       creating  angular       docs examples      creating  angular       docs examples example  filter     inflating  angular       docs examples example  filter index debug html      inflating  angular       docs examples example  filter index jquery html      inflating  angular       docs examples example  filter index production html      inflating  angular       docs examples example  filter index html      inflating  angular       docs examples example  filter manifest json      inflating  angular       docs examples example  filter script js       creating  angular       docs examples example  route service     inflating  angular       docs examples example  route service book html      inflating  angular       docs examples example  route service chapter html      inflating  angular       docs examples example  route service index debug html      inflating  angular       docs examples example  route service index jquery html      inflating  angular       docs examples example  route service index production html      inflating  angular       docs examples example  route service index html      inflating  angular       docs examples example  route service manifest json      inflating  angular       docs examples example  route service protractor js      inflating  angular       docs examples example  route service script js       creating  angular       docs examples example ngmodelcontroller     inflating  angular       docs examples example ngmodelcontroller index debug html      inflating  angular       docs examples example ngmodelcontroller index jquery html      inflating  angular       docs examples example ngmodelcontroller index production html      inflating  angular       docs examples example ngmodelcontroller index html      inflating  angular       docs examples example ngmodelcontroller manifest json      inflating  angular       docs examples example ngmodelcontroller protractor js      inflating  angular       docs examples example ngmodelcontroller script js      inflating  angular       docs examples example ngmodelcontroller style css       creating  angular       docs examples example checkbox input directive     inflating  angular       docs examples example checkbox input directive index debug html      inflating  angular       docs examples example checkbox input directive index jquery html      inflating  angular       docs examples example checkbox input directive index production html      inflating  angular       docs examples example checkbox input directive index html      inflating  angular       docs examples example checkbox input directive manifest json      inflating  angular       docs examples example checkbox input directive protractor js       creating  angular       docs examples example date input directive     inflating  angular       docs examples example date input directive index debug html      inflating  angular       docs examples example date input directive index jquery html      inflating  angular       docs examples example date input directive index production html      inflating  angular       docs examples example date input directive index html      inflating  angular       docs examples example date input directive manifest json      inflating  angular       docs examples example date input directive protractor js       creating  angular       docs examples example datetimelocal input directive     inflating  angular       docs examples example datetimelocal input directive index debug html      inflating  angular       docs examples example datetimelocal input directive index jquery html      inflating  angular       docs examples example datetimelocal input directive index production html      inflating  angular       docs examples example datetimelocal input directive index html      inflating  angular       docs examples example datetimelocal input directive manifest json      inflating  angular       docs examples example datetimelocal input directive protractor js       creating  angular       docs examples example email input directive     inflating  angular       docs examples example email input directive index debug html      inflating  angular       docs examples example email input directive index jquery html      inflating  angular       docs examples example email input directive index production html      inflating  angular       docs examples example email input directive index html      inflating  angular       docs examples example email input directive manifest json      inflating  angular       docs examples example email input directive protractor js       creating  angular       docs examples example error  rootscope inprog     inflating  angular       docs examples example error  rootscope inprog app js      inflating  angular       docs examples example error  rootscope inprog index debug html      inflating  angular       docs examples example error  rootscope inprog index jquery html      inflating  angular       docs examples example error  rootscope inprog index production html      inflating  angular       docs examples example error  rootscope inprog index html      inflating  angular       docs examples example error  rootscope inprog manifest json       creating  angular       docs examples example example      creating  angular       docs examples example example csp     inflating  angular       docs examples example example csp index debug html      inflating  angular       docs examples example example csp index jquery html      inflating  angular       docs examples example example csp index production html      inflating  angular       docs examples example example csp index html      inflating  angular       docs examples example example csp manifest json      inflating  angular       docs examples example example csp protractor js      inflating  angular       docs examples example example csp script js      inflating  angular       docs examples example example index debug html      inflating  angular       docs examples example example index jquery html      inflating  angular       docs examples example example index production html      inflating  angular       docs examples example example index html      inflating  angular       docs examples example example manifest json      inflating  angular       docs examples example example script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   http hello html      inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   my customer html      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js      inflating  angular       docs examples example   script js      inflating  angular       docs examples example   test data json       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   customer address html      inflating  angular       docs examples example   customer name html      inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   my customer html      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   my customer html      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   my customer iso html      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   my customer plus vojta html      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   my dialog html      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   my dialog html      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   my dialog close html      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   my pane html      inflating  angular       docs examples example   my tabs html      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   animations css      inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   style css       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js      inflating  angular       docs examples example   style css       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js      inflating  angular       docs examples example   style css       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js      inflating  angular       docs examples example   style css       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js      inflating  angular       docs examples example   style css       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js      inflating  angular       docs examples example   style css       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   app js      inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js      inflating  angular       docs examples example   style css       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js      inflating  angular       docs examples example   style css       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js      inflating  angular       docs examples example   style css       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js      inflating  angular       docs examples example   style css       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   app js      inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   app css      inflating  angular       docs examples example   app js      inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   animations css      inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   animations css      inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js      inflating  angular       docs examples example   script js      inflating  angular       docs examples example     html      inflating  angular       docs examples example     html       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   animations css      inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   animations css      inflating  angular       docs examples example   glyphicons css      inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   animations css      inflating  angular       docs examples example   glyphicons css      inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js      inflating  angular       docs examples example   style css       creating  angular       docs examples example       inflating  angular       docs examples example   animations css      inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   script js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example       inflating  angular       docs examples example   index debug html      inflating  angular       docs examples example   index jquery html      inflating  angular       docs examples example   index production html      inflating  angular       docs examples example   index html      inflating  angular       docs examples example   manifest json      inflating  angular       docs examples example   protractor js       creating  angular       docs examples example guide concepts       inflating  angular       docs examples example guide concepts   index debug html      inflating  angular       docs examples example guide concepts   index jquery html      inflating  angular       docs examples example guide concepts   index production html      inflating  angular       docs examples example guide concepts   index html      inflating  angular       docs examples example guide concepts   manifest json       creating  angular       docs examples example guide concepts       inflating  angular       docs examples example guide concepts   index debug html      inflating  angular       docs examples example guide concepts   index jquery html      inflating  angular       docs examples example guide concepts   index production html      inflating  angular       docs examples example guide concepts   index html      inflating  angular       docs examples example guide concepts     js      inflating  angular       docs examples example guide concepts   manifest json       creating  angular       docs examples example guide concepts       inflating  angular       docs examples example guide concepts     js      inflating  angular       docs examples example guide concepts   index debug html      inflating  angular       docs examples example guide concepts   index jquery html      inflating  angular       docs examples example guide concepts   index production html      inflating  angular       docs examples example guide concepts   index html      inflating  angular       docs examples example guide concepts     js      inflating  angular       docs examples example guide concepts   manifest json       creating  angular       docs examples example guide concepts       inflating  angular       docs examples example guide concepts     js      inflating  angular       docs examples example guide concepts   index debug html      inflating  angular       docs examples example guide concepts   index jquery html      inflating  angular       docs examples example guide concepts   index production html      inflating  angular       docs examples example guide concepts   index html      inflating  angular       docs examples example guide concepts     js      inflating  angular       docs examples example guide concepts   manifest json       creating  angular       docs examples example input directive     inflating  angular       docs examples example input directive index debug html      inflating  angular       docs examples example input directive index jquery html      inflating  angular       docs examples example input directive index production html      inflating  angular       docs examples example input directive index html      inflating  angular       docs examples example input directive manifest json      inflating  angular       docs examples example input directive protractor js       creating  angular       docs examples example location hashbang mode     inflating  angular       docs examples example location hashbang mode addressbar js      inflating  angular       docs examples example location hashbang mode app js      inflating  angular       docs examples example location hashbang mode fakebrowser js      inflating  angular       docs examples example location hashbang mode index debug html      inflating  angular       docs examples example location hashbang mode index jquery html      inflating  angular       docs examples example location hashbang mode index production html      inflating  angular       docs examples example location hashbang mode index html      inflating  angular       docs examples example location hashbang mode manifest json      inflating  angular       docs examples example location hashbang mode protractor js       creating  angular       docs examples example location   mode     inflating  angular       docs examples example location   mode addressbar js      inflating  angular       docs examples example location   mode app js      inflating  angular       docs examples example location   mode fakebrowser js      inflating  angular       docs examples example location   mode index debug html      inflating  angular       docs examples example location   mode index jquery html      inflating  angular       docs examples example location   mode index production html      inflating  angular       docs examples example location   mode index html      inflating  angular       docs examples example location   mode manifest json      inflating  angular       docs examples example location   mode protractor js       creating  angular       docs examples example month input directive     inflating  angular       docs examples example month input directive index debug html      inflating  angular       docs examples example month input directive index jquery html      inflating  angular       docs examples example month input directive index production html      inflating  angular       docs examples example month input directive index html      inflating  angular       docs examples example month input directive manifest json      inflating  angular       docs examples example month input directive protractor js       creating  angular       docs examples example ng model cancel update     inflating  angular       docs examples example ng model cancel update app js      inflating  angular       docs examples example ng model cancel update index debug html      inflating  angular       docs examples example ng model cancel update index jquery html      inflating  angular       docs examples example ng model cancel update index production html      inflating  angular       docs examples example ng model cancel update index html      inflating  angular       docs examples example ng model cancel update manifest json       creating  angular       docs examples example ngchange directive     inflating  angular       docs examples example ngchange directive index debug html      inflating  angular       docs examples example ngchange directive index jquery html      inflating  angular       docs examples example ngchange directive index production html      inflating  angular       docs examples example ngchange directive index html      inflating  angular       docs examples example ngchange directive manifest json      inflating  angular       docs examples example ngchange directive protractor js       creating  angular       docs examples example ngcontroller     inflating  angular       docs examples example ngcontroller app js      inflating  angular       docs examples example ngcontroller index debug html      inflating  angular       docs examples example ngcontroller index jquery html      inflating  angular       docs examples example ngcontroller index production html      inflating  angular       docs examples example ngcontroller index html      inflating  angular       docs examples example ngcontroller manifest json      inflating  angular       docs examples example ngcontroller protractor js       creating  angular       docs examples example ngcontrolleras     inflating  angular       docs examples example ngcontrolleras app js      inflating  angular       docs examples example ngcontrolleras index debug html      inflating  angular       docs examples example ngcontrolleras index jquery html      inflating  angular       docs examples example ngcontrolleras index production html      inflating  angular       docs examples example ngcontrolleras index html      inflating  angular       docs examples example ngcontrolleras manifest json      inflating  angular       docs examples example ngcontrolleras protractor js       creating  angular       docs examples example nglist directive      creating  angular       docs examples example nglist directive newlines     inflating  angular       docs examples example nglist directive newlines index debug html      inflating  angular       docs examples example nglist directive newlines index jquery html      inflating  angular       docs examples example nglist directive newlines index production html      inflating  angular       docs examples example nglist directive newlines index html      inflating  angular       docs examples example nglist directive newlines manifest json      inflating  angular       docs examples example nglist directive newlines protractor js      inflating  angular       docs examples example nglist directive app js      inflating  angular       docs examples example nglist directive index debug html      inflating  angular       docs examples example nglist directive index jquery html      inflating  angular       docs examples example nglist directive index production html      inflating  angular       docs examples example nglist directive index html      inflating  angular       docs examples example nglist directive manifest json      inflating  angular       docs examples example nglist directive protractor js       creating  angular       docs examples example ngmessages directive     inflating  angular       docs examples example ngmessages directive index debug html      inflating  angular       docs examples example ngmessages directive index jquery html      inflating  angular       docs examples example ngmessages directive index production html      inflating  angular       docs examples example ngmessages directive index html      inflating  angular       docs examples example ngmessages directive manifest json      inflating  angular       docs examples example ngmessages directive script js       creating  angular       docs examples example ngmodel getter setter     inflating  angular       docs examples example ngmodel getter setter app js      inflating  angular       docs examples example ngmodel getter setter index debug html      inflating  angular       docs examples example ngmodel getter setter index jquery html      inflating  angular       docs examples example ngmodel getter setter index production html      inflating  angular       docs examples example ngmodel getter setter index html      inflating  angular       docs examples example ngmodel getter setter manifest json       creating  angular       docs examples example ngmodeloptions directive blur     inflating  angular       docs examples example ngmodeloptions directive blur app js      inflating  angular       docs examples example ngmodeloptions directive blur index debug html      inflating  angular       docs examples example ngmodeloptions directive blur index jquery html      inflating  angular       docs examples example ngmodeloptions directive blur index production html      inflating  angular       docs examples example ngmodeloptions directive blur index html      inflating  angular       docs examples example ngmodeloptions directive blur manifest json      inflating  angular       docs examples example ngmodeloptions directive blur protractor js       creating  angular       docs examples example ngmodeloptions directive debounce     inflating  angular       docs examples example ngmodeloptions directive debounce app js      inflating  angular       docs examples example ngmodeloptions directive debounce index debug html      inflating  angular       docs examples example ngmodeloptions directive debounce index jquery html      inflating  angular       docs examples example ngmodeloptions directive debounce index production html      inflating  angular       docs examples example ngmodeloptions directive debounce index html      inflating  angular       docs examples example ngmodeloptions directive debounce manifest json       creating  angular       docs examples example ngmodeloptions directive getter setter     inflating  angular       docs examples example ngmodeloptions directive getter setter app js      inflating  angular       docs examples example ngmodeloptions directive getter setter index debug html      inflating  angular       docs examples example ngmodeloptions directive getter setter index jquery html      inflating  angular       docs examples example ngmodeloptions directive getter setter index production html      inflating  angular       docs examples example ngmodeloptions directive getter setter index html      inflating  angular       docs examples example ngmodeloptions directive getter setter manifest json       creating  angular       docs examples example ngvalue directive     inflating  angular       docs examples example ngvalue directive index debug html      inflating  angular       docs examples example ngvalue directive index jquery html      inflating  angular       docs examples example ngvalue directive index production html      inflating  angular       docs examples example ngvalue directive index html      inflating  angular       docs examples example ngvalue directive manifest json      inflating  angular       docs examples example ngvalue directive protractor js       creating  angular       docs examples example ngview directive     inflating  angular       docs examples example ngview directive animations css      inflating  angular       docs examples example ngview directive book html      inflating  angular       docs examples example ngview directive chapter html      inflating  angular       docs examples example ngview directive index debug html      inflating  angular       docs examples example ngview directive index jquery html      inflating  angular       docs examples example ngview directive index production html      inflating  angular       docs examples example ngview directive index html      inflating  angular       docs examples example ngview directive manifest json      inflating  angular       docs examples example ngview directive protractor js      inflating  angular       docs examples example ngview directive script js       creating  angular       docs examples example number input directive     inflating  angular       docs examples example number input directive index debug html      inflating  angular       docs examples example number input directive index jquery html      inflating  angular       docs examples example number input directive index production html      inflating  angular       docs examples example number input directive index html      inflating  angular       docs examples example number input directive manifest json      inflating  angular       docs examples example number input directive protractor js       creating  angular       docs examples example radio input directive     inflating  angular       docs examples example radio input directive index debug html      inflating  angular       docs examples example radio input directive index jquery html      inflating  angular       docs examples example radio input directive index production html      inflating  angular       docs examples example radio input directive index html      inflating  angular       docs examples example radio input directive manifest json      inflating  angular       docs examples example radio input directive protractor js       creating  angular       docs examples example text input directive     inflating  angular       docs examples example text input directive index debug html      inflating  angular       docs examples example text input directive index jquery html      inflating  angular       docs examples example text input directive index production html      inflating  angular       docs examples example text input directive index html      inflating  angular       docs examples example text input directive manifest json      inflating  angular       docs examples example text input directive protractor js       creating  angular       docs examples example time input directive     inflating  angular       docs examples example time input directive index debug html      inflating  angular       docs examples example time input directive index jquery html      inflating  angular       docs examples example time input directive index production html      inflating  angular       docs examples example time input directive index html      inflating  angular       docs examples example time input directive manifest json      inflating  angular       docs examples example time input directive protractor js       creating  angular       docs examples example url input directive     inflating  angular       docs examples example url input directive index debug html      inflating  angular       docs examples example url input directive index jquery html      inflating  angular       docs examples example url input directive index production html      inflating  angular       docs examples example url input directive index html      inflating  angular       docs examples example url input directive manifest json      inflating  angular       docs examples example url input directive protractor js       creating  angular       docs examples example week input directive     inflating  angular       docs examples example week input directive index debug html      inflating  angular       docs examples example week input directive index jquery html      inflating  angular       docs examples example week input directive index production html      inflating  angular       docs examples example week input directive index html      inflating  angular       docs examples example week input directive manifest json      inflating  angular       docs examples example week input directive protractor js      inflating  angular       docs favicon ico       creating  angular       docs img     inflating  angular       docs img angularjs small png      inflating  angular       docs img one way data binding png      inflating  angular       docs img two way data binding png      inflating  angular       docs img angular parts png      inflating  angular       docs img angularjs for header only svg      inflating  angular       docs img bullet png      inflating  angular       docs img form data flow png      inflating  angular       docs img glyphicons halflings white png      inflating  angular       docs img glyphicons halflings png       creating  angular       docs img guide     inflating  angular       docs img guide concepts   png      inflating  angular       docs img guide concepts   png      inflating  angular       docs img guide concepts directive png      inflating  angular       docs img guide concepts module injector png      inflating  angular       docs img guide concepts module service png      inflating  angular       docs img guide concepts runtime png      inflating  angular       docs img guide concepts scope watch strategies png      inflating  angular       docs img guide concepts scope png      inflating  angular       docs img guide concepts startup png      inflating  angular       docs img guide concepts view png      inflating  angular       docs img guide di sequence final png      inflating  angular       docs img guide dom scope final png      inflating  angular       docs img guide forms debounce gif      inflating  angular       docs img guide forms update on blur gif      inflating  angular       docs img guide hashbang vs regular url jpg      inflating  angular       docs img guide scenario runner png      inflating  angular       docs img guide simple scope final png      inflating  angular       docs img helloworld png      inflating  angular       docs img helloworld   png       creating  angular       docs img tutorial     inflating  angular       docs img tutorial catalog screen png      inflating  angular       docs img tutorial tutorial   png      inflating  angular       docs img tutorial tutorial   final png      inflating  angular       docs img tutorial tutorial   png      inflating  angular       docs img tutorial tutorial   png      inflating  angular       docs img tutorial tutorial   png      inflating  angular       docs img tutorial tutorial   png      inflating  angular       docs img tutorial tutorial   pptx      inflating  angular       docs img tutorial tutorial   final png      inflating  angular       docs img tutorial tutorial     final png      inflating  angular       docs img tutorial tutorial     final png      inflating  angular       docs img tutorial xhr service final png      inflating  angular       docs index debug html      inflating  angular       docs index jquery html      inflating  angular       docs index production html      inflating  angular       docs index html       creating  angular       docs js      creating  angular       docs js angular bootstrap     inflating  angular       docs js angular bootstrap bootstrap js      inflating  angular       docs js angular bootstrap bootstrap min js      inflating  angular       docs js angular bootstrap bootstrap min js map      inflating  angular       docs js angular bootstrap dropdown toggle js      inflating  angular       docs js angular bootstrap dropdown toggle min js      inflating  angular       docs js angular bootstrap dropdown toggle min js map      inflating  angular       docs js docs js      inflating  angular       docs js docs min js      inflating  angular       docs js docs min js map      inflating  angular       docs js nav data js      inflating  angular       docs js pages data js      inflating  angular       docs js search data json      inflating  angular       docs js search worker js      inflating  angular       docs js search worker min js      inflating  angular       docs js search worker min js map      inflating  angular       docs js versions data js       creating  angular       docs partials      creating  angular       docs partials api     inflating  angular       docs partials api html       creating  angular       docs partials api auto     inflating  angular       docs partials api auto html       creating  angular       docs partials api auto service     inflating  angular       docs partials api auto service html      inflating  angular       docs partials api auto service  injector html      inflating  angular       docs partials api auto service  provide html       creating  angular       docs partials api ng     inflating  angular       docs partials api ng html       creating  angular       docs partials api ng directive     inflating  angular       docs partials api ng directive html      inflating  angular       docs partials api ng directive a html      inflating  angular       docs partials api ng directive form html      inflating  angular       docs partials api ng directive input html      inflating  angular       docs partials api ng directive ngapp html      inflating  angular       docs partials api ng directive ngbind html      inflating  angular       docs partials api ng directive ngbindhtml html      inflating  angular       docs partials api ng directive ngbindtemplate html      inflating  angular       docs partials api ng directive ngblur html      inflating  angular       docs partials api ng directive ngchange html      inflating  angular       docs partials api ng directive ngchecked html      inflating  angular       docs partials api ng directive ngclass html      inflating  angular       docs partials api ng directive ngclasseven html      inflating  angular       docs partials api ng directive ngclassodd html      inflating  angular       docs partials api ng directive ngclick html      inflating  angular       docs partials api ng directive ngcloak html      inflating  angular       docs partials api ng directive ngcontroller html      inflating  angular       docs partials api ng directive ngcopy html      inflating  angular       docs partials api ng directive ngcsp html      inflating  angular       docs partials api ng directive ngcut html      inflating  angular       docs partials api ng directive ngdblclick html      inflating  angular       docs partials api ng directive ngdisabled html      inflating  angular       docs partials api ng directive ngfocus html      inflating  angular       docs partials api ng directive ngform html      inflating  angular       docs partials api ng directive nghide html      inflating  angular       docs partials api ng directive nghref html      inflating  angular       docs partials api ng directive ngif html      inflating  angular       docs partials api ng directive nginclude html      inflating  angular       docs partials api ng directive nginit html      inflating  angular       docs partials api ng directive ngkeydown html      inflating  angular       docs partials api ng directive ngkeypress html      inflating  angular       docs partials api ng directive ngkeyup html      inflating  angular       docs partials api ng directive nglist html      inflating  angular       docs partials api ng directive ngmodel html      inflating  angular       docs partials api ng directive ngmodeloptions html      inflating  angular       docs partials api ng directive ngmousedown html      inflating  angular       docs partials api ng directive ngmouseenter html      inflating  angular       docs partials api ng directive ngmouseleave html      inflating  angular       docs partials api ng directive ngmousemove html      inflating  angular       docs partials api ng directive ngmouseover html      inflating  angular       docs partials api ng directive ngmouseup html      inflating  angular       docs partials api ng directive ngnonbindable html      inflating  angular       docs partials api ng directive ngopen html      inflating  angular       docs partials api ng directive ngpaste html      inflating  angular       docs partials api ng directive ngpluralize html      inflating  angular       docs partials api ng directive ngreadonly html      inflating  angular       docs partials api ng directive ngrepeat html      inflating  angular       docs partials api ng directive ngselected html      inflating  angular       docs partials api ng directive ngshow html      inflating  angular       docs partials api ng directive ngsrc html      inflating  angular       docs partials api ng directive ngsrcset html      inflating  angular       docs partials api ng directive ngstyle html      inflating  angular       docs partials api ng directive ngsubmit html      inflating  angular       docs partials api ng directive ngswitch html      inflating  angular       docs partials api ng directive ngtransclude html      inflating  angular       docs partials api ng directive ngvalue html      inflating  angular       docs partials api ng directive script html      inflating  angular       docs partials api ng directive select html      inflating  angular       docs partials api ng directive textarea html       creating  angular       docs partials api ng filter     inflating  angular       docs partials api ng filter html      inflating  angular       docs partials api ng filter currency html      inflating  angular       docs partials api ng filter date html      inflating  angular       docs partials api ng filter filter html      inflating  angular       docs partials api ng filter json html      inflating  angular       docs partials api ng filter limitto html      inflating  angular       docs partials api ng filter lowercase html      inflating  angular       docs partials api ng filter number html      inflating  angular       docs partials api ng filter orderby html      inflating  angular       docs partials api ng filter uppercase html       creating  angular       docs partials api ng function     inflating  angular       docs partials api ng function html      inflating  angular       docs partials api ng function angular bind html      inflating  angular       docs partials api ng function angular bootstrap html      inflating  angular       docs partials api ng function angular copy html      inflating  angular       docs partials api ng function angular element html      inflating  angular       docs partials api ng function angular equals html      inflating  angular       docs partials api ng function angular extend html      inflating  angular       docs partials api ng function angular foreach html      inflating  angular       docs partials api ng function angular fromjson html      inflating  angular       docs partials api ng function angular identity html      inflating  angular       docs partials api ng function angular injector html      inflating  angular       docs partials api ng function angular isarray html      inflating  angular       docs partials api ng function angular isdate html      inflating  angular       docs partials api ng function angular isdefined html      inflating  angular       docs partials api ng function angular iselement html      inflating  angular       docs partials api ng function angular isfunction html      inflating  angular       docs partials api ng function angular isnumber html      inflating  angular       docs partials api ng function angular isobject html      inflating  angular       docs partials api ng function angular isstring html      inflating  angular       docs partials api ng function angular isundefined html      inflating  angular       docs partials api ng function angular lowercase html      inflating  angular       docs partials api ng function angular module html      inflating  angular       docs partials api ng function angular noop html      inflating  angular       docs partials api ng function angular reloadwithdebuginfo html      inflating  angular       docs partials api ng function angular tojson html      inflating  angular       docs partials api ng function angular uppercase html       creating  angular       docs partials api ng input     inflating  angular       docs partials api ng input html      inflating  angular       docs partials api ng input input  html      inflating  angular       docs partials api ng input input  html      inflating  angular       docs partials api ng input input  html      inflating  angular       docs partials api ng input input  html      inflating  angular       docs partials api ng input input  html      inflating  angular       docs partials api ng input input  html      inflating  angular       docs partials api ng input input  html      inflating  angular       docs partials api ng input input  html      inflating  angular       docs partials api ng input input  html      inflating  angular       docs partials api ng input input  html      inflating  angular       docs partials api ng input input  html       creating  angular       docs partials api ng object     inflating  angular       docs partials api ng object html      inflating  angular       docs partials api ng object angular version html       creating  angular       docs partials api ng provider     inflating  angular       docs partials api ng provider html      inflating  angular       docs partials api ng provider  anchorscrollprovider html      inflating  angular       docs partials api ng provider  animateprovider html      inflating  angular       docs partials api ng provider  compileprovider html      inflating  angular       docs partials api ng provider  controllerprovider html      inflating  angular       docs partials api ng provider  filterprovider html      inflating  angular       docs partials api ng provider  httpprovider html      inflating  angular       docs partials api ng provider  interpolateprovider html      inflating  angular       docs partials api ng provider  locationprovider html      inflating  angular       docs partials api ng provider  logprovider html      inflating  angular       docs partials api ng provider  parseprovider html      inflating  angular       docs partials api ng provider  rootscopeprovider html      inflating  angular       docs partials api ng provider  scedelegateprovider html      inflating  angular       docs partials api ng provider  sceprovider html       creating  angular       docs partials api ng service     inflating  angular       docs partials api ng service html      inflating  angular       docs partials api ng service  anchorscroll html      inflating  angular       docs partials api ng service  animate html      inflating  angular       docs partials api ng service  cachefactory html      inflating  angular       docs partials api ng service  compile html      inflating  angular       docs partials api ng service  controller html      inflating  angular       docs partials api ng service  document html      inflating  angular       docs partials api ng service  exceptionhandler html      inflating  angular       docs partials api ng service  filter html      inflating  angular       docs partials api ng service  http html      inflating  angular       docs partials api ng service  httpbackend html      inflating  angular       docs partials api ng service  interpolate html      inflating  angular       docs partials api ng service  interval html      inflating  angular       docs partials api ng service  locale html      inflating  angular       docs partials api ng service  location html      inflating  angular       docs partials api ng service  log html      inflating  angular       docs partials api ng service  parse html      inflating  angular       docs partials api ng service  q html      inflating  angular       docs partials api ng service  rootelement html      inflating  angular       docs partials api ng service  rootscope html      inflating  angular       docs partials api ng service  sce html      inflating  angular       docs partials api ng service  scedelegate html      inflating  angular       docs partials api ng service  templatecache html      inflating  angular       docs partials api ng service  templaterequest html      inflating  angular       docs partials api ng service  timeout html      inflating  angular       docs partials api ng service  window html       creating  angular       docs partials api ng type     inflating  angular       docs partials api ng type html      inflating  angular       docs partials api ng type  cachefactory cache html      inflating  angular       docs partials api ng type  compile directive attributes html      inflating  angular       docs partials api ng type  rootscope scope html      inflating  angular       docs partials api ng type angular module html      inflating  angular       docs partials api ng type form formcontroller html      inflating  angular       docs partials api ng type ngmodel ngmodelcontroller html       creating  angular       docs partials api nganimate     inflating  angular       docs partials api nganimate html       creating  angular       docs partials api nganimate provider     inflating  angular       docs partials api nganimate provider html      inflating  angular       docs partials api nganimate provider  animateprovider html       creating  angular       docs partials api nganimate service     inflating  angular       docs partials api nganimate service html      inflating  angular       docs partials api nganimate service  animate html       creating  angular       docs partials api ngaria     inflating  angular       docs partials api ngaria html       creating  angular       docs partials api ngaria provider     inflating  angular       docs partials api ngaria provider html      inflating  angular       docs partials api ngaria provider  ariaprovider html       creating  angular       docs partials api ngaria service     inflating  angular       docs partials api ngaria service html      inflating  angular       docs partials api ngaria service  aria html       creating  angular       docs partials api ngcookies     inflating  angular       docs partials api ngcookies html       creating  angular       docs partials api ngcookies service     inflating  angular       docs partials api ngcookies service html      inflating  angular       docs partials api ngcookies service  cookiestore html      inflating  angular       docs partials api ngcookies service  cookies html       creating  angular       docs partials api ngmessages     inflating  angular       docs partials api ngmessages html       creating  angular       docs partials api ngmessages directive     inflating  angular       docs partials api ngmessages directive html      inflating  angular       docs partials api ngmessages directive ngmessage html      inflating  angular       docs partials api ngmessages directive ngmessages html       creating  angular       docs partials api ngmock     inflating  angular       docs partials api ngmock html       creating  angular       docs partials api ngmock function     inflating  angular       docs partials api ngmock function html      inflating  angular       docs partials api ngmock function angular mock dump html      inflating  angular       docs partials api ngmock function angular mock inject html      inflating  angular       docs partials api ngmock function angular mock module html       creating  angular       docs partials api ngmock object     inflating  angular       docs partials api ngmock object html      inflating  angular       docs partials api ngmock object angular mock html       creating  angular       docs partials api ngmock provider     inflating  angular       docs partials api ngmock provider html      inflating  angular       docs partials api ngmock provider  exceptionhandlerprovider html       creating  angular       docs partials api ngmock service     inflating  angular       docs partials api ngmock service html      inflating  angular       docs partials api ngmock service  exceptionhandler html      inflating  angular       docs partials api ngmock service  httpbackend html      inflating  angular       docs partials api ngmock service  interval html      inflating  angular       docs partials api ngmock service  log html      inflating  angular       docs partials api ngmock service  timeout html       creating  angular       docs partials api ngmock type     inflating  angular       docs partials api ngmock type html      inflating  angular       docs partials api ngmock type  rootscope scope html      inflating  angular       docs partials api ngmock type angular mock tzdate html       creating  angular       docs partials api       inflating  angular       docs partials api   html       creating  angular       docs partials api   service     inflating  angular       docs partials api   service html      inflating  angular       docs partials api   service  httpbackend html       creating  angular       docs partials api ngresource     inflating  angular       docs partials api ngresource html       creating  angular       docs partials api ngresource service     inflating  angular       docs partials api ngresource service html      inflating  angular       docs partials api ngresource service  resource html       creating  angular       docs partials api ngroute     inflating  angular       docs partials api ngroute html       creating  angular       docs partials api ngroute directive     inflating  angular       docs partials api ngroute directive html      inflating  angular       docs partials api ngroute directive ngview html       creating  angular       docs partials api ngroute provider     inflating  angular       docs partials api ngroute provider html      inflating  angular       docs partials api ngroute provider  routeprovider html       creating  angular       docs partials api ngroute service     inflating  angular       docs partials api ngroute service html      inflating  angular       docs partials api ngroute service  route html      inflating  angular       docs partials api ngroute service  routeparams html       creating  angular       docs partials api ngsanitize     inflating  angular       docs partials api ngsanitize html       creating  angular       docs partials api ngsanitize filter     inflating  angular       docs partials api ngsanitize filter html      inflating  angular       docs partials api ngsanitize filter linky html       creating  angular       docs partials api ngsanitize service     inflating  angular       docs partials api ngsanitize service html      inflating  angular       docs partials api ngsanitize service  sanitize html       creating  angular       docs partials api ngtouch     inflating  angular       docs partials api ngtouch html       creating  angular       docs partials api ngtouch directive     inflating  angular       docs partials api ngtouch directive html      inflating  angular       docs partials api ngtouch directive ngclick html      inflating  angular       docs partials api ngtouch directive ngswipeleft html      inflating  angular       docs partials api ngtouch directive ngswiperight html       creating  angular       docs partials api ngtouch service     inflating  angular       docs partials api ngtouch service html      inflating  angular       docs partials api ngtouch service  swipe html       creating  angular       docs partials error     inflating  angular       docs partials error html       creating  angular       docs partials error  animate     inflating  angular       docs partials error  animate html      inflating  angular       docs partials error  animate notcsel html       creating  angular       docs partials error  cachefactory     inflating  angular       docs partials error  cachefactory html      inflating  angular       docs partials error  cachefactory iid html       creating  angular       docs partials error  compile     inflating  angular       docs partials error  compile html      inflating  angular       docs partials error  compile ctreq html      inflating  angular       docs partials error  compile iscp html      inflating  angular       docs partials error  compile multidir html      inflating  angular       docs partials error  compile nodomevents html      inflating  angular       docs partials error  compile nonassign html      inflating  angular       docs partials error  compile selmulti html      inflating  angular       docs partials error  compile tpload html      inflating  angular       docs partials error  compile tplrt html      inflating  angular       docs partials error  compile uterdir html       creating  angular       docs partials error  controller     inflating  angular       docs partials error  controller html      inflating  angular       docs partials error  controller noscp html       creating  angular       docs partials error  http     inflating  angular       docs partials error  http html      inflating  angular       docs partials error  http badreq html       creating  angular       docs partials error  injector     inflating  angular       docs partials error  injector html      inflating  angular       docs partials error  injector cdep html      inflating  angular       docs partials error  injector itkn html      inflating  angular       docs partials error  injector modulerr html      inflating  angular       docs partials error  injector nomod html      inflating  angular       docs partials error  injector pget html      inflating  angular       docs partials error  injector strictdi html      inflating  angular       docs partials error  injector undef html      inflating  angular       docs partials error  injector unpr html       creating  angular       docs partials error  interpolate     inflating  angular       docs partials error  interpolate html      inflating  angular       docs partials error  interpolate interr html      inflating  angular       docs partials error  interpolate noconcat html       creating  angular       docs partials error  location     inflating  angular       docs partials error  location html      inflating  angular       docs partials error  location ipthprfx html      inflating  angular       docs partials error  location isrcharg html      inflating  angular       docs partials error  location nobase html      inflating  angular       docs partials error  location nostate html       creating  angular       docs partials error  parse     inflating  angular       docs partials error  parse html      inflating  angular       docs partials error  parse isecdom html      inflating  angular       docs partials error  parse isecff html      inflating  angular       docs partials error  parse isecfld html      inflating  angular       docs partials error  parse isecfn html      inflating  angular       docs partials error  parse isecobj html      inflating  angular       docs partials error  parse isecwindow html      inflating  angular       docs partials error  parse lexerr html      inflating  angular       docs partials error  parse syntax html      inflating  angular       docs partials error  parse ueoe html       creating  angular       docs partials error  q     inflating  angular       docs partials error  q html      inflating  angular       docs partials error  q norslvr html      inflating  angular       docs partials error  q qcycle html       creating  angular       docs partials error  resource     inflating  angular       docs partials error  resource html      inflating  angular       docs partials error  resource badargs html      inflating  angular       docs partials error  resource badcfg html      inflating  angular       docs partials error  resource badmember html      inflating  angular       docs partials error  resource badname html       creating  angular       docs partials error  rootscope     inflating  angular       docs partials error  rootscope html      inflating  angular       docs partials error  rootscope infdig html      inflating  angular       docs partials error  rootscope inprog html       creating  angular       docs partials error  sanitize     inflating  angular       docs partials error  sanitize html      inflating  angular       docs partials error  sanitize badparse html       creating  angular       docs partials error  sce     inflating  angular       docs partials error  sce html      inflating  angular       docs partials error  sce icontext html      inflating  angular       docs partials error  sce iequirks html      inflating  angular       docs partials error  sce imatcher html      inflating  angular       docs partials error  sce insecurl html      inflating  angular       docs partials error  sce itype html      inflating  angular       docs partials error  sce iwcard html      inflating  angular       docs partials error  sce unsafe html       creating  angular       docs partials error jqlite     inflating  angular       docs partials error jqlite html      inflating  angular       docs partials error jqlite nosel html      inflating  angular       docs partials error jqlite offargs html      inflating  angular       docs partials error jqlite onargs html       creating  angular       docs partials error ng     inflating  angular       docs partials error ng html      inflating  angular       docs partials error ng areq html      inflating  angular       docs partials error ng badname html      inflating  angular       docs partials error ng btstrpd html      inflating  angular       docs partials error ng cpi html      inflating  angular       docs partials error ng cpws html      inflating  angular       docs partials error ng test html       creating  angular       docs partials error ngmodel     inflating  angular       docs partials error ngmodel html      inflating  angular       docs partials error ngmodel constexpr html      inflating  angular       docs partials error ngmodel datefmt html      inflating  angular       docs partials error ngmodel nonassign html       creating  angular       docs partials error ngoptions     inflating  angular       docs partials error ngoptions html      inflating  angular       docs partials error ngoptions iexp html      inflating  angular       docs partials error ngoptions trkslct html       creating  angular       docs partials error ngpattern     inflating  angular       docs partials error ngpattern html      inflating  angular       docs partials error ngpattern noregexp html       creating  angular       docs partials error ngrepeat     inflating  angular       docs partials error ngrepeat html      inflating  angular       docs partials error ngrepeat badident html      inflating  angular       docs partials error ngrepeat dupes html      inflating  angular       docs partials error ngrepeat iexp html      inflating  angular       docs partials error ngrepeat iidexp html       creating  angular       docs partials error ngtransclude     inflating  angular       docs partials error ngtransclude html      inflating  angular       docs partials error ngtransclude orphan html       creating  angular       docs partials guide     inflating  angular       docs partials guide html      inflating  angular       docs partials guide  location html      inflating  angular       docs partials guide accessibility html      inflating  angular       docs partials guide animations html      inflating  angular       docs partials guide bootstrap html      inflating  angular       docs partials guide compiler html      inflating  angular       docs partials guide concepts html      inflating  angular       docs partials guide controller html      inflating  angular       docs partials guide css styling html      inflating  angular       docs partials guide databinding html      inflating  angular       docs partials guide di html      inflating  angular       docs partials guide directive html      inflating  angular       docs partials guide   testing html      inflating  angular       docs partials guide expression html      inflating  angular       docs partials guide filter html      inflating  angular       docs partials guide forms html      inflating  angular       docs partials guide   html      inflating  angular       docs partials guide ie html      inflating  angular       docs partials guide introduction html      inflating  angular       docs partials guide migration html      inflating  angular       docs partials guide module html      inflating  angular       docs partials guide production html      inflating  angular       docs partials guide providers html      inflating  angular       docs partials guide scope html      inflating  angular       docs partials guide security html      inflating  angular       docs partials guide services html      inflating  angular       docs partials guide templates html      inflating  angular       docs partials guide unit testing html       creating  angular       docs partials misc     inflating  angular       docs partials misc html      inflating  angular       docs partials misc contribute html      inflating  angular       docs partials misc downloading html      inflating  angular       docs partials misc faq html      inflating  angular       docs partials misc started html       creating  angular       docs partials tutorial     inflating  angular       docs partials tutorial html      inflating  angular       docs partials tutorial step   html      inflating  angular       docs partials tutorial step   html      inflating  angular       docs partials tutorial step   html      inflating  angular       docs partials tutorial step   html      inflating  angular       docs partials tutorial step   html      inflating  angular       docs partials tutorial step   html      inflating  angular       docs partials tutorial step   html      inflating  angular       docs partials tutorial step   html      inflating  angular       docs partials tutorial step   html      inflating  angular       docs partials tutorial step   html      inflating  angular       docs partials tutorial step   html      inflating  angular       docs partials tutorial step   html      inflating  angular       docs partials tutorial step   html      inflating  angular       docs partials tutorial the end html       creating  angular       docs        creating  angular       docs   example  route service     inflating  angular       docs   example  route service default test js      inflating  angular       docs   example  route service jquery test js       creating  angular       docs   example ngmodelcontroller     inflating  angular       docs   example ngmodelcontroller default test js      inflating  angular       docs   example ngmodelcontroller jquery test js       creating  angular       docs   example checkbox input directive     inflating  angular       docs   example checkbox input directive default test js      inflating  angular       docs   example checkbox input directive jquery test js       creating  angular       docs   example date input directive     inflating  angular       docs   example date input directive default test js      inflating  angular       docs   example date input directive jquery test js       creating  angular       docs   example datetimelocal input directive     inflating  angular       docs   example datetimelocal input directive default test js      inflating  angular       docs   example datetimelocal input directive jquery test js       creating  angular       docs   example email input directive     inflating  angular       docs   example email input directive default test js      inflating  angular       docs   example email input directive jquery test js       creating  angular       docs   example example csp     inflating  angular       docs   example example csp default test js      inflating  angular       docs   example example csp jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example       inflating  angular       docs   example   default test js      inflating  angular       docs   example   jquery test js       creating  angular       docs   example input directive     inflating  angular       docs   example input directive default test js      inflating  angular       docs   example input directive jquery test js       creating  angular       docs   example location hashbang mode     inflating  angular       docs   example location hashbang mode default test js      inflating  angular       docs   example location hashbang mode jquery test js       creating  angular       docs   example location   mode     inflating  angular       docs   example location   mode default test js      inflating  angular       docs   example location   mode jquery test js       creating  angular       docs   example month input directive     inflating  angular       docs   example month input directive default test js      inflating  angular       docs   example month input directive jquery test js       creating  angular       docs   example ngchange directive     inflating  angular       docs   example ngchange directive default test js      inflating  angular       docs   example ngchange directive jquery test js       creating  angular       docs   example ngcontroller     inflating  angular       docs   example ngcontroller default test js      inflating  angular       docs   example ngcontroller jquery test js       creating  angular       docs   example ngcontrolleras     inflating  angular       docs   example ngcontrolleras default test js      inflating  angular       docs   example ngcontrolleras jquery test js       creating  angular       docs   example nglist directive      creating  angular       docs   example nglist directive newlines     inflating  angular       docs   example nglist directive newlines default test js      inflating  angular       docs   example nglist directive newlines jquery test js      inflating  angular       docs   example nglist directive default test js      inflating  angular       docs   example nglist directive jquery test js       creating  angular       docs   example ngmodeloptions directive blur     inflating  angular       docs   example ngmodeloptions directive blur default test js      inflating  angular       docs   example ngmodeloptions directive blur jquery test js       creating  angular       docs   example ngvalue directive     inflating  angular       docs   example ngvalue directive default test js      inflating  angular       docs   example ngvalue directive jquery test js       creating  angular       docs   example ngview directive     inflating  angular       docs   example ngview directive default test js      inflating  angular       docs   example ngview directive jquery test js       creating  angular       docs   example number input directive     inflating  angular       docs   example number input directive default test js      inflating  angular       docs   example number input directive jquery test js       creating  angular       docs   example radio input directive     inflating  angular       docs   example radio input directive default test js      inflating  angular       docs   example radio input directive jquery test js       creating  angular       docs   example text input directive     inflating  angular       docs   example text input directive default test js      inflating  angular       docs   example text input directive jquery test js       creating  angular       docs   example time input directive     inflating  angular       docs   example time input directive default test js      inflating  angular       docs   example time input directive jquery test js       creating  angular       docs   example url input directive     inflating  angular       docs   example url input directive default test js      inflating  angular       docs   example url input directive jquery test js       creating  angular       docs   example week input directive     inflating  angular       docs   example week input directive default test js      inflating  angular       docs   example week input directive jquery test js      inflating  angular       errors json       creating  angular             inflating  angular         angular locale aa dj js      inflating  angular         angular locale aa er js      inflating  angular         angular locale aa et js      inflating  angular         angular locale aa js      inflating  angular         angular locale af na js      inflating  angular         angular locale af za js      inflating  angular         angular locale af js      inflating  angular         angular locale agq cm js      inflating  angular         angular locale agq js      inflating  angular         angular locale ak gh js      inflating  angular         angular locale ak js      inflating  angular         angular locale am et js      inflating  angular         angular locale am js      inflating  angular         angular locale ar   js      inflating  angular         angular locale ar ae js      inflating  angular         angular locale ar bh js      inflating  angular         angular locale ar dj js      inflating  angular         angular locale ar dz js      inflating  angular         angular locale ar eg js      inflating  angular         angular locale ar eh js      inflating  angular         angular locale ar er js      inflating  angular         angular locale ar il js      inflating  angular         angular locale ar iq js      inflating  angular         angular locale ar jo js      inflating  angular         angular locale ar km js      inflating  angular         angular locale ar kw js      inflating  angular         angular locale ar lb js      inflating  angular         angular locale ar ly js      inflating  angular         angular locale ar ma js      inflating  angular         angular locale ar mr js      inflating  angular         angular locale ar om js      inflating  angular         angular locale ar ps js      inflating  angular         angular locale ar qa js      inflating  angular         angular locale ar sa js      inflating  angular         angular locale ar sd js      inflating  angular         angular locale ar so js      inflating  angular         angular locale ar ss js      inflating  angular         angular locale ar sy js      inflating  angular         angular locale ar td js      inflating  angular         angular locale ar tn js      inflating  angular         angular locale ar ye js      inflating  angular         angular locale ar js      inflating  angular         angular locale as in js      inflating  angular         angular locale as js      inflating  angular         angular locale asa tz js      inflating  angular         angular locale asa js      inflating  angular         angular locale ast es js      inflating  angular         angular locale ast js      inflating  angular         angular locale az cyrl az js      inflating  angular         angular locale az cyrl js      inflating  angular         angular locale az latn az js      inflating  angular         angular locale az latn js      inflating  angular         angular locale az js      inflating  angular         angular locale bas cm js      inflating  angular         angular locale bas js      inflating  angular         angular locale be by js      inflating  angular         angular locale be js      inflating  angular         angular locale bem zm js      inflating  angular         angular locale bem js      inflating  angular         angular locale bez tz js      inflating  angular         angular locale bez js      inflating  angular         angular locale bg bg js      inflating  angular         angular locale bg js      inflating  angular         angular locale bm latn ml js      inflating  angular         angular locale bm latn js      inflating  angular         angular locale bm ml js      inflating  angular         angular locale bm js      inflating  angular         angular locale bn bd js      inflating  angular         angular locale bn in js      inflating  angular         angular locale bn js      inflating  angular         angular locale bo cn js      inflating  angular         angular locale bo in js      inflating  angular         angular locale bo js      inflating  angular         angular locale br fr js      inflating  angular         angular locale br js      inflating  angular         angular locale brx in js      inflating  angular         angular locale brx js      inflating  angular         angular locale bs cyrl ba js      inflating  angular         angular locale bs cyrl js      inflating  angular         angular locale bs latn ba js      inflating  angular         angular locale bs latn js      inflating  angular         angular locale bs js      inflating  angular         angular locale byn er js      inflating  angular         angular locale byn js      inflating  angular         angular locale ca ad js      inflating  angular         angular locale ca es valencia js      inflating  angular         angular locale ca es js      inflating  angular         angular locale ca fr js      inflating  angular         angular locale ca it js      inflating  angular         angular locale ca js      inflating  angular         angular locale cgg ug js      inflating  angular         angular locale cgg js      inflating  angular         angular locale chr us js      inflating  angular         angular locale chr js      inflating  angular         angular locale ckb arab iq js      inflating  angular         angular locale ckb arab ir js      inflating  angular         angular locale ckb arab js      inflating  angular         angular locale ckb iq js      inflating  angular         angular locale ckb ir js      inflating  angular         angular locale ckb latn iq js      inflating  angular         angular locale ckb latn js      inflating  angular         angular locale ckb js      inflating  angular         angular locale cs cz js      inflating  angular         angular locale cs js      inflating  angular         angular locale cy gb js      inflating  angular         angular locale cy js      inflating  angular         angular locale da dk js      inflating  angular         angular locale da gl js      inflating  angular         angular locale da js      inflating  angular         angular locale dav ke js      inflating  angular         angular locale dav js      inflating  angular         angular locale de at js      inflating  angular         angular locale de be js      inflating  angular         angular locale de ch js      inflating  angular         angular locale de de js      inflating  angular         angular locale de li js      inflating  angular         angular locale de lu js      inflating  angular         angular locale de js      inflating  angular         angular locale dje ne js      inflating  angular         angular locale dje js      inflating  angular         angular locale dsb de js      inflating  angular         angular locale dsb js      inflating  angular         angular locale dua cm js      inflating  angular         angular locale dua js      inflating  angular         angular locale dyo sn js      inflating  angular         angular locale dyo js      inflating  angular         angular locale dz bt js      inflating  angular         angular locale dz js      inflating  angular         angular locale ebu ke js      inflating  angular         angular locale ebu js      inflating  angular         angular locale ee gh js      inflating  angular         angular locale ee tg js      inflating  angular         angular locale ee js      inflating  angular         angular locale el cy js      inflating  angular         angular locale el gr js      inflating  angular         angular locale el js      inflating  angular         angular locale en   js      inflating  angular         angular locale en   js      inflating  angular         angular locale en ag js      inflating  angular         angular locale en ai js      inflating  angular         angular locale en as js      inflating  angular         angular locale en au js      inflating  angular         angular locale en bb js      inflating  angular         angular locale en be js      inflating  angular         angular locale en bm js      inflating  angular         angular locale en bs js      inflating  angular         angular locale en bw js      inflating  angular         angular locale en bz js      inflating  angular         angular locale en ca js      inflating  angular         angular locale en cc js      inflating  angular         angular locale en ck js      inflating  angular         angular locale en cm js      inflating  angular         angular locale en cx js      inflating  angular         angular locale en dg js      inflating  angular         angular locale en dm js      inflating  angular         angular locale en er js      inflating  angular         angular locale en fj js      inflating  angular         angular locale en fk js      inflating  angular         angular locale en fm js      inflating  angular         angular locale en gb js      inflating  angular         angular locale en gd js      inflating  angular         angular locale en gg js      inflating  angular         angular locale en gh js      inflating  angular         angular locale en gi js      inflating  angular         angular locale en gm js      inflating  angular         angular locale en gu js      inflating  angular         angular locale en gy js      inflating  angular         angular locale en hk js      inflating  angular         angular locale en ie js      inflating  angular         angular locale en im js      inflating  angular         angular locale en in js      inflating  angular         angular locale en io js      inflating  angular         angular locale en iso js      inflating  angular         angular locale en je js      inflating  angular         angular locale en jm js      inflating  angular         angular locale en ke js      inflating  angular         angular locale en ki js      inflating  angular         angular locale en kn js      inflating  angular         angular locale en ky js      inflating  angular         angular locale en lc js      inflating  angular         angular locale en lr js      inflating  angular         angular locale en ls js      inflating  angular         angular locale en mg js      inflating  angular         angular locale en mh js      inflating  angular         angular locale en mo js      inflating  angular         angular locale en mp js      inflating  angular         angular locale en ms js      inflating  angular         angular locale en mt js      inflating  angular         angular locale en mu js      inflating  angular         angular locale en mw js      inflating  angular         angular locale en my js      inflating  angular         angular locale en na js      inflating  angular         angular locale en nf js      inflating  angular         angular locale en ng js      inflating  angular         angular locale en nr js      inflating  angular         angular locale en nu js      inflating  angular         angular locale en nz js      inflating  angular         angular locale en pg js      inflating  angular         angular locale en ph js      inflating  angular         angular locale en pk js      inflating  angular         angular locale en pn js      inflating  angular         angular locale en pr js      inflating  angular         angular locale en pw js      inflating  angular         angular locale en rw js      inflating  angular         angular locale en sb js      inflating  angular         angular locale en sc js      inflating  angular         angular locale en sd js      inflating  angular         angular locale en sg js      inflating  angular         angular locale en sh js      inflating  angular         angular locale en sl js      inflating  angular         angular locale en ss js      inflating  angular         angular locale en sx js      inflating  angular         angular locale en sz js      inflating  angular         angular locale en tc js      inflating  angular         angular locale en tk js      inflating  angular         angular locale en to js      inflating  angular         angular locale en tt js      inflating  angular         angular locale en tv js      inflating  angular         angular locale en tz js      inflating  angular         angular locale en ug js      inflating  angular         angular locale en um js      inflating  angular         angular locale en us js      inflating  angular         angular locale en vc js      inflating  angular         angular locale en vg js      inflating  angular         angular locale en vi js      inflating  angular         angular locale en vu js      inflating  angular         angular locale en ws js      inflating  angular         angular locale en za js      inflating  angular         angular locale en zm js      inflating  angular         angular locale en zw js      inflating  angular         angular locale en js      inflating  angular         angular locale eo   js      inflating  angular         angular locale eo js      inflating  angular         angular locale es   js      inflating  angular         angular locale es ar js      inflating  angular         angular locale es bo js      inflating  angular         angular locale es cl js      inflating  angular         angular locale es co js      inflating  angular         angular locale es cr js      inflating  angular         angular locale es cu js      inflating  angular         angular locale es do js      inflating  angular         angular locale es ea js      inflating  angular         angular locale es ec js      inflating  angular         angular locale es es js      inflating  angular         angular locale es gq js      inflating  angular         angular locale es gt js      inflating  angular         angular locale es hn js      inflating  angular         angular locale es ic js      inflating  angular         angular locale es mx js      inflating  angular         angular locale es ni js      inflating  angular         angular locale es pa js      inflating  angular         angular locale es pe js      inflating  angular         angular locale es ph js      inflating  angular         angular locale es pr js      inflating  angular         angular locale es py js      inflating  angular         angular locale es sv js      inflating  angular         angular locale es us js      inflating  angular         angular locale es uy js      inflating  angular         angular locale es ve js      inflating  angular         angular locale es js      inflating  angular         angular locale et ee js      inflating  angular         angular locale et js      inflating  angular         angular locale eu es js      inflating  angular         angular locale eu js      inflating  angular         angular locale ewo cm js      inflating  angular         angular locale ewo js      inflating  angular         angular locale fa af js      inflating  angular         angular locale fa ir js      inflating  angular         angular locale fa js      inflating  angular         angular locale ff cm js      inflating  angular         angular locale ff gn js      inflating  angular         angular locale ff mr js      inflating  angular         angular locale ff sn js      inflating  angular         angular locale ff js      inflating  angular         angular locale fi fi js      inflating  angular         angular locale fi js      inflating  angular         angular locale fil ph js      inflating  angular         angular locale fil js      inflating  angular         angular locale fo fo js      inflating  angular         angular locale fo js      inflating  angular         angular locale fr be js      inflating  angular         angular locale fr bf js      inflating  angular         angular locale fr bi js      inflating  angular         angular locale fr bj js      inflating  angular         angular locale fr bl js      inflating  angular         angular locale fr ca js      inflating  angular         angular locale fr cd js      inflating  angular         angular locale fr cf js      inflating  angular         angular locale fr cg js      inflating  angular         angular locale fr ch js      inflating  angular         angular locale fr ci js      inflating  angular         angular locale fr cm js      inflating  angular         angular locale fr dj js      inflating  angular         angular locale fr dz js      inflating  angular         angular locale fr fr js      inflating  angular         angular locale fr ga js      inflating  angular         angular locale fr gf js      inflating  angular         angular locale fr gn js      inflating  angular         angular locale fr gp js      inflating  angular         angular locale fr gq js      inflating  angular         angular locale fr ht js      inflating  angular         angular locale fr km js      inflating  angular         angular locale fr lu js      inflating  angular         angular locale fr ma js      inflating  angular         angular locale fr mc js      inflating  angular         angular locale fr mf js      inflating  angular         angular locale fr mg js      inflating  angular         angular locale fr ml js      inflating  angular         angular locale fr mq js      inflating  angular         angular locale fr mr js      inflating  angular         angular locale fr mu js      inflating  angular         angular locale fr nc js      inflating  angular         angular locale fr ne js      inflating  angular         angular locale fr pf js      inflating  angular         angular locale fr pm js      inflating  angular         angular locale fr re js      inflating  angular         angular locale fr rw js      inflating  angular         angular locale fr sc js      inflating  angular         angular locale fr sn js      inflating  angular         angular locale fr sy js      inflating  angular         angular locale fr td js      inflating  angular         angular locale fr tg js      inflating  angular         angular locale fr tn js      inflating  angular         angular locale fr vu js      inflating  angular         angular locale fr wf js      inflating  angular         angular locale fr yt js      inflating  angular         angular locale fr js      inflating  angular         angular locale fur it js      inflating  angular         angular locale fur js      inflating  angular         angular locale fy nl js      inflating  angular         angular locale fy js      inflating  angular         angular locale ga ie js      inflating  angular         angular locale ga js      inflating  angular         angular locale gd gb js      inflating  angular         angular locale gd js      inflating  angular         angular locale gl es js      inflating  angular         angular locale gl js      inflating  angular         angular locale gsw ch js      inflating  angular         angular locale gsw fr js      inflating  angular         angular locale gsw li js      inflating  angular         angular locale gsw js      inflating  angular         angular locale gu in js      inflating  angular         angular locale gu js      inflating  angular         angular locale guz ke js      inflating  angular         angular locale guz js      inflating  angular         angular locale gv im js      inflating  angular         angular locale gv js      inflating  angular         angular locale ha latn gh js      inflating  angular         angular locale ha latn ne js      inflating  angular         angular locale ha latn ng js      inflating  angular         angular locale ha latn js      inflating  angular         angular locale ha js      inflating  angular         angular locale haw us js      inflating  angular         angular locale haw js      inflating  angular         angular locale he il js      inflating  angular         angular locale he js      inflating  angular         angular locale hi in js      inflating  angular         angular locale hi js      inflating  angular         angular locale hr ba js      inflating  angular         angular locale hr hr js      inflating  angular         angular locale hr js      inflating  angular         angular locale hsb de js      inflating  angular         angular locale hsb js      inflating  angular         angular locale hu hu js      inflating  angular         angular locale hu js      inflating  angular         angular locale hy am js      inflating  angular         angular locale hy js      inflating  angular         angular locale ia fr js      inflating  angular         angular locale ia js      inflating  angular         angular locale id id js      inflating  angular         angular locale id js      inflating  angular         angular locale ig ng js      inflating  angular         angular locale ig js      inflating  angular         angular locale ii cn js      inflating  angular         angular locale ii js      inflating  angular         angular locale in js      inflating  angular         angular locale is is js      inflating  angular         angular locale is js      inflating  angular         angular locale it ch js      inflating  angular         angular locale it it js      inflating  angular         angular locale it sm js      inflating  angular         angular locale it js      inflating  angular         angular locale iw js      inflating  angular         angular locale ja jp js      inflating  angular         angular locale ja js      inflating  angular         angular locale jgo cm js      inflating  angular         angular locale jgo js      inflating  angular         angular locale jmc tz js      inflating  angular         angular locale jmc js      inflating  angular         angular locale ka ge js      inflating  angular         angular locale ka js      inflating  angular         angular locale kab dz js      inflating  angular         angular locale kab js      inflating  angular         angular locale kam ke js      inflating  angular         angular locale kam js      inflating  angular         angular locale kde tz js      inflating  angular         angular locale kde js      inflating  angular         angular locale kea cv js      inflating  angular         angular locale kea js      inflating  angular         angular locale khq ml js      inflating  angular         angular locale khq js      inflating  angular         angular locale ki ke js      inflating  angular         angular locale ki js      inflating  angular         angular locale kk cyrl kz js      inflating  angular         angular locale kk cyrl js      inflating  angular         angular locale kk js      inflating  angular         angular locale kkj cm js      inflating  angular         angular locale kkj js      inflating  angular         angular locale kl gl js      inflating  angular         angular locale kl js      inflating  angular         angular locale kln ke js      inflating  angular         angular locale kln js      inflating  angular         angular locale km kh js      inflating  angular         angular locale km js      inflating  angular         angular locale kn in js      inflating  angular         angular locale kn js      inflating  angular         angular locale ko kp js      inflating  angular         angular locale ko kr js      inflating  angular         angular locale ko js      inflating  angular         angular locale kok in js      inflating  angular         angular locale kok js      inflating  angular         angular locale ks arab in js      inflating  angular         angular locale ks arab js      inflating  angular         angular locale ks js      inflating  angular         angular locale ksb tz js      inflating  angular         angular locale ksb js      inflating  angular         angular locale ksf cm js      inflating  angular         angular locale ksf js      inflating  angular         angular locale ksh de js      inflating  angular         angular locale ksh js      inflating  angular         angular locale kw gb js      inflating  angular         angular locale kw js      inflating  angular         angular locale ky cyrl kg js      inflating  angular         angular locale ky cyrl js      inflating  angular         angular locale ky js      inflating  angular         angular locale lag tz js      inflating  angular         angular locale lag js      inflating  angular         angular locale lb lu js      inflating  angular         angular locale lb js      inflating  angular         angular locale lg ug js      inflating  angular         angular locale lg js      inflating  angular         angular locale lkt us js      inflating  angular         angular locale lkt js      inflating  angular         angular locale ln ao js      inflating  angular         angular locale ln cd js      inflating  angular         angular locale ln cf js      inflating  angular         angular locale ln cg js      inflating  angular         angular locale ln js      inflating  angular         angular locale lo la js      inflating  angular         angular locale lo js      inflating  angular         angular locale lt lt js      inflating  angular         angular locale lt js      inflating  angular         angular locale lu cd js      inflating  angular         angular locale lu js      inflating  angular         angular locale luo ke js      inflating  angular         angular locale luo js      inflating  angular         angular locale luy ke js      inflating  angular         angular locale luy js      inflating  angular         angular locale lv lv js      inflating  angular         angular locale lv js      inflating  angular         angular locale mas ke js      inflating  angular         angular locale mas tz js      inflating  angular         angular locale mas js      inflating  angular         angular locale mer ke js      inflating  angular         angular locale mer js      inflating  angular         angular locale mfe mu js      inflating  angular         angular locale mfe js      inflating  angular         angular locale mg mg js      inflating  angular         angular locale mg js      inflating  angular         angular locale mgh mz js      inflating  angular         angular locale mgh js      inflating  angular         angular locale mgo cm js      inflating  angular         angular locale mgo js      inflating  angular         angular locale mk mk js      inflating  angular         angular locale mk js      inflating  angular         angular locale ml in js      inflating  angular         angular locale ml js      inflating  angular         angular locale mn cyrl mn js      inflating  angular         angular locale mn cyrl js      inflating  angular         angular locale mn js      inflating  angular         angular locale mr in js      inflating  angular         angular locale mr js      inflating  angular         angular locale ms latn bn js      inflating  angular         angular locale ms latn my js      inflating  angular         angular locale ms latn sg js      inflating  angular         angular locale ms latn js      inflating  angular         angular locale ms js      inflating  angular         angular locale mt mt js      inflating  angular         angular locale mt js      inflating  angular         angular locale mua cm js      inflating  angular         angular locale mua js      inflating  angular         angular locale my mm js      inflating  angular         angular locale my js      inflating  angular         angular locale naq na js      inflating  angular         angular locale naq js      inflating  angular         angular locale nb no js      inflating  angular         angular locale nb sj js      inflating  angular         angular locale nb js      inflating  angular         angular locale nd zw js      inflating  angular         angular locale nd js      inflating  angular         angular locale ne in js      inflating  angular         angular locale ne np js      inflating  angular         angular locale ne js      inflating  angular         angular locale nl aw js      inflating  angular         angular locale nl be js      inflating  angular         angular locale nl bq js      inflating  angular         angular locale nl cw js      inflating  angular         angular locale nl nl js      inflating  angular         angular locale nl sr js      inflating  angular         angular locale nl sx js      inflating  angular         angular locale nl js      inflating  angular         angular locale nmg cm js      inflating  angular         angular locale nmg js      inflating  angular         angular locale nn no js      inflating  angular         angular locale nn js      inflating  angular         angular locale nnh cm js      inflating  angular         angular locale nnh js      inflating  angular         angular locale no no js      inflating  angular         angular locale no js      inflating  angular         angular locale nr za js      inflating  angular         angular locale nr js      inflating  angular         angular locale nso za js      inflating  angular         angular locale nso js      inflating  angular         angular locale nus sd js      inflating  angular         angular locale nus js      inflating  angular         angular locale nyn ug js      inflating  angular         angular locale nyn js      inflating  angular         angular locale om et js      inflating  angular         angular locale om ke js      inflating  angular         angular locale om js      inflating  angular         angular locale or in js      inflating  angular         angular locale or js      inflating  angular         angular locale os ge js      inflating  angular         angular locale os ru js      inflating  angular         angular locale os js      inflating  angular         angular locale pa arab pk js      inflating  angular         angular locale pa arab js      inflating  angular         angular locale pa guru in js      inflating  angular         angular locale pa guru js      inflating  angular         angular locale pa js      inflating  angular         angular locale pl pl js      inflating  angular         angular locale pl js      inflating  angular         angular locale ps af js      inflating  angular         angular locale ps js      inflating  angular         angular locale pt ao js      inflating  angular         angular locale pt br js      inflating  angular         angular locale pt cv js      inflating  angular         angular locale pt gw js      inflating  angular         angular locale pt mo js      inflating  angular         angular locale pt mz js      inflating  angular         angular locale pt pt js      inflating  angular         angular locale pt st js      inflating  angular         angular locale pt tl js      inflating  angular         angular locale pt js      inflating  angular         angular locale qu bo js      inflating  angular         angular locale qu ec js      inflating  angular         angular locale qu pe js      inflating  angular         angular locale qu js      inflating  angular         angular locale rm ch js      inflating  angular         angular locale rm js      inflating  angular         angular locale rn bi js      inflating  angular         angular locale rn js      inflating  angular         angular locale ro md js      inflating  angular         angular locale ro ro js      inflating  angular         angular locale ro js      inflating  angular         angular locale rof tz js      inflating  angular         angular locale rof js      inflating  angular         angular locale ru by js      inflating  angular         angular locale ru kg js      inflating  angular         angular locale ru kz js      inflating  angular         angular locale ru md js      inflating  angular         angular locale ru ru js      inflating  angular         angular locale ru ua js      inflating  angular         angular locale ru js      inflating  angular         angular locale rw rw js      inflating  angular         angular locale rw js      inflating  angular         angular locale rwk tz js      inflating  angular         angular locale rwk js      inflating  angular         angular locale sah ru js      inflating  angular         angular locale sah js      inflating  angular         angular locale saq ke js      inflating  angular         angular locale saq js      inflating  angular         angular locale sbp tz js      inflating  angular         angular locale sbp js      inflating  angular         angular locale se fi js      inflating  angular         angular locale se no js      inflating  angular         angular locale se se js      inflating  angular         angular locale se js      inflating  angular         angular locale seh mz js      inflating  angular         angular locale seh js      inflating  angular         angular locale ses ml js      inflating  angular         angular locale ses js      inflating  angular         angular locale sg cf js      inflating  angular         angular locale sg js      inflating  angular         angular locale shi latn ma js      inflating  angular         angular locale shi latn js      inflating  angular         angular locale shi tfng ma js      inflating  angular         angular locale shi tfng js      inflating  angular         angular locale shi js      inflating  angular         angular locale si lk js      inflating  angular         angular locale si js      inflating  angular         angular locale sk sk js      inflating  angular         angular locale sk js      inflating  angular         angular locale sl si js      inflating  angular         angular locale sl js      inflating  angular         angular locale smn fi js      inflating  angular         angular locale smn js      inflating  angular         angular locale sn zw js      inflating  angular         angular locale sn js      inflating  angular         angular locale so dj js      inflating  angular         angular locale so et js      inflating  angular         angular locale so ke js      inflating  angular         angular locale so so js      inflating  angular         angular locale so js      inflating  angular         angular locale sq al js      inflating  angular         angular locale sq mk js      inflating  angular         angular locale sq xk js      inflating  angular         angular locale sq js      inflating  angular         angular locale sr cyrl ba js      inflating  angular         angular locale sr cyrl me js      inflating  angular         angular locale sr cyrl rs js      inflating  angular         angular locale sr cyrl xk js      inflating  angular         angular locale sr cyrl js      inflating  angular         angular locale sr latn ba js      inflating  angular         angular locale sr latn me js      inflating  angular         angular locale sr latn rs js      inflating  angular         angular locale sr latn xk js      inflating  angular         angular locale sr latn js      inflating  angular         angular locale sr js      inflating  angular         angular locale ss sz js      inflating  angular         angular locale ss za js      inflating  angular         angular locale ss js      inflating  angular         angular locale ssy er js      inflating  angular         angular locale ssy js      inflating  angular         angular locale st ls js      inflating  angular         angular locale st za js      inflating  angular         angular locale st js      inflating  angular         angular locale sv ax js      inflating  angular         angular locale sv fi js      inflating  angular         angular locale sv se js      inflating  angular         angular locale sv js      inflating  angular         angular locale sw ke js      inflating  angular         angular locale sw tz js      inflating  angular         angular locale sw ug js      inflating  angular         angular locale sw js      inflating  angular         angular locale swc cd js      inflating  angular         angular locale swc js      inflating  angular         angular locale ta in js      inflating  angular         angular locale ta lk js      inflating  angular         angular locale ta my js      inflating  angular         angular locale ta sg js      inflating  angular         angular locale ta js      inflating  angular         angular locale te in js      inflating  angular         angular locale te js      inflating  angular         angular locale teo ke js      inflating  angular         angular locale teo ug js      inflating  angular         angular locale teo js      inflating  angular         angular locale tg cyrl tj js      inflating  angular         angular locale tg cyrl js      inflating  angular         angular locale tg js      inflating  angular         angular locale th th js      inflating  angular         angular locale th js      inflating  angular         angular locale ti er js      inflating  angular         angular locale ti et js      inflating  angular         angular locale ti js      inflating  angular         angular locale tig er js      inflating  angular         angular locale tig js      inflating  angular         angular locale tl js      inflating  angular         angular locale tn bw js      inflating  angular         angular locale tn za js      inflating  angular         angular locale tn js      inflating  angular         angular locale to to js      inflating  angular         angular locale to js      inflating  angular         angular locale tr cy js      inflating  angular         angular locale tr tr js      inflating  angular         angular locale tr js      inflating  angular         angular locale ts za js      inflating  angular         angular locale ts js      inflating  angular         angular locale twq ne js      inflating  angular         angular locale twq js      inflating  angular         angular locale tzm latn ma js      inflating  angular         angular locale tzm latn js      inflating  angular         angular locale tzm js      inflating  angular         angular locale ug arab cn js      inflating  angular         angular locale ug arab js      inflating  angular         angular locale ug js      inflating  angular         angular locale uk ua js      inflating  angular         angular locale uk js      inflating  angular         angular locale ur in js      inflating  angular         angular locale ur pk js      inflating  angular         angular locale ur js      inflating  angular         angular locale uz arab af js      inflating  angular         angular locale uz arab js      inflating  angular         angular locale uz cyrl uz js      inflating  angular         angular locale uz cyrl js      inflating  angular         angular locale uz latn uz js      inflating  angular         angular locale uz latn js      inflating  angular         angular locale uz js      inflating  angular         angular locale vai latn lr js      inflating  angular         angular locale vai latn js      inflating  angular         angular locale vai vaii lr js      inflating  angular         angular locale vai vaii js      inflating  angular         angular locale vai js      inflating  angular         angular locale ve za js      inflating  angular         angular locale ve js      inflating  angular         angular locale vi vn js      inflating  angular         angular locale vi js      inflating  angular         angular locale vo   js      inflating  angular         angular locale vo js      inflating  angular         angular locale vun tz js      inflating  angular         angular locale vun js      inflating  angular         angular locale wae ch js      inflating  angular         angular locale wae js      inflating  angular         angular locale wal et js      inflating  angular         angular locale wal js      inflating  angular         angular locale xh za js      inflating  angular         angular locale xh js      inflating  angular         angular locale xog ug js      inflating  angular         angular locale xog js      inflating  angular         angular locale yav cm js      inflating  angular         angular locale yav js      inflating  angular         angular locale yi   js      inflating  angular         angular locale yi js      inflating  angular         angular locale yo bj js      inflating  angular         angular locale yo ng js      inflating  angular         angular locale yo js      inflating  angular         angular locale zgh ma js      inflating  angular         angular locale zgh js      inflating  angular         angular locale zh cn js      inflating  angular         angular locale zh hans cn js      inflating  angular         angular locale zh hans hk js      inflating  angular         angular locale zh hans mo js      inflating  angular         angular locale zh hans sg js      inflating  angular         angular locale zh hans js      inflating  angular         angular locale zh hant hk js      inflating  angular         angular locale zh hant mo js      inflating  angular         angular locale zh hant tw js      inflating  angular         angular locale zh hant js      inflating  angular         angular locale zh hk js      inflating  angular         angular locale zh tw js      inflating  angular         angular locale zh js      inflating  angular         angular locale zu za js      inflating  angular         angular locale zu js       creating  angular         nglocale     inflating  angular       version json      inflating  angular       version txt     cd angularjs    unzip  u ui utils       zip   archive   ui utils       zip        creating  ui utils           inflating  ui utils        travis yml      inflating  ui utils       changelog md      inflating  ui utils       bower json      inflating  ui utils       ui utils ieshiv js      inflating  ui utils       ui utils ieshiv min js      inflating  ui utils       ui utils js      inflating  ui utils       ui utils min js    if     then mkdir  p bootstrap            cd bootstrap          unzip  u    bootstrap       dist zip    mv dist        rmdir dist     fi  archive      bootstrap       dist zip     creating  dist      creating  dist css     inflating  dist css bootstrap theme css      inflating  dist css bootstrap theme css map      inflating  dist css bootstrap theme min css      inflating  dist css bootstrap css      inflating  dist css bootstrap css map      inflating  dist css bootstrap min css       creating  dist fonts     inflating  dist fonts glyphicons halflings regular eot      inflating  dist fonts glyphicons halflings regular svg      inflating  dist fonts glyphicons halflings regular ttf      inflating  dist fonts glyphicons halflings regular woff       creating  dist js     inflating  dist js bootstrap js        inflating  dist js bootstrap min js      inflating  dist js npm js            mkdir  p     cd      unzip  u            zip   archive              zip    inflating  license                     inflating    js                       inflating    min js                 make   leaving directory   tmp nagioscore html   if    then    		cd   module    make     	fi  make   entering directory   tmp nagioscore module   gcc  i    fpic  g     dhave config h  o helloworld o helloworld c  shared    make   leaving directory   tmp nagioscore module   cd   worker    make all  make   entering directory   tmp nagioscore worker   cd   ping    make all  make   entering directory   tmp nagioscore worker ping   gcc  i    i       include  i        g     dhave config h  o worker ping worker ping c  l       lib  l nagios    make   leaving directory   tmp nagioscore worker ping   make   leaving directory   tmp nagioscore worker         compile finished        if the main program and cgis compiled without any errors  you  can continue with installing nagios as follows  type  make   without any arguments for a list of all possible options        make install         this installs the main program  cgis  and html files      make install init         this installs the init script in  etc init      make install commandmode         this installs and configures permissions on the         directory for holding the external command file      make install config         this installs  sample  config files in  usr local nagios etc         you ll have to modify these sample files before you can         use nagios   read the html documentation for more info         on doing this   pay particular attention to the docs on         object configuration files  as they determine what how         things get monitored       make install webconf         this installs the apache config file for the nagios         web interface      make install exfoliation         this installs the exfoliation theme for the nagios         web interface      make install classicui         this installs the classic theme for the nagios         web interface          support notes                                                if you have questions about configuring or running nagios   please make sure that you            look at the sample config files         read the documentation on the nagios library at                   before you post a question to one of the mailing lists   also make sure to include pertinent information that could  help others help you   this might include            what version of nagios you are using         what version of the plugins you are using         relevant snippets from your config files         relevant error messages from the nagios log file    for more information on obtaining support for nagios  visit                                                                                  enjoy        useradd nagios     usermod  a  g nagios apache          make install  cd   base    make install  make   entering directory   tmp nagioscore base   make install basic  make   entering directory   tmp nagioscore base    usr bin install  c  m    o nagios  g nagios  d  usr local nagios bin   usr bin install  c  m    o nagios  g nagios nagios  usr local nagios bin   usr bin install  c  m    o nagios  g nagios nagiostats  usr local nagios bin  make   leaving directory   tmp nagioscore base   make strip post install  make   entering directory   tmp nagioscore base    usr bin strip  usr local nagios bin nagios   usr bin strip  usr local nagios bin nagiostats  make   leaving directory   tmp nagioscore base   make   leaving directory   tmp nagioscore base   cd   cgi    make install  make   entering directory   tmp nagioscore cgi   make install basic  make   entering directory   tmp nagioscore cgi    usr bin install  c  m    o nagios  g nagios  d  usr local nagios bin  for file in   cgi  do    		 usr bin install  c  m    o nagios  g nagios  file  usr local nagios bin     	done  make   leaving directory   tmp nagioscore cgi   make strip post install  make   entering directory   tmp nagioscore cgi   for file in   cgi  do    		 usr bin strip  usr local nagios bin  file     	done  make   leaving directory   tmp nagioscore cgi   make   leaving directory   tmp nagioscore cgi   cd   html    make install  make   entering directory   tmp nagioscore html    usr bin install  c  m    o nagios  g nagios  d  usr local nagios share   usr bin install  c  m    o nagios  g nagios  d  usr local nagios share media   usr bin install  c  m    o nagios  g nagios  d  usr local nagios share stylesheets   usr bin install  c  m    o nagios  g nagios  d  usr local nagios share contexthelp   usr bin install  c  m    o nagios  g nagios  d  usr local nagios share docs   usr bin install  c  m    o nagios  g nagios  d  usr local nagios share docs images   usr bin install  c  m    o nagios  g nagios  d  usr local nagios share js   usr bin install  c  m    o nagios  g nagios  d  usr local nagios share images   usr bin install  c  m    o nagios  g nagios  d  usr local nagios share images logos   usr bin install  c  m    o nagios  g nagios  d  usr local nagios share includes   usr bin install  c  m    o nagios  g nagios  d  usr local nagios share ssi   usr bin install  c  m    o nagios  g nagios  d  usr local nagios share angularjs   usr bin install  c  m    o nagios  g nagios  d  usr local nagios share angularjs angular         usr bin install  c  m    o nagios  g nagios  d  usr local nagios share angularjs ui utils         usr bin install  c  m    o nagios  g nagios  d  usr local nagios share bootstrap         usr bin install  c  m    o nagios  g nagios  d  usr local nagios share bootstrap       css   usr bin install  c  m    o nagios  g nagios  d  usr local nagios share     usr bin install  c  m    o nagios  g nagios  d  usr local nagios share spin   usr bin install  c  m    o nagios  g nagios robots txt  usr local nagios share  rm  f  usr local nagios share index html  rm  f  usr local nagios share main html  rm  f  usr local nagios share side html  rm  f  usr local nagios share map html  rm  f  usr local nagios share rss    rm  rf  usr local nagios share include rss   usr bin install  c  m    o nagios  g nagios jsonquery html  usr local nagios share   usr bin install  c  m    o nagios  g nagios graph header html  usr local nagios share   usr bin install  c  m    o nagios  g nagios histogram html  usr local nagios share   usr bin install  c  m    o nagios  g nagios histogram form html  usr local nagios share   usr bin install  c  m    o nagios  g nagios histogram graph html  usr local nagios share   usr bin install  c  m    o nagios  g nagios histogram links html  usr local nagios share   usr bin install  c  m    o nagios  g nagios infobox html  usr local nagios share   usr bin install  c  m    o nagios  g nagios map php  usr local nagios share   usr bin install  c  m    o nagios  g nagios map directive html  usr local nagios share   usr bin install  c  m    o nagios  g nagios map form html  usr local nagios share   usr bin install  c  m    o nagios  g nagios map links html  usr local nagios share   usr bin install  c  m    o nagios  g nagios map popup html  usr local nagios share   usr bin install  c  m    o nagios  g nagios trends html  usr local nagios share   usr bin install  c  m    o nagios  g nagios trends form html  usr local nagios share   usr bin install  c  m    o nagios  g nagios trends graph html  usr local nagios share   usr bin install  c  m    o nagios  g nagios trends host yaxis html  usr local nagios share   usr bin install  c  m    o nagios  g nagios trends links html  usr local nagios share   usr bin install  c  m    o nagios  g nagios trends service yaxis html  usr local nagios share  for file in   php     	do  usr bin install  c  m    o nagios  g nagios  file  usr local nagios share  done  for file in stylesheets   css     	do  usr bin install  c  m    o nagios  g nagios  file  usr local nagios share stylesheets  done  for file in contexthelp   html     	do  usr bin install  c  m    o nagios  g nagios  file  usr local nagios share contexthelp  done  for file in js   js     	do  usr bin install  c  m    o nagios  g nagios  file  usr local nagios share js  done  for file in images   gif     	do  usr bin install  c  m    o nagios  g nagios  file  usr local nagios share images  done  for file in images   jpg     	do  usr bin install  c  m    o nagios  g nagios  file  usr local nagios share images  done  for file in images   png     	do  usr bin install  c  m    o nagios  g nagios  file  usr local nagios share images  done  for file in images   ico     	do  usr bin install  c  m    o nagios  g nagios  file  usr local nagios share images  done  for file in images logos         	do  usr bin install  c  m    o nagios  g nagios  file  usr local nagios share images logos  done  for file in includes         	do  usr bin install  c  m    o nagios  g nagios  file  usr local nagios share includes  done   usr bin install  c  m    o nagios  g nagios angularjs angular       angular min js   usr local nagios share angularjs angular         usr bin install  c  m    o nagios  g nagios angularjs angular       angular min js map   usr local nagios share angularjs angular         usr bin install  c  m    o nagios  g nagios angularjs ui bootstrap tpls       min js   usr local nagios share angularjs   usr bin install  c  m    o nagios  g nagios angularjs ui utils       ui utils js    usr local nagios share angularjs ui utils         usr bin install  c  m    o nagios  g nagios bootstrap       css bootstrap min css  usr local nagios share bootstrap       css   usr bin install  c  m    o nagios  g nagios bootstrap       css bootstrap theme min css  usr local nagios share bootstrap       css   usr bin install  c  m    o nagios  g nagios     min js  usr local nagios share     usr bin install  c  m    o nagios  g nagios spin spin min js  usr local nagios share spin  make   leaving directory   tmp nagioscore html   make install exfoliation  make   entering directory   tmp nagioscore         exfoliation theme installed      note  use  make install classicui  to revert to classic nagios theme    make   leaving directory   tmp nagioscore   make install basic  make   entering directory   tmp nagioscore    usr bin install  c  m    o nagios  g nagios  d  usr local nagios libexec   usr bin install  c  m    o nagios  g nagios  d  usr local nagios var   usr bin install  c  m    o nagios  g nagios  d  usr local nagios var archives   usr bin install  c  m    o nagios  g nagios  d  usr local nagios var spool checkresults  chmod g s  usr local nagios var spool checkresults        main program  cgis and html files installed        you can continue with installing nagios as follows  type  make   without any arguments for a list of all possible options        make install init         this installs the init script in  etc init      make install commandmode         this installs and configures permissions on the         directory for holding the external command file      make install config         this installs sample config files in  usr local nagios etc    make   leaving directory   tmp nagioscore      make install init   usr bin install  c  m    o root  g root startup rh upstart init  etc init nagios conf   usr bin install  cannot stat  startup rh upstart init   no such file or directory  make        error       ,0
168335,14146115157.0,IssuesEvent,2020-11-10 18:43:31,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: add release note for defaulting to -mod=readonly,Documentation NeedsFix release-blocker,"As noted in https://github.com/golang/go/issues/40728#issuecomment-723561987, the change to default to `-mod=readonly` for Go 1.16 has a substantial impact on user workflows, so it should have a release note before the beta.

(The main issue is tagged as a proposal, so rather than reopening that issue and disrupting the proposal automation, I'm filing a separate doc issue.)

CC @jayconrod @matloob @mvdan ",1.0,"cmd/go: add release note for defaulting to -mod=readonly - As noted in https://github.com/golang/go/issues/40728#issuecomment-723561987, the change to default to `-mod=readonly` for Go 1.16 has a substantial impact on user workflows, so it should have a release note before the beta.

(The main issue is tagged as a proposal, so rather than reopening that issue and disrupting the proposal automation, I'm filing a separate doc issue.)

CC @jayconrod @matloob @mvdan ",1,cmd go  add release note for defaulting to  mod readonly   as noted in   the change to default to   mod readonly  for go     has a substantial impact on user workflows  so it should have a release note before the beta      the main issue is tagged as a proposal  so rather than reopening that issue and disrupting the proposal automation  i m filing a separate doc issue      cc  jayconrod  matloob  mvdan ,1
106312,11483767345.0,IssuesEvent,2020-02-11 01:00:36,golang/go,https://api.github.com/repos/golang/go,closed,"crypto/elliptic: document what the ""canonical names"" for curves are",Documentation NeedsFix,"I needed to write code to distinguish whether a `pk *ecdsa.PublicKey` refers to a point on P-256, P-384, P-521, or some other curve. It looks like the proper way to do this is to switch on `pk.Curve().Name`, which provides ""the canonical name of the curve"". (Aside: If this is *not* the best way to do this, please let me know.)

However, I'm aware of many possible [""canonical""](https://xkcd.com/927/) names for P-256; for example, ""P256"" (the package elliptic function name), ""P-256"" (what package elliptic's documentation calls it), ""Curve P-256"" (what FIPS 186-3 calls it), ""NIST P256"" (what the TCG Algorithm Registry calls it), ""prime256v1"" (what RFC 3279 calls it), ""secp256r1"" (what RFC 5480 calls it), ""nistp256"" (what RFC 5656 calls it), etc.

I had to inspect package elliptic's source to figure out what to expect `pk.Curve().Name` to return.

/cc @agl @FiloSottile ",1.0,"crypto/elliptic: document what the ""canonical names"" for curves are - I needed to write code to distinguish whether a `pk *ecdsa.PublicKey` refers to a point on P-256, P-384, P-521, or some other curve. It looks like the proper way to do this is to switch on `pk.Curve().Name`, which provides ""the canonical name of the curve"". (Aside: If this is *not* the best way to do this, please let me know.)

However, I'm aware of many possible [""canonical""](https://xkcd.com/927/) names for P-256; for example, ""P256"" (the package elliptic function name), ""P-256"" (what package elliptic's documentation calls it), ""Curve P-256"" (what FIPS 186-3 calls it), ""NIST P256"" (what the TCG Algorithm Registry calls it), ""prime256v1"" (what RFC 3279 calls it), ""secp256r1"" (what RFC 5480 calls it), ""nistp256"" (what RFC 5656 calls it), etc.

I had to inspect package elliptic's source to figure out what to expect `pk.Curve().Name` to return.

/cc @agl @FiloSottile ",1,crypto elliptic  document what the  canonical names  for curves are   i needed to write code to distinguish whether a  pk  ecdsa publickey  refers to a point on p    p    p    or some other curve  it looks like the proper way to do this is to switch on  pk curve   name   which provides  the canonical name of the curve    aside  if this is  not  the best way to do this  please let me know      however  i m aware of many possible     names for p    for example       the package elliptic function name    p     what package elliptic s documentation calls it    curve p     what fips     calls it    nist     what the tcg algorithm registry calls it        what rfc   calls it        what rfc   calls it        what rfc   calls it   etc     i had to inspect package elliptic s source to figure out what to expect  pk curve   name  to return      cc  agl  filosottile ,1
10342,3377540970.0,IssuesEvent,2015-11-25 04:25:01,golang/go,https://api.github.com/repos/golang/go,reopened,spec: docs for iota could give an example of incrementing over non-iota definitions,Documentation,"i.e. demonstrate the latter half of ""It is reset to 0 whenever the reserved word const appears in the source and increments after each ConstSpec."" with something like
```
const (
	s = ""a"" // increments iota
	c0 = iota // c0 == 1
	t = 5
	c1 = iota // c1 == 3
)
```
as this behaviour wasn't obvious to me (as a lazy reader who prefers looking at examples).",1.0,"spec: docs for iota could give an example of incrementing over non-iota definitions - i.e. demonstrate the latter half of ""It is reset to 0 whenever the reserved word const appears in the source and increments after each ConstSpec."" with something like
```
const (
	s = ""a"" // increments iota
	c0 = iota // c0 == 1
	t = 5
	c1 = iota // c1 == 3
)
```
as this behaviour wasn't obvious to me (as a lazy reader who prefers looking at examples).",1,spec  docs for iota could give an example of incrementing over non iota definitions   i e  demonstrate the latter half of  it is reset to   whenever the reserved word const appears in the source and increments after each constspec   with something like       const    	s    a     increments iota  	    iota            	t      	    iota                    as this behaviour wasn t obvious to me  as a lazy reader who prefers looking at examples  ,1
272884,20762116106.0,IssuesEvent,2022-03-15 17:03:02,golang/go,https://api.github.com/repos/golang/go,closed,doc: write Go 1.18 release notes,Documentation help wanted NeedsFix recurring umbrella,"Tracking bug for writing the Go 1.18 Release Notes.

The latest state on tip can be viewed at https://tip.golang.org/doc/go1.18.

When the Go 1.18 Release Notes are complete, this should be closed, and a similar issue should be made for the next release. Previous issues are #44513, #40700, #37419, #36878, #17929, #15810, #5929, etc.",1.0,"doc: write Go 1.18 release notes - Tracking bug for writing the Go 1.18 Release Notes.

The latest state on tip can be viewed at https://tip.golang.org/doc/go1.18.

When the Go 1.18 Release Notes are complete, this should be closed, and a similar issue should be made for the next release. Previous issues are #44513, #40700, #37419, #36878, #17929, #15810, #5929, etc.",1,doc  write go     release notes   tracking bug for writing the go     release notes     the latest state on tip can be viewed at      when the go     release notes are complete  this should be closed  and a similar issue should be made for the next release  previous issues are                             etc ,1
50010,7550638635.0,IssuesEvent,2018-04-18 17:32:43,golang/go,https://api.github.com/repos/golang/go,closed,reflect: documentation on NumMethod is incorrect,Documentation,"[Consider the following](https://play.golang.org/p/rsC-F8IYO8w):
```go
type iface interface {
	private()
	Public()
}
t := reflect.TypeOf((*iface)(nil)).Elem()
for i := 0; i < t.NumMethod(); i++ {
	fmt.Println(t.Method(i))
}
```

This currently prints:
```
{Public  func() <invalid Value> 0}
{private main func() <invalid Value> 1}
```

The documented behavior of `reflect.Type.NumMethod` is:
> NumMethod returns the number of **exported** methods in the value's method set.

However, you can clearly see that `private` is included as part of the count.

It seems to me that for `reflect.Interface`, the `NumMethod` does include unexported methods, while it excludes them for all other kinds.",1.0,"reflect: documentation on NumMethod is incorrect - [Consider the following](https://play.golang.org/p/rsC-F8IYO8w):
```go
type iface interface {
	private()
	Public()
}
t := reflect.TypeOf((*iface)(nil)).Elem()
for i := 0; i < t.NumMethod(); i++ {
	fmt.Println(t.Method(i))
}
```

This currently prints:
```
{Public  func() <invalid Value> 0}
{private main func() <invalid Value> 1}
```

The documented behavior of `reflect.Type.NumMethod` is:
> NumMethod returns the number of **exported** methods in the value's method set.

However, you can clearly see that `private` is included as part of the count.

It seems to me that for `reflect.Interface`, the `NumMethod` does include unexported methods, while it excludes them for all other kinds.",1,reflect  documentation on nummethod is incorrect           go  type iface interface    	private    	public       t    reflect typeof   iface  nil   elem    for i       i   t nummethod    i      	fmt println t method i              this currently prints         public  func          private main func                the documented behavior of  reflect type nummethod  is     nummethod returns the number of   exported   methods in the value s method set     however  you can clearly see that  private  is included as part of the count     it seems to me that for  reflect interface   the  nummethod  does include unexported methods  while it excludes them for all other kinds ,1
295328,22207963410.0,IssuesEvent,2022-06-07 16:23:52,golang/go,https://api.github.com/repos/golang/go,closed,go/doc: find a better home for Go documentation features like section headings,Documentation NeedsFix,"[fluhus/godoc-tricks](https://github.com/fluhus/godoc-tricks) describes several extended tricks for the Godoc renderer that remain relevant for https://pkg.go.dev.  Particularly notable is the technique described as [Titles](https://pkg.go.dev/github.com/fluhus/godoc-tricks#Titles), which can be thought of as naive section headings as demonstrated below with the word ""Limitations"":

```go
// CreditCard models a lender-backed payment instrument.
//
// Limitations
//
// The type provides no native validation against its issuer.  It is a dumb data type.
type CreditCard struct{}
```

To date this technique is not substantively mentioned in any of the following:

* https://blog.golang.org/godoc
* https://golang.org/pkg/go/doc/ (minor prosaic allusion)

Considering its utility for information presentation, anchoring, etc., I propose the feature earn proper documentation.  I tried to search for an existing bug for this, but the closest thing I could find was https://github.com/golang/go/issues/18342.  The correct approach would probably involve amending the previous documents somehow (or maybe another).",1.0,"go/doc: find a better home for Go documentation features like section headings - [fluhus/godoc-tricks](https://github.com/fluhus/godoc-tricks) describes several extended tricks for the Godoc renderer that remain relevant for https://pkg.go.dev.  Particularly notable is the technique described as [Titles](https://pkg.go.dev/github.com/fluhus/godoc-tricks#Titles), which can be thought of as naive section headings as demonstrated below with the word ""Limitations"":

```go
// CreditCard models a lender-backed payment instrument.
//
// Limitations
//
// The type provides no native validation against its issuer.  It is a dumb data type.
type CreditCard struct{}
```

To date this technique is not substantively mentioned in any of the following:

* https://blog.golang.org/godoc
* https://golang.org/pkg/go/doc/ (minor prosaic allusion)

Considering its utility for information presentation, anchoring, etc., I propose the feature earn proper documentation.  I tried to search for an existing bug for this, but the closest thing I could find was https://github.com/golang/go/issues/18342.  The correct approach would probably involve amending the previous documents somehow (or maybe another).",1,go doc  find a better home for go documentation features like section headings       describes several extended tricks for the godoc renderer that remain relevant for    particularly notable is the technique described as     which can be thought of as naive section headings as demonstrated below with the word  limitations         go     creditcard models a lender backed payment instrument          limitations         the type provides no native validation against its issuer   it is a dumb data type   type creditcard struct           to date this technique is not substantively mentioned in any of the following               minor prosaic allusion     considering its utility for information presentation  anchoring  etc   i propose the feature earn proper documentation   i tried to search for an existing bug for this  but the closest thing i could find was    the correct approach would probably involve amending the previous documents somehow  or maybe another  ,1
76489,9942996311.0,IssuesEvent,2019-07-03 14:58:17,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: cannot find module for path,Documentation NeedsFix,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
go version go1.12.6 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""/Users/tristian/go/bin""
GOCACHE=""/Users/tristian/Library/Caches/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/tristian/go""
GOPROXY=""""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.12.6/libexec""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/1.12.6/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/tristian/Repositories/github.com/triztian/my.binary.project/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/g1/v3hz1sm92nv7wbzpg3dx_h_h0000gp/T/go-build549198414=/tmp/go-build -gno-record-gcc-switches -fno-common""

</pre></details>

### What did you do?
Tried to build the executable after running `rm -rf $GOPATH/pkg`, I then ran `go mod download` and tried to do a build:

```
λ ~/Repositories/code.blockwave.com/blockwave/core.bin: go build -x -a -v
WORK=/var/folders/g1/v3hz1sm92nv7wbzpg3dx_h_h0000gp/T/go-build723678509
build code.blockwave.com/blockwave/core.bin: cannot find module for path code.blockwave.com/blockwave/core.components.engine/wave/plugin-master
```

After getting that error message, I ensured that the module is fetched and downloaded:
```
 λ ~/Repositories/code.blockwave.com/blockwave/core.bin: go get code.blockwave.com/blockwave/core.components.engine/wave/plugin-master
go: finding code.blockwave.com/blockwave/core.components.engine/wave/plugin-master latest
go: finding code.blockwave.com/blockwave/core.components.engine/wave latest
go: finding code.blockwave.com/blockwave/core.components.engine latest
```

Then I retried the build:
```
 λ ~/Repositories/code.blockwave.com/blockwave/core.bin: go build -x -a -v
WORK=/var/folders/g1/v3hz1sm92nv7wbzpg3dx_h_h0000gp/T/go-build629362765
build code.blockwave.com/blockwave/core.bin: cannot find module for path code.blockwave.com/blockwave/core.components.engine/wave/plugin-master
```

Same result, so I now tried cleaning the cache:

```
 λ ~/Repositories/code.blockwave.com/blockwave/core.bin: go clean -modcache
build code.blockwave.com/blockwave/core.bin: cannot find module for path code.blockwave.com/blockwave/core.components.engine/wave/plugin-master
```

I've also ran `go mod verify`, and it reports no issues:

```
λ ~/Repositories/code.blockwave.com/blockwave/core.bin (issue/blockwave.trunk.11): go mod verify
all modules verified
```
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

### What did you expect to see?

I expected to see a `core.bin` executable in my current directory.


### What did you see instead?

```
build code.blockwave.com/blockwave/core.bin: cannot find module for path code.blockwave.com/blockwave/core.components.engine/wave/plugin-master
```

---- 

I tried to reproduce the issue and to setup a project that mimics the structure of the one that I'm experiencing issues with but it seems to be specific to my setup:

 * Main Executable: https://github.com/triztian/my.binary.project
 * Library that uses cgo: https://github.com/triztian/my.special.library

However with such setup I'm able to produce a valid executable:

```
 λ ~/Repositories/github.com/triztian/my.binary.project (master): go build -v
 λ ~/Repositories/github.com/triztian/my.binary.project (master): ls
build_commands.txt	go.mod			main.go
cmd			go.sum			my.binary.project
```
And it runs correctly:

```
./my.binary.project
42
```

Is there a way for me to get more information about the specific package that is failing?",1.0,"cmd/go: cannot find module for path - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
go version go1.12.6 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""/Users/tristian/go/bin""
GOCACHE=""/Users/tristian/Library/Caches/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/tristian/go""
GOPROXY=""""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.12.6/libexec""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/1.12.6/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/tristian/Repositories/github.com/triztian/my.binary.project/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/g1/v3hz1sm92nv7wbzpg3dx_h_h0000gp/T/go-build549198414=/tmp/go-build -gno-record-gcc-switches -fno-common""

</pre></details>

### What did you do?
Tried to build the executable after running `rm -rf $GOPATH/pkg`, I then ran `go mod download` and tried to do a build:

```
λ ~/Repositories/code.blockwave.com/blockwave/core.bin: go build -x -a -v
WORK=/var/folders/g1/v3hz1sm92nv7wbzpg3dx_h_h0000gp/T/go-build723678509
build code.blockwave.com/blockwave/core.bin: cannot find module for path code.blockwave.com/blockwave/core.components.engine/wave/plugin-master
```

After getting that error message, I ensured that the module is fetched and downloaded:
```
 λ ~/Repositories/code.blockwave.com/blockwave/core.bin: go get code.blockwave.com/blockwave/core.components.engine/wave/plugin-master
go: finding code.blockwave.com/blockwave/core.components.engine/wave/plugin-master latest
go: finding code.blockwave.com/blockwave/core.components.engine/wave latest
go: finding code.blockwave.com/blockwave/core.components.engine latest
```

Then I retried the build:
```
 λ ~/Repositories/code.blockwave.com/blockwave/core.bin: go build -x -a -v
WORK=/var/folders/g1/v3hz1sm92nv7wbzpg3dx_h_h0000gp/T/go-build629362765
build code.blockwave.com/blockwave/core.bin: cannot find module for path code.blockwave.com/blockwave/core.components.engine/wave/plugin-master
```

Same result, so I now tried cleaning the cache:

```
 λ ~/Repositories/code.blockwave.com/blockwave/core.bin: go clean -modcache
build code.blockwave.com/blockwave/core.bin: cannot find module for path code.blockwave.com/blockwave/core.components.engine/wave/plugin-master
```

I've also ran `go mod verify`, and it reports no issues:

```
λ ~/Repositories/code.blockwave.com/blockwave/core.bin (issue/blockwave.trunk.11): go mod verify
all modules verified
```
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

### What did you expect to see?

I expected to see a `core.bin` executable in my current directory.


### What did you see instead?

```
build code.blockwave.com/blockwave/core.bin: cannot find module for path code.blockwave.com/blockwave/core.components.engine/wave/plugin-master
```

---- 

I tried to reproduce the issue and to setup a project that mimics the structure of the one that I'm experiencing issues with but it seems to be specific to my setup:

 * Main Executable: https://github.com/triztian/my.binary.project
 * Library that uses cgo: https://github.com/triztian/my.special.library

However with such setup I'm able to produce a valid executable:

```
 λ ~/Repositories/github.com/triztian/my.binary.project (master): go build -v
 λ ~/Repositories/github.com/triztian/my.binary.project (master): ls
build_commands.txt	go.mod			main.go
cmd			go.sum			my.binary.project
```
And it runs correctly:

```
./my.binary.project
42
```

Is there a way for me to get more information about the specific package that is failing?",1,cmd go  cannot find module for path            what version of go are you using   go version          go version       darwin             does this issue reproduce with the latest release     yes          what operating system and processor architecture are you using   go env          go env  output       go env  goarch      gobin   users tristian go bin   gocache   users tristian library caches go build   goexe     goflags     gohostarch      gohostos  darwin   goos  darwin   gopath   users tristian go   goproxy     gorace     goroot   usr local cellar go       libexec   gotmpdir     gotooldir   usr local cellar go       libexec pkg tool darwin     gccgo  gccgo   cc  clang   cxx  clang     cgo enabled      gomod   users tristian repositories github com triztian my binary project go mod   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders     h   t go    tmp go build  gno record gcc switches  fno common               what did you do   tried to build the executable after running  rm  rf  gopath pkg   i then ran  go mod download  and tried to do a build          λ   repositories code blockwave com blockwave core bin  go build  x  a  v  work  var folders     h   t go    build code blockwave com blockwave core bin  cannot find module for path code blockwave com blockwave core components engine wave plugin master         after getting that error message  i ensured that the module is fetched and downloaded         λ   repositories code blockwave com blockwave core bin  go get code blockwave com blockwave core components engine wave plugin master  go  finding code blockwave com blockwave core components engine wave plugin master latest  go  finding code blockwave com blockwave core components engine wave latest  go  finding code blockwave com blockwave core components engine latest         then i retried the build         λ   repositories code blockwave com blockwave core bin  go build  x  a  v  work  var folders     h   t go    build code blockwave com blockwave core bin  cannot find module for path code blockwave com blockwave core components engine wave plugin master         same result  so i now tried cleaning the cache           λ   repositories code blockwave com blockwave core bin  go clean  modcache  build code blockwave com blockwave core bin  cannot find module for path code blockwave com blockwave core components engine wave plugin master         i ve also ran  go mod verify   and it reports no issues          λ   repositories code blockwave com blockwave core bin  issue blockwave trunk     go mod verify  all modules verified             if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best              what did you expect to see     i expected to see a  core bin  executable in my current directory           what did you see instead          build code blockwave com blockwave core bin  cannot find module for path code blockwave com blockwave core components engine wave plugin master                  i tried to reproduce the issue and to setup a project that mimics the structure of the one that i m experiencing issues with but it seems to be specific to my setup        main executable        library that uses cgo       however with such setup i m able to produce a valid executable           λ   repositories github com triztian my binary project  master   go build  v   λ   repositories github com triztian my binary project  master   ls  build commands txt	go mod			main go  cmd			go sum			my binary project       and it runs correctly            my binary project            is there a way for me to get more information about the specific package that is failing ,1
69186,3296032278.0,IssuesEvent,2015-11-01 14:24:01,cs2103aug2015-w11-3j/main,https://api.github.com/repos/cs2103aug2015-w11-3j/main,closed,Logic: Better user feedback for filtering start/end dates,priority.medium type.task,Will check if is EoT for start/end and change the feedback accordingly,1.0,Logic: Better user feedback for filtering start/end dates - Will check if is EoT for start/end and change the feedback accordingly,0,logic  better user feedback for filtering start end dates   will check if is eot for start end and change the feedback accordingly,0
57909,8213405542.0,IssuesEvent,2018-09-04 19:26:58,golang/go,https://api.github.com/repos/golang/go,closed,"cmd/go: for go mod download, -dir option does not exist",Documentation NeedsFix modules,"### What version of Go are you using (`go version`)?

go version go1.11 linux/amd64

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

GOARCH=""amd64""
GOOS=""linux""

### What did you do?

$ echo $PWD
/home/mpl/src/perkeep.org
$ echo $GOPATH
/home/mpl
$ echo $GO111MODULE
on
$ go mod download -dir github.com/gopherjs/gopherjs
flag provided but not defined: -dir
usage: go mod download [-dir] [-json] [modules]
Run 'go help mod download' for details.

### What did you expect to see?

I wanted to see what the -dir option does.
The longer answer is I was trying to find out where go get/download stores the downloaded sources, since I hadn't found it in the documentation. I now see with a more thorough read that it is in GOPATH/pkg/mod 

",1.0,"cmd/go: for go mod download, -dir option does not exist - ### What version of Go are you using (`go version`)?

go version go1.11 linux/amd64

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

GOARCH=""amd64""
GOOS=""linux""

### What did you do?

$ echo $PWD
/home/mpl/src/perkeep.org
$ echo $GOPATH
/home/mpl
$ echo $GO111MODULE
on
$ go mod download -dir github.com/gopherjs/gopherjs
flag provided but not defined: -dir
usage: go mod download [-dir] [-json] [modules]
Run 'go help mod download' for details.

### What did you expect to see?

I wanted to see what the -dir option does.
The longer answer is I was trying to find out where go get/download stores the downloaded sources, since I hadn't found it in the documentation. I now see with a more thorough read that it is in GOPATH/pkg/mod 

",1,cmd go  for go mod download   dir option does not exist       what version of go are you using   go version       go version     linux          does this issue reproduce with the latest release     yes         what operating system and processor architecture are you using   go env       goarch      goos  linux         what did you do       echo  pwd   home mpl src perkeep org    echo  gopath   home mpl    echo     on    go mod download  dir github com gopherjs gopherjs  flag provided but not defined   dir  usage  go mod download        run  go help mod download  for details         what did you expect to see     i wanted to see what the  dir option does   the longer answer is i was trying to find out where go get download stores the downloaded sources  since i hadn t found it in the documentation  i now see with a more thorough read that it is in gopath pkg mod     ,1
278802,21097007494.0,IssuesEvent,2022-04-04 11:17:01,golang/go,https://api.github.com/repos/golang/go,closed,strings: Docs & Examples unclear about difference between ToTitle and ToUpper,Documentation NeedsInvestigation,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

The current documentation on https://golang.org/pkg/strings/

### Does this issue reproduce with the latest release?

Yes, using the examples inside the strings package documentation

### What operating system and processor architecture are you using (`go env`)?

None providable

### What did you do?

Copied `strings.ToTitle` example to `strings.ToUpper` and changed `ToTitle()` to `ToUpper()`:
```
package main

import (
	""fmt""
	""strings""
)

func main() {
	fmt.Println(strings.ToUpper(""her royal highness""))
	fmt.Println(strings.ToUpper(""loud noises""))
	fmt.Println(strings.ToUpper(""хлеб""))
}
```

### What did you expect to see?

A difference in output.

### What did you see instead?

Example ToTitle (unmodified) outputs:
```
HER ROYAL HIGHNESS
LOUD NOISES
ХЛЕБ
```

Example ToUpper (modified as described above) outputs:
```
HER ROYAL HIGHNESS
LOUD NOISES
ХЛЕБ
```

No difference. So for me it is unclear which function is now the correct one to use for an imaginary case.",1.0,"strings: Docs & Examples unclear about difference between ToTitle and ToUpper - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

The current documentation on https://golang.org/pkg/strings/

### Does this issue reproduce with the latest release?

Yes, using the examples inside the strings package documentation

### What operating system and processor architecture are you using (`go env`)?

None providable

### What did you do?

Copied `strings.ToTitle` example to `strings.ToUpper` and changed `ToTitle()` to `ToUpper()`:
```
package main

import (
	""fmt""
	""strings""
)

func main() {
	fmt.Println(strings.ToUpper(""her royal highness""))
	fmt.Println(strings.ToUpper(""loud noises""))
	fmt.Println(strings.ToUpper(""хлеб""))
}
```

### What did you expect to see?

A difference in output.

### What did you see instead?

Example ToTitle (unmodified) outputs:
```
HER ROYAL HIGHNESS
LOUD NOISES
ХЛЕБ
```

Example ToUpper (modified as described above) outputs:
```
HER ROYAL HIGHNESS
LOUD NOISES
ХЛЕБ
```

No difference. So for me it is unclear which function is now the correct one to use for an imaginary case.",1,strings  docs   examples unclear about difference between totitle and toupper         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version       the current documentation on          does this issue reproduce with the latest release     yes  using the examples inside the strings package documentation        what operating system and processor architecture are you using   go env       none providable        what did you do     copied  strings totitle  example to  strings toupper  and changed  totitle    to  toupper           package main    import    	 fmt   	 strings        func main      	fmt println strings toupper  her royal highness     	fmt println strings toupper  loud noises     	fmt println strings toupper  хлеб                   what did you expect to see     a difference in output         what did you see instead     example totitle  unmodified  outputs        her royal highness  loud noises  хлеб         example toupper  modified as described above  outputs        her royal highness  loud noises  хлеб         no difference  so for me it is unclear which function is now the correct one to use for an imaginary case ,1
5803,2974785975.0,IssuesEvent,2015-07-15 04:31:56,golang/go,https://api.github.com/repos/golang/go,closed,database/sql: Document that prepared statements must be Close()' ,Documentation,"<pre>Before filing a bug, please check whether it has been fixed since the
latest release. Search the issue tracker and check that you're running the
latest version of Go:

Run &quot;go version&quot; and compare against
<a href=""http://golang.org/doc/devel/release.html"">http://golang.org/doc/devel/release.html</a>  If a newer version of Go exists,
install it and retry what you did to reproduce the problem.

Thanks.

What does 'go version' print?

What steps reproduce the problem?
If possible, include a link to a program on play.golang.org.

1.
2.
3.

What happened?

What should have happened instead?

Please provide any additional information below.</pre>",1.0,"database/sql: Document that prepared statements must be Close()'  - <pre>Before filing a bug, please check whether it has been fixed since the
latest release. Search the issue tracker and check that you're running the
latest version of Go:

Run &quot;go version&quot; and compare against
<a href=""http://golang.org/doc/devel/release.html"">http://golang.org/doc/devel/release.html</a>  If a newer version of Go exists,
install it and retry what you did to reproduce the problem.

Thanks.

What does 'go version' print?

What steps reproduce the problem?
If possible, include a link to a program on play.golang.org.

1.
2.
3.

What happened?

What should have happened instead?

Please provide any additional information below.</pre>",1,database sql  document that prepared statements must be close        before filing a bug  please check whether it has been fixed since the latest release  search the issue tracker and check that you re running the latest version of go   run  quot go version quot  and compare against  a href     if a newer version of go exists  install it and retry what you did to reproduce the problem   thanks   what does  go version  print   what steps reproduce the problem  if possible  include a link to a program on play golang org             what happened   what should have happened instead   please provide any additional information below  ,1
73350,9660745838.0,IssuesEvent,2019-05-20 16:09:57,golang/go,https://api.github.com/repos/golang/go,closed,context: CancelFunc isn't documented to be safe for simultaneous use by multiple goroutines,Documentation NeedsFix,"There are two types defined in the `context` package. The documentation makes it very clear that the `context.Context` type and its methods are safe for simultaneous use by multiple goroutines:

- In the [package comment](https://godoc.org/context):

    > The same Context may be passed to functions running in different goroutines; Contexts are safe for simultaneous use by multiple goroutines.

- In the [`context.Context`](https://godoc.org/context#Context) type documentation:

  > Context's methods may be called by multiple goroutines simultaneously.

There is another type in the context package, the [`context.CancelFunc`](https://godoc.org/context#CancelFunc) type. It is currently documented as:

> A CancelFunc tells an operation to abandon its work. A CancelFunc does not wait for the work to stop. After the first call, subsequent calls to a CancelFunc do nothing.

It states that after the first call, subsequent calls to a CancelFunc do nothing. The three `With*` methods that return a Context and CancelFunc say:

> Canceling this context releases resources associated with it, so code should call cancel as soon as the operations running in this Context complete.

As I understand it, the documentation does not state that ContextFunc is safe for simultaneous use by multiple goroutines. Is that a documentation bug?

/cc @Sajmani, @bradfitz as [owners](https://dev.golang.org/owners); also /cc @mvdan",1.0,"context: CancelFunc isn't documented to be safe for simultaneous use by multiple goroutines - There are two types defined in the `context` package. The documentation makes it very clear that the `context.Context` type and its methods are safe for simultaneous use by multiple goroutines:

- In the [package comment](https://godoc.org/context):

    > The same Context may be passed to functions running in different goroutines; Contexts are safe for simultaneous use by multiple goroutines.

- In the [`context.Context`](https://godoc.org/context#Context) type documentation:

  > Context's methods may be called by multiple goroutines simultaneously.

There is another type in the context package, the [`context.CancelFunc`](https://godoc.org/context#CancelFunc) type. It is currently documented as:

> A CancelFunc tells an operation to abandon its work. A CancelFunc does not wait for the work to stop. After the first call, subsequent calls to a CancelFunc do nothing.

It states that after the first call, subsequent calls to a CancelFunc do nothing. The three `With*` methods that return a Context and CancelFunc say:

> Canceling this context releases resources associated with it, so code should call cancel as soon as the operations running in this Context complete.

As I understand it, the documentation does not state that ContextFunc is safe for simultaneous use by multiple goroutines. Is that a documentation bug?

/cc @Sajmani, @bradfitz as [owners](https://dev.golang.org/owners); also /cc @mvdan",1,context  cancelfunc isn t documented to be safe for simultaneous use by multiple goroutines   there are two types defined in the  context  package  the documentation makes it very clear that the  context context  type and its methods are safe for simultaneous use by multiple goroutines       in the              the same context may be passed to functions running in different goroutines  contexts are safe for simultaneous use by multiple goroutines       in the     type documentation         context s methods may be called by multiple goroutines simultaneously     there is another type in the context package  the     type  it is currently documented as       a cancelfunc tells an operation to abandon its work  a cancelfunc does not wait for the work to stop  after the first call  subsequent calls to a cancelfunc do nothing     it states that after the first call  subsequent calls to a cancelfunc do nothing  the three  with   methods that return a context and cancelfunc say       canceling this context releases resources associated with it  so code should call cancel as soon as the operations running in this context complete     as i understand it  the documentation does not state that contextfunc is safe for simultaneous use by multiple goroutines  is that a documentation bug      cc  sajmani   bradfitz as     also  cc  mvdan,1
27152,11451354155.0,IssuesEvent,2020-02-06 11:25:13,fetchai/agents-aea,https://api.github.com/repos/fetchai/agents-aea,closed,Use tool 'bandit' in the CI pipeline,enhancement security,"**Is your feature request related to a problem? Please describe.**

There is no quality check regarding security issues in the codebase.

**Describe the solution you'd like**

A tool like [Bandit](https://bandit.readthedocs.io/en/latest/) to add in the CI pipeline.

**Describe alternatives you've considered**

None.

**Additional context**

None.
",True,"Use tool 'bandit' in the CI pipeline - **Is your feature request related to a problem? Please describe.**

There is no quality check regarding security issues in the codebase.

**Describe the solution you'd like**

A tool like [Bandit](https://bandit.readthedocs.io/en/latest/) to add in the CI pipeline.

**Describe alternatives you've considered**

None.

**Additional context**

None.
",0,use tool  bandit  in the ci pipeline     is your feature request related to a problem  please describe       there is no quality check regarding security issues in the codebase       describe the solution you d like      a tool like     to add in the ci pipeline       describe alternatives you ve considered      none       additional context      none   ,0
1155,2508310988.0,IssuesEvent,2015-01-13 00:54:29,flynn/go-tuf,https://api.github.com/repos/flynn/go-tuf,closed,Test attack scenarios,enhancement priority,The client tests need improving to cover the attack scenarios discussed in [section 1.5.2 of the TUF spec](https://github.com/theupdateframework/tuf/blob/v0.9.9/docs/tuf-spec.txt#L121-L155) (there are some good examples in the Python test suite).,1.0,Test attack scenarios - The client tests need improving to cover the attack scenarios discussed in [section 1.5.2 of the TUF spec](https://github.com/theupdateframework/tuf/blob/v0.9.9/docs/tuf-spec.txt#L121-L155) (there are some good examples in the Python test suite).,0,test attack scenarios   the client tests need improving to cover the attack scenarios discussed in      there are some good examples in the python test suite  ,0
19617,5908875778.0,IssuesEvent,2017-05-19 21:42:21,phetsims/fractions-intro,https://api.github.com/repos/phetsims/fractions-intro,closed,ICON_SCALE,dev:code-review,"RepresentationPanel's ICON_SCALE is currently set to `1.00`. Can it be removed, or potentially refactored so that there is a common set of Node options for each icon like `{ scale: 1.2, stroke: 'black' }`?",1.0,"ICON_SCALE - RepresentationPanel's ICON_SCALE is currently set to `1.00`. Can it be removed, or potentially refactored so that there is a common set of Node options for each icon like `{ scale: 1.2, stroke: 'black' }`?",0,icon scale   representationpanel s icon scale is currently set to        can it be removed  or potentially refactored so that there is a common set of node options for each icon like    scale       stroke   black     ,0
79691,28496449528.0,IssuesEvent,2023-04-18 14:33:29,vector-im/element-desktop,https://api.github.com/repos/vector-im/element-desktop,opened,"if you press alt, the top menu appears.",T-Defect,"The menu on the top (with file, edit, view, etc) opens when you release alt on the client, this is problematic for tiling window managers, where you press alt and then a number to switch workspaces.

when you release it on riot, it opens the menu, and its quite annoying.

- **Platform**: Desktop
- **OS**:  Arch Linux
- **Version**: 0.14.1",1.0,"if you press alt, the top menu appears. - The menu on the top (with file, edit, view, etc) opens when you release alt on the client, this is problematic for tiling window managers, where you press alt and then a number to switch workspaces.

when you release it on riot, it opens the menu, and its quite annoying.

- **Platform**: Desktop
- **OS**:  Arch Linux
- **Version**: 0.14.1",0,if you press alt  the top menu appears    the menu on the top  with file  edit  view  etc  opens when you release alt on the client  this is problematic for tiling window managers  where you press alt and then a number to switch workspaces     when you release it on riot  it opens the menu  and its quite annoying         platform    desktop      os     arch linux      version         ,0
563446,16685049830.0,IssuesEvent,2021-06-08 07:06:07,siodb/siodb,https://api.github.com/repos/siodb/siodb,opened,Create database issue with wrong permissions on underlaying FS,component:iomgr priority:major type:bug,"## Issue

```sql
siocli> create database dfb850cd6c55e5f with uuid = 'fb850cd6-c55e-5fc3-87fb-6949c004dbf3', data_directory_must_exist = false;

Connected to localhost:50000

<hanging>

```

```log
2021-06-08 06:41:24.494042 error 2460 2465 IOManagerConnectionHandler-15[3181]: Request execution exception: boost::filesystem::status: Permission denied: ""/var/lib/siodb/siodb0100/data/db-fb850cd6-c55e-5fc3-87fb-6949c004dbf3/initialized"".
```

## Expected

The command should not hang and immediately returns with the error.",1.0,"Create database issue with wrong permissions on underlaying FS - ## Issue

```sql
siocli> create database dfb850cd6c55e5f with uuid = 'fb850cd6-c55e-5fc3-87fb-6949c004dbf3', data_directory_must_exist = false;

Connected to localhost:50000

<hanging>

```

```log
2021-06-08 06:41:24.494042 error 2460 2465 IOManagerConnectionHandler-15[3181]: Request execution exception: boost::filesystem::status: Permission denied: ""/var/lib/siodb/siodb0100/data/db-fb850cd6-c55e-5fc3-87fb-6949c004dbf3/initialized"".
```

## Expected

The command should not hang and immediately returns with the error.",0,create database issue with wrong permissions on underlaying fs      issue       sql  siocli  create database   with uuid                data directory must exist   false     connected to localhost                     log                error     iomanagerconnectionhandler     request execution exception  boost  filesystem  status  permission denied    var lib siodb   data db           initialized              expected    the command should not hang and immediately returns with the error ,0
53761,7855096922.0,IssuesEvent,2018-06-20 23:36:15,golang/go,https://api.github.com/repos/golang/go,closed,doc: update gopherbot wiki to account for backporting command,Documentation NeedsFix,"In https://github.com/golang/go/wiki/gopherbot the section for backporting is currently empty. We should fill it out :)

/cc @filippo

@gopherbot needsfix",1.0,"doc: update gopherbot wiki to account for backporting command - In https://github.com/golang/go/wiki/gopherbot the section for backporting is currently empty. We should fill it out :)

/cc @filippo

@gopherbot needsfix",1,doc  update gopherbot wiki to account for backporting command   in   the section for backporting is currently empty  we should fill it out        cc  filippo     gopherbot needsfix,1
14662,3872871474.0,IssuesEvent,2016-04-11 15:10:57,golang/go,https://api.github.com/repos/golang/go,closed,spec: define what a function is,Documentation,<pre>There's almost no text on what a function actually is. Needs to be expanded.</pre>,1.0,spec: define what a function is - <pre>There's almost no text on what a function actually is. Needs to be expanded.</pre>,1,spec  define what a function is    there s almost no text on what a function actually is  needs to be expanded  ,1
47619,7334300307.0,IssuesEvent,2018-03-05 22:17:16,golang/go,https://api.github.com/repos/golang/go,closed,x/playground: link to the playground source code in the help page,Documentation NeedsFix,"I can never remember where it is. It's pretty standard nowadays to link back to the implementation of any open source website. IIRC, there are actually multiple playground moving parts. It'd be nice to link to all of them. I'd send a CL, but, um, I can't remember where the code is.

cc @andybons 
",1.0,"x/playground: link to the playground source code in the help page - I can never remember where it is. It's pretty standard nowadays to link back to the implementation of any open source website. IIRC, there are actually multiple playground moving parts. It'd be nice to link to all of them. I'd send a CL, but, um, I can't remember where the code is.

cc @andybons 
",1,x playground  link to the playground source code in the help page   i can never remember where it is  it s pretty standard nowadays to link back to the implementation of any open source website  iirc  there are actually multiple playground moving parts  it d be nice to link to all of them  i d send a cl  but  um  i can t remember where the code is     cc  andybons   ,1
73978,9742421800.0,IssuesEvent,2019-06-02 16:58:30,golang/go,https://api.github.com/repos/golang/go,closed,wiki: transfer label descriptions from wiki to labels themselves,Documentation,"Now that GitHub has [added descriptions to labels](https://github.com/blog/2505-label-improvements-emoji-descriptions-and-more), it would probably be helpful to transfer the label descriptions from https://github.com/golang/go/wiki/IssueLabels to the labels themselves.

I think it would make it easier for more people to discover what the labels mean.

If we do this, I think the wiki page should be removed (maybe not right away, and also having made a backup), to avoid having to maintain same information in two places.

This issue is to consider/discuss this opportunity.",1.0,"wiki: transfer label descriptions from wiki to labels themselves - Now that GitHub has [added descriptions to labels](https://github.com/blog/2505-label-improvements-emoji-descriptions-and-more), it would probably be helpful to transfer the label descriptions from https://github.com/golang/go/wiki/IssueLabels to the labels themselves.

I think it would make it easier for more people to discover what the labels mean.

If we do this, I think the wiki page should be removed (maybe not right away, and also having made a backup), to avoid having to maintain same information in two places.

This issue is to consider/discuss this opportunity.",1,wiki  transfer label descriptions from wiki to labels themselves   now that github has     it would probably be helpful to transfer the label descriptions from   to the labels themselves     i think it would make it easier for more people to discover what the labels mean     if we do this  i think the wiki page should be removed  maybe not right away  and also having made a backup   to avoid having to maintain same information in two places     this issue is to consider discuss this opportunity ,1
173105,14402445562.0,IssuesEvent,2020-12-03 14:54:55,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.16: document os changes for Go 1.16,Documentation NeedsFix help wanted release-blocker,"As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

<dl id=""os""><dt><a href=""/pkg/os/"">os</a></dt>
  <dd>
    <p><!-- CL 242998 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/242998"">https://golang.org/cl/242998</a>: export errFinished as ErrProcessDone
    </p>
  </dd>
</dl><!-- os -->

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.",1.0,"doc/go1.16: document os changes for Go 1.16 - As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

<dl id=""os""><dt><a href=""/pkg/os/"">os</a></dt>
  <dd>
    <p><!-- CL 242998 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/242998"">https://golang.org/cl/242998</a>: export errFinished as ErrProcessDone
    </p>
  </dd>
</dl><!-- os -->

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.",1,doc      document os changes for go       as of filing this issue  the     contained the following html        os                        todo    a href    export errfinished as errprocessdone                           per     it s a release blocker for go     beta   to have a complete draft of the eventual release notes  and so the todo needs to be resolved     a sequence of steps to resolve this issue may be        come up with a draft release note entry in this issue  then move the issue to needsfix state      send a cl with  doc           and include  for     fixes   this issue    in the body ,1
103985,11387294431.0,IssuesEvent,2020-01-29 14:47:36,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.14: RISC-V status,Documentation NeedsFix arch-riscv,"<p>
(I'm not sure if making issues about draft documents is allowed, so
please feel free to close.)
</p>
<p>
<a href=""https://tip.golang.org/doc/go1.14"">https://tip.golang.org/doc/go1.14</a>
doesn't seem to mention the new RISC-V port anywhere.  AFAIK, the port
will probably enter Go 1.14 in some way, even if highly experimental, so
I think it needs to be documented.
<p>
",1.0,"doc/go1.14: RISC-V status - <p>
(I'm not sure if making issues about draft documents is allowed, so
please feel free to close.)
</p>
<p>
<a href=""https://tip.golang.org/doc/go1.14"">https://tip.golang.org/doc/go1.14</a>
doesn't seem to mention the new RISC-V port anywhere.  AFAIK, the port
will probably enter Go 1.14 in some way, even if highly experimental, so
I think it needs to be documented.
<p>
",1,doc      risc v status       i m not sure if making issues about draft documents is allowed  so  please feel free to close           a href     doesn t seem to mention the new risc v port anywhere   afaik  the port  will probably enter go     in some way  even if highly experimental  so  i think it needs to be documented      ,1
15256,3321403376.0,IssuesEvent,2015-11-09 08:43:17,osakagamba/7GIQSKRNE5P3AVTZCEFXE3ON,https://api.github.com/repos/osakagamba/7GIQSKRNE5P3AVTZCEFXE3ON,closed,fvaHSSnfwSHiUGQlYVln5Qu6D0ZHaZYM6jobyApi6IbU+AivgCjEYOq1GKCuqPW4DQG9bJhIe6CZkiZTy9CNsugpkZmbMdUBljYGG5OXLlRjMNKZJWarZuz6O0Y7bUoJC97AdezL2ghr0QrJYgC+teRoYnYShmgQTzAlJiPY+XI=,design,9ynu2xiwRV1xTe62oYDwPizZvjCj/Mz5JIAmEr+4+lccH6VNNrH79hKXlOwTV2UFaH5aRekW/rf8Pcgr+5zmkRtKJ63Q5hJLgiPP3KQMdS0mGFkfqogx2AqPmWI4gAi/khUapkS6IT5dhEB8LI9JBuQHyeIFVU0Bh5z74OuqLqiBOX5WGikFoe5TqHJjbvJeIyhLMJ1eLFSiQcWyKlyER3BEpjM6PY9R9N2Uk9y7yGI6TUZMopjhm+oxn92ef8lu8/Zqu8Yi7abSxEkx+H4gwiU4TN2hENMfECsYrtHDxcSuYGxEWd/KrKUrzQ0EgnjpnCk3Knr0wCvgFDjM4/XAs9O+T1s0T83FnwGAvCbgY7j0+X8rWBbr647SwOdJVswA4rMwY4s23Xr71xDYgBvf6HVMK6b5Jd/j1Gdf2X2hRVt07yFGa1PxwCgaYRSwxmb8i7gSllcMe/vBquMtVbKMDE0J0EuuPGoCyTy2TZL35LD4H5eX8ockBbjB6xn+iCDzXc3tgXTrCaRUa1HRU0YIOycKZ66cL38uZv7iBwcAXpHbMIH6LmXNhldBootIg08EbcVKh6s0g73CL5QtySlG31gvfPdmknHv6x1O4w/wWP4ej1tawee3csMt8uQhFf/l7s+9CamBYNXYCVP++kqWtpvA0A0YJQfJV2Y0B/OsHqHM2bNhAqFSydyQ4P93p2m+Ts3VxkrRglTZhLlTrBL2CiDcARo6KxnhX98aIc0RWZODIq4aFrDDYC9unL0SFqPfFwIH4SEtPc5i609ILFcsZpVQjuvonHYTpkm6iSbf91OJ76PJQ9De448SzfxchuBOkOK5ll4YLVlfguY/FcdUGnqhYtH8E16s1l0oKUh3UV9LlCpP7QOiX+3q4ZVPIiKzc2EGY3XaPH5Px0iEI5pgLfrA+G3o6E/Z7nK0VTm+HFd7lxEF7MTZYwk4uvXBps7GCndzuxm+xFC80SCddUkIWRc2LmLHaY1HbUoJrk5TymF5MLuQpjdl8AMT/XVpVlrNIXULBDskoXFI67vtcNz6HL6QaQf40Ivcii1Y+C5OKWzSZgPJdWYsKDJhlNtpxS4F6oCQgiDjsNb5yKE1ObxLxQezyog/LUv4i2O9KvlpGdo4+gdZHNm0mMEYvC/0q44CMr0aofebugdbZH+UH6qAlzreb4uw7LrO7a9w1Jy0X31RoAyTOLJFi62oYsdRWjGGtHBzBMILJ3spaSaq1bidkClkzELJqQwouuFksZtkehUMzjYwSTjBbO1uXZ78Pp7PWMICTOV9GmrWegPbdPd94v1fwl+/EqKqe5ctHuApXdndGjkuegMTxNNC6lgTIHP6A3LsaAMxHt5LZHYSyXuvZGvPQ0Q7EdoKDFqQLIjozZpLlCpP7QOiX+3q4ZVPIiKzcCS1vyMjR15HFPILKb/LHzI5KNx11RBDEquzEgBB9rB24Xo91BeQvSfLRYAgVMwYIrSjjsNZhLjabbrqk2mwUDBIDUG3BJX0huRLwRDXMyE/EkZoIqrzCe1KMDq5qrYdbg8TX716eXDvk5E6WI8FGKB6jKxGxhakBbZgQvPVkttfMkRxoVKlUUm0B9+pd/AxbuUdWWg28QlsQpM7AqbFfe0rdzWM3CzgBETilkEidUVwdVBf7jRKjfik91k2XbOHa+hb1jZy34y7vH8uQrdVQfPa9Lz93zG4XvITAOxdu+OH0QXCqX1ESzVroNwx+VUy05HR3vQwzLiEVZ9D79e/1TMrxrqTz3EvNPGy6yvhQht849YIrp7KLEqwOcpzftF80eBXh8nG9nPcEQq2BFzhVQ7DZ4fDsTxnzvmJHJinXzkKNJrgHhcYUURh48di04EU3oczP/m4iYjJ4/NxM0WUAZVW2Xwd8CdHbg60CYMDxuOrIvg6zZ5F8H0u9atzV9LM,1.0,fvaHSSnfwSHiUGQlYVln5Qu6D0ZHaZYM6jobyApi6IbU+AivgCjEYOq1GKCuqPW4DQG9bJhIe6CZkiZTy9CNsugpkZmbMdUBljYGG5OXLlRjMNKZJWarZuz6O0Y7bUoJC97AdezL2ghr0QrJYgC+teRoYnYShmgQTzAlJiPY+XI= - 9ynu2xiwRV1xTe62oYDwPizZvjCj/Mz5JIAmEr+4+lccH6VNNrH79hKXlOwTV2UFaH5aRekW/rf8Pcgr+5zmkRtKJ63Q5hJLgiPP3KQMdS0mGFkfqogx2AqPmWI4gAi/khUapkS6IT5dhEB8LI9JBuQHyeIFVU0Bh5z74OuqLqiBOX5WGikFoe5TqHJjbvJeIyhLMJ1eLFSiQcWyKlyER3BEpjM6PY9R9N2Uk9y7yGI6TUZMopjhm+oxn92ef8lu8/Zqu8Yi7abSxEkx+H4gwiU4TN2hENMfECsYrtHDxcSuYGxEWd/KrKUrzQ0EgnjpnCk3Knr0wCvgFDjM4/XAs9O+T1s0T83FnwGAvCbgY7j0+X8rWBbr647SwOdJVswA4rMwY4s23Xr71xDYgBvf6HVMK6b5Jd/j1Gdf2X2hRVt07yFGa1PxwCgaYRSwxmb8i7gSllcMe/vBquMtVbKMDE0J0EuuPGoCyTy2TZL35LD4H5eX8ockBbjB6xn+iCDzXc3tgXTrCaRUa1HRU0YIOycKZ66cL38uZv7iBwcAXpHbMIH6LmXNhldBootIg08EbcVKh6s0g73CL5QtySlG31gvfPdmknHv6x1O4w/wWP4ej1tawee3csMt8uQhFf/l7s+9CamBYNXYCVP++kqWtpvA0A0YJQfJV2Y0B/OsHqHM2bNhAqFSydyQ4P93p2m+Ts3VxkrRglTZhLlTrBL2CiDcARo6KxnhX98aIc0RWZODIq4aFrDDYC9unL0SFqPfFwIH4SEtPc5i609ILFcsZpVQjuvonHYTpkm6iSbf91OJ76PJQ9De448SzfxchuBOkOK5ll4YLVlfguY/FcdUGnqhYtH8E16s1l0oKUh3UV9LlCpP7QOiX+3q4ZVPIiKzc2EGY3XaPH5Px0iEI5pgLfrA+G3o6E/Z7nK0VTm+HFd7lxEF7MTZYwk4uvXBps7GCndzuxm+xFC80SCddUkIWRc2LmLHaY1HbUoJrk5TymF5MLuQpjdl8AMT/XVpVlrNIXULBDskoXFI67vtcNz6HL6QaQf40Ivcii1Y+C5OKWzSZgPJdWYsKDJhlNtpxS4F6oCQgiDjsNb5yKE1ObxLxQezyog/LUv4i2O9KvlpGdo4+gdZHNm0mMEYvC/0q44CMr0aofebugdbZH+UH6qAlzreb4uw7LrO7a9w1Jy0X31RoAyTOLJFi62oYsdRWjGGtHBzBMILJ3spaSaq1bidkClkzELJqQwouuFksZtkehUMzjYwSTjBbO1uXZ78Pp7PWMICTOV9GmrWegPbdPd94v1fwl+/EqKqe5ctHuApXdndGjkuegMTxNNC6lgTIHP6A3LsaAMxHt5LZHYSyXuvZGvPQ0Q7EdoKDFqQLIjozZpLlCpP7QOiX+3q4ZVPIiKzcCS1vyMjR15HFPILKb/LHzI5KNx11RBDEquzEgBB9rB24Xo91BeQvSfLRYAgVMwYIrSjjsNZhLjabbrqk2mwUDBIDUG3BJX0huRLwRDXMyE/EkZoIqrzCe1KMDq5qrYdbg8TX716eXDvk5E6WI8FGKB6jKxGxhakBbZgQvPVkttfMkRxoVKlUUm0B9+pd/AxbuUdWWg28QlsQpM7AqbFfe0rdzWM3CzgBETilkEidUVwdVBf7jRKjfik91k2XbOHa+hb1jZy34y7vH8uQrdVQfPa9Lz93zG4XvITAOxdu+OH0QXCqX1ESzVroNwx+VUy05HR3vQwzLiEVZ9D79e/1TMrxrqTz3EvNPGy6yvhQht849YIrp7KLEqwOcpzftF80eBXh8nG9nPcEQq2BFzhVQ7DZ4fDsTxnzvmJHJinXzkKNJrgHhcYUURh48di04EU3oczP/m4iYjJ4/NxM0WUAZVW2Xwd8CdHbg60CYMDxuOrIvg6zZ5F8H0u9atzV9LM,0,    teroynyshmgqtzaljipy xi                                                                                    pd              ,0
33019,6997097239.0,IssuesEvent,2017-12-16 10:15:55,Quantum64/ExGregilo,https://api.github.com/repos/Quantum64/ExGregilo,closed,GUI Elements Missing or unable to load,defect,"I have tested the Auto Sieve of varying tiers and they seem to work however, the GUI seems to not be working. They are not loading for the Auto Sieve and Auto Sieve recipes.

![auto sieve recipes](https://user-images.githubusercontent.com/34498631/33978443-c65f78f2-e06d-11e7-81bd-85a163de29d7.PNG)
![auto sieve gui](https://user-images.githubusercontent.com/34498631/33978444-c668abf2-e06d-11e7-9659-c7c487e43312.PNG)

",1.0,"GUI Elements Missing or unable to load - I have tested the Auto Sieve of varying tiers and they seem to work however, the GUI seems to not be working. They are not loading for the Auto Sieve and Auto Sieve recipes.

![auto sieve recipes](https://user-images.githubusercontent.com/34498631/33978443-c65f78f2-e06d-11e7-81bd-85a163de29d7.PNG)
![auto sieve gui](https://user-images.githubusercontent.com/34498631/33978444-c668abf2-e06d-11e7-9659-c7c487e43312.PNG)

",0,gui elements missing or unable to load   i have tested the auto sieve of varying tiers and they seem to work however  the gui seems to not be working  they are not loading for the auto sieve and auto sieve recipes                   ,0
40840,6850459313.0,IssuesEvent,2017-11-14 03:23:08,golang/go,https://api.github.com/repos/golang/go,closed,net/http: add examples/comments for Server.Shutdown,Documentation NeedsFix release-blocker,"Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
Go 1.8

### What operating system and processor architecture are you using (`go env`)?
amd64(windows 7 & Ubuntu 16.04)

### What did you do?
https://play.golang.org/p/Akv3se9kkZ

### What did you expect to see?
Go file server shutdown after download the file or timeout is reached

### What did you see instead?
File server shutdown immediately

This issue is related to https://github.com/golang/go/issues/19541. 

The Shutdown function may need some comments or examples to warn gophers to keep ListenAndServe running until it finished. 

Or if possible, make Shutdown communicate with ListenAndServe internally to make https://play.golang.org/p/Akv3se9kkZ works.

Thanks,
Andrew


",1.0,"net/http: add examples/comments for Server.Shutdown - Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
Go 1.8

### What operating system and processor architecture are you using (`go env`)?
amd64(windows 7 & Ubuntu 16.04)

### What did you do?
https://play.golang.org/p/Akv3se9kkZ

### What did you expect to see?
Go file server shutdown after download the file or timeout is reached

### What did you see instead?
File server shutdown immediately

This issue is related to https://github.com/golang/go/issues/19541. 

The Shutdown function may need some comments or examples to warn gophers to keep ListenAndServe running until it finished. 

Or if possible, make Shutdown communicate with ListenAndServe internally to make https://play.golang.org/p/Akv3se9kkZ works.

Thanks,
Andrew


",1,net http  add examples comments for server shutdown   please answer these questions before submitting your issue  thanks         what version of go are you using   go version     go            what operating system and processor architecture are you using   go env       windows     ubuntu             what did you do            what did you expect to see   go file server shutdown after download the file or timeout is reached        what did you see instead   file server shutdown immediately    this issue is related to       the shutdown function may need some comments or examples to warn gophers to keep listenandserve running until it finished      or if possible  make shutdown communicate with listenandserve internally to make   works     thanks   andrew      ,1
44168,7094226588.0,IssuesEvent,2018-01-13 00:46:37,golang/go,https://api.github.com/repos/golang/go,closed,dist: one-line installer: additional safety/trust features,Documentation NeedsInvestigation WaitingForInfo,"The one-line installer tracked in https://github.com/golang/go/issues/23381 is something many new and current Go programmers will use, likely downloaded from golang.org. In that issue I mentioned having a sensation of distrust when using the Go 1.10 beta installer, and this issue is to discuss any additional features that may reduce such distrust.

My opinion is the valid HTTPS link source is trustworthy enough (I still ran the Go 1.10 beta) and that this issue is a nice to have perception improvement. @broady mentions in the other issue that a GPG signature is provided for all downloads on golang.org already.

The sensation of distrust is due to thinking that the features provided in the downloaded binary could be easily replicated by a third party with deconstructive intent. Due to the open source of the tool I'm not sure there's much else that could be done there and the website seems to have just about every necessary security feature, but maybe documentation saying ""only download from golang.org and check for the browser green certificate verification and verify the GPG key this way"" could be part of the tool distribution.",1.0,"dist: one-line installer: additional safety/trust features - The one-line installer tracked in https://github.com/golang/go/issues/23381 is something many new and current Go programmers will use, likely downloaded from golang.org. In that issue I mentioned having a sensation of distrust when using the Go 1.10 beta installer, and this issue is to discuss any additional features that may reduce such distrust.

My opinion is the valid HTTPS link source is trustworthy enough (I still ran the Go 1.10 beta) and that this issue is a nice to have perception improvement. @broady mentions in the other issue that a GPG signature is provided for all downloads on golang.org already.

The sensation of distrust is due to thinking that the features provided in the downloaded binary could be easily replicated by a third party with deconstructive intent. Due to the open source of the tool I'm not sure there's much else that could be done there and the website seems to have just about every necessary security feature, but maybe documentation saying ""only download from golang.org and check for the browser green certificate verification and verify the GPG key this way"" could be part of the tool distribution.",1,dist  one line installer  additional safety trust features   the one line installer tracked in   is something many new and current go programmers will use  likely downloaded from golang org  in that issue i mentioned having a sensation of distrust when using the go     beta installer  and this issue is to discuss any additional features that may reduce such distrust     my opinion is the valid https link source is trustworthy enough  i still ran the go     beta  and that this issue is a nice to have perception improvement   broady mentions in the other issue that a gpg signature is provided for all downloads on golang org already     the sensation of distrust is due to thinking that the features provided in the downloaded binary could be easily replicated by a third party with deconstructive intent  due to the open source of the tool i m not sure there s much else that could be done there and the website seems to have just about every necessary security feature  but maybe documentation saying  only download from golang org and check for the browser green certificate verification and verify the gpg key this way  could be part of the tool distribution ,1
115395,4668552106.0,IssuesEvent,2016-10-06 03:11:08,OctopusDeploy/Issues,https://api.github.com/repos/OctopusDeploy/Issues,closed,Project Overview error - Sequence contains no matching element,bug forreview priority,"The progression API returns a `System.InvalidOperationException: Sequence contains no matching element` exception in some cases:

http://help.octopusdeploy.com/discussions/problems/46424-project-overview-throws-an-exception (v3.2.7)
http://help.octopusdeploy.com/discussions/problems/47292-systeminvalidoperationexception-sequence-contains-no-matching-element (v3.4.1)
http://help.octopusdeploy.com/discussions/problems/47762 (after upgrade from v3.3.0 to v3.4.11)",1.0,"Project Overview error - Sequence contains no matching element - The progression API returns a `System.InvalidOperationException: Sequence contains no matching element` exception in some cases:

http://help.octopusdeploy.com/discussions/problems/46424-project-overview-throws-an-exception (v3.2.7)
http://help.octopusdeploy.com/discussions/problems/47292-systeminvalidoperationexception-sequence-contains-no-matching-element (v3.4.1)
http://help.octopusdeploy.com/discussions/problems/47762 (after upgrade from v3.3.0 to v3.4.11)",0,project overview error   sequence contains no matching element   the progression api returns a  system invalidoperationexception  sequence contains no matching element  exception in some cases                              after upgrade from       to       ,0
122618,12156398853.0,IssuesEvent,2020-04-25 17:09:44,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/gopls: hoverKind FullDocumentation is incorrectly escaping various characters,Documentation Tools gopls,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
❯ gopls version                          
golang.org/x/tools/gopls v0.3.4
    golang.org/x/tools/gopls@v0.3.4 h1:4GC7q/pXQ/tsxHBGVdsMdlB4gCxVC06m/7rIXg1Px4E=
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
❯ go env                                 
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/james/.cache/go-build""
GOENV=""/home/james/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/james/go:/home/james/godev""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/lib/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/lib/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build613753881=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->
I have set `""hoverKind"": ""FullDocumentation""` as added in https://github.com/golang/go/issues/32561. This works, but it inserts a lot of escaped characters into the markdown description that it doesn't need to. I'm not quite sure why.

Here is an example for `fmt#Errorf`:

```markdown

[`fmt.Errorf` on pkg.go.dev](https://pkg.go.dev/fmt#Errorf)

Errorf formats according to a format specifier and returns the string as a
value that satisfies error\\.

If the format specifier includes a \\%w verb with an error operand,
the returned error will implement an Unwrap method returning the operand\\. It is
invalid to include more than one \\%w verb or to supply it with an operand
that does not implement the error interface\\. The \\%w verb is otherwise
a synonym for \\%v\\.
```

Rendering this via markdown (inside Emacs via lsp-mode) produces this:

![image](https://user-images.githubusercontent.com/522123/80281358-69076c80-8702-11ea-99a9-93e69422d657.png)

I'm also seeing html entities being escaped:

![image](https://user-images.githubusercontent.com/522123/80284964-c3f88e00-8719-11ea-96fa-32f4c7106c4f.png)

In the raw JSON this looks like `\u0026nbsp;`.

### What did you expect to see?

Full documentation without any escape characters.

### What did you see instead?

Full documentation with lots of embedded escape characters.",1.0,"x/tools/gopls: hoverKind FullDocumentation is incorrectly escaping various characters - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
❯ gopls version                          
golang.org/x/tools/gopls v0.3.4
    golang.org/x/tools/gopls@v0.3.4 h1:4GC7q/pXQ/tsxHBGVdsMdlB4gCxVC06m/7rIXg1Px4E=
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
❯ go env                                 
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/james/.cache/go-build""
GOENV=""/home/james/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/james/go:/home/james/godev""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/lib/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/lib/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build613753881=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->
I have set `""hoverKind"": ""FullDocumentation""` as added in https://github.com/golang/go/issues/32561. This works, but it inserts a lot of escaped characters into the markdown description that it doesn't need to. I'm not quite sure why.

Here is an example for `fmt#Errorf`:

```markdown

[`fmt.Errorf` on pkg.go.dev](https://pkg.go.dev/fmt#Errorf)

Errorf formats according to a format specifier and returns the string as a
value that satisfies error\\.

If the format specifier includes a \\%w verb with an error operand,
the returned error will implement an Unwrap method returning the operand\\. It is
invalid to include more than one \\%w verb or to supply it with an operand
that does not implement the error interface\\. The \\%w verb is otherwise
a synonym for \\%v\\.
```

Rendering this via markdown (inside Emacs via lsp-mode) produces this:

![image](https://user-images.githubusercontent.com/522123/80281358-69076c80-8702-11ea-99a9-93e69422d657.png)

I'm also seeing html entities being escaped:

![image](https://user-images.githubusercontent.com/522123/80284964-c3f88e00-8719-11ea-96fa-32f4c7106c4f.png)

In the raw JSON this looks like `\u0026nbsp;`.

### What did you expect to see?

Full documentation without any escape characters.

### What did you see instead?

Full documentation with lots of embedded escape characters.",1,x tools gopls  hoverkind fulldocumentation is incorrectly escaping various characters         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version          ❯ gopls version                            golang org x tools gopls            golang org x tools gopls           pxq                does this issue reproduce with the latest release     yes         what operating system and processor architecture are you using   go env          go env  output     ❯ go env                                         goarch      gobin     gocache   home james  cache go build   goenv   home james  config go env   goexe     goflags     gohostarch      gohostos  linux   goinsecure     gonoproxy     gonosumdb     goos  linux   gopath   home james go  home james godev   goprivate     goproxy     goroot   usr lib go   gosumdb  sum golang org   gotmpdir     gotooldir   usr lib go pkg tool linux     gccgo  gccgo   ar  ar   cc  gcc   cxx  g     cgo enabled      gomod     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches             what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best        i have set   hoverkind    fulldocumentation   as added in   this works  but it inserts a lot of escaped characters into the markdown description that it doesn t need to  i m not quite sure why     here is an example for  fmt errorf         markdown           errorf formats according to a format specifier and returns the string as a  value that satisfies error       if the format specifier includes a    w verb with an error operand   the returned error will implement an unwrap method returning the operand    it is  invalid to include more than one    w verb or to supply it with an operand  that does not implement the error interface    the    w verb is otherwise  a synonym for    v            rendering this via markdown  inside emacs via lsp mode  produces this             i m also seeing html entities being escaped             in the raw json this looks like               what did you expect to see     full documentation without any escape characters         what did you see instead     full documentation with lots of embedded escape characters ,1
186846,6743066388.0,IssuesEvent,2017-10-20 10:21:48,ArmaAchilles/AresModAchillesExpansion,https://api.github.com/repos/ArmaAchilles/AresModAchillesExpansion,reopened,Weaponry Dependencies,bug priority/low,"Some weaponry in the vanilla ArmA list is being taken over by Achilles mod. Therefor causing 
Achilles to become a dependency. This isn't a do or die situation but it is frustrating have to edit the
mission.sqm before pushing an update to a server that doesn't require any mods ",1.0,"Weaponry Dependencies - Some weaponry in the vanilla ArmA list is being taken over by Achilles mod. Therefor causing 
Achilles to become a dependency. This isn't a do or die situation but it is frustrating have to edit the
mission.sqm before pushing an update to a server that doesn't require any mods ",0,weaponry dependencies   some weaponry in the vanilla arma list is being taken over by achilles mod  therefor causing   achilles to become a dependency  this isn t a do or die situation but it is frustrating have to edit the  mission sqm before pushing an update to a server that doesn t require any mods ,0
450212,12992164255.0,IssuesEvent,2020-07-23 06:08:35,kubeflow/kubeflow,https://api.github.com/repos/kubeflow/kubeflow,closed,Allow creation of profiles within dashboard,area/front-end kind/feature lifecycle/stale priority/p1,"/kind feature

**Describe the solution you'd like:**
Currently to create a new profile (other than with the first registration flow) users must manually create Profile resources (in the default namespace).

This means many use-cases for kubeflow are cumbersome, for example, creating a profile for a specific business project, and adding collaborators.

Therefore, we should allow users to create new Profiles within the dashboard",1.0,"Allow creation of profiles within dashboard - /kind feature

**Describe the solution you'd like:**
Currently to create a new profile (other than with the first registration flow) users must manually create Profile resources (in the default namespace).

This means many use-cases for kubeflow are cumbersome, for example, creating a profile for a specific business project, and adding collaborators.

Therefore, we should allow users to create new Profiles within the dashboard",0,allow creation of profiles within dashboard    kind feature      describe the solution you d like     currently to create a new profile  other than with the first registration flow  users must manually create profile resources  in the default namespace      this means many use cases for kubeflow are cumbersome  for example  creating a profile for a specific business project  and adding collaborators     therefore  we should allow users to create new profiles within the dashboard,0
481572,13889180579.0,IssuesEvent,2020-10-19 07:31:12,NetaM-OSC/NetAM,https://api.github.com/repos/NetaM-OSC/NetAM,opened,migration to v1.3.0 scan issue,Priority::1 bug,"Problem after update to v1.3.0.  

All scans failed with error :  
```
E, [2020-10-19T07:17:33.655918 #1] ERROR -- : [ActiveJob] [ScanNetworkWithPingJob] [8f37429b-3b27-4558-a272-2358ee8a2600] Error performing ScanNetworkWithPingJob (Job ID: 8f37429b-3b27-4558-a272-2358ee8a2600) from Sidekiq(default) in 3844.96ms: ArgumentError (All objects being inserted must have the same keys):
```

Problem caused by missing database manipulation at upgrade. All identifier fields in database are empty.",1.0,"migration to v1.3.0 scan issue - Problem after update to v1.3.0.  

All scans failed with error :  
```
E, [2020-10-19T07:17:33.655918 #1] ERROR -- : [ActiveJob] [ScanNetworkWithPingJob] [8f37429b-3b27-4558-a272-2358ee8a2600] Error performing ScanNetworkWithPingJob (Job ID: 8f37429b-3b27-4558-a272-2358ee8a2600) from Sidekiq(default) in 3844.96ms: ArgumentError (All objects being inserted must have the same keys):
```

Problem caused by missing database manipulation at upgrade. All identifier fields in database are empty.",0,migration to       scan issue   problem after update to             all scans failed with error           e    error            error performing scannetworkwithpingjob  job id             from sidekiq default  in      argumenterror  all objects being inserted must have the same keys           problem caused by missing database manipulation at upgrade  all identifier fields in database are empty ,0
95588,12016340933.0,IssuesEvent,2020-04-10 15:53:48,hpe-design/design-system,https://api.github.com/repos/hpe-design/design-system,closed,Text Color compliance with WCAG 2.1 AA,design,"Color Study, proposal and styles published for our text colors to meet accessibility compliance.",1.0,"Text Color compliance with WCAG 2.1 AA - Color Study, proposal and styles published for our text colors to meet accessibility compliance.",0,text color compliance with wcag     aa   color study  proposal and styles published for our text colors to meet accessibility compliance ,0
68612,9203750142.0,IssuesEvent,2019-03-08 03:58:48,golang/go,https://api.github.com/repos/golang/go,closed,encoding/gob: doc.go is out of date,Documentation,"It does reproduce in Go 1.12 and my guess it is outdated since Go 1.2.

The section on encoding details does not reflect changes made to wireType.
Current documentation:

    type wireType struct {
        ArrayT  *ArrayType
        SliceT  *SliceType
        StructT *StructType
        MapT    *MapType
    }

Actual:

    type wireType struct {
        ArrayT           *arrayType
        SliceT           *sliceType
        StructT          *structType
        MapT             *mapType
        GobEncoderT      *gobEncoderType
        BinaryMarshalerT *gobEncoderType
        TextMarshalerT   *gobEncoderType
    }

I also suggest adding `gobEncoderType` to this section. Also to mention is that the types in the documentation are incorrectly capitalized (arrayType, not ArrayType).

Edit: Quick link https://golang.org/pkg/encoding/gob/#hdr-Encoding_Details",1.0,"encoding/gob: doc.go is out of date - It does reproduce in Go 1.12 and my guess it is outdated since Go 1.2.

The section on encoding details does not reflect changes made to wireType.
Current documentation:

    type wireType struct {
        ArrayT  *ArrayType
        SliceT  *SliceType
        StructT *StructType
        MapT    *MapType
    }

Actual:

    type wireType struct {
        ArrayT           *arrayType
        SliceT           *sliceType
        StructT          *structType
        MapT             *mapType
        GobEncoderT      *gobEncoderType
        BinaryMarshalerT *gobEncoderType
        TextMarshalerT   *gobEncoderType
    }

I also suggest adding `gobEncoderType` to this section. Also to mention is that the types in the documentation are incorrectly capitalized (arrayType, not ArrayType).

Edit: Quick link https://golang.org/pkg/encoding/gob/#hdr-Encoding_Details",1,encoding gob  doc go is out of date   it does reproduce in go     and my guess it is outdated since go         the section on encoding details does not reflect changes made to wiretype   current documentation         type wiretype struct            arrayt   arraytype          slicet   slicetype          structt  structtype          mapt     maptype           actual         type wiretype struct            arrayt            arraytype          slicet            slicetype          structt           structtype          mapt              maptype          gobencodert       gobencodertype          binarymarshalert  gobencodertype          textmarshalert    gobencodertype           i also suggest adding  gobencodertype  to this section  also to mention is that the types in the documentation are incorrectly capitalized  arraytype  not arraytype      edit  quick link  ,1
533036,15575797228.0,IssuesEvent,2021-03-17 11:31:52,codetapacademy/codetap.academy,https://api.github.com/repos/codetapacademy/codetap.academy,closed,feat: separate landing page based on user level,Priority: High Status: In Progress Type: Enhancement,"**Is your feature request related to a problem? Please describe.**
At the moment users are redirected to the **/dashboard**

**Describe the solution you'd like**
As an admin, I'd like to redirect to the **/dashboard** and as a user, I'd like to be redirected to my **profile** or **activities** or something else page.",1.0,"feat: separate landing page based on user level - **Is your feature request related to a problem? Please describe.**
At the moment users are redirected to the **/dashboard**

**Describe the solution you'd like**
As an admin, I'd like to redirect to the **/dashboard** and as a user, I'd like to be redirected to my **profile** or **activities** or something else page.",0,feat  separate landing page based on user level     is your feature request related to a problem  please describe     at the moment users are redirected to the    dashboard        describe the solution you d like    as an admin  i d like to redirect to the    dashboard   and as a user  i d like to be redirected to my   profile   or   activities   or something else page ,0
173894,14441461608.0,IssuesEvent,2020-12-07 16:49:30,golang/go,https://api.github.com/repos/golang/go,opened,cmd/go: add release note for rejection of non-ASCII import paths in module mode,Documentation NeedsFix release-blocker,"In [CL 251878](https://golang.org/cl/251878) (for #29101), we tightened up the import-path check in module mode so that it now disallows all non-ASCII _package import_ paths, not just non-ASCII _module_ paths (see https://github.com/golang/go/issues/29101#issuecomment-639050809).

Although we believe the number of affected packages to be very small, we should add a release note for this change so that users can easily verify that the change was intentional (see #43035).

CC @jayconrod @matloob @maruel",1.0,"cmd/go: add release note for rejection of non-ASCII import paths in module mode - In [CL 251878](https://golang.org/cl/251878) (for #29101), we tightened up the import-path check in module mode so that it now disallows all non-ASCII _package import_ paths, not just non-ASCII _module_ paths (see https://github.com/golang/go/issues/29101#issuecomment-639050809).

Although we believe the number of affected packages to be very small, we should add a release note for this change so that users can easily verify that the change was intentional (see #43035).

CC @jayconrod @matloob @maruel",1,cmd go  add release note for rejection of non ascii import paths in module mode   in      for      we tightened up the import path check in module mode so that it now disallows all non ascii  package import  paths  not just non ascii  module  paths  see      although we believe the number of affected packages to be very small  we should add a release note for this change so that users can easily verify that the change was intentional  see         cc  jayconrod  matloob  maruel,1
146202,13173719873.0,IssuesEvent,2020-08-11 20:52:30,golang/go,https://api.github.com/repos/golang/go,opened,doc: write Go 1.16 release notes,Documentation NeedsFix help wanted recurring release-blocker,"Tracking bug for writing the Go 1.16 Release Notes.

The latest state on tip can be viewed at https://tip.golang.org/doc/go1.16 (it hasn't been created yet, so 404 at this time).

Previously #37419, #36878, #17929, #15810, #5929, etc.",1.0,"doc: write Go 1.16 release notes - Tracking bug for writing the Go 1.16 Release Notes.

The latest state on tip can be viewed at https://tip.golang.org/doc/go1.16 (it hasn't been created yet, so 404 at this time).

Previously #37419, #36878, #17929, #15810, #5929, etc.",1,doc  write go     release notes   tracking bug for writing the go     release notes     the latest state on tip can be viewed at    it hasn t been created yet  so   at this time      previously                     etc ,1
69603,9310121042.0,IssuesEvent,2019-03-25 18:00:16,golang/go,https://api.github.com/repos/golang/go,closed,"cmd/go: building Go distribution from source fails with ""missing $GOPATH""",Documentation NeedsFix release-blocker,"On an amd64 GNU/Linux system with no `GOPATH` set in the environment, and with the Go source code at `$HOME/go` so that the default `GOPATH` setting does not work, running make.bash fails with

```
Building Go cmd/dist using /usr/local/google/home/iant/go1.4.
Building Go toolchain1 using /usr/local/google/home/iant/go1.4.
Building Go bootstrap cmd/go (go_bootstrap) using Go toolchain1.
Building Go toolchain2 using go_bootstrap and Go toolchain1.
missing $GOPATH
go tool dist: FAILED: /usr/local/google/home/iant/go/pkg/tool/linux_amd64/go_bootstrap install -gcflags=all= -ldflags=all= -i cmd/asm cmd/cgo cmd/compile cmd/link: exit status 1
```",1.0,"cmd/go: building Go distribution from source fails with ""missing $GOPATH"" - On an amd64 GNU/Linux system with no `GOPATH` set in the environment, and with the Go source code at `$HOME/go` so that the default `GOPATH` setting does not work, running make.bash fails with

```
Building Go cmd/dist using /usr/local/google/home/iant/go1.4.
Building Go toolchain1 using /usr/local/google/home/iant/go1.4.
Building Go bootstrap cmd/go (go_bootstrap) using Go toolchain1.
Building Go toolchain2 using go_bootstrap and Go toolchain1.
missing $GOPATH
go tool dist: FAILED: /usr/local/google/home/iant/go/pkg/tool/linux_amd64/go_bootstrap install -gcflags=all= -ldflags=all= -i cmd/asm cmd/cgo cmd/compile cmd/link: exit status 1
```",1,cmd go  building go distribution from source fails with  missing  gopath    on an   gnu linux system with no  gopath  set in the environment  and with the go source code at   home go  so that the default  gopath  setting does not work  running make bash fails with         building go cmd dist using  usr local google home iant       building go   using  usr local google home iant       building go bootstrap cmd go  go bootstrap  using go     building go   using go bootstrap and go     missing  gopath  go tool dist  failed   usr local google home iant go pkg tool linux   go bootstrap install  gcflags all   ldflags all   i cmd asm cmd cgo cmd compile cmd link  exit status       ,1
245983,26577428633.0,IssuesEvent,2023-01-22 01:13:40,Trinadh465/device_renesas_kernel_AOSP10_r33_CVE-2021-33034,https://api.github.com/repos/Trinadh465/device_renesas_kernel_AOSP10_r33_CVE-2021-33034,closed,CVE-2022-41858 (Medium) detected in linuxlinux-4.19.239 - autoclosed,security vulnerability,"## CVE-2022-41858 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.19.239</b></p></summary>
<p>

<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/net/slip/slip.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/net/slip/slip.c</b>
</p>
</details>
<p></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>  
  
A NULL pointer dereference was discovered in Linux Kernel. When a slip driver is detaching, the slip_close() will act to
cleanup necessary resources and sl->tty is set to NULL in
slip_close(). Meanwhile, the packet we transmit is blocked,
sl_tx_timeout() will be called. Although slip_close() and
sl_tx_timeout() use sl->lock to synchronize, we don`t judge
whether sl->tty equals to NULL in sl_tx_timeout() and the
null pointer dereference bug will happen.

<p>Publish Date: 2022-09-30
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-41858>CVE-2022-41858</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>4.4</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: Low
  - Privileges Required: High
  - 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://www.linuxkernelcves.com/cves/CVE-2022-41858"">https://www.linuxkernelcves.com/cves/CVE-2022-41858</a></p>
<p>Release Date: 2022-09-30</p>
<p>Fix Resolution: v4.9.311,v4.14.276,v4.19.239,v5.4.190,v5.10.112,v5.15.35,v5.17.4,v5.18-rc2</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2022-41858 (Medium) detected in linuxlinux-4.19.239 - autoclosed - ## CVE-2022-41858 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.19.239</b></p></summary>
<p>

<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/net/slip/slip.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/net/slip/slip.c</b>
</p>
</details>
<p></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>  
  
A NULL pointer dereference was discovered in Linux Kernel. When a slip driver is detaching, the slip_close() will act to
cleanup necessary resources and sl->tty is set to NULL in
slip_close(). Meanwhile, the packet we transmit is blocked,
sl_tx_timeout() will be called. Although slip_close() and
sl_tx_timeout() use sl->lock to synchronize, we don`t judge
whether sl->tty equals to NULL in sl_tx_timeout() and the
null pointer dereference bug will happen.

<p>Publish Date: 2022-09-30
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-41858>CVE-2022-41858</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>4.4</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: Low
  - Privileges Required: High
  - 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://www.linuxkernelcves.com/cves/CVE-2022-41858"">https://www.linuxkernelcves.com/cves/CVE-2022-41858</a></p>
<p>Release Date: 2022-09-30</p>
<p>Fix Resolution: v4.9.311,v4.14.276,v4.19.239,v5.4.190,v5.10.112,v5.15.35,v5.17.4,v5.18-rc2</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      medium  detected in linuxlinux         autoclosed      cve       medium severity vulnerability     vulnerable library    linuxlinux              the linux kernel   library home page   a href     found in base branch   master             vulnerable source files                  drivers net slip slip c        drivers net slip slip c                    vulnerability details         a null pointer dereference was discovered in linux kernel  when a slip driver is detaching  the slip close   will act to cleanup necessary resources and sl  tty is set to null in slip close    meanwhile  the packet we transmit is blocked  sl tx timeout   will be called  although slip close   and sl tx timeout   use sl  lock to synchronize  we don t judge whether sl  tty equals to null in sl tx timeout   and the null pointer dereference bug will happen    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  local     attack complexity  low     privileges required  high     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                                                                step up your open source security game with mend    ,0
143774,19248619072.0,IssuesEvent,2021-12-09 01:07:29,Benderr-TP/blip,https://api.github.com/repos/Benderr-TP/blip,opened,CVE-2018-3728 (High) detected in hoek-2.16.3.tgz,security vulnerability,"## CVE-2018-3728 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hoek-2.16.3.tgz</b></p></summary>

<p>General purpose node utilities</p>
<p>Library home page: <a href=""https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz"">https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz</a></p>
<p>

Dependency Hierarchy:
  - gitbook-cli-2.3.2.tgz (Root Library)
    - npm-5.1.0.tgz
      - request-2.81.0.tgz
        - hawk-3.1.3.tgz
          - :x: **hoek-2.16.3.tgz** (Vulnerable Library)
<p>Found in base branch: <b>develop</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>  
  
hoek node module before 4.2.0 and 5.0.x before 5.0.3 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via 'merge' and 'applyToDefaults' functions, which allows a malicious user to modify the prototype of ""Object"" via __proto__, causing the addition or modification of an existing property that will exist on all objects.

<p>Publish Date: 2018-03-30
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3728>CVE-2018-3728</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>8.8</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16082"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16082</a></p>
<p>Release Date: 2018-03-30</p>
<p>Fix Resolution: 4.2.0,5.0.3</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":false,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""hoek"",""packageVersion"":""2.16.3"",""packageFilePaths"":[],""isTransitiveDependency"":true,""dependencyTree"":""gitbook-cli:2.3.2;npm:5.1.0;request:2.81.0;hawk:3.1.3;hoek:2.16.3"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""4.2.0,5.0.3"",""isBinary"":true}],""baseBranches"":[""develop""],""vulnerabilityIdentifier"":""CVE-2018-3728"",""vulnerabilityDetails"":""hoek node module before 4.2.0 and 5.0.x before 5.0.3 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via \u0027merge\u0027 and \u0027applyToDefaults\u0027 functions, which allows a malicious user to modify the prototype of \""Object\"" via __proto__, causing the addition or modification of an existing property that will exist on all objects."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3728"",""cvss3Severity"":""high"",""cvss3Score"":""8.8"",""cvss3Metrics"":{""A"":""High"",""AC"":""Low"",""PR"":""Low"",""S"":""Unchanged"",""C"":""High"",""UI"":""None"",""AV"":""Network"",""I"":""High""},""extraData"":{}}</REMEDIATE> -->",True,"CVE-2018-3728 (High) detected in hoek-2.16.3.tgz - ## CVE-2018-3728 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hoek-2.16.3.tgz</b></p></summary>

<p>General purpose node utilities</p>
<p>Library home page: <a href=""https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz"">https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz</a></p>
<p>

Dependency Hierarchy:
  - gitbook-cli-2.3.2.tgz (Root Library)
    - npm-5.1.0.tgz
      - request-2.81.0.tgz
        - hawk-3.1.3.tgz
          - :x: **hoek-2.16.3.tgz** (Vulnerable Library)
<p>Found in base branch: <b>develop</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>  
  
hoek node module before 4.2.0 and 5.0.x before 5.0.3 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via 'merge' and 'applyToDefaults' functions, which allows a malicious user to modify the prototype of ""Object"" via __proto__, causing the addition or modification of an existing property that will exist on all objects.

<p>Publish Date: 2018-03-30
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3728>CVE-2018-3728</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>8.8</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16082"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16082</a></p>
<p>Release Date: 2018-03-30</p>
<p>Fix Resolution: 4.2.0,5.0.3</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":false,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""hoek"",""packageVersion"":""2.16.3"",""packageFilePaths"":[],""isTransitiveDependency"":true,""dependencyTree"":""gitbook-cli:2.3.2;npm:5.1.0;request:2.81.0;hawk:3.1.3;hoek:2.16.3"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""4.2.0,5.0.3"",""isBinary"":true}],""baseBranches"":[""develop""],""vulnerabilityIdentifier"":""CVE-2018-3728"",""vulnerabilityDetails"":""hoek node module before 4.2.0 and 5.0.x before 5.0.3 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via \u0027merge\u0027 and \u0027applyToDefaults\u0027 functions, which allows a malicious user to modify the prototype of \""Object\"" via __proto__, causing the addition or modification of an existing property that will exist on all objects."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3728"",""cvss3Severity"":""high"",""cvss3Score"":""8.8"",""cvss3Metrics"":{""A"":""High"",""AC"":""Low"",""PR"":""Low"",""S"":""Unchanged"",""C"":""High"",""UI"":""None"",""AV"":""Network"",""I"":""High""},""extraData"":{}}</REMEDIATE> -->",0,cve      high  detected in hoek       tgz      cve       high severity vulnerability     vulnerable library    hoek       tgz      general purpose node utilities   library home page   a href       dependency hierarchy      gitbook cli       tgz  root library        npm       tgz         request       tgz           hawk       tgz              x    hoek       tgz    vulnerable library   found in base branch   develop              vulnerability details         hoek node module before       and     x before       suffers from a modification of assumed immutable data  maid  vulnerability via  merge  and  applytodefaults  functions  which allows a malicious user to modify the prototype of  object  via   proto    causing the addition or modification of an existing property that will exist on all objects    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  low     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                           isopenpronvulnerability  false  ispackagebased  true  isdefaultbranch  true  packages     istransitivedependency  true  dependencytree   gitbook cli       npm       request       hawk       hoek         isminimumfixversionavailable  true  minimumfixversion                 isbinary  true    basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   hoek node module before       and     x before       suffers from a modification of assumed immutable data  maid  vulnerability via      and      functions  which allows a malicious user to modify the prototype of   object   via   proto    causing the addition or modification of an existing property that will exist on all objects    vulnerabilityurl        ,0
180410,21625728162.0,IssuesEvent,2022-05-05 01:41:09,Sh2dowFi3nd/Test_2,https://api.github.com/repos/Sh2dowFi3nd/Test_2,closed,CVE-2012-0213 (Medium) detected in poi-3.8.jar - autoclosed,security vulnerability,"## CVE-2012-0213 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>poi-3.8.jar</b></p></summary>

<p>Apache POI - Java API To Access Microsoft Format Files</p>
<p>Library home page: <a href=""http://poi.apache.org/"">http://poi.apache.org/</a></p>
<p>

Dependency Hierarchy:
  - :x: **poi-3.8.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/Sh2dowFi3nd/Test_2/commit/496ee93a49670cf2906171c7293cf9b50cc09d47"">496ee93a49670cf2906171c7293cf9b50cc09d47</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The UnhandledDataStructure function in hwpf/model/UnhandledDataStructure.java in Apache POI 3.8 and earlier allows remote attackers to cause a denial of service (OutOfMemoryError exception and possibly JVM destabilization) via a crafted length value in a Channel Definition Format (CDF) or Compound File Binary Format (CFBF) document.

<p>Publish Date: 2012-08-07
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0213>CVE-2012-0213</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>5.0</b>)</summary>
<p>

Base Score Metrics not available</p>

</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0213"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0213</a></p>
<p>Release Date: 2012-08-07</p>
<p>Fix Resolution: org.apache.poi:poi-scratchpad:3.9,org.apache.poi:poi:3.9</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-2012-0213 (Medium) detected in poi-3.8.jar - autoclosed - ## CVE-2012-0213 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>poi-3.8.jar</b></p></summary>

<p>Apache POI - Java API To Access Microsoft Format Files</p>
<p>Library home page: <a href=""http://poi.apache.org/"">http://poi.apache.org/</a></p>
<p>

Dependency Hierarchy:
  - :x: **poi-3.8.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/Sh2dowFi3nd/Test_2/commit/496ee93a49670cf2906171c7293cf9b50cc09d47"">496ee93a49670cf2906171c7293cf9b50cc09d47</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The UnhandledDataStructure function in hwpf/model/UnhandledDataStructure.java in Apache POI 3.8 and earlier allows remote attackers to cause a denial of service (OutOfMemoryError exception and possibly JVM destabilization) via a crafted length value in a Channel Definition Format (CDF) or Compound File Binary Format (CFBF) document.

<p>Publish Date: 2012-08-07
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0213>CVE-2012-0213</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>5.0</b>)</summary>
<p>

Base Score Metrics not available</p>

</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0213"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0213</a></p>
<p>Release Date: 2012-08-07</p>
<p>Fix Resolution: org.apache.poi:poi-scratchpad:3.9,org.apache.poi:poi:3.9</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      medium  detected in poi     jar   autoclosed      cve       medium severity vulnerability     vulnerable library    poi     jar      apache poi   java api to access microsoft format files   library home page   a href       dependency hierarchy       x    poi     jar    vulnerable library   found in head commit   a href               vulnerability details         the unhandleddatastructure function in hwpf model unhandleddatastructure java in apache poi     and earlier allows remote attackers to cause a denial of service  outofmemoryerror exception and possibly jvm destabilization  via a crafted length value in a channel definition format  cdf  or compound file binary format  cfbf  document    publish date         url   a href              cvss   score details             base score metrics not available              suggested fix      type  upgrade version   origin   a href     release date          fix resolution  org apache poi poi scratchpad     org apache poi poi                   step up your open source security game with whitesource    ,0
182403,14913986345.0,IssuesEvent,2021-01-22 14:51:11,golang/go,https://api.github.com/repos/golang/go,closed,time: Timer.Reset documentation not accurate for AfterFunc timers,Documentation NeedsFix help wanted,"https://golang.org/pkg/time/#Timer.Reset says:

> Resetting a timer must take care not to race with the send into t.C that happens when the current timer expires. If a program has already received a value from t.C, the timer is known to have expired, and t.Reset can be used directly. If a program has not yet received a value from t.C, however, the timer must be stopped and—if Stop reports that the timer expired before being stopped—the channel explicitly drained:

And proceeds to give an example of proper usage of Reset.

But a Timer created by [AfterFunc](https://golang.org/pkg/time/#AfterFunc) never sends on the channel.

We should probably say something about AfterFunc in the Timer.Reset docs.

/cc @dmitshur @ianlancetaylor  ",1.0,"time: Timer.Reset documentation not accurate for AfterFunc timers - https://golang.org/pkg/time/#Timer.Reset says:

> Resetting a timer must take care not to race with the send into t.C that happens when the current timer expires. If a program has already received a value from t.C, the timer is known to have expired, and t.Reset can be used directly. If a program has not yet received a value from t.C, however, the timer must be stopped and—if Stop reports that the timer expired before being stopped—the channel explicitly drained:

And proceeds to give an example of proper usage of Reset.

But a Timer created by [AfterFunc](https://golang.org/pkg/time/#AfterFunc) never sends on the channel.

We should probably say something about AfterFunc in the Timer.Reset docs.

/cc @dmitshur @ianlancetaylor  ",1,time  timer reset documentation not accurate for afterfunc timers     says       resetting a timer must take care not to race with the send into t c that happens when the current timer expires  if a program has already received a value from t c  the timer is known to have expired  and t reset can be used directly  if a program has not yet received a value from t c  however  the timer must be stopped and—if stop reports that the timer expired before being stopped—the channel explicitly drained     and proceeds to give an example of proper usage of reset     but a timer created by     never sends on the channel     we should probably say something about afterfunc in the timer reset docs      cc  dmitshur  ianlancetaylor  ,1
304901,23089769467.0,IssuesEvent,2022-07-26 14:21:20,golang/go,https://api.github.com/repos/golang/go,closed,bytes: Reader.Size method documentation is inaccurate,Documentation NeedsFix,"<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

Documentation issue; currently visible default version is 1.18.4

### Does this issue reproduce with the latest release?

Yes, 1.18.4 is the latest release. This doesn't seem to have been fixed as of 1.19rc2 either.

### What operating system and processor architecture are you using (`go env`)?

N/A (platform-agnostic documentation issue)

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->

Viewed the docs for [`Reader.Size`](https://pkg.go.dev/bytes#Reader.Size) method in `bytes` standard library package

### What did you expect to see?

The [`Reader.Reset`](https://pkg.go.dev/bytes#Reader.Reset) method can change the underlying byte slice. The docs for `Size` method should say something like (changes italicized):

> Size returns the original length of the underlying byte slice. Size is the number of bytes available for reading via ReadAt. The returned value _will not change between calls unless the byte slice is changed by Reset_.

### What did you see instead?

The docs currently say:

> Size returns the original length of the underlying byte slice. Size is the number of bytes available for reading via ReadAt. The returned value is always the same and is not affected by calls to any other method.

The `Reset` method is the only violation of this wording, and it was added in Go 1.7, but the `Size` method dates back to 1.5. This minor documentation issue seems to have arisen because an assumption (immutability of the byte slice) changed between versions of the language/library.",1.0,"bytes: Reader.Size method documentation is inaccurate - <!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

Documentation issue; currently visible default version is 1.18.4

### Does this issue reproduce with the latest release?

Yes, 1.18.4 is the latest release. This doesn't seem to have been fixed as of 1.19rc2 either.

### What operating system and processor architecture are you using (`go env`)?

N/A (platform-agnostic documentation issue)

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->

Viewed the docs for [`Reader.Size`](https://pkg.go.dev/bytes#Reader.Size) method in `bytes` standard library package

### What did you expect to see?

The [`Reader.Reset`](https://pkg.go.dev/bytes#Reader.Reset) method can change the underlying byte slice. The docs for `Size` method should say something like (changes italicized):

> Size returns the original length of the underlying byte slice. Size is the number of bytes available for reading via ReadAt. The returned value _will not change between calls unless the byte slice is changed by Reset_.

### What did you see instead?

The docs currently say:

> Size returns the original length of the underlying byte slice. Size is the number of bytes available for reading via ReadAt. The returned value is always the same and is not affected by calls to any other method.

The `Reset` method is the only violation of this wording, and it was added in Go 1.7, but the `Size` method dates back to 1.5. This minor documentation issue seems to have arisen because an assumption (immutability of the byte slice) changed between versions of the language/library.",1,bytes  reader size method documentation is inaccurate         please answer these questions before submitting your issue  thanks              what version of go are you using   go version       documentation issue  currently visible default version is              does this issue reproduce with the latest release     yes        is the latest release  this doesn t seem to have been fixed as of     either         what operating system and processor architecture are you using   go env       n a  platform agnostic documentation issue         what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on go dev play is best          viewed the docs for     method in  bytes  standard library package        what did you expect to see     the     method can change the underlying byte slice  the docs for  size  method should say something like  changes italicized        size returns the original length of the underlying byte slice  size is the number of bytes available for reading via readat  the returned value  will not change between calls unless the byte slice is changed by reset          what did you see instead     the docs currently say       size returns the original length of the underlying byte slice  size is the number of bytes available for reading via readat  the returned value is always the same and is not affected by calls to any other method     the  reset  method is the only violation of this wording  and it was added in go      but the  size  method dates back to      this minor documentation issue seems to have arisen because an assumption  immutability of the byte slice  changed between versions of the language library ,1
22100,4773034418.0,IssuesEvent,2016-10-26 22:46:43,golang/go,https://api.github.com/repos/golang/go,closed,net/http/httptest: Better document usage of ResponseRecorder.HeaderMap vs. ResponseRecorder.Result,Documentation NeedsFix,"The Go 1.7 release notes say:

> The ResponseRecorder's new Result method returns the recorded http.Response. Tests that need to check the response's headers or trailers should call Result and inspect the response fields instead of accessing ResponseRecorder's HeaderMap directly.

However, the documentation itself doesn't give much guidance. The closest it says is

> The Response.Header is a snapshot of the headers at the time of the first write call, or at the time of this call, if the handler never did a write.

If I were just reading the httptest docs, I would probably just use HeaderMap as it's more convenient. It would be good to put a caveat by the definition of HeaderMap.",1.0,"net/http/httptest: Better document usage of ResponseRecorder.HeaderMap vs. ResponseRecorder.Result - The Go 1.7 release notes say:

> The ResponseRecorder's new Result method returns the recorded http.Response. Tests that need to check the response's headers or trailers should call Result and inspect the response fields instead of accessing ResponseRecorder's HeaderMap directly.

However, the documentation itself doesn't give much guidance. The closest it says is

> The Response.Header is a snapshot of the headers at the time of the first write call, or at the time of this call, if the handler never did a write.

If I were just reading the httptest docs, I would probably just use HeaderMap as it's more convenient. It would be good to put a caveat by the definition of HeaderMap.",1,net http httptest  better document usage of responserecorder headermap vs  responserecorder result   the go     release notes say       the responserecorder s new result method returns the recorded http response  tests that need to check the response s headers or trailers should call result and inspect the response fields instead of accessing responserecorder s headermap directly     however  the documentation itself doesn t give much guidance  the closest it says is      the response header is a snapshot of the headers at the time of the first write call  or at the time of this call  if the handler never did a write     if i were just reading the httptest docs  i would probably just use headermap as it s more convenient  it would be good to put a caveat by the definition of headermap ,1
32731,6105403670.0,IssuesEvent,2017-06-20 23:40:43,golang/go,https://api.github.com/repos/golang/go,closed,crypto/x509: ParseCertificate returns a certificate with MaxPathLen of -1 if pathLenConstraint is not set,Documentation NeedsDecision,"Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?

`go version go1.7.4 darwin/amd64`

### What operating system and processor architecture are you using (`go env`)?

```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/cyli/Go""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.7.4/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.7.4/libexec/pkg/tool/darwin_amd64""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/v9/wzpq8hm56b943960j1qrnblm0000gp/T/go-build860790401=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
```

### What did you do?

I parsed a CA certificate which did not have `pathLenConstraint` set:  https://play.golang.org/p/lFCQJQPRLh

### What did you expect to see?

Given the following comment in https://golang.org/pkg/crypto/x509/#Certificate:

```
        // MaxPathLenZero indicates that BasicConstraintsValid==true and
        // MaxPathLen==0 should be interpreted as an actual maximum path length
        // of zero. Otherwise, that combination is interpreted as MaxPathLen
        // not being set.
``` 
and that [RFC5280 4.2.1.9](https://tools.ietf.org/html/rfc5280#section-4.2.1.9) specifies that the `pathLenConstraint` must be >= 0, I expected to see `MaxPathLen` as 0 and `MaxPathLenZero` as false.

### What did you see instead?

`MaxPathLen` was -1 and `MaxPathLenZero` was false.

I don't oppose using `-1` to indicate that it wasn't set, but comments for `MaxPathLen`, etc. imply that `-1` is not valid.  If `-1` is a valid value, should the docs be updated and possibly `MaxPathLenZero` be deprecated?",1.0,"crypto/x509: ParseCertificate returns a certificate with MaxPathLen of -1 if pathLenConstraint is not set - Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?

`go version go1.7.4 darwin/amd64`

### What operating system and processor architecture are you using (`go env`)?

```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/cyli/Go""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.7.4/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.7.4/libexec/pkg/tool/darwin_amd64""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/v9/wzpq8hm56b943960j1qrnblm0000gp/T/go-build860790401=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
```

### What did you do?

I parsed a CA certificate which did not have `pathLenConstraint` set:  https://play.golang.org/p/lFCQJQPRLh

### What did you expect to see?

Given the following comment in https://golang.org/pkg/crypto/x509/#Certificate:

```
        // MaxPathLenZero indicates that BasicConstraintsValid==true and
        // MaxPathLen==0 should be interpreted as an actual maximum path length
        // of zero. Otherwise, that combination is interpreted as MaxPathLen
        // not being set.
``` 
and that [RFC5280 4.2.1.9](https://tools.ietf.org/html/rfc5280#section-4.2.1.9) specifies that the `pathLenConstraint` must be >= 0, I expected to see `MaxPathLen` as 0 and `MaxPathLenZero` as false.

### What did you see instead?

`MaxPathLen` was -1 and `MaxPathLenZero` was false.

I don't oppose using `-1` to indicate that it wasn't set, but comments for `MaxPathLen`, etc. imply that `-1` is not valid.  If `-1` is a valid value, should the docs be updated and possibly `MaxPathLenZero` be deprecated?",1,crypto    parsecertificate returns a certificate with maxpathlen of    if pathlenconstraint is not set   please answer these questions before submitting your issue  thanks         what version of go are you using   go version        go version       darwin           what operating system and processor architecture are you using   go env            goarch      gobin     goexe     gohostarch      gohostos  darwin   goos  darwin   gopath   users cyli go   gorace     goroot   usr local cellar go       libexec   gotooldir   usr local cellar go       libexec pkg tool darwin     cc  clang   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders     t go    tmp go build  gno record gcc switches  fno common   cxx  clang     cgo enabled                 what did you do     i parsed a ca certificate which did not have  pathlenconstraint  set            what did you expect to see     given the following comment in                      maxpathlenzero indicates that basicconstraintsvalid  true and             maxpathlen    should be interpreted as an actual maximum path length             of zero  otherwise  that combination is interpreted as maxpathlen             not being set         and that     specifies that the  pathlenconstraint  must be       i expected to see  maxpathlen  as   and  maxpathlenzero  as false         what did you see instead      maxpathlen  was    and  maxpathlenzero  was false     i don t oppose using      to indicate that it wasn t set  but comments for  maxpathlen   etc  imply that      is not valid   if      is a valid value  should the docs be updated and possibly  maxpathlenzero  be deprecated ,1
145862,22821740793.0,IssuesEvent,2022-07-12 03:31:17,raerpo/lupper,https://api.github.com/repos/raerpo/lupper,opened,Home page animation,design,Every awesome startup needs a great animation. Maybe something that uses threejs with blender 🤔 ,1.0,Home page animation - Every awesome startup needs a great animation. Maybe something that uses threejs with blender 🤔 ,0,home page animation   every awesome startup needs a great animation  maybe something that uses threejs with blender 🤔 ,0
214635,16569051449.0,IssuesEvent,2021-05-30 02:38:18,golang/go,https://api.github.com/repos/golang/go,closed,go/types: unexport the GoVersion configuration option for Go 1.17,Documentation NeedsFix release-blocker,"`+pkg go/types, type Config struct, GoVersion string`

The `GoVersion` field was added to `types.Config` to configure the language version being type checked.

CC @griesemer ",1.0,"go/types: unexport the GoVersion configuration option for Go 1.17 - `+pkg go/types, type Config struct, GoVersion string`

The `GoVersion` field was added to `types.Config` to configure the language version being type checked.

CC @griesemer ",1,go types  unexport the goversion configuration option for go         pkg go types  type config struct  goversion string     the  goversion  field was added to  types config  to configure the language version being type checked     cc  griesemer ,1
68844,29765572908.0,IssuesEvent,2023-06-15 00:22:13,Azure/azure-sdk-for-net,https://api.github.com/repos/Azure/azure-sdk-for-net,closed,[BUG] EventsResults Not show @odata:count when send parameter count: true,Monitor Service Attention Client customer-reported question Monitor - ApplicationInsights needs-team-attention,"**Describe the bug**
I'm using the library for Microsoft.Azure.ApplicationInsights.Query and when I made the request through the method client.Events.GetCustomEventsAsync, the response didn't contain the value for the global count.

**Expected behavior**
When make a call to the Application Insight REST API, it returns a json object with those properties:
```json
 ...
    }
  ],
  ""@odata.count"": 17389
}
```
The value for @odata.count didn't exist on the model for the response.

I reviewed the code and saw that in the model Microsoft.Azure.ApplicationInsights.Query.Models.EventsResults this property not exist (and it couldn't be parsed):
```
       [JsonProperty(PropertyName = ""@odata.context"")]
        public string Odatacontext { get; set; }

       ///THIS PROPERTY MUST EXIST IN THE MODEL, but not
       [JsonProperty(PropertyName = ""@odata.count"")]
        public string Odatacount { get; set; }
```
I think that it missed the most kind of Models in the library.

**To Reproduce**
1. Configure the AppInsight client
2. Make a call 
```
var events = await client.Events.GetCustomEventsAsync(appId, timespan, count: true, cancellationToken: cancellationToken); 
```
3. Expected result must have the global count, but doesn't exist.

**Environment:**
 - Name and version of the Library package used: MicrosoftApplicationInsightsQuery 1.0.0
 - Hosting platform or OS and .NET runtime version: Any
 - IDE and version : Visual Studio 16.9.5
",1.0,"[BUG] EventsResults Not show @odata:count when send parameter count: true - **Describe the bug**
I'm using the library for Microsoft.Azure.ApplicationInsights.Query and when I made the request through the method client.Events.GetCustomEventsAsync, the response didn't contain the value for the global count.

**Expected behavior**
When make a call to the Application Insight REST API, it returns a json object with those properties:
```json
 ...
    }
  ],
  ""@odata.count"": 17389
}
```
The value for @odata.count didn't exist on the model for the response.

I reviewed the code and saw that in the model Microsoft.Azure.ApplicationInsights.Query.Models.EventsResults this property not exist (and it couldn't be parsed):
```
       [JsonProperty(PropertyName = ""@odata.context"")]
        public string Odatacontext { get; set; }

       ///THIS PROPERTY MUST EXIST IN THE MODEL, but not
       [JsonProperty(PropertyName = ""@odata.count"")]
        public string Odatacount { get; set; }
```
I think that it missed the most kind of Models in the library.

**To Reproduce**
1. Configure the AppInsight client
2. Make a call 
```
var events = await client.Events.GetCustomEventsAsync(appId, timespan, count: true, cancellationToken: cancellationToken); 
```
3. Expected result must have the global count, but doesn't exist.

**Environment:**
 - Name and version of the Library package used: MicrosoftApplicationInsightsQuery 1.0.0
 - Hosting platform or OS and .NET runtime version: Any
 - IDE and version : Visual Studio 16.9.5
",0,  eventsresults not show  odata count when send parameter count  true     describe the bug    i m using the library for microsoft azure applicationinsights query and when i made the request through the method client events getcustomeventsasync  the response didn t contain the value for the global count       expected behavior    when make a call to the application insight rest api  it returns a json object with those properties      json                         odata count              the value for  odata count didn t exist on the model for the response     i reviewed the code and saw that in the model microsoft azure applicationinsights query models eventsresults this property not exist  and it couldn t be parsed                           public string odatacontext   get  set                 this property must exist in the model  but not                    public string odatacount   get  set          i think that it missed the most kind of models in the library       to reproduce       configure the appinsight client     make a call        var events   await client events getcustomeventsasync appid  timespan  count  true  cancellationtoken  cancellationtoken             expected result must have the global count  but doesn t exist       environment        name and version of the library package used  microsoftapplicationinsightsquery           hosting platform or os and  net runtime version  any     ide and version   visual studio        ,0
71614,18795141684.0,IssuesEvent,2021-11-08 21:19:36,MobiFlight/MobiFlight-FirmwareSource,https://api.github.com/repos/MobiFlight/MobiFlight-FirmwareSource,closed,Add CodeTour explaining how versioning works,Build process,"* Local vs release builds
* How to override the local build number
* Add CodeTour as a recommended vscode extension",1.0,"Add CodeTour explaining how versioning works - * Local vs release builds
* How to override the local build number
* Add CodeTour as a recommended vscode extension",0,add codetour explaining how versioning works     local vs release builds    how to override the local build number    add codetour as a recommended vscode extension,0
19320,13213905676.0,IssuesEvent,2020-08-16 15:08:46,ForNeVeR/AvaloniaRider,https://api.github.com/repos/ForNeVeR/AvaloniaRider,closed,Use JavaFX Runtime for Plugins,kind:infrastructure,"In 2020.2, JavaFX gets unbundled from the IntelliJ platform. So, to properly utilize the web view in the plugin, we'll need to depend on [JavaFX Runtime for Plugins](https://plugins.jetbrains.com/plugin/14250-javafx-runtime-for-plugins).",1.0,"Use JavaFX Runtime for Plugins - In 2020.2, JavaFX gets unbundled from the IntelliJ platform. So, to properly utilize the web view in the plugin, we'll need to depend on [JavaFX Runtime for Plugins](https://plugins.jetbrains.com/plugin/14250-javafx-runtime-for-plugins).",0,use javafx runtime for plugins   in      javafx gets unbundled from the intellij platform  so  to properly utilize the web view in the plugin  we ll need to depend on    ,0
11613,3508959598.0,IssuesEvent,2016-01-08 20:18:42,golang/go,https://api.github.com/repos/golang/go,closed,math/big: Typo in the documentation of Int.DivMod,Documentation,"The documentation for DivMod, in the big library, suggests that z.DivMod(x,y,w) sets z to the quotient q and w to the modulus m, where q and m satisfy
> m = x - y*q  with 0 <= m < |q|

I believe that this should read
> m = x - y*q  with 0 <= m < |y|

so that it agrees with the reference mentioned in the documentation for DivMod: Raymond T. Boute, “The Euclidean definition of the functions div and mod”. ACM Transactions on Programming Languages and Systems (TOPLAS), 14(2):127-144, New York, NY, USA, 4/1992. ACM press. ",1.0,"math/big: Typo in the documentation of Int.DivMod - The documentation for DivMod, in the big library, suggests that z.DivMod(x,y,w) sets z to the quotient q and w to the modulus m, where q and m satisfy
> m = x - y*q  with 0 <= m < |q|

I believe that this should read
> m = x - y*q  with 0 <= m < |y|

so that it agrees with the reference mentioned in the documentation for DivMod: Raymond T. Boute, “The Euclidean definition of the functions div and mod”. ACM Transactions on Programming Languages and Systems (TOPLAS), 14(2):127-144, New York, NY, USA, 4/1992. ACM press. ",1,math big  typo in the documentation of int divmod   the documentation for divmod  in the big library  suggests that z divmod x y w  sets z to the quotient q and w to the modulus m  where q and m satisfy    m   x   y q  with      m    q     i believe that this should read    m   x   y q  with      m    y     so that it agrees with the reference mentioned in the documentation for divmod  raymond t  boute  “the euclidean definition of the functions div and mod”  acm transactions on programming languages and systems  toplas             new york  ny  usa       acm press  ,1
150190,13325334725.0,IssuesEvent,2020-08-27 09:48:27,golang/go,https://api.github.com/repos/golang/go,closed,doc: include fix for #34437 in Go 1.14 release notes,Documentation NeedsFix help wanted,"Hello,

I wanted to reach out and see whether there is an interest in the fix for #34437 being included in the Go release notes. Someone I know was finally working through upgrading to Go 1.14 and ran in to some peculiar issues with their JSON being unmarshaled differently. Here is that commit on our side:

- https://github.com/golang/go/commit/fb9af8411eaa3e38d2f72e28a305772f50042657#diff-4299c3082a8bb7e546723132c992fa4c

It took them some time to figure it out, while it having been mentioned in the release notes could have saved them some time (as they looked there first). I understand we can't document all fixes without the release notes becoming silly, but wondered whether that change may meet the bar of inclusion.

Cheers!",1.0,"doc: include fix for #34437 in Go 1.14 release notes - Hello,

I wanted to reach out and see whether there is an interest in the fix for #34437 being included in the Go release notes. Someone I know was finally working through upgrading to Go 1.14 and ran in to some peculiar issues with their JSON being unmarshaled differently. Here is that commit on our side:

- https://github.com/golang/go/commit/fb9af8411eaa3e38d2f72e28a305772f50042657#diff-4299c3082a8bb7e546723132c992fa4c

It took them some time to figure it out, while it having been mentioned in the release notes could have saved them some time (as they looked there first). I understand we can't document all fixes without the release notes becoming silly, but wondered whether that change may meet the bar of inclusion.

Cheers!",1,doc  include fix for    in go     release notes   hello     i wanted to reach out and see whether there is an interest in the fix for    being included in the go release notes  someone i know was finally working through upgrading to go     and ran in to some peculiar issues with their json being unmarshaled differently  here is that commit on our side            it took them some time to figure it out  while it having been mentioned in the release notes could have saved them some time  as they looked there first   i understand we can t document all fixes without the release notes becoming silly  but wondered whether that change may meet the bar of inclusion     cheers ,1
104785,16621965645.0,IssuesEvent,2021-06-03 03:16:51,dreamboy9/fuchsia,https://api.github.com/repos/dreamboy9/fuchsia,opened,CVE-2019-12900 (High) detected in bzip2-sys-0.1.7.crate,security vulnerability,"## CVE-2019-12900 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>bzip2-sys-0.1.7.crate</b></p></summary>

<p>Bindings to libbzip2 for bzip2 compression and decompression exposed as
Reader/Writer streams.
</p>
<p>Library home page: <a href=""https://crates.io/api/v1/crates/bzip2-sys/0.1.7/download"">https://crates.io/api/v1/crates/bzip2-sys/0.1.7/download</a></p>
<p>

Dependency Hierarchy:
  - bzip2-0.3.3.crate (Root Library)
    - :x: **bzip2-sys-0.1.7.crate** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/dreamboy9/fuchsia/commit/4ec0c406a28f193fe6e7376ee7696cca0532d4ba"">4ec0c406a28f193fe6e7376ee7696cca0532d4ba</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>  
  
BZ2_decompress in decompress.c in bzip2 through 1.0.6 has an out-of-bounds write when there are many selectors.

<p>Publish Date: 2019-06-19
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-12900>CVE-2019-12900</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://gitlab.com/federicomenaquintero/bzip2/-/commit/812a898b7622de90e98f103ff7fed0984e4548e4#951eb5324dc64ed8c9225bfcdcb72ee7a3932918"">https://gitlab.com/federicomenaquintero/bzip2/-/commit/812a898b7622de90e98f103ff7fed0984e4548e4#951eb5324dc64ed8c9225bfcdcb72ee7a3932918</a></p>
<p>Release Date: 2020-05-24</p>
<p>Fix Resolution: 1.0.8</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2019-12900 (High) detected in bzip2-sys-0.1.7.crate - ## CVE-2019-12900 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>bzip2-sys-0.1.7.crate</b></p></summary>

<p>Bindings to libbzip2 for bzip2 compression and decompression exposed as
Reader/Writer streams.
</p>
<p>Library home page: <a href=""https://crates.io/api/v1/crates/bzip2-sys/0.1.7/download"">https://crates.io/api/v1/crates/bzip2-sys/0.1.7/download</a></p>
<p>

Dependency Hierarchy:
  - bzip2-0.3.3.crate (Root Library)
    - :x: **bzip2-sys-0.1.7.crate** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/dreamboy9/fuchsia/commit/4ec0c406a28f193fe6e7376ee7696cca0532d4ba"">4ec0c406a28f193fe6e7376ee7696cca0532d4ba</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>  
  
BZ2_decompress in decompress.c in bzip2 through 1.0.6 has an out-of-bounds write when there are many selectors.

<p>Publish Date: 2019-06-19
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-12900>CVE-2019-12900</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://gitlab.com/federicomenaquintero/bzip2/-/commit/812a898b7622de90e98f103ff7fed0984e4548e4#951eb5324dc64ed8c9225bfcdcb72ee7a3932918"">https://gitlab.com/federicomenaquintero/bzip2/-/commit/812a898b7622de90e98f103ff7fed0984e4548e4#951eb5324dc64ed8c9225bfcdcb72ee7a3932918</a></p>
<p>Release Date: 2020-05-24</p>
<p>Fix Resolution: 1.0.8</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in   sys       crate      cve       high severity vulnerability     vulnerable library      sys       crate      bindings to   for   compression and decompression exposed as reader writer streams     library home page   a href       dependency hierarchy              crate  root library         x      sys       crate    vulnerable library   found in head commit   a href     found in base branch   master              vulnerability details           decompress in decompress c in   through       has an out of bounds write when there are many selectors    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
65085,8787304684.0,IssuesEvent,2018-12-20 18:13:40,golang/go,https://api.github.com/repos/golang/go,closed,os: clarify documentation for O_TRUNC,Documentation NeedsInvestigation,"The comment for `os.O_TRUNC` currently says:
https://github.com/golang/go/blob/78c0e1f81d4052f8ca5a50e4e7c5bb35ddec6519/src/os/file.go#L76

The “if possible” part of that comment is ambiguous: on Linux it seems to mean “if the file is a regular file or symlink to a regular file” (i.e., not a stream like `/dev/stdout`), but it could be “impossible” to truncate the file for other reasons (such as a permission error), and `os.OpenFile` with `os.O_TRUNC` seems to report an error in those cases.

We should drop the “if possible” phrase and instead explicitly document the conditions under which `O_TRUNC` is ignored.",1.0,"os: clarify documentation for O_TRUNC - The comment for `os.O_TRUNC` currently says:
https://github.com/golang/go/blob/78c0e1f81d4052f8ca5a50e4e7c5bb35ddec6519/src/os/file.go#L76

The “if possible” part of that comment is ambiguous: on Linux it seems to mean “if the file is a regular file or symlink to a regular file” (i.e., not a stream like `/dev/stdout`), but it could be “impossible” to truncate the file for other reasons (such as a permission error), and `os.OpenFile` with `os.O_TRUNC` seems to report an error in those cases.

We should drop the “if possible” phrase and instead explicitly document the conditions under which `O_TRUNC` is ignored.",1,os  clarify documentation for o trunc   the comment for  os o trunc  currently says        the “if possible” part of that comment is ambiguous  on linux it seems to mean “if the file is a regular file or symlink to a regular file”  i e   not a stream like   dev stdout    but it could be “impossible” to truncate the file for other reasons  such as a permission error   and  os openfile  with  os o trunc  seems to report an error in those cases     we should drop the “if possible” phrase and instead explicitly document the conditions under which  o trunc  is ignored ,1
354373,25163542308.0,IssuesEvent,2022-11-10 18:43:35,golang/go,https://api.github.com/repos/golang/go,closed,os: document that WriteFile is not atomic,Documentation help wanted NeedsFix,"As I was replying to https://github.com/golang/go/issues/56172, I was looking at the docs for https://pkg.go.dev/os#WriteFile, which say:

```
// WriteFile writes data to the named file, creating it if necessary.
// If the file does not exist, WriteFile creates it with permissions perm (before umask);
// otherwise WriteFile truncates it before writing, without changing permissions.
func WriteFile(name string, data []byte, perm FileMode) error {
```

I know that this operation isn't atomic: for example, if a write to the file fails half-way through, we may be left with a partial file. That is why alternatives like https://pkg.go.dev/github.com/google/renameio#WriteFile exist.

However, by just reading the docs as a new user, it could be an easy misconception. A lot of the other `os` APIs like `Create`, `Mkdir`, or `Chmod` are atomic at the system level - they only perform a single system call which modifies the filesystem, so we can't be left with partial changes.

Perhaps we should add a godoc note that the API is not atomic. That is, that if an error occurs, the file might be left behind. I imagine this won't matter for many cases, but the warning would be very useful for any Go program which cares about invalid or incomplete states.

cc @ianlancetaylor @stapelberg ",1.0,"os: document that WriteFile is not atomic - As I was replying to https://github.com/golang/go/issues/56172, I was looking at the docs for https://pkg.go.dev/os#WriteFile, which say:

```
// WriteFile writes data to the named file, creating it if necessary.
// If the file does not exist, WriteFile creates it with permissions perm (before umask);
// otherwise WriteFile truncates it before writing, without changing permissions.
func WriteFile(name string, data []byte, perm FileMode) error {
```

I know that this operation isn't atomic: for example, if a write to the file fails half-way through, we may be left with a partial file. That is why alternatives like https://pkg.go.dev/github.com/google/renameio#WriteFile exist.

However, by just reading the docs as a new user, it could be an easy misconception. A lot of the other `os` APIs like `Create`, `Mkdir`, or `Chmod` are atomic at the system level - they only perform a single system call which modifies the filesystem, so we can't be left with partial changes.

Perhaps we should add a godoc note that the API is not atomic. That is, that if an error occurs, the file might be left behind. I imagine this won't matter for many cases, but the warning would be very useful for any Go program which cares about invalid or incomplete states.

cc @ianlancetaylor @stapelberg ",1,os  document that writefile is not atomic   as i was replying to   i was looking at the docs for   which say             writefile writes data to the named file  creating it if necessary      if the file does not exist  writefile creates it with permissions perm  before umask       otherwise writefile truncates it before writing  without changing permissions   func writefile name string  data  byte  perm filemode  error           i know that this operation isn t atomic  for example  if a write to the file fails half way through  we may be left with a partial file  that is why alternatives like   exist     however  by just reading the docs as a new user  it could be an easy misconception  a lot of the other  os  apis like  create    mkdir   or  chmod  are atomic at the system level   they only perform a single system call which modifies the filesystem  so we can t be left with partial changes     perhaps we should add a godoc note that the api is not atomic  that is  that if an error occurs  the file might be left behind  i imagine this won t matter for many cases  but the warning would be very useful for any go program which cares about invalid or incomplete states     cc  ianlancetaylor  stapelberg ,1
26295,5242638739.0,IssuesEvent,2017-01-31 18:35:54,golang/go,https://api.github.com/repos/golang/go,closed,go/types: confusing Object method comment,Documentation NeedsFix,"[type Object](https://golang.org/pkg/go/types/#Object) method `Id` docs read:

```
        Id() string     // object id (see Id below)
```

There is no Id anywhere obvious below. The comment actually refers to [func Id](https://golang.org/pkg/go/types/#Id), which is [immediately below `type Object`](https://golang.org/src/go/types/object.go?#L57) in the actual code.

Some sort of [cross-linking inside godoc](https://github.com/golang/go/issues/18342#issuecomment-271419866) might help here, as would minor textual changes.
",1.0,"go/types: confusing Object method comment - [type Object](https://golang.org/pkg/go/types/#Object) method `Id` docs read:

```
        Id() string     // object id (see Id below)
```

There is no Id anywhere obvious below. The comment actually refers to [func Id](https://golang.org/pkg/go/types/#Id), which is [immediately below `type Object`](https://golang.org/src/go/types/object.go?#L57) in the actual code.

Some sort of [cross-linking inside godoc](https://github.com/golang/go/issues/18342#issuecomment-271419866) might help here, as would minor textual changes.
",1,go types  confusing object method comment       method  id  docs read                  id   string        object id  see id below          there is no id anywhere obvious below  the comment actually refers to     which is     in the actual code     some sort of     might help here  as would minor textual changes   ,1
312849,23445610329.0,IssuesEvent,2022-08-15 19:17:30,golang/go,https://api.github.com/repos/golang/go,closed,runtime: cpu suboption for GODEBUG is not documented with the others for GODEBUG,Documentation help wanted NeedsFix compiler/runtime,"I've seen mention of using GODEBUG=cpu to disable certain cpu capabilities in various issues. I expected to find it described in runtime/extern.go where the other GODEBUG suboptions are documented, but it is not.",1.0,"runtime: cpu suboption for GODEBUG is not documented with the others for GODEBUG - I've seen mention of using GODEBUG=cpu to disable certain cpu capabilities in various issues. I expected to find it described in runtime/extern.go where the other GODEBUG suboptions are documented, but it is not.",1,runtime  cpu suboption for godebug is not documented with the others for godebug   i ve seen mention of using godebug cpu to disable certain cpu capabilities in various issues  i expected to find it described in runtime extern go where the other godebug suboptions are documented  but it is not ,1
173146,14403565531.0,IssuesEvent,2020-12-03 16:12:42,golang/go,https://api.github.com/repos/golang/go,closed,"doc/go1.16: document new packages in Go 1.16 standard library (io/fs, embed, runtime/metrics, testing/fstest)",Documentation NeedsInvestigation help wanted release-blocker,"As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

```HTML
<h2 id=""library"">Core library</h2>

<p>
  TODO: mention significant additions like new packages (<code>io/fs</code>),
  new proposal-scoped features (<code>//go:embed</code>), and so on
</p>
```

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.",1.0,"doc/go1.16: document new packages in Go 1.16 standard library (io/fs, embed, runtime/metrics, testing/fstest) - As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

```HTML
<h2 id=""library"">Core library</h2>

<p>
  TODO: mention significant additions like new packages (<code>io/fs</code>),
  new proposal-scoped features (<code>//go:embed</code>), and so on
</p>
```

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.",1,doc      document new packages in go     standard library  io fs  embed  runtime metrics  testing fstest    as of filing this issue  the     contained the following html        html   core library          todo  mention significant additions like new packages   io fs       new proposal scoped features     go embed    and so on            per     it s a release blocker for go     beta   to have a complete draft of the eventual release notes  and so the todo needs to be resolved     a sequence of steps to resolve this issue may be        come up with a draft release note entry in this issue  then move the issue to needsfix state      send a cl with  doc           and include  for     fixes   this issue    in the body ,1
26966,5302645011.0,IssuesEvent,2017-02-10 13:40:23,golang/go,https://api.github.com/repos/golang/go,closed,encoding/json: Unmarshal to nil pointer documentation discrepancy,Documentation,"When trying to unmarshal a json string into a nil pointer, the operation fails as can be seen here:
https://play.golang.org/p/wL6UDpaJ-h

The error returned is InvalidUnmarshalError whose docs clearly state:
""The argument to Unmarshal must be a non-nil pointer."" (https://golang.org/pkg/encoding/json/#InvalidUnmarshalError)

But the docs for the Unmarshal function state:
""Unmarshal unmarshals the JSON into the value pointed at by the pointer. If the pointer is nil, Unmarshal allocates a new value for it to point to.""
(https://golang.org/pkg/encoding/json/#Unmarshal)

Obviously, the behaviour implemented is the one from the error docs.

Curiously, this works:
https://play.golang.org/p/w-Sg24qcCo
So, a reference to a nil pointer is accepted but the nil pointer itself is not. Anyone care to clarify?

go1.7.4 darwin/amd64



",1.0,"encoding/json: Unmarshal to nil pointer documentation discrepancy - When trying to unmarshal a json string into a nil pointer, the operation fails as can be seen here:
https://play.golang.org/p/wL6UDpaJ-h

The error returned is InvalidUnmarshalError whose docs clearly state:
""The argument to Unmarshal must be a non-nil pointer."" (https://golang.org/pkg/encoding/json/#InvalidUnmarshalError)

But the docs for the Unmarshal function state:
""Unmarshal unmarshals the JSON into the value pointed at by the pointer. If the pointer is nil, Unmarshal allocates a new value for it to point to.""
(https://golang.org/pkg/encoding/json/#Unmarshal)

Obviously, the behaviour implemented is the one from the error docs.

Curiously, this works:
https://play.golang.org/p/w-Sg24qcCo
So, a reference to a nil pointer is accepted but the nil pointer itself is not. Anyone care to clarify?

go1.7.4 darwin/amd64



",1,encoding json  unmarshal to nil pointer documentation discrepancy   when trying to unmarshal a json string into a nil pointer  the operation fails as can be seen here        the error returned is invalidunmarshalerror whose docs clearly state    the argument to unmarshal must be a non nil pointer         but the docs for the unmarshal function state    unmarshal unmarshals the json into the value pointed at by the pointer  if the pointer is nil  unmarshal allocates a new value for it to point to          obviously  the behaviour implemented is the one from the error docs     curiously  this works      so  a reference to a nil pointer is accepted but the nil pointer itself is not  anyone care to clarify           darwin          ,1
272196,23660335351.0,IssuesEvent,2022-08-26 14:59:28,spring-projects/spring-framework,https://api.github.com/repos/spring-projects/spring-framework,opened,Implement GraalVM native image support in the TestContext framework,in: test theme: aot,"This is an umbrella issue for GraalVM native image support in the _Spring TestContext Framework_ and serves as an overview of related issues and their current status.

- #29028
- #29021
- #29022
- #29023
- #29024
- #29025
- #29026
- #29027
",1.0,"Implement GraalVM native image support in the TestContext framework - This is an umbrella issue for GraalVM native image support in the _Spring TestContext Framework_ and serves as an overview of related issues and their current status.

- #29028
- #29021
- #29022
- #29023
- #29024
- #29025
- #29026
- #29027
",0,implement graalvm native image support in the testcontext framework   this is an umbrella issue for graalvm native image support in the  spring testcontext framework  and serves as an overview of related issues and their current status                                                     ,0
14079,3796766037.0,IssuesEvent,2016-03-23 02:42:55,golang/go,https://api.github.com/repos/golang/go,closed,database/sql/driver: Scan.Next documentation incorrect,Documentation,"by **Christopher.Pfohl**:

<pre>What is the expected output?

String types from a database should have a go type of 'string' in Scanner.Scan.

What do you see instead?

String types have a go type of `[]byte`

Which compiler are you using (5g, 6g, 8g, gccgo)?

Whatever installed when I apt-get'ed from ppa:duh/golang

Which operating system are you using?

Ubuntu 13.04

Which version are you using?  (run 'go version')

1.1.1 linux/amd64

Please provide any additional information below.

database/sql/driver.Rows.Next's documentation states that all strings ought to be
converted to []byte

database/sql.Scanner.Scan's documentation suggests that a string is a legitimate type to
expect...but all the types that actually *are* strings actually wind up being []byte
because the driver's obey the above documentation (see mgodbc for a case in point, line
916).

Note, that removing the conversion to []byte still works, so I suspect that the
database/sql/driver.Rows.Next documentation is simply out of date.</pre>",1.0,"database/sql/driver: Scan.Next documentation incorrect - by **Christopher.Pfohl**:

<pre>What is the expected output?

String types from a database should have a go type of 'string' in Scanner.Scan.

What do you see instead?

String types have a go type of `[]byte`

Which compiler are you using (5g, 6g, 8g, gccgo)?

Whatever installed when I apt-get'ed from ppa:duh/golang

Which operating system are you using?

Ubuntu 13.04

Which version are you using?  (run 'go version')

1.1.1 linux/amd64

Please provide any additional information below.

database/sql/driver.Rows.Next's documentation states that all strings ought to be
converted to []byte

database/sql.Scanner.Scan's documentation suggests that a string is a legitimate type to
expect...but all the types that actually *are* strings actually wind up being []byte
because the driver's obey the above documentation (see mgodbc for a case in point, line
916).

Note, that removing the conversion to []byte still works, so I suspect that the
database/sql/driver.Rows.Next documentation is simply out of date.</pre>",1,database sql driver  scan next documentation incorrect   by   christopher pfohl      what is the expected output   string types from a database should have a go type of  string  in scanner scan   what do you see instead   string types have a go type of   byte   which compiler are you using           gccgo    whatever installed when i apt get ed from ppa duh golang  which operating system are you using   ubuntu      which version are you using    run  go version          linux    please provide any additional information below   database sql driver rows next s documentation states that all strings ought to be converted to  byte  database sql scanner scan s documentation suggests that a string is a legitimate type to expect   but all the types that actually  are  strings actually wind up being  byte because the driver s obey the above documentation  see mgodbc for a case in point  line      note  that removing the conversion to  byte still works  so i suspect that the database sql driver rows next documentation is simply out of date  ,1
389290,26806326668.0,IssuesEvent,2023-02-01 18:35:29,golang/go,https://api.github.com/repos/golang/go,closed,doc: write Go 1.20 release notes,Documentation NeedsFix early-in-cycle umbrella,"This is the tracking issue for writing the Go 1.20 Release Notes. The version at tip can be viewed at https://tip.golang.org/doc/go1.20.

When the Go 1.20 Release Notes are complete, this should be closed, and a similar issue should be made for the next release. Previous issues are #51400, #47694, #44513, etc.",1.0,"doc: write Go 1.20 release notes - This is the tracking issue for writing the Go 1.20 Release Notes. The version at tip can be viewed at https://tip.golang.org/doc/go1.20.

When the Go 1.20 Release Notes are complete, this should be closed, and a similar issue should be made for the next release. Previous issues are #51400, #47694, #44513, etc.",1,doc  write go     release notes   this is the tracking issue for writing the go     release notes  the version at tip can be viewed at      when the go     release notes are complete  this should be closed  and a similar issue should be made for the next release  previous issues are             etc ,1
652669,21558691024.0,IssuesEvent,2022-04-30 21:28:02,sriramalagappan/Mentor-ReactNative,https://api.github.com/repos/sriramalagappan/Mentor-ReactNative,closed,Sign Up Page + UI,high priority,Develop a Sign Up page where users can enter their information and create an account,1.0,Sign Up Page + UI - Develop a Sign Up page where users can enter their information and create an account,0,sign up page   ui   develop a sign up page where users can enter their information and create an account,0
84029,3652363075.0,IssuesEvent,2016-02-17 00:02:05,Macainian/Django-Maced,https://api.github.com/repos/Macainian/Django-Maced,closed,Switching to a mergeable combination will not reenable Accept,Bug High Priority,This could be a false positive since I found it while messing with other stuff. I'll check later.,1.0,Switching to a mergeable combination will not reenable Accept - This could be a false positive since I found it while messing with other stuff. I'll check later.,0,switching to a mergeable combination will not reenable accept   this could be a false positive since i found it while messing with other stuff  i ll check later ,0
9499,3288577372.0,IssuesEvent,2015-10-29 15:39:36,golang/go,https://api.github.com/repos/golang/go,closed,os/signal: code example for Notify tries to catch os.Kill which doesn't work,Documentation HelpWanted,"In the code example for os/signal/#Notify,

    signal.Notify(c, os.Interrupt, os.Kill)

tries to catch os.Kill signal, which doesn't work on Linux platforms.

Steps to reproduce:
Code is taken from the doc.
```
$ cat kill.go
package main

import (
        ""fmt""
        ""os""
        ""os/signal""
)

func main() {
        c := make(chan os.Signal, 1)
        signal.Notify(c, os.Interrupt, os.Kill)
        s := <-c
        fmt.Println(""Got signal "", s)
}

$ go build kill.go
$ ./kill &
[1] 10300
$ kill -KILL $!
$
[1]+  Killed                  ./kill
```

Ctrl-C / -s SIGINT works fine but SIGKILL is not caught.",1.0,"os/signal: code example for Notify tries to catch os.Kill which doesn't work - In the code example for os/signal/#Notify,

    signal.Notify(c, os.Interrupt, os.Kill)

tries to catch os.Kill signal, which doesn't work on Linux platforms.

Steps to reproduce:
Code is taken from the doc.
```
$ cat kill.go
package main

import (
        ""fmt""
        ""os""
        ""os/signal""
)

func main() {
        c := make(chan os.Signal, 1)
        signal.Notify(c, os.Interrupt, os.Kill)
        s := <-c
        fmt.Println(""Got signal "", s)
}

$ go build kill.go
$ ./kill &
[1] 10300
$ kill -KILL $!
$
[1]+  Killed                  ./kill
```

Ctrl-C / -s SIGINT works fine but SIGKILL is not caught.",1,os signal  code example for notify tries to catch os kill which doesn t work   in the code example for os signal  notify         signal notify c  os interrupt  os kill     tries to catch os kill signal  which doesn t work on linux platforms     steps to reproduce   code is taken from the doc          cat kill go  package main    import             fmt            os            os signal        func main              c    make chan os signal              signal notify c  os interrupt  os kill           s      c          fmt println  got signal    s          go build kill go      kill           kill  kill            killed                    kill         ctrl c    s sigint works fine but sigkill is not caught ,1
119556,17620325145.0,IssuesEvent,2021-08-18 14:37:21,jgeraigery/experian-java,https://api.github.com/repos/jgeraigery/experian-java,closed,CVE-2020-8840 (High) detected in jackson-databind-2.9.2.jar - autoclosed,security vulnerability,"## CVE-2020-8840 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.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/9ade2a959068cca30ecfdbb254939af6f67affb1"">9ade2a959068cca30ecfdbb254939af6f67affb1</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>  
  
FasterXML jackson-databind 2.0.0 through 2.9.10.2 lacks certain xbean-reflect/JNDI blocking, as demonstrated by org.apache.xbean.propertyeditor.JndiConverter.

<p>Publish Date: 2020-02-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8840>CVE-2020-8840</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/FasterXML/jackson-databind/issues/2620"">https://github.com/FasterXML/jackson-databind/issues/2620</a></p>
<p>Release Date: 2020-02-10</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.9.10.3</p>

</p>
</details>
<p></p>

***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""com.fasterxml.jackson.core"",""packageName"":""jackson-databind"",""packageVersion"":""2.9.2"",""packageFilePaths"":[""/MavenWorkspace/bis-services-lib/bis-services-base/pom.xml""],""isTransitiveDependency"":false,""dependencyTree"":""com.fasterxml.jackson.core:jackson-databind:2.9.2"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""com.fasterxml.jackson.core:jackson-databind:2.9.10.3""}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""CVE-2020-8840"",""vulnerabilityDetails"":""FasterXML jackson-databind 2.0.0 through 2.9.10.2 lacks certain xbean-reflect/JNDI blocking, as demonstrated by org.apache.xbean.propertyeditor.JndiConverter."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8840"",""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-8840 (High) detected in jackson-databind-2.9.2.jar - autoclosed - ## CVE-2020-8840 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.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/9ade2a959068cca30ecfdbb254939af6f67affb1"">9ade2a959068cca30ecfdbb254939af6f67affb1</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>  
  
FasterXML jackson-databind 2.0.0 through 2.9.10.2 lacks certain xbean-reflect/JNDI blocking, as demonstrated by org.apache.xbean.propertyeditor.JndiConverter.

<p>Publish Date: 2020-02-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8840>CVE-2020-8840</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/FasterXML/jackson-databind/issues/2620"">https://github.com/FasterXML/jackson-databind/issues/2620</a></p>
<p>Release Date: 2020-02-10</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.9.10.3</p>

</p>
</details>
<p></p>

***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""com.fasterxml.jackson.core"",""packageName"":""jackson-databind"",""packageVersion"":""2.9.2"",""packageFilePaths"":[""/MavenWorkspace/bis-services-lib/bis-services-base/pom.xml""],""isTransitiveDependency"":false,""dependencyTree"":""com.fasterxml.jackson.core:jackson-databind:2.9.2"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""com.fasterxml.jackson.core:jackson-databind:2.9.10.3""}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""CVE-2020-8840"",""vulnerabilityDetails"":""FasterXML jackson-databind 2.0.0 through 2.9.10.2 lacks certain xbean-reflect/JNDI blocking, as demonstrated by org.apache.xbean.propertyeditor.JndiConverter."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8840"",""cvss3Severity"":""high"",""cvss3Score"":""9.8"",""cvss3Metrics"":{""A"":""High"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""High"",""UI"":""None"",""AV"":""Network"",""I"":""High""},""extraData"":{}}</REMEDIATE> -->",0,cve      high  detected in jackson databind       jar   autoclosed      cve       high severity vulnerability     vulnerable library    jackson databind       jar      general data binding functionality for jackson  works on core streaming api   library home page   a href     path to 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       through         lacks certain xbean reflect jndi blocking  as demonstrated by org apache xbean propertyeditor jndiconverter    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  com fasterxml jackson core jackson databind                        rescue worker helmet  automatic remediation is available for this issue    isopenpronvulnerability  true  ispackagebased  true  isdefaultbranch  true  packages     istransitivedependency  false  dependencytree   com fasterxml jackson core jackson databind         isminimumfixversionavailable  true  minimumfixversion   com fasterxml jackson core jackson databind             basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   fasterxml jackson databind       through         lacks certain xbean reflect jndi blocking  as demonstrated by org apache xbean propertyeditor jndiconverter    vulnerabilityurl        ,0
116266,11905976622.0,IssuesEvent,2020-03-30 19:32:15,golang/go,https://api.github.com/repos/golang/go,closed,doc: BuildNameToCertificate deprecated in go 1.14 not mentioned in the release notes [1.14 backport] [1.14 backport],CherryPickApproved Documentation,"@Aboood412 requested issue #38030 to be considered for backport to the next 1.14 minor release.

> > @FiloSottile requested issue #37626 to be considered for backport to the next 1.14 minor release.
> > 
> > > @gopherbot please open a backport issue for Go 1.14, this is a documentation change that needs to go live on golang.org.
",1.0,"doc: BuildNameToCertificate deprecated in go 1.14 not mentioned in the release notes [1.14 backport] [1.14 backport] - @Aboood412 requested issue #38030 to be considered for backport to the next 1.14 minor release.

> > @FiloSottile requested issue #37626 to be considered for backport to the next 1.14 minor release.
> > 
> > > @gopherbot please open a backport issue for Go 1.14, this is a documentation change that needs to go live on golang.org.
",1,doc  buildnametocertificate deprecated in go     not mentioned in the release notes          requested issue    to be considered for backport to the next     minor release        filosottile requested issue    to be considered for backport to the next     minor release                gopherbot please open a backport issue for go      this is a documentation change that needs to go live on golang org  ,1
664583,22281989256.0,IssuesEvent,2022-06-11 02:40:36,Stuyk/altv-athena-issues,https://api.github.com/repos/Stuyk/altv-athena-issues,closed,Clothing store makes your cash go below zero,bug scope: server priority: critical status: pull-request,"### Description of the problem

If reproduction steps are followed, the clothing store makes your cash go below zero.

### Reproduction steps

1. Go to the clothing store with X amount of money.
2. Pick clothes that are all above X$.
3. Press 'Buy All' and 'Buy' after.
4. Press ESC and check your money.

### Expected behaviour

It should keep your money on positive numbers.

### Additional context

_No response_

### Version

3.4.0",1.0,"Clothing store makes your cash go below zero - ### Description of the problem

If reproduction steps are followed, the clothing store makes your cash go below zero.

### Reproduction steps

1. Go to the clothing store with X amount of money.
2. Pick clothes that are all above X$.
3. Press 'Buy All' and 'Buy' after.
4. Press ESC and check your money.

### Expected behaviour

It should keep your money on positive numbers.

### Additional context

_No response_

### Version

3.4.0",0,clothing store makes your cash go below zero       description of the problem  if reproduction steps are followed  the clothing store makes your cash go below zero       reproduction steps     go to the clothing store with x amount of money      pick clothes that are all above x       press  buy all  and  buy  after      press esc and check your money       expected behaviour  it should keep your money on positive numbers       additional context   no response       version       ,0
18987,5773196427.0,IssuesEvent,2017-04-28 00:54:34,PowerShell/vscode-powershell,https://api.github.com/repos/PowerShell/vscode-powershell,closed,Whitespace before open brace while invoking members,Area-Code Formatting Issue-Bug,"Code formatter formats `$someIterable.foreach{$_}` to `$someIterable.foreach {$_}`, which invalidates the expression. 
",1.0,"Whitespace before open brace while invoking members - Code formatter formats `$someIterable.foreach{$_}` to `$someIterable.foreach {$_}`, which invalidates the expression. 
",0,whitespace before open brace while invoking members   code formatter formats   someiterable foreach      to   someiterable foreach        which invalidates the expression    ,0
11594,3508093615.0,IssuesEvent,2016-01-08 16:20:33,golang/go,https://api.github.com/repos/golang/go,closed,net: inconsistent documentation for Listen addrs.,Documentation,"See http://golang.org/pkg/net/.

The example in the Overview section says:

    The Listen function creates servers:
    ln, err := net.Listen(""tcp"", "":8080"")

The comment for `Listen` says:

    See Dial for the syntax of laddr.

The comment for `Dial` says:

    For TCP and UDP networks, addresses have the form host:port.

This contradicts the example in the Overview section, which elides the host.  Assuming the Overview example is correct, the comment for `Dial` comment should be updated to describe what happens if the host and/or port is omitted.",1.0,"net: inconsistent documentation for Listen addrs. - See http://golang.org/pkg/net/.

The example in the Overview section says:

    The Listen function creates servers:
    ln, err := net.Listen(""tcp"", "":8080"")

The comment for `Listen` says:

    See Dial for the syntax of laddr.

The comment for `Dial` says:

    For TCP and UDP networks, addresses have the form host:port.

This contradicts the example in the Overview section, which elides the host.  Assuming the Overview example is correct, the comment for `Dial` comment should be updated to describe what happens if the host and/or port is omitted.",1,net  inconsistent documentation for listen addrs    see      the example in the overview section says         the listen function creates servers       ln  err    net listen  tcp            the comment for  listen  says         see dial for the syntax of laddr     the comment for  dial  says         for tcp and udp networks  addresses have the form host port     this contradicts the example in the overview section  which elides the host   assuming the overview example is correct  the comment for  dial  comment should be updated to describe what happens if the host and or port is omitted ,1
176636,28129192046.0,IssuesEvent,2023-03-31 20:45:03,ethereum/ethereum-org-website,https://api.github.com/repos/ethereum/ethereum-org-website,closed,Inconsistency with theme switch button on small screen sizes,bug :bug: design required 🎨 needs-triage,"### Describe the bug

On screen sizes including mobile devices and tablets, when the theme is set to light mode, the theme switch button in the sidebar displays the label ""Light"" and respective icon instead of the expected label ""Dark"" and vice versa. This issue can confuse users who are trying to switch themes.

### To reproduce

1. Go to any page on ethereum.org on a mobile device or a tablet.
2. Click on the menu icon in the top-right corner to open the sidebar
3. Look at the bottom panel to see the theme switch button
4. Observe the label and icon displayed on the theme switch button

### Expected behavior

1. When the theme is set to light mode, the theme switch button in the sidebar should show the label ""Dark"" and a moon icon. This indicates that clicking the button will switch the theme to dark mode.

2. When the theme is set to dark mode, the theme switch button in the sidebar should show the label ""Light"" and a sun icon. This indicates that clicking the button will switch the theme to light mode.

### Screenshots

<img src=""https://user-images.githubusercontent.com/42074753/228359936-65c3c4c8-8f77-4f5a-8ceb-00a1bc5b9383.png"" alt=""in light mode"" width=""250"" height=""450""/>

<img src=""https://user-images.githubusercontent.com/42074753/228360353-7fa3eb9e-dcd1-45ad-9f0d-ab75dddd4440.png"" alt=""in dark mode"" width=""250"" height=""450""/>




### Desktop (please complete the following information)

_No response_

### Smartphone (please complete the following information)

_No response_

### Additional context

_No response_

### Would you like to work on this issue?

- [X] Yes
- [ ] No",1.0,"Inconsistency with theme switch button on small screen sizes - ### Describe the bug

On screen sizes including mobile devices and tablets, when the theme is set to light mode, the theme switch button in the sidebar displays the label ""Light"" and respective icon instead of the expected label ""Dark"" and vice versa. This issue can confuse users who are trying to switch themes.

### To reproduce

1. Go to any page on ethereum.org on a mobile device or a tablet.
2. Click on the menu icon in the top-right corner to open the sidebar
3. Look at the bottom panel to see the theme switch button
4. Observe the label and icon displayed on the theme switch button

### Expected behavior

1. When the theme is set to light mode, the theme switch button in the sidebar should show the label ""Dark"" and a moon icon. This indicates that clicking the button will switch the theme to dark mode.

2. When the theme is set to dark mode, the theme switch button in the sidebar should show the label ""Light"" and a sun icon. This indicates that clicking the button will switch the theme to light mode.

### Screenshots

<img src=""https://user-images.githubusercontent.com/42074753/228359936-65c3c4c8-8f77-4f5a-8ceb-00a1bc5b9383.png"" alt=""in light mode"" width=""250"" height=""450""/>

<img src=""https://user-images.githubusercontent.com/42074753/228360353-7fa3eb9e-dcd1-45ad-9f0d-ab75dddd4440.png"" alt=""in dark mode"" width=""250"" height=""450""/>




### Desktop (please complete the following information)

_No response_

### Smartphone (please complete the following information)

_No response_

### Additional context

_No response_

### Would you like to work on this issue?

- [X] Yes
- [ ] No",0,inconsistency with theme switch button on small screen sizes       describe the bug  on screen sizes including mobile devices and tablets  when the theme is set to light mode  the theme switch button in the sidebar displays the label  light  and respective icon instead of the expected label  dark  and vice versa  this issue can confuse users who are trying to switch themes       to reproduce     go to any page on ethereum org on a mobile device or a tablet      click on the menu icon in the top right corner to open the sidebar     look at the bottom panel to see the theme switch button     observe the label and icon displayed on the theme switch button      expected behavior     when the theme is set to light mode  the theme switch button in the sidebar should show the label  dark  and a moon icon  this indicates that clicking the button will switch the theme to dark mode        when the theme is set to dark mode  the theme switch button in the sidebar should show the label  light  and a sun icon  this indicates that clicking the button will switch the theme to light mode       screenshots                    desktop  please complete the following information    no response       smartphone  please complete the following information    no response       additional context   no response       would you like to work on this issue       yes     no,0
171398,27112795828.0,IssuesEvent,2023-02-15 16:24:18,hackforla/expunge-assist,https://api.github.com/repos/hackforla/expunge-assist,closed,[Re-organize Figma: Archive] Archive FAQ page,role: design priority: medium role: UX content writing size: 1pt,"### Overview
Extension of #807 

### Action Items
- [x] Read through comments and determine if they can be marked as ""resolved"" 
- [x] For comments that cannot be marked as resolved, add a box on the side of the wireframe where the comment is as and copy and paste the comment/thread of comments to the side. 
- [x] Draw an arrow to the area the comment was referencing 
- [x] Once this is done to all the comments on the page, copy all the content on the ""FAQ"" and pasting it under ""IUT2 (2022)"" page under the ""Archive"" section on Figma 
- [x] Select the FAQ page content and make it into a ""section""
- [x] Name it ""FAQ page""
- [x] Let team know when complete

### Resources/Instructions
Reach out to  @anitadesigns or @SamHyler for questions
",1.0,"[Re-organize Figma: Archive] Archive FAQ page - ### Overview
Extension of #807 

### Action Items
- [x] Read through comments and determine if they can be marked as ""resolved"" 
- [x] For comments that cannot be marked as resolved, add a box on the side of the wireframe where the comment is as and copy and paste the comment/thread of comments to the side. 
- [x] Draw an arrow to the area the comment was referencing 
- [x] Once this is done to all the comments on the page, copy all the content on the ""FAQ"" and pasting it under ""IUT2 (2022)"" page under the ""Archive"" section on Figma 
- [x] Select the FAQ page content and make it into a ""section""
- [x] Name it ""FAQ page""
- [x] Let team know when complete

### Resources/Instructions
Reach out to  @anitadesigns or @SamHyler for questions
",0,  archive faq page       overview  extension of            action items      read through comments and determine if they can be marked as  resolved        for comments that cannot be marked as resolved  add a box on the side of the wireframe where the comment is as and copy and paste the comment thread of comments to the side        draw an arrow to the area the comment was referencing       once this is done to all the comments on the page  copy all the content on the  faq  and pasting it under         page under the  archive  section on figma       select the faq page content and make it into a  section       name it  faq page       let team know when complete        resources instructions  reach out to   anitadesigns or  samhyler for questions  ,0
27068,5311814303.0,IssuesEvent,2017-02-13 06:10:50,golang/go,https://api.github.com/repos/golang/go,closed,runtime: Frames.Next is confusing,Documentation NeedsDecision,"### What version of Go are you using (`go version`)?
play.golang.org

### What operating system and processor architecture are you using (`go env`)?
play.golang.org

### What did you do?
Sample program:
https://play.golang.org/p/5ckof3s_kJ

### What did you expect to see?
The documentation for [Frames.Next](https://golang.org/pkg/runtime/#Frames.Next) says ""Next returns frame information for the next caller. If more is false, there are no more callers (the Frame value is valid).""

Reading that I would expect that more return this sort of thing
```
-> valid_frame, true
-> valid_frame, true
-> valid_frame, false
-> invalid_frame, false
-> etc.
```

Where `invalid_frame` is the default-valued frame.

### What did you see instead?
```
-> valid_frame, true
-> valid_frame, true
-> valid_frame, true
-> invalid_frame, true
-> etc.
-> invalid_frame, false
-> etc.
```

### So what?
This behavior of returning `more=true` and spitting out invalid `Frame`s seems pretty weird. But I assume that changing the behavior of `Next` is out of the question. So I propose the documentation be updated by someone who knows how this thing works. The docs could read ""Next returns frame information for the next caller. If `more` is `false`, no further calls to `Next` should be made. If `frame` is nil-valued, no further frames will be non-nil valued."" And an example in the docs of how to go from a `Frames` to a complete `[]Frame` would be great!",1.0,"runtime: Frames.Next is confusing - ### What version of Go are you using (`go version`)?
play.golang.org

### What operating system and processor architecture are you using (`go env`)?
play.golang.org

### What did you do?
Sample program:
https://play.golang.org/p/5ckof3s_kJ

### What did you expect to see?
The documentation for [Frames.Next](https://golang.org/pkg/runtime/#Frames.Next) says ""Next returns frame information for the next caller. If more is false, there are no more callers (the Frame value is valid).""

Reading that I would expect that more return this sort of thing
```
-> valid_frame, true
-> valid_frame, true
-> valid_frame, false
-> invalid_frame, false
-> etc.
```

Where `invalid_frame` is the default-valued frame.

### What did you see instead?
```
-> valid_frame, true
-> valid_frame, true
-> valid_frame, true
-> invalid_frame, true
-> etc.
-> invalid_frame, false
-> etc.
```

### So what?
This behavior of returning `more=true` and spitting out invalid `Frame`s seems pretty weird. But I assume that changing the behavior of `Next` is out of the question. So I propose the documentation be updated by someone who knows how this thing works. The docs could read ""Next returns frame information for the next caller. If `more` is `false`, no further calls to `Next` should be made. If `frame` is nil-valued, no further frames will be non-nil valued."" And an example in the docs of how to go from a `Frames` to a complete `[]Frame` would be great!",1,runtime  frames next is confusing       what version of go are you using   go version     play golang org        what operating system and processor architecture are you using   go env     play golang org        what did you do   sample program            what did you expect to see   the documentation for     says  next returns frame information for the next caller  if more is false  there are no more callers  the frame value is valid       reading that i would expect that more return this sort of thing          valid frame  true     valid frame  true     valid frame  false     invalid frame  false     etc          where  invalid frame  is the default valued frame         what did you see instead           valid frame  true     valid frame  true     valid frame  true     invalid frame  true     etc      invalid frame  false     etc              so what   this behavior of returning  more true  and spitting out invalid  frame s seems pretty weird  but i assume that changing the behavior of  next  is out of the question  so i propose the documentation be updated by someone who knows how this thing works  the docs could read  next returns frame information for the next caller  if  more  is  false   no further calls to  next  should be made  if  frame  is nil valued  no further frames will be non nil valued   and an example in the docs of how to go from a  frames  to a complete   frame  would be great ,1
2282,2674186104.0,IssuesEvent,2015-03-24 23:57:13,golang/go,https://api.github.com/repos/golang/go,closed,net/url: inaccurate documentation for method URL.String,documentation,"go version: 1.4.2

problem: The [godoc](http://golang.org/pkg/net/url/#URL.String) for URL.String in ""net/url"" does not accurately describe the method's behavior when the Opaque field is set.

>     scheme:opaque
>     scheme://userinfo@host/path?query#fragment
> If u.Opaque is non-empty, String uses the first form; otherwise it uses the second form.

The following playground link demonstrates a `*url.URL` which does not fall into these categories.

http://play.golang.org/p/SPGP5eSieA

The documentation states that the snippet should print ""https://example.com/foo"". But they observed string is ""https://example.com/foo?bar=baz#qux""",1.0,"net/url: inaccurate documentation for method URL.String - go version: 1.4.2

problem: The [godoc](http://golang.org/pkg/net/url/#URL.String) for URL.String in ""net/url"" does not accurately describe the method's behavior when the Opaque field is set.

>     scheme:opaque
>     scheme://userinfo@host/path?query#fragment
> If u.Opaque is non-empty, String uses the first form; otherwise it uses the second form.

The following playground link demonstrates a `*url.URL` which does not fall into these categories.

http://play.golang.org/p/SPGP5eSieA

The documentation states that the snippet should print ""https://example.com/foo"". But they observed string is ""https://example.com/foo?bar=baz#qux""",1,net url  inaccurate documentation for method url string   go version           problem  the     for url string in  net url  does not accurately describe the method s behavior when the opaque field is set           scheme opaque        scheme   userinfo host path query fragment    if u opaque is non empty  string uses the first form  otherwise it uses the second form     the following playground link demonstrates a   url url  which does not fall into these categories          the documentation states that the snippet should print    but they observed string is   ,1
684004,23402794931.0,IssuesEvent,2022-08-12 09:41:35,opencrvs/opencrvs-core,https://api.github.com/repos/opencrvs/opencrvs-core,closed,Conflict bug:Profile icon is not showing in record audit page if local registrar/national registrar unassign any user and assign themselves in any record ,👹Bug Priority: medium,"**Bug description:**
Conflict bug: assigned user not showing only in record audit page, when local registrar/national registrar unassign any user and assign themselves in any record. If the unassigned user log in , they see the local registrar/national registrar's profile icon in  workqueue but after clicking on the application the profile icon doesn't show

**Steps to reproduce:**
1. Application is assigned and downloaded by Registration agent/Local Register/National Registrar is available
2. log in as registrar/ national registrar
3. Unassign a record that is assigned to any other user except themself (for example unassigned a registration agent.)
4. Assign the record to themself
5. Log out
6. Log in as the user who was unassigned from the application (for example registration agent who was unassigned in step 3) 
7. Click on the Review/Update/Reject of the application
8.  Observe that the error message- ""You were unassigned from [tracking id] shows and the profile icon of the assigned user is showing in workqueue
9. Click on the application

**Actual result:**
Profile icon not showing in record audit page, but showing in workqueue

**Expected result:**
Profile icon should show record audit page and workqueue

**Screenrecording:**
https://www.screencast.com/t/HrUgFxM6d

 **Tested on:**
https://login.farajaland-qa.opencrvs.org/",1.0,"Conflict bug:Profile icon is not showing in record audit page if local registrar/national registrar unassign any user and assign themselves in any record  - **Bug description:**
Conflict bug: assigned user not showing only in record audit page, when local registrar/national registrar unassign any user and assign themselves in any record. If the unassigned user log in , they see the local registrar/national registrar's profile icon in  workqueue but after clicking on the application the profile icon doesn't show

**Steps to reproduce:**
1. Application is assigned and downloaded by Registration agent/Local Register/National Registrar is available
2. log in as registrar/ national registrar
3. Unassign a record that is assigned to any other user except themself (for example unassigned a registration agent.)
4. Assign the record to themself
5. Log out
6. Log in as the user who was unassigned from the application (for example registration agent who was unassigned in step 3) 
7. Click on the Review/Update/Reject of the application
8.  Observe that the error message- ""You were unassigned from [tracking id] shows and the profile icon of the assigned user is showing in workqueue
9. Click on the application

**Actual result:**
Profile icon not showing in record audit page, but showing in workqueue

**Expected result:**
Profile icon should show record audit page and workqueue

**Screenrecording:**
https://www.screencast.com/t/HrUgFxM6d

 **Tested on:**
https://login.farajaland-qa.opencrvs.org/",0,conflict bug profile icon is not showing in record audit page if local registrar national registrar unassign any user and assign themselves in any record      bug description     conflict bug  assigned user not showing only in record audit page  when local registrar national registrar unassign any user and assign themselves in any record  if the unassigned user log in   they see the local registrar national registrar s profile icon in  workqueue but after clicking on the application the profile icon doesn t show      steps to reproduce        application is assigned and downloaded by registration agent local register national registrar is available     log in as registrar  national registrar     unassign a record that is assigned to any other user except themself  for example unassigned a registration agent       assign the record to themself     log out     log in as the user who was unassigned from the application  for example registration agent who was unassigned in step         click on the review update reject of the application      observe that the error message   you were unassigned from   shows and the profile icon of the assigned user is showing in workqueue     click on the application      actual result     profile icon not showing in record audit page  but showing in workqueue      expected result     profile icon should show record audit page and workqueue      screenrecording             tested on      ,0
33121,6157501553.0,IssuesEvent,2017-06-28 19:05:26,golang/go,https://api.github.com/repos/golang/go,opened,http: Document change in cookie sanitization in the release notes?,Documentation,"[This](https://github.com/golang/go/commit/8f6d68ebaa660c6db8a87d418e95f8c0d3a221e4) change to sanitizeCookieValue (to fix #18627) broke the quic-go unit tests going from 1.8 to 1.9b2. I don't know about the policy for mentioning bugfixes there, but maybe this should be mentioned in the release notes for net/http? I'd be happy to write a CL if you feel like it's worth it.",1.0,"http: Document change in cookie sanitization in the release notes? - [This](https://github.com/golang/go/commit/8f6d68ebaa660c6db8a87d418e95f8c0d3a221e4) change to sanitizeCookieValue (to fix #18627) broke the quic-go unit tests going from 1.8 to 1.9b2. I don't know about the policy for mentioning bugfixes there, but maybe this should be mentioned in the release notes for net/http? I'd be happy to write a CL if you feel like it's worth it.",1,http  document change in cookie sanitization in the release notes        change to sanitizecookievalue  to fix     broke the quic go unit tests going from     to      i don t know about the policy for mentioning bugfixes there  but maybe this should be mentioned in the release notes for net http  i d be happy to write a cl if you feel like it s worth it ,1
399443,27241224725.0,IssuesEvent,2023-02-21 20:38:56,golang/go,https://api.github.com/repos/golang/go,closed,path/filepath: Clean changed in Go 1.20,Documentation NeedsFix,"I have some GitHub action tests that started to fail on Windows after I bumped the build matrix to Go 1.20.

I have distilled the issue into this small repo: https://github.com/bep/go120winpathregression


```
--- FAIL: TestTo (0.00s)
    lib_test.go:12: 
        error:
          values are not equal
        got:
          ""\\\\\\\\post""
        want:
          ""\\post""
        stack:
          D:/a/go[12](https://github.com/bep/go120winpathregression/actions/runs/4102512994/jobs/7075566395#step:11:13)0winpathregression/go120winpathregression/lib_test.go:12
            c.Assert(Clean(""////post/////""), qt.Equals, filepath.FromSlash(""/post""))
```

I have looked closely in the release notes for Go 1.20 about this, but that does not mention this change. Also, the GoDoc for `filepath.Clean` is pretty clear about what happens to ""multiple Separator elements"":

> 1. Replace multiple Separator elements with a single one.",1.0,"path/filepath: Clean changed in Go 1.20 - I have some GitHub action tests that started to fail on Windows after I bumped the build matrix to Go 1.20.

I have distilled the issue into this small repo: https://github.com/bep/go120winpathregression


```
--- FAIL: TestTo (0.00s)
    lib_test.go:12: 
        error:
          values are not equal
        got:
          ""\\\\\\\\post""
        want:
          ""\\post""
        stack:
          D:/a/go[12](https://github.com/bep/go120winpathregression/actions/runs/4102512994/jobs/7075566395#step:11:13)0winpathregression/go120winpathregression/lib_test.go:12
            c.Assert(Clean(""////post/////""), qt.Equals, filepath.FromSlash(""/post""))
```

I have looked closely in the release notes for Go 1.20 about this, but that does not mention this change. Also, the GoDoc for `filepath.Clean` is pretty clear about what happens to ""multiple Separator elements"":

> 1. Replace multiple Separator elements with a single one.",1,path filepath  clean changed in go       i have some github action tests that started to fail on windows after i bumped the build matrix to go         i have distilled the issue into this small repo                  fail  testto            lib test go              error             values are not equal          got                      post           want                post           stack             d  a go                 c assert clean      post         qt equals  filepath fromslash   post            i have looked closely in the release notes for go     about this  but that does not mention this change  also  the godoc for  filepath clean  is pretty clear about what happens to  multiple separator elements           replace multiple separator elements with a single one ,1
167413,14112202675.0,IssuesEvent,2020-11-07 03:53:23,golang/go,https://api.github.com/repos/golang/go,closed,archive/zip: documentation refers to io.FS instead of fs.FS,Documentation NeedsFix,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version devel +633f9e2060 Wed Nov 4 06:42:33 2020 +0000 darwin/amd64

</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""on""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/artyom/Library/Caches/go-build""
GOENV=""/Users/artyom/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""-ldflags=-w -trimpath""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/artyom/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/artyom/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/Users/artyom/Repositories/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/Users/artyom/Repositories/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/lb/3rk8rqs53czgb4v35w_342xc0000gn/T/go-build536273506=/tmp/go-build -gno-record-gcc-switches -fno-common""

</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

Checked archive/zip documentation to see whether package implements newly added FS interface:

```
go (master) ¶ ./bin/go doc -all archive/zip | grep -C2 FS
func (r *Reader) Open(name string) (fs.File, error)
    Open opens the named file in the ZIP archive, using the semantics of
    io.FS.Open: paths are always slash separated, with no leading / or ../
    elements.

```

### What did you expect to see?

Documentation mentions [fs.FS interface](https://tip.golang.org/pkg/io/fs/#FS)

### What did you see instead?

Documentation refers to non-existing io.FS",1.0,"archive/zip: documentation refers to io.FS instead of fs.FS - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version devel +633f9e2060 Wed Nov 4 06:42:33 2020 +0000 darwin/amd64

</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""on""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/artyom/Library/Caches/go-build""
GOENV=""/Users/artyom/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""-ldflags=-w -trimpath""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/artyom/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/artyom/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/Users/artyom/Repositories/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/Users/artyom/Repositories/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/lb/3rk8rqs53czgb4v35w_342xc0000gn/T/go-build536273506=/tmp/go-build -gno-record-gcc-switches -fno-common""

</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

Checked archive/zip documentation to see whether package implements newly added FS interface:

```
go (master) ¶ ./bin/go doc -all archive/zip | grep -C2 FS
func (r *Reader) Open(name string) (fs.File, error)
    Open opens the named file in the ZIP archive, using the semantics of
    io.FS.Open: paths are always slash separated, with no leading / or ../
    elements.

```

### What did you expect to see?

Documentation mentions [fs.FS interface](https://tip.golang.org/pkg/io/fs/#FS)

### What did you see instead?

Documentation refers to non-existing io.FS",1,archive zip  documentation refers to io fs instead of fs fs         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version            go version  go version devel    wed nov              darwin               does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env          go env  output       go env     on   goarch      gobin     gocache   users artyom library caches go build   goenv   users artyom library application support go env   goexe     goflags   ldflags  w  trimpath   gohostarch      gohostos  darwin   goinsecure     gomodcache   users artyom go pkg mod   gonoproxy     gonosumdb     goos  darwin   gopath   users artyom go   goprivate     goproxy     goroot   users artyom repositories go   gosumdb  sum golang org   gotmpdir     gotooldir   users artyom repositories go pkg tool darwin     gccgo  gccgo   ar  ar   cc  clang   cxx  clang     cgo enabled      gomod   dev null   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders lb     t go    tmp go build  gno record gcc switches  fno common               what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best          checked archive zip documentation to see whether package implements newly added fs interface          go  master  ¶   bin go doc  all archive zip   grep    fs  func  r  reader  open name string   fs file  error       open opens the named file in the zip archive  using the semantics of      io fs open  paths are always slash separated  with no leading   or          elements                what did you expect to see     documentation mentions            what did you see instead     documentation refers to non existing io fs,1
772624,27129016725.0,IssuesEvent,2023-02-16 08:23:37,GEWIS/gewisweb,https://api.github.com/repos/GEWIS/gewisweb,opened,Cannot search for destroyed decisions,Type: Bug Priority: High For: Backend Status: Confirmed Module: Decision,GH-1568 breaks being able to search for destroyed decisions.,1.0,Cannot search for destroyed decisions - GH-1568 breaks being able to search for destroyed decisions.,0,cannot search for destroyed decisions   gh   breaks being able to search for destroyed decisions ,0
32069,6028917795.0,IssuesEvent,2017-06-08 16:46:45,golang/go,https://api.github.com/repos/golang/go,closed,spec: clarify restrictions on RHS of non-constant shifts,Documentation,"The spec says (https://golang.org/ref/spec#Operators):

> The right operand in a shift expression must have unsigned integer type or be an untyped constant
> that can be converted to unsigned integer type.

All of go, gotype and gccgo seem to allow any unsigned type as the right operand. However, if the right operand is untyped, all of them seem to try to convert the operand specifically to `uint`, as opposed to, say, trying to find some unsigned integer type, capable of representing the value.

``` Go
package main
const A0 uint64 = 0xffffffff + 1
const A1 = 0xffffffff
const A2 = 0xffffffff + 1
var B, C uint64
func main() {
    C = B << A0
    C = B << A1
    C = B << A2 // error
}
```

If this is the intended behavior, then the spec should look like:

> The right operand in a shift expression must have unsigned integer type or be an untyped constant
> that can be converted to `uint`.
",1.0,"spec: clarify restrictions on RHS of non-constant shifts - The spec says (https://golang.org/ref/spec#Operators):

> The right operand in a shift expression must have unsigned integer type or be an untyped constant
> that can be converted to unsigned integer type.

All of go, gotype and gccgo seem to allow any unsigned type as the right operand. However, if the right operand is untyped, all of them seem to try to convert the operand specifically to `uint`, as opposed to, say, trying to find some unsigned integer type, capable of representing the value.

``` Go
package main
const A0 uint64 = 0xffffffff + 1
const A1 = 0xffffffff
const A2 = 0xffffffff + 1
var B, C uint64
func main() {
    C = B << A0
    C = B << A1
    C = B << A2 // error
}
```

If this is the intended behavior, then the spec should look like:

> The right operand in a shift expression must have unsigned integer type or be an untyped constant
> that can be converted to `uint`.
",1,spec  clarify restrictions on rhs of non constant shifts   the spec says       the right operand in a shift expression must have unsigned integer type or be an untyped constant   that can be converted to unsigned integer type   all of go  gotype and gccgo seem to allow any unsigned type as the right operand  however  if the right operand is untyped  all of them seem to try to convert the operand specifically to  uint   as opposed to  say  trying to find some unsigned integer type  capable of representing the value       go package main const             const       const           var b  c   func main         c   b          c   b          c   b         error        if this is the intended behavior  then the spec should look like     the right operand in a shift expression must have unsigned integer type or be an untyped constant   that can be converted to  uint   ,1
97167,28117364366.0,IssuesEvent,2023-03-31 11:50:44,unikraft/unikraft,https://api.github.com/repos/unikraft/unikraft,closed,`lib/ukdebug`: Build warning in `uk/print.h`,good-first-issue lib/ukdebug arch/x86_64 kind/build-warning kind/hackathon,"### Describe the bug

There are build warnings when using `uk_pr_debug` and `uk_printd` in `lib/ukdebug`.

**Hackathon points**: 10

### Steps to reproduce

This happens with [`app-elfloader`](https://github.com/unikraft/app-elfloader), but any application using `lib/posix-process` should be able to get the warnings.

### Expected behavior

There shouldn't be any build warnings.

### Which architectures were you using or does this bug affect?

x86_64

### Which platforms were you using or does this bug affect?

kvm

### Relevant log output

```shell
In file included from /home/razvan/projects/unikraft/bin-compat/unikraft/lib/ukdebug/include/uk/assert.h:42,                                                                           
                 from /home/razvan/projects/unikraft/bin-compat/apps/app-elfloader/elf_load.c:46:                                                                                      
/home/razvan/projects/unikraft/bin-compat/apps/app-elfloader/elf_load.c: In function ‘elf_load_img’:                                                                                   
/home/razvan/projects/unikraft/bin-compat/unikraft/lib/ukdebug/include/uk/print.h:104:17: warning: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 6 has type ‘
long long unsigned int’ [-Wformat=]                                                                                                                                                    
  104 |       __LINE__, (fmt), ##__VA_ARGS__);  \                                                                                                                                      
      |                 ^~~~~                                                                                                                                                          
/home/razvan/projects/unikraft/bin-compat/unikraft/lib/ukdebug/include/uk/print.h:225:31: note: in expansion of macro ‘uk_printd’                                                      
  225 | #define uk_pr_debug(fmt, ...) uk_printd((fmt), ##__VA_ARGS__)                                                                                                                  
      |                               ^~~~~~~~~                                                                                                                                        
/home/razvan/projects/unikraft/bin-compat/apps/app-elfloader/elf_load.c:288:4: note: in expansion of macro ‘uk_pr_debug’                                                               
  288 |    uk_pr_debug(""%p: Protecting 0x%""PRIx64"" - 0x%""PRIx64"": %c%c%c\n"",                                                                                                           
      |    ^~~~~~~~~~~                                                                                                                                                                 
/home/razvan/projects/unikraft/bin-compat/unikraft/lib/ukdebug/include/uk/print.h:104:17: warning: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 7 has type $
long long unsigned int’ [-Wformat=]
  104 |       __LINE__, (fmt), ##__VA_ARGS__);  \
      |                 ^~~~~
/home/razvan/projects/unikraft/bin-compat/unikraft/lib/ukdebug/include/uk/print.h:225:31: note: in expansion of macro ‘uk_printd’
  225 | #define uk_pr_debug(fmt, ...) uk_printd((fmt), ##__VA_ARGS__)
      |                               ^~~~~~~~~
/home/razvan/projects/unikraft/bin-compat/apps/app-elfloader/elf_load.c:288:4: note: in expansion of macro ‘uk_pr_debug’
  288 |    uk_pr_debug(""%p: Protecting 0x%""PRIx64"" - 0x%""PRIx64"": %c%c%c\n"",
```
",1.0,"`lib/ukdebug`: Build warning in `uk/print.h` - ### Describe the bug

There are build warnings when using `uk_pr_debug` and `uk_printd` in `lib/ukdebug`.

**Hackathon points**: 10

### Steps to reproduce

This happens with [`app-elfloader`](https://github.com/unikraft/app-elfloader), but any application using `lib/posix-process` should be able to get the warnings.

### Expected behavior

There shouldn't be any build warnings.

### Which architectures were you using or does this bug affect?

x86_64

### Which platforms were you using or does this bug affect?

kvm

### Relevant log output

```shell
In file included from /home/razvan/projects/unikraft/bin-compat/unikraft/lib/ukdebug/include/uk/assert.h:42,                                                                           
                 from /home/razvan/projects/unikraft/bin-compat/apps/app-elfloader/elf_load.c:46:                                                                                      
/home/razvan/projects/unikraft/bin-compat/apps/app-elfloader/elf_load.c: In function ‘elf_load_img’:                                                                                   
/home/razvan/projects/unikraft/bin-compat/unikraft/lib/ukdebug/include/uk/print.h:104:17: warning: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 6 has type ‘
long long unsigned int’ [-Wformat=]                                                                                                                                                    
  104 |       __LINE__, (fmt), ##__VA_ARGS__);  \                                                                                                                                      
      |                 ^~~~~                                                                                                                                                          
/home/razvan/projects/unikraft/bin-compat/unikraft/lib/ukdebug/include/uk/print.h:225:31: note: in expansion of macro ‘uk_printd’                                                      
  225 | #define uk_pr_debug(fmt, ...) uk_printd((fmt), ##__VA_ARGS__)                                                                                                                  
      |                               ^~~~~~~~~                                                                                                                                        
/home/razvan/projects/unikraft/bin-compat/apps/app-elfloader/elf_load.c:288:4: note: in expansion of macro ‘uk_pr_debug’                                                               
  288 |    uk_pr_debug(""%p: Protecting 0x%""PRIx64"" - 0x%""PRIx64"": %c%c%c\n"",                                                                                                           
      |    ^~~~~~~~~~~                                                                                                                                                                 
/home/razvan/projects/unikraft/bin-compat/unikraft/lib/ukdebug/include/uk/print.h:104:17: warning: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 7 has type $
long long unsigned int’ [-Wformat=]
  104 |       __LINE__, (fmt), ##__VA_ARGS__);  \
      |                 ^~~~~
/home/razvan/projects/unikraft/bin-compat/unikraft/lib/ukdebug/include/uk/print.h:225:31: note: in expansion of macro ‘uk_printd’
  225 | #define uk_pr_debug(fmt, ...) uk_printd((fmt), ##__VA_ARGS__)
      |                               ^~~~~~~~~
/home/razvan/projects/unikraft/bin-compat/apps/app-elfloader/elf_load.c:288:4: note: in expansion of macro ‘uk_pr_debug’
  288 |    uk_pr_debug(""%p: Protecting 0x%""PRIx64"" - 0x%""PRIx64"": %c%c%c\n"",
```
",0, lib ukdebug   build warning in  uk print h        describe the bug    there are build warnings when using  uk pr debug  and  uk printd  in  lib ukdebug        hackathon points             steps to reproduce    this happens with     but any application using  lib posix process  should be able to get the warnings         expected behavior    there shouldn t be any build warnings         which architectures were you using or does this bug affect                which platforms were you using or does this bug affect     kvm        relevant log output       shell  in file included from  home razvan projects unikraft bin compat unikraft lib ukdebug include uk assert h                                                                                                 from  home razvan projects unikraft bin compat apps app elfloader elf load c                                                                                            home razvan projects unikraft bin compat apps app elfloader elf load c  in function ‘elf load img’                                                                                       home razvan projects unikraft bin compat unikraft lib ukdebug include uk print h      warning  format ‘ lx’ expects argument of type ‘long unsigned int’  but argument   has type ‘  long long unsigned int’                                                                                                                                                                      line     fmt       va args                                                                                                                                                                                                                                                                                                                                         home razvan projects unikraft bin compat unikraft lib ukdebug include uk print h      note  in expansion of macro ‘uk printd’                                                               define uk pr debug fmt       uk printd  fmt       va args                                                                                                                                                                                                                                                                                                                 home razvan projects unikraft bin compat apps app elfloader elf load c      note  in expansion of macro ‘uk pr debug’                                                                          uk pr debug   p  protecting                 c c c n                                                                                                                                                                                                                                                                                                         home razvan projects unikraft bin compat unikraft lib ukdebug include uk print h      warning  format ‘ lx’ expects argument of type ‘long unsigned int’  but argument   has type    long long unsigned int’                  line     fmt       va args                                         home razvan projects unikraft bin compat unikraft lib ukdebug include uk print h      note  in expansion of macro ‘uk printd’         define uk pr debug fmt       uk printd  fmt       va args                                                       home razvan projects unikraft bin compat apps app elfloader elf load c      note  in expansion of macro ‘uk pr debug’           uk pr debug   p  protecting                 c c c n         ,0
310492,26718944978.0,IssuesEvent,2023-01-28 22:20:17,ssbc/go-ssb,https://api.github.com/repos/ssbc/go-ssb,closed,TestSignMessages is flaky,testing,"After a bunch of PASSes, two failures in a row:

```
2023/01/02 12:05:35 [margaret/indexes/badger] overwrote batch limit 0
=== RUN   TestSignMessages
badger 2023/01/02 12:05:35 INFO: All 0 tables opened in 0s
badger 2023/01/02 12:05:35 INFO: Discard stats nextEmptySlot: 0
badger 2023/01/02 12:05:35 INFO: Set nextTxnTs to 0
    publish_test.go:104: msg:0
        {
            ""about"": ""@z+xJSnzIQtg0Dywzvl7VUzTLpj5VFajA8wZ3IRz6ztQ=.ed25519"",
            ""name"": ""test user"",
            ""type"": ""about""
          }
    publish_test.go:104: msg:1
        {
            ""contact"": ""@p13zSAiOpguI9nsawkGijsnMfWmFd5rlUNpzekEE+vI=.ed25519"",
            ""following"": true,
            ""type"": ""contact""
          }
    publish_test.go:107: 
        	Error Trace:	/home/go-ssb/go-ssb/message/publish_test.go:107
        	Error:      	Expected value not to be nil.
        	Test:       	TestSignMessages
        	Messages:   	msg:1 - previous
    publish_test.go:104: msg:2
        {
            ""text"": ""# hello world!"",
            ""type"": ""text""
          }
    publish_test.go:107: 
        	Error Trace:	/home/go-ssb/go-ssb/message/publish_test.go:107
        	Error:      	Expected value not to be nil.
        	Test:       	TestSignMessages
        	Messages:   	msg:2 - previous
badger 2023/01/02 12:05:35 INFO: Lifetime L0 stalled for: 0s
badger 2023/01/02 12:05:35 INFO: 
Level 0 [ ]: NumTables: 01. Size: 264 B of 0 B. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 64 MiB
Level 1 [ ]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level 2 [ ]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level 3 [ ]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level 4 [ ]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level 5 [ ]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level 6 [B]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level Done
--- FAIL: TestSignMessages (0.05s)
FAIL
FAIL	github.com/ssbc/go-ssb/message	0.068s
FAIL
2023/01/02 12:05:38 [margaret/indexes/badger] overwrote batch limit 0
=== RUN   TestSignMessages
badger 2023/01/02 12:05:38 INFO: All 0 tables opened in 0s
badger 2023/01/02 12:05:38 INFO: Discard stats nextEmptySlot: 0
badger 2023/01/02 12:05:38 INFO: Set nextTxnTs to 0
    publish_test.go:104: msg:0
        {
            ""about"": ""@z+xJSnzIQtg0Dywzvl7VUzTLpj5VFajA8wZ3IRz6ztQ=.ed25519"",
            ""name"": ""test user"",
            ""type"": ""about""
          }
    publish_test.go:104: msg:1
        {
            ""contact"": ""@p13zSAiOpguI9nsawkGijsnMfWmFd5rlUNpzekEE+vI=.ed25519"",
            ""following"": true,
            ""type"": ""contact""
          }
    publish_test.go:107: 
        	Error Trace:	/home/go-ssb/go-ssb/message/publish_test.go:107
        	Error:      	Expected value not to be nil.
        	Test:       	TestSignMessages
        	Messages:   	msg:1 - previous
    publish_test.go:104: msg:2
        {
            ""text"": ""# hello world!"",
            ""type"": ""text""
          }
badger 2023/01/02 12:05:38 INFO: Lifetime L0 stalled for: 0s
badger 2023/01/02 12:05:38 INFO: 
Level 0 [ ]: NumTables: 01. Size: 264 B of 0 B. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 64 MiB
Level 1 [ ]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level 2 [ ]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level 3 [ ]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level 4 [ ]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level 5 [ ]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level 6 [B]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level Done
--- FAIL: TestSignMessages (0.04s)
FAIL
FAIL	github.com/ssbc/go-ssb/message	0.064s
FAIL
```",1.0,"TestSignMessages is flaky - After a bunch of PASSes, two failures in a row:

```
2023/01/02 12:05:35 [margaret/indexes/badger] overwrote batch limit 0
=== RUN   TestSignMessages
badger 2023/01/02 12:05:35 INFO: All 0 tables opened in 0s
badger 2023/01/02 12:05:35 INFO: Discard stats nextEmptySlot: 0
badger 2023/01/02 12:05:35 INFO: Set nextTxnTs to 0
    publish_test.go:104: msg:0
        {
            ""about"": ""@z+xJSnzIQtg0Dywzvl7VUzTLpj5VFajA8wZ3IRz6ztQ=.ed25519"",
            ""name"": ""test user"",
            ""type"": ""about""
          }
    publish_test.go:104: msg:1
        {
            ""contact"": ""@p13zSAiOpguI9nsawkGijsnMfWmFd5rlUNpzekEE+vI=.ed25519"",
            ""following"": true,
            ""type"": ""contact""
          }
    publish_test.go:107: 
        	Error Trace:	/home/go-ssb/go-ssb/message/publish_test.go:107
        	Error:      	Expected value not to be nil.
        	Test:       	TestSignMessages
        	Messages:   	msg:1 - previous
    publish_test.go:104: msg:2
        {
            ""text"": ""# hello world!"",
            ""type"": ""text""
          }
    publish_test.go:107: 
        	Error Trace:	/home/go-ssb/go-ssb/message/publish_test.go:107
        	Error:      	Expected value not to be nil.
        	Test:       	TestSignMessages
        	Messages:   	msg:2 - previous
badger 2023/01/02 12:05:35 INFO: Lifetime L0 stalled for: 0s
badger 2023/01/02 12:05:35 INFO: 
Level 0 [ ]: NumTables: 01. Size: 264 B of 0 B. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 64 MiB
Level 1 [ ]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level 2 [ ]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level 3 [ ]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level 4 [ ]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level 5 [ ]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level 6 [B]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level Done
--- FAIL: TestSignMessages (0.05s)
FAIL
FAIL	github.com/ssbc/go-ssb/message	0.068s
FAIL
2023/01/02 12:05:38 [margaret/indexes/badger] overwrote batch limit 0
=== RUN   TestSignMessages
badger 2023/01/02 12:05:38 INFO: All 0 tables opened in 0s
badger 2023/01/02 12:05:38 INFO: Discard stats nextEmptySlot: 0
badger 2023/01/02 12:05:38 INFO: Set nextTxnTs to 0
    publish_test.go:104: msg:0
        {
            ""about"": ""@z+xJSnzIQtg0Dywzvl7VUzTLpj5VFajA8wZ3IRz6ztQ=.ed25519"",
            ""name"": ""test user"",
            ""type"": ""about""
          }
    publish_test.go:104: msg:1
        {
            ""contact"": ""@p13zSAiOpguI9nsawkGijsnMfWmFd5rlUNpzekEE+vI=.ed25519"",
            ""following"": true,
            ""type"": ""contact""
          }
    publish_test.go:107: 
        	Error Trace:	/home/go-ssb/go-ssb/message/publish_test.go:107
        	Error:      	Expected value not to be nil.
        	Test:       	TestSignMessages
        	Messages:   	msg:1 - previous
    publish_test.go:104: msg:2
        {
            ""text"": ""# hello world!"",
            ""type"": ""text""
          }
badger 2023/01/02 12:05:38 INFO: Lifetime L0 stalled for: 0s
badger 2023/01/02 12:05:38 INFO: 
Level 0 [ ]: NumTables: 01. Size: 264 B of 0 B. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 64 MiB
Level 1 [ ]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level 2 [ ]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level 3 [ ]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level 4 [ ]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level 5 [ ]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level 6 [B]: NumTables: 00. Size: 0 B of 10 MiB. Score: 0.00->0.00 StaleData: 0 B Target FileSize: 2.0 MiB
Level Done
--- FAIL: TestSignMessages (0.04s)
FAIL
FAIL	github.com/ssbc/go-ssb/message	0.064s
FAIL
```",0,testsignmessages is flaky   after a bunch of passes  two failures in a row                        overwrote batch limit        run   testsignmessages  badger             info  all   tables opened in    badger             info  discard stats nextemptyslot     badger             info  set nexttxnts to        publish test go    msg                            about     z                      name    test user                 type    about                    publish test go    msg                            contact       vi                    following   true                type    contact                    publish test go              	error trace 	 home go ssb go ssb message publish test go            	error       	expected value not to be nil           	test        	testsignmessages          	messages    	msg     previous      publish test go    msg                            text      hello world                  type    text                    publish test go              	error trace 	 home go ssb go ssb message publish test go            	error       	expected value not to be nil           	test        	testsignmessages          	messages    	msg     previous  badger             info  lifetime   stalled for     badger             info    level      numtables     size    b of   b  score           staledata    b target filesize    mib  level      numtables     size    b of   mib  score           staledata    b target filesize      mib  level      numtables     size    b of   mib  score           staledata    b target filesize      mib  level      numtables     size    b of   mib  score           staledata    b target filesize      mib  level      numtables     size    b of   mib  score           staledata    b target filesize      mib  level      numtables     size    b of   mib  score           staledata    b target filesize      mib  level      numtables     size    b of   mib  score           staledata    b target filesize      mib  level done      fail  testsignmessages        fail  fail	github com ssbc go ssb message	     fail                overwrote batch limit        run   testsignmessages  badger             info  all   tables opened in    badger             info  discard stats nextemptyslot     badger             info  set nexttxnts to        publish test go    msg                            about     z                      name    test user                 type    about                    publish test go    msg                            contact       vi                    following   true                type    contact                    publish test go              	error trace 	 home go ssb go ssb message publish test go            	error       	expected value not to be nil           	test        	testsignmessages          	messages    	msg     previous      publish test go    msg                            text      hello world                  type    text                badger             info  lifetime   stalled for     badger             info    level      numtables     size    b of   b  score           staledata    b target filesize    mib  level      numtables     size    b of   mib  score           staledata    b target filesize      mib  level      numtables     size    b of   mib  score           staledata    b target filesize      mib  level      numtables     size    b of   mib  score           staledata    b target filesize      mib  level      numtables     size    b of   mib  score           staledata    b target filesize      mib  level      numtables     size    b of   mib  score           staledata    b target filesize      mib  level      numtables     size    b of   mib  score           staledata    b target filesize      mib  level done      fail  testsignmessages        fail  fail	github com ssbc go ssb message	     fail     ,0
106231,11473388820.0,IssuesEvent,2020-02-09 22:51:10,golang/go,https://api.github.com/repos/golang/go,closed,wiki: SettingGOPATH (redesign),Documentation NeedsInvestigation,"suggested to overwrite that [page](https://github.com/golang/go/wiki/SettingGOPATH)

Basic information on GOPATH is accessible by typing `go help gopath`.

```
$ go help gopath | head -7
The Go path is used to resolve import statements.
It is implemented by and documented in the go/build package.

The GOPATH environment variable lists places to look for Go code.
On Unix, the value is a colon-separated string.
On Windows, the value is a semicolon-separated string.
On Plan 9, the value is a list.
$ 
```

The value is unset, but a default is encoded in the go compiler.

($HOME/go on Unix, %USERPROFILE%\go on Windows, and $home/go on Plan 9)

login shells (Unix)

```
$ echo ""export GOPATH=$HOME/go"" >> ~/.profile
$
```

```
% echo ""setenv GOPATH $HOME/go"" >> ~/.login
%
```

interactive shells (Unix)

```
$ echo ""export GOPATH=$HOME/go"" >> ~/.bashrc
$
```

```
% echo ""setenv GOPATH $HOME/go"" >> ~/.cshrc
%
```

sourced files (Unix)

```
$ cat gopher
# GNU Bourne-Again SHell

export GOPATH=$HOME/go:/usr/share/gocode
$ . ~/gopher
$
```

```
% cat go-gopher
# Berkeley UNIX C shell

setenv GOPATH $HOME/go:/usr/share/gocode
% source ~/go-gopher
%
```

scripts (Windows)

```
C:\>TYPE gopher.bat
@ECHO OFF
SET GOPATH=%USERPROFILE%\go
C:\>
```

```
PS C:\> gc gopher.ps1
$env:GOPATH = ""$HOME\go""
PS C:\> .\gopher.ps1
PS C:\>
```

sourced file (Plan 9)

```
% cat gopher
# Rc shell (usually a value of a single component)

GOPATH=$home/go
% . gopher
%
```

using GOENV (all)

```
$ go version
go version go1.13.3 linux/386
$ ed $GOROOT/src/os/file.go
17452
406,415p
// UserConfigDir returns the default root directory to use for user-specific
// configuration data. Users should create their own application-specific
// subdirectory within this one and use that.
//
// On Unix systems, it returns $XDG_CONFIG_HOME as specified by
// https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html if
// non-empty, else $HOME/.config.
// On Darwin, it returns $HOME/Library/Application Support.
// On Windows, it returns %AppData%.
// On Plan 9, it returns $home/lib.
q
$
```

NB: The root of the Go tree cannot be included as a value in the Go path.",1.0,"wiki: SettingGOPATH (redesign) - suggested to overwrite that [page](https://github.com/golang/go/wiki/SettingGOPATH)

Basic information on GOPATH is accessible by typing `go help gopath`.

```
$ go help gopath | head -7
The Go path is used to resolve import statements.
It is implemented by and documented in the go/build package.

The GOPATH environment variable lists places to look for Go code.
On Unix, the value is a colon-separated string.
On Windows, the value is a semicolon-separated string.
On Plan 9, the value is a list.
$ 
```

The value is unset, but a default is encoded in the go compiler.

($HOME/go on Unix, %USERPROFILE%\go on Windows, and $home/go on Plan 9)

login shells (Unix)

```
$ echo ""export GOPATH=$HOME/go"" >> ~/.profile
$
```

```
% echo ""setenv GOPATH $HOME/go"" >> ~/.login
%
```

interactive shells (Unix)

```
$ echo ""export GOPATH=$HOME/go"" >> ~/.bashrc
$
```

```
% echo ""setenv GOPATH $HOME/go"" >> ~/.cshrc
%
```

sourced files (Unix)

```
$ cat gopher
# GNU Bourne-Again SHell

export GOPATH=$HOME/go:/usr/share/gocode
$ . ~/gopher
$
```

```
% cat go-gopher
# Berkeley UNIX C shell

setenv GOPATH $HOME/go:/usr/share/gocode
% source ~/go-gopher
%
```

scripts (Windows)

```
C:\>TYPE gopher.bat
@ECHO OFF
SET GOPATH=%USERPROFILE%\go
C:\>
```

```
PS C:\> gc gopher.ps1
$env:GOPATH = ""$HOME\go""
PS C:\> .\gopher.ps1
PS C:\>
```

sourced file (Plan 9)

```
% cat gopher
# Rc shell (usually a value of a single component)

GOPATH=$home/go
% . gopher
%
```

using GOENV (all)

```
$ go version
go version go1.13.3 linux/386
$ ed $GOROOT/src/os/file.go
17452
406,415p
// UserConfigDir returns the default root directory to use for user-specific
// configuration data. Users should create their own application-specific
// subdirectory within this one and use that.
//
// On Unix systems, it returns $XDG_CONFIG_HOME as specified by
// https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html if
// non-empty, else $HOME/.config.
// On Darwin, it returns $HOME/Library/Application Support.
// On Windows, it returns %AppData%.
// On Plan 9, it returns $home/lib.
q
$
```

NB: The root of the Go tree cannot be included as a value in the Go path.",1,wiki  settinggopath  redesign    suggested to overwrite that        basic information on gopath is accessible by typing  go help gopath             go help gopath   head     the go path is used to resolve import statements   it is implemented by and documented in the go build package     the gopath environment variable lists places to look for go code   on unix  the value is a colon separated string   on windows  the value is a semicolon separated string   on plan    the value is a list              the value is unset  but a default is encoded in the go compiler       home go on unix   userprofile  go on windows  and  home go on plan       login shells  unix            echo  export gopath  home go        profile                   echo  setenv gopath  home go        login            interactive shells  unix            echo  export gopath  home go        bashrc                   echo  setenv gopath  home go        cshrc            sourced files  unix            cat gopher    gnu bourne again shell    export gopath  home go  usr share gocode        gopher                   cat go gopher    berkeley unix c shell    setenv gopath  home go  usr share gocode    source   go gopher            scripts  windows          c   type gopher bat   echo off  set gopath  userprofile  go  c                 ps c    gc gopher     env gopath     home go   ps c      gopher    ps c            sourced file  plan              cat gopher    rc shell  usually a value of a single component     gopath  home go      gopher            using goenv  all            go version  go version       linux      ed  goroot src os file go             userconfigdir returns the default root directory to use for user specific     configuration data  users should create their own application specific     subdirectory within this one and use that          on unix systems  it returns  xdg config home as specified by       if     non empty  else  home  config      on darwin  it returns  home library application support      on windows  it returns  appdata       on plan    it returns  home lib   q            nb  the root of the go tree cannot be included as a value in the go path ,1
113865,9666984262.0,IssuesEvent,2019-05-21 12:14:08,telstra/open-kilda,https://api.github.com/repos/telstra/open-kilda,opened,OpenTsdbTopologyTest fails periodically,area/testing bug,"```
[ERROR]   OpenTsdbTopologyTest.shouldSendDatapointRequestsTwice:127 Request not found exactly 2 times, expected:<{ }> but was:<{
  ""method"" : ""POST"",
  ""path"" : ""/api/put"",
  ""queryStringParameters"" : [ {
    ""name"" : ""details"",
    ""values"" : [ """" ]
  } ],
  ""headers"" : [ {
    ""name"" : ""Content-Type"",
    ""values"" : [ ""application/json"" ]
  }, {
    ""name"" : ""User-Agent"",
    ""values"" : [ ""Jersey/2.25.1 (Apache HttpClient 4.5)"" ]
  }, {
    ""name"" : ""Host"",
    ""values"" : [ ""localhost:4242"" ]
  }, {
    ""name"" : ""Accept-Encoding"",
    ""values"" : [ ""gzip,deflate"" ]
  }, {
    ""name"" : ""content-length"",
    ""values"" : [ ""137"" ]
  } ],
  ""keepAlive"" : true,
  ""secure"" : false,
  ""body"" : {
    ""type"" : ""STRING"",
    ""string"" : ""[{\""metric\"":\""metric\"",\""tags\"":{},\""timestamp\"":1558437049749,\""value\"":456},{\""metric\"":\""metric\"",\""tags\"":{},\""timestamp\"":1558437049749,\""value\"":123}]"",
    ""contentType"" : ""text/plain; charset=utf-8""
  }
}>
```
with the cause of

```
java.lang.RuntimeException: Exception while binding MockServer to port 4242

	at org.mockserver.mockserver.MockServer.bindToPorts(MockServer.java:124)
	at org.mockserver.mockserver.MockServer.<init>(MockServer.java:68)
	at org.mockserver.integration.ClientAndServer.<init>(ClientAndServer.java:20)
	at org.mockserver.integration.ClientAndServer.startClientAndServer(ClientAndServer.java:29)
	at org.openkilda.wfm.topology.opentsdb.OpenTsdbTopologyTest.setupOnce(OpenTsdbTopologyTest.java:49)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
	at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
	at org.junit.rules.RunRules.evaluate(RunRules.java:20)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
	at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
	at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:54)
	at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
	at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
Caused by: java.net.BindException: Address already in use
```",1.0,"OpenTsdbTopologyTest fails periodically - ```
[ERROR]   OpenTsdbTopologyTest.shouldSendDatapointRequestsTwice:127 Request not found exactly 2 times, expected:<{ }> but was:<{
  ""method"" : ""POST"",
  ""path"" : ""/api/put"",
  ""queryStringParameters"" : [ {
    ""name"" : ""details"",
    ""values"" : [ """" ]
  } ],
  ""headers"" : [ {
    ""name"" : ""Content-Type"",
    ""values"" : [ ""application/json"" ]
  }, {
    ""name"" : ""User-Agent"",
    ""values"" : [ ""Jersey/2.25.1 (Apache HttpClient 4.5)"" ]
  }, {
    ""name"" : ""Host"",
    ""values"" : [ ""localhost:4242"" ]
  }, {
    ""name"" : ""Accept-Encoding"",
    ""values"" : [ ""gzip,deflate"" ]
  }, {
    ""name"" : ""content-length"",
    ""values"" : [ ""137"" ]
  } ],
  ""keepAlive"" : true,
  ""secure"" : false,
  ""body"" : {
    ""type"" : ""STRING"",
    ""string"" : ""[{\""metric\"":\""metric\"",\""tags\"":{},\""timestamp\"":1558437049749,\""value\"":456},{\""metric\"":\""metric\"",\""tags\"":{},\""timestamp\"":1558437049749,\""value\"":123}]"",
    ""contentType"" : ""text/plain; charset=utf-8""
  }
}>
```
with the cause of

```
java.lang.RuntimeException: Exception while binding MockServer to port 4242

	at org.mockserver.mockserver.MockServer.bindToPorts(MockServer.java:124)
	at org.mockserver.mockserver.MockServer.<init>(MockServer.java:68)
	at org.mockserver.integration.ClientAndServer.<init>(ClientAndServer.java:20)
	at org.mockserver.integration.ClientAndServer.startClientAndServer(ClientAndServer.java:29)
	at org.openkilda.wfm.topology.opentsdb.OpenTsdbTopologyTest.setupOnce(OpenTsdbTopologyTest.java:49)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
	at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
	at org.junit.rules.RunRules.evaluate(RunRules.java:20)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
	at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
	at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:54)
	at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
	at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
Caused by: java.net.BindException: Address already in use
```",0,opentsdbtopologytest fails periodically            opentsdbtopologytest shouldsenddatapointrequeststwice   request not found exactly   times  expected   but was        method     post       path      api put       querystringparameters              name     details         values                  headers              name     content type         values                    name     user agent         values                    name     host         values                    name     accept encoding         values                    name     content length         values                  keepalive    true      secure    false      body            type     string         string               contenttype     text plain  charset utf                   with the cause of         java lang runtimeexception  exception while binding mockserver to port      	at org mockserver mockserver mockserver bindtoports mockserver java     	at org mockserver mockserver mockserver   mockserver java     	at org mockserver integration clientandserver   clientandserver java     	at org mockserver integration clientandserver startclientandserver clientandserver java     	at org openkilda wfm topology opentsdb opentsdbtopologytest setuponce opentsdbtopologytest java     	at sun reflect nativemethodaccessorimpl   native method   	at sun reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java     	at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java     	at java lang reflect method invoke method java     	at org junit runners model frameworkmethod   runreflectivecall frameworkmethod java     	at org junit internal runners model reflectivecallable run reflectivecallable java     	at org junit runners model frameworkmethod invokeexplosively frameworkmethod java     	at org junit internal runners statements runbefores evaluate runbefores java     	at org junit rules externalresource   evaluate externalresource java     	at org junit rules runrules evaluate runrules java     	at org junit runners parentrunner run parentrunner java     	at org junit runner junitcore run junitcore java     	at com intellij     startrunnerwithargs   java     	at com intellij rt execution junit ideatestrunner repeater startrunnerwithargs ideatestrunner java     	at com intellij rt execution junit junitstarter preparestreamsandstart junitstarter java     	at com intellij rt execution junit junitstarter main junitstarter java     caused by  java net bindexception  address already in use     ,0
370178,25892540986.0,IssuesEvent,2022-12-14 19:14:24,golang/go,https://api.github.com/repos/golang/go,closed,spec: document new behavior for `comparable`,Documentation,Reminder issue to document the spec change for #56548.,1.0,spec: document new behavior for `comparable` - Reminder issue to document the spec change for #56548.,1,spec  document new behavior for  comparable    reminder issue to document the spec change for    ,1
52208,7752878849.0,IssuesEvent,2018-05-30 21:48:36,golang/go,https://api.github.com/repos/golang/go,closed,blog: one sentence typo of blog go-maps-in-action,Documentation NeedsFix help wanted,"in blog

https://blog.golang.org/go-maps-in-action

section `Iteration order`

>When iterating over a map with a range loop, the iteration order is not specified and is not guaranteed to be the same from one iteration to the next. Since Go 1 the runtime randomizes map iteration order, as programmers relied on the stable iteration order of the previous implementation. If you require a stable iteration order you must maintain a separate data structure that specifies that order. This example uses a separate sorted slice of keys to print a map[int]string in key order:

may be the sentence should be below

```
Since Go in the runtime randomizes map iteration order
```",1.0,"blog: one sentence typo of blog go-maps-in-action - in blog

https://blog.golang.org/go-maps-in-action

section `Iteration order`

>When iterating over a map with a range loop, the iteration order is not specified and is not guaranteed to be the same from one iteration to the next. Since Go 1 the runtime randomizes map iteration order, as programmers relied on the stable iteration order of the previous implementation. If you require a stable iteration order you must maintain a separate data structure that specifies that order. This example uses a separate sorted slice of keys to print a map[int]string in key order:

may be the sentence should be below

```
Since Go in the runtime randomizes map iteration order
```",1,blog  one sentence typo of blog go maps in action   in blog         section  iteration order      when iterating over a map with a range loop  the iteration order is not specified and is not guaranteed to be the same from one iteration to the next  since go   the runtime randomizes map iteration order  as programmers relied on the stable iteration order of the previous implementation  if you require a stable iteration order you must maintain a separate data structure that specifies that order  this example uses a separate sorted slice of keys to print a map string in key order     may be the sentence should be below         since go in the runtime randomizes map iteration order     ,1
211587,16450014678.0,IssuesEvent,2021-05-21 03:24:00,golang/go,https://api.github.com/repos/golang/go,closed,io/fs: no examples for how to use it with the operating system,Documentation NeedsFix help wanted,"I needed to walk a directory, so I pulled up the `io/fs.WalkDir` docs, but there was nothing telling me how to get an `FS` instance for the operating system's filesystem. The only mention of `os.DirFS` is in `fs.Sub`, and I only found it because I had a hunch to search `os.`.",1.0,"io/fs: no examples for how to use it with the operating system - I needed to walk a directory, so I pulled up the `io/fs.WalkDir` docs, but there was nothing telling me how to get an `FS` instance for the operating system's filesystem. The only mention of `os.DirFS` is in `fs.Sub`, and I only found it because I had a hunch to search `os.`.",1,io fs  no examples for how to use it with the operating system   i needed to walk a directory  so i pulled up the  io fs walkdir  docs  but there was nothing telling me how to get an  fs  instance for the operating system s filesystem  the only mention of  os dirfs  is in  fs sub   and i only found it because i had a hunch to search  os   ,1
219252,16823886235.0,IssuesEvent,2021-06-17 15:58:56,golang/go,https://api.github.com/repos/golang/go,closed,"cmd/go: on malformed ""go mod edit -go"", suggest current version of go, not hardcoded 1.12",Documentation NeedsFix help wanted modules,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version devel +0f897f916a Tue May 28 02:52:39 2019 +0000 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

n/a, `go mod edit` suggests `-go 1.12` on go1.12.5.

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

I wasn't sure if there was a way to `go mod edit` to put the `go 1.12` directive in the ""right"" place in 1.12, prior to #31960 on tip, so I ran with a garbage argument to `-go`. This command has the same output in 1.12 and tip:

```
$  go mod edit -go=x
go mod: invalid -go option; expecting something like ""-go 1.12""
```

### What did you expect to see?

I expected the output to suggest `-go 1.13` when running with tip.

### What did you see instead?

It suggested `-go 1.12`, which seems odd given that I am running what is going to be 1.13.

I suppose there's an argument to suggest 1.12 as a ""downgrading"" case when go.mod already provides `go 1.13`, but the argument to use `-go 1.13` to upgrade from a `go 1.12` in go.mod seems just as valid.",1.0,"cmd/go: on malformed ""go mod edit -go"", suggest current version of go, not hardcoded 1.12 - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version devel +0f897f916a Tue May 28 02:52:39 2019 +0000 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

n/a, `go mod edit` suggests `-go 1.12` on go1.12.5.

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

I wasn't sure if there was a way to `go mod edit` to put the `go 1.12` directive in the ""right"" place in 1.12, prior to #31960 on tip, so I ran with a garbage argument to `-go`. This command has the same output in 1.12 and tip:

```
$  go mod edit -go=x
go mod: invalid -go option; expecting something like ""-go 1.12""
```

### What did you expect to see?

I expected the output to suggest `-go 1.13` when running with tip.

### What did you see instead?

It suggested `-go 1.12`, which seems odd given that I am running what is going to be 1.13.

I suppose there's an argument to suggest 1.12 as a ""downgrading"" case when go.mod already provides `go 1.13`, but the argument to use `-go 1.13` to upgrade from a `go 1.12` in go.mod seems just as valid.",1,cmd go  on malformed  go mod edit  go   suggest current version of go  not hardcoded                what version of go are you using   go version            go version  go version devel    tue may              darwin             does this issue reproduce with the latest release     n a   go mod edit  suggests   go      on               what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best          i wasn t sure if there was a way to  go mod edit  to put the  go      directive in the  right  place in      prior to    on tip  so i ran with a garbage argument to   go   this command has the same output in     and tip             go mod edit  go x  go mod  invalid  go option  expecting something like   go                  what did you expect to see     i expected the output to suggest   go      when running with tip         what did you see instead     it suggested   go       which seems odd given that i am running what is going to be         i suppose there s an argument to suggest     as a  downgrading  case when go mod already provides  go       but the argument to use   go      to upgrade from a  go      in go mod seems just as valid ,1
688477,23583963052.0,IssuesEvent,2022-08-23 09:58:09,naev/naev,https://api.github.com/repos/naev/naev,closed,More Save Control,Type-Enhancement Priority-Low GoodFirstProject,Allow players to clone or rename save games freely in-game. Probably will need to decouple save file name from player name.,1.0,More Save Control - Allow players to clone or rename save games freely in-game. Probably will need to decouple save file name from player name.,0,more save control   allow players to clone or rename save games freely in game  probably will need to decouple save file name from player name ,0
541683,15831474726.0,IssuesEvent,2021-04-06 13:40:21,hassio-addons/repository-updater,https://api.github.com/repos/hassio-addons/repository-updater,closed,AppArmor.txt not being updated,enhancement priority-medium,"# Problem/Motivation

The apparmor.txt file in the addon-repository is not updated in the addonS-repo

## Expected behavior

I was expecting that the update would take the apparmor.txt file in consideration

## Steps to reproduce

Create an addon with the apparmor
Setup the workflow to update the addonS-repository
The apparmor file won't be added/updated
",1.0,"AppArmor.txt not being updated - # Problem/Motivation

The apparmor.txt file in the addon-repository is not updated in the addonS-repo

## Expected behavior

I was expecting that the update would take the apparmor.txt file in consideration

## Steps to reproduce

Create an addon with the apparmor
Setup the workflow to update the addonS-repository
The apparmor file won't be added/updated
",0,apparmor txt not being updated     problem motivation    the apparmor txt file in the addon repository is not updated in the addons repo       expected behavior    i was expecting that the update would take the apparmor txt file in consideration       steps to reproduce    create an addon with the apparmor  setup the workflow to update the addons repository  the apparmor file won t be added updated  ,0
93375,3899353861.0,IssuesEvent,2016-04-17 17:52:18,okfn/okfn.github.com,https://api.github.com/repos/okfn/okfn.github.com,closed,[Post] Review of PDF data wrangling tools,Priority: ★★★ Topic: Blog Post,"Write a post reviewing data wrangling tools for PDFs

**Text in progress at: <del>http://pad.okfn.org/p/labs-post-pdf-tools</del> inlined below**

Based on research material in https://github.com/okfn/ideas/issues/52

Questions:

* [ ] should we split into a series e.g. [ans: no]
  * libraries and tools
  * web services
  * specific examples - e.g. scraping in python, scraping in node etc
  * using scraperwiki
* [ ] should this go on schoolofdata? [ans: no]

# Libraries for Extracting Data and Text from PDFs: A Review

<meta>
* Authors: Rufus Pollock
    [add your name here if you contribute and want to be credited]
* Who is this for? Data wranglers who would be looking to extract information from PDF
* We should try and offer opinions on tools where possible
[should actually review the tools ie. which is best? pros/cons? level of capability required? reliability
[paragraph on crowd-scraping as well? ""alternative approaches when your geeks can't do it""]
[perhaps find a sample PDF and see how each tool does? show the differences in output?] - This is a GREAT idea.
</meta>

Extracting data from PDFs unfortunately remains a common data wrangling task. This post reviews various tools and services for doing this with a focus on free (and preferably) open source options.


3 categories:

* Extracting text from PDF
* Extracting tables from PDF
* Extracting data (text or otherwise) from PDFs with scans

The last case is really a situation for OCR (optical character recognition) so we're going to ignore it here.
[should include a short para on OCR too, just to provide an indication of the limits of automated extraction without much pre-processing]

[[TODO: some nice PDF screenshots - perhaps we can reference]]

## Generic (PDF -> text)

* [PDFMiner][pdfminer] - PDFMiner is a tool for extracting information from PDF documents. Unlike other PDF-related tools, it focuses entirely on getting and analyzing text data. PDFMiner allows one to obtain the exact location of text in a page, as well as other information such as fonts or lines. It includes a PDF converter that can transform PDF files into other text formats (such as HTML). It has an extensible PDF parser that can be used for other purposes than text analysis.
  * Pure python
* [pdftohtml][] - pdftohtml is a utility which converts PDF files into HTML and XML formats. Based on xpdf
  * Command-line Linux
* [pdftoxml][] - command line utility to convert PDF to XML built on poppler.
* [docsplit][] - part of DocumentCloud. Docsplit is a command-line utility and Ruby library for splitting apart documents into their component parts: searchable UTF-8 plain text via OCR if necessary, page images or thumbnails in any format, PDFs, single pages, and document metadata (title, author, number of pages...)
* [pypdf2xml][] - convert PDF to XML. Built on pdfminer. Started as an alternative to poppler's pdftoxml, which didn't properly decode CID Type2 fonts in PDFs.
* [pdf2htmlEX][] - Convert PDF to HTML without losing text or format. C++. Fast. Primarily focused on producing HTML that exactly resembles the original PDF. Limited use for straightforward text extraction.

[pdf2htmlEX]: http://coolwanglu.github.io/pdf2htmlEX/
[pypdf2xml]: https://github.com/zejn/pypdf2xml
[docsplit]: http://documentcloud.github.io/docsplit/
[pdfminer]: http://www.unixuser.org/~euske/python/pdfminer/
[pdftohtml]: http://pdftohtml.sourceforge.net/
[pdftoxml]: http://pdftoxml.sourceforge.net/

### Tables from PDF

* <http://tabula.nerdpower.org/> - open-source, designed specifically for tabular data. Now easy to install. Ruby-based.
* https://github.com/okfn/pdftables - open-source. Created by Scraperwiki but no longer seems to be available so here is a fork)
* <http://pdftoxml.sourceforge.net/> - one of the better for tables but have not used for a while
* <http://pdftohtml.sourceforge.net/> - linux only afaict
* <https://github.com/liberit/scraptils/blob/master/scraptils/tools/pdf2csv.py> AGPLv3+, python, scraptils has other useful tools as well, pdf2csv needs pdfminer==20110515
* [pdf.js](http://mozilla.github.io/pdf.js/) - you probably want a fork like [pdf2json](https://github.com/modesty/pdf2json) or [node-pdfreader](https://github.com/jviereck/node-pdfreader) that integrates this better with node. I have not tried this on tables though ...
* Using scraperwiki + pdftoxml - see this recent tutorial [Get Started With Scraping – Extracting Simple Tables from PDF Documents][scoda-simple-tables]

### Existing open services

* http://pdfx.cs.man.ac.uk/ - has a nice command line interface
  * Is this open? Says at [bottom of usage](http://pdfx.cs.man.ac.uk/usage) that it is powered by http://www.utopiadocs.com/
* Scraperwiki - https://views.scraperwiki.com/run/pdf-to-html-preview-1/ and [this tutorial](http://blog.scraperwiki.com/2010/12/17/scraping-pdfs-now-26-less-unpleasant-with-scraperwiki/)

### Existing proprietary free or paid-for services

* http://www.newocr.com/ - free, no API
* http://www.free-ocr.com/ - free, no API, captcha
* http://www.onlineocr.net/ - free
* http://captricity.com/
* https://pdftables.com/ - pay-per-page service

Google app engine used to do this http://developers.google.com/appengine/docs/python/conversion/overview

### By Language

@maxogden has this list of Node libraries and tools:

https://gist.github.com/maxogden/5842859

Here's a gist showing how to use pdf2json: https://gist.github.com/rgrp/5944247

## Other good intros

* <http://thomaslevine.com/!/parsing-pdfs/>
* [Extracting Data from PDFs - School of Data][scoda-1]

[scoda-1]: http://schoolofdata.org/handbook/courses/extracting-data-from-pdf/
[scoda-simple-tables]: http://schoolofdata.org/2013/06/18/get-started-with-scraping-extracting-simple-tables-from-pdf-documents/
",1.0,"[Post] Review of PDF data wrangling tools - Write a post reviewing data wrangling tools for PDFs

**Text in progress at: <del>http://pad.okfn.org/p/labs-post-pdf-tools</del> inlined below**

Based on research material in https://github.com/okfn/ideas/issues/52

Questions:

* [ ] should we split into a series e.g. [ans: no]
  * libraries and tools
  * web services
  * specific examples - e.g. scraping in python, scraping in node etc
  * using scraperwiki
* [ ] should this go on schoolofdata? [ans: no]

# Libraries for Extracting Data and Text from PDFs: A Review

<meta>
* Authors: Rufus Pollock
    [add your name here if you contribute and want to be credited]
* Who is this for? Data wranglers who would be looking to extract information from PDF
* We should try and offer opinions on tools where possible
[should actually review the tools ie. which is best? pros/cons? level of capability required? reliability
[paragraph on crowd-scraping as well? ""alternative approaches when your geeks can't do it""]
[perhaps find a sample PDF and see how each tool does? show the differences in output?] - This is a GREAT idea.
</meta>

Extracting data from PDFs unfortunately remains a common data wrangling task. This post reviews various tools and services for doing this with a focus on free (and preferably) open source options.


3 categories:

* Extracting text from PDF
* Extracting tables from PDF
* Extracting data (text or otherwise) from PDFs with scans

The last case is really a situation for OCR (optical character recognition) so we're going to ignore it here.
[should include a short para on OCR too, just to provide an indication of the limits of automated extraction without much pre-processing]

[[TODO: some nice PDF screenshots - perhaps we can reference]]

## Generic (PDF -> text)

* [PDFMiner][pdfminer] - PDFMiner is a tool for extracting information from PDF documents. Unlike other PDF-related tools, it focuses entirely on getting and analyzing text data. PDFMiner allows one to obtain the exact location of text in a page, as well as other information such as fonts or lines. It includes a PDF converter that can transform PDF files into other text formats (such as HTML). It has an extensible PDF parser that can be used for other purposes than text analysis.
  * Pure python
* [pdftohtml][] - pdftohtml is a utility which converts PDF files into HTML and XML formats. Based on xpdf
  * Command-line Linux
* [pdftoxml][] - command line utility to convert PDF to XML built on poppler.
* [docsplit][] - part of DocumentCloud. Docsplit is a command-line utility and Ruby library for splitting apart documents into their component parts: searchable UTF-8 plain text via OCR if necessary, page images or thumbnails in any format, PDFs, single pages, and document metadata (title, author, number of pages...)
* [pypdf2xml][] - convert PDF to XML. Built on pdfminer. Started as an alternative to poppler's pdftoxml, which didn't properly decode CID Type2 fonts in PDFs.
* [pdf2htmlEX][] - Convert PDF to HTML without losing text or format. C++. Fast. Primarily focused on producing HTML that exactly resembles the original PDF. Limited use for straightforward text extraction.

[pdf2htmlEX]: http://coolwanglu.github.io/pdf2htmlEX/
[pypdf2xml]: https://github.com/zejn/pypdf2xml
[docsplit]: http://documentcloud.github.io/docsplit/
[pdfminer]: http://www.unixuser.org/~euske/python/pdfminer/
[pdftohtml]: http://pdftohtml.sourceforge.net/
[pdftoxml]: http://pdftoxml.sourceforge.net/

### Tables from PDF

* <http://tabula.nerdpower.org/> - open-source, designed specifically for tabular data. Now easy to install. Ruby-based.
* https://github.com/okfn/pdftables - open-source. Created by Scraperwiki but no longer seems to be available so here is a fork)
* <http://pdftoxml.sourceforge.net/> - one of the better for tables but have not used for a while
* <http://pdftohtml.sourceforge.net/> - linux only afaict
* <https://github.com/liberit/scraptils/blob/master/scraptils/tools/pdf2csv.py> AGPLv3+, python, scraptils has other useful tools as well, pdf2csv needs pdfminer==20110515
* [pdf.js](http://mozilla.github.io/pdf.js/) - you probably want a fork like [pdf2json](https://github.com/modesty/pdf2json) or [node-pdfreader](https://github.com/jviereck/node-pdfreader) that integrates this better with node. I have not tried this on tables though ...
* Using scraperwiki + pdftoxml - see this recent tutorial [Get Started With Scraping – Extracting Simple Tables from PDF Documents][scoda-simple-tables]

### Existing open services

* http://pdfx.cs.man.ac.uk/ - has a nice command line interface
  * Is this open? Says at [bottom of usage](http://pdfx.cs.man.ac.uk/usage) that it is powered by http://www.utopiadocs.com/
* Scraperwiki - https://views.scraperwiki.com/run/pdf-to-html-preview-1/ and [this tutorial](http://blog.scraperwiki.com/2010/12/17/scraping-pdfs-now-26-less-unpleasant-with-scraperwiki/)

### Existing proprietary free or paid-for services

* http://www.newocr.com/ - free, no API
* http://www.free-ocr.com/ - free, no API, captcha
* http://www.onlineocr.net/ - free
* http://captricity.com/
* https://pdftables.com/ - pay-per-page service

Google app engine used to do this http://developers.google.com/appengine/docs/python/conversion/overview

### By Language

@maxogden has this list of Node libraries and tools:

https://gist.github.com/maxogden/5842859

Here's a gist showing how to use pdf2json: https://gist.github.com/rgrp/5944247

## Other good intros

* <http://thomaslevine.com/!/parsing-pdfs/>
* [Extracting Data from PDFs - School of Data][scoda-1]

[scoda-1]: http://schoolofdata.org/handbook/courses/extracting-data-from-pdf/
[scoda-simple-tables]: http://schoolofdata.org/2013/06/18/get-started-with-scraping-extracting-simple-tables-from-pdf-documents/
",0,  review of pdf data wrangling tools   write a post reviewing data wrangling tools for pdfs      text in progress at     inlined below      based on research material in      questions         should we split into a series e g         libraries and tools      web services      specific examples   e g  scraping in python  scraping in node etc      using scraperwiki      should this go on schoolofdata         libraries for extracting data and text from pdfs  a review         authors  rufus pollock           who is this for  data wranglers who would be looking to extract information from pdf    we should try and offer opinions on tools where possible   should actually review the tools ie  which is best  pros cons  level of capability required  reliability         this is a great idea        extracting data from pdfs unfortunately remains a common data wrangling task  this post reviews various tools and services for doing this with a focus on free  and preferably  open source options         categories       extracting text from pdf    extracting tables from pdf    extracting data  text or otherwise  from pdfs with scans    the last case is really a situation for ocr  optical character recognition  so we re going to ignore it here                 generic  pdf    text            pdfminer is a tool for extracting information from pdf documents  unlike other pdf related tools  it focuses entirely on getting and analyzing text data  pdfminer allows one to obtain the exact location of text in a page  as well as other information such as fonts or lines  it includes a pdf converter that can transform pdf files into other text formats  such as html   it has an extensible pdf parser that can be used for other purposes than text analysis       pure python         pdftohtml is a utility which converts pdf files into html and xml formats  based on xpdf      command line linux         command line utility to convert pdf to xml built on poppler          part of documentcloud  docsplit is a command line utility and ruby library for splitting apart documents into their component parts  searchable utf   plain text via ocr if necessary  page images or thumbnails in any format  pdfs  single pages  and document metadata  title  author  number of pages             convert pdf to xml  built on pdfminer  started as an alternative to poppler s pdftoxml  which didn t properly decode cid   fonts in pdfs          convert pdf to html without losing text or format  c    fast  primarily focused on producing html that exactly resembles the original pdf  limited use for straightforward text extraction                                               tables from pdf           open source  designed specifically for tabular data  now easy to install  ruby based         open source  created by scraperwiki but no longer seems to be available so here is a fork          one of the better for tables but have not used for a while         linux only afaict           python  scraptils has other useful tools as well    needs pdfminer             you probably want a fork like     or     that integrates this better with node  i have not tried this on tables though        using scraperwiki   pdftoxml   see this recent tutorial           existing open services          has a nice command line interface      is this open  says at     that it is powered by      scraperwiki     and            existing proprietary free or paid for services          free  no api        free  no api  captcha        free             pay per page service    google app engine used to do this          by language     maxogden has this list of node libraries and tools          here s a gist showing how to use            other good intros                              ,0
28866,5543546478.0,IssuesEvent,2017-03-22 17:09:47,golang/go,https://api.github.com/repos/golang/go,closed,wiki: wrong/outdated instructions on the Ubuntu page,Documentation,"Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
1.8

### What operating system and processor architecture are you using (`go env`)?
Ubuntu Linux 16.10

### What did you do?
Followed the readme

If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.


### What did you expect to see?
Golang 1.8 as a package.

### What did you see instead?
Your instructions appear to be installing LXD PPA repo and then installing golang 1.6 from the universe repository.

>sudo add-apt-repository ppa:ubuntu-lxc/lxd-stable
sudo apt-get update
sudo apt-get install golang

That's just wrong.
The bottom of the page instructions work alright.
But if you have a PPA you should update the instructions and if you don't have a PPA (I couldn't find one), then you should remove those instructions.

Thanks!",1.0,"wiki: wrong/outdated instructions on the Ubuntu page - Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
1.8

### What operating system and processor architecture are you using (`go env`)?
Ubuntu Linux 16.10

### What did you do?
Followed the readme

If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.


### What did you expect to see?
Golang 1.8 as a package.

### What did you see instead?
Your instructions appear to be installing LXD PPA repo and then installing golang 1.6 from the universe repository.

>sudo add-apt-repository ppa:ubuntu-lxc/lxd-stable
sudo apt-get update
sudo apt-get install golang

That's just wrong.
The bottom of the page instructions work alright.
But if you have a PPA you should update the instructions and if you don't have a PPA (I couldn't find one), then you should remove those instructions.

Thanks!",1,wiki  wrong outdated instructions on the ubuntu page   please answer these questions before submitting your issue  thanks         what version of go are you using   go version                what operating system and processor architecture are you using   go env     ubuntu linux            what did you do   followed the readme    if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best           what did you expect to see   golang     as a package         what did you see instead   your instructions appear to be installing lxd ppa repo and then installing golang     from the universe repository      sudo add apt repository ppa ubuntu lxc lxd stable  sudo apt get update  sudo apt get install golang    that s just wrong   the bottom of the page instructions work alright   but if you have a ppa you should update the instructions and if you don t have a ppa  i couldn t find one   then you should remove those instructions     thanks ,1
3684,5903616146.0,IssuesEvent,2017-05-19 07:24:30,Microsoft/vsts-tasks,https://api.github.com/repos/Microsoft/vsts-tasks,closed,using variable with AzureRmWebAppDeployment App Service name,Area: Release AzureAppService,"I can't use variable in App Service name of AzureRmWebAppDeployment (it requires had coded name to figure out application  type (""visibleRule"": ""WebAppKind = app || WebAppKind = functionapp"")

We use Release Definition and environments for environment creation we run Azure Resource Group Deployment to create the Web Apps and AzureRmWebAppDeployment to deploy base files (Sitecore etc.  dll) I can use version 2 without a problem but when I try to update to version 3 only Azure Subscription and App Service name is visible 
",1.0,"using variable with AzureRmWebAppDeployment App Service name - I can't use variable in App Service name of AzureRmWebAppDeployment (it requires had coded name to figure out application  type (""visibleRule"": ""WebAppKind = app || WebAppKind = functionapp"")

We use Release Definition and environments for environment creation we run Azure Resource Group Deployment to create the Web Apps and AzureRmWebAppDeployment to deploy base files (Sitecore etc.  dll) I can use version 2 without a problem but when I try to update to version 3 only Azure Subscription and App Service name is visible 
",0,using variable with azurermwebappdeployment app service name   i can t use variable in app service name of azurermwebappdeployment  it requires had coded name to figure out application  type   visiblerule    webappkind   app    webappkind   functionapp      we use release definition and environments for environment creation we run azure resource group deployment to create the web apps and azurermwebappdeployment to deploy base files  sitecore etc   dll  i can use version   without a problem but when i try to update to version   only azure subscription and app service name is visible   ,0
55480,23486519113.0,IssuesEvent,2022-08-17 14:49:08,cityofaustin/atd-data-tech,https://api.github.com/repos/cityofaustin/atd-data-tech,closed,Enhancements for HR Employee Surveys,Workgroup: HR Service: Apps Service: Product Type: Enhancement Product: Human Resources,"Enhancements requested by the stakeholders:

- [x] 1. Can we retitle the staff form from “Supervisor Surveys for Employee SSPRs” to “Onboarding Surveys for New Employees”  and 
- [x] 2. Can we retitle the employee form from “30 Day Employee Follow-ups” to “Employee Onboarding Survey”. 
- [x] 3. Could we also add a note and progress section on the HR employee tracking side?  Something similar to what you added to the supervisor side would be great. 
- [x] 4. On the 90 Day Survey, question 2. Can we move “Check all that apply” above the options? See below. 
 ![image.png](https://images.zenhubusercontent.com/5da61135c9a7f8000179986e/598503df-750e-47d4-acae-920594389df5)
- [x] 5. On the 120 survey, can we edit question 5 to ask “Do you require additional assistance for conducting the employee performance?”
- we should have an update on the start date for the onboarding surveys after our meeting. 
",2.0,"Enhancements for HR Employee Surveys - Enhancements requested by the stakeholders:

- [x] 1. Can we retitle the staff form from “Supervisor Surveys for Employee SSPRs” to “Onboarding Surveys for New Employees”  and 
- [x] 2. Can we retitle the employee form from “30 Day Employee Follow-ups” to “Employee Onboarding Survey”. 
- [x] 3. Could we also add a note and progress section on the HR employee tracking side?  Something similar to what you added to the supervisor side would be great. 
- [x] 4. On the 90 Day Survey, question 2. Can we move “Check all that apply” above the options? See below. 
 ![image.png](https://images.zenhubusercontent.com/5da61135c9a7f8000179986e/598503df-750e-47d4-acae-920594389df5)
- [x] 5. On the 120 survey, can we edit question 5 to ask “Do you require additional assistance for conducting the employee performance?”
- we should have an update on the start date for the onboarding surveys after our meeting. 
",0,enhancements for hr employee surveys   enhancements requested by the stakeholders            can we retitle the staff form from “supervisor surveys for employee ssprs” to “onboarding surveys for new employees”  and          can we retitle the employee form from “  day employee follow ups” to “employee onboarding survey”           could we also add a note and progress section on the hr employee tracking side   something similar to what you added to the supervisor side would be great           on the   day survey  question    can we move “check all that apply” above the options  see below                  on the   survey  can we edit question   to ask “do you require additional assistance for conducting the employee performance ”    we should have an update on the start date for the onboarding surveys after our meeting    ,0
455782,13132516744.0,IssuesEvent,2020-08-06 19:03:46,LorittaBot/Loritta,https://api.github.com/repos/LorittaBot/Loritta,opened,"Sometimes the member isn't in the guild when trying to configure the server, causing issues",Module: Loritta (Discord) 🎀 Priority: Medium Type: Bug 🐞,"Maybe a better error message should be shown, since this can happen *sometimes*

![image](https://user-images.githubusercontent.com/9496359/89571600-53740980-d7fe-11ea-8dbe-a68dc8738dae.png)
",1.0,"Sometimes the member isn't in the guild when trying to configure the server, causing issues - Maybe a better error message should be shown, since this can happen *sometimes*

![image](https://user-images.githubusercontent.com/9496359/89571600-53740980-d7fe-11ea-8dbe-a68dc8738dae.png)
",0,sometimes the member isn t in the guild when trying to configure the server  causing issues   maybe a better error message should be shown  since this can happen  sometimes           ,0
197771,22606137303.0,IssuesEvent,2022-06-29 13:25:18,crouchr/learnage,https://api.github.com/repos/crouchr/learnage,closed,CVE-2015-2222 (Medium) detected in multiple libraries - autoclosed,security vulnerability,"## CVE-2015-2222 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>clamavclamav-0.88</b>, <b>clamavclamav-0.88.6</b>, <b>switchfinblackfin-linux-dist-2011R1-RC3</b>, <b>clamav-develclamav-0.97</b>, <b>clamav-develclamav-0.84</b>, <b>clamav-develclamav-0.90.1</b>, <b>clamav-develclamav-0.98.4</b></p></summary>
<p>


</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
ClamAV before 0.98.7 allows remote attackers to cause a denial of service (crash) via a crafted petite packed file.

<p>Publish Date: 2015-05-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-2222>CVE-2015-2222</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2222"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2222</a></p>
<p>Release Date: 2015-05-12</p>
<p>Fix Resolution: 0.97</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2015-2222 (Medium) detected in multiple libraries - autoclosed - ## CVE-2015-2222 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>clamavclamav-0.88</b>, <b>clamavclamav-0.88.6</b>, <b>switchfinblackfin-linux-dist-2011R1-RC3</b>, <b>clamav-develclamav-0.97</b>, <b>clamav-develclamav-0.84</b>, <b>clamav-develclamav-0.90.1</b>, <b>clamav-develclamav-0.98.4</b></p></summary>
<p>


</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
ClamAV before 0.98.7 allows remote attackers to cause a denial of service (crash) via a crafted petite packed file.

<p>Publish Date: 2015-05-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-2222>CVE-2015-2222</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2222"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2222</a></p>
<p>Release Date: 2015-05-12</p>
<p>Fix Resolution: 0.97</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      medium  detected in multiple libraries   autoclosed      cve       medium severity vulnerability     vulnerable libraries    clamavclamav        clamavclamav          switchfinblackfin linux dist        clamav develclamav        clamav develclamav        clamav develclamav          clamav develclamav                         vulnerability details         clamav before       allows remote attackers to cause a denial of service  crash  via a crafted petite packed file    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  low   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                    step up your open source security game with mend    ,0
89742,11275873843.0,IssuesEvent,2020-01-14 21:45:56,neomad-team/neomad.org,https://api.github.com/repos/neomad-team/neomad.org,closed,Article edit meta data,design frontend,"An article has meta data such has a status (draft/published), a slug, a publication date, …
We should find a way to present the editable meta data form within the article page.",1.0,"Article edit meta data - An article has meta data such has a status (draft/published), a slug, a publication date, …
We should find a way to present the editable meta data form within the article page.",0,article edit meta data   an article has meta data such has a status  draft published   a slug  a publication date  …  we should find a way to present the editable meta data form within the article page ,0
31006,5893901807.0,IssuesEvent,2017-05-17 23:31:27,golang/go,https://api.github.com/repos/golang/go,closed,doc: add IntelliJ Go editor guide,DevExp Documentation,"This is a tracking bug for an editor guide on IntelliJ Go, see #20398 .

Create a brief info card based on the template at #20398 and create screencast for a few top features as 1280x640 gifs.

/cc @dlsniper ",1.0,"doc: add IntelliJ Go editor guide - This is a tracking bug for an editor guide on IntelliJ Go, see #20398 .

Create a brief info card based on the template at #20398 and create screencast for a few top features as 1280x640 gifs.

/cc @dlsniper ",1,doc  add intellij go editor guide   this is a tracking bug for an editor guide on intellij go  see         create a brief info card based on the template at    and create screencast for a few top features as   gifs      cc  dlsniper ,1
292385,21965420305.0,IssuesEvent,2022-05-24 19:46:04,golang/go,https://api.github.com/repos/golang/go,closed,builtin: description of close behavior of reading from closed channel is vague,Documentation NeedsFix,"<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What is the URL of the page with the issue?

https://pkg.go.dev/builtin#close

The documentation of the built in close function states explicitly: 

```
The form

x, ok := <-c
will also set ok to false for a closed channel.
```

This comes after the sentence that states after every item has been read from the channel, but it does not seem clear to me that applies to this statement as well.

When reading from a closed channel that has unread elements in it. It seems intuitive that the behavior that currently exists should be the actual behavior of the language ie. reading from the channel should read all of the available elements, but the documentation currently suggests that is not the case and should be amended.

Wrote a small unit test:

```
func TestReadClosedChannel(t *testing.T) {
	c := make(chan struct{}, 1)

	c <- struct{}{}
	close(c)

	_, ok := <-c
	assert.True(t, ok)
}
```

It seems that this was always the intention of the language to work this way, so this issue is just to ask that the documentation be made a little more clear for the close function.
",1.0,"builtin: description of close behavior of reading from closed channel is vague - <!--
Please answer these questions before submitting your issue. Thanks!
-->

### What is the URL of the page with the issue?

https://pkg.go.dev/builtin#close

The documentation of the built in close function states explicitly: 

```
The form

x, ok := <-c
will also set ok to false for a closed channel.
```

This comes after the sentence that states after every item has been read from the channel, but it does not seem clear to me that applies to this statement as well.

When reading from a closed channel that has unread elements in it. It seems intuitive that the behavior that currently exists should be the actual behavior of the language ie. reading from the channel should read all of the available elements, but the documentation currently suggests that is not the case and should be amended.

Wrote a small unit test:

```
func TestReadClosedChannel(t *testing.T) {
	c := make(chan struct{}, 1)

	c <- struct{}{}
	close(c)

	_, ok := <-c
	assert.True(t, ok)
}
```

It seems that this was always the intention of the language to work this way, so this issue is just to ask that the documentation be made a little more clear for the close function.
",1,builtin  description of close behavior of reading from closed channel is vague         please answer these questions before submitting your issue  thanks              what is the url of the page with the issue          the documentation of the built in close function states explicitly           the form    x  ok      c  will also set ok to false for a closed channel          this comes after the sentence that states after every item has been read from the channel  but it does not seem clear to me that applies to this statement as well     when reading from a closed channel that has unread elements in it  it seems intuitive that the behavior that currently exists should be the actual behavior of the language ie  reading from the channel should read all of the available elements  but the documentation currently suggests that is not the case and should be amended     wrote a small unit test          func testreadclosedchannel t  testing t     	c    make chan struct          	c    struct      	close c     	   ok      c  	assert true t  ok             it seems that this was always the intention of the language to work this way  so this issue is just to ask that the documentation be made a little more clear for the close function   ,1
59289,8356255540.0,IssuesEvent,2018-10-02 17:57:17,golang/go,https://api.github.com/repos/golang/go,closed,regexp: document that FindReaderIndex reads past the match in some cases,Documentation NeedsFix help wanted,"### What did you do?
https://play.golang.org/p/aKIosxo6aP
```
func main() {
	br := bytes.NewReader([]byte(""abaab""))
	re := regexp.MustCompile(""a"")
	for i:=0;;i++{
		q := re.FindReaderIndex(br)
		fmt.Printf(""step %d q=%v\n"",i,q)
		if q==nil{
			break
		}
	}
}

```

### What did you expect to see?
```
step 0 q=[0 1]
step 1 q=[1 2]
step 2 q=[0 1]
```

### What did you see instead?
```
step 0 q=[0 1]
step 1 q=[]
```

I remember reading somewhere in the godoc that the readers can eat the underlying runes to an arbitrarily degree, but it's not clear from the documentation for FindReaderIndex that this is possible. 

```
func (re *Regexp) FindReaderIndex(r io.RuneReader) (loc []int)
    FindReaderIndex returns a two-element slice of integers defining the
    location of the leftmost match of the regular expression in text read from
    the RuneReader. The match text was found in the input stream at byte offset
    loc[0] through loc[1]-1. A return value of nil indicates no match.
```

### Workaround
I had to manually rewind the reader. This solution was not obvious at first, maybe a short addendum to the package function will clarify that it the function may skip matches.

https://play.golang.org/p/J9ubm_43wW
",1.0,"regexp: document that FindReaderIndex reads past the match in some cases - ### What did you do?
https://play.golang.org/p/aKIosxo6aP
```
func main() {
	br := bytes.NewReader([]byte(""abaab""))
	re := regexp.MustCompile(""a"")
	for i:=0;;i++{
		q := re.FindReaderIndex(br)
		fmt.Printf(""step %d q=%v\n"",i,q)
		if q==nil{
			break
		}
	}
}

```

### What did you expect to see?
```
step 0 q=[0 1]
step 1 q=[1 2]
step 2 q=[0 1]
```

### What did you see instead?
```
step 0 q=[0 1]
step 1 q=[]
```

I remember reading somewhere in the godoc that the readers can eat the underlying runes to an arbitrarily degree, but it's not clear from the documentation for FindReaderIndex that this is possible. 

```
func (re *Regexp) FindReaderIndex(r io.RuneReader) (loc []int)
    FindReaderIndex returns a two-element slice of integers defining the
    location of the leftmost match of the regular expression in text read from
    the RuneReader. The match text was found in the input stream at byte offset
    loc[0] through loc[1]-1. A return value of nil indicates no match.
```

### Workaround
I had to manually rewind the reader. This solution was not obvious at first, maybe a short addendum to the package function will clarify that it the function may skip matches.

https://play.golang.org/p/J9ubm_43wW
",1,regexp  document that findreaderindex reads past the match in some cases       what did you do           func main      	br    bytes newreader  byte  abaab     	re    regexp mustcompile  a    	for i     i     		q    re findreaderindex br   		fmt printf  step  d q  v n  i q   		if q  nil   			break  		   	                   what did you expect to see        step   q    step   q    step   q               what did you see instead        step   q    step   q           i remember reading somewhere in the godoc that the readers can eat the underlying runes to an arbitrarily degree  but it s not clear from the documentation for findreaderindex that this is possible           func  re  regexp  findreaderindex r io runereader   loc  int       findreaderindex returns a two element slice of integers defining the      location of the leftmost match of the regular expression in text read from      the runereader  the match text was found in the input stream at byte offset      loc  through loc     a return value of nil indicates no match              workaround  i had to manually rewind the reader  this solution was not obvious at first  maybe a short addendum to the package function will clarify that it the function may skip matches        ,1
310332,9488721333.0,IssuesEvent,2019-04-22 20:21:22,yamovie/client,https://api.github.com/repos/yamovie/client,opened,Redesign movie list component,feature front end priority 1 - high,"More Twitter-like style with movie list cards being wider/bigger and actually showing information, as opposed to just a grid of posters",1.0,"Redesign movie list component - More Twitter-like style with movie list cards being wider/bigger and actually showing information, as opposed to just a grid of posters",0,redesign movie list component   more twitter like style with movie list cards being wider bigger and actually showing information  as opposed to just a grid of posters,0
423981,29040800028.0,IssuesEvent,2023-05-13 00:23:25,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go/internal/modindex: index_format.txt is out of date,Documentation NeedsFix GoCommand,"As of Apr 2023 (87272bd1a18666ec38ac44c63e11c739f3054056), [`cmd/go/internal/modindex/index_format.go`](https://github.com/golang/go/blob/87272bd1a18666ec38ac44c63e11c739f3054056/src/cmd/go/internal/modindex/index_format.txt) describes `""go index v0""`.

But the index format was updated to `""go index v1""` in 7510e597def68cee77e8ba280fc0f04d3cfd2a22 and `""go index v2""` in bd8ec78b08ead1fb34ec8dc7bc4bf2ff7a9e8b82",1.0,"cmd/go/internal/modindex: index_format.txt is out of date - As of Apr 2023 (87272bd1a18666ec38ac44c63e11c739f3054056), [`cmd/go/internal/modindex/index_format.go`](https://github.com/golang/go/blob/87272bd1a18666ec38ac44c63e11c739f3054056/src/cmd/go/internal/modindex/index_format.txt) describes `""go index v0""`.

But the index format was updated to `""go index v1""` in 7510e597def68cee77e8ba280fc0f04d3cfd2a22 and `""go index v2""` in bd8ec78b08ead1fb34ec8dc7bc4bf2ff7a9e8b82",1,cmd go internal modindex  index format txt is out of date   as of apr            describes   go index         but the index format was updated to   go index     in   and   go index     in  ,1
678,2974415352.0,IssuesEvent,2015-07-15 00:23:00,nsaid-team/gotopaws,https://api.github.com/repos/nsaid-team/gotopaws,closed,Links for About Page still missing,enhancement requirement,"      a link to the Apiary API
           a link to the GitHub Issue Tracker
                    a link to the GitHub Repo
                    a link to the GitHub Wiki
                    data:
                    links to the data sources
                    description of how each was scraped
",1.0,"Links for About Page still missing -       a link to the Apiary API
           a link to the GitHub Issue Tracker
                    a link to the GitHub Repo
                    a link to the GitHub Wiki
                    data:
                    links to the data sources
                    description of how each was scraped
",0,links for about page still missing         a link to the apiary api             a link to the github issue tracker                      a link to the github repo                      a link to the github wiki                      data                       links to the data sources                      description of how each was scraped  ,0
47882,7359096522.0,IssuesEvent,2018-03-10 02:02:30,golang/go,https://api.github.com/repos/golang/go,closed,text/scanner: add examples,Documentation help wanted,"I recently worked with the text/scanner package and, although the documentation was straight forward, it could stand to use more [examples](https://golang.org/pkg/text/scanner/#pkg-examples).

I've been looking for opportunities to contribute to Go and I wouldn't mind working on improving the examples of the text/scanner package.  I would like to add examples detailing the use of white space modifiers and tokens, as well as the various scanner and position methods.  I would keep each example succinct, of course.

Are there particular guidelines to follow when it comes to examples?",1.0,"text/scanner: add examples - I recently worked with the text/scanner package and, although the documentation was straight forward, it could stand to use more [examples](https://golang.org/pkg/text/scanner/#pkg-examples).

I've been looking for opportunities to contribute to Go and I wouldn't mind working on improving the examples of the text/scanner package.  I would like to add examples detailing the use of white space modifiers and tokens, as well as the various scanner and position methods.  I would keep each example succinct, of course.

Are there particular guidelines to follow when it comes to examples?",1,text scanner  add examples   i recently worked with the text scanner package and  although the documentation was straight forward  it could stand to use more        i ve been looking for opportunities to contribute to go and i wouldn t mind working on improving the examples of the text scanner package   i would like to add examples detailing the use of white space modifiers and tokens  as well as the various scanner and position methods   i would keep each example succinct  of course     are there particular guidelines to follow when it comes to examples ,1
289150,31931221026.0,IssuesEvent,2023-09-19 07:34:04,Trinadh465/linux-4.1.15_CVE-2023-4128,https://api.github.com/repos/Trinadh465/linux-4.1.15_CVE-2023-4128,opened,CVE-2020-27675 (Medium) detected in linux-stable-rtv4.1.33,Mend: dependency security vulnerability,"## CVE-2020-27675 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>

<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Trinadh465/linux-4.1.15_CVE-2023-4128/commit/0c6c8d8c809f697cd5fc581c6c08e9ad646c55a8"">0c6c8d8c809f697cd5fc581c6c08e9ad646c55a8</a></p>

<p>Found in base branch: <b>main</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/xen/events/events_base.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/xen/events/events_base.c</b>
</p>
</details>
<p></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>  
  
An issue was discovered in the Linux kernel through 5.9.1, as used with Xen through 4.14.x. drivers/xen/events/events_base.c allows event-channel removal during the event-handling loop (a race condition). This can cause a use-after-free or NULL pointer dereference, as demonstrated by a dom0 crash via events for an in-reconfiguration paravirtualized device, aka CID-073d0552ead5.

<p>Publish Date: 2020-10-22
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-27675>CVE-2020-27675</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>4.7</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: High
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2020-27675"">https://nvd.nist.gov/vuln/detail/CVE-2020-27675</a></p>
<p>Release Date: 2020-10-22</p>
<p>Fix Resolution: linux-libc-headers - 5.10;linux-yocto - 4.8.26+gitAUTOINC+1c60e003c7_27efc3ba68,5.4.20+gitAUTOINC+c11911d4d1_f4d7dbafb1</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2020-27675 (Medium) detected in linux-stable-rtv4.1.33 - ## CVE-2020-27675 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>

<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Trinadh465/linux-4.1.15_CVE-2023-4128/commit/0c6c8d8c809f697cd5fc581c6c08e9ad646c55a8"">0c6c8d8c809f697cd5fc581c6c08e9ad646c55a8</a></p>

<p>Found in base branch: <b>main</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/xen/events/events_base.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/xen/events/events_base.c</b>
</p>
</details>
<p></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>  
  
An issue was discovered in the Linux kernel through 5.9.1, as used with Xen through 4.14.x. drivers/xen/events/events_base.c allows event-channel removal during the event-handling loop (a race condition). This can cause a use-after-free or NULL pointer dereference, as demonstrated by a dom0 crash via events for an in-reconfiguration paravirtualized device, aka CID-073d0552ead5.

<p>Publish Date: 2020-10-22
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-27675>CVE-2020-27675</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>4.7</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: High
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2020-27675"">https://nvd.nist.gov/vuln/detail/CVE-2020-27675</a></p>
<p>Release Date: 2020-10-22</p>
<p>Fix Resolution: linux-libc-headers - 5.10;linux-yocto - 4.8.26+gitAUTOINC+1c60e003c7_27efc3ba68,5.4.20+gitAUTOINC+c11911d4d1_f4d7dbafb1</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      medium  detected in linux stable            cve       medium severity vulnerability     vulnerable library    linux stable              julia cartwright s fork of linux stable rt git   library home page   a href    found in head commit   a href      found in base branch   main             vulnerable source files                  drivers xen events events base c        drivers xen events events base c                    vulnerability details         an issue was discovered in the linux kernel through        as used with xen through     x  drivers xen events events base c allows event channel removal during the event handling loop  a race condition   this can cause a use after free or null pointer dereference  as demonstrated by a   crash via events for an in reconfiguration paravirtualized device  aka cid      publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  local     attack complexity  high     privileges required  low     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  linux libc headers       linux yocto         gitautoinc           gitautoinc                   step up your open source security game with mend    ,0
114731,9753401466.0,IssuesEvent,2019-06-04 09:03:23,spacemeshos/go-spacemesh,https://api.github.com/repos/spacemeshos/go-spacemesh,closed,create query for test run when test ends,automation tests,"# Overview / Motivation

we want developers to easily access logs from their test run when the test ends.

# The Task

The tests themselves are run in a certain namespace and deployment id. we can use this to automatically create a query that returns all the test's relevant logs. the option to run this query and collect the logs locally should be set by config or cli param

# Implementation Notes
TODO: Add links to relevant resources, specs, related issues, etc...

# Contribution Guidelines
Important: Issue assignment to developers will be by the order of their application and proficiency level according to the tasks complexity. We will not assign tasks to developers who have'nt introduced themselves on our Gitter [dev channel](https://gitter.im/spacemesh-os/Lobby)

1. Introduce yourself on go-spacemesh [dev chat channel](https://gitter.im/spacemesh-os/Lobby) - ask our team any question you may have about this task
2. Fork branch `develop` to your own repo and work in your repo
3. You must document all methods, enums and types with [godoc comments](https://blog.golang.org/godoc-documenting-go-code)
4. You must write go unit tests for all types and methods when submitting a component, and integration tests if you submit a feature
5. When ready for code review, submit a PR from your repo back to branch `develop`
6. Attach relevant issue to PR
",1.0,"create query for test run when test ends - # Overview / Motivation

we want developers to easily access logs from their test run when the test ends.

# The Task

The tests themselves are run in a certain namespace and deployment id. we can use this to automatically create a query that returns all the test's relevant logs. the option to run this query and collect the logs locally should be set by config or cli param

# Implementation Notes
TODO: Add links to relevant resources, specs, related issues, etc...

# Contribution Guidelines
Important: Issue assignment to developers will be by the order of their application and proficiency level according to the tasks complexity. We will not assign tasks to developers who have'nt introduced themselves on our Gitter [dev channel](https://gitter.im/spacemesh-os/Lobby)

1. Introduce yourself on go-spacemesh [dev chat channel](https://gitter.im/spacemesh-os/Lobby) - ask our team any question you may have about this task
2. Fork branch `develop` to your own repo and work in your repo
3. You must document all methods, enums and types with [godoc comments](https://blog.golang.org/godoc-documenting-go-code)
4. You must write go unit tests for all types and methods when submitting a component, and integration tests if you submit a feature
5. When ready for code review, submit a PR from your repo back to branch `develop`
6. Attach relevant issue to PR
",0,create query for test run when test ends     overview   motivation    we want developers to easily access logs from their test run when the test ends       the task    the tests themselves are run in a certain namespace and deployment id  we can use this to automatically create a query that returns all the test s relevant logs  the option to run this query and collect the logs locally should be set by config or cli param      implementation notes  todo  add links to relevant resources  specs  related issues  etc         contribution guidelines  important  issue assignment to developers will be by the order of their application and proficiency level according to the tasks complexity  we will not assign tasks to developers who have nt introduced themselves on our gitter           introduce yourself on go spacemesh       ask our team any question you may have about this task     fork branch  develop  to your own repo and work in your repo     you must document all methods  enums and types with         you must write go unit tests for all types and methods when submitting a component  and integration tests if you submit a feature     when ready for code review  submit a pr from your repo back to branch  develop      attach relevant issue to pr  ,0
237686,18167765197.0,IssuesEvent,2021-09-27 16:17:36,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: remove references to 'go help fuzz',Documentation NeedsFix GoCommand fuzz,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?
tip

<pre>
$ go version
go version devel go1.18-8854368cb0 Sat Sep 25 01:24:46 2021 +0000 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
I did not check for the release, but the tip of `master` branch [as of 25-Sep-2021]



### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary> <br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/mfrw/.cache/go-build""
GOENV=""/home/mfrw/.config/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/mfrw/g/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/mfrw/g""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/home/mfrw/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/home/mfrw/go/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""devel go1.18-8854368cb0 Sat Sep 25 01:24:46 2021 +0000""
GCCGO=""gccgo""
GOAMD64=""v1""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/mfrw/go/src/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build6268976=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->
`go help fuzz`



### What did you expect to see?

Help about fuzzing.

### What did you see instead?
go help fuzz: unknown help topic. Run 'go help'.


Although:

git branch --contains [2212a1a339c7ac72ff2133855c97ae097444cb5c](https://go-review.googlesource.com/c/go/+/317973)
has `master`

Maybe I am missing something trivial :(

Apologies in advance if its known already or if its by design.",1.0,"cmd/go: remove references to 'go help fuzz' - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?
tip

<pre>
$ go version
go version devel go1.18-8854368cb0 Sat Sep 25 01:24:46 2021 +0000 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
I did not check for the release, but the tip of `master` branch [as of 25-Sep-2021]



### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary> <br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/mfrw/.cache/go-build""
GOENV=""/home/mfrw/.config/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/mfrw/g/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/mfrw/g""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/home/mfrw/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/home/mfrw/go/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""devel go1.18-8854368cb0 Sat Sep 25 01:24:46 2021 +0000""
GCCGO=""gccgo""
GOAMD64=""v1""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/mfrw/go/src/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build6268976=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->
`go help fuzz`



### What did you expect to see?

Help about fuzzing.

### What did you see instead?
go help fuzz: unknown help topic. Run 'go help'.


Although:

git branch --contains [2212a1a339c7ac72ff2133855c97ae097444cb5c](https://go-review.googlesource.com/c/go/+/317973)
has `master`

Maybe I am missing something trivial :(

Apologies in advance if its known already or if its by design.",1,cmd go  remove references to  go help fuzz          please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version     tip         go version  go version devel       sat sep              linux             does this issue reproduce with the latest release   i did not check for the release  but the tip of  master  branch              what operating system and processor architecture are you using   go env          go env  output        go env        goarch      gobin     gocache   home mfrw  cache go build   goenv   home mfrw  config go env   goexe     goexperiment     goflags     gohostarch      gohostos  linux   goinsecure     gomodcache   home mfrw g pkg mod   gonoproxy     gonosumdb     goos  linux   gopath   home mfrw g   goprivate     goproxy     goroot   home mfrw go   gosumdb  sum golang org   gotmpdir     gotooldir   home mfrw go pkg tool linux     govcs     goversion  devel       sat sep                gccgo  gccgo          ar  ar   cc  gcc   cxx  g     cgo enabled      gomod   home mfrw go src go mod   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches             what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best         go help fuzz             what did you expect to see     help about fuzzing         what did you see instead   go help fuzz  unknown help topic  run  go help        although     git branch   contains      has  master     maybe i am missing something trivial       apologies in advance if its known already or if its by design ,1
260971,8221750974.0,IssuesEvent,2018-09-06 03:49:37,hack4impact-uiuc/h4i-recruitment,https://api.github.com/repos/hack4impact-uiuc/h4i-recruitment,closed,"FaceMash should only match candidates that aren't ""Rejected""",Priority: Critical,"We may need to filter through candidates even before facemash starts. If they have the status ""Rejected"", they shouldn't be part of the match. ",1.0,"FaceMash should only match candidates that aren't ""Rejected"" - We may need to filter through candidates even before facemash starts. If they have the status ""Rejected"", they shouldn't be part of the match. ",0,facemash should only match candidates that aren t  rejected    we may need to filter through candidates even before facemash starts  if they have the status  rejected   they shouldn t be part of the match  ,0
25921,19424947032.0,IssuesEvent,2021-12-21 03:20:48,odrusso/eduace,https://api.github.com/repos/odrusso/eduace,closed,Replace hard-coded S3 bucket with env variable/dynamic call,Infrastructure,"See /infra/scripts/deploy-python-to-s3.py
Value of S3 bucket is a CFN output, can see in the console or in the GA InfraCI output ",1.0,"Replace hard-coded S3 bucket with env variable/dynamic call - See /infra/scripts/deploy-python-to-s3.py
Value of S3 bucket is a CFN output, can see in the console or in the GA InfraCI output ",0,replace hard coded   bucket with env variable dynamic call   see  infra scripts deploy python to   py  value of   bucket is a cfn output  can see in the console or in the ga infraci output ,0
810302,30235481405.0,IssuesEvent,2023-07-06 09:54:51,nacht-falter/aikido-course-website-django,https://api.github.com/repos/nacht-falter/aikido-course-website-django,closed,USER STORY: Course Registration for logged-in users,EPIC: Course Registration THEME: Course Registration and Management PRIORITY: Must-Have SIZE: L,"As a **logged-in user**, I can **fill out a sign-up form** to **sign up for a course**.

### Acceptance Criteria
- [x] A logged-in user can click on a link in the course with open registration status and will be directed to to a registration form.
- [x] The registration-form provides fields for all necessary details.
- [x] Upon filling out the form, a new registration will be stored in the database.

### Tasks
- [x] Create course registration form
- [x] Create registration form template
- [x] Create view
- [x] Register url
- [x] Write tests for form and view

",1.0,"USER STORY: Course Registration for logged-in users - As a **logged-in user**, I can **fill out a sign-up form** to **sign up for a course**.

### Acceptance Criteria
- [x] A logged-in user can click on a link in the course with open registration status and will be directed to to a registration form.
- [x] The registration-form provides fields for all necessary details.
- [x] Upon filling out the form, a new registration will be stored in the database.

### Tasks
- [x] Create course registration form
- [x] Create registration form template
- [x] Create view
- [x] Register url
- [x] Write tests for form and view

",0,user story  course registration for logged in users   as a   logged in user    i can   fill out a sign up form   to   sign up for a course         acceptance criteria     a logged in user can click on a link in the course with open registration status and will be directed to to a registration form      the registration form provides fields for all necessary details      upon filling out the form  a new registration will be stored in the database       tasks     create course registration form     create registration form template     create view     register url     write tests for form and view  ,0
4655,24096938338.0,IssuesEvent,2022-09-19 19:39:04,aws/aws-sam-cli,https://api.github.com/repos/aws/aws-sam-cli,closed,Bug: How to use --use-container for sam sync (because local python is not same as runtime),type/feature stage/waiting-for-release area/sync maintainer/need-followup,"I was able to build using --use-container so i dont have to bother about the local python version.

But while syncing it creates problem
```
$ sam sync --debug --stack-name santhosh-testing              
2022-06-30 12:35:13,556 | Telemetry endpoint configured to be https://aws-serverless-tools-telemetry.us-west-2.amazonaws.com/metrics
2022-06-30 12:35:13,563 | Telemetry endpoint configured to be https://aws-serverless-tools-telemetry.us-west-2.amazonaws.com/metrics
2022-06-30 12:35:13,564 | Sending Telemetry: {'metrics': [{'templateWarning': {'requestId': '5b6c9cb7-e4a9-4c00-84c5-952ce7f5f5ab', 'installationId': 'a87120b0-ef01-4fa9-a2b4-d881501b50fc', 'sessionId': 'fb48edde-cf6e-46ea-8ac2-31688d6f3178', 'executionEnvironment': 'CLI', 'ci': False, 'pyversion': '3.7.10', 'samcliVersion': '1.40.0', 'awsProfileProvided': True, 'debugFlagProvided': True, 'region': '', 'warningName': 'CodeDeployWarning', 'warningCount': 0}}]}
2022-06-30 12:35:14,839 | HTTPSConnectionPool(host='aws-serverless-tools-telemetry.us-west-2.amazonaws.com', port=443): Read timed out. (read timeout=0.1)
2022-06-30 12:35:14,839 | Sending Telemetry: {'metrics': [{'templateWarning': {'requestId': '984e898d-8839-4b3d-8b0e-db500562c47c', 'installationId': 'a87120b0-ef01-4fa9-a2b4-d881501b50fc', 'sessionId': 'fb48edde-cf6e-46ea-8ac2-31688d6f3178', 'executionEnvironment': 'CLI', 'ci': False, 'pyversion': '3.7.10', 'samcliVersion': '1.40.0', 'awsProfileProvided': True, 'debugFlagProvided': True, 'region': '', 'warningName': 'CodeDeployConditionWarning', 'warningCount': 0}}]}
2022-06-30 12:35:16,040 | HTTPSConnectionPool(host='aws-serverless-tools-telemetry.us-west-2.amazonaws.com', port=443): Read timed out. (read timeout=0.1)
2022-06-30 12:35:16,040 | Using config file: samconfig.toml, config environment: default
2022-06-30 12:35:16,040 | Expand command line arguments to:
2022-06-30 12:35:16,041 | --template_file=/home/simha_personal_data/programming_arch_firefox/extra/Unsorted/vid/web_dev/hss_iqgateway/aws_sam/sam-app/template.yaml --stack_name=santhosh-testing --dependency_layer --capabilities=('CAPABILITY_NAMED_IAM', 'CAPABILITY_AUTO_EXPAND') 

		Managed S3 bucket: aws-sam-cli-managed-default-samclisourcebucket-1cqyp2bwbvv8u

		Default capabilities applied: ('CAPABILITY_NAMED_IAM', 'CAPABILITY_AUTO_EXPAND')
To override with customized capabilities, use --capabilities flag or set it in samconfig.toml
2022-06-30 12:35:17,944 | Using build directory as .aws-sam/auto-dependency-layer
2022-06-30 12:35:17,945 | Using build directory as .aws-sam/auto-dependency-layer

This feature is currently in beta. Visit the docs page to learn more about the AWS Beta terms https://aws.amazon.com/service-terms/.

The SAM CLI will use the AWS Lambda, Amazon API Gateway, and AWS StepFunctions APIs to upload your code without 
performing a CloudFormation deployment. This will cause drift in your CloudFormation stack. 
**The sync command should only be used against a development stack**.

Confirm that you are synchronizing a development stack and want to turn on beta features.

Enter Y to proceed with the command, or enter N to cancel:
 [y/N]: Y
2022-06-30 12:35:22,217 | 
Experimental features are enabled for this session.
Visit the docs page to learn more about the AWS Beta terms https://aws.amazon.com/service-terms/.

2022-06-30 12:35:22,225 | No Parameters detected in the template
2022-06-30 12:35:22,249 | There is no customer defined id or cdk path defined for resource HelloWorldFunction, so we will use the resource logical id as the resource id
2022-06-30 12:35:22,249 | There is no customer defined id or cdk path defined for resource ServerlessRestApi, so we will use the resource logical id as the resource id
2022-06-30 12:35:22,251 | 2 stacks found in the template
2022-06-30 12:35:22,251 | No Parameters detected in the template
2022-06-30 12:35:22,268 | There is no customer defined id or cdk path defined for resource HelloWorldFunction, so we will use the resource logical id as the resource id
2022-06-30 12:35:22,268 | There is no customer defined id or cdk path defined for resource ServerlessRestApi, so we will use the resource logical id as the resource id
2022-06-30 12:35:22,269 | 2 resources found in the stack 
2022-06-30 12:35:22,269 | No Parameters detected in the template
2022-06-30 12:35:22,289 | There is no customer defined id or cdk path defined for resource HelloWorldFunction, so we will use the resource logical id as the resource id
2022-06-30 12:35:22,290 | There is no customer defined id or cdk path defined for resource ServerlessRestApi, so we will use the resource logical id as the resource id
2022-06-30 12:35:22,290 | Found Serverless function with name='HelloWorldFunction' and CodeUri='hello_world/'
2022-06-30 12:35:22,290 | --base-dir is not presented, adjusting uri hello_world/ relative to /home/simha_personal_data/programming_arch_firefox/extra/Unsorted/vid/web_dev/hss_iqgateway/aws_sam/sam-app/template.yaml
2022-06-30 12:35:22,290 | No Parameters detected in the template
2022-06-30 12:35:22,307 | There is no customer defined id or cdk path defined for resource HelloWorldFunction, so we will use the resource logical id as the resource id
2022-06-30 12:35:22,307 | There is no customer defined id or cdk path defined for resource ServerlessRestApi, so we will use the resource logical id as the resource id
2022-06-30 12:35:22,309 | Executing the build using build context.
2022-06-30 12:35:22,319 | No Parameters detected in the template
2022-06-30 12:35:22,344 | There is no customer defined id or cdk path defined for resource HelloWorldFunction, so we will use the resource logical id as the resource id
2022-06-30 12:35:22,344 | There is no customer defined id or cdk path defined for resource ServerlessRestApi, so we will use the resource logical id as the resource id
2022-06-30 12:35:22,345 | Your template contains a resource with logical ID ""ServerlessRestApi"", which is a reserved logical ID in AWS SAM. It could result in unexpected behaviors and is not recommended.
2022-06-30 12:35:22,346 | Instantiating build definitions
2022-06-30 12:35:22,351 | Same function build definition found, adding function (Previous: BuildDefinition(python3.7, /home/simha_personal_data/programming_arch_firefox/extra/Unsorted/vid/web_dev/hss_iqgateway/aws_sam/sam-app/hello_world, Zip, , fb2df3d3-6088-413d-a68d-fef68238b0c7, {}, {}, x86_64, []), Current: BuildDefinition(python3.7, /home/simha_personal_data/programming_arch_firefox/extra/Unsorted/vid/web_dev/hss_iqgateway/aws_sam/sam-app/hello_world, Zip, , 8dd59822-1269-438b-9689-5ab100c44500, {}, {}, x86_64, []), Function: Function(function_id='HelloWorldFunction', name='HelloWorldFunction', functionname='HelloWorldFunction', runtime='python3.7', memory=None, timeout=500, handler='app.lambda_handler', imageuri=None, packagetype='Zip', imageconfig=None, codeuri='/home/simha_personal_data/programming_arch_firefox/extra/Unsorted/vid/web_dev/hss_iqgateway/aws_sam/sam-app/hello_world', environment=None, rolearn=None, layers=[], events={'HelloWorld': {'Type': 'Api', 'Properties': {'Path': '/copy_files', 'Method': 'post', 'RestApiId': 'ServerlessRestApi'}}}, metadata={'SamResourceId': 'HelloWorldFunction'}, inlinecode=None, codesign_config_arn=None, architectures=['x86_64'], stack_path=''))
2022-06-30 12:35:22,353 | Async execution started
2022-06-30 12:35:22,353 | Invoking function functools.partial(<bound method CachedOrIncrementalBuildStrategyWrapper.build_single_function_definition of <samcli.lib.build.build_strategy.CachedOrIncrementalBuildStrategyWrapper object at 0x7fd85f7e9210>>, <samcli.lib.build.build_graph.FunctionBuildDefinition object at 0x7fd85f7fab10>)
2022-06-30 12:35:22,353 | Running incremental build for runtime python3.7 for build definition fb2df3d3-6088-413d-a68d-fef68238b0c7
2022-06-30 12:35:22,353 | Waiting for async results
2022-06-30 12:35:22,354 | Manifest file is changed (new hash: 523939fbec58410a5ca9b187c33945d0) or dependency folder (.aws-sam/deps/fb2df3d3-6088-413d-a68d-fef68238b0c7) is missing for fb2df3d3-6088-413d-a68d-fef68238b0c7, downloading dependencies and copying/building source
2022-06-30 12:35:22,354 | Building codeuri: /home/simha_personal_data/programming_arch_firefox/extra/Unsorted/vid/web_dev/hss_iqgateway/aws_sam/sam-app/hello_world runtime: python3.7 metadata: {} architecture: x86_64 functions: ['HelloWorldFunction']
2022-06-30 12:35:22,354 | Building to following folder /home/simha_personal_data/programming_arch_firefox/extra/Unsorted/vid/web_dev/hss_iqgateway/aws_sam/sam-app/.aws-sam/auto-dependency-layer/HelloWorldFunction
2022-06-30 12:35:22,355 | Loading workflow module 'aws_lambda_builders.workflows'
2022-06-30 12:35:22,358 | Registering workflow 'PythonPipBuilder' with capability 'Capability(language='python', dependency_manager='pip', application_framework=None)'
2022-06-30 12:35:22,359 | Registering workflow 'NodejsNpmBuilder' with capability 'Capability(language='nodejs', dependency_manager='npm', application_framework=None)'
2022-06-30 12:35:22,362 | Registering workflow 'RubyBundlerBuilder' with capability 'Capability(language='ruby', dependency_manager='bundler', application_framework=None)'
2022-06-30 12:35:22,363 | Registering workflow 'GoDepBuilder' with capability 'Capability(language='go', dependency_manager='dep', application_framework=None)'
2022-06-30 12:35:22,365 | Registering workflow 'GoModulesBuilder' with capability 'Capability(language='go', dependency_manager='modules', application_framework=None)'
2022-06-30 12:35:22,367 | Registering workflow 'JavaGradleWorkflow' with capability 'Capability(language='java', dependency_manager='gradle', application_framework=None)'
2022-06-30 12:35:22,369 | Registering workflow 'JavaMavenWorkflow' with capability 'Capability(language='java', dependency_manager='maven', application_framework=None)'
2022-06-30 12:35:22,370 | Registering workflow 'DotnetCliPackageBuilder' with capability 'Capability(language='dotnet', dependency_manager='cli-package', application_framework=None)'
2022-06-30 12:35:22,371 | Registering workflow 'CustomMakeBuilder' with capability 'Capability(language='provided', dependency_manager=None, application_framework=None)'
2022-06-30 12:35:22,374 | Registering workflow 'NodejsNpmEsbuildBuilder' with capability 'Capability(language='nodejs', dependency_manager='npm-esbuild', application_framework=None)'
2022-06-30 12:35:22,375 | Found workflow 'PythonPipBuilder' to support capabilities 'Capability(language='python', dependency_manager='pip', application_framework=None)'
2022-06-30 12:35:22,439 | Invalid executable for python at /usr/bin/python
Traceback (most recent call last):
  File ""aws_lambda_builders/workflow.py"", line 66, in wrapper
  File ""aws_lambda_builders/workflows/python_pip/validator.py"", line 51, in validate
aws_lambda_builders.exceptions.MisMatchRuntimeError: python executable found in your path does not match runtime. 
 Expected version: python3.7, Found version: /usr/bin/python. 
 Possibly related: https://github.com/awslabs/aws-lambda-builders/issues/30
2022-06-30 12:35:22,490 | Invalid executable for python at /bin/python
Traceback (most recent call last):
  File ""aws_lambda_builders/workflow.py"", line 66, in wrapper
  File ""aws_lambda_builders/workflows/python_pip/validator.py"", line 51, in validate
aws_lambda_builders.exceptions.MisMatchRuntimeError: python executable found in your path does not match runtime. 
 Expected version: python3.7, Found version: /bin/python. 
 Possibly related: https://github.com/awslabs/aws-lambda-builders/issues/30
2022-06-30 12:35:22,491 | Exception raised during the execution

Build Failed
2022-06-30 12:35:22,494 | Sending Telemetry: {'metrics': [{'commandRunExperimental': {'requestId': 'fde47179-0655-4f96-89a7-ebf26da76734', 'installationId': 'a87120b0-ef01-4fa9-a2b4-d881501b50fc', 'sessionId': 'fb48edde-cf6e-46ea-8ac2-31688d6f3178', 'executionEnvironment': 'CLI', 'ci': False, 'pyversion': '3.7.10', 'samcliVersion': '1.40.0', 'awsProfileProvided': True, 'debugFlagProvided': True, 'region': '', 'commandName': 'sam sync', 'metricSpecificAttributes': {'experimentalAccelerate': True, 'experimentalAll': False, 'experimentalEsbuild': False, 'experimentalMavenScopeAndLayer': False, 'projectType': 'CFN'}, 'duration': 8937, 'exitReason': 'WorkflowFailedError', 'exitCode': 1}}]}
2022-06-30 12:35:23,703 | HTTPSConnectionPool(host='aws-serverless-tools-telemetry.us-west-2.amazonaws.com', port=443): Read timed out. (read timeout=0.1)
Error: PythonPipBuilder:Validation - Binary validation failed for python, searched for python in following locations  : ['/usr/bin/python', '/bin/python'] which did not satisfy constraints for runtime: python3.7. Do you have python for runtime: python3.7 on your PATH?
```


Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
OS: Linux
sam --version:
$ sam --version
SAM CLI, version 1.40.0
AWS region:
",True,"Bug: How to use --use-container for sam sync (because local python is not same as runtime) - I was able to build using --use-container so i dont have to bother about the local python version.

But while syncing it creates problem
```
$ sam sync --debug --stack-name santhosh-testing              
2022-06-30 12:35:13,556 | Telemetry endpoint configured to be https://aws-serverless-tools-telemetry.us-west-2.amazonaws.com/metrics
2022-06-30 12:35:13,563 | Telemetry endpoint configured to be https://aws-serverless-tools-telemetry.us-west-2.amazonaws.com/metrics
2022-06-30 12:35:13,564 | Sending Telemetry: {'metrics': [{'templateWarning': {'requestId': '5b6c9cb7-e4a9-4c00-84c5-952ce7f5f5ab', 'installationId': 'a87120b0-ef01-4fa9-a2b4-d881501b50fc', 'sessionId': 'fb48edde-cf6e-46ea-8ac2-31688d6f3178', 'executionEnvironment': 'CLI', 'ci': False, 'pyversion': '3.7.10', 'samcliVersion': '1.40.0', 'awsProfileProvided': True, 'debugFlagProvided': True, 'region': '', 'warningName': 'CodeDeployWarning', 'warningCount': 0}}]}
2022-06-30 12:35:14,839 | HTTPSConnectionPool(host='aws-serverless-tools-telemetry.us-west-2.amazonaws.com', port=443): Read timed out. (read timeout=0.1)
2022-06-30 12:35:14,839 | Sending Telemetry: {'metrics': [{'templateWarning': {'requestId': '984e898d-8839-4b3d-8b0e-db500562c47c', 'installationId': 'a87120b0-ef01-4fa9-a2b4-d881501b50fc', 'sessionId': 'fb48edde-cf6e-46ea-8ac2-31688d6f3178', 'executionEnvironment': 'CLI', 'ci': False, 'pyversion': '3.7.10', 'samcliVersion': '1.40.0', 'awsProfileProvided': True, 'debugFlagProvided': True, 'region': '', 'warningName': 'CodeDeployConditionWarning', 'warningCount': 0}}]}
2022-06-30 12:35:16,040 | HTTPSConnectionPool(host='aws-serverless-tools-telemetry.us-west-2.amazonaws.com', port=443): Read timed out. (read timeout=0.1)
2022-06-30 12:35:16,040 | Using config file: samconfig.toml, config environment: default
2022-06-30 12:35:16,040 | Expand command line arguments to:
2022-06-30 12:35:16,041 | --template_file=/home/simha_personal_data/programming_arch_firefox/extra/Unsorted/vid/web_dev/hss_iqgateway/aws_sam/sam-app/template.yaml --stack_name=santhosh-testing --dependency_layer --capabilities=('CAPABILITY_NAMED_IAM', 'CAPABILITY_AUTO_EXPAND') 

		Managed S3 bucket: aws-sam-cli-managed-default-samclisourcebucket-1cqyp2bwbvv8u

		Default capabilities applied: ('CAPABILITY_NAMED_IAM', 'CAPABILITY_AUTO_EXPAND')
To override with customized capabilities, use --capabilities flag or set it in samconfig.toml
2022-06-30 12:35:17,944 | Using build directory as .aws-sam/auto-dependency-layer
2022-06-30 12:35:17,945 | Using build directory as .aws-sam/auto-dependency-layer

This feature is currently in beta. Visit the docs page to learn more about the AWS Beta terms https://aws.amazon.com/service-terms/.

The SAM CLI will use the AWS Lambda, Amazon API Gateway, and AWS StepFunctions APIs to upload your code without 
performing a CloudFormation deployment. This will cause drift in your CloudFormation stack. 
**The sync command should only be used against a development stack**.

Confirm that you are synchronizing a development stack and want to turn on beta features.

Enter Y to proceed with the command, or enter N to cancel:
 [y/N]: Y
2022-06-30 12:35:22,217 | 
Experimental features are enabled for this session.
Visit the docs page to learn more about the AWS Beta terms https://aws.amazon.com/service-terms/.

2022-06-30 12:35:22,225 | No Parameters detected in the template
2022-06-30 12:35:22,249 | There is no customer defined id or cdk path defined for resource HelloWorldFunction, so we will use the resource logical id as the resource id
2022-06-30 12:35:22,249 | There is no customer defined id or cdk path defined for resource ServerlessRestApi, so we will use the resource logical id as the resource id
2022-06-30 12:35:22,251 | 2 stacks found in the template
2022-06-30 12:35:22,251 | No Parameters detected in the template
2022-06-30 12:35:22,268 | There is no customer defined id or cdk path defined for resource HelloWorldFunction, so we will use the resource logical id as the resource id
2022-06-30 12:35:22,268 | There is no customer defined id or cdk path defined for resource ServerlessRestApi, so we will use the resource logical id as the resource id
2022-06-30 12:35:22,269 | 2 resources found in the stack 
2022-06-30 12:35:22,269 | No Parameters detected in the template
2022-06-30 12:35:22,289 | There is no customer defined id or cdk path defined for resource HelloWorldFunction, so we will use the resource logical id as the resource id
2022-06-30 12:35:22,290 | There is no customer defined id or cdk path defined for resource ServerlessRestApi, so we will use the resource logical id as the resource id
2022-06-30 12:35:22,290 | Found Serverless function with name='HelloWorldFunction' and CodeUri='hello_world/'
2022-06-30 12:35:22,290 | --base-dir is not presented, adjusting uri hello_world/ relative to /home/simha_personal_data/programming_arch_firefox/extra/Unsorted/vid/web_dev/hss_iqgateway/aws_sam/sam-app/template.yaml
2022-06-30 12:35:22,290 | No Parameters detected in the template
2022-06-30 12:35:22,307 | There is no customer defined id or cdk path defined for resource HelloWorldFunction, so we will use the resource logical id as the resource id
2022-06-30 12:35:22,307 | There is no customer defined id or cdk path defined for resource ServerlessRestApi, so we will use the resource logical id as the resource id
2022-06-30 12:35:22,309 | Executing the build using build context.
2022-06-30 12:35:22,319 | No Parameters detected in the template
2022-06-30 12:35:22,344 | There is no customer defined id or cdk path defined for resource HelloWorldFunction, so we will use the resource logical id as the resource id
2022-06-30 12:35:22,344 | There is no customer defined id or cdk path defined for resource ServerlessRestApi, so we will use the resource logical id as the resource id
2022-06-30 12:35:22,345 | Your template contains a resource with logical ID ""ServerlessRestApi"", which is a reserved logical ID in AWS SAM. It could result in unexpected behaviors and is not recommended.
2022-06-30 12:35:22,346 | Instantiating build definitions
2022-06-30 12:35:22,351 | Same function build definition found, adding function (Previous: BuildDefinition(python3.7, /home/simha_personal_data/programming_arch_firefox/extra/Unsorted/vid/web_dev/hss_iqgateway/aws_sam/sam-app/hello_world, Zip, , fb2df3d3-6088-413d-a68d-fef68238b0c7, {}, {}, x86_64, []), Current: BuildDefinition(python3.7, /home/simha_personal_data/programming_arch_firefox/extra/Unsorted/vid/web_dev/hss_iqgateway/aws_sam/sam-app/hello_world, Zip, , 8dd59822-1269-438b-9689-5ab100c44500, {}, {}, x86_64, []), Function: Function(function_id='HelloWorldFunction', name='HelloWorldFunction', functionname='HelloWorldFunction', runtime='python3.7', memory=None, timeout=500, handler='app.lambda_handler', imageuri=None, packagetype='Zip', imageconfig=None, codeuri='/home/simha_personal_data/programming_arch_firefox/extra/Unsorted/vid/web_dev/hss_iqgateway/aws_sam/sam-app/hello_world', environment=None, rolearn=None, layers=[], events={'HelloWorld': {'Type': 'Api', 'Properties': {'Path': '/copy_files', 'Method': 'post', 'RestApiId': 'ServerlessRestApi'}}}, metadata={'SamResourceId': 'HelloWorldFunction'}, inlinecode=None, codesign_config_arn=None, architectures=['x86_64'], stack_path=''))
2022-06-30 12:35:22,353 | Async execution started
2022-06-30 12:35:22,353 | Invoking function functools.partial(<bound method CachedOrIncrementalBuildStrategyWrapper.build_single_function_definition of <samcli.lib.build.build_strategy.CachedOrIncrementalBuildStrategyWrapper object at 0x7fd85f7e9210>>, <samcli.lib.build.build_graph.FunctionBuildDefinition object at 0x7fd85f7fab10>)
2022-06-30 12:35:22,353 | Running incremental build for runtime python3.7 for build definition fb2df3d3-6088-413d-a68d-fef68238b0c7
2022-06-30 12:35:22,353 | Waiting for async results
2022-06-30 12:35:22,354 | Manifest file is changed (new hash: 523939fbec58410a5ca9b187c33945d0) or dependency folder (.aws-sam/deps/fb2df3d3-6088-413d-a68d-fef68238b0c7) is missing for fb2df3d3-6088-413d-a68d-fef68238b0c7, downloading dependencies and copying/building source
2022-06-30 12:35:22,354 | Building codeuri: /home/simha_personal_data/programming_arch_firefox/extra/Unsorted/vid/web_dev/hss_iqgateway/aws_sam/sam-app/hello_world runtime: python3.7 metadata: {} architecture: x86_64 functions: ['HelloWorldFunction']
2022-06-30 12:35:22,354 | Building to following folder /home/simha_personal_data/programming_arch_firefox/extra/Unsorted/vid/web_dev/hss_iqgateway/aws_sam/sam-app/.aws-sam/auto-dependency-layer/HelloWorldFunction
2022-06-30 12:35:22,355 | Loading workflow module 'aws_lambda_builders.workflows'
2022-06-30 12:35:22,358 | Registering workflow 'PythonPipBuilder' with capability 'Capability(language='python', dependency_manager='pip', application_framework=None)'
2022-06-30 12:35:22,359 | Registering workflow 'NodejsNpmBuilder' with capability 'Capability(language='nodejs', dependency_manager='npm', application_framework=None)'
2022-06-30 12:35:22,362 | Registering workflow 'RubyBundlerBuilder' with capability 'Capability(language='ruby', dependency_manager='bundler', application_framework=None)'
2022-06-30 12:35:22,363 | Registering workflow 'GoDepBuilder' with capability 'Capability(language='go', dependency_manager='dep', application_framework=None)'
2022-06-30 12:35:22,365 | Registering workflow 'GoModulesBuilder' with capability 'Capability(language='go', dependency_manager='modules', application_framework=None)'
2022-06-30 12:35:22,367 | Registering workflow 'JavaGradleWorkflow' with capability 'Capability(language='java', dependency_manager='gradle', application_framework=None)'
2022-06-30 12:35:22,369 | Registering workflow 'JavaMavenWorkflow' with capability 'Capability(language='java', dependency_manager='maven', application_framework=None)'
2022-06-30 12:35:22,370 | Registering workflow 'DotnetCliPackageBuilder' with capability 'Capability(language='dotnet', dependency_manager='cli-package', application_framework=None)'
2022-06-30 12:35:22,371 | Registering workflow 'CustomMakeBuilder' with capability 'Capability(language='provided', dependency_manager=None, application_framework=None)'
2022-06-30 12:35:22,374 | Registering workflow 'NodejsNpmEsbuildBuilder' with capability 'Capability(language='nodejs', dependency_manager='npm-esbuild', application_framework=None)'
2022-06-30 12:35:22,375 | Found workflow 'PythonPipBuilder' to support capabilities 'Capability(language='python', dependency_manager='pip', application_framework=None)'
2022-06-30 12:35:22,439 | Invalid executable for python at /usr/bin/python
Traceback (most recent call last):
  File ""aws_lambda_builders/workflow.py"", line 66, in wrapper
  File ""aws_lambda_builders/workflows/python_pip/validator.py"", line 51, in validate
aws_lambda_builders.exceptions.MisMatchRuntimeError: python executable found in your path does not match runtime. 
 Expected version: python3.7, Found version: /usr/bin/python. 
 Possibly related: https://github.com/awslabs/aws-lambda-builders/issues/30
2022-06-30 12:35:22,490 | Invalid executable for python at /bin/python
Traceback (most recent call last):
  File ""aws_lambda_builders/workflow.py"", line 66, in wrapper
  File ""aws_lambda_builders/workflows/python_pip/validator.py"", line 51, in validate
aws_lambda_builders.exceptions.MisMatchRuntimeError: python executable found in your path does not match runtime. 
 Expected version: python3.7, Found version: /bin/python. 
 Possibly related: https://github.com/awslabs/aws-lambda-builders/issues/30
2022-06-30 12:35:22,491 | Exception raised during the execution

Build Failed
2022-06-30 12:35:22,494 | Sending Telemetry: {'metrics': [{'commandRunExperimental': {'requestId': 'fde47179-0655-4f96-89a7-ebf26da76734', 'installationId': 'a87120b0-ef01-4fa9-a2b4-d881501b50fc', 'sessionId': 'fb48edde-cf6e-46ea-8ac2-31688d6f3178', 'executionEnvironment': 'CLI', 'ci': False, 'pyversion': '3.7.10', 'samcliVersion': '1.40.0', 'awsProfileProvided': True, 'debugFlagProvided': True, 'region': '', 'commandName': 'sam sync', 'metricSpecificAttributes': {'experimentalAccelerate': True, 'experimentalAll': False, 'experimentalEsbuild': False, 'experimentalMavenScopeAndLayer': False, 'projectType': 'CFN'}, 'duration': 8937, 'exitReason': 'WorkflowFailedError', 'exitCode': 1}}]}
2022-06-30 12:35:23,703 | HTTPSConnectionPool(host='aws-serverless-tools-telemetry.us-west-2.amazonaws.com', port=443): Read timed out. (read timeout=0.1)
Error: PythonPipBuilder:Validation - Binary validation failed for python, searched for python in following locations  : ['/usr/bin/python', '/bin/python'] which did not satisfy constraints for runtime: python3.7. Do you have python for runtime: python3.7 on your PATH?
```


Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
OS: Linux
sam --version:
$ sam --version
SAM CLI, version 1.40.0
AWS region:
",0,bug  how to use   use container for sam sync  because local python is not same as runtime    i was able to build using   use container so i dont have to bother about the local python version     but while syncing it creates problem         sam sync   debug   stack name santhosh testing                                telemetry endpoint configured to be                    telemetry endpoint configured to be                    sending telemetry    metrics                       httpsconnectionpool host  aws serverless tools telemetry us west   amazonaws com   port     read timed out   read timeout                       sending telemetry    metrics                       httpsconnectionpool host  aws serverless tools telemetry us west   amazonaws com   port     read timed out   read timeout                       using config file  samconfig toml  config environment  default                  expand command line arguments to                     template file  home simha personal data programming arch firefox extra unsorted vid web dev hss iqgateway aws sam sam app template yaml   stack name santhosh testing   dependency layer   capabilities   capability named iam    capability auto expand       		managed   bucket  aws sam cli managed default samclisourcebucket      		default capabilities applied    capability named iam    capability auto expand    to override with customized capabilities  use   capabilities flag or set it in samconfig toml                  using build directory as  aws sam auto dependency layer                  using build directory as  aws sam auto dependency layer    this feature is currently in beta  visit the docs page to learn more about the aws beta terms      the sam cli will use the aws lambda  amazon api gateway  and aws stepfunctions apis to upload your code without   performing a cloudformation deployment  this will cause drift in your cloudformation stack      the sync command should only be used against a development stack       confirm that you are synchronizing a development stack and want to turn on beta features     enter y to proceed with the command  or enter n to cancel       y                    experimental features are enabled for this session   visit the docs page to learn more about the aws beta terms                      no parameters detected in the template                  there is no customer defined id or cdk path defined for resource helloworldfunction  so we will use the resource logical id as the resource id                  there is no customer defined id or cdk path defined for resource serverlessrestapi  so we will use the resource logical id as the resource id                    stacks found in the template                  no parameters detected in the template                  there is no customer defined id or cdk path defined for resource helloworldfunction  so we will use the resource logical id as the resource id                  there is no customer defined id or cdk path defined for resource serverlessrestapi  so we will use the resource logical id as the resource id                    resources found in the stack                   no parameters detected in the template                  there is no customer defined id or cdk path defined for resource helloworldfunction  so we will use the resource logical id as the resource id                  there is no customer defined id or cdk path defined for resource serverlessrestapi  so we will use the resource logical id as the resource id                  found serverless function with name  helloworldfunction  and codeuri  hello world                      base dir is not presented  adjusting uri hello world  relative to  home simha personal data programming arch firefox extra unsorted vid web dev hss iqgateway aws sam sam app template yaml                  no parameters detected in the template                  there is no customer defined id or cdk path defined for resource helloworldfunction  so we will use the resource logical id as the resource id                  there is no customer defined id or cdk path defined for resource serverlessrestapi  so we will use the resource logical id as the resource id                  executing the build using build context                   no parameters detected in the template                  there is no customer defined id or cdk path defined for resource helloworldfunction  so we will use the resource logical id as the resource id                  there is no customer defined id or cdk path defined for resource serverlessrestapi  so we will use the resource logical id as the resource id                  your template contains a resource with logical id  serverlessrestapi   which is a reserved logical id in aws sam  it could result in unexpected behaviors and is not recommended                   instantiating build definitions                  same function build definition found  adding function  previous  builddefinition       home simha personal data programming arch firefox extra unsorted vid web dev hss iqgateway aws sam sam app hello world  zip                                current  builddefinition       home simha personal data programming arch firefox extra unsorted vid web dev hss iqgateway aws sam sam app hello world  zip                                function  function function id  helloworldfunction   name  helloworldfunction   functionname  helloworldfunction   runtime        memory none  timeout    handler  app lambda handler   imageuri none  packagetype  zip   imageconfig none  codeuri   home simha personal data programming arch firefox extra unsorted vid web dev hss iqgateway aws sam sam app hello world   environment none  rolearn none  layers    events   helloworld     type    api    properties     path     copy files    method    post    restapiid    serverlessrestapi      metadata   samresourceid    helloworldfunction    inlinecode none  codesign config arn none  architectures    stack path                       async execution started                  invoking function functools partial                        running incremental build for runtime     for build definition                            waiting for async results                  manifest file is changed  new hash     or dependency folder   aws sam deps            is missing for            downloading dependencies and copying building source                  building codeuri   home simha personal data programming arch firefox extra unsorted vid web dev hss iqgateway aws sam sam app hello world runtime      metadata     architecture      functions                     building to following folder  home simha personal data programming arch firefox extra unsorted vid web dev hss iqgateway aws sam sam app  aws sam auto dependency layer helloworldfunction                  loading workflow module  aws lambda builders workflows                   registering workflow  pythonpipbuilder  with capability  capability language  python   dependency manager  pip   application framework none                    registering workflow  nodejsnpmbuilder  with capability  capability language  nodejs   dependency manager  npm   application framework none                    registering workflow  rubybundlerbuilder  with capability  capability language  ruby   dependency manager  bundler   application framework none                    registering workflow  godepbuilder  with capability  capability language  go   dependency manager  dep   application framework none                    registering workflow  gomodulesbuilder  with capability  capability language  go   dependency manager  modules   application framework none                    registering workflow  javagradleworkflow  with capability  capability language  java   dependency manager  gradle   application framework none                    registering workflow  javamavenworkflow  with capability  capability language  java   dependency manager  maven   application framework none                    registering workflow  dotnetclipackagebuilder  with capability  capability language  dotnet   dependency manager  cli package   application framework none                    registering workflow  custommakebuilder  with capability  capability language  provided   dependency manager none  application framework none                    registering workflow  nodejsnpmesbuildbuilder  with capability  capability language  nodejs   dependency manager  npm esbuild   application framework none                    found workflow  pythonpipbuilder  to support capabilities  capability language  python   dependency manager  pip   application framework none                    invalid executable for python at  usr bin python  traceback  most recent call last      file  aws lambda builders workflow py   line    in wrapper    file  aws lambda builders workflows python pip validator py   line    in validate  aws lambda builders exceptions mismatchruntimeerror  python executable found in your path does not match runtime     expected version       found version   usr bin python     possibly related                     invalid executable for python at  bin python  traceback  most recent call last      file  aws lambda builders workflow py   line    in wrapper    file  aws lambda builders workflows python pip validator py   line    in validate  aws lambda builders exceptions mismatchruntimeerror  python executable found in your path does not match runtime     expected version       found version   bin python     possibly related                     exception raised during the execution    build failed                  sending telemetry    metrics                       httpsconnectionpool host  aws serverless tools telemetry us west   amazonaws com   port     read timed out   read timeout       error  pythonpipbuilder validation   binary validation failed for python  searched for python in following locations      which did not satisfy constraints for runtime       do you have python for runtime      on your path            additional environment details  ex  windows  mac  amazon linux etc   os  linux  sam   version     sam   version  sam cli  version        aws region   ,0
243122,7853558671.0,IssuesEvent,2018-06-20 17:49:04,bcgov/name-examination,https://api.github.com/repos/bcgov/name-examination,closed,Identify Name Parts,Priority: 1 Sprint Priority 3 Story invalid,"[Names Guidelines.pdf](https://github.com/bcgov/name-examination/files/1804224/Names.Guidelines.pdf)

#### **Story**
As an examiner I want the system to prepare, determine and visually indicate the distinctive and descriptive words in the selected name choice.

##### BDD Pseudo-Code (GIVEN ""context"" ... AND ""more context"" ... WHEN ""this action occurs"" ... THEN ...""result"")

GIVEN the NR is the current one the examiner is working on and it has a status ""IN PROGRESS"" and the name choice is selected and we have a good thesaurus 
WHEN the name choice words are prepared
THEN identify each word in the name choice as descriptive or distinctive.

##### _**Logic**_
- compare each word in the name choice against the thesaurus table to see if there is a match.
- look for thesaurus words embedded inside the name choice words.
- store the prepared words for later use.

##### _**Acceptance Criteria**_
- visually flag all words that match as descriptive.
- visually flag all other words in the name choice as distinctive


##### _**Issue Checklist**_ 
- [x] BDD Pseudo-Code 
- [x] Estimate 
- [x] Priority Label 
- [x] Story Label
- [x] Linked EPIC


##### _**Definition of Done**_
- [x] Analysis/Design 
- [ ] DB 
- [ ] UI 
- [ ] Integration Points
- [x] Logic
- [ ] Test Script
",2.0,"Identify Name Parts - [Names Guidelines.pdf](https://github.com/bcgov/name-examination/files/1804224/Names.Guidelines.pdf)

#### **Story**
As an examiner I want the system to prepare, determine and visually indicate the distinctive and descriptive words in the selected name choice.

##### BDD Pseudo-Code (GIVEN ""context"" ... AND ""more context"" ... WHEN ""this action occurs"" ... THEN ...""result"")

GIVEN the NR is the current one the examiner is working on and it has a status ""IN PROGRESS"" and the name choice is selected and we have a good thesaurus 
WHEN the name choice words are prepared
THEN identify each word in the name choice as descriptive or distinctive.

##### _**Logic**_
- compare each word in the name choice against the thesaurus table to see if there is a match.
- look for thesaurus words embedded inside the name choice words.
- store the prepared words for later use.

##### _**Acceptance Criteria**_
- visually flag all words that match as descriptive.
- visually flag all other words in the name choice as distinctive


##### _**Issue Checklist**_ 
- [x] BDD Pseudo-Code 
- [x] Estimate 
- [x] Priority Label 
- [x] Story Label
- [x] Linked EPIC


##### _**Definition of Done**_
- [x] Analysis/Design 
- [ ] DB 
- [ ] UI 
- [ ] Integration Points
- [x] Logic
- [ ] Test Script
",0,identify name parts                 story    as an examiner i want the system to prepare  determine and visually indicate the distinctive and descriptive words in the selected name choice           bdd pseudo code  given  context      and  more context      when  this action occurs      then     result      given the nr is the current one the examiner is working on and it has a status  in progress  and the name choice is selected and we have a good thesaurus   when the name choice words are prepared  then identify each word in the name choice as descriptive or distinctive              logic       compare each word in the name choice against the thesaurus table to see if there is a match     look for thesaurus words embedded inside the name choice words     store the prepared words for later use              acceptance criteria       visually flag all words that match as descriptive     visually flag all other words in the name choice as distinctive               issue checklist          bdd pseudo code       estimate       priority label       story label      linked epic               definition of done         analysis design       db       ui       integration points      logic      test script  ,0
62394,8603381558.0,IssuesEvent,2018-11-16 16:40:17,golang/go,https://api.github.com/repos/golang/go,closed,net/http: SameSite description is grammatically incorrect,Documentation help wanted,"Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
go 1.11.x

### Does this issue reproduce with the latest release?
The issue is with the documentation for net/http/SameSite documentation which was added in go 1.11

### What did you expect to see?
I believe the following captures the intended description, without restructuring it too significantly

**SameSite allows a server to define a cookie attribute making it impossible for the browser to send this cookie along with cross-site requests. The main goal is to mitigate the risk of cross-origin information leakage and provide some protection against cross-site request forgery attacks.**

### What did you see instead?
SameSite allows a server define a cookie attribute making it impossible to the browser send this cookie along with cross-site requests. The main goal is mitigate the risk of cross-origin information leakage, and provides some protection against cross-site request forgery attacks.
",1.0,"net/http: SameSite description is grammatically incorrect - Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
go 1.11.x

### Does this issue reproduce with the latest release?
The issue is with the documentation for net/http/SameSite documentation which was added in go 1.11

### What did you expect to see?
I believe the following captures the intended description, without restructuring it too significantly

**SameSite allows a server to define a cookie attribute making it impossible for the browser to send this cookie along with cross-site requests. The main goal is to mitigate the risk of cross-origin information leakage and provide some protection against cross-site request forgery attacks.**

### What did you see instead?
SameSite allows a server define a cookie attribute making it impossible to the browser send this cookie along with cross-site requests. The main goal is mitigate the risk of cross-origin information leakage, and provides some protection against cross-site request forgery attacks.
",1,net http  samesite description is grammatically incorrect   please answer these questions before submitting your issue  thanks           what version of go are you using   go version     go     x        does this issue reproduce with the latest release   the issue is with the documentation for net http samesite documentation which was added in go            what did you expect to see   i believe the following captures the intended description  without restructuring it too significantly      samesite allows a server to define a cookie attribute making it impossible for the browser to send this cookie along with cross site requests  the main goal is to mitigate the risk of cross origin information leakage and provide some protection against cross site request forgery attacks           what did you see instead   samesite allows a server define a cookie attribute making it impossible to the browser send this cookie along with cross site requests  the main goal is mitigate the risk of cross origin information leakage  and provides some protection against cross site request forgery attacks   ,1
326119,27976217555.0,IssuesEvent,2023-03-25 16:10:19,unifyai/ivy,https://api.github.com/repos/unifyai/ivy,reopened,Fix manipulation.test_swapaxes,Sub Task Failing Test,"|   |   |
|---|---|
|tensorflow|<a href=""https://github.com/unifyai/ivy/actions/runs/4489924240/jobs/7896356921"" rel=""noopener noreferrer"" target=""_blank""><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href=""null"" rel=""noopener noreferrer"" target=""_blank""><img src=https://img.shields.io/badge/-failure-red></a>
|numpy|<a href=""https://github.com/unifyai/ivy/actions/runs/4489924240/jobs/7896356921"" rel=""noopener noreferrer"" target=""_blank""><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href=""https://github.com/unifyai/ivy/actions/runs/4489924240/jobs/7896356921"" rel=""noopener noreferrer"" target=""_blank""><img src=https://img.shields.io/badge/-success-success></a>


",1.0,"Fix manipulation.test_swapaxes - |   |   |
|---|---|
|tensorflow|<a href=""https://github.com/unifyai/ivy/actions/runs/4489924240/jobs/7896356921"" rel=""noopener noreferrer"" target=""_blank""><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href=""null"" rel=""noopener noreferrer"" target=""_blank""><img src=https://img.shields.io/badge/-failure-red></a>
|numpy|<a href=""https://github.com/unifyai/ivy/actions/runs/4489924240/jobs/7896356921"" rel=""noopener noreferrer"" target=""_blank""><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href=""https://github.com/unifyai/ivy/actions/runs/4489924240/jobs/7896356921"" rel=""noopener noreferrer"" target=""_blank""><img src=https://img.shields.io/badge/-success-success></a>


",0,fix manipulation test swapaxes                          tensorflow   img src     torch   img src     numpy   img src     jax   img src        ,0
97569,12246464636.0,IssuesEvent,2020-05-05 14:29:52,meloneminze/famly,https://api.github.com/repos/meloneminze/famly,closed,Create Icons,component design storybook,"### User Story
As a developer I need icons! I will build them in storybook. 

### Clarification
##To do
Create icons for different pages:
- [ ] Birthday
- [ ] cloth
- [ ] shoes/footprint
- [ ] plus
- [ ] pen
- [ ] go back
- [ ] X
- [ ] child
- [ ]  house

## Criteria
- [ ] Use design prototype
- [ ] Use storybook to build the components
- [ ] different colors


### Material | Images
Design:
https://xd.adobe.com/view/7f86dc69-703e-48db-70d4-8d3d07276926-09b7/

icons examples:
![image](https://user-images.githubusercontent.com/36224722/79105746-8b4bd280-7d71-11ea-9c0f-b3cd3e33c80b.png)

",1.0,"Create Icons - ### User Story
As a developer I need icons! I will build them in storybook. 

### Clarification
##To do
Create icons for different pages:
- [ ] Birthday
- [ ] cloth
- [ ] shoes/footprint
- [ ] plus
- [ ] pen
- [ ] go back
- [ ] X
- [ ] child
- [ ]  house

## Criteria
- [ ] Use design prototype
- [ ] Use storybook to build the components
- [ ] different colors


### Material | Images
Design:
https://xd.adobe.com/view/7f86dc69-703e-48db-70d4-8d3d07276926-09b7/

icons examples:
![image](https://user-images.githubusercontent.com/36224722/79105746-8b4bd280-7d71-11ea-9c0f-b3cd3e33c80b.png)

",0,create icons       user story  as a developer i need icons  i will build them in storybook          clarification    to do  create icons for different pages       birthday      cloth      shoes footprint      plus      pen      go back      x      child       house       criteria      use design prototype      use storybook to build the components      different colors          material   images  design        icons examples           ,0
7157,3081443706.0,IssuesEvent,2015-08-22 18:40:32,golang/go,https://api.github.com/repos/golang/go,closed,all: move all examples to external test packages,Documentation,"This is an extraction from #11254.

Having the package prefix in examples is clearer than omitting it. Since examples must not make use of unexported functionality anyway, it is always ok to have them in an external test package. Let's move all examples to external test packages.

If Go 1 compatibility didn't prevent it, I'd suggest that we modify the testing package to enforce this.
",1.0,"all: move all examples to external test packages - This is an extraction from #11254.

Having the package prefix in examples is clearer than omitting it. Since examples must not make use of unexported functionality anyway, it is always ok to have them in an external test package. Let's move all examples to external test packages.

If Go 1 compatibility didn't prevent it, I'd suggest that we modify the testing package to enforce this.
",1,all  move all examples to external test packages   this is an extraction from        having the package prefix in examples is clearer than omitting it  since examples must not make use of unexported functionality anyway  it is always ok to have them in an external test package  let s move all examples to external test packages     if go   compatibility didn t prevent it  i d suggest that we modify the testing package to enforce this   ,1
27867,5401131769.0,IssuesEvent,2017-02-28 00:03:53,golang/go,https://api.github.com/repos/golang/go,closed,net/url: document what is a valid URL,Documentation,"This [post on go-nuts](https://groups.google.com/forum/#!topic/golang-nuts/I8fVgXbdz7Q) is indicative that the url package is very frequently mis-used. Even when I was running go1.8 over Go code inside Google, incorrect usages of `url.Parse` were a frequent source of problems.

One very common mistake I see is something like the following:
```go
u, err := url.Parse(""192.168.0.1/path/to/endpoint"")
fmt.Printf(""%#v\n"", u)
```

This is a valid URL, but it does not do what people expect it to do. When printed, it shows:
```go
&url.URL{Host:"""", Path:""192.168.0.1/path/to/endpoint""}
```
What the user was expecting was:
```go
&url.URL{Host:""192.168.0.1"", Path:""/path/to/endpoint""}
```
Notice that the IP address is part of the Path component and *not* the Host?

The current behavior is correct because the URL provided is not an absolute URL and therefore must be parsed as a relative URL. However, this behavior is not obvious.

In order to get around this issue, I have seen users do `url.Parse(""//192.168.0.1/path/to/endpoint"")` to achieve the desired behavior. While this properly parses ""192.168.0.1"" as the Host and ""/path/to/endpoint"" as the Path, it is not obvious to users that this is a valid URL. (this format is called the ""network-path reference"" from RFC 3986, section 4.2)",1.0,"net/url: document what is a valid URL - This [post on go-nuts](https://groups.google.com/forum/#!topic/golang-nuts/I8fVgXbdz7Q) is indicative that the url package is very frequently mis-used. Even when I was running go1.8 over Go code inside Google, incorrect usages of `url.Parse` were a frequent source of problems.

One very common mistake I see is something like the following:
```go
u, err := url.Parse(""192.168.0.1/path/to/endpoint"")
fmt.Printf(""%#v\n"", u)
```

This is a valid URL, but it does not do what people expect it to do. When printed, it shows:
```go
&url.URL{Host:"""", Path:""192.168.0.1/path/to/endpoint""}
```
What the user was expecting was:
```go
&url.URL{Host:""192.168.0.1"", Path:""/path/to/endpoint""}
```
Notice that the IP address is part of the Path component and *not* the Host?

The current behavior is correct because the URL provided is not an absolute URL and therefore must be parsed as a relative URL. However, this behavior is not obvious.

In order to get around this issue, I have seen users do `url.Parse(""//192.168.0.1/path/to/endpoint"")` to achieve the desired behavior. While this properly parses ""192.168.0.1"" as the Host and ""/path/to/endpoint"" as the Path, it is not obvious to users that this is a valid URL. (this format is called the ""network-path reference"" from RFC 3986, section 4.2)",1,net url  document what is a valid url   this     is indicative that the url package is very frequently mis used  even when i was running     over go code inside google  incorrect usages of  url parse  were a frequent source of problems     one very common mistake i see is something like the following      go  u  err    url parse          path to endpoint    fmt printf    v n   u          this is a valid url  but it does not do what people expect it to do  when printed  it shows      go   url url host     path          path to endpoint         what the user was expecting was      go   url url host            path   path to endpoint         notice that the ip address is part of the path component and  not  the host     the current behavior is correct because the url provided is not an absolute url and therefore must be parsed as a relative url  however  this behavior is not obvious     in order to get around this issue  i have seen users do  url parse            path to endpoint    to achieve the desired behavior  while this properly parses           as the host and   path to endpoint  as the path  it is not obvious to users that this is a valid url   this format is called the  network path reference  from rfc    section     ,1
297486,22359543598.0,IssuesEvent,2022-06-15 18:59:55,golang/go,https://api.github.com/repos/golang/go,closed,"doc: cmd/go: document use with modules ""from the ground up""",Documentation help wanted modules,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.11.3 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

NA

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
NA
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

I am a go newbie trying to set up several folders with go code in a monorepo (which also contains code built in other languages). Some of these folders will contain services, others library utilities.

### What did you expect to see?

I would like documentation based on the new ""module"" paradigm that explain:

* module
* package
* file
* folder

and their relationship to each other ""from the ground up"" (without assuming knowledge of how things used to work). In particular, in a monorepo,

* should there be an overall ""go.mod"", or one in each folder (or both??)
* if there is only one ""go.mod"" how do I specify different dependencies for each folder? If not,
is there a way to specify common dependencies to force version synchronization (or if there isn't
doc should flag as gotcha).
* how do I refer to code in one folder from another?

### What did you see instead?

The tutorials don't cover modules. The official doc for modules are geared to explain what is different for experienced go users. There seems to be no good documentation anywhere on
use of modules in monorepos.
",1.0,"doc: cmd/go: document use with modules ""from the ground up"" - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.11.3 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

NA

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
NA
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

I am a go newbie trying to set up several folders with go code in a monorepo (which also contains code built in other languages). Some of these folders will contain services, others library utilities.

### What did you expect to see?

I would like documentation based on the new ""module"" paradigm that explain:

* module
* package
* file
* folder

and their relationship to each other ""from the ground up"" (without assuming knowledge of how things used to work). In particular, in a monorepo,

* should there be an overall ""go.mod"", or one in each folder (or both??)
* if there is only one ""go.mod"" how do I specify different dependencies for each folder? If not,
is there a way to specify common dependencies to force version synchronization (or if there isn't
doc should flag as gotcha).
* how do I refer to code in one folder from another?

### What did you see instead?

The tutorials don't cover modules. The official doc for modules are geared to explain what is different for experienced go users. There seems to be no good documentation anywhere on
use of modules in monorepos.
",1,doc  cmd go  document use with modules  from the ground up             what version of go are you using   go version            go version  go version       darwin             does this issue reproduce with the latest release     na        what operating system and processor architecture are you using   go env          go env  output       go env  na            what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best          i am a go newbie trying to set up several folders with go code in a monorepo  which also contains code built in other languages   some of these folders will contain services  others library utilities         what did you expect to see     i would like documentation based on the new  module  paradigm that explain       module    package    file    folder    and their relationship to each other  from the ground up   without assuming knowledge of how things used to work   in particular  in a monorepo       should there be an overall  go mod   or one in each folder  or both       if there is only one  go mod  how do i specify different dependencies for each folder  if not   is there a way to specify common dependencies to force version synchronization  or if there isn t  doc should flag as gotcha      how do i refer to code in one folder from another         what did you see instead     the tutorials don t cover modules  the official doc for modules are geared to explain what is different for experienced go users  there seems to be no good documentation anywhere on  use of modules in monorepos   ,1
143614,5520875146.0,IssuesEvent,2017-03-19 10:29:35,minishift/minishift,https://api.github.com/repos/minishift/minishift,closed,Inconsistent output between oc and web interface,kind/bug priority/major,"I'm using origin 1.4 from a minishift setup with the CentOS image. All functioning and up and running. It is in a kvm VM on Fedora 25.

The list of projects between the web interface and oc are pretty drastically different.

logged into the web UI and oc as system:admin

in the web interface you cannot see the default, openshift, openshift-infra, etc. projects. However they are visible to oc.
If you create a project in the web interface you can see it in oc
If you create a project in oc, you cannot see it in the web interface
I would assume that the project listings would be consistent in the web interface and with oc.

Version

OpenShift Master:
v1.4.1+3f9807a
Kubernetes Master:
v1.4.0+776c994

I've confirmed the same functionality with oc v1.4.1+3f9807a and oc v1.3.1

Steps To Reproduce

set up minishift with a CentOS image
log in as system:admin in the gui and with oc
create a project in the gui
create a project with oc
compare the lists
Current Result

in the web interface you cannot see the default, openshift, openshift-infra, etc. projects. However they are visible to oc.
If you create a project in the web interface you can see it in oc
If you create a project in oc, you cannot see it in the web interface
Expected Result

The project listings should be consistent using both methods.

I also opened this as https://github.com/openshift/origin/issues/13440 ",1.0,"Inconsistent output between oc and web interface - I'm using origin 1.4 from a minishift setup with the CentOS image. All functioning and up and running. It is in a kvm VM on Fedora 25.

The list of projects between the web interface and oc are pretty drastically different.

logged into the web UI and oc as system:admin

in the web interface you cannot see the default, openshift, openshift-infra, etc. projects. However they are visible to oc.
If you create a project in the web interface you can see it in oc
If you create a project in oc, you cannot see it in the web interface
I would assume that the project listings would be consistent in the web interface and with oc.

Version

OpenShift Master:
v1.4.1+3f9807a
Kubernetes Master:
v1.4.0+776c994

I've confirmed the same functionality with oc v1.4.1+3f9807a and oc v1.3.1

Steps To Reproduce

set up minishift with a CentOS image
log in as system:admin in the gui and with oc
create a project in the gui
create a project with oc
compare the lists
Current Result

in the web interface you cannot see the default, openshift, openshift-infra, etc. projects. However they are visible to oc.
If you create a project in the web interface you can see it in oc
If you create a project in oc, you cannot see it in the web interface
Expected Result

The project listings should be consistent using both methods.

I also opened this as https://github.com/openshift/origin/issues/13440 ",0,inconsistent output between oc and web interface   i m using origin     from a minishift setup with the centos image  all functioning and up and running  it is in a kvm vm on fedora       the list of projects between the web interface and oc are pretty drastically different     logged into the web ui and oc as system admin    in the web interface you cannot see the default  openshift  openshift infra  etc  projects  however they are visible to oc   if you create a project in the web interface you can see it in oc  if you create a project in oc  you cannot see it in the web interface  i would assume that the project listings would be consistent in the web interface and with oc     version    openshift master            kubernetes master              i ve confirmed the same functionality with oc         and oc          steps to reproduce    set up minishift with a centos image  log in as system admin in the gui and with oc  create a project in the gui  create a project with oc  compare the lists  current result    in the web interface you cannot see the default  openshift  openshift infra  etc  projects  however they are visible to oc   if you create a project in the web interface you can see it in oc  if you create a project in oc  you cannot see it in the web interface  expected result    the project listings should be consistent using both methods     i also opened this as   ,0
85742,10458255295.0,IssuesEvent,2019-09-20 08:07:36,golang/go,https://api.github.com/repos/golang/go,closed,"doc: Effective Go doc misuses word ""anew"", resulting in confusing usage rule",Documentation,"In Effective Go, in the section on ""Redeclaration and reassignment,"" it says that an existing variable may appear in a short declaration if ""there is at least one other variable in the declaration that is being declared anew.""

Doesn't it really mean being declared for the first time? That's not what ""anew"" means; if anything, it means ""again.""",1.0,"doc: Effective Go doc misuses word ""anew"", resulting in confusing usage rule - In Effective Go, in the section on ""Redeclaration and reassignment,"" it says that an existing variable may appear in a short declaration if ""there is at least one other variable in the declaration that is being declared anew.""

Doesn't it really mean being declared for the first time? That's not what ""anew"" means; if anything, it means ""again.""",1,doc  effective go doc misuses word  anew   resulting in confusing usage rule   in effective go  in the section on  redeclaration and reassignment   it says that an existing variable may appear in a short declaration if  there is at least one other variable in the declaration that is being declared anew      doesn t it really mean being declared for the first time  that s not what  anew  means  if anything  it means  again  ,1
199506,6989834686.0,IssuesEvent,2017-12-14 17:24:30,salesagility/SuiteCRM,https://api.github.com/repos/salesagility/SuiteCRM,closed,Subsciptions missing Save/Cancel Buttons 7.8.5 ThemeP,bug Fix Proposed Low Priority Resolved: Next Release,"<!--- Provide a general summary of the issue in the **Title** above -->
<!--- Before you open an issue, please check if a similar issue already exists or has been closed before. --->

#### Issue
<!--- Provide a more detailed introduction to the issue itself, and why you consider it to be a bug -->
The Buttons are missing in manage subscription page
![grafik](https://user-images.githubusercontent.com/16813374/29658071-f338f300-88b9-11e7-8d5d-d3c04fe22bf3.png)

#### Expected Behavior
<!--- Tell us what should happen -->
Display Buttons
#### Actual Behavior
<!--- Tell us what happens instead -->
No Buttons available, unabel to save change
#### Possible Fix
<!--- Not obligatory, but suggest a fix or reason for the bug -->
Fix in Subscription.tpl
#### Steps to Reproduce
<!--- Provide a link to a live example, or an unambiguous set of steps to -->
<!--- reproduce this bug include code to reproduce, if relevant -->
1.open Contact-> Manage Subscripitions


#### Context
<!--- How has this bug affected you? What were you trying to accomplish? -->
<!--- If you feel this should be a low/medium/high priority then please state so -->

#### Your Environment
<!--- Include as many relevant details about the environment you experienced the bug in -->
* SuiteCRM Version used: 7.8.5 ThemeP
* Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): all Browsers
* Environment name and version (e.g. MySQL, PHP 7):
* Operating System and version (e.g Ubuntu 16.04):
",1.0,"Subsciptions missing Save/Cancel Buttons 7.8.5 ThemeP - <!--- Provide a general summary of the issue in the **Title** above -->
<!--- Before you open an issue, please check if a similar issue already exists or has been closed before. --->

#### Issue
<!--- Provide a more detailed introduction to the issue itself, and why you consider it to be a bug -->
The Buttons are missing in manage subscription page
![grafik](https://user-images.githubusercontent.com/16813374/29658071-f338f300-88b9-11e7-8d5d-d3c04fe22bf3.png)

#### Expected Behavior
<!--- Tell us what should happen -->
Display Buttons
#### Actual Behavior
<!--- Tell us what happens instead -->
No Buttons available, unabel to save change
#### Possible Fix
<!--- Not obligatory, but suggest a fix or reason for the bug -->
Fix in Subscription.tpl
#### Steps to Reproduce
<!--- Provide a link to a live example, or an unambiguous set of steps to -->
<!--- reproduce this bug include code to reproduce, if relevant -->
1.open Contact-> Manage Subscripitions


#### Context
<!--- How has this bug affected you? What were you trying to accomplish? -->
<!--- If you feel this should be a low/medium/high priority then please state so -->

#### Your Environment
<!--- Include as many relevant details about the environment you experienced the bug in -->
* SuiteCRM Version used: 7.8.5 ThemeP
* Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): all Browsers
* Environment name and version (e.g. MySQL, PHP 7):
* Operating System and version (e.g Ubuntu 16.04):
",0,subsciptions missing save cancel buttons       themep                issue     the buttons are missing in manage subscription page               expected behavior     display buttons       actual behavior     no buttons available  unabel to save change       possible fix     fix in subscription tpl       steps to reproduce          open contact   manage subscripitions           context               your environment       suitecrm version used        themep    browser name and version  e g  chrome version            bit    all browsers    environment name and version  e g  mysql  php        operating system and version  e g ubuntu        ,0
19231,6689317112.0,IssuesEvent,2017-10-09 00:47:16,tensorflow/tensorflow,https://api.github.com/repos/tensorflow/tensorflow,closed,Problem importing Tensorflow in Windows 10 64bits,stat:awaiting response type:build/install,"Hello everybody. I'm new in Tensorflow. So, forgive me for any mistakes that a make. 

I'm importing Tensorfow-gpu in Windows but I'm getting the message bellow. 

**### System information**
- **OS Platform and Distribution:** Windows 10 64 bits
- **TensorFlow installed from:** pip
- **TensorFlow version:** 1.3
- **Python version:** 3.6.2 - v3.6.2:5fd33b5, Jul  8 2017, 04:57:36
- **CUDA:** 9.0.176
- **cuDNN version:** I've tried with version 5, 6 and 7
- **GPU model and memory**: 1050 4GB
- **Exact command to reproduce**: import tensorflow

**PS:** all the path settings have been set. 

**### The error message**
C:\Windows\system32>python
Python 3.6.2 (v3.6.2:5fd33b5, Jul  8 2017, 04:57:36) [MSC v.1900 64 bit (AMD64)] on win32
Type ""help"", ""copyright"", ""credits"" or ""license"" for more information.
>>> import tensorflow
Traceback (most recent call last):
  File ""C:\python\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py"", line 18, in swig_import_helper
    return importlib.import_module(mname)
  File ""C:\python\lib\importlib\__init__.py"", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File ""<frozen importlib._bootstrap>"", line 978, in _gcd_import
  File ""<frozen importlib._bootstrap>"", line 961, in _find_and_load
  File ""<frozen importlib._bootstrap>"", line 950, in _find_and_load_unlocked
  File ""<frozen importlib._bootstrap>"", line 648, in _load_unlocked
  File ""<frozen importlib._bootstrap>"", line 560, in module_from_spec
  File ""<frozen importlib._bootstrap_external>"", line 922, in create_module
  File ""<frozen importlib._bootstrap>"", line 205, in _call_with_frames_removed
ImportError: DLL load failed: Não foi possível encontrar o módulo especificado.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File ""C:\python\lib\site-packages\tensorflow\python\pywrap_tensorflow.py"", line 41, in <module>
    from tensorflow.python.pywrap_tensorflow_internal import *
  File ""C:\python\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py"", line 21, in <module>
    _pywrap_tensorflow_internal = swig_import_helper()
  File ""C:\python\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py"", line 20, in swig_import_helper
    return importlib.import_module('_pywrap_tensorflow_internal')
  File ""C:\python\lib\importlib\__init__.py"", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
ModuleNotFoundError: No module named '_pywrap_tensorflow_internal'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File ""<stdin>"", line 1, in <module>
  File ""C:\python\lib\site-packages\tensorflow\__init__.py"", line 24, in <module>
    from tensorflow.python import *
  File ""C:\python\lib\site-packages\tensorflow\python\__init__.py"", line 49, in <module>
    from tensorflow.python import pywrap_tensorflow
  File ""C:\python\lib\site-packages\tensorflow\python\pywrap_tensorflow.py"", line 52, in <module>
    raise ImportError(msg)
ImportError: Traceback (most recent call last):
  File ""C:\python\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py"", line 18, in swig_import_helper
    return importlib.import_module(mname)
  File ""C:\python\lib\importlib\__init__.py"", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File ""<frozen importlib._bootstrap>"", line 978, in _gcd_import
  File ""<frozen importlib._bootstrap>"", line 961, in _find_and_load
  File ""<frozen importlib._bootstrap>"", line 950, in _find_and_load_unlocked
  File ""<frozen importlib._bootstrap>"", line 648, in _load_unlocked
  File ""<frozen importlib._bootstrap>"", line 560, in module_from_spec
  File ""<frozen importlib._bootstrap_external>"", line 922, in create_module
  File ""<frozen importlib._bootstrap>"", line 205, in _call_with_frames_removed
ImportError: DLL load failed: Não foi possível encontrar o módulo especificado.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File ""C:\python\lib\site-packages\tensorflow\python\pywrap_tensorflow.py"", line 41, in <module>
    from tensorflow.python.pywrap_tensorflow_internal import *
  File ""C:\python\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py"", line 21, in <module>
    _pywrap_tensorflow_internal = swig_import_helper()
  File ""C:\python\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py"", line 20, in swig_import_helper
    return importlib.import_module('_pywrap_tensorflow_internal')
  File ""C:\python\lib\importlib\__init__.py"", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
ModuleNotFoundError: No module named '_pywrap_tensorflow_internal'


Failed to load the native TensorFlow runtime.

See https://www.tensorflow.org/install/install_sources#common_installation_problems

for some common reasons and solutions.  Include the entire stack trace
above this error message when asking for help.
>>>",1.0,"Problem importing Tensorflow in Windows 10 64bits - Hello everybody. I'm new in Tensorflow. So, forgive me for any mistakes that a make. 

I'm importing Tensorfow-gpu in Windows but I'm getting the message bellow. 

**### System information**
- **OS Platform and Distribution:** Windows 10 64 bits
- **TensorFlow installed from:** pip
- **TensorFlow version:** 1.3
- **Python version:** 3.6.2 - v3.6.2:5fd33b5, Jul  8 2017, 04:57:36
- **CUDA:** 9.0.176
- **cuDNN version:** I've tried with version 5, 6 and 7
- **GPU model and memory**: 1050 4GB
- **Exact command to reproduce**: import tensorflow

**PS:** all the path settings have been set. 

**### The error message**
C:\Windows\system32>python
Python 3.6.2 (v3.6.2:5fd33b5, Jul  8 2017, 04:57:36) [MSC v.1900 64 bit (AMD64)] on win32
Type ""help"", ""copyright"", ""credits"" or ""license"" for more information.
>>> import tensorflow
Traceback (most recent call last):
  File ""C:\python\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py"", line 18, in swig_import_helper
    return importlib.import_module(mname)
  File ""C:\python\lib\importlib\__init__.py"", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File ""<frozen importlib._bootstrap>"", line 978, in _gcd_import
  File ""<frozen importlib._bootstrap>"", line 961, in _find_and_load
  File ""<frozen importlib._bootstrap>"", line 950, in _find_and_load_unlocked
  File ""<frozen importlib._bootstrap>"", line 648, in _load_unlocked
  File ""<frozen importlib._bootstrap>"", line 560, in module_from_spec
  File ""<frozen importlib._bootstrap_external>"", line 922, in create_module
  File ""<frozen importlib._bootstrap>"", line 205, in _call_with_frames_removed
ImportError: DLL load failed: Não foi possível encontrar o módulo especificado.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File ""C:\python\lib\site-packages\tensorflow\python\pywrap_tensorflow.py"", line 41, in <module>
    from tensorflow.python.pywrap_tensorflow_internal import *
  File ""C:\python\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py"", line 21, in <module>
    _pywrap_tensorflow_internal = swig_import_helper()
  File ""C:\python\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py"", line 20, in swig_import_helper
    return importlib.import_module('_pywrap_tensorflow_internal')
  File ""C:\python\lib\importlib\__init__.py"", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
ModuleNotFoundError: No module named '_pywrap_tensorflow_internal'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File ""<stdin>"", line 1, in <module>
  File ""C:\python\lib\site-packages\tensorflow\__init__.py"", line 24, in <module>
    from tensorflow.python import *
  File ""C:\python\lib\site-packages\tensorflow\python\__init__.py"", line 49, in <module>
    from tensorflow.python import pywrap_tensorflow
  File ""C:\python\lib\site-packages\tensorflow\python\pywrap_tensorflow.py"", line 52, in <module>
    raise ImportError(msg)
ImportError: Traceback (most recent call last):
  File ""C:\python\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py"", line 18, in swig_import_helper
    return importlib.import_module(mname)
  File ""C:\python\lib\importlib\__init__.py"", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File ""<frozen importlib._bootstrap>"", line 978, in _gcd_import
  File ""<frozen importlib._bootstrap>"", line 961, in _find_and_load
  File ""<frozen importlib._bootstrap>"", line 950, in _find_and_load_unlocked
  File ""<frozen importlib._bootstrap>"", line 648, in _load_unlocked
  File ""<frozen importlib._bootstrap>"", line 560, in module_from_spec
  File ""<frozen importlib._bootstrap_external>"", line 922, in create_module
  File ""<frozen importlib._bootstrap>"", line 205, in _call_with_frames_removed
ImportError: DLL load failed: Não foi possível encontrar o módulo especificado.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File ""C:\python\lib\site-packages\tensorflow\python\pywrap_tensorflow.py"", line 41, in <module>
    from tensorflow.python.pywrap_tensorflow_internal import *
  File ""C:\python\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py"", line 21, in <module>
    _pywrap_tensorflow_internal = swig_import_helper()
  File ""C:\python\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py"", line 20, in swig_import_helper
    return importlib.import_module('_pywrap_tensorflow_internal')
  File ""C:\python\lib\importlib\__init__.py"", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
ModuleNotFoundError: No module named '_pywrap_tensorflow_internal'


Failed to load the native TensorFlow runtime.

See https://www.tensorflow.org/install/install_sources#common_installation_problems

for some common reasons and solutions.  Include the entire stack trace
above this error message when asking for help.
>>>",0,problem importing tensorflow in windows       hello everybody  i m new in tensorflow  so  forgive me for any mistakes that a make      i m importing tensorfow gpu in windows but i m getting the message bellow            system information        os platform and distribution    windows     bits      tensorflow installed from    pip      tensorflow version             python version                     jul                  cuda               cudnn version    i ve tried with version      and        gpu model and memory             exact command to reproduce    import tensorflow      ps    all the path settings have been set            the error message    c  windows   python  python                 jul                on    type  help    copyright    credits  or  license  for more information       import tensorflow  traceback  most recent call last      file  c  python lib site packages tensorflow python pywrap tensorflow internal py   line    in swig import helper      return importlib import module mname     file  c  python lib importlib   init   py   line    in import module      return  bootstrap  gcd import name   package  level     file      line    in  gcd import    file      line    in  find and load    file      line    in  find and load unlocked    file      line    in  load unlocked    file      line    in module from spec    file      line    in create module    file      line    in  call with frames removed  importerror  dll load failed  não foi possível encontrar o módulo especificado     during handling of the above exception  another exception occurred     traceback  most recent call last      file  c  python lib site packages tensorflow python pywrap tensorflow py   line    in        from tensorflow python pywrap tensorflow internal import      file  c  python lib site packages tensorflow python pywrap tensorflow internal py   line    in         pywrap tensorflow internal   swig import helper      file  c  python lib site packages tensorflow python pywrap tensorflow internal py   line    in swig import helper      return importlib import module   pywrap tensorflow internal      file  c  python lib importlib   init   py   line    in import module      return  bootstrap  gcd import name   package  level   modulenotfounderror  no module named   pywrap tensorflow internal     during handling of the above exception  another exception occurred     traceback  most recent call last      file      line    in      file  c  python lib site packages tensorflow   init   py   line    in        from tensorflow python import      file  c  python lib site packages tensorflow python   init   py   line    in        from tensorflow python import pywrap tensorflow    file  c  python lib site packages tensorflow python pywrap tensorflow py   line    in        raise importerror msg   importerror  traceback  most recent call last      file  c  python lib site packages tensorflow python pywrap tensorflow internal py   line    in swig import helper      return importlib import module mname     file  c  python lib importlib   init   py   line    in import module      return  bootstrap  gcd import name   package  level     file      line    in  gcd import    file      line    in  find and load    file      line    in  find and load unlocked    file      line    in  load unlocked    file      line    in module from spec    file      line    in create module    file      line    in  call with frames removed  importerror  dll load failed  não foi possível encontrar o módulo especificado     during handling of the above exception  another exception occurred     traceback  most recent call last      file  c  python lib site packages tensorflow python pywrap tensorflow py   line    in        from tensorflow python pywrap tensorflow internal import      file  c  python lib site packages tensorflow python pywrap tensorflow internal py   line    in         pywrap tensorflow internal   swig import helper      file  c  python lib site packages tensorflow python pywrap tensorflow internal py   line    in swig import helper      return importlib import module   pywrap tensorflow internal      file  c  python lib importlib   init   py   line    in import module      return  bootstrap  gcd import name   package  level   modulenotfounderror  no module named   pywrap tensorflow internal       failed to load the native tensorflow runtime     see      for some common reasons and solutions   include the entire stack trace  above this error message when asking for help      ,0
237331,26084094067.0,IssuesEvent,2022-12-25 21:23:34,billmcchesney1/davinci,https://api.github.com/repos/billmcchesney1/davinci,opened,CVE-2022-46175 (High) detected in multiple libraries,security vulnerability,"## CVE-2022-46175 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>json5-0.5.1.tgz</b>, <b>json5-2.1.1.tgz</b>, <b>json5-1.0.1.tgz</b></p></summary>
<p>

<details><summary><b>json5-0.5.1.tgz</b></p></summary>

<p>JSON for the ES5 era.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/json5/-/json5-0.5.1.tgz"">https://registry.npmjs.org/json5/-/json5-0.5.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/vuepress-html-webpack-plugin/node_modules/json5/package.json</p>
<p>

Dependency Hierarchy:
  - vuepress-1.2.0.tgz (Root Library)
    - core-1.3.0.tgz
      - vuepress-html-webpack-plugin-3.2.0.tgz
        - loader-utils-0.2.17.tgz
          - :x: **json5-0.5.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>json5-2.1.1.tgz</b></p></summary>

<p>JSON for humans.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/json5/-/json5-2.1.1.tgz"">https://registry.npmjs.org/json5/-/json5-2.1.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/json5/package.json</p>
<p>

Dependency Hierarchy:
  - vuepress-1.2.0.tgz (Root Library)
    - core-1.3.0.tgz
      - core-7.8.4.tgz
        - :x: **json5-2.1.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>json5-1.0.1.tgz</b></p></summary>

<p>JSON for humans.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/json5/-/json5-1.0.1.tgz"">https://registry.npmjs.org/json5/-/json5-1.0.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/loader-utils/node_modules/json5/package.json</p>
<p>

Dependency Hierarchy:
  - vuepress-1.2.0.tgz (Root Library)
    - core-1.3.0.tgz
      - markdown-loader-1.3.0.tgz
        - loader-utils-1.2.3.tgz
          - :x: **json5-1.0.1.tgz** (Vulnerable Library)
</details>

<p>Found in HEAD commit: <a href=""https://github.com/billmcchesney1/davinci/commit/40c2bf435e91fe54575f47a7d13aef79ce92ae42"">40c2bf435e91fe54575f47a7d13aef79ce92ae42</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>  
  
JSON5 is an extension to the popular JSON file format that aims to be easier to write and maintain by hand (e.g. for config files). The `parse` method of the JSON5 library before and including version `2.2.1` does not restrict parsing of keys named `__proto__`, allowing specially crafted strings to pollute the prototype of the resulting object. This vulnerability pollutes the prototype of the object returned by `JSON5.parse` and not the global Object prototype, which is the commonly understood definition of Prototype Pollution. However, polluting the prototype of a single object can have significant security impact for an application if the object is later used in trusted operations. This vulnerability could allow an attacker to set arbitrary and unexpected keys on the object returned from `JSON5.parse`. The actual impact will depend on how applications utilize the returned object and how they filter unwanted keys, but could include denial of service, cross-site scripting, elevation of privilege, and in extreme cases, remote code execution. `JSON5.parse` should restrict parsing of `__proto__` keys when parsing JSON strings to objects. As a point of reference, the `JSON.parse` method included in JavaScript ignores `__proto__` keys. Simply changing `JSON5.parse` to `JSON.parse` in the examples above mitigates this vulnerability. This vulnerability is patched in json5 version 2.2.2 and later.

<p>Publish Date: 2022-12-24
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-46175>CVE-2022-46175</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.1</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: Low
  - 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://www.cve.org/CVERecord?id=CVE-2022-46175"">https://www.cve.org/CVERecord?id=CVE-2022-46175</a></p>
<p>Release Date: 2022-12-24</p>
<p>Fix Resolution: json5 - 2.2.2</p>

</p>
</details>
<p></p>
",True,"CVE-2022-46175 (High) detected in multiple libraries - ## CVE-2022-46175 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>json5-0.5.1.tgz</b>, <b>json5-2.1.1.tgz</b>, <b>json5-1.0.1.tgz</b></p></summary>
<p>

<details><summary><b>json5-0.5.1.tgz</b></p></summary>

<p>JSON for the ES5 era.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/json5/-/json5-0.5.1.tgz"">https://registry.npmjs.org/json5/-/json5-0.5.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/vuepress-html-webpack-plugin/node_modules/json5/package.json</p>
<p>

Dependency Hierarchy:
  - vuepress-1.2.0.tgz (Root Library)
    - core-1.3.0.tgz
      - vuepress-html-webpack-plugin-3.2.0.tgz
        - loader-utils-0.2.17.tgz
          - :x: **json5-0.5.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>json5-2.1.1.tgz</b></p></summary>

<p>JSON for humans.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/json5/-/json5-2.1.1.tgz"">https://registry.npmjs.org/json5/-/json5-2.1.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/json5/package.json</p>
<p>

Dependency Hierarchy:
  - vuepress-1.2.0.tgz (Root Library)
    - core-1.3.0.tgz
      - core-7.8.4.tgz
        - :x: **json5-2.1.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>json5-1.0.1.tgz</b></p></summary>

<p>JSON for humans.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/json5/-/json5-1.0.1.tgz"">https://registry.npmjs.org/json5/-/json5-1.0.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/loader-utils/node_modules/json5/package.json</p>
<p>

Dependency Hierarchy:
  - vuepress-1.2.0.tgz (Root Library)
    - core-1.3.0.tgz
      - markdown-loader-1.3.0.tgz
        - loader-utils-1.2.3.tgz
          - :x: **json5-1.0.1.tgz** (Vulnerable Library)
</details>

<p>Found in HEAD commit: <a href=""https://github.com/billmcchesney1/davinci/commit/40c2bf435e91fe54575f47a7d13aef79ce92ae42"">40c2bf435e91fe54575f47a7d13aef79ce92ae42</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>  
  
JSON5 is an extension to the popular JSON file format that aims to be easier to write and maintain by hand (e.g. for config files). The `parse` method of the JSON5 library before and including version `2.2.1` does not restrict parsing of keys named `__proto__`, allowing specially crafted strings to pollute the prototype of the resulting object. This vulnerability pollutes the prototype of the object returned by `JSON5.parse` and not the global Object prototype, which is the commonly understood definition of Prototype Pollution. However, polluting the prototype of a single object can have significant security impact for an application if the object is later used in trusted operations. This vulnerability could allow an attacker to set arbitrary and unexpected keys on the object returned from `JSON5.parse`. The actual impact will depend on how applications utilize the returned object and how they filter unwanted keys, but could include denial of service, cross-site scripting, elevation of privilege, and in extreme cases, remote code execution. `JSON5.parse` should restrict parsing of `__proto__` keys when parsing JSON strings to objects. As a point of reference, the `JSON.parse` method included in JavaScript ignores `__proto__` keys. Simply changing `JSON5.parse` to `JSON.parse` in the examples above mitigates this vulnerability. This vulnerability is patched in json5 version 2.2.2 and later.

<p>Publish Date: 2022-12-24
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-46175>CVE-2022-46175</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.1</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: Low
  - 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://www.cve.org/CVERecord?id=CVE-2022-46175"">https://www.cve.org/CVERecord?id=CVE-2022-46175</a></p>
<p>Release Date: 2022-12-24</p>
<p>Fix Resolution: json5 - 2.2.2</p>

</p>
</details>
<p></p>
",0,cve      high  detected in multiple libraries      cve       high severity vulnerability     vulnerable libraries            tgz            tgz            tgz                  tgz      json for the   era    library home page   a href     path to dependency file   package json   path to vulnerable library   node modules vuepress html webpack plugin node modules   package json     dependency hierarchy      vuepress       tgz  root library        core       tgz         vuepress html webpack plugin       tgz           loader utils       tgz              x            tgz    vulnerable library               tgz      json for humans    library home page   a href     path to dependency file   package json   path to vulnerable library   node modules   package json     dependency hierarchy      vuepress       tgz  root library        core       tgz         core       tgz            x            tgz    vulnerable library               tgz      json for humans    library home page   a href     path to dependency file   package json   path to vulnerable library   node modules loader utils node modules   package json     dependency hierarchy      vuepress       tgz  root library        core       tgz         markdown loader       tgz           loader utils       tgz              x            tgz    vulnerable library      found in head commit   a href     found in base branch   master              vulnerability details           is an extension to the popular json file format that aims to be easier to write and maintain by hand  e g  for config files   the  parse  method of the   library before and including version         does not restrict parsing of keys named    proto     allowing specially crafted strings to pollute the prototype of the resulting object  this vulnerability pollutes the prototype of the object returned by    parse  and not the global object prototype  which is the commonly understood definition of prototype pollution  however  polluting the prototype of a single object can have significant security impact for an application if the object is later used in trusted operations  this vulnerability could allow an attacker to set arbitrary and unexpected keys on the object returned from    parse   the actual impact will depend on how applications utilize the returned object and how they filter unwanted keys  but could include denial of service  cross site scripting  elevation of privilege  and in extreme cases  remote code execution     parse  should restrict parsing of    proto    keys when parsing json strings to objects  as a point of reference  the  json parse  method included in javascript ignores    proto    keys  simply changing    parse  to  json parse  in the examples above mitigates this vulnerability  this vulnerability is patched in   version       and later    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  low     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  low     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                     ,0
87957,8127703145.0,IssuesEvent,2018-08-17 09:03:10,TerriaJS/aremi-natmap,https://api.github.com/repos/TerriaJS/aremi-natmap,closed,AREMI v2018-03-26 pre-release test - Observation - Layer fail on 1st attempt but works fine on second,GA-testing,"This is confusing, generates error on 1st attempt but works fine on later attempts!!

For example:
Layer: Renewable Energy/Bioenergy/Victoria/Horticulture/Fruit and vegetable/Cull fruit
Layer: Renewable Energy/Bioenergy/Victoria/Municipal Solid Waste/Organics

![slide3](https://user-images.githubusercontent.com/22827786/38070274-e5dacee2-3366-11e8-98cc-3770500f7632.JPG)

![slide4](https://user-images.githubusercontent.com/22827786/38070237-b0d978e2-3366-11e8-948c-108a2f7e4ad9.JPG)

![slide5](https://user-images.githubusercontent.com/22827786/38070281-ec345ad8-3366-11e8-8276-d270fd299249.JPG)

![slide6](https://user-images.githubusercontent.com/22827786/38070285-f247dd1e-3366-11e8-9e38-3146e9a19897.JPG)




",1.0,"AREMI v2018-03-26 pre-release test - Observation - Layer fail on 1st attempt but works fine on second - This is confusing, generates error on 1st attempt but works fine on later attempts!!

For example:
Layer: Renewable Energy/Bioenergy/Victoria/Horticulture/Fruit and vegetable/Cull fruit
Layer: Renewable Energy/Bioenergy/Victoria/Municipal Solid Waste/Organics

![slide3](https://user-images.githubusercontent.com/22827786/38070274-e5dacee2-3366-11e8-98cc-3770500f7632.JPG)

![slide4](https://user-images.githubusercontent.com/22827786/38070237-b0d978e2-3366-11e8-948c-108a2f7e4ad9.JPG)

![slide5](https://user-images.githubusercontent.com/22827786/38070281-ec345ad8-3366-11e8-8276-d270fd299249.JPG)

![slide6](https://user-images.githubusercontent.com/22827786/38070285-f247dd1e-3366-11e8-9e38-3146e9a19897.JPG)




",0,aremi       pre release test   observation   layer fail on   attempt but works fine on second   this is confusing  generates error on   attempt but works fine on later attempts      for example   layer  renewable energy bioenergy victoria horticulture fruit and vegetable cull fruit  layer  renewable energy bioenergy victoria municipal solid waste organics                                          ,0
53210,7811867516.0,IssuesEvent,2018-06-12 11:36:55,golang/go,https://api.github.com/repos/golang/go,closed,"encoding/gob: no way to skip marshalling exported struct field, docs unclear that a struct must have minimum one exported field",Documentation NeedsDecision,"Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
go1.8

### What operating system and processor architecture are you using (`go env`)?
go env

set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\home\auld\godev\
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Use
rs\auld\AppData\Local\Temp\go-build485133467=/tmp/go-build -gno-record-gcc
-switches
set CXX=g++
set CGO_ENABLED=1
set PKG_CONFIG=pkg-config
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2


### What did you do?

The program should transmit its User struct and receive it via a fake network and print the transferred data. Line 15-17 of the below play area program contains three cases. The third case (3) works correctly and transfers all the data as expected. Case two (2) also transfers all the data but based on the documentation I believe only the values associated with exported field should be transferred. Case one (1) does not transfer any data, not even the exported fields from User. 

I believe both case 1 and 2 represent bugs.

If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.

 https://play.golang.org/p/Y7ZPpq9-8v

### What did you expect to see?

Case 1: &{Donald DuckPass []}
Case 2: &{Donald DuckPass [{ 2} { 1}]}
Case 3: &{Donald DuckPass [{1 2} {2 1}]}

### What did you see instead?

Case 1: 2009/11/10 23:00:00 encode error:gob: type main.j has no exported fields
Case 2: &{Donald DuckPass [{1 2} {2 1}]}
Case 3: &{Donald DuckPass [{1 2} {2 1}]}


",1.0,"encoding/gob: no way to skip marshalling exported struct field, docs unclear that a struct must have minimum one exported field - Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
go1.8

### What operating system and processor architecture are you using (`go env`)?
go env

set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\home\auld\godev\
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Use
rs\auld\AppData\Local\Temp\go-build485133467=/tmp/go-build -gno-record-gcc
-switches
set CXX=g++
set CGO_ENABLED=1
set PKG_CONFIG=pkg-config
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2


### What did you do?

The program should transmit its User struct and receive it via a fake network and print the transferred data. Line 15-17 of the below play area program contains three cases. The third case (3) works correctly and transfers all the data as expected. Case two (2) also transfers all the data but based on the documentation I believe only the values associated with exported field should be transferred. Case one (1) does not transfer any data, not even the exported fields from User. 

I believe both case 1 and 2 represent bugs.

If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.

 https://play.golang.org/p/Y7ZPpq9-8v

### What did you expect to see?

Case 1: &{Donald DuckPass []}
Case 2: &{Donald DuckPass [{ 2} { 1}]}
Case 3: &{Donald DuckPass [{1 2} {2 1}]}

### What did you see instead?

Case 1: 2009/11/10 23:00:00 encode error:gob: type main.j has no exported fields
Case 2: &{Donald DuckPass [{1 2} {2 1}]}
Case 3: &{Donald DuckPass [{1 2} {2 1}]}


",1,encoding gob  no way to skip marshalling exported struct field  docs unclear that a struct must have minimum one exported field   please answer these questions before submitting your issue  thanks         what version of go are you using   go version                what operating system and processor architecture are you using   go env     go env    set goarch    set gobin   set goexe  exe  set gohostarch    set gohostos windows  set goos windows  set gopath c  home auld godev   set gorace   set goroot c  go  set gotooldir c  go pkg tool windows    set gccgo gccgo  set cc gcc  set gogccflags     mthreads  fmessage length    fdebug prefix map c  use  rs auld appdata local temp go    tmp go build  gno record gcc   switches  set cxx g    set cgo enabled    set pkg config pkg config  set cgo cflags  g     set cgo cppflags   set cgo cxxflags  g     set cgo fflags  g     set cgo ldflags  g             what did you do     the program should transmit its user struct and receive it via a fake network and print the transferred data  line     of the below play area program contains three cases  the third case     works correctly and transfers all the data as expected  case two     also transfers all the data but based on the documentation i believe only the values associated with exported field should be transferred  case one     does not transfer any data  not even the exported fields from user      i believe both case   and   represent bugs     if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best               what did you expect to see     case      donald duckpass     case      donald duckpass     case      donald duckpass           what did you see instead     case                encode error gob  type main j has no exported fields  case      donald duckpass     case      donald duckpass         ,1
327587,24143862200.0,IssuesEvent,2022-09-21 16:55:50,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/gopls: index out of range while trying to run textDocument/codeAction on entire document,Documentation gopls Tools,"<!--
Please answer these questions before submitting your issue. Thanks!
-->

### gopls version

<!--
Output of `gopls -v version` on the command line
-->

```
Build info
----------
golang.org/x/tools/gopls master
    golang.org/x/tools/gopls@(devel)
    github.com/BurntSushi/toml@v1.2.0 h1:Rt8g24XnyGTyglgET/PRUNlrUeu9F5L+7FilkXfZgs0=
    github.com/google/go-cmp@v0.5.8 h1:e6P7q2lk1O+qJJb4BtCQXlK8vWEO8V1ZeuEdJNOqZyg=
    github.com/sergi/go-diff@v1.1.0 h1:we8PVUC3FE2uYfodKH/nBHMSetSfHDR6scGdBi+erh0=
    golang.org/x/exp@v0.0.0-20220722155223-a9213eeb770e h1:+WEEuIdZHnUeJJmEUjyYC2gfUMj69yZXw17EnHg/otA=
    golang.org/x/exp/typeparams@v0.0.0-20220722155223-a9213eeb770e h1:7Xs2YCOpMlNqSQSmrrnhlzBXIE/bpMecZplbLePTJvE=
    golang.org/x/mod@v0.6.0-dev.0.20220419223038-86c51ed26bb4 h1:6zppjxzCulZykYSLyVDYbneBfbaBIQPYMevg0bEwv2s=
    golang.org/x/sync@v0.0.0-20220722155255-886fb9371eb4 h1:uVc8UZUe6tr40fFVnUP5Oj+veunVezqYl9z7DYw9xzw=
    golang.org/x/sys@v0.0.0-20220808155132-1c4a2a72c664 h1:v1W7bwXHsnLLloWYTVEdvGvA7BHMeBYsPcF0GLDxIRs=
    golang.org/x/text@v0.3.7 h1:olpwvP2KacW1ZWvsR7uQhoyTYvKAupfQrRGBFM352Gk=
    golang.org/x/tools@v0.1.13-0.20220810174125-0ad49fdeb955 => ../
    golang.org/x/vuln@v0.0.0-20220919155316-41b1fc70d0a6 h1:tQFrcJZ95V1wiLLPoAIaEuEVXJ7JkhbZI4Hws7Fx69c=
    honnef.co/go/tools@v0.3.3 h1:oDx7VAwstgpYpb3wv0oxiZlxY+foCpRAwY7Vk6XpAgA=
    mvdan.cc/gofumpt@v0.3.1 h1:avhhrOmv0IuvQVK7fvwV91oFSGAk5/6Po8GXTzICeu8=
    mvdan.cc/xurls/v2@v2.4.0 h1:tzxjVAj+wSBmDcF6zBB7/myTy3gX9xvi8Tyr28AuQgc=
go: devel go1.20-d11c58eedb Wed Sep 21 01:56:24 2022 +0000
```

### go env

<!--
Output of `go env` on the command line in your workspace directory
-->

```
％ go env
GO111MODULE=""""
GOARCH=""arm64""
GOBIN=""/Users/fsouza/bin""
GOCACHE=""/Users/fsouza/Library/Caches/go-build""
GOENV=""/Users/fsouza/Library/Application Support/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""-modcacherw""
GOHOSTARCH=""arm64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/fsouza/.cache/go/path/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/fsouza/.cache/go/path""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/Users/fsouza/.cache/go/sdk/gotip""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/Users/fsouza/.cache/go/sdk/gotip/pkg/tool/darwin_arm64""
GOVCS=""""
GOVERSION=""devel go1.20-d11c58eedb Wed Sep 21 01:56:24 2022 +0000""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/fsouza/Projects/os/p/fake-gcs-server/go.mod""
GOWORK=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/rz/8d0l4yp51sd3jh9f34x7pkg80000gn/T/go-build3810227374=/tmp/go-build -gno-record-gcc-switches -fno-common""
```

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is better.
A failing unit test is the best.
-->

Invoke `textDocument/codeAction` passing a range that covers the entire file
(following the [spec for
range](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#range),
which means that the end position is exclusive). Here's what the range I'm
sending looks like (in JSON-ish):

```json
{
  ... other fields
  ""range"": {
    ""start"": {
      ""line"": 0,
      ""character"": 0
    },
    ""end"": {
      ""line"": $N,
      ""character"": 0
    }
  }
}
```

Where `$N` = number of lines in the file.

For full reproduction steps, see ""Editor & Settings"" below.

### What did you expect to see?

The list of code actions available in the entire file.

### What did you see instead?

gopls panics with an index out of range. Since this is a panic, the stacktrace
isn't available in the logs for gopls, but I'm able to get the process output
from my editor's logs:

```
[ERROR][2022-09-21 09:02:06] .../vim/lsp/rpc.lua:733    ""rpc""   ""/Users/fsouza/.cache/nvim/langservers/bin/gopls""  ""stderr""        ""panic: runtime error: index out of range [2] with length 2\n\ngoroutine 8707 [running]:\ngolang.org/x/tools/gopls/internal/lsp/source.adjustRangeForCommentsAndWhiteSpace({0x140038d9380?, 0x69?, 0x1?}, 0x140038d9380, {0x14001dea000, 0xbc7, 0x140000f4640?}, 0x1400370b400)\n\t/Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/source/extract.go:704 +0x3e0\ngolang.org/x/tools/gopls/internal/lsp/source.CanExtractFunction(0x140038d9380, {0x140038d9380, 0x92e342, 0x92eef2}, {0x14001dea000, 0xbc7, 0xbc8""
[ERROR][2022-09-21 09:02:06] .../vim/lsp/rpc.lua:733    ""rpc""   ""/Users/fsouza/.cache/nvim/langservers/bin/gopls""  ""stderr""        ""}, 0x102f5bfe4?)\n\t/Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/source/extract.go:984 +0xc4\ngolang.org/x/tools/gopls/internal/lsp.extractionFixes({0x1034480e0, 0x1400d856440}, {0x103453b18?, 0x140038e2640?}, {0x103408780?, 0x0?}, {0x140069ec9c0, 0x3a}, {{0x0?, 0x0?}, ...})\n\t/Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/code_action.go:301 +0x180\ngolang.org/x/tools/gopls/internal/lsp.(*Server).codeAction(0x1400d8b4180?, {0x1034480e0, 0x1400d856440}, 0x1400d8b4180)\n\t/Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/code_action.go:196 +0x13c4\ngolang.org/x/tools/gopls/internal/lsp.(*Server).CodeAction(0x14000138210?, {0x1034480e0?, 0x1400d856440?}, 0x1032e84c0?)\n\t/Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/server_gen.go:16 +0x24\ngolang.org/x/tools/gopls/internal/lsp/protocol.serverDispatch({0x1034480e0, 0x1400d856440}, {0x1034571a8, 0x140004f2360}, 0x1400d66e750, {0x103448498, 0x1400d8562c0})\n\t/Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/protocol/tsserver.go:239 +0x18cc\ngolang.org/x/tools/gopls/internal/lsp/protocol.ServerHandler.func1({0x1034480e0, 0x1400d856440}, 0x1400d66e750, {0x103448498, 0x1400d8562c0})\n\t/Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/protocol/protocol.go:157 +0x6c\ngolang.org/x/tools/gopls/internal/lsp/lsprpc.handshaker.func1({0x1034480e0, 0x1400d856440}, 0x1400d66e750, {0x103448498?, 0x1400d8562c0?})\n\t/Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/lsprpc/lsprpc.go:515 +0x768\ngolang.org/x/tools/internal/jsonrpc2.MustReplyHandler.func1({0x1034480e0, 0x1400d856440}, 0x1400d5bd128, {0x103448498?, 0x1400d8562c0?})\n\t/Users/fsouza/.cache/nvim/langservers/tools/internal/jsonrpc2/handler.go:35 +0xf0\ngolang.org/x/tools/internal/jsonrpc2.AsyncHandler.func1.2()\n\t/Users/fsouza/.cache/nvim/langservers/tools/internal/jsonrpc2/handler.go:103 +0x90\ncreated by golang.org/x/tools/internal/jsonrpc2.AsyncHandler.func1\n\t/Users/fsouza/.cache/nvim/langservers/tools/internal/jsonrpc2/handler.go:100 +0x1dc\n""
```

In order to make it easier to read, I've also expanded the two lines above. This is the output from gopls:

```
panic: runtime error: index out of range [2] with length 2

goroutine 8707 [running]:
golang.org/x/tools/gopls/internal/lsp/source.adjustRangeForCommentsAndWhiteSpace({0x140038d9380?, 0x69?, 0x1?}, 0x140038d9380, {0x14001dea000, 0xbc7, 0x140000f4640?}, 0x1400370b400)
        /Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/source/extract.go:704 +0x3e0
golang.org/x/tools/gopls/internal/lsp/source.CanExtractFunction(0x140038d9380, {0x140038d9380, 0x92e342, 0x92eef2}, {0x14001dea000, 0xbc7, 0xbc8}, 0x102f5bfe4?)
        /Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/source/extract.go:984 +0xc4
golang.org/x/tools/gopls/internal/lsp.extractionFixes({0x1034480e0, 0x1400d856440}, {0x103453b18?, 0x140038e2640?}, {0x103408780?, 0x0?}, {0x140069ec9c0, 0x3a}, {{0x0?, 0x0?}, ...})
        /Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/code_action.go:301 +0x180
golang.org/x/tools/gopls/internal/lsp.(*Server).codeAction(0x1400d8b4180?, {0x1034480e0, 0x1400d856440}, 0x1400d8b4180)
        /Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/code_action.go:196 +0x13c4
golang.org/x/tools/gopls/internal/lsp.(*Server).CodeAction(0x14000138210?, {0x1034480e0?, 0x1400d856440?}, 0x1032e84c0?)
        /Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/server_gen.go:16 +0x24
golang.org/x/tools/gopls/internal/lsp/protocol.serverDispatch({0x1034480e0, 0x1400d856440}, {0x1034571a8, 0x140004f2360}, 0x1400d66e750, {0x103448498, 0x1400d8562c0})
        /Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/protocol/tsserver.go:239 +0x18cc
golang.org/x/tools/gopls/internal/lsp/protocol.ServerHandler.func1({0x1034480e0, 0x1400d856440}, 0x1400d66e750, {0x103448498, 0x1400d8562c0})
        /Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/protocol/protocol.go:157 +0x6c
golang.org/x/tools/gopls/internal/lsp/lsprpc.handshaker.func1({0x1034480e0, 0x1400d856440}, 0x1400d66e750, {0x103448498?, 0x1400d8562c0?})
        /Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/lsprpc/lsprpc.go:515 +0x768
golang.org/x/tools/internal/jsonrpc2.MustReplyHandler.func1({0x1034480e0, 0x1400d856440}, 0x1400d5bd128, {0x103448498?, 0x1400d8562c0?})
        /Users/fsouza/.cache/nvim/langservers/tools/internal/jsonrpc2/handler.go:35 +0xf0
golang.org/x/tools/internal/jsonrpc2.AsyncHandler.func1.2()
        /Users/fsouza/.cache/nvim/langservers/tools/internal/jsonrpc2/handler.go:103 +0x90
created by golang.org/x/tools/internal/jsonrpc2.AsyncHandler.func1
        /Users/fsouza/.cache/nvim/langservers/tools/internal/jsonrpc2/handler.go:100 +0x1dc
```

This is a regression and I was able to bisect it to this commit:

```
fdf581fdab091d9dd12425be67e59db67a2ad501 is the first bad commit
commit fdf581fdab091d9dd12425be67e59db67a2ad501
Author: Suzy Mueller <suzmue@golang.org>
Date:   Thu Sep 23 19:52:37 2021 -0600

    internal/lsp: allow extract func ranges to begin/end with comments

    CanExtract strips of the whitespace on either end of the range in
    order to get an exact range to extract to function. We can do the
    same thing for comments by moving adjusting the range if the start
    or end positions contain the position.

    Updates golang/go#37170
    Fixes golang/go#54816

    Change-Id: I3508c822434400f084a273730380c89611803e97
    Reviewed-on: https://go-review.googlesource.com/c/tools/+/351989
    Reviewed-by: Robert Findley <rfindley@google.com>
    gopls-CI: kokoro <noreply+kokoro@google.com>
    Run-TryBot: Suzy Mueller <suzmue@golang.org>
    TryBot-Result: Gopher Robot <gobot@golang.org>

 gopls/internal/lsp/source/extract.go               | 94 +++++++++++++++-------
 .../extract_function/extract_basic_comment.go      | 10 ++-
 .../extract_basic_comment.go.golden                | 46 ++++++++++-
 gopls/internal/lsp/testdata/summary.txt.golden     |  2 +-
 .../lsp/testdata/summary_go1.18.txt.golden         |  2 +-
 5 files changed, 115 insertions(+), 39 deletions(-)
```

### Editor and settings

<!--
Your editor and any settings you have configured (for example, your VSCode settings.json file)
-->

This is neovim. It can be reproduced with just gopls installed. Minimal
reproducer in neovim:
https://gist.github.com/fsouza/01bf91accbce744ae528bad2472c79f3

How to reproduce in neovim with the config file above, using some Go repo (I
tested with [fake-gcs-server](https://github.com/fsouza/fake-gcs-server), but
I suspect that any project/file will do):

```
nvim -u minimal_init.lua
:e main.go
:lua document_code_action()
```

### Logs

<!--
If possible please include gopls logs. Instructions for capturing them can be found here:
https://github.com/golang/tools/blob/master/gopls/doc/troubleshooting.md#capture-logs
-->

Logs from gopls: https://gist.github.com/fsouza/ecc217ae4f2bbdc4dbcf2033c6b34581

Logs from the editor (includes the process stderr with the crash at the very end): https://gist.github.com/fsouza/9700b8daa4658fb226440fbedf1dbff5",1.0,"x/tools/gopls: index out of range while trying to run textDocument/codeAction on entire document - <!--
Please answer these questions before submitting your issue. Thanks!
-->

### gopls version

<!--
Output of `gopls -v version` on the command line
-->

```
Build info
----------
golang.org/x/tools/gopls master
    golang.org/x/tools/gopls@(devel)
    github.com/BurntSushi/toml@v1.2.0 h1:Rt8g24XnyGTyglgET/PRUNlrUeu9F5L+7FilkXfZgs0=
    github.com/google/go-cmp@v0.5.8 h1:e6P7q2lk1O+qJJb4BtCQXlK8vWEO8V1ZeuEdJNOqZyg=
    github.com/sergi/go-diff@v1.1.0 h1:we8PVUC3FE2uYfodKH/nBHMSetSfHDR6scGdBi+erh0=
    golang.org/x/exp@v0.0.0-20220722155223-a9213eeb770e h1:+WEEuIdZHnUeJJmEUjyYC2gfUMj69yZXw17EnHg/otA=
    golang.org/x/exp/typeparams@v0.0.0-20220722155223-a9213eeb770e h1:7Xs2YCOpMlNqSQSmrrnhlzBXIE/bpMecZplbLePTJvE=
    golang.org/x/mod@v0.6.0-dev.0.20220419223038-86c51ed26bb4 h1:6zppjxzCulZykYSLyVDYbneBfbaBIQPYMevg0bEwv2s=
    golang.org/x/sync@v0.0.0-20220722155255-886fb9371eb4 h1:uVc8UZUe6tr40fFVnUP5Oj+veunVezqYl9z7DYw9xzw=
    golang.org/x/sys@v0.0.0-20220808155132-1c4a2a72c664 h1:v1W7bwXHsnLLloWYTVEdvGvA7BHMeBYsPcF0GLDxIRs=
    golang.org/x/text@v0.3.7 h1:olpwvP2KacW1ZWvsR7uQhoyTYvKAupfQrRGBFM352Gk=
    golang.org/x/tools@v0.1.13-0.20220810174125-0ad49fdeb955 => ../
    golang.org/x/vuln@v0.0.0-20220919155316-41b1fc70d0a6 h1:tQFrcJZ95V1wiLLPoAIaEuEVXJ7JkhbZI4Hws7Fx69c=
    honnef.co/go/tools@v0.3.3 h1:oDx7VAwstgpYpb3wv0oxiZlxY+foCpRAwY7Vk6XpAgA=
    mvdan.cc/gofumpt@v0.3.1 h1:avhhrOmv0IuvQVK7fvwV91oFSGAk5/6Po8GXTzICeu8=
    mvdan.cc/xurls/v2@v2.4.0 h1:tzxjVAj+wSBmDcF6zBB7/myTy3gX9xvi8Tyr28AuQgc=
go: devel go1.20-d11c58eedb Wed Sep 21 01:56:24 2022 +0000
```

### go env

<!--
Output of `go env` on the command line in your workspace directory
-->

```
％ go env
GO111MODULE=""""
GOARCH=""arm64""
GOBIN=""/Users/fsouza/bin""
GOCACHE=""/Users/fsouza/Library/Caches/go-build""
GOENV=""/Users/fsouza/Library/Application Support/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""-modcacherw""
GOHOSTARCH=""arm64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/fsouza/.cache/go/path/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/fsouza/.cache/go/path""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/Users/fsouza/.cache/go/sdk/gotip""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/Users/fsouza/.cache/go/sdk/gotip/pkg/tool/darwin_arm64""
GOVCS=""""
GOVERSION=""devel go1.20-d11c58eedb Wed Sep 21 01:56:24 2022 +0000""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/fsouza/Projects/os/p/fake-gcs-server/go.mod""
GOWORK=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/rz/8d0l4yp51sd3jh9f34x7pkg80000gn/T/go-build3810227374=/tmp/go-build -gno-record-gcc-switches -fno-common""
```

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is better.
A failing unit test is the best.
-->

Invoke `textDocument/codeAction` passing a range that covers the entire file
(following the [spec for
range](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#range),
which means that the end position is exclusive). Here's what the range I'm
sending looks like (in JSON-ish):

```json
{
  ... other fields
  ""range"": {
    ""start"": {
      ""line"": 0,
      ""character"": 0
    },
    ""end"": {
      ""line"": $N,
      ""character"": 0
    }
  }
}
```

Where `$N` = number of lines in the file.

For full reproduction steps, see ""Editor & Settings"" below.

### What did you expect to see?

The list of code actions available in the entire file.

### What did you see instead?

gopls panics with an index out of range. Since this is a panic, the stacktrace
isn't available in the logs for gopls, but I'm able to get the process output
from my editor's logs:

```
[ERROR][2022-09-21 09:02:06] .../vim/lsp/rpc.lua:733    ""rpc""   ""/Users/fsouza/.cache/nvim/langservers/bin/gopls""  ""stderr""        ""panic: runtime error: index out of range [2] with length 2\n\ngoroutine 8707 [running]:\ngolang.org/x/tools/gopls/internal/lsp/source.adjustRangeForCommentsAndWhiteSpace({0x140038d9380?, 0x69?, 0x1?}, 0x140038d9380, {0x14001dea000, 0xbc7, 0x140000f4640?}, 0x1400370b400)\n\t/Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/source/extract.go:704 +0x3e0\ngolang.org/x/tools/gopls/internal/lsp/source.CanExtractFunction(0x140038d9380, {0x140038d9380, 0x92e342, 0x92eef2}, {0x14001dea000, 0xbc7, 0xbc8""
[ERROR][2022-09-21 09:02:06] .../vim/lsp/rpc.lua:733    ""rpc""   ""/Users/fsouza/.cache/nvim/langservers/bin/gopls""  ""stderr""        ""}, 0x102f5bfe4?)\n\t/Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/source/extract.go:984 +0xc4\ngolang.org/x/tools/gopls/internal/lsp.extractionFixes({0x1034480e0, 0x1400d856440}, {0x103453b18?, 0x140038e2640?}, {0x103408780?, 0x0?}, {0x140069ec9c0, 0x3a}, {{0x0?, 0x0?}, ...})\n\t/Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/code_action.go:301 +0x180\ngolang.org/x/tools/gopls/internal/lsp.(*Server).codeAction(0x1400d8b4180?, {0x1034480e0, 0x1400d856440}, 0x1400d8b4180)\n\t/Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/code_action.go:196 +0x13c4\ngolang.org/x/tools/gopls/internal/lsp.(*Server).CodeAction(0x14000138210?, {0x1034480e0?, 0x1400d856440?}, 0x1032e84c0?)\n\t/Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/server_gen.go:16 +0x24\ngolang.org/x/tools/gopls/internal/lsp/protocol.serverDispatch({0x1034480e0, 0x1400d856440}, {0x1034571a8, 0x140004f2360}, 0x1400d66e750, {0x103448498, 0x1400d8562c0})\n\t/Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/protocol/tsserver.go:239 +0x18cc\ngolang.org/x/tools/gopls/internal/lsp/protocol.ServerHandler.func1({0x1034480e0, 0x1400d856440}, 0x1400d66e750, {0x103448498, 0x1400d8562c0})\n\t/Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/protocol/protocol.go:157 +0x6c\ngolang.org/x/tools/gopls/internal/lsp/lsprpc.handshaker.func1({0x1034480e0, 0x1400d856440}, 0x1400d66e750, {0x103448498?, 0x1400d8562c0?})\n\t/Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/lsprpc/lsprpc.go:515 +0x768\ngolang.org/x/tools/internal/jsonrpc2.MustReplyHandler.func1({0x1034480e0, 0x1400d856440}, 0x1400d5bd128, {0x103448498?, 0x1400d8562c0?})\n\t/Users/fsouza/.cache/nvim/langservers/tools/internal/jsonrpc2/handler.go:35 +0xf0\ngolang.org/x/tools/internal/jsonrpc2.AsyncHandler.func1.2()\n\t/Users/fsouza/.cache/nvim/langservers/tools/internal/jsonrpc2/handler.go:103 +0x90\ncreated by golang.org/x/tools/internal/jsonrpc2.AsyncHandler.func1\n\t/Users/fsouza/.cache/nvim/langservers/tools/internal/jsonrpc2/handler.go:100 +0x1dc\n""
```

In order to make it easier to read, I've also expanded the two lines above. This is the output from gopls:

```
panic: runtime error: index out of range [2] with length 2

goroutine 8707 [running]:
golang.org/x/tools/gopls/internal/lsp/source.adjustRangeForCommentsAndWhiteSpace({0x140038d9380?, 0x69?, 0x1?}, 0x140038d9380, {0x14001dea000, 0xbc7, 0x140000f4640?}, 0x1400370b400)
        /Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/source/extract.go:704 +0x3e0
golang.org/x/tools/gopls/internal/lsp/source.CanExtractFunction(0x140038d9380, {0x140038d9380, 0x92e342, 0x92eef2}, {0x14001dea000, 0xbc7, 0xbc8}, 0x102f5bfe4?)
        /Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/source/extract.go:984 +0xc4
golang.org/x/tools/gopls/internal/lsp.extractionFixes({0x1034480e0, 0x1400d856440}, {0x103453b18?, 0x140038e2640?}, {0x103408780?, 0x0?}, {0x140069ec9c0, 0x3a}, {{0x0?, 0x0?}, ...})
        /Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/code_action.go:301 +0x180
golang.org/x/tools/gopls/internal/lsp.(*Server).codeAction(0x1400d8b4180?, {0x1034480e0, 0x1400d856440}, 0x1400d8b4180)
        /Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/code_action.go:196 +0x13c4
golang.org/x/tools/gopls/internal/lsp.(*Server).CodeAction(0x14000138210?, {0x1034480e0?, 0x1400d856440?}, 0x1032e84c0?)
        /Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/server_gen.go:16 +0x24
golang.org/x/tools/gopls/internal/lsp/protocol.serverDispatch({0x1034480e0, 0x1400d856440}, {0x1034571a8, 0x140004f2360}, 0x1400d66e750, {0x103448498, 0x1400d8562c0})
        /Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/protocol/tsserver.go:239 +0x18cc
golang.org/x/tools/gopls/internal/lsp/protocol.ServerHandler.func1({0x1034480e0, 0x1400d856440}, 0x1400d66e750, {0x103448498, 0x1400d8562c0})
        /Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/protocol/protocol.go:157 +0x6c
golang.org/x/tools/gopls/internal/lsp/lsprpc.handshaker.func1({0x1034480e0, 0x1400d856440}, 0x1400d66e750, {0x103448498?, 0x1400d8562c0?})
        /Users/fsouza/.cache/nvim/langservers/tools/gopls/internal/lsp/lsprpc/lsprpc.go:515 +0x768
golang.org/x/tools/internal/jsonrpc2.MustReplyHandler.func1({0x1034480e0, 0x1400d856440}, 0x1400d5bd128, {0x103448498?, 0x1400d8562c0?})
        /Users/fsouza/.cache/nvim/langservers/tools/internal/jsonrpc2/handler.go:35 +0xf0
golang.org/x/tools/internal/jsonrpc2.AsyncHandler.func1.2()
        /Users/fsouza/.cache/nvim/langservers/tools/internal/jsonrpc2/handler.go:103 +0x90
created by golang.org/x/tools/internal/jsonrpc2.AsyncHandler.func1
        /Users/fsouza/.cache/nvim/langservers/tools/internal/jsonrpc2/handler.go:100 +0x1dc
```

This is a regression and I was able to bisect it to this commit:

```
fdf581fdab091d9dd12425be67e59db67a2ad501 is the first bad commit
commit fdf581fdab091d9dd12425be67e59db67a2ad501
Author: Suzy Mueller <suzmue@golang.org>
Date:   Thu Sep 23 19:52:37 2021 -0600

    internal/lsp: allow extract func ranges to begin/end with comments

    CanExtract strips of the whitespace on either end of the range in
    order to get an exact range to extract to function. We can do the
    same thing for comments by moving adjusting the range if the start
    or end positions contain the position.

    Updates golang/go#37170
    Fixes golang/go#54816

    Change-Id: I3508c822434400f084a273730380c89611803e97
    Reviewed-on: https://go-review.googlesource.com/c/tools/+/351989
    Reviewed-by: Robert Findley <rfindley@google.com>
    gopls-CI: kokoro <noreply+kokoro@google.com>
    Run-TryBot: Suzy Mueller <suzmue@golang.org>
    TryBot-Result: Gopher Robot <gobot@golang.org>

 gopls/internal/lsp/source/extract.go               | 94 +++++++++++++++-------
 .../extract_function/extract_basic_comment.go      | 10 ++-
 .../extract_basic_comment.go.golden                | 46 ++++++++++-
 gopls/internal/lsp/testdata/summary.txt.golden     |  2 +-
 .../lsp/testdata/summary_go1.18.txt.golden         |  2 +-
 5 files changed, 115 insertions(+), 39 deletions(-)
```

### Editor and settings

<!--
Your editor and any settings you have configured (for example, your VSCode settings.json file)
-->

This is neovim. It can be reproduced with just gopls installed. Minimal
reproducer in neovim:
https://gist.github.com/fsouza/01bf91accbce744ae528bad2472c79f3

How to reproduce in neovim with the config file above, using some Go repo (I
tested with [fake-gcs-server](https://github.com/fsouza/fake-gcs-server), but
I suspect that any project/file will do):

```
nvim -u minimal_init.lua
:e main.go
:lua document_code_action()
```

### Logs

<!--
If possible please include gopls logs. Instructions for capturing them can be found here:
https://github.com/golang/tools/blob/master/gopls/doc/troubleshooting.md#capture-logs
-->

Logs from gopls: https://gist.github.com/fsouza/ecc217ae4f2bbdc4dbcf2033c6b34581

Logs from the editor (includes the process stderr with the crash at the very end): https://gist.github.com/fsouza/9700b8daa4658fb226440fbedf1dbff5",1,x tools gopls  index out of range while trying to run textdocument codeaction on entire document         please answer these questions before submitting your issue  thanks              gopls version          output of  gopls  v version  on the command line              build info              golang org x tools gopls master      golang org x tools gopls  devel       github com burntsushi toml                     github com google go cmp                   github com sergi go diff                     golang org x exp                ota       golang org x exp typeparams               bpmeczplbleptjve       golang org x mod       dev                 golang org x sync                       golang org x sys                     golang org x text                 golang org x tools                         golang org x vuln                     honnef co go tools                   mvdan cc gofumpt                   mvdan cc xurls           tzxjvaj       go  devel       wed sep                          go env          output of  go env  on the command line in your workspace directory              ％ go env        goarch      gobin   users fsouza bin   gocache   users fsouza library caches go build   goenv   users fsouza library application support go env   goexe     goexperiment     goflags   modcacherw   gohostarch      gohostos  darwin   goinsecure     gomodcache   users fsouza  cache go path pkg mod   gonoproxy     gonosumdb     goos  darwin   gopath   users fsouza  cache go path   goprivate     goproxy     goroot   users fsouza  cache go sdk gotip   gosumdb  sum golang org   gotmpdir     gotooldir   users fsouza  cache go sdk gotip pkg tool darwin     govcs     goversion  devel       wed sep                gccgo  gccgo   ar  ar   cc  clang   cxx  clang     cgo enabled      gomod   users fsouza projects os p fake gcs server go mod   gowork     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic  arch    pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders rz   t go    tmp go build  gno record gcc switches  fno common              what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on go dev play is better   a failing unit test is the best          invoke  textdocument codeaction  passing a range that covers the entire file   following the  spec for  range     which means that the end position is exclusive   here s what the range i m  sending looks like  in json ish         json           other fields     range           start             line              character                   end             line    n          character                            where   n    number of lines in the file     for full reproduction steps  see  editor   settings  below         what did you expect to see     the list of code actions available in the entire file         what did you see instead     gopls panics with an index out of range  since this is a panic  the stacktrace  isn t available in the logs for gopls  but i m able to get the process output  from my editor s logs                 vim lsp rpc lua       rpc      users fsouza  cache nvim langservers bin gopls    stderr          panic  runtime error  index out of range   with length   n ngoroutine      ngolang org x tools gopls internal lsp source adjustrangeforcommentsandwhitespace                                 n t users fsouza  cache nvim langservers tools gopls internal lsp source extract go      ngolang org x tools gopls internal lsp source canextractfunction                                 vim lsp rpc lua       rpc      users fsouza  cache nvim langservers bin gopls    stderr                 n t users fsouza  cache nvim langservers tools gopls internal lsp source extract go      ngolang org x tools gopls internal lsp extractionfixes                                                      n t users fsouza  cache nvim langservers tools gopls internal lsp code action go      ngolang org x tools gopls internal lsp   server  codeaction                n t users fsouza  cache nvim langservers tools gopls internal lsp code action go      ngolang org x tools gopls internal lsp   server  codeaction                   n t users fsouza  cache nvim langservers tools gopls internal lsp server gen go      ngolang org x tools gopls internal lsp protocol serverdispatch                            n t users fsouza  cache nvim langservers tools gopls internal lsp protocol tsserver go      ngolang org x tools gopls internal lsp protocol serverhandler                      n t users fsouza  cache nvim langservers tools gopls internal lsp protocol protocol go      ngolang org x tools gopls internal lsp lsprpc handshaker                        n t users fsouza  cache nvim langservers tools gopls internal lsp lsprpc lsprpc go      ngolang org x tools internal   mustreplyhandler                        n t users fsouza  cache nvim langservers tools internal   handler go      ngolang org x tools internal   asynchandler       n t users fsouza  cache nvim langservers tools internal   handler go      ncreated by golang org x tools internal   asynchandler   n t users fsouza  cache nvim langservers tools internal   handler go      n          in order to make it easier to read  i ve also expanded the two lines above  this is the output from gopls          panic  runtime error  index out of range   with length      goroutine       golang org x tools gopls internal lsp source adjustrangeforcommentsandwhitespace                                           users fsouza  cache nvim langservers tools gopls internal lsp source extract go       golang org x tools gopls internal lsp source canextractfunction                                        users fsouza  cache nvim langservers tools gopls internal lsp source extract go       golang org x tools gopls internal lsp extractionfixes                                                                users fsouza  cache nvim langservers tools gopls internal lsp code action go       golang org x tools gopls internal lsp   server  codeaction                          users fsouza  cache nvim langservers tools gopls internal lsp code action go       golang org x tools gopls internal lsp   server  codeaction                             users fsouza  cache nvim langservers tools gopls internal lsp server gen go       golang org x tools gopls internal lsp protocol serverdispatch                                      users fsouza  cache nvim langservers tools gopls internal lsp protocol tsserver go       golang org x tools gopls internal lsp protocol serverhandler                                users fsouza  cache nvim langservers tools gopls internal lsp protocol protocol go       golang org x tools gopls internal lsp lsprpc handshaker                                  users fsouza  cache nvim langservers tools gopls internal lsp lsprpc lsprpc go       golang org x tools internal   mustreplyhandler                                  users fsouza  cache nvim langservers tools internal   handler go       golang org x tools internal   asynchandler                 users fsouza  cache nvim langservers tools internal   handler go       created by golang org x tools internal   asynchandler             users fsouza  cache nvim langservers tools internal   handler go              this is a regression and i was able to bisect it to this commit            is the first bad commit  commit    author  suzy mueller    date    thu sep                     internal lsp  allow extract func ranges to begin end with comments        canextract strips of the whitespace on either end of the range in      order to get an exact range to extract to function  we can do the      same thing for comments by moving adjusting the range if the start      or end positions contain the position         updates golang go        fixes golang go          change id         reviewed on         reviewed by  robert findley        gopls ci  kokoro        run trybot  suzy mueller        trybot result  gopher robot       gopls internal lsp source extract go                                                extract function extract basic comment go                    extract basic comment go golden                                  gopls internal lsp testdata summary txt golden                   lsp testdata summary     txt golden                     files changed    insertions       deletions                editor and settings          your editor and any settings you have configured  for example  your vscode settings json file          this is neovim  it can be reproduced with just gopls installed  minimal  reproducer in neovim        how to reproduce in neovim with the config file above  using some go repo  i  tested with     but  i suspect that any project file will do           nvim  u minimal init lua   e main go   lua document code action               logs          if possible please include gopls logs  instructions for capturing them can be found here             logs from gopls       logs from the editor  includes the process stderr with the crash at the very end    ,1
156614,13651623347.0,IssuesEvent,2020-09-27 02:24:59,golang/go,https://api.github.com/repos/golang/go,closed,os: File implicitly closed when garbage-collected due to runtime finalizer but this behavior is not documented,Documentation NeedsFix help wanted,"### What version of Go are you using (`go version`)?

<pre>
$ go version
go 1.15.2
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

Linux and macOS.

### What did you do?

Code: https://play.golang.org/p/YmHIIc7sha4

Note: This does not reproduce in go playground, but can reproduce on my mac/linux.

### What did you expect to see?

No panic.

### What did you see instead?

panic: bad file descriptor

### Reason

I found that this is because there's an implicitly close call when the `file` object is garbage-collected.

In os/file_unix.go:
```
func newFile(fd uintptr, name string, kind newFileKind) *File {
	...

	runtime.SetFinalizer(f.file, (*file).close)
	return f
}
```

### What do I expect

I know there's thousands of method to avoid being garbage-collected such as runtime.KeepAlive, but I think this is unreasonable, either this behaviour should be removed or the `file` object should not be garbage-collected.

If a user forgets to call file.Close, the memory should be leaking.

Also, this behaviour isn't documented anywhere.
",1.0,"os: File implicitly closed when garbage-collected due to runtime finalizer but this behavior is not documented - ### What version of Go are you using (`go version`)?

<pre>
$ go version
go 1.15.2
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

Linux and macOS.

### What did you do?

Code: https://play.golang.org/p/YmHIIc7sha4

Note: This does not reproduce in go playground, but can reproduce on my mac/linux.

### What did you expect to see?

No panic.

### What did you see instead?

panic: bad file descriptor

### Reason

I found that this is because there's an implicitly close call when the `file` object is garbage-collected.

In os/file_unix.go:
```
func newFile(fd uintptr, name string, kind newFileKind) *File {
	...

	runtime.SetFinalizer(f.file, (*file).close)
	return f
}
```

### What do I expect

I know there's thousands of method to avoid being garbage-collected such as runtime.KeepAlive, but I think this is unreasonable, either this behaviour should be removed or the `file` object should not be garbage-collected.

If a user forgets to call file.Close, the memory should be leaking.

Also, this behaviour isn't documented anywhere.
",1,os  file implicitly closed when garbage collected due to runtime finalizer but this behavior is not documented       what version of go are you using   go version            go version  go                 does this issue reproduce with the latest release     yes         what operating system and processor architecture are you using   go env       linux and macos         what did you do     code       note  this does not reproduce in go playground  but can reproduce on my mac linux         what did you expect to see     no panic         what did you see instead     panic  bad file descriptor        reason    i found that this is because there s an implicitly close call when the  file  object is garbage collected     in os file unix go        func newfile fd uintptr  name string  kind newfilekind   file    	       	runtime setfinalizer f file    file  close   	return f                what do i expect    i know there s thousands of method to avoid being garbage collected such as runtime keepalive  but i think this is unreasonable  either this behaviour should be removed or the  file  object should not be garbage collected     if a user forgets to call file close  the memory should be leaking     also  this behaviour isn t documented anywhere   ,1
275064,20905232072.0,IssuesEvent,2022-03-24 00:54:36,golang/go,https://api.github.com/repos/golang/go,closed,"x/website: ""Contribution Guide"" is hard to find",Documentation NeedsFix,"<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What is the URL of the page with the issue?

https://go.dev/doc/contribute

### What is your user agent?

<!--
You can find your user agent here:
https://www.google.com/search?q=what+is+my+user+agent
-->

`Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:96.0) Gecko/20100101 Firefox/96.0`


### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
-->

Looked for the contribution guide, since it has been a while. I don't remember the URL of the page.

### What did you expect to see?

A link on go.dev/doc.

### What did you see instead?

No such link. The way I found it was ""Get Started"" -> ""view the install documentation"" -> ""Installing Go from source"" -> ""contribute your changes,"" following links in a variety of places on their respective pages.

Granted, I could have found it from the contribution guidelines here on GitHub, but I didn't expect it to be so hard to find on go.dev.
",1.0,"x/website: ""Contribution Guide"" is hard to find - <!--
Please answer these questions before submitting your issue. Thanks!
-->

### What is the URL of the page with the issue?

https://go.dev/doc/contribute

### What is your user agent?

<!--
You can find your user agent here:
https://www.google.com/search?q=what+is+my+user+agent
-->

`Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:96.0) Gecko/20100101 Firefox/96.0`


### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
-->

Looked for the contribution guide, since it has been a while. I don't remember the URL of the page.

### What did you expect to see?

A link on go.dev/doc.

### What did you see instead?

No such link. The way I found it was ""Get Started"" -> ""view the install documentation"" -> ""Installing Go from source"" -> ""contribute your changes,"" following links in a variety of places on their respective pages.

Granted, I could have found it from the contribution guidelines here on GitHub, but I didn't expect it to be so hard to find on go.dev.
",1,x website   contribution guide  is hard to find         please answer these questions before submitting your issue  thanks              what is the url of the page with the issue              what is your user agent           you can find your user agent here              mozilla         ubuntu  linux      rv      gecko   firefox               what did you do           if possible  provide a recipe for reproducing the error          looked for the contribution guide  since it has been a while  i don t remember the url of the page         what did you expect to see     a link on go dev doc         what did you see instead     no such link  the way i found it was  get started      view the install documentation      installing go from source      contribute your changes   following links in a variety of places on their respective pages     granted  i could have found it from the contribution guidelines here on github  but i didn t expect it to be so hard to find on go dev   ,1
64575,8744852552.0,IssuesEvent,2018-12-12 23:51:56,golang/go,https://api.github.com/repos/golang/go,closed,go/build: document when Context.BuildTags is used/populated,Documentation NeedsFix,"Context.BuildTags is not set when you read go/build.Default.BuildTags.

It's only used by (*BuildTags).Import, etc.

Document that.
",1.0,"go/build: document when Context.BuildTags is used/populated - Context.BuildTags is not set when you read go/build.Default.BuildTags.

It's only used by (*BuildTags).Import, etc.

Document that.
",1,go build  document when context buildtags is used populated   context buildtags is not set when you read go build default buildtags     it s only used by   buildtags  import  etc     document that   ,1
28026,4350656216.0,IssuesEvent,2016-07-31 11:45:37,cockroachdb/cockroach,https://api.github.com/repos/cockroachdb/cockroach,closed,stress: failed test in cockroach/gossip/gossip.test: TestClientDisconnectRedundant,Robot test-failure,"Binary: cockroach/static-tests.tar.gz sha: https://github.com/cockroachdb/cockroach/commits/cf1708206ce61409aebecb2238ee4e9148935fef

Stress build found a failed test:

```
=== RUN   TestClientDisconnectRedundant
W160731 05:34:21.959196 gossip/gossip.go:1006  not connected to cluster; use --join to specify a connected node
W160731 05:34:21.960557 gossip/gossip.go:1006  not connected to cluster; use --join to specify a connected node
I160731 05:34:21.962536 gossip/client.go:75  starting client to 127.0.0.1:44837
I160731 05:34:21.962606 gossip/client.go:75  starting client to 127.0.0.1:40774
I160731 05:34:21.969036 gossip/client.go:99  closing client to node 2 (127.0.0.1:44837): stopping outgoing client to node 2 (127.0.0.1:44837); already have incoming
I160731 05:34:21.976633 http2_server.go:268  transport: http2Server.HandleStreams failed to read frame: read tcp 127.0.0.1:40774->127.0.0.1:35832: use of closed network connection
I160731 05:34:21.976669 http2_client.go:1019  transport: http2Client.notifyError got notified that the client transport was broken EOF.
I160731 05:34:21.976741 http2_server.go:268  transport: http2Server.HandleStreams failed to read frame: EOF
--- FAIL: TestClientDisconnectRedundant (5.06s)
	leaktest.go:105: Leaked goroutine: goroutine 137 [select]:
		google.golang.org/grpc/transport.(*http2Client).controller(0xc8200a6900)
			/go/src/google.golang.org/grpc/transport/http2_client.go:965 +0x5e0
		created by google.golang.org/grpc/transport.newHTTP2Client
			/go/src/google.golang.org/grpc/transport/http2_client.go:206 +0x14bd
```

Run Details:

```
67 runs so far, 0 failures, over 5s
92 runs completed, 1 failures, over 7s
FAIL
```
Please assign, take a look and update the issue accordingly.",1.0,"stress: failed test in cockroach/gossip/gossip.test: TestClientDisconnectRedundant - Binary: cockroach/static-tests.tar.gz sha: https://github.com/cockroachdb/cockroach/commits/cf1708206ce61409aebecb2238ee4e9148935fef

Stress build found a failed test:

```
=== RUN   TestClientDisconnectRedundant
W160731 05:34:21.959196 gossip/gossip.go:1006  not connected to cluster; use --join to specify a connected node
W160731 05:34:21.960557 gossip/gossip.go:1006  not connected to cluster; use --join to specify a connected node
I160731 05:34:21.962536 gossip/client.go:75  starting client to 127.0.0.1:44837
I160731 05:34:21.962606 gossip/client.go:75  starting client to 127.0.0.1:40774
I160731 05:34:21.969036 gossip/client.go:99  closing client to node 2 (127.0.0.1:44837): stopping outgoing client to node 2 (127.0.0.1:44837); already have incoming
I160731 05:34:21.976633 http2_server.go:268  transport: http2Server.HandleStreams failed to read frame: read tcp 127.0.0.1:40774->127.0.0.1:35832: use of closed network connection
I160731 05:34:21.976669 http2_client.go:1019  transport: http2Client.notifyError got notified that the client transport was broken EOF.
I160731 05:34:21.976741 http2_server.go:268  transport: http2Server.HandleStreams failed to read frame: EOF
--- FAIL: TestClientDisconnectRedundant (5.06s)
	leaktest.go:105: Leaked goroutine: goroutine 137 [select]:
		google.golang.org/grpc/transport.(*http2Client).controller(0xc8200a6900)
			/go/src/google.golang.org/grpc/transport/http2_client.go:965 +0x5e0
		created by google.golang.org/grpc/transport.newHTTP2Client
			/go/src/google.golang.org/grpc/transport/http2_client.go:206 +0x14bd
```

Run Details:

```
67 runs so far, 0 failures, over 5s
92 runs completed, 1 failures, over 7s
FAIL
```
Please assign, take a look and update the issue accordingly.",0,stress  failed test in cockroach gossip gossip test  testclientdisconnectredundant   binary  cockroach static tests tar gz sha     stress build found a failed test           run   testclientdisconnectredundant           gossip gossip go    not connected to cluster  use   join to specify a connected node           gossip gossip go    not connected to cluster  use   join to specify a connected node           gossip client go    starting client to                     gossip client go    starting client to                     gossip client go    closing client to node                stopping outgoing client to node                already have incoming             server go    transport    handlestreams failed to read frame  read tcp                       use of closed network connection             client go    transport    notifyerror got notified that the client transport was broken eof              server go    transport    handlestreams failed to read frame  eof     fail  testclientdisconnectredundant       	leaktest go    leaked goroutine  goroutine      		google golang org grpc transport      controller    			 go src google golang org grpc transport   client go      		created by google golang org grpc transport   			 go src google golang org grpc transport   client go           run details         runs so far    failures  over     runs completed    failures  over   fail     please assign  take a look and update the issue accordingly ,0
24988,5115853271.0,IssuesEvent,2017-01-06 23:19:17,golang/go,https://api.github.com/repos/golang/go,closed,CONTRIBUTING.md doesn't describe proper procedure for proposals in issues,Documentation,"### What did you do?
Make a proposal for golang

### What did you expect to see?
[guidelines for contributing](https://github.com/golang/go/blob/master/CONTRIBUTING.md) telling me when using issues is a proper venue for discussing things (rather than ex. go-nuts@)

While I'm not quite sure myself, some GitHub-centric people might not even be aware of especially the mailing-lists used for discussing all things Go.",1.0,"CONTRIBUTING.md doesn't describe proper procedure for proposals in issues - ### What did you do?
Make a proposal for golang

### What did you expect to see?
[guidelines for contributing](https://github.com/golang/go/blob/master/CONTRIBUTING.md) telling me when using issues is a proper venue for discussing things (rather than ex. go-nuts@)

While I'm not quite sure myself, some GitHub-centric people might not even be aware of especially the mailing-lists used for discussing all things Go.",1,contributing md doesn t describe proper procedure for proposals in issues       what did you do   make a proposal for golang        what did you expect to see       telling me when using issues is a proper venue for discussing things  rather than ex  go nuts      while i m not quite sure myself  some github centric people might not even be aware of especially the mailing lists used for discussing all things go ,1
245742,18792487874.0,IssuesEvent,2021-11-08 18:17:05,golang/go,https://api.github.com/repos/golang/go,closed,proxy.golang.org: document process for unpublishing compromised modules,Documentation,"Given the recent security incident with the coa and rc node packages, I would like to request that the process for getting compromised module versions unpublished from proxy.golang.org be recorded in the [FAQ](https://proxy.golang.org/) to allow for a speedy resolution should an incident occur. In a situation like this, simply retracting the compromised version is insufficient.

Please note that I am NOT intending to report a compromised version of any Go module in this issue. I'm just looking for documentation.",1.0,"proxy.golang.org: document process for unpublishing compromised modules - Given the recent security incident with the coa and rc node packages, I would like to request that the process for getting compromised module versions unpublished from proxy.golang.org be recorded in the [FAQ](https://proxy.golang.org/) to allow for a speedy resolution should an incident occur. In a situation like this, simply retracting the compromised version is insufficient.

Please note that I am NOT intending to report a compromised version of any Go module in this issue. I'm just looking for documentation.",1,proxy golang org  document process for unpublishing compromised modules   given the recent security incident with the coa and rc node packages  i would like to request that the process for getting compromised module versions unpublished from proxy golang org be recorded in the     to allow for a speedy resolution should an incident occur  in a situation like this  simply retracting the compromised version is insufficient     please note that i am not intending to report a compromised version of any go module in this issue  i m just looking for documentation ,1
253958,19183445048.0,IssuesEvent,2021-12-04 20:09:52,golang/go,https://api.github.com/repos/golang/go,opened,net: Resolver.LookupSRV first result param not documented well,Documentation,"https://pkg.go.dev/net#Resolver.LookupSRV has signature:

```go
func (r *Resolver) LookupSRV(ctx context.Context, service, proto, name string) (string, []*SRV, error)
```

... but the docs don't make it super clear what that `string` result is.

There's a hint in the docs:

> LookupSRV constructs the DNS name to look up following RFC 2782. That is, it looks up _service._proto.name.

But that makes it sound like it's an implementation detail, not that the first result is indeed that DNS name.
",1.0,"net: Resolver.LookupSRV first result param not documented well - https://pkg.go.dev/net#Resolver.LookupSRV has signature:

```go
func (r *Resolver) LookupSRV(ctx context.Context, service, proto, name string) (string, []*SRV, error)
```

... but the docs don't make it super clear what that `string` result is.

There's a hint in the docs:

> LookupSRV constructs the DNS name to look up following RFC 2782. That is, it looks up _service._proto.name.

But that makes it sound like it's an implementation detail, not that the first result is indeed that DNS name.
",1,net  resolver lookupsrv first result param not documented well     has signature        go  func  r  resolver  lookupsrv ctx context context  service  proto  name string   string    srv  error              but the docs don t make it super clear what that  string  result is     there s a hint in the docs       lookupsrv constructs the dns name to look up following rfc    that is  it looks up  service  proto name     but that makes it sound like it s an implementation detail  not that the first result is indeed that dns name   ,1
560485,16597802340.0,IssuesEvent,2021-06-01 15:20:20,BTAA-Geospatial-Data-Project/geoportal,https://api.github.com/repos/BTAA-Geospatial-Data-Project/geoportal,closed,Consider disabling the spatial display update from the GeoBlacklight version 3.3,priority:medium type:bug type:question or discussion version:GBL 3.3,"From what I think I am seeing, the updated GeoBlacklight is causing a number of problems for coordinates.  The application will error if a record:

- is missing coordinates
- has coordinates that form a point or line.

We have many records that fall into one of these scenarios. Recent versions of GeoBlacklight did not require bounding boxes or displayed points/lines OK. I am not sure if I will be able to find all of these, so it seems likely that we will end up with many error pages before GBL 4.0 is ready.

Would it be possible to revert to previous code for that part only?",1.0,"Consider disabling the spatial display update from the GeoBlacklight version 3.3 - From what I think I am seeing, the updated GeoBlacklight is causing a number of problems for coordinates.  The application will error if a record:

- is missing coordinates
- has coordinates that form a point or line.

We have many records that fall into one of these scenarios. Recent versions of GeoBlacklight did not require bounding boxes or displayed points/lines OK. I am not sure if I will be able to find all of these, so it seems likely that we will end up with many error pages before GBL 4.0 is ready.

Would it be possible to revert to previous code for that part only?",0,consider disabling the spatial display update from the geoblacklight version       from what i think i am seeing  the updated geoblacklight is causing a number of problems for coordinates   the application will error if a record       is missing coordinates    has coordinates that form a point or line     we have many records that fall into one of these scenarios  recent versions of geoblacklight did not require bounding boxes or displayed points lines ok  i am not sure if i will be able to find all of these  so it seems likely that we will end up with many error pages before gbl     is ready     would it be possible to revert to previous code for that part only ,0
631479,20152267784.0,IssuesEvent,2022-02-09 13:32:46,ita-social-projects/horondi_client_fe,https://api.github.com/repos/ita-social-projects/horondi_client_fe,closed,[Registration page]  No field 'Confirm Password' ,bug priority: high severity: major Functional,"**Environment:** MacOS Big Sur 11.6,  Firefox 93 (64 bit)
**Reproducible:** always

**Steps to reproduce**

1. Go to Horondi page

**Actual result**
No field 'Confirm Password' after field 'Password'
**Actual result (Update)**
Field 'Confirm **the** password' 

**Expected result**
Field 'Confirm Password' without 'the'  

**User story and test case links**
""User story #191
[Test case](https://jira.softserve.academy/browse/LVHRB-311)""


",1.0,"[Registration page]  No field 'Confirm Password'  - **Environment:** MacOS Big Sur 11.6,  Firefox 93 (64 bit)
**Reproducible:** always

**Steps to reproduce**

1. Go to Horondi page

**Actual result**
No field 'Confirm Password' after field 'Password'
**Actual result (Update)**
Field 'Confirm **the** password' 

**Expected result**
Field 'Confirm Password' without 'the'  

**User story and test case links**
""User story #191
[Test case](https://jira.softserve.academy/browse/LVHRB-311)""


",0,   no field  confirm password       environment    macos big sur       firefox      bit     reproducible    always      steps to reproduce         go to horondi page      actual result    no field  confirm password  after field  password     actual result  update     field  confirm   the   password        expected result    field  confirm password  without  the         user story and test case links     user story              ,0
101870,21799974929.0,IssuesEvent,2022-05-16 03:17:04,cubeFS/cubefs,https://api.github.com/repos/cubeFS/cubefs,closed,Meta startup process problem,bug SODACODE2022 SODAHIGH,"**Describe the bug**
If an mp fails to start during meta startup, the listen process will be blocked, while other mps that have been successfully started by raft can participate in the election and become the leader, causing other mps to be unserviceable to the outside world.

Adjust the startup process. After the meta service is up, it will listen to the service port 17210, and then load the mp asynchronously. If the timeout fails to load, then panic
",1.0,"Meta startup process problem - **Describe the bug**
If an mp fails to start during meta startup, the listen process will be blocked, while other mps that have been successfully started by raft can participate in the election and become the leader, causing other mps to be unserviceable to the outside world.

Adjust the startup process. After the meta service is up, it will listen to the service port 17210, and then load the mp asynchronously. If the timeout fails to load, then panic
",0,meta startup process problem     describe the bug    if an mp fails to start during meta startup  the listen process will be blocked  while other mps that have been successfully started by raft can participate in the election and become the leader  causing other mps to be unserviceable to the outside world     adjust the startup process  after the meta service is up  it will listen to the service port    and then load the mp asynchronously  if the timeout fails to load  then panic  ,0
177769,13747732777.0,IssuesEvent,2020-10-06 08:04:22,kubernetes/kubernetes,https://api.github.com/repos/kubernetes/kubernetes,opened,Summary API [NodeConformance] test breaks on CRIO,kind/failing-test,"<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->

**Which jobs are failing**:
While trying to run the node conformance tests with CRIO, the test `Summary API [NodeConformance]` I noticed failures like 
`ping: permission denied (are you root?)` on the logs of the test containers. This happens because CRIO doesn't ship with `CAP_NEW_RAW` capability enabled by default. Since only this test in `NodeConformance` requires it, we should add this capability only in this test and not runtime wide. 

**Which test(s) are failing**:
`Summary API [NodeConformance]`

**Since when has it been failing**:

**Testgrid link**:

**Reason for failure**:
CRIO doesn't ship with `CAP_NEW_RAW` by default. 

**Anything else we need to know**:
",1.0,"Summary API [NodeConformance] test breaks on CRIO - <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->

**Which jobs are failing**:
While trying to run the node conformance tests with CRIO, the test `Summary API [NodeConformance]` I noticed failures like 
`ping: permission denied (are you root?)` on the logs of the test containers. This happens because CRIO doesn't ship with `CAP_NEW_RAW` capability enabled by default. Since only this test in `NodeConformance` requires it, we should add this capability only in this test and not runtime wide. 

**Which test(s) are failing**:
`Summary API [NodeConformance]`

**Since when has it been failing**:

**Testgrid link**:

**Reason for failure**:
CRIO doesn't ship with `CAP_NEW_RAW` by default. 

**Anything else we need to know**:
",0,summary api   test breaks on crio          which jobs are failing     while trying to run the node conformance tests with crio  the test  summary api    i noticed failures like    ping  permission denied  are you root    on the logs of the test containers  this happens because crio doesn t ship with  cap new raw  capability enabled by default  since only this test in  nodeconformance  requires it  we should add this capability only in this test and not runtime wide        which test s  are failing      summary api         since when has it been failing         testgrid link         reason for failure     crio doesn t ship with  cap new raw  by default        anything else we need to know     ,0
166777,12971637453.0,IssuesEvent,2020-07-21 11:16:03,apache/shardingsphere-elasticjob,https://api.github.com/repos/apache/shardingsphere-elasticjob,closed,Add test cases for JobExecutor,test volunteer wanted,"- [ ] SimpleJobExecutor
- [ ] DataflowJobExecutor
- [ ] ScriptJobExecutor",1.0,"Add test cases for JobExecutor - - [ ] SimpleJobExecutor
- [ ] DataflowJobExecutor
- [ ] ScriptJobExecutor",0,add test cases for jobexecutor       simplejobexecutor      dataflowjobexecutor      scriptjobexecutor,0
108232,16762820384.0,IssuesEvent,2021-06-14 03:17:09,gms-ws-sandbox/nibrs-pr-test,https://api.github.com/repos/gms-ws-sandbox/nibrs-pr-test,opened,"CVE-2020-7238 (High) detected in netty-codec-http-4.1.36.Final.jar, netty-codec-http-4.1.29.Final.jar",security vulnerability,"## CVE-2020-7238 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>netty-codec-http-4.1.36.Final.jar</b>, <b>netty-codec-http-4.1.29.Final.jar</b></p></summary>
<p>

<details><summary><b>netty-codec-http-4.1.36.Final.jar</b></p></summary>

<p>Netty is an asynchronous event-driven network application framework for
    rapid development of maintainable high performance protocol servers and
    clients.</p>
<p>Library home page: <a href=""http://netty.io/"">http://netty.io/</a></p>
<p>Path to dependency file: nibrs-pr-test/tools/nibrs-summary-report-common/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/io/netty/netty-codec-http/4.1.36.Final/netty-codec-http-4.1.36.Final.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-starter-webflux-2.1.5.RELEASE.jar (Root Library)
    - spring-boot-starter-reactor-netty-2.1.5.RELEASE.jar
      - reactor-netty-0.8.8.RELEASE.jar
        - :x: **netty-codec-http-4.1.36.Final.jar** (Vulnerable Library)
</details>
<details><summary><b>netty-codec-http-4.1.29.Final.jar</b></p></summary>

<p>Netty is an asynchronous event-driven network application framework for
    rapid development of maintainable high performance protocol servers and
    clients.</p>
<p>Library home page: <a href=""http://netty.io/"">http://netty.io/</a></p>
<p>Path to dependency file: nibrs-pr-test/tools/nibrs-summary-report/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/io/netty/netty-codec-http/4.1.29.Final/netty-codec-http-4.1.29.Final.jar</p>
<p>

Dependency Hierarchy:
  - nibrs-summary-report-common-1.0.0.jar (Root Library)
    - spring-boot-starter-webflux-2.0.5.RELEASE.jar
      - spring-boot-starter-reactor-netty-2.0.5.RELEASE.jar
        - reactor-netty-0.7.9.RELEASE.jar
          - :x: **netty-codec-http-4.1.29.Final.jar** (Vulnerable Library)
</details>

<p>Found in HEAD commit: <a href=""https://github.com/gms-ws-sandbox/nibrs-pr-test/commit/860cc22f54e17594e32e303f0716fb065202fff5"">860cc22f54e17594e32e303f0716fb065202fff5</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>  
  
Netty 4.1.43.Final allows HTTP Request Smuggling because it mishandles Transfer-Encoding whitespace (such as a [space]Transfer-Encoding:chunked line) and a later Content-Length header. This issue exists because of an incomplete fix for CVE-2019-16869.

<p>Publish Date: 2020-01-27
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7238>CVE-2020-7238</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: High
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/netty/netty/issues/9861"">https://github.com/netty/netty/issues/9861</a></p>
<p>Release Date: 2020-01-27</p>
<p>Fix Resolution: io.netty:netty-all:4.1.44.Final;io.netty:netty-codec-http:4.1.44.Final</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""io.netty"",""packageName"":""netty-codec-http"",""packageVersion"":""4.1.36.Final"",""packageFilePaths"":[""/tools/nibrs-summary-report-common/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.springframework.boot:spring-boot-starter-webflux:2.1.5.RELEASE;org.springframework.boot:spring-boot-starter-reactor-netty:2.1.5.RELEASE;io.projectreactor.netty:reactor-netty:0.8.8.RELEASE;io.netty:netty-codec-http:4.1.36.Final"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""io.netty:netty-all:4.1.44.Final;io.netty:netty-codec-http:4.1.44.Final""},{""packageType"":""Java"",""groupId"":""io.netty"",""packageName"":""netty-codec-http"",""packageVersion"":""4.1.29.Final"",""packageFilePaths"":[""/tools/nibrs-summary-report/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.search.nibrs:nibrs-summary-report-common:1.0.0;org.springframework.boot:spring-boot-starter-webflux:2.0.5.RELEASE;org.springframework.boot:spring-boot-starter-reactor-netty:2.0.5.RELEASE;io.projectreactor.ipc:reactor-netty:0.7.9.RELEASE;io.netty:netty-codec-http:4.1.29.Final"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""io.netty:netty-all:4.1.44.Final;io.netty:netty-codec-http:4.1.44.Final""}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""CVE-2020-7238"",""vulnerabilityDetails"":""Netty 4.1.43.Final allows HTTP Request Smuggling because it mishandles Transfer-Encoding whitespace (such as a [space]Transfer-Encoding:chunked line) and a later Content-Length header. This issue exists because of an incomplete fix for CVE-2019-16869."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7238"",""cvss3Severity"":""high"",""cvss3Score"":""7.5"",""cvss3Metrics"":{""A"":""None"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""None"",""AV"":""Network"",""I"":""High""},""extraData"":{}}</REMEDIATE> -->",True,"CVE-2020-7238 (High) detected in netty-codec-http-4.1.36.Final.jar, netty-codec-http-4.1.29.Final.jar - ## CVE-2020-7238 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>netty-codec-http-4.1.36.Final.jar</b>, <b>netty-codec-http-4.1.29.Final.jar</b></p></summary>
<p>

<details><summary><b>netty-codec-http-4.1.36.Final.jar</b></p></summary>

<p>Netty is an asynchronous event-driven network application framework for
    rapid development of maintainable high performance protocol servers and
    clients.</p>
<p>Library home page: <a href=""http://netty.io/"">http://netty.io/</a></p>
<p>Path to dependency file: nibrs-pr-test/tools/nibrs-summary-report-common/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/io/netty/netty-codec-http/4.1.36.Final/netty-codec-http-4.1.36.Final.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-starter-webflux-2.1.5.RELEASE.jar (Root Library)
    - spring-boot-starter-reactor-netty-2.1.5.RELEASE.jar
      - reactor-netty-0.8.8.RELEASE.jar
        - :x: **netty-codec-http-4.1.36.Final.jar** (Vulnerable Library)
</details>
<details><summary><b>netty-codec-http-4.1.29.Final.jar</b></p></summary>

<p>Netty is an asynchronous event-driven network application framework for
    rapid development of maintainable high performance protocol servers and
    clients.</p>
<p>Library home page: <a href=""http://netty.io/"">http://netty.io/</a></p>
<p>Path to dependency file: nibrs-pr-test/tools/nibrs-summary-report/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/io/netty/netty-codec-http/4.1.29.Final/netty-codec-http-4.1.29.Final.jar</p>
<p>

Dependency Hierarchy:
  - nibrs-summary-report-common-1.0.0.jar (Root Library)
    - spring-boot-starter-webflux-2.0.5.RELEASE.jar
      - spring-boot-starter-reactor-netty-2.0.5.RELEASE.jar
        - reactor-netty-0.7.9.RELEASE.jar
          - :x: **netty-codec-http-4.1.29.Final.jar** (Vulnerable Library)
</details>

<p>Found in HEAD commit: <a href=""https://github.com/gms-ws-sandbox/nibrs-pr-test/commit/860cc22f54e17594e32e303f0716fb065202fff5"">860cc22f54e17594e32e303f0716fb065202fff5</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>  
  
Netty 4.1.43.Final allows HTTP Request Smuggling because it mishandles Transfer-Encoding whitespace (such as a [space]Transfer-Encoding:chunked line) and a later Content-Length header. This issue exists because of an incomplete fix for CVE-2019-16869.

<p>Publish Date: 2020-01-27
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7238>CVE-2020-7238</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: High
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/netty/netty/issues/9861"">https://github.com/netty/netty/issues/9861</a></p>
<p>Release Date: 2020-01-27</p>
<p>Fix Resolution: io.netty:netty-all:4.1.44.Final;io.netty:netty-codec-http:4.1.44.Final</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""io.netty"",""packageName"":""netty-codec-http"",""packageVersion"":""4.1.36.Final"",""packageFilePaths"":[""/tools/nibrs-summary-report-common/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.springframework.boot:spring-boot-starter-webflux:2.1.5.RELEASE;org.springframework.boot:spring-boot-starter-reactor-netty:2.1.5.RELEASE;io.projectreactor.netty:reactor-netty:0.8.8.RELEASE;io.netty:netty-codec-http:4.1.36.Final"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""io.netty:netty-all:4.1.44.Final;io.netty:netty-codec-http:4.1.44.Final""},{""packageType"":""Java"",""groupId"":""io.netty"",""packageName"":""netty-codec-http"",""packageVersion"":""4.1.29.Final"",""packageFilePaths"":[""/tools/nibrs-summary-report/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.search.nibrs:nibrs-summary-report-common:1.0.0;org.springframework.boot:spring-boot-starter-webflux:2.0.5.RELEASE;org.springframework.boot:spring-boot-starter-reactor-netty:2.0.5.RELEASE;io.projectreactor.ipc:reactor-netty:0.7.9.RELEASE;io.netty:netty-codec-http:4.1.29.Final"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""io.netty:netty-all:4.1.44.Final;io.netty:netty-codec-http:4.1.44.Final""}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""CVE-2020-7238"",""vulnerabilityDetails"":""Netty 4.1.43.Final allows HTTP Request Smuggling because it mishandles Transfer-Encoding whitespace (such as a [space]Transfer-Encoding:chunked line) and a later Content-Length header. This issue exists because of an incomplete fix for CVE-2019-16869."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7238"",""cvss3Severity"":""high"",""cvss3Score"":""7.5"",""cvss3Metrics"":{""A"":""None"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""None"",""AV"":""Network"",""I"":""High""},""extraData"":{}}</REMEDIATE> -->",0,cve      high  detected in netty codec http       final jar  netty codec http       final jar      cve       high severity vulnerability     vulnerable libraries    netty codec http       final jar    netty codec http       final jar          netty codec http       final jar      netty is an asynchronous event driven network application framework for     rapid development of maintainable high performance protocol servers and     clients    library home page   a href     path to dependency file  nibrs pr test tools nibrs summary report common pom xml   path to vulnerable library   home wss scanner    repository io netty netty codec http       final netty codec http       final jar     dependency hierarchy      spring boot starter webflux       release jar  root library        spring boot starter reactor netty       release jar         reactor netty       release jar            x    netty codec http       final jar    vulnerable library       netty codec http       final jar      netty is an asynchronous event driven network application framework for     rapid development of maintainable high performance protocol servers and     clients    library home page   a href     path to dependency file  nibrs pr test tools nibrs summary report pom xml   path to vulnerable library   home wss scanner    repository io netty netty codec http       final netty codec http       final jar     dependency hierarchy      nibrs summary report common       jar  root library        spring boot starter webflux       release jar         spring boot starter reactor netty       release jar           reactor netty       release jar              x    netty codec http       final jar    vulnerable library      found in head commit   a href     found in base branch   master              vulnerability details         netty       final allows http request smuggling because it mishandles transfer encoding whitespace  such as a  transfer encoding chunked line  and a later content length header  this issue exists because of an incomplete fix for cve        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  high     availability impact  none   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  io netty netty all       final io netty netty codec http       final              isopenpronvulnerability  true  ispackagebased  true  isdefaultbranch  true  packages     istransitivedependency  true  dependencytree   org springframework boot spring boot starter webflux       release org springframework boot spring boot starter reactor netty       release io projectreactor netty reactor netty       release io netty netty codec http       final   isminimumfixversionavailable  true  minimumfixversion   io netty netty all       final io netty netty codec http       final     packagetype   java   groupid   io netty   packagename   netty codec http   packageversion         final   packagefilepaths     istransitivedependency  true  dependencytree   org search nibrs nibrs summary report common       org springframework boot spring boot starter webflux       release org springframework boot spring boot starter reactor netty       release io projectreactor ipc reactor netty       release io netty netty codec http       final   isminimumfixversionavailable  true  minimumfixversion   io netty netty all       final io netty netty codec http       final     basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   netty       final allows http request smuggling because it mishandles transfer encoding whitespace  such as a  transfer encoding chunked line  and a later content length header  this issue exists because of an incomplete fix for cve        vulnerabilityurl        ,0
11618,17603903949.0,IssuesEvent,2021-08-17 14:50:55,renovatebot/renovate,https://api.github.com/repos/renovatebot/renovate,closed,Lock file only updates for Bundler,type:feature status:requirements priority-5-triage,"### What would you like Renovate to be able to do?

I have a ruby project with Renovate bot enabled but not receiving any updates. After searching I found a similar issue fired two years ago, and a Renovate bot dev replied that `Gemfile.lock`-only update was not implemented at that time: https://github.com/renovatebot/renovate/issues/3860#issuecomment-497935910 which is exactly what I need. However, that issue was closed by the resolution of another bug found by the guy.

May I know the status of the feature? Is it implemented now?

### If you have any ideas on how this should be implemented, please tell us here.

Shouldn’t be too much work according to https://github.com/renovatebot/renovate/issues/3860#issuecomment-497938239

### Is this a feature you are interested in implementing yourself?

No",1.0,"Lock file only updates for Bundler - ### What would you like Renovate to be able to do?

I have a ruby project with Renovate bot enabled but not receiving any updates. After searching I found a similar issue fired two years ago, and a Renovate bot dev replied that `Gemfile.lock`-only update was not implemented at that time: https://github.com/renovatebot/renovate/issues/3860#issuecomment-497935910 which is exactly what I need. However, that issue was closed by the resolution of another bug found by the guy.

May I know the status of the feature? Is it implemented now?

### If you have any ideas on how this should be implemented, please tell us here.

Shouldn’t be too much work according to https://github.com/renovatebot/renovate/issues/3860#issuecomment-497938239

### Is this a feature you are interested in implementing yourself?

No",0,lock file only updates for bundler       what would you like renovate to be able to do   i have a ruby project with renovate bot enabled but not receiving any updates  after searching i found a similar issue fired two years ago  and a renovate bot dev replied that  gemfile lock  only update was not implemented at that time    which is exactly what i need  however  that issue was closed by the resolution of another bug found by the guy     may i know the status of the feature  is it implemented now       if you have any ideas on how this should be implemented  please tell us here   shouldn’t be too much work according to        is this a feature you are interested in implementing yourself   no,0
40812,6849208247.0,IssuesEvent,2017-11-13 21:15:21,golang/go,https://api.github.com/repos/golang/go,opened,"cmd/gofmt: document that tools must invoke gofmt, not use go/format",Documentation,"We've had reports of skew where people are using one tool that links against go/printer (or go/format, which wraps it) and writes code, and then some other tool runs gofmt and sees that the formatting is different, because gofmt has a newer/older/different version of go/printer.

We should document that tools that write code files that will be checked in should run gofmt (the program) over their output, not assume that their copy of go/printer matches. One such tool is goimports.

The alternative is that we somehow never ever again change the output of gofmt on existing code, which seems too restrictive.

See:
  - https://github.com/golang/go/issues/18782 (cmd/gofmt: comment lines broken at new position)
  - https://github.com/golang/go/issues/18790 (proposal: cmd/gofmt: write official spec for gofmt)
  - https://github.com/golang/go/issues/22607 (cmd/gofmt: formatting improvements may break existing presubmit checks)

",1.0,"cmd/gofmt: document that tools must invoke gofmt, not use go/format - We've had reports of skew where people are using one tool that links against go/printer (or go/format, which wraps it) and writes code, and then some other tool runs gofmt and sees that the formatting is different, because gofmt has a newer/older/different version of go/printer.

We should document that tools that write code files that will be checked in should run gofmt (the program) over their output, not assume that their copy of go/printer matches. One such tool is goimports.

The alternative is that we somehow never ever again change the output of gofmt on existing code, which seems too restrictive.

See:
  - https://github.com/golang/go/issues/18782 (cmd/gofmt: comment lines broken at new position)
  - https://github.com/golang/go/issues/18790 (proposal: cmd/gofmt: write official spec for gofmt)
  - https://github.com/golang/go/issues/22607 (cmd/gofmt: formatting improvements may break existing presubmit checks)

",1,cmd gofmt  document that tools must invoke gofmt  not use go format   we ve had reports of skew where people are using one tool that links against go printer  or go format  which wraps it  and writes code  and then some other tool runs gofmt and sees that the formatting is different  because gofmt has a newer older different version of go printer     we should document that tools that write code files that will be checked in should run gofmt  the program  over their output  not assume that their copy of go printer matches  one such tool is goimports     the alternative is that we somehow never ever again change the output of gofmt on existing code  which seems too restrictive     see          cmd gofmt  comment lines broken at new position          proposal  cmd gofmt  write official spec for gofmt          cmd gofmt  formatting improvements may break existing presubmit checks     ,1
92389,18847436627.0,IssuesEvent,2021-11-11 16:25:49,sourcegraph/codeintellify,https://api.github.com/repos/sourcegraph/codeintellify,closed,Delay hiding the tooltip when mouse is moved away,bug team/code-intelligence,"Reported in https://github.com/sourcegraph/issues/issues/132

> - sourcegraph.com
> - Chrome Version 68.0.3440.106 (Official Build) (64-bit), OSX 10.13.6
> 
> #### Steps to reproduce:
> 
> 1. Go here: https://sourcegraph.com/github.com/src-d/go-git/-/blob/options.go#L325
> 2. Hover the mouse over an identifier (e.g: `All` attribute inside `CommitOptions`)
> 3. Quickly move the mouse towards the ""Find references"" button
> 
> #### Expected: 
> - Popup should remain in place and let me click on find references
> 
> #### Actual:
> - Sometimes the popup disappear, probably because it thinks the mouse isn't hovering over the identifier anymore
> 
> I'll post a link to a video with the repro in a follow-up update.",1.0,"Delay hiding the tooltip when mouse is moved away - Reported in https://github.com/sourcegraph/issues/issues/132

> - sourcegraph.com
> - Chrome Version 68.0.3440.106 (Official Build) (64-bit), OSX 10.13.6
> 
> #### Steps to reproduce:
> 
> 1. Go here: https://sourcegraph.com/github.com/src-d/go-git/-/blob/options.go#L325
> 2. Hover the mouse over an identifier (e.g: `All` attribute inside `CommitOptions`)
> 3. Quickly move the mouse towards the ""Find references"" button
> 
> #### Expected: 
> - Popup should remain in place and let me click on find references
> 
> #### Actual:
> - Sometimes the popup disappear, probably because it thinks the mouse isn't hovering over the identifier anymore
> 
> I'll post a link to a video with the repro in a follow-up update.",0,delay hiding the tooltip when mouse is moved away   reported in          sourcegraph com      chrome version          official build     bit   osx                   steps to reproduce            go here          hover the mouse over an identifier  e g   all  attribute inside  commitoptions         quickly move the mouse towards the  find references  button             expected        popup should remain in place and let me click on find references             actual       sometimes the popup disappear  probably because it thinks the mouse isn t hovering over the identifier anymore        i ll post a link to a video with the repro in a follow up update ,0
493723,14237071416.0,IssuesEvent,2020-11-18 16:45:37,conan-io/conan-center-index,https://api.github.com/repos/conan-io/conan-center-index,closed,[service] cairo is not available,bug enhancement priority: medium,"Just an issue so that this is not getting lost

https://github.com/conan-io/conan-center-index/pull/2847#issuecomment-727255681

// @ericLemanissier @jgsogo @danimtb ",1.0,"[service] cairo is not available - Just an issue so that this is not getting lost

https://github.com/conan-io/conan-center-index/pull/2847#issuecomment-727255681

// @ericLemanissier @jgsogo @danimtb ",0,  cairo is not available   just an issue so that this is not getting lost             ericlemanissier  jgsogo  danimtb ,0
34133,28312750305.0,IssuesEvent,2023-04-10 16:52:31,MaxCunningham19/legal_spellcheck,https://api.github.com/repos/MaxCunningham19/legal_spellcheck,closed,Sprint 1: Set up Auto Versioning,feature infrastructure change Sprint 1,Set up automatic versioning as per Professors standards. (will align with DEMOs),1.0,Sprint 1: Set up Auto Versioning - Set up automatic versioning as per Professors standards. (will align with DEMOs),0,sprint    set up auto versioning   set up automatic versioning as per professors standards   will align with demos ,0
16679,3549589258.0,IssuesEvent,2016-01-20 18:36:44,elastic/kibana,https://api.github.com/repos/elastic/kibana,closed,Fix automated test data load remove deprecated multi-field use,chore P1 test,"We need to switch branch from 2.1 to 2.x in kibana\tasks\config\esvm.js
and then fix kibana\test\fixtures to remove multi_field and still load all data so tests pass.",1.0,"Fix automated test data load remove deprecated multi-field use - We need to switch branch from 2.1 to 2.x in kibana\tasks\config\esvm.js
and then fix kibana\test\fixtures to remove multi_field and still load all data so tests pass.",0,fix automated test data load remove deprecated multi field use   we need to switch branch from     to   x in kibana tasks config esvm js  and then fix kibana test fixtures to remove multi field and still load all data so tests pass ,0
189718,15193903713.0,IssuesEvent,2021-02-16 02:04:31,golang/go,https://api.github.com/repos/golang/go,closed,x/website: update /doc/install/source page after GO386 changes,Documentation NeedsFix early-in-cycle release-blocker,"The [Installing Go from source](https://tip.golang.org/doc/install/source#environment) page says (in the section dedicated to Env Variables):

> $GO386 (for 386 only, default is auto-detected if built on either 386 or amd64, 387 otherwise)
> 
> This controls the code generated by gc to use either the 387 floating-point unit (set to 387) or SSE2 instructions (set to sse2) for floating point computations.
> - GO386=387: use x87 for floating point operations; should support all x86 chips (Pentium MMX or later).
> - GO386=sse2: use SSE2 for floating point operations; has better performance than 387, but only available on Pentium 4/Opteron/Athlon 64 or later.

The section should be updated to reflect the planned 1.16 deprecation of 387, and the softfloat support.

cc @dmitshur ",1.0,"x/website: update /doc/install/source page after GO386 changes - The [Installing Go from source](https://tip.golang.org/doc/install/source#environment) page says (in the section dedicated to Env Variables):

> $GO386 (for 386 only, default is auto-detected if built on either 386 or amd64, 387 otherwise)
> 
> This controls the code generated by gc to use either the 387 floating-point unit (set to 387) or SSE2 instructions (set to sse2) for floating point computations.
> - GO386=387: use x87 for floating point operations; should support all x86 chips (Pentium MMX or later).
> - GO386=sse2: use SSE2 for floating point operations; has better performance than 387, but only available on Pentium 4/Opteron/Athlon 64 or later.

The section should be updated to reflect the planned 1.16 deprecation of 387, and the softfloat support.

cc @dmitshur ",1,x website  update  doc install source page after   changes   the     page says  in the section dedicated to env variables            for   only  default is auto detected if built on either   or      otherwise         this controls the code generated by gc to use either the   floating point unit  set to    or   instructions  set to    for floating point computations            use   for floating point operations  should support all   chips  pentium mmx or later             use   for floating point operations  has better performance than    but only available on pentium   opteron athlon   or later     the section should be updated to reflect the planned     deprecation of    and the softfloat support     cc  dmitshur ,1
155788,13633041677.0,IssuesEvent,2020-09-24 20:41:51,golang/go,https://api.github.com/repos/golang/go,closed,spec: a small imperfection in spec,Documentation NeedsFix,"There is one line in spec:
```
x == y+1 && <-chanPtr > 0
```

The name `chanPtr` looks not very nature. Is `chanInt` better?",1.0,"spec: a small imperfection in spec - There is one line in spec:
```
x == y+1 && <-chanPtr > 0
```

The name `chanPtr` looks not very nature. Is `chanInt` better?",1,spec  a small imperfection in spec   there is one line in spec        x    y                  the name  chanptr  looks not very nature  is  chanint  better ,1
65092,8787521746.0,IssuesEvent,2018-12-20 18:57:26,golang/go,https://api.github.com/repos/golang/go,closed,"os, os/signal: inconsistent documentation",Documentation NeedsFix OS-Windows,"I'm trying to define cleanup behavior in a Windows program, so I want to catch a signal, do some cleanup, and then exit the program. I don't have a Windows machine though so testing this is sort of tricky.

The docs for `os.Interrupt` state:

>  The only signal values guaranteed to be present in the os package on all systems are Interrupt (send the process an interrupt) and Kill (force the process to exit). Interrupt is not implemented on Windows; using it with os.Process.Signal will return an error. 

However, the docs for `os/signal` state, under the Windows section:

>  On Windows a ^C (Control-C) or ^BREAK (Control-Break) normally cause the program to exit. If Notify is called for os.Interrupt, ^C or ^BREAK will cause os.Interrupt to be sent on the channel, and the program will not exit. 

I'm confused how Interrupt can be all of:

- guaranteed to be present
- not implemented
- calling Notify() can cause it to be sent on the channel when a user hits ^BREAK

Searching the `os` package source code for Interrupt seems to show it's only defined for unix/posix GOOS's and not for Windows. It might be nice to add a short doc to the `os` package explaining how it gets sent (if I am reading correctly, from `runtime/os_windows.go:ctrlhandler1` and `runtime/sigqueue.go:sigsend`).",1.0,"os, os/signal: inconsistent documentation - I'm trying to define cleanup behavior in a Windows program, so I want to catch a signal, do some cleanup, and then exit the program. I don't have a Windows machine though so testing this is sort of tricky.

The docs for `os.Interrupt` state:

>  The only signal values guaranteed to be present in the os package on all systems are Interrupt (send the process an interrupt) and Kill (force the process to exit). Interrupt is not implemented on Windows; using it with os.Process.Signal will return an error. 

However, the docs for `os/signal` state, under the Windows section:

>  On Windows a ^C (Control-C) or ^BREAK (Control-Break) normally cause the program to exit. If Notify is called for os.Interrupt, ^C or ^BREAK will cause os.Interrupt to be sent on the channel, and the program will not exit. 

I'm confused how Interrupt can be all of:

- guaranteed to be present
- not implemented
- calling Notify() can cause it to be sent on the channel when a user hits ^BREAK

Searching the `os` package source code for Interrupt seems to show it's only defined for unix/posix GOOS's and not for Windows. It might be nice to add a short doc to the `os` package explaining how it gets sent (if I am reading correctly, from `runtime/os_windows.go:ctrlhandler1` and `runtime/sigqueue.go:sigsend`).",1,os  os signal  inconsistent documentation   i m trying to define cleanup behavior in a windows program  so i want to catch a signal  do some cleanup  and then exit the program  i don t have a windows machine though so testing this is sort of tricky     the docs for  os interrupt  state        the only signal values guaranteed to be present in the os package on all systems are interrupt  send the process an interrupt  and kill  force the process to exit   interrupt is not implemented on windows  using it with os process signal will return an error      however  the docs for  os signal  state  under the windows section        on windows a  c  control c  or  break  control break  normally cause the program to exit  if notify is called for os interrupt   c or  break will cause os interrupt to be sent on the channel  and the program will not exit      i m confused how interrupt can be all of       guaranteed to be present    not implemented    calling notify   can cause it to be sent on the channel when a user hits  break    searching the  os  package source code for interrupt seems to show it s only defined for unix posix goos s and not for windows  it might be nice to add a short doc to the  os  package explaining how it gets sent  if i am reading correctly  from  runtime os windows go    and  runtime sigqueue go sigsend   ,1
400037,27266359620.0,IssuesEvent,2023-02-22 18:21:39,golang/go,https://api.github.com/repos/golang/go,opened,doc: write release notes for Go 1.21,Documentation NeedsFix release-blocker umbrella,"This is the tracking issue for writing the Go 1.21 Release Notes. The version at tip can be viewed at https://tip.golang.org/doc/go1.21.

When the Go 1.21 Release Notes are complete, this should be closed, and a similar issue should be made for the next release. Previous issues are https://github.com/golang/go/issues/51400, https://github.com/golang/go/issues/47694, https://github.com/golang/go/issues/44513, etc.

",1.0,"doc: write release notes for Go 1.21 - This is the tracking issue for writing the Go 1.21 Release Notes. The version at tip can be viewed at https://tip.golang.org/doc/go1.21.

When the Go 1.21 Release Notes are complete, this should be closed, and a similar issue should be made for the next release. Previous issues are https://github.com/golang/go/issues/51400, https://github.com/golang/go/issues/47694, https://github.com/golang/go/issues/44513, etc.

",1,doc  write release notes for go       this is the tracking issue for writing the go     release notes  the version at tip can be viewed at      when the go     release notes are complete  this should be closed  and a similar issue should be made for the next release  previous issues are       etc     ,1
90325,10678700100.0,IssuesEvent,2019-10-21 17:48:09,golang/go,https://api.github.com/repos/golang/go,closed,io: CopyBuffer should document when buf is not used,Documentation NeedsDecision,"The follow is the comment for io.CopyBuffer,
// CopyBuffer is identical to Copy except that it stages through the
// provided buffer (if one is required) rather than allocating a
// temporary one. If buf is nil, one is allocated; otherwise if it has
// zero length, CopyBuffer panics.
func CopyBuffer(dst Writer, src Reader, buf []byte) (written int64, err error) 

 which is not precise enough, in the case of src implements the WriterTo interface or the case of if dst implements the ReaderFrom interface , buf will be ignore ,which is not mentioned at all. Which is very easy to lead people to wrong way.
",1.0,"io: CopyBuffer should document when buf is not used - The follow is the comment for io.CopyBuffer,
// CopyBuffer is identical to Copy except that it stages through the
// provided buffer (if one is required) rather than allocating a
// temporary one. If buf is nil, one is allocated; otherwise if it has
// zero length, CopyBuffer panics.
func CopyBuffer(dst Writer, src Reader, buf []byte) (written int64, err error) 

 which is not precise enough, in the case of src implements the WriterTo interface or the case of if dst implements the ReaderFrom interface , buf will be ignore ,which is not mentioned at all. Which is very easy to lead people to wrong way.
",1,io  copybuffer should document when buf is not used   the follow is the comment for io copybuffer      copybuffer is identical to copy except that it stages through the     provided buffer  if one is required  rather than allocating a     temporary one  if buf is nil  one is allocated  otherwise if it has     zero length  copybuffer panics   func copybuffer dst writer  src reader  buf  byte   written    err error       which is not precise enough  in the case of src implements the writerto interface or the case of if dst implements the readerfrom interface   buf will be ignore  which is not mentioned at all  which is very easy to lead people to wrong way   ,1
57429,3082003661.0,IssuesEvent,2015-08-23 09:35:19,pavel-pimenov/flylinkdc-r5xx,https://api.github.com/repos/pavel-pimenov/flylinkdc-r5xx,opened,Сделать более простым для понимания пользователя перевод ошибок подключения к хабу.,Component-UI enhancement imported Priority-Medium,"_From [tret2...@gmail.com](https://code.google.com/u/116508191076211387118/) on March 20, 2013 04:22:30_

Например:
*** Удаленный хост принудительно разорвал существующее подключение.[error: 10054]
*** Требуемый адрес для своего контекста неверен.[error: 10049]
*** Попытка установить соединение была безуспешной, т.к. от другого компьютера за требуемое время не получен нужный отклик, или было разорвано уже установленное соединение из-за неверного отклика уже подключенного компьютера.[error: 10060]

Большая часть пользователей не понимает что это означает. За перевод кода ошибки в удобочитаемый текст на языке интерфейса ОС отвечает функция FormatMessage. Однако если мы сами начнём переводить сообщения об ошибках сокетов, то получится что пока сообщение не будет переведено на какой либо язык, ошибка будет отображаться на английском.

Я пока вижу вариант к сообщению об ошибке лепить ссылку вида http://flylinkdc.com/dokuwiki/doku.php?id=en:socketerror с дальнейшим указанием кода. Ссылку легко локализовать. На сайте будет только поясняющий данную ошибку текст в более простом для понимания изложении и так мы не потеряем оригинальный перевод ошибки от ОС, пока не будет готов более простое изложение ошибки на языке интерфейса.

У кого какие предложения будут ?

_Original issue: http://code.google.com/p/flylinkdc/issues/detail?id=948_",1.0,"Сделать более простым для понимания пользователя перевод ошибок подключения к хабу. - _From [tret2...@gmail.com](https://code.google.com/u/116508191076211387118/) on March 20, 2013 04:22:30_

Например:
*** Удаленный хост принудительно разорвал существующее подключение.[error: 10054]
*** Требуемый адрес для своего контекста неверен.[error: 10049]
*** Попытка установить соединение была безуспешной, т.к. от другого компьютера за требуемое время не получен нужный отклик, или было разорвано уже установленное соединение из-за неверного отклика уже подключенного компьютера.[error: 10060]

Большая часть пользователей не понимает что это означает. За перевод кода ошибки в удобочитаемый текст на языке интерфейса ОС отвечает функция FormatMessage. Однако если мы сами начнём переводить сообщения об ошибках сокетов, то получится что пока сообщение не будет переведено на какой либо язык, ошибка будет отображаться на английском.

Я пока вижу вариант к сообщению об ошибке лепить ссылку вида http://flylinkdc.com/dokuwiki/doku.php?id=en:socketerror с дальнейшим указанием кода. Ссылку легко локализовать. На сайте будет только поясняющий данную ошибку текст в более простом для понимания изложении и так мы не потеряем оригинальный перевод ошибки от ОС, пока не будет готов более простое изложение ошибки на языке интерфейса.

У кого какие предложения будут ?

_Original issue: http://code.google.com/p/flylinkdc/issues/detail?id=948_",0,сделать более простым для понимания пользователя перевод ошибок подключения к хабу     from     on march              например       удаленный хост принудительно разорвал существующее подключение        требуемый адрес для своего контекста неверен        попытка установить соединение была безуспешной  т к  от другого компьютера за требуемое время не получен нужный отклик  или было разорвано уже установленное соединение из за неверного отклика уже подключенного компьютера      большая часть пользователей не понимает что это означает  за перевод кода ошибки в удобочитаемый текст на языке интерфейса ос отвечает функция formatmessage  однако если мы сами начнём переводить сообщения об ошибках сокетов  то получится что пока сообщение не будет переведено на какой либо язык  ошибка будет отображаться на английском     я пока вижу вариант к сообщению об ошибке лепить ссылку вида   с дальнейшим указанием кода  ссылку легко локализовать  на сайте будет только поясняющий данную ошибку текст в более простом для понимания изложении и так мы не потеряем оригинальный перевод ошибки от ос  пока не будет готов более простое изложение ошибки на языке интерфейса     у кого какие предложения будут     original issue   ,0
13763,10452203283.0,IssuesEvent,2019-09-19 14:17:06,code4romania/monitorizare-vot-votanti-client,https://api.github.com/repos/code4romania/monitorizare-vot-votanti-client,opened,Move configuration from code to env file,enhancement frontend infrastructure react,"Currently the configuration for the API url is found in app/api/config.js
The configuration should be moved in env files, with an env file for each of the environments we might want to deploy: development / testing / production.",1.0,"Move configuration from code to env file - Currently the configuration for the API url is found in app/api/config.js
The configuration should be moved in env files, with an env file for each of the environments we might want to deploy: development / testing / production.",0,move configuration from code to env file   currently the configuration for the api url is found in app api config js  the configuration should be moved in env files  with an env file for each of the environments we might want to deploy  development   testing   production ,0
208731,23643127498.0,IssuesEvent,2022-08-25 19:05:49,elastic/kibana,https://api.github.com/repos/elastic/kibana,closed,Copy to Space should allow associated index patterns to be changed ,blocked Team:Security enhancement loe:hours Feature:Security/Spaces impact:low,"When _importing_ saved objects there's a mechanism for changing the associated index pattern, however this doesn't seem to be an option when copying saved objects between spaces (it would be excellent if we could have this!).

_Originally posted by @rozling in https://github.com/elastic/kibana/issues/27004#issuecomment-595261579_",True,"Copy to Space should allow associated index patterns to be changed  - When _importing_ saved objects there's a mechanism for changing the associated index pattern, however this doesn't seem to be an option when copying saved objects between spaces (it would be excellent if we could have this!).

_Originally posted by @rozling in https://github.com/elastic/kibana/issues/27004#issuecomment-595261579_",0,copy to space should allow associated index patterns to be changed    when  importing  saved objects there s a mechanism for changing the associated index pattern  however this doesn t seem to be an option when copying saved objects between spaces  it would be excellent if we could have this        originally posted by  rozling in  ,0
19780,13451958169.0,IssuesEvent,2020-09-08 21:11:13,pulibrary/dspace-development,https://api.github.com/repos/pulibrary/dspace-development,opened,Request a new VM and migrate the OA Waiver application from the QA environment (oawaiverdev.princeton.edu),infrastructure oawaiver,This is probably best to recommend given that long-term maintenance commitments for this service require continued server administration for the current OIT-managed server.,1.0,Request a new VM and migrate the OA Waiver application from the QA environment (oawaiverdev.princeton.edu) - This is probably best to recommend given that long-term maintenance commitments for this service require continued server administration for the current OIT-managed server.,0,request a new vm and migrate the oa waiver application from the qa environment  oawaiverdev princeton edu    this is probably best to recommend given that long term maintenance commitments for this service require continued server administration for the current oit managed server ,0
365987,25562770277.0,IssuesEvent,2022-11-30 12:06:32,golang/go,https://api.github.com/repos/golang/go,opened,testing: document the usage of export_test.go ,Documentation,"While I am trying to introduce the usage of `export_test.go` to someone new to Go, I failed to find a document regarding this feature neither in [testing](https://pkg.go.dev/testing) nor in [go command](https://pkg.go.dev/cmd/go@go1.19.3#hdr-Testing_flags), not even in the wiki.

I am not sure if I overlooked somewhere, but I would propose documenting this somewhere more visible, such as the [testing](https://pkg.go.dev/testing) package's document.

",1.0,"testing: document the usage of export_test.go  - While I am trying to introduce the usage of `export_test.go` to someone new to Go, I failed to find a document regarding this feature neither in [testing](https://pkg.go.dev/testing) nor in [go command](https://pkg.go.dev/cmd/go@go1.19.3#hdr-Testing_flags), not even in the wiki.

I am not sure if I overlooked somewhere, but I would propose documenting this somewhere more visible, such as the [testing](https://pkg.go.dev/testing) package's document.

",1,testing  document the usage of export test go    while i am trying to introduce the usage of  export test go  to someone new to go  i failed to find a document regarding this feature neither in     nor in     not even in the wiki     i am not sure if i overlooked somewhere  but i would propose documenting this somewhere more visible  such as the     package s document     ,1
14607,3869666475.0,IssuesEvent,2016-04-10 18:50:52,golang/go,https://api.github.com/repos/golang/go,closed,html: UnescapeString documentation error,Documentation,"Go 1.6, Go Playground environment

Documentation of [`html.UnescapeString()`](https://golang.org/pkg/html/#UnescapeString) contains a mistake. Quoting:

> It unescapes a larger range of entities than EscapeString escapes. For example, `""&aacute;""` unescapes to ""á"", as does `""&#225;""` and **""&xE1;""**. 

It should be **`&#xE1;`** (there is a missing hashmark `#` in the doc).

The implementation is good, but it is documented falsely.

	fmt.Println(html.UnescapeString(`&xE1;`))  // Output: &xE1;
	fmt.Println(html.UnescapeString(`&#xE1;`)) // Output: á

Output is as expected.

Playground example:

http://play.golang.org/p/S5EaiVfMKs
",1.0,"html: UnescapeString documentation error - Go 1.6, Go Playground environment

Documentation of [`html.UnescapeString()`](https://golang.org/pkg/html/#UnescapeString) contains a mistake. Quoting:

> It unescapes a larger range of entities than EscapeString escapes. For example, `""&aacute;""` unescapes to ""á"", as does `""&#225;""` and **""&xE1;""**. 

It should be **`&#xE1;`** (there is a missing hashmark `#` in the doc).

The implementation is good, but it is documented falsely.

	fmt.Println(html.UnescapeString(`&xE1;`))  // Output: &xE1;
	fmt.Println(html.UnescapeString(`&#xE1;`)) // Output: á

Output is as expected.

Playground example:

http://play.golang.org/p/S5EaiVfMKs
",1,html  unescapestring documentation error   go      go playground environment    documentation of     contains a mistake  quoting       it unescapes a larger range of entities than escapestring escapes  for example     aacute    unescapes to  á   as does          and                it should be             there is a missing hashmark     in the doc      the implementation is good  but it is documented falsely     	fmt println html unescapestring             output       	fmt println html unescapestring             output  á    output is as expected     playground example        ,1
138194,30828428603.0,IssuesEvent,2023-08-01 22:20:35,dotnet/runtime,https://api.github.com/repos/dotnet/runtime,closed,Assertion failed 'assignedInterval->isActive == false',arch-arm64 os-windows JitStress area-CodeGen-coreclr blocking-clean-ci-optional in-pr,"win/arm64

Pipeline: runtime-coreclr jitstress-isas-arm
coreclr windows arm64 Checked jitstress_isas_nohwintrinsic @ Windows.11.Arm64.Open
Directed_3 Work Item

https://dev.azure.com/dnceng-public/public/_build/results?buildId=302647&view=ms.vss-test-web.build-test-results-tab&runId=6137478&paneView=debug&resultId=110091

```
set DOTNET_TieredCompilation=0
set DOTNET_EnableHWIntrinsic=0
```

```
21:11:55.978 Running test: JIT/Directed/StructABI/structreturn/structreturn.dll

Assert failure(PID 5716 [0x00001654], Thread: 2944 [0x0b80]): Assertion failed 'assignedInterval->isActive == false' in 'TestHFAandHVA:ReturnVectorInt2[float](System.Numerics.Vector`1[float],System.Numerics.Vector`1[float]):System.Numerics.Vector`1[int]' during 'Linear scan register alloc' (IL size 15; hash 0x71c6e7e1; FullOpts)

    File: D:\a\_work\1\s\src\coreclr\jit\lsra.cpp Line: 3304
    Image: C:\h\w\BF8C09A5\p\corerun.exe
```
",1.0,"Assertion failed 'assignedInterval->isActive == false' - win/arm64

Pipeline: runtime-coreclr jitstress-isas-arm
coreclr windows arm64 Checked jitstress_isas_nohwintrinsic @ Windows.11.Arm64.Open
Directed_3 Work Item

https://dev.azure.com/dnceng-public/public/_build/results?buildId=302647&view=ms.vss-test-web.build-test-results-tab&runId=6137478&paneView=debug&resultId=110091

```
set DOTNET_TieredCompilation=0
set DOTNET_EnableHWIntrinsic=0
```

```
21:11:55.978 Running test: JIT/Directed/StructABI/structreturn/structreturn.dll

Assert failure(PID 5716 [0x00001654], Thread: 2944 [0x0b80]): Assertion failed 'assignedInterval->isActive == false' in 'TestHFAandHVA:ReturnVectorInt2[float](System.Numerics.Vector`1[float],System.Numerics.Vector`1[float]):System.Numerics.Vector`1[int]' during 'Linear scan register alloc' (IL size 15; hash 0x71c6e7e1; FullOpts)

    File: D:\a\_work\1\s\src\coreclr\jit\lsra.cpp Line: 3304
    Image: C:\h\w\BF8C09A5\p\corerun.exe
```
",0,assertion failed  assignedinterval  isactive    false    win      pipeline  runtime coreclr jitstress isas arm  coreclr windows   checked jitstress isas nohwintrinsic   windows     open  directed   work item              set dotnet tieredcompilation    set dotnet enablehwintrinsic                        running test  jit directed structabi structreturn structreturn dll    assert failure pid      thread        assertion failed  assignedinterval  isactive    false  in  testhfaandhva    system numerics vector    system numerics vector     system numerics vector     during  linear scan register alloc   il size    hash    fullopts         file  d  a  work   s src coreclr jit lsra cpp line         image  c  h w   p corerun exe       ,0
7151,3081299435.0,IssuesEvent,2015-08-22 15:39:45,golang/go,https://api.github.com/repos/golang/go,closed,cmd/compile: compile tool identifies itself as 6g,Documentation,"```
% go tool compile -XXX | head -n2
flag provided but not defined: -XXX
usage: 6g [options] file.go...
  -%    debug non-static initializers
```",1.0,"cmd/compile: compile tool identifies itself as 6g - ```
% go tool compile -XXX | head -n2
flag provided but not defined: -XXX
usage: 6g [options] file.go...
  -%    debug non-static initializers
```",1,cmd compile  compile tool identifies itself as            go tool compile  xxx   head     flag provided but not defined   xxx  usage      file go             debug non static initializers     ,1
644351,20975277426.0,IssuesEvent,2022-03-28 14:44:37,GoogleCloudPlatform/python-docs-samples,https://api.github.com/repos/GoogleCloudPlatform/python-docs-samples,closed,monitoring.api.v3.api-client.custom_metric_test: test_custom_metric failed,:rotating_light: priority: p1 type: bug api: monitoring samples flakybot: issue flakybot: flaky,"Note: #7105 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.

----

commit: 7c48837534a86651b1f803dadf930a5160b1c29c
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/b9e0d730-ec18-4a94-a9c0-da2eb42d97b8), [Sponge](http://sponge2/b9e0d730-ec18-4a94-a9c0-da2eb42d97b8)
status: failed
<details><summary>Test output</summary><br><pre>Traceback (most recent call last):
  File ""/workspace/monitoring/api/v3/api-client/custom_metric_test.py"", line 82, in custom_metric
    delete_metric_descriptor(client, custom_metric_descriptor['name'])
  File ""/workspace/monitoring/api/v3/api-client/custom_metric.py"", line 80, in delete_metric_descriptor
    client.projects().metricDescriptors().delete(
  File ""/workspace/monitoring/api/v3/api-client/.nox/py-3-8/lib/python3.8/site-packages/googleapiclient/_helpers.py"", line 131, in positional_wrapper
    return wrapped(*args, **kwargs)
  File ""/workspace/monitoring/api/v3/api-client/.nox/py-3-8/lib/python3.8/site-packages/googleapiclient/http.py"", line 937, in execute
    raise HttpError(resp, content, uri=self.uri)
googleapiclient.errors.HttpError: <HttpError 500 when requesting https://monitoring.googleapis.com/v3/projects/python-docs-samples-tests/metricDescriptors/custom.googleapis.com/385888ee5bc14a168e5c48ccd225231e?alt=json returned ""Internal error encountered. Please retry after a few seconds. If internal errors persist, contact support at https://cloud.google.com/support/docs."". Details: ""Internal error encountered. Please retry after a few seconds. If internal errors persist, contact support at https://cloud.google.com/support/docs.""></pre></details>",1.0,"monitoring.api.v3.api-client.custom_metric_test: test_custom_metric failed - Note: #7105 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.

----

commit: 7c48837534a86651b1f803dadf930a5160b1c29c
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/b9e0d730-ec18-4a94-a9c0-da2eb42d97b8), [Sponge](http://sponge2/b9e0d730-ec18-4a94-a9c0-da2eb42d97b8)
status: failed
<details><summary>Test output</summary><br><pre>Traceback (most recent call last):
  File ""/workspace/monitoring/api/v3/api-client/custom_metric_test.py"", line 82, in custom_metric
    delete_metric_descriptor(client, custom_metric_descriptor['name'])
  File ""/workspace/monitoring/api/v3/api-client/custom_metric.py"", line 80, in delete_metric_descriptor
    client.projects().metricDescriptors().delete(
  File ""/workspace/monitoring/api/v3/api-client/.nox/py-3-8/lib/python3.8/site-packages/googleapiclient/_helpers.py"", line 131, in positional_wrapper
    return wrapped(*args, **kwargs)
  File ""/workspace/monitoring/api/v3/api-client/.nox/py-3-8/lib/python3.8/site-packages/googleapiclient/http.py"", line 937, in execute
    raise HttpError(resp, content, uri=self.uri)
googleapiclient.errors.HttpError: <HttpError 500 when requesting https://monitoring.googleapis.com/v3/projects/python-docs-samples-tests/metricDescriptors/custom.googleapis.com/385888ee5bc14a168e5c48ccd225231e?alt=json returned ""Internal error encountered. Please retry after a few seconds. If internal errors persist, contact support at https://cloud.google.com/support/docs."". Details: ""Internal error encountered. Please retry after a few seconds. If internal errors persist, contact support at https://cloud.google.com/support/docs.""></pre></details>",0,monitoring api   api client custom metric test  test custom metric 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   traceback  most recent call last     file   workspace monitoring api   api client custom metric test py   line    in custom metric     delete metric descriptor client  custom metric descriptor     file   workspace monitoring api   api client custom metric py   line    in delete metric descriptor     client projects   metricdescriptors   delete    file   workspace monitoring api   api client  nox py     lib     site packages googleapiclient  helpers py   line    in positional wrapper     return wrapped  args    kwargs    file   workspace monitoring api   api client  nox py     lib     site packages googleapiclient http py   line    in execute     raise httperror resp  content  uri self uri  googleapiclient errors httperror   httperror   when requesting   returned  internal error encountered  please retry after a few seconds  if internal errors persist  contact support at   details   internal error encountered  please retry after a few seconds  if internal errors persist  contact support at  ,0
99756,21038532747.0,IssuesEvent,2022-03-31 10:05:11,Regalis11/Barotrauma,https://api.github.com/repos/Regalis11/Barotrauma,closed,Gender restrictions broken for custom humans [unstable],Bug Code Modding,"Gender restrictions don't seem to work on custom humans (created either by copying human in the character editor or by overriding) after the modding-refactor.

Seems to work properly in the release version though.

![image.png](https://images.zenhubusercontent.com/5c93b12055cf186934fc0a03/c757a936-bfee-4911-883d-4afe75069637)",1.0,"Gender restrictions broken for custom humans [unstable] - Gender restrictions don't seem to work on custom humans (created either by copying human in the character editor or by overriding) after the modding-refactor.

Seems to work properly in the release version though.

![image.png](https://images.zenhubusercontent.com/5c93b12055cf186934fc0a03/c757a936-bfee-4911-883d-4afe75069637)",0,gender restrictions broken for custom humans     gender restrictions don t seem to work on custom humans  created either by copying human in the character editor or by overriding  after the modding refactor   seems to work properly in the release version though       ,0
139927,12882288436.0,IssuesEvent,2020-07-12 16:12:40,golang/go,https://api.github.com/repos/golang/go,closed,spec: struct can implement an interface with an inherited method but attempting to call that method can cause an unexpected panic,Documentation NeedsInvestigation,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14.4 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

I believe go1.14.4 is the latest stable release, so yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/finnb/.cache/go-build""
GOENV=""/home/finnb/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/finnb/go:/home/finnb/git/finnbear/mazean""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/snap/go/5830""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/snap/go/5830/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build362984802=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

**Playground link:** https://play.golang.org/p/Xf3mskprGZV
```go
package main

import (
	""fmt""
)

type Nilable interface {
	IsNil() bool
}

type Child struct {

}

func (child *Child) IsNil() bool {
	return child == nil
}

type Parent struct {
	Child
}

func main() {
	var something Nilable

	var child *Child
	something = child
	fmt.Println(something.IsNil())

	var parent *Parent
	something = parent
	fmt.Println(something.IsNil()) // Panic here
}
```

### What did you expect to see?

```
true
true
```

### What did you see instead?

```
true
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x4919f5]

goroutine 1 [running]:
main.(*Parent).IsNil(0x0, 0xc0000b6008)
	<autogenerated>:1 +0x5
main.main()
	/tmp/sandbox080043792/prog.go:36 +0xad
```
I suspect what is happening is that calling `IsNil` on `parent` acts on `parent.Child`, thus dereferencing `Child` from a nil pointer `parent`, but this happens silently. I think one of the following should be done:
1) Assuming my theory is correct, the panic message should be improved to not act as if the issue occurred in the `(*Child) IsNil` receiver but in the intermediate step of accessing `parent.Child`
2) The documentation should be updated to warn about this behavior
3) In the unlikely event that this is a bug in Go, it should be fixed",1.0,"spec: struct can implement an interface with an inherited method but attempting to call that method can cause an unexpected panic - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14.4 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

I believe go1.14.4 is the latest stable release, so yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/finnb/.cache/go-build""
GOENV=""/home/finnb/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/finnb/go:/home/finnb/git/finnbear/mazean""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/snap/go/5830""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/snap/go/5830/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build362984802=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

**Playground link:** https://play.golang.org/p/Xf3mskprGZV
```go
package main

import (
	""fmt""
)

type Nilable interface {
	IsNil() bool
}

type Child struct {

}

func (child *Child) IsNil() bool {
	return child == nil
}

type Parent struct {
	Child
}

func main() {
	var something Nilable

	var child *Child
	something = child
	fmt.Println(something.IsNil())

	var parent *Parent
	something = parent
	fmt.Println(something.IsNil()) // Panic here
}
```

### What did you expect to see?

```
true
true
```

### What did you see instead?

```
true
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x4919f5]

goroutine 1 [running]:
main.(*Parent).IsNil(0x0, 0xc0000b6008)
	<autogenerated>:1 +0x5
main.main()
	/tmp/sandbox080043792/prog.go:36 +0xad
```
I suspect what is happening is that calling `IsNil` on `parent` acts on `parent.Child`, thus dereferencing `Child` from a nil pointer `parent`, but this happens silently. I think one of the following should be done:
1) Assuming my theory is correct, the panic message should be improved to not act as if the issue occurred in the `(*Child) IsNil` receiver but in the intermediate step of accessing `parent.Child`
2) The documentation should be updated to warn about this behavior
3) In the unlikely event that this is a bug in Go, it should be fixed",1,spec  struct can implement an interface with an inherited method but attempting to call that method can cause an unexpected panic         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version            go version  go version       linux             does this issue reproduce with the latest release     i believe       is the latest stable release  so yes         what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   home finnb  cache go build   goenv   home finnb  config go env   goexe     goflags     gohostarch      gohostos  linux   goinsecure     gonoproxy     gonosumdb     goos  linux   gopath   home finnb go  home finnb git finnbear mazean   goprivate     goproxy     goroot   snap go     gosumdb  sum golang org   gotmpdir     gotooldir   snap go   pkg tool linux     gccgo  gccgo   ar  ar   cc  gcc   cxx  g     cgo enabled      gomod     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches             what did you do       playground link          go  package main    import    	 fmt        type nilable interface    	isnil   bool       type child struct           func  child  child  isnil   bool    	return child    nil       type parent struct    	child       func main      	var something nilable    	var child  child  	something   child  	fmt println something isnil       	var parent  parent  	something   parent  	fmt println something isnil       panic here                what did you expect to see          true  true             what did you see instead          true  panic  runtime error  invalid memory address or nil pointer dereference       goroutine       main   parent  isnil        	        main main    	 tmp   prog go            i suspect what is happening is that calling  isnil  on  parent  acts on  parent child   thus dereferencing  child  from a nil pointer  parent   but this happens silently  i think one of the following should be done      assuming my theory is correct  the panic message should be improved to not act as if the issue occurred in the    child  isnil  receiver but in the intermediate step of accessing  parent child      the documentation should be updated to warn about this behavior     in the unlikely event that this is a bug in go  it should be fixed,1
389619,26825754641.0,IssuesEvent,2023-02-02 12:46:02,golang/go,https://api.github.com/repos/golang/go,closed,go1.20: no docs for golang.org/x/crypto/x509roots/fallback,Documentation,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.20 darwin/arm64
</pre>

### Does this issue reproduce with the latest release?

yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""arm64""
GOBIN=""""
GOCACHE=""/Users/andig/Library/Caches/go-build""
GOENV=""/Users/andig/Library/Application Support/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""arm64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/andig/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/andig/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_arm64""
GOVCS=""""
GOVERSION=""go1.20""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/andig/htdocs/evcc/go.mod""
GOWORK=""""
CGO_CFLAGS=""-O2 -g""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-O2 -g""
CGO_FFLAGS=""-O2 -g""
CGO_LDFLAGS=""-O2 -g""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/sv/rs_453y57xj86xsbz3kw1mbc0000gn/T/go-build1228287512=/tmp/go-build -gno-record-gcc-switches -fno-common""
GOROOT/bin/go version: go version go1.20 darwin/arm64
GOROOT/bin/go tool compile -V: compile version go1.20
uname -v: Darwin Kernel Version 22.2.0: Fri Nov 11 02:04:44 PST 2022; root:xnu-8792.61.2~4/RELEASE_ARM64_T8103
ProductName:		macOS
ProductVersion:		13.1
BuildVersion:		22C65
lldb --version: lldb-1400.0.38.17
Apple Swift version 5.7.2 (swiftlang-5.7.2.135.5 clang-1400.0.29.51)
</pre></details>

### What did you do?

https://go.dev/doc/go1.20 mentions https://pkg.go.dev/crypto/x509#SetFallbackRoots and links https://go.dev/pkg/golang.org/x/crypto/x509roots/fallback. The link is dead afaikt and looking at https://pkg.go.dev/crypto I cannot find any reference to `x509roots`.

### What did you expect to see?

Documentation for the https://go.dev/pkg/golang.org/x/crypto/x509roots/fallback package

### What did you see instead?

No docs.",1.0,"go1.20: no docs for golang.org/x/crypto/x509roots/fallback - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.20 darwin/arm64
</pre>

### Does this issue reproduce with the latest release?

yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""arm64""
GOBIN=""""
GOCACHE=""/Users/andig/Library/Caches/go-build""
GOENV=""/Users/andig/Library/Application Support/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""arm64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/andig/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/andig/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_arm64""
GOVCS=""""
GOVERSION=""go1.20""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/andig/htdocs/evcc/go.mod""
GOWORK=""""
CGO_CFLAGS=""-O2 -g""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-O2 -g""
CGO_FFLAGS=""-O2 -g""
CGO_LDFLAGS=""-O2 -g""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/sv/rs_453y57xj86xsbz3kw1mbc0000gn/T/go-build1228287512=/tmp/go-build -gno-record-gcc-switches -fno-common""
GOROOT/bin/go version: go version go1.20 darwin/arm64
GOROOT/bin/go tool compile -V: compile version go1.20
uname -v: Darwin Kernel Version 22.2.0: Fri Nov 11 02:04:44 PST 2022; root:xnu-8792.61.2~4/RELEASE_ARM64_T8103
ProductName:		macOS
ProductVersion:		13.1
BuildVersion:		22C65
lldb --version: lldb-1400.0.38.17
Apple Swift version 5.7.2 (swiftlang-5.7.2.135.5 clang-1400.0.29.51)
</pre></details>

### What did you do?

https://go.dev/doc/go1.20 mentions https://pkg.go.dev/crypto/x509#SetFallbackRoots and links https://go.dev/pkg/golang.org/x/crypto/x509roots/fallback. The link is dead afaikt and looking at https://pkg.go.dev/crypto I cannot find any reference to `x509roots`.

### What did you expect to see?

Documentation for the https://go.dev/pkg/golang.org/x/crypto/x509roots/fallback package

### What did you see instead?

No docs.",1,     no docs for golang org x crypto   fallback            what version of go are you using   go version            go version  go version     darwin             does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   users andig library caches go build   goenv   users andig library application support go env   goexe     goexperiment     goflags     gohostarch      gohostos  darwin   goinsecure     gomodcache   users andig go pkg mod   gonoproxy     gonosumdb     goos  darwin   gopath   users andig go   goprivate     goproxy     goroot   usr local go   gosumdb  sum golang org   gotmpdir     gotooldir   usr local go pkg tool darwin     govcs     goversion        gccgo  gccgo   ar  ar   cc  clang   cxx  clang     cgo enabled      gomod   users andig htdocs evcc go mod   gowork     cgo cflags      g   cgo cppflags     cgo cxxflags      g   cgo fflags      g   cgo ldflags      g   pkg config  pkg config   gogccflags   fpic  arch    pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders sv rs   t go    tmp go build  gno record gcc switches  fno common   goroot bin go version  go version     darwin    goroot bin go tool compile  v  compile version      uname  v  darwin kernel version        fri nov         pst    root xnu         release      productname 		macos  productversion 		     buildversion 		   lldb   version  lldb          apple swift version        swiftlang           clang                     what did you do       mentions   and links   the link is dead afaikt and looking at   i cannot find any reference to             what did you expect to see     documentation for the   package        what did you see instead     no docs ,1
87367,10544350980.0,IssuesEvent,2019-10-02 16:44:25,golang/go,https://api.github.com/repos/golang/go,closed,math/rand: package docs don't explain the interval notation,Documentation,"### What version of Go are you using (`go version`)?
Whatever version the page at https://golang.org/pkg/math/rand/ is associated with.

### Does this issue reproduce with the latest release?
It is present at the https://golang.org/pkg/math/rand/ page.

### What operating system and processor architecture are you using (`go env`)?
Not relevant for reading docs.

### What did you do?
Reading https://golang.org/pkg/math/rand/ I wanted to understand what interval notation the particular documentation page uses.

### What did you expect to see?
""The documentation for this package uses interval notation with square brackets [, ] to denote included borders and round (, ) to denote excluded. For example, for n>0, [0, n) includes 0 but excludes n.""


### What did you see instead?
""Mathematical interval notation such as [0, n) is used throughout the documentation for this package.""

I'm afraid there is no such thing as ""mathematical interval notation"". Different mathematicians define different notation. I propose that the mentioned documentation also properly defines the notation used in it. Ideally directly, or at least linking to the source of that notation.
",1.0,"math/rand: package docs don't explain the interval notation - ### What version of Go are you using (`go version`)?
Whatever version the page at https://golang.org/pkg/math/rand/ is associated with.

### Does this issue reproduce with the latest release?
It is present at the https://golang.org/pkg/math/rand/ page.

### What operating system and processor architecture are you using (`go env`)?
Not relevant for reading docs.

### What did you do?
Reading https://golang.org/pkg/math/rand/ I wanted to understand what interval notation the particular documentation page uses.

### What did you expect to see?
""The documentation for this package uses interval notation with square brackets [, ] to denote included borders and round (, ) to denote excluded. For example, for n>0, [0, n) includes 0 but excludes n.""


### What did you see instead?
""Mathematical interval notation such as [0, n) is used throughout the documentation for this package.""

I'm afraid there is no such thing as ""mathematical interval notation"". Different mathematicians define different notation. I propose that the mentioned documentation also properly defines the notation used in it. Ideally directly, or at least linking to the source of that notation.
",1,math rand  package docs don t explain the interval notation       what version of go are you using   go version     whatever version the page at   is associated with         does this issue reproduce with the latest release   it is present at the   page         what operating system and processor architecture are you using   go env     not relevant for reading docs         what did you do   reading   i wanted to understand what interval notation the particular documentation page uses         what did you expect to see    the documentation for this package uses interval notation with square brackets   to denote included borders and round      to denote excluded  for example  for n        n  includes   but excludes n            what did you see instead    mathematical interval notation such as     n  is used throughout the documentation for this package      i m afraid there is no such thing as  mathematical interval notation   different mathematicians define different notation  i propose that the mentioned documentation also properly defines the notation used in it  ideally directly  or at least linking to the source of that notation   ,1
6739,3044312415.0,IssuesEvent,2015-08-10 08:31:31,golang/go,https://api.github.com/repos/golang/go,closed,build: ARM cross compilation issue with 1.5rc1,Documentation,"I am getting the error `Illegal instruction` when running a simple program (as simple as a ""hello world"" with no dependencies, even when only using print(""hello world"")) on linux/arm (raspberry pi B model) which I cross compiled on linux/amd64 with 1.5.rc1 no matter what value I set GOARM to (tested it with 5, 6 and 7).

Running the program with gdb gives me this error:

    Program received signal SIGILL, Illegal instruction.
    runtime.check () at <GOROOT>/src/runtime/runtime1.go:146

so I guess it is related to the float32 variables here: https://github.com/golang/go/blob/master/src/runtime/runtime1.go#L146

The very same program cross compiles just fine with 1.4.2 (using GOARM 5 and 6) and just gives me the usual error when trying `GOARM=7` 

    runtime: this CPU has no VFPv3 floating point hardware, so it cannot run
    this GOARM=7 binary. Recompile using GOARM=6.",1.0,"build: ARM cross compilation issue with 1.5rc1 - I am getting the error `Illegal instruction` when running a simple program (as simple as a ""hello world"" with no dependencies, even when only using print(""hello world"")) on linux/arm (raspberry pi B model) which I cross compiled on linux/amd64 with 1.5.rc1 no matter what value I set GOARM to (tested it with 5, 6 and 7).

Running the program with gdb gives me this error:

    Program received signal SIGILL, Illegal instruction.
    runtime.check () at <GOROOT>/src/runtime/runtime1.go:146

so I guess it is related to the float32 variables here: https://github.com/golang/go/blob/master/src/runtime/runtime1.go#L146

The very same program cross compiles just fine with 1.4.2 (using GOARM 5 and 6) and just gives me the usual error when trying `GOARM=7` 

    runtime: this CPU has no VFPv3 floating point hardware, so it cannot run
    this GOARM=7 binary. Recompile using GOARM=6.",1,build  arm cross compilation issue with       i am getting the error  illegal instruction  when running a simple program  as simple as a  hello world  with no dependencies  even when only using print  hello world    on linux arm  raspberry pi b model  which i cross compiled on linux   with       no matter what value i set goarm to  tested it with      and        running the program with gdb gives me this error         program received signal sigill  illegal instruction       runtime check    at   src runtime   go      so i guess it is related to the   variables here       the very same program cross compiles just fine with        using goarm   and    and just gives me the usual error when trying  goarm            runtime  this cpu has no   floating point hardware  so it cannot run      this goarm   binary  recompile using goarm   ,1
20705,4615157172.0,IssuesEvent,2016-09-25 23:43:22,golang/go,https://api.github.com/repos/golang/go,closed,net/rpc: Client.Close() method has no godoc,Documentation,"https://tip.golang.org/pkg/net/rpc/#Client.Close

It would help to have some godoc on net/rpc Client.Close() method to explain what guarantees it makes, what happens to the Calls when Close() is called, what kind of errors one can expect, etc.
Thank you.",1.0,"net/rpc: Client.Close() method has no godoc - https://tip.golang.org/pkg/net/rpc/#Client.Close

It would help to have some godoc on net/rpc Client.Close() method to explain what guarantees it makes, what happens to the Calls when Close() is called, what kind of errors one can expect, etc.
Thank you.",1,net rpc  client close   method has no godoc        it would help to have some godoc on net rpc client close   method to explain what guarantees it makes  what happens to the calls when close   is called  what kind of errors one can expect  etc   thank you ,1
277221,21033186189.0,IssuesEvent,2022-03-31 04:12:11,golang/go,https://api.github.com/repos/golang/go,closed,cmd/link: -X requires the full import path for vendored packages,Documentation help wanted,"Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
go version go1.10.1 linux/amd64
### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/root/.cache/go-build""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/go""
GORACE=""""
GOROOT=""/usr/local/go""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build528112336=/tmp/go-build -gno-record-gcc-switches""
```

### What did you do?
```
$ find
main.go
vendor/github.com/ckeyer/commons/version/version.go

$ go build -a -v -ldflags=""-X github.com/ckeyer/commons/version.version=v0.1.0"" main.go version
```
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.


### What did you expect to see?
I want to see print the `version v0.1.0`

### What did you see instead?
none

I use `go build -a -v -ldflags=""-X github.com/ckeyer/frog/vendor/github.com/ckeyer/commons/version.version=v0.1.0"" main.go version` ,it works.
",1.0,"cmd/link: -X requires the full import path for vendored packages - Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
go version go1.10.1 linux/amd64
### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/root/.cache/go-build""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/go""
GORACE=""""
GOROOT=""/usr/local/go""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build528112336=/tmp/go-build -gno-record-gcc-switches""
```

### What did you do?
```
$ find
main.go
vendor/github.com/ckeyer/commons/version/version.go

$ go build -a -v -ldflags=""-X github.com/ckeyer/commons/version.version=v0.1.0"" main.go version
```
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.


### What did you expect to see?
I want to see print the `version v0.1.0`

### What did you see instead?
none

I use `go build -a -v -ldflags=""-X github.com/ckeyer/frog/vendor/github.com/ckeyer/commons/version.version=v0.1.0"" main.go version` ,it works.
",1,cmd link   x requires the full import path for vendored packages   please answer these questions before submitting your issue  thanks           what version of go are you using   go version     go version       linux        does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env          goarch      gobin     gocache   root  cache go build   goexe     gohostarch      gohostos  linux   goos  linux   gopath   go   gorace     goroot   usr local go   gotmpdir     gotooldir   usr local go pkg tool linux     gccgo  gccgo   cc  gcc   cxx  g     cgo enabled      cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches              what did you do          find  main go  vendor github com ckeyer commons version version go      go build  a  v  ldflags   x github com ckeyer commons version version        main go version       if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best           what did you expect to see   i want to see print the  version               what did you see instead   none    i use  go build  a  v  ldflags   x github com ckeyer frog vendor github com ckeyer commons version version        main go version   it works   ,1
267654,20239268418.0,IssuesEvent,2022-02-14 07:30:06,golang/go,https://api.github.com/repos/golang/go,opened,spec: Method sets section doesn't seem quite right for interfaces with type lists,Documentation,"https://tip.golang.org/ref/spec#Method_sets says the following:

> The method set of an [interface type](https://tip.golang.org/ref/spec#Interface_types) is the intersection of the method sets of each type in the interface's [type set](https://tip.golang.org/ref/spec#Interface_types) (the resulting method set is usually just the set of declared methods in the interface).

AFAIU, per

> - The type set of a non-empty interface is the intersection of the type sets of its interface elements. 
> - The type set of a non-interface type term is the set consisting of just that type. 

the type set of `interface { S }` for concrete type S is {S}. The intersection of the method sets is thus the method set of S. But that doesn't seem quite right. `func foo[T S](x T) { x.Foo() }` certainly doesn't compile. Was the intention to have an implicit, empty method set for the absent list of methods in the interface?

/cc @griesemer @findleyr ",1.0,"spec: Method sets section doesn't seem quite right for interfaces with type lists - https://tip.golang.org/ref/spec#Method_sets says the following:

> The method set of an [interface type](https://tip.golang.org/ref/spec#Interface_types) is the intersection of the method sets of each type in the interface's [type set](https://tip.golang.org/ref/spec#Interface_types) (the resulting method set is usually just the set of declared methods in the interface).

AFAIU, per

> - The type set of a non-empty interface is the intersection of the type sets of its interface elements. 
> - The type set of a non-interface type term is the set consisting of just that type. 

the type set of `interface { S }` for concrete type S is {S}. The intersection of the method sets is thus the method set of S. But that doesn't seem quite right. `func foo[T S](x T) { x.Foo() }` certainly doesn't compile. Was the intention to have an implicit, empty method set for the absent list of methods in the interface?

/cc @griesemer @findleyr ",1,spec  method sets section doesn t seem quite right for interfaces with type lists     says the following       the method set of an     is the intersection of the method sets of each type in the interface s      the resulting method set is usually just the set of declared methods in the interface      afaiu  per        the type set of a non empty interface is the intersection of the type sets of its interface elements        the type set of a non interface type term is the set consisting of just that type      the type set of  interface   s    for concrete type s is  s   the intersection of the method sets is thus the method set of s  but that doesn t seem quite right   func foo  x t    x foo      certainly doesn t compile  was the intention to have an implicit  empty method set for the absent list of methods in the interface      cc  griesemer  findleyr ,1
217972,7329564926.0,IssuesEvent,2018-03-05 05:55:01,wso2/product-is,https://api.github.com/repos/wso2/product-is,closed,Explain the usage of orderId element in identity.xml file. ,Priority/Normal Severity/Minor Type/Docs,"Document: https://docs.wso2.com/display/IS550/Creating+Users+Using+the+Ask+Password+Option 

- Explain the usage of orderId element in  <IS_HOME>/repository/conf/identity/identity.xml file. 
- Explain why they have been configured as below. 
```
<EventListener type=""org.wso2.carbon.user.core.listener.UserOperationEventListener"" name=""org.wso2.carbon.identity.mgt.IdentityMgtEventListener"" orderId=""50"" enable=""false""/>
<EventListener type=""org.wso2.carbon.user.core.listener.UserOperationEventListener"" name=""org.wso2.carbon.identity.governance.listener.IdentityMgtEventListener"" orderId=""95"" enable=""true"" />
<EventListener type=""org.wso2.carbon.user.core.listener.UserOperationEventListener"" name=""org.wso2.carbon.identity.governance.listener.IdentityStoreEventListener"" orderId=""97"" enable=""true"">
```


Type/Docs
Priority/Normal
Severity/Minor",1.0,"Explain the usage of orderId element in identity.xml file.  - Document: https://docs.wso2.com/display/IS550/Creating+Users+Using+the+Ask+Password+Option 

- Explain the usage of orderId element in  <IS_HOME>/repository/conf/identity/identity.xml file. 
- Explain why they have been configured as below. 
```
<EventListener type=""org.wso2.carbon.user.core.listener.UserOperationEventListener"" name=""org.wso2.carbon.identity.mgt.IdentityMgtEventListener"" orderId=""50"" enable=""false""/>
<EventListener type=""org.wso2.carbon.user.core.listener.UserOperationEventListener"" name=""org.wso2.carbon.identity.governance.listener.IdentityMgtEventListener"" orderId=""95"" enable=""true"" />
<EventListener type=""org.wso2.carbon.user.core.listener.UserOperationEventListener"" name=""org.wso2.carbon.identity.governance.listener.IdentityStoreEventListener"" orderId=""97"" enable=""true"">
```


Type/Docs
Priority/Normal
Severity/Minor",0,explain the usage of orderid element in identity xml file     document          explain the usage of orderid element in    repository conf identity identity xml file      explain why they have been configured as below                           type docs  priority normal  severity minor,0
176878,14598013182.0,IssuesEvent,2020-12-20 22:47:59,golang/go,https://api.github.com/repos/golang/go,closed,go/types: update docs for modules,Documentation,"### What did you do?

@natefinch tried to use `go/types` ([tweet](https://twitter.com/NateTheFinch/status/1338343651148173314)): https://play.golang.org/p/Ue77cJ9Dc3A

### What did you expect to see?

A recommendation to use `golang.org/x/tools/go/packages`.

### What did you see instead?

No such mention. The [gotypes tutorial](https://github.com/golang/example/tree/master/gotypes) is also out-of-date and mentions `golang.org/x/tools/go/loader`. The `golang.org/x/tools/go/loader` package does contain a deprecation notice and recommends `golang.org/x/tools/go/packages`, which is good. I would posit that almost anybody wanting to use `go/types` should be using `golang.org/x/tools/go/packages`, so surfacing that recommendation earlier would be better.

---

I'm happy to send a CL for `go/types` package doc if there's agreement. I don't have bandwidth to take on improving the gotypes tutorial.",1.0,"go/types: update docs for modules - ### What did you do?

@natefinch tried to use `go/types` ([tweet](https://twitter.com/NateTheFinch/status/1338343651148173314)): https://play.golang.org/p/Ue77cJ9Dc3A

### What did you expect to see?

A recommendation to use `golang.org/x/tools/go/packages`.

### What did you see instead?

No such mention. The [gotypes tutorial](https://github.com/golang/example/tree/master/gotypes) is also out-of-date and mentions `golang.org/x/tools/go/loader`. The `golang.org/x/tools/go/loader` package does contain a deprecation notice and recommends `golang.org/x/tools/go/packages`, which is good. I would posit that almost anybody wanting to use `go/types` should be using `golang.org/x/tools/go/packages`, so surfacing that recommendation earlier would be better.

---

I'm happy to send a CL for `go/types` package doc if there's agreement. I don't have bandwidth to take on improving the gotypes tutorial.",1,go types  update docs for modules       what did you do      natefinch tried to use  go types                what did you expect to see     a recommendation to use  golang org x tools go packages          what did you see instead     no such mention  the     is also out of date and mentions  golang org x tools go loader   the  golang org x tools go loader  package does contain a deprecation notice and recommends  golang org x tools go packages   which is good  i would posit that almost anybody wanting to use  go types  should be using  golang org x tools go packages   so surfacing that recommendation earlier would be better            i m happy to send a cl for  go types  package doc if there s agreement  i don t have bandwidth to take on improving the gotypes tutorial ,1
24895,5109451239.0,IssuesEvent,2017-01-05 20:51:06,golang/go,https://api.github.com/repos/golang/go,opened,doc: reproduce the screencast with the default GOPATH,Documentation,"""[How to write code](https://golang.org/doc/code.html#GOPATH)"" document includes a [screencast](https://www.youtube.com/watch?v=XCsL89YtqCs) to explain the workspaces and the go tool. We may need to reproduce it to avoid setting GOPATH.

A similar cast is also required for the Windows users. Even though a large portion of our existing and potential users are Windows users, our core material is lacking references.

/cc @adg @campoy @broady ",1.0,"doc: reproduce the screencast with the default GOPATH - ""[How to write code](https://golang.org/doc/code.html#GOPATH)"" document includes a [screencast](https://www.youtube.com/watch?v=XCsL89YtqCs) to explain the workspaces and the go tool. We may need to reproduce it to avoid setting GOPATH.

A similar cast is also required for the Windows users. Even though a large portion of our existing and potential users are Windows users, our core material is lacking references.

/cc @adg @campoy @broady ",1,doc  reproduce the screencast with the default gopath        document includes a     to explain the workspaces and the go tool  we may need to reproduce it to avoid setting gopath     a similar cast is also required for the windows users  even though a large portion of our existing and potential users are windows users  our core material is lacking references      cc  adg  campoy  broady ,1
56436,8072944437.0,IssuesEvent,2018-08-06 17:36:51,golang/go,https://api.github.com/repos/golang/go,closed,cmd/cgo: CoreFoundation go-keychain compile failure on tip,Documentation NeedsFix OS-Darwin release-blocker,"Please answer these questions before submitting your issue. Thanks!

#### What did you do?

Check out tip of github.com/keybase/go-keychain (commit https://github.com/keybase/go-keychain/commit/70b98e9c8d754db775c5bd3b2de3670cc76f1825) and run `go build github.com/keybase/go-keychain`

#### What did you expect to see?

I expected the program to compile.

#### What did you see instead?

```
$ go build .
# github.com/keybase/go-keychain
./corefoundation_1.10.go:55: cannot use nil as type _Ctype_CFAllocatorRef in argument to _Cfunc_CFDataCreate
./corefoundation_1.10.go:81: cannot use nil as type _Ctype_CFAllocatorRef in argument to func literal
./corefoundation_1.10.go:118: cannot use nil as type _Ctype_CFAllocatorRef in argument to _Cfunc_CFStringCreateWithBytes
./corefoundation_1.10.go:153: cannot use nil as type _Ctype_CFAllocatorRef in argument to func literal
```

#### Does this issue reproduce with the latest release (go1.10.3)?

No. I can reproduce it using tip though, which suggests that this code will break in the upcoming Go 1.11 release. 

A git bisect revealed that commit 94076feef53c41c0c558a8686d6f2650b1614414 is the first commit to break; versions of Go compiled with commits earlier than this commit successfully compile the go-keychain library, newer ones don't.

#### System details

```
go version devel +94076feef5 Mon Jul 9 22:19:21 2018 +0000 darwin/amd64
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/kevin.burke/Library/Caches/go-build""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/kevin.burke""
GOPROXY=""""
GORACE=""""
GOROOT=""/Users/kevin.burke/go""
GOTMPDIR=""""
GOTOOLDIR=""/Users/kevin.burke/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/bs/n3zm0wvn7j14n9gm_ybk4klsg6mgyh/T/go-build618247201=/tmp/go-build -gno-record-gcc-switches -fno-common""
VGOMODROOT=""""
GOROOT/bin/go version: go version devel +94076feef5 Mon Jul 9 22:19:21 2018 +0000 darwin/amd64
GOROOT/bin/go tool compile -V: compile version devel +94076feef5 Mon Jul 9 22:19:21 2018 +0000
uname -v: Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64
ProductName:	Mac OS X
ProductVersion:	10.13.6
BuildVersion:	17G65
lldb --version: lldb-902.0.79.7
  Swift-4.1
```
",1.0,"cmd/cgo: CoreFoundation go-keychain compile failure on tip - Please answer these questions before submitting your issue. Thanks!

#### What did you do?

Check out tip of github.com/keybase/go-keychain (commit https://github.com/keybase/go-keychain/commit/70b98e9c8d754db775c5bd3b2de3670cc76f1825) and run `go build github.com/keybase/go-keychain`

#### What did you expect to see?

I expected the program to compile.

#### What did you see instead?

```
$ go build .
# github.com/keybase/go-keychain
./corefoundation_1.10.go:55: cannot use nil as type _Ctype_CFAllocatorRef in argument to _Cfunc_CFDataCreate
./corefoundation_1.10.go:81: cannot use nil as type _Ctype_CFAllocatorRef in argument to func literal
./corefoundation_1.10.go:118: cannot use nil as type _Ctype_CFAllocatorRef in argument to _Cfunc_CFStringCreateWithBytes
./corefoundation_1.10.go:153: cannot use nil as type _Ctype_CFAllocatorRef in argument to func literal
```

#### Does this issue reproduce with the latest release (go1.10.3)?

No. I can reproduce it using tip though, which suggests that this code will break in the upcoming Go 1.11 release. 

A git bisect revealed that commit 94076feef53c41c0c558a8686d6f2650b1614414 is the first commit to break; versions of Go compiled with commits earlier than this commit successfully compile the go-keychain library, newer ones don't.

#### System details

```
go version devel +94076feef5 Mon Jul 9 22:19:21 2018 +0000 darwin/amd64
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/kevin.burke/Library/Caches/go-build""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/kevin.burke""
GOPROXY=""""
GORACE=""""
GOROOT=""/Users/kevin.burke/go""
GOTMPDIR=""""
GOTOOLDIR=""/Users/kevin.burke/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/bs/n3zm0wvn7j14n9gm_ybk4klsg6mgyh/T/go-build618247201=/tmp/go-build -gno-record-gcc-switches -fno-common""
VGOMODROOT=""""
GOROOT/bin/go version: go version devel +94076feef5 Mon Jul 9 22:19:21 2018 +0000 darwin/amd64
GOROOT/bin/go tool compile -V: compile version devel +94076feef5 Mon Jul 9 22:19:21 2018 +0000
uname -v: Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64
ProductName:	Mac OS X
ProductVersion:	10.13.6
BuildVersion:	17G65
lldb --version: lldb-902.0.79.7
  Swift-4.1
```
",1,cmd cgo  corefoundation go keychain compile failure on tip   please answer these questions before submitting your issue  thanks          what did you do     check out tip of github com keybase go keychain  commit   and run  go build github com keybase go keychain          what did you expect to see     i expected the program to compile          what did you see instead            go build      github com keybase go keychain    corefoundation     go    cannot use nil as type  ctype cfallocatorref in argument to  cfunc cfdatacreate    corefoundation     go    cannot use nil as type  ctype cfallocatorref in argument to func literal    corefoundation     go    cannot use nil as type  ctype cfallocatorref in argument to  cfunc cfstringcreatewithbytes    corefoundation     go    cannot use nil as type  ctype cfallocatorref in argument to func literal              does this issue reproduce with the latest release             no  i can reproduce it using tip though  which suggests that this code will break in the upcoming go     release      a git bisect revealed that commit   is the first commit to break  versions of go compiled with commits earlier than this commit successfully compile the go keychain library  newer ones don t          system details         go version devel    mon jul              darwin    goarch      gobin     gocache   users kevin burke library caches go build   goexe     gohostarch      gohostos  darwin   goos  darwin   gopath   users kevin burke   goproxy     gorace     goroot   users kevin burke go   gotmpdir     gotooldir   users kevin burke go pkg tool darwin     gccgo  gccgo   cc  clang   cxx  clang     cgo enabled      cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders bs     t go    tmp go build  gno record gcc switches  fno common   vgomodroot     goroot bin go version  go version devel    mon jul              darwin    goroot bin go tool compile  v  compile version devel    mon jul               uname  v  darwin kernel version        thu jun         pdt    root xnu         release      productname 	mac os x  productversion 	       buildversion 	   lldb   version  lldb            swift           ,1
49456,26155972262.0,IssuesEvent,2022-12-30 21:48:14,tempesta-tech/tempesta,https://api.github.com/repos/tempesta-tech/tempesta,closed,Memory overusage for paged fragments,crucial performance,"# Motivation

It was stated that Tempesta FW uses even more memory on HTTP/2 workload than Nginx.

# Scope

`__new_pgfrag()`, called e.g. just to add a new HTTP header, allocates a new page if it can't find a room in existing fragments, which happens rarely. E.g. statistics from our website (HTTPS):
```
SS pfl hits                             : 8745
SS pfl misses                           : 169902
```
Probably replacing `alloc_page()` with `pg_skb_alloc()` will solve the issue. But `pg_skb_alloc()` should be able to allocate as small fragments as 128B.

Probably this not the only place were we overuse memory, so maybe additional tracing like the `pfl` counters should be introduced and also see [page owner](https://www.kernel.org/doc/html/v4.19/vm/page_owner.html).

Probably, by the result of testing, the pfl optimization should be eliminated.

# Testing

Need to test
1. Tempesta FW consumes less memory than Nginx
2. at least 2 different files under `h2load` and `wrk/https` and analyze whether `pfl` optimization does make any sense (only when the memory overusage is fixed)",True,"Memory overusage for paged fragments - # Motivation

It was stated that Tempesta FW uses even more memory on HTTP/2 workload than Nginx.

# Scope

`__new_pgfrag()`, called e.g. just to add a new HTTP header, allocates a new page if it can't find a room in existing fragments, which happens rarely. E.g. statistics from our website (HTTPS):
```
SS pfl hits                             : 8745
SS pfl misses                           : 169902
```
Probably replacing `alloc_page()` with `pg_skb_alloc()` will solve the issue. But `pg_skb_alloc()` should be able to allocate as small fragments as 128B.

Probably this not the only place were we overuse memory, so maybe additional tracing like the `pfl` counters should be introduced and also see [page owner](https://www.kernel.org/doc/html/v4.19/vm/page_owner.html).

Probably, by the result of testing, the pfl optimization should be eliminated.

# Testing

Need to test
1. Tempesta FW consumes less memory than Nginx
2. at least 2 different files under `h2load` and `wrk/https` and analyze whether `pfl` optimization does make any sense (only when the memory overusage is fixed)",0,memory overusage for paged fragments     motivation    it was stated that tempesta fw uses even more memory on http   workload than nginx       scope       new pgfrag     called e g  just to add a new http header  allocates a new page if it can t find a room in existing fragments  which happens rarely  e g  statistics from our website  https         ss pfl hits                                  ss pfl misses                                     probably replacing  alloc page    with  pg skb alloc    will solve the issue  but  pg skb alloc    should be able to allocate as small fragments as       probably this not the only place were we overuse memory  so maybe additional tracing like the  pfl  counters should be introduced and also see        probably  by the result of testing  the pfl optimization should be eliminated       testing    need to test     tempesta fw consumes less memory than nginx     at least   different files under     and  wrk https  and analyze whether  pfl  optimization does make any sense  only when the memory overusage is fixed ,0
87388,10544893764.0,IssuesEvent,2019-10-02 17:56:22,golang/go,https://api.github.com/repos/golang/go,closed,proposal: doc: more overview of Go repo for new contributors,Documentation Proposal,"Scenario:
I want to contribute with a fix (or investigation) in an open issue and need directions to start. The contributor guidelines (https://golang.org/doc/contribute.html) are focused on describing the tooling and the overall approval process, but I'm feeling lack of orientation on the technical end.

For instance, how is the project organised? What each directory is for? What are the tools available? How do we test? How do we track test coverage? How does the `/test/fixedbugs/` directory work? If I'm fixing a bug should I create a file on fixedbugs or a _test file? Or both?

Those are a few things that come to my mind at the moment, but this is by far not an exhaustive list.

I think having a ""walkthrough""-like kind of guide teaching the high level organisation of the code, architectural components and the standard contribution process for writing a fix it would be a great addition to the contribution guide.

I offer myself to help writing it, as long as someone spend the time teaching me how it works. ",1.0,"proposal: doc: more overview of Go repo for new contributors - Scenario:
I want to contribute with a fix (or investigation) in an open issue and need directions to start. The contributor guidelines (https://golang.org/doc/contribute.html) are focused on describing the tooling and the overall approval process, but I'm feeling lack of orientation on the technical end.

For instance, how is the project organised? What each directory is for? What are the tools available? How do we test? How do we track test coverage? How does the `/test/fixedbugs/` directory work? If I'm fixing a bug should I create a file on fixedbugs or a _test file? Or both?

Those are a few things that come to my mind at the moment, but this is by far not an exhaustive list.

I think having a ""walkthrough""-like kind of guide teaching the high level organisation of the code, architectural components and the standard contribution process for writing a fix it would be a great addition to the contribution guide.

I offer myself to help writing it, as long as someone spend the time teaching me how it works. ",1,proposal  doc  more overview of go repo for new contributors   scenario   i want to contribute with a fix  or investigation  in an open issue and need directions to start  the contributor guidelines    are focused on describing the tooling and the overall approval process  but i m feeling lack of orientation on the technical end     for instance  how is the project organised  what each directory is for  what are the tools available  how do we test  how do we track test coverage  how does the   test fixedbugs   directory work  if i m fixing a bug should i create a file on fixedbugs or a  test file  or both     those are a few things that come to my mind at the moment  but this is by far not an exhaustive list     i think having a  walkthrough  like kind of guide teaching the high level organisation of the code  architectural components and the standard contribution process for writing a fix it would be a great addition to the contribution guide     i offer myself to help writing it  as long as someone spend the time teaching me how it works  ,1
131683,12488713066.0,IssuesEvent,2020-05-31 15:28:59,golang/go,https://api.github.com/repos/golang/go,opened,"x/tools/internal/gocommand: documentation doesn't state what Run{,Piped,Raw} do and what they returns",Documentation NeedsInvestigation,"There are 3 exported identifiers with the word ""Run"" in package [`golang.org/x/tools/internal/gocommand`](https://pkg.go.dev/golang.org/x/tools/internal/gocommand). None of them say what the identifiers do and what they return. Each one says ""it's like this other Run variant"". This makes it hard to know how to use the API of `gocommand` package.

```Go
// RunPiped is like Run, but relies on the given stdout/stderr
func (i *Invocation) RunPiped(ctx context.Context, stdout, stderr io.Writer) error

// Run calls Runner.RunRaw, serializing requests if they fight over go.mod changes.
func (runner *Runner) Run(ctx context.Context, inv Invocation) (*bytes.Buffer, error)

// RunRaw calls Invocation.runRaw, serializing requests if they fight over go.mod changes.
func (runner *Runner) RunRaw(ctx context.Context, inv Invocation) (*bytes.Buffer, *bytes.Buffer, error, error)
```

Documentation for `Invocation.runRaw` isn't readily visible because it's an unexported identifier, but it doesn't help:

```Go
// RunRaw is like RunPiped, but also returns the raw stderr and error for callers
// that want to do low-level error handling/recovery.
func (i *Invocation) runRaw(ctx context.Context) (stdout *bytes.Buffer, stderr *bytes.Buffer, friendlyError error, rawError error)
```

The `Runner` type is documented as follows:

```
// An Runner will run go command invocations and serialize them if it sees a concurrency error.
```

Perhaps that should be made more visible on the methods, and their `*bytes.Buffer` and `error` results can be given names like `stdout` to help clarify what's what.",1.0,"x/tools/internal/gocommand: documentation doesn't state what Run{,Piped,Raw} do and what they returns - There are 3 exported identifiers with the word ""Run"" in package [`golang.org/x/tools/internal/gocommand`](https://pkg.go.dev/golang.org/x/tools/internal/gocommand). None of them say what the identifiers do and what they return. Each one says ""it's like this other Run variant"". This makes it hard to know how to use the API of `gocommand` package.

```Go
// RunPiped is like Run, but relies on the given stdout/stderr
func (i *Invocation) RunPiped(ctx context.Context, stdout, stderr io.Writer) error

// Run calls Runner.RunRaw, serializing requests if they fight over go.mod changes.
func (runner *Runner) Run(ctx context.Context, inv Invocation) (*bytes.Buffer, error)

// RunRaw calls Invocation.runRaw, serializing requests if they fight over go.mod changes.
func (runner *Runner) RunRaw(ctx context.Context, inv Invocation) (*bytes.Buffer, *bytes.Buffer, error, error)
```

Documentation for `Invocation.runRaw` isn't readily visible because it's an unexported identifier, but it doesn't help:

```Go
// RunRaw is like RunPiped, but also returns the raw stderr and error for callers
// that want to do low-level error handling/recovery.
func (i *Invocation) runRaw(ctx context.Context) (stdout *bytes.Buffer, stderr *bytes.Buffer, friendlyError error, rawError error)
```

The `Runner` type is documented as follows:

```
// An Runner will run go command invocations and serialize them if it sees a concurrency error.
```

Perhaps that should be made more visible on the methods, and their `*bytes.Buffer` and `error` results can be given names like `stdout` to help clarify what's what.",1,x tools internal gocommand  documentation doesn t state what run  piped raw  do and what they returns   there are   exported identifiers with the word  run  in package     none of them say what the identifiers do and what they return  each one says  it s like this other run variant   this makes it hard to know how to use the api of  gocommand  package        go     runpiped is like run  but relies on the given stdout stderr  func  i  invocation  runpiped ctx context context  stdout  stderr io writer  error       run calls runner runraw  serializing requests if they fight over go mod changes   func  runner  runner  run ctx context context  inv invocation    bytes buffer  error        runraw calls invocation runraw  serializing requests if they fight over go mod changes   func  runner  runner  runraw ctx context context  inv invocation    bytes buffer   bytes buffer  error  error          documentation for  invocation runraw  isn t readily visible because it s an unexported identifier  but it doesn t help        go     runraw is like runpiped  but also returns the raw stderr and error for callers     that want to do low level error handling recovery   func  i  invocation  runraw ctx context context   stdout  bytes buffer  stderr  bytes buffer  friendlyerror error  rawerror error          the  runner  type is documented as follows             an runner will run go command invocations and serialize them if it sees a concurrency error          perhaps that should be made more visible on the methods  and their   bytes buffer  and  error  results can be given names like  stdout  to help clarify what s what ,1
13129,4641028428.0,IssuesEvent,2016-09-30 01:57:16,asterales/2DCapstoneGame,https://api.github.com/repos/asterales/2DCapstoneGame,opened,AI Test Program (Whenever we have free time),code,Program to test AI's against each other in headless mode with any number of iterations.,1.0,AI Test Program (Whenever we have free time) - Program to test AI's against each other in headless mode with any number of iterations.,0,ai test program  whenever we have free time    program to test ai s against each other in headless mode with any number of iterations ,0
3899,3602027264.0,IssuesEvent,2016-02-03 14:11:19,Yakindu/statecharts,https://api.github.com/repos/Yakindu/statecharts,closed,No separation between operation parameters in proposal provider,Comp-Graphical Editor Usability Issue,"In proposal provider, there are no separating commas between operation parameters.

There is also duplicated code in OperationDefinitionItemProvider.getText() and OperationItemProvider.getText() related to this issue.",True,"No separation between operation parameters in proposal provider - In proposal provider, there are no separating commas between operation parameters.

There is also duplicated code in OperationDefinitionItemProvider.getText() and OperationItemProvider.getText() related to this issue.",0,no separation between operation parameters in proposal provider   in proposal provider  there are no separating commas between operation parameters     there is also duplicated code in operationdefinitionitemprovider gettext   and operationitemprovider gettext   related to this issue ,0
433756,30348527179.0,IssuesEvent,2023-07-11 17:07:16,golang/go,https://api.github.com/repos/golang/go,closed,"log/slog: documentation passes nil contexts, which is discouraged",Documentation NeedsFix release-blocker,"The documentation of the slog package passes nil contexts, for example:

```
logger.LogAttrs(nil, slog.LevelInfo, ""hello"", slog.Int(""count"", 3))
```

However, the context package discourages this:

> Do not pass a nil Context, even if a function permits it. Pass context.TODO if you are unsure about which Context to use. 

slog internally turns nils into context.Background when calling methods on slog.Handler, which is probably good for resilience, but probably isn't something users should rely on.

In particular, such calls will currently trigger Staticcheck's [SA1012](https://staticcheck.dev/docs/checks/#SA1012) and I'm not sure slog warrants an exception.

I see from https://github.com/golang/exp/commit/f0f767cdffd6c3fe9fa17c685f39b1cf8e866c0c that this is intentional, so this issue might be contentious. However, I'm not sure the ""make them easier to write"" argument is as important now, considering there are helpers for pre-defined log levels that don't take context arguments, and it would be unfortunate for the standard library to ignore its own rules.

/cc @jba ",1.0,"log/slog: documentation passes nil contexts, which is discouraged - The documentation of the slog package passes nil contexts, for example:

```
logger.LogAttrs(nil, slog.LevelInfo, ""hello"", slog.Int(""count"", 3))
```

However, the context package discourages this:

> Do not pass a nil Context, even if a function permits it. Pass context.TODO if you are unsure about which Context to use. 

slog internally turns nils into context.Background when calling methods on slog.Handler, which is probably good for resilience, but probably isn't something users should rely on.

In particular, such calls will currently trigger Staticcheck's [SA1012](https://staticcheck.dev/docs/checks/#SA1012) and I'm not sure slog warrants an exception.

I see from https://github.com/golang/exp/commit/f0f767cdffd6c3fe9fa17c685f39b1cf8e866c0c that this is intentional, so this issue might be contentious. However, I'm not sure the ""make them easier to write"" argument is as important now, considering there are helpers for pre-defined log levels that don't take context arguments, and it would be unfortunate for the standard library to ignore its own rules.

/cc @jba ",1,log slog  documentation passes nil contexts  which is discouraged   the documentation of the slog package passes nil contexts  for example          logger logattrs nil  slog levelinfo   hello   slog int  count               however  the context package discourages this       do not pass a nil context  even if a function permits it  pass context todo if you are unsure about which context to use      slog internally turns nils into context background when calling methods on slog handler  which is probably good for resilience  but probably isn t something users should rely on     in particular  such calls will currently trigger staticcheck s     and i m not sure slog warrants an exception     i see from   that this is intentional  so this issue might be contentious  however  i m not sure the  make them easier to write  argument is as important now  considering there are helpers for pre defined log levels that don t take context arguments  and it would be unfortunate for the standard library to ignore its own rules      cc  jba ,1
58574,8287583489.0,IssuesEvent,2018-09-19 09:17:47,golang/go,https://api.github.com/repos/golang/go,closed,fmt: Add an example for Printf,Documentation NeedsFix,"

### What version of Go are you using (`go version`)?

go version go1.10 linux/amd64

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/vagrant/.cache/go-build""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/vagrant/go""
GORACE=""""
GOROOT=""/usr/lib/go-1.10""
GOTMPDIR=""""
GOTOOLDIR=""/usr/lib/go-1.10/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build279712786=/tmp/go-build -gno-record-gcc-switches""

### What did you do?

See how to use the `fmt.Printf function` from an example in the docs.

### What did you expect to see?

Examples at https://golang.org/pkg/fmt/ 

### What did you see instead?

Only one example at https://golang.org/pkg/fmt/ 


",1.0,"fmt: Add an example for Printf - 

### What version of Go are you using (`go version`)?

go version go1.10 linux/amd64

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/vagrant/.cache/go-build""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/vagrant/go""
GORACE=""""
GOROOT=""/usr/lib/go-1.10""
GOTMPDIR=""""
GOTOOLDIR=""/usr/lib/go-1.10/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build279712786=/tmp/go-build -gno-record-gcc-switches""

### What did you do?

See how to use the `fmt.Printf function` from an example in the docs.

### What did you expect to see?

Examples at https://golang.org/pkg/fmt/ 

### What did you see instead?

Only one example at https://golang.org/pkg/fmt/ 


",1,fmt  add an example for printf           what version of go are you using   go version       go version     linux          does this issue reproduce with the latest release     yes         what operating system and processor architecture are you using   go env       goarch      gobin     gocache   home vagrant  cache go build   goexe     gohostarch      gohostos  linux   goos  linux   gopath   home vagrant go   gorace     goroot   usr lib go       gotmpdir     gotooldir   usr lib go     pkg tool linux     gccgo  gccgo   cc  gcc   cxx  g     cgo enabled      cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches         what did you do     see how to use the  fmt printf function  from an example in the docs         what did you expect to see     examples at           what did you see instead     only one example at         ,1
234461,19183888872.0,IssuesEvent,2021-12-04 21:54:06,NikOneZ1/createfolio,https://api.github.com/repos/NikOneZ1/createfolio,closed,Test ProjectUpdateRemoveView Patch method,test,"- [x] Patch project without authentication (should give an error)
- [x] Patch project with other user (should give an error)
- [x] Change portfolio in project (should give an error)
- [x] Patch project where current user same with portfolio user",1.0,"Test ProjectUpdateRemoveView Patch method - - [x] Patch project without authentication (should give an error)
- [x] Patch project with other user (should give an error)
- [x] Change portfolio in project (should give an error)
- [x] Patch project where current user same with portfolio user",0,test projectupdateremoveview patch method       patch project without authentication  should give an error       patch project with other user  should give an error       change portfolio in project  should give an error       patch project where current user same with portfolio user,0
242784,26277822471.0,IssuesEvent,2023-01-07 01:15:44,vipinsun/fabric-token-sdk,https://api.github.com/repos/vipinsun/fabric-token-sdk,closed,CVE-2020-15257 (Medium) detected in github.com/Docker/docker-v20.10.7+incompatible - autoclosed,security vulnerability,"## CVE-2020-15257 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/Docker/docker-v20.10.7+incompatible</b></p></summary>

<p>Moby Project - a collaborative project for the container ecosystem to assemble container-based systems</p>
<p>Library home page: <a href=""https://proxy.golang.org/github.com/docker/docker/@v/v20.10.7+incompatible.zip"">https://proxy.golang.org/github.com/docker/docker/@v/v20.10.7+incompatible.zip</a></p>
<p>

Dependency Hierarchy:
  - github.com/hyperledger-labs/fabric-smart-client (Root Library)
    - :x: **github.com/Docker/docker-v20.10.7+incompatible** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/vipinsun/fabric-token-sdk/commit/999f5d255a183e22a067e6411929924a0bacd65f"">999f5d255a183e22a067e6411929924a0bacd65f</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
containerd is an industry-standard container runtime and is available as a daemon for Linux and Windows. In containerd before versions 1.3.9 and 1.4.3, the containerd-shim API is improperly exposed to host network containers. Access controls for the shim’s API socket verified that the connecting process had an effective UID of 0, but did not otherwise restrict access to the abstract Unix domain socket. This would allow malicious containers running in the same network namespace as the shim, with an effective UID of 0 but otherwise reduced privileges, to cause new processes to be run with elevated privileges. This vulnerability has been fixed in containerd 1.3.9 and 1.4.3. Users should update to these versions as soon as they are released. It should be noted that containers started with an old version of containerd-shim should be stopped and restarted, as running containers will continue to be vulnerable even after an upgrade. If you are not providing the ability for untrusted users to start containers in the same network namespace as the shim (typically the ""host"" network namespace, for example with docker run --net=host or hostNetwork: true in a Kubernetes pod) and run with an effective UID of 0, you are not vulnerable to this issue. If you are running containers with a vulnerable configuration, you can deny access to all abstract sockets with AppArmor by adding a line similar to deny unix addr=@**, to your policy. It is best practice to run containers with a reduced set of privileges, with a non-zero UID, and with isolated namespaces. The containerd maintainers strongly advise against sharing namespaces with the host. Reducing the set of isolation mechanisms used for a container necessarily increases that container's privilege, regardless of what container runtime is used for running that container.

<p>Publish Date: 2020-12-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-15257>CVE-2020-15257</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.2</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Changed
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/containerd/containerd/security/advisories/GHSA-36xw-fx78-c5r4"">https://github.com/containerd/containerd/security/advisories/GHSA-36xw-fx78-c5r4</a></p>
<p>Release Date: 2020-12-01</p>
<p>Fix Resolution: v1.3.9,v1.4.3</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2020-15257 (Medium) detected in github.com/Docker/docker-v20.10.7+incompatible - autoclosed - ## CVE-2020-15257 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/Docker/docker-v20.10.7+incompatible</b></p></summary>

<p>Moby Project - a collaborative project for the container ecosystem to assemble container-based systems</p>
<p>Library home page: <a href=""https://proxy.golang.org/github.com/docker/docker/@v/v20.10.7+incompatible.zip"">https://proxy.golang.org/github.com/docker/docker/@v/v20.10.7+incompatible.zip</a></p>
<p>

Dependency Hierarchy:
  - github.com/hyperledger-labs/fabric-smart-client (Root Library)
    - :x: **github.com/Docker/docker-v20.10.7+incompatible** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/vipinsun/fabric-token-sdk/commit/999f5d255a183e22a067e6411929924a0bacd65f"">999f5d255a183e22a067e6411929924a0bacd65f</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
containerd is an industry-standard container runtime and is available as a daemon for Linux and Windows. In containerd before versions 1.3.9 and 1.4.3, the containerd-shim API is improperly exposed to host network containers. Access controls for the shim’s API socket verified that the connecting process had an effective UID of 0, but did not otherwise restrict access to the abstract Unix domain socket. This would allow malicious containers running in the same network namespace as the shim, with an effective UID of 0 but otherwise reduced privileges, to cause new processes to be run with elevated privileges. This vulnerability has been fixed in containerd 1.3.9 and 1.4.3. Users should update to these versions as soon as they are released. It should be noted that containers started with an old version of containerd-shim should be stopped and restarted, as running containers will continue to be vulnerable even after an upgrade. If you are not providing the ability for untrusted users to start containers in the same network namespace as the shim (typically the ""host"" network namespace, for example with docker run --net=host or hostNetwork: true in a Kubernetes pod) and run with an effective UID of 0, you are not vulnerable to this issue. If you are running containers with a vulnerable configuration, you can deny access to all abstract sockets with AppArmor by adding a line similar to deny unix addr=@**, to your policy. It is best practice to run containers with a reduced set of privileges, with a non-zero UID, and with isolated namespaces. The containerd maintainers strongly advise against sharing namespaces with the host. Reducing the set of isolation mechanisms used for a container necessarily increases that container's privilege, regardless of what container runtime is used for running that container.

<p>Publish Date: 2020-12-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-15257>CVE-2020-15257</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.2</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Changed
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/containerd/containerd/security/advisories/GHSA-36xw-fx78-c5r4"">https://github.com/containerd/containerd/security/advisories/GHSA-36xw-fx78-c5r4</a></p>
<p>Release Date: 2020-12-01</p>
<p>Fix Resolution: v1.3.9,v1.4.3</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      medium  detected in github com docker docker       incompatible   autoclosed      cve       medium severity vulnerability     vulnerable library    github com docker docker       incompatible      moby project   a collaborative project for the container ecosystem to assemble container based systems   library home page   a href       dependency hierarchy      github com hyperledger labs fabric smart client  root library         x    github com docker docker       incompatible    vulnerable library   found in head commit   a href     found in base branch   main              vulnerability details         containerd is an industry standard container runtime and is available as a daemon for linux and windows  in containerd before versions       and        the containerd shim api is improperly exposed to host network containers  access controls for the shim’s api socket verified that the connecting process had an effective uid of    but did not otherwise restrict access to the abstract unix domain socket  this would allow malicious containers running in the same network namespace as the shim  with an effective uid of   but otherwise reduced privileges  to cause new processes to be run with elevated privileges  this vulnerability has been fixed in containerd       and        users should update to these versions as soon as they are released  it should be noted that containers started with an old version of containerd shim should be stopped and restarted  as running containers will continue to be vulnerable even after an upgrade  if you are not providing the ability for untrusted users to start containers in the same network namespace as the shim  typically the  host  network namespace  for example with docker run   net host or hostnetwork  true in a kubernetes pod  and run with an effective uid of    you are not vulnerable to this issue  if you are running containers with a vulnerable configuration  you can deny access to all abstract sockets with apparmor by adding a line similar to deny unix addr      to your policy  it is best practice to run containers with a reduced set of privileges  with a non zero uid  and with isolated namespaces  the containerd maintainers strongly advise against sharing namespaces with the host  reducing the set of isolation mechanisms used for a container necessarily increases that container s privilege  regardless of what container runtime is used for running that container    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  local     attack complexity  low     privileges required  low     user interaction  none     scope  changed   impact metrics      confidentiality impact  low     integrity impact  low     availability impact  none   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                            step up your open source security game with mend    ,0
122985,17772038607.0,IssuesEvent,2021-08-30 14:41:12,kapseliboi/sagefy,https://api.github.com/repos/kapseliboi/sagefy,opened,CVE-2020-15168 (Medium) detected in node-fetch-2.1.2.tgz,security vulnerability,"## CVE-2020-15168 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-fetch-2.1.2.tgz</b></p></summary>

<p>A light-weight module that brings window.fetch to node.js</p>
<p>Library home page: <a href=""https://registry.npmjs.org/node-fetch/-/node-fetch-2.1.2.tgz"">https://registry.npmjs.org/node-fetch/-/node-fetch-2.1.2.tgz</a></p>
<p>Path to dependency file: sagefy/client/package.json</p>
<p>Path to vulnerable library: sagefy/client/node_modules/node-fetch/package.json</p>
<p>

Dependency Hierarchy:
  - graphql-request-1.8.2.tgz (Root Library)
    - cross-fetch-2.2.2.tgz
      - :x: **node-fetch-2.1.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/kapseliboi/sagefy/commit/85736dad6168b94cc8ec8bfe513dc6d3fd360e38"">85736dad6168b94cc8ec8bfe513dc6d3fd360e38</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>  
  
node-fetch before versions 2.6.1 and 3.0.0-beta.9 did not honor the size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure. For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don't double-check the size of the data after fetch() has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.

<p>Publish Date: 2020-09-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15168>CVE-2020-15168</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r"">https://github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r</a></p>
<p>Release Date: 2020-07-21</p>
<p>Fix Resolution: 2.6.1,3.0.0-beta.9</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-15168 (Medium) detected in node-fetch-2.1.2.tgz - ## CVE-2020-15168 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-fetch-2.1.2.tgz</b></p></summary>

<p>A light-weight module that brings window.fetch to node.js</p>
<p>Library home page: <a href=""https://registry.npmjs.org/node-fetch/-/node-fetch-2.1.2.tgz"">https://registry.npmjs.org/node-fetch/-/node-fetch-2.1.2.tgz</a></p>
<p>Path to dependency file: sagefy/client/package.json</p>
<p>Path to vulnerable library: sagefy/client/node_modules/node-fetch/package.json</p>
<p>

Dependency Hierarchy:
  - graphql-request-1.8.2.tgz (Root Library)
    - cross-fetch-2.2.2.tgz
      - :x: **node-fetch-2.1.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/kapseliboi/sagefy/commit/85736dad6168b94cc8ec8bfe513dc6d3fd360e38"">85736dad6168b94cc8ec8bfe513dc6d3fd360e38</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>  
  
node-fetch before versions 2.6.1 and 3.0.0-beta.9 did not honor the size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure. For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don't double-check the size of the data after fetch() has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.

<p>Publish Date: 2020-09-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15168>CVE-2020-15168</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r"">https://github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r</a></p>
<p>Release Date: 2020-07-21</p>
<p>Fix Resolution: 2.6.1,3.0.0-beta.9</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      medium  detected in node fetch       tgz      cve       medium severity vulnerability     vulnerable library    node fetch       tgz      a light weight module that brings window fetch to node js   library home page   a href     path to dependency file  sagefy client package json   path to vulnerable library  sagefy client node modules node fetch package json     dependency hierarchy      graphql request       tgz  root library        cross fetch       tgz          x    node fetch       tgz    vulnerable library   found in head commit   a href     found in base branch   master              vulnerability details         node fetch before versions       and       beta   did not honor the size option after following a redirect  which means that when a content size was over the limit  a fetcherror would never get thrown and the process would end without failure  for most people  this fix will have a little or no impact  however  if you are relying on node fetch to gate files above a size  the impact could be significant  for example  if you don t double check the size of the data after fetch   has completed  your js thread could get tied up doing work on a large file  dos  and or cost you money in computing    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  low   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution              beta                 step up your open source security game with whitesource    ,0
193106,15367368212.0,IssuesEvent,2021-03-02 03:08:44,golang/go,https://api.github.com/repos/golang/go,closed,x/website:https://golang.org/doc/code,Documentation NeedsFix help wanted,"Using https://golang.org/doc/code and Go 1.16.

The part where you use `go install` does not automatically download the remote package. What you see is in the document is:

```
$ go install example.com/user/hello
go: finding module for package github.com/google/go-cmp/cmp
go: downloading github.com/google/go-cmp v0.4.0
go: found github.com/google/go-cmp/cmp in github.com/google/go-cmp v0.4.0
```

What I got was:

```
$ go install example.com/user/hello
hello.go:7:2: no required module provides package github.com/google/go-cmp/cmp; to add it:
	go get github.com/google/go-cmp/cmp
```

After running `go get github.com/google/go-cmp/cmp`, rerunning produces:

```
$ go install example.com/user/hello
$
```

If I am correct, I am happy to update the document. If I am wrong, happy to learn why!
",1.0,"x/website:https://golang.org/doc/code - Using https://golang.org/doc/code and Go 1.16.

The part where you use `go install` does not automatically download the remote package. What you see is in the document is:

```
$ go install example.com/user/hello
go: finding module for package github.com/google/go-cmp/cmp
go: downloading github.com/google/go-cmp v0.4.0
go: found github.com/google/go-cmp/cmp in github.com/google/go-cmp v0.4.0
```

What I got was:

```
$ go install example.com/user/hello
hello.go:7:2: no required module provides package github.com/google/go-cmp/cmp; to add it:
	go get github.com/google/go-cmp/cmp
```

After running `go get github.com/google/go-cmp/cmp`, rerunning produces:

```
$ go install example.com/user/hello
$
```

If I am correct, I am happy to update the document. If I am wrong, happy to learn why!
",1,x website     using   and go         the part where you use  go install  does not automatically download the remote package  what you see is in the document is            go install example com user hello  go  finding module for package github com google go cmp cmp  go  downloading github com google go cmp        go  found github com google go cmp cmp in github com google go cmp               what i got was            go install example com user hello  hello go      no required module provides package github com google go cmp cmp  to add it   	go get github com google go cmp cmp         after running  go get github com google go cmp cmp   rerunning produces            go install example com user hello            if i am correct  i am happy to update the document  if i am wrong  happy to learn why   ,1
155019,24391196600.0,IssuesEvent,2022-10-04 15:21:01,devmount/third-stats,https://api.github.com/repos/devmount/third-stats,closed,Please add a ThirdStats icon to the Thunderbird Spaces Toolbar,design feature,"Thunderbird version 102 has a Spaces Toolbar.
https://blog.thunderbird.net/2022/09/thunderbird-tip-customize-colors-in-the-spaces-toolbar/

Can a ThirdStats icon please be added to the Thunderbird Spaces Toolbar?

Perhaps code pointers from the CardBook add-on can help as a CardBook icon shows in the Spaces Toolbar.
https://addons.thunderbird.net/thunderbird/addon/cardbook/
https://gitlab.com/CardBook/CardBook/

What do you think?

Thank you",1.0,"Please add a ThirdStats icon to the Thunderbird Spaces Toolbar - Thunderbird version 102 has a Spaces Toolbar.
https://blog.thunderbird.net/2022/09/thunderbird-tip-customize-colors-in-the-spaces-toolbar/

Can a ThirdStats icon please be added to the Thunderbird Spaces Toolbar?

Perhaps code pointers from the CardBook add-on can help as a CardBook icon shows in the Spaces Toolbar.
https://addons.thunderbird.net/thunderbird/addon/cardbook/
https://gitlab.com/CardBook/CardBook/

What do you think?

Thank you",0,please add a thirdstats icon to the thunderbird spaces toolbar   thunderbird version   has a spaces toolbar        can a thirdstats icon please be added to the thunderbird spaces toolbar     perhaps code pointers from the cardbook add on can help as a cardbook icon shows in the spaces toolbar           what do you think     thank you,0
211048,16416280521.0,IssuesEvent,2021-05-19 07:11:43,golang/go,https://api.github.com/repos/golang/go,closed,Can we document net.Conn Write as being atomic?,Documentation,"I answered this [stackoverflow question](https://stackoverflow.com/a/67595487/152580) about the atomicity of net.Conn Write.

It seems the implementation on both Unix and Windows is atomic in practice by acquiring a mutex around the OS write/send call(s).

One could possibly remove the mutex and thus allow writes to interleave - but that seems senseless and very likely will break real-world code at this point.

Not documenting that guarantee requires callers to maintain their own mutex around calls to write, and it is redundant and expensive to nest mutexes like that. Is it possible to document that interleaved writes are not permitted (i.e. that Write is atomic)?

One might argue the threadsafe guarantee for net.Conn already promises that - but it's ambiguous - it might just mean it doesn't crash.

",1.0,"Can we document net.Conn Write as being atomic? - I answered this [stackoverflow question](https://stackoverflow.com/a/67595487/152580) about the atomicity of net.Conn Write.

It seems the implementation on both Unix and Windows is atomic in practice by acquiring a mutex around the OS write/send call(s).

One could possibly remove the mutex and thus allow writes to interleave - but that seems senseless and very likely will break real-world code at this point.

Not documenting that guarantee requires callers to maintain their own mutex around calls to write, and it is redundant and expensive to nest mutexes like that. Is it possible to document that interleaved writes are not permitted (i.e. that Write is atomic)?

One might argue the threadsafe guarantee for net.Conn already promises that - but it's ambiguous - it might just mean it doesn't crash.

",1,can we document net conn write as being atomic    i answered this     about the atomicity of net conn write     it seems the implementation on both unix and windows is atomic in practice by acquiring a mutex around the os write send call s      one could possibly remove the mutex and thus allow writes to interleave   but that seems senseless and very likely will break real world code at this point     not documenting that guarantee requires callers to maintain their own mutex around calls to write  and it is redundant and expensive to nest mutexes like that  is it possible to document that interleaved writes are not permitted  i e  that write is atomic      one might argue the threadsafe guarantee for net conn already promises that   but it s ambiguous   it might just mean it doesn t crash     ,1
54661,3070940596.0,IssuesEvent,2015-08-19 08:52:15,pavel-pimenov/flylinkdc-r5xx,https://api.github.com/repos/pavel-pimenov/flylinkdc-r5xx,closed,Не работает отключение медленных источников,bug imported Priority-High,"_From [dron...@gmail.com](https://code.google.com/u/100503176640586570494/) on December 13, 2008 10:55:22_

What steps will reproduce the problem? Поставить галочку в ""Отключать медленные источники"" и ""Только при сегм. 
скачивании"".
Разорвать скачку, если скорость ниже 25 кб/с.
Дольше чем 15 сек
И скорость скачивания превысит 100 кб/с
и размер файла больше 10 мб
удалить источник, если скорость ниже 5 кб/с What is the expected output? What do you see instead? При скачивании файлов превыщающих 10 мб и суммарная скорость скачивания 
больше 100 кб/с должны отключаться источники со скоростью скачки меньше 
25 кб/с, если эта скорость держится на протяжении не менее 15 секунд. Но 
они не отключаются, хоть и проходит 1 минута на скорости с этого 
источника например 3 кб/с. Суммарная скорость скачки 600 кб/с. What version of the product are you using? On what operating system? Сломалось это в версии 364-365 вроде. Сейчас уже 370 и все равно не 
работает. Пытался на блоге писать, но почему-то никто не реагировал даже 
ответом. Версия под Windows XP sp3. На других не пробовал. Please provide any additional information below.

_Original issue: http://code.google.com/p/flylinkdc/issues/detail?id=7_",1.0,"Не работает отключение медленных источников - _From [dron...@gmail.com](https://code.google.com/u/100503176640586570494/) on December 13, 2008 10:55:22_

What steps will reproduce the problem? Поставить галочку в ""Отключать медленные источники"" и ""Только при сегм. 
скачивании"".
Разорвать скачку, если скорость ниже 25 кб/с.
Дольше чем 15 сек
И скорость скачивания превысит 100 кб/с
и размер файла больше 10 мб
удалить источник, если скорость ниже 5 кб/с What is the expected output? What do you see instead? При скачивании файлов превыщающих 10 мб и суммарная скорость скачивания 
больше 100 кб/с должны отключаться источники со скоростью скачки меньше 
25 кб/с, если эта скорость держится на протяжении не менее 15 секунд. Но 
они не отключаются, хоть и проходит 1 минута на скорости с этого 
источника например 3 кб/с. Суммарная скорость скачки 600 кб/с. What version of the product are you using? On what operating system? Сломалось это в версии 364-365 вроде. Сейчас уже 370 и все равно не 
работает. Пытался на блоге писать, но почему-то никто не реагировал даже 
ответом. Версия под Windows XP sp3. На других не пробовал. Please provide any additional information below.

_Original issue: http://code.google.com/p/flylinkdc/issues/detail?id=7_",0,не работает отключение медленных источников    from     on december              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  сломалось это в версии     вроде  сейчас уже   и все равно не   работает  пытался на блоге писать  но почему то никто не реагировал даже   ответом  версия под windows xp    на других не пробовал  please provide any additional information below    original issue   ,0
749117,26150104017.0,IssuesEvent,2022-12-30 12:15:27,NomicFoundation/hardhat,https://api.github.com/repos/NomicFoundation/hardhat,closed,Feature Request:  `buidler node` option to not log private key in the console,priority:low,"Currently when executing `buidler node` the set of account private key is outputed in the console. It would be great to have an option to not show them

On that note, if https://github.com/nomiclabs/buidler/issues/621 is implemented, `buidler node` should not show the private key by default as this could be sensitive enough.",1.0,"Feature Request:  `buidler node` option to not log private key in the console - Currently when executing `buidler node` the set of account private key is outputed in the console. It would be great to have an option to not show them

On that note, if https://github.com/nomiclabs/buidler/issues/621 is implemented, `buidler node` should not show the private key by default as this could be sensitive enough.",0,feature request    buidler node  option to not log private key in the console   currently when executing  buidler node  the set of account private key is outputed in the console  it would be great to have an option to not show them    on that note  if   is implemented   buidler node  should not show the private key by default as this could be sensitive enough ,0
262034,19759202042.0,IssuesEvent,2022-01-16 05:15:59,golang/go,https://api.github.com/repos/golang/go,closed,strings: typo in comment,Documentation NeedsFix,"<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
1.17.5 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/hlushch/Library/Caches/go-build""
GOENV=""/Users/hlushch/Library/Application Support/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/hlushch/Projects/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/hlushch/Projects/go/""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/Cellar/go/1.17.5/libexec""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/1.17.5/libexec/pkg/tool/darwin_amd64""
GOVCS=""""
GOVERSION=""go1.17.5""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/nz/cqlmbdfs23schf6ndmr7gz440000gn/T/go-build2546855830=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?

Went to L20C51 in src/strings/builder.go



### What did you expect to see?

No extra whitespace

### What did you see instead?

Unneeded whitespace
",1.0,"strings: typo in comment - <!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
1.17.5 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/hlushch/Library/Caches/go-build""
GOENV=""/Users/hlushch/Library/Application Support/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/hlushch/Projects/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/hlushch/Projects/go/""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/Cellar/go/1.17.5/libexec""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/1.17.5/libexec/pkg/tool/darwin_amd64""
GOVCS=""""
GOVERSION=""go1.17.5""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/nz/cqlmbdfs23schf6ndmr7gz440000gn/T/go-build2546855830=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?

Went to L20C51 in src/strings/builder.go



### What did you expect to see?

No extra whitespace

### What did you see instead?

Unneeded whitespace
",1,strings  typo in comment         please answer these questions before submitting your issue  thanks              what version of go are you using   go version            go version        darwin             does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   users hlushch library caches go build   goenv   users hlushch library application support go env   goexe     goexperiment     goflags     gohostarch      gohostos  darwin   goinsecure     gomodcache   users hlushch projects go pkg mod   gonoproxy     gonosumdb     goos  darwin   gopath   users hlushch projects go    goprivate     goproxy     goroot   usr local cellar go       libexec   gosumdb  sum golang org   gotmpdir     gotooldir   usr local cellar go       libexec pkg tool darwin     govcs     goversion          gccgo  gccgo   ar  ar   cc  clang   cxx  clang     cgo enabled      gomod   dev null   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic  arch         pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders nz   t go    tmp go build  gno record gcc switches  fno common             what did you do     went to   in src strings builder go            what did you expect to see     no extra whitespace        what did you see instead     unneeded whitespace  ,1
16719,4080260311.0,IssuesEvent,2016-05-31 00:23:23,golang/go,https://api.github.com/repos/golang/go,closed,sync: document that double RLock isn't safe,Documentation NeedsFix,"Please answer these questions before submitting your issue. Thanks!

1. What version of Go are you using (`go version`)?
go version go1.6 darwin/amd64

2. What operating system and processor architecture are you using (`go env`)?
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""""
GORACE=""""
GOROOT=""/usr/local/go""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GO15VENDOREXPERIMENT=""1""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""

3. What did you do?
```go
package main

import (
	""fmt""
	""sync""
)

func main() {
	ch := make(chan int)
	testFunc := func() {
		weirdLock := sync.RWMutex{}
		go func() {
			weirdLock.RLock()
			go func() {
				weirdLock.RLock()
				for i := 0; i < 3; i++ {
					func() {
						weirdLock.RLock()
						ch <- 1
						weirdLock.RUnlock()
					}()
				}
				weirdLock.RUnlock()
			}()
			weirdLock.RUnlock()
		}()
		go func() {
			weirdLock.Lock()
			ch <- 1
			weirdLock.Unlock()
		}()
	}
	runNum := 1000
	for i := 0; i < runNum; i++ {
		testFunc()
	}
	total := 0
	for i := 0; i < 4*runNum; i++ {
		total += <-ch
	}
	//Expect 4*runNum
	fmt.Println(total)
}
```
http://play.golang.org/p/UWIAmPCRCu

4. What did you expect to see?
output 4000

5. What did you see instead?
`fatal error: all goroutines are asleep - deadlock!`
runNum more big，the probability of deadlock more often
",1.0,"sync: document that double RLock isn't safe - Please answer these questions before submitting your issue. Thanks!

1. What version of Go are you using (`go version`)?
go version go1.6 darwin/amd64

2. What operating system and processor architecture are you using (`go env`)?
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""""
GORACE=""""
GOROOT=""/usr/local/go""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GO15VENDOREXPERIMENT=""1""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""

3. What did you do?
```go
package main

import (
	""fmt""
	""sync""
)

func main() {
	ch := make(chan int)
	testFunc := func() {
		weirdLock := sync.RWMutex{}
		go func() {
			weirdLock.RLock()
			go func() {
				weirdLock.RLock()
				for i := 0; i < 3; i++ {
					func() {
						weirdLock.RLock()
						ch <- 1
						weirdLock.RUnlock()
					}()
				}
				weirdLock.RUnlock()
			}()
			weirdLock.RUnlock()
		}()
		go func() {
			weirdLock.Lock()
			ch <- 1
			weirdLock.Unlock()
		}()
	}
	runNum := 1000
	for i := 0; i < runNum; i++ {
		testFunc()
	}
	total := 0
	for i := 0; i < 4*runNum; i++ {
		total += <-ch
	}
	//Expect 4*runNum
	fmt.Println(total)
}
```
http://play.golang.org/p/UWIAmPCRCu

4. What did you expect to see?
output 4000

5. What did you see instead?
`fatal error: all goroutines are asleep - deadlock!`
runNum more big，the probability of deadlock more often
",1,sync  document that double rlock isn t safe   please answer these questions before submitting your issue  thanks        what version of go are you using   go version     go version     darwin         what operating system and processor architecture are you using   go env     goarch      gobin     goexe     gohostarch      gohostos  darwin   goos  darwin   gopath     gorace     goroot   usr local go   gotooldir   usr local go pkg tool darwin            cc  clang   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fno common   cxx  clang     cgo enabled           what did you do      go  package main    import    	 fmt   	 sync        func main      	ch    make chan int   	testfunc    func      		weirdlock    sync rwmutex    		go func      			weirdlock rlock    			go func      				weirdlock rlock    				for i       i      i      					func      						weirdlock rlock    						ch       						weirdlock runlock    					     				   				weirdlock runlock    			     			weirdlock runlock    		     		go func      			weirdlock lock    			ch       			weirdlock unlock    		     	   	runnum       	for i       i   runnum  i      		testfunc    	   	total       	for i       i     runnum  i      		total      ch  	   	  expect   runnum  	fmt println total                   what did you expect to see   output         what did you see instead    fatal error  all goroutines are asleep   deadlock    runnum more big，the probability of deadlock more often  ,1
214013,16544575177.0,IssuesEvent,2021-05-27 21:42:44,golang/go,https://api.github.com/repos/golang/go,closed,net/http: Client.Do documentation is incorrect about *url.Error.Timeout,Documentation NeedsFix,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.16.4 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.
It also reproduces with go1.17 devel.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""on""
GOARCH=""amd64""
GOBIN=""/home/manlio/.local/bin""
GOCACHE=""/home/manlio/.cache/go-build""
GOENV=""/home/manlio/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""*.local""
GOMODCACHE=""/home/manlio/.local/lib/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""*.local""
GOOS=""linux""
GOPATH=""/home/manlio/.local/lib/go:/home/manlio/src/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/lib/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/lib/go/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""go1.16.4""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build1653706074=/tmp/go-build -gno-record-gcc-switches""
GOROOT/bin/go version: go version go1.16.4 linux/amd64
GOROOT/bin/go tool compile -V: compile version go1.16.4
uname -sr: Linux 5.12.5-arch1-1
/usr/lib/libc.so.6: GNU C Library (GNU libc) release release version 2.33.
gdb --version: GNU gdb (GDB) 10.2
</pre></details>

### What did you do?

https://play.golang.org/p/YQH5oWtQWjC

### What did you expect to see?

`timed out: true`

As documented by https://golang.org/pkg/net/http/#Client.Do:
```
Any returned error will be of type *url.Error. The url.Error value's Timeout method will report true if request timed out or was canceled.
```

### What did you see instead?

`timed out: false`
",1.0,"net/http: Client.Do documentation is incorrect about *url.Error.Timeout - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.16.4 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.
It also reproduces with go1.17 devel.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""on""
GOARCH=""amd64""
GOBIN=""/home/manlio/.local/bin""
GOCACHE=""/home/manlio/.cache/go-build""
GOENV=""/home/manlio/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""*.local""
GOMODCACHE=""/home/manlio/.local/lib/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""*.local""
GOOS=""linux""
GOPATH=""/home/manlio/.local/lib/go:/home/manlio/src/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/lib/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/lib/go/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""go1.16.4""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build1653706074=/tmp/go-build -gno-record-gcc-switches""
GOROOT/bin/go version: go version go1.16.4 linux/amd64
GOROOT/bin/go tool compile -V: compile version go1.16.4
uname -sr: Linux 5.12.5-arch1-1
/usr/lib/libc.so.6: GNU C Library (GNU libc) release release version 2.33.
gdb --version: GNU gdb (GDB) 10.2
</pre></details>

### What did you do?

https://play.golang.org/p/YQH5oWtQWjC

### What did you expect to see?

`timed out: true`

As documented by https://golang.org/pkg/net/http/#Client.Do:
```
Any returned error will be of type *url.Error. The url.Error value's Timeout method will report true if request timed out or was canceled.
```

### What did you see instead?

`timed out: false`
",1,net http  client do documentation is incorrect about  url error timeout            what version of go are you using   go version            go version  go version       linux             does this issue reproduce with the latest release     yes   it also reproduces with     devel         what operating system and processor architecture are you using   go env          go env  output       go env     on   goarch      gobin   home manlio  local bin   gocache   home manlio  cache go build   goenv   home manlio  config go env   goexe     goflags     gohostarch      gohostos  linux   goinsecure    local   gomodcache   home manlio  local lib go pkg mod   gonoproxy     gonosumdb    local   goos  linux   gopath   home manlio  local lib go  home manlio src go   goprivate     goproxy     goroot   usr lib go   gosumdb  sum golang org   gotmpdir     gotooldir   usr lib go pkg tool linux     govcs     goversion          gccgo  gccgo   ar  ar   cc  gcc   cxx  g     cgo enabled      gomod   dev null   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches   goroot bin go version  go version       linux    goroot bin go tool compile  v  compile version        uname  sr  linux             usr lib libc so    gnu c library  gnu libc  release release version       gdb   version  gnu gdb  gdb                 what did you do              what did you expect to see      timed out  true     as documented by         any returned error will be of type  url error  the url error value s timeout method will report true if request timed out or was canceled              what did you see instead      timed out  false   ,1
132422,5185556174.0,IssuesEvent,2017-01-20 10:49:41,openvstorage/volumedriver,https://api.github.com/repos/openvstorage/volumedriver,closed,Scrubber hangs when logging to stderr,priority_urgent SRP type_bug,Possibly caused by a pipe buffer filling up and not being drained via the read end.,1.0,Scrubber hangs when logging to stderr - Possibly caused by a pipe buffer filling up and not being drained via the read end.,0,scrubber hangs when logging to stderr   possibly caused by a pipe buffer filling up and not being drained via the read end ,0
51762,7726726277.0,IssuesEvent,2018-05-24 22:21:33,golang/go,https://api.github.com/repos/golang/go,closed,"""json"" links on https://go.googlesource.com/ return invalid JSON documents",Documentation,"Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?

N/A

### Does this issue reproduce with the latest release?

N/A

### What operating system and processor architecture are you using (`go env`)?

N/A

### What did you do?

    curl -s 'https://go.googlesource.com/go/+refs?format=JSON' | jq .

### What did you expect to see?

A valid JSON document retrieved by `curl` and `jq` displaying a pretty JSON data.



### What did you see instead?

```sh-session
$ curl -s 'https://go.googlesource.com/go/+refs?format=JSON' | jq .
parse error: Invalid numeric literal at line 1, column 2
```

The first line of returned document is:

```
)]}'
```

which is indeed invalid JSON.
",1.0,"""json"" links on https://go.googlesource.com/ return invalid JSON documents - Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?

N/A

### Does this issue reproduce with the latest release?

N/A

### What operating system and processor architecture are you using (`go env`)?

N/A

### What did you do?

    curl -s 'https://go.googlesource.com/go/+refs?format=JSON' | jq .

### What did you expect to see?

A valid JSON document retrieved by `curl` and `jq` displaying a pretty JSON data.



### What did you see instead?

```sh-session
$ curl -s 'https://go.googlesource.com/go/+refs?format=JSON' | jq .
parse error: Invalid numeric literal at line 1, column 2
```

The first line of returned document is:

```
)]}'
```

which is indeed invalid JSON.
",1, json  links on   return invalid json documents   please answer these questions before submitting your issue  thanks           what version of go are you using   go version       n a        does this issue reproduce with the latest release     n a        what operating system and processor architecture are you using   go env       n a        what did you do         curl  s      jq          what did you expect to see     a valid json document retrieved by  curl  and  jq  displaying a pretty json data             what did you see instead        sh session    curl  s      jq    parse error  invalid numeric literal at line    column           the first line of returned document is                       which is indeed invalid json   ,1
406363,27561139336.0,IssuesEvent,2023-03-07 22:08:46,golang/go,https://api.github.com/repos/golang/go,closed,net: document that on some systems SetLinger causes conn.Close to block,Documentation help wanted NeedsFix,"<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.20.1 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/stephen/.cache/go-build""
GOENV=""/home/stephen/.config/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/stephen/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/stephen/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""go1.20.1""
GCCGO=""gccgo""
GOAMD64=""v1""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
GOWORK=""""
CGO_CFLAGS=""-O2 -g""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-O2 -g""
CGO_FFLAGS=""-O2 -g""
CGO_LDFLAGS=""-O2 -g""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build223210887=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->

We added an explicit call to `SetLinger(15)` here: https://github.com/ava-labs/avalanchego/commit/1a2dca18d22a7a78e421e95dbdbe038287ee8361

### What did you expect to see?

https://github.com/golang/go/blob/b94dc384cabf75e7e8703265cd80f5324f84b642/src/net/tcpsock.go#L161-L173 claims that providing `SetLinger` with a positive value will:

> // If sec > 0, the data is sent in the background as with sec < 0. On
> // some operating systems after sec seconds have elapsed any remaining
> // unsent data may be discarded.

We expected for the OS to flush any outstanding data over the TCP stream in the background.

### What did you see instead?

It doesn't seem that the data is being sent in the backaground, but that `conn.Close()` may block until the specified timeout.

I don't think this is actually unexpected for the behavior of [SO_LINGER](https://linux.die.net/man/3/setsockopt):

> SO_LINGER
> Lingers on a close() if data is present. This option controls the action taken when unsent messages queue on a socket and close() is performed. If SO_LINGER is set, the system shall block the process during close() until it can transmit the data or until the time expires. If SO_LINGER is not specified, and close() is issued, the system handles the call in a way that allows the process to continue as quickly as possible. This option takes a linger structure, as defined in the <[sys/socket.h](https://linux.die.net/include/sys/socket.h)> header, to specify the state of the option and linger interval.

However, I feel like the comment on `SetLinger` seems to contradict the man pages.
",1.0,"net: document that on some systems SetLinger causes conn.Close to block - <!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.20.1 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/stephen/.cache/go-build""
GOENV=""/home/stephen/.config/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/stephen/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/stephen/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""go1.20.1""
GCCGO=""gccgo""
GOAMD64=""v1""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
GOWORK=""""
CGO_CFLAGS=""-O2 -g""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-O2 -g""
CGO_FFLAGS=""-O2 -g""
CGO_LDFLAGS=""-O2 -g""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build223210887=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->

We added an explicit call to `SetLinger(15)` here: https://github.com/ava-labs/avalanchego/commit/1a2dca18d22a7a78e421e95dbdbe038287ee8361

### What did you expect to see?

https://github.com/golang/go/blob/b94dc384cabf75e7e8703265cd80f5324f84b642/src/net/tcpsock.go#L161-L173 claims that providing `SetLinger` with a positive value will:

> // If sec > 0, the data is sent in the background as with sec < 0. On
> // some operating systems after sec seconds have elapsed any remaining
> // unsent data may be discarded.

We expected for the OS to flush any outstanding data over the TCP stream in the background.

### What did you see instead?

It doesn't seem that the data is being sent in the backaground, but that `conn.Close()` may block until the specified timeout.

I don't think this is actually unexpected for the behavior of [SO_LINGER](https://linux.die.net/man/3/setsockopt):

> SO_LINGER
> Lingers on a close() if data is present. This option controls the action taken when unsent messages queue on a socket and close() is performed. If SO_LINGER is set, the system shall block the process during close() until it can transmit the data or until the time expires. If SO_LINGER is not specified, and close() is issued, the system handles the call in a way that allows the process to continue as quickly as possible. This option takes a linger structure, as defined in the <[sys/socket.h](https://linux.die.net/include/sys/socket.h)> header, to specify the state of the option and linger interval.

However, I feel like the comment on `SetLinger` seems to contradict the man pages.
",1,net  document that on some systems setlinger causes conn close to block         please answer these questions before submitting your issue  thanks              what version of go are you using   go version            go version  go version       linux             does this issue reproduce with the latest release     yes         what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   home stephen  cache go build   goenv   home stephen  config go env   goexe     goexperiment     goflags     gohostarch      gohostos  linux   goinsecure     gomodcache   home stephen go pkg mod   gonoproxy     gonosumdb     goos  linux   gopath   home stephen go   goprivate     goproxy     goroot   usr local go   gosumdb  sum golang org   gotmpdir     gotooldir   usr local go pkg tool linux     govcs     goversion          gccgo  gccgo          ar  ar   cc  gcc   cxx  g     cgo enabled      gomod   dev null   gowork     cgo cflags      g   cgo cppflags     cgo cxxflags      g   cgo fflags      g   cgo ldflags      g   pkg config  pkg config   gogccflags   fpic     pthread  wl   no gc sections  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches             what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on go dev play is best          we added an explicit call to  setlinger     here           what did you expect to see       claims that providing  setlinger  with a positive value will          if sec      the data is sent in the background as with sec      on       some operating systems after sec seconds have elapsed any remaining       unsent data may be discarded     we expected for the os to flush any outstanding data over the tcp stream in the background         what did you see instead     it doesn t seem that the data is being sent in the backaground  but that  conn close    may block until the specified timeout     i don t think this is actually unexpected for the behavior of          so linger    lingers on a close   if data is present  this option controls the action taken when unsent messages queue on a socket and close   is performed  if so linger is set  the system shall block the process during close   until it can transmit the data or until the time expires  if so linger is not specified  and close   is issued  the system handles the call in a way that allows the process to continue as quickly as possible  this option takes a linger structure  as defined in the      header  to specify the state of the option and linger interval     however  i feel like the comment on  setlinger  seems to contradict the man pages   ,1
31748,4288930771.0,IssuesEvent,2016-07-17 19:45:58,wffls/waffles,https://api.github.com/repos/wffls/waffles,opened,Enable resources to call other resources,design resource thinking,"The main reason I began exploring using Bash and core utils as a configuration management tool is because I admire the [Unix philosophy](https://en.wikipedia.org/wiki/Unix_philosophy). I've assumed that by building atomic resources, they could automatically be used to compose more complex resources. A simple example of this is with the [sudoers.cmd](https://github.com/wffls/waffles/blob/a2b53efaa0307f8a239396ac8a36df625655d47b/resources/sudoers_cmd.sh) resource.

However, this difficult to achieve with the way resources are currently designed. Discussions in #175 and #180 give details as to where this begins to cause problems.

This issue will serve as an area for discussion about how resources could be redesigned to enable them to be completely independent and atomic, thus allowing them to be called by other resources.",1.0,"Enable resources to call other resources - The main reason I began exploring using Bash and core utils as a configuration management tool is because I admire the [Unix philosophy](https://en.wikipedia.org/wiki/Unix_philosophy). I've assumed that by building atomic resources, they could automatically be used to compose more complex resources. A simple example of this is with the [sudoers.cmd](https://github.com/wffls/waffles/blob/a2b53efaa0307f8a239396ac8a36df625655d47b/resources/sudoers_cmd.sh) resource.

However, this difficult to achieve with the way resources are currently designed. Discussions in #175 and #180 give details as to where this begins to cause problems.

This issue will serve as an area for discussion about how resources could be redesigned to enable them to be completely independent and atomic, thus allowing them to be called by other resources.",0,enable resources to call other resources   the main reason i began exploring using bash and core utils as a configuration management tool is because i admire the     i ve assumed that by building atomic resources  they could automatically be used to compose more complex resources  a simple example of this is with the     resource     however  this difficult to achieve with the way resources are currently designed  discussions in    and    give details as to where this begins to cause problems     this issue will serve as an area for discussion about how resources could be redesigned to enable them to be completely independent and atomic  thus allowing them to be called by other resources ,0
173132,14403475916.0,IssuesEvent,2020-12-03 16:06:10,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.16: document mime/multipart changes for Go 1.16,Documentation NeedsInvestigation help wanted release-blocker,"As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

<dl id=""mime/multipart""><dt><a href=""/pkg/mime/multipart/"">mime/multipart</a></dt>
  <dd>
    <p><!-- CL 247477 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/247477"">https://golang.org/cl/247477</a>: return overflow errors in Reader.ReadForm
    </p>
  </dd>
</dl><!-- mime/multipart -->

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.",1.0,"doc/go1.16: document mime/multipart changes for Go 1.16 - As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

<dl id=""mime/multipart""><dt><a href=""/pkg/mime/multipart/"">mime/multipart</a></dt>
  <dd>
    <p><!-- CL 247477 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/247477"">https://golang.org/cl/247477</a>: return overflow errors in Reader.ReadForm
    </p>
  </dd>
</dl><!-- mime/multipart -->

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.",1,doc      document mime multipart changes for go       as of filing this issue  the     contained the following html        mime multipart                        todo    a href    return overflow errors in reader readform                           per     it s a release blocker for go     beta   to have a complete draft of the eventual release notes  and so the todo needs to be resolved     a sequence of steps to resolve this issue may be        come up with a draft release note entry in this issue  then move the issue to needsfix state      send a cl with  doc           and include  for     fixes   this issue    in the body ,1
155432,5955254225.0,IssuesEvent,2017-05-28 03:33:07,NodeBB/NodeBB,https://api.github.com/repos/NodeBB/NodeBB,closed,Changing admin setting 'Custom Default Avatar' has no effect,low priority regression,"* NodeBB version 1.4.5, hash d19e59f1e13f4a22eb44d5334b2a81d99e030b36
* MongoDB version 3.2.11
* Exact steps to cause this issue
    1. With admin user set custom default avatar within Admin > Settings > Uploads > Profile Avatars:
        * Allow users to upload profile images: on (default) changed to off
        * Custom Default Avatar: none (default) changed to uploaded custom 128 x 128 PNG image file
        * Save (blue button at bottom right)
        * Restart nodeBB in Dashboard
    2. Registered a new user (using another browser)
* What you expected
    * I expected the new user to have my custom PNG image as default avatar.
* What happened instead
    * Instead the new user still has the NodeBB-default avatar with the first letter of its user name in it (it simply is a single letter inside a `<div>` element plus some styling: `.avatar.avatar-rounded { border-radius: 50%; }`)",1.0,"Changing admin setting 'Custom Default Avatar' has no effect - * NodeBB version 1.4.5, hash d19e59f1e13f4a22eb44d5334b2a81d99e030b36
* MongoDB version 3.2.11
* Exact steps to cause this issue
    1. With admin user set custom default avatar within Admin > Settings > Uploads > Profile Avatars:
        * Allow users to upload profile images: on (default) changed to off
        * Custom Default Avatar: none (default) changed to uploaded custom 128 x 128 PNG image file
        * Save (blue button at bottom right)
        * Restart nodeBB in Dashboard
    2. Registered a new user (using another browser)
* What you expected
    * I expected the new user to have my custom PNG image as default avatar.
* What happened instead
    * Instead the new user still has the NodeBB-default avatar with the first letter of its user name in it (it simply is a single letter inside a `<div>` element plus some styling: `.avatar.avatar-rounded { border-radius: 50%; }`)",0,changing admin setting  custom default avatar  has no effect     nodebb version        hash      mongodb version          exact steps to cause this issue         with admin user set custom default avatar within admin   settings   uploads   profile avatars             allow users to upload profile images  on  default  changed to off            custom default avatar  none  default  changed to uploaded custom   x   png image file            save  blue button at bottom right             restart nodebb in dashboard         registered a new user  using another browser     what you expected        i expected the new user to have my custom png image as default avatar     what happened instead        instead the new user still has the nodebb default avatar with the first letter of its user name in it  it simply is a single letter inside a     element plus some styling    avatar avatar rounded   border radius         ,0
94330,27171183163.0,IssuesEvent,2023-02-17 19:35:52,apache/daffodil-vscode,https://api.github.com/repos/apache/daffodil-vscode,opened,Add build-time launch file schema constraints from allowed tunable properties,enhancement javascript build typescript,"#200 adds the ability to specify variables and tunables as maps of string-valued properties. The allowed set of tunable property names is fixed in [an XML configuration file](https://github.com/apache/daffodil/blob/163fa7336148b2e1a6d1f2e44967edaf1fea6616/daffodil-propgen/src/main/resources/org/apache/daffodil/xsd/dafext.xsd#L101) that is packaged in the daffodil-lib artifact.

It should be possible to create a build task that re-writes the package.json file to include schema restrictions on the tunable property names that are derived from that upstream configuration file. Then the built extension could better validate launch.json files that use tunables.",1.0,"Add build-time launch file schema constraints from allowed tunable properties - #200 adds the ability to specify variables and tunables as maps of string-valued properties. The allowed set of tunable property names is fixed in [an XML configuration file](https://github.com/apache/daffodil/blob/163fa7336148b2e1a6d1f2e44967edaf1fea6616/daffodil-propgen/src/main/resources/org/apache/daffodil/xsd/dafext.xsd#L101) that is packaged in the daffodil-lib artifact.

It should be possible to create a build task that re-writes the package.json file to include schema restrictions on the tunable property names that are derived from that upstream configuration file. Then the built extension could better validate launch.json files that use tunables.",0,add build time launch file schema constraints from allowed tunable properties      adds the ability to specify variables and tunables as maps of string valued properties  the allowed set of tunable property names is fixed in     that is packaged in the daffodil lib artifact     it should be possible to create a build task that re writes the package json file to include schema restrictions on the tunable property names that are derived from that upstream configuration file  then the built extension could better validate launch json files that use tunables ,0
311696,26806211387.0,IssuesEvent,2023-02-01 18:29:55,gravitational/teleport,https://api.github.com/repos/gravitational/teleport,opened,`TestIntegrations/CmdLabels` flakiness,flaky tests,"## Failure

#### Link(s) to logs

- https://github.com/gravitational/teleport/actions/runs/4067295252/jobs/7004473695

#### Relevant snippet

```
integration_test.go:5237: 
[976](https://github.com/gravitational/teleport/actions/runs/4067295252/jobs/7004473695#step:6:977)
        	Error Trace:	/__w/teleport/teleport/integration/integration_test.go:5237
[977](https://github.com/gravitational/teleport/actions/runs/4067295252/jobs/7004473695#step:6:978)
        	Error:      	Received unexpected error:
[978](https://github.com/gravitational/teleport/actions/runs/4067295252/jobs/7004473695#step:6:979)
        	            	failed connecting to node 00000000-0000-0000-0000-000000000000. Teleport proxy failed to connect to ""node"" agent """" over reverse tunnel:
[979](https://github.com/gravitational/teleport/actions/runs/4067295252/jobs/7004473695#step:6:980)
        	            	
[980](https://github.com/gravitational/teleport/actions/runs/4067295252/jobs/7004473695#step:6:981)
        	            	  no tunnel connection found: no node reverse tunnel for 00000000-0000-0000-0000-000000000000.local-site found
[981](https://github.com/gravitational/teleport/actions/runs/4067295252/jobs/7004473695#step:6:982)
        	            	
[982](https://github.com/gravitational/teleport/actions/runs/4067295252/jobs/7004473695#step:6:983)
        	            	This usually means that the agent is offline or has disconnected. Check the
[983](https://github.com/gravitational/teleport/actions/runs/4067295252/jobs/7004473695#step:6:984)
        	            	agent logs and, if the issue persists, try restarting it or re-registering it
[984](https://github.com/gravitational/teleport/actions/runs/4067295252/jobs/7004473695#step:6:985)
        	            	with the cluster.
[985](https://github.com/gravitational/teleport/actions/runs/4067295252/jobs/7004473695#step:6:986)
        	Test:       	TestIntegrations/CmdLabels/Worker_only
[986](https://github.com/gravitational/teleport/actions/runs/4067295252/jobs/7004473695#step:6:987)
        --- FAIL: TestIntegrations/CmdLabels/Worker_only (1.14s)```
",1.0,"`TestIntegrations/CmdLabels` flakiness - ## Failure

#### Link(s) to logs

- https://github.com/gravitational/teleport/actions/runs/4067295252/jobs/7004473695

#### Relevant snippet

```
integration_test.go:5237: 
[976](https://github.com/gravitational/teleport/actions/runs/4067295252/jobs/7004473695#step:6:977)
        	Error Trace:	/__w/teleport/teleport/integration/integration_test.go:5237
[977](https://github.com/gravitational/teleport/actions/runs/4067295252/jobs/7004473695#step:6:978)
        	Error:      	Received unexpected error:
[978](https://github.com/gravitational/teleport/actions/runs/4067295252/jobs/7004473695#step:6:979)
        	            	failed connecting to node 00000000-0000-0000-0000-000000000000. Teleport proxy failed to connect to ""node"" agent """" over reverse tunnel:
[979](https://github.com/gravitational/teleport/actions/runs/4067295252/jobs/7004473695#step:6:980)
        	            	
[980](https://github.com/gravitational/teleport/actions/runs/4067295252/jobs/7004473695#step:6:981)
        	            	  no tunnel connection found: no node reverse tunnel for 00000000-0000-0000-0000-000000000000.local-site found
[981](https://github.com/gravitational/teleport/actions/runs/4067295252/jobs/7004473695#step:6:982)
        	            	
[982](https://github.com/gravitational/teleport/actions/runs/4067295252/jobs/7004473695#step:6:983)
        	            	This usually means that the agent is offline or has disconnected. Check the
[983](https://github.com/gravitational/teleport/actions/runs/4067295252/jobs/7004473695#step:6:984)
        	            	agent logs and, if the issue persists, try restarting it or re-registering it
[984](https://github.com/gravitational/teleport/actions/runs/4067295252/jobs/7004473695#step:6:985)
        	            	with the cluster.
[985](https://github.com/gravitational/teleport/actions/runs/4067295252/jobs/7004473695#step:6:986)
        	Test:       	TestIntegrations/CmdLabels/Worker_only
[986](https://github.com/gravitational/teleport/actions/runs/4067295252/jobs/7004473695#step:6:987)
        --- FAIL: TestIntegrations/CmdLabels/Worker_only (1.14s)```
",0, testintegrations cmdlabels  flakiness      failure         link s  to logs                relevant snippet         integration test go                   	error trace 	   w teleport teleport integration integration test go                 	error       	received unexpected error                	            	failed connecting to node            teleport proxy failed to connect to  node  agent    over reverse tunnel                	            	               	            	  no tunnel connection found  no node reverse tunnel for           local site found               	            	               	            	this usually means that the agent is offline or has disconnected  check the               	            	agent logs and  if the issue persists  try restarting it or re registering it               	            	with the cluster                	test        	testintegrations cmdlabels worker only                   fail  testintegrations cmdlabels worker only           ,0
21667,4731514014.0,IssuesEvent,2016-10-19 02:32:39,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: test -i and -o options together don't work as expected,Documentation NeedsFix,"### What version of Go are you using (`go version`)?

`go version go1.7 darwin/amd64`

### What operating system and processor architecture are you using (`go env`)?

```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/aaronl/go""
GORACE=""""
GOROOT=""/usr/local/go""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
```

### What did you do?

I tried to run `go test` with both the `-i` and `-o` flags. The help output implies this combination is supported:

```
           -i
               Install packages that are dependencies of the test.
               Do not run the test.

           -o file
               Compile the test binary to the named file.
               The test still runs (unless -c or -i is specified).
```

```
$ go test
PASS
ok     	fmt    	0.070s
$ go test -i -o testbinary
$ ./testbinary
-bash: ./testbinary: No such file or directory
```

### What did you expect to see?

I expected `go test -i -o testbinary` to create a `testbinary` executable, and also install the package's dependencies.

### What did you see instead?

No executable created.",1.0,"cmd/go: test -i and -o options together don't work as expected - ### What version of Go are you using (`go version`)?

`go version go1.7 darwin/amd64`

### What operating system and processor architecture are you using (`go env`)?

```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/aaronl/go""
GORACE=""""
GOROOT=""/usr/local/go""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
```

### What did you do?

I tried to run `go test` with both the `-i` and `-o` flags. The help output implies this combination is supported:

```
           -i
               Install packages that are dependencies of the test.
               Do not run the test.

           -o file
               Compile the test binary to the named file.
               The test still runs (unless -c or -i is specified).
```

```
$ go test
PASS
ok     	fmt    	0.070s
$ go test -i -o testbinary
$ ./testbinary
-bash: ./testbinary: No such file or directory
```

### What did you expect to see?

I expected `go test -i -o testbinary` to create a `testbinary` executable, and also install the package's dependencies.

### What did you see instead?

No executable created.",1,cmd go  test  i and  o options together don t work as expected       what version of go are you using   go version        go version     darwin           what operating system and processor architecture are you using   go env            goarch      gobin     goexe     gohostarch      gohostos  darwin   goos  darwin   gopath   users aaronl go   gorace     goroot   usr local go   gotooldir   usr local go pkg tool darwin     cc  clang   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    gno record gcc switches  fno common   cxx  clang     cgo enabled                 what did you do     i tried to run  go test  with both the   i  and   o  flags  the help output implies this combination is supported                      i                 install packages that are dependencies of the test                  do not run the test                 o file                 compile the test binary to the named file                  the test still runs  unless  c or  i is specified                  go test  pass  ok     	fmt    	       go test  i  o testbinary      testbinary   bash    testbinary  no such file or directory             what did you expect to see     i expected  go test  i  o testbinary  to create a  testbinary  executable  and also install the package s dependencies         what did you see instead     no executable created ,1
32561,6086592786.0,IssuesEvent,2017-06-18 03:04:18,golang/go,https://api.github.com/repos/golang/go,opened,Unusual code in proc.go could use documentation,Documentation,"### What version of Go are you using (`go version`)?
go version devel +d293c85e39 Sat Jun 17 08:17:14 2017 +0000 linux/amd64

### What operating system and processor architecture are you using (`go env`)?
```GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/velovix/go""
GORACE=""""
GOROOT=""/home/velovix/go-source""
GOTOOLDIR=""/home/velovix/go-source/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build407292918=/tmp/go-build -gno-record-gcc-switches""
CXX=""g++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
```

Please see this discussion on golang-nuts:
https://groups.google.com/d/topic/golang-nuts/FnF3oZeJ7aY/discussion

There is some code at lines 198-202 in `/src/runtime/proc.go` that could do with a bit of documentation. The code in question can be found [here](https://github.com/golang/go/blob/df0892cbf854e76fae6e875043b05c194e37f52d/src/runtime/proc.go#L208) on Github.

Here is my current draft:
```
// In case exit fails to stop the program, try to stop it by causing a
// panic. If that doesn't work, stall the program.
// This is here to help catch problems with new ports, where exit may not
// be properly implemented.
```

I will send in a CL if that looks okay.",1.0,"Unusual code in proc.go could use documentation - ### What version of Go are you using (`go version`)?
go version devel +d293c85e39 Sat Jun 17 08:17:14 2017 +0000 linux/amd64

### What operating system and processor architecture are you using (`go env`)?
```GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/velovix/go""
GORACE=""""
GOROOT=""/home/velovix/go-source""
GOTOOLDIR=""/home/velovix/go-source/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build407292918=/tmp/go-build -gno-record-gcc-switches""
CXX=""g++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
```

Please see this discussion on golang-nuts:
https://groups.google.com/d/topic/golang-nuts/FnF3oZeJ7aY/discussion

There is some code at lines 198-202 in `/src/runtime/proc.go` that could do with a bit of documentation. The code in question can be found [here](https://github.com/golang/go/blob/df0892cbf854e76fae6e875043b05c194e37f52d/src/runtime/proc.go#L208) on Github.

Here is my current draft:
```
// In case exit fails to stop the program, try to stop it by causing a
// panic. If that doesn't work, stall the program.
// This is here to help catch problems with new ports, where exit may not
// be properly implemented.
```

I will send in a CL if that looks okay.",1,unusual code in proc go could use documentation       what version of go are you using   go version     go version devel    sat jun              linux          what operating system and processor architecture are you using   go env        goarch      gobin     goexe     gohostarch      gohostos  linux   goos  linux   gopath   home velovix go   gorace     goroot   home velovix go source   gotooldir   home velovix go source pkg tool linux     gccgo  gccgo   cc  gcc   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches   cxx  g     cgo enabled      cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config          please see this discussion on golang nuts        there is some code at lines     in   src runtime proc go  that could do with a bit of documentation  the code in question can be found     on github     here is my current draft           in case exit fails to stop the program  try to stop it by causing a     panic  if that doesn t work  stall the program      this is here to help catch problems with new ports  where exit may not     be properly implemented          i will send in a cl if that looks okay ,1
599499,18275506441.0,IssuesEvent,2021-10-04 18:19:17,magento/magento2,https://api.github.com/repos/magento/magento2,closed,Stabilize Integration Tests,Progress: PR in progress Priority: P1 Project: Platform Health,"* <https://github.com/magento/magento2>
* <https://github.com/magento/partners-magento2ee>
* <https://github.com/magento/partners-magento2b2b>
* <https://github.com/magento/partners-magento2-infrastructure>
* <https://github.com/magento/magento2-sample-data>

AC:
* Integration test build is green (PHP 7.4 & PHP 8.0)
* Fix functional issues that cause failed tests",1.0,"Stabilize Integration Tests - * <https://github.com/magento/magento2>
* <https://github.com/magento/partners-magento2ee>
* <https://github.com/magento/partners-magento2b2b>
* <https://github.com/magento/partners-magento2-infrastructure>
* <https://github.com/magento/magento2-sample-data>

AC:
* Integration test build is green (PHP 7.4 & PHP 8.0)
* Fix functional issues that cause failed tests",0,stabilize integration tests                                   ac     integration test build is green  php       php         fix functional issues that cause failed tests,0
24186,5037440604.0,IssuesEvent,2016-12-17 17:26:39,golang/go,https://api.github.com/repos/golang/go,opened,doc: mention that CGO_ENABLED is now sticky in 1.8,Documentation,"CGO_ENABLED is sticky in Go 1.8. Document this.

Some discussion in:
https://github.com/golang/go/issues/18360#issuecomment-267752866

",1.0,"doc: mention that CGO_ENABLED is now sticky in 1.8 - CGO_ENABLED is sticky in Go 1.8. Document this.

Some discussion in:
https://github.com/golang/go/issues/18360#issuecomment-267752866

",1,doc  mention that cgo enabled is now sticky in       cgo enabled is sticky in go      document this     some discussion in        ,1
31657,5967677178.0,IssuesEvent,2017-05-30 16:26:17,golang/go,https://api.github.com/repos/golang/go,closed,x/text/unicode/collate/build: docs out of date,Documentation,"The [docs](https://godoc.org/golang.org/x/text/collate/build) for (* Builder).Build() say ""TODO: return Weighter instead"", but the method does indeed return a Weighter. The docs should be updated.",1.0,"x/text/unicode/collate/build: docs out of date - The [docs](https://godoc.org/golang.org/x/text/collate/build) for (* Builder).Build() say ""TODO: return Weighter instead"", but the method does indeed return a Weighter. The docs should be updated.",1,x text unicode collate build  docs out of date   the     for    builder  build   say  todo  return weighter instead   but the method does indeed return a weighter  the docs should be updated ,1
275121,20907589675.0,IssuesEvent,2022-03-24 05:09:39,golang/go,https://api.github.com/repos/golang/go,closed,"spec: in array and slice literals, the index/key can be non-integer type",Documentation NeedsFix,"### What version of Go are you using (`go version`)?
Go playground

### What operating system and processor architecture are you using (`go env`)?
```golang
package main

const k float64 = 3.0

var _ = []int{k: 3}
var _ = [...]int{k: 3}

func main() {}
```
See https://play.golang.org/p/x3keRiD0fVT. This compiles without an error.

### What did you expect to see?

From the spec:

> For array and slice literals the following rules apply:
> * Each element has an associated integer index marking its position in the array.
> * An element with a key uses the key as its index. The key must be a non-negative constant representable by a value of type int; and **_if it is typed it must be of integer type_**.
> * An element without a key uses the previous element's index plus one. If the first element has no key, its index is zero.

It mentions that if the index is typed, it must be of integer type. However, the above code compiles even if the index has type `float64`. Probably the spec should be saying ""can be converted to int"" or something, or the compiler should report an error?",1.0,"spec: in array and slice literals, the index/key can be non-integer type - ### What version of Go are you using (`go version`)?
Go playground

### What operating system and processor architecture are you using (`go env`)?
```golang
package main

const k float64 = 3.0

var _ = []int{k: 3}
var _ = [...]int{k: 3}

func main() {}
```
See https://play.golang.org/p/x3keRiD0fVT. This compiles without an error.

### What did you expect to see?

From the spec:

> For array and slice literals the following rules apply:
> * Each element has an associated integer index marking its position in the array.
> * An element with a key uses the key as its index. The key must be a non-negative constant representable by a value of type int; and **_if it is typed it must be of integer type_**.
> * An element without a key uses the previous element's index plus one. If the first element has no key, its index is zero.

It mentions that if the index is typed, it must be of integer type. However, the above code compiles even if the index has type `float64`. Probably the spec should be saying ""can be converted to int"" or something, or the compiler should report an error?",1,spec  in array and slice literals  the index key can be non integer type       what version of go are you using   go version     go playground        what operating system and processor architecture are you using   go env        golang  package main    const k            var      int k      var      int k        func main            see   this compiles without an error         what did you expect to see     from the spec       for array and slice literals the following rules apply       each element has an associated integer index marking its position in the array       an element with a key uses the key as its index  the key must be a non negative constant representable by a value of type int  and    if it is typed it must be of integer type          an element without a key uses the previous element s index plus one  if the first element has no key  its index is zero     it mentions that if the index is typed  it must be of integer type  however  the above code compiles even if the index has type      probably the spec should be saying  can be converted to int  or something  or the compiler should report an error ,1
213859,16541619935.0,IssuesEvent,2021-05-27 17:33:26,http4s/http4s,https://api.github.com/repos/http4s/http4s,opened,Flaky Tomcat test,module:tomcat testing,"```
==> X org.http4s.tomcat.server.TomcatServerSuite.server should route requests on the service executor  5.567s munit.ComparisonFailException: /home/runner/work/http4s/http4s/tomcat-server/src/test/scala/org/http4s/tomcat/server/TomcatServerSuite.scala:97
96:      .map(_.startsWith(""http4s-suite-""))
97:      .assert
98:  }
value is not true
=> Obtained
false
=> Diff (- obtained, + expected)
-false
+true
```

https://github.com/http4s/http4s/pull/4898/checks?check_run_id=2687198536",1.0,"Flaky Tomcat test - ```
==> X org.http4s.tomcat.server.TomcatServerSuite.server should route requests on the service executor  5.567s munit.ComparisonFailException: /home/runner/work/http4s/http4s/tomcat-server/src/test/scala/org/http4s/tomcat/server/TomcatServerSuite.scala:97
96:      .map(_.startsWith(""http4s-suite-""))
97:      .assert
98:  }
value is not true
=> Obtained
false
=> Diff (- obtained, + expected)
-false
+true
```

https://github.com/http4s/http4s/pull/4898/checks?check_run_id=2687198536",0,flaky tomcat test            x org   tomcat server tomcatserversuite server should route requests on the service executor      munit comparisonfailexception   home runner work     tomcat server src test scala org   tomcat server tomcatserversuite scala             map   startswith    suite               assert         value is not true     obtained  false     diff    obtained    expected    false   true          ,0
173135,14403476244.0,IssuesEvent,2020-12-03 16:06:11,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.16: document net/http/httputil changes for Go 1.16,Documentation NeedsInvestigation help wanted release-blocker,"As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

<dl id=""net/http/httputil""><dt><a href=""/pkg/net/http/httputil/"">net/http/httputil</a></dt>
  <dd>
    <p><!-- CL 260637 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/260637"">https://golang.org/cl/260637</a>: flush ReverseProxy immediately if Content-Length is -1
    </p>
  </dd>
</dl><!-- net/http/httputil -->

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.",1.0,"doc/go1.16: document net/http/httputil changes for Go 1.16 - As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

<dl id=""net/http/httputil""><dt><a href=""/pkg/net/http/httputil/"">net/http/httputil</a></dt>
  <dd>
    <p><!-- CL 260637 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/260637"">https://golang.org/cl/260637</a>: flush ReverseProxy immediately if Content-Length is -1
    </p>
  </dd>
</dl><!-- net/http/httputil -->

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.",1,doc      document net http httputil changes for go       as of filing this issue  the     contained the following html        net http httputil                        todo    a href    flush reverseproxy immediately if content length is                              per     it s a release blocker for go     beta   to have a complete draft of the eventual release notes  and so the todo needs to be resolved     a sequence of steps to resolve this issue may be        come up with a draft release note entry in this issue  then move the issue to needsfix state      send a cl with  doc           and include  for     fixes   this issue    in the body ,1
453955,13092539708.0,IssuesEvent,2020-08-03 08:47:03,Nitrokey/nitrokey-start-firmware,https://api.github.com/repos/Nitrokey/nitrokey-start-firmware,opened,Show firmware version in the reader string,bug priority/high,"Following reader string should reflect currently flashed version of our release:
```
Reader ...........: 20A0:4211:FSIJ-1.2.15-431xxxxx:0
```
E.g.:
```
Reader ...........: 20A0:4211:NK10-1.2.15-431xxxxx:0
```",1.0,"Show firmware version in the reader string - Following reader string should reflect currently flashed version of our release:
```
Reader ...........: 20A0:4211:FSIJ-1.2.15-431xxxxx:0
```
E.g.:
```
Reader ...........: 20A0:4211:NK10-1.2.15-431xxxxx:0
```",0,show firmware version in the reader string   following reader string should reflect currently flashed version of our release        reader                  fsij                 e g         reader                                  ,0
69853,9336421954.0,IssuesEvent,2019-03-28 21:11:34,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/cmd/gopls: zero-effect deltas returned in response to textDocument/formatting,Documentation gopls,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.12.1 linux/amd64
$ go list -m golang.org/x/tools
golang.org/x/tools v0.0.0-20190328030505-8f05a32dce9f
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""/home/myitcv/gostuff/src/github.com/myitcv/govim/.bin""
GOCACHE=""/home/myitcv/.cache/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/myitcv/gostuff""
GOPROXY=""""
GORACE=""""
GOROOT=""/home/myitcv/gos""
GOTMPDIR=""""
GOTOOLDIR=""/home/myitcv/gos/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/myitcv/gostuff/src/github.com/myitcv/govim/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build709084862=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

Call `textDocument/formatting` to format the following:

```go
package govim

const ( x = 5
)
```

### What did you expect to see?

A `[]TextEdit` result that only contains non-zero-effect deltas.

### What did you see instead?

A `[]TextEdit` result that contained one zero-effect delta:

```
[]protocol.TextEdit{
    {
        Range: protocol.Range{
            Start: protocol.Position{Line:2, Character:0},
            End:   protocol.Position{Line:3, Character:0},
        },
        NewText: """",
    },
    {
        Range: protocol.Range{
            Start: protocol.Position{Line:3, Character:0},
            End:   protocol.Position{Line:4, Character:0},
        },
        NewText: """",
    },
    {
        Range: protocol.Range{
            Start: protocol.Position{Line:4, Character:0},
            End:   protocol.Position{Line:4, Character:0},
        },
        NewText: ""const (\n"",
    },
    {
        Range: protocol.Range{
            Start: protocol.Position{Line:4, Character:0},
            End:   protocol.Position{Line:4, Character:0},
        },
        NewText: ""\tx = 5\n"",
    },
    {
        Range: protocol.Range{
            Start: protocol.Position{Line:4, Character:0},
            End:   protocol.Position{Line:4, Character:0},
        },
        NewText: "")\n"",
    },
    {
        Range: protocol.Range{
            Start: protocol.Position{Line:4, Character:0},
            End:   protocol.Position{Line:4, Character:0},
        },
        NewText: """",
    },
}
```

The last `TextEdit` implies zero delta.

cc @stamblerre 
",1.0,"x/tools/cmd/gopls: zero-effect deltas returned in response to textDocument/formatting - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.12.1 linux/amd64
$ go list -m golang.org/x/tools
golang.org/x/tools v0.0.0-20190328030505-8f05a32dce9f
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""/home/myitcv/gostuff/src/github.com/myitcv/govim/.bin""
GOCACHE=""/home/myitcv/.cache/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/myitcv/gostuff""
GOPROXY=""""
GORACE=""""
GOROOT=""/home/myitcv/gos""
GOTMPDIR=""""
GOTOOLDIR=""/home/myitcv/gos/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/myitcv/gostuff/src/github.com/myitcv/govim/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build709084862=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

Call `textDocument/formatting` to format the following:

```go
package govim

const ( x = 5
)
```

### What did you expect to see?

A `[]TextEdit` result that only contains non-zero-effect deltas.

### What did you see instead?

A `[]TextEdit` result that contained one zero-effect delta:

```
[]protocol.TextEdit{
    {
        Range: protocol.Range{
            Start: protocol.Position{Line:2, Character:0},
            End:   protocol.Position{Line:3, Character:0},
        },
        NewText: """",
    },
    {
        Range: protocol.Range{
            Start: protocol.Position{Line:3, Character:0},
            End:   protocol.Position{Line:4, Character:0},
        },
        NewText: """",
    },
    {
        Range: protocol.Range{
            Start: protocol.Position{Line:4, Character:0},
            End:   protocol.Position{Line:4, Character:0},
        },
        NewText: ""const (\n"",
    },
    {
        Range: protocol.Range{
            Start: protocol.Position{Line:4, Character:0},
            End:   protocol.Position{Line:4, Character:0},
        },
        NewText: ""\tx = 5\n"",
    },
    {
        Range: protocol.Range{
            Start: protocol.Position{Line:4, Character:0},
            End:   protocol.Position{Line:4, Character:0},
        },
        NewText: "")\n"",
    },
    {
        Range: protocol.Range{
            Start: protocol.Position{Line:4, Character:0},
            End:   protocol.Position{Line:4, Character:0},
        },
        NewText: """",
    },
}
```

The last `TextEdit` implies zero delta.

cc @stamblerre 
",1,x tools cmd gopls  zero effect deltas returned in response to textdocument formatting            what version of go are you using   go version            go version  go version       linux      go list  m golang org x tools  golang org x tools                     does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env          go env  output       go env  goarch      gobin   home myitcv gostuff src github com myitcv govim  bin   gocache   home myitcv  cache go build   goexe     goflags     gohostarch      gohostos  linux   goos  linux   gopath   home myitcv gostuff   goproxy     gorace     goroot   home myitcv gos   gotmpdir     gotooldir   home myitcv gos pkg tool linux     gccgo  gccgo   cc  gcc   cxx  g     cgo enabled      gomod   home myitcv gostuff src github com myitcv govim go mod   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches             what did you do     call  textdocument formatting  to format the following        go  package govim    const   x                    what did you expect to see     a   textedit  result that only contains non zero effect deltas         what did you see instead     a   textedit  result that contained one zero effect delta           protocol textedit                  range  protocol range               start  protocol position line    character                  end    protocol position line    character                          newtext                              range  protocol range               start  protocol position line    character                  end    protocol position line    character                          newtext                              range  protocol range               start  protocol position line    character                  end    protocol position line    character                          newtext   const   n                           range  protocol range               start  protocol position line    character                  end    protocol position line    character                          newtext    tx     n                           range  protocol range               start  protocol position line    character                  end    protocol position line    character                          newtext     n                           range  protocol range               start  protocol position line    character                  end    protocol position line    character                          newtext                         the last  textedit  implies zero delta     cc  stamblerre   ,1
133123,12532366536.0,IssuesEvent,2020-06-04 15:50:50,golang/go,https://api.github.com/repos/golang/go,closed,go.dev: Missing documentation and misleading link on godoc.org,Documentation go.dev,"
### What is the URL of the page with the issue?
 
https://pkg.go.dev/golang.org/x/vgo/vendor/cmd/go/internal/modfile
  
### What did you do?
 
Open https://godoc.org/golang.org/x/vgo/vendor/cmd/go/internal/modfile
which says I should check out https://pkg.go.dev/golang.org/x/vgo/vendor/cmd/go/internal/modfile
 
### What did you expect to see?
 
Documentation of golang.org/x/vgo/vendor/cmd/go/internal/modfile
 
### What did you see instead?

![image](https://user-images.githubusercontent.com/653777/80304753-636c5e00-87b8-11ea-8214-a52667644bf7.png)

**404 Not Found**
",1.0,"go.dev: Missing documentation and misleading link on godoc.org - 
### What is the URL of the page with the issue?
 
https://pkg.go.dev/golang.org/x/vgo/vendor/cmd/go/internal/modfile
  
### What did you do?
 
Open https://godoc.org/golang.org/x/vgo/vendor/cmd/go/internal/modfile
which says I should check out https://pkg.go.dev/golang.org/x/vgo/vendor/cmd/go/internal/modfile
 
### What did you expect to see?
 
Documentation of golang.org/x/vgo/vendor/cmd/go/internal/modfile
 
### What did you see instead?

![image](https://user-images.githubusercontent.com/653777/80304753-636c5e00-87b8-11ea-8214-a52667644bf7.png)

**404 Not Found**
",1,go dev  missing documentation and misleading link on godoc org         what is the url of the page with the issue                 what did you do      open    which says i should check out           what did you expect to see      documentation of golang org x vgo vendor cmd go internal modfile         what did you see instead                 not found    ,1
346122,30868470897.0,IssuesEvent,2023-08-03 09:39:57,pytorch/pytorch,https://api.github.com/repos/pytorch/pytorch,opened,DISABLED test_batchnorm_nhwc_cpu (__main__.TestNN),module: nn triaged module: flaky-tests skipped,"Platforms: linux, mac, macos

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_batchnorm_nhwc_cpu&suite=TestNN) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/15574080336).

Over the past 3 hours, it has been determined flaky in 6 workflow(s) with 18 failures and 6 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_batchnorm_nhwc_cpu`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


Test file path: `test_nn.py`",1.0,"DISABLED test_batchnorm_nhwc_cpu (__main__.TestNN) - Platforms: linux, mac, macos

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_batchnorm_nhwc_cpu&suite=TestNN) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/15574080336).

Over the past 3 hours, it has been determined flaky in 6 workflow(s) with 18 failures and 6 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_batchnorm_nhwc_cpu`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


Test file path: `test_nn.py`",0,disabled test batchnorm nhwc cpu    main   testnn    platforms  linux  mac  macos  this test was disabled because it is failing in ci  see     and the most recent trunk      over the past   hours  it has been determined flaky in   workflow s  with   failures and   successes     debugging instructions  after clicking on the recent samples link     do not assume things are okay if the ci is green  we now shield flaky tests from developers so ci will thus be green but it will be harder to parse the logs  to find relevant log snippets     click on the workflow logs linked above    click on the test step of the job so that it is expanded  otherwise  the grepping will not work     grep for  test batchnorm nhwc cpu     there should be several instances run  as flaky tests are rerun in ci  from which you can study the logs    test file path   test nn py ,0
13551,3738856939.0,IssuesEvent,2016-03-09 00:53:05,golang/go,https://api.github.com/repos/golang/go,closed,website: https://golang.org/doc/contribute.html uses old Gerrit link,Documentation,"https://golang.org/doc/contribute.html, https://github.com/golang/go/blob/master/CONTRIBUTING.md, and https://github.com/golang/go/blob/master/doc/contribute.html link to https://code.google.com/p/gerrit/.
It's not a big deal for the first and third link, but https://github.com/golang/go/blob/master/CONTRIBUTING.md doesn't link to Google's Gerrit instance at all.",1.0,"website: https://golang.org/doc/contribute.html uses old Gerrit link - https://golang.org/doc/contribute.html, https://github.com/golang/go/blob/master/CONTRIBUTING.md, and https://github.com/golang/go/blob/master/doc/contribute.html link to https://code.google.com/p/gerrit/.
It's not a big deal for the first and third link, but https://github.com/golang/go/blob/master/CONTRIBUTING.md doesn't link to Google's Gerrit instance at all.",1,website    uses old gerrit link       and   link to    it s not a big deal for the first and third link  but   doesn t link to google s gerrit instance at all ,1
399825,27257367447.0,IssuesEvent,2023-02-22 12:33:22,golang/go,https://api.github.com/repos/golang/go,opened,crypto: document that GenerateKey functions are not deterministic,Documentation NeedsFix,"In Go 1.20 we finally made crypto/ecdsa.GenerateKey call MaybeReadByte, so that now all GenerateKey implementation are non-deterministic, avoiding applications relying on the internals of our implementation, which would stop us from ever changing them. We should document this.",1.0,"crypto: document that GenerateKey functions are not deterministic - In Go 1.20 we finally made crypto/ecdsa.GenerateKey call MaybeReadByte, so that now all GenerateKey implementation are non-deterministic, avoiding applications relying on the internals of our implementation, which would stop us from ever changing them. We should document this.",1,crypto  document that generatekey functions are not deterministic   in go     we finally made crypto ecdsa generatekey call maybereadbyte  so that now all generatekey implementation are non deterministic  avoiding applications relying on the internals of our implementation  which would stop us from ever changing them  we should document this ,1
146204,13173730659.0,IssuesEvent,2020-08-11 20:53:48,golang/go,https://api.github.com/repos/golang/go,closed,doc: write Go 1.15 release notes,Documentation NeedsFix help wanted recurring release-blocker,"Tracking bug for writing the Go 1.15 Release Notes.

The latest state on tip can be viewed at https://tip.golang.org/doc/go1.15.

Previously #36878, #17929, #15810, #5929, etc.",1.0,"doc: write Go 1.15 release notes - Tracking bug for writing the Go 1.15 Release Notes.

The latest state on tip can be viewed at https://tip.golang.org/doc/go1.15.

Previously #36878, #17929, #15810, #5929, etc.",1,doc  write go     release notes   tracking bug for writing the go     release notes     the latest state on tip can be viewed at      previously                 etc ,1
308998,9459927578.0,IssuesEvent,2019-04-17 09:40:39,metasfresh/metasfresh-webui-frontend,https://api.github.com/repos/metasfresh/metasfresh-webui-frontend,closed,"View: after calling getByIds, frontend shall remove the rows which are no longer in the result",branch:master branch:release priority:high type:enhancement,"### Is this a bug or feature request?
bug/FR

### What is the current behavior?

#### Which are the steps to reproduce?
Let's consider following test case: https://w101.metasfresh.com:8443/window/247.
(NOTE: i've picked this window because it's easy to create / delete rows)
* create some new record
* open https://w101.metasfresh.com:8443/window/247 in 2 browser tabs
* in one of them, delete one of the records.
* check the other tab:
** it gets the websocket notification about that row which was changed/deleted => OK
** queries the backend about it => OK
** the backed returns an empty array => OK
** frontend does not kick out that row from the list => NOK
![image](https://user-images.githubusercontent.com/1244701/54903784-5f9b4780-4ee5-11e9-8742-be4a4124ed5f.png)


### What is the expected or desired behavior?
Frontend shall remove all those rows which were not returned back by getByIds API call.

",1.0,"View: after calling getByIds, frontend shall remove the rows which are no longer in the result - ### Is this a bug or feature request?
bug/FR

### What is the current behavior?

#### Which are the steps to reproduce?
Let's consider following test case: https://w101.metasfresh.com:8443/window/247.
(NOTE: i've picked this window because it's easy to create / delete rows)
* create some new record
* open https://w101.metasfresh.com:8443/window/247 in 2 browser tabs
* in one of them, delete one of the records.
* check the other tab:
** it gets the websocket notification about that row which was changed/deleted => OK
** queries the backend about it => OK
** the backed returns an empty array => OK
** frontend does not kick out that row from the list => NOK
![image](https://user-images.githubusercontent.com/1244701/54903784-5f9b4780-4ee5-11e9-8742-be4a4124ed5f.png)


### What is the expected or desired behavior?
Frontend shall remove all those rows which were not returned back by getByIds API call.

",0,view  after calling getbyids  frontend shall remove the rows which are no longer in the result       is this a bug or feature request   bug fr        what is the current behavior          which are the steps to reproduce   let s consider following test case      note  i ve picked this window because it s easy to create   delete rows     create some new record    open   in   browser tabs    in one of them  delete one of the records     check the other tab      it gets the websocket notification about that row which was changed deleted    ok     queries the backend about it    ok     the backed returns an empty array    ok     frontend does not kick out that row from the list    nok                what is the expected or desired behavior   frontend shall remove all those rows which were not returned back by getbyids api call     ,0
370179,25892541239.0,IssuesEvent,2022-12-14 19:14:25,golang/go,https://api.github.com/repos/golang/go,closed,spec: document that recursive type declarations through type parameters are not permitted,Documentation,"Here's a type:
```go
type Rec[type T Rec[T]] interface{ r(T) }
```

Currently `go2go` complains with confusing errors; the first declaration fails with `Rec is not a generic type` (it obviously is) and the equivalent `type Rec[type T Rec] interface{ r(T) }` fails with `Rec is not an interface` (it also obviously is).

I assume this shouldn't be allowed: to know if `Rec[T]` is a valid type for `T` to implement, we need to know if `T` implements `Rec[T]`, which is circular.  But I can't find anything in the draft design that would prohibit it.

([playground for convenience](https://go2goplay.golang.org/p/TsopGuR9oFR))",1.0,"spec: document that recursive type declarations through type parameters are not permitted - Here's a type:
```go
type Rec[type T Rec[T]] interface{ r(T) }
```

Currently `go2go` complains with confusing errors; the first declaration fails with `Rec is not a generic type` (it obviously is) and the equivalent `type Rec[type T Rec] interface{ r(T) }` fails with `Rec is not an interface` (it also obviously is).

I assume this shouldn't be allowed: to know if `Rec[T]` is a valid type for `T` to implement, we need to know if `T` implements `Rec[T]`, which is circular.  But I can't find anything in the draft design that would prohibit it.

([playground for convenience](https://go2goplay.golang.org/p/TsopGuR9oFR))",1,spec  document that recursive type declarations through type parameters are not permitted   here s a type      go  type rec   interface  r t            currently     complains with confusing errors  the first declaration fails with  rec is not a generic type   it obviously is  and the equivalent  type rec  interface  r t     fails with  rec is not an interface   it also obviously is      i assume this shouldn t be allowed  to know if  rec   is a valid type for  t  to implement  we need to know if  t  implements  rec    which is circular   but i can t find anything in the draft design that would prohibit it         ,1
58625,11900667883.0,IssuesEvent,2020-03-30 11:04:24,appsody/appsody,https://api.github.com/repos/appsody/appsody,closed,Let APPSODY_MOUNT_HOME to override with named docker volume,external/codewind priority/medium,"**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

I recall that appsody exposed the `APPSODY_MOUNT_HOME` env variable for Codewind to use, primarily for mounting the local system's m2 cache when running `appsody` inside of Codewind's container. 

However, Codewind currently no longer does this, as it was deemed that mounting the m2 cache is inherently unsafe (there are some details in this [issue](https://github.com/eclipse/codewind/issues/583))

This means for stacks that require m2 cache, when used in Codewind there's no caching of dependencies at all (since such stacks typically don't set `APPSODY_DEPS` either).  This leads to 2 problems:

1. Dependencies need to be downloaded each time the application starts (https://github.com/eclipse/codewind/issues/583) 
2. Users will have problems working on projects based on these stacks in air-gap/offline scenarios

**Describe the solution you'd like**
A clear and concise description of what you want to happen.

Would like to repurpose/enhance the `APPSODY_MOUNT_HOME` mechanism so we can use it to specify a named docker volume to cache the dependencies

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.
",1.0,"Let APPSODY_MOUNT_HOME to override with named docker volume - **Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

I recall that appsody exposed the `APPSODY_MOUNT_HOME` env variable for Codewind to use, primarily for mounting the local system's m2 cache when running `appsody` inside of Codewind's container. 

However, Codewind currently no longer does this, as it was deemed that mounting the m2 cache is inherently unsafe (there are some details in this [issue](https://github.com/eclipse/codewind/issues/583))

This means for stacks that require m2 cache, when used in Codewind there's no caching of dependencies at all (since such stacks typically don't set `APPSODY_DEPS` either).  This leads to 2 problems:

1. Dependencies need to be downloaded each time the application starts (https://github.com/eclipse/codewind/issues/583) 
2. Users will have problems working on projects based on these stacks in air-gap/offline scenarios

**Describe the solution you'd like**
A clear and concise description of what you want to happen.

Would like to repurpose/enhance the `APPSODY_MOUNT_HOME` mechanism so we can use it to specify a named docker volume to cache the dependencies

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.
",0,let appsody mount home to override with named docker volume     is your feature request related to a problem  please describe     a clear and concise description of what the problem is  ex  i m always frustrated when      i recall that appsody exposed the  appsody mount home  env variable for codewind to use  primarily for mounting the local system s   cache when running  appsody  inside of codewind s container      however  codewind currently no longer does this  as it was deemed that mounting the   cache is inherently unsafe  there are some details in this        this means for stacks that require   cache  when used in codewind there s no caching of dependencies at all  since such stacks typically don t set  appsody deps  either    this leads to   problems        dependencies need to be downloaded each time the application starts         users will have problems working on projects based on these stacks in air gap offline scenarios      describe the solution you d like    a clear and concise description of what you want to happen     would like to repurpose enhance the  appsody mount home  mechanism so we can use it to specify a named docker volume to cache the dependencies      describe alternatives you ve considered    a clear and concise description of any alternative solutions or features you ve considered       additional context    add any other context or screenshots about the feature request here   ,0
399607,27247588425.0,IssuesEvent,2023-02-22 04:16:36,golang/go,https://api.github.com/repos/golang/go,closed,"spec: unable to create constraint based upon type parameter: ""type in term ~T cannot be a type parameter""",Documentation,"<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?
<pre>
https://go.dev/play/p/Ztyu2FJaajl
go1.20.1
</pre>

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
Go Playground server

### What did you do?
```go
package main

type A[T any, U ~T] struct{}
type B[T any, U ~T | ~*T] struct{}
type C[T any] interface{ ~T | ~*T }

func main() {}
```

### What did you expect to see?
no error

### What did you see instead?
```
./prog.go:3:18: type in term ~T cannot be a type parameter
./prog.go:4:18: type in term ~T cannot be a type parameter
./prog.go:5:27: type in term ~T cannot be a type parameter

Go build failed.
```

Too bad Google isn't using numbered sections in the Go spec, that would make it easier to cite precise specification items.

So constraints are interfaces and implicitly converted to them using the syntax of the first four examples. The spec states that ""An interface type <code>T</code> may not embed a type element that is, contains, or embeds <code>T</code>, directly or indirectly."" However, we're specifying a type with T as an underlying type. If I read the specification correctly then this should be legal.

It's probably a separate issue with the specification that a constraint of `type A[T any, U T | *T] struct{}` is not legal.",1.0,"spec: unable to create constraint based upon type parameter: ""type in term ~T cannot be a type parameter"" - <!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?
<pre>
https://go.dev/play/p/Ztyu2FJaajl
go1.20.1
</pre>

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
Go Playground server

### What did you do?
```go
package main

type A[T any, U ~T] struct{}
type B[T any, U ~T | ~*T] struct{}
type C[T any] interface{ ~T | ~*T }

func main() {}
```

### What did you expect to see?
no error

### What did you see instead?
```
./prog.go:3:18: type in term ~T cannot be a type parameter
./prog.go:4:18: type in term ~T cannot be a type parameter
./prog.go:5:27: type in term ~T cannot be a type parameter

Go build failed.
```

Too bad Google isn't using numbered sections in the Go spec, that would make it easier to cite precise specification items.

So constraints are interfaces and implicitly converted to them using the syntax of the first four examples. The spec states that ""An interface type <code>T</code> may not embed a type element that is, contains, or embeds <code>T</code>, directly or indirectly."" However, we're specifying a type with T as an underlying type. If I read the specification correctly then this should be legal.

It's probably a separate issue with the specification that a constraint of `type A[T any, U T | *T] struct{}` is not legal.",1,spec  unable to create constraint based upon type parameter   type in term  t cannot be a type parameter          please answer these questions before submitting your issue  thanks              what version of go are you using   go version                           does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env     go playground server        what did you do      go  package main    type a  struct    type b  struct    type c  interface   t     t      func main                  what did you expect to see   no error        what did you see instead          prog go      type in term  t cannot be a type parameter    prog go      type in term  t cannot be a type parameter    prog go      type in term  t cannot be a type parameter    go build failed          too bad google isn t using numbered sections in the go spec  that would make it easier to cite precise specification items     so constraints are interfaces and implicitly converted to them using the syntax of the first four examples  the spec states that  an interface type  t  may not embed a type element that is  contains  or embeds  t   directly or indirectly   however  we re specifying a type with t as an underlying type  if i read the specification correctly then this should be legal     it s probably a separate issue with the specification that a constraint of  type a  struct    is not legal ,1
36234,6521145108.0,IssuesEvent,2017-08-28 19:22:22,golang/go,https://api.github.com/repos/golang/go,closed,net/http: update docs for LocalAddrContextKey,Documentation,"### What version of Go are you using (`go version`)?
1.9

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?
amd64

### What did you do?

r is a *http.Request
r.Context().Value(http.LocalAddrContextKey)


### What did you expect to see?
Listener Addr

### What did you see instead?
Connection Local Addr

I replied to an older closed issue, I'm not sure if it will be seen or not so I am posting again: https://github.com/golang/go/issues/18686
It seems that the functionality of LocalAddrContextKey has changed to what it was possibly intended to do, if so it should be mentioned in the patch notes

source change: https://go-review.googlesource.com/c/go/+/35490/10/src/net/http/server.go",1.0,"net/http: update docs for LocalAddrContextKey - ### What version of Go are you using (`go version`)?
1.9

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?
amd64

### What did you do?

r is a *http.Request
r.Context().Value(http.LocalAddrContextKey)


### What did you expect to see?
Listener Addr

### What did you see instead?
Connection Local Addr

I replied to an older closed issue, I'm not sure if it will be seen or not so I am posting again: https://github.com/golang/go/issues/18686
It seems that the functionality of LocalAddrContextKey has changed to what it was possibly intended to do, if so it should be mentioned in the patch notes

source change: https://go-review.googlesource.com/c/go/+/35490/10/src/net/http/server.go",1,net http  update docs for localaddrcontextkey       what version of go are you using   go version                does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env              what did you do     r is a  http request  r context   value http localaddrcontextkey           what did you expect to see   listener addr        what did you see instead   connection local addr    i replied to an older closed issue  i m not sure if it will be seen or not so i am posting again     it seems that the functionality of localaddrcontextkey has changed to what it was possibly intended to do  if so it should be mentioned in the patch notes    source change   ,1
2462,5196267402.0,IssuesEvent,2017-01-23 12:13:56,JoryHogeveen/view-admin-as,https://api.github.com/repos/JoryHogeveen/view-admin-as,closed,Also change the current user object properties on a view,compatibility enhancement,"Currently I only use capability mapping for the role and capability views.

- [x] update the current user roles property (only on a role view)
- [x] update the current user caps property
- [x] update the current user allcaps property
- [x] compatibility with blog switching (caused the original values to reset)

Only for capability and role views + add a filter for modules to hook into.",True,"Also change the current user object properties on a view - Currently I only use capability mapping for the role and capability views.

- [x] update the current user roles property (only on a role view)
- [x] update the current user caps property
- [x] update the current user allcaps property
- [x] compatibility with blog switching (caused the original values to reset)

Only for capability and role views + add a filter for modules to hook into.",0,also change the current user object properties on a view   currently i only use capability mapping for the role and capability views         update the current user roles property  only on a role view       update the current user caps property      update the current user allcaps property      compatibility with blog switching  caused the original values to reset     only for capability and role views   add a filter for modules to hook into ,0
35945,6515005389.0,IssuesEvent,2017-08-26 09:21:11,golang/go,https://api.github.com/repos/golang/go,closed,website: Command Documentation,Documentation,"Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
konstantin@debian:~$ go version
go version go1.8.3 linux/amd64

### What operating system and processor architecture are you using (`go env`)?
debian

### What did you do?

Read documentation on web site https://golang.org/doc/cmd

### What did you expect to see?

Not clear organization of ""command"":
* some ...
* full command reference

### What did you see instead?

Merge 2 list of commands to one solid list, like we see in page https://golang.org/pkg/ for packages and . Preliminary :
* go                | Descriptions for go
    * go commands | Descriptions for go commands
    * go build | Descriptions for go build
    * go clean | Descriptions for go clean
...

But I want to clarify some points:
1. If we open link **go** on page https://golang.org/doc/cmd, then we will see big good information about **go doc**. But, If we open on link **full command reference** https://golang.org/doc/cmd, after that link **doc** - then we see short information.
2. On page https://golang.org/doc/cmd link **cover** ---> result documentation from X tools. But on page https://golang.org/cmd/ link **cover** ---> result looks nice.

Please separate page https://golang.org/cmd/go/ to single small parts.

### The reason

Simple organization of documents is clear and easy to translate.
",1.0,"website: Command Documentation - Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
konstantin@debian:~$ go version
go version go1.8.3 linux/amd64

### What operating system and processor architecture are you using (`go env`)?
debian

### What did you do?

Read documentation on web site https://golang.org/doc/cmd

### What did you expect to see?

Not clear organization of ""command"":
* some ...
* full command reference

### What did you see instead?

Merge 2 list of commands to one solid list, like we see in page https://golang.org/pkg/ for packages and . Preliminary :
* go                | Descriptions for go
    * go commands | Descriptions for go commands
    * go build | Descriptions for go build
    * go clean | Descriptions for go clean
...

But I want to clarify some points:
1. If we open link **go** on page https://golang.org/doc/cmd, then we will see big good information about **go doc**. But, If we open on link **full command reference** https://golang.org/doc/cmd, after that link **doc** - then we see short information.
2. On page https://golang.org/doc/cmd link **cover** ---> result documentation from X tools. But on page https://golang.org/cmd/ link **cover** ---> result looks nice.

Please separate page https://golang.org/cmd/go/ to single small parts.

### The reason

Simple organization of documents is clear and easy to translate.
",1,website  command documentation   please answer these questions before submitting your issue  thanks         what version of go are you using   go version     konstantin debian    go version  go version       linux          what operating system and processor architecture are you using   go env     debian        what did you do     read documentation on web site          what did you expect to see     not clear organization of  command      some        full command reference        what did you see instead     merge   list of commands to one solid list  like we see in page   for packages and   preliminary      go                  descriptions for go        go commands   descriptions for go commands        go build   descriptions for go build        go clean   descriptions for go clean         but i want to clarify some points      if we open link   go   on page   then we will see big good information about   go doc    but  if we open on link   full command reference     after that link   doc     then we see short information      on page   link   cover        result documentation from x tools  but on page   link   cover        result looks nice     please separate page   to single small parts         the reason    simple organization of documents is clear and easy to translate   ,1
421490,28321443287.0,IssuesEvent,2023-04-11 01:46:24,golang/go,https://api.github.com/repos/golang/go,closed,"spec: typo ""are"" -> ""or"" in Core types",Documentation NeedsFix,"<!--
Please answer these questions before submitting your issue. Thanks!
-->
 
### What is the URL of the page with the issue?
 
https://go.dev/ref/spec#Core_types
 
### What is your user agent?
 
<!-- 
You can find your user agent here:
https://www.whatismybrowser.com/detect/what-is-my-user-agent
-->
 
Safari 16.5
 
### Screenshot
 
<!--
Please paste a screenshot of the page.
-->
 
<img width=""887"" alt=""image"" src=""https://user-images.githubusercontent.com/4759874/230736927-7847dd32-c599-426b-aa52-f237edfa3b70.png"">
 
### What did you do?
 
<!--
If possible, provide a recipe for reproducing the error.
-->
 
 
 
### What did you expect to see?

The conjunction ""or""

""to declare variables or compose other types"" in the bytestring discussion under ""Core Types""
 
Note that bytestring is not a real type; it cannot be used to declare variables or compose other types. It exists solely to describe the behavior of some operations that read from a sequence of bytes, which may be a byte slice or a string.
 
### What did you see instead?

The verb ""are""

""to declare variables are compose other types""

Note that bytestring is not a real type; it cannot be used to declare variables are compose other types. It exists solely to describe the behavior of some operations that read from a sequence of bytes, which may be a byte slice or a string.



",1.0,"spec: typo ""are"" -> ""or"" in Core types - <!--
Please answer these questions before submitting your issue. Thanks!
-->
 
### What is the URL of the page with the issue?
 
https://go.dev/ref/spec#Core_types
 
### What is your user agent?
 
<!-- 
You can find your user agent here:
https://www.whatismybrowser.com/detect/what-is-my-user-agent
-->
 
Safari 16.5
 
### Screenshot
 
<!--
Please paste a screenshot of the page.
-->
 
<img width=""887"" alt=""image"" src=""https://user-images.githubusercontent.com/4759874/230736927-7847dd32-c599-426b-aa52-f237edfa3b70.png"">
 
### What did you do?
 
<!--
If possible, provide a recipe for reproducing the error.
-->
 
 
 
### What did you expect to see?

The conjunction ""or""

""to declare variables or compose other types"" in the bytestring discussion under ""Core Types""
 
Note that bytestring is not a real type; it cannot be used to declare variables or compose other types. It exists solely to describe the behavior of some operations that read from a sequence of bytes, which may be a byte slice or a string.
 
### What did you see instead?

The verb ""are""

""to declare variables are compose other types""

Note that bytestring is not a real type; it cannot be used to declare variables are compose other types. It exists solely to describe the behavior of some operations that read from a sequence of bytes, which may be a byte slice or a string.



",1,spec  typo  are      or  in core types         please answer these questions before submitting your issue  thanks               what is the url of the page with the issue                what is your user agent             you can find your user agent here              safari             screenshot           please paste a screenshot of the page            img width     alt  image  src            what did you do            if possible  provide a recipe for reproducing the error                     what did you expect to see     the conjunction  or      to declare variables or compose other types  in the bytestring discussion under  core types      note that bytestring is not a real type  it cannot be used to declare variables or compose other types  it exists solely to describe the behavior of some operations that read from a sequence of bytes  which may be a byte slice or a string          what did you see instead     the verb  are      to declare variables are compose other types     note that bytestring is not a real type  it cannot be used to declare variables are compose other types  it exists solely to describe the behavior of some operations that read from a sequence of bytes  which may be a byte slice or a string         ,1
127472,27051780856.0,IssuesEvent,2023-02-13 13:45:03,Azure/autorest.typescript,https://api.github.com/repos/Azure/autorest.typescript,closed,[RLC] Support the top-level shortcut both in Cadl and Swagger,Client RLC DPG/RLC Backlog Epic: Coordinate Client Customizations WS: Code Generation,"If there is no top-level operation group defined in Cadl or Swagger we will fail to generate RLC SDK, we need to fix it to support this case.",1.0,"[RLC] Support the top-level shortcut both in Cadl and Swagger - If there is no top-level operation group defined in Cadl or Swagger we will fail to generate RLC SDK, we need to fix it to support this case.",0,  support the top level shortcut both in cadl and swagger   if there is no top level operation group defined in cadl or swagger we will fail to generate rlc sdk  we need to fix it to support this case ,0
185835,21844835280.0,IssuesEvent,2022-05-18 02:56:39,project-chip/connectedhomeip,https://api.github.com/repos/project-chip/connectedhomeip,closed,`SetDeviceAttestationVerifier` prevents clean multiple concurrent usage of AutoCommissioner,V1.0 security commissioning," #### Problem
In case of attempting to commission multiple nodes on same fabric, the global singleton set/gotten by  `SetDeviceAttestationVerifier`/`GetDeviceAttestationVerifier` is not sufficient as the statefullness of it (especially if doing async operations) cannot be managed with the correct context for a given commissioning.

It should be possible to override the `DeviceAttestationVerifier` per commissioning attempt, similar to other commissioning parameters.

 #### Proposed Solution
- Add an optional override to `CommissioningParameters` for DeviceAttestationVerifier, and ensure that if not set, it uses verifier set by SetDeviceAttestationVerifier
",True,"`SetDeviceAttestationVerifier` prevents clean multiple concurrent usage of AutoCommissioner -  #### Problem
In case of attempting to commission multiple nodes on same fabric, the global singleton set/gotten by  `SetDeviceAttestationVerifier`/`GetDeviceAttestationVerifier` is not sufficient as the statefullness of it (especially if doing async operations) cannot be managed with the correct context for a given commissioning.

It should be possible to override the `DeviceAttestationVerifier` per commissioning attempt, similar to other commissioning parameters.

 #### Proposed Solution
- Add an optional override to `CommissioningParameters` for DeviceAttestationVerifier, and ensure that if not set, it uses verifier set by SetDeviceAttestationVerifier
",0, setdeviceattestationverifier  prevents clean multiple concurrent usage of autocommissioner         problem  in case of attempting to commission multiple nodes on same fabric  the global singleton set gotten by   setdeviceattestationverifier   getdeviceattestationverifier  is not sufficient as the statefullness of it  especially if doing async operations  cannot be managed with the correct context for a given commissioning     it should be possible to override the  deviceattestationverifier  per commissioning attempt  similar to other commissioning parameters           proposed solution    add an optional override to  commissioningparameters  for deviceattestationverifier  and ensure that if not set  it uses verifier set by setdeviceattestationverifier  ,0
484187,13935827502.0,IssuesEvent,2020-10-22 12:06:50,RasaHQ/rasa,https://api.github.com/repos/RasaHQ/rasa,closed,Setting slots before conversation starts leads to empty bot responses,area:rasa-oss :ferris_wheel: priority:normal type:bug :bug:,"<!-- THIS INFORMATION IS MANDATORY - YOUR ISSUE WILL BE CLOSED IF IT IS MISSING. If you don't know your Rasa version, use `rasa --version`. 
Please format any code or console output with three ticks ``` above and below.
If you are asking a usage question (e.g. ""How do I do xyz"") please post your question on https://forum.rasa.com instead -->

**Rasa version**: 2.0.0rc1

**Python version**: 3.7.8

**Operating system** (windows, osx, ...): osx

**Issue**: Settings lots via the API for a new conversation ID leads to an empty bot response after the first regular user message. The issue was first reported here: https://forum.rasa.com/t/api-unexpected-behavior-bug/33400",1.0,"Setting slots before conversation starts leads to empty bot responses - <!-- THIS INFORMATION IS MANDATORY - YOUR ISSUE WILL BE CLOSED IF IT IS MISSING. If you don't know your Rasa version, use `rasa --version`. 
Please format any code or console output with three ticks ``` above and below.
If you are asking a usage question (e.g. ""How do I do xyz"") please post your question on https://forum.rasa.com instead -->

**Rasa version**: 2.0.0rc1

**Python version**: 3.7.8

**Operating system** (windows, osx, ...): osx

**Issue**: Settings lots via the API for a new conversation ID leads to an empty bot response after the first regular user message. The issue was first reported here: https://forum.rasa.com/t/api-unexpected-behavior-bug/33400",0,setting slots before conversation starts leads to empty bot responses        this information is mandatory   your issue will be closed if it is missing  if you don t know your rasa version  use  rasa   version     please format any code or console output with three ticks     above and below   if you are asking a usage question  e g   how do i do xyz   please post your question on   instead          rasa version               python version               operating system    windows  osx        osx      issue    settings lots via the api for a new conversation id leads to an empty bot response after the first regular user message  the issue was first reported here   ,0
15048,3921626275.0,IssuesEvent,2016-04-22 00:14:54,golang/go,https://api.github.com/repos/golang/go,closed,encoding/gob: document gob format compatibility promise ,Documentation,"Using ```go1.5```.

The ```encoding/gob``` package does a fair job at describing the underlying gob format as it appears on the wire. However, it makes no explicit statements about the stability of the format *across* different versions of Go. For example, will a gob output from ```go1.5``` still be decodable by a hypothetical future ```go1.8```? 

The docstring for the ```GobEncoder``` type, seems to indicate that this is true given the fact that gobs can be stored:
> Note: Since gobs can be stored permanently, It is good design to guarantee the encoding used by a GobEncoder is stable as the software evolves. For instance, it might make sense for GobEncode to include a version number in the encoding.

However, the fact that gobs can be stored permanently is mentioned nowhere else in the package documentation, except for the linked blog post. (In fact, most of package refers to gobs as a data interchange format to be sent over the network, rather than as a format that is suitable for disk storage.)

Can the format compatibility promise be more explicit? Perhaps in the Overview section of the package documentation? Obviously, this promise can only be kept if custom GobEncoder and BinaryMarshaler implementations remain stable. However, a promise could be made for types that do not implement those interfaces.",1.0,"encoding/gob: document gob format compatibility promise  - Using ```go1.5```.

The ```encoding/gob``` package does a fair job at describing the underlying gob format as it appears on the wire. However, it makes no explicit statements about the stability of the format *across* different versions of Go. For example, will a gob output from ```go1.5``` still be decodable by a hypothetical future ```go1.8```? 

The docstring for the ```GobEncoder``` type, seems to indicate that this is true given the fact that gobs can be stored:
> Note: Since gobs can be stored permanently, It is good design to guarantee the encoding used by a GobEncoder is stable as the software evolves. For instance, it might make sense for GobEncode to include a version number in the encoding.

However, the fact that gobs can be stored permanently is mentioned nowhere else in the package documentation, except for the linked blog post. (In fact, most of package refers to gobs as a data interchange format to be sent over the network, rather than as a format that is suitable for disk storage.)

Can the format compatibility promise be more explicit? Perhaps in the Overview section of the package documentation? Obviously, this promise can only be kept if custom GobEncoder and BinaryMarshaler implementations remain stable. However, a promise could be made for types that do not implement those interfaces.",1,encoding gob  document gob format compatibility promise    using               the    encoding gob    package does a fair job at describing the underlying gob format as it appears on the wire  however  it makes no explicit statements about the stability of the format  across  different versions of go  for example  will a gob output from           still be decodable by a hypothetical future                the docstring for the    gobencoder    type  seems to indicate that this is true given the fact that gobs can be stored     note  since gobs can be stored permanently  it is good design to guarantee the encoding used by a gobencoder is stable as the software evolves  for instance  it might make sense for gobencode to include a version number in the encoding     however  the fact that gobs can be stored permanently is mentioned nowhere else in the package documentation  except for the linked blog post   in fact  most of package refers to gobs as a data interchange format to be sent over the network  rather than as a format that is suitable for disk storage      can the format compatibility promise be more explicit  perhaps in the overview section of the package documentation  obviously  this promise can only be kept if custom gobencoder and binarymarshaler implementations remain stable  however  a promise could be made for types that do not implement those interfaces ,1
68393,9172155451.0,IssuesEvent,2019-03-04 05:48:23,golang/go,https://api.github.com/repos/golang/go,closed,encoding/csv: document that Writer is buffered,Documentation NeedsFix,"`csv.Writer` is implemented as a `bufio.Writer`, but this isn't clearly documented.  The only place buffering is mentioned is in the `Writer` example and in the `Flush()` method.  This makes it easy for a user to neglect to flush the underlying buffer and check for an error when writing a CSV, which can result in data loss.  I believe the documentation on `csv.Writer` should clearly state that the implementation is buffered and thus must be flushed.  Here is the current documentation:
  
```
// A Writer writes records to a CSV encoded file.
//
// As returned by NewWriter, a Writer writes records terminated by a
// newline and uses ',' as the field delimiter. The exported fields can be
// changed to customize the details before the first call to Write or WriteAll.
//
// Comma is the field delimiter.
//
// If UseCRLF is true, the Writer ends each output line with \r\n instead of \n.
type Writer struct {
	Comma   rune // Field delimiter (set to ',' by NewWriter)
	UseCRLF bool // True to use \r\n as the line terminator
	w       *bufio.Writer
}
```",1.0,"encoding/csv: document that Writer is buffered - `csv.Writer` is implemented as a `bufio.Writer`, but this isn't clearly documented.  The only place buffering is mentioned is in the `Writer` example and in the `Flush()` method.  This makes it easy for a user to neglect to flush the underlying buffer and check for an error when writing a CSV, which can result in data loss.  I believe the documentation on `csv.Writer` should clearly state that the implementation is buffered and thus must be flushed.  Here is the current documentation:
  
```
// A Writer writes records to a CSV encoded file.
//
// As returned by NewWriter, a Writer writes records terminated by a
// newline and uses ',' as the field delimiter. The exported fields can be
// changed to customize the details before the first call to Write or WriteAll.
//
// Comma is the field delimiter.
//
// If UseCRLF is true, the Writer ends each output line with \r\n instead of \n.
type Writer struct {
	Comma   rune // Field delimiter (set to ',' by NewWriter)
	UseCRLF bool // True to use \r\n as the line terminator
	w       *bufio.Writer
}
```",1,encoding csv  document that writer is buffered    csv writer  is implemented as a  bufio writer   but this isn t clearly documented   the only place buffering is mentioned is in the  writer  example and in the  flush    method   this makes it easy for a user to neglect to flush the underlying buffer and check for an error when writing a csv  which can result in data loss   i believe the documentation on  csv writer  should clearly state that the implementation is buffered and thus must be flushed   here is the current documentation               a writer writes records to a csv encoded file          as returned by newwriter  a writer writes records terminated by a     newline and uses     as the field delimiter  the exported fields can be     changed to customize the details before the first call to write or writeall          comma is the field delimiter          if usecrlf is true  the writer ends each output line with  r n instead of  n   type writer struct    	comma   rune    field delimiter  set to     by newwriter   	usecrlf bool    true to use  r n as the line terminator  	w        bufio writer        ,1
152570,13461104866.0,IssuesEvent,2020-09-09 14:25:20,golang/go,https://api.github.com/repos/golang/go,closed,x/website: ref/mod go.mod section has broken ids,Documentation NeedsInvestigation,"
### What version of Go are you using (`go version`)?

current website

### Does this issue reproduce with the latest release?

repros with https://tip.golang.org/ref/mod

### What operating system and processor architecture are you using (`go env`)?

Google Chrome | 85.0.4183.83

### What did you do?

visit  https://golang.org/ref/mod and click on the `require directive` link in table of contents

### What did you expect to see?

link/jump to ""require directive"" section

`<h3 id=""go.mod-require"" class=""mod-require""><code>require</code> directive</h3>`

### What did you see instead?

link/jump to ""go.mod files"" section

`<h3 id=""go"" class=""mod-require""><code>require</code> directive</h3>`

### additional info

it appears that the entire ""go.mod files"" section has their ids truncated to just `go`",1.0,"x/website: ref/mod go.mod section has broken ids - 
### What version of Go are you using (`go version`)?

current website

### Does this issue reproduce with the latest release?

repros with https://tip.golang.org/ref/mod

### What operating system and processor architecture are you using (`go env`)?

Google Chrome | 85.0.4183.83

### What did you do?

visit  https://golang.org/ref/mod and click on the `require directive` link in table of contents

### What did you expect to see?

link/jump to ""require directive"" section

`<h3 id=""go.mod-require"" class=""mod-require""><code>require</code> directive</h3>`

### What did you see instead?

link/jump to ""go.mod files"" section

`<h3 id=""go"" class=""mod-require""><code>require</code> directive</h3>`

### additional info

it appears that the entire ""go.mod files"" section has their ids truncated to just `go`",1,x website  ref mod go mod section has broken ids         what version of go are you using   go version       current website        does this issue reproduce with the latest release     repros with          what operating system and processor architecture are you using   go env       google chrome                  what did you do     visit    and click on the  require directive  link in table of contents        what did you expect to see     link jump to  require directive  section       require  directive          what did you see instead     link jump to  go mod files  section       require  directive          additional info    it appears that the entire  go mod files  section has their ids truncated to just  go ,1
202794,23104586668.0,IssuesEvent,2022-07-27 07:40:26,elastic/kibana,https://api.github.com/repos/elastic/kibana,opened,[Security Solution] The error message is not displayed for an incorrect PID,bug impact:medium Team: SecuritySolution Team:Onboarding and Lifecycle Mgt v8.4.0,"**Description:**
The error message is not displayed for an incorrect PID. The PID is an integer but relatively long.

**Build Details:**
```
VERSION: 8.4.0
BUILD: 54789
COMMIT: af3a3cba9a7fa3b3e0d2e4766a1db11a5ff4f192
ARTIFACT PAGE: https://artifacts-api.elastic.co/v1/search/8.4.0-SNAPSHOT
```

**Browser Details:**
All

**Preconditions:**
1. Kibana user should be logged in
2. Create a new user without super user privilege and provide access 'all' to the user

**Steps to Reproduce:**
1. Navigate to the Fleet tab under the left-hand side navigation bar
2. Click on the endpoint to which the endpoint security integration is added
3. Click on the endpoint integration
4. Update & save the the changes in the policy
5. Observe the user should be able to update the policy even when the user did not had the super user role privileges

**Impacted Test case:**
N/A

**What's not working:**
The failure message and failure log is also not shown

**Actual Result:**
The error message is not displayed for an incorrect PID

**Expected Result:**
The error message should be displayed for an incorrect PID

**Screenshot:**
![Failure](https://user-images.githubusercontent.com/60252716/181190009-a280fd13-f005-4641-8d86-7349c1438a4a.PNG)
![FAilure123](https://user-images.githubusercontent.com/60252716/181190039-4300a6ed-83fc-4971-9618-369506463b99.PNG)

**Logs:**
N/A",True,"[Security Solution] The error message is not displayed for an incorrect PID - **Description:**
The error message is not displayed for an incorrect PID. The PID is an integer but relatively long.

**Build Details:**
```
VERSION: 8.4.0
BUILD: 54789
COMMIT: af3a3cba9a7fa3b3e0d2e4766a1db11a5ff4f192
ARTIFACT PAGE: https://artifacts-api.elastic.co/v1/search/8.4.0-SNAPSHOT
```

**Browser Details:**
All

**Preconditions:**
1. Kibana user should be logged in
2. Create a new user without super user privilege and provide access 'all' to the user

**Steps to Reproduce:**
1. Navigate to the Fleet tab under the left-hand side navigation bar
2. Click on the endpoint to which the endpoint security integration is added
3. Click on the endpoint integration
4. Update & save the the changes in the policy
5. Observe the user should be able to update the policy even when the user did not had the super user role privileges

**Impacted Test case:**
N/A

**What's not working:**
The failure message and failure log is also not shown

**Actual Result:**
The error message is not displayed for an incorrect PID

**Expected Result:**
The error message should be displayed for an incorrect PID

**Screenshot:**
![Failure](https://user-images.githubusercontent.com/60252716/181190009-a280fd13-f005-4641-8d86-7349c1438a4a.PNG)
![FAilure123](https://user-images.githubusercontent.com/60252716/181190039-4300a6ed-83fc-4971-9618-369506463b99.PNG)

**Logs:**
N/A",0,  the error message is not displayed for an incorrect pid     description     the error message is not displayed for an incorrect pid  the pid is an integer but relatively long       build details          version         build     commit     artifact page              browser details     all      preconditions        kibana user should be logged in     create a new user without super user privilege and provide access  all  to the user      steps to reproduce        navigate to the fleet tab under the left hand side navigation bar     click on the endpoint to which the endpoint security integration is added     click on the endpoint integration     update   save the the changes in the policy     observe the user should be able to update the policy even when the user did not had the super user role privileges      impacted test case     n a      what s not working     the failure message and failure log is also not shown      actual result     the error message is not displayed for an incorrect pid      expected result     the error message should be displayed for an incorrect pid      screenshot                     logs     n a,0
320992,27497339092.0,IssuesEvent,2023-03-05 09:44:30,Slimefun/Slimefun4,https://api.github.com/repos/Slimefun/Slimefun4,opened,Nuclear Reactor randomly stops working.,🐞 Bug Report 🎯 Needs testing,"### ❗ Checklist

- [X] I am using the official english version of Slimefun and did not modify the jar.
- [X] I am using an up to date ""DEV"" (not ""RC"") version of Slimefun.
- [X] I am aware that issues related to Slimefun addons need to be reported on their bug trackers and not here.
- [X] I searched for similar open issues and could not find an existing bug report on this.

### 📍 Description

Issue is that nuclear reactors randomly stops taking any items from acess port and even if you put them manualy into reactor, they will not product anything until you broke them a place them on another spot. Time until they stop working is randomly, sometimes it takes longer.

### 📑 Reproduction Steps

Just place reactor and after some time of production, they will stop working.

### 💡 Expected Behavior

It would be good to fix this, so you do not need them to move them constantly.

### 📷 Screenshots / Videos

_No response_

### 📜 Server Log

_No response_

### 📂 `/error-reports/` folder

_No response_

### 💻 Server Software

Spigot

### 🎮 Minecraft Version

1.19.x

### ⭐ Slimefun version

DEV - 1046

### 🧭 Other plugins

_No response_",1.0,"Nuclear Reactor randomly stops working. - ### ❗ Checklist

- [X] I am using the official english version of Slimefun and did not modify the jar.
- [X] I am using an up to date ""DEV"" (not ""RC"") version of Slimefun.
- [X] I am aware that issues related to Slimefun addons need to be reported on their bug trackers and not here.
- [X] I searched for similar open issues and could not find an existing bug report on this.

### 📍 Description

Issue is that nuclear reactors randomly stops taking any items from acess port and even if you put them manualy into reactor, they will not product anything until you broke them a place them on another spot. Time until they stop working is randomly, sometimes it takes longer.

### 📑 Reproduction Steps

Just place reactor and after some time of production, they will stop working.

### 💡 Expected Behavior

It would be good to fix this, so you do not need them to move them constantly.

### 📷 Screenshots / Videos

_No response_

### 📜 Server Log

_No response_

### 📂 `/error-reports/` folder

_No response_

### 💻 Server Software

Spigot

### 🎮 Minecraft Version

1.19.x

### ⭐ Slimefun version

DEV - 1046

### 🧭 Other plugins

_No response_",0,nuclear reactor randomly stops working        ❗ checklist      i am using the official english version of slimefun and did not modify the jar      i am using an up to date  dev   not  rc   version of slimefun      i am aware that issues related to slimefun addons need to be reported on their bug trackers and not here      i searched for similar open issues and could not find an existing bug report on this       📍 description  issue is that nuclear reactors randomly stops taking any items from acess port and even if you put them manualy into reactor  they will not product anything until you broke them a place them on another spot  time until they stop working is randomly  sometimes it takes longer       📑 reproduction steps  just place reactor and after some time of production  they will stop working       💡 expected behavior  it would be good to fix this  so you do not need them to move them constantly       📷 screenshots   videos   no response       📜 server log   no response       📂   error reports   folder   no response       💻 server software  spigot      🎮 minecraft version      x      ⭐ slimefun version  dev          🧭 other plugins   no response ,0
77750,27144244050.0,IssuesEvent,2023-02-16 18:36:40,hpcc-systems/Tombolo,https://api.github.com/repos/hpcc-systems/Tombolo,opened,Application Tab Random Popup Window,Defect,"In Application tab, as you try to Edit the application details, following window keeps popping up.

![Screen Shot 2023-02-16 at 1 34 32 PM](https://user-images.githubusercontent.com/26062557/219456957-e90d26ee-61d6-4293-a5c9-9144b77b3a06.JPG)
",1.0,"Application Tab Random Popup Window - In Application tab, as you try to Edit the application details, following window keeps popping up.

![Screen Shot 2023-02-16 at 1 34 32 PM](https://user-images.githubusercontent.com/26062557/219456957-e90d26ee-61d6-4293-a5c9-9144b77b3a06.JPG)
",0,application tab random popup window   in application tab  as you try to edit the application details  following window keeps popping up           ,0
81029,10220995730.0,IssuesEvent,2019-08-15 23:26:13,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/gopls: propagate hoverKind to completion,Documentation gopls,"As per #32561 atm, there is a configuration to provide full docs on hover:
```
""gopls"": {
     ""hoverKind"": ""FullDocumentation"",
}
```
However it's not the case when we want docs on completion:
```
""gopls"": {
    ""wantCompletionDocumentation"": true,
}
```
Please make completion return full docs when `FullDocumentation` option is set or add another config for completion.
",1.0,"x/tools/gopls: propagate hoverKind to completion - As per #32561 atm, there is a configuration to provide full docs on hover:
```
""gopls"": {
     ""hoverKind"": ""FullDocumentation"",
}
```
However it's not the case when we want docs on completion:
```
""gopls"": {
    ""wantCompletionDocumentation"": true,
}
```
Please make completion return full docs when `FullDocumentation` option is set or add another config for completion.
",1,x tools gopls  propagate hoverkind to completion   as per    atm  there is a configuration to provide full docs on hover         gopls            hoverkind    fulldocumentation            however it s not the case when we want docs on completion         gopls           wantcompletiondocumentation   true           please make completion return full docs when  fulldocumentation  option is set or add another config for completion   ,1
43500,5541947555.0,IssuesEvent,2017-03-22 14:03:44,codetodesign/NYUAMS,https://api.github.com/repos/codetodesign/NYUAMS,closed,WIREFRAMES - Admin/account - Grant Administrator,$^~PAID~^$ 1.0DEV 1.1BRANCH_maintenance1 1.1v2 1.2TEST_CASE 2.5CLOSE 3.5_PUSH_TO_PROD 4.0gaa,"The Grant Administrator is considered a ""Client"" in the system, with the University Status of ""Grant Administrator.

We will have this portion of the New Account Wizard work the same way as New Client.  If the Grant Administrator aka client is already in the system, the user will ""skip LDAP search"" and pull their name up directly from the EBS.

Once an existing client is assigned to a Grant Account, there will be a popup warning:

```
   ""The client already exists in the system.  University Status is being set to Grant Administrator""
```
",1.0,"WIREFRAMES - Admin/account - Grant Administrator - The Grant Administrator is considered a ""Client"" in the system, with the University Status of ""Grant Administrator.

We will have this portion of the New Account Wizard work the same way as New Client.  If the Grant Administrator aka client is already in the system, the user will ""skip LDAP search"" and pull their name up directly from the EBS.

Once an existing client is assigned to a Grant Account, there will be a popup warning:

```
   ""The client already exists in the system.  University Status is being set to Grant Administrator""
```
",0,wireframes   admin account   grant administrator   the grant administrator is considered a  client  in the system  with the university status of  grant administrator   we will have this portion of the new account wizard work the same way as new client   if the grant administrator aka client is already in the system  the user will  skip ldap search  and pull their name up directly from the ebs   once an existing client is assigned to a grant account  there will be a popup warning           the client already exists in the system   university status is being set to grant administrator      ,0
15074,26419748969.0,IssuesEvent,2023-01-13 19:11:17,NASA-PDS/nucleus,https://api.github.com/repos/NASA-PDS/nucleus,opened,"As a user, I want to add a new component to the baseline nucleus workflow",needs:triage requirement,"<!--
   For more information on how to populate this new feature request, see the PDS Wiki on User Story Development:
   https://github.com/NASA-PDS/nasa-pds.github.io/wiki/Issue-Tracking#user-story-development
-->

## 🧑‍🔬 User Persona(s)
<!-- Ideally this would be consistent within a repo and documented with the requirements. -->
Node Operator

## 💪 Motivation
...so that I can add my own custom data processing tools into the baseline nucleus pipeline

## 📖 Additional Details
<!-- Please prove any additional details or information that could help provide some context for the user story. -->
- [ ] Adaptation User Guide


## ⚖️ Acceptance Criteria
**Given** <!-- a condition -->
**When I perform** <!-- an action -->
**Then I expect** <!-- the result -->

<!-- For Internal Dev Team Use -->

## ⚙️ Engineering Details
<!--
    Provide some design / implementation details and/or a sub-task checklist as needed. 
    Convert issue to Epic if estimate is outside the scope of 1 sprint.
-->
",1.0,"As a user, I want to add a new component to the baseline nucleus workflow - <!--
   For more information on how to populate this new feature request, see the PDS Wiki on User Story Development:
   https://github.com/NASA-PDS/nasa-pds.github.io/wiki/Issue-Tracking#user-story-development
-->

## 🧑‍🔬 User Persona(s)
<!-- Ideally this would be consistent within a repo and documented with the requirements. -->
Node Operator

## 💪 Motivation
...so that I can add my own custom data processing tools into the baseline nucleus pipeline

## 📖 Additional Details
<!-- Please prove any additional details or information that could help provide some context for the user story. -->
- [ ] Adaptation User Guide


## ⚖️ Acceptance Criteria
**Given** <!-- a condition -->
**When I perform** <!-- an action -->
**Then I expect** <!-- the result -->

<!-- For Internal Dev Team Use -->

## ⚙️ Engineering Details
<!--
    Provide some design / implementation details and/or a sub-task checklist as needed. 
    Convert issue to Epic if estimate is outside the scope of 1 sprint.
-->
",0,as a user  i want to add a new component to the baseline nucleus workflow            for more information on how to populate this new feature request  see the pds wiki on user story development                   🧑‍🔬 user persona s      node operator       💪 motivation     so that i can add my own custom data processing tools into the baseline nucleus pipeline       📖 additional details         adaptation user guide         ⚖️ acceptance criteria    given        when i perform        then i expect                ⚙️ engineering details            provide some design   implementation details and or a sub task checklist as needed        convert issue to epic if estimate is outside the scope of   sprint        ,0
46754,7278778137.0,IssuesEvent,2018-02-22 00:33:50,golang/go,https://api.github.com/repos/golang/go,opened,transfer label descriptions from wiki to labels themselves,Documentation,"Now that GitHub [added descriptions to labels](https://github.com/blog/2505-label-improvements-emoji-descriptions-and-more), it would probably be helpful to transfer the label descriptions from https://github.com/golang/go/wiki/IssueLabels to the labels themselves.

I think it would make it easier for more people to discover what the labels mean.

If we do this, I think the wiki page should be removed, to avoid having to maintain same information in two places.

This issue is to consider/discuss this opportunity.",1.0,"transfer label descriptions from wiki to labels themselves - Now that GitHub [added descriptions to labels](https://github.com/blog/2505-label-improvements-emoji-descriptions-and-more), it would probably be helpful to transfer the label descriptions from https://github.com/golang/go/wiki/IssueLabels to the labels themselves.

I think it would make it easier for more people to discover what the labels mean.

If we do this, I think the wiki page should be removed, to avoid having to maintain same information in two places.

This issue is to consider/discuss this opportunity.",1,transfer label descriptions from wiki to labels themselves   now that github     it would probably be helpful to transfer the label descriptions from   to the labels themselves     i think it would make it easier for more people to discover what the labels mean     if we do this  i think the wiki page should be removed  to avoid having to maintain same information in two places     this issue is to consider discuss this opportunity ,1
53288,28066270214.0,IssuesEvent,2023-03-29 15:37:43,opensearch-project/OpenSearch,https://api.github.com/repos/opensearch-project/OpenSearch,closed,[BUG] OpenSearch sort query performance regression,bug distributed framework needs more info Performance Search,"### Summary

OpenSearch performance for sort queries appears to have degraded since version 7.10.  A simple timestamp sort query was executed on a 100 GB data set in Amazon's managed service on a few different versions:   AES 7.10, AOS 1.3 and AOS 2.3.  The clusters used were of two types: the first configured with `t3.medium` data nodes, and the other with `r5.large` data nodes.

AES 7.10 had the best sort performance with regard to latency, while AOS 2.3 was the worst of the three. 

 It was presumed that the memory footprint might have increased as newer OpenSearch versions were released and that this might have had an impact on performance, especially since `t3.medium` has only 4 GB RAM (and 2 vCPUs).

Therefore, the clusters were upgraded to `r5.large`, which has 2 vCPUs and 16 GB RAM.  Latencies did not change substantially  for AES 7.10, degraded somewhat for AOS 1.3 and improved substantially for AOS 2.3 (compared to the smaller instance type.)  It seems likely that AOS 2.3 has a larger memory footprint, and would benefit from memory-optimized instance types.

It is true that the sort query used in the tests is rather simple-minded and that sophisticated users will use a more optimized query; however, not all users have that level of sophistication.  The reference query used here was:

```
        ""query"": {
          ""match_all"": {}
        },
        ""sort"" : [
          {""@timestamp"" : ""asc""}
        ]
```

The other point to note is the difference in performance with regard to sort ordering (ascending vs. descending):
  * There is a substantial degradation of descending sort performance vis-a-vis ascending in AOS 1.3.
  * On AOS 2.3 with the `r5.large` instance type, ascending sort performance is worse than descending in memory-constrained mode with t3’s.  Notably, the performance of both is similar with the r5 instances, but still worse than in AOS 1.3.
 
### Methodology

Performance was measured using OpenSearch Benchmark (OSB).  The data set was a synthetically generated one based on the `http_logs` workload packaged with OSB.  Each document was relatively small, ~128 bytes.

After the data was ingested and a force-merge carried out, the query above was run for 200 iterations after some warmup iterations.

The clusters each had 3 master nodes (r5.large) and 2 data nodes.

### Results

_All numbers are latencies in ms.  There were two runs in each mode to ensure repeatability._

Data Node Instance Type | Sort Mode | AES 7.10 | AOS 1.3 | AOS 2.3
------------------------|-----------|:--------:|:-------:|:-------:
t3.medium | desc | 47 | 4207 | 11541
t3.medium       |   asc | 181 | 389 | 43773
r5.large | desc | 53 | 6133 | 7894
r5.large         |   asc | 168 | 459 | 7229

",True,"[BUG] OpenSearch sort query performance regression - ### Summary

OpenSearch performance for sort queries appears to have degraded since version 7.10.  A simple timestamp sort query was executed on a 100 GB data set in Amazon's managed service on a few different versions:   AES 7.10, AOS 1.3 and AOS 2.3.  The clusters used were of two types: the first configured with `t3.medium` data nodes, and the other with `r5.large` data nodes.

AES 7.10 had the best sort performance with regard to latency, while AOS 2.3 was the worst of the three. 

 It was presumed that the memory footprint might have increased as newer OpenSearch versions were released and that this might have had an impact on performance, especially since `t3.medium` has only 4 GB RAM (and 2 vCPUs).

Therefore, the clusters were upgraded to `r5.large`, which has 2 vCPUs and 16 GB RAM.  Latencies did not change substantially  for AES 7.10, degraded somewhat for AOS 1.3 and improved substantially for AOS 2.3 (compared to the smaller instance type.)  It seems likely that AOS 2.3 has a larger memory footprint, and would benefit from memory-optimized instance types.

It is true that the sort query used in the tests is rather simple-minded and that sophisticated users will use a more optimized query; however, not all users have that level of sophistication.  The reference query used here was:

```
        ""query"": {
          ""match_all"": {}
        },
        ""sort"" : [
          {""@timestamp"" : ""asc""}
        ]
```

The other point to note is the difference in performance with regard to sort ordering (ascending vs. descending):
  * There is a substantial degradation of descending sort performance vis-a-vis ascending in AOS 1.3.
  * On AOS 2.3 with the `r5.large` instance type, ascending sort performance is worse than descending in memory-constrained mode with t3’s.  Notably, the performance of both is similar with the r5 instances, but still worse than in AOS 1.3.
 
### Methodology

Performance was measured using OpenSearch Benchmark (OSB).  The data set was a synthetically generated one based on the `http_logs` workload packaged with OSB.  Each document was relatively small, ~128 bytes.

After the data was ingested and a force-merge carried out, the query above was run for 200 iterations after some warmup iterations.

The clusters each had 3 master nodes (r5.large) and 2 data nodes.

### Results

_All numbers are latencies in ms.  There were two runs in each mode to ensure repeatability._

Data Node Instance Type | Sort Mode | AES 7.10 | AOS 1.3 | AOS 2.3
------------------------|-----------|:--------:|:-------:|:-------:
t3.medium | desc | 47 | 4207 | 11541
t3.medium       |   asc | 181 | 389 | 43773
r5.large | desc | 53 | 6133 | 7894
r5.large         |   asc | 168 | 459 | 7229

",0,  opensearch sort query performance regression       summary    opensearch performance for sort queries appears to have degraded since version       a simple timestamp sort query was executed on a   gb data set in amazon s managed service on a few different versions    aes      aos     and aos       the clusters used were of two types  the first configured with    medium  data nodes  and the other with    large  data nodes     aes     had the best sort performance with regard to latency  while aos     was the worst of the three       it was presumed that the memory footprint might have increased as newer opensearch versions were released and that this might have had an impact on performance  especially since    medium  has only   gb ram  and   vcpus      therefore  the clusters were upgraded to    large   which has   vcpus and   gb ram   latencies did not change substantially  for aes      degraded somewhat for aos     and improved substantially for aos      compared to the smaller instance type    it seems likely that aos     has a larger memory footprint  and would benefit from memory optimized instance types     it is true that the sort query used in the tests is rather simple minded and that sophisticated users will use a more optimized query  however  not all users have that level of sophistication   the reference query used here was                   query                 match all                            sort                    timestamp     asc                      the other point to note is the difference in performance with regard to sort ordering  ascending vs  descending        there is a substantial degradation of descending sort performance vis a vis ascending in aos           on aos     with the    large  instance type  ascending sort performance is worse than descending in memory constrained mode with  ’s   notably  the performance of both is similar with the   instances  but still worse than in aos              methodology    performance was measured using opensearch benchmark  osb    the data set was a synthetically generated one based on the  http logs  workload packaged with osb   each document was relatively small     bytes     after the data was ingested and a force merge carried out  the query above was run for   iterations after some warmup iterations     the clusters each had   master nodes    large  and   data nodes         results     all numbers are latencies in ms   there were two runs in each mode to ensure repeatability      data node instance type   sort mode   aes       aos       aos                                                                             medium   desc                medium           asc                large   desc                large             asc                ,0
16513,4056576916.0,IssuesEvent,2016-05-24 19:05:32,golang/go,https://api.github.com/repos/golang/go,closed,"testing: document that ""testdata"" is idiomatic and special",Documentation NeedsFix,"What version of Go are you using (go version)?
go version go1.6 linux/amd64

What operating system and processor architecture are you using (go env)?
GOOS=""linux""
GOARCH=""amd64""

What did you do?
I read documentation at https://golang.org/pkg/testing/.

What did you expect to see?
I expected easy to find documentation about writing a test which manipulates a file.

What did you see instead?
Instead I had difficulty discovering that I can use `""."", ""_"", ""testdata""` ([source](https://github.com/golang/go/blob/master/src/cmd/go/main.go#L595)). I don't know which one is the most idomatic.",1.0,"testing: document that ""testdata"" is idiomatic and special - What version of Go are you using (go version)?
go version go1.6 linux/amd64

What operating system and processor architecture are you using (go env)?
GOOS=""linux""
GOARCH=""amd64""

What did you do?
I read documentation at https://golang.org/pkg/testing/.

What did you expect to see?
I expected easy to find documentation about writing a test which manipulates a file.

What did you see instead?
Instead I had difficulty discovering that I can use `""."", ""_"", ""testdata""` ([source](https://github.com/golang/go/blob/master/src/cmd/go/main.go#L595)). I don't know which one is the most idomatic.",1,testing  document that  testdata  is idiomatic and special   what version of go are you using  go version    go version     linux      what operating system and processor architecture are you using  go env    goos  linux   goarch        what did you do   i read documentation at      what did you expect to see   i expected easy to find documentation about writing a test which manipulates a file     what did you see instead   instead i had difficulty discovering that i can use             testdata        i don t know which one is the most idomatic ,1
108611,11596596900.0,IssuesEvent,2020-02-24 19:15:53,golang/go,https://api.github.com/repos/golang/go,closed,doc: write Go 1.14 release notes,Documentation NeedsFix help wanted release-blocker,"Tracking bug for writing the Go 1.14 Release Notes.

The latest state on tip can be viewed at https://tip.golang.org/doc/go1.14.

Previously #17929, #15810, #5929, etc.",1.0,"doc: write Go 1.14 release notes - Tracking bug for writing the Go 1.14 Release Notes.

The latest state on tip can be viewed at https://tip.golang.org/doc/go1.14.

Previously #17929, #15810, #5929, etc.",1,doc  write go     release notes   tracking bug for writing the go     release notes     the latest state on tip can be viewed at      previously             etc ,1
62654,7622025620.0,IssuesEvent,2018-05-03 10:36:36,ev3dev-lang-java/ev3dev-lang-java,https://api.github.com/repos/ev3dev-lang-java/ev3dev-lang-java,closed,Iteration Planning,Agile Debian Jessie Debian Stretch community design in progress operations,"In this session, Active members will discuss about the content of the next iteration.
https://github.com/ev3dev-lang-java/ev3dev-lang-java/milestone/10

In the backlog exist a set of issues categorised in the following areas:

- Infrastructure
- Internal Refactoring
- New features
- Design
- Performance
- Documentation
- ROS
- Communications

It could be interesting the discussion.",1.0,"Iteration Planning - In this session, Active members will discuss about the content of the next iteration.
https://github.com/ev3dev-lang-java/ev3dev-lang-java/milestone/10

In the backlog exist a set of issues categorised in the following areas:

- Infrastructure
- Internal Refactoring
- New features
- Design
- Performance
- Documentation
- ROS
- Communications

It could be interesting the discussion.",0,iteration planning   in this session  active members will discuss about the content of the next iteration        in the backlog exist a set of issues categorised in the following areas       infrastructure    internal refactoring    new features    design    performance    documentation    ros    communications    it could be interesting the discussion ,0
50245,7574484424.0,IssuesEvent,2018-04-23 21:07:41,golang/go,https://api.github.com/repos/golang/go,closed,proposal: decide & document policy for giving out golang.org emails,Documentation Proposal,"We should decide on & document the policy for who gets golang.org email addresses.

The community is curious.

Empirically, the policy seems to be ""anybody who's ever been paid by Google either now or in the past"". But it's not obvious that's the correct policy. (if that's even accurate)

/cc @andybons @namusyaka 
",1.0,"proposal: decide & document policy for giving out golang.org emails - We should decide on & document the policy for who gets golang.org email addresses.

The community is curious.

Empirically, the policy seems to be ""anybody who's ever been paid by Google either now or in the past"". But it's not obvious that's the correct policy. (if that's even accurate)

/cc @andybons @namusyaka 
",1,proposal  decide   document policy for giving out golang org emails   we should decide on   document the policy for who gets golang org email addresses     the community is curious     empirically  the policy seems to be  anybody who s ever been paid by google either now or in the past   but it s not obvious that s the correct policy   if that s even accurate      cc  andybons  namusyaka   ,1
178435,14669556632.0,IssuesEvent,2020-12-30 01:13:13,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/gopls: add autogenerated documentation for analyzers,Documentation Tools gopls,`gopls/analyzers.md` could be populated from the analyzer.Doc fields of all of the analyzers in internal/lsp/source/options.go.,1.0,x/tools/gopls: add autogenerated documentation for analyzers - `gopls/analyzers.md` could be populated from the analyzer.Doc fields of all of the analyzers in internal/lsp/source/options.go.,1,x tools gopls  add autogenerated documentation for analyzers    gopls analyzers md  could be populated from the analyzer doc fields of all of the analyzers in internal lsp source options go ,1
98202,11047903658.0,IssuesEvent,2019-12-09 19:59:09,golang/go,https://api.github.com/repos/golang/go,closed,doc: release history webpage contains suboptimal links [1.13 backport],CherryPickApproved Documentation,"@dmitshur requested issue #35988 to be considered for backport to the next 1.13 minor release.

> @gopherbot, could you please be so kind as to open two backport issues: one for Go 1.13 and another for Go 1.12. This is a documentation fix.
",1.0,"doc: release history webpage contains suboptimal links [1.13 backport] - @dmitshur requested issue #35988 to be considered for backport to the next 1.13 minor release.

> @gopherbot, could you please be so kind as to open two backport issues: one for Go 1.13 and another for Go 1.12. This is a documentation fix.
",1,doc  release history webpage contains suboptimal links      dmitshur requested issue    to be considered for backport to the next     minor release      gopherbot  could you please be so kind as to open two backport issues  one for go     and another for go      this is a documentation fix  ,1
154023,19710763090.0,IssuesEvent,2022-01-13 04:52:50,ChoeMinji/react-17.0.2,https://api.github.com/repos/ChoeMinji/react-17.0.2,opened,CVE-2022-0155 (High) detected in multiple libraries,security vulnerability,"## CVE-2022-0155 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>follow-redirects-1.7.0.tgz</b>, <b>follow-redirects-1.10.0.tgz</b>, <b>follow-redirects-1.5.8.tgz</b></p></summary>
<p>

<details><summary><b>follow-redirects-1.7.0.tgz</b></p></summary>

<p>HTTP and HTTPS modules that follow redirects.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.7.0.tgz"">https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.7.0.tgz</a></p>
<p>

Dependency Hierarchy:
  - react-devtools-shell-0.0.0.tgz (Root Library)
    - webpack-dev-server-3.10.3.tgz
      - http-proxy-middleware-0.19.1.tgz
        - http-proxy-1.17.0.tgz
          - :x: **follow-redirects-1.7.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>follow-redirects-1.10.0.tgz</b></p></summary>

<p>HTTP and HTTPS modules that follow redirects.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.10.0.tgz"">https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.10.0.tgz</a></p>
<p>

Dependency Hierarchy:
  - react-scripts-3.4.1.tgz (Root Library)
    - webpack-dev-server-3.10.3.tgz
      - http-proxy-middleware-0.19.1.tgz
        - http-proxy-1.18.0.tgz
          - :x: **follow-redirects-1.10.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>follow-redirects-1.5.8.tgz</b></p></summary>

<p>HTTP and HTTPS modules that follow redirects.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.5.8.tgz"">https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.5.8.tgz</a></p>
<p>

Dependency Hierarchy:
  - webpack-dev-server-3.2.1.tgz (Root Library)
    - http-proxy-middleware-0.19.1.tgz
      - http-proxy-1.18.0.tgz
        - :x: **follow-redirects-1.5.8.tgz** (Vulnerable Library)
</details>

<p>Found in HEAD commit: <a href=""https://github.com/ChoeMinji/react-17.0.2/commit/4669645897ed4ebcd4ee037f4dabb509ed4754c7"">4669645897ed4ebcd4ee037f4dabb509ed4754c7</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>  
  
follow-redirects is vulnerable to Exposure of Private Personal Information to an Unauthorized Actor

<p>Publish Date: 2022-01-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0155>CVE-2022-0155</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>8.0</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: Required
  - 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://huntr.dev/bounties/fc524e4b-ebb6-427d-ab67-a64181020406/"">https://huntr.dev/bounties/fc524e4b-ebb6-427d-ab67-a64181020406/</a></p>
<p>Release Date: 2022-01-10</p>
<p>Fix Resolution: follow-redirects - v1.14.7</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-2022-0155 (High) detected in multiple libraries - ## CVE-2022-0155 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>follow-redirects-1.7.0.tgz</b>, <b>follow-redirects-1.10.0.tgz</b>, <b>follow-redirects-1.5.8.tgz</b></p></summary>
<p>

<details><summary><b>follow-redirects-1.7.0.tgz</b></p></summary>

<p>HTTP and HTTPS modules that follow redirects.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.7.0.tgz"">https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.7.0.tgz</a></p>
<p>

Dependency Hierarchy:
  - react-devtools-shell-0.0.0.tgz (Root Library)
    - webpack-dev-server-3.10.3.tgz
      - http-proxy-middleware-0.19.1.tgz
        - http-proxy-1.17.0.tgz
          - :x: **follow-redirects-1.7.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>follow-redirects-1.10.0.tgz</b></p></summary>

<p>HTTP and HTTPS modules that follow redirects.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.10.0.tgz"">https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.10.0.tgz</a></p>
<p>

Dependency Hierarchy:
  - react-scripts-3.4.1.tgz (Root Library)
    - webpack-dev-server-3.10.3.tgz
      - http-proxy-middleware-0.19.1.tgz
        - http-proxy-1.18.0.tgz
          - :x: **follow-redirects-1.10.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>follow-redirects-1.5.8.tgz</b></p></summary>

<p>HTTP and HTTPS modules that follow redirects.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.5.8.tgz"">https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.5.8.tgz</a></p>
<p>

Dependency Hierarchy:
  - webpack-dev-server-3.2.1.tgz (Root Library)
    - http-proxy-middleware-0.19.1.tgz
      - http-proxy-1.18.0.tgz
        - :x: **follow-redirects-1.5.8.tgz** (Vulnerable Library)
</details>

<p>Found in HEAD commit: <a href=""https://github.com/ChoeMinji/react-17.0.2/commit/4669645897ed4ebcd4ee037f4dabb509ed4754c7"">4669645897ed4ebcd4ee037f4dabb509ed4754c7</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>  
  
follow-redirects is vulnerable to Exposure of Private Personal Information to an Unauthorized Actor

<p>Publish Date: 2022-01-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0155>CVE-2022-0155</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>8.0</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: Required
  - 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://huntr.dev/bounties/fc524e4b-ebb6-427d-ab67-a64181020406/"">https://huntr.dev/bounties/fc524e4b-ebb6-427d-ab67-a64181020406/</a></p>
<p>Release Date: 2022-01-10</p>
<p>Fix Resolution: follow-redirects - v1.14.7</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in multiple libraries      cve       high severity vulnerability     vulnerable libraries    follow redirects       tgz    follow redirects       tgz    follow redirects       tgz          follow redirects       tgz      http and https modules that follow redirects    library home page   a href       dependency hierarchy      react devtools shell       tgz  root library        webpack dev server       tgz         http proxy middleware       tgz           http proxy       tgz              x    follow redirects       tgz    vulnerable library       follow redirects       tgz      http and https modules that follow redirects    library home page   a href       dependency hierarchy      react scripts       tgz  root library        webpack dev server       tgz         http proxy middleware       tgz           http proxy       tgz              x    follow redirects       tgz    vulnerable library       follow redirects       tgz      http and https modules that follow redirects    library home page   a href       dependency hierarchy      webpack dev server       tgz  root library        http proxy middleware       tgz         http proxy       tgz            x    follow redirects       tgz    vulnerable library      found in head commit   a href     found in base branch   master              vulnerability details         follow redirects is vulnerable to exposure of private personal information to an unauthorized actor   publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  low     user interaction  required     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  follow redirects                       step up your open source security game with whitesource    ,0
378837,11209562692.0,IssuesEvent,2020-01-06 10:48:28,ECLK/Nomination,https://api.github.com/repos/ECLK/Nomination,closed,Error messages,Call election Priority 1,"In the current system call election module doesn't show any error message to the user in the event of unsuccessful form submission  

**To Reproduce**
Steps to reproduce the behavior:
1. Click on Call election tab on side navigation bar
2. Select election template from Call election card and give election name eg: Presidential 2019
3. Click on next button
4. Complete timeline section and click next
5. Complete select electorate and click finish 
6. Click the submit for approval button on next step
7. You can see the snack bar for success message 

**Expected behavior**
even though we have success message. currently there in no message showing in the event of unsuccessful form submission so we need to show informative error messages in the event of unsuccessful form submission as well

**Additional context**
we will have to do the same changes for the update call election as well  
",1.0,"Error messages - In the current system call election module doesn't show any error message to the user in the event of unsuccessful form submission  

**To Reproduce**
Steps to reproduce the behavior:
1. Click on Call election tab on side navigation bar
2. Select election template from Call election card and give election name eg: Presidential 2019
3. Click on next button
4. Complete timeline section and click next
5. Complete select electorate and click finish 
6. Click the submit for approval button on next step
7. You can see the snack bar for success message 

**Expected behavior**
even though we have success message. currently there in no message showing in the event of unsuccessful form submission so we need to show informative error messages in the event of unsuccessful form submission as well

**Additional context**
we will have to do the same changes for the update call election as well  
",0,error messages   in the current system call election module doesn t show any error message to the user in the event of unsuccessful form submission        to reproduce    steps to reproduce the behavior      click on call election tab on side navigation bar     select election template from call election card and give election name eg  presidential       click on next button     complete timeline section and click next     complete select electorate and click finish      click the submit for approval button on next step     you can see the snack bar for success message       expected behavior    even though we have success message  currently there in no message showing in the event of unsuccessful form submission so we need to show informative error messages in the event of unsuccessful form submission as well      additional context    we will have to do the same changes for the update call election as well    ,0
103100,8879878484.0,IssuesEvent,2019-01-14 01:57:22,brave/brave-browser,https://api.github.com/repos/brave/brave-browser,opened,"Sync'd bookmarks doesn't retain favicon, adds it when the bookmark is loaded ",QA/Test-Plan-Specified QA/Yes bug feature/sync priority/P4 release-notes/include,"<!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue. 

PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE. 
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->

## Description 
<!--Provide a brief description of the issue-->
Sync'd bookmarks doesn't retain favicon, adds it when the bookmark is loaded 

## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->

   1. Create sync chain and add two devices to it
   2. Import bookmarks file on device 1
   3. Wait till it sync's over to device 2, doesn't show any favicon, just has generic file icon

## Actual result:
<!--Please add screenshots if needed-->
Sync'd bookmarks doesn't retain favicon, adds it when the bookmark is loaded 

## Expected result:
Should sync favicons as well

## Reproduces how often: 
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->
Easy

## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->

Brave | 0.59.21 Chromium: 72.0.3626.28 (Official Build) beta (64-bit)
-- | --
Revision | 997b1040b63bac324e815797ba52be0cd8f616ed-refs/branch-heads/3626@{#461}
OS | All

### Reproducible on current release:
- Does it reproduce on brave-browser dev/beta builds? 
Yes on beta

### Website problems only:  
- Does the issue resolve itself when disabling Brave Shields? 
No
- Is the issue reproducible on the latest version of Chrome? 
No
### Additional Information
<!--Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue-->
",1.0,"Sync'd bookmarks doesn't retain favicon, adds it when the bookmark is loaded  - <!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue. 

PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE. 
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->

## Description 
<!--Provide a brief description of the issue-->
Sync'd bookmarks doesn't retain favicon, adds it when the bookmark is loaded 

## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->

   1. Create sync chain and add two devices to it
   2. Import bookmarks file on device 1
   3. Wait till it sync's over to device 2, doesn't show any favicon, just has generic file icon

## Actual result:
<!--Please add screenshots if needed-->
Sync'd bookmarks doesn't retain favicon, adds it when the bookmark is loaded 

## Expected result:
Should sync favicons as well

## Reproduces how often: 
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->
Easy

## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->

Brave | 0.59.21 Chromium: 72.0.3626.28 (Official Build) beta (64-bit)
-- | --
Revision | 997b1040b63bac324e815797ba52be0cd8f616ed-refs/branch-heads/3626@{#461}
OS | All

### Reproducible on current release:
- Does it reproduce on brave-browser dev/beta builds? 
Yes on beta

### Website problems only:  
- Does the issue resolve itself when disabling Brave Shields? 
No
- Is the issue reproducible on the latest version of Chrome? 
No
### Additional Information
<!--Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue-->
",0,sync d bookmarks doesn t retain favicon  adds it when the bookmark is loaded         have you searched for similar issues  before submitting this issue  please check the open issues and add a note before logging a new issue      please use the template below to provide information about the issue    insufficient info will get the issue closed  it will only be reopened after sufficient info is provided          description      sync d bookmarks doesn t retain favicon  adds it when the bookmark is loaded        steps to reproduce             create sync chain and add two devices to it        import bookmarks file on device          wait till it sync s over to device    doesn t show any favicon  just has generic file icon       actual result      sync d bookmarks doesn t retain favicon  adds it when the bookmark is loaded        expected result   should sync favicons as well       reproduces how often       easy       brave version  brave   version info        brave         chromium           official build  beta    bit            revision     refs branch heads         os   all        reproducible on current release     does it reproduce on brave browser dev beta builds    yes on beta        website problems only       does the issue resolve itself when disabling brave shields    no    is the issue reproducible on the latest version of chrome    no      additional information     ,0
547753,16046308073.0,IssuesEvent,2021-04-22 14:00:43,Shluffy/Shluffy,https://api.github.com/repos/Shluffy/Shluffy,closed,Bug: [Bookmarklet: Redirect To Scratch User] When value = null,High Priority In Progress bug,"If you just click ok you will be redirected to the scratch user null. This is not how it is supposed to work. The code for this bookmarklet is in a branch, but not in main",1.0,"Bug: [Bookmarklet: Redirect To Scratch User] When value = null - If you just click ok you will be redirected to the scratch user null. This is not how it is supposed to work. The code for this bookmarklet is in a branch, but not in main",0,bug    when value   null   if you just click ok you will be redirected to the scratch user null  this is not how it is supposed to work  the code for this bookmarklet is in a branch  but not in main,0
175166,21300828254.0,IssuesEvent,2022-04-15 02:42:21,Kijacode/dotfiles,https://api.github.com/repos/Kijacode/dotfiles,opened,CVE-2022-0436 (High) detected in grunt-1.4.1.tgz,security vulnerability,"## CVE-2022-0436 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>grunt-1.4.1.tgz</b></p></summary>

<p>The JavaScript Task Runner</p>
<p>Library home page: <a href=""https://registry.npmjs.org/grunt/-/grunt-1.4.1.tgz"">https://registry.npmjs.org/grunt/-/grunt-1.4.1.tgz</a></p>
<p>Path to dependency file: /.vscode/extensions/wallabyjs.quokka-vscode-1.0.386/package.json</p>
<p>Path to vulnerable library: /.vscode/extensions/wallabyjs.quokka-vscode-1.0.386/node_modules/grunt/package.json</p>
<p>

Dependency Hierarchy:
  - :x: **grunt-1.4.1.tgz** (Vulnerable Library)
<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>  
  
Path Traversal in GitHub repository gruntjs/grunt prior to 1.5.2.

<p>Publish Date: 2022-04-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0436>CVE-2022-0436</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.1</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0436"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0436</a></p>
<p>Release Date: 2022-04-12</p>
<p>Fix Resolution: grunt - 1.5.2</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-2022-0436 (High) detected in grunt-1.4.1.tgz - ## CVE-2022-0436 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>grunt-1.4.1.tgz</b></p></summary>

<p>The JavaScript Task Runner</p>
<p>Library home page: <a href=""https://registry.npmjs.org/grunt/-/grunt-1.4.1.tgz"">https://registry.npmjs.org/grunt/-/grunt-1.4.1.tgz</a></p>
<p>Path to dependency file: /.vscode/extensions/wallabyjs.quokka-vscode-1.0.386/package.json</p>
<p>Path to vulnerable library: /.vscode/extensions/wallabyjs.quokka-vscode-1.0.386/node_modules/grunt/package.json</p>
<p>

Dependency Hierarchy:
  - :x: **grunt-1.4.1.tgz** (Vulnerable Library)
<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>  
  
Path Traversal in GitHub repository gruntjs/grunt prior to 1.5.2.

<p>Publish Date: 2022-04-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0436>CVE-2022-0436</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.1</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0436"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0436</a></p>
<p>Release Date: 2022-04-12</p>
<p>Fix Resolution: grunt - 1.5.2</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in grunt       tgz      cve       high severity vulnerability     vulnerable library    grunt       tgz      the javascript task runner   library home page   a href     path to dependency file    vscode extensions wallabyjs quokka vscode       package json   path to vulnerable library    vscode extensions wallabyjs quokka vscode       node modules grunt package json     dependency hierarchy       x    grunt       tgz    vulnerable library   found in base branch   main              vulnerability details         path traversal in github repository gruntjs grunt prior to          publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  local     attack complexity  low     privileges required  low     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  none   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  grunt                       step up your open source security game with whitesource    ,0
30703,7244798268.0,IssuesEvent,2018-02-14 16:08:09,Fake-Api/FakeApi,https://api.github.com/repos/Fake-Api/FakeApi,opened,Remove duplicated validation,code duplicate,"Similar blocks of code found in 2 locations. Consider refactoring.

https://codeclimate.com/github/wnascimento/FakeApi/server/app/requests/Request.js#issue_5a787a3224cbe00001000051",1.0,"Remove duplicated validation - Similar blocks of code found in 2 locations. Consider refactoring.

https://codeclimate.com/github/wnascimento/FakeApi/server/app/requests/Request.js#issue_5a787a3224cbe00001000051",0,remove duplicated validation   similar blocks of code found in   locations  consider refactoring      ,0
393821,11625291098.0,IssuesEvent,2020-02-27 12:24:27,SacredDuckwhale/Rarity,https://api.github.com/repos/SacredDuckwhale/Rarity,closed,Add tracking for collectibles dropped in Horrific Visions,complexity: moderate module:core module:database priority:normal status:in-progress type:task,"Mounts:

- [x] https://ptr.wowhead.com/item=174653/mail-muncher 

---

Pets:

- [x] https://ptr.wowhead.com/item=174458/void-scarred-hare
- [x] https://ptr.wowhead.com/item=174460/box-labeled-danger-void-rat-inside#comments
- [x] https://ptr.wowhead.com/item=173726/box-with-faintly-glowing-air-holes
- [x] https://ptr.wowhead.com/item=174461/swirling-black-bottle#comments
- [x] https://ptr.wowhead.com/item=174459/voidwoven-cat-collar#comments
- [x] https://ptr.wowhead.com/item=174646/void-link-frostwolf-collar#comments
- [x] https://ptr.wowhead.com/item=174457/cthuffer#comments

---

Toys:

- [x] https://ptr.wowhead.com/item=174926/overly-sensitive-void-spectacles#comments
- [x] https://ptr.wowhead.com/item=174924/void-touched-souvenir-totem#comments",1.0,"Add tracking for collectibles dropped in Horrific Visions - Mounts:

- [x] https://ptr.wowhead.com/item=174653/mail-muncher 

---

Pets:

- [x] https://ptr.wowhead.com/item=174458/void-scarred-hare
- [x] https://ptr.wowhead.com/item=174460/box-labeled-danger-void-rat-inside#comments
- [x] https://ptr.wowhead.com/item=173726/box-with-faintly-glowing-air-holes
- [x] https://ptr.wowhead.com/item=174461/swirling-black-bottle#comments
- [x] https://ptr.wowhead.com/item=174459/voidwoven-cat-collar#comments
- [x] https://ptr.wowhead.com/item=174646/void-link-frostwolf-collar#comments
- [x] https://ptr.wowhead.com/item=174457/cthuffer#comments

---

Toys:

- [x] https://ptr.wowhead.com/item=174926/overly-sensitive-void-spectacles#comments
- [x] https://ptr.wowhead.com/item=174924/void-touched-souvenir-totem#comments",0,add tracking for collectibles dropped in horrific visions   mounts                      pets                                                               toys                 ,0
173274,14406753531.0,IssuesEvent,2020-12-03 20:43:06,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.16: document compiler changes for Go 1.16,Documentation NeedsInvestigation release-blocker,"As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

<h2 id=""compiler"">Compiler</h2>

<p>
  <strong>TODO</strong>
</p>

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved. (If there aren't noteworthy compiler changes in Go 1.16, the section should be removed.)

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.",1.0,"doc/go1.16: document compiler changes for Go 1.16 - As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

<h2 id=""compiler"">Compiler</h2>

<p>
  <strong>TODO</strong>
</p>

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved. (If there aren't noteworthy compiler changes in Go 1.16, the section should be removed.)

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.",1,doc      document compiler changes for go       as of filing this issue  the     contained the following html      compiler           todo               per     it s a release blocker for go     beta   to have a complete draft of the eventual release notes  and so the todo needs to be resolved   if there aren t noteworthy compiler changes in go      the section should be removed      a sequence of steps to resolve this issue may be        come up with a draft release note entry in this issue  then move the issue to needsfix state      send a cl with  doc           and include  for     fixes   this issue    in the body ,1
97802,16245126988.0,IssuesEvent,2021-05-07 13:56:11,TIBCOSoftware/TCSTK-custom-form-app-plugin,https://api.github.com/repos/TIBCOSoftware/TCSTK-custom-form-app-plugin,closed,"CVE-2021-23362 (Medium) detected in hosted-git-info-2.8.8.tgz, hosted-git-info-3.0.7.tgz",security vulnerability,"## CVE-2021-23362 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>hosted-git-info-2.8.8.tgz</b>, <b>hosted-git-info-3.0.7.tgz</b></p></summary>
<p>

<details><summary><b>hosted-git-info-2.8.8.tgz</b></p></summary>

<p>Provides metadata and conversions from repository urls for Github, Bitbucket and Gitlab</p>
<p>Library home page: <a href=""https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.8.8.tgz"">https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.8.8.tgz</a></p>
<p>Path to dependency file: TCSTK-custom-form-app-plugin/package.json</p>
<p>Path to vulnerable library: TCSTK-custom-form-app-plugin/node_modules/schematics-utilities/node_modules/hosted-git-info/package.json,TCSTK-custom-form-app-plugin/node_modules/normalize-package-data/node_modules/hosted-git-info/package.json,TCSTK-custom-form-app-plugin/node_modules/npm-registry-fetch/node_modules/hosted-git-info/package.json,TCSTK-custom-form-app-plugin/node_modules/pacote/node_modules/hosted-git-info/package.json</p>
<p>

Dependency Hierarchy:
  - cli-10.2.1.tgz (Root Library)
    - pacote-9.5.12.tgz
      - normalize-package-data-2.5.0.tgz
        - :x: **hosted-git-info-2.8.8.tgz** (Vulnerable Library)
</details>
<details><summary><b>hosted-git-info-3.0.7.tgz</b></p></summary>

<p>Provides metadata and conversions from repository urls for Github, Bitbucket and Gitlab</p>
<p>Library home page: <a href=""https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-3.0.7.tgz"">https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-3.0.7.tgz</a></p>
<p>Path to dependency file: TCSTK-custom-form-app-plugin/package.json</p>
<p>Path to vulnerable library: TCSTK-custom-form-app-plugin/node_modules/hosted-git-info/package.json</p>
<p>

Dependency Hierarchy:
  - cli-10.2.1.tgz (Root Library)
    - npm-package-arg-8.0.1.tgz
      - :x: **hosted-git-info-3.0.7.tgz** (Vulnerable Library)
</details>

<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The package hosted-git-info before 3.0.8 are vulnerable to Regular Expression Denial of Service (ReDoS) via regular expression shortcutMatch in the fromUrl function in index.js. The affected regular expression exhibits polynomial worst-case time complexity.

<p>Publish Date: 2021-03-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23362>CVE-2021-23362</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/npm/hosted-git-info/releases/tag/v3.0.8"">https://github.com/npm/hosted-git-info/releases/tag/v3.0.8</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: hosted-git-info - 3.0.8</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":false,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""hosted-git-info"",""packageVersion"":""2.8.8"",""packageFilePaths"":[""/package.json""],""isTransitiveDependency"":true,""dependencyTree"":""@angular/cli:10.2.1;pacote:9.5.12;normalize-package-data:2.5.0;hosted-git-info:2.8.8"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""hosted-git-info - 3.0.8""},{""packageType"":""javascript/Node.js"",""packageName"":""hosted-git-info"",""packageVersion"":""3.0.7"",""packageFilePaths"":[""/package.json""],""isTransitiveDependency"":true,""dependencyTree"":""@angular/cli:10.2.1;npm-package-arg:8.0.1;hosted-git-info:3.0.7"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""hosted-git-info - 3.0.8""}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""CVE-2021-23362"",""vulnerabilityDetails"":""The package hosted-git-info before 3.0.8 are vulnerable to Regular Expression Denial of Service (ReDoS) via regular expression shortcutMatch in the fromUrl function in index.js. The affected regular expression exhibits polynomial worst-case time complexity."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23362"",""cvss3Severity"":""medium"",""cvss3Score"":""5.3"",""cvss3Metrics"":{""A"":""Low"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""None"",""AV"":""Network"",""I"":""None""},""extraData"":{}}</REMEDIATE> -->",True,"CVE-2021-23362 (Medium) detected in hosted-git-info-2.8.8.tgz, hosted-git-info-3.0.7.tgz - ## CVE-2021-23362 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>hosted-git-info-2.8.8.tgz</b>, <b>hosted-git-info-3.0.7.tgz</b></p></summary>
<p>

<details><summary><b>hosted-git-info-2.8.8.tgz</b></p></summary>

<p>Provides metadata and conversions from repository urls for Github, Bitbucket and Gitlab</p>
<p>Library home page: <a href=""https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.8.8.tgz"">https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.8.8.tgz</a></p>
<p>Path to dependency file: TCSTK-custom-form-app-plugin/package.json</p>
<p>Path to vulnerable library: TCSTK-custom-form-app-plugin/node_modules/schematics-utilities/node_modules/hosted-git-info/package.json,TCSTK-custom-form-app-plugin/node_modules/normalize-package-data/node_modules/hosted-git-info/package.json,TCSTK-custom-form-app-plugin/node_modules/npm-registry-fetch/node_modules/hosted-git-info/package.json,TCSTK-custom-form-app-plugin/node_modules/pacote/node_modules/hosted-git-info/package.json</p>
<p>

Dependency Hierarchy:
  - cli-10.2.1.tgz (Root Library)
    - pacote-9.5.12.tgz
      - normalize-package-data-2.5.0.tgz
        - :x: **hosted-git-info-2.8.8.tgz** (Vulnerable Library)
</details>
<details><summary><b>hosted-git-info-3.0.7.tgz</b></p></summary>

<p>Provides metadata and conversions from repository urls for Github, Bitbucket and Gitlab</p>
<p>Library home page: <a href=""https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-3.0.7.tgz"">https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-3.0.7.tgz</a></p>
<p>Path to dependency file: TCSTK-custom-form-app-plugin/package.json</p>
<p>Path to vulnerable library: TCSTK-custom-form-app-plugin/node_modules/hosted-git-info/package.json</p>
<p>

Dependency Hierarchy:
  - cli-10.2.1.tgz (Root Library)
    - npm-package-arg-8.0.1.tgz
      - :x: **hosted-git-info-3.0.7.tgz** (Vulnerable Library)
</details>

<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The package hosted-git-info before 3.0.8 are vulnerable to Regular Expression Denial of Service (ReDoS) via regular expression shortcutMatch in the fromUrl function in index.js. The affected regular expression exhibits polynomial worst-case time complexity.

<p>Publish Date: 2021-03-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23362>CVE-2021-23362</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/npm/hosted-git-info/releases/tag/v3.0.8"">https://github.com/npm/hosted-git-info/releases/tag/v3.0.8</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: hosted-git-info - 3.0.8</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":false,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""hosted-git-info"",""packageVersion"":""2.8.8"",""packageFilePaths"":[""/package.json""],""isTransitiveDependency"":true,""dependencyTree"":""@angular/cli:10.2.1;pacote:9.5.12;normalize-package-data:2.5.0;hosted-git-info:2.8.8"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""hosted-git-info - 3.0.8""},{""packageType"":""javascript/Node.js"",""packageName"":""hosted-git-info"",""packageVersion"":""3.0.7"",""packageFilePaths"":[""/package.json""],""isTransitiveDependency"":true,""dependencyTree"":""@angular/cli:10.2.1;npm-package-arg:8.0.1;hosted-git-info:3.0.7"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""hosted-git-info - 3.0.8""}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""CVE-2021-23362"",""vulnerabilityDetails"":""The package hosted-git-info before 3.0.8 are vulnerable to Regular Expression Denial of Service (ReDoS) via regular expression shortcutMatch in the fromUrl function in index.js. The affected regular expression exhibits polynomial worst-case time complexity."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23362"",""cvss3Severity"":""medium"",""cvss3Score"":""5.3"",""cvss3Metrics"":{""A"":""Low"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""None"",""AV"":""Network"",""I"":""None""},""extraData"":{}}</REMEDIATE> -->",0,cve      medium  detected in hosted git info       tgz  hosted git info       tgz      cve       medium severity vulnerability     vulnerable libraries    hosted git info       tgz    hosted git info       tgz          hosted git info       tgz      provides metadata and conversions from repository urls for github  bitbucket and gitlab   library home page   a href     path to dependency file  tcstk custom form app plugin package json   path to vulnerable library  tcstk custom form app plugin node modules schematics utilities node modules hosted git info package json tcstk custom form app plugin node modules normalize package data node modules hosted git info package json tcstk custom form app plugin node modules npm registry fetch node modules hosted git info package json tcstk custom form app plugin node modules pacote node modules hosted git info package json     dependency hierarchy      cli       tgz  root library        pacote       tgz         normalize package data       tgz            x    hosted git info       tgz    vulnerable library       hosted git info       tgz      provides metadata and conversions from repository urls for github  bitbucket and gitlab   library home page   a href     path to dependency file  tcstk custom form app plugin package json   path to vulnerable library  tcstk custom form app plugin node modules hosted git info package json     dependency hierarchy      cli       tgz  root library        npm package arg       tgz          x    hosted git info       tgz    vulnerable library      found in base branch   master              vulnerability details         the package hosted git info before       are vulnerable to regular expression denial of service  redos  via regular expression shortcutmatch in the fromurl function in index js  the affected regular expression exhibits polynomial worst case time complexity    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  low   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  hosted git info                      isopenpronvulnerability  false  ispackagebased  true  isdefaultbranch  true  packages     istransitivedependency  true  dependencytree    angular cli       pacote       normalize package data       hosted git info         isminimumfixversionavailable  true  minimumfixversion   hosted git info             packagetype   javascript node js   packagename   hosted git info   packageversion           packagefilepaths     istransitivedependency  true  dependencytree    angular cli       npm package arg       hosted git info         isminimumfixversionavailable  true  minimumfixversion   hosted git info             basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   the package hosted git info before       are vulnerable to regular expression denial of service  redos  via regular expression shortcutmatch in the fromurl function in index js  the affected regular expression exhibits polynomial worst case time complexity    vulnerabilityurl        ,0
784968,27591405604.0,IssuesEvent,2023-03-09 00:51:51,michaelrsweet/pappl,https://api.github.com/repos/michaelrsweet/pappl,closed,papplDevice Improvements for Default Schemes,enhancement priority-high,"**Is your feature request related to a problem? Please describe.**
The CUPS 2.x USB backend provides quirk support - quirks can help in some cases when the device has a known issue which we can workaround, or it can reject the device in case its USB support is utterly broken.

**Describe the solution you'd like**
Provide a quirk support where files can be read from /usr/share/pappl/quirks/* and from /etc/pappl/quirks/* with higher priority, where printer application maintainers and admins can put quirk files regarding their devices.

**Describe alternatives you've considered**
This might be solved on printer application level as well, but a generic support in PAPPL would be great.",1.0,"papplDevice Improvements for Default Schemes - **Is your feature request related to a problem? Please describe.**
The CUPS 2.x USB backend provides quirk support - quirks can help in some cases when the device has a known issue which we can workaround, or it can reject the device in case its USB support is utterly broken.

**Describe the solution you'd like**
Provide a quirk support where files can be read from /usr/share/pappl/quirks/* and from /etc/pappl/quirks/* with higher priority, where printer application maintainers and admins can put quirk files regarding their devices.

**Describe alternatives you've considered**
This might be solved on printer application level as well, but a generic support in PAPPL would be great.",0,pappldevice improvements for default schemes     is your feature request related to a problem  please describe     the cups   x usb backend provides quirk support   quirks can help in some cases when the device has a known issue which we can workaround  or it can reject the device in case its usb support is utterly broken       describe the solution you d like    provide a quirk support where files can be read from  usr share pappl quirks   and from  etc pappl quirks   with higher priority  where printer application maintainers and admins can put quirk files regarding their devices       describe alternatives you ve considered    this might be solved on printer application level as well  but a generic support in pappl would be great ,0
48052,12140371639.0,IssuesEvent,2020-04-23 20:25:32,tensorflow/tensorflow,https://api.github.com/repos/tensorflow/tensorflow,closed,libcuda.so.1 is missing with conda env tf-gpu,stat:awaiting response type:build/install,"I get the following errors:

```
2020-04-19 05:56:24.050072: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'libcuda.so.1'; dlerror: libcuda.so.1: cannot open shared object file: No such file or directory
2020-04-19 05:56:24.050125: E tensorflow/stream_executor/cuda/cuda_driver.cc:351] failed call to cuInit: UNKNOWN ERROR (303)
2020-04-19 05:56:24.050149: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:163] no NVIDIA GPU device is present: /dev/nvidia0 does not exist
2020-04-19 05:56:24.050476: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: SSE4.1 SSE4.2 AVX AVX2 FMA
2020-04-19 05:56:24.066026: I tensorflow/core/platform/profile_utils/cpu_utils.cc:94] CPU Frequency: 2199900000 Hz
2020-04-19 05:56:24.068548: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x558e75a5b2c0 initialized for platform Host (this does not guarantee that XLA will be used). Devices:
2020-04-19 05:56:24.068591: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Host, Default Version
WARNING:root:Limited tf.compat.v2.summary API due to missing TensorBoard installation.
WARNING:root:Limited tf.compat.v2.summary API due to missing TensorBoard installation.
WARNING:root:Limited tf.compat.v2.summary API due to missing TensorBoard installation.
```
when I execute
```
 trainds = tf.data.Dataset.from_tensor_slices((helper.trainx,helper.trainm,helper.trainy)).batch(setup['BatchSize'])
```
Tensorflow cannot find the file libcuda.so.1.

I get this error in a Docker Container which uses miniconda and the tensorflow-gpu environment.
```
FROM continuumio/miniconda3
RUN conda create -n tf-gpu tensorflow-gpu
```
I don't get the error on my local machine with the same code.

As far as I understood, conda should automatically install cuda and its libraries.

When I search for the missing file I get an empty line. `find -name ""libcuda.so.1""`
Other versions of libcuda.so. can't be found either. Even `*cuda*` couldn't be found. It seems to be that cuda was entirely skipped during the installation. 

nvidia-smi returns this:
```
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 410.104      Driver Version: 410.104      CUDA Version: N/A      |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  Tesla P100-SXM2...  Off  | 00000000:89:00.0 Off |                    0 |
| N/A   30C    P0    31W / 300W |      0MiB / 16280MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|  No running processes found                                                 |
+-----------------------------------------------------------------------------+
```

**System information**
```
Python 3.7.6 | packaged by conda-forge | (default, Mar 23 2020, 23:03:20)
[GCC 7.3.0] on linux
```
- TensorFlow version: 2.1.0
- Python version: 3.7.6
- GPU model and memory: P100 / 16 GB

Additional information:
```
print(tf.test.is_gpu_available())             # False
print(tf.config.list_physical_devices('GPU')) # []
```


",1.0,"libcuda.so.1 is missing with conda env tf-gpu - I get the following errors:

```
2020-04-19 05:56:24.050072: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'libcuda.so.1'; dlerror: libcuda.so.1: cannot open shared object file: No such file or directory
2020-04-19 05:56:24.050125: E tensorflow/stream_executor/cuda/cuda_driver.cc:351] failed call to cuInit: UNKNOWN ERROR (303)
2020-04-19 05:56:24.050149: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:163] no NVIDIA GPU device is present: /dev/nvidia0 does not exist
2020-04-19 05:56:24.050476: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: SSE4.1 SSE4.2 AVX AVX2 FMA
2020-04-19 05:56:24.066026: I tensorflow/core/platform/profile_utils/cpu_utils.cc:94] CPU Frequency: 2199900000 Hz
2020-04-19 05:56:24.068548: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x558e75a5b2c0 initialized for platform Host (this does not guarantee that XLA will be used). Devices:
2020-04-19 05:56:24.068591: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Host, Default Version
WARNING:root:Limited tf.compat.v2.summary API due to missing TensorBoard installation.
WARNING:root:Limited tf.compat.v2.summary API due to missing TensorBoard installation.
WARNING:root:Limited tf.compat.v2.summary API due to missing TensorBoard installation.
```
when I execute
```
 trainds = tf.data.Dataset.from_tensor_slices((helper.trainx,helper.trainm,helper.trainy)).batch(setup['BatchSize'])
```
Tensorflow cannot find the file libcuda.so.1.

I get this error in a Docker Container which uses miniconda and the tensorflow-gpu environment.
```
FROM continuumio/miniconda3
RUN conda create -n tf-gpu tensorflow-gpu
```
I don't get the error on my local machine with the same code.

As far as I understood, conda should automatically install cuda and its libraries.

When I search for the missing file I get an empty line. `find -name ""libcuda.so.1""`
Other versions of libcuda.so. can't be found either. Even `*cuda*` couldn't be found. It seems to be that cuda was entirely skipped during the installation. 

nvidia-smi returns this:
```
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 410.104      Driver Version: 410.104      CUDA Version: N/A      |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  Tesla P100-SXM2...  Off  | 00000000:89:00.0 Off |                    0 |
| N/A   30C    P0    31W / 300W |      0MiB / 16280MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|  No running processes found                                                 |
+-----------------------------------------------------------------------------+
```

**System information**
```
Python 3.7.6 | packaged by conda-forge | (default, Mar 23 2020, 23:03:20)
[GCC 7.3.0] on linux
```
- TensorFlow version: 2.1.0
- Python version: 3.7.6
- GPU model and memory: P100 / 16 GB

Additional information:
```
print(tf.test.is_gpu_available())             # False
print(tf.config.list_physical_devices('GPU')) # []
```


",0,libcuda so   is missing with conda env tf gpu   i get the following errors                         w tensorflow stream executor platform default dso loader cc    could not load dynamic library  libcuda so     dlerror  libcuda so    cannot open shared object file  no such file or directory                 e tensorflow stream executor cuda cuda driver cc    failed call to cuinit  unknown error                     i tensorflow stream executor cuda cuda diagnostics cc    no nvidia gpu device is present   dev   does not exist                 i tensorflow core platform cpu feature guard cc    your cpu supports instructions that this tensorflow binary was not compiled to use          avx   fma                 i tensorflow core platform profile utils cpu utils cc    cpu frequency    hz                 i tensorflow compiler xla service service cc    xla service   initialized for platform host  this does not guarantee that xla will be used   devices                  i tensorflow compiler xla service service cc      streamexecutor device      host  default version  warning root limited tf compat   summary api due to missing tensorboard installation   warning root limited tf compat   summary api due to missing tensorboard installation   warning root limited tf compat   summary api due to missing tensorboard installation        when i execute        trainds   tf data dataset from tensor slices  helper trainx helper trainm helper trainy   batch setup         tensorflow cannot find the file libcuda so       i get this error in a docker container which uses miniconda and the tensorflow gpu environment        from continuumio    run conda create  n tf gpu tensorflow gpu       i don t get the error on my local machine with the same code     as far as i understood  conda should automatically install cuda and its libraries     when i search for the missing file i get an empty line   find  name  libcuda so      other versions of libcuda so  can t be found either  even   cuda   couldn t be found  it seems to be that cuda was entirely skipped during the installation      nvidia smi returns this                                                                                           nvidia smi          driver version           cuda version  n a                                                                                            gpu  name        persistence m  bus id        disp a   volatile uncorr  ecc      fan  temp  perf  pwr usage cap          memory usage   gpu util  compute m                                                                                             tesla         off            off                             n a                                               default                                                                                                                                                                          processes                                                        gpu memory       gpu       pid   type   process name                             usage                                                                                             no running processes found                                                                                                                                              system information         python         packaged by conda forge    default  mar                on linux         tensorflow version           python version           gpu model and memory        gb    additional information        print tf test is gpu available                  false  print tf config list physical devices  gpu                  ,0
675784,23105915684.0,IssuesEvent,2022-07-27 08:47:57,aura-nw/Aura-Safe,https://api.github.com/repos/aura-nw/Aura-Safe,opened,[Aura-safe][Transaction] Không execute thành công transaction trên Evmos do lấy sai link hash,bug priority high,"## Description
Không execute thành công transaction trên Evmos do lấy sai link transaction hash
Link sai: https://testnet.mintscan.io/evmos-testnet/transaction/AE35BCB8F3DA1E059BE9C6B92095CCF1E55F0C0181903C08DFB271F4CF643B76
Link đúng: https://testnet.mintscan.io/evmos-testnet/txs/AE35BCB8F3DA1E059BE9C6B92095CCF1E55F0C0181903C08DFB271F4CF643B76
## Environment
 - Browser: Chrome
 - Wallet: Keplr
 - Safe: evmos1rzkrw3z6xxf7zd2gfkv4n82dzr8hmyq3g00dhf
 - Environment: https://safe.serenity.aura.network/
   - testnet

## Steps to reproduce
 1. Go to https://safe.serenity.aura.network/
 2. Connect wallet and select Evmos safe
 3. Creat send funds transaction with correct data and valid amount
 4. All owner select execute transaction
 5. See error

## Expected result
Hiển thị đúng link transaction hash.
Thực hiện execute thành công transaction
## Screenshots
![Screen Shot 2022-07-27 at 15 39 13](https://user-images.githubusercontent.com/102220123/181204124-b9651cc2-ca6d-4e1d-9af7-721718cdb0cb.png)
",1.0,"[Aura-safe][Transaction] Không execute thành công transaction trên Evmos do lấy sai link hash - ## Description
Không execute thành công transaction trên Evmos do lấy sai link transaction hash
Link sai: https://testnet.mintscan.io/evmos-testnet/transaction/AE35BCB8F3DA1E059BE9C6B92095CCF1E55F0C0181903C08DFB271F4CF643B76
Link đúng: https://testnet.mintscan.io/evmos-testnet/txs/AE35BCB8F3DA1E059BE9C6B92095CCF1E55F0C0181903C08DFB271F4CF643B76
## Environment
 - Browser: Chrome
 - Wallet: Keplr
 - Safe: evmos1rzkrw3z6xxf7zd2gfkv4n82dzr8hmyq3g00dhf
 - Environment: https://safe.serenity.aura.network/
   - testnet

## Steps to reproduce
 1. Go to https://safe.serenity.aura.network/
 2. Connect wallet and select Evmos safe
 3. Creat send funds transaction with correct data and valid amount
 4. All owner select execute transaction
 5. See error

## Expected result
Hiển thị đúng link transaction hash.
Thực hiện execute thành công transaction
## Screenshots
![Screen Shot 2022-07-27 at 15 39 13](https://user-images.githubusercontent.com/102220123/181204124-b9651cc2-ca6d-4e1d-9af7-721718cdb0cb.png)
",0,   không execute thành công transaction trên evmos do lấy sai link hash      description  không execute thành công transaction trên evmos do lấy sai link transaction hash  link sai     link đúng        environment     browser  chrome     wallet  keplr     safe        environment          testnet       steps to reproduce      go to        connect wallet and select evmos safe      creat send funds transaction with correct data and valid amount      all owner select execute transaction      see error       expected result  hiển thị đúng link transaction hash   thực hiện execute thành công transaction     screenshots        ,0
40879,10587952447.0,IssuesEvent,2019-10-08 23:59:27,elastic/elasticsearch,https://api.github.com/repos/elastic/elasticsearch,closed,PluginBuildPluginTests fails on Mac,:Core/Infra/Build >test-failure,"This test was failing for me locally and not in CI, but turns out it's failing in our Darwin CI builds as well:

https://gradle-enterprise.elastic.co/s/t3qxgarzcyfls

Something about the randomized runner thread leak detection is tripping only on OSX. We might want to reevaluate whether we want to use any of the randomized runner stuff in `buildSrc` tests at all. We aren't actually using any of the random input capabilities, and I suspect this is just copy/paste from the regular ES code.",1.0,"PluginBuildPluginTests fails on Mac - This test was failing for me locally and not in CI, but turns out it's failing in our Darwin CI builds as well:

https://gradle-enterprise.elastic.co/s/t3qxgarzcyfls

Something about the randomized runner thread leak detection is tripping only on OSX. We might want to reevaluate whether we want to use any of the randomized runner stuff in `buildSrc` tests at all. We aren't actually using any of the random input capabilities, and I suspect this is just copy/paste from the regular ES code.",0,pluginbuildplugintests fails on mac   this test was failing for me locally and not in ci  but turns out it s failing in our darwin ci builds as well          something about the randomized runner thread leak detection is tripping only on osx  we might want to reevaluate whether we want to use any of the randomized runner stuff in  buildsrc  tests at all  we aren t actually using any of the random input capabilities  and i suspect this is just copy paste from the regular es code ,0
35368,12322265012.0,IssuesEvent,2020-05-13 10:03:00,fufunoyu/example-npm-circle,https://api.github.com/repos/fufunoyu/example-npm-circle,opened,WS-2019-0333 (Medium) detected in handlebars-4.5.2.tgz,security vulnerability,"## WS-2019-0333 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>handlebars-4.5.2.tgz</b></p></summary>

<p>Handlebars provides the power necessary to let you build semantic templates effectively with no frustration</p>
<p>Library home page: <a href=""https://registry.npmjs.org/handlebars/-/handlebars-4.5.2.tgz"">https://registry.npmjs.org/handlebars/-/handlebars-4.5.2.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/example-npm-circle/package.json</p>
<p>Path to vulnerable library: /example-npm-circle/node_modules/handlebars/package.json</p>
<p>

Dependency Hierarchy:
  - :x: **handlebars-4.5.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/fufunoyu/example-npm-circle/commit/e8f81fa1be5b23fbe5cdb37ae0a33abd6cc0741e"">e8f81fa1be5b23fbe5cdb37ae0a33abd6cc0741e</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
Prototype Pollution vulnerability found in handlebars 1.0.6 before 4.5.3. It is possible to add or modify properties to the Object prototype through a malicious template. Attacker may crash the application or execute Arbitrary Code in specific conditions.

<p>Publish Date: 2019-11-18
<p>URL: <a href=https://github.com/wycats/handlebars.js/commit/f7f05d7558e674856686b62a00cde5758f3b7a08>WS-2019-0333</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>5.0</b>)</summary>
<p>

Base Score Metrics not available</p>

</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://www.npmjs.com/advisories/1325"">https://www.npmjs.com/advisories/1325</a></p>
<p>Release Date: 2019-12-05</p>
<p>Fix Resolution: handlebars - 4.5.3</p>

</p>
</details>
<p></p>
",True,"WS-2019-0333 (Medium) detected in handlebars-4.5.2.tgz - ## WS-2019-0333 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>handlebars-4.5.2.tgz</b></p></summary>

<p>Handlebars provides the power necessary to let you build semantic templates effectively with no frustration</p>
<p>Library home page: <a href=""https://registry.npmjs.org/handlebars/-/handlebars-4.5.2.tgz"">https://registry.npmjs.org/handlebars/-/handlebars-4.5.2.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/example-npm-circle/package.json</p>
<p>Path to vulnerable library: /example-npm-circle/node_modules/handlebars/package.json</p>
<p>

Dependency Hierarchy:
  - :x: **handlebars-4.5.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/fufunoyu/example-npm-circle/commit/e8f81fa1be5b23fbe5cdb37ae0a33abd6cc0741e"">e8f81fa1be5b23fbe5cdb37ae0a33abd6cc0741e</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
Prototype Pollution vulnerability found in handlebars 1.0.6 before 4.5.3. It is possible to add or modify properties to the Object prototype through a malicious template. Attacker may crash the application or execute Arbitrary Code in specific conditions.

<p>Publish Date: 2019-11-18
<p>URL: <a href=https://github.com/wycats/handlebars.js/commit/f7f05d7558e674856686b62a00cde5758f3b7a08>WS-2019-0333</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>5.0</b>)</summary>
<p>

Base Score Metrics not available</p>

</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://www.npmjs.com/advisories/1325"">https://www.npmjs.com/advisories/1325</a></p>
<p>Release Date: 2019-12-05</p>
<p>Fix Resolution: handlebars - 4.5.3</p>

</p>
</details>
<p></p>
",0,ws      medium  detected in handlebars       tgz      ws       medium severity vulnerability     vulnerable library    handlebars       tgz      handlebars provides the power necessary to let you build semantic templates effectively with no frustration   library home page   a href     path to dependency file   tmp ws scm example npm circle package json   path to vulnerable library   example npm circle node modules handlebars package json     dependency hierarchy       x    handlebars       tgz    vulnerable library   found in head commit   a href               vulnerability details         prototype pollution vulnerability found in handlebars       before        it is possible to add or modify properties to the object prototype through a malicious template  attacker may crash the application or execute arbitrary code in specific conditions    publish date         url   a href              cvss   score details             base score metrics not available              suggested fix      type  upgrade version   origin   a href     release date          fix resolution  handlebars                  ,0
70447,9417147156.0,IssuesEvent,2019-04-10 16:04:13,golang/go,https://api.github.com/repos/golang/go,closed,gopls returns ToUTF16Column: point is missing offset on `textDocument/rangeFormatting``,Documentation gopls,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.12.1 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/bstaletic/.cache/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/bstaletic/go""
GOPROXY=""""
GORACE=""""
GOROOT=""/usr/lib/go""
GOTMPDIR=""""
GOTOOLDIR=""/usr/lib/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build434682588=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

Whenever I try to execute a `textDocument/rangeFormatting` request, gopls responds with `Request failed: 0: ToUTF16Column: point is missing offset`

### What did you expect to see?

Properly formatted part of file.

### What did you see instead?

The exception above and this in the gopls log:

```
[Trace - 4:17:20 PM] Sending request 'initialize - (1)'.
Params: {""capabilities"": {""textDocument"": {""completion"": {""completionItemKind"": {""valueSet"": [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25]}}}}, ""initializationOptions"": {}, ""processId"": 16204, ""rootPath"": ""/home/bstaletic/.vim/pack/bundle/start/YouCompleteMe/third_party/ycmd/ycmd/tests/go/go_module"", ""rootUri"": ""file:///home/bstaletic/.vim/pack/bundle/start/YouCompleteMe/third_party/ycmd/ycmd/tests/go/go_module""}


[Trace - 4:17:20 PM] Received response 'initialize - (1)' in 2ms.
Params: {""capabilities"":{""textDocumentSync"":{""openClose"":true,""change"":1},""hoverProvider"":true,""completionProvider"":{""triggerCharacters"":["".""]},""signatureHelpProvider"":{""triggerCharacters"":[""("","",""]},""definitionProvider"":true,""documentHighlightProvider"":true,""documentSymbolProvider"":true,""codeActionProvider"":true,""documentFormattingProvider"":true,""documentRangeFormattingProvider"":true,""typeDefinitionProvider"":true},""custom"":null}


[Trace - 4:17:20 PM] Sending notification 'initialized'.
Params: {}


[Trace - 4:17:20 PM] Sending notification 'workspace/didChangeConfiguration'.
Params: {""settings"": {}}


[Trace - 4:17:20 PM] Received notification 'window/logMessage'.
Params: {""type"":1,""message"":""method \""DidChangeConfiguration\"" not yet implemented""}


[Trace - 4:17:20 PM] Sending notification 'textDocument/didOpen'.
Params: {""textDocument"": {""languageId"": ""go"", ""text"": ""// Package td is dummy data for gocode completion test.\npackage td\n\nimport (\n\t\""log\""\n)\n\nfunc Hello() {\n\tlog.Log\n}\n"", ""uri"": ""file:///home/bstaletic/.vim/pack/bundle/start/YouCompleteMe/third_party/ycmd/ycmd/tests/go/go_module/td/test.go"", ""version"": 1}}


[Trace - 4:17:21 PM] Received notification 'textDocument/publishDiagnostics'.
Params: {""uri"":""file:///home/bstaletic/.vim/pack/bundle/start/YouCompleteMe/third_party/ycmd/ycmd/tests/go/go_module/td/test.go"",""diagnostics"":[{""range"":{""start"":{""line"":8,""character"":5},""end"":{""line"":8,""character"":8}},""severity"":1,""source"":""LSP"",""message"":""Log not declared by package log""}]}


[Trace - 4:17:21 PM] Received notification 'textDocument/publishDiagnostics'.
Params: {""uri"":""file:///home/bstaletic/.vim/pack/bundle/start/YouCompleteMe/third_party/ycmd/ycmd/tests/go/go_module/td/test2.go"",""diagnostics"":[]}


[Trace - 4:17:31 PM] Sending request 'textDocument/rangeFormatting - (2)'.
Params: {""options"": {""insertSpaces"": false, ""tabSize"": 8}, ""range"": {""end"": {""character"": 0, ""line"": 6}, ""start"": {""character"": 0, ""line"": 3}}, ""textDocument"": {""uri"": ""file:///home/bstaletic/.vim/pack/bundle/start/YouCompleteMe/third_party/ycmd/ycmd/tests/go/go_module/td/test.go""}}


[Error - 4:17:31 PM] send textDocument/rangeFormatting""2"" ToUTF16Column: point is missing offset


[Trace - 4:21:13 PM] Sending request 'textDocument/rangeFormatting - (3)'.
Params: {""options"": {""insertSpaces"": false, ""tabSize"": 8}, ""range"": {""end"": {""character"": 0, ""line"": 6}, ""start"": {""character"": 0, ""line"": 3}}, ""textDocument"": {""uri"": ""file:///home/bstaletic/.vim/pack/bundle/start/YouCompleteMe/third_party/ycmd/ycmd/tests/go/go_module/td/test.go""}}


[Error - 4:21:13 PM] send textDocument/rangeFormatting""3"" ToUTF16Column: point is missing offset
```",1.0,"gopls returns ToUTF16Column: point is missing offset on `textDocument/rangeFormatting`` - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.12.1 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/bstaletic/.cache/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/bstaletic/go""
GOPROXY=""""
GORACE=""""
GOROOT=""/usr/lib/go""
GOTMPDIR=""""
GOTOOLDIR=""/usr/lib/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build434682588=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

Whenever I try to execute a `textDocument/rangeFormatting` request, gopls responds with `Request failed: 0: ToUTF16Column: point is missing offset`

### What did you expect to see?

Properly formatted part of file.

### What did you see instead?

The exception above and this in the gopls log:

```
[Trace - 4:17:20 PM] Sending request 'initialize - (1)'.
Params: {""capabilities"": {""textDocument"": {""completion"": {""completionItemKind"": {""valueSet"": [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25]}}}}, ""initializationOptions"": {}, ""processId"": 16204, ""rootPath"": ""/home/bstaletic/.vim/pack/bundle/start/YouCompleteMe/third_party/ycmd/ycmd/tests/go/go_module"", ""rootUri"": ""file:///home/bstaletic/.vim/pack/bundle/start/YouCompleteMe/third_party/ycmd/ycmd/tests/go/go_module""}


[Trace - 4:17:20 PM] Received response 'initialize - (1)' in 2ms.
Params: {""capabilities"":{""textDocumentSync"":{""openClose"":true,""change"":1},""hoverProvider"":true,""completionProvider"":{""triggerCharacters"":["".""]},""signatureHelpProvider"":{""triggerCharacters"":[""("","",""]},""definitionProvider"":true,""documentHighlightProvider"":true,""documentSymbolProvider"":true,""codeActionProvider"":true,""documentFormattingProvider"":true,""documentRangeFormattingProvider"":true,""typeDefinitionProvider"":true},""custom"":null}


[Trace - 4:17:20 PM] Sending notification 'initialized'.
Params: {}


[Trace - 4:17:20 PM] Sending notification 'workspace/didChangeConfiguration'.
Params: {""settings"": {}}


[Trace - 4:17:20 PM] Received notification 'window/logMessage'.
Params: {""type"":1,""message"":""method \""DidChangeConfiguration\"" not yet implemented""}


[Trace - 4:17:20 PM] Sending notification 'textDocument/didOpen'.
Params: {""textDocument"": {""languageId"": ""go"", ""text"": ""// Package td is dummy data for gocode completion test.\npackage td\n\nimport (\n\t\""log\""\n)\n\nfunc Hello() {\n\tlog.Log\n}\n"", ""uri"": ""file:///home/bstaletic/.vim/pack/bundle/start/YouCompleteMe/third_party/ycmd/ycmd/tests/go/go_module/td/test.go"", ""version"": 1}}


[Trace - 4:17:21 PM] Received notification 'textDocument/publishDiagnostics'.
Params: {""uri"":""file:///home/bstaletic/.vim/pack/bundle/start/YouCompleteMe/third_party/ycmd/ycmd/tests/go/go_module/td/test.go"",""diagnostics"":[{""range"":{""start"":{""line"":8,""character"":5},""end"":{""line"":8,""character"":8}},""severity"":1,""source"":""LSP"",""message"":""Log not declared by package log""}]}


[Trace - 4:17:21 PM] Received notification 'textDocument/publishDiagnostics'.
Params: {""uri"":""file:///home/bstaletic/.vim/pack/bundle/start/YouCompleteMe/third_party/ycmd/ycmd/tests/go/go_module/td/test2.go"",""diagnostics"":[]}


[Trace - 4:17:31 PM] Sending request 'textDocument/rangeFormatting - (2)'.
Params: {""options"": {""insertSpaces"": false, ""tabSize"": 8}, ""range"": {""end"": {""character"": 0, ""line"": 6}, ""start"": {""character"": 0, ""line"": 3}}, ""textDocument"": {""uri"": ""file:///home/bstaletic/.vim/pack/bundle/start/YouCompleteMe/third_party/ycmd/ycmd/tests/go/go_module/td/test.go""}}


[Error - 4:17:31 PM] send textDocument/rangeFormatting""2"" ToUTF16Column: point is missing offset


[Trace - 4:21:13 PM] Sending request 'textDocument/rangeFormatting - (3)'.
Params: {""options"": {""insertSpaces"": false, ""tabSize"": 8}, ""range"": {""end"": {""character"": 0, ""line"": 6}, ""start"": {""character"": 0, ""line"": 3}}, ""textDocument"": {""uri"": ""file:///home/bstaletic/.vim/pack/bundle/start/YouCompleteMe/third_party/ycmd/ycmd/tests/go/go_module/td/test.go""}}


[Error - 4:21:13 PM] send textDocument/rangeFormatting""3"" ToUTF16Column: point is missing offset
```",1,gopls returns    point is missing offset on  textdocument rangeformatting              what version of go are you using   go version            go version  go version       linux             does this issue reproduce with the latest release     yes         what operating system and processor architecture are you using   go env          go env  output       go env  goarch      gobin     gocache   home bstaletic  cache go build   goexe     goflags     gohostarch      gohostos  linux   goos  linux   gopath   home bstaletic go   goproxy     gorace     goroot   usr lib go   gotmpdir     gotooldir   usr lib go pkg tool linux     gccgo  gccgo   cc  gcc   cxx  g     cgo enabled      gomod     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches             what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best          whenever i try to execute a  textdocument rangeformatting  request  gopls responds with  request failed        point is missing offset         what did you expect to see     properly formatted part of file         what did you see instead     the exception above and this in the gopls log            sending request  initialize          params    capabilities     textdocument     completion     completionitemkind     valueset           initializationoptions        processid       rootpath     home bstaletic  vim pack bundle start youcompleteme third party ycmd ycmd tests go go module    rooturi    file    home bstaletic  vim pack bundle start youcompleteme third party ycmd ycmd tests go go module          received response  initialize        in     params    capabilities    textdocumentsync    openclose  true  change      hoverprovider  true  completionprovider    triggercharacters      signaturehelpprovider    triggercharacters      definitionprovider  true  documenthighlightprovider  true  documentsymbolprovider  true  codeactionprovider  true  documentformattingprovider  true  documentrangeformattingprovider  true  typedefinitionprovider  true   custom  null         sending notification  initialized    params            sending notification  workspace didchangeconfiguration    params    settings              received notification  window logmessage    params    type     message   method   didchangeconfiguration   not yet implemented          sending notification  textdocument didopen    params    textdocument     languageid    go    text       package td is dummy data for gocode completion test  npackage td n nimport   n t  log   n  n nfunc hello     n tlog log n  n    uri    file    home bstaletic  vim pack bundle start youcompleteme third party ycmd ycmd tests go go module td test go    version              received notification  textdocument publishdiagnostics    params    uri   file    home bstaletic  vim pack bundle start youcompleteme third party ycmd ycmd tests go go module td test go   diagnostics            received notification  textdocument publishdiagnostics    params    uri   file    home bstaletic  vim pack bundle start youcompleteme third party ycmd ycmd tests go go module td   go   diagnostics            sending request  textdocument rangeformatting          params    options     insertspaces   false   tabsize        range     end     character       line        start     character       line         textdocument     uri    file    home bstaletic  vim pack bundle start youcompleteme third party ycmd ycmd tests go go module td test go           send textdocument rangeformatting       point is missing offset        sending request  textdocument rangeformatting          params    options     insertspaces   false   tabsize        range     end     character       line        start     character       line         textdocument     uri    file    home bstaletic  vim pack bundle start youcompleteme third party ycmd ycmd tests go go module td test go           send textdocument rangeformatting       point is missing offset     ,1
19536,4422077823.0,IssuesEvent,2016-08-16 00:23:16,golang/go,https://api.github.com/repos/golang/go,closed,encoding/json: explain how to properly Marshall RawMessage,Documentation,"encoding/json has an example for Unmarshalling `json.RawMessage` but not for Marshalling it. The example doesn't point out that Marshalling requires a `*RawMessage`. Using `RawMessage` doesn't give the expected results and it's not immediately obvious why.
https://play.golang.org/p/A1nbikzzVY",1.0,"encoding/json: explain how to properly Marshall RawMessage - encoding/json has an example for Unmarshalling `json.RawMessage` but not for Marshalling it. The example doesn't point out that Marshalling requires a `*RawMessage`. Using `RawMessage` doesn't give the expected results and it's not immediately obvious why.
https://play.golang.org/p/A1nbikzzVY",1,encoding json  explain how to properly marshall rawmessage   encoding json has an example for unmarshalling  json rawmessage  but not for marshalling it  the example doesn t point out that marshalling requires a   rawmessage   using  rawmessage  doesn t give the expected results and it s not immediately obvious why    ,1
192131,15339717270.0,IssuesEvent,2021-02-27 03:14:01,golang/go,https://api.github.com/repos/golang/go,closed,doc: Go 1.16 Release Notes has a broken golang.org link,Documentation,"In https://golang.org/doc/go1.16 where it says

> `ReadDir` => `os.ReadDir` (note: returns a slice of `os.DirEntry` rather than a slice of `fs.FileInfo`)

the hyperlink on `fs.FileInfo` goes to https://golang.org/pkg/fs/#FileInfo rather than to https://golang.org/pkg/io/fs/#FileInfo (the `io/` is missing).",1.0,"doc: Go 1.16 Release Notes has a broken golang.org link - In https://golang.org/doc/go1.16 where it says

> `ReadDir` => `os.ReadDir` (note: returns a slice of `os.DirEntry` rather than a slice of `fs.FileInfo`)

the hyperlink on `fs.FileInfo` goes to https://golang.org/pkg/fs/#FileInfo rather than to https://golang.org/pkg/io/fs/#FileInfo (the `io/` is missing).",1,doc  go     release notes has a broken golang org link   in   where it says       readdir      os readdir   note  returns a slice of  os direntry  rather than a slice of  fs fileinfo      the hyperlink on  fs fileinfo  goes to   rather than to    the  io   is missing  ,1
109934,11671523477.0,IssuesEvent,2020-03-04 03:29:24,golang/go,https://api.github.com/repos/golang/go,closed,doc: About Golang memory model-The loop in main is not guaranteed to finish.,Documentation,"> Another incorrect idiom is busy waiting for a value, as in:
> 
```
var a string
var done bool

func setup() {
	a = ""hello, world""
	done = true
}

func main() {
	go setup()
	for !done {
	}
	print(a)
}
```
> As before, there is no guarantee that, in main, observing the write to done implies observing the write to a, so this program could print an empty string too. Worse, there is no guarantee that the write to done will ever be observed by main, since there are no synchronization events between the two threads. The loop in main is not guaranteed to finish.
> 

this code from https://golang.org/ref/mem#tmp_2

what is mean The loop in main is not guaranteed to finish？is only happens on single core cpu or all mulit core cpus.

I run test on it，the main is all always finish。",1.0,"doc: About Golang memory model-The loop in main is not guaranteed to finish. - > Another incorrect idiom is busy waiting for a value, as in:
> 
```
var a string
var done bool

func setup() {
	a = ""hello, world""
	done = true
}

func main() {
	go setup()
	for !done {
	}
	print(a)
}
```
> As before, there is no guarantee that, in main, observing the write to done implies observing the write to a, so this program could print an empty string too. Worse, there is no guarantee that the write to done will ever be observed by main, since there are no synchronization events between the two threads. The loop in main is not guaranteed to finish.
> 

this code from https://golang.org/ref/mem#tmp_2

what is mean The loop in main is not guaranteed to finish？is only happens on single core cpu or all mulit core cpus.

I run test on it，the main is all always finish。",1,doc  about golang memory model the loop in main is not guaranteed to finish      another incorrect idiom is busy waiting for a value  as in            var a string  var done bool    func setup      	a    hello  world   	done   true       func main      	go setup    	for  done    	   	print a             as before  there is no guarantee that  in main  observing the write to done implies observing the write to a  so this program could print an empty string too  worse  there is no guarantee that the write to done will ever be observed by main  since there are no synchronization events between the two threads  the loop in main is not guaranteed to finish         this code from      what is mean the loop in main is not guaranteed to finish？is only happens on single core cpu or all mulit core cpus     i run test on it，the main is all always finish。,1
527276,15339325850.0,IssuesEvent,2021-02-27 01:33:11,DASSL/ClassDB,https://api.github.com/repos/DASSL/ClassDB,opened,Connection log import fails on Postgres 13 (W),priority high wrong,"Running the function `classdb.importConnectionLog` on an instance of Postgres 13 fails to import any data. Here is an example of the result table the function returns when the function is run without any parameter:

 logdate |  numconnections | numdisconnections | info |
:------ | :------ | :------ | :------ |
 2021-02-26T00:00:00Z | 0 | 0 | extra data after last expected column |

I plan to edit the issue in about an hour from now with some diagnostic information.",1.0,"Connection log import fails on Postgres 13 (W) - Running the function `classdb.importConnectionLog` on an instance of Postgres 13 fails to import any data. Here is an example of the result table the function returns when the function is run without any parameter:

 logdate |  numconnections | numdisconnections | info |
:------ | :------ | :------ | :------ |
 2021-02-26T00:00:00Z | 0 | 0 | extra data after last expected column |

I plan to edit the issue in about an hour from now with some diagnostic information.",0,connection log import fails on postgres    w    running the function  classdb importconnectionlog  on an instance of postgres   fails to import any data  here is an example of the result table the function returns when the function is run without any parameter      logdate    numconnections   numdisconnections   info                                                                  extra data after last expected column      i plan to edit the issue in about an hour from now with some diagnostic information ,0
49895,7545566991.0,IssuesEvent,2018-04-17 22:08:30,golang/go,https://api.github.com/repos/golang/go,closed,encoding/json: documented behavior unmarshaling JSON null into json.Unmarshaler is unclear,Documentation,"### What version of Go are you using (`go version`)?

1.10.1

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

N/A

### What did you do?

I read the documentation for `json.Unmarshal` and `json.Unmarshaler.UnmarshalJSON`, and the relevant code:

https://github.com/golang/go/blob/568d4848f672ecec3f9199452e9da1776a9fbba9/src/encoding/json/decode.go#L482-L494

### What did you expect to see?

A statement to the effect that `json.Unmarshal` will zero the value before calling `json.Unmarshaler.UnmarshalJSON`.

### What did you see instead?

According to the documentation, `json.Unmarshal` passes `null` to `json.Unmarshaler.UnmarshalJSON`. However, it doesn't explain that, prior to making the call, it sets the field to the zero value.

This is hinted at in the documentation for `json.Unmarshaler`, wherein it requires treating null inputs as a no-op, but this leaves the reader wondering what state the field is left in if it wasn't already the zero value.",1.0,"encoding/json: documented behavior unmarshaling JSON null into json.Unmarshaler is unclear - ### What version of Go are you using (`go version`)?

1.10.1

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

N/A

### What did you do?

I read the documentation for `json.Unmarshal` and `json.Unmarshaler.UnmarshalJSON`, and the relevant code:

https://github.com/golang/go/blob/568d4848f672ecec3f9199452e9da1776a9fbba9/src/encoding/json/decode.go#L482-L494

### What did you expect to see?

A statement to the effect that `json.Unmarshal` will zero the value before calling `json.Unmarshaler.UnmarshalJSON`.

### What did you see instead?

According to the documentation, `json.Unmarshal` passes `null` to `json.Unmarshaler.UnmarshalJSON`. However, it doesn't explain that, prior to making the call, it sets the field to the zero value.

This is hinted at in the documentation for `json.Unmarshaler`, wherein it requires treating null inputs as a no-op, but this leaves the reader wondering what state the field is left in if it wasn't already the zero value.",1,encoding json  documented behavior unmarshaling json null into json unmarshaler is unclear       what version of go are you using   go version                    does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env       n a        what did you do     i read the documentation for  json unmarshal  and  json unmarshaler unmarshaljson   and the relevant code              what did you expect to see     a statement to the effect that  json unmarshal  will zero the value before calling  json unmarshaler unmarshaljson          what did you see instead     according to the documentation   json unmarshal  passes  null  to  json unmarshaler unmarshaljson   however  it doesn t explain that  prior to making the call  it sets the field to the zero value     this is hinted at in the documentation for  json unmarshaler   wherein it requires treating null inputs as a no op  but this leaves the reader wondering what state the field is left in if it wasn t already the zero value ,1
26813,5289694231.0,IssuesEvent,2017-02-08 17:59:40,golang/go,https://api.github.com/repos/golang/go,closed,crypto/tls: session resumption (session id caching),Documentation,"### What version of Go are you using (`go version`)?

`go version go1.7.4 darwin/amd64`

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
```

### What did you do?
I have 2 web servers, one that supports TLS session resumption based on a session cache and another that supports session cache and session tickets.

https://play.golang.org/p/9n4OZRjqHh

### What did you expect to see?

I had expected the 2nd connection to each server to resume the session.

### What did you see instead?

`DidResume` is only `true` for the server that supports session _ticket_ resumption.

It appears that session ID caching is not supported in client or server mode. Perhaps the documentation for `ClientSessionCache` could be a bit more explicit that it is only a cache for session tickets.",1.0,"crypto/tls: session resumption (session id caching) - ### What version of Go are you using (`go version`)?

`go version go1.7.4 darwin/amd64`

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
```

### What did you do?
I have 2 web servers, one that supports TLS session resumption based on a session cache and another that supports session cache and session tickets.

https://play.golang.org/p/9n4OZRjqHh

### What did you expect to see?

I had expected the 2nd connection to each server to resume the session.

### What did you see instead?

`DidResume` is only `true` for the server that supports session _ticket_ resumption.

It appears that session ID caching is not supported in client or server mode. Perhaps the documentation for `ClientSessionCache` could be a bit more explicit that it is only a cache for session tickets.",1,crypto tls  session resumption  session id caching        what version of go are you using   go version        go version       darwin           what operating system and processor architecture are you using   go env          goarch      gobin     goexe     gohostarch      gohostos  darwin   goos  darwin              what did you do   i have   web servers  one that supports tls session resumption based on a session cache and another that supports session cache and session tickets              what did you expect to see     i had expected the   connection to each server to resume the session         what did you see instead      didresume  is only  true  for the server that supports session  ticket  resumption     it appears that session id caching is not supported in client or server mode  perhaps the documentation for  clientsessioncache  could be a bit more explicit that it is only a cache for session tickets ,1
23409,4934276302.0,IssuesEvent,2016-11-28 18:37:24,golang/go,https://api.github.com/repos/golang/go,closed,net/mail: not clear that Header.Get is case insensitive,Documentation NeedsFix,"Reading the godoc:

```
    func (h Header) Get(key string) string

Get gets the first value associated with the given key. If there are no values associated with the key, Get returns """".
```

It's not immediately obvious that `key` is not case sensitive. As it turns out, `Get(""From"")` and `Get(""from"")` mean the same because internally this all goes through https://golang.org/pkg/net/textproto/#CanonicalMIMEHeaderKey.

Perhaps this is just me not being used to MIME Headers being canonical in this way. But I think a sentence like ""note that key is case insensitive as it is canonicalized"" would help some people. The `net/mail` godoc does not mention MIME headers anywhere either.

Perhaps this should go in `net/textproto` too, even though that's much closer to the actual `CanonicalMIMEHeaderKey` func.",1.0,"net/mail: not clear that Header.Get is case insensitive - Reading the godoc:

```
    func (h Header) Get(key string) string

Get gets the first value associated with the given key. If there are no values associated with the key, Get returns """".
```

It's not immediately obvious that `key` is not case sensitive. As it turns out, `Get(""From"")` and `Get(""from"")` mean the same because internally this all goes through https://golang.org/pkg/net/textproto/#CanonicalMIMEHeaderKey.

Perhaps this is just me not being used to MIME Headers being canonical in this way. But I think a sentence like ""note that key is case insensitive as it is canonicalized"" would help some people. The `net/mail` godoc does not mention MIME headers anywhere either.

Perhaps this should go in `net/textproto` too, even though that's much closer to the actual `CanonicalMIMEHeaderKey` func.",1,net mail  not clear that header get is case insensitive   reading the godoc              func  h header  get key string  string    get gets the first value associated with the given key  if there are no values associated with the key  get returns             it s not immediately obvious that  key  is not case sensitive  as it turns out   get  from    and  get  from    mean the same because internally this all goes through      perhaps this is just me not being used to mime headers being canonical in this way  but i think a sentence like  note that key is case insensitive as it is canonicalized  would help some people  the  net mail  godoc does not mention mime headers anywhere either     perhaps this should go in  net textproto  too  even though that s much closer to the actual  canonicalmimeheaderkey  func ,1
50504,7607055011.0,IssuesEvent,2018-04-30 15:16:18,golang/go,https://api.github.com/repos/golang/go,closed,"doc: ""Go's New Brand"" / Brand Book (pdf)",Documentation,"Most probably it's a non-issue, though changing to Go proportionally-spaced font from Go monospaced on p19 in the Brand Book (pdf) might make the Brand Book more branded.
https://golang.org/s/brandbook

### What did you do?
Had a look at the pdf.

### What did you expect to see?
When I saw the Go font mentioned, I expected the text in proportionally-spaced font.

### What did you see instead?
Text in monospaced font.
",1.0,"doc: ""Go's New Brand"" / Brand Book (pdf) - Most probably it's a non-issue, though changing to Go proportionally-spaced font from Go monospaced on p19 in the Brand Book (pdf) might make the Brand Book more branded.
https://golang.org/s/brandbook

### What did you do?
Had a look at the pdf.

### What did you expect to see?
When I saw the Go font mentioned, I expected the text in proportionally-spaced font.

### What did you see instead?
Text in monospaced font.
",1,doc   go s new brand    brand book  pdf    most probably it s a non issue  though changing to go proportionally spaced font from go monospaced on   in the brand book  pdf  might make the brand book more branded            what did you do   had a look at the pdf         what did you expect to see   when i saw the go font mentioned  i expected the text in proportionally spaced font         what did you see instead   text in monospaced font   ,1
9031,8507691046.0,IssuesEvent,2018-10-30 19:48:05,terraform-providers/terraform-provider-aws,https://api.github.com/repos/terraform-providers/terraform-provider-aws,closed,CloudWatch Alarm ignores Threshold when comparison op is LessThan*,bug service/cloudwatch,"If you try to create a cloudwatch alarm that steps down on say, CPU Reservation for an ECS cluster, it creates something like this in AWS:

https://screencast.com/t/iNySsTAjcG

As compared to the GreaterThan version:

https://screencast.com/t/BZrmNmV4yQkB

### Terraform Version
10.8.0

### Affected Resource(s)
Please list the resources as a list, for example:
- aws_cloudwatch_metric_alarm

If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.

### Terraform Configuration Files
```hcl

variable ""name"" {
  description = ""The name of the ECS Cluster.""
}


variable ""min_size"" {
  description = ""The min number of EC2 Instances to run in the ECS Cluster.""
  default=1
}

variable ""max_size"" {
  description = ""The max number of EC2 Instances to run in the ECS Cluster.""
  default=2
}


variable ""instance_type"" {
  description = ""The type of EC2 Instance to deploy in the ECS Cluster (e.g. t2.micro).""
}

variable ""vpc_id"" {
  description = ""The ID of the VPC in which to deploy the ECS Cluster.""
}

variable ""subnet_ids"" {
  description = ""The subnet IDs in which to deploy the EC2 Instances of the ECS Cluster.""
}



variable ""key_pair_name"" {
  description = ""The name of an EC2 Key Pair to associate with each EC2 Instance in the ECS Cluster. Leave blank to not associate a Key Pair.""
  default = ""amdirent-aws""
}

variable ""allow_ssh_from_cidr_blocks"" {
  description = ""The list of CIDR-formatted IP address ranges from which the EC2 Instances in the ECS Cluster should accept SSH connections.""
  type = ""list""
  default = [""0.0.0.0/0""]
}
# ---------------------------------------------------------------------------------------------------------------------
# CREATE AN ECS CLUSTER
# ---------------------------------------------------------------------------------------------------------------------

resource ""aws_ecs_cluster"" ""example_cluster"" {
  name = ""${var.name}""
}

# ---------------------------------------------------------------------------------------------------------------------
# DEPLOY AN AUTO SCALING GROUP (ASG)
# Each EC2 Instance in the ASG will register as an ECS Cluster Instance.
# ---------------------------------------------------------------------------------------------------------------------

resource ""aws_autoscaling_policy"" ""high_cpu_policy"" {
  name                   = ""${var.name}-high-cpu-asg-policy""
  adjustment_type        = ""ChangeInCapacity""
  autoscaling_group_name = ""${aws_autoscaling_group.ecs_cluster_instances.name}""
  policy_type=""StepScaling""

  step_adjustment {
    scaling_adjustment = -1
    metric_interval_lower_bound = 0
  }
}



resource ""aws_cloudwatch_metric_alarm"" ""unused-cpu-trigger"" {
  alarm_name          = ""${var.name}-too-much-cpu-asg-alarm""
  comparison_operator = ""LessThanOrEqualToThreshold""
  evaluation_periods  = ""2""
  metric_name         = ""CPUReservation""
  namespace           = ""AWS/ECS""
  period              = ""60""
  statistic           = ""Average""
  threshold           = ""60""

  dimensions {
    ClusterName=""${var.name}""
  }

  alarm_description = ""This metric monitors too much CPU for new service tasks""
  alarm_actions     = [""${aws_autoscaling_policy.high_cpu_policy.arn}""]
}

resource ""aws_autoscaling_group"" ""ecs_cluster_instances"" {
  name = ""${var.name}-ecs-asg""
  min_size = ""${var.min_size}""
  max_size = ""${var.max_size}""
  launch_configuration = ""${aws_launch_configuration.ecs_instance.name}""
  vpc_zone_identifier = [""${split("","", var.subnet_ids)}""]

  tag {
    key = ""Name""
    value = ""${var.name}""
    propagate_at_launch = true
  }

  enabled_metrics = [""GroupMinSize"", ""GroupMaxSize"", ""GroupDesiredCapacity"", ""GroupInServiceInstances"", ""GroupPendingInstances"", ""GroupTerminatingInstances"", ""GroupStandbyInstances"", ""GroupTotalInstances""]
}

# Fetch the AWS ECS Optimized Linux AMI. Note that if you've never launched this AMI before, you have to accept the
# terms and conditions on this webpage or the EC2 instances will fail to launch:
# https://aws.amazon.com/marketplace/pp/B00U6QTYI2
data ""aws_ami"" ""ecs"" {
  most_recent = true
  owners = [""amazon""]
  filter {
    name = ""name""
    values = [""amzn-ami-*-amazon-ecs-optimized""]
  }
}


resource ""aws_launch_configuration"" ""ecs_instance"" {
  name_prefix = ""${var.name}-ec2""
  instance_type = ""${var.instance_type}""
  key_name = ""${var.key_pair_name}""
  iam_instance_profile = ""${aws_iam_instance_profile.ecs_instance.name}""
  security_groups = [""${aws_security_group.ecs_instance.id}""]
  image_id = ""${data.aws_ami.ecs.id}""
  associate_public_ip_address = false
  enable_monitoring = true

  # A shell script that will execute when on each EC2 instance when it first boots to configure the ECS Agent to talk
  # to the right ECS cluster
  user_data = ""${data.template_file.user_data.rendered}""

  # https://terraform.io/docs/configuration/resources.html
  lifecycle {
    create_before_destroy = true
  }
}

data ""template_file"" ""user_data"" {
  template = <<EOF
#!/bin/bash
echo ""ECS_CLUSTER=${var.name}"" >> /etc/ecs/ecs.config
EOF
}

# ---------------------------------------------------------------------------------------------------------------------
# CREATE AN IAM ROLE FOR EACH INSTANCE IN THE CLUSTER
# We export the IAM role ID as an output variable so users of this module can attach custom policies.
# ---------------------------------------------------------------------------------------------------------------------

resource ""aws_iam_role"" ""ecs_instance"" {
  name = ""${var.name}_ecs_instance_role""
  assume_role_policy = ""${data.aws_iam_policy_document.ecs_instance.json}""

  # aws_iam_instance_profile.ecs_instance sets create_before_destroy to true, which means every resource it depends on,
  # including this one, must also set the create_before_destroy flag to true, or you'll get a cyclic dependency error.
  lifecycle {
    create_before_destroy = true
  }
}

data ""aws_iam_policy_document"" ""ecs_instance"" {
  statement {
    effect = ""Allow""
    actions = [""sts:AssumeRole""]
    principals {
      type = ""Service""
      identifiers = [""ec2.amazonaws.com"", ""application-autoscaling.amazonaws.com""]
    }
  }
}

resource ""aws_iam_role_policy"" ""ecr_pull"" {
  name = ""${var.name}-ecr-reader-for-ecs-instance-policy""
  role     = ""${aws_iam_role.ecs_instance.id}""
  policy = <<EOF
{
  ""Version"": ""2012-10-17"",
  ""Statement"": [{
    ""Effect"": ""Allow"",
    ""Action"": [
      ""ecr:GetAuthorizationToken"",
      ""ecr:BatchCheckLayerAvailability"",
      ""ecr:GetDownloadUrlForLayer"",
      ""ecr:GetRepositoryPolicy"",
      ""ecr:DescribeRepositories"",
      ""ecr:ListImages"",
      ""ecr:DescribeImages"",
      ""ecr:BatchGetImage""
    ],
    ""Resource"": ""*""
  }]
}
EOF
}

# To attach an IAM Role to an EC2 Instance, you use an IAM Instance Profile
resource ""aws_iam_instance_profile"" ""ecs_instance"" {
  name = ""${var.name}""
  role = ""${aws_iam_role.ecs_instance.name}""

  # aws_launch_configuration.ecs_instance sets create_before_destroy to true, which means every resource it depends on,
  # including this one, must also set the create_before_destroy flag to true, or you'll get a cyclic dependency error.
  lifecycle {
    create_before_destroy = true
  }
}


# ---------------------------------------------------------------------------------------------------------------------
# ATTACH IAM POLICIES TO THE IAM ROLE
# The IAM policy allows an ECS Agent running on each EC2 Instance to communicate with the ECS scheduler.
# ---------------------------------------------------------------------------------------------------------------------

resource ""aws_iam_role_policy"" ""ecs_cluster_permissions"" {
  name = ""${var.name}-ecs-cluster-permissions""
  role = ""${aws_iam_role.ecs_instance.id}""
  policy = ""${data.aws_iam_policy_document.ecs_cluster_permissions.json}""
}

data ""aws_iam_policy_document"" ""ecs_cluster_permissions"" {
  statement {
    effect = ""Allow""
    resources = [""*""]
    actions = [
      ""ecs:CreateCluster"",
      ""ecs:DeregisterContainerInstance"",
      ""ecs:DiscoverPollEndpoint"",
      ""ecs:Poll"",
      ""ecs:RegisterContainerInstance"",
      ""ecs:StartTelemetrySession"",
      ""ecs:Submit*"",
      ""ecs:UpdateService"",
      ""cloudwatch:DescribeAlarms"",
      ""ecs:DescribeServices""
    ]
  }
}

# ---------------------------------------------------------------------------------------------------------------------
# CREATE A SECURITY GROUP THAT CONTROLS WHAT TRAFFIC CAN GO IN AND OUT OF THE CLUSTER
# We export the ID of the group as an output variable so users of this module can attach custom rules.
# ---------------------------------------------------------------------------------------------------------------------

resource ""aws_security_group"" ""ecs_instance"" {
  name = ""${var.name} ECS Cluster""
  description = ""Security group for the EC2 instances in the ECS cluster ${var.name}""
  vpc_id = ""${var.vpc_id}""

  # aws_launch_configuration.ecs_instance sets create_before_destroy to true, which means every resource it depends on,
  # including this one, must also set the create_before_destroy flag to true, or you'll get a cyclic dependency error.
  lifecycle {
    create_before_destroy = true
  }
}

resource ""aws_security_group_rule"" ""all_outbound_all"" {
  type = ""egress""
  from_port = 0
  to_port = 0
  protocol = ""-1""
  cidr_blocks = [""0.0.0.0/0""]
  security_group_id = ""${aws_security_group.ecs_instance.id}""
}

resource ""aws_security_group_rule"" ""all_inbound_all"" {
  type = ""ingress""
  from_port = 0
  to_port = 0
  protocol = ""-1""
  cidr_blocks = [""0.0.0.0/0""]
  security_group_id = ""${aws_security_group.ecs_instance.id}""
}
```

### Debug Output
https://gist.github.com/bhgames/ca2fd82dac7ef64d08c37a1451689d53

### Panic Output
Nope

### Expected Behavior
Should have set ""60"" as the proper top threshold so I had 60 >= CPU Reservation >= -Infinity instead of the weird >= CPU Res >= -Infinity which doesnt work. Have to go in to edit by hand.

### Actual Behavior

Puts in >= CPU Res >= -Infinity which doesnt work. Have to go in to edit by hand to add the threshold.

### Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
1. `terraform apply`

### Important Factoids
Are there anything atypical about your accounts that we should know? For example: Running in EC2 Classic? Custom version of OpenStack? Tight ACLs?

### References
Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:
- GH-1234
",1.0,"CloudWatch Alarm ignores Threshold when comparison op is LessThan* - If you try to create a cloudwatch alarm that steps down on say, CPU Reservation for an ECS cluster, it creates something like this in AWS:

https://screencast.com/t/iNySsTAjcG

As compared to the GreaterThan version:

https://screencast.com/t/BZrmNmV4yQkB

### Terraform Version
10.8.0

### Affected Resource(s)
Please list the resources as a list, for example:
- aws_cloudwatch_metric_alarm

If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.

### Terraform Configuration Files
```hcl

variable ""name"" {
  description = ""The name of the ECS Cluster.""
}


variable ""min_size"" {
  description = ""The min number of EC2 Instances to run in the ECS Cluster.""
  default=1
}

variable ""max_size"" {
  description = ""The max number of EC2 Instances to run in the ECS Cluster.""
  default=2
}


variable ""instance_type"" {
  description = ""The type of EC2 Instance to deploy in the ECS Cluster (e.g. t2.micro).""
}

variable ""vpc_id"" {
  description = ""The ID of the VPC in which to deploy the ECS Cluster.""
}

variable ""subnet_ids"" {
  description = ""The subnet IDs in which to deploy the EC2 Instances of the ECS Cluster.""
}



variable ""key_pair_name"" {
  description = ""The name of an EC2 Key Pair to associate with each EC2 Instance in the ECS Cluster. Leave blank to not associate a Key Pair.""
  default = ""amdirent-aws""
}

variable ""allow_ssh_from_cidr_blocks"" {
  description = ""The list of CIDR-formatted IP address ranges from which the EC2 Instances in the ECS Cluster should accept SSH connections.""
  type = ""list""
  default = [""0.0.0.0/0""]
}
# ---------------------------------------------------------------------------------------------------------------------
# CREATE AN ECS CLUSTER
# ---------------------------------------------------------------------------------------------------------------------

resource ""aws_ecs_cluster"" ""example_cluster"" {
  name = ""${var.name}""
}

# ---------------------------------------------------------------------------------------------------------------------
# DEPLOY AN AUTO SCALING GROUP (ASG)
# Each EC2 Instance in the ASG will register as an ECS Cluster Instance.
# ---------------------------------------------------------------------------------------------------------------------

resource ""aws_autoscaling_policy"" ""high_cpu_policy"" {
  name                   = ""${var.name}-high-cpu-asg-policy""
  adjustment_type        = ""ChangeInCapacity""
  autoscaling_group_name = ""${aws_autoscaling_group.ecs_cluster_instances.name}""
  policy_type=""StepScaling""

  step_adjustment {
    scaling_adjustment = -1
    metric_interval_lower_bound = 0
  }
}



resource ""aws_cloudwatch_metric_alarm"" ""unused-cpu-trigger"" {
  alarm_name          = ""${var.name}-too-much-cpu-asg-alarm""
  comparison_operator = ""LessThanOrEqualToThreshold""
  evaluation_periods  = ""2""
  metric_name         = ""CPUReservation""
  namespace           = ""AWS/ECS""
  period              = ""60""
  statistic           = ""Average""
  threshold           = ""60""

  dimensions {
    ClusterName=""${var.name}""
  }

  alarm_description = ""This metric monitors too much CPU for new service tasks""
  alarm_actions     = [""${aws_autoscaling_policy.high_cpu_policy.arn}""]
}

resource ""aws_autoscaling_group"" ""ecs_cluster_instances"" {
  name = ""${var.name}-ecs-asg""
  min_size = ""${var.min_size}""
  max_size = ""${var.max_size}""
  launch_configuration = ""${aws_launch_configuration.ecs_instance.name}""
  vpc_zone_identifier = [""${split("","", var.subnet_ids)}""]

  tag {
    key = ""Name""
    value = ""${var.name}""
    propagate_at_launch = true
  }

  enabled_metrics = [""GroupMinSize"", ""GroupMaxSize"", ""GroupDesiredCapacity"", ""GroupInServiceInstances"", ""GroupPendingInstances"", ""GroupTerminatingInstances"", ""GroupStandbyInstances"", ""GroupTotalInstances""]
}

# Fetch the AWS ECS Optimized Linux AMI. Note that if you've never launched this AMI before, you have to accept the
# terms and conditions on this webpage or the EC2 instances will fail to launch:
# https://aws.amazon.com/marketplace/pp/B00U6QTYI2
data ""aws_ami"" ""ecs"" {
  most_recent = true
  owners = [""amazon""]
  filter {
    name = ""name""
    values = [""amzn-ami-*-amazon-ecs-optimized""]
  }
}


resource ""aws_launch_configuration"" ""ecs_instance"" {
  name_prefix = ""${var.name}-ec2""
  instance_type = ""${var.instance_type}""
  key_name = ""${var.key_pair_name}""
  iam_instance_profile = ""${aws_iam_instance_profile.ecs_instance.name}""
  security_groups = [""${aws_security_group.ecs_instance.id}""]
  image_id = ""${data.aws_ami.ecs.id}""
  associate_public_ip_address = false
  enable_monitoring = true

  # A shell script that will execute when on each EC2 instance when it first boots to configure the ECS Agent to talk
  # to the right ECS cluster
  user_data = ""${data.template_file.user_data.rendered}""

  # https://terraform.io/docs/configuration/resources.html
  lifecycle {
    create_before_destroy = true
  }
}

data ""template_file"" ""user_data"" {
  template = <<EOF
#!/bin/bash
echo ""ECS_CLUSTER=${var.name}"" >> /etc/ecs/ecs.config
EOF
}

# ---------------------------------------------------------------------------------------------------------------------
# CREATE AN IAM ROLE FOR EACH INSTANCE IN THE CLUSTER
# We export the IAM role ID as an output variable so users of this module can attach custom policies.
# ---------------------------------------------------------------------------------------------------------------------

resource ""aws_iam_role"" ""ecs_instance"" {
  name = ""${var.name}_ecs_instance_role""
  assume_role_policy = ""${data.aws_iam_policy_document.ecs_instance.json}""

  # aws_iam_instance_profile.ecs_instance sets create_before_destroy to true, which means every resource it depends on,
  # including this one, must also set the create_before_destroy flag to true, or you'll get a cyclic dependency error.
  lifecycle {
    create_before_destroy = true
  }
}

data ""aws_iam_policy_document"" ""ecs_instance"" {
  statement {
    effect = ""Allow""
    actions = [""sts:AssumeRole""]
    principals {
      type = ""Service""
      identifiers = [""ec2.amazonaws.com"", ""application-autoscaling.amazonaws.com""]
    }
  }
}

resource ""aws_iam_role_policy"" ""ecr_pull"" {
  name = ""${var.name}-ecr-reader-for-ecs-instance-policy""
  role     = ""${aws_iam_role.ecs_instance.id}""
  policy = <<EOF
{
  ""Version"": ""2012-10-17"",
  ""Statement"": [{
    ""Effect"": ""Allow"",
    ""Action"": [
      ""ecr:GetAuthorizationToken"",
      ""ecr:BatchCheckLayerAvailability"",
      ""ecr:GetDownloadUrlForLayer"",
      ""ecr:GetRepositoryPolicy"",
      ""ecr:DescribeRepositories"",
      ""ecr:ListImages"",
      ""ecr:DescribeImages"",
      ""ecr:BatchGetImage""
    ],
    ""Resource"": ""*""
  }]
}
EOF
}

# To attach an IAM Role to an EC2 Instance, you use an IAM Instance Profile
resource ""aws_iam_instance_profile"" ""ecs_instance"" {
  name = ""${var.name}""
  role = ""${aws_iam_role.ecs_instance.name}""

  # aws_launch_configuration.ecs_instance sets create_before_destroy to true, which means every resource it depends on,
  # including this one, must also set the create_before_destroy flag to true, or you'll get a cyclic dependency error.
  lifecycle {
    create_before_destroy = true
  }
}


# ---------------------------------------------------------------------------------------------------------------------
# ATTACH IAM POLICIES TO THE IAM ROLE
# The IAM policy allows an ECS Agent running on each EC2 Instance to communicate with the ECS scheduler.
# ---------------------------------------------------------------------------------------------------------------------

resource ""aws_iam_role_policy"" ""ecs_cluster_permissions"" {
  name = ""${var.name}-ecs-cluster-permissions""
  role = ""${aws_iam_role.ecs_instance.id}""
  policy = ""${data.aws_iam_policy_document.ecs_cluster_permissions.json}""
}

data ""aws_iam_policy_document"" ""ecs_cluster_permissions"" {
  statement {
    effect = ""Allow""
    resources = [""*""]
    actions = [
      ""ecs:CreateCluster"",
      ""ecs:DeregisterContainerInstance"",
      ""ecs:DiscoverPollEndpoint"",
      ""ecs:Poll"",
      ""ecs:RegisterContainerInstance"",
      ""ecs:StartTelemetrySession"",
      ""ecs:Submit*"",
      ""ecs:UpdateService"",
      ""cloudwatch:DescribeAlarms"",
      ""ecs:DescribeServices""
    ]
  }
}

# ---------------------------------------------------------------------------------------------------------------------
# CREATE A SECURITY GROUP THAT CONTROLS WHAT TRAFFIC CAN GO IN AND OUT OF THE CLUSTER
# We export the ID of the group as an output variable so users of this module can attach custom rules.
# ---------------------------------------------------------------------------------------------------------------------

resource ""aws_security_group"" ""ecs_instance"" {
  name = ""${var.name} ECS Cluster""
  description = ""Security group for the EC2 instances in the ECS cluster ${var.name}""
  vpc_id = ""${var.vpc_id}""

  # aws_launch_configuration.ecs_instance sets create_before_destroy to true, which means every resource it depends on,
  # including this one, must also set the create_before_destroy flag to true, or you'll get a cyclic dependency error.
  lifecycle {
    create_before_destroy = true
  }
}

resource ""aws_security_group_rule"" ""all_outbound_all"" {
  type = ""egress""
  from_port = 0
  to_port = 0
  protocol = ""-1""
  cidr_blocks = [""0.0.0.0/0""]
  security_group_id = ""${aws_security_group.ecs_instance.id}""
}

resource ""aws_security_group_rule"" ""all_inbound_all"" {
  type = ""ingress""
  from_port = 0
  to_port = 0
  protocol = ""-1""
  cidr_blocks = [""0.0.0.0/0""]
  security_group_id = ""${aws_security_group.ecs_instance.id}""
}
```

### Debug Output
https://gist.github.com/bhgames/ca2fd82dac7ef64d08c37a1451689d53

### Panic Output
Nope

### Expected Behavior
Should have set ""60"" as the proper top threshold so I had 60 >= CPU Reservation >= -Infinity instead of the weird >= CPU Res >= -Infinity which doesnt work. Have to go in to edit by hand.

### Actual Behavior

Puts in >= CPU Res >= -Infinity which doesnt work. Have to go in to edit by hand to add the threshold.

### Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
1. `terraform apply`

### Important Factoids
Are there anything atypical about your accounts that we should know? For example: Running in EC2 Classic? Custom version of OpenStack? Tight ACLs?

### References
Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:
- GH-1234
",0,cloudwatch alarm ignores threshold when comparison op is lessthan    if you try to create a cloudwatch alarm that steps down on say  cpu reservation for an ecs cluster  it creates something like this in aws          as compared to the greaterthan version              terraform version               affected resource s   please list the resources as a list  for example     aws cloudwatch metric alarm    if this issue appears to affect multiple resources  it may be an issue with terraform s core  so please mention this         terraform configuration files     hcl    variable  name       description    the name of the ecs cluster           variable  min size       description    the min number of   instances to run in the ecs cluster      default         variable  max size       description    the max number of   instances to run in the ecs cluster      default           variable  instance type       description    the type of   instance to deploy in the ecs cluster  e g    micro          variable  vpc id       description    the id of the vpc in which to deploy the ecs cluster         variable  subnet ids       description    the subnet ids in which to deploy the   instances of the ecs cluster             variable  key pair name       description    the name of an   key pair to associate with each   instance in the ecs cluster  leave blank to not associate a key pair      default    amdirent aws        variable  allow ssh from cidr blocks       description    the list of cidr formatted ip address ranges from which the   instances in the ecs cluster should accept ssh connections      type    list     default                                                                                                                                    create an ecs cluster                                                                                                                             resource  aws ecs cluster   example cluster       name      var name                                                                                                                                    deploy an auto scaling group  asg     each   instance in the asg will register as an ecs cluster instance                                                                                                                              resource  aws autoscaling policy   high cpu policy       name                        var name  high cpu asg policy     adjustment type           changeincapacity     autoscaling group name      aws autoscaling group ecs cluster instances name      policy type  stepscaling       step adjustment        scaling adjustment           metric interval lower bound                    resource  aws cloudwatch metric alarm   unused cpu trigger       alarm name               var name  too much cpu asg alarm     comparison operator    lessthanorequaltothreshold     evaluation periods           metric name            cpureservation     namespace              aws ecs     period                       statistic              average     threshold                      dimensions        clustername    var name             alarm description    this metric monitors too much cpu for new service tasks     alarm actions               resource  aws autoscaling group   ecs cluster instances       name      var name  ecs asg     min size      var min size      max size      var max size      launch configuration      aws launch configuration ecs instance name      vpc zone identifier          tag        key    name       value      var name        propagate at launch   true           enabled metrics             fetch the aws ecs optimized linux ami  note that if you ve never launched this ami before  you have to accept the    terms and conditions on this webpage or the   instances will fail to launch        data  aws ami   ecs       most recent   true    owners        filter        name    name       values                  resource  aws launch configuration   ecs instance       name prefix      var name        instance type      var instance type      key name      var key pair name      iam instance profile      aws iam instance profile ecs instance name      security groups        image id      data aws ami ecs id      associate public ip address   false    enable monitoring   true        a shell script that will execute when on each   instance when it first boots to configure the ecs agent to talk      to the right ecs cluster    user data      data template file user data rendered               lifecycle        create before destroy   true            data  template file   user data       template     eof     bin bash  echo  ecs cluster   var name       etc ecs ecs config  eof                                                                                                                                  create an iam role for each instance in the cluster    we export the iam role id as an output variable so users of this module can attach custom policies                                                                                                                              resource  aws iam role   ecs instance       name      var name  ecs instance role     assume role policy      data aws iam policy document ecs instance json          aws iam instance profile ecs instance sets create before destroy to true  which means every resource it depends on       including this one  must also set the create before destroy flag to true  or you ll get a cyclic dependency error     lifecycle        create before destroy   true            data  aws iam policy document   ecs instance       statement        effect    allow       actions          principals          type    service         identifiers                       resource  aws iam role policy   ecr pull       name      var name  ecr reader for ecs instance policy     role          aws iam role ecs instance id      policy     eof        version                statement            effect    allow         action             ecr getauthorizationtoken           ecr batchchecklayeravailability           ecr getdownloadurlforlayer           ecr getrepositorypolicy           ecr describerepositories           ecr listimages           ecr describeimages           ecr batchgetimage                resource                 eof         to attach an iam role to an   instance  you use an iam instance profile  resource  aws iam instance profile   ecs instance       name      var name      role      aws iam role ecs instance name          aws launch configuration ecs instance sets create before destroy to true  which means every resource it depends on       including this one  must also set the create before destroy flag to true  or you ll get a cyclic dependency error     lifecycle        create before destroy   true                                                                                                                                         attach iam policies to the iam role    the iam policy allows an ecs agent running on each   instance to communicate with the ecs scheduler                                                                                                                              resource  aws iam role policy   ecs cluster permissions       name      var name  ecs cluster permissions     role      aws iam role ecs instance id      policy      data aws iam policy document ecs cluster permissions json         data  aws iam policy document   ecs cluster permissions       statement        effect    allow       resources          actions             ecs createcluster           ecs deregistercontainerinstance           ecs discoverpollendpoint           ecs poll           ecs registercontainerinstance           ecs starttelemetrysession           ecs submit            ecs updateservice           cloudwatch describealarms           ecs describeservices                                                                                                                                               create a security group that controls what traffic can go in and out of the cluster    we export the id of the group as an output variable so users of this module can attach custom rules                                                                                                                              resource  aws security group   ecs instance       name      var name  ecs cluster     description    security group for the   instances in the ecs cluster   var name      vpc id      var vpc id          aws launch configuration ecs instance sets create before destroy to true  which means every resource it depends on       including this one  must also set the create before destroy flag to true  or you ll get a cyclic dependency error     lifecycle        create before destroy   true            resource  aws security group rule   all outbound all       type    egress     from port        to port        protocol           cidr blocks        security group id      aws security group ecs instance id         resource  aws security group rule   all inbound all       type    ingress     from port        to port        protocol           cidr blocks        security group id      aws security group ecs instance id                  debug output           panic output  nope        expected behavior  should have set     as the proper top threshold so i had      cpu reservation     infinity instead of the weird    cpu res     infinity which doesnt work  have to go in to edit by hand         actual behavior    puts in    cpu res     infinity which doesnt work  have to go in to edit by hand to add the threshold         steps to reproduce  please list the steps required to reproduce the issue  for example       terraform apply         important factoids  are there anything atypical about your accounts that we should know  for example  running in   classic  custom version of openstack  tight acls         references  are there any other github issues  open or closed  or pull requests that should be linked here  for example     gh    ,0
211419,16444338085.0,IssuesEvent,2021-05-20 17:41:36,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.17: document os changes for Go 1.17,Documentation NeedsInvestigation help wanted release-blocker,"As of filing this issue, the [Go 1.17 draft release notes](https://tip.golang.org/doc/go1.17) contained the following HTML:

<dl id=""os""><dt><a href=""/pkg/os/"">os</a></dt>
  <dd>
    <p><!-- CL 268020 -->
      TODO: <a href=""https://golang.org/cl/268020"">https://golang.org/cl/268020</a>: avoid allocation in File.WriteString
    </p>
  </dd>
</dl>

---

This TODO needs to be resolved by July 1 so that we can have complete release notes for [Beta 1](https://golang.org/s/release#june-1--december-1-beta-1-issued).

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.17:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.17) and include ""For #44513. Fixes #46018."" in the body.",1.0,"doc/go1.17: document os changes for Go 1.17 - As of filing this issue, the [Go 1.17 draft release notes](https://tip.golang.org/doc/go1.17) contained the following HTML:

<dl id=""os""><dt><a href=""/pkg/os/"">os</a></dt>
  <dd>
    <p><!-- CL 268020 -->
      TODO: <a href=""https://golang.org/cl/268020"">https://golang.org/cl/268020</a>: avoid allocation in File.WriteString
    </p>
  </dd>
</dl>

---

This TODO needs to be resolved by July 1 so that we can have complete release notes for [Beta 1](https://golang.org/s/release#june-1--december-1-beta-1-issued).

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.17:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.17) and include ""For #44513. Fixes #46018."" in the body.",1,doc      document os changes for go       as of filing this issue  the     contained the following html      os                    todo   a href    avoid allocation in file writestring                   this todo needs to be resolved by july   so that we can have complete release notes for      a sequence of steps to resolve this issue may be      come up with a draft release note entry in this issue  then move the issue to needsfix state     send a cl with  doc           and include  for     fixes      in the body ,1
276135,20970537493.0,IssuesEvent,2022-03-28 10:56:25,golang/go,https://api.github.com/repos/golang/go,closed,net/netip: inconsistent terminology for IPv4-mapped IPv6 addresses in documentation,Documentation help wanted NeedsFix,"<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.18 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What did you do?

Read https://pkg.go.dev/net/netip@go1.18

### What did you expect to see?

A consistent name for IPv4 addresses wrapped in IPv6 addresses.

### What did you see instead?

Many different names or phrases have appeared in the documentation, and they seem to refer to the same thing:

- IPv4-mapped IPv6 address
- IP4-mapped IPv6 address
- IPv6-mapped IPv4 address
- v6-mapped form
- v6-mapped IPv6 address
- v6-mapped IPv4 IP



",1.0,"net/netip: inconsistent terminology for IPv4-mapped IPv6 addresses in documentation - <!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.18 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What did you do?

Read https://pkg.go.dev/net/netip@go1.18

### What did you expect to see?

A consistent name for IPv4 addresses wrapped in IPv6 addresses.

### What did you see instead?

Many different names or phrases have appeared in the documentation, and they seem to refer to the same thing:

- IPv4-mapped IPv6 address
- IP4-mapped IPv6 address
- IPv6-mapped IPv4 address
- v6-mapped form
- v6-mapped IPv6 address
- v6-mapped IPv4 IP



",1,net netip  inconsistent terminology for   mapped   addresses in documentation         please answer these questions before submitting your issue  thanks              what version of go are you using   go version            go version  go version     linux             does this issue reproduce with the latest release     yes        what did you do     read          what did you expect to see     a consistent name for   addresses wrapped in   addresses         what did you see instead     many different names or phrases have appeared in the documentation  and they seem to refer to the same thing         mapped   address      mapped   address      mapped   address      mapped form      mapped   address      mapped   ip        ,1
431060,30215611768.0,IssuesEvent,2023-07-05 15:22:48,golang/go,https://api.github.com/repos/golang/go,closed,runtime/metrics: update documentation w.r.t. stack_sys,Documentation NeedsFix compiler/runtime,"### What version of Go are you using (`go version`)?

```
$ go version 
go1.20
```
### Issue

The documentation related to stack memory in `MemStats` says:

```
        // StackInuse is bytes in stack spans.
	//
	// In-use stack spans have at least one stack in them. These
	// spans can only be used for other stacks of the same size.
	//
	// There is no StackIdle because unused stack spans are
	// returned to the heap (and hence counted toward HeapIdle).
	StackInuse [uint64](https://pkg.go.dev/builtin#uint64)

	// StackSys is bytes of stack memory obtained from the OS.
	//
	// StackSys is StackInuse, plus any memory obtained directly
	// from the OS for OS thread stacks (which should be minimal).
	StackSys [uint64](https://pkg.go.dev/builtin#uint64)
```

And, in runtime/metrics, there is also:

```
/memory/classes/heap/stacks:bytes
	Memory allocated from the heap that is reserved for stack
	space, whether or not it is currently in-use.

/memory/classes/os-stacks:bytes
	Stack memory allocated by the underlying operating system.
```

But this is at best confusing and at worst incorrect. Quoting @mknyszek from a recent conversation:

> if a program is pure Go, we use newosproc0 to allocate the first stack. this accounts to stacks_sys, which funnels into StackSys. all other system stacks are allocated from the same pool as goroutine stacks (basically, StackInuse). 8192 bytes.
if a program is cgo, then we use _cgo_sys_thread_create for the first thread which is the platform C library thread creation. we use this for every new stack, too. we don't control the size of those stacks at all, and we also don't account for them AFAICT. this is how we ensure that calls into C are fine: all system stacks are basically provided by pthreads.

This means:

 1. The behaviour is different between pure Go and cgo programs, which should be mentioned.
 2. Even for pure Go programs, stacks for syscalls are generally allocated from `stack_inuse` (in cgo programs this is not tracked at all).

This different behaviour should be called out in the docs.
",1.0,"runtime/metrics: update documentation w.r.t. stack_sys - ### What version of Go are you using (`go version`)?

```
$ go version 
go1.20
```
### Issue

The documentation related to stack memory in `MemStats` says:

```
        // StackInuse is bytes in stack spans.
	//
	// In-use stack spans have at least one stack in them. These
	// spans can only be used for other stacks of the same size.
	//
	// There is no StackIdle because unused stack spans are
	// returned to the heap (and hence counted toward HeapIdle).
	StackInuse [uint64](https://pkg.go.dev/builtin#uint64)

	// StackSys is bytes of stack memory obtained from the OS.
	//
	// StackSys is StackInuse, plus any memory obtained directly
	// from the OS for OS thread stacks (which should be minimal).
	StackSys [uint64](https://pkg.go.dev/builtin#uint64)
```

And, in runtime/metrics, there is also:

```
/memory/classes/heap/stacks:bytes
	Memory allocated from the heap that is reserved for stack
	space, whether or not it is currently in-use.

/memory/classes/os-stacks:bytes
	Stack memory allocated by the underlying operating system.
```

But this is at best confusing and at worst incorrect. Quoting @mknyszek from a recent conversation:

> if a program is pure Go, we use newosproc0 to allocate the first stack. this accounts to stacks_sys, which funnels into StackSys. all other system stacks are allocated from the same pool as goroutine stacks (basically, StackInuse). 8192 bytes.
if a program is cgo, then we use _cgo_sys_thread_create for the first thread which is the platform C library thread creation. we use this for every new stack, too. we don't control the size of those stacks at all, and we also don't account for them AFAICT. this is how we ensure that calls into C are fine: all system stacks are basically provided by pthreads.

This means:

 1. The behaviour is different between pure Go and cgo programs, which should be mentioned.
 2. Even for pure Go programs, stacks for syscalls are generally allocated from `stack_inuse` (in cgo programs this is not tracked at all).

This different behaviour should be called out in the docs.
",1,runtime metrics  update documentation w r t  stack sys       what version of go are you using   go version              go version                 issue    the documentation related to stack memory in  memstats  says                     stackinuse is bytes in stack spans   	    	   in use stack spans have at least one stack in them  these  	   spans can only be used for other stacks of the same size   	    	   there is no stackidle because unused stack spans are  	   returned to the heap  and hence counted toward heapidle    	stackinuse        	   stacksys is bytes of stack memory obtained from the os   	    	   stacksys is stackinuse  plus any memory obtained directly  	   from the os for os thread stacks  which should be minimal    	stacksys             and  in runtime metrics  there is also           memory classes heap stacks bytes  	memory allocated from the heap that is reserved for stack  	space  whether or not it is currently in use      memory classes os stacks bytes  	stack memory allocated by the underlying operating system          but this is at best confusing and at worst incorrect  quoting  mknyszek from a recent conversation       if a program is pure go  we use   to allocate the first stack  this accounts to stacks sys  which funnels into stacksys  all other system stacks are allocated from the same pool as goroutine stacks  basically  stackinuse     bytes   if a program is cgo  then we use  cgo sys thread create for the first thread which is the platform c library thread creation  we use this for every new stack  too  we don t control the size of those stacks at all  and we also don t account for them afaict  this is how we ensure that calls into c are fine  all system stacks are basically provided by pthreads     this means         the behaviour is different between pure go and cgo programs  which should be mentioned       even for pure go programs  stacks for syscalls are generally allocated from  stack inuse   in cgo programs this is not tracked at all      this different behaviour should be called out in the docs   ,1
126781,17107286719.0,IssuesEvent,2021-07-09 20:03:17,cgeo/cgeo,https://api.github.com/repos/cgeo/cgeo,closed,Spacing in title bar inconsistent,Frontend Design Prio - Low Regression SDK26,"The distances between symbols and text on the title bar is different throughout several views:

1. Main screen
There is no spacing between the c:geo icon and the text right of it, which looks ugly. Also the ""c:geo"" text could be larger and/or more bold.
![grafik](https://user-images.githubusercontent.com/949669/53305101-7d8d7200-387d-11e9-8884-949024e729ae.png)

2. List view
There is a lot of wasted space between the back navigation arrow and the list dropdown.
Not sure if more space is needed, might be helpful for long list names?
![grafik](https://user-images.githubusercontent.com/949669/53305111-9eee5e00-387d-11e9-8cde-b0f051922cdb.png)

3. Cache view
Also here there is a lot of wasted space between back navigation arrow and cache icon. This truncates the cache name more as it has to be.
![grafik](https://user-images.githubusercontent.com/949669/53305142-073d3f80-387e-11e9-8c6f-e9364c05ba87.png)

T",1.0,"Spacing in title bar inconsistent - The distances between symbols and text on the title bar is different throughout several views:

1. Main screen
There is no spacing between the c:geo icon and the text right of it, which looks ugly. Also the ""c:geo"" text could be larger and/or more bold.
![grafik](https://user-images.githubusercontent.com/949669/53305101-7d8d7200-387d-11e9-8884-949024e729ae.png)

2. List view
There is a lot of wasted space between the back navigation arrow and the list dropdown.
Not sure if more space is needed, might be helpful for long list names?
![grafik](https://user-images.githubusercontent.com/949669/53305111-9eee5e00-387d-11e9-8cde-b0f051922cdb.png)

3. Cache view
Also here there is a lot of wasted space between back navigation arrow and cache icon. This truncates the cache name more as it has to be.
![grafik](https://user-images.githubusercontent.com/949669/53305142-073d3f80-387e-11e9-8c6f-e9364c05ba87.png)

T",0,spacing in title bar inconsistent   the distances between symbols and text on the title bar is different throughout several views        main screen  there is no spacing between the c geo icon and the text right of it  which looks ugly  also the  c geo  text could be larger and or more bold              list view  there is a lot of wasted space between the back navigation arrow and the list dropdown   not sure if more space is needed  might be helpful for long list names              cache view  also here there is a lot of wasted space between back navigation arrow and cache icon  this truncates the cache name more as it has to be           t,0
161536,13851987200.0,IssuesEvent,2020-10-15 05:30:59,golang/go,https://api.github.com/repos/golang/go,closed,"reflect: documentation about ""Conversion of a reflect.SliceHeader or reflect.StringHeader Data field to or from Pointer"" is misleading",Documentation NeedsInvestigation WaitingForInfo,"The document about ""Conversion of a reflect.SliceHeader or reflect.StringHeader Data field to or from Pointer"" is misleading.
```
var s string
hdr := (*reflect.StringHeader)(unsafe.Pointer(&s)) // case 1
hdr.Data = uintptr(unsafe.Pointer(p))              // case 6 (this case)
hdr.Len = n
```
It would be great if the doc specifies one more time the risk of the code below:
```
hdr.Data = uintptr(unsafe.Pointer(p)) 
```
When p point to a temporary memory, we will have problem. For example,

```
func demo(val_copy int64) *reflect.StringHeader {
	var s string
	hdr := (*reflect.StringHeader)(unsafe.Pointer(&s)) 			// case 1
	hdr.Data = uintptr(unsafe.Pointer(&val_copy))               // case 6 (this case)
	hdr.Len = 8
	return hdr
}

func main() {
	val := int64(0xab)
	hdr := demo(val)
	s := *(*string)(unsafe.Pointer(hdr))
	fmt.Printf(""%x"", s)
}
```
The tricky thing is, it's often that the output is the same as expectation. 
But this is a bug because &val_copy is not referenced by others except uintptr, hence the content of the memory pointed by &val_copy is undefined after the demo function returned.",1.0,"reflect: documentation about ""Conversion of a reflect.SliceHeader or reflect.StringHeader Data field to or from Pointer"" is misleading - The document about ""Conversion of a reflect.SliceHeader or reflect.StringHeader Data field to or from Pointer"" is misleading.
```
var s string
hdr := (*reflect.StringHeader)(unsafe.Pointer(&s)) // case 1
hdr.Data = uintptr(unsafe.Pointer(p))              // case 6 (this case)
hdr.Len = n
```
It would be great if the doc specifies one more time the risk of the code below:
```
hdr.Data = uintptr(unsafe.Pointer(p)) 
```
When p point to a temporary memory, we will have problem. For example,

```
func demo(val_copy int64) *reflect.StringHeader {
	var s string
	hdr := (*reflect.StringHeader)(unsafe.Pointer(&s)) 			// case 1
	hdr.Data = uintptr(unsafe.Pointer(&val_copy))               // case 6 (this case)
	hdr.Len = 8
	return hdr
}

func main() {
	val := int64(0xab)
	hdr := demo(val)
	s := *(*string)(unsafe.Pointer(hdr))
	fmt.Printf(""%x"", s)
}
```
The tricky thing is, it's often that the output is the same as expectation. 
But this is a bug because &val_copy is not referenced by others except uintptr, hence the content of the memory pointed by &val_copy is undefined after the demo function returned.",1,reflect  documentation about  conversion of a reflect sliceheader or reflect stringheader data field to or from pointer  is misleading   the document about  conversion of a reflect sliceheader or reflect stringheader data field to or from pointer  is misleading        var s string  hdr      reflect stringheader  unsafe pointer  s      case    hdr data   uintptr unsafe pointer p                   case    this case   hdr len   n       it would be great if the doc specifies one more time the risk of the code below        hdr data   uintptr unsafe pointer p          when p point to a temporary memory  we will have problem  for example          func demo val copy     reflect stringheader    	var s string  	hdr      reflect stringheader  unsafe pointer  s   			   case    	hdr data   uintptr unsafe pointer  val copy                    case    this case   	hdr len      	return hdr       func main      	val          	hdr    demo val   	s       string  unsafe pointer hdr    	fmt printf   x   s           the tricky thing is  it s often that the output is the same as expectation    but this is a bug because  val copy is not referenced by others except uintptr  hence the content of the memory pointed by  val copy is undefined after the demo function returned ,1
15290,3940752474.0,IssuesEvent,2016-04-27 02:59:17,golang/go,https://api.github.com/repos/golang/go,closed,context: typo in documentation,Documentation,"In the documentation:
```
    //  func Stream(ctx context.Context, out <-chan Value) error {
    //  	for {
    //  		v, err := DoSomething(ctx)
    //  		if err != nil {
    //  			return err
    //  		}
    //  		select {
    //  		case <-ctx.Done():
    //  			return ctx.Err()
    //  		case out <- v:
    //  		}
    //  	}
    //  }
```

`out <-chan Value` should be replaced by `out chan<- Value`

There is the same typo in `golang.org/x/net/context`",1.0,"context: typo in documentation - In the documentation:
```
    //  func Stream(ctx context.Context, out <-chan Value) error {
    //  	for {
    //  		v, err := DoSomething(ctx)
    //  		if err != nil {
    //  			return err
    //  		}
    //  		select {
    //  		case <-ctx.Done():
    //  			return ctx.Err()
    //  		case out <- v:
    //  		}
    //  	}
    //  }
```

`out <-chan Value` should be replaced by `out chan<- Value`

There is the same typo in `golang.org/x/net/context`",1,context  typo in documentation   in the documentation                func stream ctx context context  out   chan value  error            	for            		v  err    dosomething ctx           		if err    nil            			return err          		           		select            		case   ctx done             			return ctx err            		case out    v           		           	                      out   chan value  should be replaced by  out chan   value     there is the same typo in  golang org x net context ,1
21593,4727235728.0,IssuesEvent,2016-10-18 12:56:51,golang/go,https://api.github.com/repos/golang/go,closed,testing: Document interaction of Skip and Error,Documentation NeedsFix,"```sh
go version go1.7rc3 linux/amd64
```

```go
package todo_test

import ""testing""

func TestIssueFixed(t *testing.T) {
	defer func() {
		if t.Failed() {
			t.Skip(""Test failed as expected; see issue XXXXXXXX."")
		}
		t.Fatal(""Test did not fail as expected; please update issue XXXXXXXX."")
	}()

	t.Log(""<no symptoms of issue XXXXXXXX>"")
}

func TestIssueOpen(t *testing.T) {
	defer func() {
		if t.Failed() {
			t.Skip(""Test failed as expected; see issue XXXXXXXX."")
		}
		t.Fatal(""Test did not fail as expected; please update issue XXXXXXXX."")
	}()

	t.Error(""<symptom of issue XXXXXXXX>"")
}
```

Expected:
```
$ go test -v todo
=== RUN   TestIssueFixed
--- FAIL: TestIssueFixed (0.00s)
        todo_test.go:13: <no symptoms of issue XXXXXXXX>
        todo_test.go:10: Test did not fail as expected; please update issue XXXXXXXX.
=== RUN   TestIssueOpen
--- SKIP: TestIssueOpen (0.00s)
        todo_test.go:24: <symptom of issue XXXXXXXX>
        todo_test.go:19: Test failed as expected; see issue XXXXXXXX.
FAIL
exit status 1
FAIL    todo    0.018s
```

Actual:
```
$ go test -v todo
=== RUN   TestIssueFixed
--- FAIL: TestIssueFixed (0.00s)
        todo_test.go:13: <no symptoms of issue XXXXXXXX>
        todo_test.go:10: Test did not fail as expected; please update issue XXXXXXXX.
=== RUN   TestIssueOpen
--- FAIL: TestIssueOpen (0.00s)
        todo_test.go:24: <symptom of issue XXXXXXXX>
        todo_test.go:19: Test failed as expected; see issue XXXXXXXX.
FAIL
exit status 1
FAIL    todo    0.031s
```

I'm guessing this is not actually a bug, but I don't see anything in https://golang.org/pkg/testing/ describing how Skip and Error are supposed to interact.  It doesn't seem unreasonable to think that a test could be Skipped after it has already Failed, but that turns out not to be the case as implemented.

Could someone with more in-depth knowledge of the testing package please confirm whether this behavior is intended (and, if so, update the documentation)?",1.0,"testing: Document interaction of Skip and Error - ```sh
go version go1.7rc3 linux/amd64
```

```go
package todo_test

import ""testing""

func TestIssueFixed(t *testing.T) {
	defer func() {
		if t.Failed() {
			t.Skip(""Test failed as expected; see issue XXXXXXXX."")
		}
		t.Fatal(""Test did not fail as expected; please update issue XXXXXXXX."")
	}()

	t.Log(""<no symptoms of issue XXXXXXXX>"")
}

func TestIssueOpen(t *testing.T) {
	defer func() {
		if t.Failed() {
			t.Skip(""Test failed as expected; see issue XXXXXXXX."")
		}
		t.Fatal(""Test did not fail as expected; please update issue XXXXXXXX."")
	}()

	t.Error(""<symptom of issue XXXXXXXX>"")
}
```

Expected:
```
$ go test -v todo
=== RUN   TestIssueFixed
--- FAIL: TestIssueFixed (0.00s)
        todo_test.go:13: <no symptoms of issue XXXXXXXX>
        todo_test.go:10: Test did not fail as expected; please update issue XXXXXXXX.
=== RUN   TestIssueOpen
--- SKIP: TestIssueOpen (0.00s)
        todo_test.go:24: <symptom of issue XXXXXXXX>
        todo_test.go:19: Test failed as expected; see issue XXXXXXXX.
FAIL
exit status 1
FAIL    todo    0.018s
```

Actual:
```
$ go test -v todo
=== RUN   TestIssueFixed
--- FAIL: TestIssueFixed (0.00s)
        todo_test.go:13: <no symptoms of issue XXXXXXXX>
        todo_test.go:10: Test did not fail as expected; please update issue XXXXXXXX.
=== RUN   TestIssueOpen
--- FAIL: TestIssueOpen (0.00s)
        todo_test.go:24: <symptom of issue XXXXXXXX>
        todo_test.go:19: Test failed as expected; see issue XXXXXXXX.
FAIL
exit status 1
FAIL    todo    0.031s
```

I'm guessing this is not actually a bug, but I don't see anything in https://golang.org/pkg/testing/ describing how Skip and Error are supposed to interact.  It doesn't seem unreasonable to think that a test could be Skipped after it has already Failed, but that turns out not to be the case as implemented.

Could someone with more in-depth knowledge of the testing package please confirm whether this behavior is intended (and, if so, update the documentation)?",1,testing  document interaction of skip and error      sh  go version     linux              go  package todo test    import  testing     func testissuefixed t  testing t     	defer func      		if t failed      			t skip  test failed as expected  see issue xxxxxxxx     		   		t fatal  test did not fail as expected  please update issue xxxxxxxx     	       	t log            func testissueopen t  testing t     	defer func      		if t failed      			t skip  test failed as expected  see issue xxxxxxxx     		   		t fatal  test did not fail as expected  please update issue xxxxxxxx     	       	t error                 expected          go test  v todo      run   testissuefixed      fail  testissuefixed                todo test go               todo test go    test did not fail as expected  please update issue xxxxxxxx       run   testissueopen      skip  testissueopen                todo test go               todo test go    test failed as expected  see issue xxxxxxxx   fail  exit status    fail    todo                actual          go test  v todo      run   testissuefixed      fail  testissuefixed                todo test go               todo test go    test did not fail as expected  please update issue xxxxxxxx       run   testissueopen      fail  testissueopen                todo test go               todo test go    test failed as expected  see issue xxxxxxxx   fail  exit status    fail    todo                i m guessing this is not actually a bug  but i don t see anything in   describing how skip and error are supposed to interact   it doesn t seem unreasonable to think that a test could be skipped after it has already failed  but that turns out not to be the case as implemented     could someone with more in depth knowledge of the testing package please confirm whether this behavior is intended  and  if so  update the documentation  ,1
199005,22674217808.0,IssuesEvent,2022-07-04 01:28:37,Techini/WebGoat,https://api.github.com/repos/Techini/WebGoat,closed,CVE-2021-39139 (High) detected in xstream-1.4.5.jar - autoclosed,security vulnerability,"## CVE-2021-39139 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xstream-1.4.5.jar</b></p></summary>

<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /webgoat-lessons/vulnerable-components/pom.xml</p>
<p>Path to vulnerable library: /m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>

Dependency Hierarchy:
  - :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://api.github.com/repos/Techini/WebGoat/git/commits/44f64ff5181d699f4750a9154b153e825edb9e3b"">44f64ff5181d699f4750a9154b153e825edb9e3b</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
XStream is a simple library to serialize objects to XML and back again. In affected versions this vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. A user is only affected if using the version out of the box with JDK 1.7u21 or below. However, this scenario can be adjusted easily to an external Xalan that works regardless of the version of the Java runtime. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. XStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.

<p>Publish Date: 2021-08-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-39139>CVE-2021-39139</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>8.8</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<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/x-stream/xstream/security/advisories/GHSA-64xx-cq4q-mf44"">https://github.com/x-stream/xstream/security/advisories/GHSA-64xx-cq4q-mf44</a></p>
<p>Release Date: 2021-08-23</p>
<p>Fix Resolution: com.thoughtworks.xstream:xstream:1.4.18</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-39139 (High) detected in xstream-1.4.5.jar - autoclosed - ## CVE-2021-39139 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xstream-1.4.5.jar</b></p></summary>

<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /webgoat-lessons/vulnerable-components/pom.xml</p>
<p>Path to vulnerable library: /m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>

Dependency Hierarchy:
  - :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://api.github.com/repos/Techini/WebGoat/git/commits/44f64ff5181d699f4750a9154b153e825edb9e3b"">44f64ff5181d699f4750a9154b153e825edb9e3b</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
XStream is a simple library to serialize objects to XML and back again. In affected versions this vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. A user is only affected if using the version out of the box with JDK 1.7u21 or below. However, this scenario can be adjusted easily to an external Xalan that works regardless of the version of the Java runtime. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. XStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.

<p>Publish Date: 2021-08-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-39139>CVE-2021-39139</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>8.8</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<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/x-stream/xstream/security/advisories/GHSA-64xx-cq4q-mf44"">https://github.com/x-stream/xstream/security/advisories/GHSA-64xx-cq4q-mf44</a></p>
<p>Release Date: 2021-08-23</p>
<p>Fix Resolution: com.thoughtworks.xstream:xstream:1.4.18</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in xstream       jar   autoclosed      cve       high severity vulnerability     vulnerable library    xstream       jar      xstream is a serialization library from java objects to xml and back    path to dependency file   webgoat lessons vulnerable components pom xml   path to vulnerable library     repository com thoughtworks xstream xstream       xstream       jar  home wss scanner    repository com thoughtworks xstream xstream       xstream       jar  home wss scanner    repository com thoughtworks xstream xstream       xstream       jar     dependency hierarchy       x    xstream       jar    vulnerable library   found in head commit   a href               vulnerability details         xstream is a simple library to serialize objects to xml and back again  in affected versions this vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream  a user is only affected if using the version out of the box with jdk     or below  however  this scenario can be adjusted easily to an external xalan that works regardless of the version of the java runtime  no user is affected  who followed the recommendation to setup xstream s security framework with a whitelist limited to the minimal required types  xstream       uses no longer a blacklist by default  since it cannot be secured for general purpose    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  low     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  com thoughtworks xstream xstream                     step up your open source security game with whitesource    ,0
45408,24049006779.0,IssuesEvent,2022-09-16 10:59:19,camunda/zeebe,https://api.github.com/repos/camunda/zeebe,closed,Remove unnecessary intermediate serialization in RaftLog#append,kind/toil scope/broker area/performance,"**Description**

At the moment, we first serialize the Raft log entry before passing it to the journal. This works fine, but requires us to have an intermediate in memory buffer. This means we have an extra copy in the journal when appending, and we have this expendable, long living buffer in memory.

Proposal:

What we need is a way to serialize only when we have the final destination buffer. One easy way is to amend the Journal interface to add a `public JournalRecord append(int entryLength, Consumer<MutableDirectBuffer> entryWriter);`. Or we we want to obviate the need for lambdas:

```java
public interface RecordDataWriter<T> {
  final void write(T entry, MutableDirectBuffer buffer, int offset);
}

public interface Journal {
  // ...
  public <T> JournalRecord append(T entry, int entryLength, RecordDataWriter<T> writer)
}
```

In the journal, we can then serialize the record data when we need it directly to the writer's buffer instead of using an intermediate write buffer.

NOTE: if we can make it without using generics, even better :slightly_smiling_face: 

/cc @deepthidevaki ",True,"Remove unnecessary intermediate serialization in RaftLog#append - **Description**

At the moment, we first serialize the Raft log entry before passing it to the journal. This works fine, but requires us to have an intermediate in memory buffer. This means we have an extra copy in the journal when appending, and we have this expendable, long living buffer in memory.

Proposal:

What we need is a way to serialize only when we have the final destination buffer. One easy way is to amend the Journal interface to add a `public JournalRecord append(int entryLength, Consumer<MutableDirectBuffer> entryWriter);`. Or we we want to obviate the need for lambdas:

```java
public interface RecordDataWriter<T> {
  final void write(T entry, MutableDirectBuffer buffer, int offset);
}

public interface Journal {
  // ...
  public <T> JournalRecord append(T entry, int entryLength, RecordDataWriter<T> writer)
}
```

In the journal, we can then serialize the record data when we need it directly to the writer's buffer instead of using an intermediate write buffer.

NOTE: if we can make it without using generics, even better :slightly_smiling_face: 

/cc @deepthidevaki ",0,remove unnecessary intermediate serialization in raftlog append     description      at the moment  we first serialize the raft log entry before passing it to the journal  this works fine  but requires us to have an intermediate in memory buffer  this means we have an extra copy in the journal when appending  and we have this expendable  long living buffer in memory     proposal     what we need is a way to serialize only when we have the final destination buffer  one easy way is to amend the journal interface to add a  public journalrecord append int entrylength  consumer  entrywriter     or we we want to obviate the need for lambdas        java  public interface recorddatawriter       final void write t entry  mutabledirectbuffer buffer  int offset         public interface journal                public   journalrecord append t entry  int entrylength  recorddatawriter  writer             in the journal  we can then serialize the record data when we need it directly to the writer s buffer instead of using an intermediate write buffer     note  if we can make it without using generics  even better  slightly smiling face       cc  deepthidevaki ,0
49610,7523318375.0,IssuesEvent,2018-04-13 00:15:58,golang/go,https://api.github.com/repos/golang/go,opened,x/build: start using Gerrit hashtags for managing open CLs,Documentation NeedsFix,"In chat with @andybons @FiloSottile @bcmills and @ianlancetaylor yesterday, I proposed we start using Gerrit's ""hashtags"" support, now that our hosted Gerrit supports it (notedb support is active for us) and PolyGerrit (the new web UI) supports it.

After discussion, we settled on using tags:

```
so, how about: ""wait-author"", ""wait-release"", ""wait-issue"", ""wait-$PERSON""
where $PERSON is some substring of a name/email in the reviewer set.
and if somebody is named ""Issue Release"" and their email is issue@release.com, then you have to use their full email in $PERSON
we can mass remove the ""wait-release"" labels when tree opens
```

While triaging today, I found we should also add support for:

```
wait-cl-NNNNN -- this CL is blocked until NNN is resolved
```

I started looking into adding hashtag support to maintner and gopherbot.

Tracking that work here, then documenting all this on the wiki.
",1.0,"x/build: start using Gerrit hashtags for managing open CLs - In chat with @andybons @FiloSottile @bcmills and @ianlancetaylor yesterday, I proposed we start using Gerrit's ""hashtags"" support, now that our hosted Gerrit supports it (notedb support is active for us) and PolyGerrit (the new web UI) supports it.

After discussion, we settled on using tags:

```
so, how about: ""wait-author"", ""wait-release"", ""wait-issue"", ""wait-$PERSON""
where $PERSON is some substring of a name/email in the reviewer set.
and if somebody is named ""Issue Release"" and their email is issue@release.com, then you have to use their full email in $PERSON
we can mass remove the ""wait-release"" labels when tree opens
```

While triaging today, I found we should also add support for:

```
wait-cl-NNNNN -- this CL is blocked until NNN is resolved
```

I started looking into adding hashtag support to maintner and gopherbot.

Tracking that work here, then documenting all this on the wiki.
",1,x build  start using gerrit hashtags for managing open cls   in chat with  andybons  filosottile  bcmills and  ianlancetaylor yesterday  i proposed we start using gerrit s  hashtags  support  now that our hosted gerrit supports it  notedb support is active for us  and polygerrit  the new web ui  supports it     after discussion  we settled on using tags          so  how about   wait author    wait release    wait issue    wait  person   where  person is some substring of a name email in the reviewer set   and if somebody is named  issue release  and their email is issue release com  then you have to use their full email in  person  we can mass remove the  wait release  labels when tree opens         while triaging today  i found we should also add support for          wait cl nnnnn    this cl is blocked until nnn is resolved         i started looking into adding hashtag support to maintner and gopherbot     tracking that work here  then documenting all this on the wiki   ,1
267561,20207356748.0,IssuesEvent,2022-02-11 22:06:35,golang/go,https://api.github.com/repos/golang/go,closed,spec: typeparams: method calls do not implicitly dereference pointer-to-TypeParams,Documentation,"This test program exercises whether implicit dereference of pointer-to-type-parameter is allowed in a method call: https://go2goplay.golang.org/p/0C-j_EutS4c

go/types and cmd/compile/internal/types2 both accept it, but then go2go, cmd/compile -G=3, and cmd/compile unified all produce a ""calling method M with receiver p (type **MyMer) requires explicit dereference"" error during code generation.

A similar issue affects instantiating type parameters with interface types: https://go2goplay.golang.org/p/-vWtl3FTslw. (Here go2go and unified both report ""p.M undefined (type *Mer is pointer to interface, not interface)""; -G=3 hits an assertion failure.)

What's the expected behavior here? Should go/types reject these cases as invalid, or do the compilers need to insert the implicit dereference? I don't see anything mentioned about this in the proposal.

My intuition is these are invalid, and go/types should reject them. Type parameter types act like interface types, and we don't allow implicit dereference of pointer-to-interface-type values in method calls.

/cc @griesemer @ianlancetaylor @findleyr @bcmills ",1.0,"spec: typeparams: method calls do not implicitly dereference pointer-to-TypeParams - This test program exercises whether implicit dereference of pointer-to-type-parameter is allowed in a method call: https://go2goplay.golang.org/p/0C-j_EutS4c

go/types and cmd/compile/internal/types2 both accept it, but then go2go, cmd/compile -G=3, and cmd/compile unified all produce a ""calling method M with receiver p (type **MyMer) requires explicit dereference"" error during code generation.

A similar issue affects instantiating type parameters with interface types: https://go2goplay.golang.org/p/-vWtl3FTslw. (Here go2go and unified both report ""p.M undefined (type *Mer is pointer to interface, not interface)""; -G=3 hits an assertion failure.)

What's the expected behavior here? Should go/types reject these cases as invalid, or do the compilers need to insert the implicit dereference? I don't see anything mentioned about this in the proposal.

My intuition is these are invalid, and go/types should reject them. Type parameter types act like interface types, and we don't allow implicit dereference of pointer-to-interface-type values in method calls.

/cc @griesemer @ianlancetaylor @findleyr @bcmills ",1,spec  typeparams  method calls do not implicitly dereference pointer to typeparams   this test program exercises whether implicit dereference of pointer to type parameter is allowed in a method call       go types and cmd compile internal   both accept it  but then    cmd compile  g    and cmd compile unified all produce a  calling method m with receiver p  type   mymer  requires explicit dereference  error during code generation     a similar issue affects instantiating type parameters with interface types     here   and unified both report  p m undefined  type  mer is pointer to interface  not interface     g   hits an assertion failure      what s the expected behavior here  should go types reject these cases as invalid  or do the compilers need to insert the implicit dereference  i don t see anything mentioned about this in the proposal     my intuition is these are invalid  and go types should reject them  type parameter types act like interface types  and we don t allow implicit dereference of pointer to interface type values in method calls      cc  griesemer  ianlancetaylor  findleyr  bcmills ,1
58100,8229532452.0,IssuesEvent,2018-09-07 09:41:02,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: clarify go.mod documentation for trivial relative modules,Documentation NeedsInvestigation modules,"### What version of Go are you using (`go version`)?
<pre><code>go version go1.11 darwin/amd64
</code></pre>

### Does this issue reproduce with the latest release?
Yes.

### What operating system and processor architecture are you using (`go env`)?
<pre><code>GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/rust/Library/Caches/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/rust/code""
GOPROXY=""""
GORACE=""""
GOROOT=""/usr/local/go""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/rust/code/modtest/b/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/_d/8n_wrc4n32d1rgx80bn6hsl80000gn/T/go-build056371648=/tmp/go-build -gno-record-gcc-switches -fno-common""
</code></pre>

### What did you do?

Created two modules <code>a</code> and <code>b</code> in the same directory, not on the <code>GOPATH</code>.

Module <code>a</code> contains <code>a.go, go.mod</code>:
<pre><code>~/code/modtest/a: cat a.go
package a

func Hello() string {
	return ""Hello""
}
~/code/modtest/a: cat go.mod
module a
</code></pre>

Module <code>b</code> contains <code>b.go, go.mod</code>:
<pre><code>~/code/modtest/b: cat b.go
package main

import (
    ""fmt""

    ""a""
)

func main() {
	fmt.Printf(""%s\n"", a.Hello())
}
~/code/modtest/b: cat go.mod 
module b

require ../a v0.0.0
</code></pre>

What is the proper syntax for the line <code>require ../a v0.0.0</code> in this particular case?
The closest I found in the docs (<code>go help modules, go help go.mod, go help mod</code>) was from <code>go help importpath</code>:
<pre><code>Relative import paths

An import path beginning with ./ or ../ is called a relative path.
The toolchain supports relative import paths as a shortcut in two ways.

First, a relative path can be used as a shorthand on the command line.
...

Second, if you are compiling a Go program not in a work space,
you can use a relative path in an import statement in that program
to refer to nearby code also not in a work space.
This makes it easy to experiment with small multipackage programs
outside of the usual work spaces, but such programs cannot be
installed with ""go install"" (there is no work space in which to install them),
so they are rebuilt from scratch each time they are built.
To avoid ambiguity, Go programs cannot use relative import paths
within a work space.
</code></pre>
It is unclear to me if the second case is supposed to apply in this situation.

### What did you expect to see?

I expect this to compile and run similarly to how it works with the existing GOPATH.
For example, copying the modules to the GOPATH gives the following:
<pre><code>~/code/src: cd a
~/code/src/a: go build
~/code/src/a: cd ../b
~/code/src/b: go build
~/code/src/b: ./b
Hello
</code></pre>

### What did you see instead?

<pre><code>~/code/modtest: cd a
~/code/modtest/a: go build
~/code/modtest/a: cd ../b
~/code/modtest/b: go build
go: ../a@v0.0.0: unrecognized import path ""../a"" (https fetch: Get https://../a?go-get=1: dial tcp: lookup ..: no such host)
go: error loading module requirements
~/code/modtest/b: 
</code></pre>

",1.0,"cmd/go: clarify go.mod documentation for trivial relative modules - ### What version of Go are you using (`go version`)?
<pre><code>go version go1.11 darwin/amd64
</code></pre>

### Does this issue reproduce with the latest release?
Yes.

### What operating system and processor architecture are you using (`go env`)?
<pre><code>GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/rust/Library/Caches/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/rust/code""
GOPROXY=""""
GORACE=""""
GOROOT=""/usr/local/go""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/rust/code/modtest/b/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/_d/8n_wrc4n32d1rgx80bn6hsl80000gn/T/go-build056371648=/tmp/go-build -gno-record-gcc-switches -fno-common""
</code></pre>

### What did you do?

Created two modules <code>a</code> and <code>b</code> in the same directory, not on the <code>GOPATH</code>.

Module <code>a</code> contains <code>a.go, go.mod</code>:
<pre><code>~/code/modtest/a: cat a.go
package a

func Hello() string {
	return ""Hello""
}
~/code/modtest/a: cat go.mod
module a
</code></pre>

Module <code>b</code> contains <code>b.go, go.mod</code>:
<pre><code>~/code/modtest/b: cat b.go
package main

import (
    ""fmt""

    ""a""
)

func main() {
	fmt.Printf(""%s\n"", a.Hello())
}
~/code/modtest/b: cat go.mod 
module b

require ../a v0.0.0
</code></pre>

What is the proper syntax for the line <code>require ../a v0.0.0</code> in this particular case?
The closest I found in the docs (<code>go help modules, go help go.mod, go help mod</code>) was from <code>go help importpath</code>:
<pre><code>Relative import paths

An import path beginning with ./ or ../ is called a relative path.
The toolchain supports relative import paths as a shortcut in two ways.

First, a relative path can be used as a shorthand on the command line.
...

Second, if you are compiling a Go program not in a work space,
you can use a relative path in an import statement in that program
to refer to nearby code also not in a work space.
This makes it easy to experiment with small multipackage programs
outside of the usual work spaces, but such programs cannot be
installed with ""go install"" (there is no work space in which to install them),
so they are rebuilt from scratch each time they are built.
To avoid ambiguity, Go programs cannot use relative import paths
within a work space.
</code></pre>
It is unclear to me if the second case is supposed to apply in this situation.

### What did you expect to see?

I expect this to compile and run similarly to how it works with the existing GOPATH.
For example, copying the modules to the GOPATH gives the following:
<pre><code>~/code/src: cd a
~/code/src/a: go build
~/code/src/a: cd ../b
~/code/src/b: go build
~/code/src/b: ./b
Hello
</code></pre>

### What did you see instead?

<pre><code>~/code/modtest: cd a
~/code/modtest/a: go build
~/code/modtest/a: cd ../b
~/code/modtest/b: go build
go: ../a@v0.0.0: unrecognized import path ""../a"" (https fetch: Get https://../a?go-get=1: dial tcp: lookup ..: no such host)
go: error loading module requirements
~/code/modtest/b: 
</code></pre>

",1,cmd go  clarify go mod documentation for trivial relative modules       what version of go are you using   go version       go version     darwin              does this issue reproduce with the latest release   yes         what operating system and processor architecture are you using   go env       goarch      gobin     gocache   users rust library caches go build   goexe     goflags     gohostarch      gohostos  darwin   goos  darwin   gopath   users rust code   goproxy     gorace     goroot   usr local go   gotmpdir     gotooldir   usr local go pkg tool darwin     gccgo  gccgo   cc  clang   cxx  clang     cgo enabled      gomod   users rust code modtest b go mod   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders  d     t go    tmp go build  gno record gcc switches  fno common             what did you do     created two modules  a  and  b  in the same directory  not on the  gopath      module  a  contains  a go  go mod        code modtest a  cat a go  package a    func hello   string    	return  hello        code modtest a  cat go mod  module a        module  b  contains  b go  go mod        code modtest b  cat b go  package main    import         fmt          a        func main      	fmt printf   s n   a hello          code modtest b  cat go mod   module b    require    a              what is the proper syntax for the line  require    a        in this particular case   the closest i found in the docs   go help modules  go help go mod  go help mod   was from  go help importpath      relative import paths    an import path beginning with    or     is called a relative path   the toolchain supports relative import paths as a shortcut in two ways     first  a relative path can be used as a shorthand on the command line          second  if you are compiling a go program not in a work space   you can use a relative path in an import statement in that program  to refer to nearby code also not in a work space   this makes it easy to experiment with small multipackage programs  outside of the usual work spaces  but such programs cannot be  installed with  go install   there is no work space in which to install them    so they are rebuilt from scratch each time they are built   to avoid ambiguity  go programs cannot use relative import paths  within a work space       it is unclear to me if the second case is supposed to apply in this situation         what did you expect to see     i expect this to compile and run similarly to how it works with the existing gopath   for example  copying the modules to the gopath gives the following       code src  cd a    code src a  go build    code src a  cd    b    code src b  go build    code src b    b  hello            what did you see instead         code modtest  cd a    code modtest a  go build    code modtest a  cd    b    code modtest b  go build  go     a        unrecognized import path     a   https fetch  get   dial tcp  lookup     no such host   go  error loading module requirements    code modtest b          ,1
20338,4537991455.0,IssuesEvent,2016-09-09 03:47:18,golang/go,https://api.github.com/repos/golang/go,closed,net/http/cookiejar: adding example,Documentation,"I've prepared two versions of examples for `net/http/cookiejar`, 

[Version 1](https://play.golang.org/p/xz74yExiHG) makes actual HTTP requests to www.google.com and https://golang.org/doc/tos.html and prints out cookies.   

*Pro:* It keeps example code small
*Con:*  One needs internet access for this test to pass, it takes `0.59s` on my MacBook Pro.  Time that adds up over many test runs.

[Version 2](https://play.golang.org/p/DTxy75fZKR) uses a dummy transport that writes `COOKIE!` cookie to response.

*Pro:* Tests run very quickly, about `0.00s` on same machine.
*Con:* Example adds additional code, which looks rather out of place in context of an example. I've not see any other example creating a separate transport. 

Any suggestions on how to proceed? 
",1.0,"net/http/cookiejar: adding example - I've prepared two versions of examples for `net/http/cookiejar`, 

[Version 1](https://play.golang.org/p/xz74yExiHG) makes actual HTTP requests to www.google.com and https://golang.org/doc/tos.html and prints out cookies.   

*Pro:* It keeps example code small
*Con:*  One needs internet access for this test to pass, it takes `0.59s` on my MacBook Pro.  Time that adds up over many test runs.

[Version 2](https://play.golang.org/p/DTxy75fZKR) uses a dummy transport that writes `COOKIE!` cookie to response.

*Pro:* Tests run very quickly, about `0.00s` on same machine.
*Con:* Example adds additional code, which looks rather out of place in context of an example. I've not see any other example creating a separate transport. 

Any suggestions on how to proceed? 
",1,net http cookiejar  adding example   i ve prepared two versions of examples for  net http cookiejar           makes actual http requests to   and   and prints out cookies         pro   it keeps example code small   con    one needs internet access for this test to pass  it takes       on my macbook pro   time that adds up over many test runs         uses a dummy transport that writes  cookie   cookie to response      pro   tests run very quickly  about       on same machine    con   example adds additional code  which looks rather out of place in context of an example  i ve not see any other example creating a separate transport      any suggestions on how to proceed    ,1
142605,13035159265.0,IssuesEvent,2020-07-28 09:54:04,golang/go,https://api.github.com/repos/golang/go,closed,x/blog: some more details in `/json` section,Documentation,"### What did you expect to see?
Iam from Python background and hence it was little bit difficult for me to understand how unmarshalling works, specially if the keywords are `lowercase`

The https://blog.golang.org/json blog appears in the top of the search while searching for json.

There is this line 
```The json package only accesses the exported fields of struct types (those that begin with an uppercase letter). Therefore only the the exported fields of a struct will be present in the JSON output.```

It would be great if we could also add an example saying
```If your json has lowercase keys, then you might have to follow the below snippet to access them. For further information check out https://golang.org/pkg/encoding/json/#Marshal```

```go
type Message struct {
    Name string `json:”name”
    Body string   `json:”body”
    Time int64    `json:”time”
}
```

### What did you see instead?
The example stops with the 
```The json package only accesses the exported fields of struct types (those that begin with an uppercase letter). Therefore only the the exported fields of a struct will be present in the JSON output.```
This makes it bit difficult for new comers to easily understand the techniques that are very trivial.

I would be happy to submit PR, but I dont know where the docs of blog are.",1.0,"x/blog: some more details in `/json` section - ### What did you expect to see?
Iam from Python background and hence it was little bit difficult for me to understand how unmarshalling works, specially if the keywords are `lowercase`

The https://blog.golang.org/json blog appears in the top of the search while searching for json.

There is this line 
```The json package only accesses the exported fields of struct types (those that begin with an uppercase letter). Therefore only the the exported fields of a struct will be present in the JSON output.```

It would be great if we could also add an example saying
```If your json has lowercase keys, then you might have to follow the below snippet to access them. For further information check out https://golang.org/pkg/encoding/json/#Marshal```

```go
type Message struct {
    Name string `json:”name”
    Body string   `json:”body”
    Time int64    `json:”time”
}
```

### What did you see instead?
The example stops with the 
```The json package only accesses the exported fields of struct types (those that begin with an uppercase letter). Therefore only the the exported fields of a struct will be present in the JSON output.```
This makes it bit difficult for new comers to easily understand the techniques that are very trivial.

I would be happy to submit PR, but I dont know where the docs of blog are.",1,x blog  some more details in   json  section       what did you expect to see   iam from python background and hence it was little bit difficult for me to understand how unmarshalling works  specially if the keywords are  lowercase     the   blog appears in the top of the search while searching for json     there is this line      the json package only accesses the exported fields of struct types  those that begin with an uppercase letter   therefore only the the exported fields of a struct will be present in the json output        it would be great if we could also add an example saying     if your json has lowercase keys  then you might have to follow the below snippet to access them  for further information check out         go  type message struct        name string  json ”name”      body string    json ”body”      time       json ”time”                what did you see instead   the example stops with the      the json package only accesses the exported fields of struct types  those that begin with an uppercase letter   therefore only the the exported fields of a struct will be present in the json output      this makes it bit difficult for new comers to easily understand the techniques that are very trivial     i would be happy to submit pr  but i dont know where the docs of blog are ,1
648217,21178869181.0,IssuesEvent,2022-04-08 05:17:15,jasonmatos23-git/DepthPerceptionHapticSystem,https://api.github.com/repos/jasonmatos23-git/DepthPerceptionHapticSystem,closed,Low power mode,high priority,"Set peripheral devices (e.g. LiDAR, camera, motor controller) to their low power modes. Mode may be revisited in the future for improved performance.",1.0,"Low power mode - Set peripheral devices (e.g. LiDAR, camera, motor controller) to their low power modes. Mode may be revisited in the future for improved performance.",0,low power mode   set peripheral devices  e g  lidar  camera  motor controller  to their low power modes  mode may be revisited in the future for improved performance ,0
34319,29482979429.0,IssuesEvent,2023-06-02 07:33:33,localstack/localstack,https://api.github.com/repos/localstack/localstack,closed,bug: downloading content at runtime results in API rate limits being hit?,type: bug area: infrastructure,"### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current Behavior

```
STDOUT: 2022-11-08 22:30:32,630 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
STDOUT: 2022-11-08 22:30:32,632 INFO supervisord started with pid 16
STDOUT: 2022-11-08 22:30:33,634 INFO spawned: 'infra' with pid 21
STDOUT: SERVICES variable is ignored if EAGER_SERVICE_LOADING=0.
STDOUT: LocalStack version: 1.2.0
STDOUT: 2022-11-08 22:30:34,840 INFO success: infra entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
STDOUT: LocalStack Docker container id: 909496f36c9b
STDOUT: LocalStack build date: 2022-10-07
STDOUT: LocalStack build git hash: 9be2a7aa
STDOUT: Error starting infrastructure: Could not get list of releases from https://api.github.com/repos/etspaceman/kinesis-mock/releases/tags/0.2.5: {""message"":""API rate limit exceeded for x.x.x.x. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)"",""documentation_url"":""https://docs.github.com/rest/overview/resources-in-the-rest-api#rate-limiting""}
STDOUT: Traceback (most recent call last):
```

### Expected Behavior

Remote content should not be checked or downloaded at runtime 

### How are you starting LocalStack?

Custom (please describe below)

### Steps To Reproduce

We are using testcontainers 


### Environment

```markdown
- OS: OS name: ""Linux"", version: 4.14.243-185.433.amzn2.x86_64, arch: amd64
- LocalStack: 1.2.0
```


### Anything else?

_No response_",1.0,"bug: downloading content at runtime results in API rate limits being hit? - ### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current Behavior

```
STDOUT: 2022-11-08 22:30:32,630 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
STDOUT: 2022-11-08 22:30:32,632 INFO supervisord started with pid 16
STDOUT: 2022-11-08 22:30:33,634 INFO spawned: 'infra' with pid 21
STDOUT: SERVICES variable is ignored if EAGER_SERVICE_LOADING=0.
STDOUT: LocalStack version: 1.2.0
STDOUT: 2022-11-08 22:30:34,840 INFO success: infra entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
STDOUT: LocalStack Docker container id: 909496f36c9b
STDOUT: LocalStack build date: 2022-10-07
STDOUT: LocalStack build git hash: 9be2a7aa
STDOUT: Error starting infrastructure: Could not get list of releases from https://api.github.com/repos/etspaceman/kinesis-mock/releases/tags/0.2.5: {""message"":""API rate limit exceeded for x.x.x.x. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)"",""documentation_url"":""https://docs.github.com/rest/overview/resources-in-the-rest-api#rate-limiting""}
STDOUT: Traceback (most recent call last):
```

### Expected Behavior

Remote content should not be checked or downloaded at runtime 

### How are you starting LocalStack?

Custom (please describe below)

### Steps To Reproduce

We are using testcontainers 


### Environment

```markdown
- OS: OS name: ""Linux"", version: 4.14.243-185.433.amzn2.x86_64, arch: amd64
- LocalStack: 1.2.0
```


### Anything else?

_No response_",0,bug  downloading content at runtime results in api rate limits being hit        is there an existing issue for this       i have searched the existing issues      current behavior       stdout                crit supervisor is running as root   privileges were not dropped because no user is specified in the config file   if you intend to run as root  you can set user root in the config file to avoid this message   stdout                info supervisord started with pid    stdout                info spawned   infra  with pid    stdout  services variable is ignored if eager service loading     stdout  localstack version         stdout                info success  infra entered running state  process has stayed up for   than   seconds  startsecs   stdout  localstack docker container id     stdout  localstack build date         stdout  localstack build git hash     stdout  error starting infrastructure  could not get list of releases from     message   api rate limit exceeded for x x x x   but here s the good news  authenticated requests get a higher rate limit  check out the documentation for more details     documentation url      stdout  traceback  most recent call last             expected behavior  remote content should not be checked or downloaded at runtime       how are you starting localstack   custom  please describe below       steps to reproduce  we are using testcontainers         environment     markdown   os  os name   linux   version                   arch       localstack                  anything else    no response ,0
52820,7786242441.0,IssuesEvent,2018-06-06 18:19:10,golang/go,https://api.github.com/repos/golang/go,closed,database/sql: DB documentation should mention DB.Conn(),Documentation NeedsFix help wanted,"https://golang.org/pkg/database/sql/#DB currently states:

> If the database has a concept of per-connection state, such state can only be reliably observed within a transaction.

This is no longer true: DB.Conn() was added to allow one to have a per-connection state without using transactions. DB documentation should be updated.",1.0,"database/sql: DB documentation should mention DB.Conn() - https://golang.org/pkg/database/sql/#DB currently states:

> If the database has a concept of per-connection state, such state can only be reliably observed within a transaction.

This is no longer true: DB.Conn() was added to allow one to have a per-connection state without using transactions. DB documentation should be updated.",1,database sql  db documentation should mention db conn       currently states       if the database has a concept of per connection state  such state can only be reliably observed within a transaction     this is no longer true  db conn   was added to allow one to have a per connection state without using transactions  db documentation should be updated ,1
22074,4771666350.0,IssuesEvent,2016-10-26 18:39:23,golang/go,https://api.github.com/repos/golang/go,opened,all: spelling inconsistency for networking terms,Documentation,"Some packages use `hostname` and others `host name`. The worst is the net package which uses both. It might be better to align to `host name` defined in RFC 7791.
```
Host name: This term and its equivalent, ""hostname"", have been
widely used but are not defined in [RFC1034], [RFC1035], [RFC1123], or [RFC2181]. 
```",1.0,"all: spelling inconsistency for networking terms - Some packages use `hostname` and others `host name`. The worst is the net package which uses both. It might be better to align to `host name` defined in RFC 7791.
```
Host name: This term and its equivalent, ""hostname"", have been
widely used but are not defined in [RFC1034], [RFC1035], [RFC1123], or [RFC2181]. 
```",1,all  spelling inconsistency for networking terms   some packages use  hostname  and others  host name   the worst is the net package which uses both  it might be better to align to  host name  defined in rfc          host name  this term and its equivalent   hostname   have been  widely used but are not defined in          or         ,1
21749,4744533323.0,IssuesEvent,2016-10-21 01:36:27,golang/go,https://api.github.com/repos/golang/go,closed,"unsafe: clarify what ""equivalent memory layout"" means",Documentation NeedsDecision,"One of package unsafe's valid patterns is:

> (1) Conversion of a *T1 to Pointer to *T2.
>
> Provided that T2 is no larger than T1 and that the two share an equivalent memory layout, this conversion allows reinterpreting data of one type as data of another type.

There have been arguments about what ""equivalent memory layout"" means (e.g., #16769, and the [""Guarantees for package unsafe""](https://groups.google.com/forum/#!topic/golang-dev/uCP4P12xS9Y) thread on golang-dev).

E.g., in C/C++, it's valid to cast from a pointer to a struct to a pointer to another struct containing a prefix of the fields to support things like casting from `struct sockaddr_in *` to `struct sockaddr *`.  But package unsafe gives an example of converting from `*float64` to `*uint64`, which wouldn't be valid in C/C++.

In [crypto/md5](https://github.com/golang/go/blob/master/src/crypto/md5/md5block.go#L41), there's code that converts `&p[0]` (of type `*byte`) to `*[16]uint32`, after verifying `len(p) >= 48`.  Assuming we think this should remain valid, that seems to suggest it's okay to convert `*[4]byte` to `*uint32`; i.e., that primitive data types need not exactly match in size either.

  * Aside: Technically this conversion isn't protected by rule 1 anyway, because T2 (`[16]uint32`) is larger than T1 (`byte`), but I think it's arguably within the spirit of the rule because of the length check.

My understanding of the phrase's intent was to disallow accessing pointer slots as non-pointer types.  E.g., you can't convert from `**int` to `*uintptr`, even though sizeof(`*int`) == sizeof(`uintptr`).

@dr2chase suggested that it could be interpreted to imply sensitivity to the machine's endianness, which may disallow converting `*uint64` to `*uint16`.

In https://go-review.googlesource.com/#/c/18640/ this wording was discussed:

> @alandonovan: Is ""equivalent memory layout"" defined anywhere?
> @rsc: No, but I'd rather not. I'm trying to write useful text without writing a legal document. I hope people can at least understand memory layouts and whether the conversion they want makes sense. If not they probably shouldn't be using unsafe.

Unfortunately it seems even within the Go compiler team there's disagreement/uncertainty on what ""equivalent memory layout"" means, even for concrete examples like converting `*uint64` to `*uint16`.

/cc @ianlancetaylor @randall77 ",1.0,"unsafe: clarify what ""equivalent memory layout"" means - One of package unsafe's valid patterns is:

> (1) Conversion of a *T1 to Pointer to *T2.
>
> Provided that T2 is no larger than T1 and that the two share an equivalent memory layout, this conversion allows reinterpreting data of one type as data of another type.

There have been arguments about what ""equivalent memory layout"" means (e.g., #16769, and the [""Guarantees for package unsafe""](https://groups.google.com/forum/#!topic/golang-dev/uCP4P12xS9Y) thread on golang-dev).

E.g., in C/C++, it's valid to cast from a pointer to a struct to a pointer to another struct containing a prefix of the fields to support things like casting from `struct sockaddr_in *` to `struct sockaddr *`.  But package unsafe gives an example of converting from `*float64` to `*uint64`, which wouldn't be valid in C/C++.

In [crypto/md5](https://github.com/golang/go/blob/master/src/crypto/md5/md5block.go#L41), there's code that converts `&p[0]` (of type `*byte`) to `*[16]uint32`, after verifying `len(p) >= 48`.  Assuming we think this should remain valid, that seems to suggest it's okay to convert `*[4]byte` to `*uint32`; i.e., that primitive data types need not exactly match in size either.

  * Aside: Technically this conversion isn't protected by rule 1 anyway, because T2 (`[16]uint32`) is larger than T1 (`byte`), but I think it's arguably within the spirit of the rule because of the length check.

My understanding of the phrase's intent was to disallow accessing pointer slots as non-pointer types.  E.g., you can't convert from `**int` to `*uintptr`, even though sizeof(`*int`) == sizeof(`uintptr`).

@dr2chase suggested that it could be interpreted to imply sensitivity to the machine's endianness, which may disallow converting `*uint64` to `*uint16`.

In https://go-review.googlesource.com/#/c/18640/ this wording was discussed:

> @alandonovan: Is ""equivalent memory layout"" defined anywhere?
> @rsc: No, but I'd rather not. I'm trying to write useful text without writing a legal document. I hope people can at least understand memory layouts and whether the conversion they want makes sense. If not they probably shouldn't be using unsafe.

Unfortunately it seems even within the Go compiler team there's disagreement/uncertainty on what ""equivalent memory layout"" means, even for concrete examples like converting `*uint64` to `*uint16`.

/cc @ianlancetaylor @randall77 ",1,unsafe  clarify what  equivalent memory layout  means   one of package unsafe s valid patterns is           conversion of a    to pointer to           provided that   is no larger than   and that the two share an equivalent memory layout  this conversion allows reinterpreting data of one type as data of another type     there have been arguments about what  equivalent memory layout  means  e g       and the     thread on golang dev      e g   in c c    it s valid to cast from a pointer to a struct to a pointer to another struct containing a prefix of the fields to support things like casting from  struct sockaddr in    to  struct sockaddr      but package unsafe gives an example of converting from      to       which wouldn t be valid in c c       in     there s code that converts   p    of type   byte   to        after verifying  len p          assuming we think this should remain valid  that seems to suggest it s okay to convert    byte  to       i e   that primitive data types need not exactly match in size either         aside  technically this conversion isn t protected by rule   anyway  because          is larger than     byte    but i think it s arguably within the spirit of the rule because of the length check     my understanding of the phrase s intent was to disallow accessing pointer slots as non pointer types   e g   you can t convert from    int  to   uintptr   even though sizeof   int      sizeof  uintptr          suggested that it could be interpreted to imply sensitivity to the machine s endianness  which may disallow converting      to          in   this wording was discussed        alandonovan  is  equivalent memory layout  defined anywhere      rsc  no  but i d rather not  i m trying to write useful text without writing a legal document  i hope people can at least understand memory layouts and whether the conversion they want makes sense  if not they probably shouldn t be using unsafe     unfortunately it seems even within the go compiler team there s disagreement uncertainty on what  equivalent memory layout  means  even for concrete examples like converting      to           cc  ianlancetaylor    ,1
17103,4127803243.0,IssuesEvent,2016-06-10 01:00:48,golang/go,https://api.github.com/repos/golang/go,closed,"encoding/csv: document that comments must begin at start of line, even when TrimLeadingSpace is true",Documentation NeedsDecision,"In looking at the docs and in the official example for csv.ReadAll() it's not clear what order TrimLeadingSpace processing occurs (i.e., prior to parsing for comments). It appears that comments are recognized *only* if they have no leading spaces. See test case here:  https://play.golang.org/p/m8GfvFWiEc
This is a modified version of the ReadAll() example: https://golang.org/pkg/encoding/csv/#example_Reader_ReadAll
If this is expected/defined behavior, it might be worth adding a note to the documentation or example on golang.org.

",1.0,"encoding/csv: document that comments must begin at start of line, even when TrimLeadingSpace is true - In looking at the docs and in the official example for csv.ReadAll() it's not clear what order TrimLeadingSpace processing occurs (i.e., prior to parsing for comments). It appears that comments are recognized *only* if they have no leading spaces. See test case here:  https://play.golang.org/p/m8GfvFWiEc
This is a modified version of the ReadAll() example: https://golang.org/pkg/encoding/csv/#example_Reader_ReadAll
If this is expected/defined behavior, it might be worth adding a note to the documentation or example on golang.org.

",1,encoding csv  document that comments must begin at start of line  even when trimleadingspace is true   in looking at the docs and in the official example for csv readall   it s not clear what order trimleadingspace processing occurs  i e   prior to parsing for comments   it appears that comments are recognized  only  if they have no leading spaces  see test case here      this is a modified version of the readall   example     if this is expected defined behavior  it might be worth adding a note to the documentation or example on golang org     ,1
150924,13385591088.0,IssuesEvent,2020-09-02 13:40:14,golang/go,https://api.github.com/repos/golang/go,closed,doc: include fix for #34437 in Go 1.14 release notes [1.14 backport],CherryPickApproved Documentation,"@dmitshur requested issue #38801 to be considered for backport to the next 1.14 minor release.

> @gopherbot Please open an issue to backport this to Go 1.14 when the fix is available. This is a documentation fix.
",1.0,"doc: include fix for #34437 in Go 1.14 release notes [1.14 backport] - @dmitshur requested issue #38801 to be considered for backport to the next 1.14 minor release.

> @gopherbot Please open an issue to backport this to Go 1.14 when the fix is available. This is a documentation fix.
",1,doc  include fix for    in go     release notes      dmitshur requested issue    to be considered for backport to the next     minor release      gopherbot please open an issue to backport this to go     when the fix is available  this is a documentation fix  ,1
436747,30567890355.0,IssuesEvent,2023-07-20 19:19:13,golang/go,https://api.github.com/repos/golang/go,reopened,doc: write release notes for Go 1.21,Documentation NeedsFix release-blocker umbrella,"This is the tracking issue for writing the Go 1.21 Release Notes. The version at tip can be viewed at https://tip.golang.org/doc/go1.21.

When the Go 1.21 Release Notes are complete, this should be closed, and a similar issue should be made for the next release. Previous issues are https://github.com/golang/go/issues/54202, https://github.com/golang/go/issues/51400, https://github.com/golang/go/issues/47694, https://github.com/golang/go/issues/44513, etc.

",1.0,"doc: write release notes for Go 1.21 - This is the tracking issue for writing the Go 1.21 Release Notes. The version at tip can be viewed at https://tip.golang.org/doc/go1.21.

When the Go 1.21 Release Notes are complete, this should be closed, and a similar issue should be made for the next release. Previous issues are https://github.com/golang/go/issues/54202, https://github.com/golang/go/issues/51400, https://github.com/golang/go/issues/47694, https://github.com/golang/go/issues/44513, etc.

",1,doc  write release notes for go       this is the tracking issue for writing the go     release notes  the version at tip can be viewed at      when the go     release notes are complete  this should be closed  and a similar issue should be made for the next release  previous issues are         etc     ,1
176411,14581262968.0,IssuesEvent,2020-12-18 10:27:08,golang/go,https://api.github.com/repos/golang/go,closed,x/website: Mention specifically that minor version is not allowed in Go directives,Documentation NeedsDecision,"I was trying out `Go` modules and find out that If I specify `1.15.4` instead of `1.15` my build failed with the following error:

```
invalid go version '1.15.4': must match format 1.23
```

I referred to this documentation https://golang.org/ref/mod#go-mod-file-go. I think it will be better If we also recommend not to use the minor version or give examples of the wrong values for better understanding. ",1.0,"x/website: Mention specifically that minor version is not allowed in Go directives - I was trying out `Go` modules and find out that If I specify `1.15.4` instead of `1.15` my build failed with the following error:

```
invalid go version '1.15.4': must match format 1.23
```

I referred to this documentation https://golang.org/ref/mod#go-mod-file-go. I think it will be better If we also recommend not to use the minor version or give examples of the wrong values for better understanding. ",1,x website  mention specifically that minor version is not allowed in go directives   i was trying out  go  modules and find out that if i specify         instead of       my build failed with the following error          invalid go version          must match format             i referred to this documentation   i think it will be better if we also recommend not to use the minor version or give examples of the wrong values for better understanding  ,1
70089,22908479434.0,IssuesEvent,2022-07-16 00:41:16,scipy/scipy,https://api.github.com/repos/scipy/scipy,opened,BUG: `scipy.optimize.linprog` reports optimal for trivially infeasible MILP,defect,"### Describe your issue.

In anticipation of the upcoming 1.9.0 release, I've been trying to update [cvxpy](https://github.com/cvxpy/cvxpy) to use SciPy's newly-introduced MILP functionality. I've been working with SciPy `1.9.0rc2`. You can find [my draft fork of cvxpy here](https://github.com/tasseff/cvxpy) and the associated issue [here](https://github.com/cvxpy/cvxpy/issues/1443). While performing cvxpy unit tests, I came across [a MILP problem](https://github.com/cvxpy/cvxpy/blob/8cc75a8616ac4643134e25147033054d92d89951/cvxpy/tests/test_mip_vars.py#L92-L97) of the form
```
Minimize
 obj: t
Subject To
 c1: y = 0.5
Bounds
 0 <= t
General
 y
End
```
The problem is clearly infeasible, as `y` cannot be both integer (indicated by the `General` entry) and equal to `0.5`. This would be solved using SciPy's new MILP functionality with the script I've added below. Curiously, the solution status is reported as optimal, although it should clearly be reported as infeasible. (It is even acknowledged as infeasible in the rest of the log.) Replacing the `options` flag with `options={'disp': True, 'presolve': False}` provides the expected result, i.e., infeasibility is proven. This suggests the issue may be with the version of HiGHS being used by SciPy, and more specifically, its presolve routine.

Indeed, building from [the HiGHS master branch](https://github.com/ERGO-Code/HiGHS) and solving using the above `.lp` problem provides the correct logging output, i.e., the problem is identified as infeasible. A similar issue raised [here](https://github.com/ERGO-Code/HiGHS/issues/902) suggests that this issue may not have been corrected, but another issue [here](https://github.com/ERGO-Code/HiGHS/issues/907) has been closed. Suffice to say, I think this is a trivial enough example where the correct behavior needs to be ensured by both SciPy and HiGHS. You may want to consider updating the version of HiGHS used in the 1.9.0 release or, if that is not enough, providing a fix within HiGHS or waiting for this fix before releasing SciPy 1.9.0.

### Reproducing Code Example

```python
import numpy as np
import scipy

res = scipy.optimize.linprog(
    c=[1.0, 0.0],
    A_eq=[[0.0, 1.0]],
    b_eq=[[0.5]],
    bounds=[(0.0, None), (None, None)],
    integrality=[0, 1],
    options={'disp': True})
```


### Error message

```shell
Presolving model
0 rows, 0 cols, 0 nonzeros
0 rows, 0 cols, 0 nonzeros
Presolve: Optimal
WARNING: Untransformed solution with objective 0 is violated by 0.5 for the original model

Solving report
  Status            Optimal
  Primal bound      0
  Dual bound        0
  Solution status   infeasible
                    0 (objective)
                    0 (bound viol.)
                    0.5 (int. viol.)
                    0 (row viol.)
  Timing            0.01 (total)
                    0.00 (presolve)
                    0.00 (postsolve)
  Nodes             0
  LP iterations     0 (total)
                    0 (strong br.)
                    0 (separation)
                    0 (heuristics)
```


### SciPy/NumPy/Python version information

1.9.0rc2 1.22.3 sys.version_info(major=3, minor=9, micro=12, releaselevel='final', serial=0)",1.0,"BUG: `scipy.optimize.linprog` reports optimal for trivially infeasible MILP - ### Describe your issue.

In anticipation of the upcoming 1.9.0 release, I've been trying to update [cvxpy](https://github.com/cvxpy/cvxpy) to use SciPy's newly-introduced MILP functionality. I've been working with SciPy `1.9.0rc2`. You can find [my draft fork of cvxpy here](https://github.com/tasseff/cvxpy) and the associated issue [here](https://github.com/cvxpy/cvxpy/issues/1443). While performing cvxpy unit tests, I came across [a MILP problem](https://github.com/cvxpy/cvxpy/blob/8cc75a8616ac4643134e25147033054d92d89951/cvxpy/tests/test_mip_vars.py#L92-L97) of the form
```
Minimize
 obj: t
Subject To
 c1: y = 0.5
Bounds
 0 <= t
General
 y
End
```
The problem is clearly infeasible, as `y` cannot be both integer (indicated by the `General` entry) and equal to `0.5`. This would be solved using SciPy's new MILP functionality with the script I've added below. Curiously, the solution status is reported as optimal, although it should clearly be reported as infeasible. (It is even acknowledged as infeasible in the rest of the log.) Replacing the `options` flag with `options={'disp': True, 'presolve': False}` provides the expected result, i.e., infeasibility is proven. This suggests the issue may be with the version of HiGHS being used by SciPy, and more specifically, its presolve routine.

Indeed, building from [the HiGHS master branch](https://github.com/ERGO-Code/HiGHS) and solving using the above `.lp` problem provides the correct logging output, i.e., the problem is identified as infeasible. A similar issue raised [here](https://github.com/ERGO-Code/HiGHS/issues/902) suggests that this issue may not have been corrected, but another issue [here](https://github.com/ERGO-Code/HiGHS/issues/907) has been closed. Suffice to say, I think this is a trivial enough example where the correct behavior needs to be ensured by both SciPy and HiGHS. You may want to consider updating the version of HiGHS used in the 1.9.0 release or, if that is not enough, providing a fix within HiGHS or waiting for this fix before releasing SciPy 1.9.0.

### Reproducing Code Example

```python
import numpy as np
import scipy

res = scipy.optimize.linprog(
    c=[1.0, 0.0],
    A_eq=[[0.0, 1.0]],
    b_eq=[[0.5]],
    bounds=[(0.0, None), (None, None)],
    integrality=[0, 1],
    options={'disp': True})
```


### Error message

```shell
Presolving model
0 rows, 0 cols, 0 nonzeros
0 rows, 0 cols, 0 nonzeros
Presolve: Optimal
WARNING: Untransformed solution with objective 0 is violated by 0.5 for the original model

Solving report
  Status            Optimal
  Primal bound      0
  Dual bound        0
  Solution status   infeasible
                    0 (objective)
                    0 (bound viol.)
                    0.5 (int. viol.)
                    0 (row viol.)
  Timing            0.01 (total)
                    0.00 (presolve)
                    0.00 (postsolve)
  Nodes             0
  LP iterations     0 (total)
                    0 (strong br.)
                    0 (separation)
                    0 (heuristics)
```


### SciPy/NumPy/Python version information

1.9.0rc2 1.22.3 sys.version_info(major=3, minor=9, micro=12, releaselevel='final', serial=0)",0,bug   scipy optimize linprog  reports optimal for trivially infeasible milp       describe your issue   in anticipation of the upcoming       release  i ve been trying to update     to use scipy s newly introduced milp functionality  i ve been working with scipy          you can find     and the associated issue     while performing cvxpy unit tests  i came across     of the form       minimize   obj  t  subject to      y        bounds        t  general   y  end       the problem is clearly infeasible  as  y  cannot be both integer  indicated by the  general  entry  and equal to        this would be solved using scipy s new milp functionality with the script i ve added below  curiously  the solution status is reported as optimal  although it should clearly be reported as infeasible   it is even acknowledged as infeasible in the rest of the log   replacing the  options  flag with  options   disp   true   presolve   false   provides the expected result  i e   infeasibility is proven  this suggests the issue may be with the version of highs being used by scipy  and more specifically  its presolve routine     indeed  building from     and solving using the above   lp  problem provides the correct logging output  i e   the problem is identified as infeasible  a similar issue raised     suggests that this issue may not have been corrected  but another issue     has been closed  suffice to say  i think this is a trivial enough example where the correct behavior needs to be ensured by both scipy and highs  you may want to consider updating the version of highs used in the       release or  if that is not enough  providing a fix within highs or waiting for this fix before releasing scipy             reproducing code example     python import numpy as np  import scipy    res   scipy optimize linprog       c         a eq          b eq          bounds         integrality         options   disp   true             error message     shell presolving model    rows    cols    nonzeros    rows    cols    nonzeros  presolve  optimal  warning  untransformed solution with objective   is violated by     for the original model    solving report    status            optimal    primal bound           dual bound             solution status   infeasible                         objective                          bound viol                             int  viol                           row viol      timing                 total                            presolve                            postsolve     nodes                  lp iterations        total                          strong br                           separation                          heuristics            scipy numpy python version information              sys version info major    minor    micro    releaselevel  final   serial   ,0
246163,18837853004.0,IssuesEvent,2021-11-11 04:48:10,golang/go,https://api.github.com/repos/golang/go,closed,sync: clarify if it's valid to call Map methods inside the Map.Range callback,Documentation help wanted NeedsFix,"Map is documented as safe for concurrent use, so I understand it is safe to call a method like LoadAndDelete while Range is running in another goroutine, for example.

However, what isn't clear is whether I can call a method like LoadAndDelete in Range's callback. Technically it's not a concurrent call, as it's happening on the same goroutine - it's just a nested call, as it happens within Range.

Is that supported? From my reading of the code it seems like it shouldn't cause a data race. I wonder if it could lead to undesirable effects however, such as if I delete a key that I haven't ranged over yet, or if I keep adding more keys and potentially make the range run for a long time.

I don't know what the answer is or what it should be, but I think the docs could be a bit clearer.

cc  @rsc @ianlancetaylor @dvyukov @aclements as per https://dev.golang.org/owners",1.0,"sync: clarify if it's valid to call Map methods inside the Map.Range callback - Map is documented as safe for concurrent use, so I understand it is safe to call a method like LoadAndDelete while Range is running in another goroutine, for example.

However, what isn't clear is whether I can call a method like LoadAndDelete in Range's callback. Technically it's not a concurrent call, as it's happening on the same goroutine - it's just a nested call, as it happens within Range.

Is that supported? From my reading of the code it seems like it shouldn't cause a data race. I wonder if it could lead to undesirable effects however, such as if I delete a key that I haven't ranged over yet, or if I keep adding more keys and potentially make the range run for a long time.

I don't know what the answer is or what it should be, but I think the docs could be a bit clearer.

cc  @rsc @ianlancetaylor @dvyukov @aclements as per https://dev.golang.org/owners",1,sync  clarify if it s valid to call map methods inside the map range callback   map is documented as safe for concurrent use  so i understand it is safe to call a method like loadanddelete while range is running in another goroutine  for example     however  what isn t clear is whether i can call a method like loadanddelete in range s callback  technically it s not a concurrent call  as it s happening on the same goroutine   it s just a nested call  as it happens within range     is that supported  from my reading of the code it seems like it shouldn t cause a data race  i wonder if it could lead to undesirable effects however  such as if i delete a key that i haven t ranged over yet  or if i keep adding more keys and potentially make the range run for a long time     i don t know what the answer is or what it should be  but i think the docs could be a bit clearer     cc   rsc  ianlancetaylor  dvyukov  aclements as per  ,1
160125,12504223363.0,IssuesEvent,2020-06-02 08:39:35,ceph/ceph-csi,https://api.github.com/repos/ceph/ceph-csi,closed,jjb-deploy and jjb-validate CI jobs show the wrong logs,bug component/testing,"# Describe the bug #

The OpenShift batch job that gets created starts a container indirectly. The script that parses the logs from the batch job, uses the logs from the 1st container that gets listed. This can be a container with old logs, showing jobs failed in the Jenkins WebUI and failed state in PRs.

Corrections need to be made in [`deploy/jjb.sh`](https://github.com/ceph/ceph-csi/blob/ci/centos/deploy/jjb.sh#L34). Possibly by adding a unique label to the container that is created by the batch job, and check the pod that has this label.",1.0,"jjb-deploy and jjb-validate CI jobs show the wrong logs - # Describe the bug #

The OpenShift batch job that gets created starts a container indirectly. The script that parses the logs from the batch job, uses the logs from the 1st container that gets listed. This can be a container with old logs, showing jobs failed in the Jenkins WebUI and failed state in PRs.

Corrections need to be made in [`deploy/jjb.sh`](https://github.com/ceph/ceph-csi/blob/ci/centos/deploy/jjb.sh#L34). Possibly by adding a unique label to the container that is created by the batch job, and check the pod that has this label.",0,jjb deploy and jjb validate ci jobs show the wrong logs     describe the bug      the openshift batch job that gets created starts a container indirectly  the script that parses the logs from the batch job  uses the logs from the   container that gets listed  this can be a container with old logs  showing jobs failed in the jenkins webui and failed state in prs     corrections need to be made in     possibly by adding a unique label to the container that is created by the batch job  and check the pod that has this label ,0
108441,23607835198.0,IssuesEvent,2022-08-24 09:45:38,pwa-builder/PWABuilder,https://api.github.com/repos/pwa-builder/PWABuilder,closed,[VSCODE] npm run dev-server exited with code 127,bug :bug: needs triage :mag: vscode,"### What happened?

Oh, just the usual stuff. You install something in the hope of getting somewhere, and then BAM! You're in a world of hurt trying to figure out what went wrong. Considering quitting (web) development once again to avoid depression. Why do you constantly make the hype ... instead of doing a proper job?

I followed the instructions on the PWABuilder extension page, and ended up with:
```
""cd /newPWA"" && npm run dev-server exited with code 127
--> Sending SIGTERM to other processes..
[swa] node ""/Users/ ... /.npm/_npx/bc929ef4963a6f17/node_modules/@azure/static-web-apps-cli/dist/msha/server.js"" exited with code SIGTERM
✖ SWA emulator stoped because SWA emulator exited with code SIGTERM.
username@MacBook-Pro newPWA % npm run build -prod
npm WARN config production Use `--omit=dev` instead.

> pwa-starter@0.0.1 build
> tsc && vite build

sh: tsc: command not found
```

### What do you expect to happen?

Well, at least something that makes sense. Not, asking for triple rainbows here ... just a simple thing that just works.

### What version of VS Code are you using?

_No response_

### Relevant log output

```shell
""cd /newPWA"" && npm run dev-server exited with code 127
--> Sending SIGTERM to other processes..
[swa] node ""/Users/ ... /.npm/_npx/bc929ef4963a6f17/node_modules/@azure/static-web-apps-cli/dist/msha/server.js"" exited with code SIGTERM
✖ SWA emulator stoped because SWA emulator exited with code SIGTERM.
username@MacBook-Pro newPWA % npm run build -prod
npm WARN config production Use `--omit=dev` instead.

> pwa-starter@0.0.1 build
> tsc && vite build

sh: tsc: command not found
```
```


### Are you using the latest version of the VS Code extension?

- [X] I am using the latest version of the VS Code extension",1.0,"[VSCODE] npm run dev-server exited with code 127 - ### What happened?

Oh, just the usual stuff. You install something in the hope of getting somewhere, and then BAM! You're in a world of hurt trying to figure out what went wrong. Considering quitting (web) development once again to avoid depression. Why do you constantly make the hype ... instead of doing a proper job?

I followed the instructions on the PWABuilder extension page, and ended up with:
```
""cd /newPWA"" && npm run dev-server exited with code 127
--> Sending SIGTERM to other processes..
[swa] node ""/Users/ ... /.npm/_npx/bc929ef4963a6f17/node_modules/@azure/static-web-apps-cli/dist/msha/server.js"" exited with code SIGTERM
✖ SWA emulator stoped because SWA emulator exited with code SIGTERM.
username@MacBook-Pro newPWA % npm run build -prod
npm WARN config production Use `--omit=dev` instead.

> pwa-starter@0.0.1 build
> tsc && vite build

sh: tsc: command not found
```

### What do you expect to happen?

Well, at least something that makes sense. Not, asking for triple rainbows here ... just a simple thing that just works.

### What version of VS Code are you using?

_No response_

### Relevant log output

```shell
""cd /newPWA"" && npm run dev-server exited with code 127
--> Sending SIGTERM to other processes..
[swa] node ""/Users/ ... /.npm/_npx/bc929ef4963a6f17/node_modules/@azure/static-web-apps-cli/dist/msha/server.js"" exited with code SIGTERM
✖ SWA emulator stoped because SWA emulator exited with code SIGTERM.
username@MacBook-Pro newPWA % npm run build -prod
npm WARN config production Use `--omit=dev` instead.

> pwa-starter@0.0.1 build
> tsc && vite build

sh: tsc: command not found
```
```


### Are you using the latest version of the VS Code extension?

- [X] I am using the latest version of the VS Code extension",0,  npm run dev server exited with code         what happened   oh  just the usual stuff  you install something in the hope of getting somewhere  and then bam  you re in a world of hurt trying to figure out what went wrong  considering quitting  web  development once again to avoid depression  why do you constantly make the hype     instead of doing a proper job     i followed the instructions on the pwabuilder extension page  and ended up with         cd  newpwa     npm run dev server exited with code        sending sigterm to other processes      node   users        npm  npx   node modules  azure static web apps cli dist msha server js  exited with code sigterm  ✖ swa emulator stoped because swa emulator exited with code sigterm   username macbook pro newpwa   npm run build  prod  npm warn config production use    omit dev  instead       pwa starter       build    tsc    vite build    sh  tsc  command not found           what do you expect to happen   well  at least something that makes sense  not  asking for triple rainbows here     just a simple thing that just works       what version of vs code are you using    no response       relevant log output     shell  cd  newpwa     npm run dev server exited with code        sending sigterm to other processes      node   users        npm  npx   node modules  azure static web apps cli dist msha server js  exited with code sigterm  ✖ swa emulator stoped because swa emulator exited with code sigterm   username macbook pro newpwa   npm run build  prod  npm warn config production use    omit dev  instead       pwa starter       build    tsc    vite build    sh  tsc  command not found                are you using the latest version of the vs code extension       i am using the latest version of the vs code extension,0
26821,5290372201.0,IssuesEvent,2017-02-08 19:43:45,golang/go,https://api.github.com/repos/golang/go,closed,"doc: from contribute.html it is not clear what ""CL"" is",Documentation,"contribute.html uses the acronym ""CL"" without defining it first:

> If your change relates to an open issue, please add a comment to the issue announcing your proposed fix, including a link to your CL. 

Not understood or misunderstood words can block one's understanding of the document or even cause one to abandon the subject. It would be better to introduce the acronym immediately after the first occurrence of ""change list"", e.g.

> Unless explicitly told otherwise, such as in the discussion leading up to sending in the **change list (CL)**, it's better not to specify a reviewer",1.0,"doc: from contribute.html it is not clear what ""CL"" is - contribute.html uses the acronym ""CL"" without defining it first:

> If your change relates to an open issue, please add a comment to the issue announcing your proposed fix, including a link to your CL. 

Not understood or misunderstood words can block one's understanding of the document or even cause one to abandon the subject. It would be better to introduce the acronym immediately after the first occurrence of ""change list"", e.g.

> Unless explicitly told otherwise, such as in the discussion leading up to sending in the **change list (CL)**, it's better not to specify a reviewer",1,doc  from contribute html it is not clear what  cl  is   contribute html uses the acronym  cl  without defining it first       if your change relates to an open issue  please add a comment to the issue announcing your proposed fix  including a link to your cl      not understood or misunderstood words can block one s understanding of the document or even cause one to abandon the subject  it would be better to introduce the acronym immediately after the first occurrence of  change list   e g       unless explicitly told otherwise  such as in the discussion leading up to sending in the   change list  cl     it s better not to specify a reviewer,1
81282,23429151267.0,IssuesEvent,2022-08-14 21:15:44,matplotlib/matplotlib,https://api.github.com/repos/matplotlib/matplotlib,closed,setuptools_scm-git-archive is obsolete,Build Maintenance,"### Bug summary

setuptools_scm starting with version 7 has native support for git archives, so this dep can go away ; in fact, the [project homepage](https://github.com/Changaco/setuptools_scm_git_archive) is a migration guide!

",1.0,"setuptools_scm-git-archive is obsolete - ### Bug summary

setuptools_scm starting with version 7 has native support for git archives, so this dep can go away ; in fact, the [project homepage](https://github.com/Changaco/setuptools_scm_git_archive) is a migration guide!

",0,setuptools scm git archive is obsolete       bug summary    setuptools scm starting with version   has native support for git archives  so this dep can go away   in fact  the     is a migration guide     ,0
135076,10961625512.0,IssuesEvent,2019-11-27 15:43:26,input-output-hk/cardano-ledger-specs,https://api.github.com/repos/input-output-hk/cardano-ledger-specs,closed,Generate _Delegate_ Certificates,executable-model :gear: property test :slot_machine: shelley :shell:,"Extend `genDCert` to also generate `Delegate` certs.

Do this in concert with testing the  property `credentialMappingAfterDelegation` against the LEDGER STS Trace generator.",1.0,"Generate _Delegate_ Certificates - Extend `genDCert` to also generate `Delegate` certs.

Do this in concert with testing the  property `credentialMappingAfterDelegation` against the LEDGER STS Trace generator.",0,generate  delegate  certificates   extend  gendcert  to also generate  delegate  certs     do this in concert with testing the  property  credentialmappingafterdelegation  against the ledger sts trace generator ,0
395242,27061616551.0,IssuesEvent,2023-02-13 20:15:00,golang/go,https://api.github.com/repos/golang/go,closed,math/big: document unsuitability for cryptography,Documentation,"We mentioned in the Go 1.20 release notes that following our own migration off math/big for cryptography (#52182), the package makes an especially bad choice for cryptographic use. The package docs should mention that too.",1.0,"math/big: document unsuitability for cryptography - We mentioned in the Go 1.20 release notes that following our own migration off math/big for cryptography (#52182), the package makes an especially bad choice for cryptographic use. The package docs should mention that too.",1,math big  document unsuitability for cryptography   we mentioned in the go     release notes that following our own migration off math big for cryptography       the package makes an especially bad choice for cryptographic use  the package docs should mention that too ,1
236780,19574085092.0,IssuesEvent,2022-01-04 13:33:28,wix/stylable,https://api.github.com/repos/wix/stylable,opened,Performance Benchmark Testing,tests core research,"### Describe your issue

So far we've gotten by without performing any sort of dedicated performance benchmark across time. This led to us sometimes being surprised by some regressions as they were reported by our users.

This issue is a placeholder for two tasks:
- Figure out our current performance bottlenecks and see if they require immediate handling
- Suggest a reproducible way of running this benchmark across time

### Additional Context

_No response_",1.0,"Performance Benchmark Testing - ### Describe your issue

So far we've gotten by without performing any sort of dedicated performance benchmark across time. This led to us sometimes being surprised by some regressions as they were reported by our users.

This issue is a placeholder for two tasks:
- Figure out our current performance bottlenecks and see if they require immediate handling
- Suggest a reproducible way of running this benchmark across time

### Additional Context

_No response_",0,performance benchmark testing       describe your issue  so far we ve gotten by without performing any sort of dedicated performance benchmark across time  this led to us sometimes being surprised by some regressions as they were reported by our users     this issue is a placeholder for two tasks     figure out our current performance bottlenecks and see if they require immediate handling    suggest a reproducible way of running this benchmark across time      additional context   no response ,0
14750,3881178911.0,IssuesEvent,2016-04-13 02:29:02,golang/go,https://api.github.com/repos/golang/go,closed,html/template: Provide an example of loading a template from a file and executing it.,Documentation,"by **kburkeorg**:

<pre>Most websites store their templates in files on disk. It would be convenient if the
documentation provided an example with template data stored in a file, then loaded into
memory and executed with variables and a byte buffer.</pre>",1.0,"html/template: Provide an example of loading a template from a file and executing it. - by **kburkeorg**:

<pre>Most websites store their templates in files on disk. It would be convenient if the
documentation provided an example with template data stored in a file, then loaded into
memory and executed with variables and a byte buffer.</pre>",1,html template  provide an example of loading a template from a file and executing it    by   kburkeorg      most websites store their templates in files on disk  it would be convenient if the documentation provided an example with template data stored in a file  then loaded into memory and executed with variables and a byte buffer  ,1
575,8679254875.0,IssuesEvent,2018-11-30 22:56:36,dotnet/corefx,https://api.github.com/repos/dotnet/corefx,closed,OnCompleted events should run after pipe is completed,area-System.IO.Pipelines tenet-reliability,So all blocks are returned at that point and it's safe to `Dispose` the pool.,True,OnCompleted events should run after pipe is completed - So all blocks are returned at that point and it's safe to `Dispose` the pool.,0,oncompleted events should run after pipe is completed   so all blocks are returned at that point and it s safe to  dispose  the pool ,0
46027,7229534937.0,IssuesEvent,2018-02-11 20:42:23,golang/go,https://api.github.com/repos/golang/go,closed,doc: An unnecessary comment exists in CONTRIBUTING.md,Documentation NeedsFix,"The following unnecessary comment exists in CONTRIBUTING.md.

> We do not accept GitHub pull requests

https://github.com/golang/go/blob/master/CONTRIBUTING.md

It has been removed in README.md, but it still exists in CONTRIBUTING.md.
https://go-review.googlesource.com/c/go/+/92995",1.0,"doc: An unnecessary comment exists in CONTRIBUTING.md - The following unnecessary comment exists in CONTRIBUTING.md.

> We do not accept GitHub pull requests

https://github.com/golang/go/blob/master/CONTRIBUTING.md

It has been removed in README.md, but it still exists in CONTRIBUTING.md.
https://go-review.googlesource.com/c/go/+/92995",1,doc  an unnecessary comment exists in contributing md   the following unnecessary comment exists in contributing md       we do not accept github pull requests         it has been removed in readme md  but it still exists in contributing md    ,1
444690,31142595228.0,IssuesEvent,2023-08-16 02:08:06,golang/go,https://api.github.com/repos/golang/go,closed,bufio: Scanner considers a buffer of length = len(token) as not enough,Documentation help wanted NeedsFix,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.15 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Haven't tried

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/k0nst4nt1n/Library/Caches/go-build""
GOENV=""/Users/k0nst4nt1n/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/k0nst4nt1n/_gopath/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/k0nst4nt1n/_gopath""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/Cellar/go/1.15/libexec""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/1.15/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/3q/jr3whwkn13ld3j1s1xms0v4w0000gp/T/go-build070878361=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

Golang bufio.Scanner considers a buffer of length = len(token) as not enough, please see example below:
(full code is here https://play.golang.org/p/3e95HG3j4H-)

```
func main() {
	d1 := ""12"" // data size == 2
	r1 := strings.NewReader(d1)
	
	s1 := bufio.NewScanner(r1)
	s1.Split(bufio.ScanLines)
	s1.Buffer(make([]byte, len(d1)), len(d1)) // buf size == 2
	
	_ = s1.Scan()
	fmt.Printf(""Token=%s, Err=%v\n"", s1.Text(), s1.Err())
}
```

### What did you expect to see?

No error (output: `Token=12, Err=<nil>`)



### What did you see instead?

Error (output: `Token=, Err=bufio.Scanner: token too long`)
",1.0,"bufio: Scanner considers a buffer of length = len(token) as not enough - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.15 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Haven't tried

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/k0nst4nt1n/Library/Caches/go-build""
GOENV=""/Users/k0nst4nt1n/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/k0nst4nt1n/_gopath/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/k0nst4nt1n/_gopath""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/Cellar/go/1.15/libexec""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/1.15/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/3q/jr3whwkn13ld3j1s1xms0v4w0000gp/T/go-build070878361=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

Golang bufio.Scanner considers a buffer of length = len(token) as not enough, please see example below:
(full code is here https://play.golang.org/p/3e95HG3j4H-)

```
func main() {
	d1 := ""12"" // data size == 2
	r1 := strings.NewReader(d1)
	
	s1 := bufio.NewScanner(r1)
	s1.Split(bufio.ScanLines)
	s1.Buffer(make([]byte, len(d1)), len(d1)) // buf size == 2
	
	_ = s1.Scan()
	fmt.Printf(""Token=%s, Err=%v\n"", s1.Text(), s1.Err())
}
```

### What did you expect to see?

No error (output: `Token=12, Err=<nil>`)



### What did you see instead?

Error (output: `Token=, Err=bufio.Scanner: token too long`)
",1,bufio  scanner considers a buffer of length   len token  as not enough         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version            go version  go version     darwin             does this issue reproduce with the latest release     haven t tried        what operating system and processor architecture are you using   go env          go env  output           goarch      gobin     gocache   users   library caches go build   goenv   users   library application support go env   goexe     goflags     gohostarch      gohostos  darwin   goinsecure     gomodcache   users    gopath pkg mod   gonoproxy     gonosumdb     goos  darwin   gopath   users    gopath   goprivate     goproxy     goroot   usr local cellar go     libexec   gosumdb  sum golang org   gotmpdir     gotooldir   usr local cellar go     libexec pkg tool darwin     gccgo  gccgo   ar  ar   cc  clang   cxx  clang     cgo enabled      gomod     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders     t go    tmp go build  gno record gcc switches  fno common             what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best          golang bufio scanner considers a buffer of length   len token  as not enough  please see example below    full code is here           func main      	            data size       	     strings newreader     	  	     bufio newscanner     	  split bufio scanlines   	  buffer make  byte  len      len        buf size       	  	      scan    	fmt printf  token  s  err  v n     text      err                   what did you expect to see     no error  output   token    err                what did you see instead     error  output   token   err bufio scanner  token too long    ,1
33468,6206523444.0,IssuesEvent,2017-07-06 18:37:28,golang/go,https://api.github.com/repos/golang/go,opened,doc: document that FreeBSD 9 support will be removed in Go 1.10,Documentation,"Maybe I missed a decision, but I thought we needed to document in Go 1.9 release notes that Go 1.10 will remove support for FreeBSD 9. I don't see that there.",1.0,"doc: document that FreeBSD 9 support will be removed in Go 1.10 - Maybe I missed a decision, but I thought we needed to document in Go 1.9 release notes that Go 1.10 will remove support for FreeBSD 9. I don't see that there.",1,doc  document that freebsd   support will be removed in go       maybe i missed a decision  but i thought we needed to document in go     release notes that go     will remove support for freebsd    i don t see that there ,1
91664,3857102452.0,IssuesEvent,2016-04-07 03:21:46,gama-platform/gama,https://api.github.com/repos/gama-platform/gama,closed,ROI selection mode not left after releasing shift key and obtaining menu ,> Bug Affects Usability Concerns Interface Display OpenGL OS All Priority High Version Git,"Invoking the ROI selection once (shift + drag), then dismissing the menu, lets the display in a state where a normal drag (without shift) acts like a ROI selection. Pressing shift once allows to leave this ""strange"" mode.",1.0,"ROI selection mode not left after releasing shift key and obtaining menu  - Invoking the ROI selection once (shift + drag), then dismissing the menu, lets the display in a state where a normal drag (without shift) acts like a ROI selection. Pressing shift once allows to leave this ""strange"" mode.",0,roi selection mode not left after releasing shift key and obtaining menu    invoking the roi selection once  shift   drag   then dismissing the menu  lets the display in a state where a normal drag  without shift  acts like a roi selection  pressing shift once allows to leave this  strange  mode ,0
146603,23093707819.0,IssuesEvent,2022-07-26 17:23:09,ParabolInc/parabol,https://api.github.com/repos/ParabolInc/parabol,closed,Pro limitations discovery,design Story Points: 13 Squad: 3,"We want to de-risk any ideas we have in pursuing these goals:
- Long-term goal — Maximize conversion of Pro-qualified accounts into a tier that matches the need
- Short-term goal — Validate limitations as a viable lever for converting Pro-qualified accounts

As a squad we’ll:
- 1) ask open questions to identify our riskiest assumptions
- 2) discuss a wide range of ideas and their pros/cons
- 3) narrow it down to a few ideas to focus on and
- 4) capture next steps

We’ll use a FigJam artifact to begin

### Acceptance criteria
- The squad participates in the process async
- The squad syncs to review and agree on a way forward
- We document any learning and takeaways
- We capture next steps as tasks and issues

### Estimated effort
- 13 hours
  - up to ~5 hours per squad member async
  - ~5 cumulative hours for a sync call
  - up to a few hours setting up and breaking down the work into issues, etc.",1.0,"Pro limitations discovery - We want to de-risk any ideas we have in pursuing these goals:
- Long-term goal — Maximize conversion of Pro-qualified accounts into a tier that matches the need
- Short-term goal — Validate limitations as a viable lever for converting Pro-qualified accounts

As a squad we’ll:
- 1) ask open questions to identify our riskiest assumptions
- 2) discuss a wide range of ideas and their pros/cons
- 3) narrow it down to a few ideas to focus on and
- 4) capture next steps

We’ll use a FigJam artifact to begin

### Acceptance criteria
- The squad participates in the process async
- The squad syncs to review and agree on a way forward
- We document any learning and takeaways
- We capture next steps as tasks and issues

### Estimated effort
- 13 hours
  - up to ~5 hours per squad member async
  - ~5 cumulative hours for a sync call
  - up to a few hours setting up and breaking down the work into issues, etc.",0,pro limitations discovery   we want to de risk any ideas we have in pursuing these goals     long term goal — maximize conversion of pro qualified accounts into a tier that matches the need    short term goal — validate limitations as a viable lever for converting pro qualified accounts    as a squad we’ll        ask open questions to identify our riskiest assumptions       discuss a wide range of ideas and their pros cons       narrow it down to a few ideas to focus on and       capture next steps    we’ll use a figjam artifact to begin        acceptance criteria    the squad participates in the process async    the squad syncs to review and agree on a way forward    we document any learning and takeaways    we capture next steps as tasks and issues        estimated effort      hours      up to    hours per squad member async         cumulative hours for a sync call      up to a few hours setting up and breaking down the work into issues  etc ,0
193595,15381051584.0,IssuesEvent,2021-03-02 22:02:12,golang/go,https://api.github.com/repos/golang/go,closed,x/website: various mistakes in documentation on modules,Documentation NeedsFix,"I read the new documentation on modules (which is great, btw) and took notes of mistakes I encountered.

https://golang.org/doc/modules/gomod-ref

1. Contradiction: The description for 'replacement-path' says:

	""[...] If this is a module path, you must specify a \_replacement-version\_ value. [...]""
	But the following example shows the replacement of a module path without a replacement version value:
	""`replace example.com/othermodule => example.com/myfork/othermodule`""

2. Section 'exclude', description of 'module-version"":

	""If this version number is omitted, all versions of the module are replaced with the content on the right side of the arrow.""

	But an 'exclude' directive doesn't have an arrow. This sentence seems to be copy&pasted from the 'replace' directive and wrong.

3. Contradiction:

	""These directives are ignored in modules that depend on the current module.""
	vs. later
	""These directives are ignored in modules that are dependencies of the current module.""
	Which one is it?

4. Formatting: In the first example one line is not correctly indented.

5. Formatting: ""\_replacement-version\_"", ""\_replacement-path\_"". The underscores are probably not intended, but unsupported Markdown syntax.

https://golang.org/doc/tutorial/create-module

6. ""This tutorial's sequence includes six brief topics [...]""

	Followed by a numbered list of seven topics. s/six/seven/

https://golang.org/doc/tutorial/call-module-code

7. Broken link: ""Here, the replace directive [...]""

8. Broken tutorial: ""In the hello directory, run go build to make Go locate the module and add it as a dependency to the go.mod file.""

	Starting with Go 1.16 'go build' doesn't add dependencies anymore, which breaks this tutorial (similar to #43672).

https://golang.org/doc/tutorial/getting-started

9. Outdated description: ""3. On the Doc tab, under Index, [...]""

	The former Doc tab is a menu item named 'Documentation' on the left side now.

https://golang.org/doc/modules/managing-dependencies
	

10. Broken link: ""See package discovery.""

11. Typo: ""One you've discovered"" s/One/Once/

https://golang.org/doc/modules/version-numbers

12. Typo: ""For more, see Managingdependencies."" (missing space)

https://golang.org/doc/modules/publishing

13. Typo: ""6. [...] with 1nformation about [...]""

    s/1nformation/information/

14. Broken links: ""go get command"" (twice)

	here: ""[ ... ] and run the go get command [...]"",
	and here: ""They can run the go get command [...]

https://golang.org/doc/modules/major-version

15. Invalid syntax:

	""Old import statement: `import example.com/mymodule/package1`
     New import statement: `import example.com/mymodule/v2/package1`""

	Package paths must be in quotes.

General

16. The anchors on most pages under doc/modules have temporary names: #tmp_0, #tmp_1, etc.

",1.0,"x/website: various mistakes in documentation on modules - I read the new documentation on modules (which is great, btw) and took notes of mistakes I encountered.

https://golang.org/doc/modules/gomod-ref

1. Contradiction: The description for 'replacement-path' says:

	""[...] If this is a module path, you must specify a \_replacement-version\_ value. [...]""
	But the following example shows the replacement of a module path without a replacement version value:
	""`replace example.com/othermodule => example.com/myfork/othermodule`""

2. Section 'exclude', description of 'module-version"":

	""If this version number is omitted, all versions of the module are replaced with the content on the right side of the arrow.""

	But an 'exclude' directive doesn't have an arrow. This sentence seems to be copy&pasted from the 'replace' directive and wrong.

3. Contradiction:

	""These directives are ignored in modules that depend on the current module.""
	vs. later
	""These directives are ignored in modules that are dependencies of the current module.""
	Which one is it?

4. Formatting: In the first example one line is not correctly indented.

5. Formatting: ""\_replacement-version\_"", ""\_replacement-path\_"". The underscores are probably not intended, but unsupported Markdown syntax.

https://golang.org/doc/tutorial/create-module

6. ""This tutorial's sequence includes six brief topics [...]""

	Followed by a numbered list of seven topics. s/six/seven/

https://golang.org/doc/tutorial/call-module-code

7. Broken link: ""Here, the replace directive [...]""

8. Broken tutorial: ""In the hello directory, run go build to make Go locate the module and add it as a dependency to the go.mod file.""

	Starting with Go 1.16 'go build' doesn't add dependencies anymore, which breaks this tutorial (similar to #43672).

https://golang.org/doc/tutorial/getting-started

9. Outdated description: ""3. On the Doc tab, under Index, [...]""

	The former Doc tab is a menu item named 'Documentation' on the left side now.

https://golang.org/doc/modules/managing-dependencies
	

10. Broken link: ""See package discovery.""

11. Typo: ""One you've discovered"" s/One/Once/

https://golang.org/doc/modules/version-numbers

12. Typo: ""For more, see Managingdependencies."" (missing space)

https://golang.org/doc/modules/publishing

13. Typo: ""6. [...] with 1nformation about [...]""

    s/1nformation/information/

14. Broken links: ""go get command"" (twice)

	here: ""[ ... ] and run the go get command [...]"",
	and here: ""They can run the go get command [...]

https://golang.org/doc/modules/major-version

15. Invalid syntax:

	""Old import statement: `import example.com/mymodule/package1`
     New import statement: `import example.com/mymodule/v2/package1`""

	Package paths must be in quotes.

General

16. The anchors on most pages under doc/modules have temporary names: #tmp_0, #tmp_1, etc.

",1,x website  various mistakes in documentation on modules   i read the new documentation on modules  which is great  btw  and took notes of mistakes i encountered             contradiction  the description for  replacement path  says     	   if this is a module path  you must specify a   replacement version   value      	but the following example shows the replacement of a module path without a replacement version value   	  replace example com othermodule    example com myfork othermodule         section  exclude   description of  module version      	 if this version number is omitted  all versions of the module are replaced with the content on the right side of the arrow      	but an  exclude  directive doesn t have an arrow  this sentence seems to be copy pasted from the  replace  directive and wrong        contradiction     	 these directives are ignored in modules that depend on the current module    	vs  later  	 these directives are ignored in modules that are dependencies of the current module    	which one is it        formatting  in the first example one line is not correctly indented        formatting     replacement version        replacement path     the underscores are probably not intended  but unsupported markdown syntax              this tutorial s sequence includes six brief topics       	followed by a numbered list of seven topics  s six seven             broken link   here  the replace directive          broken tutorial   in the hello directory  run go build to make go locate the module and add it as a dependency to the go mod file      	starting with go      go build  doesn t add dependencies anymore  which breaks this tutorial  similar to                 outdated description      on the doc tab  under index        	the former doc tab is a menu item named  documentation  on the left side now        	       broken link   see package discovery         typo   one you ve discovered  s one once             typo   for more  see managingdependencies    missing space             typo        with   about           s   information        broken links   go get command   twice     	here     and run the go get command      	and here   they can run the go get command              invalid syntax     	 old import statement   import example com mymodule          new import statement   import example com mymodule          	package paths must be in quotes     general       the anchors on most pages under doc modules have temporary names   tmp     tmp    etc     ,1
39522,16020985641.0,IssuesEvent,2021-04-20 23:16:07,seattle-uat/civiform,https://api.github.com/repos/seattle-uat/civiform,closed,Admin can create and edit repeater and repeated blocks.,Program service dev repeated entities,"**Is your feature request related to a problem? Please describe.**
Enable admin creation of a Repeater Block, and subsequently Repeated Blocks. 

Question bank needs to follow rules for adding repeater and repeated questions to blocks.

Rules:
1. A repeater question can only be added if it is the only question. 
2. No other questions can be added after a repeater question is added to a block.
3. Repeated questions for a repeated entity are only available when editing a repeated block that is created from a repeater block with a repeater question for that entity.

**Describe the solution you'd like**
A clear and concise description of what you want to happen.

**Additional context**
Add any other context or screenshots about the feature request here.

**Done when**
Repeated and Repeater blocks can be created by the admin.",1.0,"Admin can create and edit repeater and repeated blocks. - **Is your feature request related to a problem? Please describe.**
Enable admin creation of a Repeater Block, and subsequently Repeated Blocks. 

Question bank needs to follow rules for adding repeater and repeated questions to blocks.

Rules:
1. A repeater question can only be added if it is the only question. 
2. No other questions can be added after a repeater question is added to a block.
3. Repeated questions for a repeated entity are only available when editing a repeated block that is created from a repeater block with a repeater question for that entity.

**Describe the solution you'd like**
A clear and concise description of what you want to happen.

**Additional context**
Add any other context or screenshots about the feature request here.

**Done when**
Repeated and Repeater blocks can be created by the admin.",0,admin can create and edit repeater and repeated blocks      is your feature request related to a problem  please describe     enable admin creation of a repeater block  and subsequently repeated blocks      question bank needs to follow rules for adding repeater and repeated questions to blocks     rules      a repeater question can only be added if it is the only question       no other questions can be added after a repeater question is added to a block      repeated questions for a repeated entity are only available when editing a repeated block that is created from a repeater block with a repeater question for that entity       describe the solution you d like    a clear and concise description of what you want to happen       additional context    add any other context or screenshots about the feature request here       done when    repeated and repeater blocks can be created by the admin ,0
232842,17796845621.0,IssuesEvent,2021-08-31 23:55:58,golang/go,https://api.github.com/repos/golang/go,opened,spec: clarify sequencing of function calls within expressions,Documentation NeedsDecision,"The program below tests the order-of-evaluation semantics of `return *p, f(p)`. With gccgo, it prints 0 (i.e., evaluating `*p` before calling `f(p)`), and with cmd/compile it prints 2 (i.e., evaluating `*p` after `f(p)` returns).

But is it allowed to print `1`? I.e., can `*p` be evaluated *in the middle* of `f(p)` being evaluated, after the `*p = 1` and before the `*p = 2`?

The spec says simply:

> For example, in the (function-local) assignment
>
> ```
> y[f()], ok = g(h(), i()+x[j()], <-c), k()
> ```
>
> the function calls and communication happen in the order `f()`, `h()`, `i()`, `j()`, `<-c`, `g()`, and `k()`. However, the order of those events compared to the evaluation and indexing of `x` and the evaluation of `y` is not specified.

I don't think there's any other text in the spec that requires evaluation of a function call to within an expression to be handled atomically with respect to other expressions either.

@griesemer and I agree only 0 or 2 should be allowed (i.e., 1 should not be allowed), but that the spec could be clearer about this.

```
package main

func main() {
	x, _ := g()
	println(x)
}

func g() (int, int) {
	p := new(int)
	return *p, f(p)
}

func f(p *int) int {
	*p = 1
	*p = 2
	return 0
}
```

",1.0,"spec: clarify sequencing of function calls within expressions - The program below tests the order-of-evaluation semantics of `return *p, f(p)`. With gccgo, it prints 0 (i.e., evaluating `*p` before calling `f(p)`), and with cmd/compile it prints 2 (i.e., evaluating `*p` after `f(p)` returns).

But is it allowed to print `1`? I.e., can `*p` be evaluated *in the middle* of `f(p)` being evaluated, after the `*p = 1` and before the `*p = 2`?

The spec says simply:

> For example, in the (function-local) assignment
>
> ```
> y[f()], ok = g(h(), i()+x[j()], <-c), k()
> ```
>
> the function calls and communication happen in the order `f()`, `h()`, `i()`, `j()`, `<-c`, `g()`, and `k()`. However, the order of those events compared to the evaluation and indexing of `x` and the evaluation of `y` is not specified.

I don't think there's any other text in the spec that requires evaluation of a function call to within an expression to be handled atomically with respect to other expressions either.

@griesemer and I agree only 0 or 2 should be allowed (i.e., 1 should not be allowed), but that the spec could be clearer about this.

```
package main

func main() {
	x, _ := g()
	println(x)
}

func g() (int, int) {
	p := new(int)
	return *p, f(p)
}

func f(p *int) int {
	*p = 1
	*p = 2
	return 0
}
```

",1,spec  clarify sequencing of function calls within expressions   the program below tests the order of evaluation semantics of  return  p  f p    with gccgo  it prints    i e   evaluating   p  before calling  f p     and with cmd compile it prints    i e   evaluating   p  after  f p   returns      but is it allowed to print      i e   can   p  be evaluated  in the middle  of  f p   being evaluated  after the   p      and before the   p          the spec says simply       for example  in the  function local  assignment              y   ok   g h    i   x     c   k                the function calls and communication happen in the order  f      h      i      j        c    g     and  k     however  the order of those events compared to the evaluation and indexing of  x  and the evaluation of  y  is not specified     i don t think there s any other text in the spec that requires evaluation of a function call to within an expression to be handled atomically with respect to other expressions either      griesemer and i agree only   or   should be allowed  i e     should not be allowed   but that the spec could be clearer about this          package main    func main      	x       g    	println x        func g    int  int     	p    new int   	return  p  f p        func f p  int  int    	 p      	 p      	return              ,1
63202,7702414497.0,IssuesEvent,2018-05-21 02:13:00,quicwg/base-drafts,https://api.github.com/repos/quicwg/base-drafts,opened,Swap largest reference and base indices,-qpack design,"The value of the base index can be set at the start of an encoding pass.  Swapping the two values means only one change for the encoder when it comes back to update the header.

It also means less likelihood of a change in size.  If largest reference moves near (for example) 127, then its encoded size needs to change.  But it would be rare to find that the largest reference would differ from the base by more than 127 octets, even something an implementation could prevent.

The corner case here is where there are NO dynamic table references at all.  I found this to happen in tests occasionally.  This alternative design is no better in that regard because both values need to be set to 0 in that case.  Using a negative zero offset as a special case is a great idea, but the value exists.",1.0,"Swap largest reference and base indices - The value of the base index can be set at the start of an encoding pass.  Swapping the two values means only one change for the encoder when it comes back to update the header.

It also means less likelihood of a change in size.  If largest reference moves near (for example) 127, then its encoded size needs to change.  But it would be rare to find that the largest reference would differ from the base by more than 127 octets, even something an implementation could prevent.

The corner case here is where there are NO dynamic table references at all.  I found this to happen in tests occasionally.  This alternative design is no better in that regard because both values need to be set to 0 in that case.  Using a negative zero offset as a special case is a great idea, but the value exists.",0,swap largest reference and base indices   the value of the base index can be set at the start of an encoding pass   swapping the two values means only one change for the encoder when it comes back to update the header     it also means less likelihood of a change in size   if largest reference moves near  for example     then its encoded size needs to change   but it would be rare to find that the largest reference would differ from the base by more than   octets  even something an implementation could prevent     the corner case here is where there are no dynamic table references at all   i found this to happen in tests occasionally   this alternative design is no better in that regard because both values need to be set to   in that case   using a negative zero offset as a special case is a great idea  but the value exists ,0
79219,10114077046.0,IssuesEvent,2019-07-30 18:18:08,golang/go,https://api.github.com/repos/golang/go,closed,wiki: PerfDashboard links broken,Documentation NeedsFix,"### Wiki link

https://github.com/golang/go/wiki/PerfDashboard

### Which broken links

* [in detail](https://build.golang.org/perfdetail?commit=fb3d6c1631c3f3141f33a01afb4c0a23ef0ea2cf&commit0=82f48826c6c79a3d5697d5e06cac8451f3dc3c7f&kind=builder&builder=linux-amd64-perf&benchmark=http)
* [perf detail](https://build.golang.org/perfdetail?commit=fb3d6c1631c3f3141f33a01afb4c0a23ef0ea2cf&commit0=82f48826c6c79a3d5697d5e06cac8451f3dc3c7f&kind=builder&builder=linux-amd64-perf&benchmark=http)

### Using the perf dashboard

When I click to the perf dashboard on https://build.golang.org/perf?page=6, I see many empty HTML rows and links that go to the code review.  I am unable to find performance differences.  It appears the perf dashboard may not be working as intended.",1.0,"wiki: PerfDashboard links broken - ### Wiki link

https://github.com/golang/go/wiki/PerfDashboard

### Which broken links

* [in detail](https://build.golang.org/perfdetail?commit=fb3d6c1631c3f3141f33a01afb4c0a23ef0ea2cf&commit0=82f48826c6c79a3d5697d5e06cac8451f3dc3c7f&kind=builder&builder=linux-amd64-perf&benchmark=http)
* [perf detail](https://build.golang.org/perfdetail?commit=fb3d6c1631c3f3141f33a01afb4c0a23ef0ea2cf&commit0=82f48826c6c79a3d5697d5e06cac8451f3dc3c7f&kind=builder&builder=linux-amd64-perf&benchmark=http)

### Using the perf dashboard

When I click to the perf dashboard on https://build.golang.org/perf?page=6, I see many empty HTML rows and links that go to the code review.  I am unable to find performance differences.  It appears the perf dashboard may not be working as intended.",1,wiki  perfdashboard links broken       wiki link             which broken links                        using the perf dashboard    when i click to the perf dashboard on   i see many empty html rows and links that go to the code review   i am unable to find performance differences   it appears the perf dashboard may not be working as intended ,1
279320,30702505242.0,IssuesEvent,2023-07-27 01:35:55,nidhi7598/linux-3.0.35_CVE-2018-13405,https://api.github.com/repos/nidhi7598/linux-3.0.35_CVE-2018-13405,closed,CVE-2016-9178 (Medium) detected in linux-stable-rtv3.8.6 - autoclosed,Mend: dependency security vulnerability,"## CVE-2016-9178 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv3.8.6</b></p></summary>
<p>

<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/nidhi7598/linux-3.0.35_CVE-2018-13405/commit/662fbf6e1ed61fd353add2f52e2dd27e990364c7"">662fbf6e1ed61fd353add2f52e2dd27e990364c7</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>

</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The __get_user_asm_ex macro in arch/x86/include/asm/uaccess.h in the Linux kernel before 4.7.5 does not initialize a certain integer variable, which allows local users to obtain sensitive information from kernel stack memory by triggering failure of a get_user_ex call.

<p>Publish Date: 2016-11-28
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-9178>CVE-2016-9178</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: High
  - Integrity Impact: None
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2016-9178"">https://nvd.nist.gov/vuln/detail/CVE-2016-9178</a></p>
<p>Release Date: 2016-11-28</p>
<p>Fix Resolution: 4.7.5</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2016-9178 (Medium) detected in linux-stable-rtv3.8.6 - autoclosed - ## CVE-2016-9178 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv3.8.6</b></p></summary>
<p>

<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/nidhi7598/linux-3.0.35_CVE-2018-13405/commit/662fbf6e1ed61fd353add2f52e2dd27e990364c7"">662fbf6e1ed61fd353add2f52e2dd27e990364c7</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>

</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The __get_user_asm_ex macro in arch/x86/include/asm/uaccess.h in the Linux kernel before 4.7.5 does not initialize a certain integer variable, which allows local users to obtain sensitive information from kernel stack memory by triggering failure of a get_user_ex call.

<p>Publish Date: 2016-11-28
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-9178>CVE-2016-9178</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: High
  - Integrity Impact: None
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2016-9178"">https://nvd.nist.gov/vuln/detail/CVE-2016-9178</a></p>
<p>Release Date: 2016-11-28</p>
<p>Fix Resolution: 4.7.5</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      medium  detected in linux stable         autoclosed      cve       medium severity vulnerability     vulnerable library    linux stable              julia cartwright s fork of linux stable rt git   library home page   a href    found in head commit   a href      found in base branch   master             vulnerable source files                              vulnerability details         the   get user asm ex macro in arch   include asm uaccess h in the linux kernel before       does not initialize a certain integer variable  which allows local users to obtain sensitive information from kernel stack memory by triggering failure of a get user ex call    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  local     attack complexity  low     privileges required  low     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  none     availability impact  none   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                      step up your open source security game with mend    ,0
53853,13262390222.0,IssuesEvent,2020-08-20 21:41:53,icecube-trac/tix4,https://api.github.com/repos/icecube-trac/tix4,closed,filterscripts: TypeError: 'I3Geometry' object has no attribute '__getitem__' (Trac #2197),Migrated from Trac defect infrastructure,"Hi,

I saw this error while experimenting with the trunk of filterscripts:


```text
Traceback (most recent call last):
  File ""./IceCube_BaseProc_only_MM_trunk.py"", line 309, in <module>
    tray.Execute()
  File ""/data/user/flauber/software/py2-v3.0.1/icerec_trunk/build/lib/I3Tray.py"", line 256, in Execute
    super(I3Tray, self).Execute()
  File ""/data/user/flauber/software/py2-v3.0.1/icerec_trunk/build/lib/icecube/icetray/i3logging.py"", line 28, in log
    record = logging.LogRecord(logger.name, self.pylevels[level], file, line, msg, tuple(), None, None)
  File ""/cvmfs/icecube.opensciencegrid.org/py2-v3.0.1/RHEL_7_x86_64/lib/python2.7/logging/__init__.py"", line 285, in __init__
    self.threadName = threading.current_thread().name
  File ""/cvmfs/icecube.opensciencegrid.org/py2-v3.0.1/RHEL_7_x86_64/lib/python2.7/threading.py"", line 1151, in currentThread
    return _active[_get_ident()]
  File ""/data/user/flauber/software/py2-v3.0.1/icerec_trunk/build/lib/icecube/icetray/i3logging.py"", line 28, in log
    record = logging.LogRecord(logger.name, self.pylevels[level], file, line, msg, tuple(), None, None)
  File ""/cvmfs/icecube.opensciencegrid.org/py2-v3.0.1/RHEL_7_x86_64/lib/python2.7/logging/__init__.py"", line 285, in __init__
    self.threadName = threading.current_thread().name
  File ""/cvmfs/icecube.opensciencegrid.org/py2-v3.0.1/RHEL_7_x86_64/lib/python2.7/threading.py"", line 1151, in currentThread
    return _active[_get_ident()]
  File ""/data/user/flauber/software/py2-v3.0.1/icerec_trunk/build/lib/icecube/filterscripts/baseproc_superdst.py"", line 26, in MaskMaker
    g = omgeo[omkey]
TypeError: 'I3Geometry' object has no attribute '__getitem__'
```

I think the problem is line 26 in 
http://code.icecube.wisc.edu/svn/projects/filterscripts/trunk/python/baseproc_superdst.py

and should be fixed by replacing
``` 
g = omgeo[omkey]
```
with 

```text
g = omgeo.omgeo[omkey]
```
(thanks to alex olivias and jvs for pointing this out to me)
Cheers,
Frederik




<details>
 <summary><em>Migrated from <a href=""https://code.icecube.wisc.edu/projects/icecube/ticket/2197"">https://code.icecube.wisc.edu/projects/icecube/ticket/2197</a>, reported by flauberand owned by olivas</em></summary>
<p>

```json
{
    ""status"": ""closed"",
    ""changetime"": ""2019-01-12T03:53:01"",
    ""_ts"": ""1547265181974434"",
    ""description"": ""Hi,\n\nI saw this error while experimenting with the trunk of filterscripts:\n\n{{{\nTraceback (most recent call last):\n  File \""./IceCube_BaseProc_only_MM_trunk.py\"", line 309, in <module>\n    tray.Execute()\n  File \""/data/user/flauber/software/py2-v3.0.1/icerec_trunk/build/lib/I3Tray.py\"", line 256, in Execute\n    super(I3Tray, self).Execute()\n  File \""/data/user/flauber/software/py2-v3.0.1/icerec_trunk/build/lib/icecube/icetray/i3logging.py\"", line 28, in log\n    record = logging.LogRecord(logger.name, self.pylevels[level], file, line, msg, tuple(), None, None)\n  File \""/cvmfs/icecube.opensciencegrid.org/py2-v3.0.1/RHEL_7_x86_64/lib/python2.7/logging/__init__.py\"", line 285, in __init__\n    self.threadName = threading.current_thread().name\n  File \""/cvmfs/icecube.opensciencegrid.org/py2-v3.0.1/RHEL_7_x86_64/lib/python2.7/threading.py\"", line 1151, in currentThread\n    return _active[_get_ident()]\n  File \""/data/user/flauber/software/py2-v3.0.1/icerec_trunk/build/lib/icecube/icetray/i3logging.py\"", line 28, in log\n    record = logging.LogRecord(logger.name, self.pylevels[level], file, line, msg, tuple(), None, None)\n  File \""/cvmfs/icecube.opensciencegrid.org/py2-v3.0.1/RHEL_7_x86_64/lib/python2.7/logging/__init__.py\"", line 285, in __init__\n    self.threadName = threading.current_thread().name\n  File \""/cvmfs/icecube.opensciencegrid.org/py2-v3.0.1/RHEL_7_x86_64/lib/python2.7/threading.py\"", line 1151, in currentThread\n    return _active[_get_ident()]\n  File \""/data/user/flauber/software/py2-v3.0.1/icerec_trunk/build/lib/icecube/filterscripts/baseproc_superdst.py\"", line 26, in MaskMaker\n    g = omgeo[omkey]\nTypeError: 'I3Geometry' object has no attribute '__getitem__'\n}}}\n\nI think the problem is line 26 in \nhttp://code.icecube.wisc.edu/svn/projects/filterscripts/trunk/python/baseproc_superdst.py\n\nand should be fixed by replacing\n{{{ \ng = omgeo[omkey]\n}}}\nwith \n{{{\ng = omgeo.omgeo[omkey]\n}}}\n(thanks to alex olivias and jvs for pointing this out to me)\nCheers,\nFrederik\n\n\n"",
    ""reporter"": ""flauber"",
    ""cc"": """",
    ""resolution"": ""fixed"",
    ""time"": ""2018-10-09T14:06:46"",
    ""component"": ""infrastructure"",
    ""summary"": ""filterscripts: TypeError: 'I3Geometry' object has no attribute '__getitem__'"",
    ""priority"": ""normal"",
    ""keywords"": ""filterscripts"",
    ""milestone"": """",
    ""owner"": ""olivas"",
    ""type"": ""defect""
}
```

</p>
</details>
",1.0,"filterscripts: TypeError: 'I3Geometry' object has no attribute '__getitem__' (Trac #2197) - Hi,

I saw this error while experimenting with the trunk of filterscripts:


```text
Traceback (most recent call last):
  File ""./IceCube_BaseProc_only_MM_trunk.py"", line 309, in <module>
    tray.Execute()
  File ""/data/user/flauber/software/py2-v3.0.1/icerec_trunk/build/lib/I3Tray.py"", line 256, in Execute
    super(I3Tray, self).Execute()
  File ""/data/user/flauber/software/py2-v3.0.1/icerec_trunk/build/lib/icecube/icetray/i3logging.py"", line 28, in log
    record = logging.LogRecord(logger.name, self.pylevels[level], file, line, msg, tuple(), None, None)
  File ""/cvmfs/icecube.opensciencegrid.org/py2-v3.0.1/RHEL_7_x86_64/lib/python2.7/logging/__init__.py"", line 285, in __init__
    self.threadName = threading.current_thread().name
  File ""/cvmfs/icecube.opensciencegrid.org/py2-v3.0.1/RHEL_7_x86_64/lib/python2.7/threading.py"", line 1151, in currentThread
    return _active[_get_ident()]
  File ""/data/user/flauber/software/py2-v3.0.1/icerec_trunk/build/lib/icecube/icetray/i3logging.py"", line 28, in log
    record = logging.LogRecord(logger.name, self.pylevels[level], file, line, msg, tuple(), None, None)
  File ""/cvmfs/icecube.opensciencegrid.org/py2-v3.0.1/RHEL_7_x86_64/lib/python2.7/logging/__init__.py"", line 285, in __init__
    self.threadName = threading.current_thread().name
  File ""/cvmfs/icecube.opensciencegrid.org/py2-v3.0.1/RHEL_7_x86_64/lib/python2.7/threading.py"", line 1151, in currentThread
    return _active[_get_ident()]
  File ""/data/user/flauber/software/py2-v3.0.1/icerec_trunk/build/lib/icecube/filterscripts/baseproc_superdst.py"", line 26, in MaskMaker
    g = omgeo[omkey]
TypeError: 'I3Geometry' object has no attribute '__getitem__'
```

I think the problem is line 26 in 
http://code.icecube.wisc.edu/svn/projects/filterscripts/trunk/python/baseproc_superdst.py

and should be fixed by replacing
``` 
g = omgeo[omkey]
```
with 

```text
g = omgeo.omgeo[omkey]
```
(thanks to alex olivias and jvs for pointing this out to me)
Cheers,
Frederik




<details>
 <summary><em>Migrated from <a href=""https://code.icecube.wisc.edu/projects/icecube/ticket/2197"">https://code.icecube.wisc.edu/projects/icecube/ticket/2197</a>, reported by flauberand owned by olivas</em></summary>
<p>

```json
{
    ""status"": ""closed"",
    ""changetime"": ""2019-01-12T03:53:01"",
    ""_ts"": ""1547265181974434"",
    ""description"": ""Hi,\n\nI saw this error while experimenting with the trunk of filterscripts:\n\n{{{\nTraceback (most recent call last):\n  File \""./IceCube_BaseProc_only_MM_trunk.py\"", line 309, in <module>\n    tray.Execute()\n  File \""/data/user/flauber/software/py2-v3.0.1/icerec_trunk/build/lib/I3Tray.py\"", line 256, in Execute\n    super(I3Tray, self).Execute()\n  File \""/data/user/flauber/software/py2-v3.0.1/icerec_trunk/build/lib/icecube/icetray/i3logging.py\"", line 28, in log\n    record = logging.LogRecord(logger.name, self.pylevels[level], file, line, msg, tuple(), None, None)\n  File \""/cvmfs/icecube.opensciencegrid.org/py2-v3.0.1/RHEL_7_x86_64/lib/python2.7/logging/__init__.py\"", line 285, in __init__\n    self.threadName = threading.current_thread().name\n  File \""/cvmfs/icecube.opensciencegrid.org/py2-v3.0.1/RHEL_7_x86_64/lib/python2.7/threading.py\"", line 1151, in currentThread\n    return _active[_get_ident()]\n  File \""/data/user/flauber/software/py2-v3.0.1/icerec_trunk/build/lib/icecube/icetray/i3logging.py\"", line 28, in log\n    record = logging.LogRecord(logger.name, self.pylevels[level], file, line, msg, tuple(), None, None)\n  File \""/cvmfs/icecube.opensciencegrid.org/py2-v3.0.1/RHEL_7_x86_64/lib/python2.7/logging/__init__.py\"", line 285, in __init__\n    self.threadName = threading.current_thread().name\n  File \""/cvmfs/icecube.opensciencegrid.org/py2-v3.0.1/RHEL_7_x86_64/lib/python2.7/threading.py\"", line 1151, in currentThread\n    return _active[_get_ident()]\n  File \""/data/user/flauber/software/py2-v3.0.1/icerec_trunk/build/lib/icecube/filterscripts/baseproc_superdst.py\"", line 26, in MaskMaker\n    g = omgeo[omkey]\nTypeError: 'I3Geometry' object has no attribute '__getitem__'\n}}}\n\nI think the problem is line 26 in \nhttp://code.icecube.wisc.edu/svn/projects/filterscripts/trunk/python/baseproc_superdst.py\n\nand should be fixed by replacing\n{{{ \ng = omgeo[omkey]\n}}}\nwith \n{{{\ng = omgeo.omgeo[omkey]\n}}}\n(thanks to alex olivias and jvs for pointing this out to me)\nCheers,\nFrederik\n\n\n"",
    ""reporter"": ""flauber"",
    ""cc"": """",
    ""resolution"": ""fixed"",
    ""time"": ""2018-10-09T14:06:46"",
    ""component"": ""infrastructure"",
    ""summary"": ""filterscripts: TypeError: 'I3Geometry' object has no attribute '__getitem__'"",
    ""priority"": ""normal"",
    ""keywords"": ""filterscripts"",
    ""milestone"": """",
    ""owner"": ""olivas"",
    ""type"": ""defect""
}
```

</p>
</details>
",0,filterscripts  typeerror      object has no attribute    getitem     trac       hi   i saw this error while experimenting with the trunk of filterscripts       text traceback  most recent call last     file    icecube baseproc only mm trunk py   line    in       tray execute     file   data user flauber software         icerec trunk build lib   py   line    in execute     super    self  execute     file   data user flauber software         icerec trunk build lib icecube icetray   py   line    in log     record   logging logrecord logger name  self pylevels   file  line  msg  tuple    none  none    file   cvmfs icecube opensciencegrid org         rhel       lib     logging   init   py   line    in   init       self threadname   threading current thread   name   file   cvmfs icecube opensciencegrid org         rhel       lib     threading py   line    in currentthread     return  active    file   data user flauber software         icerec trunk build lib icecube icetray   py   line    in log     record   logging logrecord logger name  self pylevels   file  line  msg  tuple    none  none    file   cvmfs icecube opensciencegrid org         rhel       lib     logging   init   py   line    in   init       self threadname   threading current thread   name   file   cvmfs icecube opensciencegrid org         rhel       lib     threading py   line    in currentthread     return  active    file   data user flauber software         icerec trunk build lib icecube filterscripts baseproc superdst py   line    in maskmaker     g   omgeo  typeerror      object has no attribute    getitem         i think the problem is line   in     and should be fixed by replacing      g   omgeo      with      text g   omgeo omgeo       thanks to alex olivias and jvs for pointing this out to me  cheers  frederik          migrated from          json        status    closed        changetime                      ts             description    hi  n ni saw this error while experimenting with the trunk of filterscripts  n n    ntraceback  most recent call last   n  file     icecube baseproc only mm trunk py    line    in   n    tray execute   n  file    data user flauber software         icerec trunk build lib   py    line    in execute n    super    self  execute   n  file    data user flauber software         icerec trunk build lib icecube icetray   py    line    in log n    record   logging logrecord logger name  self pylevels   file  line  msg  tuple    none  none  n  file    cvmfs icecube opensciencegrid org         rhel       lib     logging   init   py    line    in   init   n    self threadname   threading current thread   name n  file    cvmfs icecube opensciencegrid org         rhel       lib     threading py    line    in currentthread n    return  active  n  file    data user flauber software         icerec trunk build lib icecube icetray   py    line    in log n    record   logging logrecord logger name  self pylevels   file  line  msg  tuple    none  none  n  file    cvmfs icecube opensciencegrid org         rhel       lib     logging   init   py    line    in   init   n    self threadname   threading current thread   name n  file    cvmfs icecube opensciencegrid org         rhel       lib     threading py    line    in currentthread n    return  active  n  file    data user flauber software         icerec trunk build lib icecube filterscripts baseproc superdst py    line    in maskmaker n    g   omgeo  ntypeerror      object has no attribute    getitem    n    n ni think the problem is line   in  n  should be fixed by replacing n     ng   omgeo  n    nwith  n    ng   omgeo omgeo  n    n thanks to alex olivias and jvs for pointing this out to me  ncheers  nfrederik n n n        reporter    flauber        cc            resolution    fixed        time                     component    infrastructure        summary    filterscripts  typeerror      object has no attribute    getitem           priority    normal        keywords    filterscripts        milestone            owner    olivas        type    defect             ,0
161899,20164110639.0,IssuesEvent,2022-02-10 01:22:58,Jellyfrog/librenms,https://api.github.com/repos/Jellyfrog/librenms,closed,CVE-2021-3807 (High) detected in ansi-regex-5.0.0.tgz - autoclosed,security vulnerability,"## CVE-2021-3807 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ansi-regex-5.0.0.tgz</b></p></summary>

<p>Regular expression for matching ANSI escape codes</p>
<p>Library home page: <a href=""https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.0.tgz"">https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/ansi-regex/package.json</p>
<p>

Dependency Hierarchy:
  - laravel-mix-6.0.19.tgz (Root Library)
    - strip-ansi-6.0.0.tgz
      - :x: **ansi-regex-5.0.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
ansi-regex is vulnerable to Inefficient Regular Expression Complexity

<p>Publish Date: 2021-09-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3807>CVE-2021-3807</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://huntr.dev/bounties/5b3cf33b-ede0-4398-9974-800876dfd994/"">https://huntr.dev/bounties/5b3cf33b-ede0-4398-9974-800876dfd994/</a></p>
<p>Release Date: 2021-09-17</p>
<p>Fix Resolution: ansi-regex - 5.0.1,6.0.1</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2021-3807 (High) detected in ansi-regex-5.0.0.tgz - autoclosed - ## CVE-2021-3807 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ansi-regex-5.0.0.tgz</b></p></summary>

<p>Regular expression for matching ANSI escape codes</p>
<p>Library home page: <a href=""https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.0.tgz"">https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/ansi-regex/package.json</p>
<p>

Dependency Hierarchy:
  - laravel-mix-6.0.19.tgz (Root Library)
    - strip-ansi-6.0.0.tgz
      - :x: **ansi-regex-5.0.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
ansi-regex is vulnerable to Inefficient Regular Expression Complexity

<p>Publish Date: 2021-09-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3807>CVE-2021-3807</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://huntr.dev/bounties/5b3cf33b-ede0-4398-9974-800876dfd994/"">https://huntr.dev/bounties/5b3cf33b-ede0-4398-9974-800876dfd994/</a></p>
<p>Release Date: 2021-09-17</p>
<p>Fix Resolution: ansi-regex - 5.0.1,6.0.1</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in ansi regex       tgz   autoclosed      cve       high severity vulnerability     vulnerable library    ansi regex       tgz      regular expression for matching ansi escape codes   library home page   a href     path to dependency file   package json   path to vulnerable library   node modules ansi regex package json     dependency hierarchy      laravel mix       tgz  root library        strip ansi       tgz          x    ansi regex       tgz    vulnerable library   found in base branch   master              vulnerability details         ansi regex is vulnerable to inefficient regular expression complexity   publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  ansi regex                             step up your open source security game with whitesource    ,0
30258,5774072367.0,IssuesEvent,2017-04-28 05:29:07,golang/go,https://api.github.com/repos/golang/go,closed, syscall: fix documentation typo,Documentation HelpWanted NeedsFix,"At [https://gowalker.org/syscall#StringToUTF16Ptr](https://gowalker.org/syscall#StringToUTF16Ptr):
_(...) with a terminating **NUL** #added. **If s If s** contains (...)_
* _If s_ is duplicated.
* Along all the page ([https://gowalker.org/syscall](https://gowalker.org/syscall)) you can find repeatedly _NUL_ instead of _NULL_.",1.0," syscall: fix documentation typo - At [https://gowalker.org/syscall#StringToUTF16Ptr](https://gowalker.org/syscall#StringToUTF16Ptr):
_(...) with a terminating **NUL** #added. **If s If s** contains (...)_
* _If s_ is duplicated.
* Along all the page ([https://gowalker.org/syscall](https://gowalker.org/syscall)) you can find repeatedly _NUL_ instead of _NULL_.",1, syscall  fix documentation typo   at             with a terminating   nul    added    if s if s   contains            if s  is duplicated     along all the page      you can find repeatedly  nul  instead of  null  ,1
232748,17793469290.0,IssuesEvent,2021-08-31 19:03:27,golang/go,https://api.github.com/repos/golang/go,closed,dl: switch to go install path@latest syntax in documentation,Documentation NeedsFix modules,"Now that Go 1.17 is released and Go 1.15 in unsupported per [release policy](https://golang.org/doc/devel/release#policy), we should update documentation of [`golang.org/dl/go1.N` commands](https://pkg.go.dev/golang.org/dl#section-directories) to suggest the new `go install path@latest` installation syntax instead of `go get` per #43684.

It should be okay to update documentation for all `golang.org/dl/...` commands, even pre-1.15 ones, since they're still meant to serve supported Go versions, all of which by now understand the new syntax.

CC @golang/release, @bcmills, @jayconrod, @matloob.",1.0,"dl: switch to go install path@latest syntax in documentation - Now that Go 1.17 is released and Go 1.15 in unsupported per [release policy](https://golang.org/doc/devel/release#policy), we should update documentation of [`golang.org/dl/go1.N` commands](https://pkg.go.dev/golang.org/dl#section-directories) to suggest the new `go install path@latest` installation syntax instead of `go get` per #43684.

It should be okay to update documentation for all `golang.org/dl/...` commands, even pre-1.15 ones, since they're still meant to serve supported Go versions, all of which by now understand the new syntax.

CC @golang/release, @bcmills, @jayconrod, @matloob.",1,dl  switch to go install path latest syntax in documentation   now that go     is released and go     in unsupported per     we should update documentation of     to suggest the new  go install path latest  installation syntax instead of  go get  per        it should be okay to update documentation for all  golang org dl      commands  even pre     ones  since they re still meant to serve supported go versions  all of which by now understand the new syntax     cc  golang release   bcmills   jayconrod   matloob ,1
72930,9632630654.0,IssuesEvent,2019-05-15 16:38:19,golang/go,https://api.github.com/repos/golang/go,opened,cmd/go: replace directives are not thoroughly documented,Documentation GoCommand modules,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version devel +f0c383b833 Wed May 1 16:53:19 2019 +0000 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What did you do?

Read `go help modules` and `go help go.mod`.

### What did you expect to see?

Some discussion of what replacements are and what they do.

### What did you see instead?

The only documentation I can find is these lines in `go help go.mod`:
```
	replace bad/thing v1.4.5 => good/thing v1.4.5
```
```
	replace, to replace a module version with a different module version.
Exclude and replace apply only in the main module's go.mod and are ignored
in dependencies.  See https://research.swtch.com/vgo-mvs for details.
```

I think there's probably more to say about how replace works. For example, it doesn't explicitly state that the thing to replace is on the left side of the arrow. It also doesn't mention that the version on the left is optional.",1.0,"cmd/go: replace directives are not thoroughly documented - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version devel +f0c383b833 Wed May 1 16:53:19 2019 +0000 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What did you do?

Read `go help modules` and `go help go.mod`.

### What did you expect to see?

Some discussion of what replacements are and what they do.

### What did you see instead?

The only documentation I can find is these lines in `go help go.mod`:
```
	replace bad/thing v1.4.5 => good/thing v1.4.5
```
```
	replace, to replace a module version with a different module version.
Exclude and replace apply only in the main module's go.mod and are ignored
in dependencies.  See https://research.swtch.com/vgo-mvs for details.
```

I think there's probably more to say about how replace works. For example, it doesn't explicitly state that the thing to replace is on the left side of the arrow. It also doesn't mention that the version on the left is optional.",1,cmd go  replace directives are not thoroughly documented            what version of go are you using   go version            go version  go version devel    wed may              linux             does this issue reproduce with the latest release     yes        what did you do     read  go help modules  and  go help go mod          what did you expect to see     some discussion of what replacements are and what they do         what did you see instead     the only documentation i can find is these lines in  go help go mod         	replace bad thing          good thing                  	replace  to replace a module version with a different module version   exclude and replace apply only in the main module s go mod and are ignored  in dependencies   see   for details          i think there s probably more to say about how replace works  for example  it doesn t explicitly state that the thing to replace is on the left side of the arrow  it also doesn t mention that the version on the left is optional ,1
33349,6198137992.0,IssuesEvent,2017-07-05 18:27:49,golang/go,https://api.github.com/repos/golang/go,closed,runtime/pprof: Undefined type referred to in function comment,Documentation NeedsFix,"### What version of Go are you using (`go version`)?
1.9beta

### What did you do?
Read documentation of `runtime/pprof` for Profiler Labels (http://tip.golang.org/pkg/runtime/pprof/#Labels)

### What did you expect to see?
The function comment for http://tip.golang.org/pkg/runtime/pprof/#Labels
should describe the return value as  type LabelSet.

### What did you see instead?
The typename returned by http://tip.golang.org/pkg/runtime/pprof/#Labels
 is LabelSet, but the documentation string refers to it as LabelList. 

",1.0,"runtime/pprof: Undefined type referred to in function comment - ### What version of Go are you using (`go version`)?
1.9beta

### What did you do?
Read documentation of `runtime/pprof` for Profiler Labels (http://tip.golang.org/pkg/runtime/pprof/#Labels)

### What did you expect to see?
The function comment for http://tip.golang.org/pkg/runtime/pprof/#Labels
should describe the return value as  type LabelSet.

### What did you see instead?
The typename returned by http://tip.golang.org/pkg/runtime/pprof/#Labels
 is LabelSet, but the documentation string refers to it as LabelList. 

",1,runtime pprof  undefined type referred to in function comment       what version of go are you using   go version                what did you do   read documentation of  runtime pprof  for profiler labels           what did you expect to see   the function comment for    should describe the return value as  type labelset         what did you see instead   the typename returned by     is labelset  but the documentation string refers to it as labellist      ,1
221375,24621487666.0,IssuesEvent,2022-10-16 00:58:55,etcd-io/etcd,https://api.github.com/repos/etcd-io/etcd,closed,"Etcd has some security issues involving password complexity, sensitive information leakage, interfaces that do not require authentication, and accounts that cannot be locked",area/security stale,"1. Reuse of wrong password to access interface /v2/auth/users, account will not be locked out
2. Call etcd api to use weak password to perform user creation and update user password operations, there is no weak password checking mechanism
3. Open etcd debug log, call etcd api to perform user creation and update user password operations, the password ciphertext will be 
4. Etcd has interfaces that can be accessed without authentication, health and version interfaces


",True,"Etcd has some security issues involving password complexity, sensitive information leakage, interfaces that do not require authentication, and accounts that cannot be locked - 1. Reuse of wrong password to access interface /v2/auth/users, account will not be locked out
2. Call etcd api to use weak password to perform user creation and update user password operations, there is no weak password checking mechanism
3. Open etcd debug log, call etcd api to perform user creation and update user password operations, the password ciphertext will be 
4. Etcd has interfaces that can be accessed without authentication, health and version interfaces


",0,etcd has some security issues involving password complexity  sensitive information leakage  interfaces that do not require authentication  and accounts that cannot be locked      reuse of wrong password to access interface    auth users  account will not be locked out     call etcd api to use weak password to perform user creation and update user password operations  there is no weak password checking mechanism     open etcd debug log  call etcd api to perform user creation and update user password operations  the password ciphertext will be      etcd has interfaces that can be accessed without authentication  health and version interfaces      ,0
71659,15207827308.0,IssuesEvent,2021-02-17 01:06:40,billmcchesney1/foxtrot,https://api.github.com/repos/billmcchesney1/foxtrot,closed,CVE-2018-11768 (High) detected in hadoop-hdfs-2.5.1.jar - autoclosed,security vulnerability,"## CVE-2018-11768 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hadoop-hdfs-2.5.1.jar</b></p></summary>

<p>Apache Hadoop HDFS</p>
<p>Path to dependency file: foxtrot/foxtrot-sql/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/hadoop/hadoop-hdfs/2.5.1/hadoop-hdfs-2.5.1.jar,/home/wss-scanner/.m2/repository/org/apache/hadoop/hadoop-hdfs/2.5.1/hadoop-hdfs-2.5.1.jar,/home/wss-scanner/.m2/repository/org/apache/hadoop/hadoop-hdfs/2.5.1/hadoop-hdfs-2.5.1.jar,/home/wss-scanner/.m2/repository/org/apache/hadoop/hadoop-hdfs/2.5.1/hadoop-hdfs-2.5.1.jar</p>
<p>

Dependency Hierarchy:
  - hbase-server-1.2.1.jar (Root Library)
    - :x: **hadoop-hdfs-2.5.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/billmcchesney1/foxtrot/commit/ffb8a6014463ce8aac1bf6e7dc9a23fc4a2a8adc"">ffb8a6014463ce8aac1bf6e7dc9a23fc4a2a8adc</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 Hadoop 3.1.0 to 3.1.1, 3.0.0-alpha1 to 3.0.3, 2.9.0 to 2.9.1, and 2.0.0-alpha to 2.8.4, the user/group information can be corrupted across storing in fsimage and reading back from fsimage.

<p>Publish Date: 2019-10-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-11768>CVE-2018-11768</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: High
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://lists.apache.org/thread.html/ea6d2dfbefab8ebe46be18b05136b83ae53b7866f1bc60c680a2b600@%3Chdfs-dev.hadoop.apache.org%3E"">https://lists.apache.org/thread.html/ea6d2dfbefab8ebe46be18b05136b83ae53b7866f1bc60c680a2b600@%3Chdfs-dev.hadoop.apache.org%3E</a></p>
<p>Release Date: 2019-10-04</p>
<p>Fix Resolution: org.apache.hadoop:hadoop-hdfs:2.8.5,2.9.2,3.1.2</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""org.apache.hadoop"",""packageName"":""hadoop-hdfs"",""packageVersion"":""2.5.1"",""packageFilePaths"":[""/foxtrot-sql/pom.xml"",""/foxtrot-server/pom.xml"",""/foxtrot-core/pom.xml"",""/foxtrot-translator/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.apache.hbase:hbase-server:1.2.1;org.apache.hadoop:hadoop-hdfs:2.5.1"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""org.apache.hadoop:hadoop-hdfs:2.8.5,2.9.2,3.1.2""}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""CVE-2018-11768"",""vulnerabilityDetails"":""In Apache Hadoop 3.1.0 to 3.1.1, 3.0.0-alpha1 to 3.0.3, 2.9.0 to 2.9.1, and 2.0.0-alpha to 2.8.4, the user/group information can be corrupted across storing in fsimage and reading back from fsimage."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-11768"",""cvss3Severity"":""high"",""cvss3Score"":""7.5"",""cvss3Metrics"":{""A"":""None"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""None"",""AV"":""Network"",""I"":""High""},""extraData"":{}}</REMEDIATE> -->",True,"CVE-2018-11768 (High) detected in hadoop-hdfs-2.5.1.jar - autoclosed - ## CVE-2018-11768 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hadoop-hdfs-2.5.1.jar</b></p></summary>

<p>Apache Hadoop HDFS</p>
<p>Path to dependency file: foxtrot/foxtrot-sql/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/hadoop/hadoop-hdfs/2.5.1/hadoop-hdfs-2.5.1.jar,/home/wss-scanner/.m2/repository/org/apache/hadoop/hadoop-hdfs/2.5.1/hadoop-hdfs-2.5.1.jar,/home/wss-scanner/.m2/repository/org/apache/hadoop/hadoop-hdfs/2.5.1/hadoop-hdfs-2.5.1.jar,/home/wss-scanner/.m2/repository/org/apache/hadoop/hadoop-hdfs/2.5.1/hadoop-hdfs-2.5.1.jar</p>
<p>

Dependency Hierarchy:
  - hbase-server-1.2.1.jar (Root Library)
    - :x: **hadoop-hdfs-2.5.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/billmcchesney1/foxtrot/commit/ffb8a6014463ce8aac1bf6e7dc9a23fc4a2a8adc"">ffb8a6014463ce8aac1bf6e7dc9a23fc4a2a8adc</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 Hadoop 3.1.0 to 3.1.1, 3.0.0-alpha1 to 3.0.3, 2.9.0 to 2.9.1, and 2.0.0-alpha to 2.8.4, the user/group information can be corrupted across storing in fsimage and reading back from fsimage.

<p>Publish Date: 2019-10-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-11768>CVE-2018-11768</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: High
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://lists.apache.org/thread.html/ea6d2dfbefab8ebe46be18b05136b83ae53b7866f1bc60c680a2b600@%3Chdfs-dev.hadoop.apache.org%3E"">https://lists.apache.org/thread.html/ea6d2dfbefab8ebe46be18b05136b83ae53b7866f1bc60c680a2b600@%3Chdfs-dev.hadoop.apache.org%3E</a></p>
<p>Release Date: 2019-10-04</p>
<p>Fix Resolution: org.apache.hadoop:hadoop-hdfs:2.8.5,2.9.2,3.1.2</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""org.apache.hadoop"",""packageName"":""hadoop-hdfs"",""packageVersion"":""2.5.1"",""packageFilePaths"":[""/foxtrot-sql/pom.xml"",""/foxtrot-server/pom.xml"",""/foxtrot-core/pom.xml"",""/foxtrot-translator/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.apache.hbase:hbase-server:1.2.1;org.apache.hadoop:hadoop-hdfs:2.5.1"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""org.apache.hadoop:hadoop-hdfs:2.8.5,2.9.2,3.1.2""}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""CVE-2018-11768"",""vulnerabilityDetails"":""In Apache Hadoop 3.1.0 to 3.1.1, 3.0.0-alpha1 to 3.0.3, 2.9.0 to 2.9.1, and 2.0.0-alpha to 2.8.4, the user/group information can be corrupted across storing in fsimage and reading back from fsimage."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-11768"",""cvss3Severity"":""high"",""cvss3Score"":""7.5"",""cvss3Metrics"":{""A"":""None"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""None"",""AV"":""Network"",""I"":""High""},""extraData"":{}}</REMEDIATE> -->",0,cve      high  detected in hadoop hdfs       jar   autoclosed      cve       high severity vulnerability     vulnerable library    hadoop hdfs       jar      apache hadoop hdfs   path to dependency file  foxtrot foxtrot sql pom xml   path to vulnerable library   home wss scanner    repository org apache hadoop hadoop hdfs       hadoop hdfs       jar  home wss scanner    repository org apache hadoop hadoop hdfs       hadoop hdfs       jar  home wss scanner    repository org apache hadoop hadoop hdfs       hadoop hdfs       jar  home wss scanner    repository org apache hadoop hadoop hdfs       hadoop hdfs       jar     dependency hierarchy      hbase server       jar  root library         x    hadoop hdfs       jar    vulnerable library   found in head commit   a href     found in base branch   master              vulnerability details         in apache hadoop       to                to              to        and       alpha to        the user group information can be corrupted across storing in fsimage and reading back from fsimage    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  high     availability impact  none   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  org apache hadoop hadoop hdfs                                isopenpronvulnerability  true  ispackagebased  true  isdefaultbranch  true  packages     istransitivedependency  true  dependencytree   org apache hbase hbase server       org apache hadoop hadoop hdfs         isminimumfixversionavailable  true  minimumfixversion   org apache hadoop hadoop hdfs                       basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   in apache hadoop       to                to              to        and       alpha to        the user group information can be corrupted across storing in fsimage and reading back from fsimage    vulnerabilityurl        ,0
80625,10195250833.0,IssuesEvent,2019-08-12 17:39:48,golang/go,https://api.github.com/repos/golang/go,closed,encoding/json: Unmarshal map[string]interface{} target mishandled when passed as an interface{},Documentation,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.12.6 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""xxx""
GOCACHE=""xxx""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""xxx""
GOPROXY=""""
GORACE=""""
GOROOT=""xxx""
GOTMPDIR=""""
GOTOOLDIR=""xxx""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build894533395=/tmp/go-build -gno-record-gcc-switches""

</pre></details>

### What did you do?

Used a reference to the same map in multiple call to json.Unmarshal. See https://play.golang.org/p/bum-Q01e96M

### What did you expect to see?

Expected JSON unmarshaling into maps to merge entries between different calls to json.Unmarshal, as indicated by the docs.

The play example should output:

<pre>
map1: map[key1:data1 key2:data2]
map2: map[key1:data1 key2:data2]
map3: map[key1:map[key1.1:data1 key1.2:data2]]
</pre>

### What did you see instead?

Whenever the type of the unmarshal target is interface{} then a replacement value is created even if the existing entry is of type map[string]interface{} and is a suitable instance for unmarshal to use.

The play example outputs:

<pre>
result: map[key2:data2]
result: map[key1:data1 key2:data2]
result: map[key1:map[key1.2:data2]]
</pre>
",1.0,"encoding/json: Unmarshal map[string]interface{} target mishandled when passed as an interface{} - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.12.6 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""xxx""
GOCACHE=""xxx""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""xxx""
GOPROXY=""""
GORACE=""""
GOROOT=""xxx""
GOTMPDIR=""""
GOTOOLDIR=""xxx""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build894533395=/tmp/go-build -gno-record-gcc-switches""

</pre></details>

### What did you do?

Used a reference to the same map in multiple call to json.Unmarshal. See https://play.golang.org/p/bum-Q01e96M

### What did you expect to see?

Expected JSON unmarshaling into maps to merge entries between different calls to json.Unmarshal, as indicated by the docs.

The play example should output:

<pre>
map1: map[key1:data1 key2:data2]
map2: map[key1:data1 key2:data2]
map3: map[key1:map[key1.1:data1 key1.2:data2]]
</pre>

### What did you see instead?

Whenever the type of the unmarshal target is interface{} then a replacement value is created even if the existing entry is of type map[string]interface{} and is a suitable instance for unmarshal to use.

The play example outputs:

<pre>
result: map[key2:data2]
result: map[key1:data1 key2:data2]
result: map[key1:map[key1.2:data2]]
</pre>
",1,encoding json  unmarshal map interface   target mishandled when passed as an interface              what version of go are you using   go version            go version  go version       linux             does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env          go env  output       go env  goarch      gobin  xxx   gocache  xxx   goexe     goflags     gohostarch      gohostos  linux   goos  linux   gopath  xxx   goproxy     gorace     goroot  xxx   gotmpdir     gotooldir  xxx   gccgo  gccgo   cc  gcc   cxx  g     cgo enabled      gomod     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches               what did you do     used a reference to the same map in multiple call to json unmarshal  see          what did you expect to see     expected json unmarshaling into maps to merge entries between different calls to json unmarshal  as indicated by the docs     the play example should output           map      map      map             what did you see instead     whenever the type of the unmarshal target is interface   then a replacement value is created even if the existing entry is of type map interface   and is a suitable instance for unmarshal to use     the play example outputs        result  map   result  map   result  map       ,1
106385,23225251246.0,IssuesEvent,2022-08-02 22:56:26,WordPress/openverse-catalog,https://api.github.com/repos/WordPress/openverse-catalog,opened,Backfill image dimensions data,🟨 priority: medium 🛠 goal: fix 💻 aspect: code,"## Problem
<!-- Describe the part of the code you think should improve -->
Depends on #646 

Once we've added image dimensions detection for the providers that don't currently support them, we'll need to backfill the data for previously ingested records. The providers to backfill are:
* NYPL
* Smithsonian
* Walters Art Museum
* Finnish Museums
* Metropolitan*

\* Since Metropolitan is a dated DAG, we could potentially rely on the metropolitan reingestion workflow to backfill the data over time (#616).


## Implementation
<!-- Replace the [ ] with [x] to check the box. -->
- [ ] 🙋 I would be interested in implementing this feature.
",1.0,"Backfill image dimensions data - ## Problem
<!-- Describe the part of the code you think should improve -->
Depends on #646 

Once we've added image dimensions detection for the providers that don't currently support them, we'll need to backfill the data for previously ingested records. The providers to backfill are:
* NYPL
* Smithsonian
* Walters Art Museum
* Finnish Museums
* Metropolitan*

\* Since Metropolitan is a dated DAG, we could potentially rely on the metropolitan reingestion workflow to backfill the data over time (#616).


## Implementation
<!-- Replace the [ ] with [x] to check the box. -->
- [ ] 🙋 I would be interested in implementing this feature.
",0,backfill image dimensions data      problem     depends on        once we ve added image dimensions detection for the providers that don t currently support them  we ll need to backfill the data for previously ingested records  the providers to backfill are     nypl    smithsonian    walters art museum    finnish museums    metropolitan        since metropolitan is a dated dag  we could potentially rely on the metropolitan reingestion workflow to backfill the data over time               implementation         🙋 i would be interested in implementing this feature   ,0
324583,24008001258.0,IssuesEvent,2022-09-14 16:13:48,golang/go,https://api.github.com/repos/golang/go,closed,net/http: DefaultTransport documentation should describe HTTPS_PROXY,Documentation NeedsDecision,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
go version go1.12.4 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
Affirmative.


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/howard/.cache/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/howard/gopath""
GOPROXY=""""
GORACE=""""
GOROOT=""/home/howard/go""
GOTMPDIR=""""
GOTOOLDIR=""/home/howard/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build043222332=/tmp/go-build -gno-record-gcc-switches""

</pre></details>

### What did you do?

In https://golang.org/pkg/net/http/#RoundTripper, the online manual explains the following for RoundTripper:

> DefaultTransport is the default implementation of Transport and is used by DefaultClient. It establishes network connections as needed and caches them for reuse by subsequent calls. It uses HTTP proxies as directed by the $HTTP_PROXY and $NO_PROXY (or $http_proxy and $no_proxy) environment variables.

Although DefaultTransport uses proxy settings from system environment via [ProxyFromEnvironment](https://golang.org/pkg/net/http/#ProxyFromEnvironment), which not even recognises HTTP proxy, but HTTPS proxy also:

> ProxyFromEnvironment returns the URL of the proxy to use for a given request, as indicated by the environment variables HTTP_PROXY, HTTPS_PROXY and NO_PROXY (or the lowercase versions thereof). HTTPS_PROXY takes precedence over HTTP_PROXY for https requests.

`DefaultTransport` indeed behaves correctly and recognises both HTTPS and HTTP proxy settings from system environment. Therefore, please elaborate about the support of HTTPS proxy in the documentation for `DefaultTransport`.

Thanks!",1.0,"net/http: DefaultTransport documentation should describe HTTPS_PROXY - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
go version go1.12.4 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
Affirmative.


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/howard/.cache/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/howard/gopath""
GOPROXY=""""
GORACE=""""
GOROOT=""/home/howard/go""
GOTMPDIR=""""
GOTOOLDIR=""/home/howard/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build043222332=/tmp/go-build -gno-record-gcc-switches""

</pre></details>

### What did you do?

In https://golang.org/pkg/net/http/#RoundTripper, the online manual explains the following for RoundTripper:

> DefaultTransport is the default implementation of Transport and is used by DefaultClient. It establishes network connections as needed and caches them for reuse by subsequent calls. It uses HTTP proxies as directed by the $HTTP_PROXY and $NO_PROXY (or $http_proxy and $no_proxy) environment variables.

Although DefaultTransport uses proxy settings from system environment via [ProxyFromEnvironment](https://golang.org/pkg/net/http/#ProxyFromEnvironment), which not even recognises HTTP proxy, but HTTPS proxy also:

> ProxyFromEnvironment returns the URL of the proxy to use for a given request, as indicated by the environment variables HTTP_PROXY, HTTPS_PROXY and NO_PROXY (or the lowercase versions thereof). HTTPS_PROXY takes precedence over HTTP_PROXY for https requests.

`DefaultTransport` indeed behaves correctly and recognises both HTTPS and HTTP proxy settings from system environment. Therefore, please elaborate about the support of HTTPS proxy in the documentation for `DefaultTransport`.

Thanks!",1,net http  defaulttransport documentation should describe https proxy            what version of go are you using   go version          go version       linux             does this issue reproduce with the latest release   affirmative           what operating system and processor architecture are you using   go env          go env  output     goarch      gobin     gocache   home howard  cache go build   goexe     goflags     gohostarch      gohostos  linux   goos  linux   gopath   home howard gopath   goproxy     gorace     goroot   home howard go   gotmpdir     gotooldir   home howard go pkg tool linux     gccgo  gccgo   cc  gcc   cxx  g     cgo enabled      gomod     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches               what did you do     in   the online manual explains the following for roundtripper       defaulttransport is the default implementation of transport and is used by defaultclient  it establishes network connections as needed and caches them for reuse by subsequent calls  it uses http proxies as directed by the  http proxy and  no proxy  or  http proxy and  no proxy  environment variables     although defaulttransport uses proxy settings from system environment via     which not even recognises http proxy  but https proxy also       proxyfromenvironment returns the url of the proxy to use for a given request  as indicated by the environment variables http proxy  https proxy and no proxy  or the lowercase versions thereof   https proxy takes precedence over http proxy for https requests      defaulttransport  indeed behaves correctly and recognises both https and http proxy settings from system environment  therefore  please elaborate about the support of https proxy in the documentation for  defaulttransport      thanks ,1
7072,3077653295.0,IssuesEvent,2015-08-21 02:42:23,golang/go,https://api.github.com/repos/golang/go,closed,encoding/base64: documentation typo,Documentation,"In the docs for the base64 package in the [variables](http://golang.org/pkg/encoding/base64/#URLEncoding) section there is a typo.

The description under `var RawURLEncoding = URLEncoding.WithPadding(NoPadding)` uses `URLEncoding` to describe the above variable when it should be using `RawURLEncoding`.",1.0,"encoding/base64: documentation typo - In the docs for the base64 package in the [variables](http://golang.org/pkg/encoding/base64/#URLEncoding) section there is a typo.

The description under `var RawURLEncoding = URLEncoding.WithPadding(NoPadding)` uses `URLEncoding` to describe the above variable when it should be using `RawURLEncoding`.",1,encoding    documentation typo   in the docs for the   package in the     section there is a typo     the description under  var rawurlencoding   urlencoding withpadding nopadding   uses  urlencoding  to describe the above variable when it should be using  rawurlencoding  ,1
687084,23513300618.0,IssuesEvent,2022-08-18 18:46:26,livesup-dev/livesup,https://api.github.com/repos/livesup-dev/livesup,closed,Add api support for todos,priority:medium v0.0.5,"As a way to add support to keep track of tasks a project might have, we need to add the ability to manage them

Tasks will be grouped in a list. A list of tasks will be defined as follow:

Todo
* id
* title
* description
* project_id
",1.0,"Add api support for todos - As a way to add support to keep track of tasks a project might have, we need to add the ability to manage them

Tasks will be grouped in a list. A list of tasks will be defined as follow:

Todo
* id
* title
* description
* project_id
",0,add api support for todos   as a way to add support to keep track of tasks a project might have  we need to add the ability to manage them  tasks will be grouped in a list  a list of tasks will be defined as follow   todo   id   title   description   project id ,0
229443,18348909917.0,IssuesEvent,2021-10-08 09:58:51,tasks-delivery/MuOnline,https://api.github.com/repos/tasks-delivery/MuOnline,closed,Statistic tab implementation,feature implemented front-end p1 Tested,"Statistic tab should have several blocks

Block with general metrics with the following items:

- Server
- Server status
- Online
- Accounts
- Characters
- Guilds
- Version

Block with Castle Siege info with the following items:
- Castle owner
- Siege time
- Chronology of cycles
- Registered guilds

Block with Crywolf info with the following items:

- Fortress status
- Attack time

Block with Classes info with the following items:

- Magic Gladiator 
- Duel Master
- Dark Lord 
- Lord Emperor 
- Dark Wizard
- Soul Master 
- Grand Master 
- Dark Knight
- Blade Knight 
- Blade Master
- Elf 
- Muse Elf
- High Elf
- Summoner
- Bloody Summoner
- Dimension Master",1.0,"Statistic tab implementation - Statistic tab should have several blocks

Block with general metrics with the following items:

- Server
- Server status
- Online
- Accounts
- Characters
- Guilds
- Version

Block with Castle Siege info with the following items:
- Castle owner
- Siege time
- Chronology of cycles
- Registered guilds

Block with Crywolf info with the following items:

- Fortress status
- Attack time

Block with Classes info with the following items:

- Magic Gladiator 
- Duel Master
- Dark Lord 
- Lord Emperor 
- Dark Wizard
- Soul Master 
- Grand Master 
- Dark Knight
- Blade Knight 
- Blade Master
- Elf 
- Muse Elf
- High Elf
- Summoner
- Bloody Summoner
- Dimension Master",0,statistic tab implementation   statistic tab should have several blocks    block with general metrics with the following items       server    server status    online    accounts    characters    guilds    version    block with castle siege info with the following items     castle owner    siege time    chronology of cycles    registered guilds    block with crywolf info with the following items       fortress status    attack time    block with classes info with the following items       magic gladiator     duel master    dark lord     lord emperor     dark wizard    soul master     grand master     dark knight    blade knight     blade master    elf     muse elf    high elf    summoner    bloody summoner    dimension master,0
429278,30033557566.0,IssuesEvent,2023-06-27 11:14:00,golang/go,https://api.github.com/repos/golang/go,opened,doc: incomplete documentation for vanity import paths in combination with Go modules,Documentation,"https://go.dev/ref/mod#vcs documents the `<meta>` tag that needs to be hosted at the module path, with the concrete example of `golang.org/x/mod`. However, it doesn't document how the module path is determined, and which pages need to exist for that process. For example, a user can do `go get golang.org/x/mod/zip` in module mode. The documentation doesn't state whether `https://golang.org/x/mod/zip?go-get=1` needs to serve the meta tag or not.

Some vanity paths, like `gioui.org` suggest that these subpages don't have to exist, and that `go get` walks up the path until it gets a successful response that specifies the module path.

For example, `GOPROXY=direct go get gioui.org/widget/material` sends requests to the following URLs:

```
# get https://gioui.org/widget/material?go-get=1
# get https://gioui.org/widget?go-get=1
# get https://gioui.org/?go-get=1
# get https://gioui.org/widget?go-get=1: 404 Not Found (0.198s)
# get https://gioui.org/widget/material?go-get=1: 404 Not Found (0.200s)
# get https://gioui.org/?go-get=1: 200 OK (0.201s)
```

Out of these, only `https://gioui.org/?go-get=1` responds with a meta tag.

https://pkg.go.dev/cmd/go@go1.21rc2#hdr-Remote_import_paths also contains documentation on vanity import paths, but doesn't discuss module paths. It does suggest, however, that only one request — to the full import path — is being made:

> If the import path is not a known code hosting site and also lacks a version control qualifier, the go tool attempts to fetch the import over https/http and looks for a <meta> tag in the document's HTML <head>. 

This doesn't match the actual behavior of `go get` in module mode, but it does match `go get` in GOPATH mode. In fact, the previous example using gioui.org doesn't work in GOPATH mode, because gioui.org only serves the required meta tags for module paths, not for all possible import paths.

```
# get https://gioui.org/widget/material?go-get=1
# get https://gioui.org/widget/material?go-get=1: 404 Not Found (0.192s)
package gioui.org/widget/material: unrecognized import path ""gioui.org/widget/material"": reading https://gioui.org/widget/material?go-get=1: 404 Not Found
        server response: no such package
```

It would be nice to clarify, in the documentation, whether one can rely on the fact that `go get` walks up the import path until it finds the module path. Assuming that one can, it would also be interesting to explore whether it's acceptable to do so, as that only works for modules, not GOPATH.",1.0,"doc: incomplete documentation for vanity import paths in combination with Go modules - https://go.dev/ref/mod#vcs documents the `<meta>` tag that needs to be hosted at the module path, with the concrete example of `golang.org/x/mod`. However, it doesn't document how the module path is determined, and which pages need to exist for that process. For example, a user can do `go get golang.org/x/mod/zip` in module mode. The documentation doesn't state whether `https://golang.org/x/mod/zip?go-get=1` needs to serve the meta tag or not.

Some vanity paths, like `gioui.org` suggest that these subpages don't have to exist, and that `go get` walks up the path until it gets a successful response that specifies the module path.

For example, `GOPROXY=direct go get gioui.org/widget/material` sends requests to the following URLs:

```
# get https://gioui.org/widget/material?go-get=1
# get https://gioui.org/widget?go-get=1
# get https://gioui.org/?go-get=1
# get https://gioui.org/widget?go-get=1: 404 Not Found (0.198s)
# get https://gioui.org/widget/material?go-get=1: 404 Not Found (0.200s)
# get https://gioui.org/?go-get=1: 200 OK (0.201s)
```

Out of these, only `https://gioui.org/?go-get=1` responds with a meta tag.

https://pkg.go.dev/cmd/go@go1.21rc2#hdr-Remote_import_paths also contains documentation on vanity import paths, but doesn't discuss module paths. It does suggest, however, that only one request — to the full import path — is being made:

> If the import path is not a known code hosting site and also lacks a version control qualifier, the go tool attempts to fetch the import over https/http and looks for a <meta> tag in the document's HTML <head>. 

This doesn't match the actual behavior of `go get` in module mode, but it does match `go get` in GOPATH mode. In fact, the previous example using gioui.org doesn't work in GOPATH mode, because gioui.org only serves the required meta tags for module paths, not for all possible import paths.

```
# get https://gioui.org/widget/material?go-get=1
# get https://gioui.org/widget/material?go-get=1: 404 Not Found (0.192s)
package gioui.org/widget/material: unrecognized import path ""gioui.org/widget/material"": reading https://gioui.org/widget/material?go-get=1: 404 Not Found
        server response: no such package
```

It would be nice to clarify, in the documentation, whether one can rely on the fact that `go get` walks up the import path until it finds the module path. Assuming that one can, it would also be interesting to explore whether it's acceptable to do so, as that only works for modules, not GOPATH.",1,doc  incomplete documentation for vanity import paths in combination with go modules     documents the     tag that needs to be hosted at the module path  with the concrete example of  golang org x mod   however  it doesn t document how the module path is determined  and which pages need to exist for that process  for example  a user can do  go get golang org x mod zip  in module mode  the documentation doesn t state whether    needs to serve the meta tag or not     some vanity paths  like  gioui org  suggest that these subpages don t have to exist  and that  go get  walks up the path until it gets a successful response that specifies the module path     for example   goproxy direct go get gioui org widget material  sends requests to the following urls            get      get      get      get     not found          get     not found          get     ok               out of these  only    responds with a meta tag       also contains documentation on vanity import paths  but doesn t discuss module paths  it does suggest  however  that only one request — to the full import path — is being made       if the import path is not a known code hosting site and also lacks a version control qualifier  the go tool attempts to fetch the import over https http and looks for a   tag in the document s html        this doesn t match the actual behavior of  go get  in module mode  but it does match  go get  in gopath mode  in fact  the previous example using gioui org doesn t work in gopath mode  because gioui org only serves the required meta tags for module paths  not for all possible import paths            get      get     not found        package gioui org widget material  unrecognized import path  gioui org widget material   reading     not found          server response  no such package         it would be nice to clarify  in the documentation  whether one can rely on the fact that  go get  walks up the import path until it finds the module path  assuming that one can  it would also be interesting to explore whether it s acceptable to do so  as that only works for modules  not gopath ,1
23977,6498579355.0,IssuesEvent,2017-08-22 17:59:06,Microsoft/PTVS,https://api.github.com/repos/Microsoft/PTVS,closed,Ast interpreter needs to scrape its own builtin types,bug Code Intelligence,"Currently we get builtin types from the analyzer, which tries to get them from us. We need to scrape them ourselves first so we have good answers.",1.0,"Ast interpreter needs to scrape its own builtin types - Currently we get builtin types from the analyzer, which tries to get them from us. We need to scrape them ourselves first so we have good answers.",0,ast interpreter needs to scrape its own builtin types   currently we get builtin types from the analyzer  which tries to get them from us  we need to scrape them ourselves first so we have good answers ,0
10159,26419783803.0,IssuesEvent,2023-01-13 19:13:14,MicrosoftDocs/architecture-center,https://api.github.com/repos/MicrosoftDocs/architecture-center,closed,Not All Page Appears When Export To PDF,assigned-to-author doc-idea triaged architecture-center/svc Pri1 design-pattern/subsvc,"When I export to PDF some page doesn't appears for example:

 - Circuit Breaker Pattern
 - Claim Check
 - Compensating Transaction
 - Competing Consumers
 - Compute Resource Consolidation
 - CQRS
 - Deployment Stamps
 - Event Sourcing
 - External Configuration Store
 - Federated Identity

Best regards


---
#### Document Details

⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*

* ID: 0a4ecd26-cb7b-4cb2-ae3a-3748ada92771
* Version Independent ID: 97f96179-a22b-8401-a2f4-264a86b5d2f5
* Content: [Cloud design patterns - Azure Architecture Center](https://docs.microsoft.com/en-us/azure/architecture/patterns/)
* Content Source: [docs/patterns/index.md](https://github.com/microsoftdocs/architecture-center/blob/main/docs/patterns/index.md)
* Service: **architecture-center**
* Sub-service: **design-pattern**
* GitHub Login: @EdPrice-MSFT
* Microsoft Alias: **masashin**",1.0,"Not All Page Appears When Export To PDF - When I export to PDF some page doesn't appears for example:

 - Circuit Breaker Pattern
 - Claim Check
 - Compensating Transaction
 - Competing Consumers
 - Compute Resource Consolidation
 - CQRS
 - Deployment Stamps
 - Event Sourcing
 - External Configuration Store
 - Federated Identity

Best regards


---
#### Document Details

⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*

* ID: 0a4ecd26-cb7b-4cb2-ae3a-3748ada92771
* Version Independent ID: 97f96179-a22b-8401-a2f4-264a86b5d2f5
* Content: [Cloud design patterns - Azure Architecture Center](https://docs.microsoft.com/en-us/azure/architecture/patterns/)
* Content Source: [docs/patterns/index.md](https://github.com/microsoftdocs/architecture-center/blob/main/docs/patterns/index.md)
* Service: **architecture-center**
* Sub-service: **design-pattern**
* GitHub Login: @EdPrice-MSFT
* Microsoft Alias: **masashin**",0,not all page appears when export to pdf   when i export to pdf some page doesn t appears for example        circuit breaker pattern     claim check     compensating transaction     competing consumers     compute resource consolidation     cqrs     deployment stamps     event sourcing     external configuration store     federated identity    best regards                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    architecture center      sub service    design pattern      github login   edprice msft    microsoft alias    masashin  ,0
43594,7054602837.0,IssuesEvent,2018-01-04 01:57:03,golang/go,https://api.github.com/repos/golang/go,closed,testing: test naming guidelines are inconsistent with real-world practice,Documentation NeedsFix,"
### What version of Go are you using (`go version`)?
1.9.2

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?
linux amd64

### What did you do?
```
$ cat << EOF > foo_test.go
package foo
import ""testing""

func Test_Foo(t *testing.T) {
    println(""hello"")
}
EOF
```

```
$ go test -v ./
```

### What did you expect to see?
```
ok      _/some/dir     0.001s [no tests to run]
```

### What did you see instead?
```
=== RUN   Test_Foo
hello
--- PASS: Test_Foo (0.00s)
PASS
ok      _/some/dir     0.002s
```

Official documentation for Go [testing](https://golang.org/pkg/testing/) package states, that `go test` 

> automates execution of any function of the form `func TestXxx(*testing.T)` where `Xxx` can be any **alphanumeric** string (but the first letter must not be in [a-z]) and serves to identify the test routine.

There are tons of open-source go projects that use `_` (underscore) in tests names (although all Google projects I've seen so far do follow these naming guidelines), yet `_` is not _alphanumeric_ and, according to the documentation, should not work.

I believe either this statement in documentation has to be clarified or `go test` behavior has to be adjusted to conform to the documentation (unlikely, considering how ubiquitous `_` became)

",1.0,"testing: test naming guidelines are inconsistent with real-world practice - 
### What version of Go are you using (`go version`)?
1.9.2

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?
linux amd64

### What did you do?
```
$ cat << EOF > foo_test.go
package foo
import ""testing""

func Test_Foo(t *testing.T) {
    println(""hello"")
}
EOF
```

```
$ go test -v ./
```

### What did you expect to see?
```
ok      _/some/dir     0.001s [no tests to run]
```

### What did you see instead?
```
=== RUN   Test_Foo
hello
--- PASS: Test_Foo (0.00s)
PASS
ok      _/some/dir     0.002s
```

Official documentation for Go [testing](https://golang.org/pkg/testing/) package states, that `go test` 

> automates execution of any function of the form `func TestXxx(*testing.T)` where `Xxx` can be any **alphanumeric** string (but the first letter must not be in [a-z]) and serves to identify the test routine.

There are tons of open-source go projects that use `_` (underscore) in tests names (although all Google projects I've seen so far do follow these naming guidelines), yet `_` is not _alphanumeric_ and, according to the documentation, should not work.

I believe either this statement in documentation has to be clarified or `go test` behavior has to be adjusted to conform to the documentation (unlikely, considering how ubiquitous `_` became)

",1,testing  test naming guidelines are inconsistent with real world practice         what version of go are you using   go version                  does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env     linux          what did you do          cat   foo test go  package foo  import  testing     func test foo t  testing t         println  hello       eof                go test  v                what did you expect to see        ok        some dir                       what did you see instead            run   test foo  hello      pass  test foo        pass  ok        some dir                 official documentation for go     package states  that  go test        automates execution of any function of the form  func testxxx  testing t   where  xxx  can be any   alphanumeric   string  but the first letter must not be in    and serves to identify the test routine     there are tons of open source go projects that use      underscore  in tests names  although all google projects i ve seen so far do follow these naming guidelines   yet     is not  alphanumeric  and  according to the documentation  should not work     i believe either this statement in documentation has to be clarified or  go test  behavior has to be adjusted to conform to the documentation  unlikely  considering how ubiquitous     became     ,1
59422,8362833451.0,IssuesEvent,2018-10-03 17:59:23,golang/go,https://api.github.com/repos/golang/go,closed,proposal: go/doc: package-level functions should also be listed at the beginning of package doc page,Documentation Proposal,"It looks some package-level functions are listed with the methods of the return types of these functions instead of at the beginning of the package doc page from some version. However I find doing this is often very inconvenient for package users to find the desired package-level functions. For example, the `http.Get`, `http.Post`, etc functions are all listed under the `http.Response` type now. It is really hard to a new user to find out what global functions a package provides.

 I can't say doing this is always bad, so I propose that such package-level functions should be listed both at the beginning of the package doc page and under the return types.
",1.0,"proposal: go/doc: package-level functions should also be listed at the beginning of package doc page - It looks some package-level functions are listed with the methods of the return types of these functions instead of at the beginning of the package doc page from some version. However I find doing this is often very inconvenient for package users to find the desired package-level functions. For example, the `http.Get`, `http.Post`, etc functions are all listed under the `http.Response` type now. It is really hard to a new user to find out what global functions a package provides.

 I can't say doing this is always bad, so I propose that such package-level functions should be listed both at the beginning of the package doc page and under the return types.
",1,proposal  go doc  package level functions should also be listed at the beginning of package doc page   it looks some package level functions are listed with the methods of the return types of these functions instead of at the beginning of the package doc page from some version  however i find doing this is often very inconvenient for package users to find the desired package level functions  for example  the  http get    http post   etc functions are all listed under the  http response  type now  it is really hard to a new user to find out what global functions a package provides      i can t say doing this is always bad  so i propose that such package level functions should be listed both at the beginning of the package doc page and under the return types   ,1
467605,13451340129.0,IssuesEvent,2020-09-08 20:05:13,department-of-veterans-affairs/caseflow,https://api.github.com/repos/department-of-veterans-affairs/caseflow,closed,write hearing type to VACOLS when converting legacy hearings,Priority: High Product: caseflow-hearings Stakeholder: BVA Team: Tango 💃 Type: Enhancement,"Follows #14251
Connects #13956

## Description
Write `""R""` to HEARSCHED.HEARING_TYPE when we convert a legacy hearing to virtual, and `""V""` or `""C""` when it’s converted back.

## Acceptance criteria
- [ ] tests
",1.0,"write hearing type to VACOLS when converting legacy hearings - Follows #14251
Connects #13956

## Description
Write `""R""` to HEARSCHED.HEARING_TYPE when we convert a legacy hearing to virtual, and `""V""` or `""C""` when it’s converted back.

## Acceptance criteria
- [ ] tests
",0,write hearing type to vacols when converting legacy hearings   follows     connects          description  write   r   to hearsched hearing type when we convert a legacy hearing to virtual  and   v   or   c   when it’s converted back        acceptance criteria      tests  ,0
5453,8000835731.0,IssuesEvent,2018-07-22 20:42:11,renovatebot/renovate,https://api.github.com/repos/renovatebot/renovate,closed,Large lists of deps should be split into sections in PR body,feat needs-requirements pri4-low,"**What would you like Renovate to be able to do?**
It'd be nice to see large lists of deps split into sections for when there are multiple package files as they're currently all shown without any context to which file they belong.

**Additional context**
Please see https://github.com/pymedusa/Medusa/pull/4532#issuecomment-402117488",1.0,"Large lists of deps should be split into sections in PR body - **What would you like Renovate to be able to do?**
It'd be nice to see large lists of deps split into sections for when there are multiple package files as they're currently all shown without any context to which file they belong.

**Additional context**
Please see https://github.com/pymedusa/Medusa/pull/4532#issuecomment-402117488",0,large lists of deps should be split into sections in pr body     what would you like renovate to be able to do     it d be nice to see large lists of deps split into sections for when there are multiple package files as they re currently all shown without any context to which file they belong       additional context    please see  ,0
588392,17659508082.0,IssuesEvent,2021-08-21 07:36:07,107-systems/.github,https://api.github.com/repos/107-systems/.github,closed,Our labels and the label synchronisation action is simply the best thing ever,priority: high,"I can hardly express in words how happy the meaningful labels (which are the same across all repositories) make me :joy:

Thank you very much @per1234 

CC @generationmake @pavel-kirienko @vcaeken ",1.0,"Our labels and the label synchronisation action is simply the best thing ever - I can hardly express in words how happy the meaningful labels (which are the same across all repositories) make me :joy:

Thank you very much @per1234 

CC @generationmake @pavel-kirienko @vcaeken ",0,our labels and the label synchronisation action is simply the best thing ever   i can hardly express in words how happy the meaningful labels  which are the same across all repositories  make me  joy     thank you very much        cc  generationmake  pavel kirienko  vcaeken ,0
250900,18911832750.0,IssuesEvent,2021-11-16 14:50:00,golang/go,https://api.github.com/repos/golang/go,closed,x/website: page showing .go source file under doc/articles has invalid link to documentation,Documentation NeedsInvestigation,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?
not related

$ go version

</pre>

### Does this issue reproduce with the latest release?
not related


### What operating system and processor architecture are you using (`go env`)?
not related

### What did you do?
I was reading the code example at the following article:
https://golang.org/doc/articles/wiki/final.go
the link included at the beggining of the site didn t work:
the href at: 'Documentation: doc/articles/wiki'

### What did you expect to see?
I expected to see the the link to move me to the page :
  I expected link to redirect me to: 
golang.org/doc/articles/wiki/

### What did you see instead?
it sends me to: 
https://golang.org/pkg/doc/articles/wiki/
which is not avaliable :/",1.0,"x/website: page showing .go source file under doc/articles has invalid link to documentation - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?
not related

$ go version

</pre>

### Does this issue reproduce with the latest release?
not related


### What operating system and processor architecture are you using (`go env`)?
not related

### What did you do?
I was reading the code example at the following article:
https://golang.org/doc/articles/wiki/final.go
the link included at the beggining of the site didn t work:
the href at: 'Documentation: doc/articles/wiki'

### What did you expect to see?
I expected to see the the link to move me to the page :
  I expected link to redirect me to: 
golang.org/doc/articles/wiki/

### What did you see instead?
it sends me to: 
https://golang.org/pkg/doc/articles/wiki/
which is not avaliable :/",1,x website  page showing  go source file under doc articles has invalid link to documentation         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version     not related      go version             does this issue reproduce with the latest release   not related          what operating system and processor architecture are you using   go env     not related        what did you do   i was reading the code example at the following article      the link included at the beggining of the site didn t work   the href at   documentation  doc articles wiki         what did you expect to see   i expected to see the the link to move me to the page      i expected link to redirect me to    golang org doc articles wiki         what did you see instead   it sends me to       which is not avaliable   ,1
230635,7612435147.0,IssuesEvent,2018-05-01 17:32:33,elementary/installer,https://api.github.com/repos/elementary/installer,closed,Keyboard View: Automatically highlight/scroll to language,Priority: Wishlist Status: Confirmed,"Based on the selection of the language from the previous screen

<bountysource-plugin>

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/48782487-keyboard-view-automatically-highlight-scroll-to-language?utm_campaign=plugin&utm_content=tracker%2F46189108&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F46189108&utm_medium=issues&utm_source=github).
</bountysource-plugin>",1.0,"Keyboard View: Automatically highlight/scroll to language - Based on the selection of the language from the previous screen

<bountysource-plugin>

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/48782487-keyboard-view-automatically-highlight-scroll-to-language?utm_campaign=plugin&utm_content=tracker%2F46189108&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F46189108&utm_medium=issues&utm_source=github).
</bountysource-plugin>",0,keyboard view  automatically highlight scroll to language   based on the selection of the language from the previous screen              want to back this issue        we accept bounties via       ,0
15624,10328223995.0,IssuesEvent,2019-09-02 09:01:52,terraform-providers/terraform-provider-azurerm,https://api.github.com/repos/terraform-providers/terraform-provider-azurerm,closed,When creating kubernetes cluster I cannot label/tag the agents/nodes.,enhancement service/kubernetes-cluster upstream-microsoft,"Theres no way (that I can see) to specify the labels to apply to the nodes created when provisioning a cluster. I would expect agent `agent_pool_profile` to accept a set of pairs.

Google's provider for example has this -> https://www.terraform.io/docs/providers/google/r/container_cluster.html#labels

https://kubernetes.io/docs/concepts/configuration/assign-pod-node/
https://www.terraform.io/docs/providers/kubernetes/r/deployment.html#node_selector",1.0,"When creating kubernetes cluster I cannot label/tag the agents/nodes. - Theres no way (that I can see) to specify the labels to apply to the nodes created when provisioning a cluster. I would expect agent `agent_pool_profile` to accept a set of pairs.

Google's provider for example has this -> https://www.terraform.io/docs/providers/google/r/container_cluster.html#labels

https://kubernetes.io/docs/concepts/configuration/assign-pod-node/
https://www.terraform.io/docs/providers/kubernetes/r/deployment.html#node_selector",0,when creating kubernetes cluster i cannot label tag the agents nodes    theres no way  that i can see  to specify the labels to apply to the nodes created when provisioning a cluster  i would expect agent  agent pool profile  to accept a set of pairs     google s provider for example has this             ,0
16185,21707466693.0,IssuesEvent,2022-05-10 10:57:19,Annosz/UIInfoSuite2,https://api.github.com/repos/Annosz/UIInfoSuite2,reopened,Compatibility with Ridgeside Village,mod compatibility,"I was just wondering if it was possible to get the NPC map tracking to work with Ridgeside Village. 

All of the NPCs in RidgeSide show up in the top corner until they come to Pelican Town. And when I open the Ridgeside map, the Ridgeside NPCs are displayed overlapping the NPCs in Pelican Town.

After installing a new version of both modes today, I couldn't open the Ridgeside map until I visited Ridgeside. In the past, there was a separate rectangular ridge map on the left side of the map, so I could press it to open it, but it disappeared after this update.

I'm not sure which problem it is, so I'm asking both sides.",True,"Compatibility with Ridgeside Village - I was just wondering if it was possible to get the NPC map tracking to work with Ridgeside Village. 

All of the NPCs in RidgeSide show up in the top corner until they come to Pelican Town. And when I open the Ridgeside map, the Ridgeside NPCs are displayed overlapping the NPCs in Pelican Town.

After installing a new version of both modes today, I couldn't open the Ridgeside map until I visited Ridgeside. In the past, there was a separate rectangular ridge map on the left side of the map, so I could press it to open it, but it disappeared after this update.

I'm not sure which problem it is, so I'm asking both sides.",0,compatibility with ridgeside village   i was just wondering if it was possible to get the npc map tracking to work with ridgeside village      all of the npcs in ridgeside show up in the top corner until they come to pelican town  and when i open the ridgeside map  the ridgeside npcs are displayed overlapping the npcs in pelican town     after installing a new version of both modes today  i couldn t open the ridgeside map until i visited ridgeside  in the past  there was a separate rectangular ridge map on the left side of the map  so i could press it to open it  but it disappeared after this update     i m not sure which problem it is  so i m asking both sides ,0
748796,26137866093.0,IssuesEvent,2022-12-29 14:23:52,metabase/metabase,https://api.github.com/repos/metabase/metabase,opened,Joined columns dropped from table depending on alias name length,Type:Bug Priority:P2 Querying/GUI .Regression,"**Describe the bug**
Joined columns dropped from table depending on alias name length
Regression since 0.42
Unsure if this is BE or FE, but might just be FE doesn't handle the table aliasing returned from BE.

**Reproduce 1**
1. Admin > Data Model > Sample > Orders > rename field `Product ID` to `Product ID with a very long name`
And rename the table Products to `Products with a very long name`
2. Question > Sample > Orders join Products with a very long name
![image](https://user-images.githubusercontent.com/1447303/209963455-27ea0c55-c005-46d7-928f-1e547f577873.png)
3. Now drag one of the Products columns to the beginning
![image](https://user-images.githubusercontent.com/1447303/209964631-76052feb-b3f2-4f4f-9d4e-f6587b2565f4.png)
4. Run query, it will now drop all joined columns from the table
![image](https://user-images.githubusercontent.com/1447303/209964850-146fdc9f-54c2-4c6e-aa57-73d0f7119eb2.png)

**Reproduce 2**
It's a lot easier to trigger the problem with some database types like BigQuery (possibly also Oracle).
1. Question > **BigQuery** Sample > Orders join People on Orders.User_ID=People.ID (it will create a longer alias because the People table is not called Users)
![image](https://user-images.githubusercontent.com/1447303/209965906-1f60d194-c72a-4ada-97ad-7aea8ee062fd.png)
2. Now drag one of the People columns to the beginning
![image](https://user-images.githubusercontent.com/1447303/209965979-c66ceefb-9591-47f0-8944-f7aaabfeda31.png)
3. Run query, it will now drop all joined columns from the table
![image](https://user-images.githubusercontent.com/1447303/209966046-eac070f3-becb-46d9-9fa8-19070a31f263.png)

**Information about your Metabase Installation:**
Tested 0.41.7 thru 0.45.1. Regression since 0.42.

**Additional context**
Historically related to #20627/#20610/#20413
Related to #13455

:arrow_down: Please click the :+1: reaction instead of leaving a `+1` or `update?` comment",1.0,"Joined columns dropped from table depending on alias name length - **Describe the bug**
Joined columns dropped from table depending on alias name length
Regression since 0.42
Unsure if this is BE or FE, but might just be FE doesn't handle the table aliasing returned from BE.

**Reproduce 1**
1. Admin > Data Model > Sample > Orders > rename field `Product ID` to `Product ID with a very long name`
And rename the table Products to `Products with a very long name`
2. Question > Sample > Orders join Products with a very long name
![image](https://user-images.githubusercontent.com/1447303/209963455-27ea0c55-c005-46d7-928f-1e547f577873.png)
3. Now drag one of the Products columns to the beginning
![image](https://user-images.githubusercontent.com/1447303/209964631-76052feb-b3f2-4f4f-9d4e-f6587b2565f4.png)
4. Run query, it will now drop all joined columns from the table
![image](https://user-images.githubusercontent.com/1447303/209964850-146fdc9f-54c2-4c6e-aa57-73d0f7119eb2.png)

**Reproduce 2**
It's a lot easier to trigger the problem with some database types like BigQuery (possibly also Oracle).
1. Question > **BigQuery** Sample > Orders join People on Orders.User_ID=People.ID (it will create a longer alias because the People table is not called Users)
![image](https://user-images.githubusercontent.com/1447303/209965906-1f60d194-c72a-4ada-97ad-7aea8ee062fd.png)
2. Now drag one of the People columns to the beginning
![image](https://user-images.githubusercontent.com/1447303/209965979-c66ceefb-9591-47f0-8944-f7aaabfeda31.png)
3. Run query, it will now drop all joined columns from the table
![image](https://user-images.githubusercontent.com/1447303/209966046-eac070f3-becb-46d9-9fa8-19070a31f263.png)

**Information about your Metabase Installation:**
Tested 0.41.7 thru 0.45.1. Regression since 0.42.

**Additional context**
Historically related to #20627/#20610/#20413
Related to #13455

:arrow_down: Please click the :+1: reaction instead of leaving a `+1` or `update?` comment",0,joined columns dropped from table depending on alias name length     describe the bug    joined columns dropped from table depending on alias name length  regression since      unsure if this is be or fe  but might just be fe doesn t handle the table aliasing returned from be       reproduce         admin   data model   sample   orders   rename field  product id  to  product id with a very long name   and rename the table products to  products with a very long name      question   sample   orders join products with a very long name           now drag one of the products columns to the beginning           run query  it will now drop all joined columns from the table            reproduce      it s a lot easier to trigger the problem with some database types like bigquery  possibly also oracle       question     bigquery   sample   orders join people on orders user id people id  it will create a longer alias because the people table is not called users            now drag one of the people columns to the beginning           run query  it will now drop all joined columns from the table            information about your metabase installation     tested       thru        regression since           additional context    historically related to           related to        arrow down  please click the      reaction instead of leaving a      or  update   comment,0
152143,13446463489.0,IssuesEvent,2020-09-08 13:00:05,golang/go,https://api.github.com/repos/golang/go,closed,"x/website: It looks like there's a copy paste error in the ""Create a Go module"" tutorial",Documentation NeedsFix,"> Create a module -- Write a small module with functions you can call from another module.
> Call your code from another module -- Add simple error handling.
> Return and handle an error -- Add simple error handling.
> Return a random greeting -- Handle data in slices (Go's dynamically-sized arrays). 

The text in the 2nd list item is a duplicate of the text in the 3rd list item.",1.0,"x/website: It looks like there's a copy paste error in the ""Create a Go module"" tutorial - > Create a module -- Write a small module with functions you can call from another module.
> Call your code from another module -- Add simple error handling.
> Return and handle an error -- Add simple error handling.
> Return a random greeting -- Handle data in slices (Go's dynamically-sized arrays). 

The text in the 2nd list item is a duplicate of the text in the 3rd list item.",1,x website  it looks like there s a copy paste error in the  create a go module  tutorial     create a module    write a small module with functions you can call from another module     call your code from another module    add simple error handling     return and handle an error    add simple error handling     return a random greeting    handle data in slices  go s dynamically sized arrays       the text in the   list item is a duplicate of the text in the   list item ,1
5935,2989758065.0,IssuesEvent,2015-07-21 02:45:56,golang/go,https://api.github.com/repos/golang/go,closed,doc: effective_go.html GOMAXPROCS=1 does not hold anymore with Go1.5,Documentation,"[0] https://github.com/golang/go/blob/master/doc/effective_go.html#L3192-L3206

states that ""The current implementation of the Go runtime will not parallelize this code by default.""

as of Go 1.5 the implementation for that changed:
https://github.com/golang/go/blob/master/doc/go1.5.html#L36-L37

and ""by default, Go programs run with GOMAXPROCS set to the number of cores available"".
the section [0] should reflect that new implementation detail with perhaps something like:

The implementation of the Go runtime parallelize this code by default. 
Go programs run with <code>GOMAXPROCS</code> set to the
number of cores available but you can change this implementation default to your needs.
There are two related ways to do this.  Either run your job with environment
variable <code>GOMAXPROCS</code> set to the number of cores to use
or import the <code>runtime</code> package and call
<code>runtime.GOMAXPROCS(NCPU)</code>.",1.0,"doc: effective_go.html GOMAXPROCS=1 does not hold anymore with Go1.5 - [0] https://github.com/golang/go/blob/master/doc/effective_go.html#L3192-L3206

states that ""The current implementation of the Go runtime will not parallelize this code by default.""

as of Go 1.5 the implementation for that changed:
https://github.com/golang/go/blob/master/doc/go1.5.html#L36-L37

and ""by default, Go programs run with GOMAXPROCS set to the number of cores available"".
the section [0] should reflect that new implementation detail with perhaps something like:

The implementation of the Go runtime parallelize this code by default. 
Go programs run with <code>GOMAXPROCS</code> set to the
number of cores available but you can change this implementation default to your needs.
There are two related ways to do this.  Either run your job with environment
variable <code>GOMAXPROCS</code> set to the number of cores to use
or import the <code>runtime</code> package and call
<code>runtime.GOMAXPROCS(NCPU)</code>.",1,doc  effective go html gomaxprocs   does not hold anymore with              states that  the current implementation of the go runtime will not parallelize this code by default      as of go     the implementation for that changed        and  by default  go programs run with gomaxprocs set to the number of cores available    the section   should reflect that new implementation detail with perhaps something like     the implementation of the go runtime parallelize this code by default    go programs run with  gomaxprocs  set to the  number of cores available but you can change this implementation default to your needs   there are two related ways to do this   either run your job with environment  variable  gomaxprocs  set to the number of cores to use  or import the  runtime  package and call   runtime gomaxprocs ncpu   ,1
267705,28509178398.0,IssuesEvent,2023-04-19 01:42:02,dpteam/RK3188_TABLET,https://api.github.com/repos/dpteam/RK3188_TABLET,closed,CVE-2016-4913 (High) detected in linux-yocto-4.12v3.1.10 - autoclosed,Mend: dependency security vulnerability,"## CVE-2016-4913 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yocto-4.12v3.1.10</b></p></summary>
<p>

<p>Linux 4.12 Embedded Kernel</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto-4.12>https://git.yoctoproject.org/git/linux-yocto-4.12</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/dpteam/RK3188_TABLET/commit/0c501f5a0fd72c7b2ac82904235363bd44fd8f9e"">0c501f5a0fd72c7b2ac82904235363bd44fd8f9e</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/isofs/rock.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The get_rock_ridge_filename function in fs/isofs/rock.c in the Linux kernel before 4.5.5 mishandles NM (aka alternate name) entries containing \0 characters, which allows local users to obtain sensitive information from kernel memory or possibly have unspecified other impact via a crafted isofs filesystem.

<p>Publish Date: 2016-05-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-4913>CVE-2016-4913</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.8</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2016-4913"">https://nvd.nist.gov/vuln/detail/CVE-2016-4913</a></p>
<p>Release Date: 2016-05-23</p>
<p>Fix Resolution: 4.5.5</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2016-4913 (High) detected in linux-yocto-4.12v3.1.10 - autoclosed - ## CVE-2016-4913 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yocto-4.12v3.1.10</b></p></summary>
<p>

<p>Linux 4.12 Embedded Kernel</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto-4.12>https://git.yoctoproject.org/git/linux-yocto-4.12</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/dpteam/RK3188_TABLET/commit/0c501f5a0fd72c7b2ac82904235363bd44fd8f9e"">0c501f5a0fd72c7b2ac82904235363bd44fd8f9e</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/isofs/rock.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The get_rock_ridge_filename function in fs/isofs/rock.c in the Linux kernel before 4.5.5 mishandles NM (aka alternate name) entries containing \0 characters, which allows local users to obtain sensitive information from kernel memory or possibly have unspecified other impact via a crafted isofs filesystem.

<p>Publish Date: 2016-05-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-4913>CVE-2016-4913</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.8</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2016-4913"">https://nvd.nist.gov/vuln/detail/CVE-2016-4913</a></p>
<p>Release Date: 2016-05-23</p>
<p>Fix Resolution: 4.5.5</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in linux yocto           autoclosed      cve       high severity vulnerability     vulnerable library    linux yocto                linux     embedded kernel   library home page   a href    found in head commit   a href      found in base branch   master             vulnerable source files                  fs isofs rock c                    vulnerability details         the get rock ridge filename function in fs isofs rock c in the linux kernel before       mishandles nm  aka alternate name  entries containing    characters  which allows local users to obtain sensitive information from kernel memory or possibly have unspecified other impact via a crafted isofs filesystem    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  local     attack complexity  low     privileges required  low     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                      step up your open source security game with mend    ,0
102446,21963223144.0,IssuesEvent,2022-05-24 17:33:38,pwa-builder/PWABuilder,https://api.github.com/repos/pwa-builder/PWABuilder,opened,[VSCODE] Support Meta Oculus platform,feature request :mailbox_with_mail: needs triage :mag: vscode,"### Tell us about your feature idea

PWA Studio should support Oculus just like pwabuilder.com

### Do you have an implementation or a solution in mind?

use same platform pattern as other platforms 

### Have you considered any alternatives?

_No response_",1.0,"[VSCODE] Support Meta Oculus platform - ### Tell us about your feature idea

PWA Studio should support Oculus just like pwabuilder.com

### Do you have an implementation or a solution in mind?

use same platform pattern as other platforms 

### Have you considered any alternatives?

_No response_",0,  support meta oculus platform       tell us about your feature idea  pwa studio should support oculus just like pwabuilder com      do you have an implementation or a solution in mind   use same platform pattern as other platforms       have you considered any alternatives    no response ,0
79538,15586164033.0,IssuesEvent,2021-03-18 01:19:05,jrshutske/unit-conversion-api,https://api.github.com/repos/jrshutske/unit-conversion-api,opened,CVE-2019-14893 (High) detected in jackson-databind-2.9.8.jar,security vulnerability,"## CVE-2019-14893 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.8.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: /unit-conversion-api/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.8/jackson-databind-2.9.8.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-starter-actuator-2.1.2.RELEASE.jar (Root Library)
    - spring-boot-actuator-autoconfigure-2.1.2.RELEASE.jar
      - :x: **jackson-databind-2.9.8.jar** (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 flaw was discovered in FasterXML jackson-databind in all versions before 2.9.10 and 2.10.0, where it would permit polymorphic deserialization of malicious objects using the xalan JNDI gadget when used in conjunction with polymorphic type handling methods such as `enableDefaultTyping()` or when @JsonTypeInfo is using `Id.CLASS` or `Id.MINIMAL_CLASS` or in any other way which ObjectMapper.readValue might instantiate objects from unsafe sources. An attacker could use this flaw to execute arbitrary code.

<p>Publish Date: 2020-03-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14893>CVE-2019-14893</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14893"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14893</a></p>
<p>Release Date: 2020-03-02</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.10.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-2019-14893 (High) detected in jackson-databind-2.9.8.jar - ## CVE-2019-14893 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.8.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: /unit-conversion-api/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.8/jackson-databind-2.9.8.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-starter-actuator-2.1.2.RELEASE.jar (Root Library)
    - spring-boot-actuator-autoconfigure-2.1.2.RELEASE.jar
      - :x: **jackson-databind-2.9.8.jar** (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 flaw was discovered in FasterXML jackson-databind in all versions before 2.9.10 and 2.10.0, where it would permit polymorphic deserialization of malicious objects using the xalan JNDI gadget when used in conjunction with polymorphic type handling methods such as `enableDefaultTyping()` or when @JsonTypeInfo is using `Id.CLASS` or `Id.MINIMAL_CLASS` or in any other way which ObjectMapper.readValue might instantiate objects from unsafe sources. An attacker could use this flaw to execute arbitrary code.

<p>Publish Date: 2020-03-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14893>CVE-2019-14893</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14893"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14893</a></p>
<p>Release Date: 2020-03-02</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.10.0</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in jackson databind       jar      cve       high severity vulnerability     vulnerable library    jackson databind       jar      general data binding functionality for jackson  works on core streaming api   library home page   a href     path to dependency file   unit conversion api pom xml   path to vulnerable library   root    repository com fasterxml jackson core jackson databind       jackson databind       jar     dependency hierarchy      spring boot starter actuator       release jar  root library        spring boot actuator autoconfigure       release jar          x    jackson databind       jar    vulnerable library             vulnerability details         a flaw was discovered in fasterxml jackson databind in all versions before       and        where it would permit polymorphic deserialization of malicious objects using the xalan jndi gadget when used in conjunction with polymorphic type handling methods such as  enabledefaulttyping    or when  jsontypeinfo is using  id class  or  id minimal class  or in any other way which objectmapper readvalue might instantiate objects from unsafe sources  an attacker could use this flaw to execute arbitrary code    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  com fasterxml jackson core jackson databind                     step up your open source security game with whitesource    ,0
106648,9171981805.0,IssuesEvent,2019-03-04 04:51:04,orff/AppleWatchFaces,https://api.github.com/repos/orff/AppleWatchFaces,closed,long-drag on the spriteKit scene to time travel,enhancement idea to test,"if you tap and hold for a while, then drag to one side or the other, it would be fun to time travel forward and backward to see what the watch face will look like.  Bonus points for ""snapping"" back to the current time when it is let go.",1.0,"long-drag on the spriteKit scene to time travel - if you tap and hold for a while, then drag to one side or the other, it would be fun to time travel forward and backward to see what the watch face will look like.  Bonus points for ""snapping"" back to the current time when it is let go.",0,long drag on the spritekit scene to time travel   if you tap and hold for a while  then drag to one side or the other  it would be fun to time travel forward and backward to see what the watch face will look like   bonus points for  snapping  back to the current time when it is let go ,0
185385,15020920258.0,IssuesEvent,2021-02-01 15:14:49,golang/go,https://api.github.com/repos/golang/go,closed,x/website: tutorial function name typo,Documentation NeedsFix,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.15.7
</pre>

### Does this issue reproduce with the latest release?

This is not a 'Go' issue, but maybe a typo in the tutorial [Return greetings for multiple people](https://golang.org/doc/tutorial/greetings-multiple-people).


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
Windows , AMD Ryzen5 2600x
</pre></details>

### What did you do?

Walked through in the tutorial [Return greetings for multiple people](https://golang.org/doc/tutorial/greetings-multiple-people).
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->



### What did you expect to see?

The tutorial has this line: ""You have the **Hello** function return this map to the caller."".

### What did you see instead?

But it should be: ""You have the **Hellos** function return this map to the caller."".
Since the function that returns maps is named Hellos.",1.0,"x/website: tutorial function name typo - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.15.7
</pre>

### Does this issue reproduce with the latest release?

This is not a 'Go' issue, but maybe a typo in the tutorial [Return greetings for multiple people](https://golang.org/doc/tutorial/greetings-multiple-people).


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
Windows , AMD Ryzen5 2600x
</pre></details>

### What did you do?

Walked through in the tutorial [Return greetings for multiple people](https://golang.org/doc/tutorial/greetings-multiple-people).
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->



### What did you expect to see?

The tutorial has this line: ""You have the **Hello** function return this map to the caller."".

### What did you see instead?

But it should be: ""You have the **Hellos** function return this map to the caller."".
Since the function that returns maps is named Hellos.",1,x website  tutorial function name typo         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version            go version  go version                 does this issue reproduce with the latest release     this is not a  go  issue  but maybe a typo in the tutorial              what operating system and processor architecture are you using   go env          go env  output       go env  windows   amd                what did you do     walked through in the tutorial            if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best                  what did you expect to see     the tutorial has this line   you have the   hello   function return this map to the caller           what did you see instead     but it should be   you have the   hellos   function return this map to the caller     since the function that returns maps is named hellos ,1
153794,19708605240.0,IssuesEvent,2022-01-13 01:44:39,artsking/linux-4.19.72_CVE-2020-14386,https://api.github.com/repos/artsking/linux-4.19.72_CVE-2020-14386,opened,CVE-2019-19071 (High) detected in linux-yoctov5.4.51,security vulnerability,"## CVE-2019-19071 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yoctov5.4.51</b></p></summary>
<p>

<p>Yocto Linux Embedded kernel</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto>https://git.yoctoproject.org/git/linux-yocto</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/net/wireless/rsi/rsi_91x_mgmt.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/net/wireless/rsi/rsi_91x_mgmt.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
A memory leak in the rsi_send_beacon() function in drivers/net/wireless/rsi/rsi_91x_mgmt.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering rsi_prepare_beacon() failures, aka CID-d563131ef23c.

<p>Publish Date: 2019-11-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-19071>CVE-2019-19071</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://www.linuxkernelcves.com/cves/CVE-2019-19071"">https://www.linuxkernelcves.com/cves/CVE-2019-19071</a></p>
<p>Release Date: 2020-08-24</p>
<p>Fix Resolution: v5.5-rc1,v4.14.159,v4.19.89,v5.3.16,v5.4.3</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2019-19071 (High) detected in linux-yoctov5.4.51 - ## CVE-2019-19071 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yoctov5.4.51</b></p></summary>
<p>

<p>Yocto Linux Embedded kernel</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto>https://git.yoctoproject.org/git/linux-yocto</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/net/wireless/rsi/rsi_91x_mgmt.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/net/wireless/rsi/rsi_91x_mgmt.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
A memory leak in the rsi_send_beacon() function in drivers/net/wireless/rsi/rsi_91x_mgmt.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering rsi_prepare_beacon() failures, aka CID-d563131ef23c.

<p>Publish Date: 2019-11-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-19071>CVE-2019-19071</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://www.linuxkernelcves.com/cves/CVE-2019-19071"">https://www.linuxkernelcves.com/cves/CVE-2019-19071</a></p>
<p>Release Date: 2020-08-24</p>
<p>Fix Resolution: v5.5-rc1,v4.14.159,v4.19.89,v5.3.16,v5.4.3</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in linux            cve       high severity vulnerability     vulnerable library    linux              yocto linux embedded kernel   library home page   a href     found in base branch   master             vulnerable source files                  drivers net wireless rsi rsi   mgmt c        drivers net wireless rsi rsi   mgmt c                    vulnerability details         a memory leak in the rsi send beacon   function in drivers net wireless rsi rsi   mgmt c in the linux kernel through       allows attackers to cause a denial of service  memory consumption  by triggering rsi prepare beacon   failures  aka cid      publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                                              step up your open source security game with whitesource    ,0
60729,8459910430.0,IssuesEvent,2018-10-22 17:16:22,golang/go,https://api.github.com/repos/golang/go,closed,"x/tools/present: Docs say 'h' key in the browser will toggle extra emphasis of any highlighted lines, seemingly not true.",Documentation NeedsFix,"### What version of Go are you using (`go version`)?

```
go version go1.7.1 darwin/amd64
```
### What operating system and processor architecture are you using (`go env`)?

```
$ go env
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/Dmitri/Dropbox/Work/2013/GoLanding:/Users/Dmitri/Dropbox/Work/2013/GoLand""
GORACE=""""
GOROOT=""/usr/local/go""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/tw/kgz4v2kn4n7d7ryg5k_z3dk40000gn/T/go-build653232358=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
```
### What did you do?

I read the documentation for present slide format at https://godoc.org/golang.org/x/tools/present.

It said:

> Also, inside the displayed text a line that ends
> 
> ```
> // HL
> ```
> 
> will be highlighted in the display; the 'h' key in the browser will toggle extra emphasis of any highlighted lines.
### What did you expect to see?

Pressing 'h' key in browser would have some effect on emphasis of highlighted lines.
### What did you see instead?

Pressing 'h' key has no effect on emphasis of highlighted lines.

Looking at the code,

https://github.com/golang/tools/blob/b5358b5feea9734b97ff1e792ca6bc55170bc92a/cmd/present/static/slides.js#L408

It says `'H' hides the help text`.

So something doesn't look right here. I don't know if the documentation is wrong, or if the implementation has a bug.
",1.0,"x/tools/present: Docs say 'h' key in the browser will toggle extra emphasis of any highlighted lines, seemingly not true. - ### What version of Go are you using (`go version`)?

```
go version go1.7.1 darwin/amd64
```
### What operating system and processor architecture are you using (`go env`)?

```
$ go env
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/Dmitri/Dropbox/Work/2013/GoLanding:/Users/Dmitri/Dropbox/Work/2013/GoLand""
GORACE=""""
GOROOT=""/usr/local/go""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/tw/kgz4v2kn4n7d7ryg5k_z3dk40000gn/T/go-build653232358=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
```
### What did you do?

I read the documentation for present slide format at https://godoc.org/golang.org/x/tools/present.

It said:

> Also, inside the displayed text a line that ends
> 
> ```
> // HL
> ```
> 
> will be highlighted in the display; the 'h' key in the browser will toggle extra emphasis of any highlighted lines.
### What did you expect to see?

Pressing 'h' key in browser would have some effect on emphasis of highlighted lines.
### What did you see instead?

Pressing 'h' key has no effect on emphasis of highlighted lines.

Looking at the code,

https://github.com/golang/tools/blob/b5358b5feea9734b97ff1e792ca6bc55170bc92a/cmd/present/static/slides.js#L408

It says `'H' hides the help text`.

So something doesn't look right here. I don't know if the documentation is wrong, or if the implementation has a bug.
",1,x tools present  docs say  h  key in the browser will toggle extra emphasis of any highlighted lines  seemingly not true        what version of go are you using   go version            go version       darwin             what operating system and processor architecture are you using   go env              go env  goarch      gobin     goexe     gohostarch      gohostos  darwin   goos  darwin   gopath   users dmitri dropbox work   golanding  users dmitri dropbox work   goland   gorace     goroot   usr local go   gotooldir   usr local go pkg tool darwin     cc  clang   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders tw     t go    tmp go build  gno record gcc switches  fno common   cxx  clang     cgo enabled               what did you do     i read the documentation for present slide format at      it said       also  inside the displayed text a line that ends                  hl               will be highlighted in the display  the  h  key in the browser will toggle extra emphasis of any highlighted lines       what did you expect to see     pressing  h  key in browser would have some effect on emphasis of highlighted lines       what did you see instead     pressing  h  key has no effect on emphasis of highlighted lines     looking at the code          it says   h  hides the help text      so something doesn t look right here  i don t know if the documentation is wrong  or if the implementation has a bug   ,1
22405,3955963531.0,IssuesEvent,2016-04-29 23:39:02,area515/Creation-Workshop-Host,https://api.github.com/repos/area515/Creation-Workshop-Host,closed,Slicing Calculators Don't Recompute Unless Server Is Restarted,testing help wanted,"In the latest WesGilster/CWH dev build, at least for the ""Test"" button (haven't yet tried printing), changes to the slicing calculators do not update the graphs displayed until I restart the server. This may be due to some of the changes relating to compilation of JavaScript and I just might have caught an intermediate state of the feature in-progress.",1.0,"Slicing Calculators Don't Recompute Unless Server Is Restarted - In the latest WesGilster/CWH dev build, at least for the ""Test"" button (haven't yet tried printing), changes to the slicing calculators do not update the graphs displayed until I restart the server. This may be due to some of the changes relating to compilation of JavaScript and I just might have caught an intermediate state of the feature in-progress.",0,slicing calculators don t recompute unless server is restarted   in the latest wesgilster cwh dev build  at least for the  test  button  haven t yet tried printing   changes to the slicing calculators do not update the graphs displayed until i restart the server  this may be due to some of the changes relating to compilation of javascript and i just might have caught an intermediate state of the feature in progress ,0
10763,4821324871.0,IssuesEvent,2016-11-05 08:38:54,CleverRaven/Cataclysm-DDA,https://api.github.com/repos/CleverRaven/Cataclysm-DDA,closed,Windows 64 build failure,Build,"`make: /home/narc/mxe/usr/bin/x86_64-w64-mingw32.static-ccache: Command not found
make: *** [cataclysm.exe] Error 127
Build step 'Execute shell' marked build as failure
Recording fingerprints
IRC notifier plugin: Sending notification to: #CDDA-dev
SSH: Current build result is [FAILURE], not going to run.
[WS-CLEANUP] Deleting project workspace...[WS-CLEANUP] Skipped based on build state FAILURE
Finished: FAILURE
`",1.0,"Windows 64 build failure - `make: /home/narc/mxe/usr/bin/x86_64-w64-mingw32.static-ccache: Command not found
make: *** [cataclysm.exe] Error 127
Build step 'Execute shell' marked build as failure
Recording fingerprints
IRC notifier plugin: Sending notification to: #CDDA-dev
SSH: Current build result is [FAILURE], not going to run.
[WS-CLEANUP] Deleting project workspace...[WS-CLEANUP] Skipped based on build state FAILURE
Finished: FAILURE
`",0,windows   build failure    make   home narc mxe usr bin         static ccache  command not found  make        error    build step  execute shell  marked build as failure  recording fingerprints  irc notifier plugin  sending notification to   cdda dev  ssh  current build result is    not going to run     deleting project workspace     skipped based on build state failure  finished  failure   ,0
44499,11455014345.0,IssuesEvent,2020-02-06 18:13:28,rthadur/recaptcha,https://api.github.com/repos/rthadur/recaptcha,closed,A model that was produced by myself can't be load by load_model using Theano backend,backend:theano type:build/install,"I got same problems with theano backend. when I load_model a h5 model ,there is always a error: DLL load failed: The specified module could not be found。
model = load_model(r'my_plane_modelcnn.h5')
my_plane_modelcnn.h5 was a model by myself.
Traceback (most recent call last):

File ""F:/CODE/findplane/pre.py"", line 38, in
model = load_model(r'my_plane_modelcnn.h5')
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\engine\saving.py"", line 419, in load_model
model = _deserialize_model(f, custom_objects, compile)
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\engine\saving.py"", line 225, in deserialize_model
model = model_from_config(model_config, custom_objects=custom_objects)
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\engine\saving.py"", line 458, in model_from_config
return deserialize(config, custom_objects=custom_objects)
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\layers_init.py"", line 55, in deserialize
printable_module_name='layer')
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\utils\generic_utils.py"", line 145, in deserialize_keras_object
list(custom_objects.items())))
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\engine\sequential.py"", line 301, in from_config
model.add(layer)
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\engine\sequential.py"", line 165, in add
layer(x)
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\engine\base_layer.py"", line 431, in call
self.build(unpack_singleton(input_shapes))
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\layers\convolutional.py"", line 141, in build
constraint=self.kernel_constraint)
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\legacy\interfaces.py"", line 91, in wrapper
return func(*args, **kwargs)
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\engine\base_layer.py"", line 249, in add_weight
weight = K.variable(initializer(shape),
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\initializers.py"", line 218, in call
dtype=dtype, seed=self.seed)
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\backend\theano_backend.py"", line 2600, in random_uniform
return rng.uniform(shape, low=minval, high=maxval, dtype=dtype)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\sandbox\rng_mrg.py"", line 872, in uniform
rstates = self.get_substream_rstates(nstreams, dtype)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\configparser.py"", line 117, in res
return f(*args, **kwargs)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\sandbox\rng_mrg.py"", line 779, in get_substream_rstates
multMatVect(rval[0], A1p72, M1, A2p72, M2)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\sandbox\rng_mrg.py"", line 62, in multMatVect
[A_sym, s_sym, m_sym, A2_sym, s2_sym, m2_sym], o, profile=False)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\compile\function.py"", line 317, in function
output_keys=output_keys)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\compile\pfunc.py"", line 486, in pfunc
output_keys=output_keys)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\compile\function_module.py"", line 1841, in orig_function
fn = m.create(defaults)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\compile\function_module.py"", line 1715, in create
input_storage=input_storage_lists, storage_map=storage_map)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\gof\link.py"", line 699, in make_thunk
storage_map=storage_map)[:3]
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\gof\vm.py"", line 1091, in make_all
impl=impl))
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\gof\op.py"", line 955, in make_thunk
no_recycling)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\gof\op.py"", line 858, in make_c_thunk
output_storage=node_output_storage)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\gof\cc.py"", line 1217, in make_thunk
keep_lock=keep_lock)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\gof\cc.py"", line 1157, in compile
keep_lock=keep_lock)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\gof\cc.py"", line 1624, in cthunk_factory
key=key, lnk=self, keep_lock=keep_lock)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\gof\cmodule.py"", line 1189, in module_from_key
module = lnk.compile_cmodule(location)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\gof\cc.py"", line 1527, in compile_cmodule
preargs=preargs)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\gof\cmodule.py"", line 2405, in compile_str
return dlimport(lib_filename)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\gof\cmodule.py"", line 317, in dlimport
rval = import(module_name, {}, {}, [module_name])
ImportError: DLL load failed: The specified module could not be found。

In my mind, Theano or Keras version cause the errors, so I update the version. But the proplem still.
By the way ,when I delete the path of MinGW in the System variables of my computer , the error is gone. But when I pyinstaller it to an EXE, and run it ,command line indicated that no g++ detected. I thought that the path of MinGW could not be deleted.

And giving my list

altgraph 0.16.1 pypi_0 pypi
blas 1.0 mkl
ca-certificates 2019.1.23 0
certifi 2018.8.24 py35_1
cycler 0.10.0 py35h197a487_0
cython 0.29.6 pypi_0 pypi
freetype 2.9.1 ha9979f8_1
future 0.17.1 pypi_0 pypi
h5py 2.8.0 py35h3bdd7fb_2
hdf5 1.10.2 hac2f561_2
icc_rt 2019.0.0 h0cc432a_1
icu 58.2 h3fcc66b_1
intel-openmp 2019.1 144
jpeg 9b he27b436_2
keras 2.2.4 pypi_0 pypi
keras-applications 1.0.7 pypi_0 pypi
keras-preprocessing 1.0.9 py_0 defaults
kiwisolver 1.0.1 py35h6538335_0
libgpuarray 0.7.6 hfa6e2cd_0
libopencv 3.4.2 h20b85fd_0
libpng 1.6.36 h2a8f88b_0
libpython 2.1 py35_0
libtiff 4.0.10 hb898794_2
m2w64-binutils 2.25.1 5 defaults
m2w64-bzip2 1.0.6 6 defaults
m2w64-crt-git 5.0.0.4636.2595836 2 defaults
m2w64-gcc 5.3.0 6 defaults
m2w64-gcc-ada 5.3.0 6 defaults
m2w64-gcc-fortran 5.3.0 6 defaults
m2w64-gcc-libgfortran 5.3.0 6 defaults
m2w64-gcc-libs 5.3.0 7 defaults
m2w64-gcc-libs-core 5.3.0 7 defaults
m2w64-gcc-objc 5.3.0 6 defaults
m2w64-gmp 6.1.0 2 defaults
m2w64-headers-git 5.0.0.4636.c0ad18a 2 defaults
m2w64-isl 0.16.1 2 defaults
m2w64-libiconv 1.14 6 defaults
m2w64-libmangle-git 5.0.0.4509.2e5a9a2 2 defaults
m2w64-libwinpthread-git 5.0.0.4634.697f757 2 defaults
m2w64-make 4.1.2351.a80a8b8
m2w64-mpc 1.0.3
m2w64-mpfr 3.1.4
m2w64-pkg-config 0.29.1
m2w64-toolchain 5.3.0
m2w64-tools-git 5.0.0.4592.90b8472
m2w64-windows-default-manifest 6.4
m2w64-winpthreads-git 5.0.0.4634.697f757
m2w64-zlib 1.2.8 10 defaults
macholib 1.11 pypi_0 pypi
mako 1.0.7 pypi_0 pypi
markupsafe 1.0 py35hfa6e2cd_1
matplotlib 3.0.0 py35hd159220_0
mingw 4.7 1
mkl 2018.0.3 1
mkl-service 1.1.2 py35hb217b18_5
mkl_fft 1.0.6 py35hdbbee80_0
mkl_random 1.0.1 py35h77b88f5_1
msys2-conda-epoch 20160418 1 defaults
numpy 1.15.2 py35ha559c80_0
numpy-base 1.15.2 py35h8128ebf_0
opencv 3.3.1 py35h20b85fd_1
openssl 1.1.1b he774522_1
pefile 2018.8.8 pypi_0 pypi
pillow 5.4.1 pypi_0 pypi
pip 10.0.1 py35_0
py-opencv 3.4.2 py35hc319ecb_0
pygpu 0.7.6 py35h452e1ab_0
pyinstaller 3.4 pypi_0 pypi
pyparsing 2.2.1 py35_0
pyqt 5.9.2 py35h6538335_0
python 3.5.6 he025d50_0
python-dateutil 2.7.3 py35_0
pytz 2018.5 py35_0
pywin32 223 py35hfa6e2cd_1
pywin32-ctypes 0.2.0 pypi_0 pypi
pyyaml 3.13 pypi_0 pypi
qt 5.9.7 vc14h73c81de_0
scipy 1.2.1 pypi_0 pypi
setuptools 40.2.0 py35_0
sip 4.19.8 py35h6538335_0
six 1.11.0 py35_1
sqlite 3.27.2 he774522_0
theano 1.0.4 pypi_0 pypi
tornado 5.1.1 py35hfa6e2cd_0
vc 14.1 h0510ff6_4
vs2015_runtime 14.15.26706 h3a45250_0
wheel 0.31.1 py35_0
wincertstore 0.2 py35h3d52121_0
xz 5.2.4 h2fa13f4_4
zlib 1.2.11 h62dcd97_3
zstd 1.3.7 h508b16e_0

Thank you!

 Check that you are up-to-date with the master branch of Keras. You can update with:
pip install git+git://github.com/keras-team/keras.git --upgrade --no-deps

 Check that you are up-to-date with the master branch of Theano. You can update with:
pip install git+git://github.com/Theano/Theano.git --upgrade --no-deps

 Provide a link to a GitHub Gist of a Python script that can reproduce your issue (or just copy the script here if it is short).",1.0,"A model that was produced by myself can't be load by load_model using Theano backend - I got same problems with theano backend. when I load_model a h5 model ,there is always a error: DLL load failed: The specified module could not be found。
model = load_model(r'my_plane_modelcnn.h5')
my_plane_modelcnn.h5 was a model by myself.
Traceback (most recent call last):

File ""F:/CODE/findplane/pre.py"", line 38, in
model = load_model(r'my_plane_modelcnn.h5')
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\engine\saving.py"", line 419, in load_model
model = _deserialize_model(f, custom_objects, compile)
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\engine\saving.py"", line 225, in deserialize_model
model = model_from_config(model_config, custom_objects=custom_objects)
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\engine\saving.py"", line 458, in model_from_config
return deserialize(config, custom_objects=custom_objects)
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\layers_init.py"", line 55, in deserialize
printable_module_name='layer')
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\utils\generic_utils.py"", line 145, in deserialize_keras_object
list(custom_objects.items())))
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\engine\sequential.py"", line 301, in from_config
model.add(layer)
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\engine\sequential.py"", line 165, in add
layer(x)
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\engine\base_layer.py"", line 431, in call
self.build(unpack_singleton(input_shapes))
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\layers\convolutional.py"", line 141, in build
constraint=self.kernel_constraint)
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\legacy\interfaces.py"", line 91, in wrapper
return func(*args, **kwargs)
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\engine\base_layer.py"", line 249, in add_weight
weight = K.variable(initializer(shape),
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\initializers.py"", line 218, in call
dtype=dtype, seed=self.seed)
File ""F:\Anaconda2\envs\python35\lib\site-packages\keras\backend\theano_backend.py"", line 2600, in random_uniform
return rng.uniform(shape, low=minval, high=maxval, dtype=dtype)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\sandbox\rng_mrg.py"", line 872, in uniform
rstates = self.get_substream_rstates(nstreams, dtype)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\configparser.py"", line 117, in res
return f(*args, **kwargs)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\sandbox\rng_mrg.py"", line 779, in get_substream_rstates
multMatVect(rval[0], A1p72, M1, A2p72, M2)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\sandbox\rng_mrg.py"", line 62, in multMatVect
[A_sym, s_sym, m_sym, A2_sym, s2_sym, m2_sym], o, profile=False)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\compile\function.py"", line 317, in function
output_keys=output_keys)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\compile\pfunc.py"", line 486, in pfunc
output_keys=output_keys)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\compile\function_module.py"", line 1841, in orig_function
fn = m.create(defaults)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\compile\function_module.py"", line 1715, in create
input_storage=input_storage_lists, storage_map=storage_map)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\gof\link.py"", line 699, in make_thunk
storage_map=storage_map)[:3]
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\gof\vm.py"", line 1091, in make_all
impl=impl))
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\gof\op.py"", line 955, in make_thunk
no_recycling)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\gof\op.py"", line 858, in make_c_thunk
output_storage=node_output_storage)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\gof\cc.py"", line 1217, in make_thunk
keep_lock=keep_lock)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\gof\cc.py"", line 1157, in compile
keep_lock=keep_lock)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\gof\cc.py"", line 1624, in cthunk_factory
key=key, lnk=self, keep_lock=keep_lock)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\gof\cmodule.py"", line 1189, in module_from_key
module = lnk.compile_cmodule(location)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\gof\cc.py"", line 1527, in compile_cmodule
preargs=preargs)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\gof\cmodule.py"", line 2405, in compile_str
return dlimport(lib_filename)
File ""F:\Anaconda2\envs\python35\lib\site-packages\theano\gof\cmodule.py"", line 317, in dlimport
rval = import(module_name, {}, {}, [module_name])
ImportError: DLL load failed: The specified module could not be found。

In my mind, Theano or Keras version cause the errors, so I update the version. But the proplem still.
By the way ,when I delete the path of MinGW in the System variables of my computer , the error is gone. But when I pyinstaller it to an EXE, and run it ,command line indicated that no g++ detected. I thought that the path of MinGW could not be deleted.

And giving my list

altgraph 0.16.1 pypi_0 pypi
blas 1.0 mkl
ca-certificates 2019.1.23 0
certifi 2018.8.24 py35_1
cycler 0.10.0 py35h197a487_0
cython 0.29.6 pypi_0 pypi
freetype 2.9.1 ha9979f8_1
future 0.17.1 pypi_0 pypi
h5py 2.8.0 py35h3bdd7fb_2
hdf5 1.10.2 hac2f561_2
icc_rt 2019.0.0 h0cc432a_1
icu 58.2 h3fcc66b_1
intel-openmp 2019.1 144
jpeg 9b he27b436_2
keras 2.2.4 pypi_0 pypi
keras-applications 1.0.7 pypi_0 pypi
keras-preprocessing 1.0.9 py_0 defaults
kiwisolver 1.0.1 py35h6538335_0
libgpuarray 0.7.6 hfa6e2cd_0
libopencv 3.4.2 h20b85fd_0
libpng 1.6.36 h2a8f88b_0
libpython 2.1 py35_0
libtiff 4.0.10 hb898794_2
m2w64-binutils 2.25.1 5 defaults
m2w64-bzip2 1.0.6 6 defaults
m2w64-crt-git 5.0.0.4636.2595836 2 defaults
m2w64-gcc 5.3.0 6 defaults
m2w64-gcc-ada 5.3.0 6 defaults
m2w64-gcc-fortran 5.3.0 6 defaults
m2w64-gcc-libgfortran 5.3.0 6 defaults
m2w64-gcc-libs 5.3.0 7 defaults
m2w64-gcc-libs-core 5.3.0 7 defaults
m2w64-gcc-objc 5.3.0 6 defaults
m2w64-gmp 6.1.0 2 defaults
m2w64-headers-git 5.0.0.4636.c0ad18a 2 defaults
m2w64-isl 0.16.1 2 defaults
m2w64-libiconv 1.14 6 defaults
m2w64-libmangle-git 5.0.0.4509.2e5a9a2 2 defaults
m2w64-libwinpthread-git 5.0.0.4634.697f757 2 defaults
m2w64-make 4.1.2351.a80a8b8
m2w64-mpc 1.0.3
m2w64-mpfr 3.1.4
m2w64-pkg-config 0.29.1
m2w64-toolchain 5.3.0
m2w64-tools-git 5.0.0.4592.90b8472
m2w64-windows-default-manifest 6.4
m2w64-winpthreads-git 5.0.0.4634.697f757
m2w64-zlib 1.2.8 10 defaults
macholib 1.11 pypi_0 pypi
mako 1.0.7 pypi_0 pypi
markupsafe 1.0 py35hfa6e2cd_1
matplotlib 3.0.0 py35hd159220_0
mingw 4.7 1
mkl 2018.0.3 1
mkl-service 1.1.2 py35hb217b18_5
mkl_fft 1.0.6 py35hdbbee80_0
mkl_random 1.0.1 py35h77b88f5_1
msys2-conda-epoch 20160418 1 defaults
numpy 1.15.2 py35ha559c80_0
numpy-base 1.15.2 py35h8128ebf_0
opencv 3.3.1 py35h20b85fd_1
openssl 1.1.1b he774522_1
pefile 2018.8.8 pypi_0 pypi
pillow 5.4.1 pypi_0 pypi
pip 10.0.1 py35_0
py-opencv 3.4.2 py35hc319ecb_0
pygpu 0.7.6 py35h452e1ab_0
pyinstaller 3.4 pypi_0 pypi
pyparsing 2.2.1 py35_0
pyqt 5.9.2 py35h6538335_0
python 3.5.6 he025d50_0
python-dateutil 2.7.3 py35_0
pytz 2018.5 py35_0
pywin32 223 py35hfa6e2cd_1
pywin32-ctypes 0.2.0 pypi_0 pypi
pyyaml 3.13 pypi_0 pypi
qt 5.9.7 vc14h73c81de_0
scipy 1.2.1 pypi_0 pypi
setuptools 40.2.0 py35_0
sip 4.19.8 py35h6538335_0
six 1.11.0 py35_1
sqlite 3.27.2 he774522_0
theano 1.0.4 pypi_0 pypi
tornado 5.1.1 py35hfa6e2cd_0
vc 14.1 h0510ff6_4
vs2015_runtime 14.15.26706 h3a45250_0
wheel 0.31.1 py35_0
wincertstore 0.2 py35h3d52121_0
xz 5.2.4 h2fa13f4_4
zlib 1.2.11 h62dcd97_3
zstd 1.3.7 h508b16e_0

Thank you!

 Check that you are up-to-date with the master branch of Keras. You can update with:
pip install git+git://github.com/keras-team/keras.git --upgrade --no-deps

 Check that you are up-to-date with the master branch of Theano. You can update with:
pip install git+git://github.com/Theano/Theano.git --upgrade --no-deps

 Provide a link to a GitHub Gist of a Python script that can reproduce your issue (or just copy the script here if it is short).",0,a model that was produced by myself can t be load by load model using theano backend   i got same problems with theano backend  when i load model a   model  there is always a error  dll load failed  the specified module could not be found。  model   load model r my plane modelcnn      my plane modelcnn   was a model by myself   traceback  most recent call last      file  f  code findplane pre py   line    in  model   load model r my plane modelcnn      file  f    envs   lib site packages keras engine saving py   line    in load model  model    deserialize model f  custom objects  compile   file  f    envs   lib site packages keras engine saving py   line    in deserialize model  model   model from config model config  custom objects custom objects   file  f    envs   lib site packages keras engine saving py   line    in model from config  return deserialize config  custom objects custom objects   file  f    envs   lib site packages keras layers init py   line    in deserialize  printable module name  layer    file  f    envs   lib site packages keras utils generic utils py   line    in deserialize keras object  list custom objects items       file  f    envs   lib site packages keras engine sequential py   line    in from config  model add layer   file  f    envs   lib site packages keras engine sequential py   line    in add  layer x   file  f    envs   lib site packages keras engine base layer py   line    in call  self build unpack singleton input shapes    file  f    envs   lib site packages keras layers convolutional py   line    in build  constraint self kernel constraint   file  f    envs   lib site packages keras legacy interfaces py   line    in wrapper  return func  args    kwargs   file  f    envs   lib site packages keras engine base layer py   line    in add weight  weight   k variable initializer shape    file  f    envs   lib site packages keras initializers py   line    in call  dtype dtype  seed self seed   file  f    envs   lib site packages keras backend theano backend py   line    in random uniform  return rng uniform shape  low minval  high maxval  dtype dtype   file  f    envs   lib site packages theano sandbox rng mrg py   line    in uniform  rstates   self get substream rstates nstreams  dtype   file  f    envs   lib site packages theano configparser py   line    in res  return f  args    kwargs   file  f    envs   lib site packages theano sandbox rng mrg py   line    in get substream rstates  multmatvect rval                file  f    envs   lib site packages theano sandbox rng mrg py   line    in multmatvect     o  profile false   file  f    envs   lib site packages theano compile function py   line    in function  output keys output keys   file  f    envs   lib site packages theano compile pfunc py   line    in pfunc  output keys output keys   file  f    envs   lib site packages theano compile function module py   line    in orig function  fn   m create defaults   file  f    envs   lib site packages theano compile function module py   line    in create  input storage input storage lists  storage map storage map   file  f    envs   lib site packages theano gof link py   line    in make thunk  storage map storage map    file  f    envs   lib site packages theano gof vm py   line    in make all  impl impl    file  f    envs   lib site packages theano gof op py   line    in make thunk  no recycling   file  f    envs   lib site packages theano gof op py   line    in make c thunk  output storage node output storage   file  f    envs   lib site packages theano gof cc py   line    in make thunk  keep lock keep lock   file  f    envs   lib site packages theano gof cc py   line    in compile  keep lock keep lock   file  f    envs   lib site packages theano gof cc py   line    in cthunk factory  key key  lnk self  keep lock keep lock   file  f    envs   lib site packages theano gof cmodule py   line    in module from key  module   lnk compile cmodule location   file  f    envs   lib site packages theano gof cc py   line    in compile cmodule  preargs preargs   file  f    envs   lib site packages theano gof cmodule py   line    in compile str  return dlimport lib filename   file  f    envs   lib site packages theano gof cmodule py   line    in dlimport  rval   import module name              importerror  dll load failed  the specified module could not be found。    in my mind  theano or keras version cause the errors  so i update the version  but the proplem still   by the way  when i delete the path of mingw in the system variables of my computer   the error is gone  but when i pyinstaller it to an exe  and run it  command line indicated that no g   detected  i thought that the path of mingw could not be deleted     and giving my list    altgraph       pypi   pypi  blas     mkl  ca certificates          certifi            cycler            cython       pypi   pypi  freetype            future       pypi   pypi                            icc rt            icu          intel openmp        jpeg        keras       pypi   pypi  keras applications       pypi   pypi  keras preprocessing       py   defaults  kiwisolver            libgpuarray            libopencv            libpng            libpython          libtiff              binutils         defaults              defaults    crt git             defaults    gcc         defaults    gcc ada         defaults    gcc fortran         defaults    gcc libgfortran         defaults    gcc libs         defaults    gcc libs core         defaults    gcc objc         defaults    gmp         defaults    headers git             defaults    isl         defaults    libiconv       defaults    libmangle git             defaults    libwinpthread git             defaults    make            mpc          mpfr          pkg config          toolchain          tools git              windows default manifest        winpthreads git              zlib         defaults  macholib     pypi   pypi  mako       pypi   pypi  markupsafe          matplotlib            mingw        mkl          mkl service            mkl fft            mkl random              conda epoch     defaults  numpy            numpy base            opencv            openssl            pefile       pypi   pypi  pillow       pypi   pypi  pip            py opencv            pygpu            pyinstaller     pypi   pypi  pyparsing            pyqt            python            python dateutil            pytz                     ctypes       pypi   pypi  pyyaml     pypi   pypi  qt            scipy       pypi   pypi  setuptools            sip            six            sqlite            theano       pypi   pypi  tornado            vc            runtime            wheel            wincertstore          xz            zlib            zstd              thank you      check that you are up to date with the master branch of keras  you can update with   pip install git git   github com keras team keras git   upgrade   no deps     check that you are up to date with the master branch of theano  you can update with   pip install git git   github com theano theano git   upgrade   no deps     provide a link to a github gist of a python script that can reproduce your issue  or just copy the script here if it is short  ,0
191571,15297575146.0,IssuesEvent,2021-02-24 08:36:59,golang/go,https://api.github.com/repos/golang/go,closed,hash/maphash: typo in the documentation of Hash,Documentation NeedsFix,"The word Seed appears twice, want once.

https://github.com/golang/go/blob/66c27093d0df8be8a75b1ae35fe4ab2003fe028e/src/hash/maphash/maphash.go#L37

https://golang.org/pkg/hash/maphash/#Hash",1.0,"hash/maphash: typo in the documentation of Hash - The word Seed appears twice, want once.

https://github.com/golang/go/blob/66c27093d0df8be8a75b1ae35fe4ab2003fe028e/src/hash/maphash/maphash.go#L37

https://golang.org/pkg/hash/maphash/#Hash",1,hash maphash  typo in the documentation of hash   the word seed appears twice  want once           ,1
223840,17634480890.0,IssuesEvent,2021-08-19 12:13:28,nens/lizard-management-client,https://api.github.com/repos/nens/lizard-management-client,opened,Home page should not show snackbar message about selected organisation,bug Sprint disruption Test result,"On new arrival at the home page a snackbar message is shown with the text: ""Organisation 'A' selected"". The selected organisation is by default the first in the list a user has rights for.

We removed the organisation selection from the home page, because it is not relevant there. The message should also not show there, as it is confusing to users.

An example of the message (where it is supposed to show):
![image.png](https://images.zenhubusercontent.com/5ede3192cc5c2c4503d452e7/e08825a1-f19a-4425-9d5b-a5d28774472f)",1.0,"Home page should not show snackbar message about selected organisation - On new arrival at the home page a snackbar message is shown with the text: ""Organisation 'A' selected"". The selected organisation is by default the first in the list a user has rights for.

We removed the organisation selection from the home page, because it is not relevant there. The message should also not show there, as it is confusing to users.

An example of the message (where it is supposed to show):
![image.png](https://images.zenhubusercontent.com/5ede3192cc5c2c4503d452e7/e08825a1-f19a-4425-9d5b-a5d28774472f)",0,home page should not show snackbar message about selected organisation   on new arrival at the home page a snackbar message is shown with the text   organisation  a  selected   the selected organisation is by default the first in the list a user has rights for   we removed the organisation selection from the home page  because it is not relevant there  the message should also not show there  as it is confusing to users   an example of the message  where it is supposed to show       ,0
542853,15872545497.0,IssuesEvent,2021-04-09 00:08:24,googleapis/google-cloud-ruby,https://api.github.com/repos/googleapis/google-cloud-ruby,closed,"CloudTasks: GaxError RPC failed, caused by 3",api: cloudtasks external priority: p2 type: bug,"When I created http_request task using [GoogleCloudTasks Gem](https://github.com/googleapis/google-cloud-ruby/tree/master/google-cloud-tasks) version 1.3.2, `GaxError RPC failed, caused by 3` error occured.
I couldn't reproduced this error by version 1.3.1 and 1.3.0.

#### Environment details
  - OS: alpine (Docker image ruby:2.6.5-alpine3.9)
  - Ruby version: 2.6.5
  - Gem name and version: `gem 'google-cloud-tasks', '= 1.3.2'`

#### Steps to reproduce

  1. install google-cloud-tasks gem version 1.3.2
  2. execute bellow code

#### Code example

```ruby
require ""google/cloud/tasks""

project_id  = ARGV.shift
location_id = ARGV.shift
queue_id    = ARGV.shift

client = Google::Cloud::Tasks.new

parent = client.queue_path project_id, location_id, queue_id

task = {
  http_request: {
    http_method: ""POST"",
    url:  ""https://example.com/example/path/""
  }
}

response = client.create_task parent, task
```

run ` $ bundle exec ruby create_task.rb ""project-xxxxxxxx"" ""asia-northeast1"" ""queue-xxxxxxxx""`

#### Full backtrace

```sh
Traceback (most recent call last):
        10: from create_task.rb:19:in `<main>'
         9: from /usr/local/bundle/gems/google-cloud-tasks-1.3.2/lib/google/cloud/tasks/v2/cloud_tasks_client.rb:1120:in `create_task'
         8: from /usr/local/bundle/gems/google-gax-1.8.1/lib/google/gax/api_callable.rb:260:in `block in create_api_call'
         7: from /usr/local/bundle/gems/google-gax-1.8.1/lib/google/gax/api_callable.rb:230:in `block in create_api_call'
         6: from /usr/local/bundle/gems/google-gax-1.8.1/lib/google/gax/api_callable.rb:401:in `block in add_timeout_arg'
         5: from /usr/local/bundle/gems/grpc-1.26.0/src/ruby/lib/grpc/generic/client_stub.rb:171:in `block in request_response'
         4: from /usr/local/bundle/gems/grpc-1.26.0/src/ruby/lib/grpc/generic/interceptors.rb:170:in `intercept!'
         3: from /usr/local/bundle/gems/grpc-1.26.0/src/ruby/lib/grpc/generic/client_stub.rb:172:in `block (2 levels) in request_response'
         2: from /usr/local/bundle/gems/grpc-1.26.0/src/ruby/lib/grpc/generic/active_call.rb:377:in `request_response'
         1: from /usr/local/bundle/gems/grpc-1.26.0/src/ruby/lib/grpc/generic/active_call.rb:181:in `attach_status_results_and_complete_call'
/usr/local/bundle/gems/grpc-1.26.0/src/ruby/lib/grpc/generic/active_call.rb:31:in `check_status': 3:The request deadline is 2019-12-24T19:04:04.062331705-08:00. The deadline cannot be more than 30s in the future. (GRPC::InvalidArgument)
        3: from create_task.rb:19:in `<main>'
        2: from /usr/local/bundle/gems/google-cloud-tasks-1.3.2/lib/google/cloud/tasks/v2/cloud_tasks_client.rb:1120:in `create_task'
        1: from /usr/local/bundle/gems/google-gax-1.8.1/lib/google/gax/api_callable.rb:259:in `block in create_api_call'
/usr/local/bundle/gems/google-gax-1.8.1/lib/google/gax/api_callable.rb:264:in `rescue in block in create_api_call': GaxError RPC failed, caused by 3:The request deadline is 2019-12-24T19:04:04.062331705-08:00. The deadline cannot be more than 30s in the future. (Google::Gax::InvalidArgumentError)
```

#### related issue
- https://github.com/googleapis/google-cloud-ruby/issues/3941",1.0,"CloudTasks: GaxError RPC failed, caused by 3 - When I created http_request task using [GoogleCloudTasks Gem](https://github.com/googleapis/google-cloud-ruby/tree/master/google-cloud-tasks) version 1.3.2, `GaxError RPC failed, caused by 3` error occured.
I couldn't reproduced this error by version 1.3.1 and 1.3.0.

#### Environment details
  - OS: alpine (Docker image ruby:2.6.5-alpine3.9)
  - Ruby version: 2.6.5
  - Gem name and version: `gem 'google-cloud-tasks', '= 1.3.2'`

#### Steps to reproduce

  1. install google-cloud-tasks gem version 1.3.2
  2. execute bellow code

#### Code example

```ruby
require ""google/cloud/tasks""

project_id  = ARGV.shift
location_id = ARGV.shift
queue_id    = ARGV.shift

client = Google::Cloud::Tasks.new

parent = client.queue_path project_id, location_id, queue_id

task = {
  http_request: {
    http_method: ""POST"",
    url:  ""https://example.com/example/path/""
  }
}

response = client.create_task parent, task
```

run ` $ bundle exec ruby create_task.rb ""project-xxxxxxxx"" ""asia-northeast1"" ""queue-xxxxxxxx""`

#### Full backtrace

```sh
Traceback (most recent call last):
        10: from create_task.rb:19:in `<main>'
         9: from /usr/local/bundle/gems/google-cloud-tasks-1.3.2/lib/google/cloud/tasks/v2/cloud_tasks_client.rb:1120:in `create_task'
         8: from /usr/local/bundle/gems/google-gax-1.8.1/lib/google/gax/api_callable.rb:260:in `block in create_api_call'
         7: from /usr/local/bundle/gems/google-gax-1.8.1/lib/google/gax/api_callable.rb:230:in `block in create_api_call'
         6: from /usr/local/bundle/gems/google-gax-1.8.1/lib/google/gax/api_callable.rb:401:in `block in add_timeout_arg'
         5: from /usr/local/bundle/gems/grpc-1.26.0/src/ruby/lib/grpc/generic/client_stub.rb:171:in `block in request_response'
         4: from /usr/local/bundle/gems/grpc-1.26.0/src/ruby/lib/grpc/generic/interceptors.rb:170:in `intercept!'
         3: from /usr/local/bundle/gems/grpc-1.26.0/src/ruby/lib/grpc/generic/client_stub.rb:172:in `block (2 levels) in request_response'
         2: from /usr/local/bundle/gems/grpc-1.26.0/src/ruby/lib/grpc/generic/active_call.rb:377:in `request_response'
         1: from /usr/local/bundle/gems/grpc-1.26.0/src/ruby/lib/grpc/generic/active_call.rb:181:in `attach_status_results_and_complete_call'
/usr/local/bundle/gems/grpc-1.26.0/src/ruby/lib/grpc/generic/active_call.rb:31:in `check_status': 3:The request deadline is 2019-12-24T19:04:04.062331705-08:00. The deadline cannot be more than 30s in the future. (GRPC::InvalidArgument)
        3: from create_task.rb:19:in `<main>'
        2: from /usr/local/bundle/gems/google-cloud-tasks-1.3.2/lib/google/cloud/tasks/v2/cloud_tasks_client.rb:1120:in `create_task'
        1: from /usr/local/bundle/gems/google-gax-1.8.1/lib/google/gax/api_callable.rb:259:in `block in create_api_call'
/usr/local/bundle/gems/google-gax-1.8.1/lib/google/gax/api_callable.rb:264:in `rescue in block in create_api_call': GaxError RPC failed, caused by 3:The request deadline is 2019-12-24T19:04:04.062331705-08:00. The deadline cannot be more than 30s in the future. (Google::Gax::InvalidArgumentError)
```

#### related issue
- https://github.com/googleapis/google-cloud-ruby/issues/3941",0,cloudtasks  gaxerror rpc failed  caused by     when i created http request task using     version         gaxerror rpc failed  caused by    error occured   i couldn t reproduced this error by version       and                environment details      os  alpine  docker image ruby                 ruby version             gem name and version   gem  google cloud tasks                      steps to reproduce         install google cloud tasks gem version             execute bellow code         code example       ruby  require  google cloud tasks     project id    argv shift  location id   argv shift  queue id      argv shift    client   google  cloud  tasks new    parent   client queue path project id  location id  queue id    task        http request         http method   post        url                 response   client create task parent  task         run     bundle exec ruby create task rb  project xxxxxxxx   asia     queue xxxxxxxx           full backtrace       sh  traceback  most recent call last               from create task rb   in                  from  usr local bundle gems google cloud tasks       lib google cloud tasks   cloud tasks client rb   in  create task               from  usr local bundle gems google gax       lib google gax api callable rb   in  block in create api call               from  usr local bundle gems google gax       lib google gax api callable rb   in  block in create api call               from  usr local bundle gems google gax       lib google gax api callable rb   in  block in add timeout arg               from  usr local bundle gems grpc       src ruby lib grpc generic client stub rb   in  block in request response               from  usr local bundle gems grpc       src ruby lib grpc generic interceptors rb   in  intercept                from  usr local bundle gems grpc       src ruby lib grpc generic client stub rb   in  block    levels  in request response               from  usr local bundle gems grpc       src ruby lib grpc generic active call rb   in  request response               from  usr local bundle gems grpc       src ruby lib grpc generic active call rb   in  attach status results and complete call    usr local bundle gems grpc       src ruby lib grpc generic active call rb   in  check status     the request deadline is                  the deadline cannot be more than   in the future   grpc  invalidargument              from create task rb   in                 from  usr local bundle gems google cloud tasks       lib google cloud tasks   cloud tasks client rb   in  create task              from  usr local bundle gems google gax       lib google gax api callable rb   in  block in create api call    usr local bundle gems google gax       lib google gax api callable rb   in  rescue in block in create api call   gaxerror rpc failed  caused by   the request deadline is                  the deadline cannot be more than   in the future   google  gax  invalidargumenterror               related issue     ,0
14805,11161823355.0,IssuesEvent,2019-12-26 15:19:43,wix/yoshi,https://api.github.com/repos/wix/yoshi,closed,Build and deploy the website on PRs,:wave: Help wanted 👶 Good first issue 🛠 Infrastructure,"# 🙋 Feature Request

### 😯 Current Behavior

When someone is doing a PR to the website/docs, there is no live example to see.

### 🤔 Expected Behavior

The website can be previewed from the PR. (A comment with a link?)

### 💁 Possible Solution

Use something like https://surge.sh/ to deploy a temporary site with the changes from the PR and post a link as a comment.

### 🔦 Context

It's easier and faster to review PRs that way, which should speed up the work on the documentation.

### ⚙️ Nice to have

It would be very nice if it would run only if there was a change to the website.

(We can check if there was a change in the website/docs directories using GIT and run the publish + comment only then)",1.0,"Build and deploy the website on PRs - # 🙋 Feature Request

### 😯 Current Behavior

When someone is doing a PR to the website/docs, there is no live example to see.

### 🤔 Expected Behavior

The website can be previewed from the PR. (A comment with a link?)

### 💁 Possible Solution

Use something like https://surge.sh/ to deploy a temporary site with the changes from the PR and post a link as a comment.

### 🔦 Context

It's easier and faster to review PRs that way, which should speed up the work on the documentation.

### ⚙️ Nice to have

It would be very nice if it would run only if there was a change to the website.

(We can check if there was a change in the website/docs directories using GIT and run the publish + comment only then)",0,build and deploy the website on prs     🙋 feature request        😯 current behavior    when someone is doing a pr to the website docs  there is no live example to see         🤔 expected behavior    the website can be previewed from the pr   a comment with a link          💁 possible solution    use something like   to deploy a temporary site with the changes from the pr and post a link as a comment         🔦 context    it s easier and faster to review prs that way  which should speed up the work on the documentation         ⚙️ nice to have    it would be very nice if it would run only if there was a change to the website      we can check if there was a change in the website docs directories using git and run the publish   comment only then ,0
471342,13565337386.0,IssuesEvent,2020-09-18 11:32:10,zephyrproject-rtos/zephyr,https://api.github.com/repos/zephyrproject-rtos/zephyr,closed,gcc 10.x compile warning/error for array subscript 0 is outside the bounds in tests/bluetooth/tester/src/gap.c,area: Bluetooth bug priority: low,"When building `tests/bluetooth/tester` on `qemu_x86` with gcc 10.2 we get:

```
/home/galak/git/zephyr/tests/bluetooth/tester/src/gap.c: In function 'tester_handle_gap':
/home/galak/git/zephyr/tests/bluetooth/tester/src/gap.c:278:35: error: array subscript 254 is outside the bounds of an interior zero-length array 'const uint8_t[0]' {aka 'const unsigned char[]'} [-Werror=zero-length-bounds]
  278 |   ad[adv_len].type = cmd->adv_data[i++];
      |                      ~~~~~~~~~~~~~^~~~~
In file included from /home/galak/git/zephyr/tests/bluetooth/tester/src/gap.c:25:
/home/galak/git/zephyr/tests/bluetooth/tester/src/bttester.h:157:10: note: while referencing 'adv_data'
  157 |  uint8_t adv_data[0];
      |          ^~~~~~~~
/home/galak/git/zephyr/tests/bluetooth/tester/src/gap.c:279:39: error: array subscript 255 is outside the bounds of an interior zero-length array 'const uint8_t[0]' {aka 'const unsigned char[]'} [-Werror=zero-length-bounds]
  279 |   ad[adv_len].data_len = cmd->adv_data[i++];
      |                          ~~~~~~~~~~~~~^~~~~
In file included from /home/galak/git/zephyr/tests/bluetooth/tester/src/gap.c:25:
/home/galak/git/zephyr/tests/bluetooth/tester/src/bttester.h:157:10: note: while referencing 'adv_data'
  157 |  uint8_t adv_data[0];
      |          ^~~~~~~~
/home/galak/git/zephyr/tests/bluetooth/tester/src/gap.c:280:22: error: array subscript 256 is outside the bounds of an interior zero-length array 'const uint8_t[0]' {aka 'const unsigned char[]'} [-Werror=zero-length-bounds]
  280 |   ad[adv_len].data = &cmd->adv_data[i];
      |                      ^~~~~~~~~~~~~~~~~
In file included from /home/galak/git/zephyr/tests/bluetooth/tester/src/gap.c:25:
/home/galak/git/zephyr/tests/bluetooth/tester/src/bttester.h:157:10: note: while referencing 'adv_data'
  157 |  uint8_t adv_data[0];
      |          ^~~~~~~~
cc1: all warnings being treated as errors
```",1.0,"gcc 10.x compile warning/error for array subscript 0 is outside the bounds in tests/bluetooth/tester/src/gap.c - When building `tests/bluetooth/tester` on `qemu_x86` with gcc 10.2 we get:

```
/home/galak/git/zephyr/tests/bluetooth/tester/src/gap.c: In function 'tester_handle_gap':
/home/galak/git/zephyr/tests/bluetooth/tester/src/gap.c:278:35: error: array subscript 254 is outside the bounds of an interior zero-length array 'const uint8_t[0]' {aka 'const unsigned char[]'} [-Werror=zero-length-bounds]
  278 |   ad[adv_len].type = cmd->adv_data[i++];
      |                      ~~~~~~~~~~~~~^~~~~
In file included from /home/galak/git/zephyr/tests/bluetooth/tester/src/gap.c:25:
/home/galak/git/zephyr/tests/bluetooth/tester/src/bttester.h:157:10: note: while referencing 'adv_data'
  157 |  uint8_t adv_data[0];
      |          ^~~~~~~~
/home/galak/git/zephyr/tests/bluetooth/tester/src/gap.c:279:39: error: array subscript 255 is outside the bounds of an interior zero-length array 'const uint8_t[0]' {aka 'const unsigned char[]'} [-Werror=zero-length-bounds]
  279 |   ad[adv_len].data_len = cmd->adv_data[i++];
      |                          ~~~~~~~~~~~~~^~~~~
In file included from /home/galak/git/zephyr/tests/bluetooth/tester/src/gap.c:25:
/home/galak/git/zephyr/tests/bluetooth/tester/src/bttester.h:157:10: note: while referencing 'adv_data'
  157 |  uint8_t adv_data[0];
      |          ^~~~~~~~
/home/galak/git/zephyr/tests/bluetooth/tester/src/gap.c:280:22: error: array subscript 256 is outside the bounds of an interior zero-length array 'const uint8_t[0]' {aka 'const unsigned char[]'} [-Werror=zero-length-bounds]
  280 |   ad[adv_len].data = &cmd->adv_data[i];
      |                      ^~~~~~~~~~~~~~~~~
In file included from /home/galak/git/zephyr/tests/bluetooth/tester/src/gap.c:25:
/home/galak/git/zephyr/tests/bluetooth/tester/src/bttester.h:157:10: note: while referencing 'adv_data'
  157 |  uint8_t adv_data[0];
      |          ^~~~~~~~
cc1: all warnings being treated as errors
```",0,gcc   x compile warning error for array subscript   is outside the bounds in tests bluetooth tester src gap c   when building  tests bluetooth tester  on  qemu    with gcc     we get           home galak git zephyr tests bluetooth tester src gap c  in function  tester handle gap     home galak git zephyr tests bluetooth tester src gap c      error  array subscript   is outside the bounds of an interior zero length array  const   t    aka  const unsigned char               ad  type   cmd  adv data                                                     in file included from  home galak git zephyr tests bluetooth tester src gap c      home galak git zephyr tests bluetooth tester src bttester h      note  while referencing  adv data            t adv data                                home galak git zephyr tests bluetooth tester src gap c      error  array subscript   is outside the bounds of an interior zero length array  const   t    aka  const unsigned char               ad  data len   cmd  adv data                                                         in file included from  home galak git zephyr tests bluetooth tester src gap c      home galak git zephyr tests bluetooth tester src bttester h      note  while referencing  adv data            t adv data                                home galak git zephyr tests bluetooth tester src gap c      error  array subscript   is outside the bounds of an interior zero length array  const   t    aka  const unsigned char               ad  data    cmd  adv data                                                    in file included from  home galak git zephyr tests bluetooth tester src gap c      home galak git zephyr tests bluetooth tester src bttester h      note  while referencing  adv data            t adv data                                  all warnings being treated as errors     ,0
220873,16988194709.0,IssuesEvent,2021-06-30 16:44:53,golang/go,https://api.github.com/repos/golang/go,closed,os: example shows deprecated function,Documentation NeedsFix,"This is a documentation issue.

One of the examples in the `os` packages shows the usage of the `IsNotExist` function; however, this function's documentation recommends avoiding it in new code:

> This function predates errors.Is. It only supports errors returned by the os package. New code should use errors.Is(err, os.ErrNotExist). 

It seems like the example should be updated to demonstrate the new way of checking for this error instead.
",1.0,"os: example shows deprecated function - This is a documentation issue.

One of the examples in the `os` packages shows the usage of the `IsNotExist` function; however, this function's documentation recommends avoiding it in new code:

> This function predates errors.Is. It only supports errors returned by the os package. New code should use errors.Is(err, os.ErrNotExist). 

It seems like the example should be updated to demonstrate the new way of checking for this error instead.
",1,os  example shows deprecated function   this is a documentation issue     one of the examples in the  os  packages shows the usage of the  isnotexist  function  however  this function s documentation recommends avoiding it in new code       this function predates errors is  it only supports errors returned by the os package  new code should use errors is err  os errnotexist       it seems like the example should be updated to demonstrate the new way of checking for this error instead   ,1
144130,13097047946.0,IssuesEvent,2020-08-03 16:43:58,golang/go,https://api.github.com/repos/golang/go,closed,go.dev: Package URL for docs should end with package name,Documentation go.dev,"This is a UX issue related to how pkg.go.dev works as compared to godoc.org. Here are the API documentation URLs for the zap package,
 * godoc: https://godoc.org/go.uber.org/zap
 * pkg.go.dev: https://pkg.go.dev/go.uber.org/zap?tab=doc

If I delete the `?tab=doc`, it will end up redirecting with the URL parameter added.

Often, a user may want to navigate the package structure using the URL, e.g., Modifying `/zap` to `/zap/zaptest`. To do this with godoc, it was easy as the package name was the last element. With pkg.go.dev, it requires scanning (or deleting) `?tab=doc` before being able to make the modification, making the experience more painful.

Since the default go `pkg.go.dev/<package>` is the documentation page, can we also avoid adding the `?tab=doc` suffix to the URL?",1.0,"go.dev: Package URL for docs should end with package name - This is a UX issue related to how pkg.go.dev works as compared to godoc.org. Here are the API documentation URLs for the zap package,
 * godoc: https://godoc.org/go.uber.org/zap
 * pkg.go.dev: https://pkg.go.dev/go.uber.org/zap?tab=doc

If I delete the `?tab=doc`, it will end up redirecting with the URL parameter added.

Often, a user may want to navigate the package structure using the URL, e.g., Modifying `/zap` to `/zap/zaptest`. To do this with godoc, it was easy as the package name was the last element. With pkg.go.dev, it requires scanning (or deleting) `?tab=doc` before being able to make the modification, making the experience more painful.

Since the default go `pkg.go.dev/<package>` is the documentation page, can we also avoid adding the `?tab=doc` suffix to the URL?",1,go dev  package url for docs should end with package name   this is a ux issue related to how pkg go dev works as compared to godoc org  here are the api documentation urls for the zap package      godoc        pkg go dev       if i delete the   tab doc   it will end up redirecting with the url parameter added     often  a user may want to navigate the package structure using the url  e g   modifying   zap  to   zap zaptest   to do this with godoc  it was easy as the package name was the last element  with pkg go dev  it requires scanning  or deleting    tab doc  before being able to make the modification  making the experience more painful     since the default go  pkg go dev    is the documentation page  can we also avoid adding the   tab doc  suffix to the url ,1
40244,6808951078.0,IssuesEvent,2017-11-04 11:00:45,golang/go,https://api.github.com/repos/golang/go,closed,doc: reflect documentation doesn't show examples,Documentation,"Possibly a continuation of #21601. https://golang.org/pkg/reflect/ doesn't show examples, while https://godoc.org/reflect does.",1.0,"doc: reflect documentation doesn't show examples - Possibly a continuation of #21601. https://golang.org/pkg/reflect/ doesn't show examples, while https://godoc.org/reflect does.",1,doc  reflect documentation doesn t show examples   possibly a continuation of       doesn t show examples  while   does ,1
197921,22617747590.0,IssuesEvent,2022-06-30 01:04:34,turkdevops/sanity,https://api.github.com/repos/turkdevops/sanity,opened,CVE-2022-2217 (High) detected in parse-url-5.0.2.tgz,security vulnerability,"## CVE-2022-2217 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>parse-url-5.0.2.tgz</b></p></summary>

<p>An advanced url parser supporting git urls too.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/parse-url/-/parse-url-5.0.2.tgz"">https://registry.npmjs.org/parse-url/-/parse-url-5.0.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/parse-url/package.json</p>
<p>

Dependency Hierarchy:
  - lerna-3.22.1.tgz (Root Library)
    - version-3.22.1.tgz
      - github-client-3.22.0.tgz
        - git-url-parse-11.4.4.tgz
          - git-up-4.0.2.tgz
            - :x: **parse-url-5.0.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/turkdevops/sanity/commit/89bb5cff86a87b2bcdcd3ba981f2efd8eec9da51"">89bb5cff86a87b2bcdcd3ba981f2efd8eec9da51</a></p>
<p>Found in base branch: <b>next</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
Cross-site Scripting (XSS) - Generic in GitHub repository ionicabizau/parse-url prior to 7.0.0.

<p>Publish Date: 2022-06-27
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-2217>CVE-2022-2217</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.1</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: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://huntr.dev/bounties/4e046c63-b1ca-4bcc-b418-29796918a71b/"">https://huntr.dev/bounties/4e046c63-b1ca-4bcc-b418-29796918a71b/</a></p>
<p>Release Date: 2022-06-27</p>
<p>Fix Resolution: parse-url - 6.0.1</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2022-2217 (High) detected in parse-url-5.0.2.tgz - ## CVE-2022-2217 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>parse-url-5.0.2.tgz</b></p></summary>

<p>An advanced url parser supporting git urls too.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/parse-url/-/parse-url-5.0.2.tgz"">https://registry.npmjs.org/parse-url/-/parse-url-5.0.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/parse-url/package.json</p>
<p>

Dependency Hierarchy:
  - lerna-3.22.1.tgz (Root Library)
    - version-3.22.1.tgz
      - github-client-3.22.0.tgz
        - git-url-parse-11.4.4.tgz
          - git-up-4.0.2.tgz
            - :x: **parse-url-5.0.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/turkdevops/sanity/commit/89bb5cff86a87b2bcdcd3ba981f2efd8eec9da51"">89bb5cff86a87b2bcdcd3ba981f2efd8eec9da51</a></p>
<p>Found in base branch: <b>next</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
Cross-site Scripting (XSS) - Generic in GitHub repository ionicabizau/parse-url prior to 7.0.0.

<p>Publish Date: 2022-06-27
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-2217>CVE-2022-2217</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.1</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: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://huntr.dev/bounties/4e046c63-b1ca-4bcc-b418-29796918a71b/"">https://huntr.dev/bounties/4e046c63-b1ca-4bcc-b418-29796918a71b/</a></p>
<p>Release Date: 2022-06-27</p>
<p>Fix Resolution: parse-url - 6.0.1</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in parse url       tgz      cve       high severity vulnerability     vulnerable library    parse url       tgz      an advanced url parser supporting git urls too    library home page   a href     path to dependency file   package json   path to vulnerable library   node modules parse url package json     dependency hierarchy      lerna       tgz  root library        version       tgz         github client       tgz           git url parse       tgz             git up       tgz                x    parse url       tgz    vulnerable library   found in head commit   a href     found in base branch   next              vulnerability details         cross site scripting  xss    generic in github repository ionicabizau parse url prior to          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  none   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  parse url                       step up your open source security game with mend    ,0
686961,23510255102.0,IssuesEvent,2022-08-18 15:52:24,kubernetes-sigs/kueue,https://api.github.com/repos/kubernetes-sigs/kueue,closed,Add label to pending_workloads metric to show the inadmissible workloads,kind/feature help wanted priority/important-soon,"<!-- Please only use this template for submitting enhancement requests -->

**What would you like to be added**:

Add a label for the workloads that are inadmissible and are not being retried.

**Why is this needed**:

It's useful to understand the health of kueue and the cluster queues.
For example, if there are inadmissible workloads, the performance of the scheduler is not affected, but it might be an indication of a misconfiguration of the queues, or an attempt from a namespace to use resources that they shouldn't.

**Completion requirements**:

This enhancement requires the following artifacts:

- [ ] Design doc
- [ ] API change
- [ ] Docs update

The artifacts should be linked in subsequent comments.
",1.0,"Add label to pending_workloads metric to show the inadmissible workloads - <!-- Please only use this template for submitting enhancement requests -->

**What would you like to be added**:

Add a label for the workloads that are inadmissible and are not being retried.

**Why is this needed**:

It's useful to understand the health of kueue and the cluster queues.
For example, if there are inadmissible workloads, the performance of the scheduler is not affected, but it might be an indication of a misconfiguration of the queues, or an attempt from a namespace to use resources that they shouldn't.

**Completion requirements**:

This enhancement requires the following artifacts:

- [ ] Design doc
- [ ] API change
- [ ] Docs update

The artifacts should be linked in subsequent comments.
",0,add label to pending workloads metric to show the inadmissible workloads          what would you like to be added       add a label for the workloads that are inadmissible and are not being retried       why is this needed       it s useful to understand the health of kueue and the cluster queues   for example  if there are inadmissible workloads  the performance of the scheduler is not affected  but it might be an indication of a misconfiguration of the queues  or an attempt from a namespace to use resources that they shouldn t       completion requirements       this enhancement requires the following artifacts         design doc      api change      docs update    the artifacts should be linked in subsequent comments   ,0
196423,15594086932.0,IssuesEvent,2021-03-18 13:32:28,golang/go,https://api.github.com/repos/golang/go,closed,"crypto/rsa: EncryptOAEP documentation says ""if a given public key is used to decrypt"" instead of ""encrypt""",Documentation NeedsFix,"### What did you do?
Opened https://golang.org/pkg/crypto/rsa/#EncryptOAEP in browser

### What did you expect to see?

For example, if a given public key is used to **encrypt** two types of messages, then distinct label values could be used to ensure that a ciphertext for one purpose cannot be used for another by an attacker.

### What did you see instead?

For example, if a given public key is used to **decrypt** two types of messages then distinct label values could be used to ensure that a ciphertext for one purpose cannot be used for another by an attacker.",1.0,"crypto/rsa: EncryptOAEP documentation says ""if a given public key is used to decrypt"" instead of ""encrypt"" - ### What did you do?
Opened https://golang.org/pkg/crypto/rsa/#EncryptOAEP in browser

### What did you expect to see?

For example, if a given public key is used to **encrypt** two types of messages, then distinct label values could be used to ensure that a ciphertext for one purpose cannot be used for another by an attacker.

### What did you see instead?

For example, if a given public key is used to **decrypt** two types of messages then distinct label values could be used to ensure that a ciphertext for one purpose cannot be used for another by an attacker.",1,crypto rsa  encryptoaep documentation says  if a given public key is used to decrypt  instead of  encrypt        what did you do   opened   in browser        what did you expect to see     for example  if a given public key is used to   encrypt   two types of messages  then distinct label values could be used to ensure that a ciphertext for one purpose cannot be used for another by an attacker         what did you see instead     for example  if a given public key is used to   decrypt   two types of messages then distinct label values could be used to ensure that a ciphertext for one purpose cannot be used for another by an attacker ,1
119426,17612130061.0,IssuesEvent,2021-08-18 03:49:15,pakorn186c/paz,https://api.github.com/repos/pakorn186c/paz,opened,CVE-2021-33502 (High) detected in normalize-url-4.5.0.tgz,security vulnerability,"## CVE-2021-33502 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>normalize-url-4.5.0.tgz</b></p></summary>

<p>Normalize a URL</p>
<p>Library home page: <a href=""https://registry.npmjs.org/normalize-url/-/normalize-url-4.5.0.tgz"">https://registry.npmjs.org/normalize-url/-/normalize-url-4.5.0.tgz</a></p>
<p>Path to dependency file: paz/package.json</p>
<p>Path to vulnerable library: paz/node_modules/normalize-url</p>
<p>

Dependency Hierarchy:
  - core-2.0.0-beta.4.tgz (Root Library)
    - update-notifier-5.1.0.tgz
      - latest-version-5.1.0.tgz
        - package-json-6.5.0.tgz
          - got-9.6.0.tgz
            - cacheable-request-6.1.0.tgz
              - :x: **normalize-url-4.5.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/pakorn186c/paz/commit/192998ddea4d547d046cbe07b44f337b3cf50eda"">192998ddea4d547d046cbe07b44f337b3cf50eda</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The normalize-url package before 4.5.1, 5.x before 5.3.1, and 6.x before 6.0.1 for Node.js has a ReDoS (regular expression denial of service) issue because it has exponential performance for data: URLs.

<p>Publish Date: 2021-05-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-33502>CVE-2021-33502</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33502"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33502</a></p>
<p>Release Date: 2021-05-24</p>
<p>Fix Resolution: normalize-url - 4.5.1, 5.3.1, 6.0.1</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2021-33502 (High) detected in normalize-url-4.5.0.tgz - ## CVE-2021-33502 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>normalize-url-4.5.0.tgz</b></p></summary>

<p>Normalize a URL</p>
<p>Library home page: <a href=""https://registry.npmjs.org/normalize-url/-/normalize-url-4.5.0.tgz"">https://registry.npmjs.org/normalize-url/-/normalize-url-4.5.0.tgz</a></p>
<p>Path to dependency file: paz/package.json</p>
<p>Path to vulnerable library: paz/node_modules/normalize-url</p>
<p>

Dependency Hierarchy:
  - core-2.0.0-beta.4.tgz (Root Library)
    - update-notifier-5.1.0.tgz
      - latest-version-5.1.0.tgz
        - package-json-6.5.0.tgz
          - got-9.6.0.tgz
            - cacheable-request-6.1.0.tgz
              - :x: **normalize-url-4.5.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/pakorn186c/paz/commit/192998ddea4d547d046cbe07b44f337b3cf50eda"">192998ddea4d547d046cbe07b44f337b3cf50eda</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The normalize-url package before 4.5.1, 5.x before 5.3.1, and 6.x before 6.0.1 for Node.js has a ReDoS (regular expression denial of service) issue because it has exponential performance for data: URLs.

<p>Publish Date: 2021-05-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-33502>CVE-2021-33502</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33502"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33502</a></p>
<p>Release Date: 2021-05-24</p>
<p>Fix Resolution: normalize-url - 4.5.1, 5.3.1, 6.0.1</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in normalize url       tgz      cve       high severity vulnerability     vulnerable library    normalize url       tgz      normalize a url   library home page   a href     path to dependency file  paz package json   path to vulnerable library  paz node modules normalize url     dependency hierarchy      core       beta   tgz  root library        update notifier       tgz         latest version       tgz           package json       tgz             got       tgz               cacheable request       tgz                  x    normalize url       tgz    vulnerable library   found in head commit   a href     found in base branch   master              vulnerability details         the normalize url package before          x before        and   x before       for node js has a redos  regular expression denial of service  issue because it has exponential performance for data  urls    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  normalize url                                     step up your open source security game with whitesource    ,0
332652,10102398350.0,IssuesEvent,2019-07-29 11:05:01,radical-collaboration/hpc-workflows,https://api.github.com/repos/radical-collaboration/hpc-workflows,closed,EnTK on Princeton cluster,Princeton Rutgers help wanted priority:high,"@jeroentromp expressed interest in setting up the pilot + EnTK on one of the Princeton clusters to have a local testing ground for us to try things out before taking them to Summit.

Princeton will be getting a couple of Summit nodes in the near future, which might make the setup easier.",1.0,"EnTK on Princeton cluster - @jeroentromp expressed interest in setting up the pilot + EnTK on one of the Princeton clusters to have a local testing ground for us to try things out before taking them to Summit.

Princeton will be getting a couple of Summit nodes in the near future, which might make the setup easier.",0,entk on princeton cluster    jeroentromp expressed interest in setting up the pilot   entk on one of the princeton clusters to have a local testing ground for us to try things out before taking them to summit     princeton will be getting a couple of summit nodes in the near future  which might make the setup easier ,0
179120,6621764594.0,IssuesEvent,2017-09-21 20:28:42,vmware/vic-product,https://api.github.com/repos/vmware/vic-product,opened,Add OVA version,component/ova priority/high,"**User Statement:**

As a developer I want to know what system version and what data version is present on the VIC Appliance.
 
**Details:**

**Acceptance Criteria:**
- [ ] Add version file to somewhere in `/etc` to determine system version
- [ ] Add version file to somewhere in `/data` to determine data version
- [ ] In upgrade script, write the `/data` file so we know version from 1.2.1 going forward",1.0,"Add OVA version - **User Statement:**

As a developer I want to know what system version and what data version is present on the VIC Appliance.
 
**Details:**

**Acceptance Criteria:**
- [ ] Add version file to somewhere in `/etc` to determine system version
- [ ] Add version file to somewhere in `/data` to determine data version
- [ ] In upgrade script, write the `/data` file so we know version from 1.2.1 going forward",0,add ova version     user statement       as a developer i want to know what system version and what data version is present on the vic appliance        details         acceptance criteria         add version file to somewhere in   etc  to determine system version      add version file to somewhere in   data  to determine data version      in upgrade script  write the   data  file so we know version from       going forward,0
190501,15241005010.0,IssuesEvent,2021-02-19 07:43:29,golang/go,https://api.github.com/repos/golang/go,closed,"x/website: ""Writing Web Applications"" Link in Go documentation is broken",Documentation,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
NA
</pre>

### Does this issue reproduce with the latest release?
NA


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
NA
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->
1. Go to https://golang.org/doc
2. Click on ""Writing Web Applications""
3. It redirects to ""https://golang.org/doc/articles/wiki/"" where it simply says 
""open REDACTED: file does not exist""


### What did you expect to see?
I expected a sample web application

### What did you see instead?
Some random error message
""open REDACTED: file does not exist""",1.0,"x/website: ""Writing Web Applications"" Link in Go documentation is broken - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
NA
</pre>

### Does this issue reproduce with the latest release?
NA


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
NA
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->
1. Go to https://golang.org/doc
2. Click on ""Writing Web Applications""
3. It redirects to ""https://golang.org/doc/articles/wiki/"" where it simply says 
""open REDACTED: file does not exist""


### What did you expect to see?
I expected a sample web application

### What did you see instead?
Some random error message
""open REDACTED: file does not exist""",1,x website   writing web applications  link in go documentation is broken         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version            go version  na           does this issue reproduce with the latest release   na          what operating system and processor architecture are you using   go env          go env  output       go env  na            what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best           go to       click on  writing web applications      it redirects to    where it simply says    open redacted  file does not exist           what did you expect to see   i expected a sample web application        what did you see instead   some random error message   open redacted  file does not exist ,1
36527,6538269571.0,IssuesEvent,2017-09-01 04:52:20,golang/go,https://api.github.com/repos/golang/go,closed,cmd/vet: document better the cmd/go flags that go vet supports,Documentation,"Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
go version go1.9 linux/amd64

### Does this issue reproduce with the latest release?
this is the latest release

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/travis/gopath""
GORACE=""""
GOROOT=""/home/travis/.gimme/versions/go1.9.linux.amd64""
GOTOOLDIR=""/home/travis/.gimme/versions/go1.9.linux.amd64/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build582418013=/tmp/go-build -gno-record-gcc-switches""
CXX=""g++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
```

### What did you do?

I have a Makefile that (after variable expansion) runs:
`go vet -ldflags=""-X main.version=dev-2017-08-31T04:06:35+0000 ""  ./cmd/... ./utils/... ./pkg/... ./metadata/...`

On 1.7, 1.8, this works.  On go-1.9, this complains about `-ldflags` no longer being a valid option.

I note the go-1.9 release notes [make a point of saying](https://golang.org/doc/go1.9#vet):

> The vet command has been better integrated into the go tool, so go vet now supports all standard build flags while vet's own flags are now available from go vet as well as from go tool vet.

I think what I'm seeing is the exact opposite of this.

### What did you expect to see?

Successful `go vet` output/warnings.

### What did you see instead?

```
flag provided but not defined: -ldflags
Usage of vet:
	vet [flags] directory...
	vet [flags] files... # Must be a single package
By default, -all is set and all non-experimental checks are run.
For more information run
	go doc cmd/vet
Flags:
  -all
    	enable all non-experimental checks
  -asmdecl
  ...
```",1.0,"cmd/vet: document better the cmd/go flags that go vet supports - Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
go version go1.9 linux/amd64

### Does this issue reproduce with the latest release?
this is the latest release

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/travis/gopath""
GORACE=""""
GOROOT=""/home/travis/.gimme/versions/go1.9.linux.amd64""
GOTOOLDIR=""/home/travis/.gimme/versions/go1.9.linux.amd64/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build582418013=/tmp/go-build -gno-record-gcc-switches""
CXX=""g++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
```

### What did you do?

I have a Makefile that (after variable expansion) runs:
`go vet -ldflags=""-X main.version=dev-2017-08-31T04:06:35+0000 ""  ./cmd/... ./utils/... ./pkg/... ./metadata/...`

On 1.7, 1.8, this works.  On go-1.9, this complains about `-ldflags` no longer being a valid option.

I note the go-1.9 release notes [make a point of saying](https://golang.org/doc/go1.9#vet):

> The vet command has been better integrated into the go tool, so go vet now supports all standard build flags while vet's own flags are now available from go vet as well as from go tool vet.

I think what I'm seeing is the exact opposite of this.

### What did you expect to see?

Successful `go vet` output/warnings.

### What did you see instead?

```
flag provided but not defined: -ldflags
Usage of vet:
	vet [flags] directory...
	vet [flags] files... # Must be a single package
By default, -all is set and all non-experimental checks are run.
For more information run
	go doc cmd/vet
Flags:
  -all
    	enable all non-experimental checks
  -asmdecl
  ...
```",1,cmd vet  document better the cmd go flags that go vet supports   please answer these questions before submitting your issue  thanks           what version of go are you using   go version     go version     linux          does this issue reproduce with the latest release   this is the latest release        what operating system and processor architecture are you using   go env          goarch      gobin     goexe     gohostarch      gohostos  linux   goos  linux   gopath   home travis gopath   gorace     goroot   home travis  gimme versions     linux     gotooldir   home travis  gimme versions     linux   pkg tool linux     gccgo  gccgo   cc  gcc   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches   cxx  g     cgo enabled      cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config              what did you do     i have a makefile that  after variable expansion  runs    go vet  ldflags   x main version dev                  cmd       utils       pkg       metadata         on           this works   on go      this complains about   ldflags  no longer being a valid option     i note the go     release notes          the vet command has been better integrated into the go tool  so go vet now supports all standard build flags while vet s own flags are now available from go vet as well as from go tool vet     i think what i m seeing is the exact opposite of this         what did you expect to see     successful  go vet  output warnings         what did you see instead          flag provided but not defined   ldflags  usage of vet   	vet   directory     	vet   files      must be a single package  by default   all is set and all non experimental checks are run   for more information run  	go doc cmd vet  flags      all      	enable all non experimental checks     asmdecl            ,1
109752,11648500779.0,IssuesEvent,2020-03-01 21:04:53,golang/go,https://api.github.com/repos/golang/go,closed,syscall/js: unclear behavior of js-triggered and wrapped functions,Arch-Wasm Documentation NeedsFix help wanted,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
go version go1.13 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
go env
GO111MODULE=""on""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/tschinke/Library/Caches/go-build""
GOENV=""/Users/tschinke/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/tschinke/go""
GOPRIVATE=""""
GOPROXY=""direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/tschinke/repos/wdy_ausbildung/trainiety/app/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/bv/6rt5ck194ls704dz9p4c0hlh0000gn/T/go-build951955169=/tmp/go-build -gno-record-gcc-switches -fno-common""


</pre></details>

### What did you do?
```
<div id=""outer"" class=""fullscreen"">
  <div id=""inner"" class=""dialog"">
  </div>
</div>

var outerDiv js.Value = ...
var innerDiv js.Value = ...

outerDiv.Call(""addEventListener"", ""click"", js.FuncOf(func(this js.Value, args []js.Value) interface{} {
		log.Println(""listener called: "", this, this.Get(""id""))
		return nil
	}), once)
[...]
innerDiv.Call(""addEventListener"", ""click"", js.FuncOf(func(this js.Value, args []js.Value) interface{} {
                 args[0].Call(""stopPropagation"")
		log.Println(""listener called: "", this, this.Get(""id""))
		return nil
	}), once)
```




### What did you expect to see?
Naturally I expected that the listener to the inner div should always be called first. However looking at  the documentation of js.FuncOf, I don't know what to expect:

> Invoking the JavaScript function will synchronously call the Go function fn with the value of JavaScript's ""this"" keyword and the arguments of the invocation.
> [...]
> A wrapped function triggered by JavaScript's event loop gets executed on an extra goroutine.
> Blocking operations in the wrapped function will block the event loop.
>[...]
>A blocking function should therefore explicitly start a new goroutine.

The logic of these statements is contradictory: 
* What exactly is meant by a  ""synchronous call"" in the first statement?
* If a wrapped and triggered function is always executed in a goroutine, why should it block the event loop?

### What did you see instead?
I tried to use `stopPropagation` but the calling order is always wrong (outer-div first), independent of registration order. Also if a callback is always executed within a new goroutine, it sounds like `stopPropagation` et. al cannot be used properly. 

The documentation of js.FuncOf does not help me much to understand the actual calling behavior or at least if this works as ""expected"".
",1.0,"syscall/js: unclear behavior of js-triggered and wrapped functions - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
go version go1.13 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
go env
GO111MODULE=""on""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/tschinke/Library/Caches/go-build""
GOENV=""/Users/tschinke/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/tschinke/go""
GOPRIVATE=""""
GOPROXY=""direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/tschinke/repos/wdy_ausbildung/trainiety/app/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/bv/6rt5ck194ls704dz9p4c0hlh0000gn/T/go-build951955169=/tmp/go-build -gno-record-gcc-switches -fno-common""


</pre></details>

### What did you do?
```
<div id=""outer"" class=""fullscreen"">
  <div id=""inner"" class=""dialog"">
  </div>
</div>

var outerDiv js.Value = ...
var innerDiv js.Value = ...

outerDiv.Call(""addEventListener"", ""click"", js.FuncOf(func(this js.Value, args []js.Value) interface{} {
		log.Println(""listener called: "", this, this.Get(""id""))
		return nil
	}), once)
[...]
innerDiv.Call(""addEventListener"", ""click"", js.FuncOf(func(this js.Value, args []js.Value) interface{} {
                 args[0].Call(""stopPropagation"")
		log.Println(""listener called: "", this, this.Get(""id""))
		return nil
	}), once)
```




### What did you expect to see?
Naturally I expected that the listener to the inner div should always be called first. However looking at  the documentation of js.FuncOf, I don't know what to expect:

> Invoking the JavaScript function will synchronously call the Go function fn with the value of JavaScript's ""this"" keyword and the arguments of the invocation.
> [...]
> A wrapped function triggered by JavaScript's event loop gets executed on an extra goroutine.
> Blocking operations in the wrapped function will block the event loop.
>[...]
>A blocking function should therefore explicitly start a new goroutine.

The logic of these statements is contradictory: 
* What exactly is meant by a  ""synchronous call"" in the first statement?
* If a wrapped and triggered function is always executed in a goroutine, why should it block the event loop?

### What did you see instead?
I tried to use `stopPropagation` but the calling order is always wrong (outer-div first), independent of registration order. Also if a callback is always executed within a new goroutine, it sounds like `stopPropagation` et. al cannot be used properly. 

The documentation of js.FuncOf does not help me much to understand the actual calling behavior or at least if this works as ""expected"".
",1,syscall js  unclear behavior of js triggered and wrapped functions            what version of go are you using   go version          go version     darwin             does this issue reproduce with the latest release   yes          what operating system and processor architecture are you using   go env          go env  output     go env     on   goarch      gobin     gocache   users tschinke library caches go build   goenv   users tschinke library application support go env   goexe     goflags     gohostarch      gohostos  darwin   gonoproxy     gonosumdb     goos  darwin   gopath   users tschinke go   goprivate     goproxy  direct   goroot   usr local go   gosumdb  sum golang org   gotmpdir     gotooldir   usr local go pkg tool darwin     gccgo  gccgo   ar  ar   cc  clang   cxx  clang     cgo enabled      gomod   users tschinke repos wdy ausbildung trainiety app go mod   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders bv   t go    tmp go build  gno record gcc switches  fno common                 what did you do                          var outerdiv js value        var innerdiv js value          outerdiv call  addeventlistener    click   js funcof func this js value  args  js value  interface      		log println  listener called     this  this get  id     		return nil  	    once      innerdiv call  addeventlistener    click   js funcof func this js value  args  js value  interface                       args  call  stoppropagation    		log println  listener called     this  this get  id     		return nil  	    once                    what did you expect to see   naturally i expected that the listener to the inner div should always be called first  however looking at  the documentation of js funcof  i don t know what to expect       invoking the javascript function will synchronously call the go function fn with the value of javascript s  this  keyword and the arguments of the invocation          a wrapped function triggered by javascript s event loop gets executed on an extra goroutine     blocking operations in the wrapped function will block the event loop        a blocking function should therefore explicitly start a new goroutine     the logic of these statements is contradictory      what exactly is meant by a   synchronous call  in the first statement     if a wrapped and triggered function is always executed in a goroutine  why should it block the event loop         what did you see instead   i tried to use  stoppropagation  but the calling order is always wrong  outer div first   independent of registration order  also if a callback is always executed within a new goroutine  it sounds like  stoppropagation  et  al cannot be used properly      the documentation of js funcof does not help me much to understand the actual calling behavior or at least if this works as  expected    ,1
32412,6060684286.0,IssuesEvent,2017-06-14 02:55:18,golang/go,https://api.github.com/repos/golang/go,closed,path: make path/filepath suggestion more visible,Documentation NeedsFix,"Forking from https://github.com/golang/go/issues/18581#issuecomment-294511925, it is not clear that `path/filepath` needs to be used for operating system path manipulation and path is only for slash-separated. Make it easier for users to see the `path/filepath` suggestion.",1.0,"path: make path/filepath suggestion more visible - Forking from https://github.com/golang/go/issues/18581#issuecomment-294511925, it is not clear that `path/filepath` needs to be used for operating system path manipulation and path is only for slash-separated. Make it easier for users to see the `path/filepath` suggestion.",1,path  make path filepath suggestion more visible   forking from   it is not clear that  path filepath  needs to be used for operating system path manipulation and path is only for slash separated  make it easier for users to see the  path filepath  suggestion ,1
43468,7047463876.0,IssuesEvent,2018-01-02 13:40:17,golang/go,https://api.github.com/repos/golang/go,closed,reflect: Is reflect.Type guaranteed to be hashable?,Documentation,"<pre>I want to construct a cache of properties computed from a reflect.Type.
(For an example application, see <a href=""http://play.golang.org/p/csLP1bBXJV)"">http://play.golang.org/p/csLP1bBXJV)</a>

The natural representation for that is map[reflect.Type]properties, but the correctness
of that approach depends on the implementation details of reflect.Type.

The documentation for (reflect.Type).String() says, &quot;To test for equality, compare
the Types directly.&quot;  So that gives me some indication that what I'm trying to do
is reasonable.  However, nothing in the package tells me whether I can rely on the fact
that a reflect.Type is hashable.  (In practice, it currently is.)


The other alternatives I've considered are:

    map[struct{ pkgPath, name string }]properties - fails for unnamed types.

    map[uintptr]properties using reflect.Value.UnsafeAddr(t) - seems much worse than relying on hashability.

    map[uintptr]struct{reflect.Type, properties} using a hand-rolled hash function - very, very messy.


Since reflect.Type is hashable in practice anyway, the simplest solution would be to
document that that must be the case.

Obviously that has some drawbacks - it prevents reflect.Type from ever acquiring a
non-hashable field - but that still seems preferable to adding some kind of user-side
hashing or a new method for retrieving a unique ID.

On the other hand, if reflect.Type is not hashable, it would be good to document the
preferred workaround for constructing maps with Types as keys.</pre>
",1.0,"reflect: Is reflect.Type guaranteed to be hashable? - <pre>I want to construct a cache of properties computed from a reflect.Type.
(For an example application, see <a href=""http://play.golang.org/p/csLP1bBXJV)"">http://play.golang.org/p/csLP1bBXJV)</a>

The natural representation for that is map[reflect.Type]properties, but the correctness
of that approach depends on the implementation details of reflect.Type.

The documentation for (reflect.Type).String() says, &quot;To test for equality, compare
the Types directly.&quot;  So that gives me some indication that what I'm trying to do
is reasonable.  However, nothing in the package tells me whether I can rely on the fact
that a reflect.Type is hashable.  (In practice, it currently is.)


The other alternatives I've considered are:

    map[struct{ pkgPath, name string }]properties - fails for unnamed types.

    map[uintptr]properties using reflect.Value.UnsafeAddr(t) - seems much worse than relying on hashability.

    map[uintptr]struct{reflect.Type, properties} using a hand-rolled hash function - very, very messy.


Since reflect.Type is hashable in practice anyway, the simplest solution would be to
document that that must be the case.

Obviously that has some drawbacks - it prevents reflect.Type from ever acquiring a
non-hashable field - but that still seems preferable to adding some kind of user-side
hashing or a new method for retrieving a unique ID.

On the other hand, if reflect.Type is not hashable, it would be good to document the
preferred workaround for constructing maps with Types as keys.</pre>
",1,reflect  is reflect type guaranteed to be hashable     i want to construct a cache of properties computed from a reflect type   for an example application  see  a href     the natural representation for that is map properties  but the correctness of that approach depends on the implementation details of reflect type   the documentation for  reflect type  string   says   quot to test for equality  compare the types directly  quot   so that gives me some indication that what i m trying to do is reasonable   however  nothing in the package tells me whether i can rely on the fact that a reflect type is hashable    in practice  it currently is     the other alternatives i ve considered are       map properties   fails for unnamed types       map properties using reflect value unsafeaddr t    seems much worse than relying on hashability       map struct reflect type  properties  using a hand rolled hash function   very  very messy    since reflect type is hashable in practice anyway  the simplest solution would be to document that that must be the case   obviously that has some drawbacks   it prevents reflect type from ever acquiring a non hashable field   but that still seems preferable to adding some kind of user side hashing or a new method for retrieving a unique id   on the other hand  if reflect type is not hashable  it would be good to document the preferred workaround for constructing maps with types as keys   ,1
85274,24552967724.0,IssuesEvent,2022-10-12 13:55:07,gchq/sleeper,https://api.github.com/repos/gchq/sleeper,opened,Hitting rate limits in GitHub Actions,bug build-pipeline,"Here are some builds that failed because we hit a rate limit:

https://github.com/gchq/sleeper/actions/runs/3235165786/jobs/5299217395
https://github.com/gchq/sleeper/actions/runs/3235165799/jobs/5299217705
https://github.com/gchq/sleeper/actions/runs/3235165823/jobs/5299217643",1.0,"Hitting rate limits in GitHub Actions - Here are some builds that failed because we hit a rate limit:

https://github.com/gchq/sleeper/actions/runs/3235165786/jobs/5299217395
https://github.com/gchq/sleeper/actions/runs/3235165799/jobs/5299217705
https://github.com/gchq/sleeper/actions/runs/3235165823/jobs/5299217643",0,hitting rate limits in github actions   here are some builds that failed because we hit a rate limit            ,0
35128,6415848860.0,IssuesEvent,2017-08-08 13:41:39,golang/go,https://api.github.com/repos/golang/go,closed,wiki: apt-get install golang-1.8-go: did not work,Documentation,"### What operating system and processor architecture are you using (`go env`)?
ubuntu 16.x

### What did you do?

provision vagrant box to run some go app,

```
$provision = <<SCRIPT
sudo apt-get -qq update
sudo apt-get install -y libleptonica-dev libtesseract-dev tesseract-ocr imagemagick

sudo add-apt-repository -y ppa:longsleep/golang-backports
sudo apt-get update -y
sudo apt-get install -y golang-1.8-go

go version
go env

go get github.com/otiai10/ocrserver/...
SCRIPT

Vagrant.configure(""2"") do |config|

  config.vm.box = ""ubuntu/xenial64""
  config.vm.box_version = ""20170803.0.0""
  config.vm.synced_folder ""."", ""/home/ubuntu/go/src/github.com/otiai10/ocrserver""
  config.vm.provision :shell, inline: $script
  config.vm.network ""forwarded_port"", guest: 8080, host: 8090
end
```

then i ran this bunch of commands,

```sh
// .. end of provisioning output with sudo apt-get install -y golang-go
==> default: Setting up golang-1.8-src (1.8.3-2ubuntu1~longsleep1-xenial) ...
==> default: Setting up golang-1.8-go (1.8.3-2ubuntu1~longsleep1-xenial) ...
==> default: Setting up libalgorithm-diff-perl (1.19.03-1) ...
==> default: Setting up libalgorithm-diff-xs-perl (0.04-4build1) ...
==> default: Setting up libalgorithm-merge-perl (0.08-3) ...
==> default: Setting up libfile-fcntllock-perl (0.22-3) ...
==> default: Setting up pkg-config (0.29.1-0ubuntu1) ...
==> default: Setting up golang-1.8-race-detector-runtime (0.0+svn285455~ubuntu16.04.2~ppa1) ...

** ==> default: /tmp/vagrant-shell: line 10: go: command not found **
** ==> default: /tmp/vagrant-shell: line 11: go: command not found **
** ==> default: /tmp/vagrant-shell: line 13: go: command not found **

The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

[mh-cbon@pc4 ocrserver] $ vagrant ssh -c ""go env""
bash: go: command not found
Connection to 127.0.0.1 closed.

[mh-cbon@pc4 ocrserver] $ vagrant ssh -c ""go1.8""
bash: go1.8: command not found
Connection to 127.0.0.1 closed.

[mh-cbon@pc4 ocrserver] $ vagrant ssh -c ""go18""
bash: go18: command not found
Connection to 127.0.0.1 closed.

[mh-cbon@pc4 ocrserver] $ vagrant ssh -c ""go""
bash: go: command not found
Connection to 127.0.0.1 closed.

[mh-cbon@pc4 ocrserver] $ vagrant ssh -c ""sudo apt-get install -y golang-1.8-go""
Reading package lists... Done
Building dependency tree       
Reading state information... Done
golang-1.8-go is already the newest version (1.8.3-2ubuntu1~longsleep1-xenial).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Connection to 127.0.0.1 closed.

[mh-cbon@pc4 ocrserver] $ vagrant ssh -c ""go""
bash: go: command not found
Connection to 127.0.0.1 closed.

[mh-cbon@pc4 ocrserver] $ vagrant ssh -c ""sudo apt-get install -y golang-go""
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  golang-race-detector-runtime golang-src
The following NEW packages will be installed:
  golang-go golang-race-detector-runtime golang-src
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 30.0 kB of archives.
After this operation, 72.7 kB of additional disk space will be used.
Get:1 http://ppa.launchpad.net/longsleep/golang-backports/ubuntu xenial/main amd64 golang-src amd64 2:1.8~1ubuntu2~xenial [3,684 B]
Get:2 http://ppa.launchpad.net/longsleep/golang-backports/ubuntu xenial/main amd64 golang-go amd64 2:1.8~1ubuntu2~xenial [22.9 kB]
Get:3 http://ppa.launchpad.net/longsleep/golang-backports/ubuntu xenial/main amd64 golang-race-detector-runtime amd64 2:1.8~1ubuntu2~xenial [3,480 B]
Fetched 30.0 kB in 1s (20.8 kB/s)                  
Selecting previously unselected package golang-src.
(Reading database ... 68642 files and directories currently installed.)
Preparing to unpack .../golang-src_2%3a1.8~1ubuntu2~xenial_amd64.deb ...
Unpacking golang-src (2:1.8~1ubuntu2~xenial) ...
Selecting previously unselected package golang-go.
Preparing to unpack .../golang-go_2%3a1.8~1ubuntu2~xenial_amd64.deb ...
Unpacking golang-go (2:1.8~1ubuntu2~xenial) ...
Selecting previously unselected package golang-race-detector-runtime.
Preparing to unpack .../golang-race-detector-runtime_2%3a1.8~1ubuntu2~xenial_amd64.deb ...
Unpacking golang-race-detector-runtime (2:1.8~1ubuntu2~xenial) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up golang-src (2:1.8~1ubuntu2~xenial) ...
Setting up golang-go (2:1.8~1ubuntu2~xenial) ...
Setting up golang-race-detector-runtime (2:1.8~1ubuntu2~xenial) ...
Connection to 127.0.0.1 closed.

[mh-cbon@pc4 ocrserver] $ vagrant ssh -c ""go env""
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/ubuntu/go""
GORACE=""""
GOROOT=""/usr/lib/go-1.8""
GOTOOLDIR=""/usr/lib/go-1.8/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build747827949=/tmp/go-build -gno-record-gcc-switches""
CXX=""g++""
CGO_ENABLED=""1""
PKG_CONFIG=""pkg-config""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
Connection to 127.0.0.1 closed.
[mh-cbon@pc4 ocrserver] $ 
```


### What did you expect to see?

The commands provided in the wiki page at https://github.com/golang/go/wiki/Ubuntu just works out of the box without confusion.

### What did you see instead?

needed to fix tings.
",1.0,"wiki: apt-get install golang-1.8-go: did not work - ### What operating system and processor architecture are you using (`go env`)?
ubuntu 16.x

### What did you do?

provision vagrant box to run some go app,

```
$provision = <<SCRIPT
sudo apt-get -qq update
sudo apt-get install -y libleptonica-dev libtesseract-dev tesseract-ocr imagemagick

sudo add-apt-repository -y ppa:longsleep/golang-backports
sudo apt-get update -y
sudo apt-get install -y golang-1.8-go

go version
go env

go get github.com/otiai10/ocrserver/...
SCRIPT

Vagrant.configure(""2"") do |config|

  config.vm.box = ""ubuntu/xenial64""
  config.vm.box_version = ""20170803.0.0""
  config.vm.synced_folder ""."", ""/home/ubuntu/go/src/github.com/otiai10/ocrserver""
  config.vm.provision :shell, inline: $script
  config.vm.network ""forwarded_port"", guest: 8080, host: 8090
end
```

then i ran this bunch of commands,

```sh
// .. end of provisioning output with sudo apt-get install -y golang-go
==> default: Setting up golang-1.8-src (1.8.3-2ubuntu1~longsleep1-xenial) ...
==> default: Setting up golang-1.8-go (1.8.3-2ubuntu1~longsleep1-xenial) ...
==> default: Setting up libalgorithm-diff-perl (1.19.03-1) ...
==> default: Setting up libalgorithm-diff-xs-perl (0.04-4build1) ...
==> default: Setting up libalgorithm-merge-perl (0.08-3) ...
==> default: Setting up libfile-fcntllock-perl (0.22-3) ...
==> default: Setting up pkg-config (0.29.1-0ubuntu1) ...
==> default: Setting up golang-1.8-race-detector-runtime (0.0+svn285455~ubuntu16.04.2~ppa1) ...

** ==> default: /tmp/vagrant-shell: line 10: go: command not found **
** ==> default: /tmp/vagrant-shell: line 11: go: command not found **
** ==> default: /tmp/vagrant-shell: line 13: go: command not found **

The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

[mh-cbon@pc4 ocrserver] $ vagrant ssh -c ""go env""
bash: go: command not found
Connection to 127.0.0.1 closed.

[mh-cbon@pc4 ocrserver] $ vagrant ssh -c ""go1.8""
bash: go1.8: command not found
Connection to 127.0.0.1 closed.

[mh-cbon@pc4 ocrserver] $ vagrant ssh -c ""go18""
bash: go18: command not found
Connection to 127.0.0.1 closed.

[mh-cbon@pc4 ocrserver] $ vagrant ssh -c ""go""
bash: go: command not found
Connection to 127.0.0.1 closed.

[mh-cbon@pc4 ocrserver] $ vagrant ssh -c ""sudo apt-get install -y golang-1.8-go""
Reading package lists... Done
Building dependency tree       
Reading state information... Done
golang-1.8-go is already the newest version (1.8.3-2ubuntu1~longsleep1-xenial).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Connection to 127.0.0.1 closed.

[mh-cbon@pc4 ocrserver] $ vagrant ssh -c ""go""
bash: go: command not found
Connection to 127.0.0.1 closed.

[mh-cbon@pc4 ocrserver] $ vagrant ssh -c ""sudo apt-get install -y golang-go""
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  golang-race-detector-runtime golang-src
The following NEW packages will be installed:
  golang-go golang-race-detector-runtime golang-src
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 30.0 kB of archives.
After this operation, 72.7 kB of additional disk space will be used.
Get:1 http://ppa.launchpad.net/longsleep/golang-backports/ubuntu xenial/main amd64 golang-src amd64 2:1.8~1ubuntu2~xenial [3,684 B]
Get:2 http://ppa.launchpad.net/longsleep/golang-backports/ubuntu xenial/main amd64 golang-go amd64 2:1.8~1ubuntu2~xenial [22.9 kB]
Get:3 http://ppa.launchpad.net/longsleep/golang-backports/ubuntu xenial/main amd64 golang-race-detector-runtime amd64 2:1.8~1ubuntu2~xenial [3,480 B]
Fetched 30.0 kB in 1s (20.8 kB/s)                  
Selecting previously unselected package golang-src.
(Reading database ... 68642 files and directories currently installed.)
Preparing to unpack .../golang-src_2%3a1.8~1ubuntu2~xenial_amd64.deb ...
Unpacking golang-src (2:1.8~1ubuntu2~xenial) ...
Selecting previously unselected package golang-go.
Preparing to unpack .../golang-go_2%3a1.8~1ubuntu2~xenial_amd64.deb ...
Unpacking golang-go (2:1.8~1ubuntu2~xenial) ...
Selecting previously unselected package golang-race-detector-runtime.
Preparing to unpack .../golang-race-detector-runtime_2%3a1.8~1ubuntu2~xenial_amd64.deb ...
Unpacking golang-race-detector-runtime (2:1.8~1ubuntu2~xenial) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up golang-src (2:1.8~1ubuntu2~xenial) ...
Setting up golang-go (2:1.8~1ubuntu2~xenial) ...
Setting up golang-race-detector-runtime (2:1.8~1ubuntu2~xenial) ...
Connection to 127.0.0.1 closed.

[mh-cbon@pc4 ocrserver] $ vagrant ssh -c ""go env""
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/ubuntu/go""
GORACE=""""
GOROOT=""/usr/lib/go-1.8""
GOTOOLDIR=""/usr/lib/go-1.8/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build747827949=/tmp/go-build -gno-record-gcc-switches""
CXX=""g++""
CGO_ENABLED=""1""
PKG_CONFIG=""pkg-config""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
Connection to 127.0.0.1 closed.
[mh-cbon@pc4 ocrserver] $ 
```


### What did you expect to see?

The commands provided in the wiki page at https://github.com/golang/go/wiki/Ubuntu just works out of the box without confusion.

### What did you see instead?

needed to fix tings.
",1,wiki  apt get install golang     go  did not work       what operating system and processor architecture are you using   go env     ubuntu   x        what did you do     provision vagrant box to run some go app           provision     script  sudo apt get  qq update  sudo apt get install  y libleptonica dev libtesseract dev tesseract ocr imagemagick    sudo add apt repository  y ppa longsleep golang backports  sudo apt get update  y  sudo apt get install  y golang     go    go version  go env    go get github com   ocrserver      script    vagrant configure      do  config       config vm box    ubuntu       config vm box version              config vm synced folder        home ubuntu go src github com   ocrserver     config vm provision  shell  inline   script    config vm network  forwarded port   guest     host     end         then i ran this bunch of commands        sh        end of provisioning output with sudo apt get install  y golang go      default  setting up golang     src            xenial           default  setting up golang     go            xenial           default  setting up libalgorithm diff perl                    default  setting up libalgorithm diff xs perl                  default  setting up libalgorithm merge perl                  default  setting up libfile fcntllock perl                  default  setting up pkg config                    default  setting up golang     race detector runtime                               default   tmp vagrant shell  line    go  command not found            default   tmp vagrant shell  line    go  command not found            default   tmp vagrant shell  line    go  command not found       the ssh command responded with a non zero exit status  vagrant  assumes that this means the command failed  the output for this command  should be in the log above  please read the output to determine what  went wrong         vagrant ssh  c  go env   bash  go  command not found  connection to         closed         vagrant ssh  c        bash       command not found  connection to         closed         vagrant ssh  c      bash     command not found  connection to         closed         vagrant ssh  c  go   bash  go  command not found  connection to         closed         vagrant ssh  c  sudo apt get install  y golang     go   reading package lists    done  building dependency tree         reading state information    done  golang     go is already the newest version            xenial      upgraded    newly installed    to remove and   not upgraded   connection to         closed         vagrant ssh  c  go   bash  go  command not found  connection to         closed         vagrant ssh  c  sudo apt get install  y golang go   reading package lists    done  building dependency tree         reading state information    done  the following additional packages will be installed     golang race detector runtime golang src  the following new packages will be installed     golang go golang race detector runtime golang src    upgraded    newly installed    to remove and   not upgraded   need to get     kb of archives   after this operation      kb of additional disk space will be used   get     xenial main   golang src           xenial    get     xenial main   golang go           xenial    get     xenial main   golang race detector runtime           xenial    fetched     kb in        kb s                     selecting previously unselected package golang src    reading database       files and directories currently installed    preparing to unpack     golang src         xenial   deb      unpacking golang src          xenial       selecting previously unselected package golang go   preparing to unpack     golang go         xenial   deb      unpacking golang go          xenial       selecting previously unselected package golang race detector runtime   preparing to unpack     golang race detector runtime         xenial   deb      unpacking golang race detector runtime          xenial       processing triggers for man db                setting up golang src          xenial       setting up golang go          xenial       setting up golang race detector runtime          xenial       connection to         closed         vagrant ssh  c  go env   goarch      gobin     goexe     gohostarch      gohostos  linux   goos  linux   gopath   home ubuntu go   gorace     goroot   usr lib go       gotooldir   usr lib go     pkg tool linux     gccgo  gccgo   cc  gcc   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches   cxx  g     cgo enabled      pkg config  pkg config   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      connection to         closed                      what did you expect to see     the commands provided in the wiki page at   just works out of the box without confusion         what did you see instead     needed to fix tings   ,1
93686,10773251761.0,IssuesEvent,2019-11-02 19:31:02,golang/go,https://api.github.com/repos/golang/go,closed,"doc: outdated assessment of ARCHs maturity in ""Installing Go from source"" list",Documentation NeedsFix,"The [Installing Go from source](https://golang.org/doc/install/source) document contains, in the [introduction section](https://golang.org/doc/install/source#introduction), a list of supported architectures. It says:

> The Go compilers support nine instruction sets. There are important differences in the quality of the compilers for the different architectures. 

The assessment of the various ports' ""maturity grade"" is outdated and somewhat misleading. A few issues:

- s390x is listed as ""new"" and ""not as well exercised as other ports.""; but in reality is probably one of the ports that receive the most attention.
- the arm64 port is mature, but it is listed as ""not as well exercised as other ports""; it also says ""New in 1.5"", it seems unnecessary to note the newness of something that is 4 years old.
- for 386 it says ""Comparable to the amd64 port"" (which is the most mature one), but in reality 386 is probably much less exercised than ports like arm / arm64 / s390x.
- In general, the point of the list is not to present a chronological history of new ports, but to help the reader assess the newness and maturity of the archs. For this reason, mentioning that mips64 is ""New in 1.6"" is not useful (at this point, anything introduced in 1.6 is quite old). 

I suggest we update the list to reflect the current status of the various ports. I'll send a CL.",1.0,"doc: outdated assessment of ARCHs maturity in ""Installing Go from source"" list - The [Installing Go from source](https://golang.org/doc/install/source) document contains, in the [introduction section](https://golang.org/doc/install/source#introduction), a list of supported architectures. It says:

> The Go compilers support nine instruction sets. There are important differences in the quality of the compilers for the different architectures. 

The assessment of the various ports' ""maturity grade"" is outdated and somewhat misleading. A few issues:

- s390x is listed as ""new"" and ""not as well exercised as other ports.""; but in reality is probably one of the ports that receive the most attention.
- the arm64 port is mature, but it is listed as ""not as well exercised as other ports""; it also says ""New in 1.5"", it seems unnecessary to note the newness of something that is 4 years old.
- for 386 it says ""Comparable to the amd64 port"" (which is the most mature one), but in reality 386 is probably much less exercised than ports like arm / arm64 / s390x.
- In general, the point of the list is not to present a chronological history of new ports, but to help the reader assess the newness and maturity of the archs. For this reason, mentioning that mips64 is ""New in 1.6"" is not useful (at this point, anything introduced in 1.6 is quite old). 

I suggest we update the list to reflect the current status of the various ports. I'll send a CL.",1,doc  outdated assessment of archs maturity in  installing go from source  list   the     document contains  in the     a list of supported architectures  it says       the go compilers support nine instruction sets  there are important differences in the quality of the compilers for the different architectures      the assessment of the various ports   maturity grade  is outdated and somewhat misleading  a few issues         is listed as  new  and  not as well exercised as other ports    but in reality is probably one of the ports that receive the most attention     the   port is mature  but it is listed as  not as well exercised as other ports   it also says  new in       it seems unnecessary to note the newness of something that is   years old     for   it says  comparable to the   port   which is the most mature one   but in reality   is probably much less exercised than ports like arm             in general  the point of the list is not to present a chronological history of new ports  but to help the reader assess the newness and maturity of the archs  for this reason  mentioning that   is  new in      is not useful  at this point  anything introduced in     is quite old       i suggest we update the list to reflect the current status of the various ports  i ll send a cl ,1
6531,3028401317.0,IssuesEvent,2015-08-04 04:50:19,golang/go,https://api.github.com/repos/golang/go,closed,"doc: for -buildmode=c-shared, document that //export requires import ""C""",Documentation,"This may just be a misunderstanding of how this is supposed to work - if so I'd appreciate some guidance.

*What version of Go are you using (go version)?*
`go version go1.5beta3 darwin/amd64`

*What operating system and processor architecture are you using?*
`Mac OS X 10.10.4 Intel Core i7`

*What did you do?*
I'm trying to build a C archive to link to a C++ app.  I read the release notes and the **Go Execution Modes** doc.  The second document states:

> The only callable symbols will be those functions marked as exported (by any package), as described in the cgo documentation.

I wrote a small test:
```go
package main

import ""log""

//export Foo
func Foo() {
	log.Println(""Foo"")
}

func main() {
	// unused
}
```

`go build -buildmode=c-archive`

*What did you expect to see?*

I expected it to create **foo.a** and a header file with *Foo* exported.

*What did you see instead?*

It generated **foo.a**, but no header file.

*nm* also doesn't show my function being exported:

```
$ nm -g foo.a

foo.a(000000.o):
                 U ___stack_chk_fail
                 U ___stack_chk_guard
                 U ___stderrp
00000000000001f0 T __cgo_sys_thread_start
0000000000000360 T __cgo_wait_runtime_init_done
                 U _abort
00000000000004e1 T _crosscall_amd64
                 U _fprintf
                 U _fputc
                 U _free
                 U _fwrite
                 U _malloc
                 U _pthread_attr_destroy
                 U _pthread_attr_getstacksize
                 U _pthread_attr_init
                 U _pthread_cond_broadcast
                 U _pthread_cond_wait
                 U _pthread_create
                 U _pthread_key_create
                 U _pthread_key_delete
                 U _pthread_mutex_lock
                 U _pthread_mutex_unlock
                 U _pthread_setspecific
                 U _pthread_sigmask
                 U _setenv
                 U _strerror
                 U _unsetenv
0000000000000470 T _x_cgo_free
0000000000000000 T _x_cgo_init
0000000000000430 T _x_cgo_malloc
00000000000003c0 T _x_cgo_notify_runtime_init_done
0000000000000400 T _x_cgo_setenv
0000000000000300 T _x_cgo_sys_thread_create
0000000000000480 T _x_cgo_thread_start
0000000000000420 T _x_cgo_unsetenv

foo.a(go.o):
00000000000b49f0 T __cgo_panic
0000000000054fe0 T __cgo_topofstack
00000000000b4a20 T _crosscall2
                 U _x_cgo_free
                 U _x_cgo_init
                 U _x_cgo_malloc
                 U _x_cgo_notify_runtime_init_done
                 U _x_cgo_setenv
                 U _x_cgo_sys_thread_create
                 U _x_cgo_thread_start
                 U _x_cgo_unsetenv
```",1.0,"doc: for -buildmode=c-shared, document that //export requires import ""C"" - This may just be a misunderstanding of how this is supposed to work - if so I'd appreciate some guidance.

*What version of Go are you using (go version)?*
`go version go1.5beta3 darwin/amd64`

*What operating system and processor architecture are you using?*
`Mac OS X 10.10.4 Intel Core i7`

*What did you do?*
I'm trying to build a C archive to link to a C++ app.  I read the release notes and the **Go Execution Modes** doc.  The second document states:

> The only callable symbols will be those functions marked as exported (by any package), as described in the cgo documentation.

I wrote a small test:
```go
package main

import ""log""

//export Foo
func Foo() {
	log.Println(""Foo"")
}

func main() {
	// unused
}
```

`go build -buildmode=c-archive`

*What did you expect to see?*

I expected it to create **foo.a** and a header file with *Foo* exported.

*What did you see instead?*

It generated **foo.a**, but no header file.

*nm* also doesn't show my function being exported:

```
$ nm -g foo.a

foo.a(000000.o):
                 U ___stack_chk_fail
                 U ___stack_chk_guard
                 U ___stderrp
00000000000001f0 T __cgo_sys_thread_start
0000000000000360 T __cgo_wait_runtime_init_done
                 U _abort
00000000000004e1 T _crosscall_amd64
                 U _fprintf
                 U _fputc
                 U _free
                 U _fwrite
                 U _malloc
                 U _pthread_attr_destroy
                 U _pthread_attr_getstacksize
                 U _pthread_attr_init
                 U _pthread_cond_broadcast
                 U _pthread_cond_wait
                 U _pthread_create
                 U _pthread_key_create
                 U _pthread_key_delete
                 U _pthread_mutex_lock
                 U _pthread_mutex_unlock
                 U _pthread_setspecific
                 U _pthread_sigmask
                 U _setenv
                 U _strerror
                 U _unsetenv
0000000000000470 T _x_cgo_free
0000000000000000 T _x_cgo_init
0000000000000430 T _x_cgo_malloc
00000000000003c0 T _x_cgo_notify_runtime_init_done
0000000000000400 T _x_cgo_setenv
0000000000000300 T _x_cgo_sys_thread_create
0000000000000480 T _x_cgo_thread_start
0000000000000420 T _x_cgo_unsetenv

foo.a(go.o):
00000000000b49f0 T __cgo_panic
0000000000054fe0 T __cgo_topofstack
00000000000b4a20 T _crosscall2
                 U _x_cgo_free
                 U _x_cgo_init
                 U _x_cgo_malloc
                 U _x_cgo_notify_runtime_init_done
                 U _x_cgo_setenv
                 U _x_cgo_sys_thread_create
                 U _x_cgo_thread_start
                 U _x_cgo_unsetenv
```",1,doc  for  buildmode c shared  document that   export requires import  c    this may just be a misunderstanding of how this is supposed to work   if so i d appreciate some guidance      what version of go are you using  go version      go version     darwin        what operating system and processor architecture are you using     mac os x       intel core        what did you do    i m trying to build a c archive to link to a c   app   i read the release notes and the   go execution modes   doc   the second document states       the only callable symbols will be those functions marked as exported  by any package   as described in the cgo documentation     i wrote a small test      go  package main    import  log       export foo  func foo      	log println  foo         func main      	   unused             go build  buildmode c archive      what did you expect to see      i expected it to create   foo a   and a header file with  foo  exported      what did you see instead      it generated   foo a    but no header file      nm  also doesn t show my function being exported            nm  g foo a    foo a   o                     u    stack chk fail                   u    stack chk guard                   u    stderrp    t   cgo sys thread start    t   cgo wait runtime init done                   u  abort    t  crosscall                     u  fprintf                   u  fputc                   u  free                   u  fwrite                   u  malloc                   u  pthread attr destroy                   u  pthread attr getstacksize                   u  pthread attr init                   u  pthread cond broadcast                   u  pthread cond wait                   u  pthread create                   u  pthread key create                   u  pthread key delete                   u  pthread mutex lock                   u  pthread mutex unlock                   u  pthread setspecific                   u  pthread sigmask                   u  setenv                   u  strerror                   u  unsetenv    t  x cgo free    t  x cgo init    t  x cgo malloc    t  x cgo notify runtime init done    t  x cgo setenv    t  x cgo sys thread create    t  x cgo thread start    t  x cgo unsetenv    foo a go o      t   cgo panic    t   cgo topofstack    t                      u  x cgo free                   u  x cgo init                   u  x cgo malloc                   u  x cgo notify runtime init done                   u  x cgo setenv                   u  x cgo sys thread create                   u  x cgo thread start                   u  x cgo unsetenv     ,1
353941,25142855577.0,IssuesEvent,2022-11-10 01:12:42,golang/go,https://api.github.com/repos/golang/go,opened,spec: `append` doesn't specify zero values when growing underlying array,Documentation,"When `append` is called on a slice and the underlying array is not large enough, a new underlying array is allocated, possibly increasing the slice's capacity significantly (typically doubling it). The spec doesn't specify the value of any slice elements past the slice length and up to the capacity.",1.0,"spec: `append` doesn't specify zero values when growing underlying array - When `append` is called on a slice and the underlying array is not large enough, a new underlying array is allocated, possibly increasing the slice's capacity significantly (typically doubling it). The spec doesn't specify the value of any slice elements past the slice length and up to the capacity.",1,spec   append  doesn t specify zero values when growing underlying array   when  append  is called on a slice and the underlying array is not large enough  a new underlying array is allocated  possibly increasing the slice s capacity significantly  typically doubling it   the spec doesn t specify the value of any slice elements past the slice length and up to the capacity ,1
151629,13428050122.0,IssuesEvent,2020-09-06 20:24:28,golang/go,https://api.github.com/repos/golang/go,closed,go/ast: mention strconv.Unquote in BasicLit documentation,Documentation NeedsFix,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14.4 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/tenntenn/Library/Caches/go-build""
GOENV=""/Users/tenntenn/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/tenntenn/Documents/gopath""
GOPRIVATE=""""
GOPROXY=""direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/wm/76fqhrc52ls25p4cmjrjbdqh0000gp/T/go-build969893907=/tmp/go-build -gno-record-gcc-switches -fno-common""

</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

https://golang.org/pkg/go/ast/#BasicLit

### What did you expect to see?

I propose improve the document of `ast.BasicLit`.

When `BasicLit.Kind` is `token.STRING`, we must call `strconv.Unquote` to get unquoted string value.

So I think the document of `ast.BasicLit` should refer to `strconv.Unquote`.

### What did you see instead?

https://golang.org/pkg/go/ast/#BasicLit",1.0,"go/ast: mention strconv.Unquote in BasicLit documentation - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14.4 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/tenntenn/Library/Caches/go-build""
GOENV=""/Users/tenntenn/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/tenntenn/Documents/gopath""
GOPRIVATE=""""
GOPROXY=""direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/wm/76fqhrc52ls25p4cmjrjbdqh0000gp/T/go-build969893907=/tmp/go-build -gno-record-gcc-switches -fno-common""

</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

https://golang.org/pkg/go/ast/#BasicLit

### What did you expect to see?

I propose improve the document of `ast.BasicLit`.

When `BasicLit.Kind` is `token.STRING`, we must call `strconv.Unquote` to get unquoted string value.

So I think the document of `ast.BasicLit` should refer to `strconv.Unquote`.

### What did you see instead?

https://golang.org/pkg/go/ast/#BasicLit",1,go ast  mention strconv unquote in basiclit documentation         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version            go version  go version       darwin             does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   users tenntenn library caches go build   goenv   users tenntenn library application support go env   goexe     goflags     gohostarch      gohostos  darwin   goinsecure     gonoproxy     gonosumdb     goos  darwin   gopath   users tenntenn documents gopath   goprivate     goproxy  direct   goroot   usr local go   gosumdb  sum golang org   gotmpdir     gotooldir   usr local go pkg tool darwin     gccgo  gccgo   ar  ar   cc  clang   cxx  clang     cgo enabled      gomod     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders wm   t go    tmp go build  gno record gcc switches  fno common               what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best                   what did you expect to see     i propose improve the document of  ast basiclit      when  basiclit kind  is  token string   we must call  strconv unquote  to get unquoted string value     so i think the document of  ast basiclit  should refer to  strconv unquote          what did you see instead      ,1
85963,24731426467.0,IssuesEvent,2022-10-20 17:56:31,elastic/elastic-agent-shipper,https://api.github.com/repos/elastic/elastic-agent-shipper,closed,Build 1 for 8.5 with status FAILURE,Team:Elastic-Agent-Data-Plane ci-reported automation build-failures,"
## :broken_heart: Build Failed


<!-- BUILD BADGES-->
> _the below badges are clickable and redirect to their specific view in the CI or DOCS_
[![Pipeline View](https://img.shields.io/badge/pipeline-pipeline%20-green)](https://fleet-ci.elastic.co/blue/organizations/jenkins/elastic-agent-shipper-mbp%2F8.5/detail/8.5/1//pipeline) [![Test View](https://img.shields.io/badge/test-test-green)](https://fleet-ci.elastic.co/blue/organizations/jenkins/elastic-agent-shipper-mbp%2F8.5/detail/8.5/1//tests) [![Changes](https://img.shields.io/badge/changes-changes-green)](https://fleet-ci.elastic.co/blue/organizations/jenkins/elastic-agent-shipper-mbp%2F8.5/detail/8.5/1//changes) [![Artifacts](https://img.shields.io/badge/artifacts-artifacts-yellow)](https://fleet-ci.elastic.co/blue/organizations/jenkins/elastic-agent-shipper-mbp%2F8.5/detail/8.5/1//artifacts) [![preview](https://img.shields.io/badge/docs-preview-yellowgreen)](http://elastic-agent-shipper_null.docs-preview.app.elstc.co/diff)  [![preview](https://img.shields.io/badge/elastic-observability-blue)](https://ci-stats.elastic.co/app/apm/services/fleet-ci/transactions/view?rangeFrom=2022-09-21T13:18:19.149Z&rangeTo=2022-09-21T13:38:19.149Z&transactionName=BUILD+elastic-agent-shipper-mbp%2F8.5&transactionType=job&latencyAggregationType=avg&traceId=aca5cb7eeba496be97dcb7bf530cb83b&transactionId=25c3087df1edab1b)

<!-- BUILD SUMMARY-->
<details><summary>Expand to view the summary</summary>
<p>

#### Build stats




* Start Time: 2022-09-21T13:28:19.149+0000


* Duration: 4 min 4 sec





</p>
</details>

<!-- TEST RESULTS IF ANY-->


<!-- STEPS ERRORS IF ANY -->














### Steps errors [![1](https://img.shields.io/badge/1%20-red)](https://fleet-ci.elastic.co/blue/organizations/jenkins/elastic-agent-shipper-mbp%2F8.5/detail/8.5/1//pipeline)
  <details><summary>Expand to view the steps failures</summary>
  <p>


  
  
  
  
##### `Git fetch`
<ul>
<li>Took 2 min 13 sec . View more details <a href=""https://fleet-ci.elastic.co//blue/rest/organizations/jenkins/pipelines/elastic-agent-shipper-mbp/pipelines/8.5/runs/1/steps/41/log/?start=0"">here</a></li>
<li>Description: <code>git fetch https://${GIT_USERNAME}:${GIT_PASSWORD}@github.com/elastic/elastic-agent-shipper.git +refs/pull/*/head:refs/remotes/origin/pr/* > .git/fetch.log 2>&1</code></l1>
</ul>
  
  </p>
  </details>


",1.0,"Build 1 for 8.5 with status FAILURE - 
## :broken_heart: Build Failed


<!-- BUILD BADGES-->
> _the below badges are clickable and redirect to their specific view in the CI or DOCS_
[![Pipeline View](https://img.shields.io/badge/pipeline-pipeline%20-green)](https://fleet-ci.elastic.co/blue/organizations/jenkins/elastic-agent-shipper-mbp%2F8.5/detail/8.5/1//pipeline) [![Test View](https://img.shields.io/badge/test-test-green)](https://fleet-ci.elastic.co/blue/organizations/jenkins/elastic-agent-shipper-mbp%2F8.5/detail/8.5/1//tests) [![Changes](https://img.shields.io/badge/changes-changes-green)](https://fleet-ci.elastic.co/blue/organizations/jenkins/elastic-agent-shipper-mbp%2F8.5/detail/8.5/1//changes) [![Artifacts](https://img.shields.io/badge/artifacts-artifacts-yellow)](https://fleet-ci.elastic.co/blue/organizations/jenkins/elastic-agent-shipper-mbp%2F8.5/detail/8.5/1//artifacts) [![preview](https://img.shields.io/badge/docs-preview-yellowgreen)](http://elastic-agent-shipper_null.docs-preview.app.elstc.co/diff)  [![preview](https://img.shields.io/badge/elastic-observability-blue)](https://ci-stats.elastic.co/app/apm/services/fleet-ci/transactions/view?rangeFrom=2022-09-21T13:18:19.149Z&rangeTo=2022-09-21T13:38:19.149Z&transactionName=BUILD+elastic-agent-shipper-mbp%2F8.5&transactionType=job&latencyAggregationType=avg&traceId=aca5cb7eeba496be97dcb7bf530cb83b&transactionId=25c3087df1edab1b)

<!-- BUILD SUMMARY-->
<details><summary>Expand to view the summary</summary>
<p>

#### Build stats




* Start Time: 2022-09-21T13:28:19.149+0000


* Duration: 4 min 4 sec





</p>
</details>

<!-- TEST RESULTS IF ANY-->


<!-- STEPS ERRORS IF ANY -->














### Steps errors [![1](https://img.shields.io/badge/1%20-red)](https://fleet-ci.elastic.co/blue/organizations/jenkins/elastic-agent-shipper-mbp%2F8.5/detail/8.5/1//pipeline)
  <details><summary>Expand to view the steps failures</summary>
  <p>


  
  
  
  
##### `Git fetch`
<ul>
<li>Took 2 min 13 sec . View more details <a href=""https://fleet-ci.elastic.co//blue/rest/organizations/jenkins/pipelines/elastic-agent-shipper-mbp/pipelines/8.5/runs/1/steps/41/log/?start=0"">here</a></li>
<li>Description: <code>git fetch https://${GIT_USERNAME}:${GIT_PASSWORD}@github.com/elastic/elastic-agent-shipper.git +refs/pull/*/head:refs/remotes/origin/pr/* > .git/fetch.log 2>&1</code></l1>
</ul>
  
  </p>
  </details>


",0,build   for     with status failure        broken heart  build failed        the below badges are clickable and redirect to their specific view in the ci or docs                                expand to view the summary          build stats       start time                    duration    min   sec                                   steps errors         expand to view the steps failures                           git fetch     took   min   sec   view more details  a href     description   git fetch    refs pull   head refs remotes origin pr      git fetch log                       ,0
61447,8519434360.0,IssuesEvent,2018-11-01 14:42:43,golang/go,https://api.github.com/repos/golang/go,closed,doc: contribute: sending a change gerrit: incorrect language,Documentation,"### What did you do and see?
https://golang.org/doc/contribute.html#sending_a_change_gerrit

There is a sentence:

> It's different but powerful and familiarity with help you understand the flow.

### What did you expect to see?

> It's different but powerful and familiarity with it will help you understand the flow.",1.0,"doc: contribute: sending a change gerrit: incorrect language - ### What did you do and see?
https://golang.org/doc/contribute.html#sending_a_change_gerrit

There is a sentence:

> It's different but powerful and familiarity with help you understand the flow.

### What did you expect to see?

> It's different but powerful and familiarity with it will help you understand the flow.",1,doc  contribute  sending a change gerrit  incorrect language       what did you do and see        there is a sentence       it s different but powerful and familiarity with help you understand the flow         what did you expect to see       it s different but powerful and familiarity with it will help you understand the flow ,1
376478,26202496780.0,IssuesEvent,2023-01-03 18:54:24,golang/go,https://api.github.com/repos/golang/go,closed,net/http: incorrect http.ResponseController usage example in Go 1.20 release notes,Documentation NeedsFix,"<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
go version go1.20rc1 darwin/arm64
</pre>

### What did you do?

Pasted a [HTTP ResponseController](https://tip.golang.org/doc/go1.20#http_responsecontroller) usage example from Go 1.20 release notes draft:

```go
package pkg

import (
	""io""
	""net/http""
	""strings""
)

func RequestHandler(w http.ResponseWriter, r *http.Request) {
	rc := http.NewResponseController(w)
	rc.SetWriteDeadline(0) // disable Server.WriteTimeout when sending a large response
	io.Copy(w, strings.NewReader(""hello""))
}
```

https://go.dev/play/p/F16HmEJ7NUU


### What did you expect to see?

No build errors.

### What did you see instead?

Incorrect [http.ResponseController.SetWriteDeadline](https://pkg.go.dev/net/http@master#ResponseController.SetWriteDeadline) call — it's called with an int constant, when this method expects time.Time type.

```
¶ go vet
# pkg
vet: ./pkg.go:11:22: cannot use 0 (untyped int constant) as time.Time value in argument to rc.SetWriteDeadline
```
",1.0,"net/http: incorrect http.ResponseController usage example in Go 1.20 release notes - <!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
go version go1.20rc1 darwin/arm64
</pre>

### What did you do?

Pasted a [HTTP ResponseController](https://tip.golang.org/doc/go1.20#http_responsecontroller) usage example from Go 1.20 release notes draft:

```go
package pkg

import (
	""io""
	""net/http""
	""strings""
)

func RequestHandler(w http.ResponseWriter, r *http.Request) {
	rc := http.NewResponseController(w)
	rc.SetWriteDeadline(0) // disable Server.WriteTimeout when sending a large response
	io.Copy(w, strings.NewReader(""hello""))
}
```

https://go.dev/play/p/F16HmEJ7NUU


### What did you expect to see?

No build errors.

### What did you see instead?

Incorrect [http.ResponseController.SetWriteDeadline](https://pkg.go.dev/net/http@master#ResponseController.SetWriteDeadline) call — it's called with an int constant, when this method expects time.Time type.

```
¶ go vet
# pkg
vet: ./pkg.go:11:22: cannot use 0 (untyped int constant) as time.Time value in argument to rc.SetWriteDeadline
```
",1,net http  incorrect http responsecontroller usage example in go     release notes         please answer these questions before submitting your issue  thanks              what version of go are you using   go version          go version     darwin             what did you do     pasted a     usage example from go     release notes draft        go  package pkg    import    	 io   	 net http   	 strings        func requesthandler w http responsewriter  r  http request     	rc    http newresponsecontroller w   	rc setwritedeadline       disable server writetimeout when sending a large response  	io copy w  strings newreader  hello                          what did you expect to see     no build errors         what did you see instead     incorrect     call — it s called with an int constant  when this method expects time time type          ¶ go vet    pkg  vet    pkg go      cannot use    untyped int constant  as time time value in argument to rc setwritedeadline       ,1
60475,6691772676.0,IssuesEvent,2017-10-09 14:15:25,edenlabllc/ehealth.api,https://api.github.com/repos/edenlabllc/ehealth.api,closed,Update Program Medication,epic/medication kind/task priority/medium project/reimbursement status/test,"Create Update Program Medication according to requirements

Requirements: [confluence](https://edenlab.atlassian.net/wiki/x/p4CoAQ)

 - [x] Create WS spec
 - [x] Implement
 - [x] Deploy
 - [x] Improve test scenarios
",1.0,"Update Program Medication - Create Update Program Medication according to requirements

Requirements: [confluence](https://edenlab.atlassian.net/wiki/x/p4CoAQ)

 - [x] Create WS spec
 - [x] Implement
 - [x] Deploy
 - [x] Improve test scenarios
",0,update program medication   create update program medication according to requirements    requirements              create ws spec       implement       deploy       improve test scenarios  ,0
33957,6276688397.0,IssuesEvent,2017-07-18 10:10:22,golang/go,https://api.github.com/repos/golang/go,closed,x/review/git-codereview: -trybot option not documented,Documentation,"Please answer these questions before submitting your issue. Thanks!
1. What version of Go are you using (`go version`)? - 
   `go version go1.6 darwin/amd64`
2. What operating system and processor architecture are you using (`go env`)?

```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/.../Source/go""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.6/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.6/libexec/pkg/tool/darwin_amd64""
GO15VENDOREXPERIMENT=""1""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
```
1. What did you do?
   `go codereview mail -h` describes an option, `-trybot`, but neither `go codereview help` nor https://godoc.org/golang.org/x/review/git-codereview describes the option
2. What did you expect to see?
   Something telling me what the `-trybot` option does (esp. if I can use it).
3. What did you see instead?
   Nothing telling me what `-trybot` does.
",1.0,"x/review/git-codereview: -trybot option not documented - Please answer these questions before submitting your issue. Thanks!
1. What version of Go are you using (`go version`)? - 
   `go version go1.6 darwin/amd64`
2. What operating system and processor architecture are you using (`go env`)?

```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/.../Source/go""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.6/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.6/libexec/pkg/tool/darwin_amd64""
GO15VENDOREXPERIMENT=""1""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
```
1. What did you do?
   `go codereview mail -h` describes an option, `-trybot`, but neither `go codereview help` nor https://godoc.org/golang.org/x/review/git-codereview describes the option
2. What did you expect to see?
   Something telling me what the `-trybot` option does (esp. if I can use it).
3. What did you see instead?
   Nothing telling me what `-trybot` does.
",1,x review git codereview   trybot option not documented   please answer these questions before submitting your issue  thanks     what version of go are you using   go version           go version     darwin       what operating system and processor architecture are you using   go env         goarch     gobin    goexe    gohostarch     gohostos  darwin  goos  darwin  gopath   users     source go  gorace    goroot   usr local cellar go     libexec  gotooldir   usr local cellar go     libexec pkg tool darwin          cc  clang  gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fno common  cxx  clang    cgo enabled            what did you do      go codereview mail  h  describes an option    trybot   but neither  go codereview help  nor   describes the option    what did you expect to see     something telling me what the   trybot  option does  esp  if i can use it      what did you see instead     nothing telling me what   trybot  does  ,1
35097,6412710171.0,IssuesEvent,2017-08-08 04:39:29,golang/go,https://api.github.com/repos/golang/go,closed,cmd/cgo: Go type not supported in export: struct,Documentation,"# go version
go version go1.7.4 linux/amd64
 
# go env
```
# go env
GOARCH=""amd64""
GOBIN=""/root/go/bin""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/root/go_pkgs""
GORACE=""""
GOROOT=""/root/go""
GOTOOLDIR=""/root/go/pkg/tool/linux_amd64""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build716839048=/tmp/go-build -gno-record-gcc-switches""
CXX=""g++""
CGO_ENABLED=""1""
```

### What did you do?
I am trying to build a shared object from go code (code has a struct and some functions). I am exporting all the functions and then run go build, but I see this error: `Go type not supported in export: struct`. There's [this thread](https://groups.google.com/forum/#!topic/Golang-nuts/MDoqVSXszdU) on the go-nuts mailing list about this issue, but there doesn't seem to be a resolution.

Here's an example program that generates the error:

**vertex.go**
```
package main

import ""C""
import ""fmt""

type Vertex struct {
  X,Y int
}

//export getVertex
func getVertex(X,Y int) Vertex {
  return Vertex{X,Y}
}

func main() {
  fmt.Println(getVertex(1,2))
}
```

**go build commandline output**
```
# go build -buildmode=c-shared -o vertex.so vertex.go
# command-line-arguments
./struct.go:6:13: Go type not supported in export: struct {
	X, Y int
}
./struct.go:6:13: Go type not supported in export: struct {
	X, Y int
}
```

### What did you expect to see?
I expect the `go build` to run successfully, and generate the shared object.

### What did you see instead?
I see an error `Go type not supported in export: struct`.


",1.0,"cmd/cgo: Go type not supported in export: struct - # go version
go version go1.7.4 linux/amd64
 
# go env
```
# go env
GOARCH=""amd64""
GOBIN=""/root/go/bin""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/root/go_pkgs""
GORACE=""""
GOROOT=""/root/go""
GOTOOLDIR=""/root/go/pkg/tool/linux_amd64""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build716839048=/tmp/go-build -gno-record-gcc-switches""
CXX=""g++""
CGO_ENABLED=""1""
```

### What did you do?
I am trying to build a shared object from go code (code has a struct and some functions). I am exporting all the functions and then run go build, but I see this error: `Go type not supported in export: struct`. There's [this thread](https://groups.google.com/forum/#!topic/Golang-nuts/MDoqVSXszdU) on the go-nuts mailing list about this issue, but there doesn't seem to be a resolution.

Here's an example program that generates the error:

**vertex.go**
```
package main

import ""C""
import ""fmt""

type Vertex struct {
  X,Y int
}

//export getVertex
func getVertex(X,Y int) Vertex {
  return Vertex{X,Y}
}

func main() {
  fmt.Println(getVertex(1,2))
}
```

**go build commandline output**
```
# go build -buildmode=c-shared -o vertex.so vertex.go
# command-line-arguments
./struct.go:6:13: Go type not supported in export: struct {
	X, Y int
}
./struct.go:6:13: Go type not supported in export: struct {
	X, Y int
}
```

### What did you expect to see?
I expect the `go build` to run successfully, and generate the shared object.

### What did you see instead?
I see an error `Go type not supported in export: struct`.


",1,cmd cgo  go type not supported in export  struct     go version  go version       linux         go env         go env  goarch      gobin   root go bin   goexe     gohostarch      gohostos  linux   goos  linux   gopath   root go pkgs   gorace     goroot   root go   gotooldir   root go pkg tool linux     cc  gcc   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches   cxx  g     cgo enabled                 what did you do   i am trying to build a shared object from go code  code has a struct and some functions   i am exporting all the functions and then run go build  but i see this error   go type not supported in export  struct   there s     on the go nuts mailing list about this issue  but there doesn t seem to be a resolution     here s an example program that generates the error       vertex go         package main    import  c   import  fmt     type vertex struct      x y int         export getvertex  func getvertex x y int  vertex      return vertex x y        func main        fmt println getvertex                    go build commandline output           go build  buildmode c shared  o vertex so vertex go    command line arguments    struct go      go type not supported in export  struct    	x  y int       struct go      go type not supported in export  struct    	x  y int                what did you expect to see   i expect the  go build  to run successfully  and generate the shared object         what did you see instead   i see an error  go type not supported in export  struct        ,1
73449,19688033211.0,IssuesEvent,2022-01-12 01:34:32,facebook/zstd,https://api.github.com/repos/facebook/zstd,closed,Build failure using Visual Studio 2022,build issue release-blocking,"**Describe the bug**
When I build zstd using Visual Studio 2022, I got some build error:
```
[1/3] C:\PROGRA~1\MICROS~2\2022\COMMUN~1\VC\Tools\MSVC\1430~1.307\bin\Hostx64\x64\cl.exe -DXXH_NAMESPACE=ZSTD_ -DZSTD_DLL_EXPORT=1 -DZSTD_HEAPMODE=0 -DZSTD_LEGACY_SUPPORT=5 -DZSTD_MULTITHREAD -D_CONSOLE -D_CRT_SECURE_NO_WARNINGS -Dlibzstd_shared_EXPORTS -IC:\src\vcpkg\buildtrees\zstd\x64-windows-dbg\lib -IC:\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\build\cmake\lib -IC:\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\build\cmake\..\..\lib -IC:\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\build\cmake\..\..\lib\common -IC:\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\build\cmake\..\..\lib\legacy  -o lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\decompress\huf_decompress_amd64.S.obj -c C:\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\decompress\huf_decompress_amd64.S
Microsoft (R) C/C++ Optimizing Compiler Version 19.30.30706 for x64
Copyright (C) Microsoft Corporation.  All rights reserved.

cl : Command line warning D9035 : option 'o' has been deprecated and will be removed in a future release
cl : Command line warning D9024 : unrecognized source file type 'C:\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\decompress\huf_decompress_amd64.S', object file assumed
cl : Command line warning D9027 : source file 'C:\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\decompress\huf_decompress_amd64.S' ignored
cl : Command line warning D9021 : no action performed
...
LINK Pass 1: command ""C:\PROGRA~1\MICROS~2\2022\COMMUN~1\VC\Tools\MSVC\1430~1.307\bin\Hostx64\x64\link.exe lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\common\debug.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\common\entropy_common.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\common\error_private.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\common\fse_decompress.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\common\pool.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\common\threading.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\common\xxhash.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\common\zstd_common.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\fse_compress.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\hist.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\huf_compress.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\zstd_compress.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\zstd_compress_literals.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\zstd_compress_sequences.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\zstd_compress_superblock.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\zstd_double_fast.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\zstd_fast.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\zstd_lazy.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\zstd_ldm.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\zstd_opt.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\zstdmt_compress.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\decompress\huf_decompress.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\decompress\huf_decompress_amd64.S.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\decompress\zstd_ddict.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\decompress\zstd_decompress.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\decompress\zstd_decompress_block.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\dictBuilder\cover.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\dictBuilder\divsufsort.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\dictBuilder\fastcover.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\dictBuilder\zdict.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\legacy\zstd_v01.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\legacy\zstd_v02.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\legacy\zstd_v03.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\legacy\zstd_v04.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\legacy\zstd_v05.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\legacy\zstd_v06.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\legacy\zstd_v07.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\build\VS2010\libzstd-dll\libzstd-dll.rc.res /out:lib\zstdd.dll /implib:lib\zstdd.lib /pdb:lib\zstdd.pdb /dll /version:1.5 /machine:x64 /nologo /debug /INCREMENTAL kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib /MANIFEST /MANIFESTFILE:lib\CMakeFiles\libzstd_shared.dir/intermediate.manifest lib\CMakeFiles\libzstd_shared.dir/manifest.res"" failed (exit code 1104) with the following output:
LINK : fatal error LNK1104: cannot open file 'lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\decompress\huf_decompress_amd64.S.obj'
ninja: build stopped: subcommand failed.
```
The cmake options are:
```cmake
        -DZSTD_BUILD_SHARED=${ZSTD_BUILD_SHARED}
        -DZSTD_BUILD_STATIC=${ZSTD_BUILD_STATIC}
        -DZSTD_LEGACY_SUPPORT=1
        -DZSTD_BUILD_PROGRAMS=0
        -DZSTD_BUILD_TESTS=0
        -DZSTD_BUILD_CONTRIB=0
```
It seems that Visual Studio 2022 doesn't recognize this source file.

**Expected behavior**
Build success.

**Desktop (please complete the following information):**
 - OS: Windows
 - Version 10
 - Compiler Visual Studio 2022
 - Flags see log above
 - Other relevant hardware specs N/A
 - Build system CMake

**Additional context**
N/A",1.0,"Build failure using Visual Studio 2022 - **Describe the bug**
When I build zstd using Visual Studio 2022, I got some build error:
```
[1/3] C:\PROGRA~1\MICROS~2\2022\COMMUN~1\VC\Tools\MSVC\1430~1.307\bin\Hostx64\x64\cl.exe -DXXH_NAMESPACE=ZSTD_ -DZSTD_DLL_EXPORT=1 -DZSTD_HEAPMODE=0 -DZSTD_LEGACY_SUPPORT=5 -DZSTD_MULTITHREAD -D_CONSOLE -D_CRT_SECURE_NO_WARNINGS -Dlibzstd_shared_EXPORTS -IC:\src\vcpkg\buildtrees\zstd\x64-windows-dbg\lib -IC:\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\build\cmake\lib -IC:\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\build\cmake\..\..\lib -IC:\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\build\cmake\..\..\lib\common -IC:\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\build\cmake\..\..\lib\legacy  -o lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\decompress\huf_decompress_amd64.S.obj -c C:\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\decompress\huf_decompress_amd64.S
Microsoft (R) C/C++ Optimizing Compiler Version 19.30.30706 for x64
Copyright (C) Microsoft Corporation.  All rights reserved.

cl : Command line warning D9035 : option 'o' has been deprecated and will be removed in a future release
cl : Command line warning D9024 : unrecognized source file type 'C:\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\decompress\huf_decompress_amd64.S', object file assumed
cl : Command line warning D9027 : source file 'C:\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\decompress\huf_decompress_amd64.S' ignored
cl : Command line warning D9021 : no action performed
...
LINK Pass 1: command ""C:\PROGRA~1\MICROS~2\2022\COMMUN~1\VC\Tools\MSVC\1430~1.307\bin\Hostx64\x64\link.exe lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\common\debug.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\common\entropy_common.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\common\error_private.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\common\fse_decompress.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\common\pool.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\common\threading.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\common\xxhash.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\common\zstd_common.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\fse_compress.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\hist.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\huf_compress.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\zstd_compress.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\zstd_compress_literals.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\zstd_compress_sequences.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\zstd_compress_superblock.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\zstd_double_fast.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\zstd_fast.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\zstd_lazy.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\zstd_ldm.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\zstd_opt.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\compress\zstdmt_compress.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\decompress\huf_decompress.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\decompress\huf_decompress_amd64.S.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\decompress\zstd_ddict.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\decompress\zstd_decompress.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\decompress\zstd_decompress_block.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\dictBuilder\cover.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\dictBuilder\divsufsort.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\dictBuilder\fastcover.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\dictBuilder\zdict.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\legacy\zstd_v01.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\legacy\zstd_v02.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\legacy\zstd_v03.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\legacy\zstd_v04.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\legacy\zstd_v05.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\legacy\zstd_v06.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\legacy\zstd_v07.c.obj lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\build\VS2010\libzstd-dll\libzstd-dll.rc.res /out:lib\zstdd.dll /implib:lib\zstdd.lib /pdb:lib\zstdd.pdb /dll /version:1.5 /machine:x64 /nologo /debug /INCREMENTAL kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib /MANIFEST /MANIFESTFILE:lib\CMakeFiles\libzstd_shared.dir/intermediate.manifest lib\CMakeFiles\libzstd_shared.dir/manifest.res"" failed (exit code 1104) with the following output:
LINK : fatal error LNK1104: cannot open file 'lib\CMakeFiles\libzstd_shared.dir\C_\src\vcpkg\buildtrees\zstd\src\dd82848e01-1d82dd46ac\lib\decompress\huf_decompress_amd64.S.obj'
ninja: build stopped: subcommand failed.
```
The cmake options are:
```cmake
        -DZSTD_BUILD_SHARED=${ZSTD_BUILD_SHARED}
        -DZSTD_BUILD_STATIC=${ZSTD_BUILD_STATIC}
        -DZSTD_LEGACY_SUPPORT=1
        -DZSTD_BUILD_PROGRAMS=0
        -DZSTD_BUILD_TESTS=0
        -DZSTD_BUILD_CONTRIB=0
```
It seems that Visual Studio 2022 doesn't recognize this source file.

**Expected behavior**
Build success.

**Desktop (please complete the following information):**
 - OS: Windows
 - Version 10
 - Compiler Visual Studio 2022
 - Flags see log above
 - Other relevant hardware specs N/A
 - Build system CMake

**Additional context**
N/A",0,build failure using visual studio       describe the bug    when i build zstd using visual studio    i got some build error          c  progra   micros     commun   vc tools msvc       bin     cl exe  dxxh namespace zstd   dzstd dll export    dzstd heapmode    dzstd legacy support    dzstd multithread  d console  d crt secure no warnings  dlibzstd shared exports  ic  src vcpkg buildtrees zstd   windows dbg lib  ic  src vcpkg buildtrees zstd src     build cmake lib  ic  src vcpkg buildtrees zstd src     build cmake       lib  ic  src vcpkg buildtrees zstd src     build cmake       lib common  ic  src vcpkg buildtrees zstd src     build cmake       lib legacy   o lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib decompress huf decompress   s obj  c c  src vcpkg buildtrees zstd src     lib decompress huf decompress   s  microsoft  r  c c   optimizing compiler version       for    copyright  c  microsoft corporation   all rights reserved     cl   command line warning     option  o  has been deprecated and will be removed in a future release  cl   command line warning     unrecognized source file type  c  src vcpkg buildtrees zstd src     lib decompress huf decompress   s   object file assumed  cl   command line warning     source file  c  src vcpkg buildtrees zstd src     lib decompress huf decompress   s  ignored  cl   command line warning     no action performed       link pass    command  c  progra   micros     commun   vc tools msvc       bin     link exe lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib common debug c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib common entropy common c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib common error private c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib common fse decompress c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib common pool c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib common threading c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib common xxhash c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib common zstd common c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib compress fse compress c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib compress hist c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib compress huf compress c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib compress zstd compress c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib compress zstd compress literals c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib compress zstd compress sequences c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib compress zstd compress superblock c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib compress zstd double fast c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib compress zstd fast c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib compress zstd lazy c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib compress zstd ldm c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib compress zstd opt c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib compress zstdmt compress c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib decompress huf decompress c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib decompress huf decompress   s obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib decompress zstd ddict c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib decompress zstd decompress c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib decompress zstd decompress block c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib dictbuilder cover c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib dictbuilder divsufsort c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib dictbuilder fastcover c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib dictbuilder zdict c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib legacy zstd   c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib legacy zstd   c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib legacy zstd   c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib legacy zstd   c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib legacy zstd   c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib legacy zstd   c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib legacy zstd   c obj lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     build   libzstd dll libzstd dll rc res  out lib zstdd dll  implib lib zstdd lib  pdb lib zstdd pdb  dll  version      machine    nologo  debug  incremental   lib   lib   lib winspool lib   lib   lib   lib uuid lib   lib   lib  manifest  manifestfile lib cmakefiles libzstd shared dir intermediate manifest lib cmakefiles libzstd shared dir manifest res  failed  exit code    with the following output   link   fatal error    cannot open file  lib cmakefiles libzstd shared dir c  src vcpkg buildtrees zstd src     lib decompress huf decompress   s obj   ninja  build stopped  subcommand failed        the cmake options are      cmake           dzstd build shared   zstd build shared            dzstd build static   zstd build static            dzstd legacy support             dzstd build programs             dzstd build tests             dzstd build contrib         it seems that visual studio   doesn t recognize this source file       expected behavior    build success       desktop  please complete the following information         os  windows     version       compiler visual studio       flags see log above     other relevant hardware specs n a     build system cmake      additional context    n a,0
3405,2762357609.0,IssuesEvent,2015-04-28 22:10:13,golang/go,https://api.github.com/repos/golang/go,closed,net/http: clarify docs on ResponseWriter.Write and Response.Write,Documentation,"by **opennota**:

<pre>When writing to the http.ResponseWriter, the http.Response's method Write doesn't do
what is expected.

    func handler(w http.ResponseWriter, r *http.Request) {
    	resp, _ := client.Get(&quot;<a href=""http://google.com/&quot"">http://google.com/&quot</a>;)
    	resp.Write(w)
    }

This will write resp's headers to the *body* of the handler's response, with the
text/plain content type.

A method that *copies* a Response would be helpful.</pre>",1.0,"net/http: clarify docs on ResponseWriter.Write and Response.Write - by **opennota**:

<pre>When writing to the http.ResponseWriter, the http.Response's method Write doesn't do
what is expected.

    func handler(w http.ResponseWriter, r *http.Request) {
    	resp, _ := client.Get(&quot;<a href=""http://google.com/&quot"">http://google.com/&quot</a>;)
    	resp.Write(w)
    }

This will write resp's headers to the *body* of the handler's response, with the
text/plain content type.

A method that *copies* a Response would be helpful.</pre>",1,net http  clarify docs on responsewriter write and response write   by   opennota      when writing to the http responsewriter  the http response s method write doesn t do what is expected       func handler w http responsewriter  r  http request        	resp       client get  quot  a href        	resp write w         this will write resp s headers to the  body  of the handler s response  with the text plain content type   a method that  copies  a response would be helpful  ,1
34544,9397343818.0,IssuesEvent,2019-04-08 09:30:50,avast-tl/retdec,https://api.github.com/repos/avast-tl/retdec,opened,Parallelize compilation of YARA rules during installation,C-build-system P-install enhancement,"## Current state

When you run `cmake` with `-DRETDEC_COMPILE_YARA=ON`, YARA rules that RetDec uses are compiled during the installation step, which makes decompilations run faster (no need to compile them on the fly during each decompilation).

## Drawback

YARA rules are compiled sequentially, which takes around 50 seconds to compile them on my machine.

## Suggestion

We could parallelize their compilation, either by using all available cores (easy), or by taking the `/m` or `-j` parameter into account (harder, as I am not sure if we are able to get the value of this parameter in `install-yara.py`).",1.0,"Parallelize compilation of YARA rules during installation - ## Current state

When you run `cmake` with `-DRETDEC_COMPILE_YARA=ON`, YARA rules that RetDec uses are compiled during the installation step, which makes decompilations run faster (no need to compile them on the fly during each decompilation).

## Drawback

YARA rules are compiled sequentially, which takes around 50 seconds to compile them on my machine.

## Suggestion

We could parallelize their compilation, either by using all available cores (easy), or by taking the `/m` or `-j` parameter into account (harder, as I am not sure if we are able to get the value of this parameter in `install-yara.py`).",0,parallelize compilation of yara rules during installation      current state    when you run  cmake  with   dretdec compile yara on   yara rules that retdec uses are compiled during the installation step  which makes decompilations run faster  no need to compile them on the fly during each decompilation         drawback    yara rules are compiled sequentially  which takes around   seconds to compile them on my machine        suggestion    we could parallelize their compilation  either by using all available cores  easy   or by taking the   m  or   j  parameter into account  harder  as i am not sure if we are able to get the value of this parameter in  install yara py   ,0
249698,21186159425.0,IssuesEvent,2022-04-08 12:58:04,ory/k8s,https://api.github.com/repos/ory/k8s,closed,Add Prometheus stack to the CI kind cluster,feat tests,"### Preflight checklist

- [X] I could not find a solution in the existing issues, docs, nor discussions.
- [X] I agree to follow this project's [Code of Conduct](https://github.com/ory/k8s/blob/master/CODE_OF_CONDUCT.md).
- [X] I have read and am following this repository's [Contribution Guidelines](https://github.com/ory/k8s/blob/master/CONTRIBUTING.md).
- [ ] This issue affects my [Ory Cloud](https://www.ory.sh/) project.
- [X] I have joined the [Ory Community Slack](https://slack.ory.sh).
- [ ] I am signed up to the [Ory Security Patch Newsletter](https://ory.us10.list-manage.com/subscribe?u=ffb1a878e4ec6c0ed312a3480&id=f605a41b53).

### Describe your problem

Currently most of the Ory component charts come with the support for ServiceMonitors, and are deployed if the required CRD are present on the cluster. However, in the CI we do not deploy the CRDs, which make testing changes to those objects difficult. 

### Describe your ideal solution

The CI cluster is updated with the proper CRD, or the whole promethus stack, which will allow for better tests.

### Workarounds or alternatives

Installing only the CRDS without the controller, to create the ServiceMonitors and validate them only on a syntax level.

### Version

yes

### Additional Context

_No response_",1.0,"Add Prometheus stack to the CI kind cluster - ### Preflight checklist

- [X] I could not find a solution in the existing issues, docs, nor discussions.
- [X] I agree to follow this project's [Code of Conduct](https://github.com/ory/k8s/blob/master/CODE_OF_CONDUCT.md).
- [X] I have read and am following this repository's [Contribution Guidelines](https://github.com/ory/k8s/blob/master/CONTRIBUTING.md).
- [ ] This issue affects my [Ory Cloud](https://www.ory.sh/) project.
- [X] I have joined the [Ory Community Slack](https://slack.ory.sh).
- [ ] I am signed up to the [Ory Security Patch Newsletter](https://ory.us10.list-manage.com/subscribe?u=ffb1a878e4ec6c0ed312a3480&id=f605a41b53).

### Describe your problem

Currently most of the Ory component charts come with the support for ServiceMonitors, and are deployed if the required CRD are present on the cluster. However, in the CI we do not deploy the CRDs, which make testing changes to those objects difficult. 

### Describe your ideal solution

The CI cluster is updated with the proper CRD, or the whole promethus stack, which will allow for better tests.

### Workarounds or alternatives

Installing only the CRDS without the controller, to create the ServiceMonitors and validate them only on a syntax level.

### Version

yes

### Additional Context

_No response_",0,add prometheus stack to the ci kind cluster       preflight checklist      i could not find a solution in the existing issues  docs  nor discussions      i agree to follow this project s         i have read and am following this repository s         this issue affects my     project      i have joined the         i am signed up to the          describe your problem  currently most of the ory component charts come with the support for servicemonitors  and are deployed if the required crd are present on the cluster  however  in the ci we do not deploy the crds  which make testing changes to those objects difficult        describe your ideal solution  the ci cluster is updated with the proper crd  or the whole promethus stack  which will allow for better tests       workarounds or alternatives  installing only the crds without the controller  to create the servicemonitors and validate them only on a syntax level       version  yes      additional context   no response ,0
282410,30889323777.0,IssuesEvent,2023-08-04 02:33:27,maddyCode23/linux-4.1.15,https://api.github.com/repos/maddyCode23/linux-4.1.15,reopened,CVE-2017-18017 (Critical) detected in linux-stable-rtv4.1.33,Mend: dependency security vulnerability,"## CVE-2017-18017 - Critical Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>

<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/maddyCode23/linux-4.1.15/commit/f1f3d2b150be669390b32dfea28e773471bdd6e7"">f1f3d2b150be669390b32dfea28e773471bdd6e7</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/netfilter/xt_TCPMSS.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/netfilter/xt_TCPMSS.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The tcpmss_mangle_packet function in net/netfilter/xt_TCPMSS.c in the Linux kernel before 4.11, and 4.9.x before 4.9.36, allows remote attackers to cause a denial of service (use-after-free and memory corruption) or possibly have unspecified other impact by leveraging the presence of xt_TCPMSS in an iptables action.

<p>Publish Date: 2018-01-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-18017>CVE-2017-18017</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://www.linuxkernelcves.com/cves/CVE-2017-18017"">https://www.linuxkernelcves.com/cves/CVE-2017-18017</a></p>
<p>Release Date: 2018-01-03</p>
<p>Fix Resolution: v4.11-rc7,v3.16.54,v3.18.60,v3.2.99,v4.1.43,v4.4.76,v4.9.36</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2017-18017 (Critical) detected in linux-stable-rtv4.1.33 - ## CVE-2017-18017 - Critical Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>

<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/maddyCode23/linux-4.1.15/commit/f1f3d2b150be669390b32dfea28e773471bdd6e7"">f1f3d2b150be669390b32dfea28e773471bdd6e7</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/netfilter/xt_TCPMSS.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/netfilter/xt_TCPMSS.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The tcpmss_mangle_packet function in net/netfilter/xt_TCPMSS.c in the Linux kernel before 4.11, and 4.9.x before 4.9.36, allows remote attackers to cause a denial of service (use-after-free and memory corruption) or possibly have unspecified other impact by leveraging the presence of xt_TCPMSS in an iptables action.

<p>Publish Date: 2018-01-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-18017>CVE-2017-18017</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://www.linuxkernelcves.com/cves/CVE-2017-18017"">https://www.linuxkernelcves.com/cves/CVE-2017-18017</a></p>
<p>Release Date: 2018-01-03</p>
<p>Fix Resolution: v4.11-rc7,v3.16.54,v3.18.60,v3.2.99,v4.1.43,v4.4.76,v4.9.36</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      critical  detected in linux stable            cve       critical severity vulnerability     vulnerable library    linux stable              julia cartwright s fork of linux stable rt git   library home page   a href    found in head commit   a href      found in base branch   master             vulnerable source files                  net netfilter xt tcpmss c        net netfilter xt tcpmss c                    vulnerability details         the tcpmss mangle packet function in net netfilter xt tcpmss c in the linux kernel before      and     x before        allows remote attackers to cause a denial of service  use after free and memory corruption  or possibly have unspecified other impact by leveraging the presence of xt tcpmss in an iptables action    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 mend    ,0
69102,9256549528.0,IssuesEvent,2019-03-16 20:02:06,golang/go,https://api.github.com/repos/golang/go,closed,blog: document Code generated convention in the Generating code blog post,Documentation NeedsFix,"As the Go community has reached consensus on the convention to use for distinguishing machine-generated code (i.e. https://golang.org/s/generatedcode), it would be good if the [Generating code](https://blog.golang.org/generate) article on the Go blog was updated to reflect this. Preferably a link could also be added from the Generating code article to https://golang.org/s/generatedcode

In particular, the Generating code article is still using the convention `// generated by stringer -type Pill pill.go; DO NOT EDIT`. Since the blog post is the first hit (for me at least) on Google which searching for *generate code golang*, the article should in my opinion be updated so that new Gophers learn the newly established convention.",1.0,"blog: document Code generated convention in the Generating code blog post - As the Go community has reached consensus on the convention to use for distinguishing machine-generated code (i.e. https://golang.org/s/generatedcode), it would be good if the [Generating code](https://blog.golang.org/generate) article on the Go blog was updated to reflect this. Preferably a link could also be added from the Generating code article to https://golang.org/s/generatedcode

In particular, the Generating code article is still using the convention `// generated by stringer -type Pill pill.go; DO NOT EDIT`. Since the blog post is the first hit (for me at least) on Google which searching for *generate code golang*, the article should in my opinion be updated so that new Gophers learn the newly established convention.",1,blog  document code generated convention in the generating code blog post   as the go community has reached consensus on the convention to use for distinguishing machine generated code  i e    it would be good if the     article on the go blog was updated to reflect this  preferably a link could also be added from the generating code article to      in particular  the generating code article is still using the convention     generated by stringer  type pill pill go  do not edit   since the blog post is the first hit  for me at least  on google which searching for  generate code golang   the article should in my opinion be updated so that new gophers learn the newly established convention ,1
8843,3226051888.0,IssuesEvent,2015-10-10 00:49:18,golang/go,https://api.github.com/repos/golang/go,closed,compress/flate: Inconsistent error handling,Documentation,"The package defines a ReadError which ""reports an error encountered while reading input"" and a WriteError which ""reports an error encountered while writing output"". However, a quick peruse through the package code shows that WriteError is never used. Secondly, its use of ReadError is inconsistent.

There are 3 instances where the Reader is used in inflate.go: [L635](https://github.com/golang/go/blob/b03129aa2758a337823071ffda37e49da5a814d0/src/compress/flate/inflate.go#L635), [L677](https://github.com/golang/go/blob/b03129aa2758a337823071ffda37e49da5a814d0/src/compress/flate/inflate.go#L667), and [L699](https://github.com/golang/go/blob/b03129aa2758a337823071ffda37e49da5a814d0/src/compress/flate/inflate.go#L699). The call to ReadByte lacks a the wrapper for ReadError. Interestingly, the bulk of DEFLATE compression will be done through the ReadByte call, thus, usage of ReadError seems to only occur when decoding a raw block.

Should use of ReadError and WriteError be removed and marked as deprecated? Or should the library properly handle both error types? Other packages don't seem to wrap IO errors with package specific errors.",1.0,"compress/flate: Inconsistent error handling - The package defines a ReadError which ""reports an error encountered while reading input"" and a WriteError which ""reports an error encountered while writing output"". However, a quick peruse through the package code shows that WriteError is never used. Secondly, its use of ReadError is inconsistent.

There are 3 instances where the Reader is used in inflate.go: [L635](https://github.com/golang/go/blob/b03129aa2758a337823071ffda37e49da5a814d0/src/compress/flate/inflate.go#L635), [L677](https://github.com/golang/go/blob/b03129aa2758a337823071ffda37e49da5a814d0/src/compress/flate/inflate.go#L667), and [L699](https://github.com/golang/go/blob/b03129aa2758a337823071ffda37e49da5a814d0/src/compress/flate/inflate.go#L699). The call to ReadByte lacks a the wrapper for ReadError. Interestingly, the bulk of DEFLATE compression will be done through the ReadByte call, thus, usage of ReadError seems to only occur when decoding a raw block.

Should use of ReadError and WriteError be removed and marked as deprecated? Or should the library properly handle both error types? Other packages don't seem to wrap IO errors with package specific errors.",1,compress flate  inconsistent error handling   the package defines a readerror which  reports an error encountered while reading input  and a writeerror which  reports an error encountered while writing output   however  a quick peruse through the package code shows that writeerror is never used  secondly  its use of readerror is inconsistent     there are   instances where the reader is used in inflate go          and     the call to readbyte lacks a the wrapper for readerror  interestingly  the bulk of deflate compression will be done through the readbyte call  thus  usage of readerror seems to only occur when decoding a raw block     should use of readerror and writeerror be removed and marked as deprecated  or should the library properly handle both error types  other packages don t seem to wrap io errors with package specific errors ,1
444686,12819293831.0,IssuesEvent,2020-07-06 01:32:33,kubeflow/code-intelligence,https://api.github.com/repos/kubeflow/code-intelligence,closed,Train an org wide model for Kubeflow to predict area and platform labels,area/gsoc kind/feature priority/p2,"We should train a model on all Kubeflow repositories that attempts to predict the area and platform
labels.

We already have a model for kubeflow/kubeflow but this model was last trained this summer. So
we should have significantly more data.

We'd also like to start tuning the thresholds so that more issues get area labels added automatically.

Background

* Read the [README](https://github.com/kubeflow/code-intelligence/tree/master/Label_Microservice) to understand how the issue label works

* Notebook to download GitHub issues and compute embeddings for them [https://github.com/kubeflow/code-intelligence/blob/master/Label_Microservice/notebooks/issues_loader.ipynb]
* This [notebook](https://github.com/kubeflow/code-intelligence/blob/master/Label_Microservice/notebooks/repo_mlp.ipynb) can train the model
  * The embeddings of the training data must already be computed
* This [notebook](https://github.com/kubeflow/code-intelligence/blob/master/Label_Microservice/notebooks/Training_Pipeline.ipynb) is used to launch Kubeflow pipelines to train the model

* The code to download github issues for a specific repo is [here](https://github.com/kubeflow/code-intelligence/blob/2197c647b62bcfb93e0be13d0bbfc7753fd96177/py/code_intelligence/embeddings.py#L76)

I think we can break this down into steps

1. Create a Kubelfow pipeline to download the github issues for each repo in Kubeflow
1. Add steps to the KFP pipeline to compute embeddings for the issues
1. Train a model using the combined dataset
1. Update the Kubeflow label bot to use this model to predict labels for Kubeflow


Follow on to #70",1.0,"Train an org wide model for Kubeflow to predict area and platform labels - We should train a model on all Kubeflow repositories that attempts to predict the area and platform
labels.

We already have a model for kubeflow/kubeflow but this model was last trained this summer. So
we should have significantly more data.

We'd also like to start tuning the thresholds so that more issues get area labels added automatically.

Background

* Read the [README](https://github.com/kubeflow/code-intelligence/tree/master/Label_Microservice) to understand how the issue label works

* Notebook to download GitHub issues and compute embeddings for them [https://github.com/kubeflow/code-intelligence/blob/master/Label_Microservice/notebooks/issues_loader.ipynb]
* This [notebook](https://github.com/kubeflow/code-intelligence/blob/master/Label_Microservice/notebooks/repo_mlp.ipynb) can train the model
  * The embeddings of the training data must already be computed
* This [notebook](https://github.com/kubeflow/code-intelligence/blob/master/Label_Microservice/notebooks/Training_Pipeline.ipynb) is used to launch Kubeflow pipelines to train the model

* The code to download github issues for a specific repo is [here](https://github.com/kubeflow/code-intelligence/blob/2197c647b62bcfb93e0be13d0bbfc7753fd96177/py/code_intelligence/embeddings.py#L76)

I think we can break this down into steps

1. Create a Kubelfow pipeline to download the github issues for each repo in Kubeflow
1. Add steps to the KFP pipeline to compute embeddings for the issues
1. Train a model using the combined dataset
1. Update the Kubeflow label bot to use this model to predict labels for Kubeflow


Follow on to #70",0,train an org wide model for kubeflow to predict area and platform labels   we should train a model on all kubeflow repositories that attempts to predict the area and platform  labels     we already have a model for kubeflow kubeflow but this model was last trained this summer  so  we should have significantly more data     we d also like to start tuning the thresholds so that more issues get area labels added automatically     background      read the     to understand how the issue label works      notebook to download github issues and compute embeddings for them      this     can train the model      the embeddings of the training data must already be computed    this     is used to launch kubeflow pipelines to train the model      the code to download github issues for a specific repo is        i think we can break this down into steps       create a kubelfow pipeline to download the github issues for each repo in kubeflow     add steps to the kfp pipeline to compute embeddings for the issues     train a model using the combined dataset     update the kubeflow label bot to use this model to predict labels for kubeflow      follow on to   ,0
400799,11780808477.0,IssuesEvent,2020-03-16 20:54:01,silverbackis/ApiComponentBundle,https://api.github.com/repos/silverbackis/ApiComponentBundle,opened,Testing & Bug Fixes,High Priority,"We need to introduce tests to ensure code is working as expected and to prevent regression.

This includes unit and functional tests. We must also ensure that we get a good mutation score for the tests.

Target: 90% test coverage + 80% mutation score

^^ These targets are a little arbitrary at the moment due to a lack of experience writing tests. I'm not sure whether they will be achievable within budget for the current stage, but it is important to make a start. We can adjust these 1st stage targets and we progress and add a less important issue to increase coverage and mutation score at a later date if required.",1.0,"Testing & Bug Fixes - We need to introduce tests to ensure code is working as expected and to prevent regression.

This includes unit and functional tests. We must also ensure that we get a good mutation score for the tests.

Target: 90% test coverage + 80% mutation score

^^ These targets are a little arbitrary at the moment due to a lack of experience writing tests. I'm not sure whether they will be achievable within budget for the current stage, but it is important to make a start. We can adjust these 1st stage targets and we progress and add a less important issue to increase coverage and mutation score at a later date if required.",0,testing   bug fixes   we need to introduce tests to ensure code is working as expected and to prevent regression     this includes unit and functional tests  we must also ensure that we get a good mutation score for the tests     target     test coverage      mutation score       these targets are a little arbitrary at the moment due to a lack of experience writing tests  i m not sure whether they will be achievable within budget for the current stage  but it is important to make a start  we can adjust these   stage targets and we progress and add a less important issue to increase coverage and mutation score at a later date if required ,0
60854,8469455475.0,IssuesEvent,2018-10-23 23:04:42,golang/go,https://api.github.com/repos/golang/go,closed,"spec: don't use ""exception"" instead of ""panic""",Documentation NeedsFix,"When the [Spec](https://tip.golang.org/ref/spec#Integer_overflow) talks about integer overflow, there is this sentence:

>(…) No *exception* is raised as a result of overflow. (…)

Emphasis added. Go doesn't have exceptions, it has panics. I think this sentence should be rewritten to something like:

>(…) Overflow does not trigger a run-time panic. (…)

As far as I can see, the word ""exception"" meaning ""run-time error"" isn't used anywhere else in the Spec.",1.0,"spec: don't use ""exception"" instead of ""panic"" - When the [Spec](https://tip.golang.org/ref/spec#Integer_overflow) talks about integer overflow, there is this sentence:

>(…) No *exception* is raised as a result of overflow. (…)

Emphasis added. Go doesn't have exceptions, it has panics. I think this sentence should be rewritten to something like:

>(…) Overflow does not trigger a run-time panic. (…)

As far as I can see, the word ""exception"" meaning ""run-time error"" isn't used anywhere else in the Spec.",1,spec  don t use  exception  instead of  panic    when the     talks about integer overflow  there is this sentence       …  no  exception  is raised as a result of overflow   …     emphasis added  go doesn t have exceptions  it has panics  i think this sentence should be rewritten to something like       …  overflow does not trigger a run time panic   …     as far as i can see  the word  exception  meaning  run time error  isn t used anywhere else in the spec ,1
53634,7846973481.0,IssuesEvent,2018-06-19 16:58:33,golang/go,https://api.github.com/repos/golang/go,opened,crypto/rand: decide on the hyphenation of pseudorandom vs pseudo-random,Documentation,"The docs for crypto/rand contain both ""pseudorandom"" and ""pseudo-random"" for the same part of speech.

Decide which to use.

Also, the package doc says:

> Package rand implements a cryptographically secure pseudorandom number generator.

But the Reader says:

> Reader is a global, shared instance of a cryptographically strong pseudo-random generator.

Is it cryptographically ""strong"" or is it ""secure""? Can we pick a word there too?

Or can we just remove ""pseudorandom"" altogether? I feel like it makes it sound too much like math/rand.

Can we just say ""cryptographically secure random number generator""?

/cc @FiloSottile @agl @ianlancetaylor ",1.0,"crypto/rand: decide on the hyphenation of pseudorandom vs pseudo-random - The docs for crypto/rand contain both ""pseudorandom"" and ""pseudo-random"" for the same part of speech.

Decide which to use.

Also, the package doc says:

> Package rand implements a cryptographically secure pseudorandom number generator.

But the Reader says:

> Reader is a global, shared instance of a cryptographically strong pseudo-random generator.

Is it cryptographically ""strong"" or is it ""secure""? Can we pick a word there too?

Or can we just remove ""pseudorandom"" altogether? I feel like it makes it sound too much like math/rand.

Can we just say ""cryptographically secure random number generator""?

/cc @FiloSottile @agl @ianlancetaylor ",1,crypto rand  decide on the hyphenation of pseudorandom vs pseudo random   the docs for crypto rand contain both  pseudorandom  and  pseudo random  for the same part of speech     decide which to use     also  the package doc says       package rand implements a cryptographically secure pseudorandom number generator     but the reader says       reader is a global  shared instance of a cryptographically strong pseudo random generator     is it cryptographically  strong  or is it  secure   can we pick a word there too     or can we just remove  pseudorandom  altogether  i feel like it makes it sound too much like math rand     can we just say  cryptographically secure random number generator       cc  filosottile  agl  ianlancetaylor ,1
382191,26488149526.0,IssuesEvent,2023-01-17 19:55:47,golang/go,https://api.github.com/repos/golang/go,closed,spec: constraint type inference should proceed even if an individual unification step fails,Documentation NeedsFix TypeInference compiler/runtime,"Edit: See https://github.com/golang/go/issues/53650#issuecomment-1334495063 for a summary of the problem.

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.18.3 windows/amd64
</pre>

### What did you do?

```go

type BaseT interface {
	Type1 | Type2
}
type BaseType int
type Type1 BaseType
type Type2 BaseType // float64

type ValueT[T BaseT] struct {
	A1 T
}

func NewType1() *ValueT[Type1] {
	r := NewT[Type1]()
	return r
}
func NewType2() *ValueT[Type2] {
	r := NewT[Type2]()
	return r
}

func NewT[TBase BaseT, TVal ValueT[TBase]]() *TVal {
	ret := TVal{}
	return &ret
}
func TestGoType(t *testing.T) {
	r1 := NewType1()
	r2 := NewType2()
	t.Log(r1, r2)
	t.Log(reflect.TypeOf(r1), reflect.TypeOf(r2))
	fooT1(r1.A1)
	fooT2(r2.A1)
}

func fooT1(t1 Type1) {

}
func fooT2(t2 Type2) {

}

```

### What did you expect to see?

Compile success

### What did you see instead?

error:  
```
TBase does not match int
TBase does not match int
```
",1.0,"spec: constraint type inference should proceed even if an individual unification step fails - Edit: See https://github.com/golang/go/issues/53650#issuecomment-1334495063 for a summary of the problem.

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.18.3 windows/amd64
</pre>

### What did you do?

```go

type BaseT interface {
	Type1 | Type2
}
type BaseType int
type Type1 BaseType
type Type2 BaseType // float64

type ValueT[T BaseT] struct {
	A1 T
}

func NewType1() *ValueT[Type1] {
	r := NewT[Type1]()
	return r
}
func NewType2() *ValueT[Type2] {
	r := NewT[Type2]()
	return r
}

func NewT[TBase BaseT, TVal ValueT[TBase]]() *TVal {
	ret := TVal{}
	return &ret
}
func TestGoType(t *testing.T) {
	r1 := NewType1()
	r2 := NewType2()
	t.Log(r1, r2)
	t.Log(reflect.TypeOf(r1), reflect.TypeOf(r2))
	fooT1(r1.A1)
	fooT2(r2.A1)
}

func fooT1(t1 Type1) {

}
func fooT2(t2 Type2) {

}

```

### What did you expect to see?

Compile success

### What did you see instead?

error:  
```
TBase does not match int
TBase does not match int
```
",1,spec  constraint type inference should proceed even if an individual unification step fails   edit  see   for a summary of the problem         what version of go are you using   go version            go version  go version       windows             what did you do        go    type baset interface    	          type basetype int  type   basetype  type   basetype         type valuet  struct    	  t       func      valuet     	r    newt     	return r     func      valuet     	r    newt     	return r       func newt      tval    	ret    tval    	return  ret     func testgotype t  testing t     	          	          	t log        	t log reflect typeof     reflect typeof      	        	             func                func                             what did you expect to see     compile success        what did you see instead     error          tbase does not match int  tbase does not match int       ,1
3330,2610060730.0,IssuesEvent,2015-02-26 18:17:53,chrsmith/jsjsj122,https://api.github.com/repos/chrsmith/jsjsj122,opened,路桥治不育哪里效果好,auto-migrated Priority-Medium Type-Defect,"```
路桥治不育哪里效果好【台州五洲生殖医院】24小时健康咨询
热线:0576-88066933-(扣扣800080609)-(微信号tzwzszyy)医院地址:台州市
椒江区枫南路229号（枫南大转盘旁）乘车线路:乘坐104、108、1
18、198及椒江一金清公交车直达枫南小区，乘坐107、105、109、
112、901、 902公交车到星星广场下车，步行即可到院。
诊疗项目：阳痿，早泄，前列腺炎，前列腺增生，龟头炎，��
�精，无精。包皮包茎，精索静脉曲张，淋病等。
台州五洲生殖医院是台州最大的男科医院，权威专家在线免��
�咨询，拥有专业完善的男科检查治疗设备，严格按照国家标�
��收费。尖端医疗设备，与世界同步。权威专家，成就专业典
范。人性化服务，一切以患者为中心。
看男科就选台州五洲生殖医院，专业男科为男人。

```

-----
Original issue reported on code.google.com by `poweragr...@gmail.com` on 30 May 2014 at 7:14",1.0,"路桥治不育哪里效果好 - ```
路桥治不育哪里效果好【台州五洲生殖医院】24小时健康咨询
热线:0576-88066933-(扣扣800080609)-(微信号tzwzszyy)医院地址:台州市
椒江区枫南路229号（枫南大转盘旁）乘车线路:乘坐104、108、1
18、198及椒江一金清公交车直达枫南小区，乘坐107、105、109、
112、901、 902公交车到星星广场下车，步行即可到院。
诊疗项目：阳痿，早泄，前列腺炎，前列腺增生，龟头炎，��
�精，无精。包皮包茎，精索静脉曲张，淋病等。
台州五洲生殖医院是台州最大的男科医院，权威专家在线免��
�咨询，拥有专业完善的男科检查治疗设备，严格按照国家标�
��收费。尖端医疗设备，与世界同步。权威专家，成就专业典
范。人性化服务，一切以患者为中心。
看男科就选台州五洲生殖医院，专业男科为男人。

```

-----
Original issue reported on code.google.com by `poweragr...@gmail.com` on 30 May 2014 at 7:14",0,路桥治不育哪里效果好       路桥治不育哪里效果好【台州五洲生殖医院】  热线          微信号tzwzszyy 医院地址 台州市  （枫南大转盘旁）乘车线路  、 、   、 ， 、 、 、  、 、  ，步行即可到院。 诊疗项目：阳痿，早泄，前列腺炎，前列腺增生，龟头炎，�� �精，无精。包皮包茎，精索静脉曲张，淋病等。 台州五洲生殖医院是台州最大的男科医院，权威专家在线免�� �咨询，拥有专业完善的男科检查治疗设备，严格按照国家标� ��收费。尖端医疗设备，与世界同步。权威专家，成就专业典 范。人性化服务，一切以患者为中心。 看男科就选台州五洲生殖医院，专业男科为男人。             original issue reported on code google com by  poweragr    gmail com  on   may   at    ,0
47053,11950830111.0,IssuesEvent,2020-04-03 15:50:17,callahantiff/PheKnowLator,https://api.github.com/repos/callahantiff/PheKnowLator,opened,Build V3 - knowledge_graph.py,coding next build,"**V3 Build Changes**. 
**Script:** [`knowledge_graph.py.py`](https://github.com/callahantiff/PheKnowLator/blob/master/pkt_kg/knowledge_graph.py)  

Requested Changes:  
- [ ]  Extend functionality of the code to improve KR for instance-based builds that include connections between 2 instance nodes (for example, the `complex` and `reaction` nodes from Reactome (shown in Figure below) 

<br>

![PheKnowLator_v2 0 0_KnowledgeRepresentation_Instance_all](https://user-images.githubusercontent.com/8030363/78380041-80828800-7590-11ea-8972-34cc1401f614.png)
",1.0,"Build V3 - knowledge_graph.py - **V3 Build Changes**. 
**Script:** [`knowledge_graph.py.py`](https://github.com/callahantiff/PheKnowLator/blob/master/pkt_kg/knowledge_graph.py)  

Requested Changes:  
- [ ]  Extend functionality of the code to improve KR for instance-based builds that include connections between 2 instance nodes (for example, the `complex` and `reaction` nodes from Reactome (shown in Figure below) 

<br>

![PheKnowLator_v2 0 0_KnowledgeRepresentation_Instance_all](https://user-images.githubusercontent.com/8030363/78380041-80828800-7590-11ea-8972-34cc1401f614.png)
",0,build     knowledge graph py       build changes        script             requested changes          extend functionality of the code to improve kr for instance based builds that include connections between   instance nodes  for example  the  complex  and  reaction  nodes from reactome  shown in figure below                 ,0
150938,11994508277.0,IssuesEvent,2020-04-08 13:49:11,crytic/echidna,https://api.github.com/repos/crytic/echidna,opened,Reenable OSX building in Github actions,help wanted testing,"OSX compilation was disabled when we migrated to github actions because we had an error in the linking:

https://github.com/crytic/echidna/runs/552743533#step:10:6467

To fix this, you can follow how we [compiled echidna in osx using travis](https://github.com/crytic/echidna/blob/v1.4.0.1/.travis.yml). Please note that we don't need to run the tests, just make sure echidna compiles correctly. ",1.0,"Reenable OSX building in Github actions - OSX compilation was disabled when we migrated to github actions because we had an error in the linking:

https://github.com/crytic/echidna/runs/552743533#step:10:6467

To fix this, you can follow how we [compiled echidna in osx using travis](https://github.com/crytic/echidna/blob/v1.4.0.1/.travis.yml). Please note that we don't need to run the tests, just make sure echidna compiles correctly. ",0,reenable osx building in github actions   osx compilation was disabled when we migrated to github actions because we had an error in the linking          to fix this  you can follow how we     please note that we don t need to run the tests  just make sure echidna compiles correctly  ,0
66611,12806542300.0,IssuesEvent,2020-07-03 09:38:38,topcoder-platform/community-app,https://api.github.com/repos/topcoder-platform/community-app,closed,colorStyle need calculated in Frontend,Challenge Listing P3 v5-intgration-sub-code,"**Describe the bug**
Before **challenges-api** returning `colorStyle` from DB, this sets the color of the handle by rating. In V5 this need be done by FE following this: https://www.topcoder.com/community/competitive-programming/how-to-compete/ratings

**To Reproduce**
Steps to reproduce the behavior:
1. Go to challenge details
2. Click on Registrants or Submissions
3. See all handle have black color

**Expected behavior**
Handle need to show color follow the rank rating

**Screenshots**
![image](https://user-images.githubusercontent.com/7029641/84584710-fd767d00-addd-11ea-8c72-2f0fbcae5602.png)
",1.0,"colorStyle need calculated in Frontend - **Describe the bug**
Before **challenges-api** returning `colorStyle` from DB, this sets the color of the handle by rating. In V5 this need be done by FE following this: https://www.topcoder.com/community/competitive-programming/how-to-compete/ratings

**To Reproduce**
Steps to reproduce the behavior:
1. Go to challenge details
2. Click on Registrants or Submissions
3. See all handle have black color

**Expected behavior**
Handle need to show color follow the rank rating

**Screenshots**
![image](https://user-images.githubusercontent.com/7029641/84584710-fd767d00-addd-11ea-8c72-2f0fbcae5602.png)
",0,colorstyle need calculated in frontend     describe the bug    before   challenges api   returning  colorstyle  from db  this sets the color of the handle by rating  in   this need be done by fe following this         to reproduce    steps to reproduce the behavior      go to challenge details     click on registrants or submissions     see all handle have black color      expected behavior    handle need to show color follow the rank rating      screenshots          ,0
86504,10508518969.0,IssuesEvent,2019-09-27 08:50:32,golang/go,https://api.github.com/repos/golang/go,closed,x/tour: instructions for running Go tour offline are malformatted,Documentation NeedsFix help wanted,"There seem to be two issues with the instructions for how to run the Go tour offline [here](https://tour.golang.org/welcome/3).

First, on my Fedora system, even though I have installed Go 1.10.1 from binary rpms, running `go tool tour` doesn't work (perhaps this requires installing a distinct Fedora package that is not mentioned):

```
$ go tool tour
go tool: no such tool ""tour""
$
```

The second issue is that, before trying to run these commands:

```
$ go get golang.org/x/tour/gotour
$ gotour
```

the reader should be reminded to add `${GOPATH}/bin` to their search path.",1.0,"x/tour: instructions for running Go tour offline are malformatted - There seem to be two issues with the instructions for how to run the Go tour offline [here](https://tour.golang.org/welcome/3).

First, on my Fedora system, even though I have installed Go 1.10.1 from binary rpms, running `go tool tour` doesn't work (perhaps this requires installing a distinct Fedora package that is not mentioned):

```
$ go tool tour
go tool: no such tool ""tour""
$
```

The second issue is that, before trying to run these commands:

```
$ go get golang.org/x/tour/gotour
$ gotour
```

the reader should be reminded to add `${GOPATH}/bin` to their search path.",1,x tour  instructions for running go tour offline are malformatted   there seem to be two issues with the instructions for how to run the go tour offline        first  on my fedora system  even though i have installed go       from binary rpms  running  go tool tour  doesn t work  perhaps this requires installing a distinct fedora package that is not mentioned             go tool tour  go tool  no such tool  tour             the second issue is that  before trying to run these commands            go get golang org x tour gotour    gotour         the reader should be reminded to add    gopath  bin  to their search path ,1
51724,13645384165.0,IssuesEvent,2020-09-25 20:41:02,TreyM-WSS/WebGoat,https://api.github.com/repos/TreyM-WSS/WebGoat,opened,CVE-2018-20677 (Medium) detected in bootstrap-3.1.1.min.js,security vulnerability,"## CVE-2018-20677 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>bootstrap-3.1.1.min.js</b></p></summary>

<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href=""https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.min.js"">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.min.js</a></p>
<p>Path to vulnerable library: WebGoat/webgoat-container/src/main/resources/static/plugins/bootstrap/js/bootstrap.min.js,WebGoat/webgoat-lessons/challenge/src/main/resources/js/bootstrap.min.js,WebGoat/webgoat-container/target/classes/static/plugins/bootstrap/js/bootstrap.min.js</p>
<p>

Dependency Hierarchy:
  - :x: **bootstrap-3.1.1.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/TreyM-WSS/WebGoat/commit/0b6b6b4926a0f3f0d2dbbe6647e362afe5390cc0"">0b6b6b4926a0f3f0d2dbbe6647e362afe5390cc0</a></p>
<p>Found in base branch: <b>develop</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
In Bootstrap before 3.4.0, XSS is possible in the affix configuration target property.

<p>Publish Date: 2019-01-09
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20677>CVE-2018-20677</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Changed
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20677"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20677</a></p>
<p>Release Date: 2019-01-09</p>
<p>Fix Resolution: Bootstrap - v3.4.0;NorDroN.AngularTemplate - 0.1.6;Dynamic.NET.Express.ProjectTemplates - 0.8.0;dotnetng.template - 1.0.0.4;ZNxtApp.Core.Module.Theme - 1.0.9-Beta;JMeter - 5.0.0</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""JavaScript"",""packageName"":""twitter-bootstrap"",""packageVersion"":""3.1.1"",""isTransitiveDependency"":false,""dependencyTree"":""twitter-bootstrap:3.1.1"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""Bootstrap - v3.4.0;NorDroN.AngularTemplate - 0.1.6;Dynamic.NET.Express.ProjectTemplates - 0.8.0;dotnetng.template - 1.0.0.4;ZNxtApp.Core.Module.Theme - 1.0.9-Beta;JMeter - 5.0.0""}],""vulnerabilityIdentifier"":""CVE-2018-20677"",""vulnerabilityDetails"":""In Bootstrap before 3.4.0, XSS is possible in the affix configuration target property."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20677"",""cvss3Severity"":""medium"",""cvss3Score"":""6.1"",""cvss3Metrics"":{""A"":""None"",""AC"":""Low"",""PR"":""None"",""S"":""Changed"",""C"":""Low"",""UI"":""Required"",""AV"":""Network"",""I"":""Low""},""extraData"":{}}</REMEDIATE> -->",True,"CVE-2018-20677 (Medium) detected in bootstrap-3.1.1.min.js - ## CVE-2018-20677 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>bootstrap-3.1.1.min.js</b></p></summary>

<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href=""https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.min.js"">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.min.js</a></p>
<p>Path to vulnerable library: WebGoat/webgoat-container/src/main/resources/static/plugins/bootstrap/js/bootstrap.min.js,WebGoat/webgoat-lessons/challenge/src/main/resources/js/bootstrap.min.js,WebGoat/webgoat-container/target/classes/static/plugins/bootstrap/js/bootstrap.min.js</p>
<p>

Dependency Hierarchy:
  - :x: **bootstrap-3.1.1.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/TreyM-WSS/WebGoat/commit/0b6b6b4926a0f3f0d2dbbe6647e362afe5390cc0"">0b6b6b4926a0f3f0d2dbbe6647e362afe5390cc0</a></p>
<p>Found in base branch: <b>develop</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
In Bootstrap before 3.4.0, XSS is possible in the affix configuration target property.

<p>Publish Date: 2019-01-09
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20677>CVE-2018-20677</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Changed
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20677"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20677</a></p>
<p>Release Date: 2019-01-09</p>
<p>Fix Resolution: Bootstrap - v3.4.0;NorDroN.AngularTemplate - 0.1.6;Dynamic.NET.Express.ProjectTemplates - 0.8.0;dotnetng.template - 1.0.0.4;ZNxtApp.Core.Module.Theme - 1.0.9-Beta;JMeter - 5.0.0</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""JavaScript"",""packageName"":""twitter-bootstrap"",""packageVersion"":""3.1.1"",""isTransitiveDependency"":false,""dependencyTree"":""twitter-bootstrap:3.1.1"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""Bootstrap - v3.4.0;NorDroN.AngularTemplate - 0.1.6;Dynamic.NET.Express.ProjectTemplates - 0.8.0;dotnetng.template - 1.0.0.4;ZNxtApp.Core.Module.Theme - 1.0.9-Beta;JMeter - 5.0.0""}],""vulnerabilityIdentifier"":""CVE-2018-20677"",""vulnerabilityDetails"":""In Bootstrap before 3.4.0, XSS is possible in the affix configuration target property."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20677"",""cvss3Severity"":""medium"",""cvss3Score"":""6.1"",""cvss3Metrics"":{""A"":""None"",""AC"":""Low"",""PR"":""None"",""S"":""Changed"",""C"":""Low"",""UI"":""Required"",""AV"":""Network"",""I"":""Low""},""extraData"":{}}</REMEDIATE> -->",0,cve      medium  detected in bootstrap       min js      cve       medium severity vulnerability     vulnerable library    bootstrap       min js      the most popular front end framework for developing responsive  mobile first projects on the web    library home page   a href     path to vulnerable library  webgoat webgoat container src main resources static plugins bootstrap js bootstrap min js webgoat webgoat lessons challenge src main resources js bootstrap min js webgoat webgoat container target classes static plugins bootstrap js bootstrap min js     dependency hierarchy       x    bootstrap       min js    vulnerable library   found in head commit   a href     found in base branch   develop              vulnerability details         in bootstrap before        xss is possible in the affix configuration target property    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  required     scope  changed   impact metrics      confidentiality impact  low     integrity impact  low     availability impact  none   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  bootstrap         nordron angulartemplate         dynamic net express projecttemplates         dotnetng template           znxtapp core module theme         beta jmeter                      isopenpronvulnerability  true  ispackagebased  true  isdefaultbranch  true  packages     vulnerabilityidentifier   cve       vulnerabilitydetails   in bootstrap before        xss is possible in the affix configuration target property    vulnerabilityurl        ,0
708087,24329537508.0,IssuesEvent,2022-09-30 17:59:57,roujiawang/me203fun,https://api.github.com/repos/roujiawang/me203fun,opened,Jekyll remote theme 'Agency' not working for posts not in the default '_posts' folder,enhancement priority: nice to have,"**Description**
I was trying to change the Jekyll (remote) theme of this website to [Agency](https://jekyllthemes.io/theme/agency-jekyll-theme). 
However, after having set up `Gemfile` and `_config.yml` per tutorial on [jekyllthemes.org](http://jekyllthemes.org/themes/agency/ ""curious that the url begins with http:// instead of https://""), **[LOCALLY](https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll)** the web page corresponding to the post in the folder `_people` displayed in an unorganized format despite that the theme displayed correctly on the web page corresponding to the post in the folder `_posts`.
This does not happen currently as I am using the default theme [minima](https://github.com/jekyll/minima) as one of those themes by default [supported by GitHub Pages](https://pages.github.com/themes/).<br>
**Question**
It would be helpful to figure out a way to apply the Jekyll (remote) theme to all posts of the website that are in valid folders, even when I'm not using one of those default themes.",1.0,"Jekyll remote theme 'Agency' not working for posts not in the default '_posts' folder - **Description**
I was trying to change the Jekyll (remote) theme of this website to [Agency](https://jekyllthemes.io/theme/agency-jekyll-theme). 
However, after having set up `Gemfile` and `_config.yml` per tutorial on [jekyllthemes.org](http://jekyllthemes.org/themes/agency/ ""curious that the url begins with http:// instead of https://""), **[LOCALLY](https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll)** the web page corresponding to the post in the folder `_people` displayed in an unorganized format despite that the theme displayed correctly on the web page corresponding to the post in the folder `_posts`.
This does not happen currently as I am using the default theme [minima](https://github.com/jekyll/minima) as one of those themes by default [supported by GitHub Pages](https://pages.github.com/themes/).<br>
**Question**
It would be helpful to figure out a way to apply the Jekyll (remote) theme to all posts of the website that are in valid folders, even when I'm not using one of those default themes.",0,jekyll remote theme  agency  not working for posts not in the default   posts  folder     description    i was trying to change the jekyll  remote  theme of this website to       however  after having set up  gemfile  and   config yml  per tutorial on      curious that the url begins with http    instead of         the web page corresponding to the post in the folder   people  displayed in an unorganized format despite that the theme displayed correctly on the web page corresponding to the post in the folder   posts    this does not happen currently as i am using the default theme     as one of those themes by default        question    it would be helpful to figure out a way to apply the jekyll  remote  theme to all posts of the website that are in valid folders  even when i m not using one of those default themes ,0
119994,15688278824.0,IssuesEvent,2021-03-25 14:31:49,ampproject/amphtml,https://api.github.com/repos/ampproject/amphtml,closed,Design Review 2021-03-24 16:30 UTC (Africa/Europe/western Asia),Type: Design Review,"Time: [2021-03-24 16:30 UTC](https://www.timeanddate.com/worldclock/meeting.html?year=2021&month=03&day=24&iv=0) ([add to Google Calendar](https://calendar.google.com/calendar/u/0/r/eventedit?text=AMP+Project+Design+Review&dates=20210324T163000Z/20210324T173000Z&details=https://bit.ly/amp-dr&sf=true
))
Location: [Video conference via Google Meet](https://bit.ly/amp-dr)

The AMP community holds weekly engineering [design reviews](https://github.com/ampproject/amphtml/blob/master/contributing/design-reviews.md).  **We encourage everyone in the community to participate in these design reviews.**

If you are interested in bringing your design to design review, read the [design review documentation](https://github.com/ampproject/amphtml/blob/master/contributing/design-reviews.md) and add a link to your design doc or issue by the Monday before your design review.

When attending a design review please read through the designs *before* the design review starts.  This allows us to spend more time on discussion of the design.

We rotate our design review between times that work better for different parts of the world as described in our [design review documentation](https://github.com/ampproject/amphtml/blob/master/contributing/design-reviews.md), but you are welcome to attend any design review.  If you cannot make any of the design reviews but have a design to discuss please let mrjoro@ know on [Slack](https://github.com/ampproject/amphtml/blob/master/CONTRIBUTING.md#discussion-channels) and we will find a time that works for you.",1.0,"Design Review 2021-03-24 16:30 UTC (Africa/Europe/western Asia) - Time: [2021-03-24 16:30 UTC](https://www.timeanddate.com/worldclock/meeting.html?year=2021&month=03&day=24&iv=0) ([add to Google Calendar](https://calendar.google.com/calendar/u/0/r/eventedit?text=AMP+Project+Design+Review&dates=20210324T163000Z/20210324T173000Z&details=https://bit.ly/amp-dr&sf=true
))
Location: [Video conference via Google Meet](https://bit.ly/amp-dr)

The AMP community holds weekly engineering [design reviews](https://github.com/ampproject/amphtml/blob/master/contributing/design-reviews.md).  **We encourage everyone in the community to participate in these design reviews.**

If you are interested in bringing your design to design review, read the [design review documentation](https://github.com/ampproject/amphtml/blob/master/contributing/design-reviews.md) and add a link to your design doc or issue by the Monday before your design review.

When attending a design review please read through the designs *before* the design review starts.  This allows us to spend more time on discussion of the design.

We rotate our design review between times that work better for different parts of the world as described in our [design review documentation](https://github.com/ampproject/amphtml/blob/master/contributing/design-reviews.md), but you are welcome to attend any design review.  If you cannot make any of the design reviews but have a design to discuss please let mrjoro@ know on [Slack](https://github.com/ampproject/amphtml/blob/master/CONTRIBUTING.md#discussion-channels) and we will find a time that works for you.",0,design review           utc  africa europe western asia    time                location         the amp community holds weekly engineering        we encourage everyone in the community to participate in these design reviews       if you are interested in bringing your design to design review  read the     and add a link to your design doc or issue by the monday before your design review     when attending a design review please read through the designs  before  the design review starts   this allows us to spend more time on discussion of the design     we rotate our design review between times that work better for different parts of the world as described in our     but you are welcome to attend any design review   if you cannot make any of the design reviews but have a design to discuss please let mrjoro  know on     and we will find a time that works for you ,0
48578,7444787440.0,IssuesEvent,2018-03-28 00:31:51,golang/go,https://api.github.com/repos/golang/go,closed,regexp: document that in *All if n < 0 means return all matches,Documentation help wanted,"I was just working on a simple login router and while examining regexp.FindAllString, I had to use the common knowledge that usually when you ask for n<0, that means return all the matches. However, this isn't intuitive to everyone. Perhaps let's document it.

<img width=""909"" alt=""screen shot 2018-03-25 at 2 45 03 pm"" src=""https://user-images.githubusercontent.com/4898263/37879778-3250fa64-303b-11e8-8b69-c2133d73b3ec.png"">

Sharing this with my other team members who might not be experienced would definitely lead to confusion as in https://play.golang.org/p/5J4Me7dgNML",1.0,"regexp: document that in *All if n < 0 means return all matches - I was just working on a simple login router and while examining regexp.FindAllString, I had to use the common knowledge that usually when you ask for n<0, that means return all the matches. However, this isn't intuitive to everyone. Perhaps let's document it.

<img width=""909"" alt=""screen shot 2018-03-25 at 2 45 03 pm"" src=""https://user-images.githubusercontent.com/4898263/37879778-3250fa64-303b-11e8-8b69-c2133d73b3ec.png"">

Sharing this with my other team members who might not be experienced would definitely lead to confusion as in https://play.golang.org/p/5J4Me7dgNML",1,regexp  document that in  all if n     means return all matches   i was just working on a simple login router and while examining regexp findallstring  i had to use the common knowledge that usually when you ask for n    that means return all the matches  however  this isn t intuitive to everyone  perhaps let s document it      img width     alt  screen shot       at       pm  src       sharing this with my other team members who might not be experienced would definitely lead to confusion as in  ,1
487630,14049514126.0,IssuesEvent,2020-11-02 10:22:59,AY2021S1-CS2103-F10-1/tp,https://api.github.com/repos/AY2021S1-CS2103-F10-1/tp,closed,[PE-D] Date time formatting for Trainings,priority.High,"I think one of the bugs is in handling of the date-time formats.

For the date 2021-02-32, it is an invalid format whilst adding 2021-02-31 gives us a rounding off to 2021-02-28, and when i try to add 2021-02-31 again it says the date is already added. By right it should not even be a valid date? I think its a corner case not covered yet.


![Screenshot 2020-10-30 at 12.33.55 PM.png](https://raw.githubusercontent.com/Vielheim/ped/main/files/4b9051f8-2b0f-4527-84ba-ba25e0a0ecd8.png)


![Screenshot 2020-10-30 at 12.35.04 PM.png](https://raw.githubusercontent.com/Vielheim/ped/main/files/e59f4f66-1c09-4356-ac73-743b89dd85b3.png)




<!--session: 1604030110875-d8c12ff9-ed68-4df1-860b-61cb5f306279-->

-------------
Labels: `severity.High` `type.FunctionalityBug`
original: Vielheim/ped#4",1.0,"[PE-D] Date time formatting for Trainings - I think one of the bugs is in handling of the date-time formats.

For the date 2021-02-32, it is an invalid format whilst adding 2021-02-31 gives us a rounding off to 2021-02-28, and when i try to add 2021-02-31 again it says the date is already added. By right it should not even be a valid date? I think its a corner case not covered yet.


![Screenshot 2020-10-30 at 12.33.55 PM.png](https://raw.githubusercontent.com/Vielheim/ped/main/files/4b9051f8-2b0f-4527-84ba-ba25e0a0ecd8.png)


![Screenshot 2020-10-30 at 12.35.04 PM.png](https://raw.githubusercontent.com/Vielheim/ped/main/files/e59f4f66-1c09-4356-ac73-743b89dd85b3.png)




<!--session: 1604030110875-d8c12ff9-ed68-4df1-860b-61cb5f306279-->

-------------
Labels: `severity.High` `type.FunctionalityBug`
original: Vielheim/ped#4",0,  date time formatting for trainings   i think one of the bugs is in handling of the date time formats   for the date        it is an invalid format whilst adding       gives us a rounding off to        and when i try to add       again it says the date is already added  by right it should not even be a valid date  i think its a corner case not covered yet                                     labels   severity high   type functionalitybug  original  vielheim ped  ,0
16244,4030114778.0,IssuesEvent,2016-05-18 13:18:05,golang/go,https://api.github.com/repos/golang/go,closed,"doc: Clarify what code is referred in the ""Pointers vs. Values"" section of Effective Go",Documentation,"![Pointers vs. Values section of Effective Go document](https://cloud.githubusercontent.com/assets/6612636/13546602/d39a73ae-e2dc-11e5-8f01-d89fe0a40181.png)
[`Append`](https://tip.golang.org/doc/effective_go.html#append) section is a few screens before [`Pointers vs. Values`](https://tip.golang.org/doc/effective_go.html#pointers_vs_values) and (1) is easy to miss. It is therefore not clear for the reader what code is referred in the comment of snippet (2) and subsequent ones. At least, that was my experience.

I would, transform (1) into a link to `#append` (to attract reader's attention and clarify what exactly `Append` is meant) and change (2) to something like:
```diff
- // Body exactly the same as above
+ // Body is exactly the same as described in the Append section above.
```
",1.0,"doc: Clarify what code is referred in the ""Pointers vs. Values"" section of Effective Go - ![Pointers vs. Values section of Effective Go document](https://cloud.githubusercontent.com/assets/6612636/13546602/d39a73ae-e2dc-11e5-8f01-d89fe0a40181.png)
[`Append`](https://tip.golang.org/doc/effective_go.html#append) section is a few screens before [`Pointers vs. Values`](https://tip.golang.org/doc/effective_go.html#pointers_vs_values) and (1) is easy to miss. It is therefore not clear for the reader what code is referred in the comment of snippet (2) and subsequent ones. At least, that was my experience.

I would, transform (1) into a link to `#append` (to attract reader's attention and clarify what exactly `Append` is meant) and change (2) to something like:
```diff
- // Body exactly the same as above
+ // Body is exactly the same as described in the Append section above.
```
",1,doc  clarify what code is referred in the  pointers vs  values  section of effective go             section is a few screens before     and     is easy to miss  it is therefore not clear for the reader what code is referred in the comment of snippet     and subsequent ones  at least  that was my experience     i would  transform     into a link to   append   to attract reader s attention and clarify what exactly  append  is meant  and change     to something like      diff       body exactly the same as above       body is exactly the same as described in the append section above        ,1
269867,8443997285.0,IssuesEvent,2018-10-18 17:07:20,cosmos/voyager,https://api.github.com/repos/cosmos/voyager,closed,Migrate to latest SDK develop,high priority,"In order to start on governance we should migrate to the latest SDK code.

Concerns:
- [ ] we will probably not be able to connect to gaia-8001 after",1.0,"Migrate to latest SDK develop - In order to start on governance we should migrate to the latest SDK code.

Concerns:
- [ ] we will probably not be able to connect to gaia-8001 after",0,migrate to latest sdk develop   in order to start on governance we should migrate to the latest sdk code     concerns       we will probably not be able to connect to gaia   after,0
55814,8031414597.0,IssuesEvent,2018-07-28 01:16:07,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: `go help mod` should mention `go help module`,Documentation NeedsFix modules,"go version devel +5f5402b Tue Jul 24 23:54:08 2018 +0000 linux/amd64

The help for `go help mod` should mention the existence of the modules help page
which contains crucial information about GO111MODULE and how modules work.
I didn't know that existed until I grepped for GO111 in the Go source tree and found
that help text.

Perhaps if #26581 was addressed, then the output of `go help mod` could be the same as that of `go help modules` now, as well as mentioning the subcommands.",1.0,"cmd/go: `go help mod` should mention `go help module` - go version devel +5f5402b Tue Jul 24 23:54:08 2018 +0000 linux/amd64

The help for `go help mod` should mention the existence of the modules help page
which contains crucial information about GO111MODULE and how modules work.
I didn't know that existed until I grepped for GO111 in the Go source tree and found
that help text.

Perhaps if #26581 was addressed, then the output of `go help mod` could be the same as that of `go help modules` now, as well as mentioning the subcommands.",1,cmd go   go help mod  should mention  go help module    go version devel    tue jul              linux      the help for  go help mod  should mention the existence of the modules help page  which contains crucial information about   and how modules work   i didn t know that existed until i grepped for   in the go source tree and found  that help text     perhaps if    was addressed  then the output of  go help mod  could be the same as that of  go help modules  now  as well as mentioning the subcommands ,1
603293,18536950843.0,IssuesEvent,2021-10-21 12:34:10,knative/docs,https://api.github.com/repos/knative/docs,opened," Create a new section for the website called ""Code Samples""",kind/good-first-issue priority/high,"### Context 
During the Card Sort, many folks grouped the code samples under a ""Code samples"" section, see https://miro.com/app/board/o9J_l1Iv2e4=/ 

### Story 
**As a** Knative user 
**I want** to have a go-to place for Knative code samples
**So that** I can more easily find all of the samples

### Acceptance Criteria
- [ ] Create new site-wide Subheading
```
GIVEN I have arrived at the Knative homepage 
WHEN I look at the top Nav 
THEN I see a ""Code samples"" tab to the right of ""Knative Eventing"" 
```

---

- [ ] Move all code samples from the Serving and Eventing guides including `samples.md` as the overview page.
```
GIVEN I have clicked on the ""Code samples"" tab 
WHEN I look at the left-hand side navigation
THEN I see all of the content that is currently under ""Code samples"" in the Serving and Eventing guides 
AND WHEN I look at the Serving and Eventing guides 
THEN I see that content no longer appears there
```

---

- [ ] Match directory structure to site structure 
```
GIVEN All of the above changes have been made
WHEN I look at the file structure 
THEN it makes sense considering the site changes that have been made
```

---

- [ ] Fix existing links to this content 
```
GIVEN all of the content has already been moved from elsewhere into the Code samples section
WHEN I try to access any URL linking to the content's previous location
THEN I am taken the to content's new location
```
",1.0," Create a new section for the website called ""Code Samples"" - ### Context 
During the Card Sort, many folks grouped the code samples under a ""Code samples"" section, see https://miro.com/app/board/o9J_l1Iv2e4=/ 

### Story 
**As a** Knative user 
**I want** to have a go-to place for Knative code samples
**So that** I can more easily find all of the samples

### Acceptance Criteria
- [ ] Create new site-wide Subheading
```
GIVEN I have arrived at the Knative homepage 
WHEN I look at the top Nav 
THEN I see a ""Code samples"" tab to the right of ""Knative Eventing"" 
```

---

- [ ] Move all code samples from the Serving and Eventing guides including `samples.md` as the overview page.
```
GIVEN I have clicked on the ""Code samples"" tab 
WHEN I look at the left-hand side navigation
THEN I see all of the content that is currently under ""Code samples"" in the Serving and Eventing guides 
AND WHEN I look at the Serving and Eventing guides 
THEN I see that content no longer appears there
```

---

- [ ] Match directory structure to site structure 
```
GIVEN All of the above changes have been made
WHEN I look at the file structure 
THEN it makes sense considering the site changes that have been made
```

---

- [ ] Fix existing links to this content 
```
GIVEN all of the content has already been moved from elsewhere into the Code samples section
WHEN I try to access any URL linking to the content's previous location
THEN I am taken the to content's new location
```
",0, create a new section for the website called  code samples        context   during the card sort  many folks grouped the code samples under a  code samples  section  see           story     as a   knative user     i want   to have a go to place for knative code samples    so that   i can more easily find all of the samples        acceptance criteria      create new site wide subheading       given i have arrived at the knative homepage   when i look at the top nav   then i see a  code samples  tab to the right of  knative eventing                      move all code samples from the serving and eventing guides including  samples md  as the overview page        given i have clicked on the  code samples  tab   when i look at the left hand side navigation  then i see all of the content that is currently under  code samples  in the serving and eventing guides   and when i look at the serving and eventing guides   then i see that content no longer appears there                    match directory structure to site structure        given all of the above changes have been made  when i look at the file structure   then it makes sense considering the site changes that have been made                    fix existing links to this content        given all of the content has already been moved from elsewhere into the code samples section  when i try to access any url linking to the content s previous location  then i am taken the to content s new location       ,0
242012,18509320577.0,IssuesEvent,2021-10-19 23:23:39,golang/go,https://api.github.com/repos/golang/go,closed,net/http: document that ProxyFromEnvironment also ignores loopback addresses,Documentation help wanted NeedsFix,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?
go version go1.11.12 linux/amd64 (but the code seems to indicate that this also happens on master).

This also seems to be affecting all platforms.

### What did you do?
I set the local proxy to some address. The address does not really matter, because the client never connects to it (unexpected). http.Get to the loopback ip: 127.0.0.1 or [::1].

<!--
export http_client=http://example.org:55555
go run https://play.golang.org/p/BWIUSYCivyg
-->

### What did you expect to see?

Since the docs [1](https://golang.org/pkg/net/http/#ProxyFromEnvironment), [2](https://godoc.org/golang.org/x/net/http/httpproxy#Config.ProxyFunc) specifically mention that only requests who's req.URL.Host is `localhost` get ignored (not proxied), it is to be expected that the loopback would still work (e.g. `127.0.0.1` or `[::1]`). Instead, [the code](https://github.com/golang/net/blob/master/http/httpproxy/proxy.go#L188) ensures that the Host is neither localhost nor any loopback ip.

### What did you see instead?

The request never made it to the proxy, it went to the website directly. (I expected to see something along those lines: cannot connect to proxy example.org:12345) but got: Get http://127.0.0.1: dial tcp 127.0.0.1:80: connect: connection refused.

---

The documentation should be updated to point out that any loopback ip address will also get ignored. It would also be helpful to post the workaround mentioned [here](https://github.com/golang/go/issues/7256#issuecomment-66090979) where it was discussed why localhost is ignored and how to ""disable"" that (using localhost.localdomain or localhost4, which is available on every linux machine works fine). That would have saved me quit a bit of time since the thread was hard to find.

It would probably be also worth discussing why this was implemented in the first place. If you don't want to use a proxy, there are several ways to do it (set `Transport.Proxy = nil` or set the environment variable `noproxy`). This makes debugging client requests harder then it needs to be (I find it easiest to use mitm-proxy to verify that all headers, etc are set correctly).",1.0,"net/http: document that ProxyFromEnvironment also ignores loopback addresses - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?
go version go1.11.12 linux/amd64 (but the code seems to indicate that this also happens on master).

This also seems to be affecting all platforms.

### What did you do?
I set the local proxy to some address. The address does not really matter, because the client never connects to it (unexpected). http.Get to the loopback ip: 127.0.0.1 or [::1].

<!--
export http_client=http://example.org:55555
go run https://play.golang.org/p/BWIUSYCivyg
-->

### What did you expect to see?

Since the docs [1](https://golang.org/pkg/net/http/#ProxyFromEnvironment), [2](https://godoc.org/golang.org/x/net/http/httpproxy#Config.ProxyFunc) specifically mention that only requests who's req.URL.Host is `localhost` get ignored (not proxied), it is to be expected that the loopback would still work (e.g. `127.0.0.1` or `[::1]`). Instead, [the code](https://github.com/golang/net/blob/master/http/httpproxy/proxy.go#L188) ensures that the Host is neither localhost nor any loopback ip.

### What did you see instead?

The request never made it to the proxy, it went to the website directly. (I expected to see something along those lines: cannot connect to proxy example.org:12345) but got: Get http://127.0.0.1: dial tcp 127.0.0.1:80: connect: connection refused.

---

The documentation should be updated to point out that any loopback ip address will also get ignored. It would also be helpful to post the workaround mentioned [here](https://github.com/golang/go/issues/7256#issuecomment-66090979) where it was discussed why localhost is ignored and how to ""disable"" that (using localhost.localdomain or localhost4, which is available on every linux machine works fine). That would have saved me quit a bit of time since the thread was hard to find.

It would probably be also worth discussing why this was implemented in the first place. If you don't want to use a proxy, there are several ways to do it (set `Transport.Proxy = nil` or set the environment variable `noproxy`). This makes debugging client requests harder then it needs to be (I find it easiest to use mitm-proxy to verify that all headers, etc are set correctly).",1,net http  document that proxyfromenvironment also ignores loopback addresses            what version of go are you using   go version     go version       linux    but the code seems to indicate that this also happens on master      this also seems to be affecting all platforms         what did you do   i set the local proxy to some address  the address does not really matter  because the client never connects to it  unexpected   http get to the loopback ip          or             export http client    go run               what did you expect to see     since the docs         specifically mention that only requests who s req url host is  localhost  get ignored  not proxied   it is to be expected that the loopback would still work  e g            or       instead      ensures that the host is neither localhost nor any loopback ip         what did you see instead     the request never made it to the proxy  it went to the website directly   i expected to see something along those lines  cannot connect to proxy example org    but got  get   dial tcp            connect  connection refused            the documentation should be updated to point out that any loopback ip address will also get ignored  it would also be helpful to post the workaround mentioned     where it was discussed why localhost is ignored and how to  disable  that  using localhost localdomain or    which is available on every linux machine works fine   that would have saved me quit a bit of time since the thread was hard to find     it would probably be also worth discussing why this was implemented in the first place  if you don t want to use a proxy  there are several ways to do it  set  transport proxy   nil  or set the environment variable  noproxy    this makes debugging client requests harder then it needs to be  i find it easiest to use mitm proxy to verify that all headers  etc are set correctly  ,1
126850,17114279978.0,IssuesEvent,2021-07-11 01:54:57,EnigmaDragons/ProjectNeon,https://api.github.com/repos/EnigmaDragons/ProjectNeon,closed,Clinic Corps,design,"at least 2 clinic corps
clinic corps should either differ in pricing model or service provided in addition they need a logo and color",1.0,"Clinic Corps - at least 2 clinic corps
clinic corps should either differ in pricing model or service provided in addition they need a logo and color",0,clinic corps   at least   clinic corps  clinic corps should either differ in pricing model or service provided in addition they need a logo and color,0
386963,11453870085.0,IssuesEvent,2020-02-06 16:06:11,googlemaps/android-maps-utils,https://api.github.com/repos/googlemaps/android-maps-utils,closed,KML style not working for polygon fill,priority: p1 type: bug,"I am currently getting black polygon straight lines in maps after adding the KML layer and it was not at all looking good. 

But in ios it was loaded with nice colors and without any black lines ... showing the KML layer like a heat map.. which is looking good.

So, is the KML utility for android not yet fully rolled or is this a bug?",1.0,"KML style not working for polygon fill - I am currently getting black polygon straight lines in maps after adding the KML layer and it was not at all looking good. 

But in ios it was loaded with nice colors and without any black lines ... showing the KML layer like a heat map.. which is looking good.

So, is the KML utility for android not yet fully rolled or is this a bug?",0,kml style not working for polygon fill   i am currently getting black polygon straight lines in maps after adding the kml layer and it was not at all looking good      but in ios it was loaded with nice colors and without any black lines     showing the kml layer like a heat map   which is looking good     so  is the kml utility for android not yet fully rolled or is this a bug ,0
333823,29811757827.0,IssuesEvent,2023-06-16 15:35:01,anoma/juvix,https://api.github.com/repos/anoma/juvix,closed,Update to the new version of VampIR in the tests and the CI,CI test-suite pipeline:vampir,"The latest version of VampIR on the main branch:
* supports the `-q` flag to suppress message printing,
* correctly returns non-zero exit code on verification error.

We should create a tag for VampIR 0.1.3 and use this version. Currently, verification errors are not checked by the tests, because the 0.1.2 version of VampIR always returns zero exit code on verification, even if there is an error.
",1.0,"Update to the new version of VampIR in the tests and the CI - The latest version of VampIR on the main branch:
* supports the `-q` flag to suppress message printing,
* correctly returns non-zero exit code on verification error.

We should create a tag for VampIR 0.1.3 and use this version. Currently, verification errors are not checked by the tests, because the 0.1.2 version of VampIR always returns zero exit code on verification, even if there is an error.
",0,update to the new version of vampir in the tests and the ci   the latest version of vampir on the main branch     supports the   q  flag to suppress message printing     correctly returns non zero exit code on verification error     we should create a tag for vampir       and use this version  currently  verification errors are not checked by the tests  because the       version of vampir always returns zero exit code on verification  even if there is an error   ,0
32467,6065945794.0,IssuesEvent,2017-06-14 17:21:38,golang/go,https://api.github.com/repos/golang/go,closed,time: documentation sends mixed signals regarding == operator on time.Time values,Documentation,"On tip, in `time` package documentation, there are currently at least 3 places that talk about the == operator on `time.Time` values. They've been added at different times and are somewhat out of sync, sending mixed signals about status of == operator on `time.Time` values.

1.	As part of [`time.Time.Equal`](http://tip.golang.org/pkg/time/#Time.Equal) method documentation, [modified 4 months ago](https://go-review.googlesource.com/c/32411/) from:

	```
	// Note that using == with Time values produces unpredictable results.
	```

	To:

	```
	// Do not use == with Time values.
	```

2.	As part of [`time.Time`](http://tip.golang.org/pkg/time/#Time) type documentation, [added 3 years ago](https://github.com/golang/go/commit/cfae41ff36d833719b073d1eec5f0fd535ca9e61):

	```
	// Note that the Go == operator compares not just the time instant but also the
	// Location. Therefore, Time values should not be used as map or database keys
	// without first guaranteeing that the identical Location has been set for all
	// values, which can be achieved through use of the UTC or Local method.
	```

3.	As part of [package comment](http://tip.golang.org/pkg/time/#pkg-overview), [added a month ago](https://github.com/golang/go/commit/0e3355903d2ebcf5ee9e76096f51ac9a116a9dbb):

	```
	// Note that the Go == operator includes the monotonic clock reading in
	// its comparison. If time values returned from time.Now and time values
	// constructed by other means (for example, by time.Parse or time.Unix)
	// are meant to compare equal when used as map keys, the times returned
	// by time.Now must have the monotonic clock reading stripped, by setting
	// t = t.AddDate(0, 0, 0). In general, prefer t.Equal(u) to t == u, since
	// t.Equal uses the most accurate comparison available and correctly
	// handles the case when only one of its arguments has a monotonic clock
	// reading.
	```

	(I like this version the best, it seems most accurate, clear and well-phrased. It's also the latest touched and mentions the recent monotonic support.)

This issue is primarily about the following phrase:

> Do not use == with Time values.

Which was added on Oct 30, 2016 as part of [CL 32411](https://golang.org/cl/32411), and the commit message was:

> time: simplify: tell people to not use == with Time values

When I first saw that, I understood that to mean that valid Go code should never use == operator on `time.Time` values. I [filed a suggestion](https://github.com/dominikh/go-tools/issues/47) in staticcheck to detect and report instances of == operator being used on `time.Time` values, but in the discussion there it turned out that using == operator on `time.Time` values is okay given certain precautions are taken. As I understand it, the actual reality is that people should ""prefer Time.Equal"" but it's not illegal to use == operator, one just needs to be aware of certain rules.

""Do not use == with Time values."" means something very different and doesn't seem to accurately represent the current state. This phrase is much better:

> In general, prefer t.Equal(u) to t == u, since ...",1.0,"time: documentation sends mixed signals regarding == operator on time.Time values - On tip, in `time` package documentation, there are currently at least 3 places that talk about the == operator on `time.Time` values. They've been added at different times and are somewhat out of sync, sending mixed signals about status of == operator on `time.Time` values.

1.	As part of [`time.Time.Equal`](http://tip.golang.org/pkg/time/#Time.Equal) method documentation, [modified 4 months ago](https://go-review.googlesource.com/c/32411/) from:

	```
	// Note that using == with Time values produces unpredictable results.
	```

	To:

	```
	// Do not use == with Time values.
	```

2.	As part of [`time.Time`](http://tip.golang.org/pkg/time/#Time) type documentation, [added 3 years ago](https://github.com/golang/go/commit/cfae41ff36d833719b073d1eec5f0fd535ca9e61):

	```
	// Note that the Go == operator compares not just the time instant but also the
	// Location. Therefore, Time values should not be used as map or database keys
	// without first guaranteeing that the identical Location has been set for all
	// values, which can be achieved through use of the UTC or Local method.
	```

3.	As part of [package comment](http://tip.golang.org/pkg/time/#pkg-overview), [added a month ago](https://github.com/golang/go/commit/0e3355903d2ebcf5ee9e76096f51ac9a116a9dbb):

	```
	// Note that the Go == operator includes the monotonic clock reading in
	// its comparison. If time values returned from time.Now and time values
	// constructed by other means (for example, by time.Parse or time.Unix)
	// are meant to compare equal when used as map keys, the times returned
	// by time.Now must have the monotonic clock reading stripped, by setting
	// t = t.AddDate(0, 0, 0). In general, prefer t.Equal(u) to t == u, since
	// t.Equal uses the most accurate comparison available and correctly
	// handles the case when only one of its arguments has a monotonic clock
	// reading.
	```

	(I like this version the best, it seems most accurate, clear and well-phrased. It's also the latest touched and mentions the recent monotonic support.)

This issue is primarily about the following phrase:

> Do not use == with Time values.

Which was added on Oct 30, 2016 as part of [CL 32411](https://golang.org/cl/32411), and the commit message was:

> time: simplify: tell people to not use == with Time values

When I first saw that, I understood that to mean that valid Go code should never use == operator on `time.Time` values. I [filed a suggestion](https://github.com/dominikh/go-tools/issues/47) in staticcheck to detect and report instances of == operator being used on `time.Time` values, but in the discussion there it turned out that using == operator on `time.Time` values is okay given certain precautions are taken. As I understand it, the actual reality is that people should ""prefer Time.Equal"" but it's not illegal to use == operator, one just needs to be aware of certain rules.

""Do not use == with Time values."" means something very different and doesn't seem to accurately represent the current state. This phrase is much better:

> In general, prefer t.Equal(u) to t == u, since ...",1,time  documentation sends mixed signals regarding    operator on time time values   on tip  in  time  package documentation  there are currently at least   places that talk about the    operator on  time time  values  they ve been added at different times and are somewhat out of sync  sending mixed signals about status of    operator on  time time  values       	as part of     method documentation      from     	     	   note that using    with time values produces unpredictable results   	       	to     	     	   do not use    with time values   	         	as part of     type documentation         	     	   note that the go    operator compares not just the time instant but also the  	   location  therefore  time values should not be used as map or database keys  	   without first guaranteeing that the identical location has been set for all  	   values  which can be achieved through use of the utc or local method   	         	as part of            	     	   note that the go    operator includes the monotonic clock reading in  	   its comparison  if time values returned from time now and time values  	   constructed by other means  for example  by time parse or time unix   	   are meant to compare equal when used as map keys  the times returned  	   by time now must have the monotonic clock reading stripped  by setting  	   t   t adddate           in general  prefer t equal u  to t    u  since  	   t equal uses the most accurate comparison available and correctly  	   handles the case when only one of its arguments has a monotonic clock  	   reading   	       	 i like this version the best  it seems most accurate  clear and well phrased  it s also the latest touched and mentions the recent monotonic support      this issue is primarily about the following phrase       do not use    with time values     which was added on oct      as part of     and the commit message was       time  simplify  tell people to not use    with time values    when i first saw that  i understood that to mean that valid go code should never use    operator on  time time  values  i     in staticcheck to detect and report instances of    operator being used on  time time  values  but in the discussion there it turned out that using    operator on  time time  values is okay given certain precautions are taken  as i understand it  the actual reality is that people should  prefer time equal  but it s not illegal to use    operator  one just needs to be aware of certain rules      do not use    with time values   means something very different and doesn t seem to accurately represent the current state  this phrase is much better       in general  prefer t equal u  to t    u  since    ,1
29974,14357327238.0,IssuesEvent,2020-11-30 12:55:05,pschachte/wybe,https://api.github.com/repos/pschachte/wybe,opened,Support parallel computation,enhancement performance research project,This also interacts with aliasing analysis and compile-time garbage collection,True,Support parallel computation - This also interacts with aliasing analysis and compile-time garbage collection,0,support parallel computation   this also interacts with aliasing analysis and compile time garbage collection,0
381687,11278587390.0,IssuesEvent,2020-01-15 07:14:31,StrangeLoopGames/EcoIssues,https://api.github.com/repos/StrangeLoopGames/EcoIssues,opened,"[0.9.0 satging-1337] Double ""Action prevented"" in error notification.",Priority: Low,"Create law with prevent effect. Do it:
![image](https://user-images.githubusercontent.com/45708377/72412946-aeb9ae00-377f-11ea-9776-1ab293f3fff6.png)
",1.0,"[0.9.0 satging-1337] Double ""Action prevented"" in error notification. - Create law with prevent effect. Do it:
![image](https://user-images.githubusercontent.com/45708377/72412946-aeb9ae00-377f-11ea-9776-1ab293f3fff6.png)
",0,  double  action prevented  in error notification    create law with prevent effect  do it         ,0
435522,12536526899.0,IssuesEvent,2020-06-05 00:22:09,eclipse-ee4j/glassfish,https://api.github.com/repos/eclipse-ee4j/glassfish,closed,Timer.getTimeRemaining() returns 10ms less with each call,Component: ejb_container ERR: Assignee Priority: Minor Stale Type: Bug,"I need to look why is it happening as the timeout method is called at regular
intervals.
#### Environment
Operating System: All
Platform: Sun
#### Affected Versions
[V3]",1.0,"Timer.getTimeRemaining() returns 10ms less with each call - I need to look why is it happening as the timeout method is called at regular
intervals.
#### Environment
Operating System: All
Platform: Sun
#### Affected Versions
[V3]",0,timer gettimeremaining   returns   less with each call   i need to look why is it happening as the timeout method is called at regular intervals       environment operating system  all platform  sun      affected versions  ,0
206733,23396862551.0,IssuesEvent,2022-08-12 01:17:41,xlizaluizax/datocms-Dating-WIKI---React-Blog,https://api.github.com/repos/xlizaluizax/datocms-Dating-WIKI---React-Blog,closed,"CVE-2021-35065 (High) detected in glob-parent-3.1.0.tgz, glob-parent-5.1.1.tgz - autoclosed",security vulnerability,"## CVE-2021-35065 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>glob-parent-3.1.0.tgz</b>, <b>glob-parent-5.1.1.tgz</b></p></summary>
<p>

<details><summary><b>glob-parent-3.1.0.tgz</b></p></summary>

<p>Strips glob magic from a string to provide the parent directory path</p>
<p>Library home page: <a href=""https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz"">https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/glob-parent/package.json</p>
<p>

Dependency Hierarchy:
  - react-scripts-3.0.1.tgz (Root Library)
    - webpack-dev-server-3.2.1.tgz
      - chokidar-2.1.8.tgz
        - :x: **glob-parent-3.1.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>glob-parent-5.1.1.tgz</b></p></summary>

<p>Extract the non-magic parent path from a glob string.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.1.tgz"">https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/watchpack/node_modules/glob-parent/package.json</p>
<p>

Dependency Hierarchy:
  - react-scripts-3.0.1.tgz (Root Library)
    - webpack-4.29.6.tgz
      - watchpack-1.7.4.tgz
        - chokidar-3.4.1.tgz
          - :x: **glob-parent-5.1.1.tgz** (Vulnerable Library)
</details>

<p>Found in HEAD commit: <a href=""https://github.com/xlizaluizax/datocms-Dating-WIKI---React-Blog/commit/f28f06b6cbc52fcdd0ce3f5eab40a431a262e08e"">f28f06b6cbc52fcdd0ce3f5eab40a431a262e08e</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The package glob-parent before  6.0.1 are vulnerable to Regular Expression Denial of Service (ReDoS) 

<p>Publish Date: 2021-06-22
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35065>CVE-2021-35065</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/advisories/GHSA-cj88-88mr-972w"">https://github.com/advisories/GHSA-cj88-88mr-972w</a></p>
<p>Release Date: 2021-06-22</p>
<p>Fix Resolution (glob-parent): 6.0.1</p>
<p>Direct dependency fix Resolution (react-scripts): 5.0.1</p><p>Fix Resolution (glob-parent): 6.0.1</p>
<p>Direct dependency fix Resolution (react-scripts): 5.0.1</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2021-35065 (High) detected in glob-parent-3.1.0.tgz, glob-parent-5.1.1.tgz - autoclosed - ## CVE-2021-35065 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>glob-parent-3.1.0.tgz</b>, <b>glob-parent-5.1.1.tgz</b></p></summary>
<p>

<details><summary><b>glob-parent-3.1.0.tgz</b></p></summary>

<p>Strips glob magic from a string to provide the parent directory path</p>
<p>Library home page: <a href=""https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz"">https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/glob-parent/package.json</p>
<p>

Dependency Hierarchy:
  - react-scripts-3.0.1.tgz (Root Library)
    - webpack-dev-server-3.2.1.tgz
      - chokidar-2.1.8.tgz
        - :x: **glob-parent-3.1.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>glob-parent-5.1.1.tgz</b></p></summary>

<p>Extract the non-magic parent path from a glob string.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.1.tgz"">https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/watchpack/node_modules/glob-parent/package.json</p>
<p>

Dependency Hierarchy:
  - react-scripts-3.0.1.tgz (Root Library)
    - webpack-4.29.6.tgz
      - watchpack-1.7.4.tgz
        - chokidar-3.4.1.tgz
          - :x: **glob-parent-5.1.1.tgz** (Vulnerable Library)
</details>

<p>Found in HEAD commit: <a href=""https://github.com/xlizaluizax/datocms-Dating-WIKI---React-Blog/commit/f28f06b6cbc52fcdd0ce3f5eab40a431a262e08e"">f28f06b6cbc52fcdd0ce3f5eab40a431a262e08e</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The package glob-parent before  6.0.1 are vulnerable to Regular Expression Denial of Service (ReDoS) 

<p>Publish Date: 2021-06-22
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35065>CVE-2021-35065</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/advisories/GHSA-cj88-88mr-972w"">https://github.com/advisories/GHSA-cj88-88mr-972w</a></p>
<p>Release Date: 2021-06-22</p>
<p>Fix Resolution (glob-parent): 6.0.1</p>
<p>Direct dependency fix Resolution (react-scripts): 5.0.1</p><p>Fix Resolution (glob-parent): 6.0.1</p>
<p>Direct dependency fix Resolution (react-scripts): 5.0.1</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in glob parent       tgz  glob parent       tgz   autoclosed      cve       high severity vulnerability     vulnerable libraries    glob parent       tgz    glob parent       tgz          glob parent       tgz      strips glob magic from a string to provide the parent directory path   library home page   a href     path to dependency file   package json   path to vulnerable library   node modules glob parent package json     dependency hierarchy      react scripts       tgz  root library        webpack dev server       tgz         chokidar       tgz            x    glob parent       tgz    vulnerable library       glob parent       tgz      extract the non magic parent path from a glob string    library home page   a href     path to dependency file   package json   path to vulnerable library   node modules watchpack node modules glob parent package json     dependency hierarchy      react scripts       tgz  root library        webpack       tgz         watchpack       tgz           chokidar       tgz              x    glob parent       tgz    vulnerable library      found in head commit   a href               vulnerability details         the package glob parent before        are vulnerable to regular expression denial of service  redos     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  glob parent           direct dependency fix resolution  react scripts          fix resolution  glob parent           direct dependency fix resolution  react scripts                       step up your open source security game with mend    ,0
3690,2539120369.0,IssuesEvent,2015-01-27 13:08:45,readium/readium-js-viewer,https://api.github.com/repos/readium/readium-js-viewer,closed,"When NCX / Navigation Document is not found, TOC pane displays Readium toolbar UI!",enhancement priority medium,"Culprit:
jQuery $(NULL/UNDEFINED).html() function!",1.0,"When NCX / Navigation Document is not found, TOC pane displays Readium toolbar UI! - Culprit:
jQuery $(NULL/UNDEFINED).html() function!",0,when ncx   navigation document is not found  toc pane displays readium toolbar ui    culprit   jquery   null undefined  html   function ,0
394736,11648062209.0,IssuesEvent,2020-03-01 18:35:14,bounswe/bounswe2020group5,https://api.github.com/repos/bounswe/bounswe2020group5,closed,Determining who asks our questions and who takes note in meeting,Priority: Medium Status: Accepted Type: Meeting question,Determining who asks our questions and who takes note etc.,1.0,Determining who asks our questions and who takes note in meeting - Determining who asks our questions and who takes note etc.,0,determining who asks our questions and who takes note in meeting   determining who asks our questions and who takes note etc ,0
55799,8030781312.0,IssuesEvent,2018-07-27 21:01:48,golang/go,https://api.github.com/repos/golang/go,closed,net/http: document filepath sanitization for ServeFile,Documentation NeedsFix Security help wanted,"This is a petty formulation issue, but the subject is quite sensitive so I thought I would bring it up. The documentation for http.ServeFile(w ResponseWriter, r *Request, name string) states that name needs to be sanitized to prevent ascension into parent directories. It further states that ServeFile rejects requests that contain "".."" as path elements.

I assume the implication of both statements combined is that patterns like
```
http.ServeFile(w, r, filepath.Join(""."", r.URL.Path))
http.ServeFile(w, r, filepath.Join(""dir"", r.URL.Path))
```
are ""safe"" in the sense that ascension into the respective parent directories is not possible.
However this is not obvious from the current documentation as there may more obscure ways of ascending than "".."" that are less obvious (I am honestly not sure).

Imo it would be a good idea to state explicitly whether the file path in the above patterns is sufficiently sanitized or not because I see only two scenarios:
-If the patterns above are not safe the current documentation may cause security problems
-If the patterns are safe some users won't take advantage of this great function because it is not explicitly stated (this is me right now).",1.0,"net/http: document filepath sanitization for ServeFile - This is a petty formulation issue, but the subject is quite sensitive so I thought I would bring it up. The documentation for http.ServeFile(w ResponseWriter, r *Request, name string) states that name needs to be sanitized to prevent ascension into parent directories. It further states that ServeFile rejects requests that contain "".."" as path elements.

I assume the implication of both statements combined is that patterns like
```
http.ServeFile(w, r, filepath.Join(""."", r.URL.Path))
http.ServeFile(w, r, filepath.Join(""dir"", r.URL.Path))
```
are ""safe"" in the sense that ascension into the respective parent directories is not possible.
However this is not obvious from the current documentation as there may more obscure ways of ascending than "".."" that are less obvious (I am honestly not sure).

Imo it would be a good idea to state explicitly whether the file path in the above patterns is sufficiently sanitized or not because I see only two scenarios:
-If the patterns above are not safe the current documentation may cause security problems
-If the patterns are safe some users won't take advantage of this great function because it is not explicitly stated (this is me right now).",1,net http  document filepath sanitization for servefile   this is a petty formulation issue  but the subject is quite sensitive so i thought i would bring it up  the documentation for http servefile w responsewriter  r  request  name string  states that name needs to be sanitized to prevent ascension into parent directories  it further states that servefile rejects requests that contain      as path elements     i assume the implication of both statements combined is that patterns like       http servefile w  r  filepath join      r url path    http servefile w  r  filepath join  dir   r url path         are  safe  in the sense that ascension into the respective parent directories is not possible   however this is not obvious from the current documentation as there may more obscure ways of ascending than      that are less obvious  i am honestly not sure      imo it would be a good idea to state explicitly whether the file path in the above patterns is sufficiently sanitized or not because i see only two scenarios    if the patterns above are not safe the current documentation may cause security problems   if the patterns are safe some users won t take advantage of this great function because it is not explicitly stated  this is me right now  ,1
80022,15586259957.0,IssuesEvent,2021-03-18 01:32:08,D-M-Moriarty/Mail-Parser,https://api.github.com/repos/D-M-Moriarty/Mail-Parser,opened,CVE-2020-5398 (High) detected in spring-web-5.0.4.RELEASE.jar,security vulnerability,"## CVE-2020-5398 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-web-5.0.4.RELEASE.jar</b></p></summary>

<p>Spring Web</p>
<p>Library home page: <a href=""https://github.com/spring-projects/spring-framework"">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /Mail-Parser/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/org/springframework/spring-web/5.0.4.RELEASE/spring-web-5.0.4.RELEASE.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-starter-web-2.0.0.RELEASE.jar (Root Library)
    - :x: **spring-web-5.0.4.RELEASE.jar** (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>  
  
In Spring Framework, versions 5.2.x prior to 5.2.3, versions 5.1.x prior to 5.1.13, and versions 5.0.x prior to 5.0.16, an application is vulnerable to a reflected file download (RFD) attack when it sets a ""Content-Disposition"" header in the response where the filename attribute is derived from user supplied input.

<p>Publish Date: 2020-01-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-5398>CVE-2020-5398</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: High
  - Privileges Required: None
  - User Interaction: Required
  - 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://pivotal.io/security/cve-2020-5398"">https://pivotal.io/security/cve-2020-5398</a></p>
<p>Release Date: 2020-01-17</p>
<p>Fix Resolution: org.springframework:spring-web:5.0.16.RELEASE,org.springframework:spring-web:5.1.13.RELEASE,org.springframework:spring-web:5.2.3.RELEASE</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-5398 (High) detected in spring-web-5.0.4.RELEASE.jar - ## CVE-2020-5398 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-web-5.0.4.RELEASE.jar</b></p></summary>

<p>Spring Web</p>
<p>Library home page: <a href=""https://github.com/spring-projects/spring-framework"">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /Mail-Parser/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/org/springframework/spring-web/5.0.4.RELEASE/spring-web-5.0.4.RELEASE.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-starter-web-2.0.0.RELEASE.jar (Root Library)
    - :x: **spring-web-5.0.4.RELEASE.jar** (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>  
  
In Spring Framework, versions 5.2.x prior to 5.2.3, versions 5.1.x prior to 5.1.13, and versions 5.0.x prior to 5.0.16, an application is vulnerable to a reflected file download (RFD) attack when it sets a ""Content-Disposition"" header in the response where the filename attribute is derived from user supplied input.

<p>Publish Date: 2020-01-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-5398>CVE-2020-5398</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: High
  - Privileges Required: None
  - User Interaction: Required
  - 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://pivotal.io/security/cve-2020-5398"">https://pivotal.io/security/cve-2020-5398</a></p>
<p>Release Date: 2020-01-17</p>
<p>Fix Resolution: org.springframework:spring-web:5.0.16.RELEASE,org.springframework:spring-web:5.1.13.RELEASE,org.springframework:spring-web:5.2.3.RELEASE</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in spring web       release jar      cve       high severity vulnerability     vulnerable library    spring web       release jar      spring web   library home page   a href     path to dependency file   mail parser pom xml   path to vulnerable library   root    repository org springframework spring web       release spring web       release jar     dependency hierarchy      spring boot starter web       release jar  root library         x    spring web       release jar    vulnerable library             vulnerability details         in spring framework  versions     x prior to        versions     x prior to        and versions     x prior to        an application is vulnerable to a reflected file download  rfd  attack when it sets a  content disposition  header in the response where the filename attribute is derived from user supplied input    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  required     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  org springframework spring web       release org springframework spring web       release org springframework spring web       release               step up your open source security game with whitesource    ,0
58180,8233632943.0,IssuesEvent,2018-09-08 03:27:50,golang/go,https://api.github.com/repos/golang/go,closed,doc/effective_go.html: select is not mentioned in control structures section,Documentation NeedsInvestigation,"### What version of Go are you using (`go version`)?
N/A ,  see https://golang.org/doc/effective_go.html#control-structures 

### Does this issue reproduce with the latest release?
N/A

### What operating system and processor architecture are you using (`go env`)?
N/A

### What did you do?
opened effective go and searched for `select`

### What did you expect to see?
documentation about the nuances and patterns of usage for select:
* Frequently used within a ""while loop"" (`for {`) 
```go
 for  {
    select {
        case o := <-one:
           fmt.Println(""one"", o)
        case o := <- two:
           fmt.Println(""two"", o)
     }
}
```
* Chooses at random if multiple available
```go
one := make(chan bool)
two := make(chan int)
go func() { one <- true }
go func() { two <- 13 }
select {
   case o := <- one:
        fmt.Println(""one"", o)
   case o := <- two:
        fmt.Println(""two"", o)
}
// Output: will randomly output either ""one true"" or ""two 13""
```

* timeout pattern: https://gobyexample.com/timeouts
* wait for N channels to close pattern: https://stackoverflow.com/a/13666733/1114274

personally, i prefer: 
```go
for o != nil && e != nil {
	select {
	case i, ok := <-o:
		if !ok {
			o = nil
		}
		fmt.Println(""o"", i)
	case i, ok := <-e:
		if !ok {
			e = nil
		}
		fmt.Println(""e"", i)
	}
}

```

### What did you see instead?
only one example in ""Leaky Buffer"" section? https://golang.org/doc/effective_go.html#leaky_buffer
",1.0,"doc/effective_go.html: select is not mentioned in control structures section - ### What version of Go are you using (`go version`)?
N/A ,  see https://golang.org/doc/effective_go.html#control-structures 

### Does this issue reproduce with the latest release?
N/A

### What operating system and processor architecture are you using (`go env`)?
N/A

### What did you do?
opened effective go and searched for `select`

### What did you expect to see?
documentation about the nuances and patterns of usage for select:
* Frequently used within a ""while loop"" (`for {`) 
```go
 for  {
    select {
        case o := <-one:
           fmt.Println(""one"", o)
        case o := <- two:
           fmt.Println(""two"", o)
     }
}
```
* Chooses at random if multiple available
```go
one := make(chan bool)
two := make(chan int)
go func() { one <- true }
go func() { two <- 13 }
select {
   case o := <- one:
        fmt.Println(""one"", o)
   case o := <- two:
        fmt.Println(""two"", o)
}
// Output: will randomly output either ""one true"" or ""two 13""
```

* timeout pattern: https://gobyexample.com/timeouts
* wait for N channels to close pattern: https://stackoverflow.com/a/13666733/1114274

personally, i prefer: 
```go
for o != nil && e != nil {
	select {
	case i, ok := <-o:
		if !ok {
			o = nil
		}
		fmt.Println(""o"", i)
	case i, ok := <-e:
		if !ok {
			e = nil
		}
		fmt.Println(""e"", i)
	}
}

```

### What did you see instead?
only one example in ""Leaky Buffer"" section? https://golang.org/doc/effective_go.html#leaky_buffer
",1,doc effective go html  select is not mentioned in control structures section       what version of go are you using   go version     n a    see           does this issue reproduce with the latest release   n a        what operating system and processor architecture are you using   go env     n a        what did you do   opened effective go and searched for  select         what did you expect to see   documentation about the nuances and patterns of usage for select     frequently used within a  while loop    for          go   for         select            case o      one              fmt println  one   o           case o       two              fmt println  two   o                     chooses at random if multiple available     go  one    make chan bool   two    make chan int   go func     one    true    go func     two         select       case o       one           fmt println  one   o      case o       two           fmt println  two   o         output  will randomly output either  one true  or  two              timeout pattern       wait for n channels to close pattern       personally  i prefer       go  for o    nil    e    nil    	select    	case i  ok      o   		if  ok    			o   nil  		   		fmt println  o   i   	case i  ok      e   		if  ok    			e   nil  		   		fmt println  e   i   	                   what did you see instead   only one example in  leaky buffer  section     ,1
33652,9199272249.0,IssuesEvent,2019-03-07 14:36:22,quicklisp/quicklisp-projects,https://api.github.com/repos/quicklisp/quicklisp-projects,closed,Please add water,canbuild,"Hello! I've developed a very small library which is designed to simplify creation of javascript classes in parenscript code because it does not have that feature included.

It should be pretty easy to build because it only depends on parenscript and it is meant to generate code which will then be executed in a javascript environment (like a browser).

https://github.com/handicraftsman/water",1.0,"Please add water - Hello! I've developed a very small library which is designed to simplify creation of javascript classes in parenscript code because it does not have that feature included.

It should be pretty easy to build because it only depends on parenscript and it is meant to generate code which will then be executed in a javascript environment (like a browser).

https://github.com/handicraftsman/water",0,please add water   hello  i ve developed a very small library which is designed to simplify creation of javascript classes in parenscript code because it does not have that feature included     it should be pretty easy to build because it only depends on parenscript and it is meant to generate code which will then be executed in a javascript environment  like a browser       ,0
90853,11439218272.0,IssuesEvent,2020-02-05 06:34:10,brave/brave-browser,https://api.github.com/repos/brave/brave-browser,closed,Style Chrome browser dialog with the Brave themed dialog component,design priority/P3,"## Description
Currently, our browser dialogs follow the default Chrome theme. We need to style them with our Brave themed dialog component and de-Chromify our browser.
",1.0,"Style Chrome browser dialog with the Brave themed dialog component - ## Description
Currently, our browser dialogs follow the default Chrome theme. We need to style them with our Brave themed dialog component and de-Chromify our browser.
",0,style chrome browser dialog with the brave themed dialog component      description  currently  our browser dialogs follow the default chrome theme  we need to style them with our brave themed dialog component and de chromify our browser   ,0
365120,25520859921.0,IssuesEvent,2022-11-28 20:20:29,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: 'go test -race' fails with 'relocation target __popcountdi2 not defined' when GCC not installed,Documentation RaceDetector NeedsFix,"### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.19.3 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/brian/.cache/go-build""
GOENV=""/home/brian/.config/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/brian/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/brian/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""go1.19.3""
GCCGO=""gccgo""
GOAMD64=""v1""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/brian/z/go.mod""
GOWORK=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build3661110452=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

NOTE: this is running on an ubuntu-minimal lxd container (22.04.1) which does not have gcc installed.

### What did you do?

```
$ cat go.mod
module example.com/test

go 1.19

$ cat main_test.go
package main

$ go test -race . -vet=off
# example.com/test.test
runtime/race(.text): relocation target __popcountdi2 not defined
FAIL	example.com/test [build failed]
FAIL
```

There is a separate but possibly related problem #56755, which is why `-vet=off` is required. Without it:

```
$ go test -race .
# runtime/cgo
cgo: C compiler ""gcc"" not found: exec: ""gcc"": executable file not found in $PATH
FAIL	example.com/test [build failed]
FAIL
```

### What did you expect to see?

Successful test execution.

Or: documentation that the race detector does not work without GCC. I checked [here](https://go.dev/blog/race-detector) and [here](https://go.dev/doc/articles/race_detector).

### What did you see instead?

See above.

Possibly relates to #3261 (old ticket, but it does reference missing `__popcountdi2` explicitly)",1.0,"cmd/go: 'go test -race' fails with 'relocation target __popcountdi2 not defined' when GCC not installed - ### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.19.3 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/brian/.cache/go-build""
GOENV=""/home/brian/.config/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/brian/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/brian/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""go1.19.3""
GCCGO=""gccgo""
GOAMD64=""v1""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/brian/z/go.mod""
GOWORK=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build3661110452=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

NOTE: this is running on an ubuntu-minimal lxd container (22.04.1) which does not have gcc installed.

### What did you do?

```
$ cat go.mod
module example.com/test

go 1.19

$ cat main_test.go
package main

$ go test -race . -vet=off
# example.com/test.test
runtime/race(.text): relocation target __popcountdi2 not defined
FAIL	example.com/test [build failed]
FAIL
```

There is a separate but possibly related problem #56755, which is why `-vet=off` is required. Without it:

```
$ go test -race .
# runtime/cgo
cgo: C compiler ""gcc"" not found: exec: ""gcc"": executable file not found in $PATH
FAIL	example.com/test [build failed]
FAIL
```

### What did you expect to see?

Successful test execution.

Or: documentation that the race detector does not work without GCC. I checked [here](https://go.dev/blog/race-detector) and [here](https://go.dev/doc/articles/race_detector).

### What did you see instead?

See above.

Possibly relates to #3261 (old ticket, but it does reference missing `__popcountdi2` explicitly)",1,cmd go   go test  race  fails with  relocation target     not defined  when gcc not installed       what version of go are you using   go version            go version  go version       linux             does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   home brian  cache go build   goenv   home brian  config go env   goexe     goexperiment     goflags     gohostarch      gohostos  linux   goinsecure     gomodcache   home brian go pkg mod   gonoproxy     gonosumdb     goos  linux   gopath   home brian go   goprivate     goproxy     goroot   usr local go   gosumdb  sum golang org   gotmpdir     gotooldir   usr local go pkg tool linux     govcs     goversion          gccgo  gccgo          ar  ar   cc  gcc   cxx  g     cgo enabled      gomod   home brian z go mod   gowork     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  wl   no gc sections  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches         note  this is running on an ubuntu minimal lxd container         which does not have gcc installed         what did you do            cat go mod  module example com test    go          cat main test go  package main      go test  race    vet off    example com test test  runtime race  text   relocation target     not defined  fail	example com test    fail         there is a separate but possibly related problem     which is why   vet off  is required  without it            go test  race      runtime cgo  cgo  c compiler  gcc  not found  exec   gcc   executable file not found in  path  fail	example com test    fail             what did you expect to see     successful test execution     or  documentation that the race detector does not work without gcc  i checked     and            what did you see instead     see above     possibly relates to     old ticket  but it does reference missing       explicitly ,1
55370,7978387939.0,IssuesEvent,2018-07-17 18:09:41,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/cmd/godoc: show which version of Go introduced symbols,Documentation FeatureRequest NeedsFix help wanted,"<pre>Go documentation is very good, but it doesn't clearly label which go version features
are available in.

For instance I was caught out by <a href=""http://golang.org/pkg/time/#Timer.Reset"">http://golang.org/pkg/time/#Timer.Reset</a> being a go 1.1
feature which meant my code would no longer compile with go 1.0.

Other examples are 

  * <a href=""http://golang.org/pkg/net/http/#Transport.CancelRequest"">http://golang.org/pkg/net/http/#Transport.CancelRequest</a>
  * ResponseHeaderTimeout in <a href=""http://golang.org/pkg/net/http/#Transport"">http://golang.org/pkg/net/http/#Transport</a></pre>
",1.0,"x/tools/cmd/godoc: show which version of Go introduced symbols - <pre>Go documentation is very good, but it doesn't clearly label which go version features
are available in.

For instance I was caught out by <a href=""http://golang.org/pkg/time/#Timer.Reset"">http://golang.org/pkg/time/#Timer.Reset</a> being a go 1.1
feature which meant my code would no longer compile with go 1.0.

Other examples are 

  * <a href=""http://golang.org/pkg/net/http/#Transport.CancelRequest"">http://golang.org/pkg/net/http/#Transport.CancelRequest</a>
  * ResponseHeaderTimeout in <a href=""http://golang.org/pkg/net/http/#Transport"">http://golang.org/pkg/net/http/#Transport</a></pre>
",1,x tools cmd godoc  show which version of go introduced symbols    go documentation is very good  but it doesn t clearly label which go version features are available in   for instance i was caught out by  a href    being a go     feature which meant my code would no longer compile with go       other examples are        a href        responseheadertimeout in  a href    ,1
32094,6031807615.0,IssuesEvent,2017-06-09 00:41:28,golang/go,https://api.github.com/repos/golang/go,opened,net/http: document SOCKS5 proxy support,Documentation,SOCKS5 proxy support was added by https://golang.org/cl/35488. Documentation should be added to net/http.,1.0,net/http: document SOCKS5 proxy support - SOCKS5 proxy support was added by https://golang.org/cl/35488. Documentation should be added to net/http.,1,net http  document   proxy support     proxy support was added by   documentation should be added to net http ,1
348794,10452850682.0,IssuesEvent,2019-09-19 15:24:44,fac-17/Plantbase-Me,https://api.github.com/repos/fac-17/Plantbase-Me,closed,Queries set-up,High Priority MVP,"GET
- [x] - getCravings
- [x] - getAllProducts
- [x] - getProductsAndRatingByCraving
- [x] - getProductAndRatingById

POST
- [x] - createProduct
- [x] - createCommentAndRating

Extra

_- [ ] - getTopRatedProducts ????_
",1.0,"Queries set-up - GET
- [x] - getCravings
- [x] - getAllProducts
- [x] - getProductsAndRatingByCraving
- [x] - getProductAndRatingById

POST
- [x] - createProduct
- [x] - createCommentAndRating

Extra

_- [ ] - getTopRatedProducts ????_
",0,queries set up   get        getcravings        getallproducts        getproductsandratingbycraving        getproductandratingbyid    post        createproduct        createcommentandrating    extra           gettopratedproducts        ,0
426585,29576891865.0,IssuesEvent,2023-06-07 00:03:31,golang/go,https://api.github.com/repos/golang/go,closed,spec: Index expressions spec is fragmented for map type code,Documentation NeedsInvestigation,"### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.20.2 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
```
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/paj/Library/Caches/go-build""
GOENV=""/Users/paj/Library/Application Support/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/paj/.asdf/installs/golang/1.20.2/packages/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/paj/.asdf/installs/golang/1.20.2/packages""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/Users/paj/.asdf/installs/golang/1.20.2/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/Users/paj/.asdf/installs/golang/1.20.2/go/pkg/tool/darwin_amd64""
GOVCS=""""
GOVERSION=""go1.20.2""
GCCGO=""gccgo""
GOAMD64=""v1""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
GOWORK=""""
CGO_CFLAGS=""-O2 -g""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-O2 -g""
CGO_FFLAGS=""-O2 -g""
CGO_LDFLAGS=""-O2 -g""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/4d/zd6b5xpn7rq00306yspzfy3r0000gn/T/go-build17349328=/tmp/go-build -gno-record-gcc-switches -fno-common""

</pre></details>

### What did you do?

Reading the Index expressions spec at https://go.dev/ref/spec#Map_types to determine how to handle the case where a key is not present in a map.

### What did you expect to see?

Information about the above.

### What did you see instead?

Information about type parameter types, introduced in 68da368a4e .

### Note

Pull request incoming.",1.0,"spec: Index expressions spec is fragmented for map type code - ### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.20.2 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
```
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/paj/Library/Caches/go-build""
GOENV=""/Users/paj/Library/Application Support/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/paj/.asdf/installs/golang/1.20.2/packages/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/paj/.asdf/installs/golang/1.20.2/packages""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/Users/paj/.asdf/installs/golang/1.20.2/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/Users/paj/.asdf/installs/golang/1.20.2/go/pkg/tool/darwin_amd64""
GOVCS=""""
GOVERSION=""go1.20.2""
GCCGO=""gccgo""
GOAMD64=""v1""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
GOWORK=""""
CGO_CFLAGS=""-O2 -g""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-O2 -g""
CGO_FFLAGS=""-O2 -g""
CGO_LDFLAGS=""-O2 -g""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/4d/zd6b5xpn7rq00306yspzfy3r0000gn/T/go-build17349328=/tmp/go-build -gno-record-gcc-switches -fno-common""

</pre></details>

### What did you do?

Reading the Index expressions spec at https://go.dev/ref/spec#Map_types to determine how to handle the case where a key is not present in a map.

### What did you expect to see?

Information about the above.

### What did you see instead?

Information about type parameter types, introduced in 68da368a4e .

### Note

Pull request incoming.",1,spec  index expressions spec is fragmented for map type code       what version of go are you using   go version            go version  go version       darwin             does this issue reproduce with the latest release     yes         what operating system and processor architecture are you using   go env          go env  output                goarch      gobin     gocache   users paj library caches go build   goenv   users paj library application support go env   goexe     goexperiment     goflags     gohostarch      gohostos  darwin   goinsecure     gomodcache   users paj  asdf installs golang       packages pkg mod   gonoproxy     gonosumdb     goos  darwin   gopath   users paj  asdf installs golang       packages   goprivate     goproxy     goroot   users paj  asdf installs golang       go   gosumdb  sum golang org   gotmpdir     gotooldir   users paj  asdf installs golang       go pkg tool darwin     govcs     goversion          gccgo  gccgo          ar  ar   cc  clang   cxx  clang     cgo enabled      gomod   dev null   gowork     cgo cflags      g   cgo cppflags     cgo cxxflags      g   cgo fflags      g   cgo ldflags      g   pkg config  pkg config   gogccflags   fpic  arch         pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders     t go    tmp go build  gno record gcc switches  fno common               what did you do     reading the index expressions spec at   to determine how to handle the case where a key is not present in a map         what did you expect to see     information about the above         what did you see instead     information about type parameter types  introduced in            note    pull request incoming ,1
208980,16167071285.0,IssuesEvent,2021-05-01 18:12:23,golang/go,https://api.github.com/repos/golang/go,opened,"go/types, go/constant: improve documentation on constant.Kind and relationship to concrete types",Documentation,"ISTM that go/types and go/constant don't currently do a good job at explaining which constant.Kind can be encountered in which contexts. For example, before seeing #43891 I wasn't aware that a floating point constant may have Kind() == Int.

And while that issue explains that go/constant may use a more efficient representation, it doesn't mention if it may use a _less efficient_ representation, especially in relationship with the type checker. For example, in the following example

```
var foo func(int)
const k = 4.0
_ = 1 << k
foo(k)
```

it is not clear to me whether the types.TypeAndValue for the ast.Ident `k` as used in the bit shift and function call are guaranteed to be a constant.Int or not. It currently seems to be, and existing code in `vet` doesn't defensively use ToInt before using Uint64Val

Summarizing, I'd like to see documentation that at least
- mentions that constant kinds aren't directly related to concrete types
- explains which simplifying guarantees go/types makes, if any
- states how defensively code has to be written in practice

/cc @griesemer ",1.0,"go/types, go/constant: improve documentation on constant.Kind and relationship to concrete types - ISTM that go/types and go/constant don't currently do a good job at explaining which constant.Kind can be encountered in which contexts. For example, before seeing #43891 I wasn't aware that a floating point constant may have Kind() == Int.

And while that issue explains that go/constant may use a more efficient representation, it doesn't mention if it may use a _less efficient_ representation, especially in relationship with the type checker. For example, in the following example

```
var foo func(int)
const k = 4.0
_ = 1 << k
foo(k)
```

it is not clear to me whether the types.TypeAndValue for the ast.Ident `k` as used in the bit shift and function call are guaranteed to be a constant.Int or not. It currently seems to be, and existing code in `vet` doesn't defensively use ToInt before using Uint64Val

Summarizing, I'd like to see documentation that at least
- mentions that constant kinds aren't directly related to concrete types
- explains which simplifying guarantees go/types makes, if any
- states how defensively code has to be written in practice

/cc @griesemer ",1,go types  go constant  improve documentation on constant kind and relationship to concrete types   istm that go types and go constant don t currently do a good job at explaining which constant kind can be encountered in which contexts  for example  before seeing    i wasn t aware that a floating point constant may have kind      int     and while that issue explains that go constant may use a more efficient representation  it doesn t mention if it may use a  less efficient  representation  especially in relationship with the type checker  for example  in the following example         var foo func int   const k                 k  foo k          it is not clear to me whether the types typeandvalue for the ast ident  k  as used in the bit shift and function call are guaranteed to be a constant int or not  it currently seems to be  and existing code in  vet  doesn t defensively use toint before using      summarizing  i d like to see documentation that at least    mentions that constant kinds aren t directly related to concrete types    explains which simplifying guarantees go types makes  if any    states how defensively code has to be written in practice     cc  griesemer ,1
356003,10587399760.0,IssuesEvent,2019-10-08 22:01:54,sjawhar/enchanted-brain,https://api.github.com/repos/sjawhar/enchanted-brain,opened,The user listens to a song and picks emotions,area/client kind/feature priority/q1 size/S,"## Expected Behavior
* After filling out demographic information, the user should see instructions for the emotion picker. There should be a button to begin.
* When the begin button is pressed, [song playback begins](https://docs.expo.io/versions/latest/sdk/audio/) and the user is prompted for emotions in the same way as concert attendees were.
* Query string variables should control the song and emotion the user is given:
  * `songIndex`: number between 0 and 3, corresponding to the index of the song in [this table in the wiki](https://github.com/sjawhar/enchanted-brain/wiki/Requirements#part-2-coloremotion-1)
  * `choiceType`: either ""CHOICE_EMOTION_HAPPINESS"" or ""CHOICE_EMOTION_ANGER""
* The `choiceInverted` option should be set randomly (50/50)",1.0,"The user listens to a song and picks emotions - ## Expected Behavior
* After filling out demographic information, the user should see instructions for the emotion picker. There should be a button to begin.
* When the begin button is pressed, [song playback begins](https://docs.expo.io/versions/latest/sdk/audio/) and the user is prompted for emotions in the same way as concert attendees were.
* Query string variables should control the song and emotion the user is given:
  * `songIndex`: number between 0 and 3, corresponding to the index of the song in [this table in the wiki](https://github.com/sjawhar/enchanted-brain/wiki/Requirements#part-2-coloremotion-1)
  * `choiceType`: either ""CHOICE_EMOTION_HAPPINESS"" or ""CHOICE_EMOTION_ANGER""
* The `choiceInverted` option should be set randomly (50/50)",0,the user listens to a song and picks emotions      expected behavior    after filling out demographic information  the user should see instructions for the emotion picker  there should be a button to begin     when the begin button is pressed      and the user is prompted for emotions in the same way as concert attendees were     query string variables should control the song and emotion the user is given        songindex   number between   and    corresponding to the index of the song in           choicetype   either  choice emotion happiness  or  choice emotion anger     the  choiceinverted  option should be set randomly      ,0
79375,28137231393.0,IssuesEvent,2023-04-01 14:24:16,SeleniumHQ/selenium,https://api.github.com/repos/SeleniumHQ/selenium,opened,[🐛 Bug]: Unavoidable DeprecationWarning when using Safari with Python,I-defect needs-triaging,"### What happened?

I am developing a Django application, and I want to test how it behaves in Safari. I treat all deprecation warnings as errors during development so I am alerted when something becomes deprecated and can update my code accordingly.

When I try to create a Safari WebDriver instance, the Safari `WebDriver.__init__` passes `desired_capabilities=DEFAULT_SAFARI_CAPS` to its superclass's `__init__`, which will then raise a `DeprecationWarning` stating that `desired_capabilities` shouldn't be used. If I try to set `desired_capabilities` to `None`, the Safari `__init__` raises a `DeprecationWarning` stating that I should use the `options` argument instead of changing the `desired_capabilities` value.

Below is the output I got when trying to start a Safari instance using selenium:

```shell
(venv) /tmp % python -Werror
Python 3.9.13 (v3.9.13:6de2ca5339, May 17 2022, 11:37:23) 
[Clang 13.0.0 (clang-1300.0.29.30)] on darwin
Type ""help"", ""copyright"", ""credits"" or ""license"" for more information.
>>> from selenium.webdriver import Safari
>>> driver = Safari()
Traceback (most recent call last):
  File ""<stdin>"", line 1, in <module>
  File ""/private/tmp/venv/lib/python3.9/site-packages/selenium/webdriver/safari/webdriver.py"", line 110, in __init__
    super().__init__(command_executor=executor, options=options, desired_capabilities=desired_capabilities)
  File ""/private/tmp/venv/lib/python3.9/site-packages/selenium/webdriver/remote/webdriver.py"", line 231, in __init__
    warnings.warn(
DeprecationWarning: desired_capabilities has been deprecated, please pass in an Options object with options kwarg
>>> from selenium.webdriver.safari.options import Options
>>> options = Options()
>>> driver = Safari(options=options)
Traceback (most recent call last):
  File ""<stdin>"", line 1, in <module>
  File ""/private/tmp/venv/lib/python3.9/site-packages/selenium/webdriver/safari/webdriver.py"", line 110, in __init__
    super().__init__(command_executor=executor, options=options, desired_capabilities=desired_capabilities)
  File ""/private/tmp/venv/lib/python3.9/site-packages/selenium/webdriver/remote/webdriver.py"", line 231, in __init__
    warnings.warn(
DeprecationWarning: desired_capabilities has been deprecated, please pass in an Options object with options kwarg
>>> driver = Safari(options=options, desired_capabilities=None)
Traceback (most recent call last):
  File ""<stdin>"", line 1, in <module>
  File ""/private/tmp/venv/lib/python3.9/site-packages/selenium/webdriver/safari/webdriver.py"", line 80, in __init__
    warnings.warn(
DeprecationWarning: desired_capabilities has been deprecated, please use the Options class to set it
```

### How can we reproduce the issue?

```shell
python3.9 -m venv venv
. venv/bin/activate
pip install -U pip setuptools wheel
pip install selenium
python -Werror -c '
from selenium.webdriver import Safari
try:
    driver = Safari() # This will cause an error
except BaseException as e:
    print(""Bare init:"", e)
from selenium.webdriver.safari.options import Options
options = Options()
try:
    driver = Safari(options=options) # This will cause an error
except BaseException as e:
    print(""Init with options:"", e)
try:
    driver = Safari(options=options, desired_capabilities=None) # This will cause an error
except BaseException as e:
    print(""Init with options and no desired_capabilities:"", e)'
```


### Relevant log output

```shell
Requirement already satisfied: pip in ./venv/lib/python3.9/site-packages (22.0.4)
Collecting pip
  Using cached pip-23.0.1-py3-none-any.whl (2.1 MB)
Requirement already satisfied: setuptools in ./venv/lib/python3.9/site-packages (58.1.0)
Collecting setuptools
  Using cached setuptools-67.6.1-py3-none-any.whl (1.1 MB)
Collecting wheel
  Using cached wheel-0.40.0-py3-none-any.whl (64 kB)
Installing collected packages: wheel, setuptools, pip
  Attempting uninstall: setuptools
    Found existing installation: setuptools 58.1.0
    Uninstalling setuptools-58.1.0:
      Successfully uninstalled setuptools-58.1.0
  Attempting uninstall: pip
    Found existing installation: pip 22.0.4
    Uninstalling pip-22.0.4:
      Successfully uninstalled pip-22.0.4
Successfully installed pip-23.0.1 setuptools-67.6.1 wheel-0.40.0
Collecting selenium
  Using cached selenium-4.8.3-py3-none-any.whl (6.5 MB)
Collecting trio-websocket~=0.9
  Using cached trio_websocket-0.10.2-py3-none-any.whl (17 kB)
Collecting certifi>=2021.10.8
  Using cached certifi-2022.12.7-py3-none-any.whl (155 kB)
Collecting urllib3[socks]~=1.26
  Using cached urllib3-1.26.15-py2.py3-none-any.whl (140 kB)
Collecting trio~=0.17
  Using cached trio-0.22.0-py3-none-any.whl (384 kB)
Collecting sortedcontainers
  Using cached sortedcontainers-2.4.0-py2.py3-none-any.whl (29 kB)
Collecting attrs>=19.2.0
  Using cached attrs-22.2.0-py3-none-any.whl (60 kB)
Collecting sniffio
  Using cached sniffio-1.3.0-py3-none-any.whl (10 kB)
Collecting outcome
  Using cached outcome-1.2.0-py2.py3-none-any.whl (9.7 kB)
Collecting idna
  Using cached idna-3.4-py3-none-any.whl (61 kB)
Collecting async-generator>=1.9
  Using cached async_generator-1.10-py3-none-any.whl (18 kB)
Collecting exceptiongroup>=1.0.0rc9
  Using cached exceptiongroup-1.1.1-py3-none-any.whl (14 kB)
Collecting wsproto>=0.14
  Using cached wsproto-1.2.0-py3-none-any.whl (24 kB)
Collecting PySocks!=1.5.7,<2.0,>=1.5.6
  Using cached PySocks-1.7.1-py3-none-any.whl (16 kB)
Collecting h11<1,>=0.9.0
  Using cached h11-0.14.0-py3-none-any.whl (58 kB)
Installing collected packages: sortedcontainers, urllib3, sniffio, PySocks, idna, h11, exceptiongroup, certifi, attrs, async-generator, wsproto, outcome, trio, trio-websocket, selenium
Successfully installed PySocks-1.7.1 async-generator-1.10 attrs-22.2.0 certifi-2022.12.7 exceptiongroup-1.1.1 h11-0.14.0 idna-3.4 outcome-1.2.0 selenium-4.8.3 sniffio-1.3.0 sortedcontainers-2.4.0 trio-0.22.0 trio-websocket-0.10.2 urllib3-1.26.15 wsproto-1.2.0
Bare init: desired_capabilities has been deprecated, please pass in an Options object with options kwarg
Init with options: desired_capabilities has been deprecated, please pass in an Options object with options kwarg
Init with options and no desired_capabilities: desired_capabilities has been deprecated, please use the Options class to set it
```


### Operating System

macOS Ventura 13.3

### Selenium version

Python 4.8.3

### What are the browser(s) and version(s) where you see this issue?

N / A, issue is in selenium itself

### What are the browser driver(s) and version(s) where you see this issue?

N / A, issue is in selenium itself

### Are you using Selenium Grid?

_No response_",1.0,"[🐛 Bug]: Unavoidable DeprecationWarning when using Safari with Python - ### What happened?

I am developing a Django application, and I want to test how it behaves in Safari. I treat all deprecation warnings as errors during development so I am alerted when something becomes deprecated and can update my code accordingly.

When I try to create a Safari WebDriver instance, the Safari `WebDriver.__init__` passes `desired_capabilities=DEFAULT_SAFARI_CAPS` to its superclass's `__init__`, which will then raise a `DeprecationWarning` stating that `desired_capabilities` shouldn't be used. If I try to set `desired_capabilities` to `None`, the Safari `__init__` raises a `DeprecationWarning` stating that I should use the `options` argument instead of changing the `desired_capabilities` value.

Below is the output I got when trying to start a Safari instance using selenium:

```shell
(venv) /tmp % python -Werror
Python 3.9.13 (v3.9.13:6de2ca5339, May 17 2022, 11:37:23) 
[Clang 13.0.0 (clang-1300.0.29.30)] on darwin
Type ""help"", ""copyright"", ""credits"" or ""license"" for more information.
>>> from selenium.webdriver import Safari
>>> driver = Safari()
Traceback (most recent call last):
  File ""<stdin>"", line 1, in <module>
  File ""/private/tmp/venv/lib/python3.9/site-packages/selenium/webdriver/safari/webdriver.py"", line 110, in __init__
    super().__init__(command_executor=executor, options=options, desired_capabilities=desired_capabilities)
  File ""/private/tmp/venv/lib/python3.9/site-packages/selenium/webdriver/remote/webdriver.py"", line 231, in __init__
    warnings.warn(
DeprecationWarning: desired_capabilities has been deprecated, please pass in an Options object with options kwarg
>>> from selenium.webdriver.safari.options import Options
>>> options = Options()
>>> driver = Safari(options=options)
Traceback (most recent call last):
  File ""<stdin>"", line 1, in <module>
  File ""/private/tmp/venv/lib/python3.9/site-packages/selenium/webdriver/safari/webdriver.py"", line 110, in __init__
    super().__init__(command_executor=executor, options=options, desired_capabilities=desired_capabilities)
  File ""/private/tmp/venv/lib/python3.9/site-packages/selenium/webdriver/remote/webdriver.py"", line 231, in __init__
    warnings.warn(
DeprecationWarning: desired_capabilities has been deprecated, please pass in an Options object with options kwarg
>>> driver = Safari(options=options, desired_capabilities=None)
Traceback (most recent call last):
  File ""<stdin>"", line 1, in <module>
  File ""/private/tmp/venv/lib/python3.9/site-packages/selenium/webdriver/safari/webdriver.py"", line 80, in __init__
    warnings.warn(
DeprecationWarning: desired_capabilities has been deprecated, please use the Options class to set it
```

### How can we reproduce the issue?

```shell
python3.9 -m venv venv
. venv/bin/activate
pip install -U pip setuptools wheel
pip install selenium
python -Werror -c '
from selenium.webdriver import Safari
try:
    driver = Safari() # This will cause an error
except BaseException as e:
    print(""Bare init:"", e)
from selenium.webdriver.safari.options import Options
options = Options()
try:
    driver = Safari(options=options) # This will cause an error
except BaseException as e:
    print(""Init with options:"", e)
try:
    driver = Safari(options=options, desired_capabilities=None) # This will cause an error
except BaseException as e:
    print(""Init with options and no desired_capabilities:"", e)'
```


### Relevant log output

```shell
Requirement already satisfied: pip in ./venv/lib/python3.9/site-packages (22.0.4)
Collecting pip
  Using cached pip-23.0.1-py3-none-any.whl (2.1 MB)
Requirement already satisfied: setuptools in ./venv/lib/python3.9/site-packages (58.1.0)
Collecting setuptools
  Using cached setuptools-67.6.1-py3-none-any.whl (1.1 MB)
Collecting wheel
  Using cached wheel-0.40.0-py3-none-any.whl (64 kB)
Installing collected packages: wheel, setuptools, pip
  Attempting uninstall: setuptools
    Found existing installation: setuptools 58.1.0
    Uninstalling setuptools-58.1.0:
      Successfully uninstalled setuptools-58.1.0
  Attempting uninstall: pip
    Found existing installation: pip 22.0.4
    Uninstalling pip-22.0.4:
      Successfully uninstalled pip-22.0.4
Successfully installed pip-23.0.1 setuptools-67.6.1 wheel-0.40.0
Collecting selenium
  Using cached selenium-4.8.3-py3-none-any.whl (6.5 MB)
Collecting trio-websocket~=0.9
  Using cached trio_websocket-0.10.2-py3-none-any.whl (17 kB)
Collecting certifi>=2021.10.8
  Using cached certifi-2022.12.7-py3-none-any.whl (155 kB)
Collecting urllib3[socks]~=1.26
  Using cached urllib3-1.26.15-py2.py3-none-any.whl (140 kB)
Collecting trio~=0.17
  Using cached trio-0.22.0-py3-none-any.whl (384 kB)
Collecting sortedcontainers
  Using cached sortedcontainers-2.4.0-py2.py3-none-any.whl (29 kB)
Collecting attrs>=19.2.0
  Using cached attrs-22.2.0-py3-none-any.whl (60 kB)
Collecting sniffio
  Using cached sniffio-1.3.0-py3-none-any.whl (10 kB)
Collecting outcome
  Using cached outcome-1.2.0-py2.py3-none-any.whl (9.7 kB)
Collecting idna
  Using cached idna-3.4-py3-none-any.whl (61 kB)
Collecting async-generator>=1.9
  Using cached async_generator-1.10-py3-none-any.whl (18 kB)
Collecting exceptiongroup>=1.0.0rc9
  Using cached exceptiongroup-1.1.1-py3-none-any.whl (14 kB)
Collecting wsproto>=0.14
  Using cached wsproto-1.2.0-py3-none-any.whl (24 kB)
Collecting PySocks!=1.5.7,<2.0,>=1.5.6
  Using cached PySocks-1.7.1-py3-none-any.whl (16 kB)
Collecting h11<1,>=0.9.0
  Using cached h11-0.14.0-py3-none-any.whl (58 kB)
Installing collected packages: sortedcontainers, urllib3, sniffio, PySocks, idna, h11, exceptiongroup, certifi, attrs, async-generator, wsproto, outcome, trio, trio-websocket, selenium
Successfully installed PySocks-1.7.1 async-generator-1.10 attrs-22.2.0 certifi-2022.12.7 exceptiongroup-1.1.1 h11-0.14.0 idna-3.4 outcome-1.2.0 selenium-4.8.3 sniffio-1.3.0 sortedcontainers-2.4.0 trio-0.22.0 trio-websocket-0.10.2 urllib3-1.26.15 wsproto-1.2.0
Bare init: desired_capabilities has been deprecated, please pass in an Options object with options kwarg
Init with options: desired_capabilities has been deprecated, please pass in an Options object with options kwarg
Init with options and no desired_capabilities: desired_capabilities has been deprecated, please use the Options class to set it
```


### Operating System

macOS Ventura 13.3

### Selenium version

Python 4.8.3

### What are the browser(s) and version(s) where you see this issue?

N / A, issue is in selenium itself

### What are the browser driver(s) and version(s) where you see this issue?

N / A, issue is in selenium itself

### Are you using Selenium Grid?

_No response_",0,   unavoidable deprecationwarning when using safari with python       what happened   i am developing a django application  and i want to test how it behaves in safari  i treat all deprecation warnings as errors during development so i am alerted when something becomes deprecated and can update my code accordingly     when i try to create a safari webdriver instance  the safari  webdriver   init    passes  desired capabilities default safari caps  to its superclass s    init     which will then raise a  deprecationwarning  stating that  desired capabilities  shouldn t be used  if i try to set  desired capabilities  to  none   the safari    init    raises a  deprecationwarning  stating that i should use the  options  argument instead of changing the  desired capabilities  value     below is the output i got when trying to start a safari instance using selenium        shell   venv   tmp   python  werror  python                 may                 on darwin  type  help    copyright    credits  or  license  for more information       from selenium webdriver import safari      driver   safari    traceback  most recent call last      file      line    in      file   private tmp venv lib     site packages selenium webdriver safari webdriver py   line    in   init        super     init   command executor executor  options options  desired capabilities desired capabilities     file   private tmp venv lib     site packages selenium webdriver remote webdriver py   line    in   init        warnings warn   deprecationwarning  desired capabilities has been deprecated  please pass in an options object with options kwarg      from selenium webdriver safari options import options      options   options        driver   safari options options   traceback  most recent call last      file      line    in      file   private tmp venv lib     site packages selenium webdriver safari webdriver py   line    in   init        super     init   command executor executor  options options  desired capabilities desired capabilities     file   private tmp venv lib     site packages selenium webdriver remote webdriver py   line    in   init        warnings warn   deprecationwarning  desired capabilities has been deprecated  please pass in an options object with options kwarg      driver   safari options options  desired capabilities none   traceback  most recent call last      file      line    in      file   private tmp venv lib     site packages selenium webdriver safari webdriver py   line    in   init        warnings warn   deprecationwarning  desired capabilities has been deprecated  please use the options class to set it           how can we reproduce the issue      shell      m venv venv    venv bin activate  pip install  u pip setuptools wheel  pip install selenium  python  werror  c    from selenium webdriver import safari  try       driver   safari     this will cause an error  except baseexception as e       print  bare init    e   from selenium webdriver safari options import options  options   options    try       driver   safari options options    this will cause an error  except baseexception as e       print  init with options    e   try       driver   safari options options  desired capabilities none    this will cause an error  except baseexception as e       print  init with options and no desired capabilities    e             relevant log output     shell requirement already satisfied  pip in   venv lib     site packages          collecting pip    using cached pip         none any whl      mb   requirement already satisfied  setuptools in   venv lib     site packages          collecting setuptools    using cached setuptools         none any whl      mb   collecting wheel    using cached wheel         none any whl    kb   installing collected packages  wheel  setuptools  pip    attempting uninstall  setuptools      found existing installation  setuptools            uninstalling setuptools               successfully uninstalled setuptools          attempting uninstall  pip      found existing installation  pip            uninstalling pip               successfully uninstalled pip        successfully installed pip       setuptools       wheel        collecting selenium    using cached selenium         none any whl      mb   collecting trio websocket         using cached trio websocket         none any whl    kb   collecting certifi           using cached certifi         none any whl    kb   collecting            using cached             none any whl    kb   collecting trio         using cached trio         none any whl    kb   collecting sortedcontainers    using cached sortedcontainers           none any whl    kb   collecting attrs           using cached attrs         none any whl    kb   collecting sniffio    using cached sniffio         none any whl    kb   collecting outcome    using cached outcome           none any whl      kb   collecting idna    using cached idna       none any whl    kb   collecting async generator         using cached async generator       none any whl    kb   collecting exceptiongroup           using cached exceptiongroup         none any whl    kb   collecting wsproto         using cached wsproto         none any whl    kb   collecting pysocks                   using cached pysocks         none any whl    kb   collecting             using cached           none any whl    kb   installing collected packages  sortedcontainers     sniffio  pysocks  idna     exceptiongroup  certifi  attrs  async generator  wsproto  outcome  trio  trio websocket  selenium  successfully installed pysocks       async generator     attrs       certifi       exceptiongroup               idna     outcome       selenium       sniffio       sortedcontainers       trio       trio websocket               wsproto        bare init  desired capabilities has been deprecated  please pass in an options object with options kwarg  init with options  desired capabilities has been deprecated  please pass in an options object with options kwarg  init with options and no desired capabilities  desired capabilities has been deprecated  please use the options class to set it           operating system  macos ventura          selenium version  python            what are the browser s  and version s  where you see this issue   n   a  issue is in selenium itself      what are the browser driver s  and version s  where you see this issue   n   a  issue is in selenium itself      are you using selenium grid    no response ,0
98925,4043855236.0,IssuesEvent,2016-05-21 00:31:50,Solinea/goldstone-server,https://api.github.com/repos/Solinea/goldstone-server,opened,Cinder volume created saved search does not work,priority 2: high type: bug,"The cinder volume created saved search does not work.  

## Expected Behavior
This query should return hits after running RDO for a couple of minutes or manually creating a volume with the cinder API.

## Current Behavior
Log entries are sent Goldstone that indicate the volume is created but they are not stored correctly.  The saved search designed for this event expects there to be a ""program"" field in the logstash-* indices.  However if you do the following query to try to find the event you can see from the response that there is not such field for this event:
<pre>
GET logstash-*/_search
{
    ""size"": 100,
    ""query"": { 
        ""bool"": {
            ""must"": [
                {
                   ""match"" : {
                      ""message"": ""created successfully""
                   }
                }
            ]
        }
     }
}
</pre>

Hits returned:
<pre>
{
    ""_index"": ""logstash-2016.05.20"",
    ""_type"": ""syslog"",
    ""_id"": ""AVTQjkIGzqEIT_AOy6IR"",
    ""_score"": 13.031151,
    ""_source"": {
           ""@timestamp"": ""2016-05-20T23:44:24.579Z"",
           ""message"": ""2016-05-20 22:31:40.861 2970 INFO cinder.volume.flows.manager.create_volume [req-6d3045ec-c969-487f-85f7-a0b25bb7d582 17f82699df734cf0a0012accd4ff5609 df95efbe930e49d7b11a62a2afacf497 - - -] Volume volume-c8a38c58-f967-4308-9621-aeddc2d1c7d3 (c8a38c58-f967-4308-9621-aeddc2d1c7d3): created successfully"",
           ""@version"": ""1"",
           ""host"": ""172.18.0.1"",
           ""port"": 35658,
           ""type"": ""syslog"",
           ""tags"": []
       }
}
</pre>

## Possible Solution
1. This can be fixed by modifying the saved search to work with the message field, but this is just a work around.
2. The real problem is the log for this event is not being handled correctly.  There should be a ""program"" and ""openstack_message"" fields added to the document that gets indexed.",1.0,"Cinder volume created saved search does not work - The cinder volume created saved search does not work.  

## Expected Behavior
This query should return hits after running RDO for a couple of minutes or manually creating a volume with the cinder API.

## Current Behavior
Log entries are sent Goldstone that indicate the volume is created but they are not stored correctly.  The saved search designed for this event expects there to be a ""program"" field in the logstash-* indices.  However if you do the following query to try to find the event you can see from the response that there is not such field for this event:
<pre>
GET logstash-*/_search
{
    ""size"": 100,
    ""query"": { 
        ""bool"": {
            ""must"": [
                {
                   ""match"" : {
                      ""message"": ""created successfully""
                   }
                }
            ]
        }
     }
}
</pre>

Hits returned:
<pre>
{
    ""_index"": ""logstash-2016.05.20"",
    ""_type"": ""syslog"",
    ""_id"": ""AVTQjkIGzqEIT_AOy6IR"",
    ""_score"": 13.031151,
    ""_source"": {
           ""@timestamp"": ""2016-05-20T23:44:24.579Z"",
           ""message"": ""2016-05-20 22:31:40.861 2970 INFO cinder.volume.flows.manager.create_volume [req-6d3045ec-c969-487f-85f7-a0b25bb7d582 17f82699df734cf0a0012accd4ff5609 df95efbe930e49d7b11a62a2afacf497 - - -] Volume volume-c8a38c58-f967-4308-9621-aeddc2d1c7d3 (c8a38c58-f967-4308-9621-aeddc2d1c7d3): created successfully"",
           ""@version"": ""1"",
           ""host"": ""172.18.0.1"",
           ""port"": 35658,
           ""type"": ""syslog"",
           ""tags"": []
       }
}
</pre>

## Possible Solution
1. This can be fixed by modifying the saved search to work with the message field, but this is just a work around.
2. The real problem is the log for this event is not being handled correctly.  There should be a ""program"" and ""openstack_message"" fields added to the document that gets indexed.",0,cinder volume created saved search does not work   the cinder volume created saved search does not work          expected behavior  this query should return hits after running rdo for a couple of minutes or manually creating a volume with the cinder api        current behavior  log entries are sent goldstone that indicate the volume is created but they are not stored correctly   the saved search designed for this event expects there to be a  program  field in the logstash   indices   however if you do the following query to try to find the event you can see from the response that there is not such field for this event      get logstash    search          size            query                bool                   must                                             match                              message    created successfully                                                                                      hits returned               index    logstash                type    syslog          id    avtqjkigzqeit            score               source                   timestamp                               message                    info cinder volume flows manager create volume   volume volume                        created successfully                 version                     host                           port                   type    syslog                tags                           possible solution     this can be fixed by modifying the saved search to work with the message field  but this is just a work around      the real problem is the log for this event is not being handled correctly   there should be a  program  and  openstack message  fields added to the document that gets indexed ,0
6394,3019766471.0,IssuesEvent,2015-07-31 00:18:35,golang/go,https://api.github.com/repos/golang/go,closed,doc: Solaris port has many changes for Go 1.5,Documentation,"The release notes for Go 1.5 beta 3 omit a number of interesting changes made for the Solaris port of Go, some of which are bug fixes and others much larger feature support additions:

  * crypto/x509 now works ""out-of-the-box"" as the ""standard"" locations for the system-wide CA
    certificates file has been added
  * net package should now be fully functional (sendfile, socket options in particular)
  * cgo fully supported and enabled by default

Oracle sponsored most of the work for the last two items via contracting Aram Hăvărneanu.

There are of course numerous other bug fixes as well that others kindly contributed, but those are the big items that I'm aware of.",1.0,"doc: Solaris port has many changes for Go 1.5 - The release notes for Go 1.5 beta 3 omit a number of interesting changes made for the Solaris port of Go, some of which are bug fixes and others much larger feature support additions:

  * crypto/x509 now works ""out-of-the-box"" as the ""standard"" locations for the system-wide CA
    certificates file has been added
  * net package should now be fully functional (sendfile, socket options in particular)
  * cgo fully supported and enabled by default

Oracle sponsored most of the work for the last two items via contracting Aram Hăvărneanu.

There are of course numerous other bug fixes as well that others kindly contributed, but those are the big items that I'm aware of.",1,doc  solaris port has many changes for go       the release notes for go     beta   omit a number of interesting changes made for the solaris port of go  some of which are bug fixes and others much larger feature support additions         crypto   now works  out of the box  as the  standard  locations for the system wide ca      certificates file has been added      net package should now be fully functional  sendfile  socket options in particular       cgo fully supported and enabled by default    oracle sponsored most of the work for the last two items via contracting aram hăvărneanu     there are of course numerous other bug fixes as well that others kindly contributed  but those are the big items that i m aware of ,1
107192,23366785796.0,IssuesEvent,2022-08-10 16:00:49,microsoft/jacdac,https://api.github.com/repos/microsoft/jacdac,closed,LED ring does not light up without a pause between setting the brightness and turning the LEDs on,bug makecodeintegration makecode clients,"The LED ring does not light up without the ""set led brightness"" in Makecode. I did not see documentation related to this. Also, using Makecode, the LED ring will not light up if the code block ""set led"" to a color is immediately following the ""set led brightness"" code block. A pause of 200ms was required between the ""set led brightness"" and ""set led"" to a color. Or, other code blocks are used before setting the LEDs to a light up. ",2.0,"LED ring does not light up without a pause between setting the brightness and turning the LEDs on - The LED ring does not light up without the ""set led brightness"" in Makecode. I did not see documentation related to this. Also, using Makecode, the LED ring will not light up if the code block ""set led"" to a color is immediately following the ""set led brightness"" code block. A pause of 200ms was required between the ""set led brightness"" and ""set led"" to a color. Or, other code blocks are used before setting the LEDs to a light up. ",0,led ring does not light up without a pause between setting the brightness and turning the leds on   the led ring does not light up without the  set led brightness  in makecode  i did not see documentation related to this  also  using makecode  the led ring will not light up if the code block  set led  to a color is immediately following the  set led brightness  code block  a pause of   was required between the  set led brightness  and  set led  to a color  or  other code blocks are used before setting the leds to a light up  ,0
686782,23504388652.0,IssuesEvent,2022-08-18 11:18:22,poja/RL,https://api.github.com/repos/poja/RL,opened,Choose chess library and implement wrapper interface,priority-medium,"https://docs.rs/chess/ is a nice option for a chess library, supporting legal moves query, game status (checkmate, stalemate, ect) detection and so on.
We should write a wrapper to the library we choose, enabling our generic MCTS implementation to use it.",1.0,"Choose chess library and implement wrapper interface - https://docs.rs/chess/ is a nice option for a chess library, supporting legal moves query, game status (checkmate, stalemate, ect) detection and so on.
We should write a wrapper to the library we choose, enabling our generic MCTS implementation to use it.",0,choose chess library and implement wrapper interface     is a nice option for a chess library  supporting legal moves query  game status  checkmate  stalemate  ect  detection and so on   we should write a wrapper to the library we choose  enabling our generic mcts implementation to use it ,0
387830,11470829251.0,IssuesEvent,2020-02-09 06:40:00,IlchCMS/Ilch-2.0,https://api.github.com/repos/IlchCMS/Ilch-2.0,opened,Update-Funktion: getUpdate() anschließend ausführen,Priority: Low Type: Enhancement,"Aktuell ist es der Fall, dass man die Reihenfolge in der die getUpdate() ausgeführt werden berücksichtigen muss.

Beispiel ""Ersetzen des vendor-Ordners"":
Den neuen vendor-Ordner muss man z.B. ""_vendor"" nennen, damit dieser auf jeden Fall vor der Ausführung der getUpdate() des Admin-Moduls existiert.
Hätte man den neuen Ordner z.B. ""vendor_"" genannt, wäre die getUpdate() des Admin-Moduls zu einem Zeitpunkt ausgeführt worden, in den der ""vendor_""-Ordner noch nicht existiert.
Das z.B. Umbenennen des ""vendor_""-Ordners in ""vendor"" würde dann fehlschlagen.

Hier wäre es wahrscheinlich sinnvoller, wenn erst das komplette Update entpackt wird und die getUpdate() aller Module usw. anschließend ausgeführt werden.",1.0,"Update-Funktion: getUpdate() anschließend ausführen - Aktuell ist es der Fall, dass man die Reihenfolge in der die getUpdate() ausgeführt werden berücksichtigen muss.

Beispiel ""Ersetzen des vendor-Ordners"":
Den neuen vendor-Ordner muss man z.B. ""_vendor"" nennen, damit dieser auf jeden Fall vor der Ausführung der getUpdate() des Admin-Moduls existiert.
Hätte man den neuen Ordner z.B. ""vendor_"" genannt, wäre die getUpdate() des Admin-Moduls zu einem Zeitpunkt ausgeführt worden, in den der ""vendor_""-Ordner noch nicht existiert.
Das z.B. Umbenennen des ""vendor_""-Ordners in ""vendor"" würde dann fehlschlagen.

Hier wäre es wahrscheinlich sinnvoller, wenn erst das komplette Update entpackt wird und die getUpdate() aller Module usw. anschließend ausgeführt werden.",0,update funktion  getupdate   anschließend ausführen   aktuell ist es der fall  dass man die reihenfolge in der die getupdate   ausgeführt werden berücksichtigen muss     beispiel  ersetzen des vendor ordners    den neuen vendor ordner muss man z b    vendor  nennen  damit dieser auf jeden fall vor der ausführung der getupdate   des admin moduls existiert   hätte man den neuen ordner z b   vendor   genannt  wäre die getupdate   des admin moduls zu einem zeitpunkt ausgeführt worden  in den der  vendor   ordner noch nicht existiert   das z b  umbenennen des  vendor   ordners in  vendor  würde dann fehlschlagen     hier wäre es wahrscheinlich sinnvoller  wenn erst das komplette update entpackt wird und die getupdate   aller module usw  anschließend ausgeführt werden ,0
131071,12474322347.0,IssuesEvent,2020-05-29 09:26:43,golang/go,https://api.github.com/repos/golang/go,closed,net/http: AddCookie fails to add a malformed cookie to a request,Documentation,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14.2 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/mgrigaitis/Library/Caches/go-build""
GOENV=""/Users/mgrigaitis/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/mgrigaitis/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/Cellar/go/1.14.2_1/libexec""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/1.14.2_1/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/xd/kmhy2qkd011g0cn7pf341c_w0000gn/T/go-build009702876=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?

https://play.golang.org/p/yagiRaYwKRk
https://play.golang.org/p/UVW1Hh9O8Gc

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

### What did you expect to see?

I would expect `request.AddCookie(""name"", ""value"")` followed by `request.Cookie(""name"")` to always return Cookie with `name=value` or at least Cookie with same key but previous value. 

### What did you see instead?

request.Cookie() does not see the Cookie.

### Other considerations

Different programming languages / libraries behave differently in cookie parsing. If golang application is acting as ""proxy"" and adds cookies to the request, backend systems could parse cookies differently.
",1.0,"net/http: AddCookie fails to add a malformed cookie to a request - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14.2 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/mgrigaitis/Library/Caches/go-build""
GOENV=""/Users/mgrigaitis/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/mgrigaitis/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/Cellar/go/1.14.2_1/libexec""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/1.14.2_1/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/xd/kmhy2qkd011g0cn7pf341c_w0000gn/T/go-build009702876=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?

https://play.golang.org/p/yagiRaYwKRk
https://play.golang.org/p/UVW1Hh9O8Gc

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

### What did you expect to see?

I would expect `request.AddCookie(""name"", ""value"")` followed by `request.Cookie(""name"")` to always return Cookie with `name=value` or at least Cookie with same key but previous value. 

### What did you see instead?

request.Cookie() does not see the Cookie.

### Other considerations

Different programming languages / libraries behave differently in cookie parsing. If golang application is acting as ""proxy"" and adds cookies to the request, backend systems could parse cookies differently.
",1,net http  addcookie fails to add a malformed cookie to a request         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version            go version  go version       darwin             does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   users mgrigaitis library caches go build   goenv   users mgrigaitis library application support go env   goexe     goflags     gohostarch      gohostos  darwin   goinsecure     gonoproxy     gonosumdb     goos  darwin   gopath   users mgrigaitis go   goprivate     goproxy     goroot   usr local cellar go         libexec   gosumdb  sum golang org   gotmpdir     gotooldir   usr local cellar go         libexec pkg tool darwin     gccgo  gccgo   ar  ar   cc  clang   cxx  clang     cgo enabled      gomod     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders xd     t go    tmp go build  gno record gcc switches  fno common             what did you do                   if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best              what did you expect to see     i would expect  request addcookie  name    value    followed by  request cookie  name    to always return cookie with  name value  or at least cookie with same key but previous value          what did you see instead     request cookie   does not see the cookie         other considerations    different programming languages   libraries behave differently in cookie parsing  if golang application is acting as  proxy  and adds cookies to the request  backend systems could parse cookies differently   ,1
62155,8578619326.0,IssuesEvent,2018-11-13 06:03:14,golang/go,https://api.github.com/repos/golang/go,closed,builtin: documentation should clarify how len() behaves,Documentation,"Currently the `len( )` function returns an `int`. Changing it to `uint` has already been proposed and rejected.

Can the documentation clarify what `len( )` returns when the number of items in a slice exceeds the max value of an int?",1.0,"builtin: documentation should clarify how len() behaves - Currently the `len( )` function returns an `int`. Changing it to `uint` has already been proposed and rejected.

Can the documentation clarify what `len( )` returns when the number of items in a slice exceeds the max value of an int?",1,builtin  documentation should clarify how len   behaves   currently the  len     function returns an  int   changing it to  uint  has already been proposed and rejected     can the documentation clarify what  len     returns when the number of items in a slice exceeds the max value of an int ,1
83275,10324545105.0,IssuesEvent,2019-09-01 10:09:37,golang/go,https://api.github.com/repos/golang/go,closed,testing: example output whitespace trimming can be confusing,Documentation NeedsFix help wanted,"Consider the [Example for filepath.Split](https://godoc.org/path#Split).

The code is:

```go
fmt.Println(path.Split(""static/myfile.css""))
fmt.Println(path.Split(""myfile.css""))
fmt.Println(path.Split(""""))
```

The output is:

```
static/ myfile.css
 myfile.css
```

Given that there are three `fmt.Println` calls, it seems to me that there really ought to be three lines of output.

(And if we decide that we don't want to or can't change example output whitespace trimming, we should at least tweak this example so that the last line of output contains non-whitespace, e.g. by prefixing each output line with an asterisk or number.)
",1.0,"testing: example output whitespace trimming can be confusing - Consider the [Example for filepath.Split](https://godoc.org/path#Split).

The code is:

```go
fmt.Println(path.Split(""static/myfile.css""))
fmt.Println(path.Split(""myfile.css""))
fmt.Println(path.Split(""""))
```

The output is:

```
static/ myfile.css
 myfile.css
```

Given that there are three `fmt.Println` calls, it seems to me that there really ought to be three lines of output.

(And if we decide that we don't want to or can't change example output whitespace trimming, we should at least tweak this example so that the last line of output contains non-whitespace, e.g. by prefixing each output line with an asterisk or number.)
",1,testing  example output whitespace trimming can be confusing   consider the        the code is        go  fmt println path split  static myfile css     fmt println path split  myfile css     fmt println path split              the output is          static  myfile css   myfile css         given that there are three  fmt println  calls  it seems to me that there really ought to be three lines of output      and if we decide that we don t want to or can t change example output whitespace trimming  we should at least tweak this example so that the last line of output contains non whitespace  e g  by prefixing each output line with an asterisk or number    ,1
8825,2888997952.0,IssuesEvent,2015-06-13 01:42:20,socialappslab/appcivist-pb-client,https://api.github.com/repos/socialappslab/appcivist-pb-client,closed,First mockups for the alpha prototype,design,Basic mockups for the AppCivist Alpha prototype based on the [brainstorming](https://drive.google.com/folderview?id=0B7ShzcEnCJFNNjZISUFEWF9HN0E&usp=sharing) we made with Jose,1.0,First mockups for the alpha prototype - Basic mockups for the AppCivist Alpha prototype based on the [brainstorming](https://drive.google.com/folderview?id=0B7ShzcEnCJFNNjZISUFEWF9HN0E&usp=sharing) we made with Jose,0,first mockups for the alpha prototype   basic mockups for the appcivist alpha prototype based on the     we made with jose,0
57738,8204594104.0,IssuesEvent,2018-09-03 07:15:14,golang/go,https://api.github.com/repos/golang/go,closed,runtime/trace: incorrect WithRegion usage in code snippet,Documentation NeedsFix help wanted,"### What version of Go are you using (`go version`)?
* 1.11

### Does this issue reproduce with the latest release?
* yes (go1.11)

### What did you do?
* Read code snippet in docs for https://golang.org/pkg/runtime/trace/#NewTask

### What did you expect to see?
```
...
trace.WithRegion(ctx, ""preparation"", prepWork)
// preparation of the task
go func() {  // continue processing the task in a separate goroutine.
    defer task.End()
    trace.WithRegion(ctx, ""remaining"", remainingWork)
}()
```

### What did you see instead?
```
...
trace.WithRegion(ctx, prepWork)
// preparation of the task
go func() {  // continue processing the task in a separate goroutine.
    defer task.End()
    trace.WithRegion(ctx, remainingWork)
}
```

---

The `trace.WithRegion` requires 3 parameters (`ctx`, `regionType`, `fn`) however in the code snippet for [trace.NewTask](https://golang.org/pkg/runtime/trace/#NewTask), it seems to be missing some parameter. 

It depends what `prepWork` and `remainingWork` represent here, but if they represent function (`fn` parameter) then this code snippet is misisng `regionType` parameter.

The code snippet is also missing `()` for the `go func() ...` call.",1.0,"runtime/trace: incorrect WithRegion usage in code snippet - ### What version of Go are you using (`go version`)?
* 1.11

### Does this issue reproduce with the latest release?
* yes (go1.11)

### What did you do?
* Read code snippet in docs for https://golang.org/pkg/runtime/trace/#NewTask

### What did you expect to see?
```
...
trace.WithRegion(ctx, ""preparation"", prepWork)
// preparation of the task
go func() {  // continue processing the task in a separate goroutine.
    defer task.End()
    trace.WithRegion(ctx, ""remaining"", remainingWork)
}()
```

### What did you see instead?
```
...
trace.WithRegion(ctx, prepWork)
// preparation of the task
go func() {  // continue processing the task in a separate goroutine.
    defer task.End()
    trace.WithRegion(ctx, remainingWork)
}
```

---

The `trace.WithRegion` requires 3 parameters (`ctx`, `regionType`, `fn`) however in the code snippet for [trace.NewTask](https://golang.org/pkg/runtime/trace/#NewTask), it seems to be missing some parameter. 

It depends what `prepWork` and `remainingWork` represent here, but if they represent function (`fn` parameter) then this code snippet is misisng `regionType` parameter.

The code snippet is also missing `()` for the `go func() ...` call.",1,runtime trace  incorrect withregion usage in code snippet       what version of go are you using   go version                  does this issue reproduce with the latest release     yes              what did you do     read code snippet in docs for          what did you expect to see             trace withregion ctx   preparation   prepwork      preparation of the task  go func         continue processing the task in a separate goroutine       defer task end        trace withregion ctx   remaining   remainingwork                   what did you see instead             trace withregion ctx  prepwork      preparation of the task  go func         continue processing the task in a separate goroutine       defer task end        trace withregion ctx  remainingwork                    the  trace withregion  requires   parameters   ctx    regiontype    fn   however in the code snippet for     it seems to be missing some parameter      it depends what  prepwork  and  remainingwork  represent here  but if they represent function   fn  parameter  then this code snippet is misisng  regiontype  parameter     the code snippet is also missing      for the  go func        call ,1
468259,13463985472.0,IssuesEvent,2020-09-09 18:29:20,open-telemetry/opentelemetry-specification,https://api.github.com/repos/open-telemetry/opentelemetry-specification,closed,OTeL Java splitting SDK into multiple artifacts,area:sdk priority:p3 question release:required-for-ga spec:miscellaneous,"**What are you trying to achieve?**

I opened https://github.com/open-telemetry/opentelemetry-java/issues/1460 to split the current single SDK artifact into multiple pieces for Correlation Context, Metrics, Tracing, and then combine them all into a single artifact.

The reason for this is I'd like to use Micrometer for the metrics implementation, as it's a mature and popular framework for handling metrics in Java frameworks. Ideally, I don't want to re-implement the other pieces of the OTeL API to use Micrometer. If the SDK is split into multiple pieces it is easier to switch in Micrometer just for metrics.

**Additional context.**

There was a concern raised on the issue that this goes against the goal of OTeL to bring metrics, tracing, etc together into a single implementation. I was asked to raise an issue here to hear the perspective of the specification group on such an implementation split for Java.
",1.0,"OTeL Java splitting SDK into multiple artifacts - **What are you trying to achieve?**

I opened https://github.com/open-telemetry/opentelemetry-java/issues/1460 to split the current single SDK artifact into multiple pieces for Correlation Context, Metrics, Tracing, and then combine them all into a single artifact.

The reason for this is I'd like to use Micrometer for the metrics implementation, as it's a mature and popular framework for handling metrics in Java frameworks. Ideally, I don't want to re-implement the other pieces of the OTeL API to use Micrometer. If the SDK is split into multiple pieces it is easier to switch in Micrometer just for metrics.

**Additional context.**

There was a concern raised on the issue that this goes against the goal of OTeL to bring metrics, tracing, etc together into a single implementation. I was asked to raise an issue here to hear the perspective of the specification group on such an implementation split for Java.
",0,otel java splitting sdk into multiple artifacts     what are you trying to achieve       i opened   to split the current single sdk artifact into multiple pieces for correlation context  metrics  tracing  and then combine them all into a single artifact     the reason for this is i d like to use micrometer for the metrics implementation  as it s a mature and popular framework for handling metrics in java frameworks  ideally  i don t want to re implement the other pieces of the otel api to use micrometer  if the sdk is split into multiple pieces it is easier to switch in micrometer just for metrics       additional context       there was a concern raised on the issue that this goes against the goal of otel to bring metrics  tracing  etc together into a single implementation  i was asked to raise an issue here to hear the perspective of the specification group on such an implementation split for java   ,0
64336,14662049785.0,IssuesEvent,2020-12-29 06:04:39,tamirverthim/NodeGoat,https://api.github.com/repos/tamirverthim/NodeGoat,opened,CVE-2016-1000232 (Medium) detected in tough-cookie-2.2.2.tgz,security vulnerability,"## CVE-2016-1000232 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tough-cookie-2.2.2.tgz</b></p></summary>

<p>RFC6265 Cookies and Cookie Jar for node.js</p>
<p>Library home page: <a href=""https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.2.2.tgz"">https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.2.2.tgz</a></p>
<p>Path to dependency file: NodeGoat/package.json</p>
<p>Path to vulnerable library: NodeGoat/node_modules/grunt-retire/node_modules/tough-cookie/package.json</p>
<p>

Dependency Hierarchy:
  - grunt-retire-0.3.12.tgz (Root Library)
    - request-2.67.0.tgz
      - :x: **tough-cookie-2.2.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/tamirverthim/NodeGoat/commit/3de6c5862c1fef83d38a1fec17b579f1a5e328fb"">3de6c5862c1fef83d38a1fec17b579f1a5e328fb</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>  
  
NodeJS Tough-Cookie version 2.2.2 contains a Regular Expression Parsing vulnerability in HTTP request Cookie Header parsing that can result in Denial of Service. This attack appear to be exploitable via Custom HTTP header passed by client. This vulnerability appears to have been fixed in 2.3.0.

<p>Publish Date: 2018-09-05
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-1000232>CVE-2016-1000232</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://www.npmjs.com/advisories/130"">https://www.npmjs.com/advisories/130</a></p>
<p>Release Date: 2018-09-05</p>
<p>Fix Resolution: 2.3.0</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""tough-cookie"",""packageVersion"":""2.2.2"",""isTransitiveDependency"":true,""dependencyTree"":""grunt-retire:0.3.12;request:2.67.0;tough-cookie:2.2.2"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""2.3.0""}],""vulnerabilityIdentifier"":""CVE-2016-1000232"",""vulnerabilityDetails"":""NodeJS Tough-Cookie version 2.2.2 contains a Regular Expression Parsing vulnerability in HTTP request Cookie Header parsing that can result in Denial of Service. This attack appear to be exploitable via Custom HTTP header passed by client. This vulnerability appears to have been fixed in 2.3.0."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-1000232"",""cvss3Severity"":""medium"",""cvss3Score"":""5.3"",""cvss3Metrics"":{""A"":""Low"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""None"",""AV"":""Network"",""I"":""None""},""extraData"":{}}</REMEDIATE> -->",True,"CVE-2016-1000232 (Medium) detected in tough-cookie-2.2.2.tgz - ## CVE-2016-1000232 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tough-cookie-2.2.2.tgz</b></p></summary>

<p>RFC6265 Cookies and Cookie Jar for node.js</p>
<p>Library home page: <a href=""https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.2.2.tgz"">https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.2.2.tgz</a></p>
<p>Path to dependency file: NodeGoat/package.json</p>
<p>Path to vulnerable library: NodeGoat/node_modules/grunt-retire/node_modules/tough-cookie/package.json</p>
<p>

Dependency Hierarchy:
  - grunt-retire-0.3.12.tgz (Root Library)
    - request-2.67.0.tgz
      - :x: **tough-cookie-2.2.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/tamirverthim/NodeGoat/commit/3de6c5862c1fef83d38a1fec17b579f1a5e328fb"">3de6c5862c1fef83d38a1fec17b579f1a5e328fb</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>  
  
NodeJS Tough-Cookie version 2.2.2 contains a Regular Expression Parsing vulnerability in HTTP request Cookie Header parsing that can result in Denial of Service. This attack appear to be exploitable via Custom HTTP header passed by client. This vulnerability appears to have been fixed in 2.3.0.

<p>Publish Date: 2018-09-05
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-1000232>CVE-2016-1000232</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://www.npmjs.com/advisories/130"">https://www.npmjs.com/advisories/130</a></p>
<p>Release Date: 2018-09-05</p>
<p>Fix Resolution: 2.3.0</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""tough-cookie"",""packageVersion"":""2.2.2"",""isTransitiveDependency"":true,""dependencyTree"":""grunt-retire:0.3.12;request:2.67.0;tough-cookie:2.2.2"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""2.3.0""}],""vulnerabilityIdentifier"":""CVE-2016-1000232"",""vulnerabilityDetails"":""NodeJS Tough-Cookie version 2.2.2 contains a Regular Expression Parsing vulnerability in HTTP request Cookie Header parsing that can result in Denial of Service. This attack appear to be exploitable via Custom HTTP header passed by client. This vulnerability appears to have been fixed in 2.3.0."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-1000232"",""cvss3Severity"":""medium"",""cvss3Score"":""5.3"",""cvss3Metrics"":{""A"":""Low"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""None"",""AV"":""Network"",""I"":""None""},""extraData"":{}}</REMEDIATE> -->",0,cve      medium  detected in tough cookie       tgz      cve       medium severity vulnerability     vulnerable library    tough cookie       tgz        cookies and cookie jar for node js   library home page   a href     path to dependency file  nodegoat package json   path to vulnerable library  nodegoat node modules grunt retire node modules tough cookie package json     dependency hierarchy      grunt retire       tgz  root library        request       tgz          x    tough cookie       tgz    vulnerable library   found in head commit   a href     found in base branch   master              vulnerability details         nodejs tough cookie version       contains a regular expression parsing vulnerability in http request cookie header parsing that can result in denial of service  this attack appear to be exploitable via custom http header passed by client  this vulnerability appears to have been fixed in          publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  low   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                     isopenpronvulnerability  true  ispackagebased  true  isdefaultbranch  true  packages     vulnerabilityidentifier   cve       vulnerabilitydetails   nodejs tough cookie version       contains a regular expression parsing vulnerability in http request cookie header parsing that can result in denial of service  this attack appear to be exploitable via custom http header passed by client  this vulnerability appears to have been fixed in          vulnerabilityurl        ,0
8447,26966972645.0,IssuesEvent,2023-02-08 23:29:06,influxdata/ui,https://api.github.com/repos/influxdata/ui,closed,Save Query/Script Option,team/automation,"## User Story

<p></p>

As a user, I want to be able to save the query/script I am working on so that I can come back to it later and re-load it and edit or use it again in the future.

## Acceptance Criteria

<p></p>

- When editing a query/script, a save option will be available to the user

- When the user clicks on the save option, they will be given the option to rename the file from the original/preselected name, if they have not already saved it- Once saved, the query/script will be available later to load


<p></p>

## Notes

<p></p>

Versioning and labels will come in future stories and is not expected for this particular story.

<p></p>

Reference:  Proposal on behavior:  <https://docs.google.com/document/d/13C6JZ7CscZMTIzG_3WMCgnOCCjtZYkGKNDUgSh0YiPw/edit#heading=h.mm433mqts43v>

<p></p>

<p></p>",1.0,"Save Query/Script Option - ## User Story

<p></p>

As a user, I want to be able to save the query/script I am working on so that I can come back to it later and re-load it and edit or use it again in the future.

## Acceptance Criteria

<p></p>

- When editing a query/script, a save option will be available to the user

- When the user clicks on the save option, they will be given the option to rename the file from the original/preselected name, if they have not already saved it- Once saved, the query/script will be available later to load


<p></p>

## Notes

<p></p>

Versioning and labels will come in future stories and is not expected for this particular story.

<p></p>

Reference:  Proposal on behavior:  <https://docs.google.com/document/d/13C6JZ7CscZMTIzG_3WMCgnOCCjtZYkGKNDUgSh0YiPw/edit#heading=h.mm433mqts43v>

<p></p>

<p></p>",0,save query script option      user story      as a user  i want to be able to save the query script i am working on so that i can come back to it later and re load it and edit or use it again in the future      acceptance criteria        when editing a query script  a save option will be available to the user    when the user clicks on the save option  they will be given the option to rename the file from the original preselected name  if they have not already saved it  once saved  the query script will be available later to load          notes      versioning and labels will come in future stories and is not expected for this particular story       reference   proposal on behavior             ,0
5536,20013055973.0,IssuesEvent,2022-02-01 09:12:20,keptn/keptn,https://api.github.com/repos/keptn/keptn,closed,Add CI run info and k8s resource info to (pre-)releases,release-automation area:devops,"**Is your feature request related to a problem? Please describe.**
Before the new release automation, releases for GH were generated during integration test runs. Those also added additional information about the CI run, k8s resource limit info and other things as metadata to the release notes.
With the new release automation, this behaviour was not carried over but is still needed.

**Describe the solution you'd like**
Carry over the steps to generate additional info and metadata and attach that info to the release notes in the (pre-)release pipelines.

For the k8s resource limits, a new way of getting the resource data needs to be found. Before, the data was fetched from an active cluster but since the release process is not included in the integration test pipeline anymore, there is no option to get that data from an active cluster.

**Additional context**
The relevant code in the integration test pipeline: https://github.com/keptn/keptn/blob/master/.github/workflows/integration_tests.yml#L728-L1006",1.0,"Add CI run info and k8s resource info to (pre-)releases - **Is your feature request related to a problem? Please describe.**
Before the new release automation, releases for GH were generated during integration test runs. Those also added additional information about the CI run, k8s resource limit info and other things as metadata to the release notes.
With the new release automation, this behaviour was not carried over but is still needed.

**Describe the solution you'd like**
Carry over the steps to generate additional info and metadata and attach that info to the release notes in the (pre-)release pipelines.

For the k8s resource limits, a new way of getting the resource data needs to be found. Before, the data was fetched from an active cluster but since the release process is not included in the integration test pipeline anymore, there is no option to get that data from an active cluster.

**Additional context**
The relevant code in the integration test pipeline: https://github.com/keptn/keptn/blob/master/.github/workflows/integration_tests.yml#L728-L1006",0,add ci run info and   resource info to  pre  releases     is your feature request related to a problem  please describe    before the new release automation  releases for gh were generated during integration test runs  those also added additional information about the ci run    resource limit info and other things as metadata to the release notes  with the new release automation  this behaviour was not carried over but is still needed     describe the solution you d like   carry over the steps to generate additional info and metadata and attach that info to the release notes in the  pre  release pipelines   for the   resource limits  a new way of getting the resource data needs to be found  before  the data was fetched from an active cluster but since the release process is not included in the integration test pipeline anymore  there is no option to get that data from an active cluster     additional context   the relevant code in the integration test pipeline   ,0
229783,17577633023.0,IssuesEvent,2021-08-15 22:50:45,golang/go,https://api.github.com/repos/golang/go,closed,sync/atomic: CompareAndSwapPointer should be CompareAndSwap [1.17 backport],Documentation CherryPickApproved,"@rhysh requested issue #47699 to be considered for backport to the next 1.17 minor release.

> CC @golang/release , this is a new API for Go 1.17, and the release branch doesn't have the fix yet (see https://github.com/golang/go/blob/release-branch.go1.17/src/sync/atomic/value.go#L129 ). For your consideration, so it doesn't get lost in the shuffle on Monday.
> 
> @gopherbot please backport to 1.17
",1.0,"sync/atomic: CompareAndSwapPointer should be CompareAndSwap [1.17 backport] - @rhysh requested issue #47699 to be considered for backport to the next 1.17 minor release.

> CC @golang/release , this is a new API for Go 1.17, and the release branch doesn't have the fix yet (see https://github.com/golang/go/blob/release-branch.go1.17/src/sync/atomic/value.go#L129 ). For your consideration, so it doesn't get lost in the shuffle on Monday.
> 
> @gopherbot please backport to 1.17
",1,sync atomic  compareandswappointer should be compareandswap      rhysh requested issue    to be considered for backport to the next     minor release     cc  golang release   this is a new api for go      and the release branch doesn t have the fix yet  see      for your consideration  so it doesn t get lost in the shuffle on monday          gopherbot please backport to     ,1
22754,4836094179.0,IssuesEvent,2016-11-08 18:37:14,golang/go,https://api.github.com/repos/golang/go,closed,path: Documentation regarding `/` support,Documentation,"### What version of Go are you using (`go version`)?
`go version go1.7 windows/amd64`

### What operating system and processor architecture are you using (`go env`)?
```
set GOARCH=amd64
set GOBIN=C:\Users\tjenkins\go-dev\bin
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\Users\tjenkins\go-dev
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\tjenkins\AppData\Local\Temp\go-build759658326=/tmp/go-build -gno-record-gcc-switches
set CXX=g++
set CGO_ENABLED=1
```

### What did you do?
Creating files on the system and later retrieving them via `filepath.Glob`. Code further downstream took the returned paths and utilized `path.Base` to find the base portion, this failed due to the `\` vs `/` difference.

### What did you expect to see
Would prefer if the package documentation for `path` make explicit mention of the lack of support for systems that are not `/` separated, directing the user to sub package `filepath`. It mentions slash-separated, which was taken to mean `/` or `\`.

Thanks!",1.0,"path: Documentation regarding `/` support - ### What version of Go are you using (`go version`)?
`go version go1.7 windows/amd64`

### What operating system and processor architecture are you using (`go env`)?
```
set GOARCH=amd64
set GOBIN=C:\Users\tjenkins\go-dev\bin
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\Users\tjenkins\go-dev
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\tjenkins\AppData\Local\Temp\go-build759658326=/tmp/go-build -gno-record-gcc-switches
set CXX=g++
set CGO_ENABLED=1
```

### What did you do?
Creating files on the system and later retrieving them via `filepath.Glob`. Code further downstream took the returned paths and utilized `path.Base` to find the base portion, this failed due to the `\` vs `/` difference.

### What did you expect to see
Would prefer if the package documentation for `path` make explicit mention of the lack of support for systems that are not `/` separated, directing the user to sub package `filepath`. It mentions slash-separated, which was taken to mean `/` or `\`.

Thanks!",1,path  documentation regarding     support       what version of go are you using   go version      go version     windows           what operating system and processor architecture are you using   go env          set goarch    set gobin c  users tjenkins go dev bin  set goexe  exe  set gohostarch    set gohostos windows  set goos windows  set gopath c  users tjenkins go dev  set gorace   set goroot c  go  set gotooldir c  go pkg tool windows    set cc gcc  set gogccflags     mthreads  fmessage length    fdebug prefix map c  users tjenkins appdata local temp go    tmp go build  gno record gcc switches  set cxx g    set cgo enabled               what did you do   creating files on the system and later retrieving them via  filepath glob   code further downstream took the returned paths and utilized  path base  to find the base portion  this failed due to the     vs     difference         what did you expect to see  would prefer if the package documentation for  path  make explicit mention of the lack of support for systems that are not     separated  directing the user to sub package  filepath   it mentions slash separated  which was taken to mean     or         thanks ,1
413677,27963975050.0,IssuesEvent,2023-03-24 17:48:59,golang/go,https://api.github.com/repos/golang/go,closed,x/pkgsite: CreateOrder example on go.dev/doc/database/execute-transactions page doesn't compile,Documentation NeedsFix,"<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What is the URL of the page with the issue?

https://go.dev/doc/database/execute-transactions

### What is your user agent?

Firefox 94.0 (64-bit)

### Screenshot

The `fail` function (below the marked comment), expects 2 return values. However, the function only returns `fmt.Errorf(...)`.

![image](https://user-images.githubusercontent.com/7077157/148627818-64471923-ca04-486b-99be-b135af3c009f.png)

### What did you do?

I copy-pasted the code to my IDE (VS Code) and got an error (the `return` line was marked with a red line).

### What did you expect to see?

There should be no error in the copy-pasted function. It should return, maybe, `0, fmt.Errorf(...)`?

### What did you see instead?

Error during compilation.

```
./main.go:229:3: not enough arguments to return
	have (error)
	want (int64, error)
```

I'm new to Go, so please let me know if I did something wrong instead. Thanks!",1.0,"x/pkgsite: CreateOrder example on go.dev/doc/database/execute-transactions page doesn't compile - <!--
Please answer these questions before submitting your issue. Thanks!
-->

### What is the URL of the page with the issue?

https://go.dev/doc/database/execute-transactions

### What is your user agent?

Firefox 94.0 (64-bit)

### Screenshot

The `fail` function (below the marked comment), expects 2 return values. However, the function only returns `fmt.Errorf(...)`.

![image](https://user-images.githubusercontent.com/7077157/148627818-64471923-ca04-486b-99be-b135af3c009f.png)

### What did you do?

I copy-pasted the code to my IDE (VS Code) and got an error (the `return` line was marked with a red line).

### What did you expect to see?

There should be no error in the copy-pasted function. It should return, maybe, `0, fmt.Errorf(...)`?

### What did you see instead?

Error during compilation.

```
./main.go:229:3: not enough arguments to return
	have (error)
	want (int64, error)
```

I'm new to Go, so please let me know if I did something wrong instead. Thanks!",1,x pkgsite  createorder example on go dev doc database execute transactions page doesn t compile         please answer these questions before submitting your issue  thanks              what is the url of the page with the issue              what is your user agent     firefox        bit         screenshot    the  fail  function  below the marked comment   expects   return values  however  the function only returns  fmt errorf                       what did you do     i copy pasted the code to my ide  vs code  and got an error  the  return  line was marked with a red line          what did you expect to see     there should be no error in the copy pasted function  it should return  maybe      fmt errorf               what did you see instead     error during compilation            main go      not enough arguments to return  	have  error   	want     error          i m new to go  so please let me know if i did something wrong instead  thanks ,1
100762,30769394285.0,IssuesEvent,2023-07-30 18:07:42,neovim/neovim,https://api.github.com/repos/neovim/neovim,closed,crashes when opening any file (OpenBSD 7.2),bug build platform:bsd,"### Problem

command ""nvim file.txt"" crashes immediately.
nvim by itself works but once you open a file with "":e file.txt"" it crashes.

### Steps to reproduce

I compiled latest release following the instructions:

cmake ../cmake.deps/ -DUSE_BUNDLED=OFF -DUSE_BUNDLED_LIBUV=ON -DUSE_BUNDLED_LUV=ON -DUSE_BUNDLED_LIBVTERM=ON -DUSE_BUNDLED_TS=ON -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_C_COMPILER=egcc

cmake .. -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_C_COMPILER=egcc

I ran into a problem where dependency headers like <vterm.h> were different than the ones provided in .deps and it didn't compile at first (unknown symbol VTStringFragment or something like that). After replacing the includes with this script:

      import os
      
      BASE = os.getcwd()
      DEPS_BASE = "".deps/build/src/""
      SRC_BASE = ""src/nvim/""
      
      deps = []
      for dep in os.listdir(DEPS_BASE):
          for path, name, files in os.walk(DEPS_BASE + dep + ""/include""):
              for f in files:
                  if f.endswith("".h""):
                      deps.append((f, BASE + ""/"" + path + ""/"" + f))
      for path, name, files in os.walk(SRC_BASE):
          for f in files:
              if f.endswith("".c""):
                  contents = """"
                  with open(path + ""/"" + f, ""r"") as h:
                      contents = h.read()
                      for dep, p in deps:
                          if f""<{dep}>"" in contents:
                              print(f""{f}: <{dep}> -> \""{p}\"""")
                              contents = contents.replace(f""<{dep}>"", f""\""{p}\"""")
                              #print(contents[:500])
                  with open(path + ""/"" + f, ""w"") as h:
                      written = 0
                      while written < len(contents):
                          w = h.write(contents)
                          written += w
                          contents = contents[w:]
compilation worked and I got the executable that crashes when you open a file. 
.config/nvim
.local/share/nvim
.cache/nvim
have all been cleared. Also crashes after running :checkhealth eventhough :checkhealth doesn't give any errors. After further testing I can say that it crashes with almost every command. ""!"" works though.


### Expected behavior

Doesn't crash when opening a file.

### Neovim version (nvim -v)

0.9.1

### Vim (not Nvim) behaves the same?

NA

### Operating system/version

OpenBSD 7.2

### Terminal name/version

terminator 1.92

### $TERM environment variable

xterm-256color

### Installation

cmake",1.0,"crashes when opening any file (OpenBSD 7.2) - ### Problem

command ""nvim file.txt"" crashes immediately.
nvim by itself works but once you open a file with "":e file.txt"" it crashes.

### Steps to reproduce

I compiled latest release following the instructions:

cmake ../cmake.deps/ -DUSE_BUNDLED=OFF -DUSE_BUNDLED_LIBUV=ON -DUSE_BUNDLED_LUV=ON -DUSE_BUNDLED_LIBVTERM=ON -DUSE_BUNDLED_TS=ON -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_C_COMPILER=egcc

cmake .. -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_C_COMPILER=egcc

I ran into a problem where dependency headers like <vterm.h> were different than the ones provided in .deps and it didn't compile at first (unknown symbol VTStringFragment or something like that). After replacing the includes with this script:

      import os
      
      BASE = os.getcwd()
      DEPS_BASE = "".deps/build/src/""
      SRC_BASE = ""src/nvim/""
      
      deps = []
      for dep in os.listdir(DEPS_BASE):
          for path, name, files in os.walk(DEPS_BASE + dep + ""/include""):
              for f in files:
                  if f.endswith("".h""):
                      deps.append((f, BASE + ""/"" + path + ""/"" + f))
      for path, name, files in os.walk(SRC_BASE):
          for f in files:
              if f.endswith("".c""):
                  contents = """"
                  with open(path + ""/"" + f, ""r"") as h:
                      contents = h.read()
                      for dep, p in deps:
                          if f""<{dep}>"" in contents:
                              print(f""{f}: <{dep}> -> \""{p}\"""")
                              contents = contents.replace(f""<{dep}>"", f""\""{p}\"""")
                              #print(contents[:500])
                  with open(path + ""/"" + f, ""w"") as h:
                      written = 0
                      while written < len(contents):
                          w = h.write(contents)
                          written += w
                          contents = contents[w:]
compilation worked and I got the executable that crashes when you open a file. 
.config/nvim
.local/share/nvim
.cache/nvim
have all been cleared. Also crashes after running :checkhealth eventhough :checkhealth doesn't give any errors. After further testing I can say that it crashes with almost every command. ""!"" works though.


### Expected behavior

Doesn't crash when opening a file.

### Neovim version (nvim -v)

0.9.1

### Vim (not Nvim) behaves the same?

NA

### Operating system/version

OpenBSD 7.2

### Terminal name/version

terminator 1.92

### $TERM environment variable

xterm-256color

### Installation

cmake",0,crashes when opening any file  openbsd            problem    command  nvim file txt  crashes immediately   nvim by itself works but once you open a file with   e file txt  it crashes         steps to reproduce    i compiled latest release following the instructions     cmake    cmake deps   duse bundled off  duse bundled libuv on  duse bundled luv on  duse bundled libvterm on  duse bundled ts on  dcmake build type relwithdebinfo  dcmake c compiler egcc    cmake     dcmake build type relwithdebinfo  dcmake c compiler egcc    i ran into a problem where dependency headers like   were different than the ones provided in  deps and it didn t compile at first  unknown symbol vtstringfragment or something like that   after replacing the includes with this script           import os                base   os getcwd          deps base     deps build src          src base    src nvim                  deps            for dep in os listdir deps base              for path  name  files in os walk deps base   dep     include                   for f in files                     if f endswith   h                           deps append  f  base         path         f          for path  name  files in os walk src base              for f in files                 if f endswith   c                       contents                         with open path         f   r   as h                         contents   h read                          for dep  p in deps                             if f    in contents                                 print f  f           p                                     contents   contents replace f     f    p                                      print contents                      with open path         f   w   as h                         written                            while written   len contents                              w   h write contents                             written    w                            contents   contents   compilation worked and i got the executable that crashes when you open a file     config nvim   local share nvim   cache nvim  have all been cleared  also crashes after running  checkhealth eventhough  checkhealth doesn t give any errors  after further testing i can say that it crashes with almost every command      works though           expected behavior    doesn t crash when opening a file         neovim version  nvim  v                  vim  not nvim  behaves the same     na        operating system version    openbsd            terminal name version    terminator             term environment variable    xterm          installation    cmake,0
5291,5556338480.0,IssuesEvent,2017-03-24 08:52:15,hzi-braunschweig/SORMAS-Open,https://api.github.com/repos/hzi-braunschweig/SORMAS-Open,closed,Short captions for personas (user roles) [0],accepted Infrastructure optional sormas-api sormas-app sormas-backend,"Should be used for the text representation of a user (e.g. ""Sanaa OBASANJO - SurvOff"")

SurvOff, ContOff, CaseOff, RumOff, SurvSup, ContSup, CaseSup, LabMan",1.0,"Short captions for personas (user roles) [0] - Should be used for the text representation of a user (e.g. ""Sanaa OBASANJO - SurvOff"")

SurvOff, ContOff, CaseOff, RumOff, SurvSup, ContSup, CaseSup, LabMan",0,short captions for personas  user roles      should be used for the text representation of a user  e g   sanaa obasanjo   survoff      survoff  contoff  caseoff  rumoff  survsup  contsup  casesup  labman,0
6074,3000686612.0,IssuesEvent,2015-07-24 04:41:01,golang/go,https://api.github.com/repos/golang/go,opened,doc: document the way the tools work,Documentation,"Nowhere is it explained how go build constructs software: how the compiler and linker run, where files are placed, how test builds its code, and so on. There should be an implementation and explanation document outlining this process. Such a document would also help someone who must use Go from within an existing software construction system.
",1.0,"doc: document the way the tools work - Nowhere is it explained how go build constructs software: how the compiler and linker run, where files are placed, how test builds its code, and so on. There should be an implementation and explanation document outlining this process. Such a document would also help someone who must use Go from within an existing software construction system.
",1,doc  document the way the tools work   nowhere is it explained how go build constructs software  how the compiler and linker run  where files are placed  how test builds its code  and so on  there should be an implementation and explanation document outlining this process  such a document would also help someone who must use go from within an existing software construction system   ,1
77383,9993917866.0,IssuesEvent,2019-07-11 16:21:52,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/gopls: handle 404-ing links in documentLink,Documentation gopls,"Related to discussion on https://github.com/microsoft/vscode-go/issues/2614.
Would it be reasonable to test that a link is valid in `textDocument/documentLink`?",1.0,"x/tools/gopls: handle 404-ing links in documentLink - Related to discussion on https://github.com/microsoft/vscode-go/issues/2614.
Would it be reasonable to test that a link is valid in `textDocument/documentLink`?",1,x tools gopls  handle   ing links in documentlink   related to discussion on    would it be reasonable to test that a link is valid in  textdocument documentlink  ,1
78704,10082124595.0,IssuesEvent,2019-07-25 10:24:18,golang/go,https://api.github.com/repos/golang/go,closed,doc: wrong link in release history,Documentation NeedsFix,"### What did you do?
I visited the [release history](https://golang.org/doc/devel/release.html) page for the Go language.

### What did you expect to see?
I expected the minor revisions' links to be correct.

### What did you see instead?
Instead, the link to the [go1.6.4 milestone](https://golang.org/doc/devel/release.html#go1.6.minor) does not exist and in its place there is a link to the 1.7.4 milestone.
The same happens with go1.7.6 and go1.5.4.",1.0,"doc: wrong link in release history - ### What did you do?
I visited the [release history](https://golang.org/doc/devel/release.html) page for the Go language.

### What did you expect to see?
I expected the minor revisions' links to be correct.

### What did you see instead?
Instead, the link to the [go1.6.4 milestone](https://golang.org/doc/devel/release.html#go1.6.minor) does not exist and in its place there is a link to the 1.7.4 milestone.
The same happens with go1.7.6 and go1.5.4.",1,doc  wrong link in release history       what did you do   i visited the     page for the go language         what did you expect to see   i expected the minor revisions  links to be correct         what did you see instead   instead  the link to the     does not exist and in its place there is a link to the       milestone   the same happens with       and       ,1
75768,15495570425.0,IssuesEvent,2021-03-11 01:05:48,ignatandrei/SimpleBookRental,https://api.github.com/repos/ignatandrei/SimpleBookRental,opened,CVE-2020-28481 (Medium) detected in socket.io-2.1.1.tgz,security vulnerability,"## CVE-2020-28481 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>socket.io-2.1.1.tgz</b></p></summary>

<p>node.js realtime framework server</p>
<p>Library home page: <a href=""https://registry.npmjs.org/socket.io/-/socket.io-2.1.1.tgz"">https://registry.npmjs.org/socket.io/-/socket.io-2.1.1.tgz</a></p>
<p>Path to dependency file: SimpleBookRental/src/WebDashboardNG/book-dash/package.json</p>
<p>Path to vulnerable library: SimpleBookRental/src/WebDashboardNG/book-dash/node_modules/socket.io/package.json</p>
<p>

Dependency Hierarchy:
  - karma-4.4.1.tgz (Root Library)
    - :x: **socket.io-2.1.1.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The package socket.io before 2.4.0 are vulnerable to Insecure Defaults due to CORS Misconfiguration. All domains are whitelisted by default.

<p>Publish Date: 2021-01-19
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28481>CVE-2020-28481</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>4.3</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: None
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28481"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28481</a></p>
<p>Release Date: 2021-01-19</p>
<p>Fix Resolution: 2.4.0</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2020-28481 (Medium) detected in socket.io-2.1.1.tgz - ## CVE-2020-28481 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>socket.io-2.1.1.tgz</b></p></summary>

<p>node.js realtime framework server</p>
<p>Library home page: <a href=""https://registry.npmjs.org/socket.io/-/socket.io-2.1.1.tgz"">https://registry.npmjs.org/socket.io/-/socket.io-2.1.1.tgz</a></p>
<p>Path to dependency file: SimpleBookRental/src/WebDashboardNG/book-dash/package.json</p>
<p>Path to vulnerable library: SimpleBookRental/src/WebDashboardNG/book-dash/node_modules/socket.io/package.json</p>
<p>

Dependency Hierarchy:
  - karma-4.4.1.tgz (Root Library)
    - :x: **socket.io-2.1.1.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The package socket.io before 2.4.0 are vulnerable to Insecure Defaults due to CORS Misconfiguration. All domains are whitelisted by default.

<p>Publish Date: 2021-01-19
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28481>CVE-2020-28481</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>4.3</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: None
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28481"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28481</a></p>
<p>Release Date: 2021-01-19</p>
<p>Fix Resolution: 2.4.0</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      medium  detected in socket io       tgz      cve       medium severity vulnerability     vulnerable library    socket io       tgz      node js realtime framework server   library home page   a href     path to dependency file  simplebookrental src webdashboardng book dash package json   path to vulnerable library  simplebookrental src webdashboardng book dash node modules socket io package json     dependency hierarchy      karma       tgz  root library         x    socket io       tgz    vulnerable library             vulnerability details         the package socket io before       are vulnerable to insecure defaults due to cors misconfiguration  all domains are whitelisted by default    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  low     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  low     integrity impact  none     availability impact  none   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                      step up your open source security game with whitesource    ,0
146433,5621402743.0,IssuesEvent,2017-04-04 09:51:54,dangvd/ksmoothdock,https://api.github.com/repos/dangvd/ksmoothdock,opened,Weird animation if focus is lost when mouse is still over the dock,Priority: Low Type: Bug,"For example:
- Click on Software Manager launcher (asking for password)
- Right click, Cancel, then Right click again",1.0,"Weird animation if focus is lost when mouse is still over the dock - For example:
- Click on Software Manager launcher (asking for password)
- Right click, Cancel, then Right click again",0,weird animation if focus is lost when mouse is still over the dock   for example     click on software manager launcher  asking for password     right click  cancel  then right click again,0
108063,11579674191.0,IssuesEvent,2020-02-21 18:27:03,golang/go,https://api.github.com/repos/golang/go,closed,encoding/json: document change in Number behavior for 1.14,Documentation NeedsFix release-blocker,"I just upgraded one of our internal repositories to Go 1.14rc1 and our tests failed. 

The reason the tests failed is due to this issue: https://github.com/golang/go/issues/14702

I had to go in and update our code base to make Go 1.14 work, so it's technically a breaking change. 

More dangerously, this is a **runtime** breaking change and not a compile time one. 

so I can only imagine the number of Go apps out there running in production that would break because of this. 

As much as I like the new behavior, I imagine this might cause some production apps to go down in the wild. 

On one hand, the repository was incorrectly using json.Number and treating it as something that *could* be a number, but would also **allow strings**. In fact, people probably assume that's what json.Number is since it is of type string. 

I'm opening a new issue instead of commenting on the old one because I'd like to bring light into this breaking behavior and make sure we have a decision before Go 1.14 is officially released.

cc: @mvdan @rsc  

Thanks! 

$ go version
Go 1.14rc1, darwin
</pre>

",1.0,"encoding/json: document change in Number behavior for 1.14 - I just upgraded one of our internal repositories to Go 1.14rc1 and our tests failed. 

The reason the tests failed is due to this issue: https://github.com/golang/go/issues/14702

I had to go in and update our code base to make Go 1.14 work, so it's technically a breaking change. 

More dangerously, this is a **runtime** breaking change and not a compile time one. 

so I can only imagine the number of Go apps out there running in production that would break because of this. 

As much as I like the new behavior, I imagine this might cause some production apps to go down in the wild. 

On one hand, the repository was incorrectly using json.Number and treating it as something that *could* be a number, but would also **allow strings**. In fact, people probably assume that's what json.Number is since it is of type string. 

I'm opening a new issue instead of commenting on the old one because I'd like to bring light into this breaking behavior and make sure we have a decision before Go 1.14 is officially released.

cc: @mvdan @rsc  

Thanks! 

$ go version
Go 1.14rc1, darwin
</pre>

",1,encoding json  document change in number behavior for       i just upgraded one of our internal repositories to go     and our tests failed      the reason the tests failed is due to this issue       i had to go in and update our code base to make go     work  so it s technically a breaking change      more dangerously  this is a   runtime   breaking change and not a compile time one      so i can only imagine the number of go apps out there running in production that would break because of this      as much as i like the new behavior  i imagine this might cause some production apps to go down in the wild      on one hand  the repository was incorrectly using json number and treating it as something that  could  be a number  but would also   allow strings    in fact  people probably assume that s what json number is since it is of type string      i m opening a new issue instead of commenting on the old one because i d like to bring light into this breaking behavior and make sure we have a decision before go     is officially released     cc   mvdan  rsc      thanks        go version  go      darwin       ,1
756748,26484341637.0,IssuesEvent,2023-01-17 16:49:45,wso2/api-manager,https://api.github.com/repos/wso2/api-manager,closed,API Endpoint OAUTH2 Password Issue,Type/Bug Priority/Normal Resolution/Fixed Component/APIM Affected/APIM-3.2.0 U2/WUM,"### Description:
<!-- Describe the issue -->
Identified an issue with securing endpoints with OAuth2.0 while modifying the endpoint security parameters for every API.

### Steps to reproduce:
<!-- List the steps you followed when you encountered the issue -->

- Created a mock API as the token API
- Created a testing API and under the endpoint configuration security section added OAuth2.0 endpoint security with Password grant type.
- Saved the changes
- Once the API synapse file of the testing API is investigated, could find that the username and password is stored to a synapse property with base64 encoding and once it is decoded a given username and password could be retrieved.
- Then 
 -- opened the security configurations under the endpoint again through the publisher portal.
 -- did not make any change
 -- clicked on the save button.
- After that, the same synapse property was investigated under the API and could identify the actual password was overwritten by a few * symbols.

### Affected product version:
<!-- Members can use Affected/*** labels -->
APIM 3.2.0
",1.0,"API Endpoint OAUTH2 Password Issue - ### Description:
<!-- Describe the issue -->
Identified an issue with securing endpoints with OAuth2.0 while modifying the endpoint security parameters for every API.

### Steps to reproduce:
<!-- List the steps you followed when you encountered the issue -->

- Created a mock API as the token API
- Created a testing API and under the endpoint configuration security section added OAuth2.0 endpoint security with Password grant type.
- Saved the changes
- Once the API synapse file of the testing API is investigated, could find that the username and password is stored to a synapse property with base64 encoding and once it is decoded a given username and password could be retrieved.
- Then 
 -- opened the security configurations under the endpoint again through the publisher portal.
 -- did not make any change
 -- clicked on the save button.
- After that, the same synapse property was investigated under the API and could identify the actual password was overwritten by a few * symbols.

### Affected product version:
<!-- Members can use Affected/*** labels -->
APIM 3.2.0
",0,api endpoint   password issue       description      identified an issue with securing endpoints with     while modifying the endpoint security parameters for every api         steps to reproduce          created a mock api as the token api    created a testing api and under the endpoint configuration security section added     endpoint security with password grant type     saved the changes    once the api synapse file of the testing api is investigated  could find that the username and password is stored to a synapse property with   encoding and once it is decoded a given username and password could be retrieved     then       opened the security configurations under the endpoint again through the publisher portal       did not make any change      clicked on the save button     after that  the same synapse property was investigated under the api and could identify the actual password was overwritten by a few   symbols         affected product version      apim        ,0
144684,5544107187.0,IssuesEvent,2017-03-22 18:22:03,graphcool/console,https://api.github.com/repos/graphcool/console,closed,UX: Make sidebar collapsible,area/sidebar onhold priority/low UI UX,"Currently the sidebar occupies a decent amount of screen real-estate, particularly so in the Playground; It'd be nice if the sidebar could collapse out of the way (perhaps just to icons?)",1.0,"UX: Make sidebar collapsible - Currently the sidebar occupies a decent amount of screen real-estate, particularly so in the Playground; It'd be nice if the sidebar could collapse out of the way (perhaps just to icons?)",0,ux  make sidebar collapsible   currently the sidebar occupies a decent amount of screen real estate  particularly so in the playground  it d be nice if the sidebar could collapse out of the way  perhaps just to icons  ,0
76083,3481062548.0,IssuesEvent,2015-12-29 13:28:55,FLEXIcontent/flexicontent-cck,https://api.github.com/repos/FLEXIcontent/flexicontent-cck,closed,"Add option to turn off email cloaking in email field, aka insert real email links",enhancement Priority Normal,"Should we add a configuration option to control whether we want to render link and force email cloaking?

In this line:
```
$html = $format != 'feed' ?
	JHTML::_('email.cloak', $addr, 1, $text, $text_is_email) :
	'<a href=""mailto:'.$addr.'"" target=""_blank"" itemprop=""email"">' .$text. '</a>';
```
https://github.com/FLEXIcontent/flexicontent-cck/blob/master/plugins/flexicontent_fields/email/tmpl/value_default.php#L28

We have a situation where we need email addresses to be rendered explicitly, and with a link. I can make the changes and submit for your review.",1.0,"Add option to turn off email cloaking in email field, aka insert real email links - Should we add a configuration option to control whether we want to render link and force email cloaking?

In this line:
```
$html = $format != 'feed' ?
	JHTML::_('email.cloak', $addr, 1, $text, $text_is_email) :
	'<a href=""mailto:'.$addr.'"" target=""_blank"" itemprop=""email"">' .$text. '</a>';
```
https://github.com/FLEXIcontent/flexicontent-cck/blob/master/plugins/flexicontent_fields/email/tmpl/value_default.php#L28

We have a situation where we need email addresses to be rendered explicitly, and with a link. I can make the changes and submit for your review.",0,add option to turn off email cloaking in email field  aka insert real email links   should we add a configuration option to control whether we want to render link and force email cloaking     in this line         html    format     feed     	jhtml     email cloak    addr      text   text is email     	      text                  we have a situation where we need email addresses to be rendered explicitly  and with a link  i can make the changes and submit for your review ,0
182110,6667217326.0,IssuesEvent,2017-10-03 11:39:08,HelpyTeam/HelpyWeb,https://api.github.com/repos/HelpyTeam/HelpyWeb,opened,Update front-end,Front-end priority/3 To-do,"# Overview
Update the front-end
# Target
After update, please note the components that you had updated and send pull request.",1.0,"Update front-end - # Overview
Update the front-end
# Target
After update, please note the components that you had updated and send pull request.",0,update front end     overview  update the front end    target  after update  please note the components that you had updated and send pull request ,0
375689,11132884458.0,IssuesEvent,2019-12-20 08:02:05,ahmedkaludi/accelerated-mobile-pages,https://api.github.com/repos/ahmedkaludi/accelerated-mobile-pages,closed,MGID Ads are not loading because it is unable to fetch attributes when the Flexible AMP widget option is enabled in the AMP>>Advertisement Section.,NEXT UPDATE [Priority: HIGH] bug,"1. When the Flexible AMP widget option is turned on, the Ads are not loaded as it is not getting the attributes. 
Screenshot:- https://monosnap.com/file/HPWy6SMgTB3VkcfCRpA8cgUh0pMrS9
2. When the Flexible AMP widget option is turned off, the ads will be fixed on the same height-width in the mobile view too.
Screenshot:- https://monosnap.com/file/Ftn8tNSl2Lzl4Q5t0SJyJjdxmi19Kw",1.0,"MGID Ads are not loading because it is unable to fetch attributes when the Flexible AMP widget option is enabled in the AMP>>Advertisement Section. - 1. When the Flexible AMP widget option is turned on, the Ads are not loaded as it is not getting the attributes. 
Screenshot:- https://monosnap.com/file/HPWy6SMgTB3VkcfCRpA8cgUh0pMrS9
2. When the Flexible AMP widget option is turned off, the ads will be fixed on the same height-width in the mobile view too.
Screenshot:- https://monosnap.com/file/Ftn8tNSl2Lzl4Q5t0SJyJjdxmi19Kw",0,mgid ads are not loading because it is unable to fetch attributes when the flexible amp widget option is enabled in the amp  advertisement section       when the flexible amp widget option is turned on  the ads are not loaded as it is not getting the attributes    screenshot         when the flexible amp widget option is turned off  the ads will be fixed on the same height width in the mobile view too   screenshot    ,0
190587,15251646224.0,IssuesEvent,2021-02-20 00:01:59,golang/go,https://api.github.com/repos/golang/go,closed,spec: Every type should have a method set which may be empty,Documentation NeedsFix,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->


# Problem

The spec says:

> A type may have a method set associated with it.

https://golang.org/ref/spec#Method_sets

This sentence implies it's possible that some types do not have a method set. 
A reader may wonder what's the difference between ""a type with an empty method set"" and ""a type with no  method set"".


I would like to propose a new sentence instead.

# Proposal

```diff
- A type may have a method set associated with it.
+ A type has a method set associated with it.
```

The new sentence would fit well the description about the empty interface:

> A type implements any interface comprising any subset of its methods and may therefore implement several distinct interfaces. For instance, all types implement the empty interface:
> interface{}

https://golang.org/ref/spec#Interface_types",1.0,"spec: Every type should have a method set which may be empty - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->


# Problem

The spec says:

> A type may have a method set associated with it.

https://golang.org/ref/spec#Method_sets

This sentence implies it's possible that some types do not have a method set. 
A reader may wonder what's the difference between ""a type with an empty method set"" and ""a type with no  method set"".


I would like to propose a new sentence instead.

# Proposal

```diff
- A type may have a method set associated with it.
+ A type has a method set associated with it.
```

The new sentence would fit well the description about the empty interface:

> A type implements any interface comprising any subset of its methods and may therefore implement several distinct interfaces. For instance, all types implement the empty interface:
> interface{}

https://golang.org/ref/spec#Interface_types",1,spec  every type should have a method set which may be empty         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                problem    the spec says       a type may have a method set associated with it          this sentence implies it s possible that some types do not have a method set    a reader may wonder what s the difference between  a type with an empty method set  and  a type with no  method set        i would like to propose a new sentence instead       proposal       diff    a type may have a method set associated with it     a type has a method set associated with it          the new sentence would fit well the description about the empty interface       a type implements any interface comprising any subset of its methods and may therefore implement several distinct interfaces  for instance  all types implement the empty interface     interface       ,1
38777,12601772093.0,IssuesEvent,2020-06-11 10:27:07,rammatzkvosky/1010-1,https://api.github.com/repos/rammatzkvosky/1010-1,opened,CVE-2018-12022 (High) detected in jackson-databind-2.8.8.jar,security vulnerability,"## CVE-2018-12022 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.8.8.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: /tmp/ws-scm/1010-1/pom.xml</p>
<p>Path to vulnerable library: epository/com/fasterxml/jackson/core/jackson-databind/2.8.8/jackson-databind-2.8.8.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.8.8.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/rammatzkvosky/1010-1/commit/e42bbbd0a667a61447797ee7b7cee2bbf8be7012"">e42bbbd0a667a61447797ee7b7cee2bbf8be7012</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
An issue was discovered in FasterXML jackson-databind prior to 2.7.9.4, 2.8.11.2, and 2.9.6. When Default Typing is enabled (either globally or for a specific property), the service has the Jodd-db jar (for database access for the Jodd framework) in the classpath, and an attacker can provide an LDAP service to access, it is possible to make the service execute a malicious payload.

<p>Publish Date: 2019-03-21
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-12022>CVE-2018-12022</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: High
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12022"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12022</a></p>
<p>Release Date: 2019-03-21</p>
<p>Fix Resolution: 2.7.9.4, 2.8.11.2, 2.9.6</p>

</p>
</details>
<p></p>

***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""com.fasterxml.jackson.core"",""packageName"":""jackson-databind"",""packageVersion"":""2.8.8"",""isTransitiveDependency"":false,""dependencyTree"":""com.fasterxml.jackson.core:jackson-databind:2.8.8"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""2.7.9.4, 2.8.11.2, 2.9.6""}],""vulnerabilityIdentifier"":""CVE-2018-12022"",""vulnerabilityDetails"":""An issue was discovered in FasterXML jackson-databind prior to 2.7.9.4, 2.8.11.2, and 2.9.6. When Default Typing is enabled (either globally or for a specific property), the service has the Jodd-db jar (for database access for the Jodd framework) in the classpath, and an attacker can provide an LDAP service to access, it is possible to make the service execute a malicious payload."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-12022"",""cvss3Severity"":""high"",""cvss3Score"":""7.5"",""cvss3Metrics"":{""A"":""High"",""AC"":""High"",""PR"":""None"",""S"":""Unchanged"",""C"":""High"",""UI"":""Required"",""AV"":""Network"",""I"":""High""},""extraData"":{}}</REMEDIATE> -->",True,"CVE-2018-12022 (High) detected in jackson-databind-2.8.8.jar - ## CVE-2018-12022 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.8.8.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: /tmp/ws-scm/1010-1/pom.xml</p>
<p>Path to vulnerable library: epository/com/fasterxml/jackson/core/jackson-databind/2.8.8/jackson-databind-2.8.8.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.8.8.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/rammatzkvosky/1010-1/commit/e42bbbd0a667a61447797ee7b7cee2bbf8be7012"">e42bbbd0a667a61447797ee7b7cee2bbf8be7012</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
An issue was discovered in FasterXML jackson-databind prior to 2.7.9.4, 2.8.11.2, and 2.9.6. When Default Typing is enabled (either globally or for a specific property), the service has the Jodd-db jar (for database access for the Jodd framework) in the classpath, and an attacker can provide an LDAP service to access, it is possible to make the service execute a malicious payload.

<p>Publish Date: 2019-03-21
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-12022>CVE-2018-12022</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: High
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12022"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12022</a></p>
<p>Release Date: 2019-03-21</p>
<p>Fix Resolution: 2.7.9.4, 2.8.11.2, 2.9.6</p>

</p>
</details>
<p></p>

***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""com.fasterxml.jackson.core"",""packageName"":""jackson-databind"",""packageVersion"":""2.8.8"",""isTransitiveDependency"":false,""dependencyTree"":""com.fasterxml.jackson.core:jackson-databind:2.8.8"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""2.7.9.4, 2.8.11.2, 2.9.6""}],""vulnerabilityIdentifier"":""CVE-2018-12022"",""vulnerabilityDetails"":""An issue was discovered in FasterXML jackson-databind prior to 2.7.9.4, 2.8.11.2, and 2.9.6. When Default Typing is enabled (either globally or for a specific property), the service has the Jodd-db jar (for database access for the Jodd framework) in the classpath, and an attacker can provide an LDAP service to access, it is possible to make the service execute a malicious payload."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-12022"",""cvss3Severity"":""high"",""cvss3Score"":""7.5"",""cvss3Metrics"":{""A"":""High"",""AC"":""High"",""PR"":""None"",""S"":""Unchanged"",""C"":""High"",""UI"":""Required"",""AV"":""Network"",""I"":""High""},""extraData"":{}}</REMEDIATE> -->",0,cve      high  detected in jackson databind       jar      cve       high severity vulnerability     vulnerable library    jackson databind       jar      general data binding functionality for jackson  works on core streaming api   library home page   a href     path to dependency file   tmp ws scm     pom xml   path to vulnerable library  epository com fasterxml jackson core jackson databind       jackson databind       jar     dependency hierarchy       x    jackson databind       jar    vulnerable library   found in head commit   a href               vulnerability details         an issue was discovered in fasterxml jackson databind prior to                   and        when default typing is enabled  either globally or for a specific property   the service has the jodd db jar  for database access for the jodd framework  in the classpath  and an attacker can provide an ldap service to access  it is possible to make the service execute a malicious payload    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  required     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                                         rescue worker helmet  automatic remediation is available for this issue    isopenpronvulnerability  true  ispackagebased  true  isdefaultbranch  true  packages     vulnerabilityidentifier   cve       vulnerabilitydetails   an issue was discovered in fasterxml jackson databind prior to                   and        when default typing is enabled  either globally or for a specific property   the service has the jodd db jar  for database access for the jodd framework  in the classpath  and an attacker can provide an ldap service to access  it is possible to make the service execute a malicious payload    vulnerabilityurl        ,0
22096,4772943492.0,IssuesEvent,2016-10-26 22:25:48,golang/go,https://api.github.com/repos/golang/go,closed,net/http: ambiguous sentence in docs for Response.ParseForm,Documentation NeedsFix,"Please answer these questions before submitting your issue. Thanks!

1 What version of Go are you using (`go version`)?

go1.6.2

2 What operating system and processor architecture are you using (`go env`)?

```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/cjohnson/Documents/Code/Golang""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.6.2/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.6.2/libexec/pkg/tool/darwin_amd64""
GO15VENDOREXPERIMENT=""1""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
```

3 What did you do?

```shell
$ go doc http.ParseForm
func (r *Request) ParseForm() error
    ParseForm parses the raw query from the URL and updates r.Form.

    For POST or PUT requests, it also parses the request body as a form and put
    the results into both r.PostForm and r.Form. POST and PUT body parameters
    take precedence over URL query string values in r.Form.

    If the request Body's size has not already been limited by MaxBytesReader,
    the size is capped at 10MB.

    ParseMultipartForm calls ParseForm automatically. It is idempotent.
```

4 What did you expect to see?

Grammatically unambiguous documentation.

5 What did you see instead?

In ""It is idempotent,"" ""it"" ambiguously refers to `ParseForm` or `ParseMultipartForm` or both.

I think it should be `ParseForm`, but I'm not sure. Maybe both?",1.0,"net/http: ambiguous sentence in docs for Response.ParseForm - Please answer these questions before submitting your issue. Thanks!

1 What version of Go are you using (`go version`)?

go1.6.2

2 What operating system and processor architecture are you using (`go env`)?

```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/cjohnson/Documents/Code/Golang""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.6.2/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.6.2/libexec/pkg/tool/darwin_amd64""
GO15VENDOREXPERIMENT=""1""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
```

3 What did you do?

```shell
$ go doc http.ParseForm
func (r *Request) ParseForm() error
    ParseForm parses the raw query from the URL and updates r.Form.

    For POST or PUT requests, it also parses the request body as a form and put
    the results into both r.PostForm and r.Form. POST and PUT body parameters
    take precedence over URL query string values in r.Form.

    If the request Body's size has not already been limited by MaxBytesReader,
    the size is capped at 10MB.

    ParseMultipartForm calls ParseForm automatically. It is idempotent.
```

4 What did you expect to see?

Grammatically unambiguous documentation.

5 What did you see instead?

In ""It is idempotent,"" ""it"" ambiguously refers to `ParseForm` or `ParseMultipartForm` or both.

I think it should be `ParseForm`, but I'm not sure. Maybe both?",1,net http  ambiguous sentence in docs for response parseform   please answer these questions before submitting your issue  thanks       what version of go are you using   go version                  what operating system and processor architecture are you using   go env            goarch      gobin     goexe     gohostarch      gohostos  darwin   goos  darwin   gopath   users cjohnson documents code golang   gorace     goroot   usr local cellar go       libexec   gotooldir   usr local cellar go       libexec pkg tool darwin            cc  clang   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fno common   cxx  clang     cgo enabled               what did you do        shell    go doc http parseform  func  r  request  parseform   error      parseform parses the raw query from the url and updates r form         for post or put requests  it also parses the request body as a form and put      the results into both r postform and r form  post and put body parameters      take precedence over url query string values in r form         if the request body s size has not already been limited by maxbytesreader       the size is capped at           parsemultipartform calls parseform automatically  it is idempotent            what did you expect to see     grammatically unambiguous documentation       what did you see instead     in  it is idempotent    it  ambiguously refers to  parseform  or  parsemultipartform  or both     i think it should be  parseform   but i m not sure  maybe both ,1
8656,11796228753.0,IssuesEvent,2020-03-18 10:24:13,TOMP-WG/TOMP-API,https://api.github.com/repos/TOMP-WG/TOMP-API,closed,A high-level roadmap for TO-MP API developments,process,"In discussion with Ross we came to the conclusion that it would be beneficial to have a sort of roadmap that shows our development ideas (visually) and also shows for example data sharing standardization efforts that are at least considering and might be undertaking.
",1.0,"A high-level roadmap for TO-MP API developments - In discussion with Ross we came to the conclusion that it would be beneficial to have a sort of roadmap that shows our development ideas (visually) and also shows for example data sharing standardization efforts that are at least considering and might be undertaking.
",0,a high level roadmap for to mp api developments   in discussion with ross we came to the conclusion that it would be beneficial to have a sort of roadmap that shows our development ideas  visually  and also shows for example data sharing standardization efforts that are at least considering and might be undertaking   ,0
1761,2631695269.0,IssuesEvent,2015-03-07 10:04:43,golang/go,https://api.github.com/repos/golang/go,closed,websocket: WebSocket listener should not require Origin request header,accepted documentation priority-later release-none repo-net,"by **Jens.Alfke**:

<pre>The WebSocket hander rejects an incoming connection if the HTTP request does not include
an &quot;Origin&quot; header. This is contrary to the spec; the Origin header is only
necessary if the request came from a web browser:

        &quot;The request MUST include a header field with the name |Origin|
        [RFC6454] if the request is coming from a browser client.  If
        the connection is from a non-browser client, the request MAY
        include this header field if the semantics of that client match
        the use-case described here for browser clients.&quot;
        -- RFC 6455, section 4.1, item #8:

In my use case the request is coming from an application that's not a browser, and
there's no meaningful value for this header. I have to set it to an arbitrary value of
&quot;<a href=""http://localhost&quot"">http://localhost&quot</a>; to work around this bug.

What steps will reproduce the problem?
1. Run the WebSocket handler example shown in the package documentation:
<a href=""http://godoc.org/code.google.com/p/go.net/websocket#example-Handler"">http://godoc.org/code.google.com/p/go.net/websocket#example-Handler</a>
2. Telnet to its port and send the following data:

GET /echo HTTP/1.1
Host: localhost:12345
Sec-WebSocket-Version: 13
Upgrade: websocket
Sec-WebSocket-Key: oyPxhvkIKpUZSD9Bv9I5xg==
Connection: Upgrade


What is the expected output?

HTTP/1.1 101 Switching Protocols

What do you see instead?

HTTP/1.1 400 Bad Request

(If a line &quot;Origin: <a href=""http://localhost&quot"">http://localhost&quot</a>; is added to the request, the expected
response appears.)

Which compiler are you using (5g, 6g, 8g, gccgo)?
&quot;go&quot; command


Which operating system are you using?
Mac OS X 10.9

Which version are you using?  (run 'go version')
1.1.1

Please provide any additional information below.</pre>",1.0,"websocket: WebSocket listener should not require Origin request header - by **Jens.Alfke**:

<pre>The WebSocket hander rejects an incoming connection if the HTTP request does not include
an &quot;Origin&quot; header. This is contrary to the spec; the Origin header is only
necessary if the request came from a web browser:

        &quot;The request MUST include a header field with the name |Origin|
        [RFC6454] if the request is coming from a browser client.  If
        the connection is from a non-browser client, the request MAY
        include this header field if the semantics of that client match
        the use-case described here for browser clients.&quot;
        -- RFC 6455, section 4.1, item #8:

In my use case the request is coming from an application that's not a browser, and
there's no meaningful value for this header. I have to set it to an arbitrary value of
&quot;<a href=""http://localhost&quot"">http://localhost&quot</a>; to work around this bug.

What steps will reproduce the problem?
1. Run the WebSocket handler example shown in the package documentation:
<a href=""http://godoc.org/code.google.com/p/go.net/websocket#example-Handler"">http://godoc.org/code.google.com/p/go.net/websocket#example-Handler</a>
2. Telnet to its port and send the following data:

GET /echo HTTP/1.1
Host: localhost:12345
Sec-WebSocket-Version: 13
Upgrade: websocket
Sec-WebSocket-Key: oyPxhvkIKpUZSD9Bv9I5xg==
Connection: Upgrade


What is the expected output?

HTTP/1.1 101 Switching Protocols

What do you see instead?

HTTP/1.1 400 Bad Request

(If a line &quot;Origin: <a href=""http://localhost&quot"">http://localhost&quot</a>; is added to the request, the expected
response appears.)

Which compiler are you using (5g, 6g, 8g, gccgo)?
&quot;go&quot; command


Which operating system are you using?
Mac OS X 10.9

Which version are you using?  (run 'go version')
1.1.1

Please provide any additional information below.</pre>",1,websocket  websocket listener should not require origin request header   by   jens alfke      the websocket hander rejects an incoming connection if the http request does not include an  quot origin quot  header  this is contrary to the spec  the origin header is only necessary if the request came from a web browser            quot the request must include a header field with the name  origin            if the request is coming from a browser client   if         the connection is from a non browser client  the request may         include this header field if the semantics of that client match         the use case described here for browser clients  quot             rfc    section      item      in my use case the request is coming from an application that s not a browser  and there s no meaningful value for this header  i have to set it to an arbitrary value of  quot  a href    to work around this bug   what steps will reproduce the problem     run the websocket handler example shown in the package documentation   a href       telnet to its port and send the following data   get  echo http     host  localhost   sec websocket version    upgrade  websocket sec websocket key      connection  upgrade   what is the expected output   http       switching protocols  what do you see instead   http       bad request   if a line  quot origin   a href    is added to the request  the expected response appears    which compiler are you using           gccgo    quot go quot  command   which operating system are you using  mac os x      which version are you using    run  go version          please provide any additional information below  ,1
203013,15864952177.0,IssuesEvent,2021-04-08 14:15:58,golang/go,https://api.github.com/repos/golang/go,closed,"x/website: missing `""` in code snippet",Documentation NeedsFix,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
# Doesn't matter.
</pre>

### Does this issue reproduce with the latest release?



### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
# Doesn't matter.
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

Find typo when reading reference.

https://golang.org/ref/mod#environment-variables

![image](https://user-images.githubusercontent.com/8807977/113972037-83334f80-986c-11eb-9e97-25277273fec1.png)


### What did you expect to see?

```
GOSUMDB=""sum.golang.org+<publickey> https://sum.golang.org""
```

### What did you see instead?
",1.0,"x/website: missing `""` in code snippet - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
# Doesn't matter.
</pre>

### Does this issue reproduce with the latest release?



### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
# Doesn't matter.
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

Find typo when reading reference.

https://golang.org/ref/mod#environment-variables

![image](https://user-images.githubusercontent.com/8807977/113972037-83334f80-986c-11eb-9e97-25277273fec1.png)


### What did you expect to see?

```
GOSUMDB=""sum.golang.org+<publickey> https://sum.golang.org""
```

### What did you see instead?
",1,x website  missing     in code snippet         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version            go version    doesn t matter            does this issue reproduce with the latest release             what operating system and processor architecture are you using   go env          go env  output       go env    doesn t matter             what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best          find typo when reading reference                        what did you expect to see          gosumdb  sum golang org                 what did you see instead   ,1
163451,20363784329.0,IssuesEvent,2022-02-21 01:27:32,amccool/AngularASPNETCore2WebApiAuth,https://api.github.com/repos/amccool/AngularASPNETCore2WebApiAuth,opened,"CVE-2022-0512 (High) detected in url-parse-1.0.5.tgz, url-parse-1.2.0.tgz",security vulnerability,"## CVE-2022-0512 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>url-parse-1.0.5.tgz</b>, <b>url-parse-1.2.0.tgz</b></p></summary>
<p>

<details><summary><b>url-parse-1.0.5.tgz</b></p></summary>

<p>Small footprint URL parser that works seamlessly across Node.js and browser environments</p>
<p>Library home page: <a href=""https://registry.npmjs.org/url-parse/-/url-parse-1.0.5.tgz"">https://registry.npmjs.org/url-parse/-/url-parse-1.0.5.tgz</a></p>
<p>Path to dependency file: /src/package.json</p>
<p>Path to vulnerable library: /src/node_modules/original/node_modules/url-parse/package.json</p>
<p>

Dependency Hierarchy:
  - cli-1.6.3.tgz (Root Library)
    - webpack-dev-server-2.9.7.tgz
      - sockjs-client-1.1.4.tgz
        - eventsource-0.1.6.tgz
          - original-1.0.0.tgz
            - :x: **url-parse-1.0.5.tgz** (Vulnerable Library)
</details>
<details><summary><b>url-parse-1.2.0.tgz</b></p></summary>

<p>Small footprint URL parser that works seamlessly across Node.js and browser environments</p>
<p>Library home page: <a href=""https://registry.npmjs.org/url-parse/-/url-parse-1.2.0.tgz"">https://registry.npmjs.org/url-parse/-/url-parse-1.2.0.tgz</a></p>
<p>Path to dependency file: /src/package.json</p>
<p>Path to vulnerable library: /src/node_modules/url-parse/package.json</p>
<p>

Dependency Hierarchy:
  - cli-1.6.3.tgz (Root Library)
    - webpack-dev-server-2.9.7.tgz
      - sockjs-client-1.1.4.tgz
        - :x: **url-parse-1.2.0.tgz** (Vulnerable Library)
</details>

</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.6.

<p>Publish Date: 2022-02-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0512>CVE-2022-0512</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>8.8</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0512"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0512</a></p>
<p>Release Date: 2022-02-14</p>
<p>Fix Resolution: url-parse - 1.5.6</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-2022-0512 (High) detected in url-parse-1.0.5.tgz, url-parse-1.2.0.tgz - ## CVE-2022-0512 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>url-parse-1.0.5.tgz</b>, <b>url-parse-1.2.0.tgz</b></p></summary>
<p>

<details><summary><b>url-parse-1.0.5.tgz</b></p></summary>

<p>Small footprint URL parser that works seamlessly across Node.js and browser environments</p>
<p>Library home page: <a href=""https://registry.npmjs.org/url-parse/-/url-parse-1.0.5.tgz"">https://registry.npmjs.org/url-parse/-/url-parse-1.0.5.tgz</a></p>
<p>Path to dependency file: /src/package.json</p>
<p>Path to vulnerable library: /src/node_modules/original/node_modules/url-parse/package.json</p>
<p>

Dependency Hierarchy:
  - cli-1.6.3.tgz (Root Library)
    - webpack-dev-server-2.9.7.tgz
      - sockjs-client-1.1.4.tgz
        - eventsource-0.1.6.tgz
          - original-1.0.0.tgz
            - :x: **url-parse-1.0.5.tgz** (Vulnerable Library)
</details>
<details><summary><b>url-parse-1.2.0.tgz</b></p></summary>

<p>Small footprint URL parser that works seamlessly across Node.js and browser environments</p>
<p>Library home page: <a href=""https://registry.npmjs.org/url-parse/-/url-parse-1.2.0.tgz"">https://registry.npmjs.org/url-parse/-/url-parse-1.2.0.tgz</a></p>
<p>Path to dependency file: /src/package.json</p>
<p>Path to vulnerable library: /src/node_modules/url-parse/package.json</p>
<p>

Dependency Hierarchy:
  - cli-1.6.3.tgz (Root Library)
    - webpack-dev-server-2.9.7.tgz
      - sockjs-client-1.1.4.tgz
        - :x: **url-parse-1.2.0.tgz** (Vulnerable Library)
</details>

</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.6.

<p>Publish Date: 2022-02-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0512>CVE-2022-0512</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>8.8</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0512"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0512</a></p>
<p>Release Date: 2022-02-14</p>
<p>Fix Resolution: url-parse - 1.5.6</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in url parse       tgz  url parse       tgz      cve       high severity vulnerability     vulnerable libraries    url parse       tgz    url parse       tgz          url parse       tgz      small footprint url parser that works seamlessly across node js and browser environments   library home page   a href     path to dependency file   src package json   path to vulnerable library   src node modules original node modules url parse package json     dependency hierarchy      cli       tgz  root library        webpack dev server       tgz         sockjs client       tgz           eventsource       tgz             original       tgz                x    url parse       tgz    vulnerable library       url parse       tgz      small footprint url parser that works seamlessly across node js and browser environments   library home page   a href     path to dependency file   src package json   path to vulnerable library   src node modules url parse package json     dependency hierarchy      cli       tgz  root library        webpack dev server       tgz         sockjs client       tgz            x    url parse       tgz    vulnerable library                vulnerability details         authorization bypass through user controlled key in npm url parse prior to          publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  low     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  url parse                       step up your open source security game with whitesource    ,0
56909,8130483924.0,IssuesEvent,2018-08-17 18:39:14,golang/go,https://api.github.com/repos/golang/go,closed,doc: document go/build vs golang.org/x/tools/go/packages,Documentation NeedsFix release-blocker,"Per https://tip.golang.org/doc/go1.11#gopackages:

> TODO: Note about go/build versus golang.org/x/tools/go/packages.",1.0,"doc: document go/build vs golang.org/x/tools/go/packages - Per https://tip.golang.org/doc/go1.11#gopackages:

> TODO: Note about go/build versus golang.org/x/tools/go/packages.",1,doc  document go build vs golang org x tools go packages   per        todo  note about go build versus golang org x tools go packages ,1
312305,23422910514.0,IssuesEvent,2022-08-14 00:42:38,golang/go,https://api.github.com/repos/golang/go,closed,x/website: Installing Go from source page does not mention loong instruction set,Documentation NeedsFix website,"At https://go.dev/doc/install/source 

```
The Go compilers support the following instruction sets:

amd64, 386
    The x86 instruction set, 64- and 32-bit. 
arm64, arm
    The ARM instruction set, 64-bit (AArch64) and 32-bit. 
mips64, mips64le, mips, mipsle
    The MIPS instruction set, big- and little-endian, 64- and 32-bit. 
ppc64, ppc64le
    The 64-bit PowerPC instruction set, big- and little-endian. 
riscv64
    The 64-bit RISC-V instruction set. 
s390x
    The IBM z/Architecture. 
wasm
    WebAssembly.
```

Is missing a mention of `loong64`.

Also it says ""the Go compiler**s**"" but the plural seems wrong, the page is about `gc` which is usually called ""the Go compiler"".",1.0,"x/website: Installing Go from source page does not mention loong instruction set - At https://go.dev/doc/install/source 

```
The Go compilers support the following instruction sets:

amd64, 386
    The x86 instruction set, 64- and 32-bit. 
arm64, arm
    The ARM instruction set, 64-bit (AArch64) and 32-bit. 
mips64, mips64le, mips, mipsle
    The MIPS instruction set, big- and little-endian, 64- and 32-bit. 
ppc64, ppc64le
    The 64-bit PowerPC instruction set, big- and little-endian. 
riscv64
    The 64-bit RISC-V instruction set. 
s390x
    The IBM z/Architecture. 
wasm
    WebAssembly.
```

Is missing a mention of `loong64`.

Also it says ""the Go compiler**s**"" but the plural seems wrong, the page is about `gc` which is usually called ""the Go compiler"".",1,x website  installing go from source page does not mention loong instruction set   at            the go compilers support the following instruction sets               the   instruction set     and   bit       arm      the arm instruction set    bit     and   bit          mips  mipsle      the mips instruction set  big  and little endian     and   bit              the   bit powerpc instruction set  big  and little endian           the   bit risc v instruction set           the ibm z architecture    wasm      webassembly          is missing a mention of         also it says  the go compiler  s    but the plural seems wrong  the page is about  gc  which is usually called  the go compiler  ,1
23772,12110998403.0,IssuesEvent,2020-04-21 11:26:17,status-im/status-react,https://api.github.com/repos/status-im/status-react,opened,[perfromance] Make sign in smooth,feature performance,"The app should work smooth after sign in

1) split events on the smallest ones
2) optimize events code
3) split screens initialization (currently all subscriptions are created and rendered in one step)

[TODO add screenshots]
",True,"[perfromance] Make sign in smooth - The app should work smooth after sign in

1) split events on the smallest ones
2) optimize events code
3) split screens initialization (currently all subscriptions are created and rendered in one step)

[TODO add screenshots]
",0,  make sign in smooth   the app should work smooth after sign in       split events on the smallest ones     optimize events code     split screens initialization  currently all subscriptions are created and rendered in one step        ,0
234748,7725871341.0,IssuesEvent,2018-05-24 19:21:21,RoboJackets/apiary,https://api.github.com/repos/RoboJackets/apiary,opened,OIE travel form generation,area / backend priority / low type / feature,"Effective AY2018, RoboJackets must register international trips with OIE/Student Life. The form is not typeable and requires information from travelers. This should be included as an option in trip management functionality.",1.0,"OIE travel form generation - Effective AY2018, RoboJackets must register international trips with OIE/Student Life. The form is not typeable and requires information from travelers. This should be included as an option in trip management functionality.",0,oie travel form generation   effective    robojackets must register international trips with oie student life  the form is not typeable and requires information from travelers  this should be included as an option in trip management functionality ,0
55813,8031414585.0,IssuesEvent,2018-07-28 01:16:06,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: GOMOD env var is not documented,Documentation NeedsFix modules,"### What version of Go are you using (`go version`)?
```
go version devel +4f1f503373 Fri Jul 20 03:30:04 2018 +0000 darwin/amd64
```

### Does this issue reproduce with the latest release?
N/A

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH=""amd64""
GOBIN=""/Users/pierre/code/bin""
GOCACHE=""/Users/pierre/Library/Caches/go-build""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/pierre/go""
GOPROXY=""""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/HEAD-4f1f503/libexec""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/HEAD-4f1f503/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/7g/98rjcknd3tg687h6z8shgtmr0000gn/T/go-build873031824=/tmp/go-build -gno-record-gcc-switches -fno-common""
```

### What did you do?

```
go help environment
```


### What did you expect to see?
I expected to see some information about the `GOMOD` enviroment variable, which is listed in the output of `go env`.

### What did you see instead?
Documentation on many environment variables, but no mention of `GOMOD`:

```
The go command, and the tools it invokes, examine a few different
environment variables. For many of these, you can see the default
value of on your system by running 'go env NAME', where NAME is the
name of the variable.

General-purpose environment variables:

	GCCGO
		The gccgo command to run for 'go build -compiler=gccgo'.
	GOARCH
		The architecture, or processor, for which to compile code.
		Examples are amd64, 386, arm, ppc64.
	GOBIN
		The directory where 'go install' will install a command.
	GOCACHE
		The directory where the go command will store cached
		information for reuse in future builds.
	GOOS
		The operating system for which to compile code.
		Examples are linux, darwin, windows, netbsd.
	GOPATH
		For more details see: 'go help gopath'.
	GOPROXY
		URL of Go module proxy. See 'go help goproxy'.
	GORACE
		Options for the race detector.
		See https://golang.org/doc/articles/race_detector.html.
	GOROOT
		The root of the go tree.
	GOTMPDIR
		The directory where the go command will write
		temporary source files, packages, and binaries.
	GOTOOLDIR
		The directory where the go tools (compile, cover, doc, etc...)
		are installed. This is printed by go env, but setting the
		environment variable has no effect.

Environment variables for use with cgo:

	CC
		The command to use to compile C code.
	CGO_ENABLED
		Whether the cgo command is supported. Either 0 or 1.
	CGO_CFLAGS
		Flags that cgo will pass to the compiler when compiling
		C code.
	CGO_CFLAGS_ALLOW
		A regular expression specifying additional flags to allow
		to appear in #cgo CFLAGS source code directives.
		Does not apply to the CGO_CFLAGS environment variable.
	CGO_CFLAGS_DISALLOW
		A regular expression specifying flags that must be disallowed
		from appearing in #cgo CFLAGS source code directives.
		Does not apply to the CGO_CFLAGS environment variable.
	CGO_CPPFLAGS, CGO_CPPFLAGS_ALLOW, CGO_CPPFLAGS_DISALLOW
		Like CGO_CFLAGS, CGO_CFLAGS_ALLOW, and CGO_CFLAGS_DISALLOW,
		but for the C preprocessor.
	CGO_CXXFLAGS, CGO_CXXFLAGS_ALLOW, CGO_CXXFLAGS_DISALLOW
		Like CGO_CFLAGS, CGO_CFLAGS_ALLOW, and CGO_CFLAGS_DISALLOW,
		but for the C++ compiler.
	CGO_FFLAGS, CGO_FFLAGS_ALLOW, CGO_FFLAGS_DISALLOW
		Like CGO_CFLAGS, CGO_CFLAGS_ALLOW, and CGO_CFLAGS_DISALLOW,
		but for the Fortran compiler.
	CGO_LDFLAGS, CGO_LDFLAGS_ALLOW, CGO_LDFLAGS_DISALLOW
		Like CGO_CFLAGS, CGO_CFLAGS_ALLOW, and CGO_CFLAGS_DISALLOW,
		but for the linker.
	CXX
		The command to use to compile C++ code.
	PKG_CONFIG
		Path to pkg-config tool.

Architecture-specific environment variables:

	GOARM
		For GOARCH=arm, the ARM architecture for which to compile.
		Valid values are 5, 6, 7.
	GO386
		For GOARCH=386, the floating point instruction set.
		Valid values are 387, sse2.
	GOMIPS
		For GOARCH=mips{,le}, whether to use floating point instructions.
		Valid values are hardfloat (default), softfloat.
	GOMIPS64
		For GOARCH=mips64{,le}, whether to use floating point instructions.
		Valid values are hardfloat (default), softfloat.

Special-purpose environment variables:

	GCCGOTOOLDIR
		If set, where to find gccgo tools, such as cgo.
		The default is based on how gccgo was configured.
	GOROOT_FINAL
		The root of the installed Go tree, when it is
		installed in a location other than where it is built.
		File names in stack traces are rewritten from GOROOT to
		GOROOT_FINAL.
	GO_EXTLINK_ENABLED
		Whether the linker should use external linking mode
		when using -linkmode=auto with code that uses cgo.
		Set to 0 to disable external linking mode, 1 to enable it.
	GIT_ALLOW_PROTOCOL
		Defined by Git. A colon-separated list of schemes that are allowed to be used
		with git fetch/clone. If set, any scheme not explicitly mentioned will be
		considered insecure by 'go get'.
```

Thank you!",1.0,"cmd/go: GOMOD env var is not documented - ### What version of Go are you using (`go version`)?
```
go version devel +4f1f503373 Fri Jul 20 03:30:04 2018 +0000 darwin/amd64
```

### Does this issue reproduce with the latest release?
N/A

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH=""amd64""
GOBIN=""/Users/pierre/code/bin""
GOCACHE=""/Users/pierre/Library/Caches/go-build""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/pierre/go""
GOPROXY=""""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/HEAD-4f1f503/libexec""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/HEAD-4f1f503/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/7g/98rjcknd3tg687h6z8shgtmr0000gn/T/go-build873031824=/tmp/go-build -gno-record-gcc-switches -fno-common""
```

### What did you do?

```
go help environment
```


### What did you expect to see?
I expected to see some information about the `GOMOD` enviroment variable, which is listed in the output of `go env`.

### What did you see instead?
Documentation on many environment variables, but no mention of `GOMOD`:

```
The go command, and the tools it invokes, examine a few different
environment variables. For many of these, you can see the default
value of on your system by running 'go env NAME', where NAME is the
name of the variable.

General-purpose environment variables:

	GCCGO
		The gccgo command to run for 'go build -compiler=gccgo'.
	GOARCH
		The architecture, or processor, for which to compile code.
		Examples are amd64, 386, arm, ppc64.
	GOBIN
		The directory where 'go install' will install a command.
	GOCACHE
		The directory where the go command will store cached
		information for reuse in future builds.
	GOOS
		The operating system for which to compile code.
		Examples are linux, darwin, windows, netbsd.
	GOPATH
		For more details see: 'go help gopath'.
	GOPROXY
		URL of Go module proxy. See 'go help goproxy'.
	GORACE
		Options for the race detector.
		See https://golang.org/doc/articles/race_detector.html.
	GOROOT
		The root of the go tree.
	GOTMPDIR
		The directory where the go command will write
		temporary source files, packages, and binaries.
	GOTOOLDIR
		The directory where the go tools (compile, cover, doc, etc...)
		are installed. This is printed by go env, but setting the
		environment variable has no effect.

Environment variables for use with cgo:

	CC
		The command to use to compile C code.
	CGO_ENABLED
		Whether the cgo command is supported. Either 0 or 1.
	CGO_CFLAGS
		Flags that cgo will pass to the compiler when compiling
		C code.
	CGO_CFLAGS_ALLOW
		A regular expression specifying additional flags to allow
		to appear in #cgo CFLAGS source code directives.
		Does not apply to the CGO_CFLAGS environment variable.
	CGO_CFLAGS_DISALLOW
		A regular expression specifying flags that must be disallowed
		from appearing in #cgo CFLAGS source code directives.
		Does not apply to the CGO_CFLAGS environment variable.
	CGO_CPPFLAGS, CGO_CPPFLAGS_ALLOW, CGO_CPPFLAGS_DISALLOW
		Like CGO_CFLAGS, CGO_CFLAGS_ALLOW, and CGO_CFLAGS_DISALLOW,
		but for the C preprocessor.
	CGO_CXXFLAGS, CGO_CXXFLAGS_ALLOW, CGO_CXXFLAGS_DISALLOW
		Like CGO_CFLAGS, CGO_CFLAGS_ALLOW, and CGO_CFLAGS_DISALLOW,
		but for the C++ compiler.
	CGO_FFLAGS, CGO_FFLAGS_ALLOW, CGO_FFLAGS_DISALLOW
		Like CGO_CFLAGS, CGO_CFLAGS_ALLOW, and CGO_CFLAGS_DISALLOW,
		but for the Fortran compiler.
	CGO_LDFLAGS, CGO_LDFLAGS_ALLOW, CGO_LDFLAGS_DISALLOW
		Like CGO_CFLAGS, CGO_CFLAGS_ALLOW, and CGO_CFLAGS_DISALLOW,
		but for the linker.
	CXX
		The command to use to compile C++ code.
	PKG_CONFIG
		Path to pkg-config tool.

Architecture-specific environment variables:

	GOARM
		For GOARCH=arm, the ARM architecture for which to compile.
		Valid values are 5, 6, 7.
	GO386
		For GOARCH=386, the floating point instruction set.
		Valid values are 387, sse2.
	GOMIPS
		For GOARCH=mips{,le}, whether to use floating point instructions.
		Valid values are hardfloat (default), softfloat.
	GOMIPS64
		For GOARCH=mips64{,le}, whether to use floating point instructions.
		Valid values are hardfloat (default), softfloat.

Special-purpose environment variables:

	GCCGOTOOLDIR
		If set, where to find gccgo tools, such as cgo.
		The default is based on how gccgo was configured.
	GOROOT_FINAL
		The root of the installed Go tree, when it is
		installed in a location other than where it is built.
		File names in stack traces are rewritten from GOROOT to
		GOROOT_FINAL.
	GO_EXTLINK_ENABLED
		Whether the linker should use external linking mode
		when using -linkmode=auto with code that uses cgo.
		Set to 0 to disable external linking mode, 1 to enable it.
	GIT_ALLOW_PROTOCOL
		Defined by Git. A colon-separated list of schemes that are allowed to be used
		with git fetch/clone. If set, any scheme not explicitly mentioned will be
		considered insecure by 'go get'.
```

Thank you!",1,cmd go  gomod env var is not documented       what version of go are you using   go version          go version devel    fri jul              darwin               does this issue reproduce with the latest release   n a        what operating system and processor architecture are you using   go env          goarch      gobin   users pierre code bin   gocache   users pierre library caches go build   goexe     gohostarch      gohostos  darwin   goos  darwin   gopath   users pierre go   goproxy     gorace     goroot   usr local cellar go head   libexec   gotmpdir     gotooldir   usr local cellar go head   libexec pkg tool darwin     gccgo  gccgo   cc  clang   cxx  clang     cgo enabled      gomod     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders     t go    tmp go build  gno record gcc switches  fno common              what did you do          go help environment               what did you expect to see   i expected to see some information about the  gomod  enviroment variable  which is listed in the output of  go env          what did you see instead   documentation on many environment variables  but no mention of  gomod           the go command  and the tools it invokes  examine a few different  environment variables  for many of these  you can see the default  value of on your system by running  go env name   where name is the  name of the variable     general purpose environment variables     	gccgo  		the gccgo command to run for  go build  compiler gccgo    	goarch  		the architecture  or processor  for which to compile code   		examples are       arm      	gobin  		the directory where  go install  will install a command   	gocache  		the directory where the go command will store cached  		information for reuse in future builds   	goos  		the operating system for which to compile code   		examples are linux  darwin  windows  netbsd   	gopath  		for more details see   go help gopath    	goproxy  		url of go module proxy  see  go help goproxy    	gorace  		options for the race detector   		see    	goroot  		the root of the go tree   	gotmpdir  		the directory where the go command will write  		temporary source files  packages  and binaries   	gotooldir  		the directory where the go tools  compile  cover  doc  etc      		are installed  this is printed by go env  but setting the  		environment variable has no effect     environment variables for use with cgo     	cc  		the command to use to compile c code   	cgo enabled  		whether the cgo command is supported  either   or     	cgo cflags  		flags that cgo will pass to the compiler when compiling  		c code   	cgo cflags allow  		a regular expression specifying additional flags to allow  		to appear in  cgo cflags source code directives   		does not apply to the cgo cflags environment variable   	cgo cflags disallow  		a regular expression specifying flags that must be disallowed  		from appearing in  cgo cflags source code directives   		does not apply to the cgo cflags environment variable   	cgo cppflags  cgo cppflags allow  cgo cppflags disallow  		like cgo cflags  cgo cflags allow  and cgo cflags disallow   		but for the c preprocessor   	cgo cxxflags  cgo cxxflags allow  cgo cxxflags disallow  		like cgo cflags  cgo cflags allow  and cgo cflags disallow   		but for the c   compiler   	cgo fflags  cgo fflags allow  cgo fflags disallow  		like cgo cflags  cgo cflags allow  and cgo cflags disallow   		but for the fortran compiler   	cgo ldflags  cgo ldflags allow  cgo ldflags disallow  		like cgo cflags  cgo cflags allow  and cgo cflags disallow   		but for the linker   	cxx  		the command to use to compile c   code   	pkg config  		path to pkg config tool     architecture specific environment variables     	goarm  		for goarch arm  the arm architecture for which to compile   		valid values are           	   		for goarch    the floating point instruction set   		valid values are        	gomips  		for goarch mips  le   whether to use floating point instructions   		valid values are hardfloat  default   softfloat   	   		for goarch    le   whether to use floating point instructions   		valid values are hardfloat  default   softfloat     special purpose environment variables     	gccgotooldir  		if set  where to find gccgo tools  such as cgo   		the default is based on how gccgo was configured   	goroot final  		the root of the installed go tree  when it is  		installed in a location other than where it is built   		file names in stack traces are rewritten from goroot to  		goroot final   	go extlink enabled  		whether the linker should use external linking mode  		when using  linkmode auto with code that uses cgo   		set to   to disable external linking mode    to enable it   	git allow protocol  		defined by git  a colon separated list of schemes that are allowed to be used  		with git fetch clone  if set  any scheme not explicitly mentioned will be  		considered insecure by  go get           thank you ,1
38478,8488519572.0,IssuesEvent,2018-10-26 16:53:49,tensegrity-dapp/blend,https://api.github.com/repos/tensegrity-dapp/blend,opened,Space,code maintain important,"- [ ] Realtime чат
- [ ] Видео чат
- [ ] Проверка прохождения транзакции оплаты для QTUM
- [ ] Отправить спор
- [ ] Рассмотреть все возможные сценарии взаимодействия
- [ ] Подтвердить прохождение
- [ ] Если долго не было сообщений
- [ ] Если пропала связь, участник вышел
- [ ] Если ученик отменил процесс обучения

### Idea
Пространство обучения между учеником и учителем

### Description
Возможные сценарии:
Код | Значение
---|---
0 | Ученик сделал запрос учителю
1 | Учитель начал урок
2 | Ученик закрыл в пользу учителя
3 | Ученик закрыл со спором
4 | Учитель отменил обучение
5 | Учитель закрыл сессию
6 | Ученик не отвечал более 5 минут
7 | Учитель не отвечал более 5 минут
8 | Ученик подтвердил успешное прохождение
9 | Модератор закрыл в пользу учителя
10 | Модератор закрыл в пользу ученика
11 | Учитель не открыл вовремя урок
12 | Вышло время урока (25 минут)
13 | Никто не ответил
14 | Ученик подтвердил начало урока, транзакция учителя ещё не прошла
15 | Ученик отменил начало урока
16 | Ученик не подтвердил вовремя урок
17 | Ученик учится у бота
18 | Транзакция учителя прошла
19 | Транзакция ученика прошла

### For what
1. Процесс обучения

### Required for Implementation
1. WYSIWYG редактор",1.0,"Space - - [ ] Realtime чат
- [ ] Видео чат
- [ ] Проверка прохождения транзакции оплаты для QTUM
- [ ] Отправить спор
- [ ] Рассмотреть все возможные сценарии взаимодействия
- [ ] Подтвердить прохождение
- [ ] Если долго не было сообщений
- [ ] Если пропала связь, участник вышел
- [ ] Если ученик отменил процесс обучения

### Idea
Пространство обучения между учеником и учителем

### Description
Возможные сценарии:
Код | Значение
---|---
0 | Ученик сделал запрос учителю
1 | Учитель начал урок
2 | Ученик закрыл в пользу учителя
3 | Ученик закрыл со спором
4 | Учитель отменил обучение
5 | Учитель закрыл сессию
6 | Ученик не отвечал более 5 минут
7 | Учитель не отвечал более 5 минут
8 | Ученик подтвердил успешное прохождение
9 | Модератор закрыл в пользу учителя
10 | Модератор закрыл в пользу ученика
11 | Учитель не открыл вовремя урок
12 | Вышло время урока (25 минут)
13 | Никто не ответил
14 | Ученик подтвердил начало урока, транзакция учителя ещё не прошла
15 | Ученик отменил начало урока
16 | Ученик не подтвердил вовремя урок
17 | Ученик учится у бота
18 | Транзакция учителя прошла
19 | Транзакция ученика прошла

### For what
1. Процесс обучения

### Required for Implementation
1. WYSIWYG редактор",0,space       realtime чат      видео чат      проверка прохождения транзакции оплаты для qtum      отправить спор      рассмотреть все возможные сценарии взаимодействия      подтвердить прохождение      если долго не было сообщений      если пропала связь  участник вышел      если ученик отменил процесс обучения        idea  пространство обучения между учеником и учителем        description  возможные сценарии   код   значение               ученик сделал запрос учителю      учитель начал урок      ученик закрыл в пользу учителя      ученик закрыл со спором      учитель отменил обучение      учитель закрыл сессию      ученик не отвечал более   минут      учитель не отвечал более   минут      ученик подтвердил успешное прохождение      модератор закрыл в пользу учителя      модератор закрыл в пользу ученика      учитель не открыл вовремя урок      вышло время урока    минут       никто не ответил      ученик подтвердил начало урока  транзакция учителя ещё не прошла      ученик отменил начало урока      ученик не подтвердил вовремя урок      ученик учится у бота      транзакция учителя прошла      транзакция ученика прошла        for what     процесс обучения        required for implementation     wysiwyg редактор,0
13761,5444681861.0,IssuesEvent,2017-03-07 03:54:33,chi-immigration-task-force/icirr-app,https://api.github.com/repos/chi-immigration-task-force/icirr-app,opened,"Build out the ""Map"" screen",Building Task,"Requirements of this screen:
- Display on a map the various ICIRR [constituent organizations](http://www.icirr.org/about/partners). Ideally this could be updated without a deploy of the app but we should ensure that we have a strong story for how to prevent abuse.
- If the user has allowed us to access their location information, show them the organizations nearest to them, ideally by category.
- Make sure it's easy to get the address of the organization as well as give them a call.",1.0,"Build out the ""Map"" screen - Requirements of this screen:
- Display on a map the various ICIRR [constituent organizations](http://www.icirr.org/about/partners). Ideally this could be updated without a deploy of the app but we should ensure that we have a strong story for how to prevent abuse.
- If the user has allowed us to access their location information, show them the organizations nearest to them, ideally by category.
- Make sure it's easy to get the address of the organization as well as give them a call.",0,build out the  map  screen   requirements of this screen     display on a map the various icirr     ideally this could be updated without a deploy of the app but we should ensure that we have a strong story for how to prevent abuse     if the user has allowed us to access their location information  show them the organizations nearest to them  ideally by category     make sure it s easy to get the address of the organization as well as give them a call ,0
48768,7457047745.0,IssuesEvent,2018-03-30 01:28:03,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: docs: document that main packages cannot be imported,Documentation,"Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
```
go version go1.9 linux/amd64
```

### Does this issue reproduce with the latest release?
Yes.

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/elliott/me/projects/go""
GORACE=""""
GOROOT=""/usr/local/go""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build792066057=/tmp/go-build -gno-record-gcc-switches""
CXX=""g++""
CGO_ENABLED=""1""
PKG_CONFIG=""pkg-config""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
```

### What did you do?

A non-main package cannot import a main package. I discovered this when importing my main package by its canonical name, `github.com/e-beach/main-package-example`, in a test package. I also believe that main packages _can_ import other main packages, but did not test that here.

See https://github.com/e-beach/main-package-example for an example.
See https://groups.google.com/forum/#!topic/Golang-nuts/frh9zQPEjUk for the discussion that gave birth to the issue.

### What did you expect to see?
I expected `cd test && go test` to pass without error.

### What did you see instead?
```
# github.com/e-beach/main-package-example/test 
main_test.go:4:2: import ""github.com/e-beach/main-package-example"" is a program, not an importable package FAIL	github.com/e-beach/main-package-example/test [setup failed]
```

This behavior is reasonable, but is not in the spec and should be documented. 

",1.0,"cmd/go: docs: document that main packages cannot be imported - Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
```
go version go1.9 linux/amd64
```

### Does this issue reproduce with the latest release?
Yes.

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/elliott/me/projects/go""
GORACE=""""
GOROOT=""/usr/local/go""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build792066057=/tmp/go-build -gno-record-gcc-switches""
CXX=""g++""
CGO_ENABLED=""1""
PKG_CONFIG=""pkg-config""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
```

### What did you do?

A non-main package cannot import a main package. I discovered this when importing my main package by its canonical name, `github.com/e-beach/main-package-example`, in a test package. I also believe that main packages _can_ import other main packages, but did not test that here.

See https://github.com/e-beach/main-package-example for an example.
See https://groups.google.com/forum/#!topic/Golang-nuts/frh9zQPEjUk for the discussion that gave birth to the issue.

### What did you expect to see?
I expected `cd test && go test` to pass without error.

### What did you see instead?
```
# github.com/e-beach/main-package-example/test 
main_test.go:4:2: import ""github.com/e-beach/main-package-example"" is a program, not an importable package FAIL	github.com/e-beach/main-package-example/test [setup failed]
```

This behavior is reasonable, but is not in the spec and should be documented. 

",1,cmd go  docs  document that main packages cannot be imported   please answer these questions before submitting your issue  thanks         what version of go are you using   go version          go version     linux               does this issue reproduce with the latest release   yes         what operating system and processor architecture are you using   go env          goarch      gobin     goexe     gohostarch      gohostos  linux   goos  linux   gopath   home elliott me projects go   gorace     goroot   usr local go   gotooldir   usr local go pkg tool linux     gccgo  gccgo   cc  gcc   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches   cxx  g     cgo enabled      pkg config  pkg config   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g                 what did you do     a non main package cannot import a main package  i discovered this when importing my main package by its canonical name   github com e beach main package example   in a test package  i also believe that main packages  can  import other main packages  but did not test that here     see   for an example   see   for the discussion that gave birth to the issue         what did you expect to see   i expected  cd test    go test  to pass without error         what did you see instead          github com e beach main package example test   main test go      import  github com e beach main package example  is a program  not an importable package fail	github com e beach main package example test           this behavior is reasonable  but is not in the spec and should be documented      ,1
333858,10132357568.0,IssuesEvent,2019-08-01 22:09:31,RobotLocomotion/drake,https://api.github.com/repos/RobotLocomotion/drake,closed,Update SceneGraph call sites to use RigidTransform instead of Isometry. ,priority: medium team: dynamics,"Overarching issue: #9865
Continuation of the work for done in drake/multibody started in issues #10959, #11064, #11193.
This consolidates/replaces issue#11277 (Port SG to use RigidTransform).",1.0,"Update SceneGraph call sites to use RigidTransform instead of Isometry.  - Overarching issue: #9865
Continuation of the work for done in drake/multibody started in issues #10959, #11064, #11193.
This consolidates/replaces issue#11277 (Port SG to use RigidTransform).",0,update scenegraph call sites to use rigidtransform instead of isometry     overarching issue      continuation of the work for done in drake multibody started in issues              this consolidates replaces issue    port sg to use rigidtransform  ,0
45100,7158495178.0,IssuesEvent,2018-01-27 01:13:00,golang/go,https://api.github.com/repos/golang/go,closed,os: document that StartProcess inherits the caller's thread state,Documentation,"One of the new features of the Go 1.10 runtime is that `LockOSThread` can be used to reliably modify OS thread state. One of the main points of doing this was to make it possible to start a new process with a modified thread state, but right now we don't document that new processes created with, e.g., `os.StartProcess` will actually inherit the caller's thread state. This has [led to confusion](https://github.com/golang/go/issues/20395#issuecomment-360810662) and we should document this.",1.0,"os: document that StartProcess inherits the caller's thread state - One of the new features of the Go 1.10 runtime is that `LockOSThread` can be used to reliably modify OS thread state. One of the main points of doing this was to make it possible to start a new process with a modified thread state, but right now we don't document that new processes created with, e.g., `os.StartProcess` will actually inherit the caller's thread state. This has [led to confusion](https://github.com/golang/go/issues/20395#issuecomment-360810662) and we should document this.",1,os  document that startprocess inherits the caller s thread state   one of the new features of the go     runtime is that  lockosthread  can be used to reliably modify os thread state  one of the main points of doing this was to make it possible to start a new process with a modified thread state  but right now we don t document that new processes created with  e g    os startprocess  will actually inherit the caller s thread state  this has     and we should document this ,1
180049,21609602286.0,IssuesEvent,2022-05-04 08:44:07,detain/ConSolo,https://api.github.com/repos/detain/ConSolo,closed,CVE-2020-8203 (High) detected in lodash-4.17.12-pre.js - autoclosed,security vulnerability,"## CVE-2020-8203 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-4.17.12-pre.js</b></p></summary>

<p>A utility library delivering consistency, customization, performance, & extras.</p>
<p>Library home page: <a href=""https://cdnjs.cloudflare.com/ajax/libs/lodash.js/4.17.12-pre/lodash.js"">https://cdnjs.cloudflare.com/ajax/libs/lodash.js/4.17.12-pre/lodash.js</a></p>
<p>Path to dependency file: /public/vuetify-list-collapse/dist/index.html</p>
<p>Path to vulnerable library: /public/vuetify-list-collapse/dist/index.html</p>
<p>

Dependency Hierarchy:
  - :x: **lodash-4.17.12-pre.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/detain/ConSolo/commit/eef840d3f52ae21cb808bc3aa4232f0ed4019a91"">eef840d3f52ae21cb808bc3aa4232f0ed4019a91</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>  
  
Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.

<p>Publish Date: 2020-07-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8203>CVE-2020-8203</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.4</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - 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://www.npmjs.com/advisories/1523"">https://www.npmjs.com/advisories/1523</a></p>
<p>Release Date: 2020-07-15</p>
<p>Fix Resolution: lodash - 4.17.19</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-8203 (High) detected in lodash-4.17.12-pre.js - autoclosed - ## CVE-2020-8203 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-4.17.12-pre.js</b></p></summary>

<p>A utility library delivering consistency, customization, performance, & extras.</p>
<p>Library home page: <a href=""https://cdnjs.cloudflare.com/ajax/libs/lodash.js/4.17.12-pre/lodash.js"">https://cdnjs.cloudflare.com/ajax/libs/lodash.js/4.17.12-pre/lodash.js</a></p>
<p>Path to dependency file: /public/vuetify-list-collapse/dist/index.html</p>
<p>Path to vulnerable library: /public/vuetify-list-collapse/dist/index.html</p>
<p>

Dependency Hierarchy:
  - :x: **lodash-4.17.12-pre.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/detain/ConSolo/commit/eef840d3f52ae21cb808bc3aa4232f0ed4019a91"">eef840d3f52ae21cb808bc3aa4232f0ed4019a91</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>  
  
Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.

<p>Publish Date: 2020-07-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8203>CVE-2020-8203</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.4</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - 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://www.npmjs.com/advisories/1523"">https://www.npmjs.com/advisories/1523</a></p>
<p>Release Date: 2020-07-15</p>
<p>Fix Resolution: lodash - 4.17.19</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in lodash       pre js   autoclosed      cve       high severity vulnerability     vulnerable library    lodash       pre js      a utility library delivering consistency  customization  performance    extras    library home page   a href     path to dependency file   public vuetify list collapse dist index html   path to vulnerable library   public vuetify list collapse dist index html     dependency hierarchy       x    lodash       pre js    vulnerable library   found in head commit   a href     found in base branch   master              vulnerability details         prototype pollution attack when using   zipobjectdeep in lodash before          publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  high     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  lodash                       step up your open source security game with whitesource    ,0
136182,30493323458.0,IssuesEvent,2023-07-18 09:09:49,jOOQ/jOOQ,https://api.github.com/repos/jOOQ/jOOQ,opened,<pojosAsJavaRecordClasses/> doesn't work with tables containing more than 254 columns,T: Defect C: Code Generation P: Medium E: All Editions,"The usual Java limit of methods having at most 254 parameters (255 for static methods) is still causing trouble with generated records:

```java
    Integer c254,
    Integer c255
) implements Serializable {
```

The compiler complains:

> Too many parameters, parameter c255 is exceeding the limit of 255 words eligible for method parameters

The solution here is to just generate ordinary POJOs for these tables.

Related problems:

- https://github.com/jOOQ/jOOQ/issues/3176
- https://github.com/jOOQ/jOOQ/issues/15375

I've just noticed, we don't have any integration tests that check these limits for Scala and Kotlin generated code. I'm not sure if those compilers somehow work around the limitation, which is purely a JVM limitation, not strictly a Java language one (i.e. it would be possible for the Java compiler to create synthetic wrapper objects, and unwrap them transparently)
",1.0,"<pojosAsJavaRecordClasses/> doesn't work with tables containing more than 254 columns - The usual Java limit of methods having at most 254 parameters (255 for static methods) is still causing trouble with generated records:

```java
    Integer c254,
    Integer c255
) implements Serializable {
```

The compiler complains:

> Too many parameters, parameter c255 is exceeding the limit of 255 words eligible for method parameters

The solution here is to just generate ordinary POJOs for these tables.

Related problems:

- https://github.com/jOOQ/jOOQ/issues/3176
- https://github.com/jOOQ/jOOQ/issues/15375

I've just noticed, we don't have any integration tests that check these limits for Scala and Kotlin generated code. I'm not sure if those compilers somehow work around the limitation, which is purely a JVM limitation, not strictly a Java language one (i.e. it would be possible for the Java compiler to create synthetic wrapper objects, and unwrap them transparently)
",0,  doesn t work with tables containing more than   columns   the usual java limit of methods having at most   parameters    for static methods  is still causing trouble with generated records        java      integer         integer      implements serializable           the compiler complains       too many parameters  parameter   is exceeding the limit of   words eligible for method parameters    the solution here is to just generate ordinary pojos for these tables     related problems                 i ve just noticed  we don t have any integration tests that check these limits for scala and kotlin generated code  i m not sure if those compilers somehow work around the limitation  which is purely a jvm limitation  not strictly a java language one  i e  it would be possible for the java compiler to create synthetic wrapper objects  and unwrap them transparently   ,0
26790,13108531535.0,IssuesEvent,2020-08-04 17:00:20,terrabasedb/terrabase,https://api.github.com/repos/terrabasedb/terrabase,closed,Use a `Bytes` structure to store data,performance required-improvement server,Currently we're using a `String` object to store data which has it's own drawbacks. We should instead use a memory-efficient and thread-friendly structure which would greatly improve the time taken for reading/writing data.,True,Use a `Bytes` structure to store data - Currently we're using a `String` object to store data which has it's own drawbacks. We should instead use a memory-efficient and thread-friendly structure which would greatly improve the time taken for reading/writing data.,0,use a  bytes  structure to store data   currently we re using a  string  object to store data which has it s own drawbacks  we should instead use a memory efficient and thread friendly structure which would greatly improve the time taken for reading writing data ,0
16172,4021320195.0,IssuesEvent,2016-05-16 21:30:58,golang/go,https://api.github.com/repos/golang/go,closed,doc: update docs as a followup of deprecation of 1.4 dependent code in x/tools,Documentation,"A few packages in golang.org/x/tools have been removed as part of https://groups.google.com/forum/#!topic/golang-announce/qu_rAphYdxY, and the deletion makes a few dead links on https://golang.org/doc/cmd; e.g., https://godoc.org/golang.org/x/tools/cmd/vet. It needs to be updated for avoiding confusion.",1.0,"doc: update docs as a followup of deprecation of 1.4 dependent code in x/tools - A few packages in golang.org/x/tools have been removed as part of https://groups.google.com/forum/#!topic/golang-announce/qu_rAphYdxY, and the deletion makes a few dead links on https://golang.org/doc/cmd; e.g., https://godoc.org/golang.org/x/tools/cmd/vet. It needs to be updated for avoiding confusion.",1,doc  update docs as a followup of deprecation of     dependent code in x tools   a few packages in golang org x tools have been removed as part of   and the deletion makes a few dead links on   e g     it needs to be updated for avoiding confusion ,1
34340,6312281471.0,IssuesEvent,2017-07-24 02:31:53,golang/go,https://api.github.com/repos/golang/go,opened,"x/crypto/nacl/secretbox: document how small is ""small""",Documentation,"The documentation for secretbox states:

    Package secretbox encrypts and authenticates small messages.

However, it is unclear to a casual reader how small ""small"" is.

[""Validation and Verification"" says:](https://nacl.cr.yp.to/valid.html)

> Tests are currently limited to 4096-byte messages. This is one of several reasons that callers should (1) split all data into packets sent through the network; (2) put a small global limit on packet length; and (3) separately encrypt and authenticate each packet.

With a link to more explanation here: https://groups.google.com/forum/#!original/boring-crypto/BpUmNMXKMYQ/EEwAIeQdjacJ

We may want to provide the same advice to callers of this package, and advise them that ""small"" means ""4096 bytes or fewer""
",1.0,"x/crypto/nacl/secretbox: document how small is ""small"" - The documentation for secretbox states:

    Package secretbox encrypts and authenticates small messages.

However, it is unclear to a casual reader how small ""small"" is.

[""Validation and Verification"" says:](https://nacl.cr.yp.to/valid.html)

> Tests are currently limited to 4096-byte messages. This is one of several reasons that callers should (1) split all data into packets sent through the network; (2) put a small global limit on packet length; and (3) separately encrypt and authenticate each packet.

With a link to more explanation here: https://groups.google.com/forum/#!original/boring-crypto/BpUmNMXKMYQ/EEwAIeQdjacJ

We may want to provide the same advice to callers of this package, and advise them that ""small"" means ""4096 bytes or fewer""
",1,x crypto nacl secretbox  document how small is  small    the documentation for secretbox states         package secretbox encrypts and authenticates small messages     however  it is unclear to a casual reader how small  small  is              tests are currently limited to   byte messages  this is one of several reasons that callers should     split all data into packets sent through the network      put a small global limit on packet length  and     separately encrypt and authenticate each packet     with a link to more explanation here       we may want to provide the same advice to callers of this package  and advise them that  small  means    bytes or fewer   ,1
64397,7795934109.0,IssuesEvent,2018-06-08 09:46:43,baskager/redesign-minor-web-dev,https://api.github.com/repos/baskager/redesign-minor-web-dev,closed,Create styleguide,design enhancement must have,"**Realises goal of Bas Kager**
Bas will make the styleguide and the team members will assist",1.0,"Create styleguide - **Realises goal of Bas Kager**
Bas will make the styleguide and the team members will assist",0,create styleguide     realises goal of bas kager    bas will make the styleguide and the team members will assist,0
198944,6979348441.0,IssuesEvent,2017-12-12 20:42:37,fossasia/badgeyay,https://api.github.com/repos/fossasia/badgeyay,closed,Badgeyay web-app not working,has-PR priority,"**I'm submitting a ...**
- [x] bug report
- [ ] feature request

**Issue:**
The URL - ""https://badgeyay-dev.herokuapp.com/"" is showing some error and the application is not being deployed properly on heroku. 

**Screenshots:**

![screenshot from 2017-12-13 00 37 12](https://user-images.githubusercontent.com/28600022/33903411-52f53ac0-df9e-11e7-954f-f88cc861f659.png)",1.0,"Badgeyay web-app not working - **I'm submitting a ...**
- [x] bug report
- [ ] feature request

**Issue:**
The URL - ""https://badgeyay-dev.herokuapp.com/"" is showing some error and the application is not being deployed properly on heroku. 

**Screenshots:**

![screenshot from 2017-12-13 00 37 12](https://user-images.githubusercontent.com/28600022/33903411-52f53ac0-df9e-11e7-954f-f88cc861f659.png)",0,badgeyay web app not working     i m submitting a            bug report      feature request      issue     the url      is showing some error and the application is not being deployed properly on heroku        screenshots           ,0
338168,10225200366.0,IssuesEvent,2019-08-16 14:36:57,Warcraft-GoA-Development-Team/Warcraft-Guardians-of-Azeroth,https://api.github.com/repos/Warcraft-GoA-Development-Team/Warcraft-Guardians-of-Azeroth,closed,[LOCALIZATION] | the Light,:beetle: bug - localization :scroll: :grey_exclamation: priority low,"**Mod Version**
a2c774f4

**Please explain your issue in as much detail as possible:**
lowercase

**Upload screenshots of the problem localization:**

<details>

![image](https://user-images.githubusercontent.com/46576860/63040287-d2758100-becd-11e9-819b-80b397976fd3.png)

</details>",1.0,"[LOCALIZATION] | the Light - **Mod Version**
a2c774f4

**Please explain your issue in as much detail as possible:**
lowercase

**Upload screenshots of the problem localization:**

<details>

![image](https://user-images.githubusercontent.com/46576860/63040287-d2758100-becd-11e9-819b-80b397976fd3.png)

</details>",0,    the light     mod version           please explain your issue in as much detail as possible     lowercase      upload screenshots of the problem localization                     ,0
324519,24005185237.0,IssuesEvent,2022-09-14 14:20:25,golang/go,https://api.github.com/repos/golang/go,closed,path/filepath: document that WalkDir calls fs.WalkDirFunc with platform-specific paths,Documentation NeedsFix,"The function `filepath.WalkDir` uses the callback `fs.WalkDirFunc`.

Within `path/filepath`, paths generally use the slash separator of the host platform, so the `root` parameter to `filepath.WalkDir` is clearly a platform-specific path.

However, it wasn't obvious to me upon reading the documentation whether the path *passed to the WalkDirFunc* was a platform-specific path or used `/` as the path separator. In fact, all the paths use the platform separator, but I had to read the code to be sure. Here are some reasons I thought the `WalkDirFunc` path might be `/`-separated:

* Other types/functions inside `io/fs`, such as `fs.FS`, use `/`-separated paths.
* When the same callback function `fs.WalkDirFunc` is called via `fs.WalkDir` (rather than `filepath.WalkDir`) it sees `/`-separated paths.
* The `fs.WalkDirFunc` documentation mentions `/`-separated paths:

   ```
       The path argument contains the argument to WalkDir as a prefix. That is, if
       WalkDir is called with root argument ""dir"" and finds a file named ""a"" in
       that directory, the walk function will be called with argument ""dir/a"".
   ```
   (I believe that on Windows, *if* this is coming from `filepath.WalkDir`, then it would be `dir\a` rather than `dir/a`.)

I think the documentation of `filepath.WalkDir` and/or `fs.WalkDirFunc` could be clearer on this point.

/cc @rsc who wrote most of this stuff as part of io/fs for Go 1.16.",1.0,"path/filepath: document that WalkDir calls fs.WalkDirFunc with platform-specific paths - The function `filepath.WalkDir` uses the callback `fs.WalkDirFunc`.

Within `path/filepath`, paths generally use the slash separator of the host platform, so the `root` parameter to `filepath.WalkDir` is clearly a platform-specific path.

However, it wasn't obvious to me upon reading the documentation whether the path *passed to the WalkDirFunc* was a platform-specific path or used `/` as the path separator. In fact, all the paths use the platform separator, but I had to read the code to be sure. Here are some reasons I thought the `WalkDirFunc` path might be `/`-separated:

* Other types/functions inside `io/fs`, such as `fs.FS`, use `/`-separated paths.
* When the same callback function `fs.WalkDirFunc` is called via `fs.WalkDir` (rather than `filepath.WalkDir`) it sees `/`-separated paths.
* The `fs.WalkDirFunc` documentation mentions `/`-separated paths:

   ```
       The path argument contains the argument to WalkDir as a prefix. That is, if
       WalkDir is called with root argument ""dir"" and finds a file named ""a"" in
       that directory, the walk function will be called with argument ""dir/a"".
   ```
   (I believe that on Windows, *if* this is coming from `filepath.WalkDir`, then it would be `dir\a` rather than `dir/a`.)

I think the documentation of `filepath.WalkDir` and/or `fs.WalkDirFunc` could be clearer on this point.

/cc @rsc who wrote most of this stuff as part of io/fs for Go 1.16.",1,path filepath  document that walkdir calls fs walkdirfunc with platform specific paths   the function  filepath walkdir  uses the callback  fs walkdirfunc      within  path filepath   paths generally use the slash separator of the host platform  so the  root  parameter to  filepath walkdir  is clearly a platform specific path     however  it wasn t obvious to me upon reading the documentation whether the path  passed to the walkdirfunc  was a platform specific path or used     as the path separator  in fact  all the paths use the platform separator  but i had to read the code to be sure  here are some reasons i thought the  walkdirfunc  path might be     separated       other types functions inside  io fs   such as  fs fs   use     separated paths     when the same callback function  fs walkdirfunc  is called via  fs walkdir   rather than  filepath walkdir   it sees     separated paths     the  fs walkdirfunc  documentation mentions     separated paths                    the path argument contains the argument to walkdir as a prefix  that is  if         walkdir is called with root argument  dir  and finds a file named  a  in         that directory  the walk function will be called with argument  dir a                i believe that on windows   if  this is coming from  filepath walkdir   then it would be  dir a  rather than  dir a       i think the documentation of  filepath walkdir  and or  fs walkdirfunc  could be clearer on this point      cc  rsc who wrote most of this stuff as part of io fs for go     ,1
31963,26283242634.0,IssuesEvent,2023-01-07 14:47:06,ocaml-sf/learn-ocaml,https://api.github.com/repos/ocaml-sf/learn-ocaml,opened,Feature: continuous deployment of the learn-ocaml-public static instance,kind: feature kind: infrastructure,"**Related project scope(s):** CI

**Related user(s):**
- @erikmd

## The problem

It would be good to automatically update the learn-ocaml-corpus deployment automatically
at each merge in https://github.com/ocaml-sf/learn-ocaml/tree/master

### Wanted solution

A new CI workflow that adds a commit in https://github.com/ocaml-sf/learn-ocaml-public

### Considered alternatives

N/A

## Additional context

N/A",1.0,"Feature: continuous deployment of the learn-ocaml-public static instance - **Related project scope(s):** CI

**Related user(s):**
- @erikmd

## The problem

It would be good to automatically update the learn-ocaml-corpus deployment automatically
at each merge in https://github.com/ocaml-sf/learn-ocaml/tree/master

### Wanted solution

A new CI workflow that adds a commit in https://github.com/ocaml-sf/learn-ocaml-public

### Considered alternatives

N/A

## Additional context

N/A",0,feature  continuous deployment of the learn ocaml public static instance     related project scope s     ci      related user s         erikmd       the problem    it would be good to automatically update the learn ocaml corpus deployment automatically  at each merge in          wanted solution    a new ci workflow that adds a commit in          considered alternatives    n a       additional context    n a,0
272360,20743963172.0,IssuesEvent,2022-03-14 20:36:43,golang/go,https://api.github.com/repos/golang/go,closed,x/website: update to latest spec just before release,Documentation NeedsFix release-blocker,"To get the most up-to-date spec into the 1.18 release, rather than cherry-picking possibly multiple CLs until the release, we should create a single CL (immediately before the release) in the release branch which contains a 1:1 copy of the latest spec at tip.

cc: @dmitshur ",1.0,"x/website: update to latest spec just before release - To get the most up-to-date spec into the 1.18 release, rather than cherry-picking possibly multiple CLs until the release, we should create a single CL (immediately before the release) in the release branch which contains a 1:1 copy of the latest spec at tip.

cc: @dmitshur ",1,x website  update to latest spec just before release   to get the most up to date spec into the     release  rather than cherry picking possibly multiple cls until the release  we should create a single cl  immediately before the release  in the release branch which contains a     copy of the latest spec at tip     cc   dmitshur ,1
213576,16527644715.0,IssuesEvent,2021-05-26 22:45:08,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.17: document net changes for Go 1.17,Documentation NeedsInvestigation help wanted release-blocker,"As of filing this issue, the [Go 1.17 draft release notes](https://tip.golang.org/doc/go1.17) contained the following HTML:

<dl id=""net""><dt><a href=""/pkg/net/"">net</a></dt>
  <dd>
    <p><!-- CL 272668 -->
      TODO: <a href=""https://golang.org/cl/272668"">https://golang.org/cl/272668</a>: add IP.IsPrivate
    </p>
    <p><!-- CL 301709 -->
      TODO: <a href=""https://golang.org/cl/301709"">https://golang.org/cl/301709</a>: make go resolver aware of network parameter
    </p>
    <p><!-- CL 307030 -->
      TODO: <a href=""https://golang.org/cl/307030"">https://golang.org/cl/307030</a>: make ErrClosed and ParseError implement net.Error
    </p>
  </dd>
</dl>

---

This TODO needs to be resolved by July 1 so that we can have complete release notes for [Beta 1](https://golang.org/s/release#june-1--december-1-beta-1-issued).

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.17:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.17) and include ""For #44513. Fixes #46014."" in the body.",1.0,"doc/go1.17: document net changes for Go 1.17 - As of filing this issue, the [Go 1.17 draft release notes](https://tip.golang.org/doc/go1.17) contained the following HTML:

<dl id=""net""><dt><a href=""/pkg/net/"">net</a></dt>
  <dd>
    <p><!-- CL 272668 -->
      TODO: <a href=""https://golang.org/cl/272668"">https://golang.org/cl/272668</a>: add IP.IsPrivate
    </p>
    <p><!-- CL 301709 -->
      TODO: <a href=""https://golang.org/cl/301709"">https://golang.org/cl/301709</a>: make go resolver aware of network parameter
    </p>
    <p><!-- CL 307030 -->
      TODO: <a href=""https://golang.org/cl/307030"">https://golang.org/cl/307030</a>: make ErrClosed and ParseError implement net.Error
    </p>
  </dd>
</dl>

---

This TODO needs to be resolved by July 1 so that we can have complete release notes for [Beta 1](https://golang.org/s/release#june-1--december-1-beta-1-issued).

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.17:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.17) and include ""For #44513. Fixes #46014."" in the body.",1,doc      document net changes for go       as of filing this issue  the     contained the following html        net                       todo   a href    add ip isprivate                       todo   a href    make go resolver aware of network parameter                       todo   a href    make errclosed and parseerror implement net error                          this todo needs to be resolved by july   so that we can have complete release notes for        a sequence of steps to resolve this issue may be        come up with a draft release note entry in this issue  then move the issue to needsfix state      send a cl with  doc           and include  for     fixes      in the body ,1
24672,4104695423.0,IssuesEvent,2016-06-05 15:06:02,cockroachdb/cockroach,https://api.github.com/repos/cockroachdb/cockroach,closed,stress: failed test in cockroach/kv/kv.test: TestTxnDBLostDeleteAnomaly,Robot test-failure,"Binary: cockroach/static-tests.tar.gz sha: https://github.com/cockroachdb/cockroach/commits/f55bfc43895b6bd370112ce2af6f5d9d97fa139f

Stress build found a failed test:

```
=== RUN   TestTxnDBLostDeleteAnomaly
W160531 04:34:28.891845 gossip/gossip.go:897  not connected to cluster; use --join to specify a connected node
I160531 04:34:28.891894 storage/engine/rocksdb.go:137  opening in memory rocksdb instance
I160531 04:34:28.893474 kv/txn_correctness_test.go:525  verifying all possible histories for the ""lost update (delete)"" anomaly
I160531 04:34:28.894221 storage/replica_command.go:1484  range 1: new leader lease replica {1 1 1} 1970-01-01 00:00:00 +0000 UTC 1s following replica {0 0 0} 1970-01-01 00:00:00 +0000 UTC 0 [physicalTime=1970-01-01 00:00:00 +0000 UTC]
E160531 04:34:28.895192 config/config.go:382  unable to determine largest reserved object ID from system config: descriptor table not found in system config of 0 values
--- FAIL: TestTxnDBLostDeleteAnomaly (0.41s)
	txn_correctness_test.go:581: ([R1(A) D2(A) W1(B-A) D2(B) C2 C1]): unexpected failure running W1(B-A): txn ""kv/txn_correctness_test.go:633 txn2"" id=9d887dae key=""27.A"" rw=true pri=0.00000005 iso=SNAPSHOT stat=PENDING epo=3 ts=0.000000000,2177 orig=0.000000000,2177 max=0.000000000,2177 wto=false rop=false failed to push ""kv/txn_correctness_test.go:633 txn1"" id=90a2baba key=""27.B"" rw=true pri=0.00000009 iso=SNAPSHOT stat=PENDING epo=0 ts=0.000000000,2171 orig=0.000000000,2171 max=0.000000000,2171 wto=false rop=false
```

Run Details:

```
0 runs so far, 0 failures, over 5s
0 runs so far, 0 failures, over 10s
0 runs so far, 0 failures, over 15s
8 runs so far, 0 failures, over 20s
16 runs so far, 0 failures, over 25s
16 runs so far, 0 failures, over 30s
16 runs so far, 0 failures, over 35s
25 runs so far, 0 failures, over 40s
32 runs so far, 0 failures, over 45s
32 runs so far, 0 failures, over 50s
32 runs so far, 0 failures, over 55s
40 runs so far, 0 failures, over 1m0s
47 runs so far, 0 failures, over 1m5s
48 runs so far, 0 failures, over 1m10s
50 runs so far, 0 failures, over 1m15s
54 runs so far, 0 failures, over 1m20s
62 runs so far, 0 failures, over 1m25s
65 runs so far, 0 failures, over 1m30s
66 runs so far, 0 failures, over 1m35s
67 runs so far, 0 failures, over 1m40s
79 runs so far, 0 failures, over 1m45s
80 runs so far, 0 failures, over 1m50s
82 runs so far, 0 failures, over 1m55s
84 runs so far, 0 failures, over 2m0s
94 runs so far, 0 failures, over 2m5s
97 runs so far, 0 failures, over 2m10s
99 runs so far, 0 failures, over 2m15s
101 runs so far, 0 failures, over 2m20s
109 runs so far, 0 failures, over 2m25s
111 runs so far, 0 failures, over 2m30s
115 runs so far, 0 failures, over 2m35s
117 runs so far, 0 failures, over 2m40s
125 runs so far, 0 failures, over 2m45s
129 runs so far, 0 failures, over 2m50s
130 runs so far, 0 failures, over 2m55s
134 runs so far, 0 failures, over 3m0s
140 runs so far, 0 failures, over 3m5s
144 runs so far, 0 failures, over 3m10s
146 runs so far, 0 failures, over 3m15s
149 runs so far, 0 failures, over 3m20s
155 runs so far, 0 failures, over 3m25s
160 runs completed, 1 failures, over 3m29s
FAIL
```
Please assign, take a look and update the issue accordingly.",1.0,"stress: failed test in cockroach/kv/kv.test: TestTxnDBLostDeleteAnomaly - Binary: cockroach/static-tests.tar.gz sha: https://github.com/cockroachdb/cockroach/commits/f55bfc43895b6bd370112ce2af6f5d9d97fa139f

Stress build found a failed test:

```
=== RUN   TestTxnDBLostDeleteAnomaly
W160531 04:34:28.891845 gossip/gossip.go:897  not connected to cluster; use --join to specify a connected node
I160531 04:34:28.891894 storage/engine/rocksdb.go:137  opening in memory rocksdb instance
I160531 04:34:28.893474 kv/txn_correctness_test.go:525  verifying all possible histories for the ""lost update (delete)"" anomaly
I160531 04:34:28.894221 storage/replica_command.go:1484  range 1: new leader lease replica {1 1 1} 1970-01-01 00:00:00 +0000 UTC 1s following replica {0 0 0} 1970-01-01 00:00:00 +0000 UTC 0 [physicalTime=1970-01-01 00:00:00 +0000 UTC]
E160531 04:34:28.895192 config/config.go:382  unable to determine largest reserved object ID from system config: descriptor table not found in system config of 0 values
--- FAIL: TestTxnDBLostDeleteAnomaly (0.41s)
	txn_correctness_test.go:581: ([R1(A) D2(A) W1(B-A) D2(B) C2 C1]): unexpected failure running W1(B-A): txn ""kv/txn_correctness_test.go:633 txn2"" id=9d887dae key=""27.A"" rw=true pri=0.00000005 iso=SNAPSHOT stat=PENDING epo=3 ts=0.000000000,2177 orig=0.000000000,2177 max=0.000000000,2177 wto=false rop=false failed to push ""kv/txn_correctness_test.go:633 txn1"" id=90a2baba key=""27.B"" rw=true pri=0.00000009 iso=SNAPSHOT stat=PENDING epo=0 ts=0.000000000,2171 orig=0.000000000,2171 max=0.000000000,2171 wto=false rop=false
```

Run Details:

```
0 runs so far, 0 failures, over 5s
0 runs so far, 0 failures, over 10s
0 runs so far, 0 failures, over 15s
8 runs so far, 0 failures, over 20s
16 runs so far, 0 failures, over 25s
16 runs so far, 0 failures, over 30s
16 runs so far, 0 failures, over 35s
25 runs so far, 0 failures, over 40s
32 runs so far, 0 failures, over 45s
32 runs so far, 0 failures, over 50s
32 runs so far, 0 failures, over 55s
40 runs so far, 0 failures, over 1m0s
47 runs so far, 0 failures, over 1m5s
48 runs so far, 0 failures, over 1m10s
50 runs so far, 0 failures, over 1m15s
54 runs so far, 0 failures, over 1m20s
62 runs so far, 0 failures, over 1m25s
65 runs so far, 0 failures, over 1m30s
66 runs so far, 0 failures, over 1m35s
67 runs so far, 0 failures, over 1m40s
79 runs so far, 0 failures, over 1m45s
80 runs so far, 0 failures, over 1m50s
82 runs so far, 0 failures, over 1m55s
84 runs so far, 0 failures, over 2m0s
94 runs so far, 0 failures, over 2m5s
97 runs so far, 0 failures, over 2m10s
99 runs so far, 0 failures, over 2m15s
101 runs so far, 0 failures, over 2m20s
109 runs so far, 0 failures, over 2m25s
111 runs so far, 0 failures, over 2m30s
115 runs so far, 0 failures, over 2m35s
117 runs so far, 0 failures, over 2m40s
125 runs so far, 0 failures, over 2m45s
129 runs so far, 0 failures, over 2m50s
130 runs so far, 0 failures, over 2m55s
134 runs so far, 0 failures, over 3m0s
140 runs so far, 0 failures, over 3m5s
144 runs so far, 0 failures, over 3m10s
146 runs so far, 0 failures, over 3m15s
149 runs so far, 0 failures, over 3m20s
155 runs so far, 0 failures, over 3m25s
160 runs completed, 1 failures, over 3m29s
FAIL
```
Please assign, take a look and update the issue accordingly.",0,stress  failed test in cockroach kv kv test  testtxndblostdeleteanomaly   binary  cockroach static tests tar gz sha     stress build found a failed test           run   testtxndblostdeleteanomaly           gossip gossip go    not connected to cluster  use   join to specify a connected node           storage engine rocksdb go    opening in memory rocksdb instance           kv txn correctness test go    verifying all possible histories for the  lost update  delete   anomaly           storage replica command go    range    new leader lease replica                        utc   following replica                        utc               config config go    unable to determine largest reserved object id from system config  descriptor table not found in system config of   values     fail  testtxndblostdeleteanomaly       	txn correctness test go         unexpected failure running   b a   txn  kv txn correctness test go      id   key    a  rw true pri     iso snapshot stat pending epo   ts       orig       max       wto false rop false failed to push  kv txn correctness test go      id   key    b  rw true pri     iso snapshot stat pending epo   ts       orig       max       wto false rop false      run details         runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs so far    failures  over     runs completed    failures  over   fail     please assign  take a look and update the issue accordingly ,0
6742,23825227552.0,IssuesEvent,2022-09-05 14:22:02,mozilla-mobile/firefox-ios,https://api.github.com/repos/mozilla-mobile/firefox-ios,opened,[Bitrise] Smoketest for iPad is wrong running the Full Functional test plan instead,eng:automation,"For the workflow RunSmokeXCUITestsiPad https://github.com/mozilla-mobile/firefox-ios/blob/c6e718220467ff3b55505e993b8f88151c3b4747/bitrise.yml#L725 we are running the Full Functional test suite instead of just the Smoketest plan. See[ bitrise logs](https://app.bitrise.io/build/87a9400b-4f76-4ba0-a358-ec3c4e21b684?tab=log).

The reason is that there is a - test_plan: <unset> option that we need to use instead of the - xcodebuild_test_options: ""-testPlan SmokeXCUITests"". The latter one is unkown and the test plan appears unset, that's why bitrise is running all the tests in the Fennec_Enterprise_XCUITests instead of just the SmokeTest

cc @clarmso I will take this one and ask you for review so that you start being familiar with the bitrise.yml file.",1.0,"[Bitrise] Smoketest for iPad is wrong running the Full Functional test plan instead - For the workflow RunSmokeXCUITestsiPad https://github.com/mozilla-mobile/firefox-ios/blob/c6e718220467ff3b55505e993b8f88151c3b4747/bitrise.yml#L725 we are running the Full Functional test suite instead of just the Smoketest plan. See[ bitrise logs](https://app.bitrise.io/build/87a9400b-4f76-4ba0-a358-ec3c4e21b684?tab=log).

The reason is that there is a - test_plan: <unset> option that we need to use instead of the - xcodebuild_test_options: ""-testPlan SmokeXCUITests"". The latter one is unkown and the test plan appears unset, that's why bitrise is running all the tests in the Fennec_Enterprise_XCUITests instead of just the SmokeTest

cc @clarmso I will take this one and ask you for review so that you start being familiar with the bitrise.yml file.",0,  smoketest for ipad is wrong running the full functional test plan instead   for the workflow runsmokexcuitestsipad   we are running the full functional test suite instead of just the smoketest plan  see       the reason is that there is a   test plan    option that we need to use instead of the   xcodebuild test options    testplan smokexcuitests   the latter one is unkown and the test plan appears unset  that s why bitrise is running all the tests in the fennec enterprise xcuitests instead of just the smoketest    cc  clarmso i will take this one and ask you for review so that you start being familiar with the bitrise yml file ,0
36479,6536369706.0,IssuesEvent,2017-08-31 17:52:50,golang/go,https://api.github.com/repos/golang/go,closed,doc: Writing web applications ignores error from ListenAndServe,Documentation,"> @campoy: 
> Does everyone forget to check the error on ListenAndServe? #golang
> https://twitter.com/francesc/status/838547440710012928

Nothing in this tutorial https://golang.org/doc/articles/wiki/ **Writing Web Applications**, in the Articles section of documentation, seems to indicate that ListenAndServe may return an error. Errors should be checked.

> https://golang.org/pkg/net/http/#ListenAndServe
> func ListenAndServe(addr string, handler Handler) error
> ListenAndServe always returns a non-nil error.

Since I don't see an issue opened by @campoy , I'm opening one.

**EDIT: Clarified that the issue is in Article, not the package documentation.**",1.0,"doc: Writing web applications ignores error from ListenAndServe - > @campoy: 
> Does everyone forget to check the error on ListenAndServe? #golang
> https://twitter.com/francesc/status/838547440710012928

Nothing in this tutorial https://golang.org/doc/articles/wiki/ **Writing Web Applications**, in the Articles section of documentation, seems to indicate that ListenAndServe may return an error. Errors should be checked.

> https://golang.org/pkg/net/http/#ListenAndServe
> func ListenAndServe(addr string, handler Handler) error
> ListenAndServe always returns a non-nil error.

Since I don't see an issue opened by @campoy , I'm opening one.

**EDIT: Clarified that the issue is in Article, not the package documentation.**",1,doc  writing web applications ignores error from listenandserve      campoy      does everyone forget to check the error on listenandserve   golang         nothing in this tutorial     writing web applications    in the articles section of documentation  seems to indicate that listenandserve may return an error  errors should be checked            func listenandserve addr string  handler handler  error    listenandserve always returns a non nil error     since i don t see an issue opened by  campoy   i m opening one       edit  clarified that the issue is in article  not the package documentation   ,1
34263,6307133915.0,IssuesEvent,2017-07-21 23:26:45,golang/go,https://api.github.com/repos/golang/go,closed,doc: add Go for IntelliJ editor guide,DevExp Documentation,"This is a tracking bug for #20398 Go for IntelliJ.

### Name:
Gogland (codename, not final)
Homepage: https://www.jetbrains.com/go/
Help: https://www.jetbrains.com/help/go/1.0/getting-started-with-gogland.html

### Description:
Distributed as standalone IDE or plugin for IntelliJ Platform based IDEs.

- Editing:
  - smart code completion and type based completion
  - postfix completion and live (user defined) templates
  - formatting on save (gofmt / goimports) and as you type
  - automatic imports and disambiguation resolution for multiple-options
  - vetting, linting and code analysis as you type and on-demand
  - rename, move packages, implement interface, extract variable/method refactoring, interface stubbing
  - support for SQL and other languages features in string literals

- Navigation:
  - builtin documentation display
  - jump to definition or usage / implementation
  - interface matching for method (display which interfaces implement a method)

- Testing and Debugging:
  - run / debug / display coverage for all tests in a project, all tests in a package or a specific test in a specific package
  - Delve integration",1.0,"doc: add Go for IntelliJ editor guide - This is a tracking bug for #20398 Go for IntelliJ.

### Name:
Gogland (codename, not final)
Homepage: https://www.jetbrains.com/go/
Help: https://www.jetbrains.com/help/go/1.0/getting-started-with-gogland.html

### Description:
Distributed as standalone IDE or plugin for IntelliJ Platform based IDEs.

- Editing:
  - smart code completion and type based completion
  - postfix completion and live (user defined) templates
  - formatting on save (gofmt / goimports) and as you type
  - automatic imports and disambiguation resolution for multiple-options
  - vetting, linting and code analysis as you type and on-demand
  - rename, move packages, implement interface, extract variable/method refactoring, interface stubbing
  - support for SQL and other languages features in string literals

- Navigation:
  - builtin documentation display
  - jump to definition or usage / implementation
  - interface matching for method (display which interfaces implement a method)

- Testing and Debugging:
  - run / debug / display coverage for all tests in a project, all tests in a package or a specific test in a specific package
  - Delve integration",1,doc  add go for intellij editor guide   this is a tracking bug for    go for intellij         name   gogland  codename  not final   homepage     help           description   distributed as standalone ide or plugin for intellij platform based ides       editing       smart code completion and type based completion      postfix completion and live  user defined  templates      formatting on save  gofmt   goimports  and as you type      automatic imports and disambiguation resolution for multiple options      vetting  linting and code analysis as you type and on demand      rename  move packages  implement interface  extract variable method refactoring  interface stubbing      support for sql and other languages features in string literals      navigation       builtin documentation display      jump to definition or usage   implementation      interface matching for method  display which interfaces implement a method       testing and debugging       run   debug   display coverage for all tests in a project  all tests in a package or a specific test in a specific package      delve integration,1
3007,2730806909.0,IssuesEvent,2015-04-16 16:45:15,golang/go,https://api.github.com/repos/golang/go,closed,os: document that FileMode permission bits are Unix bits,Documentation,"by **Mortdeus@gocos2d.org**:

<pre>It would be nice to add 

`rwx(111[7]) rw(110[6]) rx(101[5]) r(100[4]) wx(011[3]) w(010[2]) x(001[1])`

as a godoc comment at

<a href=""https://code.google.com/p/go/source/browse/src/pkg/os/types.go#56"">https://code.google.com/p/go/source/browse/src/pkg/os/types.go#56</a></pre>",1.0,"os: document that FileMode permission bits are Unix bits - by **Mortdeus@gocos2d.org**:

<pre>It would be nice to add 

`rwx(111[7]) rw(110[6]) rx(101[5]) r(100[4]) wx(011[3]) w(010[2]) x(001[1])`

as a godoc comment at

<a href=""https://code.google.com/p/go/source/browse/src/pkg/os/types.go#56"">https://code.google.com/p/go/source/browse/src/pkg/os/types.go#56</a></pre>",1,os  document that filemode permission bits are unix bits   by   mortdeus   org      it would be nice to add    rwx     rw     rx     r     wx     w     x       as a godoc comment at   a href   ,1
617058,19340635576.0,IssuesEvent,2021-12-15 03:47:07,iTaylorCodes/Capstone-2-Neighborhood-fe,https://api.github.com/repos/iTaylorCodes/Capstone-2-Neighborhood-fe,opened,[10.5] Application needs a loading spinner,enhancement priority,Application needs to have a loading spinner to ensure requests to backend are processed before components are mounted.,1.0,[10.5] Application needs a loading spinner - Application needs to have a loading spinner to ensure requests to backend are processed before components are mounted.,0,  application needs a loading spinner   application needs to have a loading spinner to ensure requests to backend are processed before components are mounted ,0
32074,6029119750.0,IssuesEvent,2017-06-08 17:16:09,golang/go,https://api.github.com/repos/golang/go,closed,bufio: Reader.WriteTo documentation should clarify that multiple calls to the upstream Reader may be made,Documentation,"I am unsure if this is intended behavior (in which case this is a documentation problem), or a bug (in which case it may be a bug and a documentation problem :) ). Please advise (or perhaps it's neither, of course); I have patches for both I can submit.

### What version of Go are you using (`go version`)?

go version devel +d2fea0447f Tue Feb 14 19:44:35 2017 +0000 linux/amd64

### What did you do?

* Create a `net.Conn` that receives some bytes on the first call to Read, and then holds the connection open (so that you do not receive an io.EOF from a call to Read).
* Now wrap it in a `bufio.Reader`.
* Call `io.Copy` on the new buffered reader and copy it somewhere else (into a bytes.Buffer, for example).


### What did you expect to see?

I expected the bufio.Reader's `WriteTo` method to be called, proxy a single call to `conn.Read`, write that data, and then return.

### What did you see instead?

Instead, it attempts to call `conn.Read` a second time (the behavior is to read until EOF or an error is returned).

This may not be an issue; the documentation for [`io.WriterTo`](https://godoc.org/io#WriterTo) says:

> WriteTo writes data to w until there's no more data to write or when an error occurs.

However, it is unclear to me if ""no more data to write"" means ""until EOF"" in the case of the `bufio.Reader` implementation, or if it means ""the buffer was flushed"" or, if the buffer was empty, ""a successful proxied read call had the read data written"".

Personally I expected this to call Read at most once, much like the bufio.Reader's Read method.

I think that this behavior should either be changed to not use `fill()` (and I am happy to make this change), or the documentation should explicitly say that `bufio.Reader`'s `WriteTo` method writes until EOF or an error is returned from an upstream Read call.
",1.0,"bufio: Reader.WriteTo documentation should clarify that multiple calls to the upstream Reader may be made - I am unsure if this is intended behavior (in which case this is a documentation problem), or a bug (in which case it may be a bug and a documentation problem :) ). Please advise (or perhaps it's neither, of course); I have patches for both I can submit.

### What version of Go are you using (`go version`)?

go version devel +d2fea0447f Tue Feb 14 19:44:35 2017 +0000 linux/amd64

### What did you do?

* Create a `net.Conn` that receives some bytes on the first call to Read, and then holds the connection open (so that you do not receive an io.EOF from a call to Read).
* Now wrap it in a `bufio.Reader`.
* Call `io.Copy` on the new buffered reader and copy it somewhere else (into a bytes.Buffer, for example).


### What did you expect to see?

I expected the bufio.Reader's `WriteTo` method to be called, proxy a single call to `conn.Read`, write that data, and then return.

### What did you see instead?

Instead, it attempts to call `conn.Read` a second time (the behavior is to read until EOF or an error is returned).

This may not be an issue; the documentation for [`io.WriterTo`](https://godoc.org/io#WriterTo) says:

> WriteTo writes data to w until there's no more data to write or when an error occurs.

However, it is unclear to me if ""no more data to write"" means ""until EOF"" in the case of the `bufio.Reader` implementation, or if it means ""the buffer was flushed"" or, if the buffer was empty, ""a successful proxied read call had the read data written"".

Personally I expected this to call Read at most once, much like the bufio.Reader's Read method.

I think that this behavior should either be changed to not use `fill()` (and I am happy to make this change), or the documentation should explicitly say that `bufio.Reader`'s `WriteTo` method writes until EOF or an error is returned from an upstream Read call.
",1,bufio  reader writeto documentation should clarify that multiple calls to the upstream reader may be made   i am unsure if this is intended behavior  in which case this is a documentation problem   or a bug  in which case it may be a bug and a documentation problem       please advise  or perhaps it s neither  of course   i have patches for both i can submit         what version of go are you using   go version       go version devel    tue feb              linux          what did you do       create a  net conn  that receives some bytes on the first call to read  and then holds the connection open  so that you do not receive an io eof from a call to read      now wrap it in a  bufio reader      call  io copy  on the new buffered reader and copy it somewhere else  into a bytes buffer  for example            what did you expect to see     i expected the bufio reader s  writeto  method to be called  proxy a single call to  conn read   write that data  and then return         what did you see instead     instead  it attempts to call  conn read  a second time  the behavior is to read until eof or an error is returned      this may not be an issue  the documentation for     says       writeto writes data to w until there s no more data to write or when an error occurs     however  it is unclear to me if  no more data to write  means  until eof  in the case of the  bufio reader  implementation  or if it means  the buffer was flushed  or  if the buffer was empty   a successful proxied read call had the read data written      personally i expected this to call read at most once  much like the bufio reader s read method     i think that this behavior should either be changed to not use  fill     and i am happy to make this change   or the documentation should explicitly say that  bufio reader  s  writeto  method writes until eof or an error is returned from an upstream read call   ,1
62347,17023903105.0,IssuesEvent,2021-07-03 04:28:07,tomhughes/trac-tickets,https://api.github.com/repos/tomhughes/trac-tickets,closed,paths and tracks rendering indistinguishable,Component: mapnik Priority: major Resolution: wontfix Type: defect,"**[Submitted to the original trac issue database at 1.43pm, Saturday, 3rd May 2014]**

The rendering of highway=path and highway=track is barely distinguishable.[[BR]]
For example, many huge width highway=residential continue to an extra thin =track and then invisibly change to a =path.[[BR]]
Just like on my National Geographic maps, I suppose that highway=track should be drawn with a distinguishable width something like half that of residential highways.
",1.0,"paths and tracks rendering indistinguishable - **[Submitted to the original trac issue database at 1.43pm, Saturday, 3rd May 2014]**

The rendering of highway=path and highway=track is barely distinguishable.[[BR]]
For example, many huge width highway=residential continue to an extra thin =track and then invisibly change to a =path.[[BR]]
Just like on my National Geographic maps, I suppose that highway=track should be drawn with a distinguishable width something like half that of residential highways.
",0,paths and tracks rendering indistinguishable          the rendering of highway path and highway track is barely distinguishable     for example  many huge width highway residential continue to an extra thin  track and then invisibly change to a  path     just like on my national geographic maps  i suppose that highway track should be drawn with a distinguishable width something like half that of residential highways   ,0
492992,14224120632.0,IssuesEvent,2020-11-17 19:11:41,internetarchive/openlibrary,https://api.github.com/repos/internetarchive/openlibrary,opened,Make covers docker service scaleable,Module: Docker Priority: 2,"We currently have to `covers` instances running on our prod infra. In order to get the same effect using docker, we'll need to:

1) Change our docker-compsoe to `expose` instead of `ports`. This will be a bit of a pickle, because on local we don't want to have an nginx load balancer. It might be time to create a `docker-compose.overrides.yml` for the local environments, and make the main `docker-compose.yml` slightly more robust/bare-bones.
2) Add an `nginx` service for load balancing to `docker-compose.production`, copying as much of the config from production as possible + combining it with the config from the article (below). This might not be trivial. Also be sure to use the same (probably very old) version of nginx in the new service as prod. We can update it later.
3) Run with `--scale covers=2` on production

Read this article for a detailed breakdown of the plan: https://pspdfkit.com/blog/2018/how-to-use-docker-compose-to-run-multiple-instances-of-a-service-in-development/
",1.0,"Make covers docker service scaleable - We currently have to `covers` instances running on our prod infra. In order to get the same effect using docker, we'll need to:

1) Change our docker-compsoe to `expose` instead of `ports`. This will be a bit of a pickle, because on local we don't want to have an nginx load balancer. It might be time to create a `docker-compose.overrides.yml` for the local environments, and make the main `docker-compose.yml` slightly more robust/bare-bones.
2) Add an `nginx` service for load balancing to `docker-compose.production`, copying as much of the config from production as possible + combining it with the config from the article (below). This might not be trivial. Also be sure to use the same (probably very old) version of nginx in the new service as prod. We can update it later.
3) Run with `--scale covers=2` on production

Read this article for a detailed breakdown of the plan: https://pspdfkit.com/blog/2018/how-to-use-docker-compose-to-run-multiple-instances-of-a-service-in-development/
",0,make covers docker service scaleable   we currently have to  covers  instances running on our prod infra  in order to get the same effect using docker  we ll need to        change our docker compsoe to  expose  instead of  ports   this will be a bit of a pickle  because on local we don t want to have an nginx load balancer  it might be time to create a  docker compose overrides yml  for the local environments  and make the main  docker compose yml  slightly more robust bare bones      add an  nginx  service for load balancing to  docker compose production   copying as much of the config from production as possible   combining it with the config from the article  below   this might not be trivial  also be sure to use the same  probably very old  version of nginx in the new service as prod  we can update it later      run with    scale covers    on production    read this article for a detailed breakdown of the plan     ,0
149775,13302143613.0,IssuesEvent,2020-08-25 13:54:29,golang/go,https://api.github.com/repos/golang/go,opened,x/pkgsite: documentation how to add experiments locally,Documentation NeedsFix pkgsite,"We should add a `doc/experiment.md` file which describes how to add experiments when running locally, including:

- Running `go run devtools/cmd/experiment/experiment.go create <experiment> <rollout>`
- Where to find existing experiments
- How to add a new experiment to the codebase",1.0,"x/pkgsite: documentation how to add experiments locally - We should add a `doc/experiment.md` file which describes how to add experiments when running locally, including:

- Running `go run devtools/cmd/experiment/experiment.go create <experiment> <rollout>`
- Where to find existing experiments
- How to add a new experiment to the codebase",1,x pkgsite  documentation how to add experiments locally   we should add a  doc experiment md  file which describes how to add experiments when running locally  including       running  go run devtools cmd experiment experiment go create         where to find existing experiments    how to add a new experiment to the codebase,1
95097,10865926874.0,IssuesEvent,2019-11-14 20:04:06,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/gopls: only use import text as range for textDocument/documentLink responses ,Documentation Tools gopls,"Please answer these questions before submitting your issue. Thanks!

#### What did you do?

Have import statements, a mix of normal imports, aliased imports, `_` imports.

#### What did you expect to see?

Links which span the package path.

#### What did you see instead?

The links span the entire import statement, and not just the link. See:

![image](https://user-images.githubusercontent.com/48577114/68792039-71aa3180-05ff-11ea-8ed3-9743923ad345.png)

Note how the package aliases are also underlined, and even the `_` imported package. Including the quotes also feels wrong. I would personally prefer them to look like:

![image](https://user-images.githubusercontent.com/48577114/68792361-0ca30b80-0600-11ea-8481-cc2b9dac95b7.png)

Which is just a change to:

```go
toProtocolLink(view, m, target, n.Path.Pos()+1, n.End()-1)
```

(But I'm not sure if this is the correct way to get the span of a literal, just a PoC.)

#### Build info

```
golang.org/x/tools/gopls master
    golang.org/x/tools/gopls@v0.1.8-0.20191113163402-bc1376d635b8 h1:xSNm5FMZDYQjehCHcVzpGm4D9oNz/+AD+C/pRROxjMk=
    github.com/BurntSushi/toml@v0.3.1 h1:WXkYYl6Yr3qBf1K79EBnL4mak0OimBfB0XUf9Vl28OQ=
    github.com/sergi/go-diff@v1.0.0 h1:Kpca3qRNrduNnOQeazBd0ysaKrUJiIuISHxogkT9RPQ=
    golang.org/x/sync@v0.0.0-20190423024810-112230192c58 h1:8gQV6CLnAEikrhgkHFbMAEhagSSnXWGV915qUMm9mrU=
    golang.org/x/tools@v0.0.0-20191113163402-bc1376d635b8 h1:3xDEBhGRwlUGJue2GW3jVaqWs/HrAm+Lz4HAoQVWuJs=
    golang.org/x/xerrors@v0.0.0-20190717185122-a985d3407aa7 h1:9zdDQZ7Thm29KFXgAX/+yaf3eVbP7djjWp/dXAppNCc=
    honnef.co/go/tools@v0.0.1-2019.2.3 h1:3JgtbtFHMiCmsznwGVTUWbgGov+pVqnlf1dEJTNAXeM=
```

#### Go info

```
go version go1.13.4 linux/amd64

GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/jake/.cache/go-build""
GOENV=""/home/jake/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/jake/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/lib/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/lib/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/jake/zikaeroh/hortbot/hortbot/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build705508798=/tmp/go-build -gno-record-gcc-switches""
```
",1.0,"x/tools/gopls: only use import text as range for textDocument/documentLink responses  - Please answer these questions before submitting your issue. Thanks!

#### What did you do?

Have import statements, a mix of normal imports, aliased imports, `_` imports.

#### What did you expect to see?

Links which span the package path.

#### What did you see instead?

The links span the entire import statement, and not just the link. See:

![image](https://user-images.githubusercontent.com/48577114/68792039-71aa3180-05ff-11ea-8ed3-9743923ad345.png)

Note how the package aliases are also underlined, and even the `_` imported package. Including the quotes also feels wrong. I would personally prefer them to look like:

![image](https://user-images.githubusercontent.com/48577114/68792361-0ca30b80-0600-11ea-8481-cc2b9dac95b7.png)

Which is just a change to:

```go
toProtocolLink(view, m, target, n.Path.Pos()+1, n.End()-1)
```

(But I'm not sure if this is the correct way to get the span of a literal, just a PoC.)

#### Build info

```
golang.org/x/tools/gopls master
    golang.org/x/tools/gopls@v0.1.8-0.20191113163402-bc1376d635b8 h1:xSNm5FMZDYQjehCHcVzpGm4D9oNz/+AD+C/pRROxjMk=
    github.com/BurntSushi/toml@v0.3.1 h1:WXkYYl6Yr3qBf1K79EBnL4mak0OimBfB0XUf9Vl28OQ=
    github.com/sergi/go-diff@v1.0.0 h1:Kpca3qRNrduNnOQeazBd0ysaKrUJiIuISHxogkT9RPQ=
    golang.org/x/sync@v0.0.0-20190423024810-112230192c58 h1:8gQV6CLnAEikrhgkHFbMAEhagSSnXWGV915qUMm9mrU=
    golang.org/x/tools@v0.0.0-20191113163402-bc1376d635b8 h1:3xDEBhGRwlUGJue2GW3jVaqWs/HrAm+Lz4HAoQVWuJs=
    golang.org/x/xerrors@v0.0.0-20190717185122-a985d3407aa7 h1:9zdDQZ7Thm29KFXgAX/+yaf3eVbP7djjWp/dXAppNCc=
    honnef.co/go/tools@v0.0.1-2019.2.3 h1:3JgtbtFHMiCmsznwGVTUWbgGov+pVqnlf1dEJTNAXeM=
```

#### Go info

```
go version go1.13.4 linux/amd64

GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/jake/.cache/go-build""
GOENV=""/home/jake/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/jake/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/lib/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/lib/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/jake/zikaeroh/hortbot/hortbot/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build705508798=/tmp/go-build -gno-record-gcc-switches""
```
",1,x tools gopls  only use import text as range for textdocument documentlink responses    please answer these questions before submitting your issue  thanks          what did you do     have import statements  a mix of normal imports  aliased imports      imports          what did you expect to see     links which span the package path          what did you see instead     the links span the entire import statement  and not just the link  see             note how the package aliases are also underlined  and even the     imported package  including the quotes also feels wrong  i would personally prefer them to look like             which is just a change to        go  toprotocollink view  m  target  n path pos      n end               but i m not sure if this is the correct way to get the span of a literal  just a poc           build info         golang org x tools gopls master      golang org x tools gopls                  ad c prroxjmk       github com burntsushi toml                 github com sergi go diff                 golang org x sync                     golang org x tools               hram         golang org x xerrors                  dxappncc       honnef co go tools                                 go info         go version       linux            goarch      gobin     gocache   home jake  cache go build   goenv   home jake  config go env   goexe     goflags     gohostarch      gohostos  linux   gonoproxy     gonosumdb     goos  linux   gopath   home jake go   goprivate     goproxy     goroot   usr lib go   gosumdb  sum golang org   gotmpdir     gotooldir   usr lib go pkg tool linux     gccgo  gccgo   ar  ar   cc  gcc   cxx  g     cgo enabled      gomod   home jake zikaeroh hortbot hortbot go mod   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches        ,1
12486,7889316259.0,IssuesEvent,2018-06-28 03:20:09,OctopusDeploy/Issues,https://api.github.com/repos/OctopusDeploy/Issues,closed,Reduce polling frequency of project and main dashboards when page is hidden,area/performance kind/enhancement,"The polling frequency of the dashboards can affect overall system performance.

We should reduce polling frequency when the page is hidden.",True,"Reduce polling frequency of project and main dashboards when page is hidden - The polling frequency of the dashboards can affect overall system performance.

We should reduce polling frequency when the page is hidden.",0,reduce polling frequency of project and main dashboards when page is hidden   the polling frequency of the dashboards can affect overall system performance     we should reduce polling frequency when the page is hidden ,0
21895,4757258989.0,IssuesEvent,2016-10-24 16:05:41,golang/go,https://api.github.com/repos/golang/go,closed,doc: FAQ states copies of an interface results in copies of underlying data.,Documentation NeedsFix,"Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
go1.7

### What operating system and processor architecture are you using (`go env`)?
nacl amd64p32 (go playground https://play.golang.org/p/BRJAYJccog)

### What did you do?
The FAQ states that ""Copying an interface value makes a copy of the thing stored in the interface value. If the interface value holds a struct, copying the interface value makes a copy of the struct.""  After having been told that this was wrong on the #go-nuts irc, I did some testing, and discovered that while a copy is made when the interface value is first ""created"", from then on further copies of the interface value retain the same underlying struct.

Example playground:
https://play.golang.org/p/s0A35084oY

To my mind this is an understandable change, as it is pretty much impossible to change the underlying struct without the use of the unsafe package.  The main issue is that this leaves the FAQ at https://golang.org/doc/faq#pass_by_value out of date, so I am requesting that the FAQ be updated.

### What did you expect to see?
Expected to see the ""copies"" of the interface value to have different ""value"" pointers.

### What did you see instead?
All copies of the interface value have the same ""value"" pointer, while obviously being copies due to different addresses.

",1.0,"doc: FAQ states copies of an interface results in copies of underlying data. - Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
go1.7

### What operating system and processor architecture are you using (`go env`)?
nacl amd64p32 (go playground https://play.golang.org/p/BRJAYJccog)

### What did you do?
The FAQ states that ""Copying an interface value makes a copy of the thing stored in the interface value. If the interface value holds a struct, copying the interface value makes a copy of the struct.""  After having been told that this was wrong on the #go-nuts irc, I did some testing, and discovered that while a copy is made when the interface value is first ""created"", from then on further copies of the interface value retain the same underlying struct.

Example playground:
https://play.golang.org/p/s0A35084oY

To my mind this is an understandable change, as it is pretty much impossible to change the underlying struct without the use of the unsafe package.  The main issue is that this leaves the FAQ at https://golang.org/doc/faq#pass_by_value out of date, so I am requesting that the FAQ be updated.

### What did you expect to see?
Expected to see the ""copies"" of the interface value to have different ""value"" pointers.

### What did you see instead?
All copies of the interface value have the same ""value"" pointer, while obviously being copies due to different addresses.

",1,doc  faq states copies of an interface results in copies of underlying data    please answer these questions before submitting your issue  thanks         what version of go are you using   go version                what operating system and processor architecture are you using   go env     nacl    go playground          what did you do   the faq states that  copying an interface value makes a copy of the thing stored in the interface value  if the interface value holds a struct  copying the interface value makes a copy of the struct    after having been told that this was wrong on the  go nuts irc  i did some testing  and discovered that while a copy is made when the interface value is first  created   from then on further copies of the interface value retain the same underlying struct     example playground        to my mind this is an understandable change  as it is pretty much impossible to change the underlying struct without the use of the unsafe package   the main issue is that this leaves the faq at   out of date  so i am requesting that the faq be updated         what did you expect to see   expected to see the  copies  of the interface value to have different  value  pointers         what did you see instead   all copies of the interface value have the same  value  pointer  while obviously being copies due to different addresses     ,1
47471,13236684700.0,IssuesEvent,2020-08-18 20:14:56,finos/secref-data,https://api.github.com/repos/finos/secref-data,opened,Sep 1st 2020 - SecRef Meeting Minutes,Securities Reference Data meeting,"# Security Reference Data Project Meeting
## Date
Sep 1st 2020 - 11am EST / 4pm BST

## Untracked attendees
- Fullname, Affiliation, (optional) GitHub username
- ...

## Agenda
- [ ] Convene & roll call (5mins)
- [ ] Review and approve [July 21st](https://github.com/finos/secref-data/issues/18), [August 4th](https://github.com/finos/secref-data/issues/21) and [August 18th](https://github.com/finos/secref-data/issues/24) meeting minutes (5 mins)
- [ ] Present additional slide on how the dispute will be resolved (Sailesh) (10 mins)
- [ ] Update on cloud storage options (5 mins)
- [ ] AOB, Q&A & Adjourn (5mins)

## Decisions Made
- [ ] Decision 1
- [ ] Decision 2
- [ ] ...

## Action Items
- [ ] Action 1
- [ ] Action 2
- [ ] ...

### WebEx info
- [WebEx Meeting URL](https://finos.webex.com/finos/j.php?MTID=mf43ec72e7ce8e771da12093c940c7ab9)
- Meeting Number: 668 805 739
- Join by phone: +1.415.655.0003 USA Toll | +44-20319-88141 UK Toll | Access code: 668 805 739
- [Global call-in numbers](https://finos.webex.com/finos/globalcallin.php?serviceType=MC&ED=582460637&tollFree=0)
",True,"Sep 1st 2020 - SecRef Meeting Minutes - # Security Reference Data Project Meeting
## Date
Sep 1st 2020 - 11am EST / 4pm BST

## Untracked attendees
- Fullname, Affiliation, (optional) GitHub username
- ...

## Agenda
- [ ] Convene & roll call (5mins)
- [ ] Review and approve [July 21st](https://github.com/finos/secref-data/issues/18), [August 4th](https://github.com/finos/secref-data/issues/21) and [August 18th](https://github.com/finos/secref-data/issues/24) meeting minutes (5 mins)
- [ ] Present additional slide on how the dispute will be resolved (Sailesh) (10 mins)
- [ ] Update on cloud storage options (5 mins)
- [ ] AOB, Q&A & Adjourn (5mins)

## Decisions Made
- [ ] Decision 1
- [ ] Decision 2
- [ ] ...

## Action Items
- [ ] Action 1
- [ ] Action 2
- [ ] ...

### WebEx info
- [WebEx Meeting URL](https://finos.webex.com/finos/j.php?MTID=mf43ec72e7ce8e771da12093c940c7ab9)
- Meeting Number: 668 805 739
- Join by phone: +1.415.655.0003 USA Toll | +44-20319-88141 UK Toll | Access code: 668 805 739
- [Global call-in numbers](https://finos.webex.com/finos/globalcallin.php?serviceType=MC&ED=582460637&tollFree=0)
",0,sep       secref meeting minutes     security reference data project meeting     date  sep         est     bst       untracked attendees    fullname  affiliation   optional  github username              agenda      convene   roll call          review and approve         and     meeting minutes    mins       present additional slide on how the dispute will be resolved  sailesh     mins       update on cloud storage options    mins       aob  q a   adjourn           decisions made      decision        decision                  action items      action        action                   webex info           meeting number           join by phone           usa toll          uk toll   access code                ,0
21716,4734184741.0,IssuesEvent,2016-10-19 13:35:34,golang/go,https://api.github.com/repos/golang/go,closed,reflect: DeepEqual treats nil and empty map as not equal,Documentation NeedsFix,"Please answer these questions before submitting your issue. Thanks!

1. What version of Go are you using (`go version`)?
Go tip (be91515)

2. What operating system and processor architecture are you using (`go env`)?
linux/amd64

3. What did you do?
https://play.golang.org/p/S_vq5DdCzu

4. What did you expect to see?
`true`

5. What did you see instead?
`false`

The doc for `reflect.DeepEqual` says:

> Map values are deeply equal if they are the same map object or if they have the same length and their corresponding keys (matched using Go equality) map to deeply equal values.

Empty and nil maps both have a length of zero, so I would expect this to be true.",1.0,"reflect: DeepEqual treats nil and empty map as not equal - Please answer these questions before submitting your issue. Thanks!

1. What version of Go are you using (`go version`)?
Go tip (be91515)

2. What operating system and processor architecture are you using (`go env`)?
linux/amd64

3. What did you do?
https://play.golang.org/p/S_vq5DdCzu

4. What did you expect to see?
`true`

5. What did you see instead?
`false`

The doc for `reflect.DeepEqual` says:

> Map values are deeply equal if they are the same map object or if they have the same length and their corresponding keys (matched using Go equality) map to deeply equal values.

Empty and nil maps both have a length of zero, so I would expect this to be true.",1,reflect  deepequal treats nil and empty map as not equal   please answer these questions before submitting your issue  thanks        what version of go are you using   go version     go tip           what operating system and processor architecture are you using   go env     linux         what did you do           what did you expect to see    true        what did you see instead    false     the doc for  reflect deepequal  says       map values are deeply equal if they are the same map object or if they have the same length and their corresponding keys  matched using go equality  map to deeply equal values     empty and nil maps both have a length of zero  so i would expect this to be true ,1
11044,3454720354.0,IssuesEvent,2015-12-17 17:00:28,golang/go,https://api.github.com/repos/golang/go,closed,"cmd/go: document that ""go get"" never operates on vendor directories",Documentation,"In the docs here:
https://golang.org/cmd/go/#hdr-Vendor_Directories

There is a single section that mentions how the behavior of `go get` changes when the `GO15VENDOREXPERIMENT` env var is enabled:

```
When the vendor experiment is enabled, 'go get' 
checks out submodules when checking out or 
updating a git repository (see 'go help get').
```

A source of confusion and many questions (twitter, slack) results from the assumption that running `go get` with the flag enabled will place downloaded packages into a `vendor` directory, which is not the case. A sentence or two added to the documentation would help:

```
When the vendor experiment is enabled, 'go get' 
checks out submodules when checking out or 
updating a git repository (see 'go help get'). 
The storage location of downloaded packages 
does not change with the experiment enabled; 
'go get' will not place retrieved packages into a
'vendor' directory. 
```

Is it possible to update the documentation prior to the next release?

",1.0,"cmd/go: document that ""go get"" never operates on vendor directories - In the docs here:
https://golang.org/cmd/go/#hdr-Vendor_Directories

There is a single section that mentions how the behavior of `go get` changes when the `GO15VENDOREXPERIMENT` env var is enabled:

```
When the vendor experiment is enabled, 'go get' 
checks out submodules when checking out or 
updating a git repository (see 'go help get').
```

A source of confusion and many questions (twitter, slack) results from the assumption that running `go get` with the flag enabled will place downloaded packages into a `vendor` directory, which is not the case. A sentence or two added to the documentation would help:

```
When the vendor experiment is enabled, 'go get' 
checks out submodules when checking out or 
updating a git repository (see 'go help get'). 
The storage location of downloaded packages 
does not change with the experiment enabled; 
'go get' will not place retrieved packages into a
'vendor' directory. 
```

Is it possible to update the documentation prior to the next release?

",1,cmd go  document that  go get  never operates on vendor directories   in the docs here        there is a single section that mentions how the behavior of  go get  changes when the     env var is enabled          when the vendor experiment is enabled   go get    checks out submodules when checking out or   updating a git repository  see  go help get            a source of confusion and many questions  twitter  slack  results from the assumption that running  go get  with the flag enabled will place downloaded packages into a  vendor  directory  which is not the case  a sentence or two added to the documentation would help          when the vendor experiment is enabled   go get    checks out submodules when checking out or   updating a git repository  see  go help get      the storage location of downloaded packages   does not change with the experiment enabled     go get  will not place retrieved packages into a   vendor  directory           is it possible to update the documentation prior to the next release     ,1
10403,4764007087.0,IssuesEvent,2016-10-25 15:50:07,CartoDB/cartodb,https://api.github.com/repos/CartoDB/cartodb,opened,Lack of information about how CartoCSS and legends work,Builder,"It would be great that legends can be generated via scenario 2. But if it is not possible more information (modals, docs...) would be needed to let users be aware of this issue.

### Scenario 1
* You use the wizard to size points and the legend shows up,
* next, you modify the Turbo Carto,
* the legend updates.

### Scenario 2
* You go straight to CartoCSS editor and write Turbo Carto for marker-width,
* you now don’t have the option to add a legend for size.

cc @javisantana @makella ",1.0,"Lack of information about how CartoCSS and legends work - It would be great that legends can be generated via scenario 2. But if it is not possible more information (modals, docs...) would be needed to let users be aware of this issue.

### Scenario 1
* You use the wizard to size points and the legend shows up,
* next, you modify the Turbo Carto,
* the legend updates.

### Scenario 2
* You go straight to CartoCSS editor and write Turbo Carto for marker-width,
* you now don’t have the option to add a legend for size.

cc @javisantana @makella ",0,lack of information about how cartocss and legends work   it would be great that legends can be generated via scenario    but if it is not possible more information  modals  docs     would be needed to let users be aware of this issue         scenario      you use the wizard to size points and the legend shows up     next  you modify the turbo carto     the legend updates         scenario      you go straight to cartocss editor and write turbo carto for marker width     you now don’t have the option to add a legend for size     cc  javisantana  makella ,0
299446,25902955451.0,IssuesEvent,2022-12-15 07:53:21,dotnet/machinelearning-modelbuilder,https://api.github.com/repos/dotnet/machinelearning-modelbuilder,closed,"Value predication: Training failed with model builder error after changing the feature column 's Data type from ""String"" to ""Single"".",Priority:0 Needs Repro Reported by: Test,"**System Information (please complete the following information):**
Windows OS: Windows-11-Enterprise-21H2
ML.Net Model Builder 2022: 16.13.10.2251801 (Main Build)
Microsoft Visual Studio Enterprise: 2022(17.3.6)
.Net: 6.0

**Describe the bug**
- On which step of the process did you run into an issue: 
Training failed with model builder error after changing the feature column 's Data type from ""String"" to ""Single"".

**Data Source**
https://testpass.blob.core.windows.net/test-pass-data/iris.mdf

**To Reproduce**
Steps to reproduce the behavior:

  1. Select Create a new project from the Visual Studio 2022 start window.
  2. Choose the C# Console App (.NET Core6.0) project template.
  3. Add model builder by right click on the project.
  4. Select **Value predication** scenario.
  5. On Data page, select the data source and choose **fare_amount** column as label.
  6. Change **""rate_code"" or ""passenger_count"" or ""trip_distance""** column's Data type from ""String"" to ""Single"".
  7. On the Train page, you will see that training failed with model builder error ""Splitter/consolidator worker encountered exception while consuming source data"".

**Expected behavior**
Training successful.

**Screenshot**
![image](https://user-images.githubusercontent.com/99375895/203674407-d04af336-c434-4f49-972e-23d7db4c7bfc.png)

**Additional context:**",1.0,"Value predication: Training failed with model builder error after changing the feature column 's Data type from ""String"" to ""Single"". - **System Information (please complete the following information):**
Windows OS: Windows-11-Enterprise-21H2
ML.Net Model Builder 2022: 16.13.10.2251801 (Main Build)
Microsoft Visual Studio Enterprise: 2022(17.3.6)
.Net: 6.0

**Describe the bug**
- On which step of the process did you run into an issue: 
Training failed with model builder error after changing the feature column 's Data type from ""String"" to ""Single"".

**Data Source**
https://testpass.blob.core.windows.net/test-pass-data/iris.mdf

**To Reproduce**
Steps to reproduce the behavior:

  1. Select Create a new project from the Visual Studio 2022 start window.
  2. Choose the C# Console App (.NET Core6.0) project template.
  3. Add model builder by right click on the project.
  4. Select **Value predication** scenario.
  5. On Data page, select the data source and choose **fare_amount** column as label.
  6. Change **""rate_code"" or ""passenger_count"" or ""trip_distance""** column's Data type from ""String"" to ""Single"".
  7. On the Train page, you will see that training failed with model builder error ""Splitter/consolidator worker encountered exception while consuming source data"".

**Expected behavior**
Training successful.

**Screenshot**
![image](https://user-images.githubusercontent.com/99375895/203674407-d04af336-c434-4f49-972e-23d7db4c7bfc.png)

**Additional context:**",0,value predication  training failed with model builder error after changing the feature column  s data type from  string  to  single       system information  please complete the following information      windows os  windows   enterprise    ml net model builder             main build   microsoft visual studio enterprise             net           describe the bug      on which step of the process did you run into an issue    training failed with model builder error after changing the feature column  s data type from  string  to  single        data source           to reproduce    steps to reproduce the behavior          select create a new project from the visual studio   start window        choose the c  console app   net      project template        add model builder by right click on the project        select   value predication   scenario        on data page  select the data source and choose   fare amount   column as label        change    rate code  or  passenger count  or  trip distance    column s data type from  string  to  single         on the train page  you will see that training failed with model builder error  splitter consolidator worker encountered exception while consuming source data        expected behavior    training successful       screenshot              additional context   ,0
292159,8953810760.0,IssuesEvent,2019-01-25 20:38:55,zulip/zulip,https://api.github.com/repos/zulip/zulip,closed,import: Improve data import performance with a very large number of users,area: export/import priority: high,"When importing an organization from Slack that had 10K users, we end up spending ~20 minutes (out of 30 minutes total import time!) in the `processing_avatars` block at the end of `import_uploads`, just because serially downloading, resizing, and the re-uploading all of those avatar images is slow.  I'm pretty sure that phase could be several times faster if we were to parallelize it, and the logic is completely separate for each user, so there's no reason we couldn't parallelize it easily.   

We should do that parallelization work, making using of our handy `do_parallel` library.",1.0,"import: Improve data import performance with a very large number of users - When importing an organization from Slack that had 10K users, we end up spending ~20 minutes (out of 30 minutes total import time!) in the `processing_avatars` block at the end of `import_uploads`, just because serially downloading, resizing, and the re-uploading all of those avatar images is slow.  I'm pretty sure that phase could be several times faster if we were to parallelize it, and the logic is completely separate for each user, so there's no reason we couldn't parallelize it easily.   

We should do that parallelization work, making using of our handy `do_parallel` library.",0,import  improve data import performance with a very large number of users   when importing an organization from slack that had   users  we end up spending    minutes  out of   minutes total import time   in the  processing avatars  block at the end of  import uploads   just because serially downloading  resizing  and the re uploading all of those avatar images is slow   i m pretty sure that phase could be several times faster if we were to parallelize it  and the logic is completely separate for each user  so there s no reason we couldn t parallelize it easily        we should do that parallelization work  making using of our handy  do parallel  library ,0
358149,10618383929.0,IssuesEvent,2019-10-13 03:57:32,k8smeetup/website-tasks,https://api.github.com/repos/k8smeetup/website-tasks,closed,/docs/concepts/storage/volume-snapshots.md,lang/zh priority/P0 sync/update version/1.16 welcome,"Source File: [/docs/concepts/storage/volume-snapshots.md](https://github.com/kubernetes/website/blob/release-1.16/content/en/docs/concepts/storage/volume-snapshots.md)

Diff:
Not a git repository
To compare two paths outside a working tree:
usage: git diff [--no-index] <path> <path>
",1.0,"/docs/concepts/storage/volume-snapshots.md - Source File: [/docs/concepts/storage/volume-snapshots.md](https://github.com/kubernetes/website/blob/release-1.16/content/en/docs/concepts/storage/volume-snapshots.md)

Diff:
Not a git repository
To compare two paths outside a working tree:
usage: git diff [--no-index] <path> <path>
",0, docs concepts storage volume snapshots md   source file       diff  not a git repository to compare two paths outside a working tree  usage  git diff       ,0
196821,6949699786.0,IssuesEvent,2017-12-06 07:53:50,capnkirok/animania,https://api.github.com/repos/capnkirok/animania,closed,(SUGGESTION)gestation ticks,1.10.2 1.11.2 1.12 enhancement priority: low,"-Maybe how the time that they have a baby can be different between species (cows,pigs ) this will be more when there is more animals .
-also a way to be able to tell if they will have a baby so if they are bred.
-so basically a way to keep up age  bred just normal stats we keep on animals

Love the mod so far I was just saying this as a suggestion since irl they have different times(tho if they do change does not really have to change to be near irl times tho)

-this Mod is so awesome -",1.0,"(SUGGESTION)gestation ticks - -Maybe how the time that they have a baby can be different between species (cows,pigs ) this will be more when there is more animals .
-also a way to be able to tell if they will have a baby so if they are bred.
-so basically a way to keep up age  bred just normal stats we keep on animals

Love the mod so far I was just saying this as a suggestion since irl they have different times(tho if they do change does not really have to change to be near irl times tho)

-this Mod is so awesome -",0, suggestion gestation ticks    maybe how the time that they have a baby can be different between species  cows pigs   this will be more when there is more animals     also a way to be able to tell if they will have a baby so if they are bred    so basically a way to keep up age  bred just normal stats we keep on animals    love the mod so far i was just saying this as a suggestion since irl they have different times tho if they do change does not really have to change to be near irl times tho      this mod is so awesome  ,0
7601,3105002971.0,IssuesEvent,2015-08-31 18:44:38,golang/go,https://api.github.com/repos/golang/go,closed,fmt: example format for %e and %E float verbs is incorrect,Documentation,"From http://golang.org/pkg/fmt/:

    %e	scientific notation, e.g. -1234.456e+78
    %E	scientific notation, e.g. -1234.456E+78

while it should be (one non-zero digit before decimal point):

    %e	scientific notation, e.g. -1.234567e+78
    %E	scientific notation, e.g. -1.234567E+78

http://play.golang.org/p/llGQ0mAT73
",1.0,"fmt: example format for %e and %E float verbs is incorrect - From http://golang.org/pkg/fmt/:

    %e	scientific notation, e.g. -1234.456e+78
    %E	scientific notation, e.g. -1234.456E+78

while it should be (one non-zero digit before decimal point):

    %e	scientific notation, e.g. -1.234567e+78
    %E	scientific notation, e.g. -1.234567E+78

http://play.golang.org/p/llGQ0mAT73
",1,fmt  example format for  e and  e float verbs is incorrect   from           e	scientific notation  e g               e	scientific notation  e g            while it should be  one non zero digit before decimal point           e	scientific notation  e g               e	scientific notation  e g               ,1
23851,23037553157.0,IssuesEvent,2022-07-22 20:47:10,DataBiosphere/toil,https://api.github.com/repos/DataBiosphere/toil,closed,Toil WES support change workflow_params to be optional,usability,"When launching a workflow using a Toil WES server, the `workflow_params` (input JSON file) is required, even if the workflow itself takes no inputs. Not including the `workflow_params` body part in the HTTP request causes the WEs server to return an error:
```
io.openapi.wes.client.ApiException: {
  ""msg"": ""Missing 'workflow_params' in submission"",
  ""status_code"": 400
}
```

Ideally, this parameter should be optional, to allow easy launching of input parameter-free workflows. This is pretty easy to work around though, as passing in a dummy test parameter file suppresses the exception.

┆Issue is synchronized with this [Jira Story](https://ucsc-cgl.atlassian.net/browse/TOIL-1143)
┆friendlyId: TOIL-1143
",True,"Toil WES support change workflow_params to be optional - When launching a workflow using a Toil WES server, the `workflow_params` (input JSON file) is required, even if the workflow itself takes no inputs. Not including the `workflow_params` body part in the HTTP request causes the WEs server to return an error:
```
io.openapi.wes.client.ApiException: {
  ""msg"": ""Missing 'workflow_params' in submission"",
  ""status_code"": 400
}
```

Ideally, this parameter should be optional, to allow easy launching of input parameter-free workflows. This is pretty easy to work around though, as passing in a dummy test parameter file suppresses the exception.

┆Issue is synchronized with this [Jira Story](https://ucsc-cgl.atlassian.net/browse/TOIL-1143)
┆friendlyId: TOIL-1143
",0,toil wes support change workflow params to be optional   when launching a workflow using a toil wes server  the  workflow params   input json file  is required  even if the workflow itself takes no inputs  not including the  workflow params  body part in the http request causes the wes server to return an error      io openapi wes client apiexception       msg    missing  workflow params  in submission      status code            ideally  this parameter should be optional  to allow easy launching of input parameter free workflows  this is pretty easy to work around though  as passing in a dummy test parameter file suppresses the exception   ┆issue is synchronized with this     ┆friendlyid  toil   ,0
47699,19700443461.0,IssuesEvent,2022-01-12 16:08:38,cityofaustin/atd-data-tech,https://api.github.com/repos/cityofaustin/atd-data-tech,closed,SZB Discussion with Charles,Workgroup: AMD Service: Geo Type: Communication,Charles called me to ask about the SZB Web Map that they used to verify the SZB data.,1.0,SZB Discussion with Charles - Charles called me to ask about the SZB Web Map that they used to verify the SZB data.,0,szb discussion with charles   charles called me to ask about the szb web map that they used to verify the szb data ,0
28663,5530434699.0,IssuesEvent,2017-03-21 02:34:14,golang/go,https://api.github.com/repos/golang/go,closed,doc: source install page should mention make.bash again,Documentation,"Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
None installed yet (1.4 bootstrap)

### What operating system and processor architecture are you using (`go env`)?
OSX 10.11.6

### What did you do?
Try to build 1.4 bootstrap installation

### What did you expect to see?
Successful build

### What did you see instead?
Build produces some files including a go binary but fails during tests -
# Testing packages.
ok  	cmd/addr2line	0.765s
...
ok  	unicode/utf16	0.005s
ok  	unicode/utf8	0.009s
?   	unsafe	[no test files]
% echo $?
1
% 

I tried to cobble together the resulting binary and packages into a GOROOT that could build 1.7.4 but unsurprisingly came up short. In any case the 1.4 build should work correctly.",1.0,"doc: source install page should mention make.bash again - Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
None installed yet (1.4 bootstrap)

### What operating system and processor architecture are you using (`go env`)?
OSX 10.11.6

### What did you do?
Try to build 1.4 bootstrap installation

### What did you expect to see?
Successful build

### What did you see instead?
Build produces some files including a go binary but fails during tests -
# Testing packages.
ok  	cmd/addr2line	0.765s
...
ok  	unicode/utf16	0.005s
ok  	unicode/utf8	0.009s
?   	unsafe	[no test files]
% echo $?
1
% 

I tried to cobble together the resulting binary and packages into a GOROOT that could build 1.7.4 but unsurprisingly came up short. In any case the 1.4 build should work correctly.",1,doc  source install page should mention make bash again   please answer these questions before submitting your issue  thanks         what version of go are you using   go version     none installed yet      bootstrap         what operating system and processor architecture are you using   go env     osx              what did you do   try to build     bootstrap installation        what did you expect to see   successful build        what did you see instead   build produces some files including a go binary but fails during tests      testing packages   ok  	cmd  	          ok  	unicode  	     ok  	unicode  	         	unsafe	     echo              i tried to cobble together the resulting binary and packages into a goroot that could build       but unsurprisingly came up short  in any case the     build should work correctly ,1
36174,6517982771.0,IssuesEvent,2017-08-28 05:12:23,golang/go,https://api.github.com/repos/golang/go,closed,fmt: improve documentation about how verbs work when printing pointers,Documentation NeedsDecision,"Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?

go1.9rc2 linux/amd64

### What operating system and processor architecture are you using (`go env`)?

GOHOSTARCH=""amd64""
GOHOSTOS=""linux""

### What did you do?

https://play.golang.org/p/k89vjAT5Kt

package main

import (
	""fmt""
)

func main() {
	i := 37
	p := &i
	fmt.Printf(""Why: %d"", p)
}

### What did you expect to see?

I expected to see some sort of error / warning about the implicit conversion of a pointer type into an integer format verb %d. I expected the computer to help me catch the mistake of not derefrencing p to get the expected integer.

### What did you see instead?

No error or warning, and the output contains the address of the pointer printed in base10.


",1.0,"fmt: improve documentation about how verbs work when printing pointers - Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?

go1.9rc2 linux/amd64

### What operating system and processor architecture are you using (`go env`)?

GOHOSTARCH=""amd64""
GOHOSTOS=""linux""

### What did you do?

https://play.golang.org/p/k89vjAT5Kt

package main

import (
	""fmt""
)

func main() {
	i := 37
	p := &i
	fmt.Printf(""Why: %d"", p)
}

### What did you expect to see?

I expected to see some sort of error / warning about the implicit conversion of a pointer type into an integer format verb %d. I expected the computer to help me catch the mistake of not derefrencing p to get the expected integer.

### What did you see instead?

No error or warning, and the output contains the address of the pointer printed in base10.


",1,fmt  improve documentation about how verbs work when printing pointers   please answer these questions before submitting your issue  thanks         what version of go are you using   go version           linux          what operating system and processor architecture are you using   go env       gohostarch      gohostos  linux         what did you do          package main    import    	 fmt        func main      	i       	p     i  	fmt printf  why   d   p            what did you expect to see     i expected to see some sort of error   warning about the implicit conversion of a pointer type into an integer format verb  d  i expected the computer to help me catch the mistake of not derefrencing p to get the expected integer         what did you see instead     no error or warning  and the output contains the address of the pointer printed in         ,1
205532,15630908486.0,IssuesEvent,2021-03-22 03:26:11,Slimefun/Slimefun4,https://api.github.com/repos/Slimefun/Slimefun4,closed,Android BlockHandler Duplication,🎯 Needs testing 🐞 Bug Report,"<!-- FILL IN THE FORM BELOW -->

## :round_pushpin: Description (REQUIRED)
<!-- A clear and detailed description of what went wrong. -->
<!-- The more information you can provide, the easier we can handle this problem. -->
<!-- Start writing below this line -->
Upon breaking an android with an Explosive Pickaxe, an error appears in the console along with it duplicating the android.
 This works for every single android, and purely only androids.

## :bookmark_tabs: Steps to reproduce the Issue (REQUIRED)
<!-- Tell us the exact steps to reproduce this issue, the more detailed the easier we can reproduce it. -->
<!-- Youtube Videos and Screenshots are recommended!!! -->
<!-- Start writing below this line -->
1. Place down an android of your choice.
2. Break it with an Explosive Pickaxe.

## :bulb: Expected behavior (REQUIRED)
<!-- What were you expecting to happen? -->
<!-- What do you think would have been the correct behaviour? -->
<!-- Start writing below this line -->
Drop the proper android amount without throwing an error.

## :scroll: Server Log
<!-- Take a look at your Server Log and post any errors you can find via https://pastebin.com/ -->
<!-- If you are unsure about it, post your full log, you can find it under /logs/latest.log -->
<!-- Paste your link(s) below this line -->
1. https://pastebin.com/ETAhQTj8
2. https://pastebin.com/UdLSSy8b

## :open_file_folder: /error-reports/ Folder
<!-- Check the folder /plugins/Slimefun/error-reports/ and upload any files inside that folder. -->
<!-- You can also post these files via https://pastebin.com/ -->
<!-- Paste your link(s) below this line -->
None that correspond to the date.

## :compass: Environment (REQUIRED)
<!-- Any issue without the exact version numbers will be closed! -->
<!-- ""latest"" IS NOT A VERSION NUMBER. -->
<!-- We recommend running ""/sf versions"" and showing us a screenshot of that. -->
<!-- Make sure that the screenshot covers the entire output of that command. -->
<!-- If your issue is related to other plugins, make sure to include the versions of these plugins too! -->

![Capture](https://user-images.githubusercontent.com/16171807/111875613-1ade0600-8971-11eb-9f61-1c3aa05125d6.PNG)
",1.0,"Android BlockHandler Duplication - <!-- FILL IN THE FORM BELOW -->

## :round_pushpin: Description (REQUIRED)
<!-- A clear and detailed description of what went wrong. -->
<!-- The more information you can provide, the easier we can handle this problem. -->
<!-- Start writing below this line -->
Upon breaking an android with an Explosive Pickaxe, an error appears in the console along with it duplicating the android.
 This works for every single android, and purely only androids.

## :bookmark_tabs: Steps to reproduce the Issue (REQUIRED)
<!-- Tell us the exact steps to reproduce this issue, the more detailed the easier we can reproduce it. -->
<!-- Youtube Videos and Screenshots are recommended!!! -->
<!-- Start writing below this line -->
1. Place down an android of your choice.
2. Break it with an Explosive Pickaxe.

## :bulb: Expected behavior (REQUIRED)
<!-- What were you expecting to happen? -->
<!-- What do you think would have been the correct behaviour? -->
<!-- Start writing below this line -->
Drop the proper android amount without throwing an error.

## :scroll: Server Log
<!-- Take a look at your Server Log and post any errors you can find via https://pastebin.com/ -->
<!-- If you are unsure about it, post your full log, you can find it under /logs/latest.log -->
<!-- Paste your link(s) below this line -->
1. https://pastebin.com/ETAhQTj8
2. https://pastebin.com/UdLSSy8b

## :open_file_folder: /error-reports/ Folder
<!-- Check the folder /plugins/Slimefun/error-reports/ and upload any files inside that folder. -->
<!-- You can also post these files via https://pastebin.com/ -->
<!-- Paste your link(s) below this line -->
None that correspond to the date.

## :compass: Environment (REQUIRED)
<!-- Any issue without the exact version numbers will be closed! -->
<!-- ""latest"" IS NOT A VERSION NUMBER. -->
<!-- We recommend running ""/sf versions"" and showing us a screenshot of that. -->
<!-- Make sure that the screenshot covers the entire output of that command. -->
<!-- If your issue is related to other plugins, make sure to include the versions of these plugins too! -->

![Capture](https://user-images.githubusercontent.com/16171807/111875613-1ade0600-8971-11eb-9f61-1c3aa05125d6.PNG)
",0,android blockhandler duplication            round pushpin  description  required            upon breaking an android with an explosive pickaxe  an error appears in the console along with it duplicating the android    this works for every single android  and purely only androids         bookmark tabs  steps to reproduce the issue  required               place down an android of your choice      break it with an explosive pickaxe         bulb  expected behavior  required            drop the proper android amount without throwing an error         scroll  server log                             open file folder   error reports  folder           none that correspond to the date         compass  environment  required                          ,0
311095,26767802208.0,IssuesEvent,2023-01-31 11:58:54,hashicorp/terraform-provider-google,https://api.github.com/repos/hashicorp/terraform-provider-google,opened,Failing test(s): TestAccComputeInstanceTemplate_sourceSnapshotEncryptionKey,test failure,"<!--- This is a template for reporting test failures on nightly builds. It should only be used by core contributors who have access to our CI/CD results. --->

<!-- i.e. ""Consistently since X date"" or ""X% failure in MONTH"" -->
Failure rate: 29% failure in Jan '23

<!-- List all impacted tests for searchability. The title of the issue can instead list one or more groups of tests, or describe the overall root cause. -->
Impacted tests:
- TestAccComputeInstanceTemplate_sourceSnapshotEncryptionKey

<!-- Link to the nightly build(s), ideally with one impacted test opened -->
Nightly builds:
- [Link](https://ci-oss.hashicorp.engineering/test/-4109935072844408801?currentProjectId=GoogleCloud&branch=%3Cdefault%3E&testTab=overview&expandedTest=id%3A439733%2Cbuild%3A%28id%3A371260%29&showLog=371260_439733_427256.427267.439733&logFilter=debug)

<!-- The error message that displays in the tests tab, for reference -->
Message:

```
Error: Error creating Snapshot: googleapi: Error 400: Cloud KMS error when using key projects/PROJECT_ID/locations/us-central1/keyRings/tftest-shared-keyring-1/cryptoKeys/tftest-shared-key-1: Permission 'cloudkms.cryptoKeyVersions.useToEncrypt' denied on resource 'projects/PROJECT_ID/locations/us-central1/keyRings/tftest-shared-keyring-1/cryptoKeys/tftest-shared-key-1' (or it may not exist)., kmsPermissionDenied
```
",1.0,"Failing test(s): TestAccComputeInstanceTemplate_sourceSnapshotEncryptionKey - <!--- This is a template for reporting test failures on nightly builds. It should only be used by core contributors who have access to our CI/CD results. --->

<!-- i.e. ""Consistently since X date"" or ""X% failure in MONTH"" -->
Failure rate: 29% failure in Jan '23

<!-- List all impacted tests for searchability. The title of the issue can instead list one or more groups of tests, or describe the overall root cause. -->
Impacted tests:
- TestAccComputeInstanceTemplate_sourceSnapshotEncryptionKey

<!-- Link to the nightly build(s), ideally with one impacted test opened -->
Nightly builds:
- [Link](https://ci-oss.hashicorp.engineering/test/-4109935072844408801?currentProjectId=GoogleCloud&branch=%3Cdefault%3E&testTab=overview&expandedTest=id%3A439733%2Cbuild%3A%28id%3A371260%29&showLog=371260_439733_427256.427267.439733&logFilter=debug)

<!-- The error message that displays in the tests tab, for reference -->
Message:

```
Error: Error creating Snapshot: googleapi: Error 400: Cloud KMS error when using key projects/PROJECT_ID/locations/us-central1/keyRings/tftest-shared-keyring-1/cryptoKeys/tftest-shared-key-1: Permission 'cloudkms.cryptoKeyVersions.useToEncrypt' denied on resource 'projects/PROJECT_ID/locations/us-central1/keyRings/tftest-shared-keyring-1/cryptoKeys/tftest-shared-key-1' (or it may not exist)., kmsPermissionDenied
```
",0,failing test s   testacccomputeinstancetemplate sourcesnapshotencryptionkey           failure rate     failure in jan          impacted tests     testacccomputeinstancetemplate sourcesnapshotencryptionkey       nightly builds               message          error  error creating snapshot  googleapi  error    cloud kms error when using key projects project id locations us   keyrings tftest shared keyring   cryptokeys tftest shared key    permission  cloudkms cryptokeyversions usetoencrypt  denied on resource  projects project id locations us   keyrings tftest shared keyring   cryptokeys tftest shared key     or it may not exist    kmspermissiondenied       ,0
39209,6730303586.0,IssuesEvent,2017-10-18 00:01:21,golang/go,https://api.github.com/repos/golang/go,closed,"spec: document package unsafe's path is ""unsafe""",Documentation NeedsFix,"The Go spec mentions package unsafe's package name is `unsafe`, but it never documents the package path that users can import to use it. Intuitively it's `""unsafe""`, but as package paths are formally distinct from package names, we should still explicitly document that.",1.0,"spec: document package unsafe's path is ""unsafe"" - The Go spec mentions package unsafe's package name is `unsafe`, but it never documents the package path that users can import to use it. Intuitively it's `""unsafe""`, but as package paths are formally distinct from package names, we should still explicitly document that.",1,spec  document package unsafe s path is  unsafe    the go spec mentions package unsafe s package name is  unsafe   but it never documents the package path that users can import to use it  intuitively it s   unsafe    but as package paths are formally distinct from package names  we should still explicitly document that ,1
704510,24199172740.0,IssuesEvent,2022-09-24 09:59:34,vocascan/vocascan-frontend,https://api.github.com/repos/vocascan/vocascan-frontend,opened,Individual Learning,kind/enhancement kind/ui priority/low,"<!-- describe the feature you would like to have -->

Add the functionality to make custom queries that don't count to your daily query progress. You should be able to select specific groups and create a vocab query whenever you want
",1.0,"Individual Learning - <!-- describe the feature you would like to have -->

Add the functionality to make custom queries that don't count to your daily query progress. You should be able to select specific groups and create a vocab query whenever you want
",0,individual learning        add the functionality to make custom queries that don t count to your daily query progress  you should be able to select specific groups and create a vocab query whenever you want  ,0
43197,7031691134.0,IssuesEvent,2017-12-26 19:51:53,golang/go,https://api.github.com/repos/golang/go,closed,tools/present: Documentation link to sam documentation is dead,Documentation,"The documentation for the [`tools/present` tool](https://godoc.org/golang.org/x/tools/present) includes a link to http://plan9.bell-labs.com/sys/doc/sam/sam.html, which according to me and according to http://downforeveryoneorjustme.com/plan9.bell-labs.com cannot be reached.

This means it's hard to find out how the `.code` _address syntax_ works.",1.0,"tools/present: Documentation link to sam documentation is dead - The documentation for the [`tools/present` tool](https://godoc.org/golang.org/x/tools/present) includes a link to http://plan9.bell-labs.com/sys/doc/sam/sam.html, which according to me and according to http://downforeveryoneorjustme.com/plan9.bell-labs.com cannot be reached.

This means it's hard to find out how the `.code` _address syntax_ works.",1,tools present  documentation link to sam documentation is dead   the documentation for the     includes a link to   which according to me and according to   cannot be reached     this means it s hard to find out how the   code   address syntax  works ,1
154672,13563689433.0,IssuesEvent,2020-09-18 08:55:44,golang/go,https://api.github.com/repos/golang/go,closed,"""func (*Resolver) LookupIP"" seems not exists, but it is in the documentation",Documentation,"### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14.6 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
<pre>
package main
import ""context""
import ""net""
func GoogleDNSDialer(ctx context.Context, network, address string) (net.Conn, error) {
   d := net.Dialer{}
   return d.DialContext(ctx, ""udp"", ""8.8.8.8:53"")
}
var local_resolver net.Resolver = net.Resolver{
   Dial: GoogleDNSDialer,
}
func LocalLookupIP(name string) ([]net.IP, error) {
   return local_resolver.LookupIP(context.Background(), ""ip"", name)
}
</pre>

<pre>
go build
</pre>
### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env

GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/thierryfournier/Library/Caches/go-build""
GOENV=""/Users/thierryfournier/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/thierryfournier/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/_d/zs7l5ldx1r94fn_qh1zvn1rw0000gn/T/go-build235743352=/tmp/go-build -gno-record-gcc-switches -fno-common""


</pre></details>

### What did you do?
Compilation error is:

./a.go:12:25: local_resolver.LookupIP undefined (type net.Resolver has no field or method LookupIP)

But the documentation says that the function ""func (*Resolver) LookupIP"" exists:
https://godoc.org/net#Resolver.LookupIP

I check the file ""/usr/local/go/src/net/lookup.go"" and the function doesn't exists

### What did you expect to see?
My build works (or fix the documentation).

### What did you see instead?
",1.0,"""func (*Resolver) LookupIP"" seems not exists, but it is in the documentation - ### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14.6 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
<pre>
package main
import ""context""
import ""net""
func GoogleDNSDialer(ctx context.Context, network, address string) (net.Conn, error) {
   d := net.Dialer{}
   return d.DialContext(ctx, ""udp"", ""8.8.8.8:53"")
}
var local_resolver net.Resolver = net.Resolver{
   Dial: GoogleDNSDialer,
}
func LocalLookupIP(name string) ([]net.IP, error) {
   return local_resolver.LookupIP(context.Background(), ""ip"", name)
}
</pre>

<pre>
go build
</pre>
### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env

GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/thierryfournier/Library/Caches/go-build""
GOENV=""/Users/thierryfournier/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/thierryfournier/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/_d/zs7l5ldx1r94fn_qh1zvn1rw0000gn/T/go-build235743352=/tmp/go-build -gno-record-gcc-switches -fno-common""


</pre></details>

### What did you do?
Compilation error is:

./a.go:12:25: local_resolver.LookupIP undefined (type net.Resolver has no field or method LookupIP)

But the documentation says that the function ""func (*Resolver) LookupIP"" exists:
https://godoc.org/net#Resolver.LookupIP

I check the file ""/usr/local/go/src/net/lookup.go"" and the function doesn't exists

### What did you expect to see?
My build works (or fix the documentation).

### What did you see instead?
",1, func   resolver  lookupip  seems not exists  but it is in the documentation       what version of go are you using   go version            go version  go version       darwin             does this issue reproduce with the latest release      package main  import  context   import  net   func googlednsdialer ctx context context  network  address string   net conn  error        d    net dialer       return d dialcontext ctx   udp                    var local resolver net resolver   net resolver      dial  googlednsdialer      func locallookupip name string    net ip  error        return local resolver lookupip context background     ip   name              go build         what operating system and processor architecture are you using   go env          go env  output       go env          goarch      gobin     gocache   users thierryfournier library caches go build   goenv   users thierryfournier library application support go env   goexe     goflags     gohostarch      gohostos  darwin   goinsecure     gonoproxy     gonosumdb     goos  darwin   gopath   users thierryfournier go   goprivate     goproxy     goroot   usr local go   gosumdb  sum golang org   gotmpdir     gotooldir   usr local go pkg tool darwin     gccgo  gccgo   ar  ar   cc  clang   cxx  clang     cgo enabled      gomod     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders  d     t go    tmp go build  gno record gcc switches  fno common                 what did you do   compilation error is       a go      local resolver lookupip undefined  type net resolver has no field or method lookupip     but the documentation says that the function  func   resolver  lookupip  exists        i check the file   usr local go src net lookup go  and the function doesn t exists        what did you expect to see   my build works  or fix the documentation          what did you see instead   ,1
129734,12417791898.0,IssuesEvent,2020-05-22 21:41:29,golang/go,https://api.github.com/repos/golang/go,opened,go/printer: CommentedNode behavior is partially undocumented,Documentation NeedsInvestigation,"### What did you do?

I read the documentation of package `go/printer` in order to understand how to use `printer.CommentedNode`.

### What did you expect to see?

Documentation that would allow me to learn an answer to the question of ""what happens to comments that are already a part of the `Node` being wrapped in a `printer.CommentedNode`?"" without having to also read the source code.

### What did you see instead?

Insufficient documentation to know what the behavior is.

`CommentedNode` is currently defined as:

```Go
// A CommentedNode bundles an AST node and corresponding comments.
// It may be provided as argument to any of the Fprint functions.
//
type CommentedNode struct {
	Node     interface{} // *ast.File, or ast.Expr, ast.Decl, ast.Spec, or ast.Stmt
	Comments []*ast.CommentGroup
}
```

It is also mentioned in the documentation of the `Config.Fprint` method:

```Go
// Fprint ""pretty-prints"" an AST node to output for a given configuration cfg.
// Position information is interpreted relative to the file set fset.
// The node type must be *ast.File, *CommentedNode, []ast.Decl, []ast.Stmt,
// or assignment-compatible to ast.Expr, ast.Decl, ast.Spec, or ast.Stmt.
//
func (cfg *Config) Fprint(output io.Writer, fset *token.FileSet, node interface{}) error
```

As well as the `format.Node` function, but there isn't additional relevant information there.

/cc @griesemer @josharian",1.0,"go/printer: CommentedNode behavior is partially undocumented - ### What did you do?

I read the documentation of package `go/printer` in order to understand how to use `printer.CommentedNode`.

### What did you expect to see?

Documentation that would allow me to learn an answer to the question of ""what happens to comments that are already a part of the `Node` being wrapped in a `printer.CommentedNode`?"" without having to also read the source code.

### What did you see instead?

Insufficient documentation to know what the behavior is.

`CommentedNode` is currently defined as:

```Go
// A CommentedNode bundles an AST node and corresponding comments.
// It may be provided as argument to any of the Fprint functions.
//
type CommentedNode struct {
	Node     interface{} // *ast.File, or ast.Expr, ast.Decl, ast.Spec, or ast.Stmt
	Comments []*ast.CommentGroup
}
```

It is also mentioned in the documentation of the `Config.Fprint` method:

```Go
// Fprint ""pretty-prints"" an AST node to output for a given configuration cfg.
// Position information is interpreted relative to the file set fset.
// The node type must be *ast.File, *CommentedNode, []ast.Decl, []ast.Stmt,
// or assignment-compatible to ast.Expr, ast.Decl, ast.Spec, or ast.Stmt.
//
func (cfg *Config) Fprint(output io.Writer, fset *token.FileSet, node interface{}) error
```

As well as the `format.Node` function, but there isn't additional relevant information there.

/cc @griesemer @josharian",1,go printer  commentednode behavior is partially undocumented       what did you do     i read the documentation of package  go printer  in order to understand how to use  printer commentednode          what did you expect to see     documentation that would allow me to learn an answer to the question of  what happens to comments that are already a part of the  node  being wrapped in a  printer commentednode    without having to also read the source code         what did you see instead     insufficient documentation to know what the behavior is      commentednode  is currently defined as        go     a commentednode bundles an ast node and corresponding comments      it may be provided as argument to any of the fprint functions       type commentednode struct    	node     interface       ast file  or ast expr  ast decl  ast spec  or ast stmt  	comments   ast commentgroup            it is also mentioned in the documentation of the  config fprint  method        go     fprint  pretty prints  an ast node to output for a given configuration cfg      position information is interpreted relative to the file set fset      the node type must be  ast file   commentednode   ast decl   ast stmt      or assignment compatible to ast expr  ast decl  ast spec  or ast stmt       func  cfg  config  fprint output io writer  fset  token fileset  node interface    error         as well as the  format node  function  but there isn t additional relevant information there      cc  griesemer  josharian,1
15125,3926470838.0,IssuesEvent,2016-04-23 00:01:43,golang/go,https://api.github.com/repos/golang/go,closed,doc: add link to security@golang.org from https://golang.org/doc/contribute.html,Documentation,"CONTRIBUTING.md points to security@golang.org

> Sensitive security-related issues should be reported to security@golang.org.

but the [Contribution Guidelines](https://golang.org/doc/contribute.html) does not.",1.0,"doc: add link to security@golang.org from https://golang.org/doc/contribute.html - CONTRIBUTING.md points to security@golang.org

> Sensitive security-related issues should be reported to security@golang.org.

but the [Contribution Guidelines](https://golang.org/doc/contribute.html) does not.",1,doc  add link to security golang org from     contributing md points to security golang org      sensitive security related issues should be reported to security golang org     but the     does not ,1
793886,28014643053.0,IssuesEvent,2023-03-27 21:27:03,Greenstand/treetracker-admin-client,https://api.github.com/repos/Greenstand/treetracker-admin-client,closed,Verify: Grower map link on capture card uses incorrect URL,type: bug tool: Verify priority size: small Hackathon,"_Version: 1.108.0_

## Steps to Reproduce
1. Open Verify tool
2. Click the map icon at the bottom of a capture card
3. Web map opens but does not show grower's captures (UUID in URL)

## Expected Behaviour
Web map opens and shows grower's captures",1.0,"Verify: Grower map link on capture card uses incorrect URL - _Version: 1.108.0_

## Steps to Reproduce
1. Open Verify tool
2. Click the map icon at the bottom of a capture card
3. Web map opens but does not show grower's captures (UUID in URL)

## Expected Behaviour
Web map opens and shows grower's captures",0,verify  grower map link on capture card uses incorrect url    version               steps to reproduce     open verify tool     click the map icon at the bottom of a capture card     web map opens but does not show grower s captures  uuid in url        expected behaviour  web map opens and shows grower s captures,0
22078,4771761463.0,IssuesEvent,2016-10-26 18:55:03,golang/go,https://api.github.com/repos/golang/go,opened,net: no docs about the behavior of announcing or listening on IP dual stack,Documentation,"I asked several times on golang-nuts, golang-dev or golang-codereviews like the following:
https://groups.google.com/d/msg/golang-dev/MvAlef3CTqk/DGs5sLBcCgAJ
",1.0,"net: no docs about the behavior of announcing or listening on IP dual stack - I asked several times on golang-nuts, golang-dev or golang-codereviews like the following:
https://groups.google.com/d/msg/golang-dev/MvAlef3CTqk/DGs5sLBcCgAJ
",1,net  no docs about the behavior of announcing or listening on ip dual stack   i asked several times on golang nuts  golang dev or golang codereviews like the following      ,1
31714,5987743688.0,IssuesEvent,2017-06-02 01:04:02,golang/go,https://api.github.com/repos/golang/go,closed,compress/gzip: Close() documentation is incomplete,Documentation,"( Originally noted running Go 1.8.3 locally on MacOS Sierra 10.12.5.
Looking at current on-line documentation at golang.org/pkg/compress/gzip. )

The documentation of Close() method of gzip.Writer says that it flushes any unwritten data and implies that it does nothing more.  That's not quite correct.  Critically, it also writes a termination sequence to the output file.  Without this, the corresponding Reader will return an ""unexpected EOF"" error.

I think that's a significant omission.  From the documentation I concluded that Flush and Close were equivalent, and I initially chose the wrong one.

Sample test program:
https://play.golang.org/p/zPOjLCAttg

The same situation also exists in the very similar compress/zlib package.

",1.0,"compress/gzip: Close() documentation is incomplete - ( Originally noted running Go 1.8.3 locally on MacOS Sierra 10.12.5.
Looking at current on-line documentation at golang.org/pkg/compress/gzip. )

The documentation of Close() method of gzip.Writer says that it flushes any unwritten data and implies that it does nothing more.  That's not quite correct.  Critically, it also writes a termination sequence to the output file.  Without this, the corresponding Reader will return an ""unexpected EOF"" error.

I think that's a significant omission.  From the documentation I concluded that Flush and Close were equivalent, and I initially chose the wrong one.

Sample test program:
https://play.golang.org/p/zPOjLCAttg

The same situation also exists in the very similar compress/zlib package.

",1,compress gzip  close   documentation is incomplete     originally noted running go       locally on macos sierra         looking at current on line documentation at golang org pkg compress gzip       the documentation of close   method of gzip writer says that it flushes any unwritten data and implies that it does nothing more   that s not quite correct   critically  it also writes a termination sequence to the output file   without this  the corresponding reader will return an  unexpected eof  error     i think that s a significant omission   from the documentation i concluded that flush and close were equivalent  and i initially chose the wrong one     sample test program        the same situation also exists in the very similar compress zlib package     ,1
65237,8793841783.0,IssuesEvent,2018-12-21 21:47:30,golang/go,https://api.github.com/repos/golang/go,closed,ref/mem: misleading sentence in sync.Once example,Documentation NeedsFix,"### What version of Go are you using (`go version`)?

1.11/playground

### Does this issue reproduce with the latest release?

yes

### What operating system and processor architecture are you using (`go env`)?

linux/amd64, playground

### What did you do?

https://play.golang.org/p/w-CNHDQAGW-

### What did you expect to see?

according to ref/mem as written, ""1\n1 hello, 1\n2\n 2 hello 1\n""

### What did you see instead?

the other way around

Observation: There's two things here that I think are potentially misleading, although both are sort of trivial. The first is that, according to the ""goroutine destruction"" section, there's no guarantee that *anything* gets printed, because nothing is waiting on these, and indeed, without the extra channel operations, nothing happens.

The second is the distinction between ""the first call to doprint()"", ""the first call to doprint() which actually starts execution"", and ""the first call to doprint() which actually begins the once.Do() call"". While in the trivial example, probably the first call to start executing will win that, it's not generally a given that two goroutines acting in parallel will always complete in the same order they start, even running identical code. But in particular, it's definitely not guaranteed that the ""first call"" will start executing first.

I'm fine with handwaving the synchronization thing, but I think the wording on ""the first call"" might benefit from cleaning up. Proposed wording:

The first call to `doprint()` to begin executing the `once.Do()` calls `setup()`, any calls that reach that point later do not, regardless of the order in which the goroutines are invoked or begin executing.",1.0,"ref/mem: misleading sentence in sync.Once example - ### What version of Go are you using (`go version`)?

1.11/playground

### Does this issue reproduce with the latest release?

yes

### What operating system and processor architecture are you using (`go env`)?

linux/amd64, playground

### What did you do?

https://play.golang.org/p/w-CNHDQAGW-

### What did you expect to see?

according to ref/mem as written, ""1\n1 hello, 1\n2\n 2 hello 1\n""

### What did you see instead?

the other way around

Observation: There's two things here that I think are potentially misleading, although both are sort of trivial. The first is that, according to the ""goroutine destruction"" section, there's no guarantee that *anything* gets printed, because nothing is waiting on these, and indeed, without the extra channel operations, nothing happens.

The second is the distinction between ""the first call to doprint()"", ""the first call to doprint() which actually starts execution"", and ""the first call to doprint() which actually begins the once.Do() call"". While in the trivial example, probably the first call to start executing will win that, it's not generally a given that two goroutines acting in parallel will always complete in the same order they start, even running identical code. But in particular, it's definitely not guaranteed that the ""first call"" will start executing first.

I'm fine with handwaving the synchronization thing, but I think the wording on ""the first call"" might benefit from cleaning up. Proposed wording:

The first call to `doprint()` to begin executing the `once.Do()` calls `setup()`, any calls that reach that point later do not, regardless of the order in which the goroutines are invoked or begin executing.",1,ref mem  misleading sentence in sync once example       what version of go are you using   go version           playground        does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env       linux    playground        what did you do              what did you expect to see     according to ref mem as written       hello      n   hello   n         what did you see instead     the other way around    observation  there s two things here that i think are potentially misleading  although both are sort of trivial  the first is that  according to the  goroutine destruction  section  there s no guarantee that  anything  gets printed  because nothing is waiting on these  and indeed  without the extra channel operations  nothing happens     the second is the distinction between  the first call to doprint      the first call to doprint   which actually starts execution   and  the first call to doprint   which actually begins the once do   call   while in the trivial example  probably the first call to start executing will win that  it s not generally a given that two goroutines acting in parallel will always complete in the same order they start  even running identical code  but in particular  it s definitely not guaranteed that the  first call  will start executing first     i m fine with handwaving the synchronization thing  but i think the wording on  the first call  might benefit from cleaning up  proposed wording     the first call to  doprint    to begin executing the  once do    calls  setup     any calls that reach that point later do not  regardless of the order in which the goroutines are invoked or begin executing ,1
22399,4794298416.0,IssuesEvent,2016-10-31 20:37:35,golang/go,https://api.github.com/repos/golang/go,closed,doc/articles: references obsolete code.google.com/p/codesearch/index,Documentation NeedsFix,"This document:

""About the go command""
https://golang.org/doc/articles/go_command.html

references codesearch as part of code.google.com:

code.google.com/p/codesearch/index

This should be changed to:

github.com/google/codesearch/index

I am happy to make this change and submit a patch.
",1.0,"doc/articles: references obsolete code.google.com/p/codesearch/index - This document:

""About the go command""
https://golang.org/doc/articles/go_command.html

references codesearch as part of code.google.com:

code.google.com/p/codesearch/index

This should be changed to:

github.com/google/codesearch/index

I am happy to make this change and submit a patch.
",1,doc articles  references obsolete code google com p codesearch index   this document    about the go command     references codesearch as part of code google com   code google com p codesearch index  this should be changed to   github com google codesearch index  i am happy to make this change and submit a patch  ,1
5955,4097930800.0,IssuesEvent,2016-06-03 05:24:32,zerotier/ZeroTierOne,https://api.github.com/repos/zerotier/ZeroTierOne,closed,Allow IP to be copied,usability web,"In ZeroTier Central the I of the nodes is shown as 4 seperate numbers, which cannot be copied easily all at once
Please allow some way to copy the whole IP addres of the node easily

![selection_296](https://cloud.githubusercontent.com/assets/1491826/11029331/87b0a034-86c6-11e5-9342-9750ad91c139.jpg)


",True,"Allow IP to be copied - In ZeroTier Central the I of the nodes is shown as 4 seperate numbers, which cannot be copied easily all at once
Please allow some way to copy the whole IP addres of the node easily

![selection_296](https://cloud.githubusercontent.com/assets/1491826/11029331/87b0a034-86c6-11e5-9342-9750ad91c139.jpg)


",0,allow ip to be copied   in zerotier central the i of the nodes is shown as   seperate numbers  which cannot be copied easily all at once  please allow some way to copy the whole ip addres of the node easily              ,0
39896,6779848917.0,IssuesEvent,2017-10-29 06:04:21,golang/go,https://api.github.com/repos/golang/go,opened,doc: simplify contributing by offering clear plain git guidelines,Documentation,"### What
Change the contributing guidelines document to make the recommended process more familiar and obvious to users of plain git?

### What it is not
This issue is not a request or proposal to replace Gerrit or the review process. This issue is not a request or proposal to remove the `git-codereview` tool or to make drastic changes to how anyone on the Go team or existing contributors go about contributing. 

### Why
There are other open issues proposing a switch to GitHub, or adding the ability to support pushing to GitHub. Based on my own experience I think much of the friction that GitHub users are experiencing is caused by the contributing guidelines centering around `git-codereview`, which abstracts git away from the developer. Abstracting git away from developers is jarring when developers know how to use that tool already. It gives them the experience that they are using something that is entirely different to what they use today, even though it is not.

### Context
I recently submitted my [first](https://go-review.googlesource.com/c/go/+/73890) [contribution](https://go-review.googlesource.com/c/go/+/73891) to Go and was surprised at how straight forward and refreshing Gerrit was in comparison to GitHub. I had delayed contributing because the process described at https://golang.org/doc/contribute.html appeared so different to what I was use to. In practice it wasn't. It only appeared that way because there was a layer of abstraction.

Before contributing the main point of friction for me wasn't the use of Gerrit vs GitHub, but the fact that all of the examples centered around the use of `git-codereview`, a custom tool for interacting with the Go Gerrit instance. I realize this tool is optional, but it took time to read all of the text and note down which git commands each `git-codereview` command actually used.

At the end it came down to:
1. Install two hooks
2. `git clone`
3. `git pull -r`
4. `git checkout -b <branch>`
5. `git commit`
6. `git push -u origin HEAD:refs/for/master` (patch set 1)
7. `git commit --amend`
8. `git push -u origin HEAD:refs/for/master` (patch set 2)

The above is almost identical to the workflows I use at work and on open source on GitHub, and it is instantly familiar to me as a git user.

The contribution guidelines tell a different story:
1. `git codereview hooks`
2. `git clone`
3. `git sync`
4. `git change`
5. `git mail` (path set 1)
6. `git change` (to amend)
7. `git mail` (patch set 2)

While the above is technically less commands, it's four new commands that I had never seen before and had to learn about. These commands abstract git away from plain git users, unnecessarily.

### How
Some ideas for how the contributing guidelines document could be made more familiar to plain git users:

* Replace examples using `git-codereview` with plain git commands where the corresponding git commands are simple and straight forward. e.g. `git sync` vs `git pull -r`, `git push` vs `git mail`, etc.
* Display plain git commands side-by-side (not one after the other) in the same size, font, weight, etc.
* Make `git-codereview` the recommended path for those not familiar with git, or power users.
* Make plain git the recommended path for those familiar with git, with a suggestion to check out `git-codereview`.
* Offer the pre-commit hook at a URL that can be curl'd like how the [commit-msg hook is available](http://go-review.googlesource.com/tools/hooks/commit-msg) so that it's simple for developers to install the commit hooks how they would any others for other projects.

I've got a branch with changes to the contributing doc that I made to experiment with these ideas and to confirm if focusing on plain git commands would make it appear more familiar and approachable. I'd love to be involved with improving the guidelines in this way if this is something that the community agrees with.",1.0,"doc: simplify contributing by offering clear plain git guidelines - ### What
Change the contributing guidelines document to make the recommended process more familiar and obvious to users of plain git?

### What it is not
This issue is not a request or proposal to replace Gerrit or the review process. This issue is not a request or proposal to remove the `git-codereview` tool or to make drastic changes to how anyone on the Go team or existing contributors go about contributing. 

### Why
There are other open issues proposing a switch to GitHub, or adding the ability to support pushing to GitHub. Based on my own experience I think much of the friction that GitHub users are experiencing is caused by the contributing guidelines centering around `git-codereview`, which abstracts git away from the developer. Abstracting git away from developers is jarring when developers know how to use that tool already. It gives them the experience that they are using something that is entirely different to what they use today, even though it is not.

### Context
I recently submitted my [first](https://go-review.googlesource.com/c/go/+/73890) [contribution](https://go-review.googlesource.com/c/go/+/73891) to Go and was surprised at how straight forward and refreshing Gerrit was in comparison to GitHub. I had delayed contributing because the process described at https://golang.org/doc/contribute.html appeared so different to what I was use to. In practice it wasn't. It only appeared that way because there was a layer of abstraction.

Before contributing the main point of friction for me wasn't the use of Gerrit vs GitHub, but the fact that all of the examples centered around the use of `git-codereview`, a custom tool for interacting with the Go Gerrit instance. I realize this tool is optional, but it took time to read all of the text and note down which git commands each `git-codereview` command actually used.

At the end it came down to:
1. Install two hooks
2. `git clone`
3. `git pull -r`
4. `git checkout -b <branch>`
5. `git commit`
6. `git push -u origin HEAD:refs/for/master` (patch set 1)
7. `git commit --amend`
8. `git push -u origin HEAD:refs/for/master` (patch set 2)

The above is almost identical to the workflows I use at work and on open source on GitHub, and it is instantly familiar to me as a git user.

The contribution guidelines tell a different story:
1. `git codereview hooks`
2. `git clone`
3. `git sync`
4. `git change`
5. `git mail` (path set 1)
6. `git change` (to amend)
7. `git mail` (patch set 2)

While the above is technically less commands, it's four new commands that I had never seen before and had to learn about. These commands abstract git away from plain git users, unnecessarily.

### How
Some ideas for how the contributing guidelines document could be made more familiar to plain git users:

* Replace examples using `git-codereview` with plain git commands where the corresponding git commands are simple and straight forward. e.g. `git sync` vs `git pull -r`, `git push` vs `git mail`, etc.
* Display plain git commands side-by-side (not one after the other) in the same size, font, weight, etc.
* Make `git-codereview` the recommended path for those not familiar with git, or power users.
* Make plain git the recommended path for those familiar with git, with a suggestion to check out `git-codereview`.
* Offer the pre-commit hook at a URL that can be curl'd like how the [commit-msg hook is available](http://go-review.googlesource.com/tools/hooks/commit-msg) so that it's simple for developers to install the commit hooks how they would any others for other projects.

I've got a branch with changes to the contributing doc that I made to experiment with these ideas and to confirm if focusing on plain git commands would make it appear more familiar and approachable. I'd love to be involved with improving the guidelines in this way if this is something that the community agrees with.",1,doc  simplify contributing by offering clear plain git guidelines       what  change the contributing guidelines document to make the recommended process more familiar and obvious to users of plain git         what it is not  this issue is not a request or proposal to replace gerrit or the review process  this issue is not a request or proposal to remove the  git codereview  tool or to make drastic changes to how anyone on the go team or existing contributors go about contributing          why  there are other open issues proposing a switch to github  or adding the ability to support pushing to github  based on my own experience i think much of the friction that github users are experiencing is caused by the contributing guidelines centering around  git codereview   which abstracts git away from the developer  abstracting git away from developers is jarring when developers know how to use that tool already  it gives them the experience that they are using something that is entirely different to what they use today  even though it is not         context  i recently submitted my         to go and was surprised at how straight forward and refreshing gerrit was in comparison to github  i had delayed contributing because the process described at   appeared so different to what i was use to  in practice it wasn t  it only appeared that way because there was a layer of abstraction     before contributing the main point of friction for me wasn t the use of gerrit vs github  but the fact that all of the examples centered around the use of  git codereview   a custom tool for interacting with the go gerrit instance  i realize this tool is optional  but it took time to read all of the text and note down which git commands each  git codereview  command actually used     at the end it came down to      install two hooks      git clone       git pull  r       git checkout  b         git commit       git push  u origin head refs for master   patch set         git commit   amend       git push  u origin head refs for master   patch set       the above is almost identical to the workflows i use at work and on open source on github  and it is instantly familiar to me as a git user     the contribution guidelines tell a different story       git codereview hooks       git clone       git sync       git change       git mail   path set         git change   to amend       git mail   patch set       while the above is technically less commands  it s four new commands that i had never seen before and had to learn about  these commands abstract git away from plain git users  unnecessarily         how  some ideas for how the contributing guidelines document could be made more familiar to plain git users       replace examples using  git codereview  with plain git commands where the corresponding git commands are simple and straight forward  e g   git sync  vs  git pull  r    git push  vs  git mail   etc     display plain git commands side by side  not one after the other  in the same size  font  weight  etc     make  git codereview  the recommended path for those not familiar with git  or power users     make plain git the recommended path for those familiar with git  with a suggestion to check out  git codereview      offer the pre commit hook at a url that can be curl d like how the     so that it s simple for developers to install the commit hooks how they would any others for other projects     i ve got a branch with changes to the contributing doc that i made to experiment with these ideas and to confirm if focusing on plain git commands would make it appear more familiar and approachable  i d love to be involved with improving the guidelines in this way if this is something that the community agrees with ,1
157851,12393462424.0,IssuesEvent,2020-05-20 15:27:29,cr-ste-justine/clin-project,https://api.github.com/repos/cr-ste-justine/clin-project,closed,[CLIN-VAR] Unit Tests for SQON -> ES Mapper,SQON Test,"Please set-up base to run unit tests and write some unit tests for the following SQON to ES mapper features:

- [ ] Generic filter instructions
- [ ] NumericalComparison instructions
- [ ] GenericBoolean filter instructions
- [ ] Composite filter instructions
- [ ] Specific filter instructions
- [ ] ""Grouped"" filter instructions (query a + query b)
",1.0,"[CLIN-VAR] Unit Tests for SQON -> ES Mapper - Please set-up base to run unit tests and write some unit tests for the following SQON to ES mapper features:

- [ ] Generic filter instructions
- [ ] NumericalComparison instructions
- [ ] GenericBoolean filter instructions
- [ ] Composite filter instructions
- [ ] Specific filter instructions
- [ ] ""Grouped"" filter instructions (query a + query b)
",0,  unit tests for sqon    es mapper   please set up base to run unit tests and write some unit tests for the following sqon to es mapper features       generic filter instructions     numericalcomparison instructions     genericboolean filter instructions     composite filter instructions     specific filter instructions      grouped  filter instructions  query a   query b  ,0
20416,4543340215.0,IssuesEvent,2016-09-10 03:01:53,golang/go,https://api.github.com/repos/golang/go,closed,x/crypto/scrypt: fix scrypt example,Documentation HelpWanted,"The scrypt code example doesn't work, as `scrypt.Key` also returns an error.

`dk := scrypt.Key([]byte(""some password""), salt, 16384, 8, 1, 32)`
-->
`dk, err := scrypt.Key([]byte(""some password""), salt, 16384, 8, 1, 32)`

https://github.com/golang/crypto/blob/05d11b2ca14108dfc7f74f4f66b28c7fe92e1fd0/scrypt/scrypt.go#L221",1.0,"x/crypto/scrypt: fix scrypt example - The scrypt code example doesn't work, as `scrypt.Key` also returns an error.

`dk := scrypt.Key([]byte(""some password""), salt, 16384, 8, 1, 32)`
-->
`dk, err := scrypt.Key([]byte(""some password""), salt, 16384, 8, 1, 32)`

https://github.com/golang/crypto/blob/05d11b2ca14108dfc7f74f4f66b28c7fe92e1fd0/scrypt/scrypt.go#L221",1,x crypto scrypt  fix scrypt example   the scrypt code example doesn t work  as  scrypt key  also returns an error      dk    scrypt key  byte  some password    salt                      dk  err    scrypt key  byte  some password    salt                   ,1
729178,25112023625.0,IssuesEvent,2022-11-08 21:26:05,zulip/zulip,https://api.github.com/repos/zulip/zulip,closed,"Show Private messages heading in ""more topics"" view",area: left-sidebar in progress priority: high release goal,"As [reported on CZO](https://chat.zulip.org/#narrow/stream/101-design/topic/private.20messages.20section.20.2320870/near/1457220):

> The unread count for private messages is not visible when you're in the topic zoomed view... It would make sense to have it visible, in the same visual state as when you're scrolled down in the streams list (so it's a single line), and have clicking it both exit ""recent topics"", and scroll to it / expand it.

That way, the number of unread private messages will always be visible.
",1.0,"Show Private messages heading in ""more topics"" view - As [reported on CZO](https://chat.zulip.org/#narrow/stream/101-design/topic/private.20messages.20section.20.2320870/near/1457220):

> The unread count for private messages is not visible when you're in the topic zoomed view... It would make sense to have it visible, in the same visual state as when you're scrolled down in the streams list (so it's a single line), and have clicking it both exit ""recent topics"", and scroll to it / expand it.

That way, the number of unread private messages will always be visible.
",0,show private messages heading in  more topics  view   as          the unread count for private messages is not visible when you re in the topic zoomed view    it would make sense to have it visible  in the same visual state as when you re scrolled down in the streams list  so it s a single line   and have clicking it both exit  recent topics   and scroll to it   expand it     that way  the number of unread private messages will always be visible   ,0
8964,7520930005.0,IssuesEvent,2018-04-12 15:41:29,rchain/bounties,https://api.github.com/repos/rchain/bounties,closed,Discuss Bug Bounties,security wontfix,"## target
decide on concise list of executable, bug hunts with defined timeframe
## why?
find possible dangers in our processes 
## what? decide:
### what targets; example:
- code
- communication channels
- ...

### height of bounty, example:
someone found way to break one of our projects: 300,
or smaller exploits, even like some doc has wrong access rights: 30
### timeframe; example:
bug hunt 1 with the decided rules goes from feb-march

## est. time: 2 weeks",True,"Discuss Bug Bounties - ## target
decide on concise list of executable, bug hunts with defined timeframe
## why?
find possible dangers in our processes 
## what? decide:
### what targets; example:
- code
- communication channels
- ...

### height of bounty, example:
someone found way to break one of our projects: 300,
or smaller exploits, even like some doc has wrong access rights: 30
### timeframe; example:
bug hunt 1 with the decided rules goes from feb-march

## est. time: 2 weeks",0,discuss bug bounties      target  decide on concise list of executable  bug hunts with defined timeframe     why   find possible dangers in our processes      what  decide       what targets  example     code    communication channels               height of bounty  example   someone found way to break one of our projects      or smaller exploits  even like some doc has wrong access rights         timeframe  example   bug hunt   with the decided rules goes from feb march       est  time    weeks,0
274138,20826826495.0,IssuesEvent,2022-03-18 22:16:20,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: improving documentation for when hashes are not included in binaries,Documentation NeedsInvestigation GoCommand,"I used debug/buildinfo, which will be added in Go 1.18. As far as I can see, the hash is not included if you build it as `command-line-arguments` as follows.

https://tip.golang.org/doc/go1.18

> Version control information is embedded if the go command is invoked in a directory within a Git, Mercurial, Fossil, or Bazaar repository, and the main package and its containing main module are in the same repository.

Do I need to add to the above documentation that hashes are not included if built as `command-line-arguments`?

## Example

- Directory structure

```
.
├── go.mod
└── main.go
```

- go.mod

```
module sample

go 1.18
```

- main.go

```go
package main

import (
    ""fmt""
)

func main() {
    fmt.Println(""Hello, world"")
}
```

## When built as `command-line-arguments`

VCS hashes are not included.

```
$ go build main.go
$ go version -m main
main: go1.18beta1
        path    command-line-arguments
        build   -compiler=gc
        build   CGO_ENABLED=1
        build   CGO_CFLAGS=
        build   CGO_CPPFLAGS=
        build   CGO_CXXFLAGS=
        build   CGO_LDFLAGS=
        build   GOARCH=amd64
        build   GOOS=linux
        build   GOAMD64=v1
```

## If you build as package name.

VCS hashes are included. This is the behavior we expect in Go 1.18.

```
$ go build sample
$ go version -m sample
sample: go1.18beta1
        path    sample
        mod     sample  (devel)
        build   -compiler=gc
        build   CGO_ENABLED=1
        build   CGO_CFLAGS=
        build   CGO_CPPFLAGS=
        build   CGO_CXXFLAGS=
        build   CGO_LDFLAGS=
        build   GOARCH=amd64
        build   GOOS=linux
        build   GOAMD64=v1
        build   vcs=git
        build   vcs.revision=sample0123456789012345678901234567sample
        build   vcs.time=2021-12-27T04:24:55Z
        build   vcs.modified=true
```

The behavior of whether or not VCS hashes are included in builds with the `go build` argument is described in the draft release notes, but there is room to improve the documentation.
",1.0,"cmd/go: improving documentation for when hashes are not included in binaries - I used debug/buildinfo, which will be added in Go 1.18. As far as I can see, the hash is not included if you build it as `command-line-arguments` as follows.

https://tip.golang.org/doc/go1.18

> Version control information is embedded if the go command is invoked in a directory within a Git, Mercurial, Fossil, or Bazaar repository, and the main package and its containing main module are in the same repository.

Do I need to add to the above documentation that hashes are not included if built as `command-line-arguments`?

## Example

- Directory structure

```
.
├── go.mod
└── main.go
```

- go.mod

```
module sample

go 1.18
```

- main.go

```go
package main

import (
    ""fmt""
)

func main() {
    fmt.Println(""Hello, world"")
}
```

## When built as `command-line-arguments`

VCS hashes are not included.

```
$ go build main.go
$ go version -m main
main: go1.18beta1
        path    command-line-arguments
        build   -compiler=gc
        build   CGO_ENABLED=1
        build   CGO_CFLAGS=
        build   CGO_CPPFLAGS=
        build   CGO_CXXFLAGS=
        build   CGO_LDFLAGS=
        build   GOARCH=amd64
        build   GOOS=linux
        build   GOAMD64=v1
```

## If you build as package name.

VCS hashes are included. This is the behavior we expect in Go 1.18.

```
$ go build sample
$ go version -m sample
sample: go1.18beta1
        path    sample
        mod     sample  (devel)
        build   -compiler=gc
        build   CGO_ENABLED=1
        build   CGO_CFLAGS=
        build   CGO_CPPFLAGS=
        build   CGO_CXXFLAGS=
        build   CGO_LDFLAGS=
        build   GOARCH=amd64
        build   GOOS=linux
        build   GOAMD64=v1
        build   vcs=git
        build   vcs.revision=sample0123456789012345678901234567sample
        build   vcs.time=2021-12-27T04:24:55Z
        build   vcs.modified=true
```

The behavior of whether or not VCS hashes are included in builds with the `go build` argument is described in the draft release notes, but there is room to improve the documentation.
",1,cmd go  improving documentation for when hashes are not included in binaries   i used debug buildinfo  which will be added in go      as far as i can see  the hash is not included if you build it as  command line arguments  as follows            version control information is embedded if the go command is invoked in a directory within a git  mercurial  fossil  or bazaar repository  and the main package and its containing main module are in the same repository     do i need to add to the above documentation that hashes are not included if built as  command line arguments         example      directory structure            ├── go mod  └── main go           go mod         module sample    go               main go       go  package main    import         fmt        func main          fmt println  hello  world                 when built as  command line arguments     vcs hashes are not included            go build main go    go version  m main  main               path    command line arguments          build    compiler gc          build   cgo enabled            build   cgo cflags           build   cgo cppflags           build   cgo cxxflags           build   cgo ldflags           build   goarch            build   goos linux          build                  if you build as package name     vcs hashes are included  this is the behavior we expect in go                go build sample    go version  m sample  sample               path    sample          mod     sample   devel           build    compiler gc          build   cgo enabled            build   cgo cflags           build   cgo cppflags           build   cgo cxxflags           build   cgo ldflags           build   goarch            build   goos linux          build                build   vcs git          build   vcs revision            build   vcs time                    build   vcs modified true         the behavior of whether or not vcs hashes are included in builds with the  go build  argument is described in the draft release notes  but there is room to improve the documentation   ,1
12548,3621001402.0,IssuesEvent,2016-02-08 22:12:59,golang/go,https://api.github.com/repos/golang/go,closed,runtime: typo in comment about timer type's fields,Documentation,"https://github.com/golang/go/blob/master/src/runtime/time.go#L19
In this line should 
`// each time calling f(now, arg) in the timer goroutine, so f must be`
be replace with `// each time calling f(arg, now) in the timer goroutine, so f must be`, it seems seq is the timestamp of the timer, and it is passed as now in f.",1.0,"runtime: typo in comment about timer type's fields - https://github.com/golang/go/blob/master/src/runtime/time.go#L19
In this line should 
`// each time calling f(now, arg) in the timer goroutine, so f must be`
be replace with `// each time calling f(arg, now) in the timer goroutine, so f must be`, it seems seq is the timestamp of the timer, and it is passed as now in f.",1,runtime  typo in comment about timer type s fields      in this line should       each time calling f now  arg  in the timer goroutine  so f must be   be replace with     each time calling f arg  now  in the timer goroutine  so f must be   it seems seq is the timestamp of the timer  and it is passed as now in f ,1
722502,24864748666.0,IssuesEvent,2022-10-27 11:01:16,lowRISC/opentitan,https://api.github.com/repos/lowRISC/opentitan,closed,[aes] Shall we enable SecAllowForcingMasks for ES?,Priority:P0 Type:Question Component:RTL Component:Security Hotlist:Security IP:aes Milestone:D3,"At the moment, the masking in AES is always enabled on ASIC. Exclusively on FPGA, we allow disabling the masking using the `SecAllowForcingMasks` SV parameter in combination with the FORCE_ZERO_MASKS field in the main control register (on ASIC, the corresponding logic is simply not there). Having the option to disable the masking is useful to tune the SCA capture setup and evaluate the noise.

Recently, we have discussed in the SCA meeting and in particular with @johannheyszl and @m-temp that specifically for the positioning of the high-precision EM probes for our own evaluation of ES it would be important to have this feature also on ASIC. Otherwise, the positioning of the EM probe alone will be extremely time consuming and we won't have a way to evaluate how good the masking is compared to no masking. Therefore, I suggest the following:

1. Adapt the RTL to instead of forcing the masks to zero, forcing them to be constant by not advancing the masking PRNG if the Sec parameter and the control register are configured properly. From an SCA perspective, the effect of constant and all zero masks is the same - the masking is off. The advantage of forcing constant masks vs. zero masks is much lower area overhead. Disabling the Sec parameter for production will have a very low layout impact/could even be done with a metal fix. 
2. Move the FORCE_ZERO/CONSTANT_MASKS fields into the lockable CTRL_AUX_SHADOWED register. This has the advantage that the feature cannot be enabled anymore after some point.

It's also worth noting that in normal operation, a periodic reseed of the masking PRNG will happen after 1, 64 or 8k blocks. So even if someone managed to force constant masks, the PRNG state and thus the masks will be updated automatically at some point. For the lab evaluation, we would avoid this by setting the reseed interval to 8k, disabling the lockable KEY_TOUCH_FORCES_RESEED field in the CTRL_AUX_SHADOWED register, and by re-configuring the module after every 8k blocks (to avoid the reseed counter expiring).

Before changing the design, I would also like to get the opinion of @cdgori, @tjaychen and @moidx . WDYT?",1.0,"[aes] Shall we enable SecAllowForcingMasks for ES? - At the moment, the masking in AES is always enabled on ASIC. Exclusively on FPGA, we allow disabling the masking using the `SecAllowForcingMasks` SV parameter in combination with the FORCE_ZERO_MASKS field in the main control register (on ASIC, the corresponding logic is simply not there). Having the option to disable the masking is useful to tune the SCA capture setup and evaluate the noise.

Recently, we have discussed in the SCA meeting and in particular with @johannheyszl and @m-temp that specifically for the positioning of the high-precision EM probes for our own evaluation of ES it would be important to have this feature also on ASIC. Otherwise, the positioning of the EM probe alone will be extremely time consuming and we won't have a way to evaluate how good the masking is compared to no masking. Therefore, I suggest the following:

1. Adapt the RTL to instead of forcing the masks to zero, forcing them to be constant by not advancing the masking PRNG if the Sec parameter and the control register are configured properly. From an SCA perspective, the effect of constant and all zero masks is the same - the masking is off. The advantage of forcing constant masks vs. zero masks is much lower area overhead. Disabling the Sec parameter for production will have a very low layout impact/could even be done with a metal fix. 
2. Move the FORCE_ZERO/CONSTANT_MASKS fields into the lockable CTRL_AUX_SHADOWED register. This has the advantage that the feature cannot be enabled anymore after some point.

It's also worth noting that in normal operation, a periodic reseed of the masking PRNG will happen after 1, 64 or 8k blocks. So even if someone managed to force constant masks, the PRNG state and thus the masks will be updated automatically at some point. For the lab evaluation, we would avoid this by setting the reseed interval to 8k, disabling the lockable KEY_TOUCH_FORCES_RESEED field in the CTRL_AUX_SHADOWED register, and by re-configuring the module after every 8k blocks (to avoid the reseed counter expiring).

Before changing the design, I would also like to get the opinion of @cdgori, @tjaychen and @moidx . WDYT?",0,  shall we enable secallowforcingmasks for es    at the moment  the masking in aes is always enabled on asic  exclusively on fpga  we allow disabling the masking using the  secallowforcingmasks  sv parameter in combination with the force zero masks field in the main control register  on asic  the corresponding logic is simply not there   having the option to disable the masking is useful to tune the sca capture setup and evaluate the noise     recently  we have discussed in the sca meeting and in particular with  johannheyszl and  m temp that specifically for the positioning of the high precision em probes for our own evaluation of es it would be important to have this feature also on asic  otherwise  the positioning of the em probe alone will be extremely time consuming and we won t have a way to evaluate how good the masking is compared to no masking  therefore  i suggest the following        adapt the rtl to instead of forcing the masks to zero  forcing them to be constant by not advancing the masking prng if the sec parameter and the control register are configured properly  from an sca perspective  the effect of constant and all zero masks is the same   the masking is off  the advantage of forcing constant masks vs  zero masks is much lower area overhead  disabling the sec parameter for production will have a very low layout impact could even be done with a metal fix       move the force zero constant masks fields into the lockable ctrl aux shadowed register  this has the advantage that the feature cannot be enabled anymore after some point     it s also worth noting that in normal operation  a periodic reseed of the masking prng will happen after      or   blocks  so even if someone managed to force constant masks  the prng state and thus the masks will be updated automatically at some point  for the lab evaluation  we would avoid this by setting the reseed interval to    disabling the lockable key touch forces reseed field in the ctrl aux shadowed register  and by re configuring the module after every   blocks  to avoid the reseed counter expiring      before changing the design  i would also like to get the opinion of  cdgori   tjaychen and  moidx   wdyt ,0
215667,16614220069.0,IssuesEvent,2021-06-02 14:52:44,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.17: document time changes for Go 1.17,Documentation NeedsInvestigation help wanted release-blocker,"As of filing this issue, the [Go 1.17 draft release notes](https://tip.golang.org/doc/go1.17) contained the following HTML:

<dl id=""time""><dt><a href=""/pkg/time/"">time</a></dt>
  <dd>
    <p><!-- CL 260858 -->
      time.Time now has a <a href=""/pkg/time/#Time.GoString"">GoString</a>
      method that will return a more useful value for times when printed with
      the <code>&#34;%#v&#34;</code> format specifier in the fmt package.
    </p>
    <p><!-- CL 264077 -->
      TODO: <a href=""https://golang.org/cl/264077"">https://golang.org/cl/264077</a>: add Time.IsDST() to check if its Location is in Daylight Savings Time
    </p>
    <p><!-- CL 293349 -->
      TODO: <a href=""https://golang.org/cl/293349"">https://golang.org/cl/293349</a>: add Time.Unix{Milli,Micro} and to-Time helpers UnixMicro, UnixMilli
    </p>
    <p><!-- CL 300996 -->
      TODO: <a href=""https://golang.org/cl/300996"">https://golang.org/cl/300996</a>: support &#34;,&#34; as separator for fractional seconds
    </p>
  </dd>
</dl>

---

This TODO needs to be resolved by July 1 so that we can have complete release notes for [Beta 1](https://golang.org/s/release#june-1--december-1-beta-1-issued).

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.17:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.17) and include ""For #44513. Fixes #46026."" in the body.",1.0,"doc/go1.17: document time changes for Go 1.17 - As of filing this issue, the [Go 1.17 draft release notes](https://tip.golang.org/doc/go1.17) contained the following HTML:

<dl id=""time""><dt><a href=""/pkg/time/"">time</a></dt>
  <dd>
    <p><!-- CL 260858 -->
      time.Time now has a <a href=""/pkg/time/#Time.GoString"">GoString</a>
      method that will return a more useful value for times when printed with
      the <code>&#34;%#v&#34;</code> format specifier in the fmt package.
    </p>
    <p><!-- CL 264077 -->
      TODO: <a href=""https://golang.org/cl/264077"">https://golang.org/cl/264077</a>: add Time.IsDST() to check if its Location is in Daylight Savings Time
    </p>
    <p><!-- CL 293349 -->
      TODO: <a href=""https://golang.org/cl/293349"">https://golang.org/cl/293349</a>: add Time.Unix{Milli,Micro} and to-Time helpers UnixMicro, UnixMilli
    </p>
    <p><!-- CL 300996 -->
      TODO: <a href=""https://golang.org/cl/300996"">https://golang.org/cl/300996</a>: support &#34;,&#34; as separator for fractional seconds
    </p>
  </dd>
</dl>

---

This TODO needs to be resolved by July 1 so that we can have complete release notes for [Beta 1](https://golang.org/s/release#june-1--december-1-beta-1-issued).

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.17:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.17) and include ""For #44513. Fixes #46026."" in the body.",1,doc      document time changes for go       as of filing this issue  the     contained the following html      time                    time time now has a  gostring        method that will return a more useful value for times when printed with       the        v      format specifier in the fmt package                     todo   a href    add time isdst   to check if its location is in daylight savings time                    todo   a href    add time unix milli micro  and to time helpers unixmicro  unixmilli                    todo   a href    support           as separator for fractional seconds                   this todo needs to be resolved by july   so that we can have complete release notes for      a sequence of steps to resolve this issue may be      come up with a draft release note entry in this issue  then move the issue to needsfix state     send a cl with  doc           and include  for     fixes      in the body ,1
57667,8202281478.0,IssuesEvent,2018-09-02 07:04:41,golang/go,https://api.github.com/repos/golang/go,closed,"cmd/{godoc,vet},testing: godoc disagrees with the docs and vet about validity of example name suffixes",Documentation,"### What version of Go are you using (`go version`)?
```
$ go version
go version go1.11 linux/amd64
```

### Does this issue reproduce with the latest release?
Yes.

### What operating system and processor architecture are you using (`go env`)?
linux/amd64

### What did you do?
```
~/src/gonum.org/v1/gonum/graph/topo$ go vet
# gonum.org/v1/gonum/graph/topo_test
./2sat_example_test.go:177: ExampleTarjanSCC_2sat refers to unknown field or method: TarjanSCC.2sat
```

However, godoc [renders the 2sat example](https://godoc.org/gonum.org/v1/gonum/graph/topo#example-TarjanSCC--2sat).

### What did you expect to see?
An error from vet and a failure from godoc to render the example.

### What did you see instead?
A vet error but a rendered example.

### What would you like to see?
No error and a rendered example. That is, a relaxation of the [documented](https://golang.org/pkg/testing/#hdr-Examples) requirement for an initial lowercase **letter** in the suffix (""The suffix must start with a lower-case letter."") to allow numeric leading glyphs.
",1.0,"cmd/{godoc,vet},testing: godoc disagrees with the docs and vet about validity of example name suffixes - ### What version of Go are you using (`go version`)?
```
$ go version
go version go1.11 linux/amd64
```

### Does this issue reproduce with the latest release?
Yes.

### What operating system and processor architecture are you using (`go env`)?
linux/amd64

### What did you do?
```
~/src/gonum.org/v1/gonum/graph/topo$ go vet
# gonum.org/v1/gonum/graph/topo_test
./2sat_example_test.go:177: ExampleTarjanSCC_2sat refers to unknown field or method: TarjanSCC.2sat
```

However, godoc [renders the 2sat example](https://godoc.org/gonum.org/v1/gonum/graph/topo#example-TarjanSCC--2sat).

### What did you expect to see?
An error from vet and a failure from godoc to render the example.

### What did you see instead?
A vet error but a rendered example.

### What would you like to see?
No error and a rendered example. That is, a relaxation of the [documented](https://golang.org/pkg/testing/#hdr-Examples) requirement for an initial lowercase **letter** in the suffix (""The suffix must start with a lower-case letter."") to allow numeric leading glyphs.
",1,cmd  godoc vet  testing  godoc disagrees with the docs and vet about validity of example name suffixes       what version of go are you using   go version            go version  go version     linux               does this issue reproduce with the latest release   yes         what operating system and processor architecture are you using   go env     linux          what did you do          src gonum org   gonum graph topo  go vet    gonum org   gonum graph topo test      example test go    exampletarjanscc   refers to unknown field or method  tarjanscc           however  godoc            what did you expect to see   an error from vet and a failure from godoc to render the example         what did you see instead   a vet error but a rendered example         what would you like to see   no error and a rendered example  that is  a relaxation of the     requirement for an initial lowercase   letter   in the suffix   the suffix must start with a lower case letter    to allow numeric leading glyphs   ,1
88870,11164260563.0,IssuesEvent,2019-12-27 03:50:40,GospelAid/badiup,https://api.github.com/repos/GospelAid/badiup,opened,Need background image for login page,P0 bug design,"Currently the XD design file contains this image which contains ""Login with Google"" button:
![Screenshot 2019-12-27 at 12 49 05 PM](https://user-images.githubusercontent.com/1173819/71500223-5f324180-28a7-11ea-9151-3b60ff499e07.png)

Need an image without the button. ",1.0,"Need background image for login page - Currently the XD design file contains this image which contains ""Login with Google"" button:
![Screenshot 2019-12-27 at 12 49 05 PM](https://user-images.githubusercontent.com/1173819/71500223-5f324180-28a7-11ea-9151-3b60ff499e07.png)

Need an image without the button. ",0,need background image for login page   currently the xd design file contains this image which contains  login with google  button           need an image without the button  ,0
219980,16859591318.0,IssuesEvent,2021-06-21 11:18:25,golang/go,https://api.github.com/repos/golang/go,reopened,runtime: document gctrace output in relation to MemStats,Documentation NeedsInvestigation,"How do the heap sizes output by gctrace map to the various values of MemStats?  I assume that the heap values from gctrace roughly match _one_ (or two?) of the MemStats fields, but I can't find anything that documents that. 

I see in the code that the gctrace outputs are mostly based on `heap_live` and the MemStats values are not (directly) based on the the same thing... but I'm guessing there's an indirect or approximate link.  Knowing such a mapping would help a lot in using gctrace, since it doesn't have heaps of documentation but MemStats has lots.",1.0,"runtime: document gctrace output in relation to MemStats - How do the heap sizes output by gctrace map to the various values of MemStats?  I assume that the heap values from gctrace roughly match _one_ (or two?) of the MemStats fields, but I can't find anything that documents that. 

I see in the code that the gctrace outputs are mostly based on `heap_live` and the MemStats values are not (directly) based on the the same thing... but I'm guessing there's an indirect or approximate link.  Knowing such a mapping would help a lot in using gctrace, since it doesn't have heaps of documentation but MemStats has lots.",1,runtime  document gctrace output in relation to memstats   how do the heap sizes output by gctrace map to the various values of memstats   i assume that the heap values from gctrace roughly match  one   or two   of the memstats fields  but i can t find anything that documents that      i see in the code that the gctrace outputs are mostly based on  heap live  and the memstats values are not  directly  based on the the same thing    but i m guessing there s an indirect or approximate link   knowing such a mapping would help a lot in using gctrace  since it doesn t have heaps of documentation but memstats has lots ,1
212963,16505752816.0,IssuesEvent,2021-05-25 19:04:41,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.17: document closure inlining affects function PC comparison,Documentation NeedsFix okay-after-beta1,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version devel go1.17-d5d24dbe41 Mon Apr 26 17:13:36 2021 +0000 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

only master

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
~/go/src/playground/at-2021-04-26-204402 $ ~/Code/go/bin/go env
GO111MODULE=""on""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/rski/.cache/go-build""
GOENV=""/home/rski/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/rski/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""=""
GOOS=""linux""
GOPATH=""/home/rski/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/home/rski/Code/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/home/rski/Code/go/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""devel go1.17-d5d24dbe41 Mon Apr 26 17:13:36 2021 +0000""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""0""
GOMOD=""/home/rski/go/src/playground/at-2021-04-26-204402/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2782832869=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

https://play.golang.org/p/Yw1lgRph4Kd

### What did you expect to see?

This should print `main.WithFoo.func1`, as with go 16.3

### What did you see instead?

After the regabi branch merge, this prints 

main.init.func1

This was temporarily fixed by 1129a60f1c1e64147ca1133857c4571ce9b87a35, which disabled inlining of functions that contain closures. ",1.0,"doc/go1.17: document closure inlining affects function PC comparison - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version devel go1.17-d5d24dbe41 Mon Apr 26 17:13:36 2021 +0000 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

only master

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
~/go/src/playground/at-2021-04-26-204402 $ ~/Code/go/bin/go env
GO111MODULE=""on""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/rski/.cache/go-build""
GOENV=""/home/rski/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/rski/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""=""
GOOS=""linux""
GOPATH=""/home/rski/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/home/rski/Code/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/home/rski/Code/go/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""devel go1.17-d5d24dbe41 Mon Apr 26 17:13:36 2021 +0000""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""0""
GOMOD=""/home/rski/go/src/playground/at-2021-04-26-204402/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2782832869=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?

https://play.golang.org/p/Yw1lgRph4Kd

### What did you expect to see?

This should print `main.WithFoo.func1`, as with go 16.3

### What did you see instead?

After the regabi branch merge, this prints 

main.init.func1

This was temporarily fixed by 1129a60f1c1e64147ca1133857c4571ce9b87a35, which disabled inlining of functions that contain closures. ",1,doc      document closure inlining affects function pc comparison         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version            go version  go version devel       mon apr              linux             does this issue reproduce with the latest release     only master        what operating system and processor architecture are you using   go env          go env  output       go env    go src playground at             code go bin go env     on   goarch      gobin     gocache   home rski  cache go build   goenv   home rski  config go env   goexe     goflags     gohostarch      gohostos  linux   goinsecure     gomodcache   home rski go pkg mod   gonoproxy     gonosumdb      goos  linux   gopath   home rski go   goprivate     goproxy     goroot   home rski code go   gosumdb  sum golang org   gotmpdir     gotooldir   home rski code go pkg tool linux     govcs     goversion  devel       mon apr                gccgo  gccgo   ar  ar   cc  gcc   cxx  g     cgo enabled      gomod   home rski go src playground at         go mod   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches             what did you do              what did you expect to see     this should print  main withfoo     as with go            what did you see instead     after the regabi branch merge  this prints     main init      this was temporarily fixed by    which disabled inlining of functions that contain closures  ,1
5946,2993245496.0,IssuesEvent,2015-07-22 01:25:45,golang/go,https://api.github.com/repos/golang/go,closed,doc: clarify that new methods may be added to standard library types,Documentation,"Currently the go1compat document states that exported structs in the standard library may add new fields, but it doesn't mention that they may add new methods too.  To date, every Go release has added new methods to existing types.

For selector expressions, the risk of ambiguity from new methods is the same as for new fields.  But if a new method is added to a standard type that's embedded in a user type, it could cause that user type to no longer satisfy existing interfaces due to ambiguity, which is a risk unique to adding new methods.",1.0,"doc: clarify that new methods may be added to standard library types - Currently the go1compat document states that exported structs in the standard library may add new fields, but it doesn't mention that they may add new methods too.  To date, every Go release has added new methods to existing types.

For selector expressions, the risk of ambiguity from new methods is the same as for new fields.  But if a new method is added to a standard type that's embedded in a user type, it could cause that user type to no longer satisfy existing interfaces due to ambiguity, which is a risk unique to adding new methods.",1,doc  clarify that new methods may be added to standard library types   currently the   document states that exported structs in the standard library may add new fields  but it doesn t mention that they may add new methods too   to date  every go release has added new methods to existing types     for selector expressions  the risk of ambiguity from new methods is the same as for new fields   but if a new method is added to a standard type that s embedded in a user type  it could cause that user type to no longer satisfy existing interfaces due to ambiguity  which is a risk unique to adding new methods ,1
8723,3210522794.0,IssuesEvent,2015-10-06 03:49:18,golang/go,https://api.github.com/repos/golang/go,closed,"tour: clarify what ""export"" means",Documentation,"Context: https://tour.golang.org/basics/3

Change the title above to describe your issue and add your feedback here, including code if necessary

hI

I did not understand the description export.Please provide more clear explanation

regards,ppp ",1.0,"tour: clarify what ""export"" means - Context: https://tour.golang.org/basics/3

Change the title above to describe your issue and add your feedback here, including code if necessary

hI

I did not understand the description export.Please provide more clear explanation

regards,ppp ",1,tour  clarify what  export  means   context       change the title above to describe your issue and add your feedback here  including code if necessary    hi    i did not understand the description export please provide more clear explanation    regards ppp ,1
95612,10883718213.0,IssuesEvent,2019-11-18 06:03:44,golang/go,https://api.github.com/repos/golang/go,closed,wiki: recommended Ubuntu port still does not have security fix release,Documentation NeedsInvestigation help wanted,"Per https://github.com/golang/go/wiki/Ubuntu, the recommended Ubuntu 18.04 apt source is `longsleep/golang-backports`.

As of 5pm Pacific on October 22, that port does not have the Go 1.13.2 or Go 1.13.3 releases.

I'm not sure if this is the right place - if someone on the Go team maintains that package - but it seems bad that a recommended resource is not up to date several days after a security release.

It would be nice to maybe see instructions about what goes into the `.deb` file so we can reproduce it/upload on our own.",1.0,"wiki: recommended Ubuntu port still does not have security fix release - Per https://github.com/golang/go/wiki/Ubuntu, the recommended Ubuntu 18.04 apt source is `longsleep/golang-backports`.

As of 5pm Pacific on October 22, that port does not have the Go 1.13.2 or Go 1.13.3 releases.

I'm not sure if this is the right place - if someone on the Go team maintains that package - but it seems bad that a recommended resource is not up to date several days after a security release.

It would be nice to maybe see instructions about what goes into the `.deb` file so we can reproduce it/upload on our own.",1,wiki  recommended ubuntu port still does not have security fix release   per   the recommended ubuntu     apt source is  longsleep golang backports      as of   pacific on october    that port does not have the go       or go       releases     i m not sure if this is the right place   if someone on the go team maintains that package   but it seems bad that a recommended resource is not up to date several days after a security release     it would be nice to maybe see instructions about what goes into the   deb  file so we can reproduce it upload on our own ,1
49249,26050840883.0,IssuesEvent,2022-12-22 18:29:36,carlocardella/vscode-VirtualRepos,https://api.github.com/repos/carlocardella/vscode-VirtualRepos,closed,Improve startup performance,performance,"Starred repositories call can take a long time to return if a user has a lot of them.
It might be worth caching the list in `globalState` and update it asynchronously after the extension is fully loaded
",True,"Improve startup performance - Starred repositories call can take a long time to return if a user has a lot of them.
It might be worth caching the list in `globalState` and update it asynchronously after the extension is fully loaded
",0,improve startup performance   starred repositories call can take a long time to return if a user has a lot of them  it might be worth caching the list in  globalstate  and update it asynchronously after the extension is fully loaded ,0
14236,24681806928.0,IssuesEvent,2022-10-18 22:12:25,Croquembouche/pyWhat-2022,https://api.github.com/repos/Croquembouche/pyWhat-2022,opened,NFR: Performance,Project Backlog Non-Functional Requirements,"**Estimate:** 5
**Priority:** Must have
**Story**: As a passenger, I want several available drivers to be displayed so that I can choose the most suitable option for me.
**Acceptance criteria:**
1.The app shows drivers that were online within last 20 minutes and don’t have an ongoing ride.
2. The app shows only 5 drivers that are closest to the user.
3. A user can browse profiles of these drivers, including their photos and rates.",1.0,"NFR: Performance - **Estimate:** 5
**Priority:** Must have
**Story**: As a passenger, I want several available drivers to be displayed so that I can choose the most suitable option for me.
**Acceptance criteria:**
1.The app shows drivers that were online within last 20 minutes and don’t have an ongoing ride.
2. The app shows only 5 drivers that are closest to the user.
3. A user can browse profiles of these drivers, including their photos and rates.",0,nfr  performance     estimate         priority    must have    story    as a passenger  i want several available drivers to be displayed so that i can choose the most suitable option for me     acceptance criteria       the app shows drivers that were online within last   minutes and don’t have an ongoing ride      the app shows only   drivers that are closest to the user      a user can browse profiles of these drivers  including their photos and rates ,0
8544,3192980677.0,IssuesEvent,2015-09-30 00:39:21,golang/go,https://api.github.com/repos/golang/go,closed,math/big: Comment for Int.ProbablyPrime() is inaccurate,Documentation,"It says:

```
// ProbablyPrime performs n Miller-Rabin tests to check whether x is prime.
// If it returns true, x is prime with probability 1 - 1/4^n.
// If it returns false, x is not prime.
```

But this is backwards. It should be more like:

```
// ProbablyPrime performs n Miller-Rabin tests to check whether x is prime.
// If x is prime, it returns true.
// If x is not prime, it returns false with probability at least 1 - 1/4^n.
```

See https://en.wikipedia.org/wiki/Miller%E2%80%93Rabin_primality_test#Accuracy_of_the_test for a detailed explanation.

Also, the comment for nat.probablyPrime() needs to be changed similarly.",1.0,"math/big: Comment for Int.ProbablyPrime() is inaccurate - It says:

```
// ProbablyPrime performs n Miller-Rabin tests to check whether x is prime.
// If it returns true, x is prime with probability 1 - 1/4^n.
// If it returns false, x is not prime.
```

But this is backwards. It should be more like:

```
// ProbablyPrime performs n Miller-Rabin tests to check whether x is prime.
// If x is prime, it returns true.
// If x is not prime, it returns false with probability at least 1 - 1/4^n.
```

See https://en.wikipedia.org/wiki/Miller%E2%80%93Rabin_primality_test#Accuracy_of_the_test for a detailed explanation.

Also, the comment for nat.probablyPrime() needs to be changed similarly.",1,math big  comment for int probablyprime   is inaccurate   it says             probablyprime performs n miller rabin tests to check whether x is prime      if it returns true  x is prime with probability         n      if it returns false  x is not prime          but this is backwards  it should be more like             probablyprime performs n miller rabin tests to check whether x is prime      if x is prime  it returns true      if x is not prime  it returns false with probability at least         n          see   for a detailed explanation     also  the comment for nat probablyprime   needs to be changed similarly ,1
172687,6515401446.0,IssuesEvent,2017-08-26 15:17:00,concrete5/concrete5,https://api.github.com/repos/concrete5/concrete5,reopened,Can't handle large number of stacks,inactive:to be verified priority:like to have,"I have added around 110 stacks to website. And I have tested it with 2 different installation.
When Try to add stack to page, everything gets freeze or goes blank screen.

Everytime I get popup with javascript error to continue script or stop script.
",1.0,"Can't handle large number of stacks - I have added around 110 stacks to website. And I have tested it with 2 different installation.
When Try to add stack to page, everything gets freeze or goes blank screen.

Everytime I get popup with javascript error to continue script or stop script.
",0,can t handle large number of stacks   i have added around   stacks to website  and i have tested it with   different installation  when try to add stack to page  everything gets freeze or goes blank screen   everytime i get popup with javascript error to continue script or stop script  ,0
509467,14737200448.0,IssuesEvent,2021-01-07 01:09:16,ChainSafe/forest,https://api.github.com/repos/ChainSafe/forest,closed,Transition from 'Initial Sync' to 'Chain Follow' ,Priority: 2 - High,"**Acceptance Criteria**
- Once 'initial sync' is done, switch the ChainSync state to ChainFollow, which will allow pubsub messages to be processed from the network event channel

**Questions**
- How do we know when intial sync is done? May be worthwhile looking into how Lotus does it.
- Do we need to do another 'Initial Sync' after the first one is done (since it takes a while) before switching 'ChainFollow'?
- The whole time we're doing 'Initial Sync' we're getting gossipsub blocks, what is happening to these? What do we do with them once we switch to 'ChainFollow'?
- How to test this properly? May be difficult 
- Signalling to the ChainSyncer that 'Initial Sync' is done is not trivial.
",1.0,"Transition from 'Initial Sync' to 'Chain Follow'  - **Acceptance Criteria**
- Once 'initial sync' is done, switch the ChainSync state to ChainFollow, which will allow pubsub messages to be processed from the network event channel

**Questions**
- How do we know when intial sync is done? May be worthwhile looking into how Lotus does it.
- Do we need to do another 'Initial Sync' after the first one is done (since it takes a while) before switching 'ChainFollow'?
- The whole time we're doing 'Initial Sync' we're getting gossipsub blocks, what is happening to these? What do we do with them once we switch to 'ChainFollow'?
- How to test this properly? May be difficult 
- Signalling to the ChainSyncer that 'Initial Sync' is done is not trivial.
",0,transition from  initial sync  to  chain follow       acceptance criteria     once  initial sync  is done  switch the chainsync state to chainfollow  which will allow pubsub messages to be processed from the network event channel    questions     how do we know when intial sync is done  may be worthwhile looking into how lotus does it    do we need to do another  initial sync  after the first one is done  since it takes a while  before switching  chainfollow     the whole time we re doing  initial sync  we re getting gossipsub blocks  what is happening to these  what do we do with them once we switch to  chainfollow     how to test this properly  may be difficult    signalling to the chainsyncer that  initial sync  is done is not trivial  ,0
113785,11816310359.0,IssuesEvent,2020-03-20 08:43:54,golang/go,https://api.github.com/repos/golang/go,closed,"x/website: Potential reference to wrong variable name ""TitleValidator""",Documentation NeedsFix help wanted,"While reading this article:

https://golang.org/doc/articles/wiki/

I got to the point where the author is explaining how the `makeHandler` function uses the regex created earlier to validate the `title` provided by the user.

> The closure extracts the title from the request path, and validates it with the `TitleValidator` regexp.

The actual variable name is `validPath`. From the way the explanation is written, it seems that the text should instead be:

> The closure extracts the title from the request path, and validates it with the `validPath` regexp.

---

Many thanks for writing this article. I learned a lot and plan to reference it often as I continue to learn more about Go and writing web apps.",1.0,"x/website: Potential reference to wrong variable name ""TitleValidator"" - While reading this article:

https://golang.org/doc/articles/wiki/

I got to the point where the author is explaining how the `makeHandler` function uses the regex created earlier to validate the `title` provided by the user.

> The closure extracts the title from the request path, and validates it with the `TitleValidator` regexp.

The actual variable name is `validPath`. From the way the explanation is written, it seems that the text should instead be:

> The closure extracts the title from the request path, and validates it with the `validPath` regexp.

---

Many thanks for writing this article. I learned a lot and plan to reference it often as I continue to learn more about Go and writing web apps.",1,x website  potential reference to wrong variable name  titlevalidator    while reading this article          i got to the point where the author is explaining how the  makehandler  function uses the regex created earlier to validate the  title  provided by the user       the closure extracts the title from the request path  and validates it with the  titlevalidator  regexp     the actual variable name is  validpath   from the way the explanation is written  it seems that the text should instead be       the closure extracts the title from the request path  and validates it with the  validpath  regexp            many thanks for writing this article  i learned a lot and plan to reference it often as i continue to learn more about go and writing web apps ,1
408748,11951495077.0,IssuesEvent,2020-04-03 16:59:11,AugurProject/augur,https://api.github.com/repos/AugurProject/augur,closed,disputing form errors,Bug Needed for V2 launch Priority: High,"'null' is showing up in the text input when typing. 

doing "".1"" which should result in an error because it is not in tick size range. the error does not show up but the confirm is disabled. 

also clearing the "".1"" for the outcome clears the rep amount as well. 

seeing these on scalars",1.0,"disputing form errors - 'null' is showing up in the text input when typing. 

doing "".1"" which should result in an error because it is not in tick size range. the error does not show up but the confirm is disabled. 

also clearing the "".1"" for the outcome clears the rep amount as well. 

seeing these on scalars",0,disputing form errors    null  is showing up in the text input when typing      doing      which should result in an error because it is not in tick size range  the error does not show up but the confirm is disabled      also clearing the      for the outcome clears the rep amount as well      seeing these on scalars,0
72911,9631932239.0,IssuesEvent,2019-05-15 15:09:43,golang/go,https://api.github.com/repos/golang/go,opened,cmd/go: GONOPROXY is undocumented,Documentation NeedsFix modules release-blocker,"`GOSUMDB`, `GONOSUMDB`, and `GONOPROXY` variables were added in [CL 173951](https://golang.org/cl/173951).

Documentation for `GOSUMDB` and `GONOSUMDB` was added to https://tip.golang.org/cmd/go/#hdr-Module_authentication_failures, but I don't see any mention of `GONOPROXY` in the `cmd/go` docs at all.

CC @jayconrod @rsc ",1.0,"cmd/go: GONOPROXY is undocumented - `GOSUMDB`, `GONOSUMDB`, and `GONOPROXY` variables were added in [CL 173951](https://golang.org/cl/173951).

Documentation for `GOSUMDB` and `GONOSUMDB` was added to https://tip.golang.org/cmd/go/#hdr-Module_authentication_failures, but I don't see any mention of `GONOPROXY` in the `cmd/go` docs at all.

CC @jayconrod @rsc ",1,cmd go  gonoproxy is undocumented    gosumdb    gonosumdb   and  gonoproxy  variables were added in        documentation for  gosumdb  and  gonosumdb  was added to   but i don t see any mention of  gonoproxy  in the  cmd go  docs at all     cc  jayconrod  rsc ,1
65606,14741046445.0,IssuesEvent,2021-01-07 10:01:04,hiptest/ember-easy-datatable,https://api.github.com/repos/hiptest/ember-easy-datatable,closed,WS-2018-0232 (Medium) detected in underscore.string-2.3.3.tgz - autoclosed,security vulnerability,"## WS-2018-0232 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>underscore.string-2.3.3.tgz</b></p></summary>

<p>String manipulation extensions for Underscore.js javascript library.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/underscore.string/-/underscore.string-2.3.3.tgz"">https://registry.npmjs.org/underscore.string/-/underscore.string-2.3.3.tgz</a></p>
<p>Path to dependency file: ember-easy-datatable/package.json</p>
<p>Path to vulnerable library: ember-easy-datatable/node_modules/ember-cli/node_modules/underscore.string/package.json</p>
<p>

Dependency Hierarchy:
  - ember-cli-2.12.2.tgz (Root Library)
    - quick-temp-0.1.6.tgz
      - :x: **underscore.string-2.3.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/hiptest/ember-easy-datatable/commit/174fc2ea19b9aaaa080440d9cb938d1e9a2d6120"">174fc2ea19b9aaaa080440d9cb938d1e9a2d6120</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>  
  
Underscore.string, before 3.3.5, is vulnerable to Regular Expression Denial of Service (ReDoS).

<p>Publish Date: 2018-10-03
<p>URL: <a href=https://github.com/epeli/underscore.string/commit/f486cd684c94c12db48b45d52b1472a1b9661029>WS-2018-0232</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>5.0</b>)</summary>
<p>

Base Score Metrics not available</p>

</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://www.npmjs.com/advisories/745"">https://www.npmjs.com/advisories/745</a></p>
<p>Release Date: 2018-12-30</p>
<p>Fix Resolution: 3.3.5</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":false,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""underscore.string"",""packageVersion"":""2.3.3"",""isTransitiveDependency"":true,""dependencyTree"":""ember-cli:2.12.2;quick-temp:0.1.6;underscore.string:2.3.3"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""3.3.5""}],""vulnerabilityIdentifier"":""WS-2018-0232"",""vulnerabilityDetails"":""Underscore.string, before 3.3.5, is vulnerable to Regular Expression Denial of Service (ReDoS)."",""vulnerabilityUrl"":""https://github.com/epeli/underscore.string/commit/f486cd684c94c12db48b45d52b1472a1b9661029"",""cvss2Severity"":""medium"",""cvss2Score"":""5.0"",""extraData"":{}}</REMEDIATE> -->",True,"WS-2018-0232 (Medium) detected in underscore.string-2.3.3.tgz - autoclosed - ## WS-2018-0232 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>underscore.string-2.3.3.tgz</b></p></summary>

<p>String manipulation extensions for Underscore.js javascript library.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/underscore.string/-/underscore.string-2.3.3.tgz"">https://registry.npmjs.org/underscore.string/-/underscore.string-2.3.3.tgz</a></p>
<p>Path to dependency file: ember-easy-datatable/package.json</p>
<p>Path to vulnerable library: ember-easy-datatable/node_modules/ember-cli/node_modules/underscore.string/package.json</p>
<p>

Dependency Hierarchy:
  - ember-cli-2.12.2.tgz (Root Library)
    - quick-temp-0.1.6.tgz
      - :x: **underscore.string-2.3.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/hiptest/ember-easy-datatable/commit/174fc2ea19b9aaaa080440d9cb938d1e9a2d6120"">174fc2ea19b9aaaa080440d9cb938d1e9a2d6120</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>  
  
Underscore.string, before 3.3.5, is vulnerable to Regular Expression Denial of Service (ReDoS).

<p>Publish Date: 2018-10-03
<p>URL: <a href=https://github.com/epeli/underscore.string/commit/f486cd684c94c12db48b45d52b1472a1b9661029>WS-2018-0232</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>5.0</b>)</summary>
<p>

Base Score Metrics not available</p>

</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://www.npmjs.com/advisories/745"">https://www.npmjs.com/advisories/745</a></p>
<p>Release Date: 2018-12-30</p>
<p>Fix Resolution: 3.3.5</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":false,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""underscore.string"",""packageVersion"":""2.3.3"",""isTransitiveDependency"":true,""dependencyTree"":""ember-cli:2.12.2;quick-temp:0.1.6;underscore.string:2.3.3"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""3.3.5""}],""vulnerabilityIdentifier"":""WS-2018-0232"",""vulnerabilityDetails"":""Underscore.string, before 3.3.5, is vulnerable to Regular Expression Denial of Service (ReDoS)."",""vulnerabilityUrl"":""https://github.com/epeli/underscore.string/commit/f486cd684c94c12db48b45d52b1472a1b9661029"",""cvss2Severity"":""medium"",""cvss2Score"":""5.0"",""extraData"":{}}</REMEDIATE> -->",0,ws      medium  detected in underscore string       tgz   autoclosed      ws       medium severity vulnerability     vulnerable library    underscore string       tgz      string manipulation extensions for underscore js javascript library    library home page   a href     path to dependency file  ember easy datatable package json   path to vulnerable library  ember easy datatable node modules ember cli node modules underscore string package json     dependency hierarchy      ember cli       tgz  root library        quick temp       tgz          x    underscore string       tgz    vulnerable library   found in head commit   a href     found in base branch   master              vulnerability details         underscore string  before        is vulnerable to regular expression denial of service  redos     publish date         url   a href              cvss   score details             base score metrics not available              suggested fix      type  upgrade version   origin   a href     release date          fix resolution                     isopenpronvulnerability  false  ispackagebased  true  isdefaultbranch  true  packages     vulnerabilityidentifier   ws       vulnerabilitydetails   underscore string  before        is vulnerable to regular expression denial of service  redos     vulnerabilityurl        ,0
26984,6812967566.0,IssuesEvent,2017-11-06 06:59:06,BTDF/DeploymentFramework,https://api.github.com/repos/BTDF/DeploymentFramework,closed,Add GetRegistryValue to BuildTasks and switch registry reads from SDC task to the new task,bug CodePlexMigrationInitiated General Impact: Low Release 5.0,"Add GetRegistryValue to DF.BuildTasks and switch registry reads from the SDC task to the new task.  The SDC task wrote error messages into the output log, which could be misleading.


#### This work item was migrated from CodePlex
CodePlex work item ID: '6316'
Assigned to: 'tfabraham'
Vote count: '0'
",1.0,"Add GetRegistryValue to BuildTasks and switch registry reads from SDC task to the new task - Add GetRegistryValue to DF.BuildTasks and switch registry reads from the SDC task to the new task.  The SDC task wrote error messages into the output log, which could be misleading.


#### This work item was migrated from CodePlex
CodePlex work item ID: '6316'
Assigned to: 'tfabraham'
Vote count: '0'
",0,add getregistryvalue to buildtasks and switch registry reads from sdc task to the new task   add getregistryvalue to df buildtasks and switch registry reads from the sdc task to the new task   the sdc task wrote error messages into the output log  which could be misleading           this work item was migrated from codeplex  codeplex work item id       assigned to   tfabraham   vote count       ,0
317057,23662671297.0,IssuesEvent,2022-08-26 17:11:07,golang/go,https://api.github.com/repos/golang/go,closed,reflect: Value.NumMethod and Type.NumMethod doesn't seem to agree on exported methods,Documentation help wanted NeedsFix,"On e7d5857a5a82551b8a70b6174ec73422442250ce, I see:

```
// NumMethod returns the number of exported methods in the value's method set.
func (v Value) NumMethod() int {
    if v.typ == nil {
        panic(&ValueError{""reflect.Value.NumMethod"", Invalid})
    }
    if v.flag&flagMethod != 0 {
        return 0
    }
    return v.typ.NumMethod()
}
```

Note that `Value.NumMethod` is documented to only return the number of *exported* methods. It calls `Type.NumMethod`, which is documented as:

```
// NumMethod returns the number of methods accessible using Method.
//
// Note that NumMethod counts unexported methods only for interface types.
```

Am I misreading the docs, or do they seem to disagree when it comes to interface types?

cc @dsnet
cc @ianlancetaylor @mdempsky given some past changes regarding `NumMethods` and exported methods",1.0,"reflect: Value.NumMethod and Type.NumMethod doesn't seem to agree on exported methods - On e7d5857a5a82551b8a70b6174ec73422442250ce, I see:

```
// NumMethod returns the number of exported methods in the value's method set.
func (v Value) NumMethod() int {
    if v.typ == nil {
        panic(&ValueError{""reflect.Value.NumMethod"", Invalid})
    }
    if v.flag&flagMethod != 0 {
        return 0
    }
    return v.typ.NumMethod()
}
```

Note that `Value.NumMethod` is documented to only return the number of *exported* methods. It calls `Type.NumMethod`, which is documented as:

```
// NumMethod returns the number of methods accessible using Method.
//
// Note that NumMethod counts unexported methods only for interface types.
```

Am I misreading the docs, or do they seem to disagree when it comes to interface types?

cc @dsnet
cc @ianlancetaylor @mdempsky given some past changes regarding `NumMethods` and exported methods",1,reflect  value nummethod and type nummethod doesn t seem to agree on exported methods   on    i see             nummethod returns the number of exported methods in the value s method set   func  v value  nummethod   int        if v typ    nil            panic  valueerror  reflect value nummethod   invalid               if v flag flagmethod                 return               return v typ nummethod              note that  value nummethod  is documented to only return the number of  exported  methods  it calls  type nummethod   which is documented as             nummethod returns the number of methods accessible using method          note that nummethod counts unexported methods only for interface types          am i misreading the docs  or do they seem to disagree when it comes to interface types     cc  dsnet  cc  ianlancetaylor  mdempsky given some past changes regarding  nummethods  and exported methods,1
26679,5281003805.0,IssuesEvent,2017-02-07 15:32:48,golang/go,https://api.github.com/repos/golang/go,closed,testing: not clear whether parallel tests can run in parallel with themselves,Documentation,"https://golang.org/pkg/testing/#T.Parallel says:

> Parallel signals that this test is to be run in parallel with (and only with) other parallel tests.

Is the test itself included in `other parallel tests`? You could understand that `other` means it's not included, but the wording isn't clear to me or a couple of people I've asked.

This is important because people (including myself) often write parallel tests in a way that they don't break other parallel tests, but not themselves. For example, it might use `t.Name()` as a unique identifier/key in a database.

I ran some quick tests and it does seem like a parallel test never runs in parallel with itself. Will post a doc CL soon.",1.0,"testing: not clear whether parallel tests can run in parallel with themselves - https://golang.org/pkg/testing/#T.Parallel says:

> Parallel signals that this test is to be run in parallel with (and only with) other parallel tests.

Is the test itself included in `other parallel tests`? You could understand that `other` means it's not included, but the wording isn't clear to me or a couple of people I've asked.

This is important because people (including myself) often write parallel tests in a way that they don't break other parallel tests, but not themselves. For example, it might use `t.Name()` as a unique identifier/key in a database.

I ran some quick tests and it does seem like a parallel test never runs in parallel with itself. Will post a doc CL soon.",1,testing  not clear whether parallel tests can run in parallel with themselves     says       parallel signals that this test is to be run in parallel with  and only with  other parallel tests     is the test itself included in  other parallel tests   you could understand that  other  means it s not included  but the wording isn t clear to me or a couple of people i ve asked     this is important because people  including myself  often write parallel tests in a way that they don t break other parallel tests  but not themselves  for example  it might use  t name    as a unique identifier key in a database     i ran some quick tests and it does seem like a parallel test never runs in parallel with itself  will post a doc cl soon ,1
16531,9819170587.0,IssuesEvent,2019-06-13 21:12:20,cucumberlinux/ports,https://api.github.com/repos/cucumberlinux/ports,opened,neovim: CVE-2019-12735,help wanted security,This is indicated as affecting vim. Needs analysis to determine if neovim is also affected.,True,neovim: CVE-2019-12735 - This is indicated as affecting vim. Needs analysis to determine if neovim is also affected.,0,neovim  cve       this is indicated as affecting vim  needs analysis to determine if neovim is also affected ,0
55071,30578365282.0,IssuesEvent,2023-07-21 07:45:08,gemrb/gemrb,https://api.github.com/repos/gemrb/gemrb,closed,Speed up edge map travel,enhancement performance system: pathfinding,">  What I was talking about for the edges is taking another look at Map.cpp's LastGoCloser / CT_GO_CLOSER. In the end Game::EveryoneNearPoint gets called with a single point, so everyone's position is compared to that, not to their closest viable point (projection to the edge).

_Originally posted by @lynxlynxlynx in https://github.com/gemrb/gemrb/issues/1749#issuecomment-1334562533_
      ",True,"Speed up edge map travel - >  What I was talking about for the edges is taking another look at Map.cpp's LastGoCloser / CT_GO_CLOSER. In the end Game::EveryoneNearPoint gets called with a single point, so everyone's position is compared to that, not to their closest viable point (projection to the edge).

_Originally posted by @lynxlynxlynx in https://github.com/gemrb/gemrb/issues/1749#issuecomment-1334562533_
      ",0,speed up edge map travel      what i was talking about for the edges is taking another look at map cpp s lastgocloser   ct go closer  in the end game  everyonenearpoint gets called with a single point  so everyone s position is compared to that  not to their closest viable point  projection to the edge       originally posted by  lynxlynxlynx in          ,0
80706,7754398315.0,IssuesEvent,2018-05-31 06:30:31,adobe/brackets,https://api.github.com/repos/adobe/brackets,closed,"[Remote File] Apart from badge for protocol, the http and https are appended to the remote file if you open the same file with different protocol.",Testing,"### Description
Apart from badge for protocol, the http and https are appended to the remote file if you open the same file with different protocol.

### Steps to Reproduce
1. Launch brackets 1.13.
2. Press ctrl+shift+O for win and cmd+shift+O for mac.
3. Quick open modal bar will open.
4. Enter a network url that supports http. Example: http://www.google.com
4. Enter the same network url using https. Example: https://www.google.com
5. Two files are visible in working files with same name in file tree.
6. Apart from badge for protocol, the http and https are appended to the remote file if you open the same file with different protocol.

![remote file 1](https://user-images.githubusercontent.com/25339865/40157850-ccbd1cf2-59be-11e8-86ac-3f56b2e17633.PNG)

**Expected behavior:** Apart from badge for protocol, the http and https should not be appended to the remote file if you open the same file with different protocol.

**Actual behavior:** Apart from badge for protocol, the http and https are appended to the remote file if you open the same file with different protocol.

### Versions
Win 10 64 Bit
Mac 10.12
Release 1.13 build 1.13.0-17679",1.0,"[Remote File] Apart from badge for protocol, the http and https are appended to the remote file if you open the same file with different protocol. - ### Description
Apart from badge for protocol, the http and https are appended to the remote file if you open the same file with different protocol.

### Steps to Reproduce
1. Launch brackets 1.13.
2. Press ctrl+shift+O for win and cmd+shift+O for mac.
3. Quick open modal bar will open.
4. Enter a network url that supports http. Example: http://www.google.com
4. Enter the same network url using https. Example: https://www.google.com
5. Two files are visible in working files with same name in file tree.
6. Apart from badge for protocol, the http and https are appended to the remote file if you open the same file with different protocol.

![remote file 1](https://user-images.githubusercontent.com/25339865/40157850-ccbd1cf2-59be-11e8-86ac-3f56b2e17633.PNG)

**Expected behavior:** Apart from badge for protocol, the http and https should not be appended to the remote file if you open the same file with different protocol.

**Actual behavior:** Apart from badge for protocol, the http and https are appended to the remote file if you open the same file with different protocol.

### Versions
Win 10 64 Bit
Mac 10.12
Release 1.13 build 1.13.0-17679",0,  apart from badge for protocol  the http and https are appended to the remote file if you open the same file with different protocol        description  apart from badge for protocol  the http and https are appended to the remote file if you open the same file with different protocol         steps to reproduce     launch brackets          press ctrl shift o for win and cmd shift o for mac      quick open modal bar will open      enter a network url that supports http  example        enter the same network url using https  example        two files are visible in working files with same name in file tree      apart from badge for protocol  the http and https are appended to the remote file if you open the same file with different protocol               expected behavior    apart from badge for protocol  the http and https should not be appended to the remote file if you open the same file with different protocol       actual behavior    apart from badge for protocol  the http and https are appended to the remote file if you open the same file with different protocol         versions  win     bit  mac      release     build        ,0
42465,6980426260.0,IssuesEvent,2017-12-13 01:38:48,golang/go,https://api.github.com/repos/golang/go,closed,doc: mention plugins working on Mac,Documentation NeedsFix release-blocker,"According to the unsubmitted https://go-review.googlesource.com/c/go/+/65670 , the plugin package now works on macOS.

If that's true, it should be documented in the Go 1.10 release notes, and that CL should be submitted.

/cc @rsc @ianlancetaylor @crawshaw ",1.0,"doc: mention plugins working on Mac - According to the unsubmitted https://go-review.googlesource.com/c/go/+/65670 , the plugin package now works on macOS.

If that's true, it should be documented in the Go 1.10 release notes, and that CL should be submitted.

/cc @rsc @ianlancetaylor @crawshaw ",1,doc  mention plugins working on mac   according to the unsubmitted     the plugin package now works on macos     if that s true  it should be documented in the go     release notes  and that cl should be submitted      cc  rsc  ianlancetaylor  crawshaw ,1
344436,30746781072.0,IssuesEvent,2023-07-28 15:37:28,elastic/kibana,https://api.github.com/repos/elastic/kibana,closed,Failing test: Jest Integration Tests.src/core/server/integration_tests/saved_objects/migrations/group3 - SO default search fields make sure management types have the correct mappings for default search fields,Team:Core failed-test,"A test failed on a tracked branch

```
Error: Missing version for public endpoint GET /api/observability_onboarding/custom_logs/step/{name}
    at parseEndpoint (/var/lib/buildkite-agent/builds/kb-n2-4-spot-05ef58b5d43908c8/elastic/kibana-on-merge/kibana/packages/kbn-server-route-repository/src/parse_endpoint.ts:23:11)
    at /var/lib/buildkite-agent/builds/kb-n2-4-spot-05ef58b5d43908c8/elastic/kibana-on-merge/kibana/x-pack/plugins/observability_onboarding/server/routes/register_routes.ts:39:47
    at Array.forEach (<anonymous>)
    at forEach (/var/lib/buildkite-agent/builds/kb-n2-4-spot-05ef58b5d43908c8/elastic/kibana-on-merge/kibana/x-pack/plugins/observability_onboarding/server/routes/register_routes.ts:37:10)
    at ObservabilityOnboardingPlugin.setup (/var/lib/buildkite-agent/builds/kb-n2-4-spot-05ef58b5d43908c8/elastic/kibana-on-merge/kibana/x-pack/plugins/observability_onboarding/server/plugin.ts:66:19)
    at PluginWrapper.setup (/var/lib/buildkite-agent/builds/kb-n2-4-spot-05ef58b5d43908c8/elastic/kibana-on-merge/kibana/packages/core/plugins/core-plugins-server-internal/src/plugin.ts:105:26)
    at PluginsSystem.setup [as setupPlugins] (/var/lib/buildkite-agent/builds/kb-n2-4-spot-05ef58b5d43908c8/elastic/kibana-on-merge/kibana/packages/core/plugins/core-plugins-server-internal/src/plugins_system.ts:131:40)
    at PluginsService.setupPlugins [as setup] (/var/lib/buildkite-agent/builds/kb-n2-4-spot-05ef58b5d43908c8/elastic/kibana-on-merge/kibana/packages/core/plugins/core-plugins-server-internal/src/plugins_service.ts:166:52)
    at Server.setup (/var/lib/buildkite-agent/builds/kb-n2-4-spot-05ef58b5d43908c8/elastic/kibana-on-merge/kibana/packages/core/root/core-root-server-internal/src/server.ts:348:26)
    at Root.setup (/var/lib/buildkite-agent/builds/kb-n2-4-spot-05ef58b5d43908c8/elastic/kibana-on-merge/kibana/packages/core/root/core-root-server-internal/src/root/index.ts:66:14)
    at Object.<anonymous> (/var/lib/buildkite-agent/builds/kb-n2-4-spot-05ef58b5d43908c8/elastic/kibana-on-merge/kibana/src/core/server/integration_tests/saved_objects/migrations/group3/default_search_fields.test.ts:31:19)
```

First failure: [CI Build - main](https://buildkite.com/elastic/kibana-on-merge/builds/30745#01884a02-35b0-4943-a777-bd69fc053f9a)

<!-- kibanaCiData = {""failed-test"":{""test.class"":""Jest Integration Tests.src/core/server/integration_tests/saved_objects/migrations/group3"",""test.name"":""SO default search fields make sure management types have the correct mappings for default search fields"",""test.failCount"":3}} -->",1.0,"Failing test: Jest Integration Tests.src/core/server/integration_tests/saved_objects/migrations/group3 - SO default search fields make sure management types have the correct mappings for default search fields - A test failed on a tracked branch

```
Error: Missing version for public endpoint GET /api/observability_onboarding/custom_logs/step/{name}
    at parseEndpoint (/var/lib/buildkite-agent/builds/kb-n2-4-spot-05ef58b5d43908c8/elastic/kibana-on-merge/kibana/packages/kbn-server-route-repository/src/parse_endpoint.ts:23:11)
    at /var/lib/buildkite-agent/builds/kb-n2-4-spot-05ef58b5d43908c8/elastic/kibana-on-merge/kibana/x-pack/plugins/observability_onboarding/server/routes/register_routes.ts:39:47
    at Array.forEach (<anonymous>)
    at forEach (/var/lib/buildkite-agent/builds/kb-n2-4-spot-05ef58b5d43908c8/elastic/kibana-on-merge/kibana/x-pack/plugins/observability_onboarding/server/routes/register_routes.ts:37:10)
    at ObservabilityOnboardingPlugin.setup (/var/lib/buildkite-agent/builds/kb-n2-4-spot-05ef58b5d43908c8/elastic/kibana-on-merge/kibana/x-pack/plugins/observability_onboarding/server/plugin.ts:66:19)
    at PluginWrapper.setup (/var/lib/buildkite-agent/builds/kb-n2-4-spot-05ef58b5d43908c8/elastic/kibana-on-merge/kibana/packages/core/plugins/core-plugins-server-internal/src/plugin.ts:105:26)
    at PluginsSystem.setup [as setupPlugins] (/var/lib/buildkite-agent/builds/kb-n2-4-spot-05ef58b5d43908c8/elastic/kibana-on-merge/kibana/packages/core/plugins/core-plugins-server-internal/src/plugins_system.ts:131:40)
    at PluginsService.setupPlugins [as setup] (/var/lib/buildkite-agent/builds/kb-n2-4-spot-05ef58b5d43908c8/elastic/kibana-on-merge/kibana/packages/core/plugins/core-plugins-server-internal/src/plugins_service.ts:166:52)
    at Server.setup (/var/lib/buildkite-agent/builds/kb-n2-4-spot-05ef58b5d43908c8/elastic/kibana-on-merge/kibana/packages/core/root/core-root-server-internal/src/server.ts:348:26)
    at Root.setup (/var/lib/buildkite-agent/builds/kb-n2-4-spot-05ef58b5d43908c8/elastic/kibana-on-merge/kibana/packages/core/root/core-root-server-internal/src/root/index.ts:66:14)
    at Object.<anonymous> (/var/lib/buildkite-agent/builds/kb-n2-4-spot-05ef58b5d43908c8/elastic/kibana-on-merge/kibana/src/core/server/integration_tests/saved_objects/migrations/group3/default_search_fields.test.ts:31:19)
```

First failure: [CI Build - main](https://buildkite.com/elastic/kibana-on-merge/builds/30745#01884a02-35b0-4943-a777-bd69fc053f9a)

<!-- kibanaCiData = {""failed-test"":{""test.class"":""Jest Integration Tests.src/core/server/integration_tests/saved_objects/migrations/group3"",""test.name"":""SO default search fields make sure management types have the correct mappings for default search fields"",""test.failCount"":3}} -->",0,failing test  jest integration tests src core server integration tests saved objects migrations     so default search fields make sure management types have the correct mappings for default search fields   a test failed on a tracked branch      error  missing version for public endpoint get  api observability onboarding custom logs step  name      at parseendpoint   var lib buildkite agent builds kb     spot   elastic kibana on merge kibana packages kbn server route repository src parse endpoint ts          at  var lib buildkite agent builds kb     spot   elastic kibana on merge kibana x pack plugins observability onboarding server routes register routes ts         at array foreach         at foreach   var lib buildkite agent builds kb     spot   elastic kibana on merge kibana x pack plugins observability onboarding server routes register routes ts          at observabilityonboardingplugin setup   var lib buildkite agent builds kb     spot   elastic kibana on merge kibana x pack plugins observability onboarding server plugin ts          at pluginwrapper setup   var lib buildkite agent builds kb     spot   elastic kibana on merge kibana packages core plugins core plugins server internal src plugin ts          at pluginssystem setup     var lib buildkite agent builds kb     spot   elastic kibana on merge kibana packages core plugins core plugins server internal src plugins system ts          at pluginsservice setupplugins     var lib buildkite agent builds kb     spot   elastic kibana on merge kibana packages core plugins core plugins server internal src plugins service ts          at server setup   var lib buildkite agent builds kb     spot   elastic kibana on merge kibana packages core root core root server internal src server ts          at root setup   var lib buildkite agent builds kb     spot   elastic kibana on merge kibana packages core root core root server internal src root index ts          at object     var lib buildkite agent builds kb     spot   elastic kibana on merge kibana src core server integration tests saved objects migrations   default search fields test ts           first failure        ,0
4386,22317417675.0,IssuesEvent,2022-06-14 00:26:43,carbon-design-system/carbon,https://api.github.com/repos/carbon-design-system/carbon,closed,[a11y]: Radio buttons not working for JAWS screenreader as expected,type: a11y ♿ component: button browser: edge status: needs triage 🕵️‍♀️ status: waiting for maintainer response 💬 screen-reader: JAWS,"### Package

carbon-components

### Browser

Edge

### Operating System

Windows

### Package version

10.56.0

### React version

16.13.1

### Automated testing tool and ruleset

manual test

### Assistive technology

JAWS 2020

### Description

Focus goes to the Carbon radio buttons using JAWS. But when user uses UP/DOWN arrow keys it reads Radio button with label and state and when the user uses UP/DOWN arrow key again the focus navigates to the span text and JAWS reads the label. 

This will confuse screenreader users and also not the expected behaviour of JAWS and radio buttons. 

same issue is reproducible on [Carbon-design radio button](https://www.carbondesignsystem.com/components/radio-button/usage#live-demo)

### WCAG 2.1 Violation

_No response_

### CodeSandbox example

https://codesandbox.io/s/ecstatic-drake-3kcv4e

### Steps to reproduce

1. Using the latest Edge browser and JAWS 2020
2. Navigate to the radio buttons and then just press the down arrow key
3. ISSUE: JAWS reads out the radio label at the input checkbox and then on next down arrow keypress, it reads out the text aswell. 

### Code of Conduct

- [X] I agree to follow this project's [Code of Conduct](https://github.com/carbon-design-system/carbon/blob/f555616971a03fd454c0f4daea184adf41fff05b/.github/CODE_OF_CONDUCT.md)
- [X] I checked the [current issues](https://github.com/carbon-design-system/carbon/issues) for duplicate problems",True,"[a11y]: Radio buttons not working for JAWS screenreader as expected - ### Package

carbon-components

### Browser

Edge

### Operating System

Windows

### Package version

10.56.0

### React version

16.13.1

### Automated testing tool and ruleset

manual test

### Assistive technology

JAWS 2020

### Description

Focus goes to the Carbon radio buttons using JAWS. But when user uses UP/DOWN arrow keys it reads Radio button with label and state and when the user uses UP/DOWN arrow key again the focus navigates to the span text and JAWS reads the label. 

This will confuse screenreader users and also not the expected behaviour of JAWS and radio buttons. 

same issue is reproducible on [Carbon-design radio button](https://www.carbondesignsystem.com/components/radio-button/usage#live-demo)

### WCAG 2.1 Violation

_No response_

### CodeSandbox example

https://codesandbox.io/s/ecstatic-drake-3kcv4e

### Steps to reproduce

1. Using the latest Edge browser and JAWS 2020
2. Navigate to the radio buttons and then just press the down arrow key
3. ISSUE: JAWS reads out the radio label at the input checkbox and then on next down arrow keypress, it reads out the text aswell. 

### Code of Conduct

- [X] I agree to follow this project's [Code of Conduct](https://github.com/carbon-design-system/carbon/blob/f555616971a03fd454c0f4daea184adf41fff05b/.github/CODE_OF_CONDUCT.md)
- [X] I checked the [current issues](https://github.com/carbon-design-system/carbon/issues) for duplicate problems",0,   radio buttons not working for jaws screenreader as expected       package  carbon components      browser  edge      operating system  windows      package version             react version             automated testing tool and ruleset  manual test      assistive technology  jaws        description  focus goes to the carbon radio buttons using jaws  but when user uses up down arrow keys it reads radio button with label and state and when the user uses up down arrow key again the focus navigates to the span text and jaws reads the label      this will confuse screenreader users and also not the expected behaviour of jaws and radio buttons      same issue is reproducible on          wcag     violation   no response       codesandbox example         steps to reproduce     using the latest edge browser and jaws       navigate to the radio buttons and then just press the down arrow key     issue  jaws reads out the radio label at the input checkbox and then on next down arrow keypress  it reads out the text aswell        code of conduct      i agree to follow this project s         i checked the     for duplicate problems,0
389692,26830072290.0,IssuesEvent,2023-02-02 15:26:50,golang/go,https://api.github.com/repos/golang/go,closed,x/website: go1.20 docs refer to strings.Clone as new,Documentation NeedsFix website,"### What did you do?

Visited https://go.dev/doc/go1.20

### What did you expect to see?

No reference to strings.Clone as being new. I believe it was introduced in Go 1.18 for strings (https://go.dev/doc/go1.18) (but in 1.20 for bytes 🙂 )

### What did you see instead?

The following reference to a new function: `The new [Clone](https://go.dev/pkg/strings/#Clone) function allocates a copy of a string.`
",1.0,"x/website: go1.20 docs refer to strings.Clone as new - ### What did you do?

Visited https://go.dev/doc/go1.20

### What did you expect to see?

No reference to strings.Clone as being new. I believe it was introduced in Go 1.18 for strings (https://go.dev/doc/go1.18) (but in 1.20 for bytes 🙂 )

### What did you see instead?

The following reference to a new function: `The new [Clone](https://go.dev/pkg/strings/#Clone) function allocates a copy of a string.`
",1,x website      docs refer to strings clone as new       what did you do     visited          what did you expect to see     no reference to strings clone as being new  i believe it was introduced in go     for strings     but in     for bytes 🙂          what did you see instead     the following reference to a new function   the new     function allocates a copy of a string    ,1
551330,16166273847.0,IssuesEvent,2021-05-01 15:05:29,sopra-fs21-group-01/client,https://api.github.com/repos/sopra-fs21-group-01/client,closed,I can only select a card if it is playable,high priority task,"Implement logic that knows if any of my card is playable

Else: go into logic of drawing cards

Time: 2h

Part of: #5",1.0,"I can only select a card if it is playable - Implement logic that knows if any of my card is playable

Else: go into logic of drawing cards

Time: 2h

Part of: #5",0,i can only select a card if it is playable   implement logic that knows if any of my card is playable    else  go into logic of drawing cards    time       part of    ,0
298167,22466745453.0,IssuesEvent,2022-06-22 02:57:18,golang/go,https://api.github.com/repos/golang/go,closed,cmd/trace: document event trace viewer [freeze exception],Documentation NeedsFix,"https://go-review.googlesource.com/c/go/+/412876 adds documentation to the main page of the cmd/trace event viewer.
This issue is a request that it be granted a freeze exception, since it is essentially an addition of missing user documentation, and has no real impact on the program behavior.

@prattmic @golang/release",1.0,"cmd/trace: document event trace viewer [freeze exception] - https://go-review.googlesource.com/c/go/+/412876 adds documentation to the main page of the cmd/trace event viewer.
This issue is a request that it be granted a freeze exception, since it is essentially an addition of missing user documentation, and has no real impact on the program behavior.

@prattmic @golang/release",1,cmd trace  document event trace viewer       adds documentation to the main page of the cmd trace event viewer   this issue is a request that it be granted a freeze exception  since it is essentially an addition of missing user documentation  and has no real impact on the program behavior      prattmic  golang release,1
28756,11687309785.0,IssuesEvent,2020-03-05 12:34:49,ImpressCMS/impresscms-theme-bootup,https://api.github.com/repos/ImpressCMS/impresscms-theme-bootup,opened,CVE-2018-20677 (Medium) detected in bootstrap-3.3.6-3.3.6.min.js,security vulnerability,"## CVE-2018-20677 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>bootstrap-3.3.6-3.3.6.min.js</b></p></summary>

<p>Google-styled theme for Bootstrap.</p>
<p>Library home page: <a href=""https://cdnjs.cloudflare.com/ajax/libs/todc-bootstrap/3.3.6-3.3.6/js/bootstrap.min.js"">https://cdnjs.cloudflare.com/ajax/libs/todc-bootstrap/3.3.6-3.3.6/js/bootstrap.min.js</a></p>
<p>Path to dependency file: /tmp/ws-scm/impresscms-theme-bootup/theme.html</p>
<p>Path to vulnerable library: /impresscms-theme-bootup/theme.html</p>
<p>

Dependency Hierarchy:
  - :x: **bootstrap-3.3.6-3.3.6.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/ImpressCMS/impresscms-theme-bootup/commit/c254efee6f264850a7b6a3fa3e0b324f0940e9eb"">c254efee6f264850a7b6a3fa3e0b324f0940e9eb</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
In Bootstrap before 3.4.0, XSS is possible in the affix configuration target property.

<p>Publish Date: 2019-01-09
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20677>CVE-2018-20677</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Changed
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20677"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20677</a></p>
<p>Release Date: 2019-01-09</p>
<p>Fix Resolution: Bootstrap - v3.4.0;NorDroN.AngularTemplate - 0.1.6;Dynamic.NET.Express.ProjectTemplates - 0.8.0;dotnetng.template - 1.0.0.4;ZNxtApp.Core.Module.Theme - 1.0.9-Beta;JMeter - 5.0.0</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2018-20677 (Medium) detected in bootstrap-3.3.6-3.3.6.min.js - ## CVE-2018-20677 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>bootstrap-3.3.6-3.3.6.min.js</b></p></summary>

<p>Google-styled theme for Bootstrap.</p>
<p>Library home page: <a href=""https://cdnjs.cloudflare.com/ajax/libs/todc-bootstrap/3.3.6-3.3.6/js/bootstrap.min.js"">https://cdnjs.cloudflare.com/ajax/libs/todc-bootstrap/3.3.6-3.3.6/js/bootstrap.min.js</a></p>
<p>Path to dependency file: /tmp/ws-scm/impresscms-theme-bootup/theme.html</p>
<p>Path to vulnerable library: /impresscms-theme-bootup/theme.html</p>
<p>

Dependency Hierarchy:
  - :x: **bootstrap-3.3.6-3.3.6.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/ImpressCMS/impresscms-theme-bootup/commit/c254efee6f264850a7b6a3fa3e0b324f0940e9eb"">c254efee6f264850a7b6a3fa3e0b324f0940e9eb</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
In Bootstrap before 3.4.0, XSS is possible in the affix configuration target property.

<p>Publish Date: 2019-01-09
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20677>CVE-2018-20677</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Changed
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20677"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20677</a></p>
<p>Release Date: 2019-01-09</p>
<p>Fix Resolution: Bootstrap - v3.4.0;NorDroN.AngularTemplate - 0.1.6;Dynamic.NET.Express.ProjectTemplates - 0.8.0;dotnetng.template - 1.0.0.4;ZNxtApp.Core.Module.Theme - 1.0.9-Beta;JMeter - 5.0.0</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      medium  detected in bootstrap             min js      cve       medium severity vulnerability     vulnerable library    bootstrap             min js      google styled theme for bootstrap    library home page   a href     path to dependency file   tmp ws scm impresscms theme bootup theme html   path to vulnerable library   impresscms theme bootup theme html     dependency hierarchy       x    bootstrap             min js    vulnerable library   found in head commit   a href               vulnerability details         in bootstrap before        xss is possible in the affix configuration target property    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  required     scope  changed   impact metrics      confidentiality impact  low     integrity impact  low     availability impact  none   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  bootstrap         nordron angulartemplate         dynamic net express projecttemplates         dotnetng template           znxtapp core module theme         beta jmeter                       step up your open source security game with whitesource    ,0
266678,20161290865.0,IssuesEvent,2022-02-09 21:52:35,golang/go,https://api.github.com/repos/golang/go,closed,spec: document behavior of type switches containing type parameter cases,Documentation,"Specifically, document behavior when type instantiation leads to duplicate entries in the switch.

From conversation with @danscales:
> I think you may want to specify that a type parameter can be one of the types used in the type(s) of a case, as long as the typeparam satisfies the type of x (based on its bound).   You may want to mention explicitly that there may be duplicate cases after instantiation of a generic function/method with type args, and that is fine.   So, then, the first case matched is chosen.  Duplicate cases are only checked before instantiation.

cc: @danscales ",1.0,"spec: document behavior of type switches containing type parameter cases - Specifically, document behavior when type instantiation leads to duplicate entries in the switch.

From conversation with @danscales:
> I think you may want to specify that a type parameter can be one of the types used in the type(s) of a case, as long as the typeparam satisfies the type of x (based on its bound).   You may want to mention explicitly that there may be duplicate cases after instantiation of a generic function/method with type args, and that is fine.   So, then, the first case matched is chosen.  Duplicate cases are only checked before instantiation.

cc: @danscales ",1,spec  document behavior of type switches containing type parameter cases   specifically  document behavior when type instantiation leads to duplicate entries in the switch     from conversation with  danscales     i think you may want to specify that a type parameter can be one of the types used in the type s  of a case  as long as the typeparam satisfies the type of x  based on its bound     you may want to mention explicitly that there may be duplicate cases after instantiation of a generic function method with type args  and that is fine    so  then  the first case matched is chosen   duplicate cases are only checked before instantiation     cc   danscales ,1
237562,19656686723.0,IssuesEvent,2022-01-10 13:15:29,egc-sierrezuela/decide,https://api.github.com/repos/egc-sierrezuela/decide,closed,Arreglar Coverage GithubActions,type: internal location: backend priority: urgent test,Se ha renombrando el fichero test_navegación.py del modulo auth.,1.0,Arreglar Coverage GithubActions - Se ha renombrando el fichero test_navegación.py del modulo auth.,0,arreglar coverage githubactions   se ha renombrando el fichero test navegación py del modulo auth ,0
435639,30511131430.0,IssuesEvent,2023-07-18 20:56:44,golang/go,https://api.github.com/repos/golang/go,opened,doc: write release notes for Go 1.22,Documentation NeedsFix release-blocker umbrella,"This is the tracking issue for writing the Go 1.22 Release Notes. The version at tip can be viewed at https://tip.golang.org/doc/go1.22.

When the Go 1.22 Release Notes are complete, this should be closed, and a similar issue should be made for the next release. The previous issue was #58645.",1.0,"doc: write release notes for Go 1.22 - This is the tracking issue for writing the Go 1.22 Release Notes. The version at tip can be viewed at https://tip.golang.org/doc/go1.22.

When the Go 1.22 Release Notes are complete, this should be closed, and a similar issue should be made for the next release. The previous issue was #58645.",1,doc  write release notes for go       this is the tracking issue for writing the go     release notes  the version at tip can be viewed at      when the go     release notes are complete  this should be closed  and a similar issue should be made for the next release  the previous issue was    ,1
47006,7298966897.0,IssuesEvent,2018-02-26 18:36:23,golang/go,https://api.github.com/repos/golang/go,closed,unsafe: wrong type mentioned in explanation,Documentation NeedsFix help wanted,"> In this usage hdr.Data is really an alternate way to refer to the underlying pointer in the **slice** header, not a uintptr variable itself. 

**slice** should be **string**",1.0,"unsafe: wrong type mentioned in explanation - > In this usage hdr.Data is really an alternate way to refer to the underlying pointer in the **slice** header, not a uintptr variable itself. 

**slice** should be **string**",1,unsafe  wrong type mentioned in explanation     in this usage hdr data is really an alternate way to refer to the underlying pointer in the   slice   header  not a uintptr variable itself        slice   should be   string  ,1
72502,15238175877.0,IssuesEvent,2021-02-19 01:17:13,devikab2b/whites6,https://api.github.com/repos/devikab2b/whites6,closed,CVE-2019-10202 (High) detected in jackson-mapper-asl-1.9.13.jar - autoclosed,security vulnerability,"## CVE-2019-10202 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-mapper-asl-1.9.13.jar</b></p></summary>

<p>Data Mapper package is a high-performance data binding package
built on Jackson JSON processor</p>
<p>Path to dependency file: whites6/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/codehaus/jackson/jackson-mapper-asl/1.9.13/jackson-mapper-asl-1.9.13.jar</p>
<p>

Dependency Hierarchy:
  - spark-core_2.12-3.1.0.jar (Root Library)
    - avro-1.8.2.jar
      - :x: **jackson-mapper-asl-1.9.13.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/devikab2b/whites6/commit/3431e4533a715722c70a575c74c47499f680f6a2"">3431e4533a715722c70a575c74c47499f680f6a2</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>  
  
A series of deserialization vulnerabilities have been discovered in Codehaus 1.9.x implemented in EAP 7. This CVE fixes CVE-2017-17485, CVE-2017-7525, CVE-2017-15095, CVE-2018-5968, CVE-2018-7489, CVE-2018-1000873, CVE-2019-12086 reported for FasterXML jackson-databind by implementing a whitelist approach that will mitigate these vulnerabilities and future ones alike.

<p>Publish Date: 2019-10-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10202>CVE-2019-10202</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://access.redhat.com/errata/RHSA-2019:2938"">https://access.redhat.com/errata/RHSA-2019:2938</a></p>
<p>Release Date: 2019-10-01</p>
<p>Fix Resolution: JBoss Enterprise Application Platform - 7.2.4;com.fasterxml.jackson.core:jackson-databind:2.9.9</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2019-10202 (High) detected in jackson-mapper-asl-1.9.13.jar - autoclosed - ## CVE-2019-10202 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-mapper-asl-1.9.13.jar</b></p></summary>

<p>Data Mapper package is a high-performance data binding package
built on Jackson JSON processor</p>
<p>Path to dependency file: whites6/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/codehaus/jackson/jackson-mapper-asl/1.9.13/jackson-mapper-asl-1.9.13.jar</p>
<p>

Dependency Hierarchy:
  - spark-core_2.12-3.1.0.jar (Root Library)
    - avro-1.8.2.jar
      - :x: **jackson-mapper-asl-1.9.13.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/devikab2b/whites6/commit/3431e4533a715722c70a575c74c47499f680f6a2"">3431e4533a715722c70a575c74c47499f680f6a2</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>  
  
A series of deserialization vulnerabilities have been discovered in Codehaus 1.9.x implemented in EAP 7. This CVE fixes CVE-2017-17485, CVE-2017-7525, CVE-2017-15095, CVE-2018-5968, CVE-2018-7489, CVE-2018-1000873, CVE-2019-12086 reported for FasterXML jackson-databind by implementing a whitelist approach that will mitigate these vulnerabilities and future ones alike.

<p>Publish Date: 2019-10-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10202>CVE-2019-10202</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://access.redhat.com/errata/RHSA-2019:2938"">https://access.redhat.com/errata/RHSA-2019:2938</a></p>
<p>Release Date: 2019-10-01</p>
<p>Fix Resolution: JBoss Enterprise Application Platform - 7.2.4;com.fasterxml.jackson.core:jackson-databind:2.9.9</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in jackson mapper asl       jar   autoclosed      cve       high severity vulnerability     vulnerable library    jackson mapper asl       jar      data mapper package is a high performance data binding package built on jackson json processor   path to dependency file    pom xml   path to vulnerable library   home wss scanner    repository org codehaus jackson jackson mapper asl       jackson mapper asl       jar     dependency hierarchy      spark core           jar  root library        avro       jar          x    jackson mapper asl       jar    vulnerable library   found in head commit   a href     found in base branch   main              vulnerability details         a series of deserialization vulnerabilities have been discovered in codehaus     x implemented in eap    this cve fixes cve      cve      cve      cve      cve      cve      cve     reported for fasterxml jackson databind by implementing a whitelist approach that will mitigate these vulnerabilities and future ones alike    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  jboss enterprise application platform         com fasterxml jackson core jackson databind                     step up your open source security game with whitesource    ,0
213073,16497031861.0,IssuesEvent,2021-05-25 11:27:44,realm/realm-js,https://api.github.com/repos/realm/realm-js,closed,Improvements to the test harness,Epic Pipeline-On-Hold T-Test,"## Goals

Realm Studio has [been experiencing regressions](https://github.com/realm/realm-js/issues/1864) and I believe improvements to the test harness will help fix this:
- [x] We should run all tests from multiple environments:
  - [x] Node.js
  - [ ] Electron on MacOS
  - [x] Electron on Linux
  - [ ] Electron on Windows
  - [x] React Native on Android
  - [x] React Native on iOS
  - [ ] React Native in debug mode (runs in Chrome)
- [x] We should use mocha instead of jasmine, as we are using this everywhere else and not rely on our own assertion library but instead use chai.
- [ ] ~The server should be started and stopped for each test to prevent cross-talking between tests.~
- [ ] Write tests of installing Realm from scratch into the latest version of various environments (should not fail the build if an issue is found):
  - [ ] Electron: Install the latest available version of Electron and `electron-builder`, install the Realm JS package and use Realm JS for something simple.
  - [ ] React Native: Install the latest version of `react-native` CLI, create an app, install the Realm JS package, run `react-native link realm`, build the app and use Realm JS for something simple.
- [x] Use TypeScript when implementing the test suite.

## Version of Realm and Tooling

- Realm JS SDK Version: 2.13.0
- Node or React Native: N/A
- Client OS & Version: N/A
- Which debugger for React Native: N/A",1.0,"Improvements to the test harness - ## Goals

Realm Studio has [been experiencing regressions](https://github.com/realm/realm-js/issues/1864) and I believe improvements to the test harness will help fix this:
- [x] We should run all tests from multiple environments:
  - [x] Node.js
  - [ ] Electron on MacOS
  - [x] Electron on Linux
  - [ ] Electron on Windows
  - [x] React Native on Android
  - [x] React Native on iOS
  - [ ] React Native in debug mode (runs in Chrome)
- [x] We should use mocha instead of jasmine, as we are using this everywhere else and not rely on our own assertion library but instead use chai.
- [ ] ~The server should be started and stopped for each test to prevent cross-talking between tests.~
- [ ] Write tests of installing Realm from scratch into the latest version of various environments (should not fail the build if an issue is found):
  - [ ] Electron: Install the latest available version of Electron and `electron-builder`, install the Realm JS package and use Realm JS for something simple.
  - [ ] React Native: Install the latest version of `react-native` CLI, create an app, install the Realm JS package, run `react-native link realm`, build the app and use Realm JS for something simple.
- [x] Use TypeScript when implementing the test suite.

## Version of Realm and Tooling

- Realm JS SDK Version: 2.13.0
- Node or React Native: N/A
- Client OS & Version: N/A
- Which debugger for React Native: N/A",0,improvements to the test harness      goals  realm studio has     and i believe improvements to the test harness will help fix this      we should run all tests from multiple environments        node js       electron on macos       electron on linux       electron on windows       react native on android       react native on ios       react native in debug mode  runs in chrome      we should use mocha instead of jasmine  as we are using this everywhere else and not rely on our own assertion library but instead use chai       the server should be started and stopped for each test to prevent cross talking between tests       write tests of installing realm from scratch into the latest version of various environments  should not fail the build if an issue is found         electron  install the latest available version of electron and  electron builder   install the realm js package and use realm js for something simple        react native  install the latest version of  react native  cli  create an app  install the realm js package  run  react native link realm   build the app and use realm js for something simple      use typescript when implementing the test suite      version of realm and tooling    realm js sdk version          node or react native  n a   client os   version  n a   which debugger for react native  n a,0
54334,7883360324.0,IssuesEvent,2018-06-27 04:31:01,golang/go,https://api.github.com/repos/golang/go,closed,cmd/link: failed to set variable at build time if variable value is result from method call,Documentation NeedsFix help wanted,"Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
go version go1.10.3 linux/amd64

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/cuonglm/.cache/go-build""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/cuonglm/go""
GORACE=""""
GOROOT=""/home/cuonglm/sources/go""
GOTMPDIR=""""
GOTOOLDIR=""/home/cuonglm/sources/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build755255777=/tmp/go-build -gno-record-gcc-switches""
```

### What did you do?
https://play.golang.org/p/M9xGmognyrl

run as:

```
go run -ldflags ""-X main.X=y -X main.MyX=myY"" main.go
```
### What did you expect to see?
```
y
myY
```

### What did you see instead?
```
y
myX
```
",1.0,"cmd/link: failed to set variable at build time if variable value is result from method call - Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
go version go1.10.3 linux/amd64

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/cuonglm/.cache/go-build""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/cuonglm/go""
GORACE=""""
GOROOT=""/home/cuonglm/sources/go""
GOTMPDIR=""""
GOTOOLDIR=""/home/cuonglm/sources/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build755255777=/tmp/go-build -gno-record-gcc-switches""
```

### What did you do?
https://play.golang.org/p/M9xGmognyrl

run as:

```
go run -ldflags ""-X main.X=y -X main.MyX=myY"" main.go
```
### What did you expect to see?
```
y
myY
```

### What did you see instead?
```
y
myX
```
",1,cmd link  failed to set variable at build time if variable value is result from method call   please answer these questions before submitting your issue  thanks           what version of go are you using   go version     go version       linux          does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env          goarch      gobin     gocache   home cuonglm  cache go build   goexe     gohostarch      gohostos  linux   goos  linux   gopath   home cuonglm go   gorace     goroot   home cuonglm sources go   gotmpdir     gotooldir   home cuonglm sources go pkg tool linux     gccgo  gccgo   cc  gcc   cxx  g     cgo enabled      cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches              what did you do        run as          go run  ldflags   x main x y  x main myx myy  main go           what did you expect to see        y  myy             what did you see instead        y  myx       ,1
407745,11936810433.0,IssuesEvent,2020-04-02 11:00:03,threefoldfoundation/tft-stellar,https://api.github.com/repos/threefoldfoundation/tft-stellar,opened,Freetft faucet,priority_critical type_story,"Website where you acquire 1000 FreeTFT's on 3bot connect login.
A user can only receive hem once for now",1.0,"Freetft faucet - Website where you acquire 1000 FreeTFT's on 3bot connect login.
A user can only receive hem once for now",0,freetft faucet   website where you acquire   freetft s on   connect login   a user can only receive hem once for now,0
259237,27621756950.0,IssuesEvent,2023-03-10 01:09:22,jeduardo824/map,https://api.github.com/repos/jeduardo824/map,opened,CVE-2022-44570 (High) detected in rack-2.0.7.gem,Mend: dependency security vulnerability,"## CVE-2022-44570 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>rack-2.0.7.gem</b></p></summary>

<p>Rack provides a minimal, modular and adaptable interface for developing
web applications in Ruby.  By wrapping HTTP requests and responses in
the simplest way possible, it unifies and distills the API for web
servers, web frameworks, and software in between (the so-called
middleware) into a single method call.

Also see https://rack.github.io/.
</p>
<p>Library home page: <a href=""https://rubygems.org/gems/rack-2.0.7.gem"">https://rubygems.org/gems/rack-2.0.7.gem</a></p>
<p>Path to dependency file: /map/Gemfile.lock</p>
<p>Path to vulnerable library: /var/lib/gems/2.3.0/cache/rack-2.0.7.gem</p>
<p>

Dependency Hierarchy:
  - capybara-3.18.0.gem (Root Library)
    - :x: **rack-2.0.7.gem** (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 denial of service vulnerability in the Range header parsing component of Rack >= 1.5.0. A Carefully crafted input can cause the Range header parsing component in Rack to take an unexpected amount of time, possibly resulting in a denial of service attack vector. Any applications that deal with Range requests (such as streaming applications, or applications that serve files) may be impacted.

<p>Publish Date: 2023-02-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-44570>CVE-2022-44570</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/advisories/GHSA-65f5-mfpf-vfhj"">https://github.com/advisories/GHSA-65f5-mfpf-vfhj</a></p>
<p>Release Date: 2023-02-09</p>
<p>Fix Resolution: rack - 2.0.9.2,2.1.4.2,2.2.6.2,3.0.4.1</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2022-44570 (High) detected in rack-2.0.7.gem - ## CVE-2022-44570 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>rack-2.0.7.gem</b></p></summary>

<p>Rack provides a minimal, modular and adaptable interface for developing
web applications in Ruby.  By wrapping HTTP requests and responses in
the simplest way possible, it unifies and distills the API for web
servers, web frameworks, and software in between (the so-called
middleware) into a single method call.

Also see https://rack.github.io/.
</p>
<p>Library home page: <a href=""https://rubygems.org/gems/rack-2.0.7.gem"">https://rubygems.org/gems/rack-2.0.7.gem</a></p>
<p>Path to dependency file: /map/Gemfile.lock</p>
<p>Path to vulnerable library: /var/lib/gems/2.3.0/cache/rack-2.0.7.gem</p>
<p>

Dependency Hierarchy:
  - capybara-3.18.0.gem (Root Library)
    - :x: **rack-2.0.7.gem** (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 denial of service vulnerability in the Range header parsing component of Rack >= 1.5.0. A Carefully crafted input can cause the Range header parsing component in Rack to take an unexpected amount of time, possibly resulting in a denial of service attack vector. Any applications that deal with Range requests (such as streaming applications, or applications that serve files) may be impacted.

<p>Publish Date: 2023-02-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-44570>CVE-2022-44570</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/advisories/GHSA-65f5-mfpf-vfhj"">https://github.com/advisories/GHSA-65f5-mfpf-vfhj</a></p>
<p>Release Date: 2023-02-09</p>
<p>Fix Resolution: rack - 2.0.9.2,2.1.4.2,2.2.6.2,3.0.4.1</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in rack       gem      cve       high severity vulnerability     vulnerable library    rack       gem      rack provides a minimal  modular and adaptable interface for developing web applications in ruby   by wrapping http requests and responses in the simplest way possible  it unifies and distills the api for web servers  web frameworks  and software in between  the so called middleware  into a single method call   also see      library home page   a href     path to dependency file   map gemfile lock   path to vulnerable library   var lib gems       cache rack       gem     dependency hierarchy      capybara       gem  root library         x    rack       gem    vulnerable library             vulnerability details         a denial of service vulnerability in the range header parsing component of rack           a carefully crafted input can cause the range header parsing component in rack to take an unexpected amount of time  possibly resulting in a denial of service attack vector  any applications that deal with range requests  such as streaming applications  or applications that serve files  may be impacted    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  rack                                                 step up your open source security game with mend    ,0
34865,14533489336.0,IssuesEvent,2020-12-15 00:41:26,hashicorp/terraform-provider-aws,https://api.github.com/repos/hashicorp/terraform-provider-aws,closed,Crashing with: Error: rpc error: code = Unavailable desc = transport is closing ,bug crash service/workspaces,"<!---
Please note the following potential times when an issue might be in Terraform core:

* [Configuration Language](https://www.terraform.io/docs/configuration/index.html) or resource ordering issues
* [State](https://www.terraform.io/docs/state/index.html) and [State Backend](https://www.terraform.io/docs/backends/index.html) issues
* [Provisioner](https://www.terraform.io/docs/provisioners/index.html) issues
* [Registry](https://registry.terraform.io/) issues
* Spans resources across multiple providers

If you are running into one of these scenarios, we recommend opening an issue in the [Terraform core repository](https://github.com/hashicorp/terraform/) instead.
--->

<!--- Please keep this note for the community --->

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave ""+1"" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

<!--- Thank you for keeping this note for the community --->

### Terraform CLI and Terraform AWS Provider Version
Terraform v0.14.2 + provider registry.terraform.io/hashicorp/aws v3.20.0


### Affected Resource(s)

* aws_workspaces_directory
* aws_workspaces_workspace
* aws_directory_service_directory

### Terraform Configuration Files


```resource ""aws_workspaces_directory"" ""anotherworkspace"" {
  directory_id = aws_directory_service_directory.anotherworkspace.id
  subnet_ids   = [""subnet-xxxxxxxx"", ""subnet-yyyyyyyyyyyy""]
  #subnet_ids   = [""data.terraform_remote_state.network.public_subnets""]
  
  workspace_creation_properties {
    enable_internet_access = true
    enable_maintenance_mode = true
    #user_enabled_as_local_administrator = false
  }
}

data ""aws_workspaces_bundle"" ""w10_terraform_test"" {
  bundle_id = ""wsb-5rw9k8l9c"" # Value with Windows 10 (English)
}
```

### Debug Output

```
Error: rpc error: code = Unavailable desc = transport is closing

```

### Panic Output


### Expected Behavior

Should at least run plan without error.

### Actual Behavior

Getting the error below:
`Error: rpc error: code = Unavailable desc = transport is closing
`

### Steps to Reproduce


1. `terraform plan`

### Important Factoids
It happens all the time.
I can't even get to ``terraform apply`` as it happens during ``terraform plan``

### References


* #0000
",1.0,"Crashing with: Error: rpc error: code = Unavailable desc = transport is closing  - <!---
Please note the following potential times when an issue might be in Terraform core:

* [Configuration Language](https://www.terraform.io/docs/configuration/index.html) or resource ordering issues
* [State](https://www.terraform.io/docs/state/index.html) and [State Backend](https://www.terraform.io/docs/backends/index.html) issues
* [Provisioner](https://www.terraform.io/docs/provisioners/index.html) issues
* [Registry](https://registry.terraform.io/) issues
* Spans resources across multiple providers

If you are running into one of these scenarios, we recommend opening an issue in the [Terraform core repository](https://github.com/hashicorp/terraform/) instead.
--->

<!--- Please keep this note for the community --->

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave ""+1"" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

<!--- Thank you for keeping this note for the community --->

### Terraform CLI and Terraform AWS Provider Version
Terraform v0.14.2 + provider registry.terraform.io/hashicorp/aws v3.20.0


### Affected Resource(s)

* aws_workspaces_directory
* aws_workspaces_workspace
* aws_directory_service_directory

### Terraform Configuration Files


```resource ""aws_workspaces_directory"" ""anotherworkspace"" {
  directory_id = aws_directory_service_directory.anotherworkspace.id
  subnet_ids   = [""subnet-xxxxxxxx"", ""subnet-yyyyyyyyyyyy""]
  #subnet_ids   = [""data.terraform_remote_state.network.public_subnets""]
  
  workspace_creation_properties {
    enable_internet_access = true
    enable_maintenance_mode = true
    #user_enabled_as_local_administrator = false
  }
}

data ""aws_workspaces_bundle"" ""w10_terraform_test"" {
  bundle_id = ""wsb-5rw9k8l9c"" # Value with Windows 10 (English)
}
```

### Debug Output

```
Error: rpc error: code = Unavailable desc = transport is closing

```

### Panic Output


### Expected Behavior

Should at least run plan without error.

### Actual Behavior

Getting the error below:
`Error: rpc error: code = Unavailable desc = transport is closing
`

### Steps to Reproduce


1. `terraform plan`

### Important Factoids
It happens all the time.
I can't even get to ``terraform apply`` as it happens during ``terraform plan``

### References


* #0000
",0,crashing with  error  rpc error  code   unavailable desc   transport is closing           please note the following potential times when an issue might be in terraform core           or resource ordering issues        and     issues        issues        issues    spans resources across multiple providers    if you are running into one of these scenarios  we recommend opening an issue in the     instead                    community note      please vote on this issue by adding a 👍     to the original issue to help the community and maintainers prioritize this request    please do not leave      or other comments that do not add relevant new information or questions  they generate extra noise for issue followers and do not help prioritize the request    if you are interested in working on this issue or have submitted a pull request  please leave a comment             terraform cli and terraform aws provider version  terraform         provider registry terraform io hashicorp aws                affected resource s       aws workspaces directory    aws workspaces workspace    aws directory service directory        terraform configuration files         resource  aws workspaces directory   anotherworkspace       directory id   aws directory service directory anotherworkspace id    subnet ids           subnet ids              workspace creation properties        enable internet access   true      enable maintenance mode   true       user enabled as local administrator   false            data  aws workspaces bundle     terraform test       bundle id    wsb      value with windows    english                 debug output         error  rpc error  code   unavailable desc   transport is closing               panic output          expected behavior    should at least run plan without error         actual behavior    getting the error below    error  rpc error  code   unavailable desc   transport is closing           steps to reproduce          terraform plan         important factoids  it happens all the time   i can t even get to   terraform apply   as it happens during   terraform plan          references            ,0
124931,26560992832.0,IssuesEvent,2023-01-20 15:51:10,trezor/trezor-suite,https://api.github.com/repos/trezor/trezor-suite,opened,Use utilityProcess instead of child_process in BaseProcess,code,"newly available from Electron v22
https://www.electronjs.org/docs/latest/api/utility-process

Currently we have an issue with stdio options:
- 'pipe' can lead to buffer overload https://github.com/trezor/trezor-suite/issues/4306
- 'inherit' open CMD on Windows https://github.com/trezor/trezor-suite/issues/7375",1.0,"Use utilityProcess instead of child_process in BaseProcess - newly available from Electron v22
https://www.electronjs.org/docs/latest/api/utility-process

Currently we have an issue with stdio options:
- 'pipe' can lead to buffer overload https://github.com/trezor/trezor-suite/issues/4306
- 'inherit' open CMD on Windows https://github.com/trezor/trezor-suite/issues/7375",0,use utilityprocess instead of child process in baseprocess   newly available from electron         currently we have an issue with stdio options      pipe  can lead to buffer overload       inherit  open cmd on windows  ,0
135305,18678891828.0,IssuesEvent,2021-11-01 01:02:23,benchmarkdebricked/kubernetes,https://api.github.com/repos/benchmarkdebricked/kubernetes,opened,CVE-2020-26160 (High) detected in kubernetesv1.16.0-alpha.0,security vulnerability,"## CVE-2020-26160 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>kubernetesv1.16.0-alpha.0</b></p></summary>
<p>

<p>Production-Grade Container Scheduling and Management</p>
<p>Library home page: <a href=https://github.com/kubernetes/kubernetes.git>https://github.com/kubernetes/kubernetes.git</a></p>
</p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (3)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>kubernetes/vendor/github.com/dgrijalva/jwt-go/map_claims.go</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>kubernetes/vendor/github.com/dgrijalva/jwt-go/claims.go</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>kubernetes/vendor/github.com/dgrijalva/jwt-go/map_claims.go</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
jwt-go before 4.0.0-preview1 allows attackers to bypass intended access restrictions in situations with []string{} for m[""aud""] (which is allowed by the specification). Because the type assertion fails, """" is the value of aud. This is a security problem if the JWT token is presented to a service that lacks its own audience check.

<p>Publish Date: 2020-09-30
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-26160>CVE-2020-26160</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: High
  - Integrity Impact: None
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2020-26160"">https://nvd.nist.gov/vuln/detail/CVE-2020-26160</a></p>
<p>Release Date: 2020-09-30</p>
<p>Fix Resolution: v4.0.0-preview1</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-26160 (High) detected in kubernetesv1.16.0-alpha.0 - ## CVE-2020-26160 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>kubernetesv1.16.0-alpha.0</b></p></summary>
<p>

<p>Production-Grade Container Scheduling and Management</p>
<p>Library home page: <a href=https://github.com/kubernetes/kubernetes.git>https://github.com/kubernetes/kubernetes.git</a></p>
</p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (3)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>kubernetes/vendor/github.com/dgrijalva/jwt-go/map_claims.go</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>kubernetes/vendor/github.com/dgrijalva/jwt-go/claims.go</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>kubernetes/vendor/github.com/dgrijalva/jwt-go/map_claims.go</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
jwt-go before 4.0.0-preview1 allows attackers to bypass intended access restrictions in situations with []string{} for m[""aud""] (which is allowed by the specification). Because the type assertion fails, """" is the value of aud. This is a security problem if the JWT token is presented to a service that lacks its own audience check.

<p>Publish Date: 2020-09-30
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-26160>CVE-2020-26160</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: High
  - Integrity Impact: None
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2020-26160"">https://nvd.nist.gov/vuln/detail/CVE-2020-26160</a></p>
<p>Release Date: 2020-09-30</p>
<p>Fix Resolution: v4.0.0-preview1</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in       alpha        cve       high severity vulnerability     vulnerable library          alpha          production grade container scheduling and management   library home page   a href              vulnerable source files                 kubernetes vendor github com dgrijalva jwt go map claims go       kubernetes vendor github com dgrijalva jwt go claims go       kubernetes vendor github com dgrijalva jwt go map claims go                    vulnerability details         jwt go before         allows attackers to bypass intended access restrictions in situations with  string   for m   which is allowed by the specification   because the type assertion fails     is the value of aud  this is a security problem if the jwt token is presented to a service that lacks its own audience check    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  none     availability impact  none   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                        step up your open source security game with whitesource    ,0
248142,7927862896.0,IssuesEvent,2018-07-06 09:31:33,aiidateam/aiida_core,https://api.github.com/repos/aiidateam/aiida_core,opened,`verdi code setup` allows to setup code with identical name on same computer,priority/important topic/VerdiCommandLine type/bug,"Currently it is possible to create two codes with an identical name on the same computer, e.g. `doubler@localhost` and `verdi code setup` will not complain. However, loading either of these codes will then be impossible because the loader will always throw an `MultipleObjectsError`",1.0,"`verdi code setup` allows to setup code with identical name on same computer - Currently it is possible to create two codes with an identical name on the same computer, e.g. `doubler@localhost` and `verdi code setup` will not complain. However, loading either of these codes will then be impossible because the loader will always throw an `MultipleObjectsError`",0, verdi code setup  allows to setup code with identical name on same computer   currently it is possible to create two codes with an identical name on the same computer  e g   doubler localhost  and  verdi code setup  will not complain  however  loading either of these codes will then be impossible because the loader will always throw an  multipleobjectserror ,0
33405,6201012868.0,IssuesEvent,2017-07-06 03:54:12,golang/go,https://api.github.com/repos/golang/go,closed,time: cannot roundtrip Parse the Time.String output,Documentation NeedsFix,"On tip, the documentation of `Time.String` says:
> String returns the time formatted using the format string: ""2006-01-02 15:04:05.999999999 -0700 MST""

This is misleading since it suggests that the following should work:
```go
time.Parse(""2006-01-02 15:04:05.999999999 -0700 MST"", time.Now().String())
```

However, this does not work on Go1.9 since:
```
parsing time ""2017-06-30 17:31:36.969388848 -0700 PDT m=+0.004118679"": extra text:  m=+0.004118679
```

We should done one of the following:
* Say that round-trip parsing does not work and fix the documentation on `Time.String` to not suggest that the format string is `""2006-01-02 15:04:05.999999999 -0700 MST""`. We can suggest that `String` is intended only for human consumption and is not meant to be machine readable.
* Or fix the API for `Parse`, such that the monotonic timestamps can be ignored.

\cc @bradfitz @rsc ",1.0,"time: cannot roundtrip Parse the Time.String output - On tip, the documentation of `Time.String` says:
> String returns the time formatted using the format string: ""2006-01-02 15:04:05.999999999 -0700 MST""

This is misleading since it suggests that the following should work:
```go
time.Parse(""2006-01-02 15:04:05.999999999 -0700 MST"", time.Now().String())
```

However, this does not work on Go1.9 since:
```
parsing time ""2017-06-30 17:31:36.969388848 -0700 PDT m=+0.004118679"": extra text:  m=+0.004118679
```

We should done one of the following:
* Say that round-trip parsing does not work and fix the documentation on `Time.String` to not suggest that the format string is `""2006-01-02 15:04:05.999999999 -0700 MST""`. We can suggest that `String` is intended only for human consumption and is not meant to be machine readable.
* Or fix the API for `Parse`, such that the monotonic timestamps can be ignored.

\cc @bradfitz @rsc ",1,time  cannot roundtrip parse the time string output   on tip  the documentation of  time string  says     string returns the time formatted using the format string                    mst     this is misleading since it suggests that the following should work      go  time parse                   mst   time now   string            however  this does not work on     since        parsing time                   pdt m        extra text   m              we should done one of the following     say that round trip parsing does not work and fix the documentation on  time string  to not suggest that the format string is                    mst    we can suggest that  string  is intended only for human consumption and is not meant to be machine readable     or fix the api for  parse   such that the monotonic timestamps can be ignored      cc  bradfitz  rsc ,1
72461,24126645692.0,IssuesEvent,2022-09-21 01:30:53,idaholab/moose,https://api.github.com/repos/idaholab/moose,closed,VolumetricFlowRate fails on internal boundaries that are cut by domain boundaries,T: defect P: normal C: Modules/Navier Stokes,"## Bug Description
the a coefficients are local to elements, but they are being retrieved from the other side. The side that owns the face info doesnt own the a coefficient it seems. 

this is the backtrace. Sorry for screenshot, linux wasnt letting me paste from my xterm

![image](https://user-images.githubusercontent.com/25037151/188021354-65cb35c1-861b-4ea8-bf8f-0717d8e1e349.png)

## Steps to Reproduce
MSFR VTB input with 6 processes. I couldnt get it on my mac but on the linux box I saw it at 6 and 56 processes

## Impact
Died simulation bad bad.
Reduced flexibility in how distributed our flow simulations can be
Makes NS module look bad when we're trying to make it good
Lost analyst time",1.0,"VolumetricFlowRate fails on internal boundaries that are cut by domain boundaries - ## Bug Description
the a coefficients are local to elements, but they are being retrieved from the other side. The side that owns the face info doesnt own the a coefficient it seems. 

this is the backtrace. Sorry for screenshot, linux wasnt letting me paste from my xterm

![image](https://user-images.githubusercontent.com/25037151/188021354-65cb35c1-861b-4ea8-bf8f-0717d8e1e349.png)

## Steps to Reproduce
MSFR VTB input with 6 processes. I couldnt get it on my mac but on the linux box I saw it at 6 and 56 processes

## Impact
Died simulation bad bad.
Reduced flexibility in how distributed our flow simulations can be
Makes NS module look bad when we're trying to make it good
Lost analyst time",0,volumetricflowrate fails on internal boundaries that are cut by domain boundaries      bug description  the a coefficients are local to elements  but they are being retrieved from the other side  the side that owns the face info doesnt own the a coefficient it seems      this is the backtrace  sorry for screenshot  linux wasnt letting me paste from my xterm               steps to reproduce  msfr vtb input with   processes  i couldnt get it on my mac but on the linux box i saw it at   and   processes       impact  died simulation bad bad   reduced flexibility in how distributed our flow simulations can be  makes ns module look bad when we re trying to make it good  lost analyst time,0
23149,15864329463.0,IssuesEvent,2021-04-08 13:43:04,airyhq/airy,https://api.github.com/repos/airyhq/airy,opened,Prometheus metrics about Redis queue,infrastructure,"As we also want to know the number of elements in the Redis queues used for the webhooks, we need to add

- [ ] Prometheus [Go Client Lib](https://prometheus.io/docs/guides/go-application/) to the scheduler and expose our own `/metrics`
- [ ] another scrape target for this new endpoint
- [ ] new Dashboard to show this metric",1.0,"Prometheus metrics about Redis queue - As we also want to know the number of elements in the Redis queues used for the webhooks, we need to add

- [ ] Prometheus [Go Client Lib](https://prometheus.io/docs/guides/go-application/) to the scheduler and expose our own `/metrics`
- [ ] another scrape target for this new endpoint
- [ ] new Dashboard to show this metric",0,prometheus metrics about redis queue   as we also want to know the number of elements in the redis queues used for the webhooks  we need to add        prometheus     to the scheduler and expose our own   metrics       another scrape target for this new endpoint      new dashboard to show this metric,0
57941,8214682082.0,IssuesEvent,2018-09-05 00:49:09,golang/go,https://api.github.com/repos/golang/go,closed,go/ast: TypeSpec.Doc is nil? Have to grab documentation at GenDecl,Documentation NeedsInvestigation,"### What version of Go are you using (`go version`)?
1.11

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
darwin

### Question
Noticed in the AST for type instantiated structures, that if I go to the `Doc` field in `ast.TypeSpec` the value is `nil`. I have to visit the `ast.GenDecl` node instead to grab doc fields.

Is this intended?
If so, why does `ast.TypeSpec` have a `Doc` field? Should `Doc` along with `Comment` be deprecated, as in mentioned in the docs, since comments/documentation really do not have anything to do with the type specification?

This can reproduce by parsing the code sample below
```go
package foo

// documentation goes here
type Foo struct{}

func main() {
    f := Foo{}
}
```

### expectation
`ast.TypeSpec` contain non-`nil` value for `Doc` when documentation is provided.
",1.0,"go/ast: TypeSpec.Doc is nil? Have to grab documentation at GenDecl - ### What version of Go are you using (`go version`)?
1.11

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
darwin

### Question
Noticed in the AST for type instantiated structures, that if I go to the `Doc` field in `ast.TypeSpec` the value is `nil`. I have to visit the `ast.GenDecl` node instead to grab doc fields.

Is this intended?
If so, why does `ast.TypeSpec` have a `Doc` field? Should `Doc` along with `Comment` be deprecated, as in mentioned in the docs, since comments/documentation really do not have anything to do with the type specification?

This can reproduce by parsing the code sample below
```go
package foo

// documentation goes here
type Foo struct{}

func main() {
    f := Foo{}
}
```

### expectation
`ast.TypeSpec` contain non-`nil` value for `Doc` when documentation is provided.
",1,go ast  typespec doc is nil  have to grab documentation at gendecl       what version of go are you using   go version                does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env     darwin        question  noticed in the ast for type instantiated structures  that if i go to the  doc  field in  ast typespec  the value is  nil   i have to visit the  ast gendecl  node instead to grab doc fields     is this intended   if so  why does  ast typespec  have a  doc  field  should  doc  along with  comment  be deprecated  as in mentioned in the docs  since comments documentation really do not have anything to do with the type specification     this can reproduce by parsing the code sample below     go  package foo       documentation goes here  type foo struct      func main          f    foo                  expectation   ast typespec  contain non  nil  value for  doc  when documentation is provided   ,1
63306,12302474754.0,IssuesEvent,2020-05-11 17:02:18,phetsims/build-a-molecule,https://api.github.com/repos/phetsims/build-a-molecule,closed,Branch: mobiusBAM,dev:code-review,From #173: This branch was created to build Mobius support for the 3d Molecule representation. Those changes were merged into master and this branch no longer needs to exist. I'll delete the branch and close this issue.,1.0,Branch: mobiusBAM - From #173: This branch was created to build Mobius support for the 3d Molecule representation. Those changes were merged into master and this branch no longer needs to exist. I'll delete the branch and close this issue.,0,branch  mobiusbam   from     this branch was created to build mobius support for the   molecule representation  those changes were merged into master and this branch no longer needs to exist  i ll delete the branch and close this issue ,0
3946,10335520483.0,IssuesEvent,2019-09-03 10:47:15,MicrosoftDocs/architecture-center,https://api.github.com/repos/MicrosoftDocs/architecture-center,closed,Difference in resource type naming prefix or suffix ,Pri1 architecture-center/svc cloud-fundamentals/subsvc cxp duplicate triaged,"This document shows resource types as suffixes, yet another page (https://docs.microsoft.com/en-us/azure/architecture/cloud-adoption/ready/considerations/name-and-tag#recommended-resource-type-prefixes) has the resource types as prefixes

Consistency would be nice :-)

---
#### Document Details

⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*

* ID: 0e540bb6-9f72-0529-28ea-ae82bc869835
* Version Independent ID: 24e71392-985b-59fb-1552-46395b169612
* Content: [Naming conventions for Azure resources - Best practices for cloud applications](https://docs.microsoft.com/en-us/azure/architecture/best-practices/naming-conventions#naming-rules-and-restrictions)
* Content Source: [docs/best-practices/naming-conventions.md](https://github.com/microsoftdocs/architecture-center/blob/master/docs/best-practices/naming-conventions.md)
* Service: **architecture-center**
* Sub-service: **cloud-fundamentals**
* GitHub Login: @telmosampaio
* Microsoft Alias: **pnp**",1.0,"Difference in resource type naming prefix or suffix  - This document shows resource types as suffixes, yet another page (https://docs.microsoft.com/en-us/azure/architecture/cloud-adoption/ready/considerations/name-and-tag#recommended-resource-type-prefixes) has the resource types as prefixes

Consistency would be nice :-)

---
#### Document Details

⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*

* ID: 0e540bb6-9f72-0529-28ea-ae82bc869835
* Version Independent ID: 24e71392-985b-59fb-1552-46395b169612
* Content: [Naming conventions for Azure resources - Best practices for cloud applications](https://docs.microsoft.com/en-us/azure/architecture/best-practices/naming-conventions#naming-rules-and-restrictions)
* Content Source: [docs/best-practices/naming-conventions.md](https://github.com/microsoftdocs/architecture-center/blob/master/docs/best-practices/naming-conventions.md)
* Service: **architecture-center**
* Sub-service: **cloud-fundamentals**
* GitHub Login: @telmosampaio
* Microsoft Alias: **pnp**",0,difference in resource type naming prefix or suffix    this document shows resource types as suffixes  yet another page    has the resource types as prefixes  consistency would be nice               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    architecture center     sub service    cloud fundamentals     github login   telmosampaio   microsoft alias    pnp  ,0
368846,25811084581.0,IssuesEvent,2022-12-11 21:23:31,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: better fuzzing documentation,Documentation,"The documentation was pretty sparse on fuzzing. 

First I had a tough time finding where my corpus was because no testdata dir was being generated- so I though ""aha, must be an environment variable, something like `GOFUZZCORPUS`, but. nothing. 

Then I started looking in `go help test`, took me a while to skim though and find that I needed to check out `go help testfunc` for more details only to find there was barely anything on fuzzing.

Relevant `go help test` output:
```
These additional files can contain test functions, benchmark functions, fuzz
tests and example functions. See 'go help testfunc' for more.
```
Relevant `go help testfunc` output:
```
A fuzz test is one named FuzzXxx and should have the signature,

	func FuzzXxx(f *testing.F) { ... }
// ...
The entire test file is presented as the example when it contains a single
example function, at least one other function, type, variable, or constant
declaration, and no tests, benchmarks, or fuzz tests.
```

There is no way to make out how the fuzzing command works from this. Please add better documentation of:
* Where the non-crashign fuzz corpus is located (GOCACHE)
* Where the crashing corpus is located
* What the differences are between both
* Fuzzing by default goes on forever
* How to add non crashing fuzz corpus to unit tests
",1.0,"cmd/go: better fuzzing documentation - The documentation was pretty sparse on fuzzing. 

First I had a tough time finding where my corpus was because no testdata dir was being generated- so I though ""aha, must be an environment variable, something like `GOFUZZCORPUS`, but. nothing. 

Then I started looking in `go help test`, took me a while to skim though and find that I needed to check out `go help testfunc` for more details only to find there was barely anything on fuzzing.

Relevant `go help test` output:
```
These additional files can contain test functions, benchmark functions, fuzz
tests and example functions. See 'go help testfunc' for more.
```
Relevant `go help testfunc` output:
```
A fuzz test is one named FuzzXxx and should have the signature,

	func FuzzXxx(f *testing.F) { ... }
// ...
The entire test file is presented as the example when it contains a single
example function, at least one other function, type, variable, or constant
declaration, and no tests, benchmarks, or fuzz tests.
```

There is no way to make out how the fuzzing command works from this. Please add better documentation of:
* Where the non-crashign fuzz corpus is located (GOCACHE)
* Where the crashing corpus is located
* What the differences are between both
* Fuzzing by default goes on forever
* How to add non crashing fuzz corpus to unit tests
",1,cmd go  better fuzzing documentation   the documentation was pretty sparse on fuzzing      first i had a tough time finding where my corpus was because no testdata dir was being generated  so i though  aha  must be an environment variable  something like  gofuzzcorpus   but  nothing      then i started looking in  go help test   took me a while to skim though and find that i needed to check out  go help testfunc  for more details only to find there was barely anything on fuzzing     relevant  go help test  output        these additional files can contain test functions  benchmark functions  fuzz  tests and example functions  see  go help testfunc  for more        relevant  go help testfunc  output        a fuzz test is one named fuzzxxx and should have the signature     	func fuzzxxx f  testing f                   the entire test file is presented as the example when it contains a single  example function  at least one other function  type  variable  or constant  declaration  and no tests  benchmarks  or fuzz tests          there is no way to make out how the fuzzing command works from this  please add better documentation of     where the non crashign fuzz corpus is located  gocache     where the crashing corpus is located    what the differences are between both    fuzzing by default goes on forever    how to add non crashing fuzz corpus to unit tests  ,1
4334,4998132475.0,IssuesEvent,2016-12-09 18:53:29,zulip/zulip,https://api.github.com/repos/zulip/zulip,closed,Speed up our rate limiting test,area: testing-infrastructure bite size bug,"`test_hit_ratelimits` sleeps for a second in order to verify that our rate limiting code works correctly.  We should change it to instead mock the current time and shave 1s off our total test runtime.

```
Running zerver.tests.test_external.RateLimitTests.test_hit_ratelimits
 ** Test is TOO slow: zerver.tests.test_external.RateLimitTests.test_hit_ratelimits (1.121 s)
```",1.0,"Speed up our rate limiting test - `test_hit_ratelimits` sleeps for a second in order to verify that our rate limiting code works correctly.  We should change it to instead mock the current time and shave 1s off our total test runtime.

```
Running zerver.tests.test_external.RateLimitTests.test_hit_ratelimits
 ** Test is TOO slow: zerver.tests.test_external.RateLimitTests.test_hit_ratelimits (1.121 s)
```",0,speed up our rate limiting test    test hit ratelimits  sleeps for a second in order to verify that our rate limiting code works correctly   we should change it to instead mock the current time and shave   off our total test runtime          running zerver tests test external ratelimittests test hit ratelimits      test is too slow  zerver tests test external ratelimittests test hit ratelimits      s      ,0
71052,9477307224.0,IssuesEvent,2019-04-19 18:09:11,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go/internal/modfetch: document known bug in `isVendoredPackage`,Documentation NeedsFix Unfortunate modules,"### What version of Go are you using (`go version`)?
<pre>
$ go version
go version go1.12.1 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""/home/gheibi/.go/bin/""
GOCACHE=""/home/gheibi/.cache/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/gheibi/.go/""
GOPROXY=""""
GORACE=""""
GOROOT=""/local/go1.12.1.linux_amd64/go""
GOTMPDIR=""""
GOTOOLDIR=""/local/go1.12.1.linux_amd64/go                                                                                     /pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build865790926=/tmp/go-build""

</pre></details>

### What did you do?

```
$grep -A12 ""func isVendoredPackage"" $GOROOT/src/cmd/go/internal/modfetch/coderepo.go
```
https://github.com/golang/go/blob/c8aaec2f70c5ccbca1ec2152c57d19981ac09133/src/cmd/go/internal/modfetch/coderepo.go#L632-L642

### What did you expect to see?
```
func isVendoredPackage(name string) bool {
	var i int
	if strings.HasPrefix(name, ""vendor/"") {
		i += len(""vendor/"")
	} else if j := strings.Index(name, ""/vendor/""); j >= 0 {
		i += j + len(""/vendor/"")
	} else {
		return false
	}
	return strings.Contains(name[i:], ""/"")
}
```
### What did you see instead?
The function is not documented, but it is obvious that it is not doing what the intention is.
It seems that the intention is to match against this regex: `(^vendor/|/vendor/).*/`
But in fact it does random match by skipping first 8 bytes in case the input contains `/vendor/`.
The fix is to add the j to the i as states above.

It is quite important to fix it early on, because it may cause go-modules with different hashes and a late fix can cause more hash mismatch of the same content (defy the immutability logic).
",1.0,"cmd/go/internal/modfetch: document known bug in `isVendoredPackage` - ### What version of Go are you using (`go version`)?
<pre>
$ go version
go version go1.12.1 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""/home/gheibi/.go/bin/""
GOCACHE=""/home/gheibi/.cache/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/gheibi/.go/""
GOPROXY=""""
GORACE=""""
GOROOT=""/local/go1.12.1.linux_amd64/go""
GOTMPDIR=""""
GOTOOLDIR=""/local/go1.12.1.linux_amd64/go                                                                                     /pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build865790926=/tmp/go-build""

</pre></details>

### What did you do?

```
$grep -A12 ""func isVendoredPackage"" $GOROOT/src/cmd/go/internal/modfetch/coderepo.go
```
https://github.com/golang/go/blob/c8aaec2f70c5ccbca1ec2152c57d19981ac09133/src/cmd/go/internal/modfetch/coderepo.go#L632-L642

### What did you expect to see?
```
func isVendoredPackage(name string) bool {
	var i int
	if strings.HasPrefix(name, ""vendor/"") {
		i += len(""vendor/"")
	} else if j := strings.Index(name, ""/vendor/""); j >= 0 {
		i += j + len(""/vendor/"")
	} else {
		return false
	}
	return strings.Contains(name[i:], ""/"")
}
```
### What did you see instead?
The function is not documented, but it is obvious that it is not doing what the intention is.
It seems that the intention is to match against this regex: `(^vendor/|/vendor/).*/`
But in fact it does random match by skipping first 8 bytes in case the input contains `/vendor/`.
The fix is to add the j to the i as states above.

It is quite important to fix it early on, because it may cause go-modules with different hashes and a late fix can cause more hash mismatch of the same content (defy the immutability logic).
",1,cmd go internal modfetch  document known bug in  isvendoredpackage        what version of go are you using   go version          go version  go version       linux             does this issue reproduce with the latest release   yes          what operating system and processor architecture are you using   go env          go env  output       go env  goarch      gobin   home gheibi  go bin    gocache   home gheibi  cache go build   goexe     goflags     gohostarch      gohostos  linux   goos  linux   gopath   home gheibi  go    goproxy     gorace     goroot   local       linux   go   gotmpdir     gotooldir   local       linux   go                                                                                      pkg tool linux     gccgo  gccgo   cc  gcc   cxx  g     cgo enabled      gomod     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build               what did you do           grep     func isvendoredpackage   goroot src cmd go internal modfetch coderepo go                what did you expect to see        func isvendoredpackage name string  bool    	var i int  	if strings hasprefix name   vendor       		i    len  vendor     	  else if j    strings index name    vendor     j         		i    j   len   vendor     	  else    		return false  	   	return strings contains name                     what did you see instead   the function is not documented  but it is obvious that it is not doing what the intention is   it seems that the intention is to match against this regex     vendor   vendor        but in fact it does random match by skipping first   bytes in case the input contains   vendor     the fix is to add the j to the i as states above     it is quite important to fix it early on  because it may cause go modules with different hashes and a late fix can cause more hash mismatch of the same content  defy the immutability logic    ,1
656458,21765070593.0,IssuesEvent,2022-05-13 00:10:41,ArctosDB/arctos,https://api.github.com/repos/ArctosDB/arctos,closed,New Scientific Name pop-up slowing data entry,Priority-Critical (Arctos is broken) Enhancement,"**Is your feature request related to a problem? Please describe.**
@dusty  @acdoll 

Last week the pop-up to select a taxon for the Scientific Name field in data entry changed.  It is most noticeable when the Scientific Name is only the genus.  It took 1 minute, 11 seconds for data in the pop-up to appear when the name Pecten was entered.  It took a one minute, 24 seconds for data in the pop-up for Melanopsis to appear.  Even a species such as _Cypraea pantherina_ took 8 seconds.  Some volunteers thought Arctos was frozen, closed the pop-up and reentered the name.

Additionally, the information in the pop-up (while sometimes helpful) could be better organized.  This is the initial pop-up for Pecten

<img width=""634"" alt=""Screen Shot 2022-05-12 at 5 27 21 AM"" src=""https://user-images.githubusercontent.com/15368365/168067489-abccfd29-2853-4489-8c6a-7369324c6a70.png"">

Our preferred source is WoRMS (via Arctos) which is the last column and not visible until the screen is expanded.  And the data we are looking for is the taxon status which is buried in the middle of the metadata.

<img width=""1639"" alt=""Enhance status line"" src=""https://user-images.githubusercontent.com/15368365/168067710-d5bc8014-204c-4e61-94af-ff9f132943cf.png"">


**Describe what you're trying to accomplish** 
Make the single record data entry process as fast and smooth as possible for our volunteers.

**Describe the solution you'd like**
These ideas overlap.
Idea 1 - populate the pop-up with just the taxon names, taxon status and limited classification data as before with an option to show the extended data
Idea 2 - or provide an option on the data entry screen for condensed or expanded data in the pop-up
Idea 3 - rearrange the columns so that the preferred taxon source is in the first column.  
Idea 4 - or only show the source that will be used to populate the classification in the catalog record
Idea 5 - or dump the Arctos Relationships or make it the last column.
Idea 4 - make ""taxon status"" **bold**.

**Describe alternatives you've considered**
Tolerate the slowdown.  We have no other way to enter our data.  

**Priority**
We think it's high, but no one else has created an issue so maybe it's not a big deal overall
",1.0,"New Scientific Name pop-up slowing data entry - **Is your feature request related to a problem? Please describe.**
@dusty  @acdoll 

Last week the pop-up to select a taxon for the Scientific Name field in data entry changed.  It is most noticeable when the Scientific Name is only the genus.  It took 1 minute, 11 seconds for data in the pop-up to appear when the name Pecten was entered.  It took a one minute, 24 seconds for data in the pop-up for Melanopsis to appear.  Even a species such as _Cypraea pantherina_ took 8 seconds.  Some volunteers thought Arctos was frozen, closed the pop-up and reentered the name.

Additionally, the information in the pop-up (while sometimes helpful) could be better organized.  This is the initial pop-up for Pecten

<img width=""634"" alt=""Screen Shot 2022-05-12 at 5 27 21 AM"" src=""https://user-images.githubusercontent.com/15368365/168067489-abccfd29-2853-4489-8c6a-7369324c6a70.png"">

Our preferred source is WoRMS (via Arctos) which is the last column and not visible until the screen is expanded.  And the data we are looking for is the taxon status which is buried in the middle of the metadata.

<img width=""1639"" alt=""Enhance status line"" src=""https://user-images.githubusercontent.com/15368365/168067710-d5bc8014-204c-4e61-94af-ff9f132943cf.png"">


**Describe what you're trying to accomplish** 
Make the single record data entry process as fast and smooth as possible for our volunteers.

**Describe the solution you'd like**
These ideas overlap.
Idea 1 - populate the pop-up with just the taxon names, taxon status and limited classification data as before with an option to show the extended data
Idea 2 - or provide an option on the data entry screen for condensed or expanded data in the pop-up
Idea 3 - rearrange the columns so that the preferred taxon source is in the first column.  
Idea 4 - or only show the source that will be used to populate the classification in the catalog record
Idea 5 - or dump the Arctos Relationships or make it the last column.
Idea 4 - make ""taxon status"" **bold**.

**Describe alternatives you've considered**
Tolerate the slowdown.  We have no other way to enter our data.  

**Priority**
We think it's high, but no one else has created an issue so maybe it's not a big deal overall
",0,new scientific name pop up slowing data entry     is your feature request related to a problem  please describe      dusty   acdoll     last week the pop up to select a taxon for the scientific name field in data entry changed   it is most noticeable when the scientific name is only the genus   it took   minute    seconds for data in the pop up to appear when the name pecten was entered   it took a one minute    seconds for data in the pop up for melanopsis to appear   even a species such as  cypraea pantherina  took   seconds   some volunteers thought arctos was frozen  closed the pop up and reentered the name     additionally  the information in the pop up  while sometimes helpful  could be better organized   this is the initial pop up for pecten     img width     alt  screen shot       at       am  src       our preferred source is worms  via arctos  which is the last column and not visible until the screen is expanded   and the data we are looking for is the taxon status which is buried in the middle of the metadata      img width     alt  enhance status line  src           describe what you re trying to accomplish     make the single record data entry process as fast and smooth as possible for our volunteers       describe the solution you d like    these ideas overlap   idea     populate the pop up with just the taxon names  taxon status and limited classification data as before with an option to show the extended data  idea     or provide an option on the data entry screen for condensed or expanded data in the pop up  idea     rearrange the columns so that the preferred taxon source is in the first column     idea     or only show the source that will be used to populate the classification in the catalog record  idea     or dump the arctos relationships or make it the last column   idea     make  taxon status    bold         describe alternatives you ve considered    tolerate the slowdown   we have no other way to enter our data         priority    we think it s high  but no one else has created an issue so maybe it s not a big deal overall  ,0
60541,8443339608.0,IssuesEvent,2018-10-18 15:21:18,golang/go,https://api.github.com/repos/golang/go,closed,syscall/js: unclear what the zero js.Value represents,Arch-Wasm Documentation NeedsDecision,"The godoc of [`js.Value`](https://godoc.org/syscall/js#Value) type currently says:

> Value represents a JavaScript value.

It's not easy to figure out what the zero value represents, even after reading the rest of `syscall/js` docs.

This question came up when I had a function with the return types `(js.Value, error)` and I wanted to figure out what `js.Value` to return when an error happened. Typically, one returns the zero value, but it helps to understand what the zero value of that type represents.

From looking at the implementation, I understand that the zero `js.Value` value currently represents the JavaScript number zero, is that right @neelance? I.e.:

```Go
js.Value{} == js.ValueOf(int(0))   // true
js.Value{}.Type() == js.TypeNumber // true
```

It's also possible that what the zero `js.Value` value represents is considered an internal implementation detail and not meant to be a part of the public API. Hence, users shouldn't rely on it to have any well-defined and stable meaning.

I think it would be helpful to document what the zero value represents, so people can answer this question by reading the documentation. Depending on the intention, perhaps one of these:

```Go
// Value represents a JavaScript value.
// The zero value for a Value represents the JavaScript number 0.
type Value ...
```

(See https://godoc.org/math/big#Int documentation for a similar example.)

Or (an improved version of):

```Go
// Value represents a JavaScript value.
//
// The zero value for Value is undefined. It is not intended for direct use
// by clients, other than to signify that the value is not defined.
type Value ...
```

/cc @neelance",1.0,"syscall/js: unclear what the zero js.Value represents - The godoc of [`js.Value`](https://godoc.org/syscall/js#Value) type currently says:

> Value represents a JavaScript value.

It's not easy to figure out what the zero value represents, even after reading the rest of `syscall/js` docs.

This question came up when I had a function with the return types `(js.Value, error)` and I wanted to figure out what `js.Value` to return when an error happened. Typically, one returns the zero value, but it helps to understand what the zero value of that type represents.

From looking at the implementation, I understand that the zero `js.Value` value currently represents the JavaScript number zero, is that right @neelance? I.e.:

```Go
js.Value{} == js.ValueOf(int(0))   // true
js.Value{}.Type() == js.TypeNumber // true
```

It's also possible that what the zero `js.Value` value represents is considered an internal implementation detail and not meant to be a part of the public API. Hence, users shouldn't rely on it to have any well-defined and stable meaning.

I think it would be helpful to document what the zero value represents, so people can answer this question by reading the documentation. Depending on the intention, perhaps one of these:

```Go
// Value represents a JavaScript value.
// The zero value for a Value represents the JavaScript number 0.
type Value ...
```

(See https://godoc.org/math/big#Int documentation for a similar example.)

Or (an improved version of):

```Go
// Value represents a JavaScript value.
//
// The zero value for Value is undefined. It is not intended for direct use
// by clients, other than to signify that the value is not defined.
type Value ...
```

/cc @neelance",1,syscall js  unclear what the zero js value represents   the godoc of     type currently says       value represents a javascript value     it s not easy to figure out what the zero value represents  even after reading the rest of  syscall js  docs     this question came up when i had a function with the return types   js value  error   and i wanted to figure out what  js value  to return when an error happened  typically  one returns the zero value  but it helps to understand what the zero value of that type represents     from looking at the implementation  i understand that the zero  js value  value currently represents the javascript number zero  is that right  neelance  i e         go  js value      js valueof int          true  js value   type      js typenumber    true         it s also possible that what the zero  js value  value represents is considered an internal implementation detail and not meant to be a part of the public api  hence  users shouldn t rely on it to have any well defined and stable meaning     i think it would be helpful to document what the zero value represents  so people can answer this question by reading the documentation  depending on the intention  perhaps one of these        go     value represents a javascript value      the zero value for a value represents the javascript number     type value              see   documentation for a similar example      or  an improved version of         go     value represents a javascript value          the zero value for value is undefined  it is not intended for direct use     by clients  other than to signify that the value is not defined   type value              cc  neelance,1
71570,7247625499.0,IssuesEvent,2018-02-15 04:26:42,omegaup/omegaup,https://api.github.com/repos/omegaup/omegaup,closed,Parameter is larger than the maximum value of 5.: window_length,1 Bug P2 omegaUp For Contests,"When creating a new contest, and enabling the ""Different Starts"" option, this cryptic error message shows up if you use a value larger than 5. This is not explained in the form.",1.0,"Parameter is larger than the maximum value of 5.: window_length - When creating a new contest, and enabling the ""Different Starts"" option, this cryptic error message shows up if you use a value larger than 5. This is not explained in the form.",0,parameter is larger than the maximum value of     window length   when creating a new contest  and enabling the  different starts  option  this cryptic error message shows up if you use a value larger than    this is not explained in the form ,0
9560,12518421478.0,IssuesEvent,2020-06-03 12:55:35,metabase/metabase,https://api.github.com/repos/metabase/metabase,closed,Postgres array_agg function,Database/Postgres Priority:P3 Querying/Processor Type:New Feature,"Does anyone have any recommendations on using an aggregated array function with Metabase?

I tried using Postgres' ""array_agg"", but Metabase doesn't seem to recognize it.
",1.0,"Postgres array_agg function - Does anyone have any recommendations on using an aggregated array function with Metabase?

I tried using Postgres' ""array_agg"", but Metabase doesn't seem to recognize it.
",0,postgres array agg function   does anyone have any recommendations on using an aggregated array function with metabase     i tried using postgres   array agg   but metabase doesn t seem to recognize it   ,0
92418,18852089533.0,IssuesEvent,2021-11-11 22:26:06,google/web-stories-wp,https://api.github.com/repos/google/web-stories-wp,closed,Deduplicate Tooltip,Type: Code Quality Pod: Pea Package: Story Editor,"## Feature Description

The story-editor has it's own implementation of the Tooltip that is imported from the design system. With work done here #9668 - that implementation should be obsolete and able to be removed. 

Let's branch off of 9688 and remove that redundant tooltip (story-editor/src/components/tooltip) and use the one in the design system. I suggest branching so that we can verify that the bugfix there is actually a solution here. 

After review it can be merged into 9668 and QA'd all together. 

## Alternatives Considered

<!-- A clear and concise description of any alternative solutions or features you've considered. -->

## Additional Context

<!-- Add any other context or screenshots about the feature request. -->
",1.0,"Deduplicate Tooltip - ## Feature Description

The story-editor has it's own implementation of the Tooltip that is imported from the design system. With work done here #9668 - that implementation should be obsolete and able to be removed. 

Let's branch off of 9688 and remove that redundant tooltip (story-editor/src/components/tooltip) and use the one in the design system. I suggest branching so that we can verify that the bugfix there is actually a solution here. 

After review it can be merged into 9668 and QA'd all together. 

## Alternatives Considered

<!-- A clear and concise description of any alternative solutions or features you've considered. -->

## Additional Context

<!-- Add any other context or screenshots about the feature request. -->
",0,deduplicate tooltip      feature description    the story editor has it s own implementation of the tooltip that is imported from the design system  with work done here      that implementation should be obsolete and able to be removed      let s branch off of   and remove that redundant tooltip  story editor src components tooltip  and use the one in the design system  i suggest branching so that we can verify that the bugfix there is actually a solution here      after review it can be merged into   and qa d all together         alternatives considered            additional context       ,0
24546,17384055980.0,IssuesEvent,2021-08-01 09:09:50,freeorion/freeorion,https://api.github.com/repos/freeorion/freeorion,opened,It is not clear how to list commindline options,category:bug component:infrastructure,"When I run game with the `--help` argument output doesn't show all avaliable option. 
I have no clue how to expand groups. 

It would be great if `--help` option will have a text which will explain how to expand groups. 


```
J:\games\FreeOrion> .\FreeOrion.exe resource --help
Option Groups:
  audio                      Audio
  effects                    Effects
  network                    Network and server
  resource                   Game data resources
  save                       Save game
  setup                      New game starting settings
  ui                         User interface
  version                    Version
  video                      Video
  misc                       Miscellaneous
  ```
 ",1.0,"It is not clear how to list commindline options - When I run game with the `--help` argument output doesn't show all avaliable option. 
I have no clue how to expand groups. 

It would be great if `--help` option will have a text which will explain how to expand groups. 


```
J:\games\FreeOrion> .\FreeOrion.exe resource --help
Option Groups:
  audio                      Audio
  effects                    Effects
  network                    Network and server
  resource                   Game data resources
  save                       Save game
  setup                      New game starting settings
  ui                         User interface
  version                    Version
  video                      Video
  misc                       Miscellaneous
  ```
 ",0,it is not clear how to list commindline options   when i run game with the    help  argument output doesn t show all avaliable option    i have no clue how to expand groups      it would be great if    help  option will have a text which will explain how to expand groups             j  games freeorion    freeorion exe resource   help  option groups     audio                      audio    effects                    effects    network                    network and server    resource                   game data resources    save                       save game    setup                      new game starting settings    ui                         user interface    version                    version    video                      video    misc                       miscellaneous          ,0
74300,9779189957.0,IssuesEvent,2019-06-07 13:57:44,golang/go,https://api.github.com/repos/golang/go,closed,text/template: document concurrency properties for the instances returned by (*Template).New,Documentation NeedsFix,"```go
package main

import (
	""fmt""
	""sync""
	""text/template""
)

func main() {
	var wg sync.WaitGroup

	tpl := template.New("""")

	for i := 1; i < 20; i++ {
		name := fmt.Sprintf(""n%d.txt"", i)
		wg.Add(1)
		go func() {
			defer wg.Done()
			tpl.New(name).Parse(""Go!"")
		}()
	}

	wg.Wait()
}
```

The above fails with:


```bash
fatal error: concurrent map read and map write

goroutine 36 [running]:
runtime.throw(0x1136d33, 0x21)
	/Users/bep/sdk/go1.12beta2/src/runtime/panic.go:617 +0x72 fp=0xc000075d78 sp=0xc000075d48 pc=0x1029d02
runtime.mapaccess1_faststr(0x110d820, 0xc000066210, 0xc000016230, 0x7, 0x0)
	/Users/bep/sdk/go1.12beta2/src/runtime/map_faststr.go:21 +0x464 fp=0xc000075de8 sp=0xc000075d78 pc=0x1010a34
text/template.(*Template).associate(0xc00004a340, 0xc00004a340, 0xc0000ae800, 0xc00006ec01)
	/Users/bep/sdk/go1.12beta2/src/text/template/template.go:217 +0x62 fp=0xc000075e28 sp=0xc000075de8 pc=0x10ec762
text/template.(*Template).AddParseTree(0xc00004a340, 0xc000016230, 0x7, 0xc0000ae800, 0x0, 0x0, 0x0)
	/Users/bep/sdk/go1.12beta2/src/text/template/template.go:128 +0xfa fp=0xc000075e78 sp=0xc000075e28 pc=0x10ebb0a
text/template.(*Template).Parse(0xc00004a340, 0x1131652, 0x3, 0x0, 0x0, 0x0)
	/Users/bep/sdk/go1.12beta2/src/text/template/template.go:203 +0x1f8 fp=0xc000075f78 sp=0xc000075e78 pc=0x10ec528
main.main.func1(0xc000016114, 0xc00004a0c0, 0xc000016230, 0x7)
	/Users/bep/dev/go/bep/temp/main.go:19 +0xfa fp=0xc000075fc0 sp=0xc000075f78 pc=0x10ee17a
runtime.goexit()
	/Users/bep/sdk/go1.12beta2/src/runtime/asm_amd64.s:1337 +0x1 fp=0xc000075fc8 sp=0xc000075fc0 pc=0x1052f41
created by main.main
	/Users/bep/dev/go/bep/temp/main.go:17 +0x13b

goroutine 1 [semacquire]:
sync.runtime_Semacquire(0xc000016114)
	/Users/bep/sdk/go1.12beta2/src/runtime/sema.go:56 +0x39
sync.(*WaitGroup).Wait(0xc000016114)
	/Users/bep/sdk/go1.12beta2/src/sync/waitgroup.go:130 +0x65
main.main()
	/Users/bep/dev/go/bep/temp/main.go:23 +0x161
Error: process exited with code 2.

```

I'm currently running `go1.12beta2` (yes, I know), but I have had this failure on earlier versions, too.

Note that I'm not saying that this is a bug (the doc for `Parse` isn't clear on this), but as this has hit me more than once in real programs, I think at least a documentation update is needed.

",1.0,"text/template: document concurrency properties for the instances returned by (*Template).New - ```go
package main

import (
	""fmt""
	""sync""
	""text/template""
)

func main() {
	var wg sync.WaitGroup

	tpl := template.New("""")

	for i := 1; i < 20; i++ {
		name := fmt.Sprintf(""n%d.txt"", i)
		wg.Add(1)
		go func() {
			defer wg.Done()
			tpl.New(name).Parse(""Go!"")
		}()
	}

	wg.Wait()
}
```

The above fails with:


```bash
fatal error: concurrent map read and map write

goroutine 36 [running]:
runtime.throw(0x1136d33, 0x21)
	/Users/bep/sdk/go1.12beta2/src/runtime/panic.go:617 +0x72 fp=0xc000075d78 sp=0xc000075d48 pc=0x1029d02
runtime.mapaccess1_faststr(0x110d820, 0xc000066210, 0xc000016230, 0x7, 0x0)
	/Users/bep/sdk/go1.12beta2/src/runtime/map_faststr.go:21 +0x464 fp=0xc000075de8 sp=0xc000075d78 pc=0x1010a34
text/template.(*Template).associate(0xc00004a340, 0xc00004a340, 0xc0000ae800, 0xc00006ec01)
	/Users/bep/sdk/go1.12beta2/src/text/template/template.go:217 +0x62 fp=0xc000075e28 sp=0xc000075de8 pc=0x10ec762
text/template.(*Template).AddParseTree(0xc00004a340, 0xc000016230, 0x7, 0xc0000ae800, 0x0, 0x0, 0x0)
	/Users/bep/sdk/go1.12beta2/src/text/template/template.go:128 +0xfa fp=0xc000075e78 sp=0xc000075e28 pc=0x10ebb0a
text/template.(*Template).Parse(0xc00004a340, 0x1131652, 0x3, 0x0, 0x0, 0x0)
	/Users/bep/sdk/go1.12beta2/src/text/template/template.go:203 +0x1f8 fp=0xc000075f78 sp=0xc000075e78 pc=0x10ec528
main.main.func1(0xc000016114, 0xc00004a0c0, 0xc000016230, 0x7)
	/Users/bep/dev/go/bep/temp/main.go:19 +0xfa fp=0xc000075fc0 sp=0xc000075f78 pc=0x10ee17a
runtime.goexit()
	/Users/bep/sdk/go1.12beta2/src/runtime/asm_amd64.s:1337 +0x1 fp=0xc000075fc8 sp=0xc000075fc0 pc=0x1052f41
created by main.main
	/Users/bep/dev/go/bep/temp/main.go:17 +0x13b

goroutine 1 [semacquire]:
sync.runtime_Semacquire(0xc000016114)
	/Users/bep/sdk/go1.12beta2/src/runtime/sema.go:56 +0x39
sync.(*WaitGroup).Wait(0xc000016114)
	/Users/bep/sdk/go1.12beta2/src/sync/waitgroup.go:130 +0x65
main.main()
	/Users/bep/dev/go/bep/temp/main.go:23 +0x161
Error: process exited with code 2.

```

I'm currently running `go1.12beta2` (yes, I know), but I have had this failure on earlier versions, too.

Note that I'm not saying that this is a bug (the doc for `Parse` isn't clear on this), but as this has hit me more than once in real programs, I think at least a documentation update is needed.

",1,text template  document concurrency properties for the instances returned by   template  new      go  package main    import    	 fmt   	 sync   	 text template        func main      	var wg sync waitgroup    	tpl    template new        	for i       i      i      		name    fmt sprintf  n d txt   i   		wg add     		go func      			defer wg done    			tpl new name  parse  go     		     	     	wg wait              the above fails with          bash  fatal error  concurrent map read and map write    goroutine       runtime throw        	 users bep sdk     src runtime panic go      fp   sp   pc    runtime   faststr                 	 users bep sdk     src runtime map faststr go      fp   sp   pc    text template   template  associate              	 users bep sdk     src text template template go      fp   sp   pc    text template   template  addparsetree                       	 users bep sdk     src text template template go      fp   sp   pc    text template   template  parse                    	 users bep sdk     src text template template go      fp   sp   pc    main main                	 users bep dev go bep temp main go      fp   sp   pc    runtime goexit    	 users bep sdk     src runtime asm   s      fp   sp   pc    created by main main  	 users bep dev go bep temp main go         goroutine       sync runtime semacquire     	 users bep sdk     src runtime sema go       sync   waitgroup  wait     	 users bep sdk     src sync waitgroup go       main main    	 users bep dev go bep temp main go       error  process exited with code              i m currently running        yes  i know   but i have had this failure on earlier versions  too     note that i m not saying that this is a bug  the doc for  parse  isn t clear on this   but as this has hit me more than once in real programs  i think at least a documentation update is needed     ,1
13564,3739391460.0,IssuesEvent,2016-03-09 04:24:47,golang/go,https://api.github.com/repos/golang/go,closed,x/net/websocket: Document goroutine safety of websocket.Conn,Documentation HelpWanted,"<pre>The documentation of websocket.Conn[1] does not state that it is safe to share it among
multiple goroutines. From the implementation (rio and wio mutexes), it appears that it
is safe.

It'll be convenient if this is explicitly stated like in the case of net.Conn in
stdlib[2].

[1] - <a href=""http://godoc.org/code.google.com/p/go.net/websocket#Conn"">http://godoc.org/code.google.com/p/go.net/websocket#Conn</a></pre>",1.0,"x/net/websocket: Document goroutine safety of websocket.Conn - <pre>The documentation of websocket.Conn[1] does not state that it is safe to share it among
multiple goroutines. From the implementation (rio and wio mutexes), it appears that it
is safe.

It'll be convenient if this is explicitly stated like in the case of net.Conn in
stdlib[2].

[1] - <a href=""http://godoc.org/code.google.com/p/go.net/websocket#Conn"">http://godoc.org/code.google.com/p/go.net/websocket#Conn</a></pre>",1,x net websocket  document goroutine safety of websocket conn    the documentation of websocket conn  does not state that it is safe to share it among multiple goroutines  from the implementation  rio and wio mutexes   it appears that it is safe   it ll be convenient if this is explicitly stated like in the case of net conn in stdlib         a href   ,1
184331,14975290134.0,IssuesEvent,2021-01-28 05:47:50,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.16: document new go/build/constraint package,Documentation NeedsFix help wanted release-blocker,"The new `go/build/constraint` package in Go 1.16 should be documented in the final Go 1.16 release notes as part of #40700.

CC @rsc.",1.0,"doc/go1.16: document new go/build/constraint package - The new `go/build/constraint` package in Go 1.16 should be documented in the final Go 1.16 release notes as part of #40700.

CC @rsc.",1,doc      document new go build constraint package   the new  go build constraint  package in go     should be documented in the final go     release notes as part of        cc  rsc ,1
11065,3455708026.0,IssuesEvent,2015-12-17 21:22:05,golang/go,https://api.github.com/repos/golang/go,closed,"net/http: data race reading a ""Expect: 100-Continue"" request while writing response",Documentation,"The goroutine reading the request body will be updating ""ecr.sawEOF"", while the goroutine writing the response will be reading that boolean with no synchronization.

Using `go1.5.1 windows/amd64`.

```
WARNING: DATA RACE
Read by goroutine 438:
  net/http.(*chunkWriter).writeHeader()
      C:/workdir/go/src/net/http/server.go:866 +0xe38
  net/http.(*chunkWriter).Write()
      C:/workdir/go/src/net/http/server.go:261 +0xbf
  bufio.(*Writer).Write()
      C:/workdir/go/src/bufio/bufio.go:594 +0x17b
  net/http.(*response).write()
      C:/workdir/go/src/net/http/server.go:1140 +0x316
  net/http.(*response).Write()
      C:/workdir/go/src/net/http/server.go:1112 +0x7f
  (...app...)
      
Previous write by goroutine 870:
  net/http.(*expectContinueReader).Read()
      C:/workdir/go/src/net/http/server.go:571 +0x351
  (...app...)
```",1.0,"net/http: data race reading a ""Expect: 100-Continue"" request while writing response - The goroutine reading the request body will be updating ""ecr.sawEOF"", while the goroutine writing the response will be reading that boolean with no synchronization.

Using `go1.5.1 windows/amd64`.

```
WARNING: DATA RACE
Read by goroutine 438:
  net/http.(*chunkWriter).writeHeader()
      C:/workdir/go/src/net/http/server.go:866 +0xe38
  net/http.(*chunkWriter).Write()
      C:/workdir/go/src/net/http/server.go:261 +0xbf
  bufio.(*Writer).Write()
      C:/workdir/go/src/bufio/bufio.go:594 +0x17b
  net/http.(*response).write()
      C:/workdir/go/src/net/http/server.go:1140 +0x316
  net/http.(*response).Write()
      C:/workdir/go/src/net/http/server.go:1112 +0x7f
  (...app...)
      
Previous write by goroutine 870:
  net/http.(*expectContinueReader).Read()
      C:/workdir/go/src/net/http/server.go:571 +0x351
  (...app...)
```",1,net http  data race reading a  expect    continue  request while writing response   the goroutine reading the request body will be updating  ecr saweof   while the goroutine writing the response will be reading that boolean with no synchronization     using        windows             warning  data race  read by goroutine       net http   chunkwriter  writeheader          c  workdir go src net http server go         net http   chunkwriter  write          c  workdir go src net http server go         bufio   writer  write          c  workdir go src bufio bufio go         net http   response  write          c  workdir go src net http server go         net http   response  write          c  workdir go src net http server go             app              previous write by goroutine       net http   expectcontinuereader  read          c  workdir go src net http server go             app         ,1
28579,5518222205.0,IssuesEvent,2017-03-18 06:34:39,golang/go,https://api.github.com/repos/golang/go,closed,runtime: MemStats docs reference non-existent XSys,Documentation,"The runtime MemStats type's Sys field says:

https://golang.org/pkg/runtime/#MemStats.Sys
```go
   // Sys is the sum of the XSys fields below. Sys measures the
...
```

But there are no ""XSys"" fields anywhere in the Go tree.

```
$ git grep XSys
src/runtime/mstats.go:  // Sys is the sum of the XSys fields below. Sys measures the
src/syscall/mksyscall_windows.go:               pkgXSysWindows        // x/sys/windows package
src/syscall/mksyscall_windows.go:               pkgtype = pkgXSysWindows
src/syscall/mksyscall_windows.go:               case pkgXSysWindows:
src/syscall/mksyscall_windows.go:                       case pkgXSysWindows:
```

(nor case insensitively)

Noted while looking at #19600.
",1.0,"runtime: MemStats docs reference non-existent XSys - The runtime MemStats type's Sys field says:

https://golang.org/pkg/runtime/#MemStats.Sys
```go
   // Sys is the sum of the XSys fields below. Sys measures the
...
```

But there are no ""XSys"" fields anywhere in the Go tree.

```
$ git grep XSys
src/runtime/mstats.go:  // Sys is the sum of the XSys fields below. Sys measures the
src/syscall/mksyscall_windows.go:               pkgXSysWindows        // x/sys/windows package
src/syscall/mksyscall_windows.go:               pkgtype = pkgXSysWindows
src/syscall/mksyscall_windows.go:               case pkgXSysWindows:
src/syscall/mksyscall_windows.go:                       case pkgXSysWindows:
```

(nor case insensitively)

Noted while looking at #19600.
",1,runtime  memstats docs reference non existent xsys   the runtime memstats type s sys field says           go        sys is the sum of the xsys fields below  sys measures the              but there are no  xsys  fields anywhere in the go tree            git grep xsys  src runtime mstats go      sys is the sum of the xsys fields below  sys measures the  src syscall mksyscall windows go                pkgxsyswindows           x sys windows package  src syscall mksyscall windows go                pkgtype   pkgxsyswindows  src syscall mksyscall windows go                case pkgxsyswindows   src syscall mksyscall windows go                        case pkgxsyswindows           nor case insensitively     noted while looking at      ,1
613385,19088579027.0,IssuesEvent,2021-11-29 09:32:19,webcompat/web-bugs,https://api.github.com/repos/webcompat/web-bugs,closed,www.instagram.com - site is not usable,browser-firefox priority-critical engine-gecko,"<!-- @browser: Firefox 94.0.2. -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4495.0 Safari/537.36 -->
<!-- @reported_with: unknown -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/94982 -->

**URL**: https://www.instagram.com/

**Browser / Version**: Firefox 94.0.2.
**Operating System**: Windows 10
**Tested Another Browser**: Yes Edge

**Problem type**: Site is not usable
**Description**: Page not loading correctly
**Steps to Reproduce**:
After clearing cache in firefox, instagram shows a white screen after logging in. 
Switching user agent resolved the issue.
No problems on other browsers (tested on Edge and Chrome). 

<details>
<summary>Browser Configuration</summary>
<ul>
  <li>None</li>
</ul>
</details>

_From [webcompat.com](https://webcompat.com/) with ❤️_",1.0,"www.instagram.com - site is not usable - <!-- @browser: Firefox 94.0.2. -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4495.0 Safari/537.36 -->
<!-- @reported_with: unknown -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/94982 -->

**URL**: https://www.instagram.com/

**Browser / Version**: Firefox 94.0.2.
**Operating System**: Windows 10
**Tested Another Browser**: Yes Edge

**Problem type**: Site is not usable
**Description**: Page not loading correctly
**Steps to Reproduce**:
After clearing cache in firefox, instagram shows a white screen after logging in. 
Switching user agent resolved the issue.
No problems on other browsers (tested on Edge and Chrome). 

<details>
<summary>Browser Configuration</summary>
<ul>
  <li>None</li>
</ul>
</details>

_From [webcompat.com](https://webcompat.com/) with ❤️_",0,    site is not usable              url         browser   version    firefox          operating system    windows     tested another browser    yes edge    problem type    site is not usable   description    page not loading correctly   steps to reproduce    after clearing cache in firefox  instagram shows a white screen after logging in    switching user agent resolved the issue   no problems on other browsers  tested on edge and chrome        browser configuration       none        from     with ❤️ ,0
63386,14656708067.0,IssuesEvent,2020-12-28 14:01:25,fu1771695yongxie/wepy,https://api.github.com/repos/fu1771695yongxie/wepy,opened,CVE-2020-28275 (High) detected in cache-base-1.0.1.tgz,security vulnerability,"## CVE-2020-28275 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>cache-base-1.0.1.tgz</b></p></summary>

<p>Basic object cache with `get`, `set`, `del`, and `has` methods for node.js/javascript projects.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/cache-base/-/cache-base-1.0.1.tgz"">https://registry.npmjs.org/cache-base/-/cache-base-1.0.1.tgz</a></p>
<p>Path to dependency file: wepy/package.json</p>
<p>Path to vulnerable library: wepy/node_modules/cache-base/package.json</p>
<p>

Dependency Hierarchy:
  - babel-cli-6.26.0.tgz (Root Library)
    - chokidar-1.7.0.tgz
      - readdirp-2.2.1.tgz
        - micromatch-3.1.10.tgz
          - snapdragon-0.8.2.tgz
            - base-0.11.2.tgz
              - :x: **cache-base-1.0.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/fu1771695yongxie/wepy/commit/01d3dc60ddf82d562895250655097a09e9db1196"">01d3dc60ddf82d562895250655097a09e9db1196</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>  
  
Prototype pollution vulnerability in 'cache-base' versions 0.7.0 through 4.0.0 allows attacker to cause a denial of service and may lead to remote code execution.

<p>Publish Date: 2020-11-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28275>CVE-2020-28275</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2020-28275 (High) detected in cache-base-1.0.1.tgz - ## CVE-2020-28275 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>cache-base-1.0.1.tgz</b></p></summary>

<p>Basic object cache with `get`, `set`, `del`, and `has` methods for node.js/javascript projects.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/cache-base/-/cache-base-1.0.1.tgz"">https://registry.npmjs.org/cache-base/-/cache-base-1.0.1.tgz</a></p>
<p>Path to dependency file: wepy/package.json</p>
<p>Path to vulnerable library: wepy/node_modules/cache-base/package.json</p>
<p>

Dependency Hierarchy:
  - babel-cli-6.26.0.tgz (Root Library)
    - chokidar-1.7.0.tgz
      - readdirp-2.2.1.tgz
        - micromatch-3.1.10.tgz
          - snapdragon-0.8.2.tgz
            - base-0.11.2.tgz
              - :x: **cache-base-1.0.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/fu1771695yongxie/wepy/commit/01d3dc60ddf82d562895250655097a09e9db1196"">01d3dc60ddf82d562895250655097a09e9db1196</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>  
  
Prototype pollution vulnerability in 'cache-base' versions 0.7.0 through 4.0.0 allows attacker to cause a denial of service and may lead to remote code execution.

<p>Publish Date: 2020-11-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28275>CVE-2020-28275</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in cache base       tgz      cve       high severity vulnerability     vulnerable library    cache base       tgz      basic object cache with  get    set    del   and  has  methods for node js javascript projects    library home page   a href     path to dependency file  wepy package json   path to vulnerable library  wepy node modules cache base package json     dependency hierarchy      babel cli       tgz  root library        chokidar       tgz         readdirp       tgz           micromatch       tgz             snapdragon       tgz               base       tgz                  x    cache base       tgz    vulnerable library   found in head commit   a href     found in base branch   master              vulnerability details         prototype pollution vulnerability in  cache base  versions       through       allows attacker to cause a denial of service and may lead to remote code execution    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  high   for more information on   scores  click  a href                step up your open source security game with whitesource    ,0
52293,6608093716.0,IssuesEvent,2017-09-19 09:38:52,NG-ZORRO/ng-zorro-antd,https://api.github.com/repos/NG-ZORRO/ng-zorro-antd,closed,[bug] nz-select text truncation when nz-option has more text,type: ant-design,"<!--
1. 官方 issue 用于报告 bug 和需求建议，关于Angular的使用和开发问题在这里可能不会得到解答，感谢您的理解。
2. 建议使用英文进行提问，这样你的问题可以被更多的人阅读和回答。如果表达上确实较复杂，英文标题加中文描述也是可选的方案。
3. 报告 BUG 时请务必按照下列格式书写，并尽可能提供源代码、复现步骤、复现演示、GIF 演示等。我们和你一样都希望尽快解决问题，请不要浪费时间在互相追问上。
4. 注意你的 issue 格式，不适合阅读的格式会被忽视或直接关闭。
5. 如果需要粘贴源码，尽量避免截图并注意代码格式。关于如何在 Markdown 中书写代码可以参考：https://segmentfault.com/markdown
6. 抱怨不能解决问题，通畅有效和心情舒畅的交流才能解决。
-->

## I'm submitting a...
<!-- Check one of the following options with ""x"" -->
<pre><code>
[x] Bug report  <!-- Please search GitHub for a similar issue or PR before submitting -->
</code></pre>

## Current behavior
<!-- Describe how the issue manifests. -->

the html: 

```html
<nz-select [(ngModel)]=""s.s"" name=""s"" [nzAllowClear]=""false"">
    <nz-option nzValue="""" nzLabel=""状态不限""></nz-option>
    <nz-option nzValue=""1"" nzLabel=""正常""></nz-option>
    <nz-option nzValue=""2"" nzLabel=""已取消合作""></nz-option>
    <nz-option nzValue=""3"" nzLabel=""已删除但未被上传""></nz-option>
    <nz-option nzValue=""10"" nzLabel=""待提交""></nz-option>
    <nz-option nzValue=""11"" nzLabel=""待审核""></nz-option>
</nz-select>
```

screenshot:

![tim 20170919132401](https://user-images.githubusercontent.com/2987467/30576953-d4d36c40-9d3d-11e7-9cd0-01254c72d895.png)
",1.0,"[bug] nz-select text truncation when nz-option has more text - <!--
1. 官方 issue 用于报告 bug 和需求建议，关于Angular的使用和开发问题在这里可能不会得到解答，感谢您的理解。
2. 建议使用英文进行提问，这样你的问题可以被更多的人阅读和回答。如果表达上确实较复杂，英文标题加中文描述也是可选的方案。
3. 报告 BUG 时请务必按照下列格式书写，并尽可能提供源代码、复现步骤、复现演示、GIF 演示等。我们和你一样都希望尽快解决问题，请不要浪费时间在互相追问上。
4. 注意你的 issue 格式，不适合阅读的格式会被忽视或直接关闭。
5. 如果需要粘贴源码，尽量避免截图并注意代码格式。关于如何在 Markdown 中书写代码可以参考：https://segmentfault.com/markdown
6. 抱怨不能解决问题，通畅有效和心情舒畅的交流才能解决。
-->

## I'm submitting a...
<!-- Check one of the following options with ""x"" -->
<pre><code>
[x] Bug report  <!-- Please search GitHub for a similar issue or PR before submitting -->
</code></pre>

## Current behavior
<!-- Describe how the issue manifests. -->

the html: 

```html
<nz-select [(ngModel)]=""s.s"" name=""s"" [nzAllowClear]=""false"">
    <nz-option nzValue="""" nzLabel=""状态不限""></nz-option>
    <nz-option nzValue=""1"" nzLabel=""正常""></nz-option>
    <nz-option nzValue=""2"" nzLabel=""已取消合作""></nz-option>
    <nz-option nzValue=""3"" nzLabel=""已删除但未被上传""></nz-option>
    <nz-option nzValue=""10"" nzLabel=""待提交""></nz-option>
    <nz-option nzValue=""11"" nzLabel=""待审核""></nz-option>
</nz-select>
```

screenshot:

![tim 20170919132401](https://user-images.githubusercontent.com/2987467/30576953-d4d36c40-9d3d-11e7-9cd0-01254c72d895.png)
",0,  nz select text truncation when nz option has more text            官方 issue 用于报告 bug 和需求建议，关于angular的使用和开发问题在这里可能不会得到解答，感谢您的理解。     建议使用英文进行提问，这样你的问题可以被更多的人阅读和回答。如果表达上确实较复杂，英文标题加中文描述也是可选的方案。     报告 bug 时请务必按照下列格式书写，并尽可能提供源代码、复现步骤、复现演示、gif 演示等。我们和你一样都希望尽快解决问题，请不要浪费时间在互相追问上。     注意你的 issue 格式，不适合阅读的格式会被忽视或直接关闭。     如果需要粘贴源码，尽量避免截图并注意代码格式。关于如何在 markdown 中书写代码可以参考：      抱怨不能解决问题，通畅有效和心情舒畅的交流才能解决。            i m submitting a              bug report              current behavior       the html         html                                                               screenshot           ,0
43766,7064816639.0,IssuesEvent,2018-01-06 12:18:38,golang/go,https://api.github.com/repos/golang/go,closed,proposal: Documentation for Go package types and functions should have 'since GOVERSION' at the end,Documentation Proposal,"When browsing Go packages, it is impossible to know since when a type or a function is part of the language. In fact, off the top of my head, I don't know any feasible way to get this information, apart from:

- `git blame`ing the specified source (which won't work if there were styling adjustments / documentation updates)
- using that function/type and running a build across all Go versions and check when the build starts failing.
- browsing all Go release patch notes looking for the function/type in question.

All of these steps are very cumbersome.

A way to identify the version since when a package feature is available would be very handy, especially for projects that try to support multiple Go versions. In general, it would be very informative to browse a package and see when a feature was introduced, and enable the reader to load up the release notes of that version and see if they can find some motivation behind the feature. It could also be the last straw to make the reader finally upgrade to the latest version.

For example, Java does this and it truly has its benefits.

While the PROs are very strong, the CON obviously is that it is a lot of work to update the docs to include this information.
  ",1.0,"proposal: Documentation for Go package types and functions should have 'since GOVERSION' at the end - When browsing Go packages, it is impossible to know since when a type or a function is part of the language. In fact, off the top of my head, I don't know any feasible way to get this information, apart from:

- `git blame`ing the specified source (which won't work if there were styling adjustments / documentation updates)
- using that function/type and running a build across all Go versions and check when the build starts failing.
- browsing all Go release patch notes looking for the function/type in question.

All of these steps are very cumbersome.

A way to identify the version since when a package feature is available would be very handy, especially for projects that try to support multiple Go versions. In general, it would be very informative to browse a package and see when a feature was introduced, and enable the reader to load up the release notes of that version and see if they can find some motivation behind the feature. It could also be the last straw to make the reader finally upgrade to the latest version.

For example, Java does this and it truly has its benefits.

While the PROs are very strong, the CON obviously is that it is a lot of work to update the docs to include this information.
  ",1,proposal  documentation for go package types and functions should have  since goversion  at the end   when browsing go packages  it is impossible to know since when a type or a function is part of the language  in fact  off the top of my head  i don t know any feasible way to get this information  apart from        git blame ing the specified source  which won t work if there were styling adjustments   documentation updates     using that function type and running a build across all go versions and check when the build starts failing     browsing all go release patch notes looking for the function type in question     all of these steps are very cumbersome     a way to identify the version since when a package feature is available would be very handy  especially for projects that try to support multiple go versions  in general  it would be very informative to browse a package and see when a feature was introduced  and enable the reader to load up the release notes of that version and see if they can find some motivation behind the feature  it could also be the last straw to make the reader finally upgrade to the latest version     for example  java does this and it truly has its benefits     while the pros are very strong  the con obviously is that it is a lot of work to update the docs to include this information     ,1
58118,8230375841.0,IssuesEvent,2018-09-07 12:45:01,golang/go,https://api.github.com/repos/golang/go,closed,fmt: add examples,Community Documentation NeedsFix,"Let's add examples. I think it would be good to add examples to each function (if possible?) as well as to illustrate some points - not every example should make every point but it would be good to cover these.

- how do %d, %s, %q, %v differ

- how do you do left/right padding

- decimal formatting

- how does ""ln"" ending vary from ""f"" ending

When you open a change, put this at the bottom of the commit message:

```
Updates golang/go#27376.
```

That way gopherbot will post a comment here with a link to your CL.

Add a comment if you want to fix one and I'll put your name next to the func in question.

- [x] `func Errorf(format string, a ...interface{}) error`: @ianzapolsky

- [ ] func Fprint(w io.Writer, a ...interface{}) (n int, err error)

- [ ] `func Fprintf(w io.Writer, format string, a ...interface{}) (n int, err error)`: @MaerF0x0

- [x] `func Fprintln(w io.Writer, a ...interface{}) (n int, err error)`: @waits 

- [ ] `func Fscan(r io.Reader, a ...interface{}) (n int, err error)`: @andriisoldatenko

- [ ] func Fscanf(r io.Reader, format string, a ...interface{}) (n int, err error)

- [x] `func Fscanln(r io.Reader, a ...interface{}) (n int, err error)`: @mfrw

- [ ] func Print(a ...interface{}) (n int, err error)

- [ ] `func Printf(format string, a ...interface{}) (n int, err error)`: @mooreds 

- [x] `func Println(a ...interface{}) (n int, err error)`: @techmexdev

- [ ] func Scan(a ...interface{}) (n int, err error)

- [ ] func Scanf(format string, a ...interface{}) (n int, err error)

- [ ] func Scanln(a ...interface{}) (n int, err error)

- [ ] func Sprint(a ...interface{}) string

- [x] `func Sprintf(format string, a ...interface{}) string`: @venilnoronha

- [x] `func Sprintln(a ...interface{}) string`: @drewvanstone

- [ ] func Sscan(str string, a ...interface{}) (n int, err error)

- [ ] func Sscanf(str string, format string, a ...interface{}) (n int, err error)

- [ ] func Sscanln(str string, a ...interface{}) (n int, err error)

- [ ] type Formatter

- [ ] type GoStringer

- [ ] type ScanState

- [ ] type Scanner

- [ ] type State

- [x] type Stringer
",1.0,"fmt: add examples - Let's add examples. I think it would be good to add examples to each function (if possible?) as well as to illustrate some points - not every example should make every point but it would be good to cover these.

- how do %d, %s, %q, %v differ

- how do you do left/right padding

- decimal formatting

- how does ""ln"" ending vary from ""f"" ending

When you open a change, put this at the bottom of the commit message:

```
Updates golang/go#27376.
```

That way gopherbot will post a comment here with a link to your CL.

Add a comment if you want to fix one and I'll put your name next to the func in question.

- [x] `func Errorf(format string, a ...interface{}) error`: @ianzapolsky

- [ ] func Fprint(w io.Writer, a ...interface{}) (n int, err error)

- [ ] `func Fprintf(w io.Writer, format string, a ...interface{}) (n int, err error)`: @MaerF0x0

- [x] `func Fprintln(w io.Writer, a ...interface{}) (n int, err error)`: @waits 

- [ ] `func Fscan(r io.Reader, a ...interface{}) (n int, err error)`: @andriisoldatenko

- [ ] func Fscanf(r io.Reader, format string, a ...interface{}) (n int, err error)

- [x] `func Fscanln(r io.Reader, a ...interface{}) (n int, err error)`: @mfrw

- [ ] func Print(a ...interface{}) (n int, err error)

- [ ] `func Printf(format string, a ...interface{}) (n int, err error)`: @mooreds 

- [x] `func Println(a ...interface{}) (n int, err error)`: @techmexdev

- [ ] func Scan(a ...interface{}) (n int, err error)

- [ ] func Scanf(format string, a ...interface{}) (n int, err error)

- [ ] func Scanln(a ...interface{}) (n int, err error)

- [ ] func Sprint(a ...interface{}) string

- [x] `func Sprintf(format string, a ...interface{}) string`: @venilnoronha

- [x] `func Sprintln(a ...interface{}) string`: @drewvanstone

- [ ] func Sscan(str string, a ...interface{}) (n int, err error)

- [ ] func Sscanf(str string, format string, a ...interface{}) (n int, err error)

- [ ] func Sscanln(str string, a ...interface{}) (n int, err error)

- [ ] type Formatter

- [ ] type GoStringer

- [ ] type ScanState

- [ ] type Scanner

- [ ] type State

- [x] type Stringer
",1,fmt  add examples   let s add examples  i think it would be good to add examples to each function  if possible   as well as to illustrate some points   not every example should make every point but it would be good to cover these       how do  d   s   q   v differ      how do you do left right padding      decimal formatting      how does  ln  ending vary from  f  ending    when you open a change  put this at the bottom of the commit message          updates golang go            that way gopherbot will post a comment here with a link to your cl     add a comment if you want to fix one and i ll put your name next to the func in question          func errorf format string  a    interface    error    ianzapolsky        func fprint w io writer  a    interface     n int  err error          func fprintf w io writer  format string  a    interface     n int  err error               func fprintln w io writer  a    interface     n int  err error     waits          func fscan r io reader  a    interface     n int  err error     andriisoldatenko        func fscanf r io reader  format string  a    interface     n int  err error          func fscanln r io reader  a    interface     n int  err error     mfrw        func print a    interface     n int  err error          func printf format string  a    interface     n int  err error     mooreds          func println a    interface     n int  err error     techmexdev        func scan a    interface     n int  err error         func scanf format string  a    interface     n int  err error         func scanln a    interface     n int  err error         func sprint a    interface    string         func sprintf format string  a    interface    string    venilnoronha         func sprintln a    interface    string    drewvanstone        func sscan str string  a    interface     n int  err error         func sscanf str string  format string  a    interface     n int  err error         func sscanln str string  a    interface     n int  err error         type formatter        type gostringer        type scanstate        type scanner        type state        type stringer  ,1
21592,4727222019.0,IssuesEvent,2016-10-18 12:54:20,golang/go,https://api.github.com/repos/golang/go,closed,io: PipeWriter.Write should not block when writing zero bytes,Documentation NeedsDecision,"`io.PipeWriter.Write([]byte{})` blocks when no readers are waiting at the other end of the pipe. To unblock the pipe **zero** or more bytes must be read from `io.PipeWriter.Read`.

I expect `io.PipeWriter.Write([]byte{})` to not ever block.

See https://groups.google.com/forum/#!topic/golang-nuts/nRPhBt0zoAM for the discussion.

See http://play.golang.org/p/MNSyKafKYf for an example.",1.0,"io: PipeWriter.Write should not block when writing zero bytes - `io.PipeWriter.Write([]byte{})` blocks when no readers are waiting at the other end of the pipe. To unblock the pipe **zero** or more bytes must be read from `io.PipeWriter.Read`.

I expect `io.PipeWriter.Write([]byte{})` to not ever block.

See https://groups.google.com/forum/#!topic/golang-nuts/nRPhBt0zoAM for the discussion.

See http://play.golang.org/p/MNSyKafKYf for an example.",1,io  pipewriter write should not block when writing zero bytes    io pipewriter write  byte     blocks when no readers are waiting at the other end of the pipe  to unblock the pipe   zero   or more bytes must be read from  io pipewriter read      i expect  io pipewriter write  byte     to not ever block     see   for the discussion     see   for an example ,1
58268,8244041733.0,IssuesEvent,2018-09-11 03:53:56,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: documentation for 'fmt' subcommand is not detected as a section,Documentation NeedsFix,"### What did you do?

https://golang.org/cmd/go/


### What did you expect to see?

Section headers for each subcommand


### What did you see instead?

![znjytnggikm](https://user-images.githubusercontent.com/5200974/45323403-ffc8ea80-b518-11e8-9ae2-e78d742a73f0.png)
",1.0,"cmd/go: documentation for 'fmt' subcommand is not detected as a section - ### What did you do?

https://golang.org/cmd/go/


### What did you expect to see?

Section headers for each subcommand


### What did you see instead?

![znjytnggikm](https://user-images.githubusercontent.com/5200974/45323403-ffc8ea80-b518-11e8-9ae2-e78d742a73f0.png)
",1,cmd go  documentation for  fmt  subcommand is not detected as a section       what did you do                what did you expect to see     section headers for each subcommand          what did you see instead           ,1
23366,21768087117.0,IssuesEvent,2022-05-13 05:54:12,Bridgeconn/VachanAppReact,https://api.github.com/repos/Bridgeconn/VachanAppReact,closed,Bible Stories : Enhancement :Include the title Bible stories on the header in the content page,Usability VachanGo1.3.0-alpha.4,"Issue raised by Rina Ma'am 
Currently, the title on the drawer ie Bible stories does not display on the header in the content page.
Since the other features such as Infographics /Videos displays the same name as in the drawer, it is better to let it remain uniform for UX.

Expected : The user experience should be enhanced to include the title Bibles stories on  the header in the content page as in the drawer
",True,"Bible Stories : Enhancement :Include the title Bible stories on the header in the content page - Issue raised by Rina Ma'am 
Currently, the title on the drawer ie Bible stories does not display on the header in the content page.
Since the other features such as Infographics /Videos displays the same name as in the drawer, it is better to let it remain uniform for UX.

Expected : The user experience should be enhanced to include the title Bibles stories on  the header in the content page as in the drawer
",0,bible stories   enhancement  include the title bible stories on the header in the content page   issue raised by rina ma am   currently  the title on the drawer ie bible stories does not display on the header in the content page   since the other features such as infographics  videos displays the same name as in the drawer  it is better to let it remain uniform for ux     expected   the user experience should be enhanced to include the title bibles stories on  the header in the content page as in the drawer  ,0
244191,18750403998.0,IssuesEvent,2021-11-05 00:36:26,golang/go,https://api.github.com/repos/golang/go,closed,time: mention reference date used for formatting in time.Parse,Documentation WaitingForInfo NeedsInvestigation,"As of go1.17.1

This is a documentation issue so environment and recreation issues are irrelevent.

The documentation for the time.Parse fails to mention the ""magical reference date"" 
(https://programming.guide/go/format-parse-string-time-date-example.html)

This makes working with date parsing much harder than it needs to be.",1.0,"time: mention reference date used for formatting in time.Parse - As of go1.17.1

This is a documentation issue so environment and recreation issues are irrelevent.

The documentation for the time.Parse fails to mention the ""magical reference date"" 
(https://programming.guide/go/format-parse-string-time-date-example.html)

This makes working with date parsing much harder than it needs to be.",1,time  mention reference date used for formatting in time parse   as of          this is a documentation issue so environment and recreation issues are irrelevent     the documentation for the time parse fails to mention the  magical reference date          this makes working with date parsing much harder than it needs to be ,1
28771,5536566526.0,IssuesEvent,2017-03-21 19:57:55,golang/go,https://api.github.com/repos/golang/go,closed,"doc: figure out, document amd64 minimum requirements",Documentation NeedsDecision,"In https://golang.org/cl/38320, @khr adds POPCOUNT intrinsics for amd64.

I realize that our https://golang.org/wiki/MinimumRequirements doesn't say anything about GOARCH=amd64. (only 386)

Which version of amd64 do we assume? Decide and document.

/cc @randall77 @ianlancetaylor @griesemer @rsc @mdempsky @josharian @minux @cherrymui @aclements ",1.0,"doc: figure out, document amd64 minimum requirements - In https://golang.org/cl/38320, @khr adds POPCOUNT intrinsics for amd64.

I realize that our https://golang.org/wiki/MinimumRequirements doesn't say anything about GOARCH=amd64. (only 386)

Which version of amd64 do we assume? Decide and document.

/cc @randall77 @ianlancetaylor @griesemer @rsc @mdempsky @josharian @minux @cherrymui @aclements ",1,doc  figure out  document   minimum requirements   in    khr adds popcount intrinsics for       i realize that our   doesn t say anything about goarch     only       which version of   do we assume  decide and document      cc     ianlancetaylor  griesemer  rsc  mdempsky  josharian  minux  cherrymui  aclements ,1
290008,8881374060.0,IssuesEvent,2019-01-14 09:57:12,Activiti/Activiti,https://api.github.com/repos/Activiti/Activiti,closed,RuntimeBundle - TaskVariableController setVariables taskId param not used,priority1,"The endpoint to **setVariables** for a task receives an _taskId_ as a path param is never used, in the end is used the one sent in the body of request. As @erdemedeiros suggested I think this one should be set in the SetTaskVariablesPayload as taskId. This should be an easy fix.",1.0,"RuntimeBundle - TaskVariableController setVariables taskId param not used - The endpoint to **setVariables** for a task receives an _taskId_ as a path param is never used, in the end is used the one sent in the body of request. As @erdemedeiros suggested I think this one should be set in the SetTaskVariablesPayload as taskId. This should be an easy fix.",0,runtimebundle   taskvariablecontroller setvariables taskid param not used   the endpoint to   setvariables   for a task receives an  taskid  as a path param is never used  in the end is used the one sent in the body of request  as  erdemedeiros suggested i think this one should be set in the settaskvariablespayload as taskid  this should be an easy fix ,0
62996,8650730769.0,IssuesEvent,2018-11-26 23:43:33,golang/go,https://api.github.com/repos/golang/go,closed,doc: memclrNoHeapPointers documentation looks strange,Documentation,"https://golang.org/pkg/runtime/?m=all#memclrNoHeapPointers
<img width=""762"" alt=""2018-11-26 19 05 01"" src=""https://user-images.githubusercontent.com/2682948/49026188-44763080-f1ae-11e8-8b32-11f69e2d2fd5.png"">
This comment looks strange in Chrome(70.0.3538.102) also check in safari. Seems text recognized as part of code sample.",1.0,"doc: memclrNoHeapPointers documentation looks strange - https://golang.org/pkg/runtime/?m=all#memclrNoHeapPointers
<img width=""762"" alt=""2018-11-26 19 05 01"" src=""https://user-images.githubusercontent.com/2682948/49026188-44763080-f1ae-11e8-8b32-11f69e2d2fd5.png"">
This comment looks strange in Chrome(70.0.3538.102) also check in safari. Seems text recognized as part of code sample.",1,doc  memclrnoheappointers documentation looks strange       img width     alt               src     this comment looks strange in chrome          also check in safari  seems text recognized as part of code sample ,1
15977,3996484560.0,IssuesEvent,2016-05-10 18:56:06,golang/go,https://api.github.com/repos/golang/go,closed,website: windows download page gives bad advice,Documentation,"Please answer these questions before submitting your issue. Thanks!

1. What version of Go are you using (`go version`)?
go1.6.2 windows/amd64

2. What operating system and processor architecture are you using (`go env`)?
Windows 8.1, amd64

3. What did you do?
Download Go for the first time, to see what the language is about.

4. What did you expect to see?
Useful information on setting up and using Go.

5. What did you see instead?

Most of the advice on the website is downright wrong.  For example, the website says to set GOPATH:

    C:\> set GOPATH=%HOME%\work

On Windows, following this advice will lead to a go installation that does not work.  First, the variable is named %HOMEPATH%, and second, the variable is relative so it should be %HOMEDRIVE%\%HOMEPATH%.

After manually correcting GOPATH, I tried building the ""Hello, world!"" example, also from the page.

The page then illustrates how to build the .go file, using ""go install"" (?).  This does not work:

    C:\Users\Sean\Code\go\hello>go install github.com/user/hello
    can't load package: package github.com/user/hello: cannot find package ""github.com/user/hello"" in any of:
            C:\Go\src\github.com\user\hello (from $GOROOT)
            C:\Users\Sean\Code\go\src\github.com\user\hello (from $GOPATH)
    
    C:\Users\Sean\Code\go\hello>

As a brand-new user, this is very confusing.",1.0,"website: windows download page gives bad advice - Please answer these questions before submitting your issue. Thanks!

1. What version of Go are you using (`go version`)?
go1.6.2 windows/amd64

2. What operating system and processor architecture are you using (`go env`)?
Windows 8.1, amd64

3. What did you do?
Download Go for the first time, to see what the language is about.

4. What did you expect to see?
Useful information on setting up and using Go.

5. What did you see instead?

Most of the advice on the website is downright wrong.  For example, the website says to set GOPATH:

    C:\> set GOPATH=%HOME%\work

On Windows, following this advice will lead to a go installation that does not work.  First, the variable is named %HOMEPATH%, and second, the variable is relative so it should be %HOMEDRIVE%\%HOMEPATH%.

After manually correcting GOPATH, I tried building the ""Hello, world!"" example, also from the page.

The page then illustrates how to build the .go file, using ""go install"" (?).  This does not work:

    C:\Users\Sean\Code\go\hello>go install github.com/user/hello
    can't load package: package github.com/user/hello: cannot find package ""github.com/user/hello"" in any of:
            C:\Go\src\github.com\user\hello (from $GOROOT)
            C:\Users\Sean\Code\go\src\github.com\user\hello (from $GOPATH)
    
    C:\Users\Sean\Code\go\hello>

As a brand-new user, this is very confusing.",1,website  windows download page gives bad advice   please answer these questions before submitting your issue  thanks        what version of go are you using   go version           windows         what operating system and processor architecture are you using   go env     windows              what did you do   download go for the first time  to see what the language is about        what did you expect to see   useful information on setting up and using go        what did you see instead     most of the advice on the website is downright wrong   for example  the website says to set gopath         c    set gopath  home  work    on windows  following this advice will lead to a go installation that does not work   first  the variable is named  homepath   and second  the variable is relative so it should be  homedrive   homepath      after manually correcting gopath  i tried building the  hello  world   example  also from the page     the page then illustrates how to build the  go file  using  go install        this does not work         c  users sean code go hello go install github com user hello      can t load package  package github com user hello  cannot find package  github com user hello  in any of               c  go src github com user hello  from  goroot               c  users sean code go src github com user hello  from  gopath             c  users sean code go hello     as a brand new user  this is very confusing ,1
70500,9419186958.0,IssuesEvent,2019-04-10 21:12:32,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/internal/lsp: Wrong symbol kind for the `textDocument/symbol`.,Documentation NeedsFix,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.12 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/henrywong/Library/Caches/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/henrywong/workspace/gopath""
GOPROXY=""""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.12/libexec""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/1.12/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/fm/bk0wqlkj523gdp9pbtnyvxmm0000gn/T/go-build954865857=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?
Get the `textDocument/symbol` for the go source file.
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

```go
// The symbol kind for `int_basic_alias` should be `NumberSymbol`, not `StructSymbol`.
type int_basic_alias = int
```


### What did you expect to see?
For the type alias, lsp should strip off the type alias to get the essential type. And compute the correct symbol based on the essential type.
```go
// The symbol kind for `int_basic_alias` should be `NumberSymbol`
type int_basic_alias = int
```
### What did you see instead?
```go
// The symbol kind for `int_basic_alias` is `StructSymbol`
type int_basic_alias = int
```",1.0,"x/tools/internal/lsp: Wrong symbol kind for the `textDocument/symbol`. - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.12 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/henrywong/Library/Caches/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/henrywong/workspace/gopath""
GOPROXY=""""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.12/libexec""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/1.12/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/fm/bk0wqlkj523gdp9pbtnyvxmm0000gn/T/go-build954865857=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?
Get the `textDocument/symbol` for the go source file.
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

```go
// The symbol kind for `int_basic_alias` should be `NumberSymbol`, not `StructSymbol`.
type int_basic_alias = int
```


### What did you expect to see?
For the type alias, lsp should strip off the type alias to get the essential type. And compute the correct symbol based on the essential type.
```go
// The symbol kind for `int_basic_alias` should be `NumberSymbol`
type int_basic_alias = int
```
### What did you see instead?
```go
// The symbol kind for `int_basic_alias` is `StructSymbol`
type int_basic_alias = int
```",1,x tools internal lsp  wrong symbol kind for the  textdocument symbol              what version of go are you using   go version            go version  go version     darwin             does this issue reproduce with the latest release     yes         what operating system and processor architecture are you using   go env          go env  output       go env  goarch      gobin     gocache   users henrywong library caches go build   goexe     goflags     gohostarch      gohostos  darwin   goos  darwin   gopath   users henrywong workspace gopath   goproxy     gorace     goroot   usr local cellar go     libexec   gotmpdir     gotooldir   usr local cellar go     libexec pkg tool darwin     gccgo  gccgo   cc  clang   cxx  clang     cgo enabled      gomod     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders fm   t go    tmp go build  gno record gcc switches  fno common             what did you do   get the  textdocument symbol  for the go source file         if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best             go     the symbol kind for  int basic alias  should be  numbersymbol   not  structsymbol    type int basic alias   int               what did you expect to see   for the type alias  lsp should strip off the type alias to get the essential type  and compute the correct symbol based on the essential type      go     the symbol kind for  int basic alias  should be  numbersymbol   type int basic alias   int           what did you see instead      go     the symbol kind for  int basic alias  is  structsymbol   type int basic alias   int     ,1
454172,13095962992.0,IssuesEvent,2020-08-03 14:56:22,craftercms/craftercms,https://api.github.com/repos/craftercms/craftercms,closed,[studio-ui] Long username overlaps with some columns in Studio Dashboard,bug priority: medium,"## Describe the bug
Long usernames, for example, those that come from corporate emails, are causing overlapping of text in some sections of the Studio Dashboard

## To Reproduce
Steps to reproduce the behavior:

0. Create a site from any blueprint.
1. Create a user with a long username value, example `yacdaniel.example@example.com` Add the user to the `site_admin` group
2. Create 3 different pages, send 1 page to live, send another page to a publish schedule, and leave the last page in an In Progress state.
3. Open your browser tools then go to the device toolbar and select the resolution `Laptop with HiDPI Screen`, or set manually a resolution of `1440x900` 
![imagen](https://user-images.githubusercontent.com/6722074/87994202-9ec1b480-caa9-11ea-9474-9f64ad1b5fd0.png)
3. Go to the Studio Dashboard. Click `Show ""In-Progress"" Items` in the `Items Waiting for Approval` widget. 
4. See overlaping of text in `Last Edited By` & `Last Edited` 
![imagen](https://user-images.githubusercontent.com/6722074/87994396-0c6de080-caaa-11ea-8d09-c71ff92cab73.png)
5. Check `My Recent Activity` widget, See overlapinf of text in `Last Edited By` & `My Last Edit` 
![imagen](https://user-images.githubusercontent.com/6722074/87994537-68d10000-caaa-11ea-8ccb-ec70abfbd40d.png)

## Expected behavior
Text from username should not overlap with other columns' information.

## Screenshots
N/A

## Logs
N/A

## Specs
### Version
`3.1.x` & `3.2.x`

### OS
Any

### Browser
Chrome & Firefox

## Additional context
The max lenght of a username is going to be defined here https://github.com/craftercms/craftercms/issues/4198
",1.0,"[studio-ui] Long username overlaps with some columns in Studio Dashboard - ## Describe the bug
Long usernames, for example, those that come from corporate emails, are causing overlapping of text in some sections of the Studio Dashboard

## To Reproduce
Steps to reproduce the behavior:

0. Create a site from any blueprint.
1. Create a user with a long username value, example `yacdaniel.example@example.com` Add the user to the `site_admin` group
2. Create 3 different pages, send 1 page to live, send another page to a publish schedule, and leave the last page in an In Progress state.
3. Open your browser tools then go to the device toolbar and select the resolution `Laptop with HiDPI Screen`, or set manually a resolution of `1440x900` 
![imagen](https://user-images.githubusercontent.com/6722074/87994202-9ec1b480-caa9-11ea-9474-9f64ad1b5fd0.png)
3. Go to the Studio Dashboard. Click `Show ""In-Progress"" Items` in the `Items Waiting for Approval` widget. 
4. See overlaping of text in `Last Edited By` & `Last Edited` 
![imagen](https://user-images.githubusercontent.com/6722074/87994396-0c6de080-caaa-11ea-8d09-c71ff92cab73.png)
5. Check `My Recent Activity` widget, See overlapinf of text in `Last Edited By` & `My Last Edit` 
![imagen](https://user-images.githubusercontent.com/6722074/87994537-68d10000-caaa-11ea-8ccb-ec70abfbd40d.png)

## Expected behavior
Text from username should not overlap with other columns' information.

## Screenshots
N/A

## Logs
N/A

## Specs
### Version
`3.1.x` & `3.2.x`

### OS
Any

### Browser
Chrome & Firefox

## Additional context
The max lenght of a username is going to be defined here https://github.com/craftercms/craftercms/issues/4198
",0,  long username overlaps with some columns in studio dashboard      describe the bug  long usernames  for example  those that come from corporate emails  are causing overlapping of text in some sections of the studio dashboard       to reproduce  steps to reproduce the behavior        create a site from any blueprint      create a user with a long username value  example  yacdaniel example example com  add the user to the  site admin  group     create   different pages  send   page to live  send another page to a publish schedule  and leave the last page in an in progress state      open your browser tools then go to the device toolbar and select the resolution  laptop with hidpi screen   or set manually a resolution of                go to the studio dashboard  click  show  in progress  items  in the  items waiting for approval  widget       see overlaping of text in  last edited by     last edited             check  my recent activity  widget  see overlapinf of text in  last edited by     my last edit               expected behavior  text from username should not overlap with other columns  information        screenshots  n a       logs  n a       specs      version       x         x         os  any        browser  chrome   firefox       additional context  the max lenght of a username is going to be defined here    ,0
7405,2610366797.0,IssuesEvent,2015-02-26 19:58:30,chrsmith/scribefire-chrome,https://api.github.com/repos/chrsmith/scribefire-chrome,closed,Won't authenticate to my wordpress blog... ,auto-migrated Priority-Medium Type-Defect,"```
What's the problem?
When I go through the connect a blog process, it seems to authenticate on the 
pop-up window, then comes up with a 'well this is embarrasing' message in the 
scribefire browser window...

What browser are you using?
Firefox 21 on linux

What version of ScribeFire are you running?
Latest linux..
```

-----
Original issue reported on code.google.com by `nathansu...@gmail.com` on 27 Jun 2013 at 10:05",1.0,"Won't authenticate to my wordpress blog...  - ```
What's the problem?
When I go through the connect a blog process, it seems to authenticate on the 
pop-up window, then comes up with a 'well this is embarrasing' message in the 
scribefire browser window...

What browser are you using?
Firefox 21 on linux

What version of ScribeFire are you running?
Latest linux..
```

-----
Original issue reported on code.google.com by `nathansu...@gmail.com` on 27 Jun 2013 at 10:05",0,won t authenticate to my wordpress blog           what s the problem  when i go through the connect a blog process  it seems to authenticate on the  pop up window  then comes up with a  well this is embarrasing  message in the  scribefire browser window     what browser are you using  firefox   on linux  what version of scribefire are you running  latest linux              original issue reported on code google com by  nathansu    gmail com  on   jun   at    ,0
330234,28360883540.0,IssuesEvent,2023-04-12 10:38:15,hazelcast/hazelcast,https://api.github.com/repos/hazelcast/hazelcast,opened,com.hazelcast.jet.mongodb.MongoSinkResilienceTest.testSink_networkCutoff,Type: Test-Failure Source: Internal Team: Platform,"_master_ (commit 68d95b261950a1dfdc55d205065a1cc430b2345e)

Failed on ibm-8: https://jenkins.hazelcast.com/view/Official%20Builds/job/Hazelcast-master-IbmJDK8-nightly/99/testReport/com.hazelcast.jet.mongodb/MongoSinkResilienceTest/testSink_networkCutoff/
<details><summary>Stacktrace:</summary>

```
java.lang.AssertionError: expected:<148> but was:<20>
	at org.junit.Assert.fail(Assert.java:89)
	at org.junit.Assert.failNotEquals(Assert.java:835)
	at org.junit.Assert.assertEquals(Assert.java:647)
	at org.junit.Assert.assertEquals(Assert.java:633)
	at com.hazelcast.jet.mongodb.MongoSinkResilienceTest.lambda$sinkNetworkTest$4(MongoSinkResilienceTest.java:242)
	at com.hazelcast.test.HazelcastTestSupport.assertTrueEventually(HazelcastTestSupport.java:1288)
	at com.hazelcast.test.HazelcastTestSupport.assertTrueEventually(HazelcastTestSupport.java:1392)
	at com.hazelcast.jet.mongodb.MongoSinkResilienceTest.sinkNetworkTest(MongoSinkResilienceTest.java:241)
	at com.hazelcast.jet.mongodb.MongoSinkResilienceTest.testSink_networkCutoff(MongoSinkResilienceTest.java:165)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
	at java.lang.reflect.Method.invoke(Method.java:508)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at com.hazelcast.test.FailOnTimeoutStatement$CallableStatement.call(FailOnTimeoutStatement.java:115)
	at com.hazelcast.test.FailOnTimeoutStatement$CallableStatement.call(FailOnTimeoutStatement.java:107)
	at java.util.concurrent.FutureTask.run(FutureTask.java:277)
	at java.lang.Thread.run(Thread.java:825)

```
</details>

Standard output can be found here - https://s3.console.aws.amazon.com/s3/buckets/j-artifacts/Hazelcast-master-IbmJDK8-nightly/99/
",1.0,"com.hazelcast.jet.mongodb.MongoSinkResilienceTest.testSink_networkCutoff - _master_ (commit 68d95b261950a1dfdc55d205065a1cc430b2345e)

Failed on ibm-8: https://jenkins.hazelcast.com/view/Official%20Builds/job/Hazelcast-master-IbmJDK8-nightly/99/testReport/com.hazelcast.jet.mongodb/MongoSinkResilienceTest/testSink_networkCutoff/
<details><summary>Stacktrace:</summary>

```
java.lang.AssertionError: expected:<148> but was:<20>
	at org.junit.Assert.fail(Assert.java:89)
	at org.junit.Assert.failNotEquals(Assert.java:835)
	at org.junit.Assert.assertEquals(Assert.java:647)
	at org.junit.Assert.assertEquals(Assert.java:633)
	at com.hazelcast.jet.mongodb.MongoSinkResilienceTest.lambda$sinkNetworkTest$4(MongoSinkResilienceTest.java:242)
	at com.hazelcast.test.HazelcastTestSupport.assertTrueEventually(HazelcastTestSupport.java:1288)
	at com.hazelcast.test.HazelcastTestSupport.assertTrueEventually(HazelcastTestSupport.java:1392)
	at com.hazelcast.jet.mongodb.MongoSinkResilienceTest.sinkNetworkTest(MongoSinkResilienceTest.java:241)
	at com.hazelcast.jet.mongodb.MongoSinkResilienceTest.testSink_networkCutoff(MongoSinkResilienceTest.java:165)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
	at java.lang.reflect.Method.invoke(Method.java:508)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at com.hazelcast.test.FailOnTimeoutStatement$CallableStatement.call(FailOnTimeoutStatement.java:115)
	at com.hazelcast.test.FailOnTimeoutStatement$CallableStatement.call(FailOnTimeoutStatement.java:107)
	at java.util.concurrent.FutureTask.run(FutureTask.java:277)
	at java.lang.Thread.run(Thread.java:825)

```
</details>

Standard output can be found here - https://s3.console.aws.amazon.com/s3/buckets/j-artifacts/Hazelcast-master-IbmJDK8-nightly/99/
",0,com hazelcast jet mongodb mongosinkresiliencetest testsink networkcutoff    master   commit       failed on ibm         stacktrace           java lang assertionerror  expected   but was    	at org junit assert fail assert java     	at org junit assert failnotequals assert java     	at org junit assert assertequals assert java     	at org junit assert assertequals assert java     	at com hazelcast jet mongodb mongosinkresiliencetest lambda sinknetworktest   mongosinkresiliencetest java     	at com hazelcast test hazelcasttestsupport asserttrueeventually hazelcasttestsupport java     	at com hazelcast test hazelcasttestsupport asserttrueeventually hazelcasttestsupport java     	at com hazelcast jet mongodb mongosinkresiliencetest sinknetworktest mongosinkresiliencetest java     	at com hazelcast jet mongodb mongosinkresiliencetest testsink networkcutoff mongosinkresiliencetest java     	at sun reflect nativemethodaccessorimpl   native method   	at sun reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java     	at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java     	at java lang reflect method invoke method java     	at org junit runners model frameworkmethod   runreflectivecall frameworkmethod java     	at org junit internal runners model reflectivecallable run reflectivecallable java     	at org junit runners model frameworkmethod invokeexplosively frameworkmethod java     	at org junit internal runners statements invokemethod evaluate invokemethod java     	at com hazelcast test failontimeoutstatement callablestatement call failontimeoutstatement java     	at com hazelcast test failontimeoutstatement callablestatement call failontimeoutstatement java     	at java util concurrent futuretask run futuretask java     	at java lang thread run thread java                 standard output can be found here      ,0
55135,7962801155.0,IssuesEvent,2018-07-13 15:22:15,golang/go,https://api.github.com/repos/golang/go,opened,doc: add release notes for change in vet printf detection,Documentation,"Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?

```
go version devel +8a330454dc Fri Jul 13 03:53:00 2018 +0000 linux/amd64
```

### Does this issue reproduce with the latest release?

No, working with Go tip.

### What operating system and processor architecture are you using (`go env`)?

```
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/myitcv/.cache/go-build""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/tmp/tmp.sI0jAUcdXy""
GOPROXY=""""
GORACE=""""
GOROOT=""/home/myitcv/gos""
GOTMPDIR=""""
GOTOOLDIR=""/home/myitcv/gos/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build282886001=/tmp/go-build -gno-record-gcc-switches""
```

### What did you do?

Not a bug, but a suggestion for a release note.

Discovered whilst trying out the new `go` tool module support, upgrading https://github.com/gobuffalo/buffalo to be a Go module.

```
cd `mktemp -d`
export GOPATH=$PWD
mkdir -p src/example.com/hello
cd src/example.com/hello
cat <<EOD > main.go
package main

import ""fmt""

type T struct{}

func (t *T) String(s string, args ...interface{}) string {
    v := s
    if len(args) > 0 {
        v = fmt.Sprintf(s, args...)
    }
    return v
}

func main() {
    var t *T
    t.String(""<%="")
}
EOD
go test
```

### What did you expect to see?

A release note at https://tip.golang.org/doc/go1.11 giving details about the new `*printf` detection that now reports the above as an error:

```
# example.com/hello
./main.go:17: T.String format %= has unknown verb =
```

### What did you see instead?

No release notes 😄 

Not critical, but I suspect this will catch out a few people. Buffalo had a number of instances because of the templating language, Plush, it uses.

**/cc** @rsc ",1.0,"doc: add release notes for change in vet printf detection - Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?

```
go version devel +8a330454dc Fri Jul 13 03:53:00 2018 +0000 linux/amd64
```

### Does this issue reproduce with the latest release?

No, working with Go tip.

### What operating system and processor architecture are you using (`go env`)?

```
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/myitcv/.cache/go-build""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/tmp/tmp.sI0jAUcdXy""
GOPROXY=""""
GORACE=""""
GOROOT=""/home/myitcv/gos""
GOTMPDIR=""""
GOTOOLDIR=""/home/myitcv/gos/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build282886001=/tmp/go-build -gno-record-gcc-switches""
```

### What did you do?

Not a bug, but a suggestion for a release note.

Discovered whilst trying out the new `go` tool module support, upgrading https://github.com/gobuffalo/buffalo to be a Go module.

```
cd `mktemp -d`
export GOPATH=$PWD
mkdir -p src/example.com/hello
cd src/example.com/hello
cat <<EOD > main.go
package main

import ""fmt""

type T struct{}

func (t *T) String(s string, args ...interface{}) string {
    v := s
    if len(args) > 0 {
        v = fmt.Sprintf(s, args...)
    }
    return v
}

func main() {
    var t *T
    t.String(""<%="")
}
EOD
go test
```

### What did you expect to see?

A release note at https://tip.golang.org/doc/go1.11 giving details about the new `*printf` detection that now reports the above as an error:

```
# example.com/hello
./main.go:17: T.String format %= has unknown verb =
```

### What did you see instead?

No release notes 😄 

Not critical, but I suspect this will catch out a few people. Buffalo had a number of instances because of the templating language, Plush, it uses.

**/cc** @rsc ",1,doc  add release notes for change in vet printf detection   please answer these questions before submitting your issue  thanks           what version of go are you using   go version            go version devel    fri jul              linux               does this issue reproduce with the latest release     no  working with go tip         what operating system and processor architecture are you using   go env            goarch      gobin     gocache   home myitcv  cache go build   goexe     gohostarch      gohostos  linux   goos  linux   gopath   tmp tmp     goproxy     gorace     goroot   home myitcv gos   gotmpdir     gotooldir   home myitcv gos pkg tool linux     gccgo  gccgo   cc  gcc   cxx  g     cgo enabled      gomod     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches              what did you do     not a bug  but a suggestion for a release note     discovered whilst trying out the new  go  tool module support  upgrading   to be a go module          cd  mktemp  d   export gopath  pwd  mkdir  p src example com hello  cd src example com hello  cat   main go  package main    import  fmt     type t struct      func  t  t  string s string  args    interface    string        v    s      if len args                 v   fmt sprintf s  args                 return v       func main          var t  t      t string            eod  go test             what did you expect to see     a release note at   giving details about the new   printf  detection that now reports the above as an error            example com hello    main go    t string format    has unknown verb               what did you see instead     no release notes 😄     not critical  but i suspect this will catch out a few people  buffalo had a number of instances because of the templating language  plush  it uses        cc    rsc ,1
214826,16614438771.0,IssuesEvent,2021-06-02 15:04:47,camunda-cloud/zeebe,https://api.github.com/repos/camunda-cloud/zeebe,opened,SmallMessageSizeTest#shouldSkipJobsThatExceedMessageSize is flaky,Type: Unstable Test,"**Summary**

> Try to answer the following as best as possible

- How often does the test fail? at least twice
- Does it block your work? blocked a merge :slightly_smiling_face: 
- Do we suspect that it is a real failure? no idea, probably not

**Failures**

<details><summary>Example assertion failure</summary>
<pre>
io.camunda.zeebe.client.api.command.ClientException: Timed out waiting on client response
	at io.camunda.zeebe.client.impl.ZeebeClientFutureImpl.join(ZeebeClientFutureImpl.java:65)
	at io.camunda.zeebe.broker.it.network.SmallMessageSizeTest.shouldSkipJobsThatExceedMessageSize(SmallMessageSizeTest.java:77)
</pre>
</details>

**Hypotheses**

None

**Logs**

<details><summary>Logs</summary>
<pre>
Standard Output
14:04:07.782 [] [main] INFO  io.camunda.zeebe.test - Test failed, following records were exported:
14:04:07.833 [] [main] INFO  io.camunda.zeebe.test - Compact log representation:
--------
	['C'ommand/'E'event/'R'ejection] [valueType] [intent] - #[position]->#[source record position]  P[partitionId]K[key] - [summary of value]
	P9K999 - key; #999 - record position; ""ID"" element/process id; @""elementid""/[P9K999] - element with ID and key
	Keys are decomposed into partition id and per partition key (e.g. 2251799813685253 -> P1K005). If single partition, the partition is omitted.
	Long IDs are shortened (e.g. 'startEvent_5d56488e-0570-416c-ba2d-36d2a3acea78' -> 'star..acea78'
--------
C DEPLOYMENT         CREATE         - #35-> -1  -1 - 
E PROC               CREATED        - #36->#35 K18 - process.bpmn -> ""process"" (version:2)
E DEPLOYMENT         CREATED        - #37->#35 K19 - process.bpmn
E DEPLOYMENT         FULLY_DISTR    - #38->#35 K19 - 
C PROC_INST_CREATION CREATE         - #39-> -1  -1 - new <process """"> (no vars)
C PROC_INST          ACTIVATE       - #40->#39 K20 - PROCESS ""process"" in <process ""process""[K20]>
E PROC_INST_CREATION CREATED        - #41->#39 K21 - new <process ""process""> (no vars)
E PROC_INST          ACTIVATING     - #42->#40 K20 - PROCESS ""process"" in <process ""process""[K20]>
E PROC_INST          ACTIVATED      - #43->#40 K20 - PROCESS ""process"" in <process ""process""[K20]>
C PROC_INST          ACTIVATE       - #44->#40  -1 - START_EVENT ""startEv..efcc796"" in <process ""process""[K20]>
C VAR_DOCUMENT       UPDATE         - #45-> -1  -1 - VariableDocumentRecord {""variables"":{""0"":""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx""},""scopeKey"":2251799813685268,""updateSemantics"":""PROPAGATE""}
E PROC_INST          ACTIVATING     - #46->#44 K22 - START_EVENT ""startEv..efcc796"" in <process ""process""[K20]>
E PROC_INST          ACTIVATED      - #47->#44 K22 - START_EVENT ""startEv..efcc796"" in <process ""process""[K20]>
C PROC_INST          COMPLETE       - #48->#44 K22 - START_EVENT ""startEv..efcc796"" in <process ""process""[K20]>
E VAR                CREATED        - #49->#45 K23 - 0->""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"" in <process [K20]>
E VAR_DOCUMENT       UPDATED        - #50->#45 K24 - VariableDocumentRecord {""variables"":{""0"":""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx""},""scopeKey"":2251799813685268,""updateSemantics"":""PROPAGATE""}
E PROC_INST          COMPLETING     - #51->#48 K22 - START_EVENT ""startEv..efcc796"" in <process ""process""[K20]>
E PROC_INST          COMPLETED      - #52->#48 K22 - START_EVENT ""startEv..efcc796"" in <process ""process""[K20]>
E PROC_INST          SEQ_FLOW_TAKEN - #53->#48 K25 - SEQUENCE_FLOW ""sequenc..15e8065"" in <process ""process""[K20]>
C PROC_INST          ACTIVATE       - #54->#48 K26 - SERVICE_TASK ""task"" in <process ""process""[K20]>
C VAR_DOCUMENT       UPDATE         - #55-> -1  -1 - VariableDocumentRecord {""variables"":{""1"":""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx""},""scopeKey"":2251799813685268,""updateSemantics"":""PROPAGATE""}
E PROC_INST          ACTIVATING     - #56->#54 K26 - SERVICE_TASK ""task"" in <process ""process""[K20]>
E JOB                CREATED        - #57->#54 K27 - K27 ""acme"" @""task""[K26] 3 retries, in <process ""process""[K20]> (no vars)
E PROC_INST          ACTIVATED      - #58->#54 K26 - SERVICE_TASK ""task"" in <process ""process""[K20]>
E VAR                CREATED        - #59->#55 K28 - 1->""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"" in <process [K20]>
E VAR_DOCUMENT       UPDATED        - #60->#55 K29 - VariableDocumentRecord {""variables"":{""1"":""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx""},""scopeKey"":2251799813685268,""updateSemantics"":""PROPAGATE""}
C VAR_DOCUMENT       UPDATE         - #61-> -1  -1 - VariableDocumentRecord {""variables"":{""2"":""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx""},""scopeKey"":2251799813685268,""updateSemantics"":""PROPAGATE""}
E VAR                CREATED        - #62->#61 K30 - 2->""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"" in <process [K20]>
E VAR_DOCUMENT       UPDATED        - #63->#61 K31 - VariableDocumentRecord {""variables"":{""2"":""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx""},""scopeKey"":2251799813685268,""updateSemantics"":""PROPAGATE""}
C VAR_DOCUMENT       UPDATE         - #64-> -1  -1 - VariableDocumentRecord {""variables"":{""3"":""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx""},""scopeKey"":2251799813685268,""updateSemantics"":""PROPAGATE""}
E VAR                CREATED        - #65->#64 K32 - 3->""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"" in <process [K20]>
E VAR_DOCUMENT       UPDATED        - #66->#64 K33 - VariableDocumentRecord {""variables"":{""3"":""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx""},""scopeKey"":2251799813685268,""updateSemantics"":""PROPAGATE""}
C PROC_INST_CREATION CREATE         - #67-> -1  -1 - new <process """"> (no vars)
C PROC_INST          ACTIVATE       - #68->#67 K34 - PROCESS ""process"" in <process ""process""[K34]>
E PROC_INST_CREATION CREATED        - #69->#67 K35 - new <process ""process""> (no vars)
E PROC_INST          ACTIVATING     - #70->#68 K34 - PROCESS ""process"" in <process ""process""[K34]>
E PROC_INST          ACTIVATED      - #71->#68 K34 - PROCESS ""process"" in <process ""process""[K34]>
C PROC_INST          ACTIVATE       - #72->#68  -1 - START_EVENT ""startEv..efcc796"" in <process ""process""[K34]>
C JOB_BATCH          ACTIVATE       - #73-> -1  -1 - ""acme"" max: 2
E PROC_INST          ACTIVATING     - #74->#72 K36 - START_EVENT ""startEv..efcc796"" in <process ""process""[K34]>
E PROC_INST          ACTIVATED      - #75->#72 K36 - START_EVENT ""startEv..efcc796"" in <process ""process""[K34]>
C PROC_INST          COMPLETE       - #76->#72 K36 - START_EVENT ""startEv..efcc796"" in <process ""process""[K34]>
E INCIDENT           CREATED        - #77->#73 K38 - MESSAGE_SIZE_EXCEEDED The job with key '2251799813685275' can not be activated because it is larger than the configured message size (12.0 KB). Try to reduce the size by reducing the number of fetched variables or modifying the variable values., joBKey: K27  @""task""[K26] in <process ""process""[K20]>
E JOB_BATCH          ACTIVATED      - #78->#73 K37 - ""acme"" max: 2 (truncated)
C JOB_BATCH          ACTIVATE       - #79-> -1  -1 - ""acme"" max: 2
E PROC_INST          COMPLETING     - #80->#76 K36 - START_EVENT ""startEv..efcc796"" in <process ""process""[K34]>
E PROC_INST          COMPLETED      - #81->#76 K36 - START_EVENT ""startEv..efcc796"" in <process ""process""[K34]>
E PROC_INST          SEQ_FLOW_TAKEN - #82->#76 K39 - SEQUENCE_FLOW ""sequenc..15e8065"" in <process ""process""[K34]>
C PROC_INST          ACTIVATE       - #83->#76 K40 - SERVICE_TASK ""task"" in <process ""process""[K34]>
E JOB_BATCH          ACTIVATED      - #84->#79 K41 - ""acme"" max: 2
-------------- Deployed Processes ----------------------
process.bpmn -> ""process"" (version:2)[K18] ------
<?xml version=""1.0"" encoding=""UTF-8"" standalone=""no""?>
<definitions xmlns:bpmndi=""http://www.omg.org/spec/BPMN/20100524/DI"" xmlns:dc=""http://www.omg.org/spec/DD/20100524/DC"" xmlns:di=""http://www.omg.org/spec/DD/20100524/DI"" xmlns:ns0=""http://camunda.org/schema/zeebe/1.0"" id=""definitions_7dd99800-2a90-4e92-ae85-9bc54847575c"" targetNamespace=""http://www.omg.org/spec/BPMN/20100524/MODEL"" xmlns=""http://www.omg.org/spec/BPMN/20100524/MODEL"">
  <process id=""process"" isExecutable=""true"">
    <startEvent id=""startEvent_3d5261ed-a699-4b9d-9b8b-37c90efcc796"">
      <outgoing>sequenceFlow_8d9ed64c-2d9b-475c-8364-0d24715e8065</outgoing>
    </startEvent>
    <serviceTask id=""task"" name=""task"">
      <extensionElements>
        <ns0:taskDefinition type=""acme""/>
      </extensionElements>
      <incoming>sequenceFlow_8d9ed64c-2d9b-475c-8364-0d24715e8065</incoming>
      <outgoing>sequenceFlow_4313580d-7cc4-479b-b77d-8481934f7e60</outgoing>
    </serviceTask>
    <sequenceFlow id=""sequenceFlow_8d9ed64c-2d9b-475c-8364-0d24715e8065"" sourceRef=""startEvent_3d5261ed-a699-4b9d-9b8b-37c90efcc796"" targetRef=""task""/>
    <endEvent id=""endEvent_f9c9cae8-f4b7-407f-aba7-44db87efd3d4"">
      <incoming>sequenceFlow_4313580d-7cc4-479b-b77d-8481934f7e60</incoming>
    </endEvent>
    <sequenceFlow id=""sequenceFlow_4313580d-7cc4-479b-b77d-8481934f7e60"" sourceRef=""task"" targetRef=""endEvent_f9c9cae8-f4b7-407f-aba7-44db87efd3d4""/>
  </process>
  <bpmndi:BPMNDiagram id=""BPMNDiagram_5ec24441-ed24-46c3-8044-6b15364b327d"">
    <bpmndi:BPMNPlane bpmnElement=""process"" id=""BPMNPlane_a2e2a76e-2d76-4a8e-8f25-cd3f5a71c6d2"">
      <bpmndi:BPMNShape bpmnElement=""startEvent_3d5261ed-a699-4b9d-9b8b-37c90efcc796"" id=""BPMNShape_44d95ac1-bba4-4a44-a8e0-574c9e6bd0c2"">
        <dc:Bounds height=""36.0"" width=""36.0"" x=""100.0"" y=""100.0""/>
      </bpmndi:BPMNShape>
      <bpmndi:BPMNShape bpmnElement=""task"" id=""BPMNShape_4ac7dd05-f08e-418a-8fb8-805a217a5f99"">
        <dc:Bounds height=""80.0"" width=""100.0"" x=""186.0"" y=""78.0""/>
      </bpmndi:BPMNShape>
      <bpmndi:BPMNEdge bpmnElement=""sequenceFlow_8d9ed64c-2d9b-475c-8364-0d24715e8065"" id=""BPMNEdge_22f54955-254c-4c94-a10c-787d04d99f40"">
        <di:waypoint x=""136.0"" y=""118.0""/>
        <di:waypoint x=""186.0"" y=""118.0""/>
      </bpmndi:BPMNEdge>
      <bpmndi:BPMNShape bpmnElement=""endEvent_f9c9cae8-f4b7-407f-aba7-44db87efd3d4"" id=""BPMNShape_2eb02ca9-992e-4928-b136-1889c76edf94"">
        <dc:Bounds height=""36.0"" width=""36.0"" x=""336.0"" y=""100.0""/>
      </bpmndi:BPMNShape>
      <bpmndi:BPMNEdge bpmnElement=""sequenceFlow_4313580d-7cc4-479b-b77d-8481934f7e60"" id=""BPMNEdge_f3da6f6b-34d4-4c0f-b1f9-829409076a9c"">
        <di:waypoint x=""286.0"" y=""118.0""/>
        <di:waypoint x=""336.0"" y=""118.0""/>
      </bpmndi:BPMNEdge>
    </bpmndi:BPMNPlane>
  </bpmndi:BPMNDiagram>
</definitions>
--------------- Decomposed keys (for debugging) -----------------
 -1 <-> -1
K18 <-> 2251799813685266
K19 <-> 2251799813685267
K20 <-> 2251799813685268
K21 <-> 2251799813685269
K22 <-> 2251799813685270
K23 <-> 2251799813685271
K24 <-> 2251799813685272
K25 <-> 2251799813685273
K26 <-> 2251799813685274
K27 <-> 2251799813685275
K28 <-> 2251799813685276
K29 <-> 2251799813685277
K30 <-> 2251799813685278
K31 <-> 2251799813685279
K32 <-> 2251799813685280
K33 <-> 2251799813685281
K34 <-> 2251799813685282
K35 <-> 2251799813685283
K36 <-> 2251799813685284
K37 <-> 2251799813685285
K38 <-> 2251799813685286
K39 <-> 2251799813685287
K40 <-> 2251799813685288
K41 <-> 2251799813685289
</pre>
</details>
",1.0,"SmallMessageSizeTest#shouldSkipJobsThatExceedMessageSize is flaky - **Summary**

> Try to answer the following as best as possible

- How often does the test fail? at least twice
- Does it block your work? blocked a merge :slightly_smiling_face: 
- Do we suspect that it is a real failure? no idea, probably not

**Failures**

<details><summary>Example assertion failure</summary>
<pre>
io.camunda.zeebe.client.api.command.ClientException: Timed out waiting on client response
	at io.camunda.zeebe.client.impl.ZeebeClientFutureImpl.join(ZeebeClientFutureImpl.java:65)
	at io.camunda.zeebe.broker.it.network.SmallMessageSizeTest.shouldSkipJobsThatExceedMessageSize(SmallMessageSizeTest.java:77)
</pre>
</details>

**Hypotheses**

None

**Logs**

<details><summary>Logs</summary>
<pre>
Standard Output
14:04:07.782 [] [main] INFO  io.camunda.zeebe.test - Test failed, following records were exported:
14:04:07.833 [] [main] INFO  io.camunda.zeebe.test - Compact log representation:
--------
	['C'ommand/'E'event/'R'ejection] [valueType] [intent] - #[position]->#[source record position]  P[partitionId]K[key] - [summary of value]
	P9K999 - key; #999 - record position; ""ID"" element/process id; @""elementid""/[P9K999] - element with ID and key
	Keys are decomposed into partition id and per partition key (e.g. 2251799813685253 -> P1K005). If single partition, the partition is omitted.
	Long IDs are shortened (e.g. 'startEvent_5d56488e-0570-416c-ba2d-36d2a3acea78' -> 'star..acea78'
--------
C DEPLOYMENT         CREATE         - #35-> -1  -1 - 
E PROC               CREATED        - #36->#35 K18 - process.bpmn -> ""process"" (version:2)
E DEPLOYMENT         CREATED        - #37->#35 K19 - process.bpmn
E DEPLOYMENT         FULLY_DISTR    - #38->#35 K19 - 
C PROC_INST_CREATION CREATE         - #39-> -1  -1 - new <process """"> (no vars)
C PROC_INST          ACTIVATE       - #40->#39 K20 - PROCESS ""process"" in <process ""process""[K20]>
E PROC_INST_CREATION CREATED        - #41->#39 K21 - new <process ""process""> (no vars)
E PROC_INST          ACTIVATING     - #42->#40 K20 - PROCESS ""process"" in <process ""process""[K20]>
E PROC_INST          ACTIVATED      - #43->#40 K20 - PROCESS ""process"" in <process ""process""[K20]>
C PROC_INST          ACTIVATE       - #44->#40  -1 - START_EVENT ""startEv..efcc796"" in <process ""process""[K20]>
C VAR_DOCUMENT       UPDATE         - #45-> -1  -1 - VariableDocumentRecord {""variables"":{""0"":""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx""},""scopeKey"":2251799813685268,""updateSemantics"":""PROPAGATE""}
E PROC_INST          ACTIVATING     - #46->#44 K22 - START_EVENT ""startEv..efcc796"" in <process ""process""[K20]>
E PROC_INST          ACTIVATED      - #47->#44 K22 - START_EVENT ""startEv..efcc796"" in <process ""process""[K20]>
C PROC_INST          COMPLETE       - #48->#44 K22 - START_EVENT ""startEv..efcc796"" in <process ""process""[K20]>
E VAR                CREATED        - #49->#45 K23 - 0->""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"" in <process [K20]>
E VAR_DOCUMENT       UPDATED        - #50->#45 K24 - VariableDocumentRecord {""variables"":{""0"":""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx""},""scopeKey"":2251799813685268,""updateSemantics"":""PROPAGATE""}
E PROC_INST          COMPLETING     - #51->#48 K22 - START_EVENT ""startEv..efcc796"" in <process ""process""[K20]>
E PROC_INST          COMPLETED      - #52->#48 K22 - START_EVENT ""startEv..efcc796"" in <process ""process""[K20]>
E PROC_INST          SEQ_FLOW_TAKEN - #53->#48 K25 - SEQUENCE_FLOW ""sequenc..15e8065"" in <process ""process""[K20]>
C PROC_INST          ACTIVATE       - #54->#48 K26 - SERVICE_TASK ""task"" in <process ""process""[K20]>
C VAR_DOCUMENT       UPDATE         - #55-> -1  -1 - VariableDocumentRecord {""variables"":{""1"":""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx""},""scopeKey"":2251799813685268,""updateSemantics"":""PROPAGATE""}
E PROC_INST          ACTIVATING     - #56->#54 K26 - SERVICE_TASK ""task"" in <process ""process""[K20]>
E JOB                CREATED        - #57->#54 K27 - K27 ""acme"" @""task""[K26] 3 retries, in <process ""process""[K20]> (no vars)
E PROC_INST          ACTIVATED      - #58->#54 K26 - SERVICE_TASK ""task"" in <process ""process""[K20]>
E VAR                CREATED        - #59->#55 K28 - 1->""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"" in <process [K20]>
E VAR_DOCUMENT       UPDATED        - #60->#55 K29 - VariableDocumentRecord {""variables"":{""1"":""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx""},""scopeKey"":2251799813685268,""updateSemantics"":""PROPAGATE""}
C VAR_DOCUMENT       UPDATE         - #61-> -1  -1 - VariableDocumentRecord {""variables"":{""2"":""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx""},""scopeKey"":2251799813685268,""updateSemantics"":""PROPAGATE""}
E VAR                CREATED        - #62->#61 K30 - 2->""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"" in <process [K20]>
E VAR_DOCUMENT       UPDATED        - #63->#61 K31 - VariableDocumentRecord {""variables"":{""2"":""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx""},""scopeKey"":2251799813685268,""updateSemantics"":""PROPAGATE""}
C VAR_DOCUMENT       UPDATE         - #64-> -1  -1 - VariableDocumentRecord {""variables"":{""3"":""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx""},""scopeKey"":2251799813685268,""updateSemantics"":""PROPAGATE""}
E VAR                CREATED        - #65->#64 K32 - 3->""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"" in <process [K20]>
E VAR_DOCUMENT       UPDATED        - #66->#64 K33 - VariableDocumentRecord {""variables"":{""3"":""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx""},""scopeKey"":2251799813685268,""updateSemantics"":""PROPAGATE""}
C PROC_INST_CREATION CREATE         - #67-> -1  -1 - new <process """"> (no vars)
C PROC_INST          ACTIVATE       - #68->#67 K34 - PROCESS ""process"" in <process ""process""[K34]>
E PROC_INST_CREATION CREATED        - #69->#67 K35 - new <process ""process""> (no vars)
E PROC_INST          ACTIVATING     - #70->#68 K34 - PROCESS ""process"" in <process ""process""[K34]>
E PROC_INST          ACTIVATED      - #71->#68 K34 - PROCESS ""process"" in <process ""process""[K34]>
C PROC_INST          ACTIVATE       - #72->#68  -1 - START_EVENT ""startEv..efcc796"" in <process ""process""[K34]>
C JOB_BATCH          ACTIVATE       - #73-> -1  -1 - ""acme"" max: 2
E PROC_INST          ACTIVATING     - #74->#72 K36 - START_EVENT ""startEv..efcc796"" in <process ""process""[K34]>
E PROC_INST          ACTIVATED      - #75->#72 K36 - START_EVENT ""startEv..efcc796"" in <process ""process""[K34]>
C PROC_INST          COMPLETE       - #76->#72 K36 - START_EVENT ""startEv..efcc796"" in <process ""process""[K34]>
E INCIDENT           CREATED        - #77->#73 K38 - MESSAGE_SIZE_EXCEEDED The job with key '2251799813685275' can not be activated because it is larger than the configured message size (12.0 KB). Try to reduce the size by reducing the number of fetched variables or modifying the variable values., joBKey: K27  @""task""[K26] in <process ""process""[K20]>
E JOB_BATCH          ACTIVATED      - #78->#73 K37 - ""acme"" max: 2 (truncated)
C JOB_BATCH          ACTIVATE       - #79-> -1  -1 - ""acme"" max: 2
E PROC_INST          COMPLETING     - #80->#76 K36 - START_EVENT ""startEv..efcc796"" in <process ""process""[K34]>
E PROC_INST          COMPLETED      - #81->#76 K36 - START_EVENT ""startEv..efcc796"" in <process ""process""[K34]>
E PROC_INST          SEQ_FLOW_TAKEN - #82->#76 K39 - SEQUENCE_FLOW ""sequenc..15e8065"" in <process ""process""[K34]>
C PROC_INST          ACTIVATE       - #83->#76 K40 - SERVICE_TASK ""task"" in <process ""process""[K34]>
E JOB_BATCH          ACTIVATED      - #84->#79 K41 - ""acme"" max: 2
-------------- Deployed Processes ----------------------
process.bpmn -> ""process"" (version:2)[K18] ------
<?xml version=""1.0"" encoding=""UTF-8"" standalone=""no""?>
<definitions xmlns:bpmndi=""http://www.omg.org/spec/BPMN/20100524/DI"" xmlns:dc=""http://www.omg.org/spec/DD/20100524/DC"" xmlns:di=""http://www.omg.org/spec/DD/20100524/DI"" xmlns:ns0=""http://camunda.org/schema/zeebe/1.0"" id=""definitions_7dd99800-2a90-4e92-ae85-9bc54847575c"" targetNamespace=""http://www.omg.org/spec/BPMN/20100524/MODEL"" xmlns=""http://www.omg.org/spec/BPMN/20100524/MODEL"">
  <process id=""process"" isExecutable=""true"">
    <startEvent id=""startEvent_3d5261ed-a699-4b9d-9b8b-37c90efcc796"">
      <outgoing>sequenceFlow_8d9ed64c-2d9b-475c-8364-0d24715e8065</outgoing>
    </startEvent>
    <serviceTask id=""task"" name=""task"">
      <extensionElements>
        <ns0:taskDefinition type=""acme""/>
      </extensionElements>
      <incoming>sequenceFlow_8d9ed64c-2d9b-475c-8364-0d24715e8065</incoming>
      <outgoing>sequenceFlow_4313580d-7cc4-479b-b77d-8481934f7e60</outgoing>
    </serviceTask>
    <sequenceFlow id=""sequenceFlow_8d9ed64c-2d9b-475c-8364-0d24715e8065"" sourceRef=""startEvent_3d5261ed-a699-4b9d-9b8b-37c90efcc796"" targetRef=""task""/>
    <endEvent id=""endEvent_f9c9cae8-f4b7-407f-aba7-44db87efd3d4"">
      <incoming>sequenceFlow_4313580d-7cc4-479b-b77d-8481934f7e60</incoming>
    </endEvent>
    <sequenceFlow id=""sequenceFlow_4313580d-7cc4-479b-b77d-8481934f7e60"" sourceRef=""task"" targetRef=""endEvent_f9c9cae8-f4b7-407f-aba7-44db87efd3d4""/>
  </process>
  <bpmndi:BPMNDiagram id=""BPMNDiagram_5ec24441-ed24-46c3-8044-6b15364b327d"">
    <bpmndi:BPMNPlane bpmnElement=""process"" id=""BPMNPlane_a2e2a76e-2d76-4a8e-8f25-cd3f5a71c6d2"">
      <bpmndi:BPMNShape bpmnElement=""startEvent_3d5261ed-a699-4b9d-9b8b-37c90efcc796"" id=""BPMNShape_44d95ac1-bba4-4a44-a8e0-574c9e6bd0c2"">
        <dc:Bounds height=""36.0"" width=""36.0"" x=""100.0"" y=""100.0""/>
      </bpmndi:BPMNShape>
      <bpmndi:BPMNShape bpmnElement=""task"" id=""BPMNShape_4ac7dd05-f08e-418a-8fb8-805a217a5f99"">
        <dc:Bounds height=""80.0"" width=""100.0"" x=""186.0"" y=""78.0""/>
      </bpmndi:BPMNShape>
      <bpmndi:BPMNEdge bpmnElement=""sequenceFlow_8d9ed64c-2d9b-475c-8364-0d24715e8065"" id=""BPMNEdge_22f54955-254c-4c94-a10c-787d04d99f40"">
        <di:waypoint x=""136.0"" y=""118.0""/>
        <di:waypoint x=""186.0"" y=""118.0""/>
      </bpmndi:BPMNEdge>
      <bpmndi:BPMNShape bpmnElement=""endEvent_f9c9cae8-f4b7-407f-aba7-44db87efd3d4"" id=""BPMNShape_2eb02ca9-992e-4928-b136-1889c76edf94"">
        <dc:Bounds height=""36.0"" width=""36.0"" x=""336.0"" y=""100.0""/>
      </bpmndi:BPMNShape>
      <bpmndi:BPMNEdge bpmnElement=""sequenceFlow_4313580d-7cc4-479b-b77d-8481934f7e60"" id=""BPMNEdge_f3da6f6b-34d4-4c0f-b1f9-829409076a9c"">
        <di:waypoint x=""286.0"" y=""118.0""/>
        <di:waypoint x=""336.0"" y=""118.0""/>
      </bpmndi:BPMNEdge>
    </bpmndi:BPMNPlane>
  </bpmndi:BPMNDiagram>
</definitions>
--------------- Decomposed keys (for debugging) -----------------
 -1 <-> -1
K18 <-> 2251799813685266
K19 <-> 2251799813685267
K20 <-> 2251799813685268
K21 <-> 2251799813685269
K22 <-> 2251799813685270
K23 <-> 2251799813685271
K24 <-> 2251799813685272
K25 <-> 2251799813685273
K26 <-> 2251799813685274
K27 <-> 2251799813685275
K28 <-> 2251799813685276
K29 <-> 2251799813685277
K30 <-> 2251799813685278
K31 <-> 2251799813685279
K32 <-> 2251799813685280
K33 <-> 2251799813685281
K34 <-> 2251799813685282
K35 <-> 2251799813685283
K36 <-> 2251799813685284
K37 <-> 2251799813685285
K38 <-> 2251799813685286
K39 <-> 2251799813685287
K40 <-> 2251799813685288
K41 <-> 2251799813685289
</pre>
</details>
",0,smallmessagesizetest shouldskipjobsthatexceedmessagesize is flaky     summary        try to answer the following as best as possible      how often does the test fail  at least twice    does it block your work  blocked a merge  slightly smiling face      do we suspect that it is a real failure  no idea  probably not      failures        example assertion failure      io camunda zeebe client api command clientexception  timed out waiting on client response  	at io camunda zeebe client impl zeebeclientfutureimpl join zeebeclientfutureimpl java     	at io camunda zeebe broker it network smallmessagesizetest shouldskipjobsthatexceedmessagesize smallmessagesizetest java               hypotheses      none      logs        logs      standard output              info  io camunda zeebe test   test failed  following records were exported               info  io camunda zeebe test   compact log representation             	                p k       	    key       record position   id  element process id    elementid      element with id and key  	keys are decomposed into partition id and per partition key  e g           if single partition  the partition is omitted   	long ids are shortened  e g   startevent                star                c deployment         create                           e proc               created                     process bpmn     process   version     e deployment         created                     process bpmn  e deployment         fully distr                   c proc inst creation create                         new    no vars   c proc inst          activate                    process  process  in    e proc inst creation created                     new    no vars   e proc inst          activating                  process  process  in    e proc inst          activated                   process  process  in    c proc inst          activate                      start event  startev     in    c var document       update                         variabledocumentrecord   variables        xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx    scopekey     updatesemantics   propagate    e proc inst          activating                  start event  startev     in    e proc inst          activated                   start event  startev     in    c proc inst          complete                    start event  startev     in    e var                created                         xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx  in    e var document       updated                     variabledocumentrecord   variables        xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx    scopekey     updatesemantics   propagate    e proc inst          completing                  start event  startev     in    e proc inst          completed                   start event  startev     in    e proc inst          seq flow taken              sequence flow  sequenc     in    c proc inst          activate                    service task  task  in    c var document       update                         variabledocumentrecord   variables        xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx    scopekey     updatesemantics   propagate    e proc inst          activating                  service task  task  in    e job                created                        acme    task     retries  in    no vars   e proc inst          activated                   service task  task  in    e var                created                         xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx  in    e var document       updated                     variabledocumentrecord   variables        xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx    scopekey     updatesemantics   propagate    c var document       update                         variabledocumentrecord   variables        xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx    scopekey     updatesemantics   propagate    e var                created                         xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx  in    e var document       updated                     variabledocumentrecord   variables        xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx    scopekey     updatesemantics   propagate    c var document       update                         variabledocumentrecord   variables        xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx    scopekey     updatesemantics   propagate    e var                created                         xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx  in    e var document       updated                     variabledocumentrecord   variables        xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx    scopekey     updatesemantics   propagate    c proc inst creation create                         new    no vars   c proc inst          activate                    process  process  in    e proc inst creation created                     new    no vars   e proc inst          activating                  process  process  in    e proc inst          activated                   process  process  in    c proc inst          activate                      start event  startev     in    c job batch          activate                        acme  max     e proc inst          activating                  start event  startev     in    e proc inst          activated                   start event  startev     in    c proc inst          complete                    start event  startev     in    e incident           created                     message size exceeded the job with key     can not be activated because it is larger than the configured message size      kb   try to reduce the size by reducing the number of fetched variables or modifying the variable values   jobkey       task   in    e job batch          activated                    acme  max     truncated   c job batch          activate                        acme  max     e proc inst          completing                  start event  startev     in    e proc inst          completed                   start event  startev     in    e proc inst          seq flow taken              sequence flow  sequenc     in    c proc inst          activate                    service task  task  in    e job batch          activated                    acme  max                    deployed processes                         process bpmn     process   version                 definitions xmlns bpmndi    xmlns dc    xmlns di    xmlns      id  definitions            targetnamespace    xmlns                        sequenceflow                                                               sequenceflow                    sequenceflow                                         sequenceflow                                                                                                                                                                                                                                                  decomposed keys  for debugging                                                                                                                                                                                                             ,0
220208,7354103253.0,IssuesEvent,2018-03-09 04:42:32,CS2103JAN2018-W13-B4/main,https://api.github.com/repos/CS2103JAN2018-W13-B4/main,opened,29. As a user I want to have a task’s priority level automatically increased if still uncompleted after the deadline has passed,priority.medium type.story,... so that I can be reminded of urgent uncompleted tasks,1.0,29. As a user I want to have a task’s priority level automatically increased if still uncompleted after the deadline has passed - ... so that I can be reminded of urgent uncompleted tasks,0,   as a user i want to have a task’s priority level automatically increased if still uncompleted after the deadline has passed       so that i can be reminded of urgent uncompleted tasks,0
230052,7603689220.0,IssuesEvent,2018-04-29 17:04:42,bensku/Skript,https://api.github.com/repos/bensku/Skript,closed,Bug with function returns,bug priority: low,"So it seems like there is a big bug with function returns. The problem, I think, is that returns aren never deleted but are still stored when we use a function multiple times. If a function returns something, as longer as the function can't return something, it will return the old return!
Example:
```
function(t: text) :: text:
    if {_t} is ""hey!"":
        return ""lol"" 
```
Here, if ""{_t}"" is hey just one time, the function will always return ""lol"" all the next times, either if the text isn't ""hey!"" It's, I think, an important issue...
The only workaround about that is be do add:
```
    if {_t} is not ""hey!"":
        return ""ah, no!"" 
```

",1.0,"Bug with function returns - So it seems like there is a big bug with function returns. The problem, I think, is that returns aren never deleted but are still stored when we use a function multiple times. If a function returns something, as longer as the function can't return something, it will return the old return!
Example:
```
function(t: text) :: text:
    if {_t} is ""hey!"":
        return ""lol"" 
```
Here, if ""{_t}"" is hey just one time, the function will always return ""lol"" all the next times, either if the text isn't ""hey!"" It's, I think, an important issue...
The only workaround about that is be do add:
```
    if {_t} is not ""hey!"":
        return ""ah, no!"" 
```

",0,bug with function returns   so it seems like there is a big bug with function returns  the problem  i think  is that returns aren never deleted but are still stored when we use a function multiple times  if a function returns something  as longer as the function can t return something  it will return the old return   example        function t  text     text       if   t  is  hey             return  lol         here  if    t   is hey just one time  the function will always return  lol  all the next times  either if the text isn t  hey   it s  i think  an important issue     the only workaround about that is be do add            if   t  is not  hey             return  ah  no            ,0
41067,21448025710.0,IssuesEvent,2022-04-25 08:32:41,SciTools/iris,https://api.github.com/repos/SciTools/iris,closed,Performance Shift(s): `6c80bc4a`,Type: Performance Bot,"
Benchmark comparison has identified performance shifts at commit 6c80bc4a (#4646). Please review the report below and take corrective/congratulatory action as appropriate :slightly_smiling_face:

<details>
<summary>Performance shift report</summary>

```
       before           after         ratio
     [c151b108]       [6c80bc4a]
     <main~1>         <main>    
-      7.74±0.2ms       4.78±0.2ms     0.62  cube.AuxFactory.time_add
-      2.60±0.2μs       2.00±0.2μs     0.77  experimental.ugrid.MeshCoordLazy.time_return(10000)
-      2.70±0.2μs       2.10±0.3μs     0.78  experimental.ugrid.MeshCoordLazy.time_return(6)
```

</details>

Generated by GHA run [`2210437509`](https://github.com/SciTools/iris/actions/runs/2210437509)
    ",True,"Performance Shift(s): `6c80bc4a` - 
Benchmark comparison has identified performance shifts at commit 6c80bc4a (#4646). Please review the report below and take corrective/congratulatory action as appropriate :slightly_smiling_face:

<details>
<summary>Performance shift report</summary>

```
       before           after         ratio
     [c151b108]       [6c80bc4a]
     <main~1>         <main>    
-      7.74±0.2ms       4.78±0.2ms     0.62  cube.AuxFactory.time_add
-      2.60±0.2μs       2.00±0.2μs     0.77  experimental.ugrid.MeshCoordLazy.time_return(10000)
-      2.70±0.2μs       2.10±0.3μs     0.78  experimental.ugrid.MeshCoordLazy.time_return(6)
```

</details>

Generated by GHA run [`2210437509`](https://github.com/SciTools/iris/actions/runs/2210437509)
    ",0,performance shift s          benchmark comparison has identified performance shifts at commit         please review the report below and take corrective congratulatory action as appropriate  slightly smiling face      performance shift report              before           after         ratio                                               ±             ±             cube auxfactory time add           ±             ±             experimental ugrid meshcoordlazy time return              ±             ±             experimental ugrid meshcoordlazy time return            generated by gha run         ,0
157756,12390057931.0,IssuesEvent,2020-05-20 10:01:07,microsoft/AzureStorageExplorer,https://api.github.com/repos/microsoft/AzureStorageExplorer,opened,An extra folder displays after selecting 'Enabled overwrite' to retry one conflict blob,:beetle: regression :gear: blobs 🧪 testing,"**Storage Explorer Version:** 1.14.0-dev
**Build**: [20200520.4](https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=3742543&view=results)
**Branch**: master
**Platform/OS:** Windows 10/ Linux Ubuntu 16.04/ macOS Mojave
**Architecture:** ia32/x64
**Regression From:** Previous release (1.13.0)

**Steps to reproduce:**

1. Expand one Non-ADLS Gen2 storage account -> Blob Containers.
2. Copy one blob to another blob container -> Copy the blob to same destination again.
3. Select 'Do not paste' in the Conflict dialog -> Apply.
4. Click 'Retry...' in activity log -> Select 'Enable overwrite' in Retry AzCopy dialog -> Click 'Retry Selected'.
5. Check the result.

**Expect Experience:**

1. Succeed overwrite the blob.
2. No folder displays.


**Actual Experience:**
An extra folder displays.
![image](https://user-images.githubusercontent.com/54055206/82429579-bc30cd00-9abe-11ea-901f-733e5ea82bb6.png)


**More Info:**
This issue doesn't reproduce for one ADLS Gen2 blob conatiner.

",1.0,"An extra folder displays after selecting 'Enabled overwrite' to retry one conflict blob - **Storage Explorer Version:** 1.14.0-dev
**Build**: [20200520.4](https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=3742543&view=results)
**Branch**: master
**Platform/OS:** Windows 10/ Linux Ubuntu 16.04/ macOS Mojave
**Architecture:** ia32/x64
**Regression From:** Previous release (1.13.0)

**Steps to reproduce:**

1. Expand one Non-ADLS Gen2 storage account -> Blob Containers.
2. Copy one blob to another blob container -> Copy the blob to same destination again.
3. Select 'Do not paste' in the Conflict dialog -> Apply.
4. Click 'Retry...' in activity log -> Select 'Enable overwrite' in Retry AzCopy dialog -> Click 'Retry Selected'.
5. Check the result.

**Expect Experience:**

1. Succeed overwrite the blob.
2. No folder displays.


**Actual Experience:**
An extra folder displays.
![image](https://user-images.githubusercontent.com/54055206/82429579-bc30cd00-9abe-11ea-901f-733e5ea82bb6.png)


**More Info:**
This issue doesn't reproduce for one ADLS Gen2 blob conatiner.

",0,an extra folder displays after selecting  enabled overwrite  to retry one conflict blob     storage explorer version          dev    build           branch    master    platform os    windows    linux ubuntu      macos mojave    architecture           regression from    previous release              steps to reproduce          expand one non adls   storage account    blob containers      copy one blob to another blob container    copy the blob to same destination again      select  do not paste  in the conflict dialog    apply      click  retry     in activity log    select  enable overwrite  in retry azcopy dialog    click  retry selected       check the result       expect experience          succeed overwrite the blob      no folder displays         actual experience     an extra folder displays               more info     this issue doesn t reproduce for one adls   blob conatiner     ,0
103475,11357496626.0,IssuesEvent,2020-01-25 05:44:22,golang/go,https://api.github.com/repos/golang/go,opened,x/mod/modfile: missing a package comment,Documentation NeedsFix modules,"Per https://golang.org/doc/effective_go.html#commentary:

> Every package should have a _package comment_, a block comment preceding the package clause.

Package `modfile` does not have one, as can be seen at https://pkg.go.dev/golang.org/x/mod. It should.

/cc @jayconrod @bcmills @matloob",1.0,"x/mod/modfile: missing a package comment - Per https://golang.org/doc/effective_go.html#commentary:

> Every package should have a _package comment_, a block comment preceding the package clause.

Package `modfile` does not have one, as can be seen at https://pkg.go.dev/golang.org/x/mod. It should.

/cc @jayconrod @bcmills @matloob",1,x mod modfile  missing a package comment   per        every package should have a  package comment   a block comment preceding the package clause     package  modfile  does not have one  as can be seen at   it should      cc  jayconrod  bcmills  matloob,1
152937,12129829541.0,IssuesEvent,2020-04-22 23:41:08,futurewei-cloud/arktos,https://api.github.com/repos/futurewei-cloud/arktos,closed,AWS: Add workload-controller-manager to aws-kube-up and start-kubemark,area/performance-test,"<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!

If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->


**What happened**:
kube-up and start-kubemark on AWS missing workload-controller-manger
**What you expected to happen**:
workload-controller-manger included
**How to reproduce it (as minimally and precisely as possible)**:

**Anything else we need to know?**:
https://github.com/futurewei-cloud/arktos/pull/127
**Environment**:
- Arktos version (use `kubectl version`):
- Cloud provider or hardware configuration:
- OS (e.g: `cat /etc/os-release`):
- Kernel (e.g. `uname -a`):
- Install tools:
- Network plugin and version (if this is a network-related bug):
- Others:
",1.0,"AWS: Add workload-controller-manager to aws-kube-up and start-kubemark - <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!

If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->


**What happened**:
kube-up and start-kubemark on AWS missing workload-controller-manger
**What you expected to happen**:
workload-controller-manger included
**How to reproduce it (as minimally and precisely as possible)**:

**Anything else we need to know?**:
https://github.com/futurewei-cloud/arktos/pull/127
**Environment**:
- Arktos version (use `kubectl version`):
- Cloud provider or hardware configuration:
- OS (e.g: `cat /etc/os-release`):
- Kernel (e.g. `uname -a`):
- Install tools:
- Network plugin and version (if this is a network-related bug):
- Others:
",0,aws  add workload controller manager to aws kube up and start kubemark        please use this template while reporting a bug and provide as much info as possible  not doing so may result in your bug not being addressed in a timely manner  thanks     if the matter is security related  please disclose it privately via               what happened     kube up and start kubemark on aws missing workload controller manger    what you expected to happen     workload controller manger included    how to reproduce it  as minimally and precisely as possible          anything else we need to know           environment       arktos version  use  kubectl version       cloud provider or hardware configuration     os  e g   cat  etc os release       kernel  e g   uname  a       install tools     network plugin and version  if this is a network related bug      others   ,0
42188,6969549022.0,IssuesEvent,2017-12-11 06:13:21,golang/go,https://api.github.com/repos/golang/go,closed,doc: go1.10.html states that i386/amd64 executables fail on NetBSD amd64,Documentation,"Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?

N/A

### Does this issue reproduce with the latest release?

N/A

### What operating system and processor architecture are you using (`go env`)?

N/A

### What did you do?

N/A

### What did you expect to see?

Removed note that 32-bit applications are broken on 64-bit NetBSD kernel.

### What did you see instead?

The reverse.

The breakage was a regression on HEAD.

Fix:

```
Module Name:    src
Committed By:   christos
Date:           Thu Dec  7 16:22:22 UTC 2017

Modified Files:
        src/sys/arch/amd64/amd64: netbsd32_machdep.c

Log Message:
Keep fs/gs the same for the signal context; otherwise calling things
like __lwp_getprivate_fast() from a signal handler (that uses %gs) die.

Merge context building code.


To generate a diff of this commit:
cvs rdiff -u -r1.113 -r1.114 src/sys/arch/amd64/amd64/netbsd32_machdep.c
```

http://mail-index.netbsd.org/source-changes/2017/12/07/msg090270.html",1.0,"doc: go1.10.html states that i386/amd64 executables fail on NetBSD amd64 - Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?

N/A

### Does this issue reproduce with the latest release?

N/A

### What operating system and processor architecture are you using (`go env`)?

N/A

### What did you do?

N/A

### What did you expect to see?

Removed note that 32-bit applications are broken on 64-bit NetBSD kernel.

### What did you see instead?

The reverse.

The breakage was a regression on HEAD.

Fix:

```
Module Name:    src
Committed By:   christos
Date:           Thu Dec  7 16:22:22 UTC 2017

Modified Files:
        src/sys/arch/amd64/amd64: netbsd32_machdep.c

Log Message:
Keep fs/gs the same for the signal context; otherwise calling things
like __lwp_getprivate_fast() from a signal handler (that uses %gs) die.

Merge context building code.


To generate a diff of this commit:
cvs rdiff -u -r1.113 -r1.114 src/sys/arch/amd64/amd64/netbsd32_machdep.c
```

http://mail-index.netbsd.org/source-changes/2017/12/07/msg090270.html",1,doc      html states that     executables fail on netbsd     please answer these questions before submitting your issue  thanks           what version of go are you using   go version       n a        does this issue reproduce with the latest release     n a        what operating system and processor architecture are you using   go env       n a        what did you do     n a        what did you expect to see     removed note that   bit applications are broken on   bit netbsd kernel         what did you see instead     the reverse     the breakage was a regression on head     fix          module name     src  committed by    christos  date            thu dec          utc      modified files           src sys arch        machdep c    log message   keep fs gs the same for the signal context  otherwise calling things  like   lwp getprivate fast   from a signal handler  that uses  gs  die     merge context building code       to generate a diff of this commit   cvs rdiff  u           src sys arch       machdep c          ,1
20862,6952556527.0,IssuesEvent,2017-12-06 17:51:10,golang/go,https://api.github.com/repos/golang/go,closed,x/build: update NetBSD builders to NetBSD 8-beta,Builders HelpWanted OS-NetBSD,"In https://go-review.googlesource.com/c/47036/, Christos Zoulas mentions that there are known bugs in the NetBSD 7.1 kqueue code and we should switch our builders to NetBSD 8-beta.

Also mentioned in https://github.com/golang/go/issues/20836#issuecomment-312066066

This is a tracking bug to update our NetBSD builders past 7.1

I've updated https://golang.org/wiki/MinimumRequirements too.

/cc @krytarowski @bsiegert @zoulasc @adams-sarah @andybons ",1.0,"x/build: update NetBSD builders to NetBSD 8-beta - In https://go-review.googlesource.com/c/47036/, Christos Zoulas mentions that there are known bugs in the NetBSD 7.1 kqueue code and we should switch our builders to NetBSD 8-beta.

Also mentioned in https://github.com/golang/go/issues/20836#issuecomment-312066066

This is a tracking bug to update our NetBSD builders past 7.1

I've updated https://golang.org/wiki/MinimumRequirements too.

/cc @krytarowski @bsiegert @zoulasc @adams-sarah @andybons ",0,x build  update netbsd builders to netbsd   beta   in   christos zoulas mentions that there are known bugs in the netbsd     kqueue code and we should switch our builders to netbsd   beta     also mentioned in      this is a tracking bug to update our netbsd builders past        i ve updated   too      cc  krytarowski  bsiegert  zoulasc  adams sarah  andybons ,0
12073,4351568584.0,IssuesEvent,2016-07-31 23:04:54,colinhect/hect,https://api.github.com/repos/colinhect/hect,closed,Formalize Scene types similar with Systems and Components,api code-quality,Add a SceneRegistery class.  Have specific scene types derive from Scene and register with SceneRegistery.  The scene class will define which systems it has and defines its own tick() function (removing the need to describe system update order in data).  The scene data itself will dictate its scene type.  Scene base types should still work as-is.,1.0,Formalize Scene types similar with Systems and Components - Add a SceneRegistery class.  Have specific scene types derive from Scene and register with SceneRegistery.  The scene class will define which systems it has and defines its own tick() function (removing the need to describe system update order in data).  The scene data itself will dictate its scene type.  Scene base types should still work as-is.,0,formalize scene types similar with systems and components   add a sceneregistery class   have specific scene types derive from scene and register with sceneregistery   the scene class will define which systems it has and defines its own tick   function  removing the need to describe system update order in data    the scene data itself will dictate its scene type   scene base types should still work as is ,0
155426,12255253069.0,IssuesEvent,2020-05-06 09:53:12,microsoft/AzureStorageExplorer,https://api.github.com/repos/microsoft/AzureStorageExplorer,opened,No confirmation dialog pops up when detaching one queue,:beetle: regression :gear: attach :gear: queues 🧪 testing,"**Storage Explorer Version:** 1.13.0
**Build**: [20200504.7](https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=3700661&view=results)
**Branch**: master
**Platform/OS**: Windows 10/ macOS Catalina / Linux Ubuntu 16.04
**Architecture**: ia32/x64
**Regression From:** Previous release(1.13.0)

**Steps to reproduce:**

1. Expand one storage account -> Queues.
2. Select one queue -> Attach it via SAS.
3. Try to detach the attached queue under Local & Attached.
4. Check the result.

**Expect Experience:**
A confirmation dialog pops up.
![image](https://user-images.githubusercontent.com/54055206/81158308-6b977b00-8fba-11ea-9db9-2e3940dab023.png)

**Actual Experience:**
No dialog pops up.
",1.0,"No confirmation dialog pops up when detaching one queue - **Storage Explorer Version:** 1.13.0
**Build**: [20200504.7](https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=3700661&view=results)
**Branch**: master
**Platform/OS**: Windows 10/ macOS Catalina / Linux Ubuntu 16.04
**Architecture**: ia32/x64
**Regression From:** Previous release(1.13.0)

**Steps to reproduce:**

1. Expand one storage account -> Queues.
2. Select one queue -> Attach it via SAS.
3. Try to detach the attached queue under Local & Attached.
4. Check the result.

**Expect Experience:**
A confirmation dialog pops up.
![image](https://user-images.githubusercontent.com/54055206/81158308-6b977b00-8fba-11ea-9db9-2e3940dab023.png)

**Actual Experience:**
No dialog pops up.
",0,no confirmation dialog pops up when detaching one queue     storage explorer version             build           branch    master    platform os    windows    macos catalina   linux ubuntu        architecture           regression from    previous release             steps to reproduce          expand one storage account    queues      select one queue    attach it via sas      try to detach the attached queue under local   attached      check the result       expect experience     a confirmation dialog pops up             actual experience     no dialog pops up   ,0
56889,8129711062.0,IssuesEvent,2018-08-17 15:53:26,golang/go,https://api.github.com/repos/golang/go,closed,doc/code.html: update description of install command,Documentation NeedsFix,"### What version of Go are you using (go version)?
`go version go1.10 windows/amd64`

### Does this issue reproduce with the latest release?
1.10 is the latest at this moment

### What operating system and processor architecture are you using (go env)?
GOARCH=amd64
GOOS=windows

### What did you do?
I have small test program with two small dummy libraries.

Go program in the `src` has path `github.com/user/hello`

    package main

    import (
        ""fmt""
 
        // Libraries bellow are not automatically generated in pkg
        ""github.com/user/stringutil""
        ""github.com/user/tttt""
    )

    func main() {
        fmt.Printf(stringutil.Reverse(""\nHello, world.\n""))
        fmt.Println(add(85,tttt.Tttt(9)))
    }

`add()` function is in separate file, also in `hello` directory:

    package main

    func add(x int, y int) int {
	    return x + y
    }

When I don't have the above libraries compiled and just use go install `hello` program is installed and works but the `pkg` directory is not created and no `stringutil.a` and `tttt.a`.

If I want to have libraries generated I have to use `go install` on every library, in which case `pkg` is generated and libraries in it.

this is not behaviour according to this documentation:

> Whenever the go tool installs a package or binary, it also installs whatever dependencies it has. So when you install the hello program
$ go install github.com/user/hello
the stringutil package will be installed as well, automatically.

Note that I have just installed the latest version (1.10) and just start using it as is writing only one dummy program and two dummy libraries one of which is copied from Go documentation.

### What did you expect to see?
Dependencies installed automatically in the `pkg`

### What did you see instead?
No `pkg` and no installed dependencies",1.0,"doc/code.html: update description of install command - ### What version of Go are you using (go version)?
`go version go1.10 windows/amd64`

### Does this issue reproduce with the latest release?
1.10 is the latest at this moment

### What operating system and processor architecture are you using (go env)?
GOARCH=amd64
GOOS=windows

### What did you do?
I have small test program with two small dummy libraries.

Go program in the `src` has path `github.com/user/hello`

    package main

    import (
        ""fmt""
 
        // Libraries bellow are not automatically generated in pkg
        ""github.com/user/stringutil""
        ""github.com/user/tttt""
    )

    func main() {
        fmt.Printf(stringutil.Reverse(""\nHello, world.\n""))
        fmt.Println(add(85,tttt.Tttt(9)))
    }

`add()` function is in separate file, also in `hello` directory:

    package main

    func add(x int, y int) int {
	    return x + y
    }

When I don't have the above libraries compiled and just use go install `hello` program is installed and works but the `pkg` directory is not created and no `stringutil.a` and `tttt.a`.

If I want to have libraries generated I have to use `go install` on every library, in which case `pkg` is generated and libraries in it.

this is not behaviour according to this documentation:

> Whenever the go tool installs a package or binary, it also installs whatever dependencies it has. So when you install the hello program
$ go install github.com/user/hello
the stringutil package will be installed as well, automatically.

Note that I have just installed the latest version (1.10) and just start using it as is writing only one dummy program and two dummy libraries one of which is copied from Go documentation.

### What did you expect to see?
Dependencies installed automatically in the `pkg`

### What did you see instead?
No `pkg` and no installed dependencies",1,doc code html  update description of install command       what version of go are you using  go version     go version     windows           does this issue reproduce with the latest release       is the latest at this moment        what operating system and processor architecture are you using  go env    goarch    goos windows        what did you do   i have small test program with two small dummy libraries     go program in the  src  has path  github com user hello         package main        import             fmt                 libraries bellow are not automatically generated in pkg           github com user stringutil            github com user tttt                func main              fmt printf stringutil reverse   nhello  world  n             fmt println add   tttt tttt                 add    function is in separate file  also in  hello  directory         package main        func add x int  y int  int    	    return x   y           when i don t have the above libraries compiled and just use go install  hello  program is installed and works but the  pkg  directory is not created and no  stringutil a  and  tttt a      if i want to have libraries generated i have to use  go install  on every library  in which case  pkg  is generated and libraries in it     this is not behaviour according to this documentation       whenever the go tool installs a package or binary  it also installs whatever dependencies it has  so when you install the hello program    go install github com user hello  the stringutil package will be installed as well  automatically     note that i have just installed the latest version       and just start using it as is writing only one dummy program and two dummy libraries one of which is copied from go documentation         what did you expect to see   dependencies installed automatically in the  pkg         what did you see instead   no  pkg  and no installed dependencies,1
292571,25223682000.0,IssuesEvent,2022-11-14 14:34:41,MPMG-DCC-UFMG/F01,https://api.github.com/repos/MPMG-DCC-UFMG/F01,closed,Teste de generalizacao para a tag Informações Institucionais - Registro das Competências - Veríssimo,generalization test development template - Template1 (22) tag - Informações Institucionais subtag - Registro das Competências,DoD: Realizar o teste de Generalização do validador da tag Informações Institucionais - Registro das Competências para o Município de Veríssimo.,1.0,Teste de generalizacao para a tag Informações Institucionais - Registro das Competências - Veríssimo - DoD: Realizar o teste de Generalização do validador da tag Informações Institucionais - Registro das Competências para o Município de Veríssimo.,0,teste de generalizacao para a tag informações institucionais   registro das competências   veríssimo   dod  realizar o teste de generalização do validador da tag informações institucionais   registro das competências para o município de veríssimo ,0
282065,8703374124.0,IssuesEvent,2018-12-05 16:30:25,googleapis/google-cloud-ruby,https://api.github.com/repos/googleapis/google-cloud-ruby,closed,Race condition in stream.rb on ack deadline modification,api: pubsub priority: p2 type: bug,"#### Environment details

  - OS: Mac OS X 10.14.1
  - Ruby version: 2.5.3
  - Gem name and version: `gem(""google-cloud-pubsub"", require: ""google/cloud/pubsub"")`, locked at `0.33.2`

#### Steps to reproduce

  1. Create a job that executes in negligible time by using the thread pool implementation provided by `subscription.listen`
  2. The default `ack` deadline set on the `subscription` will be used to `modify_ack_deadline!` of `received_messages`
  3. Since this happens on another thread (?) (`AsyncUnaryPusher ` as far as I can tell, the code is a bit dense and takes time to decipher)...
  4. ...if the user defined job's delay call happens before the subscriber's call, the user defined deadline will be overridden.

The serialisation issues in the Ruby library (ignoring network ordering issues) can be solved by tracking if the user has already called delay by the time the pusher calls it.

The above is a mere supposition, please treat as such. :)",1.0,"Race condition in stream.rb on ack deadline modification - #### Environment details

  - OS: Mac OS X 10.14.1
  - Ruby version: 2.5.3
  - Gem name and version: `gem(""google-cloud-pubsub"", require: ""google/cloud/pubsub"")`, locked at `0.33.2`

#### Steps to reproduce

  1. Create a job that executes in negligible time by using the thread pool implementation provided by `subscription.listen`
  2. The default `ack` deadline set on the `subscription` will be used to `modify_ack_deadline!` of `received_messages`
  3. Since this happens on another thread (?) (`AsyncUnaryPusher ` as far as I can tell, the code is a bit dense and takes time to decipher)...
  4. ...if the user defined job's delay call happens before the subscriber's call, the user defined deadline will be overridden.

The serialisation issues in the Ruby library (ignoring network ordering issues) can be solved by tracking if the user has already called delay by the time the pusher calls it.

The above is a mere supposition, please treat as such. :)",0,race condition in stream rb on ack deadline modification        environment details        os  mac os x            ruby version             gem name and version   gem  google cloud pubsub   require   google cloud pubsub     locked at                 steps to reproduce         create a job that executes in negligible time by using the thread pool implementation provided by  subscription listen        the default  ack  deadline set on the  subscription  will be used to  modify ack deadline   of  received messages        since this happens on another thread       asyncunarypusher   as far as i can tell  the code is a bit dense and takes time to decipher              if the user defined job s delay call happens before the subscriber s call  the user defined deadline will be overridden     the serialisation issues in the ruby library  ignoring network ordering issues  can be solved by tracking if the user has already called delay by the time the pusher calls it     the above is a mere supposition  please treat as such    ,0
28857,12976146010.0,IssuesEvent,2020-07-21 18:14:53,cityofaustin/atd-data-tech,https://api.github.com/repos/cityofaustin/atd-data-tech,closed,Update By Mode Title,Product: Vision Zero Viewer Service: Dev Workgroup: VZ,Udate the title for the mode visualization from By Mode to By Travel Mode,1.0,Update By Mode Title - Udate the title for the mode visualization from By Mode to By Travel Mode,0,update by mode title   udate the title for the mode visualization from by mode to by travel mode,0
49983,7549547129.0,IssuesEvent,2018-04-18 14:31:15,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: docs need section on cross-compiling,Documentation NeedsFix,"I got OK to post this issue from:
https://groups.google.com/d/msg/golang-nuts/IW4FiCclZTw/45wa1V9UBwAJ

Add a new section to docs for cmd/go: ""Cross Compiling""

Instructions to rebuild Go source for new platform:

```
sudo GOOS=linux GOARCH=arm CGO_ENABLED=1 CC=arm-linux-gnueabihf-gcc go install -v -a std
sudo GOOS=linux GOARCH=arm CGO_ENABLED=1 CC=arm-linux-gnueabihf-gcc go install -v -a cmd

sudo is required if Go was installed via system package manager
CGO_ENABLED and CC are only required for cross-compiling with C source
CC varies for the toolchain installed
```

Instructions for cross compiling packages:

```
GOOS=linux GOARCH=arm go install -v github.com/id/package # .go only
GOOS=linux GOARCH=arm CGO_ENABLED=1 CC=... go install -v github.com/id/package # .go & .c

GOARM=5|6|7 may be included to generate optimized code for that family

Output lands in:
$GOPATH/pkg/$GOOS_$GOARCH/github.com/id/package
$GOPATH/bin/$GOOS_$GOARCH/package
```

Also need instructions for Windows, OS X, etc.
",1.0,"cmd/go: docs need section on cross-compiling - I got OK to post this issue from:
https://groups.google.com/d/msg/golang-nuts/IW4FiCclZTw/45wa1V9UBwAJ

Add a new section to docs for cmd/go: ""Cross Compiling""

Instructions to rebuild Go source for new platform:

```
sudo GOOS=linux GOARCH=arm CGO_ENABLED=1 CC=arm-linux-gnueabihf-gcc go install -v -a std
sudo GOOS=linux GOARCH=arm CGO_ENABLED=1 CC=arm-linux-gnueabihf-gcc go install -v -a cmd

sudo is required if Go was installed via system package manager
CGO_ENABLED and CC are only required for cross-compiling with C source
CC varies for the toolchain installed
```

Instructions for cross compiling packages:

```
GOOS=linux GOARCH=arm go install -v github.com/id/package # .go only
GOOS=linux GOARCH=arm CGO_ENABLED=1 CC=... go install -v github.com/id/package # .go & .c

GOARM=5|6|7 may be included to generate optimized code for that family

Output lands in:
$GOPATH/pkg/$GOOS_$GOARCH/github.com/id/package
$GOPATH/bin/$GOOS_$GOARCH/package
```

Also need instructions for Windows, OS X, etc.
",1,cmd go  docs need section on cross compiling   i got ok to post this issue from     add a new section to docs for cmd go   cross compiling   instructions to rebuild go source for new platform       sudo goos linux goarch arm cgo enabled   cc arm linux gnueabihf gcc go install  v  a std sudo goos linux goarch arm cgo enabled   cc arm linux gnueabihf gcc go install  v  a cmd  sudo is required if go was installed via system package manager cgo enabled and cc are only required for cross compiling with c source cc varies for the toolchain installed      instructions for cross compiling packages       goos linux goarch arm go install  v github com id package    go only goos linux goarch arm cgo enabled   cc     go install  v github com id package    go    c  goarm       may be included to generate optimized code for that family  output lands in   gopath pkg  goos  goarch github com id package  gopath bin  goos  goarch package      also need instructions for windows  os x  etc  ,1
22079,4771826403.0,IssuesEvent,2016-10-26 19:05:44,golang/go,https://api.github.com/repos/golang/go,opened,net: inaccurate docs about announcing or listening on all local addresses,Documentation,"The current documentation says:
```
func Listen, ListenPacket, Listen{TCP,UDP,UP}

Listen listens on all available interfaces instead of just the interface with the given
host address. 
```
I think it provides inaccurate information. What happens when you move an interface address on network interface X to another? Does it break your application? (Please consider that how VRRP or CARP works) Actually it announcing or listening on `all local addresses`.
",1.0,"net: inaccurate docs about announcing or listening on all local addresses - The current documentation says:
```
func Listen, ListenPacket, Listen{TCP,UDP,UP}

Listen listens on all available interfaces instead of just the interface with the given
host address. 
```
I think it provides inaccurate information. What happens when you move an interface address on network interface X to another? Does it break your application? (Please consider that how VRRP or CARP works) Actually it announcing or listening on `all local addresses`.
",1,net  inaccurate docs about announcing or listening on all local addresses   the current documentation says        func listen  listenpacket  listen tcp udp up     listen listens on all available interfaces instead of just the interface with the given  host address         i think it provides inaccurate information  what happens when you move an interface address on network interface x to another  does it break your application   please consider that how vrrp or carp works  actually it announcing or listening on  all local addresses    ,1
323548,27734435333.0,IssuesEvent,2023-03-15 10:15:30,kubernetes-sigs/kubespray,https://api.github.com/repos/kubernetes-sigs/kubespray,closed,Cannot deploy kubernetes using Kubespray,lifecycle/rotten kind/failing-test,"**I'm a newbie when using Kubespray.
I'm just following step-by-step from the youtube video.**
**This's the link**: [https://www.youtube.com/watch?v=CJ5G4GpqDy0](https://www.youtube.com/watch?v=CJ5G4GpqDy0)
### I created 3 VMs which run ubuntu server 22.04. With their local IP address below:

> my computer: 192.168.1.29
> master node 192.168.1.64
> worker1 node: 192.168.1.65
> worker2 node: 192.168.1.66

### I ran those commands:

> cp -rfp inventory/sample inventory/mycluster
> declare -a IPS=(192.168.1.64 192.168.1.65 192.168.1.66)
> CONFIG_FILE=inventory/mycluster/hosts.yml python3 contrib/inventory_builder/inventory.py ${IPS[@]}
> ansible-playbook -i inventory/mycluster/hosts.yml --become --become-user=root cluster.yml

### So, I received the result below:
_(**when I ran** CONFIG_FILE=inventory/mycluster/hosts.yml python3 contrib/inventory_builder/inventory.py ${IPS[@]})_

> DEBUG: Adding group all
> DEBUG: Adding group kube_control_plane
> DEBUG: Adding group kube_node
> DEBUG: Adding group etcd
> DEBUG: Adding group k8s_cluster
> DEBUG: Adding group calico_rr
> DEBUG: adding host node1 to group all
> DEBUG: adding host node2 to group all
> DEBUG: adding host node3 to group all
> DEBUG: adding host node1 to group etcd
> DEBUG: adding host node2 to group etcd
> DEBUG: adding host node3 to group etcd
> DEBUG: adding host node1 to group kube_control_plane
> DEBUG: adding host node2 to group kube_control_plane
> DEBUG: adding host node1 to group kube_node
> DEBUG: adding host node2 to group kube_node
> DEBUG: adding host node3 to group kube_node

_**When I ran** ansible-playbook -i inventory/mycluster/hosts.yml --become --become-user=root cluster.yml, **I got huge logs, but I just highlight the log that color is red**._

> fatal: [node2]: FAILED! => {""changed"": false, ""cmd"": ""/usr/local/bin/etcd --version"", ""msg"": ""[Errno 2] No such file or directory: b'/usr/local/bin/etcd'"", ""rc"": 2, ""stderr"": """", ""stderr_lines"": [], ""stdout"": """", ""stdout_lines"": []}
> ...ignoring
> fatal: [node1]: FAILED! => {""changed"": false, ""cmd"": ""/usr/local/bin/etcd --version"", ""msg"": ""[Errno 2] No such file or directory: b'/usr/local/bin/etcd'"", ""rc"": 2, ""stderr"": """", ""stderr_lines"": [], ""stdout"": """", ""stdout_lines"": []}
> ...ignoring
> fatal: [node3]: FAILED! => {""changed"": false, ""cmd"": ""/usr/local/bin/etcd --version"", ""msg"": ""[Errno 2] No such file or directory: b'/usr/local/bin/etcd'"", ""rc"": 2, ""stderr"": """", ""stderr_lines"": [], ""stdout"": """", ""stdout_lines"": []}
> ...ignoring

### And:

> fatal: [node2]: FAILED! => {""changed"": false, ""msg"": ""modprobe: FATAL: Module nf_conntrack_ipv4 not found in directory /lib/modules/5.15.0-47-generic\n"", ""name"": ""nf_conntrack_ipv4"", ""params"": """", ""rc"": 1, ""state"": ""present"", ""stderr"": ""modprobe: FATAL: Module nf_conntrack_ipv4 not found in directory /lib/modules/5.15.0-47-generic\n"", ""stderr_lines"": [""modprobe: FATAL: Module nf_conntrack_ipv4 not found in directory /lib/modules/5.15.0-47-generic""], ""stdout"": """", ""stdout_lines"": []}
> ...ignoring
> fatal: [node1]: FAILED! => {""changed"": false, ""msg"": ""modprobe: FATAL: Module nf_conntrack_ipv4 not found in directory /lib/modules/5.15.0-47-generic\n"", ""name"": ""nf_conntrack_ipv4"", ""params"": """", ""rc"": 1, ""state"": ""present"", ""stderr"": ""modprobe: FATAL: Module nf_conntrack_ipv4 not found in directory /lib/modules/5.15.0-47-generic\n"", ""stderr_lines"": [""modprobe: FATAL: Module nf_conntrack_ipv4 not found in directory /lib/modules/5.15.0-47-generic""], ""stdout"": """", ""stdout_lines"": []}
> ...ignoring
> fatal: [node3]: FAILED! => {""changed"": false, ""msg"": ""modprobe: FATAL: Module nf_conntrack_ipv4 not found in directory /lib/modules/5.15.0-47-generic\n"", ""name"": ""nf_conntrack_ipv4"", ""params"": """", ""rc"": 1, ""state"": ""present"", ""stderr"": ""modprobe: FATAL: Module nf_conntrack_ipv4 not found in directory /lib/modules/5.15.0-47-generic\n"", ""stderr_lines"": [""modprobe: FATAL: Module nf_conntrack_ipv4 not found in directory /lib/modules/5.15.0-47-generic""], ""stdout"": """", ""stdout_lines"": []}
> ...ignoring

### Next:

> fatal: [node1]: FAILED! => {""changed"": false, ""cmd"": [""/usr/local/bin/kubectl"", ""get"", ""nodes"", ""--selector=node-role.kubernetes.io/control-plane"", ""-o"", ""json""], ""delta"": ""0:00:00.060846"", ""end"": ""2022-09-19 10:07:08.286847"", ""msg"": ""non-zero return code"", ""rc"": 1, ""start"": ""2022-09-19 10:07:08.226001"", ""stderr"": ""The connection to the server localhost:8080 was refused - did you specify the right host or port?"", ""stderr_lines"": [""The connection to the server localhost:8080 was refused - did you specify the right host or port?""], ""stdout"": """", ""stdout_lines"": []}
> ...ignoring
> fatal: [node2]: FAILED! => {""changed"": false, ""cmd"": [""/usr/local/bin/kubectl"", ""get"", ""nodes"", ""--selector=node-role.kubernetes.io/control-plane"", ""-o"", ""json""], ""delta"": ""0:00:00.103256"", ""end"": ""2022-09-19 10:07:08.312432"", ""msg"": ""non-zero return code"", ""rc"": 1, ""start"": ""2022-09-19 10:07:08.209176"", ""stderr"": ""The connection to the server localhost:8080 was refused - did you specify the right host or port?"", ""stderr_lines"": [""The connection to the server localhost:8080 was refused - did you specify the right host or port?""], ""stdout"": """", ""stdout_lines"": []}
> ...ignoring
> 

### And the last:

> fatal: [node1]: FAILED! => {""attempts"": 3, ""changed"": true, ""cmd"": [""timeout"", ""-k"", ""300s"", ""300s"", ""/usr/local/bin/kubeadm"", ""init"", ""--config=/etc/kubernetes/kubeadm-config.yaml"", ""--ignore-preflight-errors=all"", ""--skip-phases=addon/coredns"", ""--upload-certs""], ""delta"": ""0:05:00.006231"", ""end"": ""2022-09-19 10:27:26.745309"", ""failed_when_result"": true, ""msg"": ""non-zero return code"", ""rc"": 124, ""start"": ""2022-09-19 10:22:26.739078"", ""stderr"": ""W0919 10:22:26.762706  227754 utils.go:69] The recommended value for \""clusterDNS\"" in \""KubeletConfiguration\"" is: [10.233.0.10]; the provided value is: [169.254.25.10]\n\t[WARNING Port-10259]: Port 10259 is in use\n\t[WARNING Port-10257]: Port 10257 is in use\n\t[WARNING FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists\n\t[WARNING FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists\n\t[WARNING FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists\n\t[WARNING SystemVerification]: missing optional cgroups: blkio\n\t[WARNING Port-10250]: Port 10250 is in use"", ""stderr_lines"": [""W0919 10:22:26.762706  227754 utils.go:69] The recommended value for \""clusterDNS\"" in \""KubeletConfiguration\"" is: [10.233.0.10]; the provided value is: [169.254.25.10]"", ""\t[WARNING Port-10259]: Port 10259 is in use"", ""\t[WARNING Port-10257]: Port 10257 is in use"", ""\t[WARNING FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists"", ""\t[WARNING FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists"", ""\t[WARNING FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists"", ""\t[WARNING SystemVerification]: missing optional cgroups: blkio"", ""\t[WARNING Port-10250]: Port 10250 is in use""], ""stdout"": ""[init] Using Kubernetes version: v1.24.4\n[preflight] Running pre-flight checks\n[preflight] Pulling images required for setting up a Kubernetes cluster\n[preflight] This might take a minute or two, depending on the speed of your internet connection\n[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'\n[certs] Using certificateDir folder \""/etc/kubernetes/ssl\""\n[certs] Using existing ca certificate authority\n[certs] Using existing apiserver certificate and key on disk\n[certs] Using existing apiserver-kubelet-client certificate and key on disk\n[certs] Using existing front-proxy-ca certificate authority\n[certs] Using existing front-proxy-client certificate and key on disk\n[certs] External etcd mode: Skipping etcd/ca certificate authority generation\n[certs] External etcd mode: Skipping etcd/server certificate generation\n[certs] External etcd mode: Skipping etcd/peer certificate generation\n[certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n[certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n[certs] Using the existing \""sa\"" key\n[kubeconfig] Using kubeconfig folder \""/etc/kubernetes\""\n[kubeconfig] Using existing kubeconfig file: \""/etc/kubernetes/admin.conf\""\n[kubeconfig] Using existing kubeconfig file: \""/etc/kubernetes/kubelet.conf\""\n[kubeconfig] Using existing kubeconfig file: \""/etc/kubernetes/controller-manager.conf\""\n[kubeconfig] Using existing kubeconfig file: \""/etc/kubernetes/scheduler.conf\""\n[kubelet-start] Writing kubelet environment file with flags to file \""/var/lib/kubelet/kubeadm-flags.env\""\n[kubelet-start] Writing kubelet configuration to file \""/var/lib/kubelet/config.yaml\""\n[kubelet-start] Starting the kubelet\n[control-plane] Using manifest folder \""/etc/kubernetes/manifests\""\n[control-plane] Creating static Pod manifest for \""kube-apiserver\""\n[control-plane] Creating static Pod manifest for \""kube-controller-manager\""\n[control-plane] Creating static Pod manifest for \""kube-scheduler\""\n[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \""/etc/kubernetes/manifests\"". This can take up to 5m0s\n[kubelet-check] Initial timeout of 40s passed."", ""stdout_lines"": [""[init] Using Kubernetes version: v1.24.4"", ""[preflight] Running pre-flight checks"", ""[preflight] Pulling images required for setting up a Kubernetes cluster"", ""[preflight] This might take a minute or two, depending on the speed of your internet connection"", ""[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'"", ""[certs] Using certificateDir folder \""/etc/kubernetes/ssl\"""", ""[certs] Using existing ca certificate authority"", ""[certs] Using existing apiserver certificate and key on disk"", ""[certs] Using existing apiserver-kubelet-client certificate and key on disk"", ""[certs] Using existing front-proxy-ca certificate authority"", ""[certs] Using existing front-proxy-client certificate and key on disk"", ""[certs] External etcd mode: Skipping etcd/ca certificate authority generation"", ""[certs] External etcd mode: Skipping etcd/server certificate generation"", ""[certs] External etcd mode: Skipping etcd/peer certificate generation"", ""[certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation"", ""[certs] External etcd mode: Skipping apiserver-etcd-client certificate generation"", ""[certs] Using the existing \""sa\"" key"", ""[kubeconfig] Using kubeconfig folder \""/etc/kubernetes\"""", ""[kubeconfig] Using existing kubeconfig file: \""/etc/kubernetes/admin.conf\"""", ""[kubeconfig] Using existing kubeconfig file: \""/etc/kubernetes/kubelet.conf\"""", ""[kubeconfig] Using existing kubeconfig file: \""/etc/kubernetes/controller-manager.conf\"""", ""[kubeconfig] Using existing kubeconfig file: \""/etc/kubernetes/scheduler.conf\"""", ""[kubelet-start] Writing kubelet environment file with flags to file \""/var/lib/kubelet/kubeadm-flags.env\"""", ""[kubelet-start] Writing kubelet configuration to file \""/var/lib/kubelet/config.yaml\"""", ""[kubelet-start] Starting the kubelet"", ""[control-plane] Using manifest folder \""/etc/kubernetes/manifests\"""", ""[control-plane] Creating static Pod manifest for \""kube-apiserver\"""", ""[control-plane] Creating static Pod manifest for \""kube-controller-manager\"""", ""[control-plane] Creating static Pod manifest for \""kube-scheduler\"""", ""[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \""/etc/kubernetes/manifests\"". This can take up to 5m0s"", ""[kubelet-check] Initial timeout of 40s passed.""]}

### And then, I also got this log below:

> PLAY RECAP *******************************************************************************************************
> localhost                  : ok=3    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   
> node1                      : ok=588  changed=73   unreachable=0    failed=1    skipped=715  rescued=0    ignored=4   
> node2                      : ok=550  changed=70   unreachable=0    failed=0    skipped=607  rescued=0    ignored=4   
> node3                      : ok=479  changed=64   unreachable=0    failed=0    skipped=531  rescued=0    ignored=3   
> 
> Monday 19 9 2022  17:27:26 +0700 (0:20:15.935)       0:30:19.822 
> =============================================================================== 
> kubernetes/control-plane : kubeadm | Initialize first master ------------------------------------------- 1215.94s
> download : download_container | Download image if required ----------------------------------------------- 38.96s
> etcd : reload etcd --------------------------------------------------------------------------------------- 31.67s
> download : download_container | Download image if required ----------------------------------------------- 31.05s
> container-engine/runc : download_file | Validate mirrors ------------------------------------------------- 29.18s
> download : download_file | Validate mirrors -------------------------------------------------------------- 25.18s
> download : download_container | Download image if required ----------------------------------------------- 23.41s
> download : download_container | Download image if required ----------------------------------------------- 22.07s
> download : download_container | Download image if required ----------------------------------------------- 18.73s
> download : download_container | Download image if required ----------------------------------------------- 18.31s
> download : download_container | Download image if required ----------------------------------------------- 17.74s
> download : download_container | Download image if required ----------------------------------------------- 15.82s
> etcd : Gen_certs | Write etcd member/admin and kube_control_plane clinet certs to other etcd nodes ------- 11.99s
> download : download_container | Download image if required ----------------------------------------------- 10.74s
> download : download_container | Download image if required ------------------------------------------------ 9.75s
> download : download_container | Download image if required ------------------------------------------------ 8.01s
> download : download_container | Download image if required ------------------------------------------------ 6.58s
> etcd : Configure | Check if etcd cluster is healthy ------------------------------------------------------- 5.39s
> container-engine/containerd : containerd | Unpack containerd archive -------------------------------------- 4.39s
> etcd : Gen_certs | Gather etcd member/admin and kube_control_plane clinet certs from first etcd node ------ 4.39s

**_That is all of the things I got._**

_**So, please tell me the reason why I can deploy Kubernetes. 
Thanks for reading.**_


",1.0,"Cannot deploy kubernetes using Kubespray - **I'm a newbie when using Kubespray.
I'm just following step-by-step from the youtube video.**
**This's the link**: [https://www.youtube.com/watch?v=CJ5G4GpqDy0](https://www.youtube.com/watch?v=CJ5G4GpqDy0)
### I created 3 VMs which run ubuntu server 22.04. With their local IP address below:

> my computer: 192.168.1.29
> master node 192.168.1.64
> worker1 node: 192.168.1.65
> worker2 node: 192.168.1.66

### I ran those commands:

> cp -rfp inventory/sample inventory/mycluster
> declare -a IPS=(192.168.1.64 192.168.1.65 192.168.1.66)
> CONFIG_FILE=inventory/mycluster/hosts.yml python3 contrib/inventory_builder/inventory.py ${IPS[@]}
> ansible-playbook -i inventory/mycluster/hosts.yml --become --become-user=root cluster.yml

### So, I received the result below:
_(**when I ran** CONFIG_FILE=inventory/mycluster/hosts.yml python3 contrib/inventory_builder/inventory.py ${IPS[@]})_

> DEBUG: Adding group all
> DEBUG: Adding group kube_control_plane
> DEBUG: Adding group kube_node
> DEBUG: Adding group etcd
> DEBUG: Adding group k8s_cluster
> DEBUG: Adding group calico_rr
> DEBUG: adding host node1 to group all
> DEBUG: adding host node2 to group all
> DEBUG: adding host node3 to group all
> DEBUG: adding host node1 to group etcd
> DEBUG: adding host node2 to group etcd
> DEBUG: adding host node3 to group etcd
> DEBUG: adding host node1 to group kube_control_plane
> DEBUG: adding host node2 to group kube_control_plane
> DEBUG: adding host node1 to group kube_node
> DEBUG: adding host node2 to group kube_node
> DEBUG: adding host node3 to group kube_node

_**When I ran** ansible-playbook -i inventory/mycluster/hosts.yml --become --become-user=root cluster.yml, **I got huge logs, but I just highlight the log that color is red**._

> fatal: [node2]: FAILED! => {""changed"": false, ""cmd"": ""/usr/local/bin/etcd --version"", ""msg"": ""[Errno 2] No such file or directory: b'/usr/local/bin/etcd'"", ""rc"": 2, ""stderr"": """", ""stderr_lines"": [], ""stdout"": """", ""stdout_lines"": []}
> ...ignoring
> fatal: [node1]: FAILED! => {""changed"": false, ""cmd"": ""/usr/local/bin/etcd --version"", ""msg"": ""[Errno 2] No such file or directory: b'/usr/local/bin/etcd'"", ""rc"": 2, ""stderr"": """", ""stderr_lines"": [], ""stdout"": """", ""stdout_lines"": []}
> ...ignoring
> fatal: [node3]: FAILED! => {""changed"": false, ""cmd"": ""/usr/local/bin/etcd --version"", ""msg"": ""[Errno 2] No such file or directory: b'/usr/local/bin/etcd'"", ""rc"": 2, ""stderr"": """", ""stderr_lines"": [], ""stdout"": """", ""stdout_lines"": []}
> ...ignoring

### And:

> fatal: [node2]: FAILED! => {""changed"": false, ""msg"": ""modprobe: FATAL: Module nf_conntrack_ipv4 not found in directory /lib/modules/5.15.0-47-generic\n"", ""name"": ""nf_conntrack_ipv4"", ""params"": """", ""rc"": 1, ""state"": ""present"", ""stderr"": ""modprobe: FATAL: Module nf_conntrack_ipv4 not found in directory /lib/modules/5.15.0-47-generic\n"", ""stderr_lines"": [""modprobe: FATAL: Module nf_conntrack_ipv4 not found in directory /lib/modules/5.15.0-47-generic""], ""stdout"": """", ""stdout_lines"": []}
> ...ignoring
> fatal: [node1]: FAILED! => {""changed"": false, ""msg"": ""modprobe: FATAL: Module nf_conntrack_ipv4 not found in directory /lib/modules/5.15.0-47-generic\n"", ""name"": ""nf_conntrack_ipv4"", ""params"": """", ""rc"": 1, ""state"": ""present"", ""stderr"": ""modprobe: FATAL: Module nf_conntrack_ipv4 not found in directory /lib/modules/5.15.0-47-generic\n"", ""stderr_lines"": [""modprobe: FATAL: Module nf_conntrack_ipv4 not found in directory /lib/modules/5.15.0-47-generic""], ""stdout"": """", ""stdout_lines"": []}
> ...ignoring
> fatal: [node3]: FAILED! => {""changed"": false, ""msg"": ""modprobe: FATAL: Module nf_conntrack_ipv4 not found in directory /lib/modules/5.15.0-47-generic\n"", ""name"": ""nf_conntrack_ipv4"", ""params"": """", ""rc"": 1, ""state"": ""present"", ""stderr"": ""modprobe: FATAL: Module nf_conntrack_ipv4 not found in directory /lib/modules/5.15.0-47-generic\n"", ""stderr_lines"": [""modprobe: FATAL: Module nf_conntrack_ipv4 not found in directory /lib/modules/5.15.0-47-generic""], ""stdout"": """", ""stdout_lines"": []}
> ...ignoring

### Next:

> fatal: [node1]: FAILED! => {""changed"": false, ""cmd"": [""/usr/local/bin/kubectl"", ""get"", ""nodes"", ""--selector=node-role.kubernetes.io/control-plane"", ""-o"", ""json""], ""delta"": ""0:00:00.060846"", ""end"": ""2022-09-19 10:07:08.286847"", ""msg"": ""non-zero return code"", ""rc"": 1, ""start"": ""2022-09-19 10:07:08.226001"", ""stderr"": ""The connection to the server localhost:8080 was refused - did you specify the right host or port?"", ""stderr_lines"": [""The connection to the server localhost:8080 was refused - did you specify the right host or port?""], ""stdout"": """", ""stdout_lines"": []}
> ...ignoring
> fatal: [node2]: FAILED! => {""changed"": false, ""cmd"": [""/usr/local/bin/kubectl"", ""get"", ""nodes"", ""--selector=node-role.kubernetes.io/control-plane"", ""-o"", ""json""], ""delta"": ""0:00:00.103256"", ""end"": ""2022-09-19 10:07:08.312432"", ""msg"": ""non-zero return code"", ""rc"": 1, ""start"": ""2022-09-19 10:07:08.209176"", ""stderr"": ""The connection to the server localhost:8080 was refused - did you specify the right host or port?"", ""stderr_lines"": [""The connection to the server localhost:8080 was refused - did you specify the right host or port?""], ""stdout"": """", ""stdout_lines"": []}
> ...ignoring
> 

### And the last:

> fatal: [node1]: FAILED! => {""attempts"": 3, ""changed"": true, ""cmd"": [""timeout"", ""-k"", ""300s"", ""300s"", ""/usr/local/bin/kubeadm"", ""init"", ""--config=/etc/kubernetes/kubeadm-config.yaml"", ""--ignore-preflight-errors=all"", ""--skip-phases=addon/coredns"", ""--upload-certs""], ""delta"": ""0:05:00.006231"", ""end"": ""2022-09-19 10:27:26.745309"", ""failed_when_result"": true, ""msg"": ""non-zero return code"", ""rc"": 124, ""start"": ""2022-09-19 10:22:26.739078"", ""stderr"": ""W0919 10:22:26.762706  227754 utils.go:69] The recommended value for \""clusterDNS\"" in \""KubeletConfiguration\"" is: [10.233.0.10]; the provided value is: [169.254.25.10]\n\t[WARNING Port-10259]: Port 10259 is in use\n\t[WARNING Port-10257]: Port 10257 is in use\n\t[WARNING FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists\n\t[WARNING FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists\n\t[WARNING FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists\n\t[WARNING SystemVerification]: missing optional cgroups: blkio\n\t[WARNING Port-10250]: Port 10250 is in use"", ""stderr_lines"": [""W0919 10:22:26.762706  227754 utils.go:69] The recommended value for \""clusterDNS\"" in \""KubeletConfiguration\"" is: [10.233.0.10]; the provided value is: [169.254.25.10]"", ""\t[WARNING Port-10259]: Port 10259 is in use"", ""\t[WARNING Port-10257]: Port 10257 is in use"", ""\t[WARNING FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists"", ""\t[WARNING FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists"", ""\t[WARNING FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists"", ""\t[WARNING SystemVerification]: missing optional cgroups: blkio"", ""\t[WARNING Port-10250]: Port 10250 is in use""], ""stdout"": ""[init] Using Kubernetes version: v1.24.4\n[preflight] Running pre-flight checks\n[preflight] Pulling images required for setting up a Kubernetes cluster\n[preflight] This might take a minute or two, depending on the speed of your internet connection\n[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'\n[certs] Using certificateDir folder \""/etc/kubernetes/ssl\""\n[certs] Using existing ca certificate authority\n[certs] Using existing apiserver certificate and key on disk\n[certs] Using existing apiserver-kubelet-client certificate and key on disk\n[certs] Using existing front-proxy-ca certificate authority\n[certs] Using existing front-proxy-client certificate and key on disk\n[certs] External etcd mode: Skipping etcd/ca certificate authority generation\n[certs] External etcd mode: Skipping etcd/server certificate generation\n[certs] External etcd mode: Skipping etcd/peer certificate generation\n[certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n[certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n[certs] Using the existing \""sa\"" key\n[kubeconfig] Using kubeconfig folder \""/etc/kubernetes\""\n[kubeconfig] Using existing kubeconfig file: \""/etc/kubernetes/admin.conf\""\n[kubeconfig] Using existing kubeconfig file: \""/etc/kubernetes/kubelet.conf\""\n[kubeconfig] Using existing kubeconfig file: \""/etc/kubernetes/controller-manager.conf\""\n[kubeconfig] Using existing kubeconfig file: \""/etc/kubernetes/scheduler.conf\""\n[kubelet-start] Writing kubelet environment file with flags to file \""/var/lib/kubelet/kubeadm-flags.env\""\n[kubelet-start] Writing kubelet configuration to file \""/var/lib/kubelet/config.yaml\""\n[kubelet-start] Starting the kubelet\n[control-plane] Using manifest folder \""/etc/kubernetes/manifests\""\n[control-plane] Creating static Pod manifest for \""kube-apiserver\""\n[control-plane] Creating static Pod manifest for \""kube-controller-manager\""\n[control-plane] Creating static Pod manifest for \""kube-scheduler\""\n[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \""/etc/kubernetes/manifests\"". This can take up to 5m0s\n[kubelet-check] Initial timeout of 40s passed."", ""stdout_lines"": [""[init] Using Kubernetes version: v1.24.4"", ""[preflight] Running pre-flight checks"", ""[preflight] Pulling images required for setting up a Kubernetes cluster"", ""[preflight] This might take a minute or two, depending on the speed of your internet connection"", ""[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'"", ""[certs] Using certificateDir folder \""/etc/kubernetes/ssl\"""", ""[certs] Using existing ca certificate authority"", ""[certs] Using existing apiserver certificate and key on disk"", ""[certs] Using existing apiserver-kubelet-client certificate and key on disk"", ""[certs] Using existing front-proxy-ca certificate authority"", ""[certs] Using existing front-proxy-client certificate and key on disk"", ""[certs] External etcd mode: Skipping etcd/ca certificate authority generation"", ""[certs] External etcd mode: Skipping etcd/server certificate generation"", ""[certs] External etcd mode: Skipping etcd/peer certificate generation"", ""[certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation"", ""[certs] External etcd mode: Skipping apiserver-etcd-client certificate generation"", ""[certs] Using the existing \""sa\"" key"", ""[kubeconfig] Using kubeconfig folder \""/etc/kubernetes\"""", ""[kubeconfig] Using existing kubeconfig file: \""/etc/kubernetes/admin.conf\"""", ""[kubeconfig] Using existing kubeconfig file: \""/etc/kubernetes/kubelet.conf\"""", ""[kubeconfig] Using existing kubeconfig file: \""/etc/kubernetes/controller-manager.conf\"""", ""[kubeconfig] Using existing kubeconfig file: \""/etc/kubernetes/scheduler.conf\"""", ""[kubelet-start] Writing kubelet environment file with flags to file \""/var/lib/kubelet/kubeadm-flags.env\"""", ""[kubelet-start] Writing kubelet configuration to file \""/var/lib/kubelet/config.yaml\"""", ""[kubelet-start] Starting the kubelet"", ""[control-plane] Using manifest folder \""/etc/kubernetes/manifests\"""", ""[control-plane] Creating static Pod manifest for \""kube-apiserver\"""", ""[control-plane] Creating static Pod manifest for \""kube-controller-manager\"""", ""[control-plane] Creating static Pod manifest for \""kube-scheduler\"""", ""[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \""/etc/kubernetes/manifests\"". This can take up to 5m0s"", ""[kubelet-check] Initial timeout of 40s passed.""]}

### And then, I also got this log below:

> PLAY RECAP *******************************************************************************************************
> localhost                  : ok=3    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   
> node1                      : ok=588  changed=73   unreachable=0    failed=1    skipped=715  rescued=0    ignored=4   
> node2                      : ok=550  changed=70   unreachable=0    failed=0    skipped=607  rescued=0    ignored=4   
> node3                      : ok=479  changed=64   unreachable=0    failed=0    skipped=531  rescued=0    ignored=3   
> 
> Monday 19 9 2022  17:27:26 +0700 (0:20:15.935)       0:30:19.822 
> =============================================================================== 
> kubernetes/control-plane : kubeadm | Initialize first master ------------------------------------------- 1215.94s
> download : download_container | Download image if required ----------------------------------------------- 38.96s
> etcd : reload etcd --------------------------------------------------------------------------------------- 31.67s
> download : download_container | Download image if required ----------------------------------------------- 31.05s
> container-engine/runc : download_file | Validate mirrors ------------------------------------------------- 29.18s
> download : download_file | Validate mirrors -------------------------------------------------------------- 25.18s
> download : download_container | Download image if required ----------------------------------------------- 23.41s
> download : download_container | Download image if required ----------------------------------------------- 22.07s
> download : download_container | Download image if required ----------------------------------------------- 18.73s
> download : download_container | Download image if required ----------------------------------------------- 18.31s
> download : download_container | Download image if required ----------------------------------------------- 17.74s
> download : download_container | Download image if required ----------------------------------------------- 15.82s
> etcd : Gen_certs | Write etcd member/admin and kube_control_plane clinet certs to other etcd nodes ------- 11.99s
> download : download_container | Download image if required ----------------------------------------------- 10.74s
> download : download_container | Download image if required ------------------------------------------------ 9.75s
> download : download_container | Download image if required ------------------------------------------------ 8.01s
> download : download_container | Download image if required ------------------------------------------------ 6.58s
> etcd : Configure | Check if etcd cluster is healthy ------------------------------------------------------- 5.39s
> container-engine/containerd : containerd | Unpack containerd archive -------------------------------------- 4.39s
> etcd : Gen_certs | Gather etcd member/admin and kube_control_plane clinet certs from first etcd node ------ 4.39s

**_That is all of the things I got._**

_**So, please tell me the reason why I can deploy Kubernetes. 
Thanks for reading.**_


",0,cannot deploy kubernetes using kubespray     i m a newbie when using kubespray   i m just following step by step from the youtube video       this s the link             i created   vms which run ubuntu server      with their local ip address below       my computer             master node              node               node                 i ran those commands       cp  rfp inventory sample inventory mycluster    declare  a ips                              config file inventory mycluster hosts yml   contrib inventory builder inventory py   ips      ansible playbook  i inventory mycluster hosts yml   become   become user root cluster yml        so  i received the result below       when i ran   config file inventory mycluster hosts yml   contrib inventory builder inventory py   ips          debug  adding group all    debug  adding group kube control plane    debug  adding group kube node    debug  adding group etcd    debug  adding group   cluster    debug  adding group calico rr    debug  adding host   to group all    debug  adding host   to group all    debug  adding host   to group all    debug  adding host   to group etcd    debug  adding host   to group etcd    debug  adding host   to group etcd    debug  adding host   to group kube control plane    debug  adding host   to group kube control plane    debug  adding host   to group kube node    debug  adding host   to group kube node    debug  adding host   to group kube node       when i ran   ansible playbook  i inventory mycluster hosts yml   become   become user root cluster yml    i got huge logs  but i just highlight the log that color is red          fatal     failed       changed   false   cmd     usr local bin etcd   version    msg      no such file or directory  b  usr local bin etcd     rc       stderr        stderr lines       stdout        stdout lines            ignoring    fatal     failed       changed   false   cmd     usr local bin etcd   version    msg      no such file or directory  b  usr local bin etcd     rc       stderr        stderr lines       stdout        stdout lines            ignoring    fatal     failed       changed   false   cmd     usr local bin etcd   version    msg      no such file or directory  b  usr local bin etcd     rc       stderr        stderr lines       stdout        stdout lines            ignoring        and       fatal     failed       changed   false   msg    modprobe  fatal  module nf conntrack   not found in directory  lib modules         generic n    name    nf conntrack      params        rc       state    present    stderr    modprobe  fatal  module nf conntrack   not found in directory  lib modules         generic n    stderr lines       stdout        stdout lines            ignoring    fatal     failed       changed   false   msg    modprobe  fatal  module nf conntrack   not found in directory  lib modules         generic n    name    nf conntrack      params        rc       state    present    stderr    modprobe  fatal  module nf conntrack   not found in directory  lib modules         generic n    stderr lines       stdout        stdout lines            ignoring    fatal     failed       changed   false   msg    modprobe  fatal  module nf conntrack   not found in directory  lib modules         generic n    name    nf conntrack      params        rc       state    present    stderr    modprobe  fatal  module nf conntrack   not found in directory  lib modules         generic n    stderr lines       stdout        stdout lines            ignoring        next       fatal     failed       changed   false   cmd       delta               end                     msg    non zero return code    rc       start                     stderr    the connection to the server localhost   was refused   did you specify the right host or port     stderr lines       stdout        stdout lines            ignoring    fatal     failed       changed   false   cmd       delta               end                     msg    non zero return code    rc       start                     stderr    the connection to the server localhost   was refused   did you specify the right host or port     stderr lines       stdout        stdout lines            ignoring            and the last       fatal     failed       attempts       changed   true   cmd       delta               end                     failed when result   true   msg    non zero return code    rc       start                     stderr                 utils go    the recommended value for   clusterdns   in   kubeletconfiguration   is     the provided value is    n t   port   is in use n t   port   is in use n t    etc kubernetes manifests kube apiserver yaml already exists n t    etc kubernetes manifests kube controller manager yaml already exists n t    etc kubernetes manifests kube scheduler yaml already exists n t   missing optional cgroups  blkio n t   port   is in use    stderr lines     the recommended value for   clusterdns   in   kubeletconfiguration   is     the provided value is        t   port   is in use     t   port   is in use     t    etc kubernetes manifests kube apiserver yaml already exists     t    etc kubernetes manifests kube controller manager yaml already exists     t    etc kubernetes manifests kube scheduler yaml already exists     t   missing optional cgroups  blkio     t   port   is in use     stdout      using kubernetes version        n  running pre flight checks n  pulling images required for setting up a kubernetes cluster n  this might take a minute or two  depending on the speed of your internet connection n  you can also perform this action in beforehand using  kubeadm config images pull  n  using certificatedir folder    etc kubernetes ssl   n  using existing ca certificate authority n  using existing apiserver certificate and key on disk n  using existing apiserver kubelet client certificate and key on disk n  using existing front proxy ca certificate authority n  using existing front proxy client certificate and key on disk n  external etcd mode  skipping etcd ca certificate authority generation n  external etcd mode  skipping etcd server certificate generation n  external etcd mode  skipping etcd peer certificate generation n  external etcd mode  skipping etcd healthcheck client certificate generation n  external etcd mode  skipping apiserver etcd client certificate generation n  using the existing   sa   key n  using kubeconfig folder    etc kubernetes   n  using existing kubeconfig file     etc kubernetes admin conf   n  using existing kubeconfig file     etc kubernetes kubelet conf   n  using existing kubeconfig file     etc kubernetes controller manager conf   n  using existing kubeconfig file     etc kubernetes scheduler conf   n  writing kubelet environment file with flags to file    var lib kubelet kubeadm flags env   n  writing kubelet configuration to file    var lib kubelet config yaml   n  starting the kubelet n  using manifest folder    etc kubernetes manifests   n  creating static pod manifest for   kube apiserver   n  creating static pod manifest for   kube controller manager   n  creating static pod manifest for   kube scheduler   n  waiting for the kubelet to boot up the control plane as static pods from directory    etc kubernetes manifests    this can take up to   n  initial timeout of   passed     stdout lines     using kubernetes version             running pre flight checks      pulling images required for setting up a kubernetes cluster      this might take a minute or two  depending on the speed of your internet connection      you can also perform this action in beforehand using  kubeadm config images pull       using certificatedir folder    etc kubernetes ssl        using existing ca certificate authority      using existing apiserver certificate and key on disk      using existing apiserver kubelet client certificate and key on disk      using existing front proxy ca certificate authority      using existing front proxy client certificate and key on disk      external etcd mode  skipping etcd ca certificate authority generation      external etcd mode  skipping etcd server certificate generation      external etcd mode  skipping etcd peer certificate generation      external etcd mode  skipping etcd healthcheck client certificate generation      external etcd mode  skipping apiserver etcd client certificate generation      using the existing   sa   key      using kubeconfig folder    etc kubernetes        using existing kubeconfig file     etc kubernetes admin conf        using existing kubeconfig file     etc kubernetes kubelet conf        using existing kubeconfig file     etc kubernetes controller manager conf        using existing kubeconfig file     etc kubernetes scheduler conf        writing kubelet environment file with flags to file    var lib kubelet kubeadm flags env        writing kubelet configuration to file    var lib kubelet config yaml        starting the kubelet      using manifest folder    etc kubernetes manifests        creating static pod manifest for   kube apiserver        creating static pod manifest for   kube controller manager        creating static pod manifest for   kube scheduler        waiting for the kubelet to boot up the control plane as static pods from directory    etc kubernetes manifests    this can take up to        initial timeout of   passed            and then  i also got this log below       play recap                                                                                                            localhost                    ok      changed      unreachable      failed      skipped      rescued      ignored                                  ok    changed     unreachable      failed      skipped    rescued      ignored                                  ok    changed     unreachable      failed      skipped    rescued      ignored                                  ok    changed     unreachable      failed      skipped    rescued      ignored             monday                                                                                                                                 kubernetes control plane   kubeadm   initialize first master                                                    download   download container   download image if required                                                        etcd   reload etcd                                                                                                download   download container   download image if required                                                        container engine runc   download file   validate mirrors                                                          download   download file   validate mirrors                                                                       download   download container   download image if required                                                        download   download container   download image if required                                                        download   download container   download image if required                                                        download   download container   download image if required                                                        download   download container   download image if required                                                        download   download container   download image if required                                                        etcd   gen certs   write etcd member admin and kube control plane clinet certs to other etcd nodes                download   download container   download image if required                                                        download   download container   download image if required                                                         download   download container   download image if required                                                         download   download container   download image if required                                                         etcd   configure   check if etcd cluster is healthy                                                                container engine containerd   containerd   unpack containerd archive                                               etcd   gen certs   gather etcd member admin and kube control plane clinet certs from first etcd node                  that is all of the things i got           so  please tell me the reason why i can deploy kubernetes    thanks for reading          ,0
52422,6255645591.0,IssuesEvent,2017-07-14 07:50:47,RachelDavids/RuleChecker,https://api.github.com/repos/RachelDavids/RuleChecker,closed,        Error CA2222: Microsoft.Usage ,enhancement question test case,"        Error CA2222: Microsoft.Usage : Make 'PolicyAdjustableRateCollection.Add(PolicyAdjustableRate)' non-private, mark it as final, or seal its declaring type. This method was originally defined in base class 'BaseCollection(Of PolicyAdjustableRate)'. (153)

Do we have any equivalent.",1.0,"        Error CA2222: Microsoft.Usage  -         Error CA2222: Microsoft.Usage : Make 'PolicyAdjustableRateCollection.Add(PolicyAdjustableRate)' non-private, mark it as final, or seal its declaring type. This method was originally defined in base class 'BaseCollection(Of PolicyAdjustableRate)'. (153)

Do we have any equivalent.",0,        error    microsoft usage            error    microsoft usage   make  policyadjustableratecollection add policyadjustablerate   non private  mark it as final  or seal its declaring type  this method was originally defined in base class  basecollection of policyadjustablerate           do we have any equivalent ,0
274259,29951071422.0,IssuesEvent,2023-06-23 01:10:52,jainhitesh9998/esignet,https://api.github.com/repos/jainhitesh9998/esignet,opened,spring-boot-starter-web-2.3.6.RELEASE.jar: 4 vulnerabilities (highest severity is: 9.8),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-web-2.3.6.RELEASE.jar</b></p></summary>

<p></p>
<p>Path to dependency file: /client-management-service-impl/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.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-web version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2016-1000027](https://www.mend.io/vulnerability-database/CVE-2016-1000027) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | spring-web-5.2.11.RELEASE.jar | Transitive | 2.4.0 | &#10060; |
| [CVE-2021-22118](https://www.mend.io/vulnerability-database/CVE-2021-22118) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.8 | spring-web-5.2.11.RELEASE.jar | Transitive | 2.3.11.RELEASE | &#10060; |
| [CVE-2021-22060](https://www.mend.io/vulnerability-database/CVE-2021-22060) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 4.3 | spring-web-5.2.11.RELEASE.jar | Transitive | 2.4.0 | &#10060; |
| [CVE-2021-22096](https://www.mend.io/vulnerability-database/CVE-2021-22096) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 4.3 | spring-web-5.2.11.RELEASE.jar | Transitive | 2.4.0 | &#10060; |


## Details

<details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> CVE-2016-1000027</summary>


###  Vulnerable Library - <b>spring-web-5.2.11.RELEASE.jar</b></p>

<p>Spring Web</p>
<p>Library home page: <a href=""https://github.com/spring-projects/spring-framework"">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /binding-service-impl/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-starter-web-2.3.6.RELEASE.jar (Root Library)
    - :x: **spring-web-5.2.11.RELEASE.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
Pivotal Spring Framework through 5.3.16 suffers from a potential remote code execution (RCE) issue if used for Java deserialization of untrusted data. Depending on how the library is implemented within a product, this issue may or not occur, and authentication may be required. NOTE: the vendor's position is that untrusted data is not an intended use case. The product's behavior will not be changed because some users rely on deserialization of trusted data.
 Mend Note: After conducting further research, Mend has determined that all versions of spring-web up to version 6.0.0 are vulnerable to CVE-2016-1000027.

<p>Publish Date: 2020-01-02
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-1000027>CVE-2016-1000027</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>9.8</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: 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-4wrc-f8pq-fpqp"">https://github.com/advisories/GHSA-4wrc-f8pq-fpqp</a></p>
<p>Release Date: 2020-01-02</p>
<p>Fix Resolution (org.springframework:spring-web): 5.2.23.RELEASE</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.4.0</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2021-22118</summary>


###  Vulnerable Library - <b>spring-web-5.2.11.RELEASE.jar</b></p>

<p>Spring Web</p>
<p>Library home page: <a href=""https://github.com/spring-projects/spring-framework"">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /binding-service-impl/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-starter-web-2.3.6.RELEASE.jar (Root Library)
    - :x: **spring-web-5.2.11.RELEASE.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
In Spring Framework, versions 5.2.x prior to 5.2.15 and versions 5.3.x prior to 5.3.7, a WebFlux application is vulnerable to a privilege escalation: by (re)creating the temporary storage directory, a locally authenticated malicious user can read or modify files that have been uploaded to the WebFlux application, or overwrite arbitrary files with multipart request data.

<p>Publish Date: 2021-05-27
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-22118>CVE-2021-22118</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.8</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://tanzu.vmware.com/security/cve-2021-22118"">https://tanzu.vmware.com/security/cve-2021-22118</a></p>
<p>Release Date: 2021-05-27</p>
<p>Fix Resolution (org.springframework:spring-web): 5.2.15.RELEASE</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.3.11.RELEASE</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2021-22060</summary>


###  Vulnerable Library - <b>spring-web-5.2.11.RELEASE.jar</b></p>

<p>Spring Web</p>
<p>Library home page: <a href=""https://github.com/spring-projects/spring-framework"">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /binding-service-impl/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-starter-web-2.3.6.RELEASE.jar (Root Library)
    - :x: **spring-web-5.2.11.RELEASE.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
In Spring Framework versions 5.3.0 - 5.3.13, 5.2.0 - 5.2.18, and older unsupported versions, it is possible for a user to provide malicious input to cause the insertion of additional log entries. This is a follow-up to CVE-2021-22096 that protects against additional types of input and in more places of the Spring Framework codebase.

<p>Publish Date: 2022-01-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-22060>CVE-2021-22060</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>4.3</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://spring.io/security/cve-2021-22060"">https://spring.io/security/cve-2021-22060</a></p>
<p>Release Date: 2022-01-10</p>
<p>Fix Resolution (org.springframework:spring-web): 5.2.19.RELEASE</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.4.0</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2021-22096</summary>


###  Vulnerable Library - <b>spring-web-5.2.11.RELEASE.jar</b></p>

<p>Spring Web</p>
<p>Library home page: <a href=""https://github.com/spring-projects/spring-framework"">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /binding-service-impl/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-starter-web-2.3.6.RELEASE.jar (Root Library)
    - :x: **spring-web-5.2.11.RELEASE.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
In Spring Framework versions 5.3.0 - 5.3.10, 5.2.0 - 5.2.17, and older unsupported versions, it is possible for a user to provide malicious input to cause the insertion of additional log entries.

<p>Publish Date: 2021-10-28
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-22096>CVE-2021-22096</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>4.3</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://tanzu.vmware.com/security/cve-2021-22096"">https://tanzu.vmware.com/security/cve-2021-22096</a></p>
<p>Release Date: 2021-10-28</p>
<p>Fix Resolution (org.springframework:spring-web): 5.2.18.RELEASE</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.4.0</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details>",True,"spring-boot-starter-web-2.3.6.RELEASE.jar: 4 vulnerabilities (highest severity is: 9.8) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-boot-starter-web-2.3.6.RELEASE.jar</b></p></summary>

<p></p>
<p>Path to dependency file: /client-management-service-impl/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.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-web version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2016-1000027](https://www.mend.io/vulnerability-database/CVE-2016-1000027) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | spring-web-5.2.11.RELEASE.jar | Transitive | 2.4.0 | &#10060; |
| [CVE-2021-22118](https://www.mend.io/vulnerability-database/CVE-2021-22118) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.8 | spring-web-5.2.11.RELEASE.jar | Transitive | 2.3.11.RELEASE | &#10060; |
| [CVE-2021-22060](https://www.mend.io/vulnerability-database/CVE-2021-22060) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 4.3 | spring-web-5.2.11.RELEASE.jar | Transitive | 2.4.0 | &#10060; |
| [CVE-2021-22096](https://www.mend.io/vulnerability-database/CVE-2021-22096) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 4.3 | spring-web-5.2.11.RELEASE.jar | Transitive | 2.4.0 | &#10060; |


## Details

<details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> CVE-2016-1000027</summary>


###  Vulnerable Library - <b>spring-web-5.2.11.RELEASE.jar</b></p>

<p>Spring Web</p>
<p>Library home page: <a href=""https://github.com/spring-projects/spring-framework"">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /binding-service-impl/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-starter-web-2.3.6.RELEASE.jar (Root Library)
    - :x: **spring-web-5.2.11.RELEASE.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
Pivotal Spring Framework through 5.3.16 suffers from a potential remote code execution (RCE) issue if used for Java deserialization of untrusted data. Depending on how the library is implemented within a product, this issue may or not occur, and authentication may be required. NOTE: the vendor's position is that untrusted data is not an intended use case. The product's behavior will not be changed because some users rely on deserialization of trusted data.
 Mend Note: After conducting further research, Mend has determined that all versions of spring-web up to version 6.0.0 are vulnerable to CVE-2016-1000027.

<p>Publish Date: 2020-01-02
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-1000027>CVE-2016-1000027</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>9.8</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: 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-4wrc-f8pq-fpqp"">https://github.com/advisories/GHSA-4wrc-f8pq-fpqp</a></p>
<p>Release Date: 2020-01-02</p>
<p>Fix Resolution (org.springframework:spring-web): 5.2.23.RELEASE</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.4.0</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2021-22118</summary>


###  Vulnerable Library - <b>spring-web-5.2.11.RELEASE.jar</b></p>

<p>Spring Web</p>
<p>Library home page: <a href=""https://github.com/spring-projects/spring-framework"">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /binding-service-impl/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-starter-web-2.3.6.RELEASE.jar (Root Library)
    - :x: **spring-web-5.2.11.RELEASE.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
In Spring Framework, versions 5.2.x prior to 5.2.15 and versions 5.3.x prior to 5.3.7, a WebFlux application is vulnerable to a privilege escalation: by (re)creating the temporary storage directory, a locally authenticated malicious user can read or modify files that have been uploaded to the WebFlux application, or overwrite arbitrary files with multipart request data.

<p>Publish Date: 2021-05-27
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-22118>CVE-2021-22118</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.8</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://tanzu.vmware.com/security/cve-2021-22118"">https://tanzu.vmware.com/security/cve-2021-22118</a></p>
<p>Release Date: 2021-05-27</p>
<p>Fix Resolution (org.springframework:spring-web): 5.2.15.RELEASE</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.3.11.RELEASE</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2021-22060</summary>


###  Vulnerable Library - <b>spring-web-5.2.11.RELEASE.jar</b></p>

<p>Spring Web</p>
<p>Library home page: <a href=""https://github.com/spring-projects/spring-framework"">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /binding-service-impl/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-starter-web-2.3.6.RELEASE.jar (Root Library)
    - :x: **spring-web-5.2.11.RELEASE.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
In Spring Framework versions 5.3.0 - 5.3.13, 5.2.0 - 5.2.18, and older unsupported versions, it is possible for a user to provide malicious input to cause the insertion of additional log entries. This is a follow-up to CVE-2021-22096 that protects against additional types of input and in more places of the Spring Framework codebase.

<p>Publish Date: 2022-01-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-22060>CVE-2021-22060</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>4.3</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://spring.io/security/cve-2021-22060"">https://spring.io/security/cve-2021-22060</a></p>
<p>Release Date: 2022-01-10</p>
<p>Fix Resolution (org.springframework:spring-web): 5.2.19.RELEASE</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.4.0</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2021-22096</summary>


###  Vulnerable Library - <b>spring-web-5.2.11.RELEASE.jar</b></p>

<p>Spring Web</p>
<p>Library home page: <a href=""https://github.com/spring-projects/spring-framework"">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /binding-service-impl/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.2.11.RELEASE/spring-web-5.2.11.RELEASE.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-starter-web-2.3.6.RELEASE.jar (Root Library)
    - :x: **spring-web-5.2.11.RELEASE.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
In Spring Framework versions 5.3.0 - 5.3.10, 5.2.0 - 5.2.17, and older unsupported versions, it is possible for a user to provide malicious input to cause the insertion of additional log entries.

<p>Publish Date: 2021-10-28
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-22096>CVE-2021-22096</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>4.3</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://tanzu.vmware.com/security/cve-2021-22096"">https://tanzu.vmware.com/security/cve-2021-22096</a></p>
<p>Release Date: 2021-10-28</p>
<p>Fix Resolution (org.springframework:spring-web): 5.2.18.RELEASE</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.4.0</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details>",0,spring boot starter web       release jar    vulnerabilities  highest severity is             vulnerable library    spring boot starter web       release jar         path to dependency file   client management service impl pom xml   path to vulnerable library   home wss scanner    repository org springframework spring web       release spring web       release jar  home wss scanner    repository org springframework spring web       release spring web       release jar  home wss scanner    repository org springframework spring web       release spring web       release jar  home wss scanner    repository org springframework spring web       release spring web       release jar  home wss scanner    repository org springframework spring web       release spring web       release jar           vulnerabilities    cve   severity     cvss   dependency   type   fixed in  spring boot starter web version    remediation available                                                                                             critical         spring web       release jar   transitive                            high         spring web       release jar   transitive         release                    medium         spring web       release jar   transitive                            medium         spring web       release jar   transitive                       details        cve             vulnerable library    spring web       release jar     spring web   library home page   a href     path to dependency file   binding service impl pom xml   path to vulnerable library   home wss scanner    repository org springframework spring web       release spring web       release jar  home wss scanner    repository org springframework spring web       release spring web       release jar  home wss scanner    repository org springframework spring web       release spring web       release jar  home wss scanner    repository org springframework spring web       release spring web       release jar  home wss scanner    repository org springframework spring web       release spring web       release jar     dependency hierarchy      spring boot starter web       release jar  root library         x    spring web       release jar    vulnerable library   found in base branch   master               vulnerability details        pivotal spring framework through       suffers from a potential remote code execution  rce  issue if used for java deserialization of untrusted data  depending on how the library is implemented within a product  this issue may or not occur  and authentication may be required  note  the vendor s position is that untrusted data is not an intended use case  the product s behavior will not be changed because some users rely on deserialization of trusted data   mend note  after conducting further research  mend has determined that all versions of spring web up to version       are vulnerable to cve        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  org springframework spring web         release   direct dependency fix resolution  org springframework boot spring boot starter web                   step up your open source security game with mend            cve             vulnerable library    spring web       release jar     spring web   library home page   a href     path to dependency file   binding service impl pom xml   path to vulnerable library   home wss scanner    repository org springframework spring web       release spring web       release jar  home wss scanner    repository org springframework spring web       release spring web       release jar  home wss scanner    repository org springframework spring web       release spring web       release jar  home wss scanner    repository org springframework spring web       release spring web       release jar  home wss scanner    repository org springframework spring web       release spring web       release jar     dependency hierarchy      spring boot starter web       release jar  root library         x    spring web       release jar    vulnerable library   found in base branch   master               vulnerability details        in spring framework  versions     x prior to       and versions     x prior to        a webflux application is vulnerable to a privilege escalation  by  re creating the temporary storage directory  a locally authenticated malicious user can read or modify files that have been uploaded to the webflux application  or overwrite arbitrary files with multipart request data    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  local     attack complexity  low     privileges required  low     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  high   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution  org springframework spring web         release   direct dependency fix resolution  org springframework boot spring boot starter web         release           step up your open source security game with mend            cve             vulnerable library    spring web       release jar     spring web   library home page   a href     path to dependency file   binding service impl pom xml   path to vulnerable library   home wss scanner    repository org springframework spring web       release spring web       release jar  home wss scanner    repository org springframework spring web       release spring web       release jar  home wss scanner    repository org springframework spring web       release spring web       release jar  home wss scanner    repository org springframework spring web       release spring web       release jar  home wss scanner    repository org springframework spring web       release spring web       release jar     dependency hierarchy      spring boot starter web       release jar  root library         x    spring web       release jar    vulnerable library   found in base branch   master               vulnerability details        in spring framework versions                               and older unsupported versions  it is possible for a user to provide malicious input to cause the insertion of additional log entries  this is a follow up to cve     that protects against additional types of input and in more places of the spring framework codebase    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  low     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  low     availability impact  none   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution  org springframework spring web         release   direct dependency fix resolution  org springframework boot spring boot starter web                   step up your open source security game with mend            cve             vulnerable library    spring web       release jar     spring web   library home page   a href     path to dependency file   binding service impl pom xml   path to vulnerable library   home wss scanner    repository org springframework spring web       release spring web       release jar  home wss scanner    repository org springframework spring web       release spring web       release jar  home wss scanner    repository org springframework spring web       release spring web       release jar  home wss scanner    repository org springframework spring web       release spring web       release jar  home wss scanner    repository org springframework spring web       release spring web       release jar     dependency hierarchy      spring boot starter web       release jar  root library         x    spring web       release jar    vulnerable library   found in base branch   master               vulnerability details        in spring framework versions                               and older unsupported versions  it is possible for a user to provide malicious input to cause the insertion of additional log entries    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  low     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  low     availability impact  none   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution  org springframework spring web         release   direct dependency fix resolution  org springframework boot spring boot starter web                   step up your open source security game with mend      ,0
118629,15342905984.0,IssuesEvent,2021-02-27 18:05:03,plotn/coolreader,https://api.github.com/repos/plotn/coolreader,closed,"Перенести настройки ""Опции рендеринга"" и ""Уровень совместимости DOM""",design,"Пользователь [написал](https://4pda.ru/forum/index.php?s=&showtopic=995536&view=findpost&p=104618639):
> ""Опции рендеринга"" и ""Уровень совместимости DOM"" на мой взгляд стоит убрать в ""Редкие и экспериментальные"". Понять что это такое у простого юзверя нет никаких шансов (даже невзирая на разъяснения), да и умолчальное их значение подойдёт подавляющему большинству. А то маячит, пугает, справки не даёт, дублируется в ""Шрифтах"" и ""CSS""

Дальше ещё немного обсуждения:
> хорошая мысль. Но лучше тогда в ""тонкие настройки шрифта"", дополнительно переименовав их в ""... рендеринга и шрифта""",1.0,"Перенести настройки ""Опции рендеринга"" и ""Уровень совместимости DOM"" - Пользователь [написал](https://4pda.ru/forum/index.php?s=&showtopic=995536&view=findpost&p=104618639):
> ""Опции рендеринга"" и ""Уровень совместимости DOM"" на мой взгляд стоит убрать в ""Редкие и экспериментальные"". Понять что это такое у простого юзверя нет никаких шансов (даже невзирая на разъяснения), да и умолчальное их значение подойдёт подавляющему большинству. А то маячит, пугает, справки не даёт, дублируется в ""Шрифтах"" и ""CSS""

Дальше ещё немного обсуждения:
> хорошая мысль. Но лучше тогда в ""тонкие настройки шрифта"", дополнительно переименовав их в ""... рендеринга и шрифта""",0,перенести настройки  опции рендеринга  и  уровень совместимости dom    пользователь         опции рендеринга  и  уровень совместимости dom  на мой взгляд стоит убрать в  редкие и экспериментальные   понять что это такое у простого юзверя нет никаких шансов  даже невзирая на разъяснения   да и умолчальное их значение подойдёт подавляющему большинству  а то маячит  пугает  справки не даёт  дублируется в  шрифтах  и  css     дальше ещё немного обсуждения     хорошая мысль  но лучше тогда в  тонкие настройки шрифта   дополнительно переименовав их в      рендеринга и шрифта ,0
48765,7456980382.0,IssuesEvent,2018-03-30 00:57:42,golang/go,https://api.github.com/repos/golang/go,closed,database/sql: improve documentation for DB.Close() (graceful close or not),Documentation,"The documentation doesn't make clear what DB.Close() does.

Does it close the Pool immediately even if there are still queries happening in some of the connections, or does it wait for the queries to finish and gradually closes the connections and then closes the pool?",1.0,"database/sql: improve documentation for DB.Close() (graceful close or not) - The documentation doesn't make clear what DB.Close() does.

Does it close the Pool immediately even if there are still queries happening in some of the connections, or does it wait for the queries to finish and gradually closes the connections and then closes the pool?",1,database sql  improve documentation for db close    graceful close or not    the documentation doesn t make clear what db close   does     does it close the pool immediately even if there are still queries happening in some of the connections  or does it wait for the queries to finish and gradually closes the connections and then closes the pool ,1
31246,5920374818.0,IssuesEvent,2017-05-22 20:07:23,golang/go,https://api.github.com/repos/golang/go,opened,x/tools/cmd/callgraph: usage text suggests invalid code,Documentation,"The [usage](https://github.com/golang/tools/blob/bf4b54dc687c73b6ef63de8b8abf0ad3951e3edc/cmd/callgraph/main.go#L117) text of `x/tools/cmd/callgraph` command mentions:

> e.g. Caller.Pkg.Object.Path yields the import path of the enclosing package.
> Consult the go/ssa API documentation for details.

> Examples:
>
>     callgraph -format '{{.Caller.Pkg.Object.Path}} -> {{.Callee.Pkg.Object.Path}}' \
>       $GOROOT/src/net/http/triv.go | sort | uniq

`Caller` is [`*ssa.Function`](https://godoc.org/golang.org/x/tools/go/ssa#Function). Its `Pkg` field is [`*ssa.Package`](https://godoc.org/golang.org/x/tools/go/ssa#Package). But `ssa.Package` struct doesn't contain either field or method named `Object`.

So one gets the following error:

```
$ callgraph -format '{{.Caller.Pkg.Object.Path}} -> {{.Callee.Pkg.Object.Path}}' $(go env GOROOT)/src/net/http/triv.go | sort | uniq
callgraph: template: -format:1:9: executing ""-format"" at <.Caller.Pkg.Object.P...>: can't evaluate field Object in type *ssa.Package
```

I'm guessing that instead of `Caller.Pkg.Object.Path`, it should be `Caller.Pkg.Pkg.Path`:

https://godoc.org/golang.org/x/tools/go/ssa#Package.Pkg

That works as expected in my testing.",1.0,"x/tools/cmd/callgraph: usage text suggests invalid code - The [usage](https://github.com/golang/tools/blob/bf4b54dc687c73b6ef63de8b8abf0ad3951e3edc/cmd/callgraph/main.go#L117) text of `x/tools/cmd/callgraph` command mentions:

> e.g. Caller.Pkg.Object.Path yields the import path of the enclosing package.
> Consult the go/ssa API documentation for details.

> Examples:
>
>     callgraph -format '{{.Caller.Pkg.Object.Path}} -> {{.Callee.Pkg.Object.Path}}' \
>       $GOROOT/src/net/http/triv.go | sort | uniq

`Caller` is [`*ssa.Function`](https://godoc.org/golang.org/x/tools/go/ssa#Function). Its `Pkg` field is [`*ssa.Package`](https://godoc.org/golang.org/x/tools/go/ssa#Package). But `ssa.Package` struct doesn't contain either field or method named `Object`.

So one gets the following error:

```
$ callgraph -format '{{.Caller.Pkg.Object.Path}} -> {{.Callee.Pkg.Object.Path}}' $(go env GOROOT)/src/net/http/triv.go | sort | uniq
callgraph: template: -format:1:9: executing ""-format"" at <.Caller.Pkg.Object.P...>: can't evaluate field Object in type *ssa.Package
```

I'm guessing that instead of `Caller.Pkg.Object.Path`, it should be `Caller.Pkg.Pkg.Path`:

https://godoc.org/golang.org/x/tools/go/ssa#Package.Pkg

That works as expected in my testing.",1,x tools cmd callgraph  usage text suggests invalid code   the     text of  x tools cmd callgraph  command mentions       e g  caller pkg object path yields the import path of the enclosing package     consult the go ssa api documentation for details       examples            callgraph  format     caller pkg object path         callee pkg object path                goroot src net http triv go   sort   uniq     caller  is     its  pkg  field is     but  ssa package  struct doesn t contain either field or method named  object      so one gets the following error            callgraph  format     caller pkg object path         callee pkg object path      go env goroot  src net http triv go   sort   uniq  callgraph  template   format      executing   format  at    can t evaluate field object in type  ssa package         i m guessing that instead of  caller pkg object path   it should be  caller pkg pkg path           that works as expected in my testing ,1
307753,9421826256.0,IssuesEvent,2019-04-11 07:54:52,pombase/canto,https://api.github.com/repos/pombase/canto,closed,"Hide selector, show all organisms on genotype management page (optionally)",FlyBase genotype management medium priority next,"I think @vmt25 mentioned this on Skype. FlyBase would like to show all genotypes on the genotype management page and hide the organism selector.  This would need to be an option as PHI-Canto needs the current functionality.

@jseager7 I won't attempt this until you're happy with the genotype management refactoring you're doing. This isn't an urgent issue.",1.0,"Hide selector, show all organisms on genotype management page (optionally) - I think @vmt25 mentioned this on Skype. FlyBase would like to show all genotypes on the genotype management page and hide the organism selector.  This would need to be an option as PHI-Canto needs the current functionality.

@jseager7 I won't attempt this until you're happy with the genotype management refactoring you're doing. This isn't an urgent issue.",0,hide selector  show all organisms on genotype management page  optionally    i think    mentioned this on skype  flybase would like to show all genotypes on the genotype management page and hide the organism selector   this would need to be an option as phi canto needs the current functionality        i won t attempt this until you re happy with the genotype management refactoring you re doing  this isn t an urgent issue ,0
439658,12685023196.0,IssuesEvent,2020-06-20 01:34:20,MyMICDS/MyMICDS-v2-Angular,https://api.github.com/repos/MyMICDS/MyMICDS-v2-Angular,closed,Finish Lazy-Loading of Modules,effort: easy performance priority: it can wait work length: short,"Lazy-loading components would allow only necessary parts of the application to be initially loaded. This would help with load times. [Read more here.](https://angular-2-training-book.rangle.io/handout/modules/lazy-loading-module.html)

This would require the project to be separated into different ng modules, which is a good thing as it would increase organization.",1.0,"Finish Lazy-Loading of Modules - Lazy-loading components would allow only necessary parts of the application to be initially loaded. This would help with load times. [Read more here.](https://angular-2-training-book.rangle.io/handout/modules/lazy-loading-module.html)

This would require the project to be separated into different ng modules, which is a good thing as it would increase organization.",0,finish lazy loading of modules   lazy loading components would allow only necessary parts of the application to be initially loaded  this would help with load times         this would require the project to be separated into different ng modules  which is a good thing as it would increase organization ,0
599062,18264992440.0,IssuesEvent,2021-10-04 07:20:49,containrrr/watchtower,https://api.github.com/repos/containrrr/watchtower,opened,"Watchtower cannot pull images anymore ""401 Unauthorized""",Type: Bug Priority: Medium Status: Available,"Running Watchtower on ARM 64 Raspbian, has been working ever since and stopped now with the following error message:

```
Could not do a head request for ""sha256:e1688bbea26473c306345275b9b1f2ccad6c9293af9298d28098c629a77fcbf6"", falling back to regular pull.
Reason: registry responded to head request with ""401 Unauthorized"", auth: ""Bearer realm=\""https://auth.docker.io/token\"",service=\""registry.docker.io\"",scope=\""repository:library/sha256:pull\"",error=\""insufficient_scope\""""
Unable to update container ""/watchtower"": Error response from daemon: pull access denied for sha256, repository does not exist or may require 'docker login': denied: requested access to the resource is denied. Proceeding to next.
```

nothing was changed in the config and i do run watchtower every 5 days, so pull request shouldn't be an issue

anyone having or had that issue and knows what to do?",1.0,"Watchtower cannot pull images anymore ""401 Unauthorized"" - Running Watchtower on ARM 64 Raspbian, has been working ever since and stopped now with the following error message:

```
Could not do a head request for ""sha256:e1688bbea26473c306345275b9b1f2ccad6c9293af9298d28098c629a77fcbf6"", falling back to regular pull.
Reason: registry responded to head request with ""401 Unauthorized"", auth: ""Bearer realm=\""https://auth.docker.io/token\"",service=\""registry.docker.io\"",scope=\""repository:library/sha256:pull\"",error=\""insufficient_scope\""""
Unable to update container ""/watchtower"": Error response from daemon: pull access denied for sha256, repository does not exist or may require 'docker login': denied: requested access to the resource is denied. Proceeding to next.
```

nothing was changed in the config and i do run watchtower every 5 days, so pull request shouldn't be an issue

anyone having or had that issue and knows what to do?",0,watchtower cannot pull images anymore    unauthorized    running watchtower on arm   raspbian  has been working ever since and stopped now with the following error message          could not do a head request for        falling back to regular pull   reason  registry responded to head request with    unauthorized   auth   bearer realm      unable to update container   watchtower   error response from daemon  pull access denied for    repository does not exist or may require  docker login   denied  requested access to the resource is denied  proceeding to next          nothing was changed in the config and i do run watchtower every   days  so pull request shouldn t be an issue    anyone having or had that issue and knows what to do ,0
467518,13450011682.0,IssuesEvent,2020-09-08 17:49:29,InstituteforDiseaseModeling/covasim,https://api.github.com/repos/InstituteforDiseaseModeling/covasim,closed,[UI 2.0] Automatic calibration,CovasimUI approved highpriority ui_wishlist,"For different country data to be useful to users, the model must be at least crudely calibrated to that setting, which the user can then refine. When the user loads a region, it should load not just the data but the parameter values for that region. These calibrations should be performed by us offline, to the level of fidelity we have time for, and saved as a library of parameter values in the webapp folder.

- [ ] Perform manual calibration to ~5 locations, determining which parameters will need to be varied (e.g. beta, initial infected population, change_beta date and magnitude)
- [ ] Choose calibration algorithm
- [ ] Apply and test calibration algorithm to match deaths data
- [ ] Once deaths are calibrated, calibrate optimal `symp_prob` value in `cv.test_prob()` to match diagnoses
- [ ] Verify calibrations for ~20 locations (~5 US states, ~5 high-income countries, ~10 low-income countries)
- [ ] Cache calibrated parameter values
- [ ] Load values in webapp",1.0,"[UI 2.0] Automatic calibration - For different country data to be useful to users, the model must be at least crudely calibrated to that setting, which the user can then refine. When the user loads a region, it should load not just the data but the parameter values for that region. These calibrations should be performed by us offline, to the level of fidelity we have time for, and saved as a library of parameter values in the webapp folder.

- [ ] Perform manual calibration to ~5 locations, determining which parameters will need to be varied (e.g. beta, initial infected population, change_beta date and magnitude)
- [ ] Choose calibration algorithm
- [ ] Apply and test calibration algorithm to match deaths data
- [ ] Once deaths are calibrated, calibrate optimal `symp_prob` value in `cv.test_prob()` to match diagnoses
- [ ] Verify calibrations for ~20 locations (~5 US states, ~5 high-income countries, ~10 low-income countries)
- [ ] Cache calibrated parameter values
- [ ] Load values in webapp",0,  automatic calibration   for different country data to be useful to users  the model must be at least crudely calibrated to that setting  which the user can then refine  when the user loads a region  it should load not just the data but the parameter values for that region  these calibrations should be performed by us offline  to the level of fidelity we have time for  and saved as a library of parameter values in the webapp folder         perform manual calibration to    locations  determining which parameters will need to be varied  e g  beta  initial infected population  change beta date and magnitude       choose calibration algorithm      apply and test calibration algorithm to match deaths data      once deaths are calibrated  calibrate optimal  symp prob  value in  cv test prob    to match diagnoses      verify calibrations for    locations     us states     high income countries     low income countries       cache calibrated parameter values      load values in webapp,0
40523,6827764966.0,IssuesEvent,2017-11-08 18:06:24,golang/go,https://api.github.com/repos/golang/go,closed,encoding/xml: Marshal fails to handle conflicting tags,Documentation NeedsFix,"Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
tip and 1.7.4
(this is not a regression)

### What operating system and processor architecture are you using (`go env`)?
linux/amd64

### What did you do?
https://play.golang.org/p/w6DV-tXCwT

### What did you expect to see?
```<A><name2></name2></A>```

### What did you see instead?
```xml: name ""name1"" in tag of main.A.B conflicts with name ""name2"" in main.B.XMLName```

https://golang.org/pkg/encoding/xml/#Marshal lists the order of preference for the name of an element. 

The example works if you remove the tag name1 or name2. This means the order of preferences (name1,name3) and (name2,name3) are working, but (name1,name2) is not.
",1.0,"encoding/xml: Marshal fails to handle conflicting tags - Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
tip and 1.7.4
(this is not a regression)

### What operating system and processor architecture are you using (`go env`)?
linux/amd64

### What did you do?
https://play.golang.org/p/w6DV-tXCwT

### What did you expect to see?
```<A><name2></name2></A>```

### What did you see instead?
```xml: name ""name1"" in tag of main.A.B conflicts with name ""name2"" in main.B.XMLName```

https://golang.org/pkg/encoding/xml/#Marshal lists the order of preference for the name of an element. 

The example works if you remove the tag name1 or name2. This means the order of preferences (name1,name3) and (name2,name3) are working, but (name1,name2) is not.
",1,encoding xml  marshal fails to handle conflicting tags   please answer these questions before submitting your issue  thanks         what version of go are you using   go version     tip and         this is not a regression         what operating system and processor architecture are you using   go env     linux          what did you do            what did you expect to see                     what did you see instead      xml  name     in tag of main a b conflicts with name     in main b xmlname         lists the order of preference for the name of an element      the example works if you remove the tag   or    this means the order of preferences       and       are working  but       is not   ,1
52348,7759306146.0,IssuesEvent,2018-05-31 22:49:05,golang/go,https://api.github.com/repos/golang/go,closed,doc: archive/zip: *Writer.Close wording,Documentation NeedsInvestigation,"The documentation for *Writer.Close states:

> Close finishes writing the zip file by writing the central directory. It does not (and cannot) close the underlying writer.

The ""(and cannot)"" seems unnecessary, and differs from the docs of other Close methods in the standard library.",1.0,"doc: archive/zip: *Writer.Close wording - The documentation for *Writer.Close states:

> Close finishes writing the zip file by writing the central directory. It does not (and cannot) close the underlying writer.

The ""(and cannot)"" seems unnecessary, and differs from the docs of other Close methods in the standard library.",1,doc  archive zip   writer close wording   the documentation for  writer close states       close finishes writing the zip file by writing the central directory  it does not  and cannot  close the underlying writer     the   and cannot   seems unnecessary  and differs from the docs of other close methods in the standard library ,1
33404,6201010290.0,IssuesEvent,2017-07-06 03:53:22,golang/go,https://api.github.com/repos/golang/go,closed,cmd/internal/dwarf: Can't run executables w/ debug info on FreeBSD 9.1,Documentation NeedsInvestigation OS-FreeBSD,"Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
master from https://go.googlesource.com/go
+
go version go1.4-bootstrap-20170531 freebsd/amd64

### What operating system and processor architecture are you using (`go env`)?
GOARCH=""amd64""
GOBIN=""""
GOCHAR=""6""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""freebsd""
GOOS=""freebsd""
GOPATH=""""
GORACE=""""
GOROOT=""/usr/home/xxx/go1.4""
GOTOOLDIR=""/usr/home/xxx/go1.4/pkg/tool/freebsd_amd64""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0""
CXX=""g++""
CGO_ENABLED=""1""


### What did you do?
Try to install go from source.

### What did you expect to see?
Successful installation 

### What did you see instead?

xxx@xxx/home/xxx/go/src>./all.bash
##### Building Go bootstrap tool.
cmd/dist

##### Building Go toolchain using /home/xxx/go1.4.
bootstrap/cmd/internal/dwarf
bootstrap/cmd/internal/objabi
bootstrap/cmd/internal/src
bootstrap/cmd/internal/sys
bootstrap/cmd/asm/internal/flags
bootstrap/cmd/internal/bio
bootstrap/math/bits
bootstrap/cmd/internal/gcprog
bootstrap/cmd/compile/internal/syntax
bootstrap/debug/pe
bootstrap/math/big
bootstrap/cmd/internal/obj
bootstrap/cmd/asm/internal/lex
bootstrap/cmd/link/internal/ld
bootstrap/cmd/internal/obj/arm
bootstrap/cmd/internal/obj/arm64
bootstrap/cmd/internal/obj/mips
bootstrap/cmd/internal/obj/ppc64
bootstrap/cmd/internal/obj/s390x
bootstrap/cmd/internal/obj/x86
bootstrap/cmd/compile/internal/types
bootstrap/cmd/asm/internal/arch
bootstrap/cmd/compile/internal/ssa
bootstrap/cmd/asm/internal/asm
bootstrap/cmd/asm
bootstrap/cmd/link/internal/amd64
bootstrap/cmd/link/internal/arm
bootstrap/cmd/link/internal/arm64
bootstrap/cmd/link/internal/mips
bootstrap/cmd/link/internal/mips64
bootstrap/cmd/link/internal/ppc64
bootstrap/cmd/link/internal/s390x
bootstrap/cmd/link/internal/x86
bootstrap/cmd/link
bootstrap/cmd/compile/internal/gc
bootstrap/cmd/compile/internal/amd64
bootstrap/cmd/compile/internal/arm
bootstrap/cmd/compile/internal/arm64
bootstrap/cmd/compile/internal/mips
bootstrap/cmd/compile/internal/mips64
bootstrap/cmd/compile/internal/ppc64
bootstrap/cmd/compile/internal/s390x
bootstrap/cmd/compile/internal/x86
bootstrap/cmd/compile

##### Building go_bootstrap for host, freebsd/amd64.
runtime/internal/sys
runtime/internal/atomic
runtime
encoding
errors
internal/cpu
internal/race
internal/syscall/windows/sysdll
math/bits
sync/atomic
unicode
unicode/utf16
unicode/utf8
math
sync
internal/singleflight
io
syscall
cmd/go/internal/web
hash
bytes
strings
hash/adler32
bufio
strconv
path
internal/syscall/windows
internal/syscall/windows/registry
time
reflect
encoding/base64
crypto
crypto/sha1
internal/poll
os
os/signal
sort
encoding/binary
fmt
container/heap
regexp/syntax
path/filepath
io/ioutil
context
flag
go/token
log
cmd/go/internal/str
net/url
text/template/parse
compress/flate
encoding/xml
encoding/json
debug/dwarf
os/exec
go/scanner
regexp
cmd/internal/objabi
go/ast
compress/zlib
text/template
debug/macho
debug/elf
go/parser
go/doc
go/build
cmd/go/internal/cfg
cmd/go/internal/base
cmd/go/internal/buildid
cmd/go/internal/cmdflag
cmd/go/internal/doc
cmd/go/internal/help
cmd/go/internal/load
cmd/go/internal/tool
cmd/go/internal/version
cmd/go/internal/fix
cmd/go/internal/fmtcmd
cmd/go/internal/work
cmd/go/internal/clean
cmd/go/internal/envcmd
cmd/go/internal/generate
cmd/go/internal/get
cmd/go/internal/list
cmd/go/internal/run
cmd/go/internal/test
cmd/go/internal/vet
cmd/go/internal/bug
cmd/go

##### Building packages and commands for freebsd/amd64.
runtime/internal/sys
runtime/internal/atomic
runtime
errors
internal/cpu
internal/race
unicode
sync/atomic
unicode/utf8
container/list
math/bits
container/ring
crypto/subtle
math
crypto/internal/cipherhw
internal/nettrace
sync
vendor/golang_org/x/crypto/poly1305
vendor/golang_org/x/crypto/curve25519
encoding
unicode/utf16
image/color
internal/syscall/windows
internal/syscall/windows/registry
internal/syscall/windows/sysdll
plugin
runtime/race
vendor/golang_org/x/text/secure
vendor/golang_org/x/text/unicode
cmd/compile/internal/test
cmd/vet/internal/whitelist
image/color/palette
io
syscall
internal/singleflight
bytes
strings
hash
crypto/cipher
runtime/trace
hash/adler32
hash/crc32
crypto/hmac
strconv
math/rand
hash/crc64
hash/fnv
math/cmplx
path
html
bufio
text/tabwriter
vendor/golang_org/x/text/transform
reflect
cmd/internal/src
encoding/base64
crypto/rc4
crypto
crypto/aes
encoding/ascii85
encoding/base32
crypto/sha512
crypto/md5
crypto/sha1
crypto/sha256
image
time
image/internal/imageutil
image/draw
image/jpeg
internal/poll
os
sort
encoding/binary
regexp/syntax
compress/bzip2
encoding/pem
container/heap
fmt
path/filepath
vendor/golang_org/x/net/route
os/signal
runtime/debug
cmd/internal/sys
crypto/des
vendor/golang_org/x/crypto/chacha20poly1305/internal/chacha20
io/ioutil
vendor/golang_org/x/crypto/chacha20poly1305
regexp
flag
log
debug/dwarf
compress/flate
debug/gosym
debug/plan9obj
cmd/vendor/golang.org/x/arch/arm/armasm
cmd/vendor/golang.org/x/arch/ppc64/ppc64asm
cmd/vendor/golang.org/x/arch/x86/x86asm
archive/tar
cmd/internal/objabi
cmd/internal/goobj
compress/lzw
compress/zlib
archive/zip
compress/gzip
context
math/big
encoding/hex
go/token
encoding/csv
os/exec
go/scanner
database/sql/driver
encoding/gob
debug/elf
debug/macho
debug/pe
go/ast
database/sql
encoding/json
encoding/xml
vendor/golang_org/x/net/http2/hpack
cmd/internal/objfile
go/parser
crypto/dsa
crypto/elliptic
encoding/asn1
crypto/rand
go/printer
crypto/rsa
vendor/golang_org/x/text/unicode/bidi
cmd/addr2line
vendor/golang_org/x/text/unicode/norm
crypto/ecdsa
crypto/x509/pkix
net/url
mime
mime/quotedprintable
net/http/internal
text/template/parse
vendor/golang_org/x/text/secure/bidirule
go/constant
text/scanner
image/gif
image/png
index/suffixarray
cmd/cgo
go/format
testing
go/types
internal/trace
runtime/pprof
text/template
vendor/golang_org/x/net/idna
net/internal/socktest
runtime/pprof/internal/profile
testing/internal/testdeps
testing/iotest
testing/quick
internal/testenv
cmd/internal/dwarf
cmd/asm/internal/flags
cmd/internal/bio
cmd/asm/internal/lex
cmd/internal/obj
cmd/compile/internal/syntax
cmd/internal/gcprog
cmd/internal/browser
cmd/dist
cmd/fix
go/doc
html/template
cmd/internal/obj/arm
go/build
cmd/internal/obj/arm64
cmd/internal/obj/mips
cmd/internal/obj/ppc64
cmd/internal/obj/s390x
cmd/internal/obj/x86
cmd/compile/internal/types
runtime/cgo
go/internal/gccgoimporter
go/internal/gcimporter
go/internal/srcimporter
cmd/api
cmd/cover
cmd/doc
cmd/go/internal/cfg
cmd/go/internal/str
go/importer
cmd/go/internal/base
cmd/go/internal/buildid
cmd/gofmt
cmd/go/internal/doc
cmd/go/internal/load
cmd/go/internal/help
cmd/go/internal/cmdflag
cmd/go/internal/tool
cmd/go/internal/version
cmd/link/internal/ld
cmd/asm/internal/arch
cmd/asm/internal/asm
cmd/compile/internal/ssa
cmd/go/internal/work
net
os/user
cmd/go/internal/fix
cmd/go/internal/fmtcmd
cmd/nm
cmd/objdump
cmd/asm
cmd/pack
cmd/vendor/github.com/google/pprof/internal/elfexec
cmd/vendor/github.com/google/pprof/profile
cmd/vendor/github.com/ianlancetaylor/demangle
cmd/vendor/github.com/google/pprof/third_party/svg
cmd/vendor/github.com/google/pprof/internal/proftest
cmd/vet/internal/cfg
cmd/vet
cmd/go/internal/envcmd
cmd/go/internal/clean
cmd/go/internal/generate
cmd/go/internal/list
cmd/go/internal/run
cmd/go/internal/test
cmd/go/internal/vet
cmd/vendor/github.com/google/pprof/internal/plugin
cmd/vendor/github.com/google/pprof/internal/measurement
cmd/vendor/github.com/google/pprof/internal/symbolz
cmd/vendor/github.com/google/pprof/internal/graph
cmd/vendor/github.com/google/pprof/internal/binutils
cmd/vendor/github.com/google/pprof/internal/report
vendor/golang_org/x/net/lex/httplex
vendor/golang_org/x/net/proxy
crypto/x509
net/textproto
log/syslog
vendor/golang_org/x/net/nettest
mime/multipart
net/mail
crypto/tls
cmd/link/internal/amd64
cmd/link/internal/arm
cmd/link/internal/arm64
cmd/link/internal/mips
cmd/link/internal/mips64
cmd/link/internal/ppc64
cmd/link/internal/s390x
cmd/link/internal/x86
cmd/link
net/http/httptrace
net/smtp
net/http
net/http/cgi
net/http/cookiejar
expvar
net/http/httptest
net/http/httputil
net/http/pprof
net/rpc
cmd/go/internal/web
cmd/vendor/github.com/google/pprof/internal/symbolizer
cmd/trace
net/rpc/jsonrpc
net/http/fcgi
cmd/go/internal/bug
cmd/go/internal/get
cmd/vendor/github.com/google/pprof/internal/driver
cmd/go
cmd/vendor/github.com/google/pprof/driver
cmd/pprof
cmd/compile/internal/gc
cmd/compile/internal/arm
cmd/compile/internal/mips
cmd/compile/internal/arm64
cmd/compile/internal/amd64
cmd/compile/internal/mips64
cmd/compile/internal/ppc64
cmd/compile/internal/s390x
cmd/compile/internal/x86
cmd/compile

run.bash: line 8: /home/xxx/go/bin/go: cannot execute binary file: Exec format error
run.bash: line 47: /home/xxx/go/bin/go: cannot execute binary file: Exec format error
run.bash: line 47: /home/xxx/go/bin/go: No error: 0
xxx@xxx/home/xxx/go/src>

",1.0,"cmd/internal/dwarf: Can't run executables w/ debug info on FreeBSD 9.1 - Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
master from https://go.googlesource.com/go
+
go version go1.4-bootstrap-20170531 freebsd/amd64

### What operating system and processor architecture are you using (`go env`)?
GOARCH=""amd64""
GOBIN=""""
GOCHAR=""6""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""freebsd""
GOOS=""freebsd""
GOPATH=""""
GORACE=""""
GOROOT=""/usr/home/xxx/go1.4""
GOTOOLDIR=""/usr/home/xxx/go1.4/pkg/tool/freebsd_amd64""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0""
CXX=""g++""
CGO_ENABLED=""1""


### What did you do?
Try to install go from source.

### What did you expect to see?
Successful installation 

### What did you see instead?

xxx@xxx/home/xxx/go/src>./all.bash
##### Building Go bootstrap tool.
cmd/dist

##### Building Go toolchain using /home/xxx/go1.4.
bootstrap/cmd/internal/dwarf
bootstrap/cmd/internal/objabi
bootstrap/cmd/internal/src
bootstrap/cmd/internal/sys
bootstrap/cmd/asm/internal/flags
bootstrap/cmd/internal/bio
bootstrap/math/bits
bootstrap/cmd/internal/gcprog
bootstrap/cmd/compile/internal/syntax
bootstrap/debug/pe
bootstrap/math/big
bootstrap/cmd/internal/obj
bootstrap/cmd/asm/internal/lex
bootstrap/cmd/link/internal/ld
bootstrap/cmd/internal/obj/arm
bootstrap/cmd/internal/obj/arm64
bootstrap/cmd/internal/obj/mips
bootstrap/cmd/internal/obj/ppc64
bootstrap/cmd/internal/obj/s390x
bootstrap/cmd/internal/obj/x86
bootstrap/cmd/compile/internal/types
bootstrap/cmd/asm/internal/arch
bootstrap/cmd/compile/internal/ssa
bootstrap/cmd/asm/internal/asm
bootstrap/cmd/asm
bootstrap/cmd/link/internal/amd64
bootstrap/cmd/link/internal/arm
bootstrap/cmd/link/internal/arm64
bootstrap/cmd/link/internal/mips
bootstrap/cmd/link/internal/mips64
bootstrap/cmd/link/internal/ppc64
bootstrap/cmd/link/internal/s390x
bootstrap/cmd/link/internal/x86
bootstrap/cmd/link
bootstrap/cmd/compile/internal/gc
bootstrap/cmd/compile/internal/amd64
bootstrap/cmd/compile/internal/arm
bootstrap/cmd/compile/internal/arm64
bootstrap/cmd/compile/internal/mips
bootstrap/cmd/compile/internal/mips64
bootstrap/cmd/compile/internal/ppc64
bootstrap/cmd/compile/internal/s390x
bootstrap/cmd/compile/internal/x86
bootstrap/cmd/compile

##### Building go_bootstrap for host, freebsd/amd64.
runtime/internal/sys
runtime/internal/atomic
runtime
encoding
errors
internal/cpu
internal/race
internal/syscall/windows/sysdll
math/bits
sync/atomic
unicode
unicode/utf16
unicode/utf8
math
sync
internal/singleflight
io
syscall
cmd/go/internal/web
hash
bytes
strings
hash/adler32
bufio
strconv
path
internal/syscall/windows
internal/syscall/windows/registry
time
reflect
encoding/base64
crypto
crypto/sha1
internal/poll
os
os/signal
sort
encoding/binary
fmt
container/heap
regexp/syntax
path/filepath
io/ioutil
context
flag
go/token
log
cmd/go/internal/str
net/url
text/template/parse
compress/flate
encoding/xml
encoding/json
debug/dwarf
os/exec
go/scanner
regexp
cmd/internal/objabi
go/ast
compress/zlib
text/template
debug/macho
debug/elf
go/parser
go/doc
go/build
cmd/go/internal/cfg
cmd/go/internal/base
cmd/go/internal/buildid
cmd/go/internal/cmdflag
cmd/go/internal/doc
cmd/go/internal/help
cmd/go/internal/load
cmd/go/internal/tool
cmd/go/internal/version
cmd/go/internal/fix
cmd/go/internal/fmtcmd
cmd/go/internal/work
cmd/go/internal/clean
cmd/go/internal/envcmd
cmd/go/internal/generate
cmd/go/internal/get
cmd/go/internal/list
cmd/go/internal/run
cmd/go/internal/test
cmd/go/internal/vet
cmd/go/internal/bug
cmd/go

##### Building packages and commands for freebsd/amd64.
runtime/internal/sys
runtime/internal/atomic
runtime
errors
internal/cpu
internal/race
unicode
sync/atomic
unicode/utf8
container/list
math/bits
container/ring
crypto/subtle
math
crypto/internal/cipherhw
internal/nettrace
sync
vendor/golang_org/x/crypto/poly1305
vendor/golang_org/x/crypto/curve25519
encoding
unicode/utf16
image/color
internal/syscall/windows
internal/syscall/windows/registry
internal/syscall/windows/sysdll
plugin
runtime/race
vendor/golang_org/x/text/secure
vendor/golang_org/x/text/unicode
cmd/compile/internal/test
cmd/vet/internal/whitelist
image/color/palette
io
syscall
internal/singleflight
bytes
strings
hash
crypto/cipher
runtime/trace
hash/adler32
hash/crc32
crypto/hmac
strconv
math/rand
hash/crc64
hash/fnv
math/cmplx
path
html
bufio
text/tabwriter
vendor/golang_org/x/text/transform
reflect
cmd/internal/src
encoding/base64
crypto/rc4
crypto
crypto/aes
encoding/ascii85
encoding/base32
crypto/sha512
crypto/md5
crypto/sha1
crypto/sha256
image
time
image/internal/imageutil
image/draw
image/jpeg
internal/poll
os
sort
encoding/binary
regexp/syntax
compress/bzip2
encoding/pem
container/heap
fmt
path/filepath
vendor/golang_org/x/net/route
os/signal
runtime/debug
cmd/internal/sys
crypto/des
vendor/golang_org/x/crypto/chacha20poly1305/internal/chacha20
io/ioutil
vendor/golang_org/x/crypto/chacha20poly1305
regexp
flag
log
debug/dwarf
compress/flate
debug/gosym
debug/plan9obj
cmd/vendor/golang.org/x/arch/arm/armasm
cmd/vendor/golang.org/x/arch/ppc64/ppc64asm
cmd/vendor/golang.org/x/arch/x86/x86asm
archive/tar
cmd/internal/objabi
cmd/internal/goobj
compress/lzw
compress/zlib
archive/zip
compress/gzip
context
math/big
encoding/hex
go/token
encoding/csv
os/exec
go/scanner
database/sql/driver
encoding/gob
debug/elf
debug/macho
debug/pe
go/ast
database/sql
encoding/json
encoding/xml
vendor/golang_org/x/net/http2/hpack
cmd/internal/objfile
go/parser
crypto/dsa
crypto/elliptic
encoding/asn1
crypto/rand
go/printer
crypto/rsa
vendor/golang_org/x/text/unicode/bidi
cmd/addr2line
vendor/golang_org/x/text/unicode/norm
crypto/ecdsa
crypto/x509/pkix
net/url
mime
mime/quotedprintable
net/http/internal
text/template/parse
vendor/golang_org/x/text/secure/bidirule
go/constant
text/scanner
image/gif
image/png
index/suffixarray
cmd/cgo
go/format
testing
go/types
internal/trace
runtime/pprof
text/template
vendor/golang_org/x/net/idna
net/internal/socktest
runtime/pprof/internal/profile
testing/internal/testdeps
testing/iotest
testing/quick
internal/testenv
cmd/internal/dwarf
cmd/asm/internal/flags
cmd/internal/bio
cmd/asm/internal/lex
cmd/internal/obj
cmd/compile/internal/syntax
cmd/internal/gcprog
cmd/internal/browser
cmd/dist
cmd/fix
go/doc
html/template
cmd/internal/obj/arm
go/build
cmd/internal/obj/arm64
cmd/internal/obj/mips
cmd/internal/obj/ppc64
cmd/internal/obj/s390x
cmd/internal/obj/x86
cmd/compile/internal/types
runtime/cgo
go/internal/gccgoimporter
go/internal/gcimporter
go/internal/srcimporter
cmd/api
cmd/cover
cmd/doc
cmd/go/internal/cfg
cmd/go/internal/str
go/importer
cmd/go/internal/base
cmd/go/internal/buildid
cmd/gofmt
cmd/go/internal/doc
cmd/go/internal/load
cmd/go/internal/help
cmd/go/internal/cmdflag
cmd/go/internal/tool
cmd/go/internal/version
cmd/link/internal/ld
cmd/asm/internal/arch
cmd/asm/internal/asm
cmd/compile/internal/ssa
cmd/go/internal/work
net
os/user
cmd/go/internal/fix
cmd/go/internal/fmtcmd
cmd/nm
cmd/objdump
cmd/asm
cmd/pack
cmd/vendor/github.com/google/pprof/internal/elfexec
cmd/vendor/github.com/google/pprof/profile
cmd/vendor/github.com/ianlancetaylor/demangle
cmd/vendor/github.com/google/pprof/third_party/svg
cmd/vendor/github.com/google/pprof/internal/proftest
cmd/vet/internal/cfg
cmd/vet
cmd/go/internal/envcmd
cmd/go/internal/clean
cmd/go/internal/generate
cmd/go/internal/list
cmd/go/internal/run
cmd/go/internal/test
cmd/go/internal/vet
cmd/vendor/github.com/google/pprof/internal/plugin
cmd/vendor/github.com/google/pprof/internal/measurement
cmd/vendor/github.com/google/pprof/internal/symbolz
cmd/vendor/github.com/google/pprof/internal/graph
cmd/vendor/github.com/google/pprof/internal/binutils
cmd/vendor/github.com/google/pprof/internal/report
vendor/golang_org/x/net/lex/httplex
vendor/golang_org/x/net/proxy
crypto/x509
net/textproto
log/syslog
vendor/golang_org/x/net/nettest
mime/multipart
net/mail
crypto/tls
cmd/link/internal/amd64
cmd/link/internal/arm
cmd/link/internal/arm64
cmd/link/internal/mips
cmd/link/internal/mips64
cmd/link/internal/ppc64
cmd/link/internal/s390x
cmd/link/internal/x86
cmd/link
net/http/httptrace
net/smtp
net/http
net/http/cgi
net/http/cookiejar
expvar
net/http/httptest
net/http/httputil
net/http/pprof
net/rpc
cmd/go/internal/web
cmd/vendor/github.com/google/pprof/internal/symbolizer
cmd/trace
net/rpc/jsonrpc
net/http/fcgi
cmd/go/internal/bug
cmd/go/internal/get
cmd/vendor/github.com/google/pprof/internal/driver
cmd/go
cmd/vendor/github.com/google/pprof/driver
cmd/pprof
cmd/compile/internal/gc
cmd/compile/internal/arm
cmd/compile/internal/mips
cmd/compile/internal/arm64
cmd/compile/internal/amd64
cmd/compile/internal/mips64
cmd/compile/internal/ppc64
cmd/compile/internal/s390x
cmd/compile/internal/x86
cmd/compile

run.bash: line 8: /home/xxx/go/bin/go: cannot execute binary file: Exec format error
run.bash: line 47: /home/xxx/go/bin/go: cannot execute binary file: Exec format error
run.bash: line 47: /home/xxx/go/bin/go: No error: 0
xxx@xxx/home/xxx/go/src>

",1,cmd internal dwarf  can t run executables w  debug info on freebsd       please answer these questions before submitting your issue  thanks         what version of go are you using   go version     master from       go version     bootstrap   freebsd          what operating system and processor architecture are you using   go env     goarch      gobin     gochar      goexe     gohostarch      gohostos  freebsd   goos  freebsd   gopath     gorace     goroot   usr home xxx       gotooldir   usr home xxx     pkg tool freebsd     cc  gcc   gogccflags   fpic     pthread  fmessage length     cxx  g     cgo enabled              what did you do   try to install go from source         what did you expect to see   successful installation         what did you see instead     xxx xxx home xxx go src   all bash        building go bootstrap tool   cmd dist          building go toolchain using  home xxx       bootstrap cmd internal dwarf  bootstrap cmd internal objabi  bootstrap cmd internal src  bootstrap cmd internal sys  bootstrap cmd asm internal flags  bootstrap cmd internal bio  bootstrap math bits  bootstrap cmd internal gcprog  bootstrap cmd compile internal syntax  bootstrap debug pe  bootstrap math big  bootstrap cmd internal obj  bootstrap cmd asm internal lex  bootstrap cmd link internal ld  bootstrap cmd internal obj arm  bootstrap cmd internal obj    bootstrap cmd internal obj mips  bootstrap cmd internal obj    bootstrap cmd internal obj    bootstrap cmd internal obj    bootstrap cmd compile internal types  bootstrap cmd asm internal arch  bootstrap cmd compile internal ssa  bootstrap cmd asm internal asm  bootstrap cmd asm  bootstrap cmd link internal    bootstrap cmd link internal arm  bootstrap cmd link internal    bootstrap cmd link internal mips  bootstrap cmd link internal    bootstrap cmd link internal    bootstrap cmd link internal    bootstrap cmd link internal    bootstrap cmd link  bootstrap cmd compile internal gc  bootstrap cmd compile internal    bootstrap cmd compile internal arm  bootstrap cmd compile internal    bootstrap cmd compile internal mips  bootstrap cmd compile internal    bootstrap cmd compile internal    bootstrap cmd compile internal    bootstrap cmd compile internal    bootstrap cmd compile          building go bootstrap for host  freebsd     runtime internal sys  runtime internal atomic  runtime  encoding  errors  internal cpu  internal race  internal syscall windows sysdll  math bits  sync atomic  unicode  unicode    unicode    math  sync  internal singleflight  io  syscall  cmd go internal web  hash  bytes  strings  hash    bufio  strconv  path  internal syscall windows  internal syscall windows registry  time  reflect  encoding    crypto  crypto    internal poll  os  os signal  sort  encoding binary  fmt  container heap  regexp syntax  path filepath  io ioutil  context  flag  go token  log  cmd go internal str  net url  text template parse  compress flate  encoding xml  encoding json  debug dwarf  os exec  go scanner  regexp  cmd internal objabi  go ast  compress zlib  text template  debug macho  debug elf  go parser  go doc  go build  cmd go internal cfg  cmd go internal base  cmd go internal buildid  cmd go internal cmdflag  cmd go internal doc  cmd go internal help  cmd go internal load  cmd go internal tool  cmd go internal version  cmd go internal fix  cmd go internal fmtcmd  cmd go internal work  cmd go internal clean  cmd go internal envcmd  cmd go internal generate  cmd go internal get  cmd go internal list  cmd go internal run  cmd go internal test  cmd go internal vet  cmd go internal bug  cmd go          building packages and commands for freebsd     runtime internal sys  runtime internal atomic  runtime  errors  internal cpu  internal race  unicode  sync atomic  unicode    container list  math bits  container ring  crypto subtle  math  crypto internal cipherhw  internal nettrace  sync  vendor golang org x crypto    vendor golang org x crypto    encoding  unicode    image color  internal syscall windows  internal syscall windows registry  internal syscall windows sysdll  plugin  runtime race  vendor golang org x text secure  vendor golang org x text unicode  cmd compile internal test  cmd vet internal whitelist  image color palette  io  syscall  internal singleflight  bytes  strings  hash  crypto cipher  runtime trace  hash    hash    crypto hmac  strconv  math rand  hash    hash fnv  math cmplx  path  html  bufio  text tabwriter  vendor golang org x text transform  reflect  cmd internal src  encoding    crypto    crypto  crypto aes  encoding    encoding    crypto    crypto    crypto    crypto    image  time  image internal imageutil  image draw  image jpeg  internal poll  os  sort  encoding binary  regexp syntax  compress    encoding pem  container heap  fmt  path filepath  vendor golang org x net route  os signal  runtime debug  cmd internal sys  crypto des  vendor golang org x crypto   internal    io ioutil  vendor golang org x crypto    regexp  flag  log  debug dwarf  compress flate  debug gosym  debug    cmd vendor golang org x arch arm armasm  cmd vendor golang org x arch      cmd vendor golang org x arch      archive tar  cmd internal objabi  cmd internal goobj  compress lzw  compress zlib  archive zip  compress gzip  context  math big  encoding hex  go token  encoding csv  os exec  go scanner  database sql driver  encoding gob  debug elf  debug macho  debug pe  go ast  database sql  encoding json  encoding xml  vendor golang org x net   hpack  cmd internal objfile  go parser  crypto dsa  crypto elliptic  encoding    crypto rand  go printer  crypto rsa  vendor golang org x text unicode bidi  cmd    vendor golang org x text unicode norm  crypto ecdsa  crypto   pkix  net url  mime  mime quotedprintable  net http internal  text template parse  vendor golang org x text secure bidirule  go constant  text scanner  image gif  image png  index suffixarray  cmd cgo  go format  testing  go types  internal trace  runtime pprof  text template  vendor golang org x net idna  net internal socktest  runtime pprof internal profile  testing internal testdeps  testing iotest  testing quick  internal testenv  cmd internal dwarf  cmd asm internal flags  cmd internal bio  cmd asm internal lex  cmd internal obj  cmd compile internal syntax  cmd internal gcprog  cmd internal browser  cmd dist  cmd fix  go doc  html template  cmd internal obj arm  go build  cmd internal obj    cmd internal obj mips  cmd internal obj    cmd internal obj    cmd internal obj    cmd compile internal types  runtime cgo  go internal gccgoimporter  go internal gcimporter  go internal srcimporter  cmd api  cmd cover  cmd doc  cmd go internal cfg  cmd go internal str  go importer  cmd go internal base  cmd go internal buildid  cmd gofmt  cmd go internal doc  cmd go internal load  cmd go internal help  cmd go internal cmdflag  cmd go internal tool  cmd go internal version  cmd link internal ld  cmd asm internal arch  cmd asm internal asm  cmd compile internal ssa  cmd go internal work  net  os user  cmd go internal fix  cmd go internal fmtcmd  cmd nm  cmd objdump  cmd asm  cmd pack  cmd vendor github com google pprof internal elfexec  cmd vendor github com google pprof profile  cmd vendor github com ianlancetaylor demangle  cmd vendor github com google pprof third party svg  cmd vendor github com google pprof internal proftest  cmd vet internal cfg  cmd vet  cmd go internal envcmd  cmd go internal clean  cmd go internal generate  cmd go internal list  cmd go internal run  cmd go internal test  cmd go internal vet  cmd vendor github com google pprof internal plugin  cmd vendor github com google pprof internal measurement  cmd vendor github com google pprof internal symbolz  cmd vendor github com google pprof internal graph  cmd vendor github com google pprof internal binutils  cmd vendor github com google pprof internal report  vendor golang org x net lex httplex  vendor golang org x net proxy  crypto    net textproto  log syslog  vendor golang org x net nettest  mime multipart  net mail  crypto tls  cmd link internal    cmd link internal arm  cmd link internal    cmd link internal mips  cmd link internal    cmd link internal    cmd link internal    cmd link internal    cmd link  net http httptrace  net smtp  net http  net http cgi  net http cookiejar  expvar  net http httptest  net http httputil  net http pprof  net rpc  cmd go internal web  cmd vendor github com google pprof internal symbolizer  cmd trace  net rpc jsonrpc  net http fcgi  cmd go internal bug  cmd go internal get  cmd vendor github com google pprof internal driver  cmd go  cmd vendor github com google pprof driver  cmd pprof  cmd compile internal gc  cmd compile internal arm  cmd compile internal mips  cmd compile internal    cmd compile internal    cmd compile internal    cmd compile internal    cmd compile internal    cmd compile internal    cmd compile    run bash  line     home xxx go bin go  cannot execute binary file  exec format error  run bash  line     home xxx go bin go  cannot execute binary file  exec format error  run bash  line     home xxx go bin go  no error     xxx xxx home xxx go src     ,1
749427,26162484127.0,IssuesEvent,2022-12-31 19:48:35,feast-dev/feast,https://api.github.com/repos/feast-dev/feast,closed,Supporting multiple online feature stores,kind/feature wontfix priority/p2 Community Contribution Needed,"**Is your feature request related to a problem? Please describe.**
We are seeing that ML feature teams want to own their feature projections and not rely on a single global online feature store with the most common reason being reduction of blast radius.

**Describe the solution you'd like**
A way to create projections of a subset of feature views to specific online stores.

**Describe alternatives you've considered**
I was pointed towards attempting to implement the requested feature using a custom provider which I managed to get working, albeit rather hacky. I've only focused on fanning out the writing of features. 

```python
class ManyOnlineStoresPassthroughConfig(RepoConfig):
    online_stores: List[dict]

class ManyOnlineStoresPassthroughProvider(PassthroughProvider):
    def online_write_batch(self, config: ManyOnlineStoresPassthroughConfig, table: FeatureView, *args, **kwargs) -> None:
        """"""
        Writes feature view to all subscribers
        """"""
        feature_view_subscribers = [store for store in config.online_stores if table.name in store[""view_subscriptions""]]

        for store in feature_view_subscribers:
            print(f""{table.name} online write to subscriber {store['name']}"")

            config.online_store = get_online_config_from_type(store[""type""])(**store)
            self.online_store = get_online_store_from_config(config.online_store)

            return super().online_write_batch(config, table, *args, **kwargs)
```

With the config update of

```yaml
project: aaaa
registry: gs://temp-feast-dev/dev/registry.db
provider: providers.custom_provider.ManyOnlineStoresPassthroughProvider

offline_store:
  type: bigquery
  dataset: temp_feast-dev
  project_id: abc
  location: EU

online_stores:
  - name: ""lovely""
    type: redis
    redis_type: redis
    connection_string: ""blah""
    view_subscriptions: [""feature_view_1""]

  - name: ""lovely""
    type: redis
    redis_type: redis
    connection_string: ""abc""
    view_subscriptions: [""feature_view_1"", ""feature_view_2""]
```

There's still some unknowns around retrieving the online features as we'd need a way of knowing what projection should be used. 

Happy to help wherever I can! ",1.0,"Supporting multiple online feature stores - **Is your feature request related to a problem? Please describe.**
We are seeing that ML feature teams want to own their feature projections and not rely on a single global online feature store with the most common reason being reduction of blast radius.

**Describe the solution you'd like**
A way to create projections of a subset of feature views to specific online stores.

**Describe alternatives you've considered**
I was pointed towards attempting to implement the requested feature using a custom provider which I managed to get working, albeit rather hacky. I've only focused on fanning out the writing of features. 

```python
class ManyOnlineStoresPassthroughConfig(RepoConfig):
    online_stores: List[dict]

class ManyOnlineStoresPassthroughProvider(PassthroughProvider):
    def online_write_batch(self, config: ManyOnlineStoresPassthroughConfig, table: FeatureView, *args, **kwargs) -> None:
        """"""
        Writes feature view to all subscribers
        """"""
        feature_view_subscribers = [store for store in config.online_stores if table.name in store[""view_subscriptions""]]

        for store in feature_view_subscribers:
            print(f""{table.name} online write to subscriber {store['name']}"")

            config.online_store = get_online_config_from_type(store[""type""])(**store)
            self.online_store = get_online_store_from_config(config.online_store)

            return super().online_write_batch(config, table, *args, **kwargs)
```

With the config update of

```yaml
project: aaaa
registry: gs://temp-feast-dev/dev/registry.db
provider: providers.custom_provider.ManyOnlineStoresPassthroughProvider

offline_store:
  type: bigquery
  dataset: temp_feast-dev
  project_id: abc
  location: EU

online_stores:
  - name: ""lovely""
    type: redis
    redis_type: redis
    connection_string: ""blah""
    view_subscriptions: [""feature_view_1""]

  - name: ""lovely""
    type: redis
    redis_type: redis
    connection_string: ""abc""
    view_subscriptions: [""feature_view_1"", ""feature_view_2""]
```

There's still some unknowns around retrieving the online features as we'd need a way of knowing what projection should be used. 

Happy to help wherever I can! ",0,supporting multiple online feature stores     is your feature request related to a problem  please describe     we are seeing that ml feature teams want to own their feature projections and not rely on a single global online feature store with the most common reason being reduction of blast radius       describe the solution you d like    a way to create projections of a subset of feature views to specific online stores       describe alternatives you ve considered    i was pointed towards attempting to implement the requested feature using a custom provider which i managed to get working  albeit rather hacky  i ve only focused on fanning out the writing of features         python  class manyonlinestorespassthroughconfig repoconfig        online stores  list     class manyonlinestorespassthroughprovider passthroughprovider        def online write batch self  config  manyonlinestorespassthroughconfig  table  featureview   args    kwargs     none                        writes feature view to all subscribers                       feature view subscribers                 for store in feature view subscribers               print f  table name  online write to subscriber  store                    config online store   get online config from type store     store               self online store   get online store from config config online store                 return super   online write batch config  table   args    kwargs          with the config update of       yaml  project  aaaa  registry  gs   temp feast dev dev registry db  provider  providers custom provider manyonlinestorespassthroughprovider    offline store     type  bigquery    dataset  temp feast dev    project id  abc    location  eu    online stores       name   lovely       type  redis      redis type  redis      connection string   blah       view subscriptions           name   lovely       type  redis      redis type  redis      connection string   abc       view subscriptions            there s still some unknowns around retrieving the online features as we d need a way of knowing what projection should be used      happy to help wherever i can  ,0
317007,23660113774.0,IssuesEvent,2022-08-26 14:48:31,golang/go,https://api.github.com/repos/golang/go,closed,all: function documentation rendering error,Documentation,"<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?
<pre>
$ go version
go version go1.19 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/shuang/Library/Caches/go-build""
GOENV=""/Users/shuang/Library/Application Support/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/shuang/.go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/shuang/.go""
GOPRIVATE=""""
GOPROXY=""https://goproxy.cn,direct""
GOROOT=""/usr/local/Cellar/go/1.19/libexec""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/1.19/libexec/pkg/tool/darwin_amd64""
GOVCS=""""
GOVERSION=""go1.19""
GCCGO=""gccgo""
GOAMD64=""v1""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
GOWORK=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/1y/2t35nccn4tg5pzrjyx6bgjhw0000gn/T/go-build1994239392=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?
https://github.com/golang/vscode-go/issues/2423

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->



### What did you expect to see?
Function documentation should be displayed normally, without red characters.


### What did you see instead?
All characters after 's are red.
",1.0,"all: function documentation rendering error - <!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?
<pre>
$ go version
go version go1.19 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/shuang/Library/Caches/go-build""
GOENV=""/Users/shuang/Library/Application Support/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/shuang/.go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/shuang/.go""
GOPRIVATE=""""
GOPROXY=""https://goproxy.cn,direct""
GOROOT=""/usr/local/Cellar/go/1.19/libexec""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/1.19/libexec/pkg/tool/darwin_amd64""
GOVCS=""""
GOVERSION=""go1.19""
GCCGO=""gccgo""
GOAMD64=""v1""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
GOWORK=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/1y/2t35nccn4tg5pzrjyx6bgjhw0000gn/T/go-build1994239392=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?
https://github.com/golang/vscode-go/issues/2423

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->



### What did you expect to see?
Function documentation should be displayed normally, without red characters.


### What did you see instead?
All characters after 's are red.
",1,all  function documentation rendering error         please answer these questions before submitting your issue  thanks              what version of go are you using   go version          go version  go version     darwin             does this issue reproduce with the latest release   yes          what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   users shuang library caches go build   goenv   users shuang library application support go env   goexe     goexperiment     goflags     gohostarch      gohostos  darwin   goinsecure     gomodcache   users shuang  go pkg mod   gonoproxy     gonosumdb     goos  darwin   gopath   users shuang  go   goprivate     goproxy     goroot   usr local cellar go     libexec   gosumdb  sum golang org   gotmpdir     gotooldir   usr local cellar go     libexec pkg tool darwin     govcs     goversion        gccgo  gccgo          ar  ar   cc  clang   cxx  clang     cgo enabled      gomod   dev null   gowork     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic  arch         pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders     t go    tmp go build  gno record gcc switches  fno common             what did you do              if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on go dev play is best                  what did you expect to see   function documentation should be displayed normally  without red characters           what did you see instead   all characters after  s are red   ,1
18359,4259810512.0,IssuesEvent,2016-07-11 12:29:15,golang/go,https://api.github.com/repos/golang/go,closed,text/template: improve documentation for creating templates,Documentation Suggested,"by **Shifter1**:

<pre><a href=""http://play.golang.org/p/YfvMjcI7b5"">http://play.golang.org/p/YfvMjcI7b5</a>


Errors from that code are unhelpful, and the documentation for 
* <a href=""http://golang.org/pkg/text/template/#New"">http://golang.org/pkg/text/template/#New</a>
* <a href=""http://golang.org/pkg/text/template/#Template.ParseFiles"">http://golang.org/pkg/text/template/#Template.ParseFiles</a>


No mention is made in the docs that when using .New() and then .ParseFiles(), the
orginal temaplte's name needs to tbe the same as the base name of the first file.</pre>",1.0,"text/template: improve documentation for creating templates - by **Shifter1**:

<pre><a href=""http://play.golang.org/p/YfvMjcI7b5"">http://play.golang.org/p/YfvMjcI7b5</a>


Errors from that code are unhelpful, and the documentation for 
* <a href=""http://golang.org/pkg/text/template/#New"">http://golang.org/pkg/text/template/#New</a>
* <a href=""http://golang.org/pkg/text/template/#Template.ParseFiles"">http://golang.org/pkg/text/template/#Template.ParseFiles</a>


No mention is made in the docs that when using .New() and then .ParseFiles(), the
orginal temaplte's name needs to tbe the same as the base name of the first file.</pre>",1,text template  improve documentation for creating templates   by           a href      errors from that code are unhelpful  and the documentation for     a href       a href      no mention is made in the docs that when using  new   and then  parsefiles    the orginal temaplte s name needs to tbe the same as the base name of the first file  ,1
110837,24015635194.0,IssuesEvent,2022-09-15 00:10:46,qhy040404/Library-One-Tap-Android,https://api.github.com/repos/qhy040404/Library-One-Tap-Android,closed,Rewrite AboutActivity to use partial chrome,enhancement large code low priority UI / UX external,"### Enhancement propose

Better UX

### Solution

![Screenshot_2022-09-15-00-20-06-760_com github android](https://user-images.githubusercontent.com/45379733/190209109-8119bf53-87b0-46b1-9924-722b13a9cc0e.jpg)


### Additional info

_No response_",1.0,"Rewrite AboutActivity to use partial chrome - ### Enhancement propose

Better UX

### Solution

![Screenshot_2022-09-15-00-20-06-760_com github android](https://user-images.githubusercontent.com/45379733/190209109-8119bf53-87b0-46b1-9924-722b13a9cc0e.jpg)


### Additional info

_No response_",0,rewrite aboutactivity to use partial chrome       enhancement propose  better ux      solution              additional info   no response ,0
32364,6050103331.0,IssuesEvent,2017-06-12 20:18:22,golang/go,https://api.github.com/repos/golang/go,closed,database/sql: QueryRow should verify that we have only one row,Documentation,"`QueryRow` is documented as follows:
```go
// QueryRow executes a query that is expected to return at most one row.
// QueryRow always returns a non-nil value. Errors are deferred until
// Row's Scan method is called.
```
This suggests that we should get an error if the query returns more than one row. However `Row.Scan()` doesn't check that `r.rows.Next()` returns false after processing one row, so it would ignore any remaining rows.

Conversely ""at most one row"" suggests that getting no rows is somehow acceptable, but an error is returned in that case. I think it should say ""exactly one row"".",1.0,"database/sql: QueryRow should verify that we have only one row - `QueryRow` is documented as follows:
```go
// QueryRow executes a query that is expected to return at most one row.
// QueryRow always returns a non-nil value. Errors are deferred until
// Row's Scan method is called.
```
This suggests that we should get an error if the query returns more than one row. However `Row.Scan()` doesn't check that `r.rows.Next()` returns false after processing one row, so it would ignore any remaining rows.

Conversely ""at most one row"" suggests that getting no rows is somehow acceptable, but an error is returned in that case. I think it should say ""exactly one row"".",1,database sql  queryrow should verify that we have only one row    queryrow  is documented as follows      go     queryrow executes a query that is expected to return at most one row      queryrow always returns a non nil value  errors are deferred until     row s scan method is called        this suggests that we should get an error if the query returns more than one row  however  row scan    doesn t check that  r rows next    returns false after processing one row  so it would ignore any remaining rows     conversely  at most one row  suggests that getting no rows is somehow acceptable  but an error is returned in that case  i think it should say  exactly one row  ,1
30099,7161174966.0,IssuesEvent,2018-01-28 11:04:11,CaenCamp/new-website,https://api.github.com/repos/CaenCamp/new-website,opened,Version mobile,bug code design,"Pour le moment, le template global du site ne résiste pas à une résolution de mobile. Une page temporaire a été mise en place afin de ne pas présenter une page toute cassée et illisible : 
![capture d ecran de 2018-01-28 12-03-35](https://user-images.githubusercontent.com/547706/35481408-50985d3a-0423-11e8-904d-56ee615f80fe.png)

Il faut reprendre le template de la grid et de certain composants (menu, vue liste des talks, ...) pour un bon affichage mobile.",1.0,"Version mobile - Pour le moment, le template global du site ne résiste pas à une résolution de mobile. Une page temporaire a été mise en place afin de ne pas présenter une page toute cassée et illisible : 
![capture d ecran de 2018-01-28 12-03-35](https://user-images.githubusercontent.com/547706/35481408-50985d3a-0423-11e8-904d-56ee615f80fe.png)

Il faut reprendre le template de la grid et de certain composants (menu, vue liste des talks, ...) pour un bon affichage mobile.",0,version mobile   pour le moment  le template global du site ne résiste pas à une résolution de mobile  une page temporaire a été mise en place afin de ne pas présenter une page toute cassée et illisible             il faut reprendre le template de la grid et de certain composants  menu  vue liste des talks       pour un bon affichage mobile ,0
372632,11018312342.0,IssuesEvent,2019-12-05 10:15:50,ukwa/ukwa-ui,https://api.github.com/repos/ukwa/ukwa-ui,opened,HTTP/HTTPS - solr search issue,Results SOLR Search priority: high,"If a user copies and pastes a url from a live site it will usually be HTTPS these days e.g. https://www.bbc.co.uk/. Historical archived versions may only be HTTP which sometimes means that the search gives no result when in fact there is a valid website in the archive. Conceivably this might also happen the other way around too.

Can url searches be tailored to take account of this? Searching by these different methods also yields different results (maybe that is a different ticket). 

![image](https://user-images.githubusercontent.com/33252622/70225805-a6fdf700-1747-11ea-92df-2ccef1e5d725.png)
![image](https://user-images.githubusercontent.com/33252622/70226036-065c0700-1748-11ea-9f3c-5aaa5011bacb.png)
",1.0,"HTTP/HTTPS - solr search issue - If a user copies and pastes a url from a live site it will usually be HTTPS these days e.g. https://www.bbc.co.uk/. Historical archived versions may only be HTTP which sometimes means that the search gives no result when in fact there is a valid website in the archive. Conceivably this might also happen the other way around too.

Can url searches be tailored to take account of this? Searching by these different methods also yields different results (maybe that is a different ticket). 

![image](https://user-images.githubusercontent.com/33252622/70225805-a6fdf700-1747-11ea-92df-2ccef1e5d725.png)
![image](https://user-images.githubusercontent.com/33252622/70226036-065c0700-1748-11ea-9f3c-5aaa5011bacb.png)
",0,http https   solr search issue   if a user copies and pastes a url from a live site it will usually be https these days e g    historical archived versions may only be http which sometimes means that the search gives no result when in fact there is a valid website in the archive  conceivably this might also happen the other way around too     can url searches be tailored to take account of this  searching by these different methods also yields different results  maybe that is a different ticket                   ,0
359615,10678721936.0,IssuesEvent,2019-10-21 17:50:48,tjmareng/Blendr,https://api.github.com/repos/tjmareng/Blendr,reopened,Registration Page(s),frontend priority: 2,"Create the components necessary for the user to register an account within the application.

**Time Estimate**
13 hours

**Acceptance Criteria**
GIVEN: I am a user
WHEN: I want to register for the application
THEN: There is a user interface form that I can fill out in order to register on the application

Components:
- [x] Email Input Field
- [x] Password Input Field
- [ ] Date of Birth Dropdown
- [x] Next Step Button to Profile Set-Up
",1.0,"Registration Page(s) - Create the components necessary for the user to register an account within the application.

**Time Estimate**
13 hours

**Acceptance Criteria**
GIVEN: I am a user
WHEN: I want to register for the application
THEN: There is a user interface form that I can fill out in order to register on the application

Components:
- [x] Email Input Field
- [x] Password Input Field
- [ ] Date of Birth Dropdown
- [x] Next Step Button to Profile Set-Up
",0,registration page s    create the components necessary for the user to register an account within the application       time estimate      hours      acceptance criteria    given  i am a user  when  i want to register for the application  then  there is a user interface form that i can fill out in order to register on the application    components       email input field      password input field      date of birth dropdown      next step button to profile set up  ,0
28246,5444462009.0,IssuesEvent,2017-03-07 02:53:38,golang/go,https://api.github.com/repos/golang/go,closed,encoding/base64: document that padchar cannot be multi-byte,Documentation,"### What version of Go are you using (`go version`)?
Go 1.8

### What did you expect to see?
Looking at encoding/base64 we see that WithPadding accepts a rune:
https://golang.org/pkg/encoding/base64/#Encoding.WithPadding

Looking at the current implementation, the padding character can not be a multi-byte rune as the code compare bytes with padChar: https://github.com/golang/go/blob/87b1aaa37cefec8deacdf9c3c30d26015bdfb00b/src/encoding/base64/base64.go#L285

### What did you see instead?
I would like the documentation to be changed so it's explicit that we don't support multi-byte padding characters as I don't think it makes sense.
",1.0,"encoding/base64: document that padchar cannot be multi-byte - ### What version of Go are you using (`go version`)?
Go 1.8

### What did you expect to see?
Looking at encoding/base64 we see that WithPadding accepts a rune:
https://golang.org/pkg/encoding/base64/#Encoding.WithPadding

Looking at the current implementation, the padding character can not be a multi-byte rune as the code compare bytes with padChar: https://github.com/golang/go/blob/87b1aaa37cefec8deacdf9c3c30d26015bdfb00b/src/encoding/base64/base64.go#L285

### What did you see instead?
I would like the documentation to be changed so it's explicit that we don't support multi-byte padding characters as I don't think it makes sense.
",1,encoding    document that padchar cannot be multi byte       what version of go are you using   go version     go            what did you expect to see   looking at encoding   we see that withpadding accepts a rune        looking at the current implementation  the padding character can not be a multi byte rune as the code compare bytes with padchar           what did you see instead   i would like the documentation to be changed so it s explicit that we don t support multi byte padding characters as i don t think it makes sense   ,1
68239,3285224119.0,IssuesEvent,2015-10-28 19:40:01,ianopolous/Peergos,https://api.github.com/repos/ianopolous/Peergos,opened,"If i try to submit a follow request with a person i already follow, no error message is displayed",bug priority:Low,Currently this scenario does not display an error message.,1.0,"If i try to submit a follow request with a person i already follow, no error message is displayed - Currently this scenario does not display an error message.",0,if i try to submit a follow request with a person i already follow  no error message is displayed   currently this scenario does not display an error message ,0
242084,20195305035.0,IssuesEvent,2022-02-11 10:06:30,revault/revaultd,https://api.github.com/repos/revault/revaultd,closed,Functional tests: Include a unique ID in the coordinator's Postgre table name,enhancement tests,So we can run the test suite in parallel with a single Postgre server without any race condition.,1.0,Functional tests: Include a unique ID in the coordinator's Postgre table name - So we can run the test suite in parallel with a single Postgre server without any race condition.,0,functional tests  include a unique id in the coordinator s postgre table name   so we can run the test suite in parallel with a single postgre server without any race condition ,0
97440,11013788834.0,IssuesEvent,2019-12-04 21:14:59,golang/go,https://api.github.com/repos/golang/go,closed,"math/rand: possibly ambiguous use of operator ""^"" in documentation",Documentation NeedsFix,"According to the doc here https://golang.org/pkg/math/rand/#Seed
> Seed values that have the same remainder when divided by 2^31-1 generate the same pseudo-random sequence.

This means seed 29 and 57 will generate the same pseudo random sequence. But I get different results. Am I missing something?

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.13.4 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/james/Library/Caches/go-build""
GOENV=""/Users/james/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/james/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/sp/n3hrxcgd3wgb8zb_3mt1w9kr0000gn/T/go-build316781643=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?
https://play.golang.org/p/AoWrOyO2rOP

### What did you expect to see?
same pseudo random sequence

### What did you see instead?
different results with seed 29 and 57
29: 3
57: 4
",1.0,"math/rand: possibly ambiguous use of operator ""^"" in documentation - According to the doc here https://golang.org/pkg/math/rand/#Seed
> Seed values that have the same remainder when divided by 2^31-1 generate the same pseudo-random sequence.

This means seed 29 and 57 will generate the same pseudo random sequence. But I get different results. Am I missing something?

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.13.4 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/james/Library/Caches/go-build""
GOENV=""/Users/james/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/james/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/sp/n3hrxcgd3wgb8zb_3mt1w9kr0000gn/T/go-build316781643=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?
https://play.golang.org/p/AoWrOyO2rOP

### What did you expect to see?
same pseudo random sequence

### What did you see instead?
different results with seed 29 and 57
29: 3
57: 4
",1,math rand  possibly ambiguous use of operator     in documentation   according to the doc here      seed values that have the same remainder when divided by       generate the same pseudo random sequence     this means seed   and   will generate the same pseudo random sequence  but i get different results  am i missing something         what version of go are you using   go version            go version  go version       darwin             does this issue reproduce with the latest release   yes          what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   users james library caches go build   goenv   users james library application support go env   goexe     goflags     gohostarch      gohostos  darwin   gonoproxy     gonosumdb     goos  darwin   gopath   users james go   goprivate     goproxy     goroot   usr local go   gosumdb  sum golang org   gotmpdir     gotooldir   usr local go pkg tool darwin     gccgo  gccgo   ar  ar   cc  clang   cxx  clang     cgo enabled      gomod     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders sp     t go    tmp go build  gno record gcc switches  fno common             what did you do            what did you expect to see   same pseudo random sequence        what did you see instead   different results with seed   and                ,1
104731,11421061493.0,IssuesEvent,2020-02-03 11:21:17,golang/go,https://api.github.com/repos/golang/go,closed,tour: clarify Buffered Channels,Documentation,"Context: http://127.0.0.1:3999/concurrency/3

Please provide a better explanation.  Even after getting it to break I was puzzled.
",1.0,"tour: clarify Buffered Channels - Context: http://127.0.0.1:3999/concurrency/3

Please provide a better explanation.  Even after getting it to break I was puzzled.
",1,tour  clarify buffered channels   context     please provide a better explanation   even after getting it to break i was puzzled  ,1
42498,6986348380.0,IssuesEvent,2017-12-14 02:52:28,golang/go,https://api.github.com/repos/golang/go,closed,testing: deferred func runs before parallel subtest,Documentation,"Also, Run's result was wrong.

#### What did you do?

I deferred a function in a package-scope test, then ran a parallel subtest that assumed the deferred function would run after it completes, but this wasn't the case, and Run returned true when the subtest failed.

Basically, this:

```go
func TestFoo(t *testing.T) {
    defer bar() // Runs before baz

    var passed = t.Run(""subtest"", func(t *testing.T) {
        t.Parallel()
        baz() // Runs after bar
        t.Fail()
    } // Passed is true

    // ...
}
```

It doesn't matter whether the package-scope test is parallel.

A full example: https://play.golang.org/p/pMsKhRvjiW. Note that you'll have to run it locally.

The documentation for testing.T.Run says:

```
func (t *T) Run(name string, f func(t *T)) bool
    Run runs f as a subtest of t called name. It reports whether f succeeded.
    Run runs f in a separate goroutine and will block until all its parallel
    subtests have completed.

    Run may be called simultaneously from multiple goroutines, but all such
    calls must return before the outer test function for t returns.
```

This seems to say that Run always returns an accurate status of the subtest, even if it's parallel, which means the subtest must finish before the Run call completes, and thus before the parent test returns, after which its deferred functions run, but I'm seeing such a deferred function run first. The discussion in https://golang.org/pkg/testing/#hdr-Subtests_and_Sub_benchmarks similarly indicates to me this is incorrect behavior, specifically the paragraphs starting with ""Subtests can also be used to control parallelism"" and ""Run does not return until parallel subtests have completed"".

The documentation for testing.T.Parallel says:

```
func (t *T) Parallel()
    Parallel signals that this test is to be run in parallel with (and only
    with) other parallel tests. When a test is run multiple times due to use of
    -test.count or -test.cpu, multiple instances of a single test never run in
    parallel with each other.
```

This doesn't seem to augment Run's documentation's guarantees, but I'm not sure.

I feel like I must be missing something obvious, but a colleague agreed with my interpretation.

#### What did you expect to see?

```
$ go test -v
=== RUN   TestFoo
=== RUN   TestFoo/sub
--- PASS: TestFoo (0.00s)
	t_test.go:34: passed: actual true, expected true
    --- PASS: TestFoo/sub (0.00s)
PASS
ok  	t	0.036s
```

#### What did you see instead?

```
$ go test -v
=== RUN   TestFoo
=== RUN   TestFoo/sub
--- FAIL: TestFoo (0.00s)
	t_test.go:34: passed: actual true, expected true
    --- FAIL: TestFoo/sub (0.10s)
    	t_test.go:24: Get http://127.0.0.1:61311: dial tcp 127.0.0.1:61311: getsockopt: connection refused
    	t_test.go:28: response: actual nil, expected not nil
FAIL
exit status 1
FAIL	t	0.141s
```

#### System details

```
go version go1.9.2 darwin/amd64
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/willfaught/Developer/go""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.9.2/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.9.2/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/_1/ggvd2t1x7hz_185crsb36zlr0000gp/T/go-build590837635=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOROOT/bin/go version: go version go1.9.2 darwin/amd64
GOROOT/bin/go tool compile -V: compile version go1.9.2
uname -v: Darwin Kernel Version 17.2.0: Fri Sep 29 18:27:05 PDT 2017; root:xnu-4570.20.62~3/RELEASE_X86_64
ProductName:	Mac OS X
ProductVersion:	10.13.1
BuildVersion:	17B1003
lldb --version: lldb-900.0.57
  Swift-4.0
```",1.0,"testing: deferred func runs before parallel subtest - Also, Run's result was wrong.

#### What did you do?

I deferred a function in a package-scope test, then ran a parallel subtest that assumed the deferred function would run after it completes, but this wasn't the case, and Run returned true when the subtest failed.

Basically, this:

```go
func TestFoo(t *testing.T) {
    defer bar() // Runs before baz

    var passed = t.Run(""subtest"", func(t *testing.T) {
        t.Parallel()
        baz() // Runs after bar
        t.Fail()
    } // Passed is true

    // ...
}
```

It doesn't matter whether the package-scope test is parallel.

A full example: https://play.golang.org/p/pMsKhRvjiW. Note that you'll have to run it locally.

The documentation for testing.T.Run says:

```
func (t *T) Run(name string, f func(t *T)) bool
    Run runs f as a subtest of t called name. It reports whether f succeeded.
    Run runs f in a separate goroutine and will block until all its parallel
    subtests have completed.

    Run may be called simultaneously from multiple goroutines, but all such
    calls must return before the outer test function for t returns.
```

This seems to say that Run always returns an accurate status of the subtest, even if it's parallel, which means the subtest must finish before the Run call completes, and thus before the parent test returns, after which its deferred functions run, but I'm seeing such a deferred function run first. The discussion in https://golang.org/pkg/testing/#hdr-Subtests_and_Sub_benchmarks similarly indicates to me this is incorrect behavior, specifically the paragraphs starting with ""Subtests can also be used to control parallelism"" and ""Run does not return until parallel subtests have completed"".

The documentation for testing.T.Parallel says:

```
func (t *T) Parallel()
    Parallel signals that this test is to be run in parallel with (and only
    with) other parallel tests. When a test is run multiple times due to use of
    -test.count or -test.cpu, multiple instances of a single test never run in
    parallel with each other.
```

This doesn't seem to augment Run's documentation's guarantees, but I'm not sure.

I feel like I must be missing something obvious, but a colleague agreed with my interpretation.

#### What did you expect to see?

```
$ go test -v
=== RUN   TestFoo
=== RUN   TestFoo/sub
--- PASS: TestFoo (0.00s)
	t_test.go:34: passed: actual true, expected true
    --- PASS: TestFoo/sub (0.00s)
PASS
ok  	t	0.036s
```

#### What did you see instead?

```
$ go test -v
=== RUN   TestFoo
=== RUN   TestFoo/sub
--- FAIL: TestFoo (0.00s)
	t_test.go:34: passed: actual true, expected true
    --- FAIL: TestFoo/sub (0.10s)
    	t_test.go:24: Get http://127.0.0.1:61311: dial tcp 127.0.0.1:61311: getsockopt: connection refused
    	t_test.go:28: response: actual nil, expected not nil
FAIL
exit status 1
FAIL	t	0.141s
```

#### System details

```
go version go1.9.2 darwin/amd64
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/willfaught/Developer/go""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.9.2/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.9.2/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/_1/ggvd2t1x7hz_185crsb36zlr0000gp/T/go-build590837635=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOROOT/bin/go version: go version go1.9.2 darwin/amd64
GOROOT/bin/go tool compile -V: compile version go1.9.2
uname -v: Darwin Kernel Version 17.2.0: Fri Sep 29 18:27:05 PDT 2017; root:xnu-4570.20.62~3/RELEASE_X86_64
ProductName:	Mac OS X
ProductVersion:	10.13.1
BuildVersion:	17B1003
lldb --version: lldb-900.0.57
  Swift-4.0
```",1,testing  deferred func runs before parallel subtest   also  run s result was wrong          what did you do     i deferred a function in a package scope test  then ran a parallel subtest that assumed the deferred function would run after it completes  but this wasn t the case  and run returned true when the subtest failed     basically  this        go  func testfoo t  testing t         defer bar      runs before baz        var passed   t run  subtest   func t  testing t             t parallel            baz      runs after bar          t fail             passed is true                          it doesn t matter whether the package scope test is parallel     a full example    note that you ll have to run it locally     the documentation for testing t run says          func  t  t  run name string  f func t  t   bool      run runs f as a subtest of t called name  it reports whether f succeeded       run runs f in a separate goroutine and will block until all its parallel      subtests have completed         run may be called simultaneously from multiple goroutines  but all such      calls must return before the outer test function for t returns          this seems to say that run always returns an accurate status of the subtest  even if it s parallel  which means the subtest must finish before the run call completes  and thus before the parent test returns  after which its deferred functions run  but i m seeing such a deferred function run first  the discussion in   similarly indicates to me this is incorrect behavior  specifically the paragraphs starting with  subtests can also be used to control parallelism  and  run does not return until parallel subtests have completed      the documentation for testing t parallel says          func  t  t  parallel        parallel signals that this test is to be run in parallel with  and only      with  other parallel tests  when a test is run multiple times due to use of       test count or  test cpu  multiple instances of a single test never run in      parallel with each other          this doesn t seem to augment run s documentation s guarantees  but i m not sure     i feel like i must be missing something obvious  but a colleague agreed with my interpretation          what did you expect to see            go test  v      run   testfoo      run   testfoo sub      pass  testfoo        	t test go    passed  actual true  expected true          pass  testfoo sub        pass  ok  	t	                 what did you see instead            go test  v      run   testfoo      run   testfoo sub      fail  testfoo        	t test go    passed  actual true  expected true          fail  testfoo sub            	t test go    get   dial tcp            getsockopt  connection refused      	t test go    response  actual nil  expected not nil  fail  exit status    fail	t	                 system details         go version       darwin    goarch      gobin     goexe     gohostarch      gohostos  darwin   goos  darwin   gopath   users willfaught developer go   gorace     goroot   usr local cellar go       libexec   gotooldir   usr local cellar go       libexec pkg tool darwin     gccgo  gccgo   cc  clang   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders        t go    tmp go build  gno record gcc switches  fno common   cxx  clang     cgo enabled      cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   goroot bin go version  go version       darwin    goroot bin go tool compile  v  compile version        uname  v  darwin kernel version        fri sep         pdt    root xnu         release      productname 	mac os x  productversion 	       buildversion 	   lldb   version  lldb          swift         ,1
14384,3833096687.0,IssuesEvent,2016-04-01 00:49:00,golang/go,https://api.github.com/repos/golang/go,closed,"net/http: documentation of ""func (*Client) Do"" doesn't state clearly when to close response.Body",Documentation,"by **fish@freigeist.org**:

<pre>The documentation for Do()[1] says:

&quot;When err is nil, resp always contains a non-nil resp.Body.&quot;

But it doesn't specify the behaviour if error is non-nil:
Do I need to close the Body if err is NOT nil?






---
[1] <a href=""https://godoc.org/net/http#Client.Do"">https://godoc.org/net/http#Client.Do</a></pre>",1.0,"net/http: documentation of ""func (*Client) Do"" doesn't state clearly when to close response.Body - by **fish@freigeist.org**:

<pre>The documentation for Do()[1] says:

&quot;When err is nil, resp always contains a non-nil resp.Body.&quot;

But it doesn't specify the behaviour if error is non-nil:
Do I need to close the Body if err is NOT nil?






---
[1] <a href=""https://godoc.org/net/http#Client.Do"">https://godoc.org/net/http#Client.Do</a></pre>",1,net http  documentation of  func   client  do  doesn t state clearly when to close response body   by   fish freigeist org      the documentation for do    says    quot when err is nil  resp always contains a non nil resp body  quot   but it doesn t specify the behaviour if error is non nil  do i need to close the body if err is not nil               a href   ,1
317303,23671319016.0,IssuesEvent,2022-08-27 11:57:59,golang/go,https://api.github.com/repos/golang/go,closed,dev.boringcrypto: documentation related to Bazel,Documentation NeedsDecision,"Hello folks,

Apologies for not sticking to the template, but this is just a question and a kind request for some documentation updates.
I have a couple of questions related to the Bazel build when using dev.boringcrypto.

https://github.com/golang/go/tree/dev.boringcrypto/misc/boring#building-from-bazel
Here is the snippet:

----
## Building from Bazel

Starting from [bazelbuild/rules_go](https://github.com/bazelbuild/rules_go) tag 0.7.1, simply download the BoringCrypto-enabled Go SDK using `go_download_sdk()` before calling `go_register_toolchains()`.

For example, to use Go 1.9.3 with BoringCrypto on Linux, use the following lines in `WORKSPACE`:
```python
load(""@io_bazel_rules_go//go:def.bzl"", ""go_rules_dependencies"", ""go_download_sdk"", ""go_register_toolchains"")

go_rules_dependencies()

go_download_sdk(
    name = ""go_sdk"",
    sdks = {
       ""linux_amd64"": (""go1.9.3b4.linux-amd64.tar.gz"", ""db1997b2454a2f27669b849d2d2cafb247a55128d53da678f06cb409310d6660""),
    },
    urls = [""https://storage.googleapis.com/go-boringcrypto/{}""],
)

go_register_toolchains()
```

**Note**: you must *not* enable `pure` mode, since cgo must be enabled. To ensure that binaries are linked with BoringCrypto, you can set `pure = ""off""` on all relevant `go_binary` rules.

-------

Now that I have refreshed your cache, let me present the questions:
1. Is this documentation up-to-date?
2. I can't help but notice that in the Note section you have explicitly mentioned that the pure mode must be disabled. Looking into its default value I can see that it is set to auto https://github.com/bazelbuild/rules_go/blob/master/go/core.rst#attributes-2 `If auto, pure mode is enabled when no C/C++ toolchain is configured or when cross-compiling`. It is also suggested to control this on the command line `--@io_bazel_rules_go//go/config:pure`, where its default value is `false`. I just wanted someone to confirm that if nothing is done explicitly, it will be default to the first case and be set to `auto`, therefore rely on the C/C++ toolchain or cross-compilation. 
3. Since compiling binaries with dev.boringcrypto requires CGO to be enabled, does one need to set `cgo=True` in every go_binary and go_library or having this only in the main package's is sufficient?

Overall, I would love if someone could elaborate on the Bazel build process when consuming dev.boringcrypto and I personally feel like having a FAQ would greatly benefit the community.",1.0,"dev.boringcrypto: documentation related to Bazel - Hello folks,

Apologies for not sticking to the template, but this is just a question and a kind request for some documentation updates.
I have a couple of questions related to the Bazel build when using dev.boringcrypto.

https://github.com/golang/go/tree/dev.boringcrypto/misc/boring#building-from-bazel
Here is the snippet:

----
## Building from Bazel

Starting from [bazelbuild/rules_go](https://github.com/bazelbuild/rules_go) tag 0.7.1, simply download the BoringCrypto-enabled Go SDK using `go_download_sdk()` before calling `go_register_toolchains()`.

For example, to use Go 1.9.3 with BoringCrypto on Linux, use the following lines in `WORKSPACE`:
```python
load(""@io_bazel_rules_go//go:def.bzl"", ""go_rules_dependencies"", ""go_download_sdk"", ""go_register_toolchains"")

go_rules_dependencies()

go_download_sdk(
    name = ""go_sdk"",
    sdks = {
       ""linux_amd64"": (""go1.9.3b4.linux-amd64.tar.gz"", ""db1997b2454a2f27669b849d2d2cafb247a55128d53da678f06cb409310d6660""),
    },
    urls = [""https://storage.googleapis.com/go-boringcrypto/{}""],
)

go_register_toolchains()
```

**Note**: you must *not* enable `pure` mode, since cgo must be enabled. To ensure that binaries are linked with BoringCrypto, you can set `pure = ""off""` on all relevant `go_binary` rules.

-------

Now that I have refreshed your cache, let me present the questions:
1. Is this documentation up-to-date?
2. I can't help but notice that in the Note section you have explicitly mentioned that the pure mode must be disabled. Looking into its default value I can see that it is set to auto https://github.com/bazelbuild/rules_go/blob/master/go/core.rst#attributes-2 `If auto, pure mode is enabled when no C/C++ toolchain is configured or when cross-compiling`. It is also suggested to control this on the command line `--@io_bazel_rules_go//go/config:pure`, where its default value is `false`. I just wanted someone to confirm that if nothing is done explicitly, it will be default to the first case and be set to `auto`, therefore rely on the C/C++ toolchain or cross-compilation. 
3. Since compiling binaries with dev.boringcrypto requires CGO to be enabled, does one need to set `cgo=True` in every go_binary and go_library or having this only in the main package's is sufficient?

Overall, I would love if someone could elaborate on the Bazel build process when consuming dev.boringcrypto and I personally feel like having a FAQ would greatly benefit the community.",1,dev boringcrypto  documentation related to bazel   hello folks     apologies for not sticking to the template  but this is just a question and a kind request for some documentation updates   i have a couple of questions related to the bazel build when using dev boringcrypto        here is the snippet              building from bazel    starting from     tag        simply download the boringcrypto enabled go sdk using  go download sdk    before calling  go register toolchains        for example  to use go       with boringcrypto on linux  use the following lines in  workspace       python  load   io bazel rules go  go def bzl    go rules dependencies    go download sdk    go register toolchains      go rules dependencies      go download sdk       name    go sdk        sdks              linux             linux   tar gz                      urls            go register toolchains             note    you must  not  enable  pure  mode  since cgo must be enabled  to ensure that binaries are linked with boringcrypto  you can set  pure    off   on all relevant  go binary  rules                now that i have refreshed your cache  let me present the questions      is this documentation up to date      i can t help but notice that in the note section you have explicitly mentioned that the pure mode must be disabled  looking into its default value i can see that it is set to auto    if auto  pure mode is enabled when no c c   toolchain is configured or when cross compiling   it is also suggested to control this on the command line     io bazel rules go  go config pure   where its default value is  false   i just wanted someone to confirm that if nothing is done explicitly  it will be default to the first case and be set to  auto   therefore rely on the c c   toolchain or cross compilation       since compiling binaries with dev boringcrypto requires cgo to be enabled  does one need to set  cgo true  in every go binary and go library or having this only in the main package s is sufficient     overall  i would love if someone could elaborate on the bazel build process when consuming dev boringcrypto and i personally feel like having a faq would greatly benefit the community ,1
233100,18948235643.0,IssuesEvent,2021-11-18 12:36:00,SAP/ui5-webcomponents,https://api.github.com/repos/SAP/ui5-webcomponents,closed,Rating Indicator: In RTL mode not round values are incorrectly visualised ,Low Prio TOPIC RL 1.0 Release Testing,"### **Bug Description**
In RTL mode not rounded values are incorrectly visualised.

### **Steps to Reproduce**
1. Go to https://sap.github.io/ui5-webcomponents/master/playground/main/pages/RatingIndicator/
2. Set dir=""rtl"" to the body
3. Check the fifth sample where the value is not round or change the value of any other instance.

<img width=""256"" alt=""Screenshot 2021-08-25 at 9 06 59"" src=""https://user-images.githubusercontent.com/38278268/130736044-7ba677fb-a2fc-4c61-88e5-b22b43875e94.png"">

### **Context**
- UI5 Web Components version: v1.0.0-rc.16

- OS/Platform: MAC OS, iOS
- Browser: Chrome/Safari
- Affected component: ui5-rating-indicator",1.0,"Rating Indicator: In RTL mode not round values are incorrectly visualised  - ### **Bug Description**
In RTL mode not rounded values are incorrectly visualised.

### **Steps to Reproduce**
1. Go to https://sap.github.io/ui5-webcomponents/master/playground/main/pages/RatingIndicator/
2. Set dir=""rtl"" to the body
3. Check the fifth sample where the value is not round or change the value of any other instance.

<img width=""256"" alt=""Screenshot 2021-08-25 at 9 06 59"" src=""https://user-images.githubusercontent.com/38278268/130736044-7ba677fb-a2fc-4c61-88e5-b22b43875e94.png"">

### **Context**
- UI5 Web Components version: v1.0.0-rc.16

- OS/Platform: MAC OS, iOS
- Browser: Chrome/Safari
- Affected component: ui5-rating-indicator",0,rating indicator  in rtl mode not round values are incorrectly visualised          bug description    in rtl mode not rounded values are incorrectly visualised           steps to reproduce       go to       set dir  rtl  to the body     check the fifth sample where the value is not round or change the value of any other instance      img width     alt  screenshot       at        src             context        web components version        rc        os platform  mac os  ios    browser  chrome safari    affected component    rating indicator,0
436681,30564976848.0,IssuesEvent,2023-07-20 17:03:55,golang/go,https://api.github.com/repos/golang/go,closed,net/url: better handling or documentation of IPv6 addresses in url.URL.Host,Documentation NeedsDecision,"### What did you do?

https://go.dev/play/p/Lypv_o9VMRf

	host := ""fc00::121:0:2:27""
	url := url.URL{
		Scheme: ""https"",
		Host:   host,
		Path:   ""/some/path"",
	}
	fmt.Println(url.String())

### What did you expect to see?

`https://[fc00::121:0:2:27]/some/path`

### What did you see instead?

`https://fc00::121:0:2:27/some/path`

This ends up being interpreted as `https://[fc00::121:0:2]:27/some/path`.

The documentation for `url.URL.Host` is `host or host:port`, which leaves it unclear as to how a literal IPv6 address would be treated.

I think it makes more sense to treat a literal IPv6 address as just that, and require the user to specify `[<ipv6-address>]:<port>` if that's what they actually wanted, though I appreciate that there would be backward compatibility issues with that.

So at this point, it's probably best to just clarify the docs and add a reference to `net.JoinHostPort`. This could perhaps be done via #61093.",1.0,"net/url: better handling or documentation of IPv6 addresses in url.URL.Host - ### What did you do?

https://go.dev/play/p/Lypv_o9VMRf

	host := ""fc00::121:0:2:27""
	url := url.URL{
		Scheme: ""https"",
		Host:   host,
		Path:   ""/some/path"",
	}
	fmt.Println(url.String())

### What did you expect to see?

`https://[fc00::121:0:2:27]/some/path`

### What did you see instead?

`https://fc00::121:0:2:27/some/path`

This ends up being interpreted as `https://[fc00::121:0:2]:27/some/path`.

The documentation for `url.URL.Host` is `host or host:port`, which leaves it unclear as to how a literal IPv6 address would be treated.

I think it makes more sense to treat a literal IPv6 address as just that, and require the user to specify `[<ipv6-address>]:<port>` if that's what they actually wanted, though I appreciate that there would be backward compatibility issues with that.

So at this point, it's probably best to just clarify the docs and add a reference to `net.JoinHostPort`. This could perhaps be done via #61093.",1,net url  better handling or documentation of   addresses in url url host       what did you do          	host                  	url    url url   		scheme   https    		host    host   		path      some path    	   	fmt println url string           what did you expect to see      https     some path         what did you see instead           this ends up being interpreted as  https       some path      the documentation for  url url host  is  host or host port   which leaves it unclear as to how a literal   address would be treated     i think it makes more sense to treat a literal   address as just that  and require the user to specify       if that s what they actually wanted  though i appreciate that there would be backward compatibility issues with that     so at this point  it s probably best to just clarify the docs and add a reference to  net joinhostport   this could perhaps be done via    ,1
169075,13113167498.0,IssuesEvent,2020-08-05 04:33:38,samblenny/ime-engine,https://api.github.com/repos/samblenny/ime-engine,opened,pre-parsing stage with language switching commands like: /en /py /zh,P3 algo doc protocol test,"Provide support for scenario like this:
1. Prompt: 词语 for 我想喝果汁
2. Answer: `woxiangheguozhi  ` --> `我想喝果汁`
3. Prompt: Pinyin for 我想喝果汁
4. Answer: **`/py`**`wo3 xiang3 he1 guo3zhi1` --> `wǒ xiǎng hē guǒzhī`
5. Prompt: Meaning of 我想喝果汁
6. Answer: **`/en`**`I want to drink fruit juice` --> `I want to drink fruit juice`",1.0,"pre-parsing stage with language switching commands like: /en /py /zh - Provide support for scenario like this:
1. Prompt: 词语 for 我想喝果汁
2. Answer: `woxiangheguozhi  ` --> `我想喝果汁`
3. Prompt: Pinyin for 我想喝果汁
4. Answer: **`/py`**`wo3 xiang3 he1 guo3zhi1` --> `wǒ xiǎng hē guǒzhī`
5. Prompt: Meaning of 我想喝果汁
6. Answer: **`/en`**`I want to drink fruit juice` --> `I want to drink fruit juice`",0,pre parsing stage with language switching commands like   en  py  zh   provide support for scenario like this      prompt  词语 for 我想喝果汁     answer   woxiangheguozhi         我想喝果汁      prompt  pinyin for 我想喝果汁     answer      py                  wǒ xiǎng hē guǒzhī      prompt  meaning of 我想喝果汁     answer      en    i want to drink fruit juice       i want to drink fruit juice ,0
293022,8971879068.0,IssuesEvent,2019-01-29 16:52:43,AnalyticalGraphicsInc/cesium,https://api.github.com/repos/AnalyticalGraphicsInc/cesium,closed,Ground polygon is wrong,category - polygons/geometry priority - next release type - bug,"![image](https://user-images.githubusercontent.com/3451886/51687502-a2fa3800-1fc0-11e9-91d3-7c7ac95dd668.png)

The red is a polygon with height: 0.  The purple is where it overlaps with the ground polygon.

```js
var viewer = new Cesium.Viewer('cesiumContainer');

viewer.entities.add({
    polygon : {
        hierarchy : Cesium.Cartesian3.fromDegreesArray([-120.0, 30.0,
                                                        -80.0, 30.0,
                                                        -80.0, 40.0,
                                                        -120.0, 40.0]),
        material : Cesium.Color.BLUE.withAlpha(0.5)
    }
});

viewer.entities.add({
    polygon : {
        hierarchy : Cesium.Cartesian3.fromDegreesArray([-120.0, 30.0,
                                                        -80.0, 30.0,
                                                        -80.0, 40.0,
                                                        -120.0, 40.0]),
        material : Cesium.Color.RED.withAlpha(0.5),
        height: 0
    }
});

viewer.zoomTo(viewer.entities);
```",1.0,"Ground polygon is wrong - ![image](https://user-images.githubusercontent.com/3451886/51687502-a2fa3800-1fc0-11e9-91d3-7c7ac95dd668.png)

The red is a polygon with height: 0.  The purple is where it overlaps with the ground polygon.

```js
var viewer = new Cesium.Viewer('cesiumContainer');

viewer.entities.add({
    polygon : {
        hierarchy : Cesium.Cartesian3.fromDegreesArray([-120.0, 30.0,
                                                        -80.0, 30.0,
                                                        -80.0, 40.0,
                                                        -120.0, 40.0]),
        material : Cesium.Color.BLUE.withAlpha(0.5)
    }
});

viewer.entities.add({
    polygon : {
        hierarchy : Cesium.Cartesian3.fromDegreesArray([-120.0, 30.0,
                                                        -80.0, 30.0,
                                                        -80.0, 40.0,
                                                        -120.0, 40.0]),
        material : Cesium.Color.RED.withAlpha(0.5),
        height: 0
    }
});

viewer.zoomTo(viewer.entities);
```",0,ground polygon is wrong           the red is a polygon with height      the purple is where it overlaps with the ground polygon        js  var viewer   new cesium viewer  cesiumcontainer       viewer entities add        polygon              hierarchy   cesium   fromdegreesarray                                                                                                                                                                                                                                    material   cesium color blue withalpha                     viewer entities add        polygon              hierarchy   cesium   fromdegreesarray                                                                                                                                                                                                                                    material   cesium color red withalpha                height                   viewer zoomto viewer entities       ,0
524646,15218377116.0,IssuesEvent,2021-02-17 17:44:59,patternfly/patternfly-elements,https://api.github.com/repos/patternfly/patternfly-elements,opened,bug with pfe-content-set moving panel content into the shadow DOM,bug priority: low,"## Description of the issue

- The content set component is moving content within the panel into the shadow DOM, and thus that content is missing styles, specifically in this case you can see that the pfe-cta is not upgrading.

### Impacted component(s)

- pfe-content-set


### Steps to reproduce

1. Put a pfe-cta inside of the `<div pfe-content-set--panel> `
2. Notice that the CTA does not upgrade 

### Expected behavior


### Screenshots

![image](https://user-images.githubusercontent.com/456863/108244763-8d16bd00-711d-11eb-899e-9ea0c2372924.png)

![image](https://user-images.githubusercontent.com/456863/108244856-a881c800-711d-11eb-9eab-700b7a2b4373.png)

## Related issues

- (#100) Description

<!-- 
  Please update the labels for this component to reflect the topic of the issue: accessibility, doc / demo, functionality, integration, styles-only, tests, tools.
  
  Note also the severity level; all new issues default to severity level 1 which is low priority.  If you feel this issue deserves more attention, please set the label to sev-2 or sev-3.
-->
",1.0,"bug with pfe-content-set moving panel content into the shadow DOM - ## Description of the issue

- The content set component is moving content within the panel into the shadow DOM, and thus that content is missing styles, specifically in this case you can see that the pfe-cta is not upgrading.

### Impacted component(s)

- pfe-content-set


### Steps to reproduce

1. Put a pfe-cta inside of the `<div pfe-content-set--panel> `
2. Notice that the CTA does not upgrade 

### Expected behavior


### Screenshots

![image](https://user-images.githubusercontent.com/456863/108244763-8d16bd00-711d-11eb-899e-9ea0c2372924.png)

![image](https://user-images.githubusercontent.com/456863/108244856-a881c800-711d-11eb-9eab-700b7a2b4373.png)

## Related issues

- (#100) Description

<!-- 
  Please update the labels for this component to reflect the topic of the issue: accessibility, doc / demo, functionality, integration, styles-only, tests, tools.
  
  Note also the severity level; all new issues default to severity level 1 which is low priority.  If you feel this issue deserves more attention, please set the label to sev-2 or sev-3.
-->
",0,bug with pfe content set moving panel content into the shadow dom      description of the issue      the content set component is moving content within the panel into the shadow dom  and thus that content is missing styles  specifically in this case you can see that the pfe cta is not upgrading         impacted component s       pfe content set          steps to reproduce       put a pfe cta inside of the          notice that the cta does not upgrade         expected behavior          screenshots                       related issues           description             please update the labels for this component to reflect the topic of the issue  accessibility  doc   demo  functionality  integration  styles only  tests  tools         note also the severity level  all new issues default to severity level   which is low priority   if you feel this issue deserves more attention  please set the label to sev   or sev          ,0
50057,7558926449.0,IssuesEvent,2018-04-20 00:53:32,golang/go,https://api.github.com/repos/golang/go,closed,net: calling (*UnixConn).File leads to performance degredation,Documentation NeedsFix help wanted,"### What version of Go are you using (`go version`)?

```
$ go version
go version go1.9.2 linux/amd64
```

### Does this issue reproduce with the latest release?

Yes, this is on 1.9.2. I haven't tried master.

### What operating system and processor architecture are you using (`go env`)?

linux/amd64, Ubuntu 17.04 with 4.10.0-40-generic kernel

### What did you do?

I was trying to track down a performance degradation when using unix socket credentials on an abstract socket (bind address starts with a null byte `\x00`). The following benchmark shows the discrepancy:

```
goos: linux
goarch: amd64
pkg: github.com/stevvooe/ttrpc
BenchmarkRoundTrip-8                  	   50000	     22078 ns/op	    2593 B/op	      43 allocs/op
BenchmarkRoundTripUnixSocketCreds-8   	   10000	    141333 ns/op	    2593 B/op	      43 allocs/op
PASS
ok  	github.com/stevvooe/ttrpc	3.142s
```

Notice that the benchmark that uses the unix socket credentials is much slower. The code in question is available here:

https://github.com/stevvooe/ttrpc/blob/45d16b41b590938186c5c7cde8088607b3933231/unixcreds.go#L23-L35

After some experimentation, I found that removing the call to `(*UnixConn).File` got rid of the performance discrepancy. As an experiment, I applied the following patch to the `net` package to access the fd directly and pass that to `unix.GetsockoptUcred`:

```diff
diff --git a/net/unixsock.go b/net/unixsock.go.fdfix
index 057940a..df44b1b 100644
--- a/net/unixsock.go
+++ b/net/unixsock.go.fdfix
@@ -63,6 +63,10 @@ type UnixConn struct {
 	conn
 }
 
+func (c *UnixConn) Fd() uintptr {
+	return uintptr(c.conn.fd.pfd.Sysfd)
+}
+
 // SyscallConn returns a raw network connection.
 // This implements the syscall.Conn interface.
 func (c *UnixConn) SyscallConn() (syscall.RawConn, error) {
```

When I ran the benchmark with that change, passing `(*UnixConn).Fd` directly to `unix.GetsockoptUcred`, without calling `(*UnixConn).File`, I then got the following benchmark numbers:

```
goos: linux
goarch: amd64
pkg: github.com/stevvooe/ttrpc
BenchmarkRoundTripUnixSocketCreds-8      50000	     21897 ns/op	    2593 B/op	      43 allocs/op
PASS
ok  	github.com/stevvooe/ttrpc	1.693s
```

While this probably isn't a great patch, as making that fd available can probably cause problems with the poller, hopefully this demonstrates the issue with call `(*UnixConn).File`. If you need a more minimal example, let me know.

### What did you expect to see?

I expected no performance degradation when calling `(*UnixConn).File`.

### What did you see instead?

A performance degradation after calling `(*UnixConn).File`.",1.0,"net: calling (*UnixConn).File leads to performance degredation - ### What version of Go are you using (`go version`)?

```
$ go version
go version go1.9.2 linux/amd64
```

### Does this issue reproduce with the latest release?

Yes, this is on 1.9.2. I haven't tried master.

### What operating system and processor architecture are you using (`go env`)?

linux/amd64, Ubuntu 17.04 with 4.10.0-40-generic kernel

### What did you do?

I was trying to track down a performance degradation when using unix socket credentials on an abstract socket (bind address starts with a null byte `\x00`). The following benchmark shows the discrepancy:

```
goos: linux
goarch: amd64
pkg: github.com/stevvooe/ttrpc
BenchmarkRoundTrip-8                  	   50000	     22078 ns/op	    2593 B/op	      43 allocs/op
BenchmarkRoundTripUnixSocketCreds-8   	   10000	    141333 ns/op	    2593 B/op	      43 allocs/op
PASS
ok  	github.com/stevvooe/ttrpc	3.142s
```

Notice that the benchmark that uses the unix socket credentials is much slower. The code in question is available here:

https://github.com/stevvooe/ttrpc/blob/45d16b41b590938186c5c7cde8088607b3933231/unixcreds.go#L23-L35

After some experimentation, I found that removing the call to `(*UnixConn).File` got rid of the performance discrepancy. As an experiment, I applied the following patch to the `net` package to access the fd directly and pass that to `unix.GetsockoptUcred`:

```diff
diff --git a/net/unixsock.go b/net/unixsock.go.fdfix
index 057940a..df44b1b 100644
--- a/net/unixsock.go
+++ b/net/unixsock.go.fdfix
@@ -63,6 +63,10 @@ type UnixConn struct {
 	conn
 }
 
+func (c *UnixConn) Fd() uintptr {
+	return uintptr(c.conn.fd.pfd.Sysfd)
+}
+
 // SyscallConn returns a raw network connection.
 // This implements the syscall.Conn interface.
 func (c *UnixConn) SyscallConn() (syscall.RawConn, error) {
```

When I ran the benchmark with that change, passing `(*UnixConn).Fd` directly to `unix.GetsockoptUcred`, without calling `(*UnixConn).File`, I then got the following benchmark numbers:

```
goos: linux
goarch: amd64
pkg: github.com/stevvooe/ttrpc
BenchmarkRoundTripUnixSocketCreds-8      50000	     21897 ns/op	    2593 B/op	      43 allocs/op
PASS
ok  	github.com/stevvooe/ttrpc	1.693s
```

While this probably isn't a great patch, as making that fd available can probably cause problems with the poller, hopefully this demonstrates the issue with call `(*UnixConn).File`. If you need a more minimal example, let me know.

### What did you expect to see?

I expected no performance degradation when calling `(*UnixConn).File`.

### What did you see instead?

A performance degradation after calling `(*UnixConn).File`.",1,net  calling   unixconn  file leads to performance degredation       what version of go are you using   go version              go version  go version       linux               does this issue reproduce with the latest release     yes  this is on        i haven t tried master         what operating system and processor architecture are you using   go env       linux    ubuntu     with         generic kernel        what did you do     i was trying to track down a performance degradation when using unix socket credentials on an abstract socket  bind address starts with a null byte        the following benchmark shows the discrepancy          goos  linux  goarch     pkg  github com stevvooe ttrpc  benchmarkroundtrip                    	    	       ns op	      b op	        allocs op  benchmarkroundtripunixsocketcreds     	    	      ns op	      b op	        allocs op  pass  ok  	github com stevvooe ttrpc	            notice that the benchmark that uses the unix socket credentials is much slower  the code in question is available here          after some experimentation  i found that removing the call to    unixconn  file  got rid of the performance discrepancy  as an experiment  i applied the following patch to the  net  package to access the fd directly and pass that to  unix getsockoptucred         diff  diff   git a net unixsock go b net unixsock go fdfix  index             a net unixsock go      b net unixsock go fdfix                  type unixconn struct     	conn          func  c  unixconn  fd   uintptr     	return uintptr c conn fd pfd sysfd              syscallconn returns a raw network connection       this implements the syscall conn interface    func  c  unixconn  syscallconn    syscall rawconn  error            when i ran the benchmark with that change  passing    unixconn  fd  directly to  unix getsockoptucred   without calling    unixconn  file   i then got the following benchmark numbers          goos  linux  goarch     pkg  github com stevvooe ttrpc  benchmarkroundtripunixsocketcreds         	       ns op	      b op	        allocs op  pass  ok  	github com stevvooe ttrpc	            while this probably isn t a great patch  as making that fd available can probably cause problems with the poller  hopefully this demonstrates the issue with call    unixconn  file   if you need a more minimal example  let me know         what did you expect to see     i expected no performance degradation when calling    unixconn  file          what did you see instead     a performance degradation after calling    unixconn  file  ,1
252225,19008337855.0,IssuesEvent,2021-11-23 05:13:34,golang/go,https://api.github.com/repos/golang/go,closed,path.Base and path.Split do not properly split the file name on Windows as documented,Documentation,"### What version of Go are you using (`go version`)?

<pre>
go version go1.17.3 windows/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\heath\AppData\Local\go-build
set GOENV=C:\Users\heath\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\heath\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\heath\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=C:\Program Files\Go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=C:\Program Files\Go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.17.3
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=NUL
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\heath\AppData\Local\Temp\go-build4257983573=/tmp/go-build -gno-record-gcc-switches
</pre></details>

### What did you do?

Using `path.Base()` and `path.Split()` on Windows, I found they do not return just the file name (or directory and filename separated) as documented. They work as documented on WSL2 (Ubunto 18.04, however).

```go
package main

import (
    ""fmt""
    ""os""
    ""path""
)

func main() {
    fmt.Println(""base ="", path.Base(os.Args[0]))

    dir, file := path.Split(os.Args[0])
    fmt.Printf(""dir = %q, file = %q\n"", dir, file)
}
```

### What did you expect to see?

I expected the file name itself to be returned from `path.Base`, as well as the directory and file name in `dir` and `file` parameters from `path.Split`.


### What did you see instead?

On Windows, the entire path was found in place of the file as shown in the output from the sample program below:

```
base = C:\Users\heath\AppData\Local\Temp\go-build2408382784\b001\exe\main.exe
dir = """", file = ""C:\\Users\\heath\\AppData\\Local\\Temp\\go-build2408382784\\b001\\exe\\main.exe""
```

On Ubuntu the content below is correct according to documentation and is what I expected:

```
base = main
dir = ""/tmp/go-build2295857948/b001/exe/"", file = ""main""
```",1.0,"path.Base and path.Split do not properly split the file name on Windows as documented - ### What version of Go are you using (`go version`)?

<pre>
go version go1.17.3 windows/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\heath\AppData\Local\go-build
set GOENV=C:\Users\heath\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\heath\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\heath\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=C:\Program Files\Go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=C:\Program Files\Go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.17.3
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=NUL
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\heath\AppData\Local\Temp\go-build4257983573=/tmp/go-build -gno-record-gcc-switches
</pre></details>

### What did you do?

Using `path.Base()` and `path.Split()` on Windows, I found they do not return just the file name (or directory and filename separated) as documented. They work as documented on WSL2 (Ubunto 18.04, however).

```go
package main

import (
    ""fmt""
    ""os""
    ""path""
)

func main() {
    fmt.Println(""base ="", path.Base(os.Args[0]))

    dir, file := path.Split(os.Args[0])
    fmt.Printf(""dir = %q, file = %q\n"", dir, file)
}
```

### What did you expect to see?

I expected the file name itself to be returned from `path.Base`, as well as the directory and file name in `dir` and `file` parameters from `path.Split`.


### What did you see instead?

On Windows, the entire path was found in place of the file as shown in the output from the sample program below:

```
base = C:\Users\heath\AppData\Local\Temp\go-build2408382784\b001\exe\main.exe
dir = """", file = ""C:\\Users\\heath\\AppData\\Local\\Temp\\go-build2408382784\\b001\\exe\\main.exe""
```

On Ubuntu the content below is correct according to documentation and is what I expected:

```
base = main
dir = ""/tmp/go-build2295857948/b001/exe/"", file = ""main""
```",1,path base and path split do not properly split the file name on windows as documented       what version of go are you using   go version          go version       windows             does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env          go env  output     set     set goarch    set gobin   set gocache c  users heath appdata local go build  set goenv c  users heath appdata roaming go env  set goexe  exe  set goexperiment   set goflags   set gohostarch    set gohostos windows  set goinsecure   set gomodcache c  users heath go pkg mod  set gonoproxy   set gonosumdb   set goos windows  set gopath c  users heath go  set goprivate   set goproxy    set goroot c  program files go  set gosumdb sum golang org  set gotmpdir   set gotooldir c  program files go pkg tool windows    set govcs   set goversion        set gccgo gccgo  set ar ar  set cc gcc  set cxx g    set cgo enabled    set gomod nul  set cgo cflags  g     set cgo cppflags   set cgo cxxflags  g     set cgo fflags  g     set cgo ldflags  g     set pkg config pkg config  set gogccflags     mthreads  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map c  users heath appdata local temp go    tmp go build  gno record gcc switches            what did you do     using  path base    and  path split    on windows  i found they do not return just the file name  or directory and filename separated  as documented  they work as documented on    ubunto      however         go  package main    import         fmt        os        path        func main          fmt println  base     path base os args           dir  file    path split os args        fmt printf  dir    q  file    q n   dir  file                 what did you expect to see     i expected the file name itself to be returned from  path base   as well as the directory and file name in  dir  and  file  parameters from  path split            what did you see instead     on windows  the entire path was found in place of the file as shown in the output from the sample program below          base   c  users heath appdata local temp go     exe main exe  dir       file    c   users  heath  appdata  local  temp  go       exe  main exe          on ubuntu the content below is correct according to documentation and is what i expected          base   main  dir     tmp go     exe    file    main      ,1
351573,10520712313.0,IssuesEvent,2019-09-30 02:37:56,AY1920S1-CS2113T-W17-2/main,https://api.github.com/repos/AY1920S1-CS2113T-W17-2/main,closed,"As a user, I can list expenses so that I can see all types of expenses and the amount associated to each of them.",priority.High type.Story,Shows a detailed expense list.,1.0,"As a user, I can list expenses so that I can see all types of expenses and the amount associated to each of them. - Shows a detailed expense list.",0,as a user  i can list expenses so that i can see all types of expenses and the amount associated to each of them    shows a detailed expense list ,0
382421,11306029734.0,IssuesEvent,2020-01-18 10:51:48,RobotLocomotion/drake,https://api.github.com/repos/RobotLocomotion/drake,closed,need animate/recording feature in planar_scenegraph_visualizer for jupyter integration,priority: medium team: dynamics type: feature request,"This was discussed during the initial PR for planar_scenegraph_visualizer.  Now it has reared it's head -- I cannot yet replace my underactuated version of `planar_scenegraph_visualizer` with the drake version because I don't know how to get the jupyter workflow yet.
https://github.com/RussTedrake/underactuated/pull/244
The goal is to be able to have the pyplot output of planar_scenegraph_visualizer appear as an animation in the juypter console (as opposed to a separate window).  

Original discussion:
https://github.com/robotlocomotion/drake/pull/12218#issuecomment-550491446

After that thread, it seems that the `animate` was removed, too.  

cc @EricCousineau-TRI in case he has a different trick for integrating the pyplot animation into a jupyter notebook. 
",1.0,"need animate/recording feature in planar_scenegraph_visualizer for jupyter integration - This was discussed during the initial PR for planar_scenegraph_visualizer.  Now it has reared it's head -- I cannot yet replace my underactuated version of `planar_scenegraph_visualizer` with the drake version because I don't know how to get the jupyter workflow yet.
https://github.com/RussTedrake/underactuated/pull/244
The goal is to be able to have the pyplot output of planar_scenegraph_visualizer appear as an animation in the juypter console (as opposed to a separate window).  

Original discussion:
https://github.com/robotlocomotion/drake/pull/12218#issuecomment-550491446

After that thread, it seems that the `animate` was removed, too.  

cc @EricCousineau-TRI in case he has a different trick for integrating the pyplot animation into a jupyter notebook. 
",0,need animate recording feature in planar scenegraph visualizer for jupyter integration   this was discussed during the initial pr for planar scenegraph visualizer   now it has reared it s head    i cannot yet replace my underactuated version of  planar scenegraph visualizer  with the drake version because i don t know how to get the jupyter workflow yet      the goal is to be able to have the pyplot output of planar scenegraph visualizer appear as an animation in the juypter console  as opposed to a separate window        original discussion        after that thread  it seems that the  animate  was removed  too       cc  ericcousineau tri in case he has a different trick for integrating the pyplot animation into a jupyter notebook    ,0
331594,29044385272.0,IssuesEvent,2023-05-13 11:13:40,elastic/kibana,https://api.github.com/repos/elastic/kibana,closed,Failing test: X-Pack Case API Integration Tests.x-pack/test/cases_api_integration/security_and_spaces/tests/trial/cases/push_case·ts - cases security and spaces enabled: trial push_case memoryless server rbac User obs_only_read with role(s) obs_only_read - should NOT push a case,failed-test Team:ResponseOps,"A test failed on a tracked branch

```
Error: expected 200 ""OK"", got 403 ""Forbidden""
    at Test._assertStatus (node_modules/supertest/lib/test.js:268:12)
    at Test._assertFunction (node_modules/supertest/lib/test.js:283:11)
    at Test.assert (node_modules/supertest/lib/test.js:173:18)
    at localAssert (node_modules/supertest/lib/test.js:131:12)
    at /home/buildkite-agent/builds/kb-n2-4-spot-0431e15284df11c1/elastic/kibana-on-merge/kibana/node_modules/supertest/lib/test.js:128:5
    at Test.Request.callback (node_modules/superagent/lib/node/index.js:728:3)
    at /home/buildkite-agent/builds/kb-n2-4-spot-0431e15284df11c1/elastic/kibana-on-merge/kibana/node_modules/superagent/lib/node/index.js:916:18
    at IncomingMessage.<anonymous> (node_modules/superagent/lib/node/parsers/json.js:19:7)
    at IncomingMessage.emit (node:events:525:35)
    at endReadableNT (node:internal/streams/readable:1358:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
```

First failure: [CI Build - 8.8](https://buildkite.com/elastic/kibana-on-merge/builds/30378#01881150-c3e6-4d3d-8eb0-32da324fbeb3)

<!-- kibanaCiData = {""failed-test"":{""test.class"":""X-Pack Case API Integration Tests.x-pack/test/cases_api_integration/security_and_spaces/tests/trial/cases/push_case·ts"",""test.name"":""cases security and spaces enabled: trial push_case memoryless server rbac User obs_only_read with role(s) obs_only_read - should NOT push a case"",""test.failCount"":2}} -->",1.0,"Failing test: X-Pack Case API Integration Tests.x-pack/test/cases_api_integration/security_and_spaces/tests/trial/cases/push_case·ts - cases security and spaces enabled: trial push_case memoryless server rbac User obs_only_read with role(s) obs_only_read - should NOT push a case - A test failed on a tracked branch

```
Error: expected 200 ""OK"", got 403 ""Forbidden""
    at Test._assertStatus (node_modules/supertest/lib/test.js:268:12)
    at Test._assertFunction (node_modules/supertest/lib/test.js:283:11)
    at Test.assert (node_modules/supertest/lib/test.js:173:18)
    at localAssert (node_modules/supertest/lib/test.js:131:12)
    at /home/buildkite-agent/builds/kb-n2-4-spot-0431e15284df11c1/elastic/kibana-on-merge/kibana/node_modules/supertest/lib/test.js:128:5
    at Test.Request.callback (node_modules/superagent/lib/node/index.js:728:3)
    at /home/buildkite-agent/builds/kb-n2-4-spot-0431e15284df11c1/elastic/kibana-on-merge/kibana/node_modules/superagent/lib/node/index.js:916:18
    at IncomingMessage.<anonymous> (node_modules/superagent/lib/node/parsers/json.js:19:7)
    at IncomingMessage.emit (node:events:525:35)
    at endReadableNT (node:internal/streams/readable:1358:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
```

First failure: [CI Build - 8.8](https://buildkite.com/elastic/kibana-on-merge/builds/30378#01881150-c3e6-4d3d-8eb0-32da324fbeb3)

<!-- kibanaCiData = {""failed-test"":{""test.class"":""X-Pack Case API Integration Tests.x-pack/test/cases_api_integration/security_and_spaces/tests/trial/cases/push_case·ts"",""test.name"":""cases security and spaces enabled: trial push_case memoryless server rbac User obs_only_read with role(s) obs_only_read - should NOT push a case"",""test.failCount"":2}} -->",0,failing test  x pack case api integration tests x pack test cases api integration security and spaces tests trial cases push case·ts   cases security and spaces enabled  trial push case memoryless server rbac user obs only read with role s  obs only read   should not push a case   a test failed on a tracked branch      error  expected    ok   got    forbidden      at test  assertstatus  node modules supertest lib test js          at test  assertfunction  node modules supertest lib test js          at test assert  node modules supertest lib test js          at localassert  node modules supertest lib test js          at  home buildkite agent builds kb     spot   elastic kibana on merge kibana node modules supertest lib test js         at test request callback  node modules superagent lib node index js          at  home buildkite agent builds kb     spot   elastic kibana on merge kibana node modules superagent lib node index js         at incomingmessage    node modules superagent lib node parsers json js          at incomingmessage emit  node events          at endreadablent  node internal streams readable          at processticksandrejections  node internal process task queues           first failure        ,0
318062,23702188462.0,IssuesEvent,2022-08-29 20:08:49,golang/go,https://api.github.com/repos/golang/go,closed,testing: mention the “_test” package idiom,Documentation NeedsFix,"https://tip.golang.org/cmd/go/#hdr-Test_packages says:
> Test files that declare a package with the suffix ""_test"" will be compiled as a separate package, and then linked and run with the main test binary.

However, https://tip.golang.org/pkg/testing/ omits that detail (emphasis mine):
> To write a new test suite, create a file whose name ends _test.go that contains the TestXxx functions as described here. **Put the file in the same package as the one being tested.**

Tests in a separate `_test` package provide more realistic examples (and are better for catching awkward [package names](https://blog.golang.org/package-names)), so it's important that users be aware of that option. The `testing` package is an important entry point for users who are new to Go: its documentation should mention both package options or neither.",1.0,"testing: mention the “_test” package idiom - https://tip.golang.org/cmd/go/#hdr-Test_packages says:
> Test files that declare a package with the suffix ""_test"" will be compiled as a separate package, and then linked and run with the main test binary.

However, https://tip.golang.org/pkg/testing/ omits that detail (emphasis mine):
> To write a new test suite, create a file whose name ends _test.go that contains the TestXxx functions as described here. **Put the file in the same package as the one being tested.**

Tests in a separate `_test` package provide more realistic examples (and are better for catching awkward [package names](https://blog.golang.org/package-names)), so it's important that users be aware of that option. The `testing` package is an important entry point for users who are new to Go: its documentation should mention both package options or neither.",1,testing  mention the “ test” package idiom     says     test files that declare a package with the suffix   test  will be compiled as a separate package  and then linked and run with the main test binary     however    omits that detail  emphasis mine      to write a new test suite  create a file whose name ends  test go that contains the testxxx functions as described here    put the file in the same package as the one being tested       tests in a separate   test  package provide more realistic examples  and are better for catching awkward     so it s important that users be aware of that option  the  testing  package is an important entry point for users who are new to go  its documentation should mention both package options or neither ,1
99695,21012878747.0,IssuesEvent,2022-03-30 08:22:37,jOOQ/jOOQ,https://api.github.com/repos/jOOQ/jOOQ,closed,Invalid import generation for pojoImplements/recordImplements using regex lookahead,T: Defect C: Code Generation P: Medium E: All Editions,"The following matcher
```xml
<strategy>
    <matchers>
        <tables>
            <table>
                <expression>.*(?&lt;!_xref)</expression> // <====

                <recordImplements>mainapplication.domain.Auditable</recordImplements>
                <pojoImplements>mainapplication.domain.Auditable</pojoImplements>
            </table>
        </tables>
    </matchers>
</strategy>
```

produces

```java
package mainapplication.domain.generated.tables.pojos;


import java.io.Serializable;
import java.time.OffsetDateTime;

import mainapplication.domain.Auditablemainapplication.domain.Auditable;  // <==============


/**
 * This class is generated by jOOQ.
 */
@SuppressWarnings({ ""all"", ""unchecked"", ""rawtypes"" })
public class Company implements Auditable, Serializable {
```

Using simple OR regular expression, e.g. `company | employee` generates correct imports.

### Versions
- jOOQ: 3.16.5
",1.0,"Invalid import generation for pojoImplements/recordImplements using regex lookahead - The following matcher
```xml
<strategy>
    <matchers>
        <tables>
            <table>
                <expression>.*(?&lt;!_xref)</expression> // <====

                <recordImplements>mainapplication.domain.Auditable</recordImplements>
                <pojoImplements>mainapplication.domain.Auditable</pojoImplements>
            </table>
        </tables>
    </matchers>
</strategy>
```

produces

```java
package mainapplication.domain.generated.tables.pojos;


import java.io.Serializable;
import java.time.OffsetDateTime;

import mainapplication.domain.Auditablemainapplication.domain.Auditable;  // <==============


/**
 * This class is generated by jOOQ.
 */
@SuppressWarnings({ ""all"", ""unchecked"", ""rawtypes"" })
public class Company implements Auditable, Serializable {
```

Using simple OR regular expression, e.g. `company | employee` generates correct imports.

### Versions
- jOOQ: 3.16.5
",0,invalid import generation for pojoimplements recordimplements using regex lookahead   the following matcher     xml                                                            lt   xref                                mainapplication domain auditable                    mainapplication domain auditable                                              produces       java  package mainapplication domain generated tables pojos       import java io serializable   import java time offsetdatetime     import mainapplication domain auditablemainapplication domain auditable                                   this class is generated by jooq         suppresswarnings    all    unchecked    rawtypes      public class company implements auditable  serializable           using simple or regular expression  e g   company   employee  generates correct imports         versions    jooq         ,0
100584,16489913388.0,IssuesEvent,2021-05-25 01:09:40,szb512/vue-storefront,https://api.github.com/repos/szb512/vue-storefront,opened,CVE-2021-23383 (High) detected in handlebars-4.1.2.tgz,security vulnerability,"## CVE-2021-23383 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>handlebars-4.1.2.tgz</b></p></summary>

<p>Handlebars provides the power necessary to let you build semantic templates effectively with no frustration</p>
<p>Library home page: <a href=""https://registry.npmjs.org/handlebars/-/handlebars-4.1.2.tgz"">https://registry.npmjs.org/handlebars/-/handlebars-4.1.2.tgz</a></p>
<p>Path to dependency file: /vue-storefront/package.json</p>
<p>Path to vulnerable library: vue-storefront/node_modules/handlebars/package.json</p>
<p>

Dependency Hierarchy:
  - lerna-2.11.0.tgz (Root Library)
    - conventional-changelog-cli-1.3.22.tgz
      - conventional-changelog-1.1.24.tgz
        - conventional-changelog-core-2.0.11.tgz
          - conventional-changelog-writer-3.0.9.tgz
            - :x: **handlebars-4.1.2.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>  
  
The package handlebars before 4.7.7 are vulnerable to Prototype Pollution when selecting certain compiling options to compile templates coming from an untrusted source.

<p>Publish Date: 2021-05-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23383>CVE-2021-23383</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23383"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23383</a></p>
<p>Release Date: 2021-05-04</p>
<p>Fix Resolution: handlebars - v4.7.7</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-23383 (High) detected in handlebars-4.1.2.tgz - ## CVE-2021-23383 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>handlebars-4.1.2.tgz</b></p></summary>

<p>Handlebars provides the power necessary to let you build semantic templates effectively with no frustration</p>
<p>Library home page: <a href=""https://registry.npmjs.org/handlebars/-/handlebars-4.1.2.tgz"">https://registry.npmjs.org/handlebars/-/handlebars-4.1.2.tgz</a></p>
<p>Path to dependency file: /vue-storefront/package.json</p>
<p>Path to vulnerable library: vue-storefront/node_modules/handlebars/package.json</p>
<p>

Dependency Hierarchy:
  - lerna-2.11.0.tgz (Root Library)
    - conventional-changelog-cli-1.3.22.tgz
      - conventional-changelog-1.1.24.tgz
        - conventional-changelog-core-2.0.11.tgz
          - conventional-changelog-writer-3.0.9.tgz
            - :x: **handlebars-4.1.2.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>  
  
The package handlebars before 4.7.7 are vulnerable to Prototype Pollution when selecting certain compiling options to compile templates coming from an untrusted source.

<p>Publish Date: 2021-05-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23383>CVE-2021-23383</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23383"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23383</a></p>
<p>Release Date: 2021-05-04</p>
<p>Fix Resolution: handlebars - v4.7.7</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in handlebars       tgz      cve       high severity vulnerability     vulnerable library    handlebars       tgz      handlebars provides the power necessary to let you build semantic templates effectively with no frustration   library home page   a href     path to dependency file   vue storefront package json   path to vulnerable library  vue storefront node modules handlebars package json     dependency hierarchy      lerna       tgz  root library        conventional changelog cli       tgz         conventional changelog       tgz           conventional changelog core       tgz             conventional changelog writer       tgz                x    handlebars       tgz    vulnerable library             vulnerability details         the package handlebars before       are vulnerable to prototype pollution when selecting certain compiling options to compile templates coming from an untrusted source    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  handlebars                       step up your open source security game with whitesource    ,0
319609,23781180211.0,IssuesEvent,2022-09-02 05:06:36,golang/go,https://api.github.com/repos/golang/go,closed,math/rand: document whether NewSource always implements Source64,Documentation NeedsInvestigation,"The [concrete type returned by `NewSource` happens to implement `Source64`](https://play.golang.org/p/gxPB1je9grf). However, this is not documented in any way. Is this always guaranteed?",1.0,"math/rand: document whether NewSource always implements Source64 - The [concrete type returned by `NewSource` happens to implement `Source64`](https://play.golang.org/p/gxPB1je9grf). However, this is not documented in any way. Is this always guaranteed?",1,math rand  document whether newsource always implements     the     however  this is not documented in any way  is this always guaranteed ,1
16184,4021735968.0,IssuesEvent,2016-05-16 23:19:34,golang/go,https://api.github.com/repos/golang/go,closed,crypto/tls: document how to use intermediate certs with LoadX509KeyPair,Documentation,"Document that tls.LoadX509KeyPair's cert file include concatenated intermediate certs.

/cc @agl ",1.0,"crypto/tls: document how to use intermediate certs with LoadX509KeyPair - Document that tls.LoadX509KeyPair's cert file include concatenated intermediate certs.

/cc @agl ",1,crypto tls  document how to use intermediate certs with     document that tls   s cert file include concatenated intermediate certs      cc  agl ,1
130295,10604829044.0,IssuesEvent,2019-10-10 19:03:16,elastic/elasticsearch,https://api.github.com/repos/elastic/elasticsearch,opened,[CI] DocsClientYamlTestSuiteIT test {yaml=reference/ccr/apis/get-ccr-stats},:Distributed/CCR >docs >test-failure,"Could not reproduce locally.

Scan:
https://gradle-enterprise.elastic.co/s/sitw4mw7yks7w/tests/jbm2x6tnwtxku-5fg27oqaedztk

Failure:
```
java.lang.AssertionError: Failure at [reference/ccr/apis/auto-follow/get-auto-follow-pattern:20]: expected [2xx] status code but api [raw[method=PUT path=_ccr/auto_follow/my_auto_follow_pattern]] returned [400 Bad Request] [{""error"":{""root_cause"":[{""type"":""no_such_remote_cluster_exception"",""reason"":""no such remote cluster: [remote_cluster]""....
```",1.0,"[CI] DocsClientYamlTestSuiteIT test {yaml=reference/ccr/apis/get-ccr-stats} - Could not reproduce locally.

Scan:
https://gradle-enterprise.elastic.co/s/sitw4mw7yks7w/tests/jbm2x6tnwtxku-5fg27oqaedztk

Failure:
```
java.lang.AssertionError: Failure at [reference/ccr/apis/auto-follow/get-auto-follow-pattern:20]: expected [2xx] status code but api [raw[method=PUT path=_ccr/auto_follow/my_auto_follow_pattern]] returned [400 Bad Request] [{""error"":{""root_cause"":[{""type"":""no_such_remote_cluster_exception"",""reason"":""no such remote cluster: [remote_cluster]""....
```",0,  docsclientyamltestsuiteit test  yaml reference ccr apis get ccr stats    could not reproduce locally     scan        failure        java lang assertionerror  failure at    expected   status code but api    returned              ,0
17555,4171880676.0,IssuesEvent,2016-06-21 02:16:27,golang/go,https://api.github.com/repos/golang/go,closed,text/template: does not document how values are formatted,Documentation NeedsFix,"go version devel +3c6b668 Thu Jun 2 00:22:03 2016 +0000 linux/amd64

I may well have missed it, but text/template package doesn't seem to specify
anywhere how values are actually displayed. For example, by reading the
documentation, it's not clear whether a value's String method will be called
to produce text to display in the template.
",1.0,"text/template: does not document how values are formatted - go version devel +3c6b668 Thu Jun 2 00:22:03 2016 +0000 linux/amd64

I may well have missed it, but text/template package doesn't seem to specify
anywhere how values are actually displayed. For example, by reading the
documentation, it's not clear whether a value's String method will be called
to produce text to display in the template.
",1,text template  does not document how values are formatted   go version devel    thu jun              linux      i may well have missed it  but text template package doesn t seem to specify  anywhere how values are actually displayed  for example  by reading the  documentation  it s not clear whether a value s string method will be called  to produce text to display in the template   ,1
108665,11597860719.0,IssuesEvent,2020-02-24 21:46:09,golang/go,https://api.github.com/repos/golang/go,closed,DocumentSymbols failed: getting file for DocumentSymbols: context canceled,Documentation,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.13.4 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env

GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""/Users/steele/go/bin""
GOCACHE=""/Users/steele/Library/Caches/go-build""
GOENV=""/Users/steele/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/steele/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/steele/conversion-service/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/m7/ks10ly_j20g2tphn554wvdcm0000gn/T/go-build947817871=/tmp/go-build -gno-record-gcc-switches -fno-common""

</pre></details>

### What did you do?

Loaded up my workspace after working in Python for a while only to notice that I wasn't getting any language server feedback anymore. 

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

Not sure if providing repo steps is possible...

### What did you expect to see?

Language server works. 

### What did you see instead?

```
[Info  - 1:12:49 PM] 2020/02/24 13:12:49 go/packages.Load
	snapshot = 0
	query = [./... builtin]
	packages = 2
2020/02/24 13:12:50 DocumentSymbols failed: getting file for DocumentSymbols: context canceled
	URI = file:///Users/steele/conversion-service/internal/svc/service.go
2020/02/24 13:12:50 : context canceled
[Error - 1:12:50 PM] 2020/02/24 13:12:50 : context canceled
```
",1.0,"DocumentSymbols failed: getting file for DocumentSymbols: context canceled - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.13.4 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env

GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""/Users/steele/go/bin""
GOCACHE=""/Users/steele/Library/Caches/go-build""
GOENV=""/Users/steele/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/steele/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/steele/conversion-service/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/m7/ks10ly_j20g2tphn554wvdcm0000gn/T/go-build947817871=/tmp/go-build -gno-record-gcc-switches -fno-common""

</pre></details>

### What did you do?

Loaded up my workspace after working in Python for a while only to notice that I wasn't getting any language server feedback anymore. 

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

Not sure if providing repo steps is possible...

### What did you expect to see?

Language server works. 

### What did you see instead?

```
[Info  - 1:12:49 PM] 2020/02/24 13:12:49 go/packages.Load
	snapshot = 0
	query = [./... builtin]
	packages = 2
2020/02/24 13:12:50 DocumentSymbols failed: getting file for DocumentSymbols: context canceled
	URI = file:///Users/steele/conversion-service/internal/svc/service.go
2020/02/24 13:12:50 : context canceled
[Error - 1:12:50 PM] 2020/02/24 13:12:50 : context canceled
```
",1,documentsymbols failed  getting file for documentsymbols  context canceled         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version            go version  go version       darwin             does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env          go env  output       go env          goarch      gobin   users steele go bin   gocache   users steele library caches go build   goenv   users steele library application support go env   goexe     goflags     gohostarch      gohostos  darwin   gonoproxy     gonosumdb     goos  darwin   gopath   users steele go   goprivate     goproxy     goroot   usr local go   gosumdb  sum golang org   gotmpdir     gotooldir   usr local go pkg tool darwin     gccgo  gccgo   ar  ar   cc  clang   cxx  clang     cgo enabled      gomod   users steele conversion service go mod   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders       t go    tmp go build  gno record gcc switches  fno common               what did you do     loaded up my workspace after working in python for a while only to notice that i wasn t getting any language server feedback anymore            if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best          not sure if providing repo steps is possible           what did you expect to see     language server works          what did you see instead                        go packages load  	snapshot      	query      	packages                  documentsymbols failed  getting file for documentsymbols  context canceled  	uri   file    users steele conversion service internal svc service go                context canceled                  context canceled       ,1
216975,16675970108.0,IssuesEvent,2021-06-07 16:12:58,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.17: document crypto/rsa changes for Go 1.17,Documentation NeedsInvestigation help wanted release-blocker,"As of filing this issue, the [Go 1.17 draft release notes](https://tip.golang.org/doc/go1.17) contained the following HTML:

<dl id=""crypto/rsa""><dt><a href=""/pkg/crypto/rsa/"">crypto/rsa</a></dt>
  <dd>
    <p><!-- CL 302230 -->
      TODO: <a href=""https://golang.org/cl/302230"">https://golang.org/cl/302230</a>: fix salt length calculation with PSSSaltLengthAuto
    </p>
  </dd>
</dl>

---

This TODO needs to be resolved by July 1 so that we can have complete release notes for [Beta 1](https://golang.org/s/release#june-1--december-1-beta-1-issued).

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.17:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.17) and include ""For #44513. Fixes #46006."" in the body.",1.0,"doc/go1.17: document crypto/rsa changes for Go 1.17 - As of filing this issue, the [Go 1.17 draft release notes](https://tip.golang.org/doc/go1.17) contained the following HTML:

<dl id=""crypto/rsa""><dt><a href=""/pkg/crypto/rsa/"">crypto/rsa</a></dt>
  <dd>
    <p><!-- CL 302230 -->
      TODO: <a href=""https://golang.org/cl/302230"">https://golang.org/cl/302230</a>: fix salt length calculation with PSSSaltLengthAuto
    </p>
  </dd>
</dl>

---

This TODO needs to be resolved by July 1 so that we can have complete release notes for [Beta 1](https://golang.org/s/release#june-1--december-1-beta-1-issued).

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.17:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.17) and include ""For #44513. Fixes #46006."" in the body.",1,doc      document crypto rsa changes for go       as of filing this issue  the     contained the following html      crypto rsa                    todo   a href    fix salt length calculation with psssaltlengthauto                   this todo needs to be resolved by july   so that we can have complete release notes for      a sequence of steps to resolve this issue may be      come up with a draft release note entry in this issue  then move the issue to needsfix state     send a cl with  doc           and include  for     fixes      in the body ,1
10738,3421599676.0,IssuesEvent,2015-12-08 19:26:49,golang/go,https://api.github.com/repos/golang/go,closed,"encoding/json: Indent is documented to ""have no trailing newline"", yet it sometimes does.",Documentation,"Tested with `go version go1.5.2 darwin/amd64`.

I'm reading the documentation for `json.Indent`:

https://godoc.org/encoding/json#Indent

Specifically, this part:

> The data appended to dst does not begin with the prefix nor any indentation, and **has no trailing newline**, to make it easier to embed inside other formatted JSON data.

But that doesn't always seem to be the case. Depending on whether the input has a trailing newline, so does the output. Here's a quick reproduce program:

https://play.golang.org/p/bSoN4Tl2q_

If I understood the documentation and the output correctly, does this mean there's a bug in `json.Indent`?

**Edit:** Sorry, I accidentally used the word ""encode"" a few times instead of ""indent"". That was a typo, now fixed.",1.0,"encoding/json: Indent is documented to ""have no trailing newline"", yet it sometimes does. - Tested with `go version go1.5.2 darwin/amd64`.

I'm reading the documentation for `json.Indent`:

https://godoc.org/encoding/json#Indent

Specifically, this part:

> The data appended to dst does not begin with the prefix nor any indentation, and **has no trailing newline**, to make it easier to embed inside other formatted JSON data.

But that doesn't always seem to be the case. Depending on whether the input has a trailing newline, so does the output. Here's a quick reproduce program:

https://play.golang.org/p/bSoN4Tl2q_

If I understood the documentation and the output correctly, does this mean there's a bug in `json.Indent`?

**Edit:** Sorry, I accidentally used the word ""encode"" a few times instead of ""indent"". That was a typo, now fixed.",1,encoding json  indent is documented to  have no trailing newline   yet it sometimes does    tested with  go version       darwin        i m reading the documentation for  json indent           specifically  this part       the data appended to dst does not begin with the prefix nor any indentation  and   has no trailing newline    to make it easier to embed inside other formatted json data     but that doesn t always seem to be the case  depending on whether the input has a trailing newline  so does the output  here s a quick reproduce program          if i understood the documentation and the output correctly  does this mean there s a bug in  json indent        edit    sorry  i accidentally used the word  encode  a few times instead of  indent   that was a typo  now fixed ,1
34832,6383544013.0,IssuesEvent,2017-08-03 00:43:11,golang/go,https://api.github.com/repos/golang/go,closed,"net: update documentation, example for error values",Documentation NeedsFix,"Suggested in a review of net: fix inconsistent errors (https://go-review.googlesource.com/#/c/9236/):

In a different CL, could you write some documentation about what kinds of errors people can expect, and perhaps an Example function showing how to work with them? See https://groups.google.com/d/msg/golang-nuts/iNVNBXdZK8Q/irnIrgLD2q4J for the kinds of issues programmers want to understand.
",1.0,"net: update documentation, example for error values - Suggested in a review of net: fix inconsistent errors (https://go-review.googlesource.com/#/c/9236/):

In a different CL, could you write some documentation about what kinds of errors people can expect, and perhaps an Example function showing how to work with them? See https://groups.google.com/d/msg/golang-nuts/iNVNBXdZK8Q/irnIrgLD2q4J for the kinds of issues programmers want to understand.
",1,net  update documentation  example for error values   suggested in a review of net  fix inconsistent errors     in a different cl  could you write some documentation about what kinds of errors people can expect  and perhaps an example function showing how to work with them  see   for the kinds of issues programmers want to understand  ,1
89837,10617592492.0,IssuesEvent,2019-10-12 20:13:29,golang/go,https://api.github.com/repos/golang/go,closed,doc:,Documentation,It would be nice for the JSON mode of golang.org/dl to be documented somewhere. I wasn't able to find it until after I built a project to recreate the same functionality and someone pointed it out.,1.0,doc: - It would be nice for the JSON mode of golang.org/dl to be documented somewhere. I wasn't able to find it until after I built a project to recreate the same functionality and someone pointed it out.,1,doc    it would be nice for the json mode of golang org dl to be documented somewhere  i wasn t able to find it until after i built a project to recreate the same functionality and someone pointed it out ,1
734363,25346359598.0,IssuesEvent,2022-11-19 08:33:08,googleapis/nodejs-ai-platform,https://api.github.com/repos/googleapis/nodejs-ai-platform,opened,AI platform create training pipeline tabular regression: should create a new tabular regression training pipeline failed,type: bug priority: p1 flakybot: issue,"Note: #408 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.

----

commit: 04f7c858217f1a3ce7b1072c7bf8946d39947532
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/2c1b5aae-a46c-4a7a-a474-79da01e686eb), [Sponge](http://sponge2/2c1b5aae-a46c-4a7a-a474-79da01e686eb)
status: failed
<details><summary>Test output</summary><br><pre>Command failed: node ./create-training-pipeline-tabular-regression.js                                             3019804287640272896                                             temp_create_training_pipeline_tables_regression_model_testc9e24b6b-8fee-4739-a624-90e2eae5917b                                             temp_create_training_pipeline_tables_regression_test_9a0bde68-989c-456a-a9c8-49ee1fb4965d                                             FLOAT_5000unique_REQUIRED                                             undefined us-central1
7 PERMISSION_DENIED: Permission denied: Consumer 'project:undefined' has been suspended.

Error: Command failed: node ./create-training-pipeline-tabular-regression.js                                             3019804287640272896                                             temp_create_training_pipeline_tables_regression_model_testc9e24b6b-8fee-4739-a624-90e2eae5917b                                             temp_create_training_pipeline_tables_regression_test_9a0bde68-989c-456a-a9c8-49ee1fb4965d                                             FLOAT_5000unique_REQUIRED                                             undefined us-central1
7 PERMISSION_DENIED: Permission denied: Consumer 'project:undefined' has been suspended.

    at checkExecSyncError (child_process.js:635:11)
    at Object.execSync (child_process.js:671:15)
    at execSync (test/create-training-pipeline-tabular-regression.test.js:25:28)
    at Context.<anonymous> (test/create-training-pipeline-tabular-regression.test.js:49:20)
    at processImmediate (internal/timers.js:461:21)</pre></details>",1.0,"AI platform create training pipeline tabular regression: should create a new tabular regression training pipeline failed - Note: #408 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.

----

commit: 04f7c858217f1a3ce7b1072c7bf8946d39947532
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/2c1b5aae-a46c-4a7a-a474-79da01e686eb), [Sponge](http://sponge2/2c1b5aae-a46c-4a7a-a474-79da01e686eb)
status: failed
<details><summary>Test output</summary><br><pre>Command failed: node ./create-training-pipeline-tabular-regression.js                                             3019804287640272896                                             temp_create_training_pipeline_tables_regression_model_testc9e24b6b-8fee-4739-a624-90e2eae5917b                                             temp_create_training_pipeline_tables_regression_test_9a0bde68-989c-456a-a9c8-49ee1fb4965d                                             FLOAT_5000unique_REQUIRED                                             undefined us-central1
7 PERMISSION_DENIED: Permission denied: Consumer 'project:undefined' has been suspended.

Error: Command failed: node ./create-training-pipeline-tabular-regression.js                                             3019804287640272896                                             temp_create_training_pipeline_tables_regression_model_testc9e24b6b-8fee-4739-a624-90e2eae5917b                                             temp_create_training_pipeline_tables_regression_test_9a0bde68-989c-456a-a9c8-49ee1fb4965d                                             FLOAT_5000unique_REQUIRED                                             undefined us-central1
7 PERMISSION_DENIED: Permission denied: Consumer 'project:undefined' has been suspended.

    at checkExecSyncError (child_process.js:635:11)
    at Object.execSync (child_process.js:671:15)
    at execSync (test/create-training-pipeline-tabular-regression.test.js:25:28)
    at Context.<anonymous> (test/create-training-pipeline-tabular-regression.test.js:49:20)
    at processImmediate (internal/timers.js:461:21)</pre></details>",0,ai platform create training pipeline tabular regression  should create a new tabular regression training pipeline 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   command failed  node   create training pipeline tabular regression js                                                                                           temp create training pipeline tables regression model                                                       temp create training pipeline tables regression test                                                       float   required                                             undefined us     permission denied  permission denied  consumer  project undefined  has been suspended   error  command failed  node   create training pipeline tabular regression js                                                                                           temp create training pipeline tables regression model                                                       temp create training pipeline tables regression test                                                       float   required                                             undefined us     permission denied  permission denied  consumer  project undefined  has been suspended       at checkexecsyncerror  child process js          at object execsync  child process js          at execsync  test create training pipeline tabular regression test js          at context    test create training pipeline tabular regression test js          at processimmediate  internal timers js       ,0
735392,25393802121.0,IssuesEvent,2022-11-22 06:53:33,webcompat/web-bugs,https://api.github.com/repos/webcompat/web-bugs,closed,www.xfinity.com - site is not usable,browser-firefox priority-important engine-gecko,"<!-- @browser: Firefox 108.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:108.0) Gecko/20100101 Firefox/108.0 -->
<!-- @reported_with: unknown -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/114442 -->

**URL**: https://www.xfinity.com/stream/

**Browser / Version**: Firefox 108.0
**Operating System**: Windows 10
**Tested Another Browser**: Yes Edge

**Problem type**: Site is not usable
**Description**: Page not loading correctly
**Steps to Reproduce**:
This site does not load on Firefox, but does load with Edge. This occurred with the lastest update of Firefox 108

<details>
<summary>Browser Configuration</summary>
<ul>
  <li>None</li>
</ul>
</details>

_From [webcompat.com](https://webcompat.com/) with ❤️_",1.0,"www.xfinity.com - site is not usable - <!-- @browser: Firefox 108.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:108.0) Gecko/20100101 Firefox/108.0 -->
<!-- @reported_with: unknown -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/114442 -->

**URL**: https://www.xfinity.com/stream/

**Browser / Version**: Firefox 108.0
**Operating System**: Windows 10
**Tested Another Browser**: Yes Edge

**Problem type**: Site is not usable
**Description**: Page not loading correctly
**Steps to Reproduce**:
This site does not load on Firefox, but does load with Edge. This occurred with the lastest update of Firefox 108

<details>
<summary>Browser Configuration</summary>
<ul>
  <li>None</li>
</ul>
</details>

_From [webcompat.com](https://webcompat.com/) with ❤️_",0,    site is not usable              url         browser   version    firefox       operating system    windows     tested another browser    yes edge    problem type    site is not usable   description    page not loading correctly   steps to reproduce    this site does not load on firefox  but does load with edge  this occurred with the lastest update of firefox       browser configuration       none        from     with ❤️ ,0
41520,6916581309.0,IssuesEvent,2017-11-29 03:25:35,golang/go,https://api.github.com/repos/golang/go,closed,faq: document why there is no way to get a goroutine ID,Documentation,"We've deliberately decided that there should be no way to get a goroutine ID, and there is no goroutine local storage.  Since this comes up from time to time, we should add the explanation to the FAQ.

Here is an explanation I just wrote which may serve as a starting point:

It's because Go makes it cheap to start new goroutines, and it is normal in Go for a single task to be implemented by a collection of goroutines.  Some of those goroutines may be newly started, some may be long running goroutines that provide some service.  Of course one must aggregate log entries and other information for a single task, but because multiple goroutines are routinely involved in performing a single task, using a goroutine ID is the wrong approach.  It is a temptation that one may naturally reach for when starting to write a program that uses a single goroutine, but that then breaks as the program evolves to use multiple goroutines.  Just as Go prohibits things like unused imports, it prohibits this temptation.  The intent is to force you to start writing your program the way it is going to wind up anyhow.

There are obviously many other approaches and the point is that they work with multiple goroutines and they are explicit in the program source rather than implicit in the program execution.",1.0,"faq: document why there is no way to get a goroutine ID - We've deliberately decided that there should be no way to get a goroutine ID, and there is no goroutine local storage.  Since this comes up from time to time, we should add the explanation to the FAQ.

Here is an explanation I just wrote which may serve as a starting point:

It's because Go makes it cheap to start new goroutines, and it is normal in Go for a single task to be implemented by a collection of goroutines.  Some of those goroutines may be newly started, some may be long running goroutines that provide some service.  Of course one must aggregate log entries and other information for a single task, but because multiple goroutines are routinely involved in performing a single task, using a goroutine ID is the wrong approach.  It is a temptation that one may naturally reach for when starting to write a program that uses a single goroutine, but that then breaks as the program evolves to use multiple goroutines.  Just as Go prohibits things like unused imports, it prohibits this temptation.  The intent is to force you to start writing your program the way it is going to wind up anyhow.

There are obviously many other approaches and the point is that they work with multiple goroutines and they are explicit in the program source rather than implicit in the program execution.",1,faq  document why there is no way to get a goroutine id   we ve deliberately decided that there should be no way to get a goroutine id  and there is no goroutine local storage   since this comes up from time to time  we should add the explanation to the faq     here is an explanation i just wrote which may serve as a starting point     it s because go makes it cheap to start new goroutines  and it is normal in go for a single task to be implemented by a collection of goroutines   some of those goroutines may be newly started  some may be long running goroutines that provide some service   of course one must aggregate log entries and other information for a single task  but because multiple goroutines are routinely involved in performing a single task  using a goroutine id is the wrong approach   it is a temptation that one may naturally reach for when starting to write a program that uses a single goroutine  but that then breaks as the program evolves to use multiple goroutines   just as go prohibits things like unused imports  it prohibits this temptation   the intent is to force you to start writing your program the way it is going to wind up anyhow     there are obviously many other approaches and the point is that they work with multiple goroutines and they are explicit in the program source rather than implicit in the program execution ,1
132994,12529201557.0,IssuesEvent,2020-06-04 10:54:18,golang/go,https://api.github.com/repos/golang/go,closed,io/ioutil: docs for WriteFile should make it clear that it does not change permissions,Documentation WaitingForInfo,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.13.1 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/andrew/.cache/go-build""
GOENV=""/home/andrew/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/andrew/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/lib/go-1.13""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/lib/go-1.13/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/andrew/go/src/code.gitea.io/gitea/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build028639981=/tmp/go-build -gno-record-gcc-switches""

</pre></details>

### What did you do?

Say you had `some-extant-file` with mode 0644 and you run:

```go
ioutil.WriteFile(""some-extant-file"", []byte(""new data""), 0777)
```

### What did you expect to see?

From a cursory glance of the documentation you would expect that the mode of `some-extant-file` would change to 0777.

### What did you see instead?

It doesn't change mode - as is implied by the documentation saying it ""truncates the file""

I think the documentation for `ioutil.WriteFile` should be clearer that when the file is already extant its mode will not change. This is implied by the current documentation, but it is subtle and a quick review of the docs will lead to and has led to developers & reviewers missing this important note causing bugs.",1.0,"io/ioutil: docs for WriteFile should make it clear that it does not change permissions - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.13.1 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/andrew/.cache/go-build""
GOENV=""/home/andrew/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/andrew/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/lib/go-1.13""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/lib/go-1.13/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/andrew/go/src/code.gitea.io/gitea/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build028639981=/tmp/go-build -gno-record-gcc-switches""

</pre></details>

### What did you do?

Say you had `some-extant-file` with mode 0644 and you run:

```go
ioutil.WriteFile(""some-extant-file"", []byte(""new data""), 0777)
```

### What did you expect to see?

From a cursory glance of the documentation you would expect that the mode of `some-extant-file` would change to 0777.

### What did you see instead?

It doesn't change mode - as is implied by the documentation saying it ""truncates the file""

I think the documentation for `ioutil.WriteFile` should be clearer that when the file is already extant its mode will not change. This is implied by the current documentation, but it is subtle and a quick review of the docs will lead to and has led to developers & reviewers missing this important note causing bugs.",1,io ioutil  docs for writefile should make it clear that it does not change permissions            what version of go are you using   go version            go version  go version       linux             does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   home andrew  cache go build   goenv   home andrew  config go env   goexe     goflags     gohostarch      gohostos  linux   gonoproxy     gonosumdb     goos  linux   gopath   home andrew go   goprivate     goproxy     goroot   usr lib go       gosumdb  sum golang org   gotmpdir     gotooldir   usr lib go     pkg tool linux     gccgo  gccgo   ar  ar   cc  gcc   cxx  g     cgo enabled      gomod   home andrew go src code gitea io gitea go mod   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches               what did you do     say you had  some extant file  with mode   and you run        go  ioutil writefile  some extant file    byte  new data                   what did you expect to see     from a cursory glance of the documentation you would expect that the mode of  some extant file  would change to           what did you see instead     it doesn t change mode   as is implied by the documentation saying it  truncates the file     i think the documentation for  ioutil writefile  should be clearer that when the file is already extant its mode will not change  this is implied by the current documentation  but it is subtle and a quick review of the docs will lead to and has led to developers   reviewers missing this important note causing bugs ,1
141144,18949104681.0,IssuesEvent,2021-11-18 13:29:06,paulius-valiunas/dotenv-expand,https://api.github.com/repos/paulius-valiunas/dotenv-expand,opened,CVE-2020-28500 (Medium) detected in lodash-4.17.15.tgz,security vulnerability,"## CVE-2020-28500 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-4.17.15.tgz</b></p></summary>

<p>Lodash modular utilities.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz"">https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz</a></p>
<p>Path to dependency file: dotenv-expand/package.json</p>
<p>Path to vulnerable library: dotenv-expand/node_modules/lodash/package.json</p>
<p>

Dependency Hierarchy:
  - lab-13.1.0.tgz (Root Library)
    - eslint-3.19.0.tgz
      - :x: **lodash-4.17.15.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/paulius-valiunas/dotenv-expand/commit/76f2af744d235e83423a6b3d04a4f551c958641e"">76f2af744d235e83423a6b3d04a4f551c958641e</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>  
  
Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions.

<p>Publish Date: 2021-02-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28500>CVE-2020-28500</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28500"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28500</a></p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution: lodash-4.17.21</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":false,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""lodash"",""packageVersion"":""4.17.15"",""packageFilePaths"":[""/package.json""],""isTransitiveDependency"":true,""dependencyTree"":""lab:13.1.0;eslint:3.19.0;lodash:4.17.15"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""lodash-4.17.21""}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""CVE-2020-28500"",""vulnerabilityDetails"":""Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28500"",""cvss3Severity"":""medium"",""cvss3Score"":""5.3"",""cvss3Metrics"":{""A"":""Low"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""None"",""AV"":""Network"",""I"":""None""},""extraData"":{}}</REMEDIATE> -->",True,"CVE-2020-28500 (Medium) detected in lodash-4.17.15.tgz - ## CVE-2020-28500 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-4.17.15.tgz</b></p></summary>

<p>Lodash modular utilities.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz"">https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz</a></p>
<p>Path to dependency file: dotenv-expand/package.json</p>
<p>Path to vulnerable library: dotenv-expand/node_modules/lodash/package.json</p>
<p>

Dependency Hierarchy:
  - lab-13.1.0.tgz (Root Library)
    - eslint-3.19.0.tgz
      - :x: **lodash-4.17.15.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/paulius-valiunas/dotenv-expand/commit/76f2af744d235e83423a6b3d04a4f551c958641e"">76f2af744d235e83423a6b3d04a4f551c958641e</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>  
  
Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions.

<p>Publish Date: 2021-02-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28500>CVE-2020-28500</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28500"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28500</a></p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution: lodash-4.17.21</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":false,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""lodash"",""packageVersion"":""4.17.15"",""packageFilePaths"":[""/package.json""],""isTransitiveDependency"":true,""dependencyTree"":""lab:13.1.0;eslint:3.19.0;lodash:4.17.15"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""lodash-4.17.21""}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""CVE-2020-28500"",""vulnerabilityDetails"":""Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28500"",""cvss3Severity"":""medium"",""cvss3Score"":""5.3"",""cvss3Metrics"":{""A"":""Low"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""None"",""AV"":""Network"",""I"":""None""},""extraData"":{}}</REMEDIATE> -->",0,cve      medium  detected in lodash       tgz      cve       medium severity vulnerability     vulnerable library    lodash       tgz      lodash modular utilities    library home page   a href     path to dependency file  dotenv expand package json   path to vulnerable library  dotenv expand node modules lodash package json     dependency hierarchy      lab       tgz  root library        eslint       tgz          x    lodash       tgz    vulnerable library   found in head commit   a href     found in base branch   master              vulnerability details         lodash versions prior to       are vulnerable to regular expression denial of service  redos  via the tonumber  trim and trimend functions    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  low   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  lodash                    isopenpronvulnerability  false  ispackagebased  true  isdefaultbranch  true  packages     istransitivedependency  true  dependencytree   lab       eslint       lodash         isminimumfixversionavailable  true  minimumfixversion   lodash           basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   lodash versions prior to       are vulnerable to regular expression denial of service  redos  via the tonumber  trim and trimend functions    vulnerabilityurl        ,0
273680,20811898403.0,IssuesEvent,2022-03-18 04:24:06,golang/go,https://api.github.com/repos/golang/go,closed,spec: document interface satisfaction more explicitly,Documentation,"<pre><a href=""http://golang.org/ref/spec#Interface_types"">http://golang.org/ref/spec#Interface_types</a> does not clearly spell out the requirements
for a type to implement an interface. It should.</pre>
",1.0,"spec: document interface satisfaction more explicitly - <pre><a href=""http://golang.org/ref/spec#Interface_types"">http://golang.org/ref/spec#Interface_types</a> does not clearly spell out the requirements
for a type to implement an interface. It should.</pre>
",1,spec  document interface satisfaction more explicitly     a href    does not clearly spell out the requirements for a type to implement an interface  it should   ,1
184289,6711808777.0,IssuesEvent,2017-10-13 06:35:31,request-factory/request-factory,https://api.github.com/repos/request-factory/request-factory,closed,Request headers/parameters screen,priority:P1 type:feature,"Includes issues:
#11 Add ability to add parameters to body of appropriate requests
#12 As a user I want to be able to easily add request parameters
#21 As a user I would like to set request headers",1.0,"Request headers/parameters screen - Includes issues:
#11 Add ability to add parameters to body of appropriate requests
#12 As a user I want to be able to easily add request parameters
#21 As a user I would like to set request headers",0,request headers parameters screen   includes issues      add ability to add parameters to body of appropriate requests     as a user i want to be able to easily add request parameters     as a user i would like to set request headers,0
372235,11011351304.0,IssuesEvent,2019-12-04 16:09:08,bbc/simorgh,https://api.github.com/repos/bbc/simorgh,closed,AV on AMP pages fails when going direct to `.amp`,Refinement Needed articles-av-epic articles-features-stream bug high priority ws-media- LiveRadioV1 ws-media-stream,"**Note: AMP tests have been disabled due to this bug causing the cypress tests to fail**

These PRs should be reverted as part of closing this issue:

- https://github.com/bbc/simorgh/pull/4591
- https://github.com/bbc/simorgh/pull/4599

**Describe the bug**
AV content on TEST for AMP page fails based on:
```
Origin of <amp-iframe> must not be equal to container  
<amp-iframe 
  sandbox=​""allow-scripts allow-same-origin"" 
  layout=​""fill"" frameborder=​""0"" 
  src=​""/​ws/​av-embeds/​media/​bbc_korean_radio/​liveradio"" 
  allowfullscreen=​""true"" 
  class=​""i-amphtml-element i-amphtml-layout-fill i-amphtml-layout-size-defined i-amphtml-error i-amphtml-layout"" 
  i-amphtml-layout=​""fill"" 
  style=​""--loader-delay-offset:​48ms !important;​"">
    ​…
​</amp-iframe>​ 
if allow-same-origin is set. See https://github.com/ampproject/amphtml/blob/master/spec/amp-iframe-origin-policy.md for details.
```

**Please note AV playback works when the page is served from AMP cache as the CDN domain is a different domain to `bbc.com`. This only fails when hitting `www.bbc.com/{service}/{assetId}.amp` directly which isn't a real user journey for the audience.**

**To Reproduce**
Steps to reproduce the behavior:

1. Go to https://www.test.bbc.com/korean/bbc_korean_radio/liveradio.amp
2. Open the console
3. See error

1. Go to https://www.test.bbc.co.uk/news/articles/c3wmq4d1y3wo.amp
2. Open the console
3. See error

**Expected behavior**
The AV content on TEST should have valid playback and no errors should appearing in the console. 

**Screenshots**
![image](https://user-images.githubusercontent.com/7791726/65610921-f8507400-dfa9-11e9-86d1-c0d371ee8dcb.png)
![image](https://user-images.githubusercontent.com/7791726/65610933-fe465500-dfa9-11e9-88f7-217fc207f10a.png)

**Testing notes**
Once fix is promoted to TEST ensure AV content plays back on AMP pages.

- [x] This bug fix is expected to need manual testing.

**Additional context**
https://github.com/ampproject/amphtml/blob/master/spec/amp-iframe-origin-policy.md
",1.0,"AV on AMP pages fails when going direct to `.amp` - **Note: AMP tests have been disabled due to this bug causing the cypress tests to fail**

These PRs should be reverted as part of closing this issue:

- https://github.com/bbc/simorgh/pull/4591
- https://github.com/bbc/simorgh/pull/4599

**Describe the bug**
AV content on TEST for AMP page fails based on:
```
Origin of <amp-iframe> must not be equal to container  
<amp-iframe 
  sandbox=​""allow-scripts allow-same-origin"" 
  layout=​""fill"" frameborder=​""0"" 
  src=​""/​ws/​av-embeds/​media/​bbc_korean_radio/​liveradio"" 
  allowfullscreen=​""true"" 
  class=​""i-amphtml-element i-amphtml-layout-fill i-amphtml-layout-size-defined i-amphtml-error i-amphtml-layout"" 
  i-amphtml-layout=​""fill"" 
  style=​""--loader-delay-offset:​48ms !important;​"">
    ​…
​</amp-iframe>​ 
if allow-same-origin is set. See https://github.com/ampproject/amphtml/blob/master/spec/amp-iframe-origin-policy.md for details.
```

**Please note AV playback works when the page is served from AMP cache as the CDN domain is a different domain to `bbc.com`. This only fails when hitting `www.bbc.com/{service}/{assetId}.amp` directly which isn't a real user journey for the audience.**

**To Reproduce**
Steps to reproduce the behavior:

1. Go to https://www.test.bbc.com/korean/bbc_korean_radio/liveradio.amp
2. Open the console
3. See error

1. Go to https://www.test.bbc.co.uk/news/articles/c3wmq4d1y3wo.amp
2. Open the console
3. See error

**Expected behavior**
The AV content on TEST should have valid playback and no errors should appearing in the console. 

**Screenshots**
![image](https://user-images.githubusercontent.com/7791726/65610921-f8507400-dfa9-11e9-86d1-c0d371ee8dcb.png)
![image](https://user-images.githubusercontent.com/7791726/65610933-fe465500-dfa9-11e9-88f7-217fc207f10a.png)

**Testing notes**
Once fix is promoted to TEST ensure AV content plays back on AMP pages.

- [x] This bug fix is expected to need manual testing.

**Additional context**
https://github.com/ampproject/amphtml/blob/master/spec/amp-iframe-origin-policy.md
",0,av on amp pages fails when going direct to   amp      note  amp tests have been disabled due to this bug causing the cypress tests to fail      these prs should be reverted as part of closing this issue                   describe the bug    av content on test for amp page fails based on        origin of   must not be equal to container     amp iframe     sandbox ​ allow scripts allow same origin      layout ​ fill  frameborder ​        src ​  ​ws ​av embeds ​media ​bbc korean radio ​liveradio      allowfullscreen ​ true      class ​ i amphtml element i amphtml layout fill i amphtml layout size defined i amphtml error i amphtml layout      i amphtml layout ​ fill      style ​   loader delay offset ​   important ​        ​…  ​ ​   if allow same origin is set  see   for details            please note av playback works when the page is served from amp cache as the cdn domain is a different domain to  bbc com   this only fails when hitting    directly which isn t a real user journey for the audience         to reproduce    steps to reproduce the behavior        go to       open the console     see error       go to       open the console     see error      expected behavior    the av content on test should have valid playback and no errors should appearing in the console        screenshots                    testing notes    once fix is promoted to test ensure av content plays back on amp pages         this bug fix is expected to need manual testing       additional context       ,0
42883,12958897989.0,IssuesEvent,2020-07-20 12:10:08,mdsaj/LP-AngularSpring,https://api.github.com/repos/mdsaj/LP-AngularSpring,closed,CVE-2020-10683 (High) detected in dom4j-2.1.1.jar,security vulnerability,"## CVE-2020-10683 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>dom4j-2.1.1.jar</b></p></summary>

<p>flexible XML framework for Java</p>
<p>Library home page: <a href=""http://dom4j.github.io/"">http://dom4j.github.io/</a></p>
<p>Path to dependency file: /tmp/ws-scm/LP-AngularSpring/AngularSpring/bin/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/org/dom4j/dom4j/2.1.1/dom4j-2.1.1.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-starter-data-jpa-2.1.1.RELEASE.jar (Root Library)
    - hibernate-core-5.3.7.Final.jar
      - :x: **dom4j-2.1.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/mdsaj/LP-AngularSpring/commit/4e7f828d4ba904c93c26ef7d7af0f753a3c44a38"">4e7f828d4ba904c93c26ef7d7af0f753a3c44a38</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
dom4j before 2.1.3 allows external DTDs and External Entities by default, which might enable XXE attacks. However, there is popular external documentation from OWASP showing how to enable the safe, non-default behavior in any application that uses dom4j.

<p>Publish Date: 2020-05-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-10683>CVE-2020-10683</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/dom4j/dom4j/tree/version-2.1.3,https://github.com/dom4j/dom4j/tree/version-2.0.3"">https://github.com/dom4j/dom4j/tree/version-2.1.3,https://github.com/dom4j/dom4j/tree/version-2.0.3</a></p>
<p>Release Date: 2020-05-01</p>
<p>Fix Resolution: org.dom4j:dom4j:2.1.3,org.dom4j:dom4j:2.0.3</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2020-10683 (High) detected in dom4j-2.1.1.jar - ## CVE-2020-10683 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>dom4j-2.1.1.jar</b></p></summary>

<p>flexible XML framework for Java</p>
<p>Library home page: <a href=""http://dom4j.github.io/"">http://dom4j.github.io/</a></p>
<p>Path to dependency file: /tmp/ws-scm/LP-AngularSpring/AngularSpring/bin/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/org/dom4j/dom4j/2.1.1/dom4j-2.1.1.jar</p>
<p>

Dependency Hierarchy:
  - spring-boot-starter-data-jpa-2.1.1.RELEASE.jar (Root Library)
    - hibernate-core-5.3.7.Final.jar
      - :x: **dom4j-2.1.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/mdsaj/LP-AngularSpring/commit/4e7f828d4ba904c93c26ef7d7af0f753a3c44a38"">4e7f828d4ba904c93c26ef7d7af0f753a3c44a38</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
dom4j before 2.1.3 allows external DTDs and External Entities by default, which might enable XXE attacks. However, there is popular external documentation from OWASP showing how to enable the safe, non-default behavior in any application that uses dom4j.

<p>Publish Date: 2020-05-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-10683>CVE-2020-10683</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/dom4j/dom4j/tree/version-2.1.3,https://github.com/dom4j/dom4j/tree/version-2.0.3"">https://github.com/dom4j/dom4j/tree/version-2.1.3,https://github.com/dom4j/dom4j/tree/version-2.0.3</a></p>
<p>Release Date: 2020-05-01</p>
<p>Fix Resolution: org.dom4j:dom4j:2.1.3,org.dom4j:dom4j:2.0.3</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in         jar      cve       high severity vulnerability     vulnerable library            jar      flexible xml framework for java   library home page   a href     path to dependency file   tmp ws scm lp angularspring angularspring bin pom xml   path to vulnerable library   root    repository org                   jar     dependency hierarchy      spring boot starter data jpa       release jar  root library        hibernate core       final jar          x            jar    vulnerable library   found in head commit   a href               vulnerability details           before       allows external dtds and external entities by default  which might enable xxe attacks  however  there is popular external documentation from owasp showing how to enable the safe  non default behavior in any application that uses      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  org           org                         step up your open source security game with whitesource    ,0
131357,27883447313.0,IssuesEvent,2023-03-21 21:20:24,MozillaFoundation/foundation.mozilla.org,https://api.github.com/repos/MozillaFoundation/foundation.mozilla.org,closed,[PNI Refactor] Add/update documentation to JS files in the /buyers-guide directory,engineering buyer's guide 🛍 code cleanup refactor,"Add/update documentation (in [JSDoc style](https://jsdoc.app/)) to the following files in `source/js/buyers-guide`.


<img width=""224"" alt=""image"" src=""https://user-images.githubusercontent.com/2896608/219780591-8acaf8bb-ccd7-4672-b82d-de4f498015fb.png"">

e.g., 

```js
/**
 * Represents a book.
 * @constructor
 * @param {string} title - The title of the book.
 * @param {string} author - The author of the book.
 */
function Book(title, author) {
}
```

",1.0,"[PNI Refactor] Add/update documentation to JS files in the /buyers-guide directory - Add/update documentation (in [JSDoc style](https://jsdoc.app/)) to the following files in `source/js/buyers-guide`.


<img width=""224"" alt=""image"" src=""https://user-images.githubusercontent.com/2896608/219780591-8acaf8bb-ccd7-4672-b82d-de4f498015fb.png"">

e.g., 

```js
/**
 * Represents a book.
 * @constructor
 * @param {string} title - The title of the book.
 * @param {string} author - The author of the book.
 */
function Book(title, author) {
}
```

",0,  add update documentation to js files in the  buyers guide directory   add update documentation  in     to the following files in  source js buyers guide         img width     alt  image  src       e g          js          represents a book       constructor      param  string  title   the title of the book       param  string  author   the author of the book        function book title  author               ,0
264559,20024979593.0,IssuesEvent,2022-02-01 20:14:33,golang/go,https://api.github.com/repos/golang/go,closed,x/website/_content/ref: lang version determining rule should be documented in Go Module Reference,Documentation NeedsFix okay-after-beta1,"The behavior implemented in https://github.com/golang/go/issues/44976 should be documented at this section: https://golang.org/ref/mod#go-mod-file-go

ref: https://groups.google.com/g/golang-nuts/c/lhedc8YaWlM
",1.0,"x/website/_content/ref: lang version determining rule should be documented in Go Module Reference - The behavior implemented in https://github.com/golang/go/issues/44976 should be documented at this section: https://golang.org/ref/mod#go-mod-file-go

ref: https://groups.google.com/g/golang-nuts/c/lhedc8YaWlM
",1,x website  content ref  lang version determining rule should be documented in go module reference   the behavior implemented in   should be documented at this section       ref     ,1
12291,2689493075.0,IssuesEvent,2015-03-31 10:37:23,juanghurtado/turbo-sort,https://api.github.com/repos/juanghurtado/turbo-sort,closed,Replace is not respecting word boundaries,auto-migrated Priority-Medium Type-Defect,"```
What steps will reproduce the problem?
1. Have a file like: Indiana.Jones.and.the.Last.Crusade.1989.720p.mkv
2. ./turbo_sort.py

What is the expected output?

Indiana Jones and The Last Crusade 1989 (720p)/Indiana Jones and The Last 
Crusade.mkv

What do you see instead?

indiana Jones and The Last Crusade 1989 (720p)/indiana Jones and The Last 
Crusade.mkv

What version of the product are you using? On what operating system?

2.1 on a linux based media player with python 2.7.3

Please provide any additional information below.

This did not happen using 2.0 and things look pretty much the same but as a 
test I created a file:

And Into and Of itself and the officer Andrew thing.mkv

when I ran that using version 2.1 I got:

and into and Of It'self and The Officer andrew Thing.mkv

Not good.  So I modified the replace line after remove_US just adding spaces 
before and after each entry:

return title.replace("" In "", "" in "").replace("" And "", "" and "").replace("" Its "", 
"" It's "").strip()

Now I get:

And Into and Of Itself and The Officer Andrew Thing.mkv

I hope that helps.

Thanks very much for the script by the way!  It is pretty amazing.

I have made a couple other modifications if you're interested I can send you a 
diff.
```

Original issue reported on code.google.com by `workingm...@gmail.com` on 13 Sep 2012 at 8:55",1.0,"Replace is not respecting word boundaries - ```
What steps will reproduce the problem?
1. Have a file like: Indiana.Jones.and.the.Last.Crusade.1989.720p.mkv
2. ./turbo_sort.py

What is the expected output?

Indiana Jones and The Last Crusade 1989 (720p)/Indiana Jones and The Last 
Crusade.mkv

What do you see instead?

indiana Jones and The Last Crusade 1989 (720p)/indiana Jones and The Last 
Crusade.mkv

What version of the product are you using? On what operating system?

2.1 on a linux based media player with python 2.7.3

Please provide any additional information below.

This did not happen using 2.0 and things look pretty much the same but as a 
test I created a file:

And Into and Of itself and the officer Andrew thing.mkv

when I ran that using version 2.1 I got:

and into and Of It'self and The Officer andrew Thing.mkv

Not good.  So I modified the replace line after remove_US just adding spaces 
before and after each entry:

return title.replace("" In "", "" in "").replace("" And "", "" and "").replace("" Its "", 
"" It's "").strip()

Now I get:

And Into and Of Itself and The Officer Andrew Thing.mkv

I hope that helps.

Thanks very much for the script by the way!  It is pretty amazing.

I have made a couple other modifications if you're interested I can send you a 
diff.
```

Original issue reported on code.google.com by `workingm...@gmail.com` on 13 Sep 2012 at 8:55",0,replace is not respecting word boundaries       what steps will reproduce the problem     have a file like  indiana jones and the last crusade     mkv      turbo sort py  what is the expected output   indiana jones and the last crusade       indiana jones and the last  crusade mkv  what do you see instead   indiana jones and the last crusade       indiana jones and the last  crusade mkv  what version of the product are you using  on what operating system       on a linux based media player with python        please provide any additional information below   this did not happen using     and things look pretty much the same but as a  test i created a file   and into and of itself and the officer andrew thing mkv  when i ran that using version     i got   and into and of it self and the officer andrew thing mkv  not good   so i modified the replace line after remove us just adding spaces  before and after each entry   return title replace   in      in    replace   and      and    replace   its       it s    strip    now i get   and into and of itself and the officer andrew thing mkv  i hope that helps   thanks very much for the script by the way   it is pretty amazing   i have made a couple other modifications if you re interested i can send you a  diff       original issue reported on code google com by  workingm    gmail com  on   sep   at    ,0
670497,22692031648.0,IssuesEvent,2022-07-04 22:14:31,WebTools-NG/WebTools-NG,https://api.github.com/repos/WebTools-NG/WebTools-NG,closed,[RFE] Refactor Settings,bug Priority-Major,"Settings are now getting too complicated, so we need to do a complete refactor of this =>

- [x] Global settings
  -  [x] PMS settings
  -  [x] Export Settings
  -  [x] Lib Mapping
 - [x] ExportTools
 - [x] Find Media

- [x] @trumpy81 does the Wiki

This sadly also involves a lot of Wiki page changes, sorry for that @trumpy81 , but WT-NG is indeed evolving beyond what I originally thought about ;)

More to come, when the time is ",1.0,"[RFE] Refactor Settings - Settings are now getting too complicated, so we need to do a complete refactor of this =>

- [x] Global settings
  -  [x] PMS settings
  -  [x] Export Settings
  -  [x] Lib Mapping
 - [x] ExportTools
 - [x] Find Media

- [x] @trumpy81 does the Wiki

This sadly also involves a lot of Wiki page changes, sorry for that @trumpy81 , but WT-NG is indeed evolving beyond what I originally thought about ;)

More to come, when the time is ",0,  refactor settings   settings are now getting too complicated  so we need to do a complete refactor of this           global settings         pms settings         export settings         lib mapping       exporttools       find media           does the wiki    this sadly also involves a lot of wiki page changes  sorry for that      but wt ng is indeed evolving beyond what i originally thought about       more to come  when the time is ,0
307268,26521111195.0,IssuesEvent,2023-01-19 02:46:56,risingwavelabs/risingwave,https://api.github.com/repos/risingwavelabs/risingwave,opened,bug: hummock panic at pinning a older version,type/bug found-by-longevity-test,"### Describe the bug

Namespace: longevity-20230118-170814
Pod: risingwave-compute-0, risingwave-compute-1, risingwave-compute-2
image: nightly-20230117

`thread 'risingwave-main' panicked at 'pinning a older version 30232. Current is 31412', src/storage/src/hummock/local_version/pinned_version.rs:102:9`

[compute-0.csv](https://github.com/risingwavelabs/risingwave/files/10452993/compute-0.csv)
[compute-1.csv](https://github.com/risingwavelabs/risingwave/files/10452994/compute-1.csv)
[compute-2.csv](https://github.com/risingwavelabs/risingwave/files/10452995/compute-2.csv)


### To Reproduce

_No response_

### Expected behavior

_No response_

### Additional context

_No response_",1.0,"bug: hummock panic at pinning a older version - ### Describe the bug

Namespace: longevity-20230118-170814
Pod: risingwave-compute-0, risingwave-compute-1, risingwave-compute-2
image: nightly-20230117

`thread 'risingwave-main' panicked at 'pinning a older version 30232. Current is 31412', src/storage/src/hummock/local_version/pinned_version.rs:102:9`

[compute-0.csv](https://github.com/risingwavelabs/risingwave/files/10452993/compute-0.csv)
[compute-1.csv](https://github.com/risingwavelabs/risingwave/files/10452994/compute-1.csv)
[compute-2.csv](https://github.com/risingwavelabs/risingwave/files/10452995/compute-2.csv)


### To Reproduce

_No response_

### Expected behavior

_No response_

### Additional context

_No response_",0,bug  hummock panic at pinning a older version       describe the bug  namespace  longevity      pod  risingwave compute    risingwave compute    risingwave compute    image  nightly       thread  risingwave main  panicked at  pinning a older version    current is     src storage src hummock local version pinned version rs                              to reproduce   no response       expected behavior   no response       additional context   no response ,0
43095,9375745447.0,IssuesEvent,2019-04-04 05:37:14,gravitystorm/openstreetmap-carto,https://api.github.com/repos/gravitystorm/openstreetmap-carto,closed,Healthcare tags do not render on closed ways without area=yes,bug code,"### Expected behavior
The key ""healthcare="" should be imported as a polygon so that the icons for clinics, hospitals etc will render properly.

### Actual behavior
A closed way (""area"") tagged with healthcare=* alone does not import or render
Adding ""area=yes"" causes it to render

### Solution
Add 'healthcare' to list of local polygon_keys in openstreetmap-carto.lua",1.0,"Healthcare tags do not render on closed ways without area=yes - ### Expected behavior
The key ""healthcare="" should be imported as a polygon so that the icons for clinics, hospitals etc will render properly.

### Actual behavior
A closed way (""area"") tagged with healthcare=* alone does not import or render
Adding ""area=yes"" causes it to render

### Solution
Add 'healthcare' to list of local polygon_keys in openstreetmap-carto.lua",0,healthcare tags do not render on closed ways without area yes       expected behavior  the key  healthcare   should be imported as a polygon so that the icons for clinics  hospitals etc will render properly         actual behavior  a closed way   area   tagged with healthcare   alone does not import or render  adding  area yes  causes it to render        solution  add  healthcare  to list of local polygon keys in openstreetmap carto lua,0
17294,5377798832.0,IssuesEvent,2017-02-23 13:16:24,joomla/joomla-cms,https://api.github.com/repos/joomla/joomla-cms,closed,[3.7.0b1] [com_fields] Media field directory transverse allowed,No Code Attached Yet,"### Steps to reproduce the issue

install 3.7.0b1
create Media custom field
Set the fields params to HOME DIRECTORY = Yes 
Dont set anything else
edit content on FRONTEND

### Expected result

That I, as username ""admin"" cannot see other users folders

### Actual result

I can manipulate the url of the popup media manager (or just click the up button) to view other folders outside of the ""home"" folder /images/images/admin/
",1.0,"[3.7.0b1] [com_fields] Media field directory transverse allowed - ### Steps to reproduce the issue

install 3.7.0b1
create Media custom field
Set the fields params to HOME DIRECTORY = Yes 
Dont set anything else
edit content on FRONTEND

### Expected result

That I, as username ""admin"" cannot see other users folders

### Actual result

I can manipulate the url of the popup media manager (or just click the up button) to view other folders outside of the ""home"" folder /images/images/admin/
",0,    media field directory transverse allowed       steps to reproduce the issue    install        create media custom field  set the fields params to home directory   yes   dont set anything else  edit content on frontend        expected result    that i  as username  admin  cannot see other users folders        actual result    i can manipulate the url of the popup media manager  or just click the up button  to view other folders outside of the  home  folder  images images admin   ,0
414321,27984207650.0,IssuesEvent,2023-03-26 14:08:07,golang/go,https://api.github.com/repos/golang/go,closed,io: Documentation of the io package at website is contrary to its documentation in comments inside source code.,Documentation,"### What version of Go are you using (`go version`)?
go version go1.20.2 windows/amd64

### Does this issue reproduce with the latest release?
Yes.

### What operating system and processor architecture are you using (`go env`)?
O.S. is Microsoft Windows 10.
CPU uses Intel x86-64 (a.k.a. AMD64) architecture.

### What did you do?
Documentation of the `io` package at website states following.

> An instance of this general case is that a Reader returning a non-zero number of bytes at the end of the input stream may return either err == EOF or err == nil. The next Read should return 0, EOF. 

Documentation of the same `io` package in comments inside the source code states following.

> EOF is the error returned by Read when no more input is available.

### What did you expect to see?
I expect to see no controversy in documentation.

### What did you see instead?
I saw the controversy in documentation.
",1.0,"io: Documentation of the io package at website is contrary to its documentation in comments inside source code. - ### What version of Go are you using (`go version`)?
go version go1.20.2 windows/amd64

### Does this issue reproduce with the latest release?
Yes.

### What operating system and processor architecture are you using (`go env`)?
O.S. is Microsoft Windows 10.
CPU uses Intel x86-64 (a.k.a. AMD64) architecture.

### What did you do?
Documentation of the `io` package at website states following.

> An instance of this general case is that a Reader returning a non-zero number of bytes at the end of the input stream may return either err == EOF or err == nil. The next Read should return 0, EOF. 

Documentation of the same `io` package in comments inside the source code states following.

> EOF is the error returned by Read when no more input is available.

### What did you expect to see?
I expect to see no controversy in documentation.

### What did you see instead?
I saw the controversy in documentation.
",1,io  documentation of the io package at website is contrary to its documentation in comments inside source code        what version of go are you using   go version     go version       windows          does this issue reproduce with the latest release   yes         what operating system and processor architecture are you using   go env     o s  is microsoft windows     cpu uses intel      a k a     architecture         what did you do   documentation of the  io  package at website states following       an instance of this general case is that a reader returning a non zero number of bytes at the end of the input stream may return either err    eof or err    nil  the next read should return    eof      documentation of the same  io  package in comments inside the source code states following       eof is the error returned by read when no more input is available         what did you expect to see   i expect to see no controversy in documentation         what did you see instead   i saw the controversy in documentation   ,1
14983,5029824534.0,IssuesEvent,2016-12-15 22:22:36,readbeyond/aeneas,https://api.github.com/repos/readbeyond/aeneas,opened,Improve selection of Festival voices,code functionality,"Probably overriding the voice with the current rconf parameter is enough, but I need to check this. In any case, the user is responsible for setting the extra deps as required by the synthesizer she wants to use (HTS, mbrola).",1.0,"Improve selection of Festival voices - Probably overriding the voice with the current rconf parameter is enough, but I need to check this. In any case, the user is responsible for setting the extra deps as required by the synthesizer she wants to use (HTS, mbrola).",0,improve selection of festival voices   probably overriding the voice with the current rconf parameter is enough  but i need to check this  in any case  the user is responsible for setting the extra deps as required by the synthesizer she wants to use  hts  mbrola  ,0
189617,15192028314.0,IssuesEvent,2021-02-15 21:07:56,golang/go,https://api.github.com/repos/golang/go,opened,os: docs say nothing about path slash types,Documentation,"The `os` package docs say:

> Package os provides a platform-independent interface to operating system functionality. The design is Unix-like, although the error handling is Go-like

But nowhere at https://golang.org/pkg/os/ is ""slash"" mentioned.

Yet there are two Go packages about paths and their slashes: `path` and `path/filepath`.

That quoted line above might suggest only forward slashes are permitted (""the design is Unix-like"").

Seems like the `os` package should say what it permits. Users will wonder: forward only? host native only? either way?",1.0,"os: docs say nothing about path slash types - The `os` package docs say:

> Package os provides a platform-independent interface to operating system functionality. The design is Unix-like, although the error handling is Go-like

But nowhere at https://golang.org/pkg/os/ is ""slash"" mentioned.

Yet there are two Go packages about paths and their slashes: `path` and `path/filepath`.

That quoted line above might suggest only forward slashes are permitted (""the design is Unix-like"").

Seems like the `os` package should say what it permits. Users will wonder: forward only? host native only? either way?",1,os  docs say nothing about path slash types   the  os  package docs say       package os provides a platform independent interface to operating system functionality  the design is unix like  although the error handling is go like    but nowhere at   is  slash  mentioned     yet there are two go packages about paths and their slashes   path  and  path filepath      that quoted line above might suggest only forward slashes are permitted   the design is unix like       seems like the  os  package should say what it permits  users will wonder  forward only  host native only  either way ,1
733467,25307265260.0,IssuesEvent,2022-11-17 15:00:22,Unity-Technologies/com.unity.netcode.gameobjects,https://api.github.com/repos/Unity-Technologies/com.unity.netcode.gameobjects,closed,NetworkVariable OnValueChanged() not being called on spawn,type:bug priority:medium stat:imported,"### Description

My game was running fine with Netcode 1.0.2, but after I upgraded to 1.1.0 some issues started to occur. There is a short example of code that works fine in 1.0.2:
```
    public override void OnNetworkSpawn()
    {
        if (!IsOwner) //called on client
        {
            //called on client right after spawning on 1.0.2 (never called on 1.1.0)
            networkInit.OnValueChanged += UpdateBulletInit; 
        }
        else //called on server/owner
        {
            //NetworkVariable value changed in server, makes OnValueChanged being called instantly on client
            networkInit.Value = new BulletNetworkInit(){ _initialForce = 1, };
        }
    }
```

If spawned on server, the NetworkVariable immediately has its value changed (initialized).
If the Bullet was spawned on client, it would listen to every change of its NetworkVariable value on server.


This works fine in 1.0.2 in the way that client always get OnValueChanged called right after its spawn and everything is initialized correctly on client-side.

But after upgrading to Netcode 1.1.0 the OnValueChanged event is not being called on client.

Instead, I had to call the initialization method directly doing something like:
```
    public override void OnNetworkSpawn()
    {
        if (!IsOwner) //called on client
        {
            //call the initialization manually
            UpdateBulletInit(networkInit.Value, networkInit.Value);
        }
        else //called on server/owner
        {
            //NetworkVariable value changed in server, makes OnValueChanged being called instantly on client
            networkInit.Value = new BulletNetworkInit(){ _initialForce = 1, };
        }
    }
```

I don't know what is the best approach, but everything was working fine before. I'm afraid there's more changes to be made in the project to suit this new Netcode version.

I'm going back to 1.0.2 for now, but I appreciate any feedback or tips regarding this issue.

### Screenshots
Piece of code working fine on 1.0.2:
![image](https://user-images.githubusercontent.com/57048433/197231961-b902d9dc-df76-4ca3-b031-1f22ab241167.png)

### Environment

- OS: Windows 10 64-bit
- Unity Version: 2021.3.9f1
- Netcode Version: 1.1.0 release
- Netcode Commit: https://github.com/Unity-Technologies/com.unity.netcode.gameobjects/commit/2c69184e5f85a025455c415145be3eeecbf98446

### Additional Context

I noticed some changes in player spawning behaviour (not spawning in prefabs transform anymore, but on world zeroed position) and messaging errors, but I haven't tracked the reason yet, because the reported issue is more concerning to me right now.",1.0,"NetworkVariable OnValueChanged() not being called on spawn - ### Description

My game was running fine with Netcode 1.0.2, but after I upgraded to 1.1.0 some issues started to occur. There is a short example of code that works fine in 1.0.2:
```
    public override void OnNetworkSpawn()
    {
        if (!IsOwner) //called on client
        {
            //called on client right after spawning on 1.0.2 (never called on 1.1.0)
            networkInit.OnValueChanged += UpdateBulletInit; 
        }
        else //called on server/owner
        {
            //NetworkVariable value changed in server, makes OnValueChanged being called instantly on client
            networkInit.Value = new BulletNetworkInit(){ _initialForce = 1, };
        }
    }
```

If spawned on server, the NetworkVariable immediately has its value changed (initialized).
If the Bullet was spawned on client, it would listen to every change of its NetworkVariable value on server.


This works fine in 1.0.2 in the way that client always get OnValueChanged called right after its spawn and everything is initialized correctly on client-side.

But after upgrading to Netcode 1.1.0 the OnValueChanged event is not being called on client.

Instead, I had to call the initialization method directly doing something like:
```
    public override void OnNetworkSpawn()
    {
        if (!IsOwner) //called on client
        {
            //call the initialization manually
            UpdateBulletInit(networkInit.Value, networkInit.Value);
        }
        else //called on server/owner
        {
            //NetworkVariable value changed in server, makes OnValueChanged being called instantly on client
            networkInit.Value = new BulletNetworkInit(){ _initialForce = 1, };
        }
    }
```

I don't know what is the best approach, but everything was working fine before. I'm afraid there's more changes to be made in the project to suit this new Netcode version.

I'm going back to 1.0.2 for now, but I appreciate any feedback or tips regarding this issue.

### Screenshots
Piece of code working fine on 1.0.2:
![image](https://user-images.githubusercontent.com/57048433/197231961-b902d9dc-df76-4ca3-b031-1f22ab241167.png)

### Environment

- OS: Windows 10 64-bit
- Unity Version: 2021.3.9f1
- Netcode Version: 1.1.0 release
- Netcode Commit: https://github.com/Unity-Technologies/com.unity.netcode.gameobjects/commit/2c69184e5f85a025455c415145be3eeecbf98446

### Additional Context

I noticed some changes in player spawning behaviour (not spawning in prefabs transform anymore, but on world zeroed position) and messaging errors, but I haven't tracked the reason yet, because the reported issue is more concerning to me right now.",0,networkvariable onvaluechanged   not being called on spawn       description    my game was running fine with netcode        but after i upgraded to       some issues started to occur  there is a short example of code that works fine in                  public override void onnetworkspawn                   if   isowner    called on client                           called on client right after spawning on        never called on                     networkinit onvaluechanged    updatebulletinit                       else   called on server owner                           networkvariable value changed in server  makes onvaluechanged being called instantly on client              networkinit value   new bulletnetworkinit     initialforce                                   if spawned on server  the networkvariable immediately has its value changed  initialized    if the bullet was spawned on client  it would listen to every change of its networkvariable value on server       this works fine in       in the way that client always get onvaluechanged called right after its spawn and everything is initialized correctly on client side     but after upgrading to netcode       the onvaluechanged event is not being called on client     instead  i had to call the initialization method directly doing something like            public override void onnetworkspawn                   if   isowner    called on client                           call the initialization manually              updatebulletinit networkinit value  networkinit value                       else   called on server owner                           networkvariable value changed in server  makes onvaluechanged being called instantly on client              networkinit value   new bulletnetworkinit     initialforce                                   i don t know what is the best approach  but everything was working fine before  i m afraid there s more changes to be made in the project to suit this new netcode version     i m going back to       for now  but i appreciate any feedback or tips regarding this issue         screenshots  piece of code working fine on                     environment      os  windows     bit    unity version           netcode version        release    netcode commit           additional context    i noticed some changes in player spawning behaviour  not spawning in prefabs transform anymore  but on world zeroed position  and messaging errors  but i haven t tracked the reason yet  because the reported issue is more concerning to me right now ,0
12172,3587787886.0,IssuesEvent,2016-01-30 15:35:26,golang/go,https://api.github.com/repos/golang/go,closed,Documentation: broken link to plan9.bell-labs.com,Documentation,"plan9.bell-labs.com seems to have been deactivated. There is now many broken links in packages documentation: https://github.com/golang/go/search?utf8=✓&q=plan9.bell-labs.com

For example, `path` package link to: http://plan9.bell-labs.com/sys/doc/lexnames.html. I found a mirror that can be helpful: https://9p.io/sys/doc/lexnames.html.",1.0,"Documentation: broken link to plan9.bell-labs.com - plan9.bell-labs.com seems to have been deactivated. There is now many broken links in packages documentation: https://github.com/golang/go/search?utf8=✓&q=plan9.bell-labs.com

For example, `path` package link to: http://plan9.bell-labs.com/sys/doc/lexnames.html. I found a mirror that can be helpful: https://9p.io/sys/doc/lexnames.html.",1,documentation  broken link to   bell labs com     bell labs com seems to have been deactivated  there is now many broken links in packages documentation       for example   path  package link to    i found a mirror that can be helpful   ,1
213960,16549211893.0,IssuesEvent,2021-05-28 06:22:10,google/autocxx,https://api.github.com/repos/google/autocxx,closed,Another 'expected identifier' problem,bug has-test-case,"Build `s2` example at revision 77c6e7f5efb1d746936ca26ede29faac117dda89.

Actual behavior:
```
  thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: InvalidCxx(Syn(Error([""expected identifier"", ""the name `_bindgen_ty_1` is defined multiple times"", ""the name `_bindgen_ty_2` is defined multiple times""])))', build.rs:21:76
```

The problem with `bindgen_ty_1` is #486. The `expected identifier` problem is this.",1.0,"Another 'expected identifier' problem - Build `s2` example at revision 77c6e7f5efb1d746936ca26ede29faac117dda89.

Actual behavior:
```
  thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: InvalidCxx(Syn(Error([""expected identifier"", ""the name `_bindgen_ty_1` is defined multiple times"", ""the name `_bindgen_ty_2` is defined multiple times""])))', build.rs:21:76
```

The problem with `bindgen_ty_1` is #486. The `expected identifier` problem is this.",0,another  expected identifier  problem   build     example at revision       actual behavior          thread  main  panicked at  called  result  unwrap    on an  err  value  invalidcxx syn error        build rs             the problem with  bindgen ty    is     the  expected identifier  problem is this ,0
68394,9172201049.0,IssuesEvent,2019-03-04 06:01:37,golang/go,https://api.github.com/repos/golang/go,closed,doc: Release History doesn't mention 1.11.5,Documentation,"The release history page doesn't list the go1.11.5 minor release:

https://golang.org/doc/devel/release.html#go1.11.minor

However, tip.golang.org has it:

https://tip.golang.org/doc/devel/release.html#go1.11.minor

Does the main website need a redeploy or something?

cc @dmitshur",1.0,"doc: Release History doesn't mention 1.11.5 - The release history page doesn't list the go1.11.5 minor release:

https://golang.org/doc/devel/release.html#go1.11.minor

However, tip.golang.org has it:

https://tip.golang.org/doc/devel/release.html#go1.11.minor

Does the main website need a redeploy or something?

cc @dmitshur",1,doc  release history doesn t mention         the release history page doesn t list the       minor release          however  tip golang org has it          does the main website need a redeploy or something     cc  dmitshur,1
36305,6524965302.0,IssuesEvent,2017-08-29 14:26:27,golang/go,https://api.github.com/repos/golang/go,closed,spec: similar sounding nomenclature is confusing,Documentation,"<pre>In the spec we use the following phrases:

1) integer value
2) value of integer type
3) value of type int (or int8, int16, etc)
4) representable as a value of type int (or int8, int16, etc)

They are very similar in English but mean different things in the spec:

1) -&gt; a (typed or untyped) constant value that is integer (1, 2.0, -4.0 + 0i)
2) -&gt; a typed value that has one of the signed/unsigned integer types (byte, int,
uint8, etc.)
3) -&gt; a value of a concrete type int, int8, etc.
4) -&gt; a value that can be represented w/o loss of accuracy as a value of a specific
type

We should clean this up, and/or introduce a section explaining the nomenclature. As is,
the English differences are small, but the spec implications are large.</pre>
",1.0,"spec: similar sounding nomenclature is confusing - <pre>In the spec we use the following phrases:

1) integer value
2) value of integer type
3) value of type int (or int8, int16, etc)
4) representable as a value of type int (or int8, int16, etc)

They are very similar in English but mean different things in the spec:

1) -&gt; a (typed or untyped) constant value that is integer (1, 2.0, -4.0 + 0i)
2) -&gt; a typed value that has one of the signed/unsigned integer types (byte, int,
uint8, etc.)
3) -&gt; a value of a concrete type int, int8, etc.
4) -&gt; a value that can be represented w/o loss of accuracy as a value of a specific
type

We should clean this up, and/or introduce a section explaining the nomenclature. As is,
the English differences are small, but the spec implications are large.</pre>
",1,spec  similar sounding nomenclature is confusing    in the spec we use the following phrases      integer value    value of integer type    value of type int  or       etc     representable as a value of type int  or       etc   they are very similar in english but mean different things in the spec        gt  a  typed or untyped  constant value that is integer                         gt  a typed value that has one of the signed unsigned integer types  byte  int     etc        gt  a value of a concrete type int     etc       gt  a value that can be represented w o loss of accuracy as a value of a specific type  we should clean this up  and or introduce a section explaining the nomenclature  as is  the english differences are small  but the spec implications are large   ,1
267892,8394166553.0,IssuesEvent,2018-10-09 23:12:36,townhallproject/townHallProject,https://api.github.com/repos/townhallproject/townHallProject,closed,change copy on '#about' 'who we are',top priority,"Juliana Amin - National Organizing Director - Before Town Hall Project, Juliana built organizing programs across the country over multiple cycles. Most recently she oversaw a team of more than 60 staff in Ohio for the Clinton campaign in 2016.",1.0,"change copy on '#about' 'who we are' - Juliana Amin - National Organizing Director - Before Town Hall Project, Juliana built organizing programs across the country over multiple cycles. Most recently she oversaw a team of more than 60 staff in Ohio for the Clinton campaign in 2016.",0,change copy on   about   who we are    juliana amin   national organizing director   before town hall project  juliana built organizing programs across the country over multiple cycles  most recently she oversaw a team of more than   staff in ohio for the clinton campaign in   ,0
137579,18753671915.0,IssuesEvent,2021-11-05 07:47:39,madhans23/linux-4.15,https://api.github.com/repos/madhans23/linux-4.15,opened,WS-2021-0215 (High) detected in linux-socfpgarel_socfpga-5.13_21.10.03_pr,security vulnerability,"## WS-2021-0215 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-socfpgarel_socfpga-5.13_21.10.03_pr</b></p></summary>
<p>

<p>Linux development repository for socfpga</p>
<p>Library home page: <a href=https://github.com/altera-opensource/linux-socfpga.git>https://github.com/altera-opensource/linux-socfpga.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/madhans23/linux-4.15/commit/0212a970b00f59b908ade7092ec2cd13230ec39d"">0212a970b00f59b908ade7092ec2cd13230ec39d</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>

</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
Linux/kernel in versions v5.8-rc1--v5.12 is vulnerable to signed overflow in ringbuf_process_ring

<p>Publish Date: 2021-05-31
<p>URL: <a href=https://github.com/torvalds/linux/commit/4aae6eb6af7d1ac2ee5762077892185884d8f169>WS-2021-0215</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://osv.dev/vulnerability/UVI-2021-1000329"">https://osv.dev/vulnerability/UVI-2021-1000329</a></p>
<p>Release Date: 2021-05-31</p>
<p>Fix Resolution: v5.13-rc1</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"WS-2021-0215 (High) detected in linux-socfpgarel_socfpga-5.13_21.10.03_pr - ## WS-2021-0215 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-socfpgarel_socfpga-5.13_21.10.03_pr</b></p></summary>
<p>

<p>Linux development repository for socfpga</p>
<p>Library home page: <a href=https://github.com/altera-opensource/linux-socfpga.git>https://github.com/altera-opensource/linux-socfpga.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/madhans23/linux-4.15/commit/0212a970b00f59b908ade7092ec2cd13230ec39d"">0212a970b00f59b908ade7092ec2cd13230ec39d</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>

</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
Linux/kernel in versions v5.8-rc1--v5.12 is vulnerable to signed overflow in ringbuf_process_ring

<p>Publish Date: 2021-05-31
<p>URL: <a href=https://github.com/torvalds/linux/commit/4aae6eb6af7d1ac2ee5762077892185884d8f169>WS-2021-0215</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://osv.dev/vulnerability/UVI-2021-1000329"">https://osv.dev/vulnerability/UVI-2021-1000329</a></p>
<p>Release Date: 2021-05-31</p>
<p>Fix Resolution: v5.13-rc1</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,ws      high  detected in linux socfpgarel socfpga           pr      ws       high severity vulnerability     vulnerable library    linux socfpgarel socfpga           pr        linux development repository for socfpga   library home page   a href    found in head commit   a href      found in base branch   master             vulnerable source files                              vulnerability details         linux kernel in versions            is vulnerable to signed overflow in ringbuf process ring   publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                      step up your open source security game with whitesource    ,0
294783,22162671649.0,IssuesEvent,2022-06-04 18:42:43,golang/go,https://api.github.com/repos/golang/go,closed,doc: update Go memory model,Documentation Proposal Proposal-Accepted release-blocker Proposal-FinalCommentPeriod,"In June 2021 I posted a series of articles about memory models, ending with an article about changes I thought we should make to the Go memory model. See https://research.swtch.com/mm especially https://research.swtch.com/gomm.

Then I opened a GitHub Discussion to discuss these changes; see #47141.

Based on that discussion, I propose the following concrete changes to the memory model:

- Document Go's overall approach.
- Document that multiword races can cause crashes.
- Document happens-before for runtime.SetFinalizer.
- Document (or link to) happens-before for more sync types.
- Document happens-before for sync/atomic, matching C++ sequentially consistent atomics (and Java, JavaScript, Rust, Swift, C, ...)
- Document disallowed compiler optimizations.

The exact details can be viewed in pending CLs prepared for concreteness, in particular [CL 381315](https://go.dev/cl/381315) (memory model) and [CL 381316](https://go.dev/cl/381316) (library docs).

I have filed a separate proposal - #50860 - for another item that arose during that discussion, namely adding typed atomic values to sync/atomic.
",1.0,"doc: update Go memory model - In June 2021 I posted a series of articles about memory models, ending with an article about changes I thought we should make to the Go memory model. See https://research.swtch.com/mm especially https://research.swtch.com/gomm.

Then I opened a GitHub Discussion to discuss these changes; see #47141.

Based on that discussion, I propose the following concrete changes to the memory model:

- Document Go's overall approach.
- Document that multiword races can cause crashes.
- Document happens-before for runtime.SetFinalizer.
- Document (or link to) happens-before for more sync types.
- Document happens-before for sync/atomic, matching C++ sequentially consistent atomics (and Java, JavaScript, Rust, Swift, C, ...)
- Document disallowed compiler optimizations.

The exact details can be viewed in pending CLs prepared for concreteness, in particular [CL 381315](https://go.dev/cl/381315) (memory model) and [CL 381316](https://go.dev/cl/381316) (library docs).

I have filed a separate proposal - #50860 - for another item that arose during that discussion, namely adding typed atomic values to sync/atomic.
",1,doc  update go memory model   in june   i posted a series of articles about memory models  ending with an article about changes i thought we should make to the go memory model  see   especially      then i opened a github discussion to discuss these changes  see        based on that discussion  i propose the following concrete changes to the memory model       document go s overall approach     document that multiword races can cause crashes     document happens before for runtime setfinalizer     document  or link to  happens before for more sync types     document happens before for sync atomic  matching c   sequentially consistent atomics  and java  javascript  rust  swift  c          document disallowed compiler optimizations     the exact details can be viewed in pending cls prepared for concreteness  in particular      memory model  and      library docs      i have filed a separate proposal        for another item that arose during that discussion  namely adding typed atomic values to sync atomic   ,1
182238,21664492826.0,IssuesEvent,2022-05-07 01:32:11,DaniOlivares/test-truffle-oz-tutorial-token,https://api.github.com/repos/DaniOlivares/test-truffle-oz-tutorial-token,closed,WS-2017-0330 (Medium) detected in mime-1.3.4.tgz - autoclosed,security vulnerability,"## WS-2017-0330 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>mime-1.3.4.tgz</b></p></summary>

<p>A comprehensive library for mime-type mapping</p>
<p>Library home page: <a href=""https://registry.npmjs.org/mime/-/mime-1.3.4.tgz"">https://registry.npmjs.org/mime/-/mime-1.3.4.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/test-truffle-oz-tutorial-token/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/test-truffle-oz-tutorial-token/node_modules/mime/package.json</p>
<p>

Dependency Hierarchy:
  - lite-server-2.3.0.tgz (Root Library)
    - browser-sync-2.23.6.tgz
      - serve-static-1.12.2.tgz
        - send-0.15.2.tgz
          - :x: **mime-1.3.4.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/DaniOlivares/test-truffle-oz-tutorial-token/commit/3909aabf9cc5c24540bdec6e0a2e7edfaae8686f"">3909aabf9cc5c24540bdec6e0a2e7edfaae8686f</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
Affected version of mime (1.0.0 throw 1.4.0 and 2.0.0 throw 2.0.2), are vulnerable to regular expression denial of service.

<p>Publish Date: 2017-09-27
<p>URL: <a href=https://github.com/broofa/node-mime/commit/1df903fdeb9ae7eaa048795b8d580ce2c98f40b0>WS-2017-0330</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>5.0</b>)</summary>
<p>

Base Score Metrics not available</p>

</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/broofa/node-mime/commit/1df903fdeb9ae7eaa048795b8d580ce2c98f40b0"">https://github.com/broofa/node-mime/commit/1df903fdeb9ae7eaa048795b8d580ce2c98f40b0</a></p>
<p>Release Date: 2019-04-03</p>
<p>Fix Resolution: 1.4.1,2.0.3</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"WS-2017-0330 (Medium) detected in mime-1.3.4.tgz - autoclosed - ## WS-2017-0330 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>mime-1.3.4.tgz</b></p></summary>

<p>A comprehensive library for mime-type mapping</p>
<p>Library home page: <a href=""https://registry.npmjs.org/mime/-/mime-1.3.4.tgz"">https://registry.npmjs.org/mime/-/mime-1.3.4.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/test-truffle-oz-tutorial-token/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/test-truffle-oz-tutorial-token/node_modules/mime/package.json</p>
<p>

Dependency Hierarchy:
  - lite-server-2.3.0.tgz (Root Library)
    - browser-sync-2.23.6.tgz
      - serve-static-1.12.2.tgz
        - send-0.15.2.tgz
          - :x: **mime-1.3.4.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/DaniOlivares/test-truffle-oz-tutorial-token/commit/3909aabf9cc5c24540bdec6e0a2e7edfaae8686f"">3909aabf9cc5c24540bdec6e0a2e7edfaae8686f</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
Affected version of mime (1.0.0 throw 1.4.0 and 2.0.0 throw 2.0.2), are vulnerable to regular expression denial of service.

<p>Publish Date: 2017-09-27
<p>URL: <a href=https://github.com/broofa/node-mime/commit/1df903fdeb9ae7eaa048795b8d580ce2c98f40b0>WS-2017-0330</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>5.0</b>)</summary>
<p>

Base Score Metrics not available</p>

</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/broofa/node-mime/commit/1df903fdeb9ae7eaa048795b8d580ce2c98f40b0"">https://github.com/broofa/node-mime/commit/1df903fdeb9ae7eaa048795b8d580ce2c98f40b0</a></p>
<p>Release Date: 2019-04-03</p>
<p>Fix Resolution: 1.4.1,2.0.3</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,ws      medium  detected in mime       tgz   autoclosed      ws       medium severity vulnerability     vulnerable library    mime       tgz      a comprehensive library for mime type mapping   library home page   a href     path to dependency file   tmp ws scm test truffle oz tutorial token package json   path to vulnerable library   tmp ws scm test truffle oz tutorial token node modules mime package json     dependency hierarchy      lite server       tgz  root library        browser sync       tgz         serve static       tgz           send       tgz              x    mime       tgz    vulnerable library   found in head commit   a href               vulnerability details         affected version of mime        throw       and       throw         are vulnerable to regular expression denial of service    publish date         url   a href              cvss   score details             base score metrics not available              suggested fix      type  upgrade version   origin   a href     release date          fix resolution                            step up your open source security game with whitesource    ,0
40053,6796333191.0,IssuesEvent,2017-11-01 18:38:49,golang/go,https://api.github.com/repos/golang/go,closed,os/signal: document how to forward all signals,Documentation HelpWanted,"I'm writing a command line wrapper that sets some state in the world, starts a child process, waits for it to complete, and then unsets some state in the world.

So basically something like

```go
doSomeStatefulThing()
cmd := exec.Command(""subcmd"", args...)
cmd.Stdin = os.Stdin
cmd.Stdout = os.Stdout
cmd.Stderr = os.Stderr
err := cmd.Run()
undoSomeStatefulThing()
return err
```

I missed the line in the `signal.Notify` docs that says 

>  If no signals are provided, all incoming signals will be relayed to c. Otherwise, just the provided signals will.

It might be good to provide a second Example for Notify where the args... list is empty, for people who are silly like me and miss the doc.

(It might also be good if it was easier to set up a proxied command - it seems like it's easy to miss some of the steps involved in proxying through all FD's/signals in both directions.)",1.0,"os/signal: document how to forward all signals - I'm writing a command line wrapper that sets some state in the world, starts a child process, waits for it to complete, and then unsets some state in the world.

So basically something like

```go
doSomeStatefulThing()
cmd := exec.Command(""subcmd"", args...)
cmd.Stdin = os.Stdin
cmd.Stdout = os.Stdout
cmd.Stderr = os.Stderr
err := cmd.Run()
undoSomeStatefulThing()
return err
```

I missed the line in the `signal.Notify` docs that says 

>  If no signals are provided, all incoming signals will be relayed to c. Otherwise, just the provided signals will.

It might be good to provide a second Example for Notify where the args... list is empty, for people who are silly like me and miss the doc.

(It might also be good if it was easier to set up a proxied command - it seems like it's easy to miss some of the steps involved in proxying through all FD's/signals in both directions.)",1,os signal  document how to forward all signals   i m writing a command line wrapper that sets some state in the world  starts a child process  waits for it to complete  and then unsets some state in the world     so basically something like       go  dosomestatefulthing    cmd    exec command  subcmd   args      cmd stdin   os stdin  cmd stdout   os stdout  cmd stderr   os stderr  err    cmd run    undosomestatefulthing    return err         i missed the line in the  signal notify  docs that says        if no signals are provided  all incoming signals will be relayed to c  otherwise  just the provided signals will     it might be good to provide a second example for notify where the args    list is empty  for people who are silly like me and miss the doc      it might also be good if it was easier to set up a proxied command   it seems like it s easy to miss some of the steps involved in proxying through all fd s signals in both directions  ,1
59712,6661436918.0,IssuesEvent,2017-10-02 08:36:31,edenlabllc/ehealth.api,https://api.github.com/repos/edenlabllc/ehealth.api,closed,Adjust behavior when user without roles is trying to login,FE FE/nhs.admin kind/bug status/test,"## env - demo

## preconditions
existing user that has no roles - `pavel.zhuk@gmail.com`

## reprosteps
enter login/pass

## actual result
UI is freezed, nothing happen

## expected result

show proper error message that access is restricted for this user
",1.0,"Adjust behavior when user without roles is trying to login - ## env - demo

## preconditions
existing user that has no roles - `pavel.zhuk@gmail.com`

## reprosteps
enter login/pass

## actual result
UI is freezed, nothing happen

## expected result

show proper error message that access is restricted for this user
",0,adjust behavior when user without roles is trying to login      env   demo       preconditions  existing user that has no roles    pavel zhuk gmail com        reprosteps  enter login pass       actual result  ui is freezed  nothing happen       expected result    show proper error message that access is restricted for this user  ,0
229857,25384797328.0,IssuesEvent,2022-11-21 20:52:01,aws/eks-distro-build-tooling,https://api.github.com/repos/aws/eks-distro-build-tooling,closed,"syscall, os/exec: unsanitized NUL in environment variables - CVE-2022-41716",security golang,"From [Golang security announcement](https://groups.google.com/g/golang-announce/c/mbHY1UY3BaM):

On Windows, syscall.StartProcess and os/exec.Cmd did not properly check for invalid environment variable values. A malicious environment variable value could exploit this behavior to set a value for a different environment variable. For example, the environment variable string ""A=B\x00C=D"" set the variables ""A=B"" and ""C=D"".

Thanks to RyotaK (https://twitter.com/ryotkak) for reporting this issue.

This is CVE-2022-41716 and Go issue https://go.dev/issue/56284.
",True,"syscall, os/exec: unsanitized NUL in environment variables - CVE-2022-41716 - From [Golang security announcement](https://groups.google.com/g/golang-announce/c/mbHY1UY3BaM):

On Windows, syscall.StartProcess and os/exec.Cmd did not properly check for invalid environment variable values. A malicious environment variable value could exploit this behavior to set a value for a different environment variable. For example, the environment variable string ""A=B\x00C=D"" set the variables ""A=B"" and ""C=D"".

Thanks to RyotaK (https://twitter.com/ryotkak) for reporting this issue.

This is CVE-2022-41716 and Go issue https://go.dev/issue/56284.
",0,syscall  os exec  unsanitized nul in environment variables   cve       from        on windows  syscall startprocess and os exec cmd did not properly check for invalid environment variable values  a malicious environment variable value could exploit this behavior to set a value for a different environment variable  for example  the environment variable string  a b   d  set the variables  a b  and  c d      thanks to ryotak    for reporting this issue     this is cve     and go issue    ,0
425255,29298484096.0,IssuesEvent,2023-05-25 00:05:52,golang/go,https://api.github.com/repos/golang/go,closed,encoding/json: please document that float +inf/-inf/nan will cause json.Marshal return error ,Documentation NeedsFix,"What version of Go are you using (go version)?
go version go1.19.2 darwin/amd64

Does this issue reproduce with the latest release?
It does with go playground

What did you do?
Same as https://github.com/golang/go/issues/3480 

https://play.golang.org/p/K4xwS7iy4MP

What did you expect to see?
Document that float +inf/-inf/nan will cause json.Marshal return error  or Not throwing serialization errors on basic numeric data types with valid state.

What did you see instead?
No document of this kind of thing and return json: unsupported value: NaN

Should golang standard library document possible/common error type of a package or a function like windows api document(https://learn.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-deletefilew) or linux man (https://linux.die.net/man/3/mmap)?
Code with standard library sometime looks like try and fix again and again without document of possible/common error type.
 
reference:
* https://stackoverflow.com/questions/1423081/json-left-out-infinity-and-nan-json-status-in-ecmascript
* https://github.com/golang/go/issues/3480
* https://github.com/golang/go/issues/25721
* https://learn.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-deletefilew
* https://linux.die.net/man/3/mmap",1.0,"encoding/json: please document that float +inf/-inf/nan will cause json.Marshal return error  - What version of Go are you using (go version)?
go version go1.19.2 darwin/amd64

Does this issue reproduce with the latest release?
It does with go playground

What did you do?
Same as https://github.com/golang/go/issues/3480 

https://play.golang.org/p/K4xwS7iy4MP

What did you expect to see?
Document that float +inf/-inf/nan will cause json.Marshal return error  or Not throwing serialization errors on basic numeric data types with valid state.

What did you see instead?
No document of this kind of thing and return json: unsupported value: NaN

Should golang standard library document possible/common error type of a package or a function like windows api document(https://learn.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-deletefilew) or linux man (https://linux.die.net/man/3/mmap)?
Code with standard library sometime looks like try and fix again and again without document of possible/common error type.
 
reference:
* https://stackoverflow.com/questions/1423081/json-left-out-infinity-and-nan-json-status-in-ecmascript
* https://github.com/golang/go/issues/3480
* https://github.com/golang/go/issues/25721
* https://learn.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-deletefilew
* https://linux.die.net/man/3/mmap",1,encoding json  please document that float  inf  inf nan will cause json marshal return error    what version of go are you using  go version    go version       darwin      does this issue reproduce with the latest release   it does with go playground    what did you do   same as            what did you expect to see   document that float  inf  inf nan will cause json marshal return error  or not throwing serialization errors on basic numeric data types with valid state     what did you see instead   no document of this kind of thing and return json  unsupported value  nan    should golang standard library document possible common error type of a package or a function like windows api document   or linux man     code with standard library sometime looks like try and fix again and again without document of possible common error type      reference                          ,1
306521,23163737507.0,IssuesEvent,2022-07-29 21:03:11,golang/go,https://api.github.com/repos/golang/go,closed,x/sys/windows: godoc is useless again,Documentation OS-Windows compiler/runtime,"The godoc for https://godoc.org/golang.org/x/sys/windows is empty, probably because of https://go-review.googlesource.com/24952 

Maybe this is a gddo problem too. (Or maybe gddo can help or have better heuristics over which build context to use)

/cc @alexbrainman @adg @broady @shantuo @alandonovan 
",1.0,"x/sys/windows: godoc is useless again - The godoc for https://godoc.org/golang.org/x/sys/windows is empty, probably because of https://go-review.googlesource.com/24952 

Maybe this is a gddo problem too. (Or maybe gddo can help or have better heuristics over which build context to use)

/cc @alexbrainman @adg @broady @shantuo @alandonovan 
",1,x sys windows  godoc is useless again   the godoc for   is empty  probably because of     maybe this is a gddo problem too   or maybe gddo can help or have better heuristics over which build context to use    cc  alexbrainman  adg  broady  shantuo  alandonovan  ,1
49618,7523803642.0,IssuesEvent,2018-04-13 03:15:47,golang/go,https://api.github.com/repos/golang/go,closed,runtime: document that calling LockOSThread in init will lock main to m0 (the first OS thread),Documentation NeedsFix,"Continued from a brief in-person discussion with Ian and Keith earlier today.

A lot of people (including myself) want to write GUI programs in Go; we even had `shiny` to provide our own solution to this desire. Most, if not all OSs, require that all GUI code runs on a single OS thread, but most don't care *which* OS thread is used. macOS is the exception — macOS consigns the idea that the very first thread created by the OS is the only one allowed to do GUI stuff, and it has a few ways to do this:

- it provides the `pthread_main_np()` function, which returns true if the current thread is the first thread the OS creates (and in the Darwin kernel, pthreads *are* the kernel threading model, in essence); WebKit calls this function directly
- libSystem.dylib, the shared library that all programs eventually link to (think kernel32.dll on Windows), uses `__attribute__((constructor))` to call a variety of thread-specific initialization functions in other libraries (such as libdispatch, which is important for modern Cocoa programming)
- Core Foundation, which Cocoa is built on top of, uses a variety of undocumented variables to control its own data structures that, while they can be overridden with the correct `extern` statements, will not catch all possible cases
- this list is probably incomplete

Various components in Cocoa have internal consistency checks to make sure they are only ever called on the ""main thread""; a program *will* abort if these checks fail.

In runtime-speak, the first thread created by the OS is called `m0` (or was called `m0` back when the runtime was written in C), so I will call it that from here on out.

On other platforms, we could just insert a `runtime.LockOSThread()` in a goroutine to tie the goroutine that will do all GUI stuff to an OS thread, but for macOS this alone wouldn't work. I have found a number of ways to bypass some of the above bullet points, but things just wind up breaking later (and I don't think the libdispatch thing can be hacked without hard-coding its internal data structures...).

And this doesn't even consider things like transpiled JavaScript (in which I don't even know what the requirements *are*) or mobile platforms (I'm sure iOS has the same requirements as macOS but I'm not sure about any other platform).

So far, the most widely used workaround has been to call `runtime.LockOSThread()` in `init`. I didn't think this was a good solution because there was no guarantee that `init` will always stay on `m0`, especially once `init` was allowed to run concurrently with other goroutines. However, after talking with Ian and Keith earlier today, I learned that this is already guaranteed, just not documented. If this was documented, then we could all safely rely on the behavior.

I wouldn't know if this should be documented in package runtime (under LockOSThread) or in the spec (as part of the definition of initialization behavior).

Furthermore, there's the potential that a different package's `init` will call `runtime.UnlockOSThread()`, most likely to undo its own `runtime.LockOSThread()` — in which case, `LockOSThread` should be nested. Nesting will handle the case of a *later* package calling `UnlockOSThread`, but not of an *earlier* one doing so too, so perhaps `UnlockOSThread` should also be made a no-op in `init` functions, if that's even possible.

And of course, all bets are off if another function in `main` calls `UnlockOSThread`. Even if this is also made a no-op (which is probably not a good idea), package authors will need to document what functions must be run in `main`. This isn't a problem, though; it's something package authors should know, though.",1.0,"runtime: document that calling LockOSThread in init will lock main to m0 (the first OS thread) - Continued from a brief in-person discussion with Ian and Keith earlier today.

A lot of people (including myself) want to write GUI programs in Go; we even had `shiny` to provide our own solution to this desire. Most, if not all OSs, require that all GUI code runs on a single OS thread, but most don't care *which* OS thread is used. macOS is the exception — macOS consigns the idea that the very first thread created by the OS is the only one allowed to do GUI stuff, and it has a few ways to do this:

- it provides the `pthread_main_np()` function, which returns true if the current thread is the first thread the OS creates (and in the Darwin kernel, pthreads *are* the kernel threading model, in essence); WebKit calls this function directly
- libSystem.dylib, the shared library that all programs eventually link to (think kernel32.dll on Windows), uses `__attribute__((constructor))` to call a variety of thread-specific initialization functions in other libraries (such as libdispatch, which is important for modern Cocoa programming)
- Core Foundation, which Cocoa is built on top of, uses a variety of undocumented variables to control its own data structures that, while they can be overridden with the correct `extern` statements, will not catch all possible cases
- this list is probably incomplete

Various components in Cocoa have internal consistency checks to make sure they are only ever called on the ""main thread""; a program *will* abort if these checks fail.

In runtime-speak, the first thread created by the OS is called `m0` (or was called `m0` back when the runtime was written in C), so I will call it that from here on out.

On other platforms, we could just insert a `runtime.LockOSThread()` in a goroutine to tie the goroutine that will do all GUI stuff to an OS thread, but for macOS this alone wouldn't work. I have found a number of ways to bypass some of the above bullet points, but things just wind up breaking later (and I don't think the libdispatch thing can be hacked without hard-coding its internal data structures...).

And this doesn't even consider things like transpiled JavaScript (in which I don't even know what the requirements *are*) or mobile platforms (I'm sure iOS has the same requirements as macOS but I'm not sure about any other platform).

So far, the most widely used workaround has been to call `runtime.LockOSThread()` in `init`. I didn't think this was a good solution because there was no guarantee that `init` will always stay on `m0`, especially once `init` was allowed to run concurrently with other goroutines. However, after talking with Ian and Keith earlier today, I learned that this is already guaranteed, just not documented. If this was documented, then we could all safely rely on the behavior.

I wouldn't know if this should be documented in package runtime (under LockOSThread) or in the spec (as part of the definition of initialization behavior).

Furthermore, there's the potential that a different package's `init` will call `runtime.UnlockOSThread()`, most likely to undo its own `runtime.LockOSThread()` — in which case, `LockOSThread` should be nested. Nesting will handle the case of a *later* package calling `UnlockOSThread`, but not of an *earlier* one doing so too, so perhaps `UnlockOSThread` should also be made a no-op in `init` functions, if that's even possible.

And of course, all bets are off if another function in `main` calls `UnlockOSThread`. Even if this is also made a no-op (which is probably not a good idea), package authors will need to document what functions must be run in `main`. This isn't a problem, though; it's something package authors should know, though.",1,runtime  document that calling lockosthread in init will lock main to    the first os thread    continued from a brief in person discussion with ian and keith earlier today     a lot of people  including myself  want to write gui programs in go  we even had  shiny  to provide our own solution to this desire  most  if not all oss  require that all gui code runs on a single os thread  but most don t care  which  os thread is used  macos is the exception — macos consigns the idea that the very first thread created by the os is the only one allowed to do gui stuff  and it has a few ways to do this       it provides the  pthread main np    function  which returns true if the current thread is the first thread the os creates  and in the darwin kernel  pthreads  are  the kernel threading model  in essence   webkit calls this function directly    libsystem dylib  the shared library that all programs eventually link to  think   dll on windows   uses    attribute    constructor    to call a variety of thread specific initialization functions in other libraries  such as libdispatch  which is important for modern cocoa programming     core foundation  which cocoa is built on top of  uses a variety of undocumented variables to control its own data structures that  while they can be overridden with the correct  extern  statements  will not catch all possible cases    this list is probably incomplete    various components in cocoa have internal consistency checks to make sure they are only ever called on the  main thread   a program  will  abort if these checks fail     in runtime speak  the first thread created by the os is called      or was called     back when the runtime was written in c   so i will call it that from here on out     on other platforms  we could just insert a  runtime lockosthread    in a goroutine to tie the goroutine that will do all gui stuff to an os thread  but for macos this alone wouldn t work  i have found a number of ways to bypass some of the above bullet points  but things just wind up breaking later  and i don t think the libdispatch thing can be hacked without hard coding its internal data structures         and this doesn t even consider things like transpiled javascript  in which i don t even know what the requirements  are   or mobile platforms  i m sure ios has the same requirements as macos but i m not sure about any other platform      so far  the most widely used workaround has been to call  runtime lockosthread    in  init   i didn t think this was a good solution because there was no guarantee that  init  will always stay on      especially once  init  was allowed to run concurrently with other goroutines  however  after talking with ian and keith earlier today  i learned that this is already guaranteed  just not documented  if this was documented  then we could all safely rely on the behavior     i wouldn t know if this should be documented in package runtime  under lockosthread  or in the spec  as part of the definition of initialization behavior      furthermore  there s the potential that a different package s  init  will call  runtime unlockosthread     most likely to undo its own  runtime lockosthread    — in which case   lockosthread  should be nested  nesting will handle the case of a  later  package calling  unlockosthread   but not of an  earlier  one doing so too  so perhaps  unlockosthread  should also be made a no op in  init  functions  if that s even possible     and of course  all bets are off if another function in  main  calls  unlockosthread   even if this is also made a no op  which is probably not a good idea   package authors will need to document what functions must be run in  main   this isn t a problem  though  it s something package authors should know  though ,1
44427,7108261829.0,IssuesEvent,2018-01-16 23:10:28,golang/go,https://api.github.com/repos/golang/go,closed,doc: inconsistent article for RWMutex,Documentation,"

### What version of Go are you using (`go version`)?

Both https://golang.org/pkg/sync/ and https://tip.golang.org/pkg/sync/

### What did you do?

I wasn't sure whether to write ""a RWMutex"" or ""an RWMutex"", so I Googled it.

https://www.google.com/search?q=golang+%22a+rwmutex%22
https://www.google.com/search?q=golang+%22an+rwmutex%22

### What did you expect to see?

I expected to see a considerably larger number of search results for one or the other of the Google results; or, I expected to see consistent usage in the sync documentation.

### What did you see instead?

I saw 268 results for ""a RWMutex"" and 212 results for ""an RWMutex"". Then I noticed the sync docs were in both search results. ""A RWMutex"" occurs twice in the official docs and ""an RWMutex"" occurs 3 times.

------

According to this [English StackExchange post](https://english.stackexchange.com/questions/1016/do-you-use-a-or-an-before-acronyms), ""a"" vs. ""an"" comes down to how the word is pronounced out loud. ""Read-write mutex"" is fewer syllables than ""arr-double-you mutex"", so I can see why it's natural to write ""a RWMutex"". Ultimately I would like to see one style or the other in the official docs so I don't have to think about which style to use.",1.0,"doc: inconsistent article for RWMutex - 

### What version of Go are you using (`go version`)?

Both https://golang.org/pkg/sync/ and https://tip.golang.org/pkg/sync/

### What did you do?

I wasn't sure whether to write ""a RWMutex"" or ""an RWMutex"", so I Googled it.

https://www.google.com/search?q=golang+%22a+rwmutex%22
https://www.google.com/search?q=golang+%22an+rwmutex%22

### What did you expect to see?

I expected to see a considerably larger number of search results for one or the other of the Google results; or, I expected to see consistent usage in the sync documentation.

### What did you see instead?

I saw 268 results for ""a RWMutex"" and 212 results for ""an RWMutex"". Then I noticed the sync docs were in both search results. ""A RWMutex"" occurs twice in the official docs and ""an RWMutex"" occurs 3 times.

------

According to this [English StackExchange post](https://english.stackexchange.com/questions/1016/do-you-use-a-or-an-before-acronyms), ""a"" vs. ""an"" comes down to how the word is pronounced out loud. ""Read-write mutex"" is fewer syllables than ""arr-double-you mutex"", so I can see why it's natural to write ""a RWMutex"". Ultimately I would like to see one style or the other in the official docs so I don't have to think about which style to use.",1,doc  inconsistent article for rwmutex           what version of go are you using   go version       both   and          what did you do     i wasn t sure whether to write  a rwmutex  or  an rwmutex   so i googled it                 what did you expect to see     i expected to see a considerably larger number of search results for one or the other of the google results  or  i expected to see consistent usage in the sync documentation         what did you see instead     i saw   results for  a rwmutex  and   results for  an rwmutex   then i noticed the sync docs were in both search results   a rwmutex  occurs twice in the official docs and  an rwmutex  occurs   times               according to this      a  vs   an  comes down to how the word is pronounced out loud   read write mutex  is fewer syllables than  arr double you mutex   so i can see why it s natural to write  a rwmutex   ultimately i would like to see one style or the other in the official docs so i don t have to think about which style to use ,1
45652,12972798660.0,IssuesEvent,2020-07-21 13:06:24,department-of-veterans-affairs/va.gov-cms,https://api.github.com/repos/department-of-veterans-affairs/va.gov-cms,closed,Migrate va_node_health_care_local_facility_status causes Database locks,Critical defect Unplanned work,"## Description

Currently the migration job `va_node_health_care_local_facility_status` causes table locks. When another request is made in the UI the following error occurs:

```
Drupal\Core\Database\DatabaseExceptionWrapper: SQLSTATE[HY000]: General error: 1205 Lock wait timeout exceeded; try restarting transaction: INSERT INTO {cache_config} ...
```

This is a follow up of https://github.com/department-of-veterans-affairs/va.gov-cms/issues/2131

## How to reproduce on stage

1. Run the following command:
`sudo -u apache bash -c 'source /etc/sysconfig/httpd; PATH=$PATH:/usr/local/bin composer yaml-tests --tests-file=tasks-periodic.yml --dry-run periodic'`
1. Go to the UI: https://staging.cms.va.gov/section/veterans-affairs

*Expected Results*
Page loads without errors

*Actual Result*
Error message occurs ""Website encountered an error"" and the error occurs in the error log: `Lock wait timeout exceeded`


## Acceptance Criteria
* The migration should not cause table locks.
",1.0,"Migrate va_node_health_care_local_facility_status causes Database locks - ## Description

Currently the migration job `va_node_health_care_local_facility_status` causes table locks. When another request is made in the UI the following error occurs:

```
Drupal\Core\Database\DatabaseExceptionWrapper: SQLSTATE[HY000]: General error: 1205 Lock wait timeout exceeded; try restarting transaction: INSERT INTO {cache_config} ...
```

This is a follow up of https://github.com/department-of-veterans-affairs/va.gov-cms/issues/2131

## How to reproduce on stage

1. Run the following command:
`sudo -u apache bash -c 'source /etc/sysconfig/httpd; PATH=$PATH:/usr/local/bin composer yaml-tests --tests-file=tasks-periodic.yml --dry-run periodic'`
1. Go to the UI: https://staging.cms.va.gov/section/veterans-affairs

*Expected Results*
Page loads without errors

*Actual Result*
Error message occurs ""Website encountered an error"" and the error occurs in the error log: `Lock wait timeout exceeded`


## Acceptance Criteria
* The migration should not cause table locks.
",0,migrate va node health care local facility status causes database locks      description  currently the migration job  va node health care local facility status  causes table locks  when another request is made in the ui the following error occurs       drupal core database databaseexceptionwrapper  sqlstate   general error    lock wait timeout exceeded  try restarting transaction  insert into  cache config           this is a follow up of       how to reproduce on stage     run the following command   sudo  u apache bash  c  source  etc sysconfig httpd  path  path  usr local bin composer yaml tests   tests file tasks periodic yml   dry run periodic      go to the ui      expected results  page loads without errors   actual result  error message occurs  website encountered an error  and the error occurs in the error log   lock wait timeout exceeded       acceptance criteria   the migration should not cause table locks  ,0
73037,9637101154.0,IssuesEvent,2019-05-16 07:59:48,golang/go,https://api.github.com/repos/golang/go,opened,crypto/tls: make it clear that implementation is compliant with RFC 5246,Documentation,"In #31933, @swanandt  pointed out that the following note at the top of the [crypto/tls package](https://golang.org/pkg/crypto/tls/):

> Package tls **partially implements** TLS 1.2, as specified in RFC 5246

may be misinterpreted as a warning about non-compliance with the RFC 5246. This is not the case, as @FiloSottile explained:

> As far as I know, we implement everything that is REQUIRED by RFC 5246, so we are in full compliance with it.

It may be useful to slightly change the wording of the doc to make it completely clear the only *optional* features (like DHE, topic of the discussion at #31933) are currently not implemented, and so the package is fully compliant with RFC 5246. 
",1.0,"crypto/tls: make it clear that implementation is compliant with RFC 5246 - In #31933, @swanandt  pointed out that the following note at the top of the [crypto/tls package](https://golang.org/pkg/crypto/tls/):

> Package tls **partially implements** TLS 1.2, as specified in RFC 5246

may be misinterpreted as a warning about non-compliance with the RFC 5246. This is not the case, as @FiloSottile explained:

> As far as I know, we implement everything that is REQUIRED by RFC 5246, so we are in full compliance with it.

It may be useful to slightly change the wording of the doc to make it completely clear the only *optional* features (like DHE, topic of the discussion at #31933) are currently not implemented, and so the package is fully compliant with RFC 5246. 
",1,crypto tls  make it clear that implementation is compliant with rfc     in      swanandt  pointed out that the following note at the top of the          package tls   partially implements   tls      as specified in rfc      may be misinterpreted as a warning about non compliance with the rfc    this is not the case  as  filosottile explained       as far as i know  we implement everything that is required by rfc    so we are in full compliance with it     it may be useful to slightly change the wording of the doc to make it completely clear the only  optional  features  like dhe  topic of the discussion at     are currently not implemented  and so the package is fully compliant with rfc      ,1
254907,8101306552.0,IssuesEvent,2018-08-12 12:11:20,curationexperts/laevigata,https://api.github.com/repos/curationexperts/laevigata,closed,Advisor and Committee Members not persisting,UI release priority review,"If I fill in a form, and enter an advisor and committee members, then save, then leave and come back, my advisor and committee members have not persisted.",1.0,"Advisor and Committee Members not persisting - If I fill in a form, and enter an advisor and committee members, then save, then leave and come back, my advisor and committee members have not persisted.",0,advisor and committee members not persisting   if i fill in a form  and enter an advisor and committee members  then save  then leave and come back  my advisor and committee members have not persisted ,0
94361,11864965098.0,IssuesEvent,2020-03-25 22:57:49,woocommerce/woocommerce-admin,https://api.github.com/repos/woocommerce/woocommerce-admin,opened,Use the <Card> WordPress component,Components Design,"As noted by @LevinMedia, all uses of the `<Card>` _WooCommerce_ component should be switched to the `<Card>` _WordPress_ component [[src](https://github.com/WordPress/gutenberg/tree/master/packages/components/src/card), [story](https://wordpress.github.io/gutenberg/?path=/story/components-card--default)]. (cc @jameskoster)

One possible approach to consider would be a deprecation path in which the `<Card>` _WooCommerce_ component would be reimplemented as a wrapper for the WordPress component (unless there is some incompatibility I'm unaware of). This way, all downstream usage (inside and outside of this repository) would use the ""common"" component sooner rather than later, and refactoring could proceed independently.

(For extra context: WooCommerce Payments is currently using `<Card>` from `@woocommerce/components` both [directly](https://github.com/Automattic/woocommerce-payments/blob/ddc2ebc1ce8305e02d93f46b9f687d57d6f6b08d/client/transaction-details/summary/index.js#L9) and [indirectly](https://github.com/Automattic/woocommerce-payments/blob/ddc2ebc1ce8305e02d93f46b9f687d57d6f6b08d/client/transactions/index.js#L10).)",1.0,"Use the <Card> WordPress component - As noted by @LevinMedia, all uses of the `<Card>` _WooCommerce_ component should be switched to the `<Card>` _WordPress_ component [[src](https://github.com/WordPress/gutenberg/tree/master/packages/components/src/card), [story](https://wordpress.github.io/gutenberg/?path=/story/components-card--default)]. (cc @jameskoster)

One possible approach to consider would be a deprecation path in which the `<Card>` _WooCommerce_ component would be reimplemented as a wrapper for the WordPress component (unless there is some incompatibility I'm unaware of). This way, all downstream usage (inside and outside of this repository) would use the ""common"" component sooner rather than later, and refactoring could proceed independently.

(For extra context: WooCommerce Payments is currently using `<Card>` from `@woocommerce/components` both [directly](https://github.com/Automattic/woocommerce-payments/blob/ddc2ebc1ce8305e02d93f46b9f687d57d6f6b08d/client/transaction-details/summary/index.js#L9) and [indirectly](https://github.com/Automattic/woocommerce-payments/blob/ddc2ebc1ce8305e02d93f46b9f687d57d6f6b08d/client/transactions/index.js#L10).)",0,use the   wordpress component   as noted by  levinmedia  all uses of the      woocommerce  component should be switched to the      wordpress  component          cc  jameskoster     one possible approach to consider would be a deprecation path in which the      woocommerce  component would be reimplemented as a wrapper for the wordpress component  unless there is some incompatibility i m unaware of   this way  all downstream usage  inside and outside of this repository  would use the  common  component sooner rather than later  and refactoring could proceed independently      for extra context  woocommerce payments is currently using     from   woocommerce components  both     and    ,0
234121,17934292723.0,IssuesEvent,2021-09-10 13:31:32,golang/go,https://api.github.com/repos/golang/go,closed,embed: guarantee `(*FS).Open`'s returning value implements `io.Seeker`,Documentation help wanted NeedsFix,"From the current document, there is no guarantee whether `(*embed.FS).Open`'s returning value implements `io.Seeker` or not.

> Open opens the named file for reading and returns it as an fs.File.

IIUC the returned value always implements `io.Seeker` in the current implementation, and actually it is fine to assume this (e.g., https://github.com/golang/go/issues/44175#issuecomment-775545730). Would it be possible to make the current behavior explicit in the document?",1.0,"embed: guarantee `(*FS).Open`'s returning value implements `io.Seeker` - From the current document, there is no guarantee whether `(*embed.FS).Open`'s returning value implements `io.Seeker` or not.

> Open opens the named file for reading and returns it as an fs.File.

IIUC the returned value always implements `io.Seeker` in the current implementation, and actually it is fine to assume this (e.g., https://github.com/golang/go/issues/44175#issuecomment-775545730). Would it be possible to make the current behavior explicit in the document?",1,embed  guarantee    fs  open  s returning value implements  io seeker    from the current document  there is no guarantee whether    embed fs  open  s returning value implements  io seeker  or not       open opens the named file for reading and returns it as an fs file     iiuc the returned value always implements  io seeker  in the current implementation  and actually it is fine to assume this  e g     would it be possible to make the current behavior explicit in the document ,1
1977,7104659926.0,IssuesEvent,2018-01-16 10:44:24,PoisonousJohn/AzureGameRoomsScaler,https://api.github.com/repos/PoisonousJohn/AzureGameRoomsScaler,closed,Proposed architecture,architecture,"The application should have a storage mechanism (Table Storage?) to store information about running VMs. This should contain
- VM unique ID (maybe its full ARM ID)
- VM state
- Public IP (if needed)
- whatever else is needed by the game (ports? if available, of course)


VM state should have one of the following values
- Creating
- Running
- MarkedForDeletion

The API Function should have the following operations
- CreateVM. This would check our storage. 
  - If there is at least one VM in the Creating state, the operation should exit. 
  - If there is at least one VM in the MarkedForDeletion state, its state will change to Running and the operation should exit. 
  - Else, this operation should use ARM API to create a new VM. The VM will be marked as Creating state in the storage. When it is created, there will be a mechanism that will update our storage with the new details of the new VM and set its status to Running. (mechanism will probably be Function + Event Grid)
- GetGameRooms(VM_ID). This would ask the VM (via a well-known REST API method) for the current running game rooms/sessions. If there are zero, this operation will call the DeleteVM operation.
- DeleteVM(VM_ID). This will delete the VM via Azure ARM API and the associated line from the storage.
- MarkVMForDeletion(VM_ID): This will mark the VM as MarkedForDeletion in the storage.
- ScheduleGameSession: This method will return a VM that is in the Running state. We should examine if we should somehow get CPU%, RAM% so that we select the VM with the current lowest load.

There should also be another Function that will run on a timed trigger (every 1 minute?) that will enumerate all VMs in the Storage that are MarkedForDeletion. For each one of them, it will call the GetGameRooms operation. If it returns zero, then the Function will call the DeleteVM operation.",1.0,"Proposed architecture - The application should have a storage mechanism (Table Storage?) to store information about running VMs. This should contain
- VM unique ID (maybe its full ARM ID)
- VM state
- Public IP (if needed)
- whatever else is needed by the game (ports? if available, of course)


VM state should have one of the following values
- Creating
- Running
- MarkedForDeletion

The API Function should have the following operations
- CreateVM. This would check our storage. 
  - If there is at least one VM in the Creating state, the operation should exit. 
  - If there is at least one VM in the MarkedForDeletion state, its state will change to Running and the operation should exit. 
  - Else, this operation should use ARM API to create a new VM. The VM will be marked as Creating state in the storage. When it is created, there will be a mechanism that will update our storage with the new details of the new VM and set its status to Running. (mechanism will probably be Function + Event Grid)
- GetGameRooms(VM_ID). This would ask the VM (via a well-known REST API method) for the current running game rooms/sessions. If there are zero, this operation will call the DeleteVM operation.
- DeleteVM(VM_ID). This will delete the VM via Azure ARM API and the associated line from the storage.
- MarkVMForDeletion(VM_ID): This will mark the VM as MarkedForDeletion in the storage.
- ScheduleGameSession: This method will return a VM that is in the Running state. We should examine if we should somehow get CPU%, RAM% so that we select the VM with the current lowest load.

There should also be another Function that will run on a timed trigger (every 1 minute?) that will enumerate all VMs in the Storage that are MarkedForDeletion. For each one of them, it will call the GetGameRooms operation. If it returns zero, then the Function will call the DeleteVM operation.",0,proposed architecture   the application should have a storage mechanism  table storage   to store information about running vms  this should contain    vm unique id  maybe its full arm id     vm state    public ip  if needed     whatever else is needed by the game  ports  if available  of course       vm state should have one of the following values    creating    running    markedfordeletion    the api function should have the following operations    createvm  this would check our storage        if there is at least one vm in the creating state  the operation should exit        if there is at least one vm in the markedfordeletion state  its state will change to running and the operation should exit        else  this operation should use arm api to create a new vm  the vm will be marked as creating state in the storage  when it is created  there will be a mechanism that will update our storage with the new details of the new vm and set its status to running   mechanism will probably be function   event grid     getgamerooms vm id   this would ask the vm  via a well known rest api method  for the current running game rooms sessions  if there are zero  this operation will call the deletevm operation     deletevm vm id   this will delete the vm via azure arm api and the associated line from the storage     markvmfordeletion vm id   this will mark the vm as markedfordeletion in the storage     schedulegamesession  this method will return a vm that is in the running state  we should examine if we should somehow get cpu   ram  so that we select the vm with the current lowest load     there should also be another function that will run on a timed trigger  every   minute   that will enumerate all vms in the storage that are markedfordeletion  for each one of them  it will call the getgamerooms operation  if it returns zero  then the function will call the deletevm operation ,0
24406,5060710608.0,IssuesEvent,2016-12-22 13:05:56,golang/go,https://api.github.com/repos/golang/go,opened,wiki: document Github Issue labels,Documentation,"People don't understand the Github issue labels we use, or our general issue lifecycle.

Document it.
",1.0,"wiki: document Github Issue labels - People don't understand the Github issue labels we use, or our general issue lifecycle.

Document it.
",1,wiki  document github issue labels   people don t understand the github issue labels we use  or our general issue lifecycle     document it   ,1
87635,10934365137.0,IssuesEvent,2019-11-24 11:04:01,MarlinFirmware/Marlin,https://api.github.com/repos/MarlinFirmware/Marlin,closed,[Discussion] Handling of junction speeds and jerk,T: Design Concept T: Development,"This is a follow-up to a topic which already was here a long time ago, but I can't find it anymore. If someone remebers it and can find the issue, you might link it here.

During the research for strange jerk behaviour today I stumbled around the suboptimal handling of junction speeds again. In one sentence: Marlins way of handling jerk and junction speeds leads to exceeded jerk in some daily situations.
The attached test gcode and the results in the table should clarify things a bit. The gcode does the following things:
- set the jerk speeds to the selected values
- First it does 4 G1 travel moves
- followed by 4 G1 print moves
- in the last round it does a prime move (extruder only), followed by two print moves, a retract - travel - prime combination and again a print move.

I printed the following values over serial:
- max junction speed as calculated by the jerk code inside the planner
- initial and final step rate of each block as it gets executed
- initial and final speed of each block (step rate / steps/mm), this one is calculated inside Excel by hand

I did two runs, first with X and Y jerk set to 5 and E jerk set to 1mm/s, and a second one switching the values. As you can see, as soon as we are switching between extruder only moves and XY moves things start to get wired. Same should be true for Z only moves and XY moves.
The problem is that Marlin connects each segment by one single junction speed, which is not always what is needed. A simple example like the one from H13 in the table, lets assume a X Jerk of 1, an E jerk of 5. Let's do a print move along X followed by a prime move. What we want ist:
- Start with a jerk speed of 1
- Accelerate to cruising speed
- Decelerate to jerk speed **1**. The extruder speed in this case is nearly 0 due to the low X jerk.
- Now the prime move, start with a jerk speed of **5**
- accelerate, cruise and decelerate to jerk speed of 5 again.

The two axis X and E are not linked, also their junction speeds shouldn't be linked. What Marlin does is in this case is:
- Start with a jerk speed of 1
- Accelerate to cruising speed
- Decelerate to jerk speed **5** -> Ignoring the needed final speed of 1!
- Now the prime move, start with a jerk speed of **5**
- accelerate, cruise and decelerate to jerk speed of **1** -> Jerk value from next print move!

![jerk](https://user-images.githubusercontent.com/10776877/36938099-ecf9eb4e-1f1c-11e8-98c9-90bdcee23900.JPG)

It becomes crucial when we replace the first print move by a Z move. Z axis often have 0.x jerk values, but the final speed would be also 5mm/s due to the following retract move.

Conclusion:
- A junction speed in terms of final speed = next start speed is only needed to give a smooth movement along a 3D path. Retracts and prime movements does not fall into this, so their speeds should be decoupled.
- Same is true for extruder speed changes due to variable width paths: the 3D movement XYZ has always a connected speed, but the extruder speed can jump at the junctions.
- If we have to connect end and start speeds, we always have to check if all axis can follow the choosen final or start speed. We can't finish X at 5mm/s if it needs 1mm/s only because the next E move can start at 5mm/s.
- That was the easy part. Any ideas how such a jerk implementation could look like? GRBL will not help, as this is a 3D printer specific problem.

Files:
[Marlin Junction speeds.zip](https://github.com/MarlinFirmware/Marlin/files/1777767/Marlin.Junction.speeds.zip)
",1.0,"[Discussion] Handling of junction speeds and jerk - This is a follow-up to a topic which already was here a long time ago, but I can't find it anymore. If someone remebers it and can find the issue, you might link it here.

During the research for strange jerk behaviour today I stumbled around the suboptimal handling of junction speeds again. In one sentence: Marlins way of handling jerk and junction speeds leads to exceeded jerk in some daily situations.
The attached test gcode and the results in the table should clarify things a bit. The gcode does the following things:
- set the jerk speeds to the selected values
- First it does 4 G1 travel moves
- followed by 4 G1 print moves
- in the last round it does a prime move (extruder only), followed by two print moves, a retract - travel - prime combination and again a print move.

I printed the following values over serial:
- max junction speed as calculated by the jerk code inside the planner
- initial and final step rate of each block as it gets executed
- initial and final speed of each block (step rate / steps/mm), this one is calculated inside Excel by hand

I did two runs, first with X and Y jerk set to 5 and E jerk set to 1mm/s, and a second one switching the values. As you can see, as soon as we are switching between extruder only moves and XY moves things start to get wired. Same should be true for Z only moves and XY moves.
The problem is that Marlin connects each segment by one single junction speed, which is not always what is needed. A simple example like the one from H13 in the table, lets assume a X Jerk of 1, an E jerk of 5. Let's do a print move along X followed by a prime move. What we want ist:
- Start with a jerk speed of 1
- Accelerate to cruising speed
- Decelerate to jerk speed **1**. The extruder speed in this case is nearly 0 due to the low X jerk.
- Now the prime move, start with a jerk speed of **5**
- accelerate, cruise and decelerate to jerk speed of 5 again.

The two axis X and E are not linked, also their junction speeds shouldn't be linked. What Marlin does is in this case is:
- Start with a jerk speed of 1
- Accelerate to cruising speed
- Decelerate to jerk speed **5** -> Ignoring the needed final speed of 1!
- Now the prime move, start with a jerk speed of **5**
- accelerate, cruise and decelerate to jerk speed of **1** -> Jerk value from next print move!

![jerk](https://user-images.githubusercontent.com/10776877/36938099-ecf9eb4e-1f1c-11e8-98c9-90bdcee23900.JPG)

It becomes crucial when we replace the first print move by a Z move. Z axis often have 0.x jerk values, but the final speed would be also 5mm/s due to the following retract move.

Conclusion:
- A junction speed in terms of final speed = next start speed is only needed to give a smooth movement along a 3D path. Retracts and prime movements does not fall into this, so their speeds should be decoupled.
- Same is true for extruder speed changes due to variable width paths: the 3D movement XYZ has always a connected speed, but the extruder speed can jump at the junctions.
- If we have to connect end and start speeds, we always have to check if all axis can follow the choosen final or start speed. We can't finish X at 5mm/s if it needs 1mm/s only because the next E move can start at 5mm/s.
- That was the easy part. Any ideas how such a jerk implementation could look like? GRBL will not help, as this is a 3D printer specific problem.

Files:
[Marlin Junction speeds.zip](https://github.com/MarlinFirmware/Marlin/files/1777767/Marlin.Junction.speeds.zip)
",0,  handling of junction speeds and jerk   this is a follow up to a topic which already was here a long time ago  but i can t find it anymore  if someone remebers it and can find the issue  you might link it here     during the research for strange jerk behaviour today i stumbled around the suboptimal handling of junction speeds again  in one sentence  marlins way of handling jerk and junction speeds leads to exceeded jerk in some daily situations   the attached test gcode and the results in the table should clarify things a bit  the gcode does the following things     set the jerk speeds to the selected values    first it does     travel moves    followed by     print moves    in the last round it does a prime move  extruder only   followed by two print moves  a retract   travel   prime combination and again a print move     i printed the following values over serial     max junction speed as calculated by the jerk code inside the planner    initial and final step rate of each block as it gets executed    initial and final speed of each block  step rate   steps mm   this one is calculated inside excel by hand    i did two runs  first with x and y jerk set to   and e jerk set to   s  and a second one switching the values  as you can see  as soon as we are switching between extruder only moves and xy moves things start to get wired  same should be true for z only moves and xy moves   the problem is that marlin connects each segment by one single junction speed  which is not always what is needed  a simple example like the one from   in the table  lets assume a x jerk of    an e jerk of    let s do a print move along x followed by a prime move  what we want ist     start with a jerk speed of      accelerate to cruising speed    decelerate to jerk speed        the extruder speed in this case is nearly   due to the low x jerk     now the prime move  start with a jerk speed of          accelerate  cruise and decelerate to jerk speed of   again     the two axis x and e are not linked  also their junction speeds shouldn t be linked  what marlin does is in this case is     start with a jerk speed of      accelerate to cruising speed    decelerate to jerk speed          ignoring the needed final speed of       now the prime move  start with a jerk speed of          accelerate  cruise and decelerate to jerk speed of          jerk value from next print move             it becomes crucial when we replace the first print move by a z move  z axis often have   x jerk values  but the final speed would be also   s due to the following retract move     conclusion     a junction speed in terms of final speed   next start speed is only needed to give a smooth movement along a   path  retracts and prime movements does not fall into this  so their speeds should be decoupled     same is true for extruder speed changes due to variable width paths  the   movement xyz has always a connected speed  but the extruder speed can jump at the junctions     if we have to connect end and start speeds  we always have to check if all axis can follow the choosen final or start speed  we can t finish x at   s if it needs   s only because the next e move can start at   s     that was the easy part  any ideas how such a jerk implementation could look like  grbl will not help  as this is a   printer specific problem     files        ,0
73211,9653282168.0,IssuesEvent,2019-05-19 02:25:26,golang/go,https://api.github.com/repos/golang/go,opened,net/http/httptest: deprecate ResponseRecorder.Header method as well,Documentation NeedsFix,"(This is a continuation of #25763 and #16717.)

The `httptest.ResponseRecorder.HeaderMap` struct field was deprecated in [CL 117675](https://golang.org/cl/117675), with the deprecation notice pointing users to the `Response.Header` map as returned by the `Result` method. This was to resolve issue #25763 (which provides rationale for why that was done).

However, there's also a `ResponseRecorder.Header` method which does little more than provide direct access to the `HeaderMap` field (it also initializes the map if it's `nil`):

```Go
// Header returns the response headers.
func (rw *ResponseRecorder) Header() http.Header {
	m := rw.HeaderMap
	if m == nil {
		m = make(http.Header)
		rw.HeaderMap = m
	}
	return m
}
```

This puts users in an awkward position. If they read the deprecation notice on the `HeaderMap` field (and understand the rationale for why it was deprecated by reading through issue #25763), and also know the internal implementation details of the `Header` method, they'll know that they shouldn't be using the `Header` method either.

If they don't know the internal implementation details of the `Header` method, they won't know how it differs from the `Response.Header` map as returned by the `Result` method and how to decide which one to use.

Users shouldn't have to read the internal implementation of methods and make these kind of deductions. If the `HeaderMap` field is deprecated, the current `Header` method should be too:

```diff
-// Header returns the response headers.
+// Header returns the response headers explicitly set by the Handler.
+// It is an internal detail.
+//
+// Deprecated: Header exists for historical compatibility
+// and should not be used. To access the headers returned by a handler,
+// use the Response.Header map as returned by the Result method.
 func (rw *ResponseRecorder) Header() http.Header {
```

/cc @cespare @bradfitz @dominikh",1.0,"net/http/httptest: deprecate ResponseRecorder.Header method as well - (This is a continuation of #25763 and #16717.)

The `httptest.ResponseRecorder.HeaderMap` struct field was deprecated in [CL 117675](https://golang.org/cl/117675), with the deprecation notice pointing users to the `Response.Header` map as returned by the `Result` method. This was to resolve issue #25763 (which provides rationale for why that was done).

However, there's also a `ResponseRecorder.Header` method which does little more than provide direct access to the `HeaderMap` field (it also initializes the map if it's `nil`):

```Go
// Header returns the response headers.
func (rw *ResponseRecorder) Header() http.Header {
	m := rw.HeaderMap
	if m == nil {
		m = make(http.Header)
		rw.HeaderMap = m
	}
	return m
}
```

This puts users in an awkward position. If they read the deprecation notice on the `HeaderMap` field (and understand the rationale for why it was deprecated by reading through issue #25763), and also know the internal implementation details of the `Header` method, they'll know that they shouldn't be using the `Header` method either.

If they don't know the internal implementation details of the `Header` method, they won't know how it differs from the `Response.Header` map as returned by the `Result` method and how to decide which one to use.

Users shouldn't have to read the internal implementation of methods and make these kind of deductions. If the `HeaderMap` field is deprecated, the current `Header` method should be too:

```diff
-// Header returns the response headers.
+// Header returns the response headers explicitly set by the Handler.
+// It is an internal detail.
+//
+// Deprecated: Header exists for historical compatibility
+// and should not be used. To access the headers returned by a handler,
+// use the Response.Header map as returned by the Result method.
 func (rw *ResponseRecorder) Header() http.Header {
```

/cc @cespare @bradfitz @dominikh",1,net http httptest  deprecate responserecorder header method as well    this is a continuation of    and         the  httptest responserecorder headermap  struct field was deprecated in     with the deprecation notice pointing users to the  response header  map as returned by the  result  method  this was to resolve issue     which provides rationale for why that was done      however  there s also a  responserecorder header  method which does little more than provide direct access to the  headermap  field  it also initializes the map if it s  nil          go     header returns the response headers   func  rw  responserecorder  header   http header    	m    rw headermap  	if m    nil    		m   make http header   		rw headermap   m  	   	return m            this puts users in an awkward position  if they read the deprecation notice on the  headermap  field  and understand the rationale for why it was deprecated by reading through issue      and also know the internal implementation details of the  header  method  they ll know that they shouldn t be using the  header  method either     if they don t know the internal implementation details of the  header  method  they won t know how it differs from the  response header  map as returned by the  result  method and how to decide which one to use     users shouldn t have to read the internal implementation of methods and make these kind of deductions  if the  headermap  field is deprecated  the current  header  method should be too        diff      header returns the response headers       header returns the response headers explicitly set by the handler       it is an internal detail            deprecated  header exists for historical compatibility      and should not be used  to access the headers returned by a handler       use the response header map as returned by the result method    func  rw  responserecorder  header   http header            cc  cespare  bradfitz  dominikh,1
25027,5118067182.0,IssuesEvent,2017-01-07 23:55:42,golang/go,https://api.github.com/repos/golang/go,closed,go/types: typo in doc,Documentation NeedsFix,"In go/types/api.go in the package comment, it says in the first paragraph ""create a new type checked with NewChecker"". It says ""checked"" but should be ""checker"".
This confused me, so I am reporting it here (since pull requests are not accepted).",1.0,"go/types: typo in doc - In go/types/api.go in the package comment, it says in the first paragraph ""create a new type checked with NewChecker"". It says ""checked"" but should be ""checker"".
This confused me, so I am reporting it here (since pull requests are not accepted).",1,go types  typo in doc   in go types api go in the package comment  it says in the first paragraph  create a new type checked with newchecker   it says  checked  but should be  checker    this confused me  so i am reporting it here  since pull requests are not accepted  ,1
64006,8705368795.0,IssuesEvent,2018-12-05 22:11:23,golang/go,https://api.github.com/repos/golang/go,closed,doc: add release notes for go run supporting for 'go run pkg' or 'go run .',Documentation,"Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
go version go1.10 linux/amd64


### Does this issue reproduce with the latest release?

yes

### What operating system and processor architecture are you using (`go env`)?
```bash
GOARCH=""amd64""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GORACE=""""
GOROOT=""/usr/local/go""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build166682806=/tmp/go-build -gno-record-gcc-switches""
```

### What did you do?
navigated to https://tip.golang.org/doc/go1.11

### What did you expect to see?
release notes about  `go run` now having support for `go run pkg` or `go run .`

### What did you see instead?
nothing on that topic

ref:
- https://github.com/golang/go/issues/22726

",1.0,"doc: add release notes for go run supporting for 'go run pkg' or 'go run .' - Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
go version go1.10 linux/amd64


### Does this issue reproduce with the latest release?

yes

### What operating system and processor architecture are you using (`go env`)?
```bash
GOARCH=""amd64""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GORACE=""""
GOROOT=""/usr/local/go""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build166682806=/tmp/go-build -gno-record-gcc-switches""
```

### What did you do?
navigated to https://tip.golang.org/doc/go1.11

### What did you expect to see?
release notes about  `go run` now having support for `go run pkg` or `go run .`

### What did you see instead?
nothing on that topic

ref:
- https://github.com/golang/go/issues/22726

",1,doc  add release notes for go run supporting for  go run pkg  or  go run      please answer these questions before submitting your issue  thanks           what version of go are you using   go version     go version     linux            does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env        bash  goarch      gohostarch      gohostos  linux   goos  linux   gorace     goroot   usr local go   gotmpdir     gotooldir   usr local go pkg tool linux     gccgo  gccgo   cc  gcc   cxx  g     cgo enabled      cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches              what did you do   navigated to          what did you expect to see   release notes about   go run  now having support for  go run pkg  or  go run           what did you see instead   nothing on that topic    ref          ,1
124612,4927647097.0,IssuesEvent,2016-11-26 21:29:06,esengoba/SWE_Project,https://api.github.com/repos/esengoba/SWE_Project,opened,Change the constant for title font to a slightly smaller size,enhancement low priority,Change the constant for title font to a slightly smaller size,1.0,Change the constant for title font to a slightly smaller size - Change the constant for title font to a slightly smaller size,0,change the constant for title font to a slightly smaller size   change the constant for title font to a slightly smaller size,0
39153,6725161212.0,IssuesEvent,2017-10-17 03:21:45,golang/go,https://api.github.com/repos/golang/go,opened,runtime: GOROOT() docs are confusing,Documentation,"The docs say:
```
GOROOT returns the root of the Go tree. It uses the GOROOT environment variable, if set, or else the root used during the Go build.
```

Thus I expect this would print ""Hi!"":

```go
package main

import (
    ""fmt""
    ""log""
    ""os""
    ""runtime""
)

func main() {
    err := os.Setenv(""GOROOT"", ""Hi!"")
    if err != nil {
        log.Fatal(err)
    }
    fmt.Println(runtime.GOROOT())
}
```

However, this prints my real goroot, not ""Hi!"".

Either GOROOT() should actually check the environment variable when called, or the docs should be clarified to specify that it returns the GOROOT environment variable set at init() time.",1.0,"runtime: GOROOT() docs are confusing - The docs say:
```
GOROOT returns the root of the Go tree. It uses the GOROOT environment variable, if set, or else the root used during the Go build.
```

Thus I expect this would print ""Hi!"":

```go
package main

import (
    ""fmt""
    ""log""
    ""os""
    ""runtime""
)

func main() {
    err := os.Setenv(""GOROOT"", ""Hi!"")
    if err != nil {
        log.Fatal(err)
    }
    fmt.Println(runtime.GOROOT())
}
```

However, this prints my real goroot, not ""Hi!"".

Either GOROOT() should actually check the environment variable when called, or the docs should be clarified to specify that it returns the GOROOT environment variable set at init() time.",1,runtime  goroot   docs are confusing   the docs say        goroot returns the root of the go tree  it uses the goroot environment variable  if set  or else the root used during the go build          thus i expect this would print  hi          go  package main    import         fmt        log        os        runtime        func main          err    os setenv  goroot    hi         if err    nil            log fatal err              fmt println runtime goroot               however  this prints my real goroot  not  hi       either goroot   should actually check the environment variable when called  or the docs should be clarified to specify that it returns the goroot environment variable set at init   time ,1
41809,6949168874.0,IssuesEvent,2017-12-06 04:40:58,golang/go,https://api.github.com/repos/golang/go,opened,build: announce end of support for old macOS releases,Documentation NeedsDecision release-blocker,"Apple continues to put out new macOS releases. We can't run builders for all of them forever.

I propose we announce in the Go 1.10 release notes that Go 1.10 will be the last release to officially support macOS 10.8 (Mountain Lion).

macOS 10.8 was last updated Oct 3, 2013, over 4 years ago.

(macOS 10.9 was last updated Mar 21, 2016, 19 months ago, which is somewhat more recent)

Apple doesn't publish official End-of-Life dates for macOS versions, but I read that their security policy is that they issue security updates for the past 3 releases.

Given that they're on 10.13 now, that means 10.13, 10.12, and 10.11 are supported by them.

Our policy of additionally supporting 10.10 and 10.8 in Go 1.11 would be even more.

/cc @rsc @ianlancetaylor ",1.0,"build: announce end of support for old macOS releases - Apple continues to put out new macOS releases. We can't run builders for all of them forever.

I propose we announce in the Go 1.10 release notes that Go 1.10 will be the last release to officially support macOS 10.8 (Mountain Lion).

macOS 10.8 was last updated Oct 3, 2013, over 4 years ago.

(macOS 10.9 was last updated Mar 21, 2016, 19 months ago, which is somewhat more recent)

Apple doesn't publish official End-of-Life dates for macOS versions, but I read that their security policy is that they issue security updates for the past 3 releases.

Given that they're on 10.13 now, that means 10.13, 10.12, and 10.11 are supported by them.

Our policy of additionally supporting 10.10 and 10.8 in Go 1.11 would be even more.

/cc @rsc @ianlancetaylor ",1,build  announce end of support for old macos releases   apple continues to put out new macos releases  we can t run builders for all of them forever     i propose we announce in the go     release notes that go     will be the last release to officially support macos      mountain lion      macos     was last updated oct       over   years ago      macos     was last updated mar         months ago  which is somewhat more recent     apple doesn t publish official end of life dates for macos versions  but i read that their security policy is that they issue security updates for the past   releases     given that they re on     now  that means           and     are supported by them     our policy of additionally supporting     and     in go     would be even more      cc  rsc  ianlancetaylor ,1
498167,14402151615.0,IssuesEvent,2020-12-03 14:35:04,Aktanusa/CookieMonster,https://api.github.com/repos/Aktanusa/CookieMonster,closed,All calculations are off when a golden cookie appears,Bug HIGH priority,"There is something going wrong with all calculations whenever a golden cookie appears on screen.
I had not time to investigate but this is a pretty important bug so should be fixed asap.

Perhaps @Chorizorro knows if something changed with the general calculations after the we merged the changes related to the Lucky/Chain calculations when cookies appear?

I made a new branch `fix/gcbug` where a hotfix to this issue should be applied to.",1.0,"All calculations are off when a golden cookie appears - There is something going wrong with all calculations whenever a golden cookie appears on screen.
I had not time to investigate but this is a pretty important bug so should be fixed asap.

Perhaps @Chorizorro knows if something changed with the general calculations after the we merged the changes related to the Lucky/Chain calculations when cookies appear?

I made a new branch `fix/gcbug` where a hotfix to this issue should be applied to.",0,all calculations are off when a golden cookie appears   there is something going wrong with all calculations whenever a golden cookie appears on screen   i had not time to investigate but this is a pretty important bug so should be fixed asap     perhaps  chorizorro knows if something changed with the general calculations after the we merged the changes related to the lucky chain calculations when cookies appear     i made a new branch  fix gcbug  where a hotfix to this issue should be applied to ,0
56257,8059339284.0,IssuesEvent,2018-08-02 21:34:55,golang/go,https://api.github.com/repos/golang/go,closed,encoding/xml: bulleted lists badly formatted in documentation,Documentation NeedsFix help wanted,"The bulleted lists in the doc comments for Marshal, Unmarshal, and perhaps others are indented in a way that confuses the formatter for golang.org/pkg. (It thinks they're code instead of prose.)

![screenshot 2018-08-02 at 16 42 16](https://user-images.githubusercontent.com/5200974/43610070-46188316-9673-11e8-9f3b-f9314c1451e4.png)
",1.0,"encoding/xml: bulleted lists badly formatted in documentation - The bulleted lists in the doc comments for Marshal, Unmarshal, and perhaps others are indented in a way that confuses the formatter for golang.org/pkg. (It thinks they're code instead of prose.)

![screenshot 2018-08-02 at 16 42 16](https://user-images.githubusercontent.com/5200974/43610070-46188316-9673-11e8-9f3b-f9314c1451e4.png)
",1,encoding xml  bulleted lists badly formatted in documentation   the bulleted lists in the doc comments for marshal  unmarshal  and perhaps others are indented in a way that confuses the formatter for golang org pkg   it thinks they re code instead of prose            ,1
651589,21482522671.0,IssuesEvent,2022-04-26 19:14:49,ntop/ntopng,https://api.github.com/repos/ntop/ntopng,closed,Data Retention Behaviour Needs Rework,enhancement waiting for review priority ticket,"In preferences, the data retention is not specified properly as it is not clear to what data it applies.

This ticket is to ask to
- Specify the ClickHouse data retention and RRD/InfluxDB data retention in two different preferences fields.
- Specify that the RRD retention (due to the RRD nature) is taken from preferences when the RRD file is created and contrary to Influx it cannot changed afterwards
- Specify that no retention is honoured for other exports (e.g. Elastic)
- Check how the MySQL retention is implemented",1.0,"Data Retention Behaviour Needs Rework - In preferences, the data retention is not specified properly as it is not clear to what data it applies.

This ticket is to ask to
- Specify the ClickHouse data retention and RRD/InfluxDB data retention in two different preferences fields.
- Specify that the RRD retention (due to the RRD nature) is taken from preferences when the RRD file is created and contrary to Influx it cannot changed afterwards
- Specify that no retention is honoured for other exports (e.g. Elastic)
- Check how the MySQL retention is implemented",0,data retention behaviour needs rework   in preferences  the data retention is not specified properly as it is not clear to what data it applies     this ticket is to ask to    specify the clickhouse data retention and rrd influxdb data retention in two different preferences fields     specify that the rrd retention  due to the rrd nature  is taken from preferences when the rrd file is created and contrary to influx it cannot changed afterwards    specify that no retention is honoured for other exports  e g  elastic     check how the mysql retention is implemented,0
263791,19975830588.0,IssuesEvent,2022-01-29 03:54:07,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: update -trimpath documentation,Documentation help wanted NeedsFix,"<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go1.18beta1
</pre>


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/hakim/Library/Caches/go-build""
GOENV=""/Users/hakim/Library/Application Support/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/hakim/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/hakim/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/Users/hakim/sdk/go1.18beta1""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/Users/hakim/sdk/go1.18beta1/pkg/tool/darwin_amd64""
GOVCS=""""
GOVERSION=""go1.18beta1""
GCCGO=""gccgo""
GOAMD64=""v1""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/hakim/ww/go.mod""
GOWORK=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/bw/6r6k9d113sv1_vvzk_1kfxbm001py5/T/go-build1609535835=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?

Built the following program with `-trimpath` ( `% go build -trimpath -o out` )    
 
```
--- go.mod ---
module work

go 1.17

require golang.org/x/mod v0.5.1

--- main.go ---
package main

import (
        ""golang.org/x/mod/semver""
)

func main() {
        if semver.IsValid(""1.0.0"") {
                println(""valid"")
        }
}
```

### What did you expect to see?

As described in `go1.18beta1 help build`, expected to see files from standard packages start with ""go""
>         -trimpath
>                 remove all file system paths from the resulting executable.
>                 Instead of absolute file system paths, the recorded file names
>                 will begin with either ""go"" (for the standard library),
>                 or a module path@version (when using modules),
>                 or a plain import path (when using GOPATH).

### What did you see instead?

Files from standard libraries without ""go"" (plain import path + file base name)
```
% strings out | grep map.go
runtime/mbitmap.go
runtime/map.go
```

Description for packages from dependency modules seems correct.

```
% strings out | grep semver.go
golang.org/x/mod@v0.5.1/semver/semver.go
```

Maybe need to mention behavior for main module files explicitly.
```
% strings out | grep main.go  
work/main.go
```",1.0,"cmd/go: update -trimpath documentation - <!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go1.18beta1
</pre>


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/hakim/Library/Caches/go-build""
GOENV=""/Users/hakim/Library/Application Support/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/hakim/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/hakim/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/Users/hakim/sdk/go1.18beta1""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/Users/hakim/sdk/go1.18beta1/pkg/tool/darwin_amd64""
GOVCS=""""
GOVERSION=""go1.18beta1""
GCCGO=""gccgo""
GOAMD64=""v1""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/hakim/ww/go.mod""
GOWORK=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/bw/6r6k9d113sv1_vvzk_1kfxbm001py5/T/go-build1609535835=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?

Built the following program with `-trimpath` ( `% go build -trimpath -o out` )    
 
```
--- go.mod ---
module work

go 1.17

require golang.org/x/mod v0.5.1

--- main.go ---
package main

import (
        ""golang.org/x/mod/semver""
)

func main() {
        if semver.IsValid(""1.0.0"") {
                println(""valid"")
        }
}
```

### What did you expect to see?

As described in `go1.18beta1 help build`, expected to see files from standard packages start with ""go""
>         -trimpath
>                 remove all file system paths from the resulting executable.
>                 Instead of absolute file system paths, the recorded file names
>                 will begin with either ""go"" (for the standard library),
>                 or a module path@version (when using modules),
>                 or a plain import path (when using GOPATH).

### What did you see instead?

Files from standard libraries without ""go"" (plain import path + file base name)
```
% strings out | grep map.go
runtime/mbitmap.go
runtime/map.go
```

Description for packages from dependency modules seems correct.

```
% strings out | grep semver.go
golang.org/x/mod@v0.5.1/semver/semver.go
```

Maybe need to mention behavior for main module files explicitly.
```
% strings out | grep main.go  
work/main.go
```",1,cmd go  update  trimpath documentation         please answer these questions before submitting your issue  thanks              what version of go are you using   go version            go version                  what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   users hakim library caches go build   goenv   users hakim library application support go env   goexe     goexperiment     goflags     gohostarch      gohostos  darwin   goinsecure     gomodcache   users hakim go pkg mod   gonoproxy     gonosumdb     goos  darwin   gopath   users hakim go   goprivate     goproxy     goroot   users hakim sdk       gosumdb  sum golang org   gotmpdir     gotooldir   users hakim sdk     pkg tool darwin     govcs     goversion        gccgo  gccgo          ar  ar   cc  clang   cxx  clang     cgo enabled      gomod   users hakim ww go mod   gowork     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic  arch         pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders bw   vvzk   t go    tmp go build  gno record gcc switches  fno common             what did you do     built the following program with   trimpath       go build  trimpath  o out                     go mod      module work    go        require golang org x mod              main go      package main    import             golang org x mod semver        func main              if semver isvalid                             println  valid                             what did you expect to see     as described in      help build   expected to see files from standard packages start with  go              trimpath                    remove all file system paths from the resulting executable                     instead of absolute file system paths  the recorded file names                    will begin with either  go   for the standard library                      or a module path version  when using modules                      or a plain import path  when using gopath          what did you see instead     files from standard libraries without  go   plain import path   file base name          strings out   grep map go  runtime mbitmap go  runtime map go         description for packages from dependency modules seems correct            strings out   grep semver go  golang org x mod       semver semver go         maybe need to mention behavior for main module files explicitly          strings out   grep main go    work main go     ,1
6644,3038103590.0,IssuesEvent,2015-08-06 20:37:58,golang/go,https://api.github.com/repos/golang/go,closed,"sync: docs say WaitGroup is a function, and that it panics",Documentation,"From https://tip.golang.org/doc/go1.5 --

> The WaitGroup function in package sync now diagnoses code that races a call to Add against a return from Wait. If it detects this condition, WaitGroup panics.

`WaitGroup` is a type, not a function.  In looking at the race-related code in the `WaitGroup.Add()` and `WaitGroup.Wait()` methods, I think this line in the docs is supposed to read more like:

> sync.WaitGroup's Add method now diagnoses code that races a call to Add against a return from Wait. If it detects this condition, Add panics.",1.0,"sync: docs say WaitGroup is a function, and that it panics - From https://tip.golang.org/doc/go1.5 --

> The WaitGroup function in package sync now diagnoses code that races a call to Add against a return from Wait. If it detects this condition, WaitGroup panics.

`WaitGroup` is a type, not a function.  In looking at the race-related code in the `WaitGroup.Add()` and `WaitGroup.Wait()` methods, I think this line in the docs is supposed to read more like:

> sync.WaitGroup's Add method now diagnoses code that races a call to Add against a return from Wait. If it detects this condition, Add panics.",1,sync  docs say waitgroup is a function  and that it panics   from           the waitgroup function in package sync now diagnoses code that races a call to add against a return from wait  if it detects this condition  waitgroup panics      waitgroup  is a type  not a function   in looking at the race related code in the  waitgroup add    and  waitgroup wait    methods  i think this line in the docs is supposed to read more like       sync waitgroup s add method now diagnoses code that races a call to add against a return from wait  if it detects this condition  add panics ,1
42619,6993127620.0,IssuesEvent,2017-12-15 10:05:40,golang/go,https://api.github.com/repos/golang/go,closed,x/perf/cmd/benchstat: documentation missing information about -alpha option,Documentation,"Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
go1.10beta1

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?
ppc64le Ubuntu

### What did you do?
Tried to use benchstat for comparing benchmark results. Thought something was wrong on ppc64le because the delta column was always ~ even though I could see significant differences in the results columns.

Tried to use benchstat -h and found -alpha which I assumed is that I needed:
```
 -alpha a
    	consider change significant if p < a (default 0.001)
```
From this it was not clear what p is, so I went here:

https://godoc.org/golang.org/x/perf/cmd/benchstat
but this documentation doesn't even mention alpha.

So after trial and error I found an alpha value that would give me what I want. ",1.0,"x/perf/cmd/benchstat: documentation missing information about -alpha option - Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
go1.10beta1

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?
ppc64le Ubuntu

### What did you do?
Tried to use benchstat for comparing benchmark results. Thought something was wrong on ppc64le because the delta column was always ~ even though I could see significant differences in the results columns.

Tried to use benchstat -h and found -alpha which I assumed is that I needed:
```
 -alpha a
    	consider change significant if p < a (default 0.001)
```
From this it was not clear what p is, so I went here:

https://godoc.org/golang.org/x/perf/cmd/benchstat
but this documentation doesn't even mention alpha.

So after trial and error I found an alpha value that would give me what I want. ",1,x perf cmd benchstat  documentation missing information about  alpha option   please answer these questions before submitting your issue  thanks           what version of go are you using   go version                does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env       ubuntu        what did you do   tried to use benchstat for comparing benchmark results  thought something was wrong on   because the delta column was always   even though i could see significant differences in the results columns     tried to use benchstat  h and found  alpha which i assumed is that i needed          alpha a      	consider change significant if p   a  default            from this it was not clear what p is  so i went here        but this documentation doesn t even mention alpha     so after trial and error i found an alpha value that would give me what i want  ,1
11035,3454434494.0,IssuesEvent,2015-12-17 15:54:52,golang/go,https://api.github.com/repos/golang/go,closed,net/http: document ListenAndServe does keep-alive stuff,Documentation,"Document that ListenAndServe is more than just Listen + Server.

See comments in #12731
",1.0,"net/http: document ListenAndServe does keep-alive stuff - Document that ListenAndServe is more than just Listen + Server.

See comments in #12731
",1,net http  document listenandserve does keep alive stuff   document that listenandserve is more than just listen   server     see comments in     ,1
169130,13125560958.0,IssuesEvent,2020-08-06 06:56:36,celo-org/celo-monorepo,https://api.github.com/repos/celo-org/celo-monorepo,closed,"[FLAKEY TEST] protocol-test -> protocol -> Contract: IntegerSortedLinkedListTest -> when there are multiple inserts, updates, and removals -> should maintain invariants when lesser and greater are incorrect",FLAKEY protocol protocol-test,"Discovered in PR https://github.com/celo-org/celo-monorepo/pull/4303

Attempt No. 1:

AssertionError: expected 0.145 to be at least 0.15000000000000002
    at /home/circleci/app/packages/protocol/test/governance/sortedlinkedlist.ts:639:40
    at step (/home/circleci/app/packages/protocol/test/governance/sortedlinkedlist.ts:33:23)
    at Object.next (/home/circleci/app/packages/protocol/test/governance/sortedlinkedlist.ts:14:53)
    at fulfilled (/home/circleci/app/packages/protocol/test/governance/sortedlinkedlist.ts:5:58)
    at process._tickCallback (internal/process/next_tick.js:68:7)

Attempt No. 2:

Test Passed!


",1.0,"[FLAKEY TEST] protocol-test -> protocol -> Contract: IntegerSortedLinkedListTest -> when there are multiple inserts, updates, and removals -> should maintain invariants when lesser and greater are incorrect - Discovered in PR https://github.com/celo-org/celo-monorepo/pull/4303

Attempt No. 1:

AssertionError: expected 0.145 to be at least 0.15000000000000002
    at /home/circleci/app/packages/protocol/test/governance/sortedlinkedlist.ts:639:40
    at step (/home/circleci/app/packages/protocol/test/governance/sortedlinkedlist.ts:33:23)
    at Object.next (/home/circleci/app/packages/protocol/test/governance/sortedlinkedlist.ts:14:53)
    at fulfilled (/home/circleci/app/packages/protocol/test/governance/sortedlinkedlist.ts:5:58)
    at process._tickCallback (internal/process/next_tick.js:68:7)

Attempt No. 2:

Test Passed!


",0,  protocol test    protocol    contract  integersortedlinkedlisttest    when there are multiple inserts  updates  and removals    should maintain invariants when lesser and greater are incorrect   discovered in pr    attempt no      assertionerror  expected     to be at least         at  home circleci app packages protocol test governance sortedlinkedlist ts         at step   home circleci app packages protocol test governance sortedlinkedlist ts          at object next   home circleci app packages protocol test governance sortedlinkedlist ts          at fulfilled   home circleci app packages protocol test governance sortedlinkedlist ts          at process  tickcallback  internal process next tick js       attempt no      test passed    ,0
96197,19913211180.0,IssuesEvent,2022-01-25 19:25:27,WordPress/openverse-api,https://api.github.com/repos/WordPress/openverse-api,opened,Move off of grequests,🟩 priority: low ✨ goal: improvement 💻 aspect: code 🐍 tech: python,"## Problem
<!-- Describe a problem solved by this feature; or delete the section entirely. -->
The API currently uses [the `grequests` library](https://github.com/spyoungtech/grequests) for handling some of the `head` requests it completes when returning results (specifically in [`validate_images.py`](https://github.com/WordPress/openverse-api/blob/main/api/catalog/api/utils/validate_images.py#L37)).

## Description
<!-- Describe the feature and how it solves the problem. -->
The README for the project says:

> Note: You should probably use requests-threads or requests-futures instead.

The project has also not had a release since 2020. We might want to consider using one of those proposed alternatives.

## Alternatives
<!-- Describe any alternative solutions or features you have considered. How is this feature better? -->
Leave as is and hope for the best!

## Additional context
<!-- Add any other context about the feature here; or delete the section entirely. -->

## Implementation
<!-- Replace the [ ] with [x] to check the box. -->
- [ ] 🙋 I would be interested in implementing this feature.
",1.0,"Move off of grequests - ## Problem
<!-- Describe a problem solved by this feature; or delete the section entirely. -->
The API currently uses [the `grequests` library](https://github.com/spyoungtech/grequests) for handling some of the `head` requests it completes when returning results (specifically in [`validate_images.py`](https://github.com/WordPress/openverse-api/blob/main/api/catalog/api/utils/validate_images.py#L37)).

## Description
<!-- Describe the feature and how it solves the problem. -->
The README for the project says:

> Note: You should probably use requests-threads or requests-futures instead.

The project has also not had a release since 2020. We might want to consider using one of those proposed alternatives.

## Alternatives
<!-- Describe any alternative solutions or features you have considered. How is this feature better? -->
Leave as is and hope for the best!

## Additional context
<!-- Add any other context about the feature here; or delete the section entirely. -->

## Implementation
<!-- Replace the [ ] with [x] to check the box. -->
- [ ] 🙋 I would be interested in implementing this feature.
",0,move off of grequests      problem     the api currently uses     for handling some of the  head  requests it completes when returning results  specifically in           description     the readme for the project says       note  you should probably use requests threads or requests futures instead     the project has also not had a release since    we might want to consider using one of those proposed alternatives        alternatives     leave as is and hope for the best        additional context          implementation         🙋 i would be interested in implementing this feature   ,0
22075,4771711930.0,IssuesEvent,2016-10-26 18:46:59,golang/go,https://api.github.com/repos/golang/go,opened,"net: no docs on ""0"" or empty name of transport service",Documentation,"#13610 and CL 17755 fixed the behavior without documentation. There is no documentation that describes what happens when the zero value of transport service in Dial, Listen, ListenPacket functions and Resolve{TCP,UDP,IP}Addr functions. I guess those two groups behave differently.",1.0,"net: no docs on ""0"" or empty name of transport service - #13610 and CL 17755 fixed the behavior without documentation. There is no documentation that describes what happens when the zero value of transport service in Dial, Listen, ListenPacket functions and Resolve{TCP,UDP,IP}Addr functions. I guess those two groups behave differently.",1,net  no docs on     or empty name of transport service      and cl   fixed the behavior without documentation  there is no documentation that describes what happens when the zero value of transport service in dial  listen  listenpacket functions and resolve tcp udp ip addr functions  i guess those two groups behave differently ,1
211839,16460094382.0,IssuesEvent,2021-05-21 17:35:40,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.17: document archive/zip changes for Go 1.17,Documentation NeedsInvestigation help wanted release-blocker,"As of filing this issue, the [Go 1.17 draft release notes](https://tip.golang.org/doc/go1.17) contained the following HTML:

<dl id=""archive/zip""><dt><a href=""/pkg/archive/zip/"">archive/zip</a></dt>
  <dd>
    <p><!-- CL 312310 -->
      TODO: <a href=""https://golang.org/cl/312310"">https://golang.org/cl/312310</a>: add File.OpenRaw, Writer.CreateRaw, Writer.Copy
    </p>
  </dd>
</dl>

---

This TODO needs to be resolved by July 1 so that we can have complete release notes for [Beta 1](https://golang.org/s/release#june-1--december-1-beta-1-issued).

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.17:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.17) and include ""For #44513. Fixes #46000."" in the body.",1.0,"doc/go1.17: document archive/zip changes for Go 1.17 - As of filing this issue, the [Go 1.17 draft release notes](https://tip.golang.org/doc/go1.17) contained the following HTML:

<dl id=""archive/zip""><dt><a href=""/pkg/archive/zip/"">archive/zip</a></dt>
  <dd>
    <p><!-- CL 312310 -->
      TODO: <a href=""https://golang.org/cl/312310"">https://golang.org/cl/312310</a>: add File.OpenRaw, Writer.CreateRaw, Writer.Copy
    </p>
  </dd>
</dl>

---

This TODO needs to be resolved by July 1 so that we can have complete release notes for [Beta 1](https://golang.org/s/release#june-1--december-1-beta-1-issued).

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.17:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.17) and include ""For #44513. Fixes #46000."" in the body.",1,doc      document archive zip changes for go       as of filing this issue  the     contained the following html        archive zip                       todo   a href    add file openraw  writer createraw  writer copy                          this todo needs to be resolved by july   so that we can have complete release notes for        a sequence of steps to resolve this issue may be        come up with a draft release note entry in this issue  then move the issue to needsfix state      send a cl with  doc           and include  for     fixes      in the body ,1
70345,9403660307.0,IssuesEvent,2019-04-09 02:25:58,golang/go,https://api.github.com/repos/golang/go,closed,spec: poorly documented slice definition syntax,Documentation WaitingForInfo,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.11.1 linux/amd64
</pre>
But also on Windows and in Go 1.12

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/felian/.cache/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/felian/go_code""
GOPROXY=""""
GORACE=""""
GOROOT=""/usr/local/go""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build955872785=/tmp/go-build -gno-record-gcc-switches""

</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

https://play.golang.org/p/clO1qELMYH2
<details><pre>package main
import ""fmt""
func main() { fmt.Println([]int{1, 2, 3, 7: 3, 6, 7}) }</pre></details>

Also works nicely with arrays, and with multiple `:`:
<pre>
fmt.Println([20]int{1, 2, 3, 7: 11, 12, 13: 10})
fmt.Println([30]int{1, 2, 3, 7: 11, 12, 13: 10, 18: 11, 25})
</pre>

### What did you expect to see?

This syntax should be well documented or invalid. 

I found one example of this after ""Examples of valid array, slice, and map literals:"" in [language specification](https://golang.org/ref/spec). But it seems not enough. 

### What did you see instead?

This syntax is valid and seems poorly documented.

Thanks for directions to @irwinnoteam2009",1.0,"spec: poorly documented slice definition syntax - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.11.1 linux/amd64
</pre>
But also on Windows and in Go 1.12

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/felian/.cache/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/felian/go_code""
GOPROXY=""""
GORACE=""""
GOROOT=""/usr/local/go""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build955872785=/tmp/go-build -gno-record-gcc-switches""

</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

https://play.golang.org/p/clO1qELMYH2
<details><pre>package main
import ""fmt""
func main() { fmt.Println([]int{1, 2, 3, 7: 3, 6, 7}) }</pre></details>

Also works nicely with arrays, and with multiple `:`:
<pre>
fmt.Println([20]int{1, 2, 3, 7: 11, 12, 13: 10})
fmt.Println([30]int{1, 2, 3, 7: 11, 12, 13: 10, 18: 11, 25})
</pre>

### What did you expect to see?

This syntax should be well documented or invalid. 

I found one example of this after ""Examples of valid array, slice, and map literals:"" in [language specification](https://golang.org/ref/spec). But it seems not enough. 

### What did you see instead?

This syntax is valid and seems poorly documented.

Thanks for directions to @irwinnoteam2009",1,spec  poorly documented slice definition syntax            what version of go are you using   go version            go version  go version       linux       but also on windows and in go            does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env          go env  output       go env  goarch      gobin     gocache   home felian  cache go build   goexe     goflags     gohostarch      gohostos  linux   goos  linux   gopath   home felian go code   goproxy     gorace     goroot   usr local go   gotmpdir     gotooldir   usr local go pkg tool linux     gccgo  gccgo   cc  gcc   cxx  g     cgo enabled      gomod     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches               what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best               package main  import  fmt   func main     fmt println  int                              also works nicely with arrays  and with multiple          fmt println  int                           fmt println  int                                             what did you expect to see     this syntax should be well documented or invalid      i found one example of this after  examples of valid array  slice  and map literals   in     but it seems not enough          what did you see instead     this syntax is valid and seems poorly documented     thanks for directions to   ,1
56102,8051004225.0,IssuesEvent,2018-08-01 14:56:33,golang/go,https://api.github.com/repos/golang/go,opened,doc/install: define minimum supported VCS versions,Documentation,"`cmd/go` shells out to version control binaries to implement `go get`.

[doc/install](https://tip.golang.org/doc/install) currently declares minimum supported OS versions for FreeBSD, macOS, and Windows, but only a minimum kernel version for Linux. Those requirements do not imply any particular version of the supported version control binaries, and those versions do matter in practice: in particular, `git` accrued a large number of flags in between 2.7 and 2.18 (https://github.com/golang/go/issues/26653).

We should be explicit about which versions are supported for use with the `go` command.

(CC: @rsc @ianlancetaylor @bradfitz @myitcv @rogpeppe @trashhalo)",1.0,"doc/install: define minimum supported VCS versions - `cmd/go` shells out to version control binaries to implement `go get`.

[doc/install](https://tip.golang.org/doc/install) currently declares minimum supported OS versions for FreeBSD, macOS, and Windows, but only a minimum kernel version for Linux. Those requirements do not imply any particular version of the supported version control binaries, and those versions do matter in practice: in particular, `git` accrued a large number of flags in between 2.7 and 2.18 (https://github.com/golang/go/issues/26653).

We should be explicit about which versions are supported for use with the `go` command.

(CC: @rsc @ianlancetaylor @bradfitz @myitcv @rogpeppe @trashhalo)",1,doc install  define minimum supported vcs versions    cmd go  shells out to version control binaries to implement  go get          currently declares minimum supported os versions for freebsd  macos  and windows  but only a minimum kernel version for linux  those requirements do not imply any particular version of the supported version control binaries  and those versions do matter in practice  in particular   git  accrued a large number of flags in between     and           we should be explicit about which versions are supported for use with the  go  command      cc   rsc  ianlancetaylor  bradfitz  myitcv  rogpeppe  trashhalo ,1
335771,30084959084.0,IssuesEvent,2023-06-29 07:56:32,istio/istio,https://api.github.com/repos/istio/istio,closed,istio telemetry envoy filter doesn't work ,area/test and release area/extensions and telemetry area/user experience,"### Is this the right place to submit this?

- [X] This is not a security vulnerability or a crashing bug
- [X] This is not a question about how to use Istio

### Bug Description

istio telemetry envoy filter doesn't work  when istio config configSources
 meshConfig:
    accessLogFile: ""/dev/stdout""
    accessLogEncoding: JSON
    enablePrometheusMerge: true
    configSources:
      - address: ""xds://xx.xx.com""

### Version

```Text
client version: 1.14.5
control plane version: 1.14.5
data plane version: 1.14.5 (3 proxies)

Client Version: v1.26.3
Kustomize Version: v4.5.7
Server Version: v1.20.6
```


### Additional Information

not jus version 1.14.5 , all version has the problem
not just telemetry envoy filter  
all envoy filter  will not work when istio configSources:

### Affected product area

- [ ] Ambient
- [ ] Docs
- [ ] Installation
- [ ] Networking
- [ ] Performance and Scalability
- [X] Extensions and Telemetry
- [ ] Security
- [X] Test and Release
- [X] User Experience
- [ ] Developer Infrastructure
- [ ] Upgrade
- [ ] Multi Cluster
- [ ] Virtual Machine
- [ ] Control Plane Revisions",1.0,"istio telemetry envoy filter doesn't work  - ### Is this the right place to submit this?

- [X] This is not a security vulnerability or a crashing bug
- [X] This is not a question about how to use Istio

### Bug Description

istio telemetry envoy filter doesn't work  when istio config configSources
 meshConfig:
    accessLogFile: ""/dev/stdout""
    accessLogEncoding: JSON
    enablePrometheusMerge: true
    configSources:
      - address: ""xds://xx.xx.com""

### Version

```Text
client version: 1.14.5
control plane version: 1.14.5
data plane version: 1.14.5 (3 proxies)

Client Version: v1.26.3
Kustomize Version: v4.5.7
Server Version: v1.20.6
```


### Additional Information

not jus version 1.14.5 , all version has the problem
not just telemetry envoy filter  
all envoy filter  will not work when istio configSources:

### Affected product area

- [ ] Ambient
- [ ] Docs
- [ ] Installation
- [ ] Networking
- [ ] Performance and Scalability
- [X] Extensions and Telemetry
- [ ] Security
- [X] Test and Release
- [X] User Experience
- [ ] Developer Infrastructure
- [ ] Upgrade
- [ ] Multi Cluster
- [ ] Virtual Machine
- [ ] Control Plane Revisions",0,istio telemetry envoy filter doesn t work        is this the right place to submit this       this is not a security vulnerability or a crashing bug     this is not a question about how to use istio      bug description  istio telemetry envoy filter doesn t work  when istio config configsources   meshconfig       accesslogfile    dev stdout       accesslogencoding  json      enableprometheusmerge  true      configsources           address   xds   xx xx com       version     text client version         control plane version         data plane version           proxies     client version         kustomize version         server version                  additional information  not jus version         all version has the problem  not just telemetry envoy filter    all envoy filter  will not work when istio configsources       affected product area      ambient     docs     installation     networking     performance and scalability     extensions and telemetry     security     test and release     user experience     developer infrastructure     upgrade     multi cluster     virtual machine     control plane revisions,0
70605,18239210771.0,IssuesEvent,2021-10-01 10:46:58,appsmithorg/appsmith,https://api.github.com/repos/appsmithorg/appsmith,closed,TypeError: Illegal invocation,Bug Pages Low Production UI Building Pod Needs Triaging UI Builders Pod,"Sentry Issue: [APPSMITH-Q9](https://sentry.io/organizations/appsmith/issues/2366661491/?referrer=github_integration)

```
TypeError: Illegal invocation
  at Object.sendBeacon (/frame-modern.85a20f96.js:1:38304)
  at Object.createMetricsWithBeacon (/frame-modern.85a20f96.js:1:23752)
  at I (/frame-modern.85a20f96.js:1:5464)
  at None (/frame-modern.85a20f96.js:1:7287)
  at r (../../src/helpers.ts:87:17)
```",2.0,"TypeError: Illegal invocation - Sentry Issue: [APPSMITH-Q9](https://sentry.io/organizations/appsmith/issues/2366661491/?referrer=github_integration)

```
TypeError: Illegal invocation
  at Object.sendBeacon (/frame-modern.85a20f96.js:1:38304)
  at Object.createMetricsWithBeacon (/frame-modern.85a20f96.js:1:23752)
  at I (/frame-modern.85a20f96.js:1:5464)
  at None (/frame-modern.85a20f96.js:1:7287)
  at r (../../src/helpers.ts:87:17)
```",0,typeerror  illegal invocation   sentry issue           typeerror  illegal invocation   at object sendbeacon   frame modern   js        at object createmetricswithbeacon   frame modern   js        at i   frame modern   js        at none   frame modern   js        at r        src helpers ts         ,0
208349,16111351968.0,IssuesEvent,2021-04-27 21:45:00,golang/go,https://api.github.com/repos/golang/go,closed,testing: document that TestMain always runs before any benchmarks,Documentation NeedsFix help wanted,"The docs for `TestMain` say:

```
It is sometimes necessary for a test program to do extra setup
or teardown before or after testing.
```

https://golang.org/pkg/testing/#hdr-Main

But what if one needs to do extra setup before benchmarking? It appears that `TestMain` would also always run before benchmarks, but neither `TestMain` doc nor `M.Run` doc say anything about benchmarks.",1.0,"testing: document that TestMain always runs before any benchmarks - The docs for `TestMain` say:

```
It is sometimes necessary for a test program to do extra setup
or teardown before or after testing.
```

https://golang.org/pkg/testing/#hdr-Main

But what if one needs to do extra setup before benchmarking? It appears that `TestMain` would also always run before benchmarks, but neither `TestMain` doc nor `M.Run` doc say anything about benchmarks.",1,testing  document that testmain always runs before any benchmarks   the docs for  testmain  say          it is sometimes necessary for a test program to do extra setup  or teardown before or after testing               but what if one needs to do extra setup before benchmarking  it appears that  testmain  would also always run before benchmarks  but neither  testmain  doc nor  m run  doc say anything about benchmarks ,1
7475,2855042749.0,IssuesEvent,2015-06-02 06:51:02,Menon24/B6T3WX3I4U4VCWIYBNAYQJLH,https://api.github.com/repos/Menon24/B6T3WX3I4U4VCWIYBNAYQJLH,closed,fXhiaTctJfUu8/0vhwW3oWP7wfz6kHt1IhdutujmakP8RZWqOXwP0fNtyIR9di3xr8WV3Sn/eAVcsjZBVmXCWpWd5XnIiBnrbtCZzYQj+gwFuZVbjjjjXcxHNyo/Et5PT667AzvesxLT6dVRsa3tTwwBxPYQWqw9R0JNp8qkbpQ=,design,Dx5C7PaG/PnN19Y5iML3Y2rtThcpFY0jes2qnRDYmwc9jietgeECJd0guP0m2KsL5Js6pcqDTCC4Wyt3h2jjfXe5A6tBxMykgDpghfrtgi0KmAtWWg7nljekMv9+KnGXF43abjFtacS/NhlnzvlPIuk41CK4ZHoq9ABwc4+v813ed69AvvI07kAlVnJ0gsOefiS9wF7HuvJilDsqMJvlXg6spLGWS9bcArTp+Yu+i0/PBGECEs8TxRhUfEDdvKdE0qvf1N60DL4lCQjeHSo5mKw6PjI7WXoj2qpq02qK0w4Ichaouy/WL7mYOkES2FMC4kxqRwdKpRZUG9FuNL0GDYbwzxtqmIpqHYNm+4XOhJkItBZW1mljzJN4RmXAuEykcV6kNQvEOG2RvMmS9EJIrUXwrmylEWHqAzGWEui9rZUPjo50zvvYklHDBK6lsIa4x8a7Ml37SLszyGuvEYR3z28N2NC8TtwFhqyJVVz3D3gT5AkYJ5s0Ru83LN8sZa9mVUTybzZecceW9tBnmZhqcxS7JYAnh67SHl+sJaoqTIyJceQwWX13A05Xm3mD9I/m19E3Ij+PcZu7oXnDFD2LQ2bihoXrDT+K+E5GC5Z11dJa6FcSDqFf0uLumXmpkhRF9mDpCXBWAnwWWlWgZLyLkImNRoW/OlKZF1KJqN6LmlTxKwXE+sbKzMAXxfU/XcV9DCFO2mWSyyBPuIw6Oey+9ApnJVaDBQ/dVG1l+gTeP5bqBatSbKC/81PtjPVB5bt1kSs+aD6+jcaxgheQmfU7GK8wr+boMCbvCbysiuwKK9dg6cXLvNGxWIKd1FDt/v41hG9ZgJT2b+mmZxevq18VwSFgWTfYoxTNR/Q7efaATm0VfexSu/LUIbhpfYMUCydN3OGCb/dGimpNv4lRSH9hOna6VCZjqDlM+HTuAZCZHgTQFPRjAzV8ewMeta8SHV37Kbyh8H/UR96y2V4a+cl9MU4KImzDrwQbOus4BUlJMRWDui5zUfHGZlC7krvUrwd+,1.0,fXhiaTctJfUu8/0vhwW3oWP7wfz6kHt1IhdutujmakP8RZWqOXwP0fNtyIR9di3xr8WV3Sn/eAVcsjZBVmXCWpWd5XnIiBnrbtCZzYQj+gwFuZVbjjjjXcxHNyo/Et5PT667AzvesxLT6dVRsa3tTwwBxPYQWqw9R0JNp8qkbpQ= - Dx5C7PaG/PnN19Y5iML3Y2rtThcpFY0jes2qnRDYmwc9jietgeECJd0guP0m2KsL5Js6pcqDTCC4Wyt3h2jjfXe5A6tBxMykgDpghfrtgi0KmAtWWg7nljekMv9+KnGXF43abjFtacS/NhlnzvlPIuk41CK4ZHoq9ABwc4+v813ed69AvvI07kAlVnJ0gsOefiS9wF7HuvJilDsqMJvlXg6spLGWS9bcArTp+Yu+i0/PBGECEs8TxRhUfEDdvKdE0qvf1N60DL4lCQjeHSo5mKw6PjI7WXoj2qpq02qK0w4Ichaouy/WL7mYOkES2FMC4kxqRwdKpRZUG9FuNL0GDYbwzxtqmIpqHYNm+4XOhJkItBZW1mljzJN4RmXAuEykcV6kNQvEOG2RvMmS9EJIrUXwrmylEWHqAzGWEui9rZUPjo50zvvYklHDBK6lsIa4x8a7Ml37SLszyGuvEYR3z28N2NC8TtwFhqyJVVz3D3gT5AkYJ5s0Ru83LN8sZa9mVUTybzZecceW9tBnmZhqcxS7JYAnh67SHl+sJaoqTIyJceQwWX13A05Xm3mD9I/m19E3Ij+PcZu7oXnDFD2LQ2bihoXrDT+K+E5GC5Z11dJa6FcSDqFf0uLumXmpkhRF9mDpCXBWAnwWWlWgZLyLkImNRoW/OlKZF1KJqN6LmlTxKwXE+sbKzMAXxfU/XcV9DCFO2mWSyyBPuIw6Oey+9ApnJVaDBQ/dVG1l+gTeP5bqBatSbKC/81PtjPVB5bt1kSs+aD6+jcaxgheQmfU7GK8wr+boMCbvCbysiuwKK9dg6cXLvNGxWIKd1FDt/v41hG9ZgJT2b+mmZxevq18VwSFgWTfYoxTNR/Q7efaATm0VfexSu/LUIbhpfYMUCydN3OGCb/dGimpNv4lRSH9hOna6VCZjqDlM+HTuAZCZHgTQFPRjAzV8ewMeta8SHV37Kbyh8H/UR96y2V4a+cl9MU4KImzDrwQbOus4BUlJMRWDui5zUfHGZlC7krvUrwd+,0,      gwfuzvbjjjjxcxhnyo                yu               k     sbkzmaxxfu                                 ,0
145712,22763579120.0,IssuesEvent,2022-07-08 00:25:11,woowa-techcamp-2022/web-baemin-leejooam,https://api.github.com/repos/woowa-techcamp-2022/web-baemin-leejooam,closed,약관동의 페이지 리펙토링,frontend design refactoring,"# 🔨 요구 사항
약관 동의 페이지를 리펙토링한다.

# 📑 완료 조건
- [x] 약관 동의 페이지 클래스명, 마크업 정리
- [ ] 약관 동의 페이지 비즈니스 로직 정리
- [ ] 약관 동의 페이지 로직 변수, 함수명 정리

# 🚧 주의 사항
",1.0,"약관동의 페이지 리펙토링 - # 🔨 요구 사항
약관 동의 페이지를 리펙토링한다.

# 📑 완료 조건
- [x] 약관 동의 페이지 클래스명, 마크업 정리
- [ ] 약관 동의 페이지 비즈니스 로직 정리
- [ ] 약관 동의 페이지 로직 변수, 함수명 정리

# 🚧 주의 사항
",0,약관동의 페이지 리펙토링     🔨 요구 사항  약관 동의 페이지를 리펙토링한다       📑 완료 조건      약관 동의 페이지 클래스명  마크업 정리      약관 동의 페이지 비즈니스 로직 정리      약관 동의 페이지 로직 변수  함수명 정리      🚧 주의 사항  ,0
490804,14140417929.0,IssuesEvent,2020-11-10 11:10:26,carbon-design-system/carbon-addons-iot-react,https://api.github.com/repos/carbon-design-system/carbon-addons-iot-react,opened,[HotspotTextStyleTab] New subcomponent for the HotSpotEditorModal text style tab,status: needs priority :inbox_tray: status: needs triage :mag: type: contribution :gift: type: discussion :speech_balloon: type: enhancement :bulb:,"Part of issue #1753

### What package is this for?

- [x] React
- [ ] Angular

### Summary
A sub component needed for #1753 to configure the label texts

**Additional context** 
![image](https://user-images.githubusercontent.com/5167091/98666563-7ce88800-234d-11eb-80d7-5f967eb48d5b.png)


_Carbon add-ons for Watson IoT is a collaborative system. We encourage teams to
build components and submit them for integration._
",1.0,"[HotspotTextStyleTab] New subcomponent for the HotSpotEditorModal text style tab - Part of issue #1753

### What package is this for?

- [x] React
- [ ] Angular

### Summary
A sub component needed for #1753 to configure the label texts

**Additional context** 
![image](https://user-images.githubusercontent.com/5167091/98666563-7ce88800-234d-11eb-80d7-5f967eb48d5b.png)


_Carbon add-ons for Watson IoT is a collaborative system. We encourage teams to
build components and submit them for integration._
",0,  new subcomponent for the hotspoteditormodal text style tab   part of issue           what package is this for         react      angular        summary  a sub component needed for    to configure the label texts      additional context                carbon add ons for watson iot is a collaborative system  we encourage teams to  build components and submit them for integration    ,0
242887,20270769733.0,IssuesEvent,2022-02-15 16:00:04,kubernetes/test-infra,https://api.github.com/repos/kubernetes/test-infra,closed,prow.k8s.io: show skip reason,area/prow sig/testing kind/feature area/prow/deck area/prow/spyglass,"**What would you like to be added**:

When an e2e test gets skipped with `e2eskipper.Skipf`, the reason passed to that function is visible in the JUnit file.  It would be nice to show that on prow.k8s.io.

**Why is this needed**:

It's not always obvious why certain tests didn't run in a job.
",1.0,"prow.k8s.io: show skip reason - **What would you like to be added**:

When an e2e test gets skipped with `e2eskipper.Skipf`, the reason passed to that function is visible in the JUnit file.  It would be nice to show that on prow.k8s.io.

**Why is this needed**:

It's not always obvious why certain tests didn't run in a job.
",0,prow   io  show skip reason     what would you like to be added       when an   test gets skipped with    skipf   the reason passed to that function is visible in the junit file   it would be nice to show that on prow   io       why is this needed       it s not always obvious why certain tests didn t run in a job   ,0
357810,10618343640.0,IssuesEvent,2019-10-13 03:32:56,carbon-design-system/ibm-dotcom-library,https://api.github.com/repos/carbon-design-system/ibm-dotcom-library,opened,Develop the Mega menu component,dev dotcom migrate package: react priority: medium,"_hahnrob created the following on Jun 25:_  

 As a developer, I need to create the Mega menu component within the Dotcom components package so that adopters can utilize this component in their application

#### Additional information
 - This issue is dependent on the design and the [package architecture #860](https://zenhub.ibm.com/app/workspaces/digital-design-system-5b3a815a8bf6a932efa6fd03/issues/webstandards/digital-design/860)
- The priority is documented in the component [Airtable](https://airtable.com/tblYos5iDYwTP6MCK/viw85GYbUVISjrXj9?blocks=hide)
 - Assigned priority:  #9

#### Acceptance criteria
 - [ ] Component has been tested using Netlify
 - [ ] The component development follows a modular component pattern
 - [ ] The component should be accessible via ES6 import
 - [ ] The component should be visible within the living documentation of the Dotcom components
 - [ ] Presented and approved Product Owner

 

_Original issue: https://github.ibm.com/webstandards/digital-design/issues/1122_",1.0,"Develop the Mega menu component - _hahnrob created the following on Jun 25:_  

 As a developer, I need to create the Mega menu component within the Dotcom components package so that adopters can utilize this component in their application

#### Additional information
 - This issue is dependent on the design and the [package architecture #860](https://zenhub.ibm.com/app/workspaces/digital-design-system-5b3a815a8bf6a932efa6fd03/issues/webstandards/digital-design/860)
- The priority is documented in the component [Airtable](https://airtable.com/tblYos5iDYwTP6MCK/viw85GYbUVISjrXj9?blocks=hide)
 - Assigned priority:  #9

#### Acceptance criteria
 - [ ] Component has been tested using Netlify
 - [ ] The component development follows a modular component pattern
 - [ ] The component should be accessible via ES6 import
 - [ ] The component should be visible within the living documentation of the Dotcom components
 - [ ] Presented and approved Product Owner

 

_Original issue: https://github.ibm.com/webstandards/digital-design/issues/1122_",0,develop the mega menu component    hahnrob created the following on jun         as a developer  i need to create the mega menu component within the dotcom components package so that adopters can utilize this component in their application       additional information    this issue is dependent on the design and the       the priority is documented in the component        assigned priority            acceptance criteria      component has been tested using netlify      the component development follows a modular component pattern      the component should be accessible via   import      the component should be visible within the living documentation of the dotcom components      presented and approved product owner      original issue   ,0
9148,3257535577.0,IssuesEvent,2015-10-20 18:17:11,golang/go,https://api.github.com/repos/golang/go,closed,spec: Do exact floating-point constants differentiate between -0.0 and 0.0?,Documentation,"The spec does not seem to be clear.

The test test/fixedbugs/bug434.go says that -0.0 and 0.0 are the same.

Clarify.",1.0,"spec: Do exact floating-point constants differentiate between -0.0 and 0.0? - The spec does not seem to be clear.

The test test/fixedbugs/bug434.go says that -0.0 and 0.0 are the same.

Clarify.",1,spec  do exact floating point constants differentiate between      and        the spec does not seem to be clear     the test test fixedbugs   go says that      and     are the same     clarify ,1
138793,31029111641.0,IssuesEvent,2023-08-10 11:12:57,DigitalExtinction/Game,https://api.github.com/repos/DigitalExtinction/Game,opened,State transition race-conditions,S-Needs-Investigation C-Code-Quality,`NextState` is set from many places. There is a possibility that two different next-states are set withing the same frame. Make this more robust.,1.0,State transition race-conditions - `NextState` is set from many places. There is a possibility that two different next-states are set withing the same frame. Make this more robust.,0,state transition race conditions    nextstate  is set from many places  there is a possibility that two different next states are set withing the same frame  make this more robust ,0
1471,6026161116.0,IssuesEvent,2017-06-08 10:31:11,Gulix/geckos,https://api.github.com/repos/Gulix/geckos,closed,Lodash framework - Replace hand-made functions,architecture,"Underscore framework needs to be added to the project.
Then, various methods need to be replaced by Underscore methods to enhance maintainability
",1.0,"Lodash framework - Replace hand-made functions - Underscore framework needs to be added to the project.
Then, various methods need to be replaced by Underscore methods to enhance maintainability
",0,lodash framework   replace hand made functions   underscore framework needs to be added to the project  then  various methods need to be replaced by underscore methods to enhance maintainability ,0
98952,11101837509.0,IssuesEvent,2019-12-16 22:19:09,golang/go,https://api.github.com/repos/golang/go,opened,cmd/go: document automatic use of -mod=readonly and less-aggressive go.mod updates for Go 1.14,Documentation NeedsFix modules release-blocker,Realized that I'm missing some release notes for `-mod=readonly` and `go.mod` file maintenance in general for Go 1.14. This is a note-to-self to remember to add them soon. (I'll add issue references in the CL.),1.0,cmd/go: document automatic use of -mod=readonly and less-aggressive go.mod updates for Go 1.14 - Realized that I'm missing some release notes for `-mod=readonly` and `go.mod` file maintenance in general for Go 1.14. This is a note-to-self to remember to add them soon. (I'll add issue references in the CL.),1,cmd go  document automatic use of  mod readonly and less aggressive go mod updates for go       realized that i m missing some release notes for   mod readonly  and  go mod  file maintenance in general for go      this is a note to self to remember to add them soon   i ll add issue references in the cl  ,1
227444,18063418774.0,IssuesEvent,2021-09-20 16:14:03,dotnet/machinelearning-modelbuilder,https://api.github.com/repos/dotnet/machinelearning-modelbuilder,closed,Remove header row from Data Preview summary count,Priority:2 Test Team,"**System Information (please complete the following information):**
- Windows OS: Windows-10-Enterprise-21H1
- ML.Net Model Builder (Preview): 16.6.2.2135501 (Main Branch)
- Microsoft Visual Studio Enterprise 2019: 16.10.2
- .Net: 5.0.301

**Describe the bug**
- On which step of the process did you run into an issue: Data Page
- Clear description of the problem: I guess that the 10 here is meant to express the number of preview rows that do not include the header row, but the 200,001 rows is including header row. So the 10 of ""10/200,001 rows"" will be understood as including the number of header row, this is confusing.

**Test matrix:**
https://testpass.blob.core.windows.net/test-pass-data/taxi-fare.csv

**To Reproduce**
Steps to reproduce the behavior:
1. Select Create a new project from the Visual Studio 2019 start window.
2. Choose the C# Console App (.NET Core) project template with .Net 5.0;
3. Add model builder by right click on the project;
4. Navigate to Data page, input the data source;
5. It is found that the number 10 of rows in the preview is ambiguous. 

**Expected behavior**
Show the correct preview number of rows seen by the naked eye, or the number 10 may need to be explained (for example, the header row is not included).

**Screenshots**
If applicable, add screenshots to help explain your problem.
![image](https://user-images.githubusercontent.com/81727020/124887757-0ac56180-e008-11eb-8bb5-f5fded6f2856.png)
![image](https://user-images.githubusercontent.com/81727020/124888360-9ccd6a00-e008-11eb-89f1-cb4e28172a69.png)


**Additional context**
Add any other context about the problem here.
",1.0,"Remove header row from Data Preview summary count - **System Information (please complete the following information):**
- Windows OS: Windows-10-Enterprise-21H1
- ML.Net Model Builder (Preview): 16.6.2.2135501 (Main Branch)
- Microsoft Visual Studio Enterprise 2019: 16.10.2
- .Net: 5.0.301

**Describe the bug**
- On which step of the process did you run into an issue: Data Page
- Clear description of the problem: I guess that the 10 here is meant to express the number of preview rows that do not include the header row, but the 200,001 rows is including header row. So the 10 of ""10/200,001 rows"" will be understood as including the number of header row, this is confusing.

**Test matrix:**
https://testpass.blob.core.windows.net/test-pass-data/taxi-fare.csv

**To Reproduce**
Steps to reproduce the behavior:
1. Select Create a new project from the Visual Studio 2019 start window.
2. Choose the C# Console App (.NET Core) project template with .Net 5.0;
3. Add model builder by right click on the project;
4. Navigate to Data page, input the data source;
5. It is found that the number 10 of rows in the preview is ambiguous. 

**Expected behavior**
Show the correct preview number of rows seen by the naked eye, or the number 10 may need to be explained (for example, the header row is not included).

**Screenshots**
If applicable, add screenshots to help explain your problem.
![image](https://user-images.githubusercontent.com/81727020/124887757-0ac56180-e008-11eb-8bb5-f5fded6f2856.png)
![image](https://user-images.githubusercontent.com/81727020/124888360-9ccd6a00-e008-11eb-89f1-cb4e28172a69.png)


**Additional context**
Add any other context about the problem here.
",0,remove header row from data preview summary count     system information  please complete the following information        windows os  windows   enterprise      ml net model builder  preview            main branch     microsoft visual studio enterprise              net             describe the bug      on which step of the process did you run into an issue  data page    clear description of the problem  i guess that the   here is meant to express the number of preview rows that do not include the header row  but the     rows is including header row  so the   of        rows  will be understood as including the number of header row  this is confusing       test matrix            to reproduce    steps to reproduce the behavior      select create a new project from the visual studio   start window      choose the c  console app   net core  project template with  net          add model builder by right click on the project      navigate to data page  input the data source      it is found that the number   of rows in the preview is ambiguous        expected behavior    show the correct preview number of rows seen by the naked eye  or the number   may need to be explained  for example  the header row is not included        screenshots    if applicable  add screenshots to help explain your problem                     additional context    add any other context about the problem here   ,0
10095,2618935638.0,IssuesEvent,2015-03-03 00:01:57,chrsmith/open-ig,https://api.github.com/repos/chrsmith/open-ig,closed,lakosság csökkenés,auto-migrated Priority-Medium Type-Defect,"```
Game version:0.95.151

Amikor megtámadnak, és még űrharc van, és veszít az ellenség, csökken a 
bolygó lakossága, még bunker esetén is. Ez a régi játékban nem így 
volt... főleg bolygópajzs esetén értelmetlen... Továbbá ha ilyen 
helyzetben a Dargslanok veszítenek, sok idő amíg új flottát állítanak 
fel, pedig a régi játékban azonnal teljes új űrhajós flottát 
állítottak fel... Ez látszik ez előbb elmentett játékon is amit 
csatoltam...
```

Original issue reported on code.google.com by `laci8...@gmail.com` on 1 Oct 2013 at 2:08
* Merged into: #817",1.0,"lakosság csökkenés - ```
Game version:0.95.151

Amikor megtámadnak, és még űrharc van, és veszít az ellenség, csökken a 
bolygó lakossága, még bunker esetén is. Ez a régi játékban nem így 
volt... főleg bolygópajzs esetén értelmetlen... Továbbá ha ilyen 
helyzetben a Dargslanok veszítenek, sok idő amíg új flottát állítanak 
fel, pedig a régi játékban azonnal teljes új űrhajós flottát 
állítottak fel... Ez látszik ez előbb elmentett játékon is amit 
csatoltam...
```

Original issue reported on code.google.com by `laci8...@gmail.com` on 1 Oct 2013 at 2:08
* Merged into: #817",0,lakosság csökkenés       game version        amikor megtámadnak  és még űrharc van  és veszít az ellenség  csökken a  bolygó lakossága  még bunker esetén is  ez a régi játékban nem így  volt    főleg bolygópajzs esetén értelmetlen    továbbá ha ilyen  helyzetben a dargslanok veszítenek  sok idő amíg új flottát állítanak  fel  pedig a régi játékban azonnal teljes új űrhajós flottát  állítottak fel    ez látszik ez előbb elmentett játékon is amit  csatoltam         original issue reported on code google com by       gmail com  on   oct   at       merged into    ,0
784458,27571869192.0,IssuesEvent,2023-03-08 09:55:50,opensrp/opensrp-client-eusm,https://api.github.com/repos/opensrp/opensrp-client-eusm,opened,Addition of Unicef to the Valid List of Donors,Medium Priority,EUSM has requested for the addition of the name `Unicef` to the valid list of donors. This list is validated by the OpenSRP Web at the point of uploading the csv files with new inventories. This will facilitate addition of commodities donated by Unicef. This is a server side validation.,1.0,Addition of Unicef to the Valid List of Donors - EUSM has requested for the addition of the name `Unicef` to the valid list of donors. This list is validated by the OpenSRP Web at the point of uploading the csv files with new inventories. This will facilitate addition of commodities donated by Unicef. This is a server side validation.,0,addition of unicef to the valid list of donors   eusm has requested for the addition of the name  unicef  to the valid list of donors  this list is validated by the opensrp web at the point of uploading the csv files with new inventories  this will facilitate addition of commodities donated by unicef  this is a server side validation ,0
90336,26050761349.0,IssuesEvent,2022-12-22 18:24:31,chaotic-aur/packages,https://api.github.com/repos/chaotic-aur/packages,closed,[Outdated] mesa-tkg-git and lib32-mesa-tkg-git,waiting:issuer-feedback request:rebuild-pkg,"### If available, link to the latest build

https://builds.garudalinux.org/repos/chaotic-aur/logs/mesa-tkg-git.log

### Package name

mesa-tkg-git and lib32-mesa-tkg-git

### Latest build

mesa-tkg-git-23.0.0_devel.164253.e4e4ba23047-1-x86_64.pkg.tar.zst

### Latest version available

Latest from git

### Have you tested if the package builds in a clean chroot?

- [X] Yes

### More information

Mesa-tkg is too old, and is failing do build, the least successful one was day 14",1.0,"[Outdated] mesa-tkg-git and lib32-mesa-tkg-git - ### If available, link to the latest build

https://builds.garudalinux.org/repos/chaotic-aur/logs/mesa-tkg-git.log

### Package name

mesa-tkg-git and lib32-mesa-tkg-git

### Latest build

mesa-tkg-git-23.0.0_devel.164253.e4e4ba23047-1-x86_64.pkg.tar.zst

### Latest version available

Latest from git

### Have you tested if the package builds in a clean chroot?

- [X] Yes

### More information

Mesa-tkg is too old, and is failing do build, the least successful one was day 14",0,  mesa tkg git and   mesa tkg git       if available  link to the latest build         package name  mesa tkg git and   mesa tkg git      latest build  mesa tkg git       devel           pkg tar zst      latest version available  latest from git      have you tested if the package builds in a clean chroot       yes      more information  mesa tkg is too old  and is failing do build  the least successful one was day  ,0
56922,7017047641.0,IssuesEvent,2017-12-21 07:55:06,EnergyWater/EMSA,https://api.github.com/repos/EnergyWater/EMSA,reopened, Efficiency Benchmarking Scenario vs Scenario,Design or grammar issue,"@david-ITCL, @AaronITCL How should we display all the values of the equipment and processes of the two selected scenarios at this page?",1.0," Efficiency Benchmarking Scenario vs Scenario - @david-ITCL, @AaronITCL How should we display all the values of the equipment and processes of the two selected scenarios at this page?",0, efficiency benchmarking scenario vs scenario    david itcl   aaronitcl how should we display all the values of the equipment and processes of the two selected scenarios at this page ,0
42905,9332808781.0,IssuesEvent,2019-03-28 13:08:10,theia-ide/theia,https://api.github.com/repos/theia-ide/theia,opened,[multi-root] unable to properly open `*.code-workspace` files,bug vscode workspace,"#### Description
Theia becomes unresponsive when attempting to open `*.code-workspace` files 
(vscode workspace files). This is likely due to the way we resolve the paths. Hovering over the explorer items shows the following for example: `/home/vince/Desktop//home/vin/workspace/ls-interact/` (notice the incorrect **path** and **double //**).

#### Reproduction Steps
1. ensure the multi-root preference is enabled `workspace.supportMultiRootWorkspace`.
2. open a `code-workspace` file in Theia.
3. notice that the explorer displays the roots but they are empty (won't expand).
4. hover over a root item and notice the incorrect path.

**OS and Theia version:**
Ubuntu 16.04 and Theia 5a39e78e99fa17b987634bc7216618ae66b65083",1.0,"[multi-root] unable to properly open `*.code-workspace` files - #### Description
Theia becomes unresponsive when attempting to open `*.code-workspace` files 
(vscode workspace files). This is likely due to the way we resolve the paths. Hovering over the explorer items shows the following for example: `/home/vince/Desktop//home/vin/workspace/ls-interact/` (notice the incorrect **path** and **double //**).

#### Reproduction Steps
1. ensure the multi-root preference is enabled `workspace.supportMultiRootWorkspace`.
2. open a `code-workspace` file in Theia.
3. notice that the explorer displays the roots but they are empty (won't expand).
4. hover over a root item and notice the incorrect path.

**OS and Theia version:**
Ubuntu 16.04 and Theia 5a39e78e99fa17b987634bc7216618ae66b65083",0,  unable to properly open    code workspace  files        description  theia becomes unresponsive when attempting to open    code workspace  files    vscode workspace files   this is likely due to the way we resolve the paths  hovering over the explorer items shows the following for example    home vince desktop  home vin workspace ls interact    notice the incorrect   path   and   double                reproduction steps     ensure the multi root preference is enabled  workspace supportmultirootworkspace       open a  code workspace  file in theia      notice that the explorer displays the roots but they are empty  won t expand       hover over a root item and notice the incorrect path       os and theia version     ubuntu     and theia  ,0
297000,25591027577.0,IssuesEvent,2022-12-01 13:02:00,dotnet/maui,https://api.github.com/repos/dotnet/maui,closed,Picker Items not showing when BindingContext is changed from null to value at runtime,t/bug platform/windows 🪟 area/controls 🎮 control-picker s/try-latest-version,"### Description


Picker Items not showing when BindingContext is changed from null to value at runtime



### Steps to Reproduce

Run the attached sample.
Click on the picker to see drop down values.
Now change the binding context by clicking on the button
See the picker shows empty.
[SampleProject.zip](https://github.com/dotnet/maui/files/9624099/SampleProject.zip)

### Link to public reproduction project repository

[SampleProject.zip](https://github.com/dotnet/maui/files/9624099/SampleProject.zip)

### Version with bug

6.0.486

### Last version that worked well

Unknown/Other

### Affected platforms

iOS, Android, Windows

### Affected platform versions

Windows SDK 10.0.19041.0

### Did you find any workaround?

no

### Relevant log output

_No response_",1.0,"Picker Items not showing when BindingContext is changed from null to value at runtime - ### Description


Picker Items not showing when BindingContext is changed from null to value at runtime



### Steps to Reproduce

Run the attached sample.
Click on the picker to see drop down values.
Now change the binding context by clicking on the button
See the picker shows empty.
[SampleProject.zip](https://github.com/dotnet/maui/files/9624099/SampleProject.zip)

### Link to public reproduction project repository

[SampleProject.zip](https://github.com/dotnet/maui/files/9624099/SampleProject.zip)

### Version with bug

6.0.486

### Last version that worked well

Unknown/Other

### Affected platforms

iOS, Android, Windows

### Affected platform versions

Windows SDK 10.0.19041.0

### Did you find any workaround?

no

### Relevant log output

_No response_",0,picker items not showing when bindingcontext is changed from null to value at runtime       description    picker items not showing when bindingcontext is changed from null to value at runtime          steps to reproduce  run the attached sample   click on the picker to see drop down values   now change the binding context by clicking on the button  see the picker shows empty            link to public reproduction project repository           version with bug             last version that worked well  unknown other      affected platforms  ios  android  windows      affected platform versions  windows sdk              did you find any workaround   no      relevant log output   no response ,0
108007,13538893660.0,IssuesEvent,2020-09-16 12:45:54,miamiworks/web,https://api.github.com/repos/miamiworks/web,closed,Jobs section gallery view,⭐️ high priority 🎨 design 💻  front-end,"We've received feedback where users are not sure how to scroll through events/jobs on the home page to access more jobs. Suggested update:

Jobs: convert with a gallery view with a CTA to the dedicated jobs page. [Figma Design](https://www.figma.com/file/6SMBgAOsrFc0Vf4oUnDsSe/MiamiTech.Works?node-id=186%3A4597) 
![image](https://user-images.githubusercontent.com/16677332/92532422-4338bb00-f1fe-11ea-9329-db21582027d2.png)
",1.0,"Jobs section gallery view - We've received feedback where users are not sure how to scroll through events/jobs on the home page to access more jobs. Suggested update:

Jobs: convert with a gallery view with a CTA to the dedicated jobs page. [Figma Design](https://www.figma.com/file/6SMBgAOsrFc0Vf4oUnDsSe/MiamiTech.Works?node-id=186%3A4597) 
![image](https://user-images.githubusercontent.com/16677332/92532422-4338bb00-f1fe-11ea-9329-db21582027d2.png)
",0,jobs section gallery view   we ve received feedback where users are not sure how to scroll through events jobs on the home page to access more jobs  suggested update     jobs  convert with a gallery view with a cta to the dedicated jobs page              ,0
315681,27094598496.0,IssuesEvent,2023-02-15 01:01:42,dotnet/maui,https://api.github.com/repos/dotnet/maui,closed,Httpclient can't use header Host SNI,t/bug partner/android s/try-latest-version partner/mono,"### Description

MAUI can't use HttpClient to specify the host of the request's header, such as the request address https://10.2.0.1:433 and I specify host as xxxx.com, and the result I get is that the program crashes.

### Steps to Reproduce

MAUI can't use HttpClient to specify the host of the request's header, such as the request address https://10.2.0.1:433 and I specify host as xxxx.com, and the result I get is that the program crashes.

### Version with bug

6.0.400 (current)

### Last version that worked well

other

### Affected platforms

Android

### Affected platform versions

Android 29

### Did you find any workaround?

NO

### Relevant log output

_No response_",1.0,"Httpclient can't use header Host SNI - ### Description

MAUI can't use HttpClient to specify the host of the request's header, such as the request address https://10.2.0.1:433 and I specify host as xxxx.com, and the result I get is that the program crashes.

### Steps to Reproduce

MAUI can't use HttpClient to specify the host of the request's header, such as the request address https://10.2.0.1:433 and I specify host as xxxx.com, and the result I get is that the program crashes.

### Version with bug

6.0.400 (current)

### Last version that worked well

other

### Affected platforms

Android

### Affected platform versions

Android 29

### Did you find any workaround?

NO

### Relevant log output

_No response_",0,httpclient can t use header host sni       description    maui can t use httpclient to specify the host of the request s header  such as the request address   and i specify host as xxxx com  and the result i get is that the program crashes         steps to reproduce    maui can t use httpclient to specify the host of the request s header  such as the request address   and i specify host as xxxx com  and the result i get is that the program crashes         version with bug           current         last version that worked well    other        affected platforms    android        affected platform versions    android          did you find any workaround     no        relevant log output     no response ,0
148576,13240030536.0,IssuesEvent,2020-08-19 05:18:26,golang/go,https://api.github.com/repos/golang/go,opened,x/debug: change the repo description used in golang.org/pkg page.,Documentation,"![image](https://user-images.githubusercontent.com/4999471/90594870-808ac980-e1b9-11ea-887a-772397d5e77a.png)
Here, the 'x/debug' repo is listed as a repo for 'an experimental debugger for Go'.
This is outdated. Please update the repo description and this documentation.",1.0,"x/debug: change the repo description used in golang.org/pkg page. - ![image](https://user-images.githubusercontent.com/4999471/90594870-808ac980-e1b9-11ea-887a-772397d5e77a.png)
Here, the 'x/debug' repo is listed as a repo for 'an experimental debugger for Go'.
This is outdated. Please update the repo description and this documentation.",1,x debug  change the repo description used in golang org pkg page          here  the  x debug  repo is listed as a repo for  an experimental debugger for go    this is outdated  please update the repo description and this documentation ,1
241855,20166919959.0,IssuesEvent,2022-02-10 06:05:10,metaplex-foundation/metaplex,https://api.github.com/repos/metaplex-foundation/metaplex,closed,[Bug]: Compilation error while starting the server,needs tests bug,"### Which package is this bug report for?

candy machine ui

### Issue description

I would start my server with the command:
    
I have already make ""Yarn install"" in the candy-machine-ui folder.
    
The local host page also opens, but I can't click the Mint button on it.
    
Anybody can help me?



### Command

```shell
PS C:\Users\Thoma\Desktop\v2\metaplex\js\packages\candy-machine-ui> yarn install
yarn install v1.22.17
[1/4] Resolving packages...
Failed to compile.

C:/Users/Thoma/Desktop/v2/metaplex/js/packages/candy-machine-ui/src/candy-machine.ts
TypeScript error in C:/Users/Thoma/Desktop/v2/metaplex/js/packages/candy-machine-ui/src/candy-machine.ts(441,40):
Property 'SYSVAR_SLOT_HASHES_PUBKEY' does not exist on type 'typeof import(""@solana/web3.js"")'.  TS2339

    439 |         rent: anchor.web3.SYSVAR_RENT_PUBKEY,
    440 |         clock: anchor.web3.SYSVAR_CLOCK_PUBKEY,
  > 441 |         recentBlockhashes: anchor.web3.SYSVAR_SLOT_HASHES_PUBKEY,
        |                                        ^
    442 |         instructionSysvarAccount: anchor.web3.SYSVAR_INSTRUCTIONS_PUBKEY,
    443 |       },
    444 |       remainingAccounts:
```


### Relevant log output

_No response_

### Operating system

Visual Studio

### Priority this issue should have

Medium (should be fixed soon)

### Check the Docs First

- [X] I have checked the docs and it didn't solve my issue",1.0,"[Bug]: Compilation error while starting the server - ### Which package is this bug report for?

candy machine ui

### Issue description

I would start my server with the command:
    
I have already make ""Yarn install"" in the candy-machine-ui folder.
    
The local host page also opens, but I can't click the Mint button on it.
    
Anybody can help me?



### Command

```shell
PS C:\Users\Thoma\Desktop\v2\metaplex\js\packages\candy-machine-ui> yarn install
yarn install v1.22.17
[1/4] Resolving packages...
Failed to compile.

C:/Users/Thoma/Desktop/v2/metaplex/js/packages/candy-machine-ui/src/candy-machine.ts
TypeScript error in C:/Users/Thoma/Desktop/v2/metaplex/js/packages/candy-machine-ui/src/candy-machine.ts(441,40):
Property 'SYSVAR_SLOT_HASHES_PUBKEY' does not exist on type 'typeof import(""@solana/web3.js"")'.  TS2339

    439 |         rent: anchor.web3.SYSVAR_RENT_PUBKEY,
    440 |         clock: anchor.web3.SYSVAR_CLOCK_PUBKEY,
  > 441 |         recentBlockhashes: anchor.web3.SYSVAR_SLOT_HASHES_PUBKEY,
        |                                        ^
    442 |         instructionSysvarAccount: anchor.web3.SYSVAR_INSTRUCTIONS_PUBKEY,
    443 |       },
    444 |       remainingAccounts:
```


### Relevant log output

_No response_

### Operating system

Visual Studio

### Priority this issue should have

Medium (should be fixed soon)

### Check the Docs First

- [X] I have checked the docs and it didn't solve my issue",0,   compilation error while starting the server       which package is this bug report for   candy machine ui      issue description  i would start my server with the command         i have already make  yarn install  in the candy machine ui folder         the local host page also opens  but i can t click the mint button on it         anybody can help me           command     shell ps c  users thoma desktop   metaplex js packages candy machine ui  yarn install  yarn install          resolving packages     failed to compile     c  users thoma desktop   metaplex js packages candy machine ui src candy machine ts  typescript error in c  users thoma desktop   metaplex js packages candy machine ui src candy machine ts        property  sysvar slot hashes pubkey  does not exist on type  typeof import   solana   js                           rent  anchor   sysvar rent pubkey                   clock  anchor   sysvar clock pubkey                   recentblockhashes  anchor   sysvar slot hashes pubkey                                                                       instructionsysvaraccount  anchor   sysvar instructions pubkey                                   remainingaccounts            relevant log output   no response       operating system  visual studio      priority this issue should have  medium  should be fixed soon       check the docs first      i have checked the docs and it didn t solve my issue,0
333298,24370014352.0,IssuesEvent,2022-10-03 18:25:19,golang/go,https://api.github.com/repos/golang/go,closed,go/build: documentation for Context still mentions +build rather than go:build,Documentation NeedsFix,"I noticed that some of the internal commentary in `go/build/build.go` still refers (exclusively) to `+build` lines rather than `go:build`. In one place this leaks in external documentation: the documentation for [`go/build.Context`](https://pkg.go.dev/go/build#Context). We should update that to refer to `go:build`, to be consistent with the package documentation.

Milestoning for 1.20 since it is not urgent.

CC @bcmills ",1.0,"go/build: documentation for Context still mentions +build rather than go:build - I noticed that some of the internal commentary in `go/build/build.go` still refers (exclusively) to `+build` lines rather than `go:build`. In one place this leaks in external documentation: the documentation for [`go/build.Context`](https://pkg.go.dev/go/build#Context). We should update that to refer to `go:build`, to be consistent with the package documentation.

Milestoning for 1.20 since it is not urgent.

CC @bcmills ",1,go build  documentation for context still mentions  build rather than go build   i noticed that some of the internal commentary in  go build build go  still refers  exclusively  to   build  lines rather than  go build   in one place this leaks in external documentation  the documentation for     we should update that to refer to  go build   to be consistent with the package documentation     milestoning for     since it is not urgent     cc  bcmills ,1
84028,10347658688.0,IssuesEvent,2019-09-04 17:55:35,golang/go,https://api.github.com/repos/golang/go,closed,doc: errors: wrong unwrap example [1.13 backport],CherryPickApproved Documentation,"@jba requested issue #34061 to be considered for backport to the next 1.13 minor release.

> @gopherbot please backport 1.13
",1.0,"doc: errors: wrong unwrap example [1.13 backport] - @jba requested issue #34061 to be considered for backport to the next 1.13 minor release.

> @gopherbot please backport 1.13
",1,doc  errors  wrong unwrap example      jba requested issue    to be considered for backport to the next     minor release      gopherbot please backport     ,1
85840,8000201398.0,IssuesEvent,2018-07-22 13:14:01,Ks89/angular-modal-gallery,https://api.github.com/repos/Ks89/angular-modal-gallery,closed,Slider Swipe in Tablet and Mobile,comp:client comp:testing effort2:medium (days) priority:high type:feature,"## I'm submitting a...
<!-- Check one of the following options with ""x"" -->
<pre><code>
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  <!-- Please search on GitHub for a similar issue or PR before submitting -->
[x] Feature request
[ ] Documentation issue or request
[ ] Support request
</code></pre>

## Current behavior
In mobile and tablet,  the swipe is inverted: when we swipe left, the slider navigates to the previous slider.


## Expected behavior
When we swipe left, the slider navigates to the next slider, wich is the expected common behavior.


## What is the motivation / use case for changing the behavior?
The most common behavior, wich we would like to have in our website, is that when we swipe left, the slider navigates to the next image and, when we swipe right, the slider navigates to the previous image. 

<!-- This template is based on angular repository :) -->
",1.0,"Slider Swipe in Tablet and Mobile - ## I'm submitting a...
<!-- Check one of the following options with ""x"" -->
<pre><code>
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  <!-- Please search on GitHub for a similar issue or PR before submitting -->
[x] Feature request
[ ] Documentation issue or request
[ ] Support request
</code></pre>

## Current behavior
In mobile and tablet,  the swipe is inverted: when we swipe left, the slider navigates to the previous slider.


## Expected behavior
When we swipe left, the slider navigates to the next slider, wich is the expected common behavior.


## What is the motivation / use case for changing the behavior?
The most common behavior, wich we would like to have in our website, is that when we swipe left, the slider navigates to the next image and, when we swipe right, the slider navigates to the previous image. 

<!-- This template is based on angular repository :) -->
",0,slider swipe in tablet and mobile      i m submitting a              regression  a behavior that used to work and stopped working in a new release     bug report       feature request    documentation issue or request    support request           current behavior  in mobile and tablet   the swipe is inverted  when we swipe left  the slider navigates to the previous slider          expected behavior  when we swipe left  the slider navigates to the next slider  wich is the expected common behavior          what is the motivation   use case for changing the behavior   the most common behavior  wich we would like to have in our website  is that when we swipe left  the slider navigates to the next image and  when we swipe right  the slider navigates to the previous image         ,0
69695,9321396990.0,IssuesEvent,2019-03-27 03:42:15,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: document that gofiles on command line must be in same directory,Documentation GoCommand NeedsFix help wanted,"### What version of Go are you using (`go version`)?

`go version go1.9rc2 darwin/amd64`

### What operating system and processor architecture are you using (`go env`)?

<details><br>

```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/Dmitri/Dropbox/Work/2013/GoLanding:/Users/Dmitri/Dropbox/Work/2013/GoLand""
GORACE=""""
GOROOT=""/usr/local/go""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/tw/kgz4v2kn4n7d7ryg5k_z3dk40000gn/T/go-build182434083=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
```

</details>

### What did you do?

I read https://golang.org/cmd/go/#hdr-Compile_and_run_Go_program, it said:

> Usage:
>
>     go run [build flags] [-exec xprog] gofiles... [arguments...]
>
> Run compiles and runs the main package comprising the named Go source files. **A Go source file is defined to be a file ending in a literal "".go"" suffix.**
>
> [more details that are not relevant]

Notice there are no restrictions on the prefix of the file, what directory it's in, or what build constraints the file has.

Then I ran:

```bash
mkdir -p $GOPATH/src/new/package
cd $GOPATH/src/new/package
echo 'package main; import ""fmt""; func main() { fmt.Println(""go"") }' > main.go
go run main.go
mv main.go 123.go
go run 123.go
mv 123.go _underscore.go
go run _underscore.go
mv _underscore.go .dot.go
go run .dot.go
mv .dot.go thisis.notgo
go run thisis.notgo
rm thisis.notgo
go run
```

(Credit goes to @natefinch for discovering this at https://twitter.com/NateTheFinch/status/898585298111787009.)

### What did you expect to see?

```
go
go
go
go
go run: no go files listed
go run: no go files listed
```

### What did you see instead?

```
go
go
package main: no Go files in /Users/Gopher/go/src/new/package
package main: no Go files in /Users/Gopher/go/src/new/package
go run: no go files listed
go run: no go files listed
```

It looks like the .go file starting with _ or . gets ignored, probably related to the logic `go/build` has to ignore files beginning with _ and . in normal Go packages.

**Edit:** Upon further reading, I think this section from https://golang.org/cmd/go/#hdr-Description_of_package_lists applies and explains the behavior:

> As a special case, if the package list is a list of .go files from a single directory, the command is applied to a single synthesized package made up of exactly those files, ignoring any build constraints in those files and ignoring any other files in the directory.
>
> Directory and file names that begin with ""."" or ""_"" are ignored by the go tool, as are directories named ""testdata"".",1.0,"cmd/go: document that gofiles on command line must be in same directory - ### What version of Go are you using (`go version`)?

`go version go1.9rc2 darwin/amd64`

### What operating system and processor architecture are you using (`go env`)?

<details><br>

```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/Dmitri/Dropbox/Work/2013/GoLanding:/Users/Dmitri/Dropbox/Work/2013/GoLand""
GORACE=""""
GOROOT=""/usr/local/go""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/tw/kgz4v2kn4n7d7ryg5k_z3dk40000gn/T/go-build182434083=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
```

</details>

### What did you do?

I read https://golang.org/cmd/go/#hdr-Compile_and_run_Go_program, it said:

> Usage:
>
>     go run [build flags] [-exec xprog] gofiles... [arguments...]
>
> Run compiles and runs the main package comprising the named Go source files. **A Go source file is defined to be a file ending in a literal "".go"" suffix.**
>
> [more details that are not relevant]

Notice there are no restrictions on the prefix of the file, what directory it's in, or what build constraints the file has.

Then I ran:

```bash
mkdir -p $GOPATH/src/new/package
cd $GOPATH/src/new/package
echo 'package main; import ""fmt""; func main() { fmt.Println(""go"") }' > main.go
go run main.go
mv main.go 123.go
go run 123.go
mv 123.go _underscore.go
go run _underscore.go
mv _underscore.go .dot.go
go run .dot.go
mv .dot.go thisis.notgo
go run thisis.notgo
rm thisis.notgo
go run
```

(Credit goes to @natefinch for discovering this at https://twitter.com/NateTheFinch/status/898585298111787009.)

### What did you expect to see?

```
go
go
go
go
go run: no go files listed
go run: no go files listed
```

### What did you see instead?

```
go
go
package main: no Go files in /Users/Gopher/go/src/new/package
package main: no Go files in /Users/Gopher/go/src/new/package
go run: no go files listed
go run: no go files listed
```

It looks like the .go file starting with _ or . gets ignored, probably related to the logic `go/build` has to ignore files beginning with _ and . in normal Go packages.

**Edit:** Upon further reading, I think this section from https://golang.org/cmd/go/#hdr-Description_of_package_lists applies and explains the behavior:

> As a special case, if the package list is a list of .go files from a single directory, the command is applied to a single synthesized package made up of exactly those files, ignoring any build constraints in those files and ignoring any other files in the directory.
>
> Directory and file names that begin with ""."" or ""_"" are ignored by the go tool, as are directories named ""testdata"".",1,cmd go  document that gofiles on command line must be in same directory       what version of go are you using   go version        go version     darwin           what operating system and processor architecture are you using   go env                  goarch      gobin     goexe     gohostarch      gohostos  darwin   goos  darwin   gopath   users dmitri dropbox work   golanding  users dmitri dropbox work   goland   gorace     goroot   usr local go   gotooldir   usr local go pkg tool darwin     gccgo  gccgo   cc  clang   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders tw     t go    tmp go build  gno record gcc switches  fno common   cxx  clang     cgo enabled      cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config                   what did you do     i read   it said       usage            go run     gofiles            run compiles and runs the main package comprising the named go source files    a go source file is defined to be a file ending in a literal   go  suffix               notice there are no restrictions on the prefix of the file  what directory it s in  or what build constraints the file has     then i ran        bash  mkdir  p  gopath src new package  cd  gopath src new package  echo  package main  import  fmt   func main     fmt println  go        main go  go run main go  mv main go   go  go run   go  mv   go  underscore go  go run  underscore go  mv  underscore go  dot go  go run  dot go  mv  dot go thisis notgo  go run thisis notgo  rm thisis notgo  go run          credit goes to  natefinch for discovering this at          what did you expect to see          go  go  go  go  go run  no go files listed  go run  no go files listed             what did you see instead          go  go  package main  no go files in  users gopher go src new package  package main  no go files in  users gopher go src new package  go run  no go files listed  go run  no go files listed         it looks like the  go file starting with   or   gets ignored  probably related to the logic  go build  has to ignore files beginning with   and   in normal go packages       edit    upon further reading  i think this section from   applies and explains the behavior       as a special case  if the package list is a list of  go files from a single directory  the command is applied to a single synthesized package made up of exactly those files  ignoring any build constraints in those files and ignoring any other files in the directory        directory and file names that begin with     or     are ignored by the go tool  as are directories named  testdata  ,1
32004,6024024196.0,IssuesEvent,2017-06-08 02:54:59,golang/go,https://api.github.com/repos/golang/go,closed,doc: improve `go test --help` -timeout usage message,Documentation,"Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?

`go version go1.8 darwin/amd64`

### What operating system and processor architecture are you using (`go env`)?

```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/glendc/go""
GORACE=""""
GOROOT=""/usr/local/go""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/gy/ldypn6dn08b_8q7cn3mg0l440000gn/T/go-build629694106=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
PKG_CONFIG=""pkg-config""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
```

### What did you do?

```
$ go test --help 2> >(grep -A2 timeout)
```
### What did you expect to see?

```
	-timeout t
	    If a package runs longer than t, panic.
	    The default is 10 minutes (10m).
```

### What did you see instead?

```
	-timeout t
	    If a test runs longer than t, panic.
	    The default is 10 minutes (10m).
```

Right now it seems to indicate that if an individual test, such as `TestFoo`, runs longer than t, it panic. But this is not true, and in fact after some local testing, it seems to be that it applies the timeout value on a package level, rather than it being applied on a single test only. Especially the ""`a test`"" is very confusing imho.

I'm not the greatest in writing clear documentation though, so there is probably a better way to put it, than what I propose.",1.0,"doc: improve `go test --help` -timeout usage message - Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?

`go version go1.8 darwin/amd64`

### What operating system and processor architecture are you using (`go env`)?

```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/glendc/go""
GORACE=""""
GOROOT=""/usr/local/go""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/gy/ldypn6dn08b_8q7cn3mg0l440000gn/T/go-build629694106=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
PKG_CONFIG=""pkg-config""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
```

### What did you do?

```
$ go test --help 2> >(grep -A2 timeout)
```
### What did you expect to see?

```
	-timeout t
	    If a package runs longer than t, panic.
	    The default is 10 minutes (10m).
```

### What did you see instead?

```
	-timeout t
	    If a test runs longer than t, panic.
	    The default is 10 minutes (10m).
```

Right now it seems to indicate that if an individual test, such as `TestFoo`, runs longer than t, it panic. But this is not true, and in fact after some local testing, it seems to be that it applies the timeout value on a package level, rather than it being applied on a single test only. Especially the ""`a test`"" is very confusing imho.

I'm not the greatest in writing clear documentation though, so there is probably a better way to put it, than what I propose.",1,doc  improve  go test   help   timeout usage message   please answer these questions before submitting your issue  thanks         what version of go are you using   go version        go version     darwin           what operating system and processor architecture are you using   go env            goarch      gobin     goexe     gohostarch      gohostos  darwin   goos  darwin   gopath   users glendc go   gorace     goroot   usr local go   gotooldir   usr local go pkg tool darwin     gccgo  gccgo   cc  clang   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders gy     t go    tmp go build  gno record gcc switches  fno common   cxx  clang     cgo enabled      pkg config  pkg config   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g                 what did you do            go test   help      grep    timeout            what did you expect to see          	 timeout t  	    if a package runs longer than t  panic   	    the default is   minutes                  what did you see instead          	 timeout t  	    if a test runs longer than t  panic   	    the default is   minutes              right now it seems to indicate that if an individual test  such as  testfoo   runs longer than t  it panic  but this is not true  and in fact after some local testing  it seems to be that it applies the timeout value on a package level  rather than it being applied on a single test only  especially the   a test   is very confusing imho     i m not the greatest in writing clear documentation though  so there is probably a better way to put it  than what i propose ,1
81442,23464041414.0,IssuesEvent,2022-08-16 15:14:19,scikit-learn/scikit-learn,https://api.github.com/repos/scikit-learn/scikit-learn,closed,⚠️ CI failed on Linux.ubuntu_atlas ⚠️,Build / CI,"**CI is still failing on [Linux.ubuntu_atlas](https://dev.azure.com/scikit-learn/scikit-learn/_build/results?buildId=45560&view=logs&j=0a287ed6-22f4-5cb4-88b1-d5fcdc4d8b7e)** (Aug 11, 2022)
- test_pairwise_distances_argkmin[80-float32-parallel_on_X-cityblock-1000000.0-500]
- test_pairwise_distances_argkmin[80-float32-parallel_on_Y-cityblock-1000000.0-500]",1.0,"⚠️ CI failed on Linux.ubuntu_atlas ⚠️ - **CI is still failing on [Linux.ubuntu_atlas](https://dev.azure.com/scikit-learn/scikit-learn/_build/results?buildId=45560&view=logs&j=0a287ed6-22f4-5cb4-88b1-d5fcdc4d8b7e)** (Aug 11, 2022)
- test_pairwise_distances_argkmin[80-float32-parallel_on_X-cityblock-1000000.0-500]
- test_pairwise_distances_argkmin[80-float32-parallel_on_Y-cityblock-1000000.0-500]",0,⚠️ ci failed on linux ubuntu atlas ⚠️     ci is still failing on      aug         test pairwise distances argkmin    test pairwise distances argkmin ,0
430236,30122302858.0,IssuesEvent,2023-06-30 16:09:31,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/go/packages/gopackages: better documentation of -mode flag,Documentation NeedsInvestigation Tools,"

### What version of Go are you using (`go version`)?

<pre>
go version go1.20 windows/amd64
</pre>

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\Steven\AppData\Local\go-build
set GOENV=C:\Users\Steven\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\Steven\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\Steven\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=D:\go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=D:\go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.20
set GCCGO=gccgo
set GOAMD64=v1
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=NUL
set GOWORK=
set CGO_CFLAGS=-O2 -g
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-O2 -g
set CGO_FFLAGS=-O2 -g
set CGO_LDFLAGS=-O2 -g
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=C:\Windows\TEMP\go-build2434007380=/tmp/go-build -gno-record-gcc-switches
</pre></details>

### What did you do?

using this input:

~~~go
package tls

type dsaSignature struct { }

type lruSessionCache struct {}

func NewLRUClientSessionCache() lruSessionCache {
	return lruSessionCache{}
}
~~~

### What did you see instead?

I get this result:

~~~
> gopackages -mode types -private tls
Go package ""tls"":
        package tls
        has complete exported type info
        file D:\Desktop\etc\common.go
        func NewLRUClientSessionCache() lruSessionCache
        type lruSessionCache struct{}
~~~

one type is listed, but the other is not.",1.0,"x/tools/go/packages/gopackages: better documentation of -mode flag - 

### What version of Go are you using (`go version`)?

<pre>
go version go1.20 windows/amd64
</pre>

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\Steven\AppData\Local\go-build
set GOENV=C:\Users\Steven\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\Steven\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\Steven\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=D:\go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=D:\go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.20
set GCCGO=gccgo
set GOAMD64=v1
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=NUL
set GOWORK=
set CGO_CFLAGS=-O2 -g
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-O2 -g
set CGO_FFLAGS=-O2 -g
set CGO_LDFLAGS=-O2 -g
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=C:\Windows\TEMP\go-build2434007380=/tmp/go-build -gno-record-gcc-switches
</pre></details>

### What did you do?

using this input:

~~~go
package tls

type dsaSignature struct { }

type lruSessionCache struct {}

func NewLRUClientSessionCache() lruSessionCache {
	return lruSessionCache{}
}
~~~

### What did you see instead?

I get this result:

~~~
> gopackages -mode types -private tls
Go package ""tls"":
        package tls
        has complete exported type info
        file D:\Desktop\etc\common.go
        func NewLRUClientSessionCache() lruSessionCache
        type lruSessionCache struct{}
~~~

one type is listed, but the other is not.",1,x tools go packages gopackages  better documentation of  mode flag           what version of go are you using   go version          go version     windows             what operating system and processor architecture are you using   go env          go env  output     set     set goarch    set gobin   set gocache c  users steven appdata local go build  set goenv c  users steven appdata roaming go env  set goexe  exe  set goexperiment   set goflags   set gohostarch    set gohostos windows  set goinsecure   set gomodcache c  users steven go pkg mod  set gonoproxy   set gonosumdb   set goos windows  set gopath c  users steven go  set goprivate   set goproxy    set goroot d  go  set gosumdb sum golang org  set gotmpdir   set gotooldir d  go pkg tool windows    set govcs   set goversion      set gccgo gccgo  set      set ar ar  set cc gcc  set cxx g    set cgo enabled    set gomod nul  set gowork   set cgo cflags     g  set cgo cppflags   set cgo cxxflags     g  set cgo fflags     g  set cgo ldflags     g  set pkg config pkg config  set gogccflags     mthreads  wl   no gc sections  fmessage length    fdebug prefix map c  windows temp go    tmp go build  gno record gcc switches            what did you do     using this input        go  package tls    type dsasignature struct        type lrusessioncache struct       func newlruclientsessioncache   lrusessioncache    	return lrusessioncache                  what did you see instead     i get this result            gopackages  mode types  private tls  go package  tls            package tls          has complete exported type info          file d  desktop etc common go          func newlruclientsessioncache   lrusessioncache          type lrusessioncache struct           one type is listed  but the other is not ,1
265284,23158469292.0,IssuesEvent,2022-07-29 15:08:58,elastic/elasticsearch,https://api.github.com/repos/elastic/elasticsearch,opened,[CI] FileSettingsServiceIT testSettingsApplied failing,:Core/Infra/Core >test-failure Team:Core/Infra,"**Build scan:**
https://gradle-enterprise.elastic.co/s/pijicvldxziw4/tests/:server:internalClusterTest/org.elasticsearch.reservedstate.service.FileSettingsServiceIT/testSettingsApplied

**Reproduction line:**
`./gradlew ':server:internalClusterTest' --tests ""org.elasticsearch.reservedstate.service.FileSettingsServiceIT.testSettingsApplied"" -Dtests.seed=129CA1A8D872CBA3 -Dtests.locale=sr-BA -Dtests.timezone=Asia/Kamchatka -Druntime.java=17`

**Applicable branches:**
main

**Reproduces locally?:**
No

**Failure history:**
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.reservedstate.service.FileSettingsServiceIT&tests.test=testSettingsApplied

**Failure excerpt:**
```
java.lang.Exception: Test abandoned because suite timeout was reached.

  at __randomizedtesting.SeedInfo.seed([129CA1A8D872CBA3]:0)

```",1.0,"[CI] FileSettingsServiceIT testSettingsApplied failing - **Build scan:**
https://gradle-enterprise.elastic.co/s/pijicvldxziw4/tests/:server:internalClusterTest/org.elasticsearch.reservedstate.service.FileSettingsServiceIT/testSettingsApplied

**Reproduction line:**
`./gradlew ':server:internalClusterTest' --tests ""org.elasticsearch.reservedstate.service.FileSettingsServiceIT.testSettingsApplied"" -Dtests.seed=129CA1A8D872CBA3 -Dtests.locale=sr-BA -Dtests.timezone=Asia/Kamchatka -Druntime.java=17`

**Applicable branches:**
main

**Reproduces locally?:**
No

**Failure history:**
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.reservedstate.service.FileSettingsServiceIT&tests.test=testSettingsApplied

**Failure excerpt:**
```
java.lang.Exception: Test abandoned because suite timeout was reached.

  at __randomizedtesting.SeedInfo.seed([129CA1A8D872CBA3]:0)

```",0,  filesettingsserviceit testsettingsapplied failing     build scan         reproduction line       gradlew   server internalclustertest    tests  org elasticsearch reservedstate service filesettingsserviceit testsettingsapplied   dtests seed    dtests locale sr ba  dtests timezone asia kamchatka  druntime java       applicable branches    main    reproduces locally     no    failure history         failure excerpt        java lang exception  test abandoned because suite timeout was reached     at   randomizedtesting seedinfo seed          ,0
49620,7523867906.0,IssuesEvent,2018-04-13 03:41:06,golang/go,https://api.github.com/repos/golang/go,closed,doc: go doc -c flag description unclear,Documentation,"### What version of Go are you using (`go version`)?

```
go version go1.8.1 darwin/amd64
```

### What operating system and processor architecture are you using (`go env`)?

```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/will.faught/Developer/go""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.8.1/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.8.1/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/jt/c0hjffqj6gxbhy00gm0btzkr79h225/T/go-build727032531=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
PKG_CONFIG=""pkg-config""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
```

### What did you do?

```sh
$ go doc -h
```

### What did you see?

```output
Usage of [go] doc:
	go doc
	go doc <pkg>
	go doc <sym>[.<method>]
	go doc [<pkg>].<sym>[.<method>]
	go doc <pkg> <sym>[.<method>]
For more information run
	go help doc

Flags:
  -c	symbol matching honors case (paths not affected)
  -cmd
    	show symbols with package docs even if package is a command
  -u	show unexported symbols as well as exported
exit status 2
```

It isn't clear what ""symbol matching honors case (paths not affected)"" means. Go doc should be fixed to print a clearer description.",1.0,"doc: go doc -c flag description unclear - ### What version of Go are you using (`go version`)?

```
go version go1.8.1 darwin/amd64
```

### What operating system and processor architecture are you using (`go env`)?

```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/will.faught/Developer/go""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.8.1/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.8.1/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/jt/c0hjffqj6gxbhy00gm0btzkr79h225/T/go-build727032531=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
PKG_CONFIG=""pkg-config""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
```

### What did you do?

```sh
$ go doc -h
```

### What did you see?

```output
Usage of [go] doc:
	go doc
	go doc <pkg>
	go doc <sym>[.<method>]
	go doc [<pkg>].<sym>[.<method>]
	go doc <pkg> <sym>[.<method>]
For more information run
	go help doc

Flags:
  -c	symbol matching honors case (paths not affected)
  -cmd
    	show symbols with package docs even if package is a command
  -u	show unexported symbols as well as exported
exit status 2
```

It isn't clear what ""symbol matching honors case (paths not affected)"" means. Go doc should be fixed to print a clearer description.",1,doc  go doc  c flag description unclear       what version of go are you using   go version            go version       darwin               what operating system and processor architecture are you using   go env            goarch      gobin     goexe     gohostarch      gohostos  darwin   goos  darwin   gopath   users will faught developer go   gorace     goroot   usr local cellar go       libexec   gotooldir   usr local cellar go       libexec pkg tool darwin     gccgo  gccgo   cc  clang   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders jt   t go    tmp go build  gno record gcc switches  fno common   cxx  clang     cgo enabled      pkg config  pkg config   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g                 what did you do        sh    go doc  h             what did you see        output  usage of   doc   	go doc  	go doc    	go doc     	go doc       	go doc       for more information run  	go help doc    flags      c	symbol matching honors case  paths not affected      cmd      	show symbols with package docs even if package is a command     u	show unexported symbols as well as exported  exit status           it isn t clear what  symbol matching honors case  paths not affected   means  go doc should be fixed to print a clearer description ,1
51903,10736028735.0,IssuesEvent,2019-10-29 10:01:28,lihe/Leetcode,https://api.github.com/repos/lihe/Leetcode,opened,Leetcode_187_Repeated DNA Sequences,Leetcode,"#### [Repeated DNA Sequences](https://leetcode-cn.com/problems/repeated-dna-sequences/)

All DNA is composed of a series of nucleotides abbreviated as A, C, G, and T, for example: ""ACGAATTCCG"". When studying DNA, it is sometimes useful to identify repeated sequences within the DNA.

Write a function to find all the 10-letter-long sequences (substrings) that occur more than once in a DNA molecule.

**Example:**

```
Input: s = ""AAAAACCCCCAAAAACCCCCCAAAAAGGGTTT""

Output: [""AAAAACCCCC"", ""CCCCCAAAAA""]
```

**题意：将DNA序列看成一个只包含`[A，B，C，D]`四个字符的字符串，给一个DNA字符串，找出所有长度为10的且出现次数超过一次的字符串。**

算法思路：

方法一：

1. 枚举DNA字符串中所有的长度为10的子串，将其插入到哈希Map中，并记录子串的数量；
2. 遍历哈希Map，将所有出现次数超过一次的子串存储到结果中

**算法复杂度为`O(n)`**

```c++
class Solution{
public:
    std::vector<std::string> findRepeatedDnaSequences(std::string s){
        std::map<std::string, int> word_map;
        std::vector<std::string> result;
        for(int i = 0; i < s.length(); i++){
            std::string word = s.substr(i, 10);
            if(word_map.find(word) != word_map.end()){
                word_map[word] += 1;
            }
            else{
                word_map[word] = 1;
            }
        }
        std::map<std::string, int> :: iterator it;
        for(it = word_map.begin(); it != word_map.end(); it++){
            if(it -> second > 1){
                result.push_back(it -> first);
            }
        }
        return result;
    }
};

```

方法二：

1. 设置全局变量哈希`int g_hash_map[1028576]` *1048576 = 2^20*，表示所有的长度为10的DNA序列；
2. 将DNA字符串的前十个字符使用左移运算转化为整数`key`，`g_hash_map[key]++`;
3. 从DNA的第11个字符开始，按顺序遍历各个字符，遇到一个字符即将`key`右移二位（去掉最低位），并将新的DNA字符`s[i]`转化为整数后，或到最后两位，`g_hash_map[key]++`;
4. 遍历哈希表`g_hash_map`，若`g_hash_map[i] > 1`，将`i`从低到高位转化为10个DNA序列，`push`到结果数组。

```c++
int g_hash_map[1048576] = {0};

std::string change_int_to_DNA(int DNA){
    static const char DNA_CHAR[] = {'A', 'C', 'G', 'T'};
    std::string str;
    for(int i = 0; i < 10; i++){
        str += DNA_CHAR[DNA & 3];
        DNA = DNA >> 2;
    }
    return str;
}

class Solution{
public:
    std::vector<std::string> findRepeatedDnaSequences(std::string s){
        std::vector<std::string> result;
        if(s.length() < 10){
            return result;
        }
        for(int i = 0; i < 1048576; i++){
            g_hash_map[i] = 0;
        }
        int char_map[128] = {0};
        char_map['A'] = 0;
        char_map['C'] = 1;
        char_map['G'] = 2;
        char_map['T'] = 3;
        int key = 0;
        for(int i = 9; i >= 0; i--){
            key = (key << 2) + char_map[s[i]];
        }
        g_hash_map[key] = 1;
        for(int i = 10; i < s.length(); i++){
            key = key >> 2;
            key = key | (char_map[s[i]] << 18);
            g_hash_map[key]++;
        }
        for(int i = 0; i < 1048576; i++){
            if(g_hash_map[i] > 1){
                result.push_back(change_int_to_DNA(i));
            }
        }
        return result;
    }
};

```

",1.0,"Leetcode_187_Repeated DNA Sequences - #### [Repeated DNA Sequences](https://leetcode-cn.com/problems/repeated-dna-sequences/)

All DNA is composed of a series of nucleotides abbreviated as A, C, G, and T, for example: ""ACGAATTCCG"". When studying DNA, it is sometimes useful to identify repeated sequences within the DNA.

Write a function to find all the 10-letter-long sequences (substrings) that occur more than once in a DNA molecule.

**Example:**

```
Input: s = ""AAAAACCCCCAAAAACCCCCCAAAAAGGGTTT""

Output: [""AAAAACCCCC"", ""CCCCCAAAAA""]
```

**题意：将DNA序列看成一个只包含`[A，B，C，D]`四个字符的字符串，给一个DNA字符串，找出所有长度为10的且出现次数超过一次的字符串。**

算法思路：

方法一：

1. 枚举DNA字符串中所有的长度为10的子串，将其插入到哈希Map中，并记录子串的数量；
2. 遍历哈希Map，将所有出现次数超过一次的子串存储到结果中

**算法复杂度为`O(n)`**

```c++
class Solution{
public:
    std::vector<std::string> findRepeatedDnaSequences(std::string s){
        std::map<std::string, int> word_map;
        std::vector<std::string> result;
        for(int i = 0; i < s.length(); i++){
            std::string word = s.substr(i, 10);
            if(word_map.find(word) != word_map.end()){
                word_map[word] += 1;
            }
            else{
                word_map[word] = 1;
            }
        }
        std::map<std::string, int> :: iterator it;
        for(it = word_map.begin(); it != word_map.end(); it++){
            if(it -> second > 1){
                result.push_back(it -> first);
            }
        }
        return result;
    }
};

```

方法二：

1. 设置全局变量哈希`int g_hash_map[1028576]` *1048576 = 2^20*，表示所有的长度为10的DNA序列；
2. 将DNA字符串的前十个字符使用左移运算转化为整数`key`，`g_hash_map[key]++`;
3. 从DNA的第11个字符开始，按顺序遍历各个字符，遇到一个字符即将`key`右移二位（去掉最低位），并将新的DNA字符`s[i]`转化为整数后，或到最后两位，`g_hash_map[key]++`;
4. 遍历哈希表`g_hash_map`，若`g_hash_map[i] > 1`，将`i`从低到高位转化为10个DNA序列，`push`到结果数组。

```c++
int g_hash_map[1048576] = {0};

std::string change_int_to_DNA(int DNA){
    static const char DNA_CHAR[] = {'A', 'C', 'G', 'T'};
    std::string str;
    for(int i = 0; i < 10; i++){
        str += DNA_CHAR[DNA & 3];
        DNA = DNA >> 2;
    }
    return str;
}

class Solution{
public:
    std::vector<std::string> findRepeatedDnaSequences(std::string s){
        std::vector<std::string> result;
        if(s.length() < 10){
            return result;
        }
        for(int i = 0; i < 1048576; i++){
            g_hash_map[i] = 0;
        }
        int char_map[128] = {0};
        char_map['A'] = 0;
        char_map['C'] = 1;
        char_map['G'] = 2;
        char_map['T'] = 3;
        int key = 0;
        for(int i = 9; i >= 0; i--){
            key = (key << 2) + char_map[s[i]];
        }
        g_hash_map[key] = 1;
        for(int i = 10; i < s.length(); i++){
            key = key >> 2;
            key = key | (char_map[s[i]] << 18);
            g_hash_map[key]++;
        }
        for(int i = 0; i < 1048576; i++){
            if(g_hash_map[i] > 1){
                result.push_back(change_int_to_DNA(i));
            }
        }
        return result;
    }
};

```

",0,leetcode   repeated dna sequences               all dna is composed of a series of nucleotides abbreviated as a  c  g  and t  for example   acgaattccg   when studying dna  it is sometimes useful to identify repeated sequences within the dna     write a function to find all the   letter long sequences  substrings  that occur more than once in a dna molecule       example            input  s    aaaaacccccaaaaaccccccaaaaagggttt     output              题意：将dna序列看成一个只包含   四个字符的字符串，给一个dna字符串， 。      算法思路：    方法一：        ，将其插入到哈希map中，并记录子串的数量；     遍历哈希map，将所有出现次数超过一次的子串存储到结果中      算法复杂度为 o n           c    class solution   public       std  vector  findrepeateddnasequences std  string s            std  map  word map           std  vector  result           for int i      i   s length    i                  std  string word   s substr i                   if word map find word     word map end                      word map                                    else                   word map                                          std  map     iterator it           for it   word map begin    it    word map end    it                  if it    second                        result push back it    first                                      return result                       方法二：       设置全局变量哈希 int g hash map            ， ；     将dna字符串的前十个字符使用左移运算转化为整数 key ， g hash map           ，按顺序遍历各个字符，遇到一个字符即将 key 右移二位（去掉最低位），并将新的dna字符 s  转化为整数后，或到最后两位， g hash map          遍历哈希表 g hash map ，若 g hash map      ，将 i  ， push 到结果数组。       c    int g hash map            std  string change int to dna int dna        static const char dna char      a    c    g    t         std  string str       for int i      i      i              str    dna char            dna   dna                   return str        class solution   public       std  vector  findrepeateddnasequences std  string s            std  vector  result           if s length                      return result                      for int i      i      i                  g hash map                           int char map                  char map                char map                char map                char map                int key               for int i      i       i                  key    key         char map                        g hash map                for int i      i   s length    i                  key   key                    key   key    char map                       g hash map                         for int i      i      i                  if g hash map                         result push back change int to dna i                                       return result                       ,0
12290,3594534024.0,IssuesEvent,2016-02-02 00:10:50,golang/go,https://api.github.com/repos/golang/go,closed,blog: /race-detector points to a dead link ,Documentation,`go get -race code.google.com/p/go.blog/support/racy` should be `go get -race golang.org/x/blog/support/racy`,1.0,blog: /race-detector points to a dead link  - `go get -race code.google.com/p/go.blog/support/racy` should be `go get -race golang.org/x/blog/support/racy`,1,blog   race detector points to a dead link     go get  race code google com p go blog support racy  should be  go get  race golang org x blog support racy ,1
165162,12831113700.0,IssuesEvent,2020-07-07 04:19:37,dotnet/efcore,https://api.github.com/repos/dotnet/efcore,closed,More TPT tests,area-query area-test closed-fixed,"Convert following test classes to use TPT in hierarchy as another flavor
- ManyToMany - Skip navs
- GearsOfWar - composite keys in hierarchy, query compositions, split queries
- FilterInheritance - Query filters

Also add split query tests to TPTRelationships for some coverage over TPT having owned collections.",1.0,"More TPT tests - Convert following test classes to use TPT in hierarchy as another flavor
- ManyToMany - Skip navs
- GearsOfWar - composite keys in hierarchy, query compositions, split queries
- FilterInheritance - Query filters

Also add split query tests to TPTRelationships for some coverage over TPT having owned collections.",0,more tpt tests   convert following test classes to use tpt in hierarchy as another flavor    manytomany   skip navs    gearsofwar   composite keys in hierarchy  query compositions  split queries    filterinheritance   query filters    also add split query tests to tptrelationships for some coverage over tpt having owned collections ,0
91956,15856786552.0,IssuesEvent,2021-04-08 03:11:02,blakenick77/laravel,https://api.github.com/repos/blakenick77/laravel,opened,CVE-2019-10742 (High) detected in axios-0.18.0.tgz,security vulnerability,"## CVE-2019-10742 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>axios-0.18.0.tgz</b></p></summary>

<p>Promise based HTTP client for the browser and node.js</p>
<p>Library home page: <a href=""https://registry.npmjs.org/axios/-/axios-0.18.0.tgz"">https://registry.npmjs.org/axios/-/axios-0.18.0.tgz</a></p>
<p>Path to dependency file: /laravel/package.json</p>
<p>Path to vulnerable library: laravel/node_modules/axios/package.json</p>
<p>

Dependency Hierarchy:
  - :x: **axios-0.18.0.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
Axios up to and including 0.18.0 allows attackers to cause a denial of service (application crash) by continuing to accepting content after maxContentLength is exceeded.

<p>Publish Date: 2019-05-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10742>CVE-2019-10742</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/axios/axios/issues/1098"">https://github.com/axios/axios/issues/1098</a></p>
<p>Release Date: 2019-05-31</p>
<p>Fix Resolution: 0.19.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-2019-10742 (High) detected in axios-0.18.0.tgz - ## CVE-2019-10742 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>axios-0.18.0.tgz</b></p></summary>

<p>Promise based HTTP client for the browser and node.js</p>
<p>Library home page: <a href=""https://registry.npmjs.org/axios/-/axios-0.18.0.tgz"">https://registry.npmjs.org/axios/-/axios-0.18.0.tgz</a></p>
<p>Path to dependency file: /laravel/package.json</p>
<p>Path to vulnerable library: laravel/node_modules/axios/package.json</p>
<p>

Dependency Hierarchy:
  - :x: **axios-0.18.0.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
Axios up to and including 0.18.0 allows attackers to cause a denial of service (application crash) by continuing to accepting content after maxContentLength is exceeded.

<p>Publish Date: 2019-05-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10742>CVE-2019-10742</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/axios/axios/issues/1098"">https://github.com/axios/axios/issues/1098</a></p>
<p>Release Date: 2019-05-31</p>
<p>Fix Resolution: 0.19.0</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in axios       tgz      cve       high severity vulnerability     vulnerable library    axios       tgz      promise based http client for the browser and node js   library home page   a href     path to dependency file   laravel package json   path to vulnerable library  laravel node modules axios package json     dependency hierarchy       x    axios       tgz    vulnerable library             vulnerability details         axios up to and including       allows attackers to cause a denial of service  application crash  by continuing to accepting content after maxcontentlength is exceeded    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                      step up your open source security game with whitesource    ,0
88811,3785729163.0,IssuesEvent,2016-03-20 18:05:56,play2-maven-plugin/play2-maven-plugin,https://api.github.com/repos/play2-maven-plugin/play2-maven-plugin,closed,Implement source position mappers,Component-Maven-Plugin Component-Source-Position-Mappers Priority-High Type-Enhancement,"SBT source position mappers support was implemented in SBT Compiler Maven Plugin [recently](https://github.com/sbt-compiler-maven-plugin/sbt-compiler-maven-plugin/issues/32).

Create Play!-specific source position mappers for:
- routes
- Twirl templates",1.0,"Implement source position mappers - SBT source position mappers support was implemented in SBT Compiler Maven Plugin [recently](https://github.com/sbt-compiler-maven-plugin/sbt-compiler-maven-plugin/issues/32).

Create Play!-specific source position mappers for:
- routes
- Twirl templates",0,implement source position mappers   sbt source position mappers support was implemented in sbt compiler maven plugin        create play  specific source position mappers for     routes    twirl templates,0
33098,6155926769.0,IssuesEvent,2017-06-28 15:39:18,golang/go,https://api.github.com/repos/golang/go,closed,Website documentation,Documentation WaitingForInfo,"Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
go version go1.8.3 windows/amd64

### What operating system and processor architecture are you using (`go env`)?
set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=Z:\GoPath
set GORACE=
set GOROOT=E:\Program Fles\Go
set GOTOOLDIR=E:\Program Fles\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0
set CXX=g++
set CGO_ENABLED=1
set PKG_CONFIG=pkg-config
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2

### What did you do?

Try to find documentation on website about:
""go:integrate""
""go:generate""
and etc...

### What did you expect to see?

Don`t foud one atricle or one part of documentation about all allowable features.

### What did you see instead?

Special part on page https://golang.org/doc/ with common and clear information about that annotations.

",1.0,"Website documentation - Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
go version go1.8.3 windows/amd64

### What operating system and processor architecture are you using (`go env`)?
set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=Z:\GoPath
set GORACE=
set GOROOT=E:\Program Fles\Go
set GOTOOLDIR=E:\Program Fles\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0
set CXX=g++
set CGO_ENABLED=1
set PKG_CONFIG=pkg-config
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2

### What did you do?

Try to find documentation on website about:
""go:integrate""
""go:generate""
and etc...

### What did you expect to see?

Don`t foud one atricle or one part of documentation about all allowable features.

### What did you see instead?

Special part on page https://golang.org/doc/ with common and clear information about that annotations.

",1,website documentation   please answer these questions before submitting your issue  thanks         what version of go are you using   go version     go version       windows          what operating system and processor architecture are you using   go env     set goarch    set gobin   set goexe  exe  set gohostarch    set gohostos windows  set goos windows  set gopath z  gopath  set gorace   set goroot e  program fles go  set gotooldir e  program fles go pkg tool windows    set gccgo gccgo  set cc gcc  set gogccflags     mthreads  fmessage length    set cxx g    set cgo enabled    set pkg config pkg config  set cgo cflags  g     set cgo cppflags   set cgo cxxflags  g     set cgo fflags  g     set cgo ldflags  g           what did you do     try to find documentation on website about    go integrate    go generate   and etc           what did you expect to see     don t foud one atricle or one part of documentation about all allowable features         what did you see instead     special part on page   with common and clear information about that annotations     ,1
361451,25340728902.0,IssuesEvent,2022-11-18 21:19:05,golang/go,https://api.github.com/repos/golang/go,closed,wiki: document gomote for first time users,Documentation help wanted NeedsFix,"Thanks for this. If there's one thing that could make the wiki significantly clearer it would be a paragraph about directory structure and the ""gomote machine model"". It took me a bunch of try-and-error runs to find out. Much of it may be ""obvious"" in retrospect, but it helps spelling it out right away, especially for first-time gomote users. This would provide newcomers a clearer model of how the gomote looks like from a client's perspective.

Some of the things that would be nice if they were spelled out:

- each instance of a gomote has its own working directory, accessible via `$WORKDIR`
- gomote push does essentially an `rsync` of the `$GOROOT` directory into the remote `$WORKDIR`; i.e., after a `gomote push`, the local `$GOROOT` appears as `go` directory on the gomote (I had to find this out by doing repeated `gomote ls` commands)
- when issuing `gomote run` commands, one needs to specify the full path for commands and files, e.g. `go/bin/go tool compile go/src/mypkg/x.go` - there appears no notion of a `cwd`, or perhaps I missed it
- to change individual uploaded files, make the changes locally and use `gomote push $MOTE` and it will only upload the changes (this was not obvious to me at first, especially because there's also a `gomote put` command to push single files. I thought I was supposed to use that one for smaller changes)
- I didn't figure out to how to use `gomote put` to get a file into a specific directory on the gomote instance (I still don't know how to do it, but I resorted to just using `gomote push` all the time.)
- explain that the gomote self-destructs after 30min of non-use
- I'm unclear on the `-system` flag

_Originally posted by @griesemer in https://github.com/golang/go/issues/31091#issuecomment-477718369_",1.0,"wiki: document gomote for first time users - Thanks for this. If there's one thing that could make the wiki significantly clearer it would be a paragraph about directory structure and the ""gomote machine model"". It took me a bunch of try-and-error runs to find out. Much of it may be ""obvious"" in retrospect, but it helps spelling it out right away, especially for first-time gomote users. This would provide newcomers a clearer model of how the gomote looks like from a client's perspective.

Some of the things that would be nice if they were spelled out:

- each instance of a gomote has its own working directory, accessible via `$WORKDIR`
- gomote push does essentially an `rsync` of the `$GOROOT` directory into the remote `$WORKDIR`; i.e., after a `gomote push`, the local `$GOROOT` appears as `go` directory on the gomote (I had to find this out by doing repeated `gomote ls` commands)
- when issuing `gomote run` commands, one needs to specify the full path for commands and files, e.g. `go/bin/go tool compile go/src/mypkg/x.go` - there appears no notion of a `cwd`, or perhaps I missed it
- to change individual uploaded files, make the changes locally and use `gomote push $MOTE` and it will only upload the changes (this was not obvious to me at first, especially because there's also a `gomote put` command to push single files. I thought I was supposed to use that one for smaller changes)
- I didn't figure out to how to use `gomote put` to get a file into a specific directory on the gomote instance (I still don't know how to do it, but I resorted to just using `gomote push` all the time.)
- explain that the gomote self-destructs after 30min of non-use
- I'm unclear on the `-system` flag

_Originally posted by @griesemer in https://github.com/golang/go/issues/31091#issuecomment-477718369_",1,wiki  document gomote for first time users   thanks for this  if there s one thing that could make the wiki significantly clearer it would be a paragraph about directory structure and the  gomote machine model   it took me a bunch of try and error runs to find out  much of it may be  obvious  in retrospect  but it helps spelling it out right away  especially for first time gomote users  this would provide newcomers a clearer model of how the gomote looks like from a client s perspective     some of the things that would be nice if they were spelled out       each instance of a gomote has its own working directory  accessible via   workdir     gomote push does essentially an  rsync  of the   goroot  directory into the remote   workdir   i e   after a  gomote push   the local   goroot  appears as  go  directory on the gomote  i had to find this out by doing repeated  gomote ls  commands     when issuing  gomote run  commands  one needs to specify the full path for commands and files  e g   go bin go tool compile go src mypkg x go    there appears no notion of a  cwd   or perhaps i missed it    to change individual uploaded files  make the changes locally and use  gomote push  mote  and it will only upload the changes  this was not obvious to me at first  especially because there s also a  gomote put  command to push single files  i thought i was supposed to use that one for smaller changes     i didn t figure out to how to use  gomote put  to get a file into a specific directory on the gomote instance  i still don t know how to do it  but i resorted to just using  gomote push  all the time      explain that the gomote self destructs after   of non use    i m unclear on the   system  flag     originally posted by  griesemer in  ,1
47125,7307953166.0,IssuesEvent,2018-02-28 05:55:56,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: go run: triggers Symantec malware alert.,Documentation,"### What version of Go are you using (`go version`)?

`go version go1.9.4 windows/amd64`

### Does this issue reproduce with the latest release?
Yes.

### What operating system and processor architecture are you using (`go env`)?
```
set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\Users\-snip-\go
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0
set CXX=g++
set CGO_ENABLED=1
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
```

### What did you do?
I ran the following program:

```
package main

import ""fmt""

func main() {
  fmt.Println(""1 + 1 ="", 1 + 1)
  fmt.Println(""1 + 1 ="", 1.0 + 1.0)
}
```

### What did you expect to see?
```
1 + 1 = 2
1 + 1 = 2
```

### What did you see instead?
```
exit status 3221225506
```
Symantec got triggered. https://www.symantec.com/security_response/writeup.jsp?docid=2017-032721-5748-99&vid=4294924267",1.0,"cmd/go: go run: triggers Symantec malware alert. - ### What version of Go are you using (`go version`)?

`go version go1.9.4 windows/amd64`

### Does this issue reproduce with the latest release?
Yes.

### What operating system and processor architecture are you using (`go env`)?
```
set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\Users\-snip-\go
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0
set CXX=g++
set CGO_ENABLED=1
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
```

### What did you do?
I ran the following program:

```
package main

import ""fmt""

func main() {
  fmt.Println(""1 + 1 ="", 1 + 1)
  fmt.Println(""1 + 1 ="", 1.0 + 1.0)
}
```

### What did you expect to see?
```
1 + 1 = 2
1 + 1 = 2
```

### What did you see instead?
```
exit status 3221225506
```
Symantec got triggered. https://www.symantec.com/security_response/writeup.jsp?docid=2017-032721-5748-99&vid=4294924267",1,cmd go  go run  triggers symantec malware alert        what version of go are you using   go version        go version       windows           does this issue reproduce with the latest release   yes         what operating system and processor architecture are you using   go env          set goarch    set gobin   set goexe  exe  set gohostarch    set gohostos windows  set goos windows  set gopath c  users  snip  go  set gorace   set goroot c  go  set gotooldir c  go pkg tool windows    set gccgo gccgo  set cc gcc  set gogccflags     mthreads  fmessage length    set cxx g    set cgo enabled    set cgo cflags  g     set cgo cppflags   set cgo cxxflags  g     set cgo fflags  g     set cgo ldflags  g     set pkg config pkg config             what did you do   i ran the following program          package main    import  fmt     func main        fmt println                      fmt println                                      what did you expect to see                                         what did you see instead        exit status         symantec got triggered   ,1
21885,4756979204.0,IssuesEvent,2016-10-24 15:23:17,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: improve documentation in go help packages,Documentation NeedsFix,"From `loadPackage` documentation:
`In addition to ordinary import paths,  loadPackage accepts pseudo-paths beginning with cmd/ to denote commands  in the Go command directory, as well as paths to those directories.`.

However this is not documented. `go help package` only says:
`""cmd"" expands to the Go repository's commands and their internal libraries.`.",1.0,"cmd/go: improve documentation in go help packages - From `loadPackage` documentation:
`In addition to ordinary import paths,  loadPackage accepts pseudo-paths beginning with cmd/ to denote commands  in the Go command directory, as well as paths to those directories.`.

However this is not documented. `go help package` only says:
`""cmd"" expands to the Go repository's commands and their internal libraries.`.",1,cmd go  improve documentation in go help packages   from  loadpackage  documentation    in addition to ordinary import paths   loadpackage accepts pseudo paths beginning with cmd  to denote commands  in the go command directory  as well as paths to those directories       however this is not documented   go help package  only says     cmd  expands to the go repository s commands and their internal libraries   ,1
3242,2752093801.0,IssuesEvent,2015-04-24 13:45:14,golang/go,https://api.github.com/repos/golang/go,closed,hash/crc32: clarify documentation,Documentation,"by **sheetjs**:

<pre>Documentation currently says:

&quot;MakeTable returns the Table constructed from the specified polynomial.&quot;

Somewhere in the doc, it should explicitly state that poly (the 32 bit integer) should
be based on the reversed representation.  It's implied by the constant &quot;IEEE =
0xedb88320&quot; (the normal representation for that case is 0x04c11db7), but making it
clear wouldn't hurt</pre>",1.0,"hash/crc32: clarify documentation - by **sheetjs**:

<pre>Documentation currently says:

&quot;MakeTable returns the Table constructed from the specified polynomial.&quot;

Somewhere in the doc, it should explicitly state that poly (the 32 bit integer) should
be based on the reversed representation.  It's implied by the constant &quot;IEEE =
0xedb88320&quot; (the normal representation for that case is 0x04c11db7), but making it
clear wouldn't hurt</pre>",1,hash    clarify documentation   by   sheetjs      documentation currently says    quot maketable returns the table constructed from the specified polynomial  quot   somewhere in the doc  it should explicitly state that poly  the   bit integer  should be based on the reversed representation   it s implied by the constant  quot ieee     quot   the normal representation for that case is     but making it clear wouldn t hurt ,1
373330,11042328401.0,IssuesEvent,2019-12-09 08:55:49,grpc/grpc,https://api.github.com/repos/grpc/grpc,opened,support to construct length-prefixed message at application layer,kind/enhancement priority/P2,"### Is your feature request related to a problem? Please describe.

Length-prefixed message is defined as
```
Length-Prefixed-Message → Compressed-Flag Message-Length Message
```

Currently it's constructed in grpc-core. However if we can construct it at application layer, grpc can be used in batch style: we can call `grpc_call_start_batch` to send many messages at once. Generally it helps to improve performance.

### Describe the solution you'd like

I want to add a new `WriteFlag`: `GRPC_WRITE_LENGTH_PREFIXED`.

With the flag, the `grpc_byte_buffer` passed in `grpc_call_start_batch` is encoded as repeated length-prefixed messages.

### Describe alternatives you've considered
We can also call `grpc_call_start_batch` many times with `buffer_hint=true`. But I think it still introduces more context switch because we need to fetch more tags back when calling `grpc_completion_queue_next`.

### Additional context
",1.0,"support to construct length-prefixed message at application layer - ### Is your feature request related to a problem? Please describe.

Length-prefixed message is defined as
```
Length-Prefixed-Message → Compressed-Flag Message-Length Message
```

Currently it's constructed in grpc-core. However if we can construct it at application layer, grpc can be used in batch style: we can call `grpc_call_start_batch` to send many messages at once. Generally it helps to improve performance.

### Describe the solution you'd like

I want to add a new `WriteFlag`: `GRPC_WRITE_LENGTH_PREFIXED`.

With the flag, the `grpc_byte_buffer` passed in `grpc_call_start_batch` is encoded as repeated length-prefixed messages.

### Describe alternatives you've considered
We can also call `grpc_call_start_batch` many times with `buffer_hint=true`. But I think it still introduces more context switch because we need to fetch more tags back when calling `grpc_completion_queue_next`.

### Additional context
",0,support to construct length prefixed message at application layer       is your feature request related to a problem  please describe     length prefixed message is defined as       length prefixed message → compressed flag message length message         currently it s constructed in grpc core  however if we can construct it at application layer  grpc can be used in batch style  we can call  grpc call start batch  to send many messages at once  generally it helps to improve performance         describe the solution you d like    i want to add a new  writeflag    grpc write length prefixed      with the flag  the  grpc byte buffer  passed in  grpc call start batch  is encoded as repeated length prefixed messages         describe alternatives you ve considered  we can also call  grpc call start batch  many times with  buffer hint true   but i think it still introduces more context switch because we need to fetch more tags back when calling  grpc completion queue next          additional context  ,0
24974,5115265922.0,IssuesEvent,2017-01-06 21:14:43,golang/go,https://api.github.com/repos/golang/go,closed,doc: define the first class ports,Documentation NeedsFix,"build.golang.org links to ""First Class Ports"":

https://github.com/golang/go/wiki/PortingPolicy

But that doesn't say which ports are the first class ones.

Further, the checkbox on https://build.golang.org to show only first class ports seems to only filter by GOOS, not (GOOS,GOARCH), so it shows things like linux-mips64le and linux-ppc64 as being first class, which I don't think is true. We don't even have linux-ppc64 big-endian builders at the moment.

Let's clarify.
",1.0,"doc: define the first class ports - build.golang.org links to ""First Class Ports"":

https://github.com/golang/go/wiki/PortingPolicy

But that doesn't say which ports are the first class ones.

Further, the checkbox on https://build.golang.org to show only first class ports seems to only filter by GOOS, not (GOOS,GOARCH), so it shows things like linux-mips64le and linux-ppc64 as being first class, which I don't think is true. We don't even have linux-ppc64 big-endian builders at the moment.

Let's clarify.
",1,doc  define the first class ports   build golang org links to  first class ports       but that doesn t say which ports are the first class ones   further  the checkbox on   to show only first class ports seems to only filter by goos  not  goos goarch   so it shows things like linux   and linux   as being first class  which i don t think is true  we don t even have linux   big endian builders at the moment   let s clarify  ,1
33407,6201046170.0,IssuesEvent,2017-07-06 04:04:43,golang/go,https://api.github.com/repos/golang/go,closed,spec: document the hint for make(map) better,Documentation Proposal Proposal-Accepted,"### What version of Go are you using (`go version`)?
go version devel +2e108a1be6 Tue Apr 4 11:55:55 2017 -0700 darwin/amd64

In https://go-review.googlesource.com/c/40113/ Rob Pike asked to add documentation about reflect.MakeMapWithSize.",1.0,"spec: document the hint for make(map) better - ### What version of Go are you using (`go version`)?
go version devel +2e108a1be6 Tue Apr 4 11:55:55 2017 -0700 darwin/amd64

In https://go-review.googlesource.com/c/40113/ Rob Pike asked to add documentation about reflect.MakeMapWithSize.",1,spec  document the hint for make map  better       what version of go are you using   go version     go version devel    tue apr              darwin      in   rob pike asked to add documentation about reflect makemapwithsize ,1
453951,13092429057.0,IssuesEvent,2020-08-03 08:34:55,MaibornWolff/codecharta,https://api.github.com/repos/MaibornWolff/codecharta,closed,"Change branch name from ""master"" to ""main""",difficulty:low priority:high tech,"Hi, 
    as a small contribution, maybe the naming could be changed.
    https://www.hanselman.com/blog/EasilyRenameYourGitDefaultBranchFromMasterToMain.aspx“

    ""git branch -m master main""
    ""git push -u origin main""",1.0,"Change branch name from ""master"" to ""main"" - Hi, 
    as a small contribution, maybe the naming could be changed.
    https://www.hanselman.com/blog/EasilyRenameYourGitDefaultBranchFromMasterToMain.aspx“

    ""git branch -m master main""
    ""git push -u origin main""",0,change branch name from  master  to  main    hi       as a small contribution  maybe the naming could be changed              git branch  m master main       git push  u origin main ,0
42105,6964010233.0,IssuesEvent,2017-12-08 19:46:32,golang/go,https://api.github.com/repos/golang/go,closed,"net: after call of {TCP,UDP,IP,Unix}Conn/{TCP,Unix}Listener.File(), the deadline will be ineffective",Documentation WaitingForInfo,"https://github.com/golang/go/blob/c2f8ed267b3fdfd06ca1a50aaf405886e52a8122/src/net/fd_unix.go#L316

in the under demo code:
the first goroutine, listener is not call (*net.TCPListener).File(), it timeout with setDeadline() works fine

the second goroutine, listener call (*net.TCPListener).File(), after that, the timeout don't work

the third goroutine, listener call (*net.TCPListener).File(), but then set it to non-blocking mode, timeout works fine too

```go
package main

import (
    ""fmt""
    ""net""
    ""sync""
    ""syscall""
    ""time""
)

func main() {
    wg := new(sync.WaitGroup)
    wg.Add(2)

    go func() {
        addr, _ := net.ResolveTCPAddr(""tcp"", "":2020"")
        l, _ := net.ListenTCP(""tcp"", addr)
        for {
            l.SetDeadline(time.Now().Add(time.Second))
            c, err := l.AcceptTCP()
            if err != nil {
                if nErr, ok := err.(net.Error); ok && nErr.Timeout() {
                    fmt.Printf(""server 1 timeout at: %s\n"", time.Now())
                    continue
                }   
                fmt.Printf(""server 1 error: %s\n"", err)
                break
            }   
            fmt.Printf(""server 1 accept from: %s %s\n"", c.RemoteAddr().String(), time.Now())
        }   
        wg.Done()
    }() 
    go func() {
        addr, _ := net.ResolveTCPAddr(""tcp"", "":2021"")
        l, _ := net.ListenTCP(""tcp"", addr)
        l.File()
        for {
            l.SetDeadline(time.Now().Add(time.Second))
            c, err := l.AcceptTCP()
            if err != nil {
                if nErr, ok := err.(net.Error); ok && nErr.Timeout() {
                    fmt.Printf(""server 2 timeout at: %s\n"", time.Now())
                    continue
                }   
                fmt.Printf(""server 2 error: %s\n"", err)
                break
            }   
            fmt.Printf(""server 2 accept from: %s %s\n"", c.RemoteAddr().String(), time.Now())
        }   
        wg.Done()
    }() 
    go func() {
        addr, _ := net.ResolveTCPAddr(""tcp"", "":2022"")
        l, _ := net.ListenTCP(""tcp"", addr)
        f, _ := l.File()
        syscall.SetNonblock(int(f.Fd()), true)
        for {
            l.SetDeadline(time.Now().Add(time.Second))
            c, err := l.AcceptTCP()
            if err != nil {
                if nErr, ok := err.(net.Error); ok && nErr.Timeout() {
                    fmt.Printf(""server 3 timeout at: %s\n"", time.Now())
                    continue
                }   
                fmt.Printf(""server 3 error: %s\n"", err)
                break
            }   
            fmt.Printf(""server 3 accept from: %s %s\n"", c.RemoteAddr().String(), time.Now())
        }   
        wg.Done()
    }() 

    wg.Wait()
}
```",1.0,"net: after call of {TCP,UDP,IP,Unix}Conn/{TCP,Unix}Listener.File(), the deadline will be ineffective - https://github.com/golang/go/blob/c2f8ed267b3fdfd06ca1a50aaf405886e52a8122/src/net/fd_unix.go#L316

in the under demo code:
the first goroutine, listener is not call (*net.TCPListener).File(), it timeout with setDeadline() works fine

the second goroutine, listener call (*net.TCPListener).File(), after that, the timeout don't work

the third goroutine, listener call (*net.TCPListener).File(), but then set it to non-blocking mode, timeout works fine too

```go
package main

import (
    ""fmt""
    ""net""
    ""sync""
    ""syscall""
    ""time""
)

func main() {
    wg := new(sync.WaitGroup)
    wg.Add(2)

    go func() {
        addr, _ := net.ResolveTCPAddr(""tcp"", "":2020"")
        l, _ := net.ListenTCP(""tcp"", addr)
        for {
            l.SetDeadline(time.Now().Add(time.Second))
            c, err := l.AcceptTCP()
            if err != nil {
                if nErr, ok := err.(net.Error); ok && nErr.Timeout() {
                    fmt.Printf(""server 1 timeout at: %s\n"", time.Now())
                    continue
                }   
                fmt.Printf(""server 1 error: %s\n"", err)
                break
            }   
            fmt.Printf(""server 1 accept from: %s %s\n"", c.RemoteAddr().String(), time.Now())
        }   
        wg.Done()
    }() 
    go func() {
        addr, _ := net.ResolveTCPAddr(""tcp"", "":2021"")
        l, _ := net.ListenTCP(""tcp"", addr)
        l.File()
        for {
            l.SetDeadline(time.Now().Add(time.Second))
            c, err := l.AcceptTCP()
            if err != nil {
                if nErr, ok := err.(net.Error); ok && nErr.Timeout() {
                    fmt.Printf(""server 2 timeout at: %s\n"", time.Now())
                    continue
                }   
                fmt.Printf(""server 2 error: %s\n"", err)
                break
            }   
            fmt.Printf(""server 2 accept from: %s %s\n"", c.RemoteAddr().String(), time.Now())
        }   
        wg.Done()
    }() 
    go func() {
        addr, _ := net.ResolveTCPAddr(""tcp"", "":2022"")
        l, _ := net.ListenTCP(""tcp"", addr)
        f, _ := l.File()
        syscall.SetNonblock(int(f.Fd()), true)
        for {
            l.SetDeadline(time.Now().Add(time.Second))
            c, err := l.AcceptTCP()
            if err != nil {
                if nErr, ok := err.(net.Error); ok && nErr.Timeout() {
                    fmt.Printf(""server 3 timeout at: %s\n"", time.Now())
                    continue
                }   
                fmt.Printf(""server 3 error: %s\n"", err)
                break
            }   
            fmt.Printf(""server 3 accept from: %s %s\n"", c.RemoteAddr().String(), time.Now())
        }   
        wg.Done()
    }() 

    wg.Wait()
}
```",1,net  after call of  tcp udp ip unix conn  tcp unix listener file    the deadline will be ineffective        in the under demo code   the first goroutine  listener is not call   net tcplistener  file    it timeout with setdeadline   works fine    the second goroutine  listener call   net tcplistener  file    after that  the timeout don t work    the third goroutine  listener call   net tcplistener  file    but then set it to non blocking mode  timeout works fine too       go  package main    import         fmt        net        sync        syscall        time        func main          wg    new sync waitgroup       wg add           go func              addr       net resolvetcpaddr  tcp                  l       net listentcp  tcp   addr           for                l setdeadline time now   add time second                c  err    l accepttcp                if err    nil                    if nerr  ok    err  net error   ok    nerr timeout                          fmt printf  server   timeout at   s n   time now                         continue                                        fmt printf  server   error   s n   err                   break                                fmt printf  server   accept from   s  s n   c remoteaddr   string    time now                           wg done                  go func              addr       net resolvetcpaddr  tcp                  l       net listentcp  tcp   addr           l file            for                l setdeadline time now   add time second                c  err    l accepttcp                if err    nil                    if nerr  ok    err  net error   ok    nerr timeout                          fmt printf  server   timeout at   s n   time now                         continue                                        fmt printf  server   error   s n   err                   break                                fmt printf  server   accept from   s  s n   c remoteaddr   string    time now                           wg done                  go func              addr       net resolvetcpaddr  tcp                  l       net listentcp  tcp   addr           f       l file            syscall setnonblock int f fd     true           for                l setdeadline time now   add time second                c  err    l accepttcp                if err    nil                    if nerr  ok    err  net error   ok    nerr timeout                          fmt printf  server   timeout at   s n   time now                         continue                                        fmt printf  server   error   s n   err                   break                                fmt printf  server   accept from   s  s n   c remoteaddr   string    time now                           wg done                    wg wait          ,1
426859,29667339532.0,IssuesEvent,2023-06-11 00:42:26,golang/go,https://api.github.com/repos/golang/go,closed,cmp: document ordering for floating point values in cmp.Ordered,Documentation NeedsFix,"Although the information is scattered about elsewhere, it would be good for the documentation for `cmp.Ordered` to explain how NaNs work. Then, the documentation for `builtin.min` and `builtin.max` should reference the documentation for `cmp.Ordered` directly (it does indirectly through the declaration).

",1.0,"cmp: document ordering for floating point values in cmp.Ordered - Although the information is scattered about elsewhere, it would be good for the documentation for `cmp.Ordered` to explain how NaNs work. Then, the documentation for `builtin.min` and `builtin.max` should reference the documentation for `cmp.Ordered` directly (it does indirectly through the declaration).

",1,cmp  document ordering for floating point values in cmp ordered   although the information is scattered about elsewhere  it would be good for the documentation for  cmp ordered  to explain how nans work  then  the documentation for  builtin min  and  builtin max  should reference the documentation for  cmp ordered  directly  it does indirectly through the declaration      ,1
31263,14918905463.0,IssuesEvent,2021-01-22 22:40:47,biocore/empress,https://api.github.com/repos/biocore/empress,closed,Speed up how node names are processed on initialization,performance,"Just making a record of this here so we don't forget it. (@kwcantrell and @ElDeveloper did all the work of finding this!!!)

Relates to the tree shown in [this twitter thread](https://twitter.com/yoshikivb/status/1336848912364175362). Basically, when there are a ton of node names, this block of code:

https://github.com/biocore/empress/blob/1b7a8d3a8da2c2a980ffc12f0f04ea6220d7e5e5/empress/support_files/js/empress.js#L463-L472

... slows things down a lot, because string comparisons are slow.

There are many possible ways we could handle this (better algorithms / data structures in JS, preprocessing stuff in Python, etc.) -- it's probably most important right now just to implement _something_ that fixes this, since this is a pretty significant bottleneck.",True,"Speed up how node names are processed on initialization - Just making a record of this here so we don't forget it. (@kwcantrell and @ElDeveloper did all the work of finding this!!!)

Relates to the tree shown in [this twitter thread](https://twitter.com/yoshikivb/status/1336848912364175362). Basically, when there are a ton of node names, this block of code:

https://github.com/biocore/empress/blob/1b7a8d3a8da2c2a980ffc12f0f04ea6220d7e5e5/empress/support_files/js/empress.js#L463-L472

... slows things down a lot, because string comparisons are slow.

There are many possible ways we could handle this (better algorithms / data structures in JS, preprocessing stuff in Python, etc.) -- it's probably most important right now just to implement _something_ that fixes this, since this is a pretty significant bottleneck.",0,speed up how node names are processed on initialization   just making a record of this here so we don t forget it    kwcantrell and  eldeveloper did all the work of finding this        relates to the tree shown in     basically  when there are a ton of node names  this block of code              slows things down a lot  because string comparisons are slow     there are many possible ways we could handle this  better algorithms   data structures in js  preprocessing stuff in python  etc      it s probably most important right now just to implement  something  that fixes this  since this is a pretty significant bottleneck ,0
52984,7801957352.0,IssuesEvent,2018-06-10 05:50:41,golang/go,https://api.github.com/repos/golang/go,closed,net/http/httptest: Explicitly discourage using ResponseRecorder.HeaderMap,Documentation,"(This is basically #16717 again.)

Quick background: if you write a header after the body has been written and status has been set in an HTTP handler, that's a bug because it has no effect. If you're testing using an httptest.ResponseRecorder, its HeaderMap will record the header and might make you think that your code is working when it's not. This is #8857. In response to that bug the behavior was changed to snapshot the headers instead, but that caused another problem (#15560) so it was reverted.

Instead, you're now supposed to use Result to get an http.Response and then look at resp.Header.

The documentation is not clear enough about this. I previously filed #16717 and 8e4ea2f5e8ee2b9c455adb329d96fb13cd3c64da added the following documentation to ResponseRecorder.HeaderMap:

```
// HeaderMap contains the headers explicitly set by the Handler.
//
// To get the implicit headers set by the server (such as
// automatic Content-Type), use the Result method.
HeaderMap http.Header
```

I think we need to be clearer and explicitly discourage looking at HeaderMap.

I've recently fixed a production bug where headers weren't being set and the tests specifically looked for them using HeaderMap. Then I found a whole bunch more places across many code bases where tests looked for headers to be set in HeaderMap. None of those would have caught headers written after Write.

/cc @bradfitz ",1.0,"net/http/httptest: Explicitly discourage using ResponseRecorder.HeaderMap - (This is basically #16717 again.)

Quick background: if you write a header after the body has been written and status has been set in an HTTP handler, that's a bug because it has no effect. If you're testing using an httptest.ResponseRecorder, its HeaderMap will record the header and might make you think that your code is working when it's not. This is #8857. In response to that bug the behavior was changed to snapshot the headers instead, but that caused another problem (#15560) so it was reverted.

Instead, you're now supposed to use Result to get an http.Response and then look at resp.Header.

The documentation is not clear enough about this. I previously filed #16717 and 8e4ea2f5e8ee2b9c455adb329d96fb13cd3c64da added the following documentation to ResponseRecorder.HeaderMap:

```
// HeaderMap contains the headers explicitly set by the Handler.
//
// To get the implicit headers set by the server (such as
// automatic Content-Type), use the Result method.
HeaderMap http.Header
```

I think we need to be clearer and explicitly discourage looking at HeaderMap.

I've recently fixed a production bug where headers weren't being set and the tests specifically looked for them using HeaderMap. Then I found a whole bunch more places across many code bases where tests looked for headers to be set in HeaderMap. None of those would have caught headers written after Write.

/cc @bradfitz ",1,net http httptest  explicitly discourage using responserecorder headermap    this is basically    again      quick background  if you write a header after the body has been written and status has been set in an http handler  that s a bug because it has no effect  if you re testing using an httptest responserecorder  its headermap will record the header and might make you think that your code is working when it s not  this is     in response to that bug the behavior was changed to snapshot the headers instead  but that caused another problem      so it was reverted     instead  you re now supposed to use result to get an http response and then look at resp header     the documentation is not clear enough about this  i previously filed    and   added the following documentation to responserecorder headermap             headermap contains the headers explicitly set by the handler          to get the implicit headers set by the server  such as     automatic content type   use the result method   headermap http header         i think we need to be clearer and explicitly discourage looking at headermap     i ve recently fixed a production bug where headers weren t being set and the tests specifically looked for them using headermap  then i found a whole bunch more places across many code bases where tests looked for headers to be set in headermap  none of those would have caught headers written after write      cc  bradfitz ,1
497083,14361755490.0,IssuesEvent,2020-11-30 18:45:00,grpc/grpc,https://api.github.com/repos/grpc/grpc,closed,Parameter to MergeFrom() must be instance of same class issue with grpc versions 1.26.0,kind/bug lang/Python priority/P2,"<!--
PLEASE DO NOT POST A QUESTION HERE.
This form is for bug reports and feature requests ONLY!

For general questions and troubleshooting, please ask/look for answers at StackOverflow, with ""grpc"" tag: https://stackoverflow.com/questions/tagged/grpc

For questions that specifically need to be answered by gRPC team members, please ask/look for answers at grpc.io mailing list: https://groups.google.com/forum/#!forum/grpc-io

Issues specific to *grpc-java*, *grpc-go*, *grpc-node*, *grpc-dart*, *grpc-web* should be created in the repository they belong to (e.g. https://github.com/grpc/grpc-LANGUAGE/issues/new)
-->

### What version of gRPC and what language are you using?

Python 3.8.6, grpc 1.33.2, tried on any grpc version 1.26.0+; protobuf 3.13
### What operating system (Linux, Windows,...) and version?

### What runtime / compiler are you using (e.g. python version or version of gcc)
Python 3.8.6

### What did you do?


I generated a pb file, compiled in python 3.8.6, called 'resource_pb2' that is used in a unit test. This pb file has a class called RecognitionResource that is called in the test. 

### What did you expect to see?
The test pass.
### What did you see instead?
Starting gRPC bi-directional streaming session
Parameter to MergeFrom() must be instance of same class: expected RecognitionResource got RecognitionResource.



### Anything else we should know about your project / environment?
I printed out all the Recognition resource class types that are called in that test, I do not see any difference in the classes or ids:
<class 'resource_pb2.RecognitionResource'> 2069160783760
<class 'resource_pb2.RecognitionResource'> 2069160783760
<class 'resource_pb2.RecognitionResource'> 2069160783760
",1.0,"Parameter to MergeFrom() must be instance of same class issue with grpc versions 1.26.0 - <!--
PLEASE DO NOT POST A QUESTION HERE.
This form is for bug reports and feature requests ONLY!

For general questions and troubleshooting, please ask/look for answers at StackOverflow, with ""grpc"" tag: https://stackoverflow.com/questions/tagged/grpc

For questions that specifically need to be answered by gRPC team members, please ask/look for answers at grpc.io mailing list: https://groups.google.com/forum/#!forum/grpc-io

Issues specific to *grpc-java*, *grpc-go*, *grpc-node*, *grpc-dart*, *grpc-web* should be created in the repository they belong to (e.g. https://github.com/grpc/grpc-LANGUAGE/issues/new)
-->

### What version of gRPC and what language are you using?

Python 3.8.6, grpc 1.33.2, tried on any grpc version 1.26.0+; protobuf 3.13
### What operating system (Linux, Windows,...) and version?

### What runtime / compiler are you using (e.g. python version or version of gcc)
Python 3.8.6

### What did you do?


I generated a pb file, compiled in python 3.8.6, called 'resource_pb2' that is used in a unit test. This pb file has a class called RecognitionResource that is called in the test. 

### What did you expect to see?
The test pass.
### What did you see instead?
Starting gRPC bi-directional streaming session
Parameter to MergeFrom() must be instance of same class: expected RecognitionResource got RecognitionResource.



### Anything else we should know about your project / environment?
I printed out all the Recognition resource class types that are called in that test, I do not see any difference in the classes or ids:
<class 'resource_pb2.RecognitionResource'> 2069160783760
<class 'resource_pb2.RecognitionResource'> 2069160783760
<class 'resource_pb2.RecognitionResource'> 2069160783760
",0,parameter to mergefrom   must be instance of same class issue with grpc versions               please do not post a question here   this form is for bug reports and feature requests only     for general questions and troubleshooting  please ask look for answers at stackoverflow  with  grpc  tag       for questions that specifically need to be answered by grpc team members  please ask look for answers at grpc io mailing list       issues specific to  grpc java    grpc go    grpc node    grpc dart    grpc web  should be created in the repository they belong to  e g                what version of grpc and what language are you using     python        grpc        tried on any grpc version         protobuf          what operating system  linux  windows      and version         what runtime   compiler are you using  e g  python version or version of gcc   python              what did you do       i generated a pb file  compiled in python        called  resource    that is used in a unit test  this pb file has a class called recognitionresource that is called in the test          what did you expect to see   the test pass       what did you see instead   starting grpc bi directional streaming session  parameter to mergefrom   must be instance of same class  expected recognitionresource got recognitionresource             anything else we should know about your project   environment   i printed out all the recognition resource class types that are called in that test  i do not see any difference in the classes or ids                  ,0
156450,5969557362.0,IssuesEvent,2017-05-30 20:34:30,shipharbor/merry,https://api.github.com/repos/shipharbor/merry,closed,use json-schema to validate querystrings,Priority: Medium Status: Available Type: Enhancement,`merry.parse.json` and then run against a querystring. BOOM! :D ,1.0,use json-schema to validate querystrings - `merry.parse.json` and then run against a querystring. BOOM! :D ,0,use json schema to validate querystrings    merry parse json  and then run against a querystring  boom   d ,0
59022,8319427373.0,IssuesEvent,2018-09-25 17:11:45,golang/go,https://api.github.com/repos/golang/go,closed,os/user: godoc for Current does not mention caching,Documentation NeedsFix Suggested,"### What version of Go are you using (`go version`)?
go version go1.10.1 linux/amd64

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?
```
11:55 AM $ go env
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/dave/.cache/go-build""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/dave/go""
GORACE=""""
GOROOT=""/usr/lib/go-1.10""
GOTMPDIR=""""
GOTOOLDIR=""/usr/lib/go-1.10/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build611611681=/tmp/go-build -gno-record-gcc-switches""
```

### What did you do?

godoc for user/os has 
```
func Current() (*User, error)
    Current returns the current user.
```
There is no mention that caching is used... so if I run code looking at user.Current() around a uid change I see unexpected results:

```
11:53 AM $ cat main.go 
package main

import ""runtime""
import ""syscall""
import ""os""
import ""os/user""
import ""log""
import ""fmt""

func main() {

	runtime.LockOSThread()

	u, _ := user.Current()
	fmt.Printf(""user.Current before priv drop: %v\n"", u.Name)

	if os.Getuid() == 0 {
		if err := syscall.Setresuid(1000, 1000, 0); err != nil {
			log.Fatalf(""failed to set user identity: %v"", err)
		}

		u, _ = user.Current()
		fmt.Printf(""user.Current after priv drop: %v\n"", u.Name)

	}
}
dave@piran:~/currentuser_test.go
11:53 AM $ sudo go run main.go 
user.Current before priv drop: root
user.Current after priv drop: root
```

### What did you expect to see?

godoc for user os mentions caching, e.g.
```
func Current() (*User, error)
    Current returns the current user.
    Note - the current user is cached at first call to Current().
    Subsequent calls will return the cached value and will not reflect changes
    to the EUID.
```


",1.0,"os/user: godoc for Current does not mention caching - ### What version of Go are you using (`go version`)?
go version go1.10.1 linux/amd64

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?
```
11:55 AM $ go env
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/dave/.cache/go-build""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/dave/go""
GORACE=""""
GOROOT=""/usr/lib/go-1.10""
GOTMPDIR=""""
GOTOOLDIR=""/usr/lib/go-1.10/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build611611681=/tmp/go-build -gno-record-gcc-switches""
```

### What did you do?

godoc for user/os has 
```
func Current() (*User, error)
    Current returns the current user.
```
There is no mention that caching is used... so if I run code looking at user.Current() around a uid change I see unexpected results:

```
11:53 AM $ cat main.go 
package main

import ""runtime""
import ""syscall""
import ""os""
import ""os/user""
import ""log""
import ""fmt""

func main() {

	runtime.LockOSThread()

	u, _ := user.Current()
	fmt.Printf(""user.Current before priv drop: %v\n"", u.Name)

	if os.Getuid() == 0 {
		if err := syscall.Setresuid(1000, 1000, 0); err != nil {
			log.Fatalf(""failed to set user identity: %v"", err)
		}

		u, _ = user.Current()
		fmt.Printf(""user.Current after priv drop: %v\n"", u.Name)

	}
}
dave@piran:~/currentuser_test.go
11:53 AM $ sudo go run main.go 
user.Current before priv drop: root
user.Current after priv drop: root
```

### What did you expect to see?

godoc for user os mentions caching, e.g.
```
func Current() (*User, error)
    Current returns the current user.
    Note - the current user is cached at first call to Current().
    Subsequent calls will return the cached value and will not reflect changes
    to the EUID.
```


",1,os user  godoc for current does not mention caching       what version of go are you using   go version     go version       linux          does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env              am   go env  goarch      gobin     gocache   home dave  cache go build   goexe     gohostarch      gohostos  linux   goos  linux   gopath   home dave go   gorace     goroot   usr lib go       gotmpdir     gotooldir   usr lib go     pkg tool linux     gccgo  gccgo   cc  gcc   cxx  g     cgo enabled      cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches              what did you do     godoc for user os has        func current     user  error       current returns the current user        there is no mention that caching is used    so if i run code looking at user current   around a uid change i see unexpected results              am   cat main go   package main    import  runtime   import  syscall   import  os   import  os user   import  log   import  fmt     func main        	runtime lockosthread      	u       user current    	fmt printf  user current before priv drop   v n   u name     	if os getuid           		if err    syscall setresuid           err    nil    			log fatalf  failed to set user identity   v   err   		     		u      user current    		fmt printf  user current after priv drop   v n   u name     	      dave piran   currentuser test go      am   sudo go run main go   user current before priv drop  root  user current after priv drop  root             what did you expect to see     godoc for user os mentions caching  e g        func current     user  error       current returns the current user       note   the current user is cached at first call to current         subsequent calls will return the cached value and will not reflect changes      to the euid            ,1
82426,10281365154.0,IssuesEvent,2019-08-26 08:19:52,golang/go,https://api.github.com/repos/golang/go,closed,x/website: Documents misaligned in menu for release notes,Documentation,"The **Documents** menu option is misaligned in the Go release notes.

<img width=""699"" alt=""Go 1.12 Release Notes"" src=""https://user-images.githubusercontent.com/565124/63676000-5989f980-c7ea-11e9-9b04-aec798cc9386.png"">

The alignment is correct on other documentation pages.

<img width=""711"" alt=""Go Documentation"" src=""https://user-images.githubusercontent.com/565124/63676213-bab1cd00-c7ea-11e9-9d3a-0badfc0b9699.png"">


### What did you do?

Go to the release notes for Go, for example [go1.11](https://golang.org/doc/go1.11), [go1.12](https://golang.org/doc/go1.12) or [go1.13 (tip)](https://tip.golang.org/doc/go1.13)

### What did you expect to see?

**Documents** aligned with the other menu options.

### What did you see instead?

**Documents** being positioned higher up than the rest of the menu options.

### Browsers tested

The following browsers were tested under macOS High Sierra.

 - Firefox Developer Edition
 - Safari
 - Google Chrome",1.0,"x/website: Documents misaligned in menu for release notes - The **Documents** menu option is misaligned in the Go release notes.

<img width=""699"" alt=""Go 1.12 Release Notes"" src=""https://user-images.githubusercontent.com/565124/63676000-5989f980-c7ea-11e9-9b04-aec798cc9386.png"">

The alignment is correct on other documentation pages.

<img width=""711"" alt=""Go Documentation"" src=""https://user-images.githubusercontent.com/565124/63676213-bab1cd00-c7ea-11e9-9d3a-0badfc0b9699.png"">


### What did you do?

Go to the release notes for Go, for example [go1.11](https://golang.org/doc/go1.11), [go1.12](https://golang.org/doc/go1.12) or [go1.13 (tip)](https://tip.golang.org/doc/go1.13)

### What did you expect to see?

**Documents** aligned with the other menu options.

### What did you see instead?

**Documents** being positioned higher up than the rest of the menu options.

### Browsers tested

The following browsers were tested under macOS High Sierra.

 - Firefox Developer Edition
 - Safari
 - Google Chrome",1,x website  documents misaligned in menu for release notes   the   documents   menu option is misaligned in the go release notes      img width     alt  go     release notes  src       the alignment is correct on other documentation pages      img width     alt  go documentation  src             what did you do     go to the release notes for go  for example         or            what did you expect to see       documents   aligned with the other menu options         what did you see instead       documents   being positioned higher up than the rest of the menu options         browsers tested    the following browsers were tested under macos high sierra        firefox developer edition     safari     google chrome,1
41043,5330890976.0,IssuesEvent,2017-02-15 18:07:58,elastic/logstash,https://api.github.com/repos/elastic/logstash,closed,Smoke Test PQ for multiple instance on the same box need to be adjusted for PQ.,bug tests,"Created from this comment: https://github.com/elastic/logstash/pull/6691#issuecomment-279678775
```
Failures:

  1) Test Logstash instance multiple of them can be started on the same box with automatically trying different ports for HTTP server
     Failure/Error: expect(is_port_open?(9601)).to be true

       expected true
            got false
     # ./specs/01_logstash_bin_smoke_spec.rb:52:in `(root)'
     # /home/travis/.rvm/gems/jruby-1.7.25/gems/stud-0.0.22/lib/stud/try.rb:79:in `try'
     # /home/travis/.rvm/gems/jruby-1.7.25/gems/stud-0.0.22/lib/stud/try.rb:95:in `try'
     # /home/travis/.rvm/gems/jruby-1.7.25/gems/stud-0.0.22/lib/stud/try.rb:91:in `try'
     # /home/travis/.rvm/gems/jruby-1.7.25/gems/stud-0.0.22/lib/stud/try.rb:123:in `try'
     # /home/travis/.rvm/gems/jruby-1.7.25/gems/logstash-devutils-1.3.1-java/lib/logstash/devutils/rspec/logstash_helpers.rb:18:in `try'
     # ./specs/01_logstash_bin_smoke_spec.rb:51:in `(root)'
     # /home/travis/.rvm/gems/jruby-1.7.25/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `(root)'

Finished in 14 minutes 27 seconds (files took 8.68 seconds to load)
32 examples, 1 failure

Failed examples:

rspec ./specs/01_logstash_bin_smoke_spec.rb:41 # Test Logstash instance multiple of them can be started on the same box with automatically trying different ports for HTTP server

Randomized with seed 
```

The test are failling we try to started 2 logstash instance with the same pipeline_id and with the same path for PQ.",1.0,"Smoke Test PQ for multiple instance on the same box need to be adjusted for PQ. - Created from this comment: https://github.com/elastic/logstash/pull/6691#issuecomment-279678775
```
Failures:

  1) Test Logstash instance multiple of them can be started on the same box with automatically trying different ports for HTTP server
     Failure/Error: expect(is_port_open?(9601)).to be true

       expected true
            got false
     # ./specs/01_logstash_bin_smoke_spec.rb:52:in `(root)'
     # /home/travis/.rvm/gems/jruby-1.7.25/gems/stud-0.0.22/lib/stud/try.rb:79:in `try'
     # /home/travis/.rvm/gems/jruby-1.7.25/gems/stud-0.0.22/lib/stud/try.rb:95:in `try'
     # /home/travis/.rvm/gems/jruby-1.7.25/gems/stud-0.0.22/lib/stud/try.rb:91:in `try'
     # /home/travis/.rvm/gems/jruby-1.7.25/gems/stud-0.0.22/lib/stud/try.rb:123:in `try'
     # /home/travis/.rvm/gems/jruby-1.7.25/gems/logstash-devutils-1.3.1-java/lib/logstash/devutils/rspec/logstash_helpers.rb:18:in `try'
     # ./specs/01_logstash_bin_smoke_spec.rb:51:in `(root)'
     # /home/travis/.rvm/gems/jruby-1.7.25/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `(root)'

Finished in 14 minutes 27 seconds (files took 8.68 seconds to load)
32 examples, 1 failure

Failed examples:

rspec ./specs/01_logstash_bin_smoke_spec.rb:41 # Test Logstash instance multiple of them can be started on the same box with automatically trying different ports for HTTP server

Randomized with seed 
```

The test are failling we try to started 2 logstash instance with the same pipeline_id and with the same path for PQ.",0,smoke test pq for multiple instance on the same box need to be adjusted for pq    created from this comment          failures          test logstash instance multiple of them can be started on the same box with automatically trying different ports for http server       failure error  expect is port open      to be true           expected true              got false           specs   logstash bin smoke spec rb   in   root            home travis  rvm gems jruby       gems stud       lib stud try rb   in  try           home travis  rvm gems jruby       gems stud       lib stud try rb   in  try           home travis  rvm gems jruby       gems stud       lib stud try rb   in  try           home travis  rvm gems jruby       gems stud       lib stud try rb   in  try           home travis  rvm gems jruby       gems logstash devutils       java lib logstash devutils rspec logstash helpers rb   in  try            specs   logstash bin smoke spec rb   in   root            home travis  rvm gems jruby       gems rspec wait       lib rspec wait rb   in   root      finished in   minutes   seconds  files took     seconds to load     examples    failure    failed examples     rspec   specs   logstash bin smoke spec rb     test logstash instance multiple of them can be started on the same box with automatically trying different ports for http server    randomized with seed          the test are failling we try to started   logstash instance with the same pipeline id and with the same path for pq ,0
105766,11457742941.0,IssuesEvent,2020-02-07 00:46:46,golang/go,https://api.github.com/repos/golang/go,opened,wiki: Go-Release-Cycle has an out of date statement on backporting policy,Documentation NeedsDecision,"There is a statement in the [Release Maintenance](https://golang.org/wiki/Go-Release-Cycle#release-maintenance) section of the Go Release Cycle wiki page that is out of date:

> Minor releases to address non-security problems for Go 1.x stop once Go 1.x+1 is released.

I plan to edit the page to make it say:

> Minor releases to address non-security problems for Go 1.x stop once Go 1.x+2 is released.

This is because we've accepted a backport policy clarification in proposal #34536, where the last two releases are supported equally.

(Filing this issue before making the change, as documented in the first paragraph of that wiki page.)

/cc @rsc @andybons @cagedmantis @toothrot",1.0,"wiki: Go-Release-Cycle has an out of date statement on backporting policy - There is a statement in the [Release Maintenance](https://golang.org/wiki/Go-Release-Cycle#release-maintenance) section of the Go Release Cycle wiki page that is out of date:

> Minor releases to address non-security problems for Go 1.x stop once Go 1.x+1 is released.

I plan to edit the page to make it say:

> Minor releases to address non-security problems for Go 1.x stop once Go 1.x+2 is released.

This is because we've accepted a backport policy clarification in proposal #34536, where the last two releases are supported equally.

(Filing this issue before making the change, as documented in the first paragraph of that wiki page.)

/cc @rsc @andybons @cagedmantis @toothrot",1,wiki  go release cycle has an out of date statement on backporting policy   there is a statement in the     section of the go release cycle wiki page that is out of date       minor releases to address non security problems for go   x stop once go   x   is released     i plan to edit the page to make it say       minor releases to address non security problems for go   x stop once go   x   is released     this is because we ve accepted a backport policy clarification in proposal     where the last two releases are supported equally      filing this issue before making the change  as documented in the first paragraph of that wiki page       cc  rsc  andybons  cagedmantis  toothrot,1
56043,8047514722.0,IssuesEvent,2018-08-01 01:10:31,golang/go,https://api.github.com/repos/golang/go,closed,strconv: FormatFloat handles prec differently from the doc with fmt='g',Documentation NeedsFix help wanted,"### What version of Go are you using (`go version`)?
go version go1.10.1 linux/amd64

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
GOARCH=""amd64""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""

### What did you do?
`fmt.Println(strconv.FormatFloat(1.5, 'g', 6, 64))`
https://play.golang.org/p/WRHc89mjuSG

### What did you expect to see?
`1.50000`

https://golang.org/pkg/strconv/#FormatFloat says:
> The precision prec controls the number of digits […]. For 'g' and 'G' it is the total number of digits.

I gave `prec=6`, so the total number of digits should be 6.

### What did you see instead?
`1.5`

The total number of digits is 2.",1.0,"strconv: FormatFloat handles prec differently from the doc with fmt='g' - ### What version of Go are you using (`go version`)?
go version go1.10.1 linux/amd64

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
GOARCH=""amd64""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""

### What did you do?
`fmt.Println(strconv.FormatFloat(1.5, 'g', 6, 64))`
https://play.golang.org/p/WRHc89mjuSG

### What did you expect to see?
`1.50000`

https://golang.org/pkg/strconv/#FormatFloat says:
> The precision prec controls the number of digits […]. For 'g' and 'G' it is the total number of digits.

I gave `prec=6`, so the total number of digits should be 6.

### What did you see instead?
`1.5`

The total number of digits is 2.",1,strconv  formatfloat handles prec differently from the doc with fmt  g        what version of go are you using   go version     go version       linux          does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env     goarch      gohostarch      gohostos  linux   goos  linux         what did you do    fmt println strconv formatfloat       g                     what did you expect to see              says     the precision prec controls the number of digits    for  g  and  g  it is the total number of digits     i gave  prec     so the total number of digits should be           what did you see instead            the total number of digits is   ,1
305083,9359132876.0,IssuesEvent,2019-04-02 05:43:32,CS2103-AY1819S2-W10-3/main,https://api.github.com/repos/CS2103-AY1819S2-W10-3/main,closed,edit SortCommand to sort by date ,priority.Medium status.Ongoing type.Enhancement type.Task v1.3,"To be able to sort the list according to the day, month and year ",1.0,"edit SortCommand to sort by date  - To be able to sort the list according to the day, month and year ",0,edit sortcommand to sort by date    to be able to sort the list according to the day  month and year ,0
188040,15114472669.0,IssuesEvent,2021-02-09 02:00:41,golang/go,https://api.github.com/repos/golang/go,closed,runtime/metrics: typos in documentation,Documentation NeedsFix,"There are some typos in the documentation of the new ""runtime/metrics"" package

* `encouranged` should be `encouraged`
* `""kind.""` should be `""kind"".`
* `the a tag` should be `the tag`",1.0,"runtime/metrics: typos in documentation - There are some typos in the documentation of the new ""runtime/metrics"" package

* `encouranged` should be `encouraged`
* `""kind.""` should be `""kind"".`
* `the a tag` should be `the tag`",1,runtime metrics  typos in documentation   there are some typos in the documentation of the new  runtime metrics  package       encouranged  should be  encouraged       kind    should be   kind        the a tag  should be  the tag ,1
173275,14406753584.0,IssuesEvent,2020-12-03 20:43:06,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.16: document runtime changes for Go 1.16,Documentation NeedsInvestigation release-blocker,"As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

<h2 id=""runtime"">Runtime</h2>

<p>
  <strong>TODO</strong>
</p>

<p><!-- CL 267100 -->
  On Linux, the runtime now defaults to releasing memory to the
  operating system promptly (using <code>MADV_DONTNEED</code>), rather
  than lazily when the operating system is under memory pressure
  (using <code>MADV_FREE</code>). This means process-level memory
  statistics like RSS will more accurately reflect the amount of
  physical memory being used by Go processes. Systems that are
  currently using <code>GODEBUG=madvdontneed=1</code> to improve
  memory monitoring behavior no longer need to set this environment
  variable.
</p>

[...]

<dl id=""runtime""><dt><a href=""/pkg/runtime/"">runtime</a></dt>
  <dd>
    <p><!-- CL 37222 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/37222"">https://golang.org/cl/37222</a>: make stack traces of endless recursion print only top and bottom 50
    </p>
    <p><!-- CL 242258 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/242258"">https://golang.org/cl/242258</a>: add 24 byte allocation size class
    </p>
    <p><!-- CL 254659 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/254659"">https://golang.org/cl/254659</a>: implement GODEBUG=inittrace=1 support
    </p>
  </dd>
</dl><!-- runtime -->

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.
",1.0,"doc/go1.16: document runtime changes for Go 1.16 - As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

<h2 id=""runtime"">Runtime</h2>

<p>
  <strong>TODO</strong>
</p>

<p><!-- CL 267100 -->
  On Linux, the runtime now defaults to releasing memory to the
  operating system promptly (using <code>MADV_DONTNEED</code>), rather
  than lazily when the operating system is under memory pressure
  (using <code>MADV_FREE</code>). This means process-level memory
  statistics like RSS will more accurately reflect the amount of
  physical memory being used by Go processes. Systems that are
  currently using <code>GODEBUG=madvdontneed=1</code> to improve
  memory monitoring behavior no longer need to set this environment
  variable.
</p>

[...]

<dl id=""runtime""><dt><a href=""/pkg/runtime/"">runtime</a></dt>
  <dd>
    <p><!-- CL 37222 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/37222"">https://golang.org/cl/37222</a>: make stack traces of endless recursion print only top and bottom 50
    </p>
    <p><!-- CL 242258 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/242258"">https://golang.org/cl/242258</a>: add 24 byte allocation size class
    </p>
    <p><!-- CL 254659 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/254659"">https://golang.org/cl/254659</a>: implement GODEBUG=inittrace=1 support
    </p>
  </dd>
</dl><!-- runtime -->

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.
",1,doc      document runtime changes for go       as of filing this issue  the     contained the following html      runtime           todo              on linux  the runtime now defaults to releasing memory to the    operating system promptly  using  madv dontneed    rather    than lazily when the operating system is under memory pressure     using  madv free    this means process level memory    statistics like rss will more accurately reflect the amount of    physical memory being used by go processes  systems that are    currently using  godebug madvdontneed    to improve    memory monitoring behavior no longer need to set this environment    variable                runtime                        todo    a href    make stack traces of endless recursion print only top and bottom                          todo    a href    add   byte allocation size class                        todo    a href    implement godebug inittrace   support                           per     it s a release blocker for go     beta   to have a complete draft of the eventual release notes  and so the todo needs to be resolved     a sequence of steps to resolve this issue may be        come up with a draft release note entry in this issue  then move the issue to needsfix state      send a cl with  doc           and include  for     fixes   this issue    in the body   ,1
94358,8486038573.0,IssuesEvent,2018-10-26 09:38:34,edenlabllc/ehealth.api,https://api.github.com/repos/edenlabllc/ehealth.api,closed,Reaction on immunization,kind/task priority/high priority/medium project/medical_events status/test,"As a Doctor I need to have an opportunity to link the reaction on immunization with the corresponding immunization so that users can see (and consider) the reaction while studying the immunization 
Implement logic according to spec

1) Add ""reaction_on""  field to the observation in the composite, validate it is an active immunization that belongs to the current patient

2) On postprocessing composite: add the observation to the immunization as a reaction [Spec](https://edenlab.atlassian.net/wiki/spaces/EH/pages/608272488/Submit+Encounter+Data+Package)",1.0,"Reaction on immunization - As a Doctor I need to have an opportunity to link the reaction on immunization with the corresponding immunization so that users can see (and consider) the reaction while studying the immunization 
Implement logic according to spec

1) Add ""reaction_on""  field to the observation in the composite, validate it is an active immunization that belongs to the current patient

2) On postprocessing composite: add the observation to the immunization as a reaction [Spec](https://edenlab.atlassian.net/wiki/spaces/EH/pages/608272488/Submit+Encounter+Data+Package)",0,reaction on immunization   as a doctor i need to have an opportunity to link the reaction on immunization with the corresponding immunization so that users can see  and consider  the reaction while studying the immunization  implement logic according to spec     add  reaction on   field to the observation in the composite  validate it is an active immunization that belongs to the current patient     on postprocessing composite  add the observation to the immunization as a reaction    ,0
153472,19706446106.0,IssuesEvent,2022-01-12 22:41:24,KaterinaOrg/maven-modular,https://api.github.com/repos/KaterinaOrg/maven-modular,opened,CVE-2018-14719 (High) detected in jackson-databind-2.9.6.jar,security vulnerability,"## CVE-2018-14719 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.6.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: /module2/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.6/jackson-databind-2.9.6.jar</p>
<p>

Dependency Hierarchy:
  - jackson-module-kotlin-2.9.6.jar (Root Library)
    - :x: **jackson-databind-2.9.6.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/KaterinaOrg/maven-modular/commit/27eea04c852891f5a7663c22ad865308b8149942"">27eea04c852891f5a7663c22ad865308b8149942</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>  
  
FasterXML jackson-databind 2.x before 2.9.7 might allow remote attackers to execute arbitrary code by leveraging failure to block the blaze-ds-opt and blaze-ds-core classes from polymorphic deserialization.

<p>Publish Date: 2019-01-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14719>CVE-2018-14719</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://nvd.nist.gov/vuln/detail/CVE-2018-14719"">https://nvd.nist.gov/vuln/detail/CVE-2018-14719</a></p>
<p>Release Date: 2019-01-02</p>
<p>Fix Resolution: 2.9.7</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.6"",""packageFilePaths"":[""/module2/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""com.fasterxml.jackson.module:jackson-module-kotlin:2.9.6;com.fasterxml.jackson.core:jackson-databind:2.9.6"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""2.9.7"",""isBinary"":false}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""CVE-2018-14719"",""vulnerabilityDetails"":""FasterXML jackson-databind 2.x before 2.9.7 might allow remote attackers to execute arbitrary code by leveraging failure to block the blaze-ds-opt and blaze-ds-core classes from polymorphic deserialization."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14719"",""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-2018-14719 (High) detected in jackson-databind-2.9.6.jar - ## CVE-2018-14719 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.6.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: /module2/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.6/jackson-databind-2.9.6.jar</p>
<p>

Dependency Hierarchy:
  - jackson-module-kotlin-2.9.6.jar (Root Library)
    - :x: **jackson-databind-2.9.6.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/KaterinaOrg/maven-modular/commit/27eea04c852891f5a7663c22ad865308b8149942"">27eea04c852891f5a7663c22ad865308b8149942</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>  
  
FasterXML jackson-databind 2.x before 2.9.7 might allow remote attackers to execute arbitrary code by leveraging failure to block the blaze-ds-opt and blaze-ds-core classes from polymorphic deserialization.

<p>Publish Date: 2019-01-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14719>CVE-2018-14719</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://nvd.nist.gov/vuln/detail/CVE-2018-14719"">https://nvd.nist.gov/vuln/detail/CVE-2018-14719</a></p>
<p>Release Date: 2019-01-02</p>
<p>Fix Resolution: 2.9.7</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.6"",""packageFilePaths"":[""/module2/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""com.fasterxml.jackson.module:jackson-module-kotlin:2.9.6;com.fasterxml.jackson.core:jackson-databind:2.9.6"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""2.9.7"",""isBinary"":false}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""CVE-2018-14719"",""vulnerabilityDetails"":""FasterXML jackson-databind 2.x before 2.9.7 might allow remote attackers to execute arbitrary code by leveraging failure to block the blaze-ds-opt and blaze-ds-core classes from polymorphic deserialization."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14719"",""cvss3Severity"":""high"",""cvss3Score"":""9.8"",""cvss3Metrics"":{""A"":""High"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""High"",""UI"":""None"",""AV"":""Network"",""I"":""High""},""extraData"":{}}</REMEDIATE> -->",0,cve      high  detected in jackson databind       jar      cve       high severity vulnerability     vulnerable library    jackson databind       jar      general data binding functionality for jackson  works on core streaming api   library home page   a href     path to dependency file     pom xml   path to vulnerable library   home wss scanner    repository com fasterxml jackson core jackson databind       jackson databind       jar     dependency hierarchy      jackson module kotlin       jar  root library         x    jackson databind       jar    vulnerable library   found in head commit   a href     found in base branch   master              vulnerability details         fasterxml jackson databind   x before       might allow remote attackers to execute arbitrary code by leveraging failure to block the blaze ds opt and blaze ds core classes from polymorphic deserialization    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                     isopenpronvulnerability  true  ispackagebased  true  isdefaultbranch  true  packages     istransitivedependency  true  dependencytree   com fasterxml jackson module jackson module kotlin       com fasterxml jackson core jackson databind         isminimumfixversionavailable  true  minimumfixversion           isbinary  false    basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   fasterxml jackson databind   x before       might allow remote attackers to execute arbitrary code by leveraging failure to block the blaze ds opt and blaze ds core classes from polymorphic deserialization    vulnerabilityurl        ,0
132580,12512274061.0,IssuesEvent,2020-06-02 22:21:24,golang/go,https://api.github.com/repos/golang/go,closed,time: document that RFC3339 accepts invalid formats when used with Parse,Documentation NeedsFix,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.13 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
It reproduces on play.golang.org and the underlying issue is still present in the source.

### What operating system and processor architecture are you using (`go env`)?

darwin/amd64

### What did you do?

Parsed a faulty ISO 8601 string with a single-digit hour using `time.RFC3339`.  E.g. `2020-02-02T2:02:02Z`.


### What did you expect to see?

I expected this parse to error because [RFC-3339 sec 5.6](https://tools.ietf.org/html/rfc3339#section-5.6) defines the following token, requiring two digits for the hour:
```
time-hour       = 2DIGIT  ; 00-23
```

### What did you see instead?

The parse succeeded.

This could be fixed by changing `time.RFC3339` to `2006-01-02T03:04:05Z07:00`.  If this is deemed a backward incompatible change, adding a new `time.RFC3339Strict` constant would also be an acceptable option.

See https://play.golang.org/p/6qyFYfx6pMr for example with one and two-digit years with `time.Parse3339` and the stricter version.",1.0,"time: document that RFC3339 accepts invalid formats when used with Parse - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.13 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
It reproduces on play.golang.org and the underlying issue is still present in the source.

### What operating system and processor architecture are you using (`go env`)?

darwin/amd64

### What did you do?

Parsed a faulty ISO 8601 string with a single-digit hour using `time.RFC3339`.  E.g. `2020-02-02T2:02:02Z`.


### What did you expect to see?

I expected this parse to error because [RFC-3339 sec 5.6](https://tools.ietf.org/html/rfc3339#section-5.6) defines the following token, requiring two digits for the hour:
```
time-hour       = 2DIGIT  ; 00-23
```

### What did you see instead?

The parse succeeded.

This could be fixed by changing `time.RFC3339` to `2006-01-02T03:04:05Z07:00`.  If this is deemed a backward incompatible change, adding a new `time.RFC3339Strict` constant would also be an acceptable option.

See https://play.golang.org/p/6qyFYfx6pMr for example with one and two-digit years with `time.Parse3339` and the stricter version.",1,time  document that   accepts invalid formats when used with parse         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version            go version  go version     darwin             does this issue reproduce with the latest release   it reproduces on play golang org and the underlying issue is still present in the source         what operating system and processor architecture are you using   go env       darwin          what did you do     parsed a faulty iso   string with a single digit hour using  time      e g                        what did you expect to see     i expected this parse to error because     defines the following token  requiring two digits for the hour        time hour                              what did you see instead     the parse succeeded     this could be fixed by changing  time    to                 if this is deemed a backward incompatible change  adding a new  time    constant would also be an acceptable option     see   for example with one and two digit years with  time    and the stricter version ,1
380645,11269046328.0,IssuesEvent,2020-01-14 07:59:21,Laravel-Backpack/CRUD,https://api.github.com/repos/Laravel-Backpack/CRUD,opened,[4.0][Feature] New widget: CRUD,Priority: SHOULD,"A stripped-down version of a CrudController could be shown as a widget.

This could be used:
- in the dashboard, for fast access to something that's often-used;
- inside the Preview operation, to allow people to quickly do things to connected entries;

Food for thought. Let's brainstorm.",1.0,"[4.0][Feature] New widget: CRUD - A stripped-down version of a CrudController could be shown as a widget.

This could be used:
- in the dashboard, for fast access to something that's often-used;
- inside the Preview operation, to allow people to quickly do things to connected entries;

Food for thought. Let's brainstorm.",0,   new widget  crud   a stripped down version of a crudcontroller could be shown as a widget     this could be used     in the dashboard  for fast access to something that s often used     inside the preview operation  to allow people to quickly do things to connected entries     food for thought  let s brainstorm ,0
50364,7600742400.0,IssuesEvent,2018-04-28 05:55:36,golang/go,https://api.github.com/repos/golang/go,closed,doc/effective_go.html: recommend the race detector,Documentation help wanted,"The race detector is an invaluable tool for detecting bugs in Go programs; ideally, everyone should test with it (and use it before filing bugs or even getting very far into debugging failures).

_Effective Go_ is one of the major starting points for new Go developers, but the string “race detector” doesn't currently appear in it at all. We should update _Effective Go_ to recommend it.",1.0,"doc/effective_go.html: recommend the race detector - The race detector is an invaluable tool for detecting bugs in Go programs; ideally, everyone should test with it (and use it before filing bugs or even getting very far into debugging failures).

_Effective Go_ is one of the major starting points for new Go developers, but the string “race detector” doesn't currently appear in it at all. We should update _Effective Go_ to recommend it.",1,doc effective go html  recommend the race detector   the race detector is an invaluable tool for detecting bugs in go programs  ideally  everyone should test with it  and use it before filing bugs or even getting very far into debugging failures       effective go  is one of the major starting points for new go developers  but the string “race detector” doesn t currently appear in it at all  we should update  effective go  to recommend it ,1
47021,7299398061.0,IssuesEvent,2018-02-26 19:59:25,golang/go,https://api.github.com/repos/golang/go,closed,archive/zip: improve Writer.Create documentation on how to add directories,Documentation NeedsFix help wanted,"I tried to add an empty folder to a zip.Writer with zip.Writer.Create. From the [docs](https://golang.org/pkg/archive/zip/#Writer.Create) it is not clear how to do this. There is a [google group post](https://groups.google.com/forum/#!topic/golang-nuts/Te0oScOV3KM) that provides the solution, which is to add a slash at the end of the path given to zip.Writer.Create.

I suggest adding this detail to the documentation comment on zip.Writer.Create, e.g. ""... To create a folder instead of a file, add a trailing slash to the path."".",1.0,"archive/zip: improve Writer.Create documentation on how to add directories - I tried to add an empty folder to a zip.Writer with zip.Writer.Create. From the [docs](https://golang.org/pkg/archive/zip/#Writer.Create) it is not clear how to do this. There is a [google group post](https://groups.google.com/forum/#!topic/golang-nuts/Te0oScOV3KM) that provides the solution, which is to add a slash at the end of the path given to zip.Writer.Create.

I suggest adding this detail to the documentation comment on zip.Writer.Create, e.g. ""... To create a folder instead of a file, add a trailing slash to the path."".",1,archive zip  improve writer create documentation on how to add directories   i tried to add an empty folder to a zip writer with zip writer create  from the     it is not clear how to do this  there is a     that provides the solution  which is to add a slash at the end of the path given to zip writer create     i suggest adding this detail to the documentation comment on zip writer create  e g       to create a folder instead of a file  add a trailing slash to the path   ,1
380722,11270412280.0,IssuesEvent,2020-01-14 10:49:45,dhowe/spectre,https://api.github.com/repos/dhowe/spectre,opened,button clickable area is too big,med-priority,"<Link><Button></Button></Link>


created a 100% width button. 

<img width=""1117"" alt=""Screenshot 2020-01-14 at 6 44 45 PM (2)"" src=""https://user-images.githubusercontent.com/4047303/72337990-7c1ba100-36fe-11ea-9d66-a24a28cb4e7a.png"">




",1.0,"button clickable area is too big - <Link><Button></Button></Link>


created a 100% width button. 

<img width=""1117"" alt=""Screenshot 2020-01-14 at 6 44 45 PM (2)"" src=""https://user-images.githubusercontent.com/4047303/72337990-7c1ba100-36fe-11ea-9d66-a24a28cb4e7a.png"">




",0,button clickable area is too big             created a    width button       img width     alt  screenshot       at       pm      src             ,0
31133,5908384943.0,IssuesEvent,2017-05-19 20:15:42,golang/go,https://api.github.com/repos/golang/go,closed,doc: docs mention non-existent yacc,Documentation,"Hello,
If you open page https://golang.org/doc/cmd and choose at the end of page, then on page https://golang.org/cmd/yacc/ you will see

../../go/src/cmd/yacc: file does not exist
",1.0,"doc: docs mention non-existent yacc - Hello,
If you open page https://golang.org/doc/cmd and choose at the end of page, then on page https://golang.org/cmd/yacc/ you will see

../../go/src/cmd/yacc: file does not exist
",1,doc  docs mention non existent yacc   hello   if you open page   and choose at the end of page  then on page   you will see          go src cmd yacc  file does not exist  ,1
55176,7964638281.0,IssuesEvent,2018-07-13 22:30:35,golang/go,https://api.github.com/repos/golang/go,closed,os/exec: document that ExtraFiles does not work on Windows,Documentation NeedsFix help wanted,"Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?

1.10.3 windows/amd64

### Does this issue reproduce with the latest release?

1.10.3 seems to be currently the latest release so: yep.

### What operating system and processor architecture are you using (`go env`)?

windows 10 home, amd64, Intel i5-6200U

```
set GOARCH=amd64
set GOBIN=%GOPATH%\bin
set GOCACHE=C:\Users\me\AppData\Local\go-build
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\Users\me\go
set GORACE=
set GOROOT=C:\Go
set GOTMPDIR=
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\me\AppData\Local\Temp\go-build361648014=/tmp/go-build -gno-record-gcc-switches
```
**BTW**: Having `GOBIN=%GOPATH%\bin` causes a lot of packages (from github) to not compile for some reason. (It works if one overrides it with manually expanding GOPATH). 

### What did you do?

The package os.Exec mentions that some examples assume Unix and might not work on Windows but it doesn't mention that it doesn't support windows and by looking at the source code it oughta support it. 

```
fork/exec prog.exe: not supported by windows
```
```go
cmd := exec.Command(normCmd)

	// direct access to datafile
	cmd.Stdin = rawfile

	// metadata-filtered observations on stdout
	obspipe, err := cmd.StdoutPipe()
	if err != nil {
		return err
	}

	// pass through stderr
	cmd.Stderr = os.Stderr

	// metadata on fd 3
	metapipeCmd, metapipe, err := os.Pipe()
	if err != nil {
		return err
	}

	cmd.ExtraFiles = make([]*os.File, 1)
	cmd.ExtraFiles[0] = metapipeCmd

	// start the command
	if err := cmd.Start(); err != nil { // errors on windows
		log.Fatal(err) 
		return err
	}
```
### What did you expect to see?

The program being run.

### What did you see instead?

An error message.",1.0,"os/exec: document that ExtraFiles does not work on Windows - Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?

1.10.3 windows/amd64

### Does this issue reproduce with the latest release?

1.10.3 seems to be currently the latest release so: yep.

### What operating system and processor architecture are you using (`go env`)?

windows 10 home, amd64, Intel i5-6200U

```
set GOARCH=amd64
set GOBIN=%GOPATH%\bin
set GOCACHE=C:\Users\me\AppData\Local\go-build
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\Users\me\go
set GORACE=
set GOROOT=C:\Go
set GOTMPDIR=
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\me\AppData\Local\Temp\go-build361648014=/tmp/go-build -gno-record-gcc-switches
```
**BTW**: Having `GOBIN=%GOPATH%\bin` causes a lot of packages (from github) to not compile for some reason. (It works if one overrides it with manually expanding GOPATH). 

### What did you do?

The package os.Exec mentions that some examples assume Unix and might not work on Windows but it doesn't mention that it doesn't support windows and by looking at the source code it oughta support it. 

```
fork/exec prog.exe: not supported by windows
```
```go
cmd := exec.Command(normCmd)

	// direct access to datafile
	cmd.Stdin = rawfile

	// metadata-filtered observations on stdout
	obspipe, err := cmd.StdoutPipe()
	if err != nil {
		return err
	}

	// pass through stderr
	cmd.Stderr = os.Stderr

	// metadata on fd 3
	metapipeCmd, metapipe, err := os.Pipe()
	if err != nil {
		return err
	}

	cmd.ExtraFiles = make([]*os.File, 1)
	cmd.ExtraFiles[0] = metapipeCmd

	// start the command
	if err := cmd.Start(); err != nil { // errors on windows
		log.Fatal(err) 
		return err
	}
```
### What did you expect to see?

The program being run.

### What did you see instead?

An error message.",1,os exec  document that extrafiles does not work on windows   please answer these questions before submitting your issue  thanks           what version of go are you using   go version             windows          does this issue reproduce with the latest release           seems to be currently the latest release so  yep         what operating system and processor architecture are you using   go env       windows   home     intel             set goarch    set gobin  gopath  bin  set gocache c  users me appdata local go build  set goexe  exe  set gohostarch    set gohostos windows  set goos windows  set gopath c  users me go  set gorace   set goroot c  go  set gotmpdir   set gotooldir c  go pkg tool windows    set gccgo gccgo  set cc gcc  set cxx g    set cgo enabled    set cgo cflags  g     set cgo cppflags   set cgo cxxflags  g     set cgo fflags  g     set cgo ldflags  g     set pkg config pkg config  set gogccflags     mthreads  fmessage length    fdebug prefix map c  users me appdata local temp go    tmp go build  gno record gcc switches         btw    having  gobin  gopath  bin  causes a lot of packages  from github  to not compile for some reason   it works if one overrides it with manually expanding gopath           what did you do     the package os exec mentions that some examples assume unix and might not work on windows but it doesn t mention that it doesn t support windows and by looking at the source code it oughta support it           fork exec prog exe  not supported by windows          go  cmd    exec command normcmd     	   direct access to datafile  	cmd stdin   rawfile    	   metadata filtered observations on stdout  	obspipe  err    cmd stdoutpipe    	if err    nil    		return err  	     	   pass through stderr  	cmd stderr   os stderr    	   metadata on fd    	metapipecmd  metapipe  err    os pipe    	if err    nil    		return err  	     	cmd extrafiles   make   os file      	cmd extrafiles    metapipecmd    	   start the command  	if err    cmd start    err    nil      errors on windows  		log fatal err    		return err  	            what did you expect to see     the program being run         what did you see instead     an error message ,1
226043,17295665395.0,IssuesEvent,2021-07-25 17:17:16,golang/go,https://api.github.com/repos/golang/go,closed,spec: typographical inconsistency in character literals,Documentation NeedsFix,"### What did you do?

* Carefully read through https://golang.org/ref/spec#Rune_literals.

### What did you expect to see?
* The Unicode code points around the text ""alert or bell"" should be sorted.
* The Unicode code points around the text ""alert or bell"" should either use uppercase or lowercase hexadecimal digits.

### What did you see instead?
* There ordering of the code points is not apparent. It is neither alphabetical nor by code point nor ""vertical first, then horizontal"".
* U+000D is uppercase, U+000b is lowercase.

These inconsistencies are not critical in any way, I just wondered whether there was some reason for this inconsistency and for ordering the code points in exactly this way.",1.0,"spec: typographical inconsistency in character literals - ### What did you do?

* Carefully read through https://golang.org/ref/spec#Rune_literals.

### What did you expect to see?
* The Unicode code points around the text ""alert or bell"" should be sorted.
* The Unicode code points around the text ""alert or bell"" should either use uppercase or lowercase hexadecimal digits.

### What did you see instead?
* There ordering of the code points is not apparent. It is neither alphabetical nor by code point nor ""vertical first, then horizontal"".
* U+000D is uppercase, U+000b is lowercase.

These inconsistencies are not critical in any way, I just wondered whether there was some reason for this inconsistency and for ordering the code points in exactly this way.",1,spec  typographical inconsistency in character literals       what did you do       carefully read through          what did you expect to see     the unicode code points around the text  alert or bell  should be sorted     the unicode code points around the text  alert or bell  should either use uppercase or lowercase hexadecimal digits         what did you see instead     there ordering of the code points is not apparent  it is neither alphabetical nor by code point nor  vertical first  then horizontal      u   is uppercase  u   is lowercase     these inconsistencies are not critical in any way  i just wondered whether there was some reason for this inconsistency and for ordering the code points in exactly this way ,1
3639,9908038990.0,IssuesEvent,2019-06-27 17:15:40,nowakprojects/PersonalEducation,https://api.github.com/repos/nowakprojects/PersonalEducation,opened,"50 Shades of Data – how, when and why Big, Relational, NoSQL, Elastic (Lucas Jellema, Netherlands)",CQRS ElastickStack Event Sourcing Event-Driven NoSQL Software Architecture,https://www.youtube.com/watch?v=xm9L3ykz-kc,1.0,"50 Shades of Data – how, when and why Big, Relational, NoSQL, Elastic (Lucas Jellema, Netherlands) - https://www.youtube.com/watch?v=xm9L3ykz-kc",0,  shades of data – how  when and why big  relational  nosql  elastic  lucas jellema  netherlands     ,0
20058,4488308326.0,IssuesEvent,2016-08-30 06:40:11,golang/go,https://api.github.com/repos/golang/go,opened,doc: document assembly calling convention,Documentation,"We should probably specify the Go calling convention in doc/asm.html, at least to a degree.

Might be especially useful as a reference when we get around to changing it.

@cherrymui @dr2chase @nigeltao 

",1.0,"doc: document assembly calling convention - We should probably specify the Go calling convention in doc/asm.html, at least to a degree.

Might be especially useful as a reference when we get around to changing it.

@cherrymui @dr2chase @nigeltao 

",1,doc  document assembly calling convention   we should probably specify the go calling convention in doc asm html  at least to a degree     might be especially useful as a reference when we get around to changing it      cherrymui     nigeltao     ,1
222625,24711202331.0,IssuesEvent,2022-10-20 01:02:53,autoai-org/AID,https://api.github.com/repos/autoai-org/AID,opened,eslint-plugin-import-2.22.1.tgz: 1 vulnerabilities (highest severity is: 7.5),security vulnerability,"<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>eslint-plugin-import-2.22.1.tgz</b></p></summary>

<p></p>
<p>Path to dependency file: /components/discovery/yarn.lock</p>
<p>Path to vulnerable library: /components/dashboard/node_modules/minimatch/package.json,/components/discovery/yarn.lock,/docs/node_modules/minimatch/package.json</p>
<p>

</details>

## Vulnerabilities

| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2022-3517](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-3517) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | minimatch-3.0.4.tgz | Transitive | N/A | &#10060; |


## Details

<details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-3517</summary>


###  Vulnerable Library - <b>minimatch-3.0.4.tgz</b></p>

<p>a glob matcher in javascript</p>
<p>Library home page: <a href=""https://registry.npmjs.org/minimatch/-/minimatch-3.0.4.tgz"">https://registry.npmjs.org/minimatch/-/minimatch-3.0.4.tgz</a></p>
<p>Path to dependency file: /components/dashboard/node_modules/minimatch/package.json</p>
<p>Path to vulnerable library: /components/dashboard/node_modules/minimatch/package.json,/components/discovery/yarn.lock,/docs/node_modules/minimatch/package.json</p>
<p>

Dependency Hierarchy:
  - eslint-plugin-import-2.22.1.tgz (Root Library)
    - :x: **minimatch-3.0.4.tgz** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
A vulnerability was found in the minimatch package. This flaw allows a Regular Expression Denial of Service (ReDoS) when calling the braceExpand function with specific arguments, resulting in a Denial of Service.

<p>Publish Date: 2022-10-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-3517>CVE-2022-3517</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Release Date: 2022-10-17</p>
<p>Fix Resolution: minimatch - 3.0.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details>",True,"eslint-plugin-import-2.22.1.tgz: 1 vulnerabilities (highest severity is: 7.5) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>eslint-plugin-import-2.22.1.tgz</b></p></summary>

<p></p>
<p>Path to dependency file: /components/discovery/yarn.lock</p>
<p>Path to vulnerable library: /components/dashboard/node_modules/minimatch/package.json,/components/discovery/yarn.lock,/docs/node_modules/minimatch/package.json</p>
<p>

</details>

## Vulnerabilities

| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2022-3517](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-3517) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | minimatch-3.0.4.tgz | Transitive | N/A | &#10060; |


## Details

<details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-3517</summary>


###  Vulnerable Library - <b>minimatch-3.0.4.tgz</b></p>

<p>a glob matcher in javascript</p>
<p>Library home page: <a href=""https://registry.npmjs.org/minimatch/-/minimatch-3.0.4.tgz"">https://registry.npmjs.org/minimatch/-/minimatch-3.0.4.tgz</a></p>
<p>Path to dependency file: /components/dashboard/node_modules/minimatch/package.json</p>
<p>Path to vulnerable library: /components/dashboard/node_modules/minimatch/package.json,/components/discovery/yarn.lock,/docs/node_modules/minimatch/package.json</p>
<p>

Dependency Hierarchy:
  - eslint-plugin-import-2.22.1.tgz (Root Library)
    - :x: **minimatch-3.0.4.tgz** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
A vulnerability was found in the minimatch package. This flaw allows a Regular Expression Denial of Service (ReDoS) when calling the braceExpand function with specific arguments, resulting in a Denial of Service.

<p>Publish Date: 2022-10-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-3517>CVE-2022-3517</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Release Date: 2022-10-17</p>
<p>Fix Resolution: minimatch - 3.0.5</p>

</p>

<p></p>


Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details>",0,eslint plugin import       tgz    vulnerabilities  highest severity is             vulnerable library    eslint plugin import       tgz         path to dependency file   components discovery yarn lock   path to vulnerable library   components dashboard node modules minimatch package json  components discovery yarn lock  docs node modules minimatch package json           vulnerabilities    cve   severity     cvss   dependency   type   fixed in   remediation available                                                                                   high         minimatch       tgz   transitive   n a               details        cve             vulnerable library    minimatch       tgz     a glob matcher in javascript   library home page   a href     path to dependency file   components dashboard node modules minimatch package json   path to vulnerable library   components dashboard node modules minimatch package json  components discovery yarn lock  docs node modules minimatch package json     dependency hierarchy      eslint plugin import       tgz  root library         x    minimatch       tgz    vulnerable library   found in base branch   main               vulnerability details        a vulnerability was found in the minimatch package  this flaw allows a regular expression denial of service  redos  when calling the braceexpand function with specific arguments  resulting in a denial of service    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  high   for more information on   scores  click  a href                suggested fix     type  upgrade version   release date          fix resolution  minimatch                   step up your open source security game with mend      ,0
24348,5051154438.0,IssuesEvent,2016-12-20 20:58:35,golang/go,https://api.github.com/repos/golang/go,closed,doc: asm.html has no discussion of mips architectures,Documentation NeedsFix,"The sections at the end of the document provide architecture-specific details. There needs to be a section for the MIPS.
",1.0,"doc: asm.html has no discussion of mips architectures - The sections at the end of the document provide architecture-specific details. There needs to be a section for the MIPS.
",1,doc  asm html has no discussion of mips architectures   the sections at the end of the document provide architecture specific details  there needs to be a section for the mips   ,1
379400,26369965461.0,IssuesEvent,2023-01-11 19:47:06,golang/go,https://api.github.com/repos/golang/go,closed,x/net/html: add StripTags example,Documentation NeedsFix,"Stripping HTML tags is absolutely required for every web related development task.
 
This was previously raised in: https://github.com/golang/go/issues/5884
",1.0,"x/net/html: add StripTags example - Stripping HTML tags is absolutely required for every web related development task.
 
This was previously raised in: https://github.com/golang/go/issues/5884
",1,x net html  add striptags example   stripping html tags is absolutely required for every web related development task      this was previously raised in     ,1
506006,14656313220.0,IssuesEvent,2020-12-28 13:08:31,google/ground-platform,https://api.github.com/repos/google/ground-platform,closed,[Sign in] Block access to sign in page if already signed in,priority: p2 type: bug,"We should not allow authenticated users to access `/signin`. Instead, we can create an auth guard (`UnauthGuard`?) that will redirect to `/p/:new` for now if the user is already logged in.",1.0,"[Sign in] Block access to sign in page if already signed in - We should not allow authenticated users to access `/signin`. Instead, we can create an auth guard (`UnauthGuard`?) that will redirect to `/p/:new` for now if the user is already logged in.",0,  block access to sign in page if already signed in   we should not allow authenticated users to access   signin   instead  we can create an auth guard   unauthguard    that will redirect to   p  new  for now if the user is already logged in ,0
72814,7312384857.0,IssuesEvent,2018-02-28 20:49:10,rancher/rancher,https://api.github.com/repos/rancher/rancher,closed,"Not able to list Certificates in ""Certificates"" view, UI hangs when we have a certificate scoped to namespace.",kind/bug status/to-test version/2.0,"Rancher Server - 2.0 build from master

Steps to reproduce the problem:
From project view , create a certificate with scope ""Available to a single namespace:""
Once user is brought back to list view , refresh this page.
UI hangs.

Relaunch project page and try to access ""Certificates"" tab.

UI hangs even after the certificate is listed.

In this case , Certificate list  in ""Add Ingress"" view does not list this certificate.",1.0,"Not able to list Certificates in ""Certificates"" view, UI hangs when we have a certificate scoped to namespace. - Rancher Server - 2.0 build from master

Steps to reproduce the problem:
From project view , create a certificate with scope ""Available to a single namespace:""
Once user is brought back to list view , refresh this page.
UI hangs.

Relaunch project page and try to access ""Certificates"" tab.

UI hangs even after the certificate is listed.

In this case , Certificate list  in ""Add Ingress"" view does not list this certificate.",0,not able to list certificates in  certificates  view  ui hangs when we have a certificate scoped to namespace    rancher server       build from master    steps to reproduce the problem   from project view   create a certificate with scope  available to a single namespace    once user is brought back to list view   refresh this page   ui hangs     relaunch project page and try to access  certificates  tab     ui hangs even after the certificate is listed     in this case   certificate list  in  add ingress  view does not list this certificate ,0
33493,4494509002.0,IssuesEvent,2016-08-31 06:34:06,angular-ui/ui-router,https://api.github.com/repos/angular-ui/ui-router,closed,[Feature] Future States,1.0 design feature,"1.0 no longer supports [future states](https://github.com/christopherthielen/ui-router-extras).

On the flip side, it is easier to swing this in 1.0 without an advanced plugin. I wanted to start the discussion for what my implementation looks like. 

This implementation relies on: ng1, oclazyload, systemjs, ui-router 1.0apha4.

```
const services = [ '$q', '$state', 'cfpLoadingBar',
  'ng2.Compiler', 'ng2.ComponentFactoryRefMap', '$transitions' ];

export const configLaziness = [
  ...services,
  ($q, $state, $ocLazyLoad, compiler, componentFactoryRefMap, $transitions) => {

    function buildState(src) {
      let def = $q.defer();

      System.import(src).then(function(loaded){
        let newModule = loaded;
        if(!loaded.name){
          newModule = loaded.default;
        }

        adapter.compileNg2Components(compiler, componentFactoryRefMap);

        $ocLazyLoad.load(newModule).then(function(){
          cfpLoadingBar.complete();
          def.resolve();
        }, function(err) {
          throw err;
        });
      });

      return def.promise;
    };

    $state.$urlRouter.urlRouterProvider.otherwise(($injector, $location) => {

     /// below few lines sucks and is a bit nieve
      const url = $location.url().replace(/^\/?|\/?$/, ''); 
      const splits = url.split('/');
      const state = routes.find(r => {
        return r.urlPrefix.indexOf(splits[0]) > -1; 
      });

      if(state) {
        buildState(state.src).then(() => {
          $state.$urlRouter.sync();
        });
      } else {
        $state.go('404');
      }
    });

    $state.stateProvider.onInvalid(($to$, $from$, $state) => {
      const name = $to$.name();
      let state = routes.find(r => { return r.stateName === name });

      if(state) {
        var redirect = {
          to: $to$.identifier(),
          toParams: $to$.params(),
          options: $to$.options()
        };

        buildState(state.src).then(() => {
          $state.go(redirect.to, redirect.toParams, redirect.options);
        });
      } else {
        $state.go('404');
      }
    });
  }
];
```

and the route definitions look like:

```
[
  {
    ""stateName"": ""apps"",
    ""urlPrefix"": ""/apps"",
    ""src"": ""app/admin/apps/apps.js""
  }
]
```

and this is configured like:

```
import angular from 'angular';
import { configRouting, configLaziness } from 'routing.js';

let app = angular.module('app', [ 'ui.router' ]);
app.config(configRouting);
app.run(configLaziness);
```

Its also worth noting this supports angular2 lazy loading.",1.0,"[Feature] Future States - 1.0 no longer supports [future states](https://github.com/christopherthielen/ui-router-extras).

On the flip side, it is easier to swing this in 1.0 without an advanced plugin. I wanted to start the discussion for what my implementation looks like. 

This implementation relies on: ng1, oclazyload, systemjs, ui-router 1.0apha4.

```
const services = [ '$q', '$state', 'cfpLoadingBar',
  'ng2.Compiler', 'ng2.ComponentFactoryRefMap', '$transitions' ];

export const configLaziness = [
  ...services,
  ($q, $state, $ocLazyLoad, compiler, componentFactoryRefMap, $transitions) => {

    function buildState(src) {
      let def = $q.defer();

      System.import(src).then(function(loaded){
        let newModule = loaded;
        if(!loaded.name){
          newModule = loaded.default;
        }

        adapter.compileNg2Components(compiler, componentFactoryRefMap);

        $ocLazyLoad.load(newModule).then(function(){
          cfpLoadingBar.complete();
          def.resolve();
        }, function(err) {
          throw err;
        });
      });

      return def.promise;
    };

    $state.$urlRouter.urlRouterProvider.otherwise(($injector, $location) => {

     /// below few lines sucks and is a bit nieve
      const url = $location.url().replace(/^\/?|\/?$/, ''); 
      const splits = url.split('/');
      const state = routes.find(r => {
        return r.urlPrefix.indexOf(splits[0]) > -1; 
      });

      if(state) {
        buildState(state.src).then(() => {
          $state.$urlRouter.sync();
        });
      } else {
        $state.go('404');
      }
    });

    $state.stateProvider.onInvalid(($to$, $from$, $state) => {
      const name = $to$.name();
      let state = routes.find(r => { return r.stateName === name });

      if(state) {
        var redirect = {
          to: $to$.identifier(),
          toParams: $to$.params(),
          options: $to$.options()
        };

        buildState(state.src).then(() => {
          $state.go(redirect.to, redirect.toParams, redirect.options);
        });
      } else {
        $state.go('404');
      }
    });
  }
];
```

and the route definitions look like:

```
[
  {
    ""stateName"": ""apps"",
    ""urlPrefix"": ""/apps"",
    ""src"": ""app/admin/apps/apps.js""
  }
]
```

and this is configured like:

```
import angular from 'angular';
import { configRouting, configLaziness } from 'routing.js';

let app = angular.module('app', [ 'ui.router' ]);
app.config(configRouting);
app.run(configLaziness);
```

Its also worth noting this supports angular2 lazy loading.",0,  future states       no longer supports        on the flip side  it is easier to swing this in     without an advanced plugin  i wanted to start the discussion for what my implementation looks like      this implementation relies on     oclazyload  systemjs  ui router              const services       q     state    cfploadingbar         compiler      componentfactoryrefmap     transitions        export const configlaziness           services       q   state   oclazyload  compiler  componentfactoryrefmap   transitions              function buildstate src           let def    q defer             system import src  then function loaded            let newmodule   loaded           if  loaded name              newmodule   loaded default                        adapter   compiler  componentfactoryrefmap               oclazyload load newmodule  then function               cfploadingbar complete               def resolve                function err               throw err                                   return def promise                  state  urlrouter urlrouterprovider otherwise   injector   location                   below few lines sucks and is a bit nieve        const url    location url   replace                           const splits   url split              const state   routes find r               return r urlprefix indexof splits                              if state             buildstate state src  then                     state  urlrouter sync                          else             state go                                 state stateprovider oninvalid   to    from    state              const name    to  name           let state   routes find r      return r statename     name              if state             var redirect                to   to  identifier               toparams   to  params               options   to  options                          buildstate state src  then                     state go redirect to  redirect toparams  redirect options                         else             state go                                          and the route definitions look like                       statename    apps         urlprefix     apps         src    app admin apps apps js                  and this is configured like          import angular from  angular    import   configrouting  configlaziness   from  routing js      let app   angular module  app        app config configrouting    app run configlaziness           its also worth noting this supports   lazy loading ,0
271156,20624022062.0,IssuesEvent,2022-03-07 20:25:30,golang/go,https://api.github.com/repos/golang/go,closed,"go/types, types2: document predicates on generic types",Documentation NeedsInvestigation,"Right now, go/types has limited functionality for computing predicates ""modulo type parameters"": signatures are considered identical modulo renaming of type parameters in their type parameter list:

```go
func F[A ~int](A) {}
func G[B ~int](B) {}
func H[C int](C) {}

type T[D ~int] func(D)
```

In this example, the types of `F` and `G` are considered identical, because they have pairwise identical type parameter constraints and their signatures are identical after substituting type parameters.  However, the signature of `F` is NOT identical to the signature of `H` (constraints don't match), and NOT identical to the underlying type of `T` (the signature itself does not have a type parameter list -- it uses type parameters from the declaration for `T`).

[CL 379540](https://go.dev/cl/379540) was intended to clean up some logic that existed to work around an earlier limitation that we didn't have instantiated methods. However, it inadvertently removed a ""feature"" that APIs like `AssignableTo` would somewhat work with uninstantiated types:

We ran into this example in kythe:
```
type Interface[T any] interface {
        Accept(T)
}

type Container[T any] struct {
        Element T
}

func (c Container[T]) Accept(t T) { c.Element = t }
```

Previously, we would report that `Container` is assignable to `Interface` (`AssignableTo(Container, Interface) == true`), because they would unify. However, this could be wrong, as in the following example:

```
type InterfaceInt[T ~int] interface {
        Accept(T)
}

type ContainerString[T ~string] struct {
        Element T
}

func (c ContainerString[T]) Accept(t T) { c.Element = t }
```

We would _also_ have `AssignableTo(ContainerString, InterfaceInt) == true`, even though there is no instantiation for which this holds.

Related:
- https://github.com/golang/go/issues/50658#issuecomment-1016975461. We don't expose any API for unification, and it would useful in several places.
- #49912 -- an outstanding bug for comparing method signatures modulo type parameters. However, notably fixing this bug would **not** address the behavior with respect to the `Interface` type above: the methods on `Interface` are parameterized by the type declaration parameters, not receiver type parameters.

~Alternatively, callers could ""instantiate"" the types with identical arguments, but then the burden is pushed onto the caller to find type arguments that satisfy both type parameter lists, which is arbitrarily complicated.~ (EDIT: this wouldn't even really work: type parameters could be in arbitrary order, and so for the caller to even know which type parameters should correspond, they'd have to do the unification themselves).

I don't believe this affects type-checking, but matters for the API and for tools. We need to reconsider what is most useful here.

My initial thoughts are as follows: rather than what we currently do for function signatures, generalize to a limited form of unification in `Identical`, where type parameters are joined and then substituted in constraints.

This runs into a problem of ""free type parameters""

```
func _[A *C, B *C, C any]() {
  var X func(A)
  var Y func(B)
}

type I[P *Q, Q any] interface{
  m(P)
}
```

The type of `X` and `Y` should not be identical.  What about the type of `X` and the signature of `I.m`? (EDIT: `X` and `Y` do NOT have identical types).

CC @griesemer @mdempsky ",1.0,"go/types, types2: document predicates on generic types - Right now, go/types has limited functionality for computing predicates ""modulo type parameters"": signatures are considered identical modulo renaming of type parameters in their type parameter list:

```go
func F[A ~int](A) {}
func G[B ~int](B) {}
func H[C int](C) {}

type T[D ~int] func(D)
```

In this example, the types of `F` and `G` are considered identical, because they have pairwise identical type parameter constraints and their signatures are identical after substituting type parameters.  However, the signature of `F` is NOT identical to the signature of `H` (constraints don't match), and NOT identical to the underlying type of `T` (the signature itself does not have a type parameter list -- it uses type parameters from the declaration for `T`).

[CL 379540](https://go.dev/cl/379540) was intended to clean up some logic that existed to work around an earlier limitation that we didn't have instantiated methods. However, it inadvertently removed a ""feature"" that APIs like `AssignableTo` would somewhat work with uninstantiated types:

We ran into this example in kythe:
```
type Interface[T any] interface {
        Accept(T)
}

type Container[T any] struct {
        Element T
}

func (c Container[T]) Accept(t T) { c.Element = t }
```

Previously, we would report that `Container` is assignable to `Interface` (`AssignableTo(Container, Interface) == true`), because they would unify. However, this could be wrong, as in the following example:

```
type InterfaceInt[T ~int] interface {
        Accept(T)
}

type ContainerString[T ~string] struct {
        Element T
}

func (c ContainerString[T]) Accept(t T) { c.Element = t }
```

We would _also_ have `AssignableTo(ContainerString, InterfaceInt) == true`, even though there is no instantiation for which this holds.

Related:
- https://github.com/golang/go/issues/50658#issuecomment-1016975461. We don't expose any API for unification, and it would useful in several places.
- #49912 -- an outstanding bug for comparing method signatures modulo type parameters. However, notably fixing this bug would **not** address the behavior with respect to the `Interface` type above: the methods on `Interface` are parameterized by the type declaration parameters, not receiver type parameters.

~Alternatively, callers could ""instantiate"" the types with identical arguments, but then the burden is pushed onto the caller to find type arguments that satisfy both type parameter lists, which is arbitrarily complicated.~ (EDIT: this wouldn't even really work: type parameters could be in arbitrary order, and so for the caller to even know which type parameters should correspond, they'd have to do the unification themselves).

I don't believe this affects type-checking, but matters for the API and for tools. We need to reconsider what is most useful here.

My initial thoughts are as follows: rather than what we currently do for function signatures, generalize to a limited form of unification in `Identical`, where type parameters are joined and then substituted in constraints.

This runs into a problem of ""free type parameters""

```
func _[A *C, B *C, C any]() {
  var X func(A)
  var Y func(B)
}

type I[P *Q, Q any] interface{
  m(P)
}
```

The type of `X` and `Y` should not be identical.  What about the type of `X` and the signature of `I.m`? (EDIT: `X` and `Y` do NOT have identical types).

CC @griesemer @mdempsky ",1,go types     document predicates on generic types   right now  go types has limited functionality for computing predicates  modulo type parameters   signatures are considered identical modulo renaming of type parameters in their type parameter list        go  func f  a      func g  b      func h  c        type t  func d          in this example  the types of  f  and  g  are considered identical  because they have pairwise identical type parameter constraints and their signatures are identical after substituting type parameters   however  the signature of  f  is not identical to the signature of  h   constraints don t match   and not identical to the underlying type of  t   the signature itself does not have a type parameter list    it uses type parameters from the declaration for  t           was intended to clean up some logic that existed to work around an earlier limitation that we didn t have instantiated methods  however  it inadvertently removed a  feature  that apis like  assignableto  would somewhat work with uninstantiated types     we ran into this example in kythe        type interface  interface            accept t        type container  struct            element t       func  c container   accept t t    c element   t           previously  we would report that  container  is assignable to  interface    assignableto container  interface     true    because they would unify  however  this could be wrong  as in the following example          type interfaceint  interface            accept t        type containerstring  struct            element t       func  c containerstring   accept t t    c element   t           we would  also  have  assignableto containerstring  interfaceint     true   even though there is no instantiation for which this holds     related       we don t expose any api for unification  and it would useful in several places           an outstanding bug for comparing method signatures modulo type parameters  however  notably fixing this bug would   not   address the behavior with respect to the  interface  type above  the methods on  interface  are parameterized by the type declaration parameters  not receiver type parameters      alternatively  callers could  instantiate  the types with identical arguments  but then the burden is pushed onto the caller to find type arguments that satisfy both type parameter lists  which is arbitrarily complicated    edit  this wouldn t even really work  type parameters could be in arbitrary order  and so for the caller to even know which type parameters should correspond  they d have to do the unification themselves      i don t believe this affects type checking  but matters for the api and for tools  we need to reconsider what is most useful here     my initial thoughts are as follows  rather than what we currently do for function signatures  generalize to a limited form of unification in  identical   where type parameters are joined and then substituted in constraints     this runs into a problem of  free type parameters          func           var x func a     var y func b        type i  interface     m p             the type of  x  and  y  should not be identical   what about the type of  x  and the signature of  i m    edit   x  and  y  do not have identical types      cc  griesemer  mdempsky ,1
423577,12298693396.0,IssuesEvent,2020-05-11 10:58:55,webcompat/web-bugs,https://api.github.com/repos/webcompat/web-bugs,closed,mobile.twitter.com - design is broken,browser-fenix engine-gecko priority-critical,"<!-- @browser: Firefox Mobile 78.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 10; Mobile; rv:78.0) Gecko/78.0 Firefox/78.0 -->
<!-- @reported_with:  -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/52687 -->
<!-- @extra_labels: browser-fenix -->

**URL**: https://mobile.twitter.com/home

**Browser / Version**: Firefox Mobile 78.0
**Operating System**: Android
**Tested Another Browser**: Yes Chrome

**Problem type**: Design is broken
**Description**: Items are misaligned
**Steps to Reproduce**:
Pressing retweet button will cause the URL bar to show up which will misalign retweet buttons. Which can make you press the wrong retweet button.
<details><summary>View the screenshot</summary><img alt='Screenshot' src='https://webcompat.com/uploads/2020/5/253458f0-dab1-46d5-a4a4-dbba63bb7516.jpg'></details>

<details>
<summary>Browser Configuration</summary>
<ul>
  <li>None</li>
</ul>
</details>

Submitted in the name of `@nfanja`

_From [webcompat.com](https://webcompat.com/) with ❤️_",1.0,"mobile.twitter.com - design is broken - <!-- @browser: Firefox Mobile 78.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 10; Mobile; rv:78.0) Gecko/78.0 Firefox/78.0 -->
<!-- @reported_with:  -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/52687 -->
<!-- @extra_labels: browser-fenix -->

**URL**: https://mobile.twitter.com/home

**Browser / Version**: Firefox Mobile 78.0
**Operating System**: Android
**Tested Another Browser**: Yes Chrome

**Problem type**: Design is broken
**Description**: Items are misaligned
**Steps to Reproduce**:
Pressing retweet button will cause the URL bar to show up which will misalign retweet buttons. Which can make you press the wrong retweet button.
<details><summary>View the screenshot</summary><img alt='Screenshot' src='https://webcompat.com/uploads/2020/5/253458f0-dab1-46d5-a4a4-dbba63bb7516.jpg'></details>

<details>
<summary>Browser Configuration</summary>
<ul>
  <li>None</li>
</ul>
</details>

Submitted in the name of `@nfanja`

_From [webcompat.com](https://webcompat.com/) with ❤️_",0,mobile twitter com   design is broken                url         browser   version    firefox mobile       operating system    android   tested another browser    yes chrome    problem type    design is broken   description    items are misaligned   steps to reproduce    pressing retweet button will cause the url bar to show up which will misalign retweet buttons  which can make you press the wrong retweet button     view the screenshot  img alt  screenshot  src        browser configuration       none       submitted in the name of   nfanja    from     with ❤️ ,0
320551,23814298091.0,IssuesEvent,2022-09-05 04:06:45,golang/go,https://api.github.com/repos/golang/go,closed,Document link always quoted 500,Documentation," In [https://go-zh.org/doc/](https://go-zh.org/doc/)

when i click `Go 语言之旅`

it always report 500

<img width=""863"" alt=""image"" src=""https://user-images.githubusercontent.com/31796988/188339719-b15542db-2dae-4165-943d-b1fc613bcb04.png"">



",1.0,"Document link always quoted 500 -  In [https://go-zh.org/doc/](https://go-zh.org/doc/)

when i click `Go 语言之旅`

it always report 500

<img width=""863"" alt=""image"" src=""https://user-images.githubusercontent.com/31796988/188339719-b15542db-2dae-4165-943d-b1fc613bcb04.png"">



",1,document link always quoted      in        when i click  go 语言之旅     it always report       img width     alt  image  src           ,1
817717,30651238487.0,IssuesEvent,2023-07-25 09:03:07,brave/brave-browser,https://api.github.com/repos/brave/brave-browser,closed,[Shortcuts]: Keyboard shortcuts are broken for non US layouts,OS/macOS feature/keyboard-shortcuts priority/P2 QA/Yes release-notes/exclude,"We have a report of Keyboard Shortcuts not working in the Czech keyboard layout in 1.56.

Report:
https://community.brave.com/t/keyboard-shortcuts-suddenly-broken/497495/5

I'm hoping that this only affects macOS.",1.0,"[Shortcuts]: Keyboard shortcuts are broken for non US layouts - We have a report of Keyboard Shortcuts not working in the Czech keyboard layout in 1.56.

Report:
https://community.brave.com/t/keyboard-shortcuts-suddenly-broken/497495/5

I'm hoping that this only affects macOS.",0,   keyboard shortcuts are broken for non us layouts   we have a report of keyboard shortcuts not working in the czech keyboard layout in         report        i m hoping that this only affects macos ,0
13291,3699724840.0,IssuesEvent,2016-02-29 02:34:11,golang/go,https://api.github.com/repos/golang/go,closed,time: Tick and NewTicker inconsistency,Documentation,"`NewTicker` will panic if the duration isn't greater than zero, while `Tick` will return `nil`.

Ideally `Tick` would panic as well but that could potentially break some code relying on this inconsistency. This special case should be documented as it's definitely not something you'd expect from reading the current `Tick` documentation.",1.0,"time: Tick and NewTicker inconsistency - `NewTicker` will panic if the duration isn't greater than zero, while `Tick` will return `nil`.

Ideally `Tick` would panic as well but that could potentially break some code relying on this inconsistency. This special case should be documented as it's definitely not something you'd expect from reading the current `Tick` documentation.",1,time  tick and newticker inconsistency    newticker  will panic if the duration isn t greater than zero  while  tick  will return  nil      ideally  tick  would panic as well but that could potentially break some code relying on this inconsistency  this special case should be documented as it s definitely not something you d expect from reading the current  tick  documentation ,1
35410,6461914133.0,IssuesEvent,2017-08-16 09:20:44,golang/go,https://api.github.com/repos/golang/go,closed,go/types: Identical ignores receiver of Signature,Documentation,"### What version of Go are you using (`go version`)?
go version go1.8.3 linux/amd64
go version devel +827be89a69 Thu Jun 15 21:53:23 2017 +0000 linux/amd64

### What did you do?
In the go/types type system, methods are represented as Func objects
with Signature types, where the Signature has a receiver that is not
nil. To me, that implies that the receiver is part of the Signature's
identity. types.Identical, however, disagrees, and only looks at the
arguments and results. This leads to two methods, with differently
typed receivers, to be considered identical.

I can see arguments for and against this behaviour. On the one hand,
it makes correct canonicalisation difficult and leads to confusing
behaviour when using e.g. typeutil.Map. Two methods with different
receivers are clearly different, requiring a different implicit first
argument. Furthermore, swapping supposedly ""identical"" signatures
would change the meaning of the program.

On the other hand, when working with interfaces and checking
whether a method matches the definition in an interface, the receiver
is irrelevant.

I ran into this behavior while serialising type information to disk,
using typeutil.Map to deduplicate type information. This led to a
function turning into a method, because it shared the signature (sans
receiver) of a method.

A program demonstrating the issue is at https://play.golang.org/p/H0FR2qbm2k

I'm not sure if this is a bug or working as intended, but either way
it is a flaw in the current API.

/cc @griesemer

### What did you expect to see?
```
func (pkg.T1).Method()
func (pkg.T2).Method()
false
```

### What did you see instead?
```
func (pkg.T1).Method()
func (pkg.T2).Method()
true
```

",1.0,"go/types: Identical ignores receiver of Signature - ### What version of Go are you using (`go version`)?
go version go1.8.3 linux/amd64
go version devel +827be89a69 Thu Jun 15 21:53:23 2017 +0000 linux/amd64

### What did you do?
In the go/types type system, methods are represented as Func objects
with Signature types, where the Signature has a receiver that is not
nil. To me, that implies that the receiver is part of the Signature's
identity. types.Identical, however, disagrees, and only looks at the
arguments and results. This leads to two methods, with differently
typed receivers, to be considered identical.

I can see arguments for and against this behaviour. On the one hand,
it makes correct canonicalisation difficult and leads to confusing
behaviour when using e.g. typeutil.Map. Two methods with different
receivers are clearly different, requiring a different implicit first
argument. Furthermore, swapping supposedly ""identical"" signatures
would change the meaning of the program.

On the other hand, when working with interfaces and checking
whether a method matches the definition in an interface, the receiver
is irrelevant.

I ran into this behavior while serialising type information to disk,
using typeutil.Map to deduplicate type information. This led to a
function turning into a method, because it shared the signature (sans
receiver) of a method.

A program demonstrating the issue is at https://play.golang.org/p/H0FR2qbm2k

I'm not sure if this is a bug or working as intended, but either way
it is a flaw in the current API.

/cc @griesemer

### What did you expect to see?
```
func (pkg.T1).Method()
func (pkg.T2).Method()
false
```

### What did you see instead?
```
func (pkg.T1).Method()
func (pkg.T2).Method()
true
```

",1,go types  identical ignores receiver of signature       what version of go are you using   go version     go version       linux    go version devel    thu jun              linux          what did you do   in the go types type system  methods are represented as func objects  with signature types  where the signature has a receiver that is not  nil  to me  that implies that the receiver is part of the signature s  identity  types identical  however  disagrees  and only looks at the  arguments and results  this leads to two methods  with differently  typed receivers  to be considered identical     i can see arguments for and against this behaviour  on the one hand   it makes correct canonicalisation difficult and leads to confusing  behaviour when using e g  typeutil map  two methods with different  receivers are clearly different  requiring a different implicit first  argument  furthermore  swapping supposedly  identical  signatures  would change the meaning of the program     on the other hand  when working with interfaces and checking  whether a method matches the definition in an interface  the receiver  is irrelevant     i ran into this behavior while serialising type information to disk   using typeutil map to deduplicate type information  this led to a  function turning into a method  because it shared the signature  sans  receiver  of a method     a program demonstrating the issue is at      i m not sure if this is a bug or working as intended  but either way  it is a flaw in the current api      cc  griesemer        what did you expect to see        func  pkg    method    func  pkg    method    false             what did you see instead        func  pkg    method    func  pkg    method    true         ,1
836,2502534129.0,IssuesEvent,2015-01-09 10:01:02,geosolutions-it/MapStore,https://api.github.com/repos/geosolutions-it/MapStore,closed,GeoBatchFlows plugin: run button in every row,enhancement Priority: Low,"Currently there is a single run button on top toolbar, enabled when a flow is selected.
We would like to have (as an option, or as a replacement of the current single button) a run action button on each row.",1.0,"GeoBatchFlows plugin: run button in every row - Currently there is a single run button on top toolbar, enabled when a flow is selected.
We would like to have (as an option, or as a replacement of the current single button) a run action button on each row.",0,geobatchflows plugin  run button in every row   currently there is a single run button on top toolbar  enabled when a flow is selected   we would like to have  as an option  or as a replacement of the current single button  a run action button on each row ,0
370260,25895992671.0,IssuesEvent,2022-12-14 22:31:04,golang/go,https://api.github.com/repos/golang/go,closed,spec: Document rules for recursive type and other self-referential decls,Documentation,"<pre>The spec says &quot;An interface type T may not embed itself or any interface type that
embeds T, recursively.&quot;, but nothing like this is mentioned for structs.

(A struct containing itself would obviously need infty memory, but the spec should
probably still explicitly mention that these are illegal while a struct containing a
pointer to itself is fine</pre>
",1.0,"spec: Document rules for recursive type and other self-referential decls - <pre>The spec says &quot;An interface type T may not embed itself or any interface type that
embeds T, recursively.&quot;, but nothing like this is mentioned for structs.

(A struct containing itself would obviously need infty memory, but the spec should
probably still explicitly mention that these are illegal while a struct containing a
pointer to itself is fine</pre>
",1,spec  document rules for recursive type and other self referential decls    the spec says  quot an interface type t may not embed itself or any interface type that embeds t  recursively  quot   but nothing like this is mentioned for structs    a struct containing itself would obviously need infty memory  but the spec should probably still explicitly mention that these are illegal while a struct containing a pointer to itself is fine  ,1
65189,7860859306.0,IssuesEvent,2018-06-21 21:27:44,Opentrons/opentrons,https://api.github.com/repos/Opentrons/opentrons,opened,Modules: New 'Modules and Pipettes' Section,app design feature,"As a Run App user, I would like to have a dedicated page for my modules and pipettes, so that they're not all crowded on the same page as my robot settings.

## Acceptance Criteria
- [ ] Robot card in robot sidebar has sub-nav for 'Robot' and 'Modules and Pipettes'
- [ ] New 'Modules and Pipettes' page 
- [ ] 'Pipettes' card moved from existing 'Robot' page to new 'Modules and Pipettes' page ",1.0,"Modules: New 'Modules and Pipettes' Section - As a Run App user, I would like to have a dedicated page for my modules and pipettes, so that they're not all crowded on the same page as my robot settings.

## Acceptance Criteria
- [ ] Robot card in robot sidebar has sub-nav for 'Robot' and 'Modules and Pipettes'
- [ ] New 'Modules and Pipettes' page 
- [ ] 'Pipettes' card moved from existing 'Robot' page to new 'Modules and Pipettes' page ",0,modules  new  modules and pipettes  section   as a run app user  i would like to have a dedicated page for my modules and pipettes  so that they re not all crowded on the same page as my robot settings        acceptance criteria      robot card in robot sidebar has sub nav for  robot  and  modules and pipettes       new  modules and pipettes  page        pipettes  card moved from existing  robot  page to new  modules and pipettes  page ,0
246405,20862852748.0,IssuesEvent,2022-03-22 01:54:07,woocommerce/woocommerce-gutenberg-products-block,https://api.github.com/repos/woocommerce/woocommerce-gutenberg-products-block,closed,Critical flows: Shopper → Mini Cart → Can see correct tax,type: enhancement category: tests ◼️ block: mini cart,"### Note

Create e2e tests to verify that a shopper can see the correct tax for products in cart.

### File

`tests/e2e/specs/shopper/mini-cart.test.js`

Part of #5814",1.0,"Critical flows: Shopper → Mini Cart → Can see correct tax - ### Note

Create e2e tests to verify that a shopper can see the correct tax for products in cart.

### File

`tests/e2e/specs/shopper/mini-cart.test.js`

Part of #5814",0,critical flows  shopper → mini cart → can see correct tax       note    create   tests to verify that a shopper can see the correct tax for products in cart         file     tests   specs shopper mini cart test js     part of   ,0
154191,13540661399.0,IssuesEvent,2020-09-16 14:55:42,golang/go,https://api.github.com/repos/golang/go,opened,cmd/go: revise 'go help' documentation for modules and module-aware commands,Documentation NeedsFix modules,"`go help modules` (and equivalently https://golang.org/cmd/go/#hdr-Modules__module_versions__and_more) is the original reference page for modules. It's fairly long for an introduction, but at the same time, it doesn't go into enough detail or provide enough examples to be a thorough reference.

https://golang.org/ref/mod is intended to replace `go help modules` as a detailed reference. In Go 1.16, we should change `go help modules` to point to that.

A few other help pages have this problem, in particular, `go help module-get` (https://golang.org/cmd/go/#hdr-Add_dependencies_to_current_module_and_install_them). The help page for each command should provide a brief synopsis of its arguments and flags, then should point to reference documentation like https://golang.org/ref/mod#go-get for more detail.",1.0,"cmd/go: revise 'go help' documentation for modules and module-aware commands - `go help modules` (and equivalently https://golang.org/cmd/go/#hdr-Modules__module_versions__and_more) is the original reference page for modules. It's fairly long for an introduction, but at the same time, it doesn't go into enough detail or provide enough examples to be a thorough reference.

https://golang.org/ref/mod is intended to replace `go help modules` as a detailed reference. In Go 1.16, we should change `go help modules` to point to that.

A few other help pages have this problem, in particular, `go help module-get` (https://golang.org/cmd/go/#hdr-Add_dependencies_to_current_module_and_install_them). The help page for each command should provide a brief synopsis of its arguments and flags, then should point to reference documentation like https://golang.org/ref/mod#go-get for more detail.",1,cmd go  revise  go help  documentation for modules and module aware commands    go help modules   and equivalently   is the original reference page for modules  it s fairly long for an introduction  but at the same time  it doesn t go into enough detail or provide enough examples to be a thorough reference       is intended to replace  go help modules  as a detailed reference  in go      we should change  go help modules  to point to that     a few other help pages have this problem  in particular   go help module get     the help page for each command should provide a brief synopsis of its arguments and flags  then should point to reference documentation like   for more detail ,1
10218,8852276353.0,IssuesEvent,2019-01-08 17:53:10,MicrosoftDocs/azure-docs,https://api.github.com/repos/MicrosoftDocs/azure-docs,closed,Endpoint Host Name not working,cognitive-services/svc cxp product-issue triaged,"What do I enter for my Host Name ? 
I am entering the full URL which works from PostMan. 
However, it is not working from the Test In Web Chat tool in Azure. 
The full url below I have entered in Host Name. 
https://jw2qnamakerservice.azurewebsites.net/qnamaker/knowledgebases/aa1fae26-94d6-4028-b4bd-8d8174d29f6d/generateAnswer

When I enter the chat question ....
""How do I programmatically update my Knowledge Base?""
I always get the same bad response of ...
No good match in FAQ.

Why is this ? Am I supposed to enter the full URL above for the Host Name ? 

Note: My PostMan call works perfectly but NOT from Azure.
Please help !!
Thanks 
James




---
#### Document Details

⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*

* ID: f45d867c-c72a-c619-b58a-777ff5f8c5c1
* Version Independent ID: e0f90b85-14bb-0925-c50b-b1d31dd9388a
* Content: [QnA bot - Azure Bot Service - QnA Maker - Azure Cognitive Services](https://docs.microsoft.com/en-us/azure/cognitive-services/qnamaker/tutorials/create-qna-bot)
* Content Source: [articles/cognitive-services/QnAMaker/Tutorials/create-qna-bot.md](https://github.com/Microsoft/azure-docs/blob/master/articles/cognitive-services/QnAMaker/Tutorials/create-qna-bot.md)
* Service: **cognitive-services**
* GitHub Login: @tulasim88
* Microsoft Alias: **tulasim**",1.0,"Endpoint Host Name not working - What do I enter for my Host Name ? 
I am entering the full URL which works from PostMan. 
However, it is not working from the Test In Web Chat tool in Azure. 
The full url below I have entered in Host Name. 
https://jw2qnamakerservice.azurewebsites.net/qnamaker/knowledgebases/aa1fae26-94d6-4028-b4bd-8d8174d29f6d/generateAnswer

When I enter the chat question ....
""How do I programmatically update my Knowledge Base?""
I always get the same bad response of ...
No good match in FAQ.

Why is this ? Am I supposed to enter the full URL above for the Host Name ? 

Note: My PostMan call works perfectly but NOT from Azure.
Please help !!
Thanks 
James




---
#### Document Details

⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*

* ID: f45d867c-c72a-c619-b58a-777ff5f8c5c1
* Version Independent ID: e0f90b85-14bb-0925-c50b-b1d31dd9388a
* Content: [QnA bot - Azure Bot Service - QnA Maker - Azure Cognitive Services](https://docs.microsoft.com/en-us/azure/cognitive-services/qnamaker/tutorials/create-qna-bot)
* Content Source: [articles/cognitive-services/QnAMaker/Tutorials/create-qna-bot.md](https://github.com/Microsoft/azure-docs/blob/master/articles/cognitive-services/QnAMaker/Tutorials/create-qna-bot.md)
* Service: **cognitive-services**
* GitHub Login: @tulasim88
* Microsoft Alias: **tulasim**",0,endpoint host name not working   what do i enter for my host name    i am entering the full url which works from postman   however  it is not working from the test in web chat tool in azure   the full url below i have entered in host name      when i enter the chat question       how do i programmatically update my knowledge base   i always get the same bad response of     no good match in faq   why is this   am i supposed to enter the full url above for the host name     note  my postman call works perfectly but not from azure  please help    thanks  james              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     github login       microsoft alias    tulasim  ,0
25485,5169270239.0,IssuesEvent,2017-01-18 00:14:20,golang/go,https://api.github.com/repos/golang/go,closed,doc: mention required OS changes in the release notes,Documentation OS-Plan9,"### What version of Go are you using (`go version`)?

Go 1.8 release candidate 1.

### What operating system and processor architecture are you using (`go env`)?
Plan 9 from Bell Labs, any supported architecture.

### What did you do?

Attempted to run net_test.go

### What did you expect to see?

Overwhelming and unrelenting success

### What did you see instead?

FAIL: TestConnClose because of an unknown control request

### Epilogue

In the draft release notes for Go 1.8[1], we get the following:

> The Plan 9 port's networking support is now much more complete and matches the behavior of Unix and Windows with respect to deadlines and cancelation. 

Sounds great! but it fails to mention that this change requires modification of the OS itself; specifically, as described in a Go commit message[2], which refers to (but does not specify) a different Github repository entirely, as 'the' Plan 9 kernel[3].  This change is not present in the latest ISO made available by Bell Labs.

In the end, it's a simple change that other Plan 9 kernels can easily accomodate, but it would be very kind of you if this sort of OS-scope change were at least mentioned somewhere in the release notes, even if it's just a tiny asterisk with an href to a changelog somewhere.  It would save us some detective work, and make it easier for us to use Go.


[1] https://beta.golang.org/doc/go1.8
[2] https://github.com/golang/go/commit/3d1ae4b75c77a88ba3b20ada874f1027365a8060
[3] https://github.com/0intro/plan9-contrib/commit/390a902aece1c009c614d3fdb3757e0470a93304",1.0,"doc: mention required OS changes in the release notes - ### What version of Go are you using (`go version`)?

Go 1.8 release candidate 1.

### What operating system and processor architecture are you using (`go env`)?
Plan 9 from Bell Labs, any supported architecture.

### What did you do?

Attempted to run net_test.go

### What did you expect to see?

Overwhelming and unrelenting success

### What did you see instead?

FAIL: TestConnClose because of an unknown control request

### Epilogue

In the draft release notes for Go 1.8[1], we get the following:

> The Plan 9 port's networking support is now much more complete and matches the behavior of Unix and Windows with respect to deadlines and cancelation. 

Sounds great! but it fails to mention that this change requires modification of the OS itself; specifically, as described in a Go commit message[2], which refers to (but does not specify) a different Github repository entirely, as 'the' Plan 9 kernel[3].  This change is not present in the latest ISO made available by Bell Labs.

In the end, it's a simple change that other Plan 9 kernels can easily accomodate, but it would be very kind of you if this sort of OS-scope change were at least mentioned somewhere in the release notes, even if it's just a tiny asterisk with an href to a changelog somewhere.  It would save us some detective work, and make it easier for us to use Go.


[1] https://beta.golang.org/doc/go1.8
[2] https://github.com/golang/go/commit/3d1ae4b75c77a88ba3b20ada874f1027365a8060
[3] https://github.com/0intro/plan9-contrib/commit/390a902aece1c009c614d3fdb3757e0470a93304",1,doc  mention required os changes in the release notes       what version of go are you using   go version       go     release candidate           what operating system and processor architecture are you using   go env     plan   from bell labs  any supported architecture         what did you do     attempted to run net test go        what did you expect to see     overwhelming and unrelenting success        what did you see instead     fail  testconnclose because of an unknown control request        epilogue    in the draft release notes for go       we get the following       the plan   port s networking support is now much more complete and matches the behavior of unix and windows with respect to deadlines and cancelation      sounds great  but it fails to mention that this change requires modification of the os itself  specifically  as described in a go commit message   which refers to  but does not specify  a different github repository entirely  as  the  plan   kernel    this change is not present in the latest iso made available by bell labs     in the end  it s a simple change that other plan   kernels can easily accomodate  but it would be very kind of you if this sort of os scope change were at least mentioned somewhere in the release notes  even if it s just a tiny asterisk with an href to a changelog somewhere   it would save us some detective work  and make it easier for us to use go                    ,1
52595,6642923667.0,IssuesEvent,2017-09-27 09:19:46,nebula-orchestrator/worker-manager,https://api.github.com/repos/nebula-orchestrator/worker-manager,opened,Support for multiple authenticated registries ,design,"Currently Nebula only support one docker registry auth, not yet sure how but support for multiple authenticated registries might be needed in some cases. ",1.0,"Support for multiple authenticated registries  - Currently Nebula only support one docker registry auth, not yet sure how but support for multiple authenticated registries might be needed in some cases. ",0,support for multiple authenticated registries    currently nebula only support one docker registry auth  not yet sure how but support for multiple authenticated registries might be needed in some cases  ,0
87368,10544380364.0,IssuesEvent,2019-10-02 16:48:15,golang/go,https://api.github.com/repos/golang/go,closed,net/http: document Request.Host value in HTTP/2,Documentation NeedsFix,"HTTP/2 has `:authority` rather than Host, but I presume the Request.Host filed is filled in with that value for HTTP/2 requests. That should be documented.

/cc @bradfitz ",1.0,"net/http: document Request.Host value in HTTP/2 - HTTP/2 has `:authority` rather than Host, but I presume the Request.Host filed is filled in with that value for HTTP/2 requests. That should be documented.

/cc @bradfitz ",1,net http  document request host value in http     http   has   authority  rather than host  but i presume the request host filed is filled in with that value for http   requests  that should be documented      cc  bradfitz ,1
32860,4792388995.0,IssuesEvent,2016-10-31 15:24:50,cockroachdb/cockroach,https://api.github.com/repos/cockroachdb/cockroach,closed,: TestJoinReader failed under stress,Robot test-failure,"SHA: https://github.com/cockroachdb/cockroach/commits/7207111aa3a43df0552509365fdec741a53f873f

Stress build found a failed test:

```
I161030 06:35:37.442188 562 gossip/gossip.go:237  [n?] initial resolvers: []
W161030 06:35:37.443146 562 gossip/gossip.go:1055  [n?] no resolvers found; use --join to specify a connected node
W161030 06:35:37.455658 562 server/status/runtime.go:116  Could not parse build timestamp: parsing time """" as ""2006/01/02 15:04:05"": cannot parse """" as ""2006""
I161030 06:35:37.459180 562 storage/engine/rocksdb.go:340  opening in memory rocksdb instance
I161030 06:35:37.460050 562 server/config.go:432  1 storage engine initialized
I161030 06:35:37.467786 562 server/node.go:420  [n?] store [n0,s0] not bootstrapped
I161030 06:35:37.480769 587 storage/replica_proposal.go:292  [s1,r1/1:/M{in-ax}] new range lease replica {1 1 1} 1970-01-01 00:00:00 +0000 UTC 410502h35m46.479007435s following replica {0 0 0} 1970-01-01 00:00:00 +0000 UTC 0s [physicalTime=2016-10-30 06:35:37.480640097 +0000 UTC]
I161030 06:35:37.483821 562 util/stop/stopper.go:383  stop has been called, stopping or quiescing all running tasks
I161030 06:35:37.484438 562 server/node.go:349  [n?] **** cluster {e49c0a14-5c43-4a56-bb7e-6c22a624d43f} has been created
I161030 06:35:37.484479 562 server/node.go:350  [n?] **** add additional nodes by specifying --join=127.0.0.1:47360
I161030 06:35:37.486324 562 base/node_id.go:62  [n1] NodeID set to 1
I161030 06:35:37.523959 562 server/node.go:433  [n1] initialized store [n1,s1]: {Capacity:536870912 Available:536870912 RangeCount:0}
I161030 06:35:37.524992 562 server/node.go:318  [n1] node ID 1 initialized
I161030 06:35:37.525058 502 storage/split_queue.go:103  [n1,split,s1,r1/1:/M{in-ax}] splitting at keys [/Table/11/0 /Table/12/0 /Table/13/0 /Table/14/0]
I161030 06:35:37.525207 562 gossip/gossip.go:280  [n1] NodeDescriptor set to node_id:1 address:<network_field:""tcp"" address_field:""127.0.0.1:47360"" > attrs:<> locality:<> 
I161030 06:35:37.525579 562 storage/stores.go:296  [n1] read 0 node addresses from persistent storage
I161030 06:35:37.525740 562 server/node.go:563  [n1] connecting to gossip network to verify cluster ID...
I161030 06:35:37.525844 562 server/node.go:584  [n1] node connected via gossip and verified as part of cluster {""e49c0a14-5c43-4a56-bb7e-6c22a624d43f""}
I161030 06:35:37.531802 562 server/node.go:368  [n1] node=1: started with [[]=] engine(s) and attributes []
I161030 06:35:37.532398 562 server/server.go:590  [n1] starting https server at 127.0.0.1:45029
I161030 06:35:37.532464 562 server/server.go:591  [n1] starting grpc/postgres server at 127.0.0.1:47360
I161030 06:35:37.532515 562 server/server.go:592  [n1] advertising CockroachDB node at 127.0.0.1:47360
I161030 06:35:37.542832 502 storage/replica_command.go:2363  [n1,split,s1,r1/1:/M{in-ax}] initiating a split of this range at key /Table/11 [r2]
I161030 06:35:37.637833 608 sql/event_log.go:95  [n1] Event: ""node_join"", target: 1, info: {Descriptor:{NodeID:1 Address:{NetworkField:tcp AddressField:127.0.0.1:47360} Attrs: Locality:} ClusterID:{UUID:e49c0a14-5c43-4a56-bb7e-6c22a624d43f} StartedAt:1477809337525972178}
I161030 06:35:37.738528 502 storage/replica_command.go:2363  [n1,split,s1,r1/1:/{Min-Table/11}] initiating a split of this range at key /Table/12 [r3]
I161030 06:35:37.762328 502 storage/replica_command.go:2363  [n1,split,s1,r1/1:/{Min-Table/11}] initiating a split of this range at key /Table/13 [r4]
I161030 06:35:37.786836 502 storage/replica_command.go:2363  [n1,split,s1,r1/1:/{Min-Table/11}] initiating a split of this range at key /Table/14 [r5]
W161030 06:35:37.622599 558 util/hlc/hlc.go:167  backward time jump detected (-0.201562 seconds)
I161030 06:35:37.624077 562 util/stop/stopper.go:383  stop has been called, stopping or quiescing all running tasks
I161030 06:35:37.624642 630 kv/transport_race.go:71  transport race promotion: ran 18 iterations on up to 95 requests
I161030 06:35:37.625862 509 http2_server.go:276  transport: http2Server.HandleStreams failed to read frame: read tcp 127.0.0.1:47360->127.0.0.1:48312: use of closed network connection
    <autogenerated>:12: error executing 'CREATE DATABASE IF NOT EXISTS test;CREATE TABLE test.t (a INT, b INT, sum INT, s STRING, PRIMARY KEY (a,b), INDEX bs (b,s));': pq: storage/store.go:2192: rejecting command with timestamp in the future: 1477809337824056937 (200.776541ms ahead)
```
",1.0,": TestJoinReader failed under stress - SHA: https://github.com/cockroachdb/cockroach/commits/7207111aa3a43df0552509365fdec741a53f873f

Stress build found a failed test:

```
I161030 06:35:37.442188 562 gossip/gossip.go:237  [n?] initial resolvers: []
W161030 06:35:37.443146 562 gossip/gossip.go:1055  [n?] no resolvers found; use --join to specify a connected node
W161030 06:35:37.455658 562 server/status/runtime.go:116  Could not parse build timestamp: parsing time """" as ""2006/01/02 15:04:05"": cannot parse """" as ""2006""
I161030 06:35:37.459180 562 storage/engine/rocksdb.go:340  opening in memory rocksdb instance
I161030 06:35:37.460050 562 server/config.go:432  1 storage engine initialized
I161030 06:35:37.467786 562 server/node.go:420  [n?] store [n0,s0] not bootstrapped
I161030 06:35:37.480769 587 storage/replica_proposal.go:292  [s1,r1/1:/M{in-ax}] new range lease replica {1 1 1} 1970-01-01 00:00:00 +0000 UTC 410502h35m46.479007435s following replica {0 0 0} 1970-01-01 00:00:00 +0000 UTC 0s [physicalTime=2016-10-30 06:35:37.480640097 +0000 UTC]
I161030 06:35:37.483821 562 util/stop/stopper.go:383  stop has been called, stopping or quiescing all running tasks
I161030 06:35:37.484438 562 server/node.go:349  [n?] **** cluster {e49c0a14-5c43-4a56-bb7e-6c22a624d43f} has been created
I161030 06:35:37.484479 562 server/node.go:350  [n?] **** add additional nodes by specifying --join=127.0.0.1:47360
I161030 06:35:37.486324 562 base/node_id.go:62  [n1] NodeID set to 1
I161030 06:35:37.523959 562 server/node.go:433  [n1] initialized store [n1,s1]: {Capacity:536870912 Available:536870912 RangeCount:0}
I161030 06:35:37.524992 562 server/node.go:318  [n1] node ID 1 initialized
I161030 06:35:37.525058 502 storage/split_queue.go:103  [n1,split,s1,r1/1:/M{in-ax}] splitting at keys [/Table/11/0 /Table/12/0 /Table/13/0 /Table/14/0]
I161030 06:35:37.525207 562 gossip/gossip.go:280  [n1] NodeDescriptor set to node_id:1 address:<network_field:""tcp"" address_field:""127.0.0.1:47360"" > attrs:<> locality:<> 
I161030 06:35:37.525579 562 storage/stores.go:296  [n1] read 0 node addresses from persistent storage
I161030 06:35:37.525740 562 server/node.go:563  [n1] connecting to gossip network to verify cluster ID...
I161030 06:35:37.525844 562 server/node.go:584  [n1] node connected via gossip and verified as part of cluster {""e49c0a14-5c43-4a56-bb7e-6c22a624d43f""}
I161030 06:35:37.531802 562 server/node.go:368  [n1] node=1: started with [[]=] engine(s) and attributes []
I161030 06:35:37.532398 562 server/server.go:590  [n1] starting https server at 127.0.0.1:45029
I161030 06:35:37.532464 562 server/server.go:591  [n1] starting grpc/postgres server at 127.0.0.1:47360
I161030 06:35:37.532515 562 server/server.go:592  [n1] advertising CockroachDB node at 127.0.0.1:47360
I161030 06:35:37.542832 502 storage/replica_command.go:2363  [n1,split,s1,r1/1:/M{in-ax}] initiating a split of this range at key /Table/11 [r2]
I161030 06:35:37.637833 608 sql/event_log.go:95  [n1] Event: ""node_join"", target: 1, info: {Descriptor:{NodeID:1 Address:{NetworkField:tcp AddressField:127.0.0.1:47360} Attrs: Locality:} ClusterID:{UUID:e49c0a14-5c43-4a56-bb7e-6c22a624d43f} StartedAt:1477809337525972178}
I161030 06:35:37.738528 502 storage/replica_command.go:2363  [n1,split,s1,r1/1:/{Min-Table/11}] initiating a split of this range at key /Table/12 [r3]
I161030 06:35:37.762328 502 storage/replica_command.go:2363  [n1,split,s1,r1/1:/{Min-Table/11}] initiating a split of this range at key /Table/13 [r4]
I161030 06:35:37.786836 502 storage/replica_command.go:2363  [n1,split,s1,r1/1:/{Min-Table/11}] initiating a split of this range at key /Table/14 [r5]
W161030 06:35:37.622599 558 util/hlc/hlc.go:167  backward time jump detected (-0.201562 seconds)
I161030 06:35:37.624077 562 util/stop/stopper.go:383  stop has been called, stopping or quiescing all running tasks
I161030 06:35:37.624642 630 kv/transport_race.go:71  transport race promotion: ran 18 iterations on up to 95 requests
I161030 06:35:37.625862 509 http2_server.go:276  transport: http2Server.HandleStreams failed to read frame: read tcp 127.0.0.1:47360->127.0.0.1:48312: use of closed network connection
    <autogenerated>:12: error executing 'CREATE DATABASE IF NOT EXISTS test;CREATE TABLE test.t (a INT, b INT, sum INT, s STRING, PRIMARY KEY (a,b), INDEX bs (b,s));': pq: storage/store.go:2192: rejecting command with timestamp in the future: 1477809337824056937 (200.776541ms ahead)
```
",0,  testjoinreader failed under stress   sha     stress build found a failed test                   gossip gossip go      initial resolvers                gossip gossip go      no resolvers found  use   join to specify a connected node             server status runtime go    could not parse build timestamp  parsing time    as                cannot parse    as                 storage engine rocksdb go    opening in memory rocksdb instance             server config go      storage engine initialized             server node go      store   not bootstrapped             storage replica proposal go      new range lease replica                        utc     following replica                        utc                 util stop stopper go    stop has been called  stopping or quiescing all running tasks             server node go           cluster             has been created             server node go           add additional nodes by specifying   join                       base node id go      nodeid set to               server node go      initialized store     capacity   available   rangecount                server node go      node id   initialized             storage split queue go      splitting at keys               gossip gossip go      nodedescriptor set to node id   address   attrs   locality                storage stores go      read   node addresses from persistent storage             server node go      connecting to gossip network to verify cluster id                server node go      node connected via gossip and verified as part of cluster                           server node go      node    started with     engine s  and attributes               server server go      starting https server at                       server server go      starting grpc postgres server at                       server server go      advertising cockroachdb node at                       storage replica command go      initiating a split of this range at key  table                 sql event log go      event   node join   target     info   descriptor  nodeid   address  networkfield tcp addressfield            attrs  locality   clusterid  uuid            startedat                storage replica command go      initiating a split of this range at key  table                 storage replica command go      initiating a split of this range at key  table                 storage replica command go      initiating a split of this range at key  table                 util hlc hlc go    backward time jump detected       seconds              util stop stopper go    stop has been called  stopping or quiescing all running tasks             kv transport race go    transport race promotion  ran   iterations on up to   requests               server go    transport    handlestreams failed to read frame  read tcp                       use of closed network connection          error executing  create database if not exists test create table test t  a int  b int  sum int  s string  primary key  a b   index bs  b s      pq  storage store go    rejecting command with timestamp in the future         ahead      ,0
250492,21302237135.0,IssuesEvent,2022-04-15 05:53:55,Azure/sonic-mgmt,https://api.github.com/repos/Azure/sonic-mgmt,closed,[Test Gap] Cover dualtor topology in PR testing,Test gap,"<!--
If you are reporting a new issue, make sure that we do not have any duplicates
already open. You can ensure this by searching the issue list for this
repository. If there is a duplicate, please close your issue and add a comment
to the existing issue instead.

If you suspect your issue is a bug, please edit your issue description to
include the BUG REPORT INFORMATION shown below. If you fail to provide this
information within 7 days, we cannot debug your issue and will close it. We
will, however, reopen it if you later provide the information.

For more information about reporting issues, see
https://github.com/Azure/SONiC/wiki#report-issues

---------------------------------------------------
GENERAL SUPPORT INFORMATION
---------------------------------------------------

The GitHub issue tracker is for bug reports and feature requests.
General support can be found at the following locations:

- SONiC Support Forums - https://groups.google.com/forum/#!forum/sonicproject

---------------------------------------------------
BUG REPORT INFORMATION
---------------------------------------------------
Use the commands below to provide key information from your environment:
You do NOT have to include this information if this is a FEATURE REQUEST
-->

**Description**

<!--
Briefly describe the problem you are having in a few paragraphs.
-->

Currently the sonic-mgmt PR testing covers t0, t1-lag and sonic-t0. 
It would be better to cover the dualtor topology as well to run dualtor specific tests.

**Steps to reproduce the issue:**
1.
2.
3.

**Describe the results you received:**


**Describe the results you expected:**


**Additional information you deem important:**
<!--
software/ASIC/Hardware Flatform version and info
-->
    **Output of `show version`:**

    ```
    (paste your output here)
    ```

    **Attach debug file `sudo generate_dump`:**

    ```
    (paste your output here)
    ```
",1.0,"[Test Gap] Cover dualtor topology in PR testing - <!--
If you are reporting a new issue, make sure that we do not have any duplicates
already open. You can ensure this by searching the issue list for this
repository. If there is a duplicate, please close your issue and add a comment
to the existing issue instead.

If you suspect your issue is a bug, please edit your issue description to
include the BUG REPORT INFORMATION shown below. If you fail to provide this
information within 7 days, we cannot debug your issue and will close it. We
will, however, reopen it if you later provide the information.

For more information about reporting issues, see
https://github.com/Azure/SONiC/wiki#report-issues

---------------------------------------------------
GENERAL SUPPORT INFORMATION
---------------------------------------------------

The GitHub issue tracker is for bug reports and feature requests.
General support can be found at the following locations:

- SONiC Support Forums - https://groups.google.com/forum/#!forum/sonicproject

---------------------------------------------------
BUG REPORT INFORMATION
---------------------------------------------------
Use the commands below to provide key information from your environment:
You do NOT have to include this information if this is a FEATURE REQUEST
-->

**Description**

<!--
Briefly describe the problem you are having in a few paragraphs.
-->

Currently the sonic-mgmt PR testing covers t0, t1-lag and sonic-t0. 
It would be better to cover the dualtor topology as well to run dualtor specific tests.

**Steps to reproduce the issue:**
1.
2.
3.

**Describe the results you received:**


**Describe the results you expected:**


**Additional information you deem important:**
<!--
software/ASIC/Hardware Flatform version and info
-->
    **Output of `show version`:**

    ```
    (paste your output here)
    ```

    **Attach debug file `sudo generate_dump`:**

    ```
    (paste your output here)
    ```
",0,  cover dualtor topology in pr testing         if you are reporting a new issue  make sure that we do not have any duplicates  already open  you can ensure this by searching the issue list for this  repository  if there is a duplicate  please close your issue and add a comment  to the existing issue instead     if you suspect your issue is a bug  please edit your issue description to  include the bug report information shown below  if you fail to provide this  information within   days  we cannot debug your issue and will close it  we  will  however  reopen it if you later provide the information     for more information about reporting issues  see                                                            general support information                                                         the github issue tracker is for bug reports and feature requests   general support can be found at the following locations       sonic support forums                                                             bug report information                                                       use the commands below to provide key information from your environment   you do not have to include this information if this is a feature request           description            briefly describe the problem you are having in a few paragraphs          currently the sonic mgmt pr testing covers      lag and sonic      it would be better to cover the dualtor topology as well to run dualtor specific tests       steps to reproduce the issue                     describe the results you received           describe the results you expected           additional information you deem important           software asic hardware flatform version and info             output of  show version                      paste your output here                    attach debug file  sudo generate dump                      paste your output here            ,0
353305,10551245101.0,IssuesEvent,2019-10-03 12:57:54,wso2/ballerina-integrator,https://api.github.com/repos/wso2/ballerina-integrator,closed,Modify Salesforce templates and guides,Priority/High Severity/Blocker,"**Description:**
Modify Salesforce templates and guides with the latest changes.

**Suggested Labels:**
<!-- Optional comma separated list of suggested labels. Non committers can’t assign labels to issues, so this will help issue creators who are not a committer to suggest possible labels-->

**Suggested Assignees:**
<!--Optional comma separated list of suggested team members who should attend the issue. Non committers can’t assign issues to assignees, so this will help issue creators who are not a committer to suggest possible assignees-->

**Affected Product Version:**

**OS, DB, other environment details and versions:**    

**Steps to reproduce:**


**Related Issues:**
<!-- Any related issues such as sub tasks, issues reported in other repositories (e.g component repositories), similar problems, etc. -->",1.0,"Modify Salesforce templates and guides - **Description:**
Modify Salesforce templates and guides with the latest changes.

**Suggested Labels:**
<!-- Optional comma separated list of suggested labels. Non committers can’t assign labels to issues, so this will help issue creators who are not a committer to suggest possible labels-->

**Suggested Assignees:**
<!--Optional comma separated list of suggested team members who should attend the issue. Non committers can’t assign issues to assignees, so this will help issue creators who are not a committer to suggest possible assignees-->

**Affected Product Version:**

**OS, DB, other environment details and versions:**    

**Steps to reproduce:**


**Related Issues:**
<!-- Any related issues such as sub tasks, issues reported in other repositories (e.g component repositories), similar problems, etc. -->",0,modify salesforce templates and guides     description     modify salesforce templates and guides with the latest changes       suggested labels            suggested assignees            affected product version         os  db  other environment details and versions             steps to reproduce           related issues      ,0
111143,14009967056.0,IssuesEvent,2020-10-29 03:46:58,dotnet/roslyn,https://api.github.com/repos/dotnet/roslyn,closed,Compilation errors cause CI to fail,Area-Infrastructure Resolution-By Design,This is a tracking issue for builds that fail due to _compiler_ errors.,1.0,Compilation errors cause CI to fail - This is a tracking issue for builds that fail due to _compiler_ errors.,0,compilation errors cause ci to fail   this is a tracking issue for builds that fail due to  compiler  errors ,0
653642,21609501947.0,IssuesEvent,2022-05-04 08:38:08,kubernetes/website,https://api.github.com/repos/kubernetes/website,closed,Blog post: historical context of the dockershim removal,kind/feature priority/important-longterm area/blog triage/accepted,"~If you aren't @amye don't assign yourself to this~

## Description 

The dockershim removal is a confusing change to communicate: why is Dockershim in Kubernetes to begin with? How is Docker as a company related to this change, 

Write a blog post describing the historical context of why dockershim was in Kubernetes in the first place, why the project is choosing to remove and deprecate it (and how that benefits both the ecosystem and the project in the long run), and how this is a chance for the community to come together in support of open standards.

Some points to highlight:
- moving towards open standards like crictl is in line with our open source philosophy!
- as is deprecating vendor-specific code!
- docker still works inside containers!
- ... and more!

## Concerns

Let @amye handle this one, as we want to make sure to message this correctly. 

## Due date 

Somewhere in the 1.24 cycle Mid to late March
",1.0,"Blog post: historical context of the dockershim removal - ~If you aren't @amye don't assign yourself to this~

## Description 

The dockershim removal is a confusing change to communicate: why is Dockershim in Kubernetes to begin with? How is Docker as a company related to this change, 

Write a blog post describing the historical context of why dockershim was in Kubernetes in the first place, why the project is choosing to remove and deprecate it (and how that benefits both the ecosystem and the project in the long run), and how this is a chance for the community to come together in support of open standards.

Some points to highlight:
- moving towards open standards like crictl is in line with our open source philosophy!
- as is deprecating vendor-specific code!
- docker still works inside containers!
- ... and more!

## Concerns

Let @amye handle this one, as we want to make sure to message this correctly. 

## Due date 

Somewhere in the 1.24 cycle Mid to late March
",0,blog post  historical context of the dockershim removal    if you aren t  amye don t assign yourself to this        description     the dockershim removal is a confusing change to communicate  why is dockershim in kubernetes to begin with  how is docker as a company related to this change      write a blog post describing the historical context of why dockershim was in kubernetes in the first place  why the project is choosing to remove and deprecate it  and how that benefits both the ecosystem and the project in the long run   and how this is a chance for the community to come together in support of open standards     some points to highlight     moving towards open standards like crictl is in line with our open source philosophy     as is deprecating vendor specific code     docker still works inside containers         and more        concerns    let  amye handle this one  as we want to make sure to message this correctly         due date     somewhere in the     cycle mid to late march  ,0
56017,8041276508.0,IssuesEvent,2018-07-31 01:58:08,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: clarify documentation for -replace flag,Documentation NeedsFix modules,"Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
go version devel +b59b42cee8 Tue Jul 17 10:07:18 2018 +0000 darwin/amd64

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?
GOARCH=""amd64""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""~/go""
GOMOD=""~/mystuff/meli/go.mod""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/p5/56z0g6pj6dq0njc1n6wccz4r0000gn/T/go-build722725015=/tmp/go-build -gno-record-gcc-switches -fno-common""


### What did you do?
try to use a go module replacement to point to a local repository

`git clone https://github.com/pkg/errors to a place outside GOPATH`
`in your application's go.mod file add a replace directive to point to the cloned github.com/pkg/errors`
`cat go.mod`
```bash
replace github.com/pkg/errors => ../errors
```
`try to build your application`

### What did you expect to see?
- my application to build succefully without problem(using the cloned errors package)

### What did you see instead?
```bash
go: parsing ../errors/go.mod: open ~/mystuff/errors/go.mod: no such file or directory
go: error loading module requirements
```

However, if I manually add a go.mod file to the cloned errors package
```bash
echo 'module ""github.com/pkg/errors""' >> ~/mystuff/errors/go.mod
```
I'm able to build my application using that local errors package.",1.0,"cmd/go: clarify documentation for -replace flag - Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
go version devel +b59b42cee8 Tue Jul 17 10:07:18 2018 +0000 darwin/amd64

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?
GOARCH=""amd64""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""~/go""
GOMOD=""~/mystuff/meli/go.mod""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/p5/56z0g6pj6dq0njc1n6wccz4r0000gn/T/go-build722725015=/tmp/go-build -gno-record-gcc-switches -fno-common""


### What did you do?
try to use a go module replacement to point to a local repository

`git clone https://github.com/pkg/errors to a place outside GOPATH`
`in your application's go.mod file add a replace directive to point to the cloned github.com/pkg/errors`
`cat go.mod`
```bash
replace github.com/pkg/errors => ../errors
```
`try to build your application`

### What did you expect to see?
- my application to build succefully without problem(using the cloned errors package)

### What did you see instead?
```bash
go: parsing ../errors/go.mod: open ~/mystuff/errors/go.mod: no such file or directory
go: error loading module requirements
```

However, if I manually add a go.mod file to the cloned errors package
```bash
echo 'module ""github.com/pkg/errors""' >> ~/mystuff/errors/go.mod
```
I'm able to build my application using that local errors package.",1,cmd go  clarify documentation for  replace flag   please answer these questions before submitting your issue  thanks           what version of go are you using   go version     go version devel    tue jul              darwin          does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env     goarch      gohostarch      gohostos  darwin   goos  darwin   gopath    go   gomod    mystuff meli go mod   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders     t go    tmp go build  gno record gcc switches  fno common           what did you do   try to use a go module replacement to point to a local repository     git clone   to a place outside gopath    in your application s go mod file add a replace directive to point to the cloned github com pkg errors    cat go mod      bash  replace github com pkg errors       errors        try to build your application         what did you expect to see     my application to build succefully without problem using the cloned errors package         what did you see instead      bash  go  parsing    errors go mod  open   mystuff errors go mod  no such file or directory  go  error loading module requirements         however  if i manually add a go mod file to the cloned errors package     bash  echo  module  github com pkg errors        mystuff errors go mod       i m able to build my application using that local errors package ,1
137178,12747259467.0,IssuesEvent,2020-06-26 17:32:53,golang/go,https://api.github.com/repos/golang/go,closed,doc: BuildNameToCertificate deprecated in go 1.14 not mentioned in the release notes,Documentation NeedsFix help wanted,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/shi03/Library/Caches/go-build""
GOENV=""/Users/shi03/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/shi03/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/Cellar/go/1.14/libexec""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/1.14/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/shi03/code/apis/gs/capi/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/dc/pxx2c5t503jdfy7c29qrlmp9nkvqm9/T/go-build781481956=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?
Looks like the `BuildNameToCertificate` function was deprecated in 1.14 but there's no mention of this on the release page.


### What did you expect to see?
Release page mentioning the deprecated


### What did you see instead?
No mention of the deprecation
",1.0,"doc: BuildNameToCertificate deprecated in go 1.14 not mentioned in the release notes - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/shi03/Library/Caches/go-build""
GOENV=""/Users/shi03/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/shi03/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/Cellar/go/1.14/libexec""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/Cellar/go/1.14/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/shi03/code/apis/gs/capi/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/dc/pxx2c5t503jdfy7c29qrlmp9nkvqm9/T/go-build781481956=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?
Looks like the `BuildNameToCertificate` function was deprecated in 1.14 but there's no mention of this on the release page.


### What did you expect to see?
Release page mentioning the deprecated


### What did you see instead?
No mention of the deprecation
",1,doc  buildnametocertificate deprecated in go     not mentioned in the release notes         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version            go version  go version     darwin             does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   users   library caches go build   goenv   users   library application support go env   goexe     goflags     gohostarch      gohostos  darwin   goinsecure     gonoproxy     gonosumdb     goos  darwin   gopath   users   go   goprivate     goproxy     goroot   usr local cellar go     libexec   gosumdb  sum golang org   gotmpdir     gotooldir   usr local cellar go     libexec pkg tool darwin     gccgo  gccgo   ar  ar   cc  clang   cxx  clang     cgo enabled      gomod   users   code apis gs capi go mod   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders dc   t go    tmp go build  gno record gcc switches  fno common             what did you do   looks like the  buildnametocertificate  function was deprecated in     but there s no mention of this on the release page           what did you expect to see   release page mentioning the deprecated          what did you see instead   no mention of the deprecation  ,1
61977,17023823801.0,IssuesEvent,2021-07-03 04:02:31,tomhughes/trac-tickets,https://api.github.com/repos/tomhughes/trac-tickets,closed,Wrong province(state) in address even after is_in tag is specified,Component: nominatim Priority: minor Resolution: duplicate Type: defect,"**[Submitted to the original trac issue database at 1.55am, Monday, 17th September 2012]**

After fixing the issue that was ticket #4557, I'm now noticing that Nominatim is picking the wrong, adjacent province for the addresses for many of the cities in Gyeonggi-do (Gyeonggi Province). Here are a few examples.

Dongducheon:
http://nominatim.openstreetmap.org/details.php?place_id=3977812

This city is well within Gyeonggi-do's border, yet it's being listed under Gangwon-do.

Paju:
http://nominatim.openstreetmap.org/details.php?place_id=2688795

This one simply doesn't have any province assigned to it.

Anseong:
http://nominatim.openstreetmap.org/details.php?place_id=3226407

This one shows up to be under Chungcheongbuk-do.


What's interesting to note is that these nodes are linked to admin borders, and these properly list them under Gyeonggi-do:
http://nominatim.openstreetmap.org/details.php?place_id=2486970788
http://nominatim.openstreetmap.org/details.php?place_id=2486970801
http://nominatim.openstreetmap.org/details.php?place_id=2486970785

I'm suspecting that Gyeonggi-do node...
http://nominatim.openstreetmap.org/details.php?place_id=2487216741

...is somehow not properly assigned to the cities. I've even explicitly put is_in tags in the city nodes as FAQ suggested, but it didn't do any good.",1.0,"Wrong province(state) in address even after is_in tag is specified - **[Submitted to the original trac issue database at 1.55am, Monday, 17th September 2012]**

After fixing the issue that was ticket #4557, I'm now noticing that Nominatim is picking the wrong, adjacent province for the addresses for many of the cities in Gyeonggi-do (Gyeonggi Province). Here are a few examples.

Dongducheon:
http://nominatim.openstreetmap.org/details.php?place_id=3977812

This city is well within Gyeonggi-do's border, yet it's being listed under Gangwon-do.

Paju:
http://nominatim.openstreetmap.org/details.php?place_id=2688795

This one simply doesn't have any province assigned to it.

Anseong:
http://nominatim.openstreetmap.org/details.php?place_id=3226407

This one shows up to be under Chungcheongbuk-do.


What's interesting to note is that these nodes are linked to admin borders, and these properly list them under Gyeonggi-do:
http://nominatim.openstreetmap.org/details.php?place_id=2486970788
http://nominatim.openstreetmap.org/details.php?place_id=2486970801
http://nominatim.openstreetmap.org/details.php?place_id=2486970785

I'm suspecting that Gyeonggi-do node...
http://nominatim.openstreetmap.org/details.php?place_id=2487216741

...is somehow not properly assigned to the cities. I've even explicitly put is_in tags in the city nodes as FAQ suggested, but it didn't do any good.",0,wrong province state  in address even after is in tag is specified          after fixing the issue that was ticket     i m now noticing that nominatim is picking the wrong  adjacent province for the addresses for many of the cities in gyeonggi do  gyeonggi province   here are a few examples     dongducheon        this city is well within gyeonggi do s border  yet it s being listed under gangwon do     paju        this one simply doesn t have any province assigned to it     anseong        this one shows up to be under chungcheongbuk do       what s interesting to note is that these nodes are linked to admin borders  and these properly list them under gyeonggi do              i m suspecting that gyeonggi do node             is somehow not properly assigned to the cities  i ve even explicitly put is in tags in the city nodes as faq suggested  but it didn t do any good ,0
243481,18715692345.0,IssuesEvent,2021-11-03 04:07:15,golang/go,https://api.github.com/repos/golang/go,closed,x/exp/event: poor package comment,Documentation NeedsFix,"I ran `go doc` in x/exp/event to see what it does. This is what is reported for the package comment:

```
% go doc 
package event // import ""golang.org/x/exp/event""

Package event provides the core functionality for observability that allows
libraries using it to interact well. It enforces the middle layer
interchange format, but allows both frontend wrappers and back end exporters
to customize the usage.
...
%
```

I learned nothing from this. Please provide a package comment that explains the purpose of the package.
",1.0,"x/exp/event: poor package comment - I ran `go doc` in x/exp/event to see what it does. This is what is reported for the package comment:

```
% go doc 
package event // import ""golang.org/x/exp/event""

Package event provides the core functionality for observability that allows
libraries using it to interact well. It enforces the middle layer
interchange format, but allows both frontend wrappers and back end exporters
to customize the usage.
...
%
```

I learned nothing from this. Please provide a package comment that explains the purpose of the package.
",1,x exp event  poor package comment   i ran  go doc  in x exp event to see what it does  this is what is reported for the package comment            go doc   package event    import  golang org x exp event     package event provides the core functionality for observability that allows  libraries using it to interact well  it enforces the middle layer  interchange format  but allows both frontend wrappers and back end exporters  to customize the usage                  i learned nothing from this  please provide a package comment that explains the purpose of the package   ,1
11540,3497345965.0,IssuesEvent,2016-01-06 00:29:21,golang/go,https://api.github.com/repos/golang/go,opened,doc: write gomote wiki docs,Documentation,"Document how to use gomote for all common tasks for all major OS types.

/cc @randall77 ",1.0,"doc: write gomote wiki docs - Document how to use gomote for all common tasks for all major OS types.

/cc @randall77 ",1,doc  write gomote wiki docs   document how to use gomote for all common tasks for all major os types      cc    ,1
111727,14140449959.0,IssuesEvent,2020-11-10 11:13:17,SAP/fundamental-ngx,https://api.github.com/repos/SAP/fundamental-ngx,closed,Bug: Responsive design-behavior for Mobile is not aligned with Visual core,bug design_team platform,"#### Is this a bug, enhancement, or feature request?
Bug, and enhancement


#### Briefly describe your proposal.

** Issue** 
Looking at the ""Page Responsive Behavior"" section - It's not aligned with Visual core breaking points and visuals for Mobile. It doesn't work when I shrank the screen.
Issue: 
![Screen Shot 2020-11-04 at 3 28 29 PM](https://user-images.githubusercontent.com/72403541/98178912-49010300-1f06-11eb-9b42-42fdf6e55347.png)

Please refer to Visual core: https://wiki.wdf.sap.corp/wiki/pages/viewpage.action?pageId=2039387288
![DynamicPage_SizeSAnatomy](https://user-images.githubusercontent.com/72403541/98174079-ece5b100-1efc-11eb-9f0a-5b317cb1d5cb.png)


",1.0,"Bug: Responsive design-behavior for Mobile is not aligned with Visual core - #### Is this a bug, enhancement, or feature request?
Bug, and enhancement


#### Briefly describe your proposal.

** Issue** 
Looking at the ""Page Responsive Behavior"" section - It's not aligned with Visual core breaking points and visuals for Mobile. It doesn't work when I shrank the screen.
Issue: 
![Screen Shot 2020-11-04 at 3 28 29 PM](https://user-images.githubusercontent.com/72403541/98178912-49010300-1f06-11eb-9b42-42fdf6e55347.png)

Please refer to Visual core: https://wiki.wdf.sap.corp/wiki/pages/viewpage.action?pageId=2039387288
![DynamicPage_SizeSAnatomy](https://user-images.githubusercontent.com/72403541/98174079-ece5b100-1efc-11eb-9f0a-5b317cb1d5cb.png)


",0,bug  responsive design behavior for mobile is not aligned with visual core        is this a bug  enhancement  or feature request   bug  and enhancement           briefly describe your proposal        issue     looking at the  page responsive behavior  section   it s not aligned with visual core breaking points and visuals for mobile  it doesn t work when i shrank the screen   issue            please refer to visual core               ,0
653416,21581837000.0,IssuesEvent,2022-05-02 19:37:09,metabase/metabase,https://api.github.com/repos/metabase/metabase,closed,Inconsistent colors in relative datetime filtering in sidebar,Type:Bug Priority:P3 Querying/Parameters & Variables .Frontend Querying/GUI,"[From @mazameli 's comment here](https://github.com/metabase/metabase/pull/22323#issuecomment-1115166895)

This purple hover state should be blue in this case:

<img width=""294"" alt=""image"" src=""https://user-images.githubusercontent.com/2223916/166296653-1fa0c4ed-c023-4ccd-8981-f297669d884d.png"">

The tabs here in the sidebar context should be purple here to match the sidebar theme:

<img width=""377"" alt=""image"" src=""https://user-images.githubusercontent.com/2223916/166296705-b74c1f42-0a03-4f0a-bdaa-68a650b0127e.png"">",1.0,"Inconsistent colors in relative datetime filtering in sidebar - [From @mazameli 's comment here](https://github.com/metabase/metabase/pull/22323#issuecomment-1115166895)

This purple hover state should be blue in this case:

<img width=""294"" alt=""image"" src=""https://user-images.githubusercontent.com/2223916/166296653-1fa0c4ed-c023-4ccd-8981-f297669d884d.png"">

The tabs here in the sidebar context should be purple here to match the sidebar theme:

<img width=""377"" alt=""image"" src=""https://user-images.githubusercontent.com/2223916/166296705-b74c1f42-0a03-4f0a-bdaa-68a650b0127e.png"">",0,inconsistent colors in relative datetime filtering in sidebar          this purple hover state should be blue in this case      img width     alt  image  src       the tabs here in the sidebar context should be purple here to match the sidebar theme      img width     alt  image  src   ,0
55414,7986133616.0,IssuesEvent,2018-07-19 00:12:45,golang/go,https://api.github.com/repos/golang/go,closed,doc: update FAQ,Documentation NeedsFix,"At the moment, just after the launch of Go 1.11 beta 1, the FAQ needs tidying. Much of the prose is about the earliest parts of the project, and the associated tone isn't right. Meanwhile, much of the modern success story is missing. As a trivial example, surely a project like Kubernetes should be mentioned, and Google's internal use is more extensive than the corresponding question implies.

The discussion of Go 2 needs updating, and so on.

I'll assign this to myself but am happy to review updates from others. I only ask we keep the answers concise; it's a FAQ, not a manual or design document.",1.0,"doc: update FAQ - At the moment, just after the launch of Go 1.11 beta 1, the FAQ needs tidying. Much of the prose is about the earliest parts of the project, and the associated tone isn't right. Meanwhile, much of the modern success story is missing. As a trivial example, surely a project like Kubernetes should be mentioned, and Google's internal use is more extensive than the corresponding question implies.

The discussion of Go 2 needs updating, and so on.

I'll assign this to myself but am happy to review updates from others. I only ask we keep the answers concise; it's a FAQ, not a manual or design document.",1,doc  update faq   at the moment  just after the launch of go     beta    the faq needs tidying  much of the prose is about the earliest parts of the project  and the associated tone isn t right  meanwhile  much of the modern success story is missing  as a trivial example  surely a project like kubernetes should be mentioned  and google s internal use is more extensive than the corresponding question implies     the discussion of go   needs updating  and so on     i ll assign this to myself but am happy to review updates from others  i only ask we keep the answers concise  it s a faq  not a manual or design document ,1
753028,26338336185.0,IssuesEvent,2023-01-10 15:51:49,poissonconsulting/fwatlasbc,https://api.github.com/repos/poissonconsulting/fwatlasbc,opened,Ensure `fwa_join_stream_segments()` and other such functions keep columns the same for blk,Difficulty: 2 Intermediate Effort: 2 Medium Priority: 2 High,"currently drops stream name but this is unique for blk in the input data.

This is best down by implementing a distinct function in tidy plus to also keep uniques.",1.0,"Ensure `fwa_join_stream_segments()` and other such functions keep columns the same for blk - currently drops stream name but this is unique for blk in the input data.

This is best down by implementing a distinct function in tidy plus to also keep uniques.",0,ensure  fwa join stream segments    and other such functions keep columns the same for blk   currently drops stream name but this is unique for blk in the input data     this is best down by implementing a distinct function in tidy plus to also keep uniques ,0
5760,2967627843.0,IssuesEvent,2015-07-13 02:05:26,golang/go,https://api.github.com/repos/golang/go,closed,"doc: answer ""Why isn't x is the standard library?""",Documentation,"This question comes up a lot. It'd be nice to have a canonical answer or set of answers that we can just link to. I don't know whether it belongs in the FAQ or the contributing page or the wiki. Probably the latter.

I don't think I'm the right person to write the first draft, although I'm happy to add to it. @bradfitz, maybe?

",1.0,"doc: answer ""Why isn't x is the standard library?"" - This question comes up a lot. It'd be nice to have a canonical answer or set of answers that we can just link to. I don't know whether it belongs in the FAQ or the contributing page or the wiki. Probably the latter.

I don't think I'm the right person to write the first draft, although I'm happy to add to it. @bradfitz, maybe?

",1,doc  answer  why isn t x is the standard library     this question comes up a lot  it d be nice to have a canonical answer or set of answers that we can just link to  i don t know whether it belongs in the faq or the contributing page or the wiki  probably the latter     i don t think i m the right person to write the first draft  although i m happy to add to it   bradfitz  maybe     ,1
182162,14901663565.0,IssuesEvent,2021-01-21 16:42:50,golang/go,https://api.github.com/repos/golang/go,closed,x/blog:Only direct dependencies are recorded in the go.mod file: needs a recheck.,Documentation WaitingForInfo,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ 1.15.6 darwin/amd64

</pre>

### Does this issue reproduce with the latest release?

N/A

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ N/A

</pre></details>

### What did you do?
cat go. mod
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->



### What did you expect to see?

Only direct dependencies

### What did you see instead?
Both direct and indirect dependency.

### Update the go blog
Udert the Sub-heading ""Adding a dependency"",
I think the statement ""Only direct dependencies are recorded in the go.mod file"" is misleading or contradictory. A better explanation should be found for this. Thanks.",1.0,"x/blog:Only direct dependencies are recorded in the go.mod file: needs a recheck. - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ 1.15.6 darwin/amd64

</pre>

### Does this issue reproduce with the latest release?

N/A

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ N/A

</pre></details>

### What did you do?
cat go. mod
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->



### What did you expect to see?

Only direct dependencies

### What did you see instead?
Both direct and indirect dependency.

### Update the go blog
Udert the Sub-heading ""Adding a dependency"",
I think the statement ""Only direct dependencies are recorded in the go.mod file"" is misleading or contradictory. A better explanation should be found for this. Thanks.",1,x blog only direct dependencies are recorded in the go mod file  needs a recheck          please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version                  darwin               does this issue reproduce with the latest release     n a        what operating system and processor architecture are you using   go env          go env  output       n a              what did you do   cat go  mod        if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best                  what did you expect to see     only direct dependencies        what did you see instead   both direct and indirect dependency         update the go blog  udert the sub heading  adding a dependency    i think the statement  only direct dependencies are recorded in the go mod file  is misleading or contradictory  a better explanation should be found for this  thanks ,1
62464,8613956615.0,IssuesEvent,2018-11-19 16:16:12,golang/go,https://api.github.com/repos/golang/go,closed,cmd/link: difference between s.P and s.Size,Documentation,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?
go version devel +66fa0ae2e6 Thu Nov 8 14:29:02 2018 -0600 aix/ppc64

### Does this issue reproduce with the latest release?
I don't know. But I think so. 


### What operating system and processor architecture are you using (`go env`)?
I'm on aix/ppc64. But I've quickly tried on linux/amd64 and I have the same issue. 

### What did you do?
This is linked with //go:cgo_import_dynamic. My program looks like this:

```
package main

import (
 	""fmt""
 	_ ""unsafe""
)

//go:cgo_import_dynamic libc_exit exit ""libc.so""
//go:linkname libc_exit libc_exit

var libc_exit uintptr

func main() {
	 fmt.Printf(""0x%x\n"", &libc_exit)
}
```

During XCOFF creation (doxcoff), I'm trying to add a relocation from ""libc_exit"" symbol to a new needed symbol ""exit"". (The same can be done in doelf on linux/amd64)
My code looks like: 

```
s := ctxt.Syms.Lookup(""libc_exit"", 0)
extsym := ctxt.Syms.Lookup(s.Extname(), 0)
// setup of extsym
s.AddAddr(ctxt.Arch, extsym) 
```

Before this operation, s.Size = 8 and len(s.P) = 0. I'm not sure if it's wanted but as libc_exit is linkname to a bss symbol, it's not that strange. 
Therefore, when I do s.AddAddr(ctxt.Arch, extsym), I've s.Size = 16 and len(s.P) = 16. But I don't want that as the relocation will be at off = 8 and ""libc_exit"" should have only 8 bytes. 

So, I've tried with s.SetAddr(ctxt.Arch, 0, extsym) to set these 8 bytes. But in this case, during relocsym I've this error: 
libc_exit: invalid relocation exit: 0+8 not in [0,0) (numbers in order: r.Off, s.Size, 0, len(s.P)) 
because s.P isn't growth during this operation. 
If I increase s.P manually, everything is OK: 
```
s.AddBytes(make([]byte, 8))
s.SetAddr(ctxt.Arch, 0, extsym)
```


Therefore, I'm understanding it's not possible to create such relocation with the current sym functions. This might not be a problem, but the second behavior doesn't seem intended. Is this a bug ? 


",1.0,"cmd/link: difference between s.P and s.Size - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?
go version devel +66fa0ae2e6 Thu Nov 8 14:29:02 2018 -0600 aix/ppc64

### Does this issue reproduce with the latest release?
I don't know. But I think so. 


### What operating system and processor architecture are you using (`go env`)?
I'm on aix/ppc64. But I've quickly tried on linux/amd64 and I have the same issue. 

### What did you do?
This is linked with //go:cgo_import_dynamic. My program looks like this:

```
package main

import (
 	""fmt""
 	_ ""unsafe""
)

//go:cgo_import_dynamic libc_exit exit ""libc.so""
//go:linkname libc_exit libc_exit

var libc_exit uintptr

func main() {
	 fmt.Printf(""0x%x\n"", &libc_exit)
}
```

During XCOFF creation (doxcoff), I'm trying to add a relocation from ""libc_exit"" symbol to a new needed symbol ""exit"". (The same can be done in doelf on linux/amd64)
My code looks like: 

```
s := ctxt.Syms.Lookup(""libc_exit"", 0)
extsym := ctxt.Syms.Lookup(s.Extname(), 0)
// setup of extsym
s.AddAddr(ctxt.Arch, extsym) 
```

Before this operation, s.Size = 8 and len(s.P) = 0. I'm not sure if it's wanted but as libc_exit is linkname to a bss symbol, it's not that strange. 
Therefore, when I do s.AddAddr(ctxt.Arch, extsym), I've s.Size = 16 and len(s.P) = 16. But I don't want that as the relocation will be at off = 8 and ""libc_exit"" should have only 8 bytes. 

So, I've tried with s.SetAddr(ctxt.Arch, 0, extsym) to set these 8 bytes. But in this case, during relocsym I've this error: 
libc_exit: invalid relocation exit: 0+8 not in [0,0) (numbers in order: r.Off, s.Size, 0, len(s.P)) 
because s.P isn't growth during this operation. 
If I increase s.P manually, everything is OK: 
```
s.AddBytes(make([]byte, 8))
s.SetAddr(ctxt.Arch, 0, extsym)
```


Therefore, I'm understanding it's not possible to create such relocation with the current sym functions. This might not be a problem, but the second behavior doesn't seem intended. Is this a bug ? 


",1,cmd link  difference between s p and s size            what version of go are you using   go version     go version devel    thu nov              aix          does this issue reproduce with the latest release   i don t know  but i think so            what operating system and processor architecture are you using   go env     i m on aix    but i ve quickly tried on linux   and i have the same issue          what did you do   this is linked with   go cgo import dynamic  my program looks like this          package main    import     	 fmt    	   unsafe          go cgo import dynamic libc exit exit  libc so     go linkname libc exit libc exit    var libc exit uintptr    func main      	 fmt printf    x n    libc exit             during xcoff creation  doxcoff   i m trying to add a relocation from  libc exit  symbol to a new needed symbol  exit    the same can be done in doelf on linux     my code looks like           s    ctxt syms lookup  libc exit       extsym    ctxt syms lookup s extname           setup of extsym  s addaddr ctxt arch  extsym           before this operation  s size     and len s p       i m not sure if it s wanted but as libc exit is linkname to a bss symbol  it s not that strange    therefore  when i do s addaddr ctxt arch  extsym   i ve s size     and len s p       but i don t want that as the relocation will be at off     and  libc exit  should have only   bytes      so  i ve tried with s setaddr ctxt arch     extsym  to set these   bytes  but in this case  during relocsym i ve this error    libc exit  invalid relocation exit      not in        numbers in order  r off  s size     len s p     because s p isn t growth during this operation    if i increase s p manually  everything is ok         s addbytes make  byte       s setaddr ctxt arch     extsym            therefore  i m understanding it s not possible to create such relocation with the current sym functions  this might not be a problem  but the second behavior doesn t seem intended  is this a bug         ,1
475460,13710653970.0,IssuesEvent,2020-10-02 01:47:37,mandarineorg/mandarinets,https://api.github.com/repos/mandarineorg/mandarinets,closed,Remove all tsconfig dependencies.,High Priority,"It really feels like https://github.com/denoland/deno/issues/7732 will be the final choice to make, more than a proposal it feels like a warning. Mandarine needs to be non-dependent on a `tsconfig.json` file as soon as possible. The only dependencies it should have is `emitDecoratorMetadata` and `experimentalDecorators` which _should be_ easy to address when `tsconfig.json` is removed",1.0,"Remove all tsconfig dependencies. - It really feels like https://github.com/denoland/deno/issues/7732 will be the final choice to make, more than a proposal it feels like a warning. Mandarine needs to be non-dependent on a `tsconfig.json` file as soon as possible. The only dependencies it should have is `emitDecoratorMetadata` and `experimentalDecorators` which _should be_ easy to address when `tsconfig.json` is removed",0,remove all tsconfig dependencies    it really feels like   will be the final choice to make  more than a proposal it feels like a warning  mandarine needs to be non dependent on a  tsconfig json  file as soon as possible  the only dependencies it should have is  emitdecoratormetadata  and  experimentaldecorators  which  should be  easy to address when  tsconfig json  is removed,0
390623,11551086386.0,IssuesEvent,2020-02-19 00:19:28,googleapis/java-conformance-tests,https://api.github.com/repos/googleapis/java-conformance-tests,closed,Synthesis failed for java-conformance-tests,autosynth failure priority: p1 type: bug,"Hello! Autosynth couldn't regenerate java-conformance-tests. :broken_heart:

Here's the output from running `synth.py`:

```
Cloning into 'working_repo'...
Switched to branch 'autosynth'
Running synthtool
['/tmpfs/src/git/autosynth/env/bin/python3', '-m', 'synthtool', 'synth.py', '--']
synthtool > Executing /tmpfs/src/git/autosynth/working_repo/synth.py.
On branch autosynth
nothing to commit, working tree clean
HEAD detached at FETCH_HEAD
nothing to commit, working tree clean
synthtool > Ensuring dependencies.
synthtool > Pulling artman image.
latest: Pulling from googleapis/artman
Digest: sha256:6aec9c34db0e4be221cdaf6faba27bdc07cfea846808b3d3b964dfce3a9a0f9b
Status: Image is up to date for googleapis/artman:latest
synthtool > Wrote metadata to synth.metadata.
Traceback (most recent call last):
  File ""/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py"", line 193, in _run_module_as_main
    ""__main__"", mod_spec)
  File ""/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py"", line 85, in _run_code
    exec(code, run_globals)
  File ""/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/__main__.py"", line 102, in <module>
    main()
  File ""/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py"", line 764, in __call__
    return self.main(*args, **kwargs)
  File ""/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py"", line 717, in main
    rv = self.invoke(ctx)
  File ""/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py"", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File ""/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py"", line 555, in invoke
    return callback(*args, **kwargs)
  File ""/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/__main__.py"", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File ""<frozen importlib._bootstrap_external>"", line 678, in exec_module
  File ""<frozen importlib._bootstrap>"", line 205, in _call_with_frames_removed
  File ""/tmpfs/src/git/autosynth/working_repo/synth.py"", line 24, in <module>
    templates = common_templates.java_library()
  File ""/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/gcp/common.py"", line 75, in java_library
    return self._generic_library(""java_library"", **kwargs)
  File ""/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/gcp/common.py"", line 43, in _generic_library
    if not kwargs[""metadata""][""samples""]:
KeyError: 'samples'

Synthesis failed

```

Google internal developers can see the full log [here](https://sponge/7769bc45-4de7-4c4e-8e43-b07e6b6eba12).
",1.0,"Synthesis failed for java-conformance-tests - Hello! Autosynth couldn't regenerate java-conformance-tests. :broken_heart:

Here's the output from running `synth.py`:

```
Cloning into 'working_repo'...
Switched to branch 'autosynth'
Running synthtool
['/tmpfs/src/git/autosynth/env/bin/python3', '-m', 'synthtool', 'synth.py', '--']
synthtool > Executing /tmpfs/src/git/autosynth/working_repo/synth.py.
On branch autosynth
nothing to commit, working tree clean
HEAD detached at FETCH_HEAD
nothing to commit, working tree clean
synthtool > Ensuring dependencies.
synthtool > Pulling artman image.
latest: Pulling from googleapis/artman
Digest: sha256:6aec9c34db0e4be221cdaf6faba27bdc07cfea846808b3d3b964dfce3a9a0f9b
Status: Image is up to date for googleapis/artman:latest
synthtool > Wrote metadata to synth.metadata.
Traceback (most recent call last):
  File ""/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py"", line 193, in _run_module_as_main
    ""__main__"", mod_spec)
  File ""/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py"", line 85, in _run_code
    exec(code, run_globals)
  File ""/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/__main__.py"", line 102, in <module>
    main()
  File ""/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py"", line 764, in __call__
    return self.main(*args, **kwargs)
  File ""/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py"", line 717, in main
    rv = self.invoke(ctx)
  File ""/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py"", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File ""/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py"", line 555, in invoke
    return callback(*args, **kwargs)
  File ""/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/__main__.py"", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File ""<frozen importlib._bootstrap_external>"", line 678, in exec_module
  File ""<frozen importlib._bootstrap>"", line 205, in _call_with_frames_removed
  File ""/tmpfs/src/git/autosynth/working_repo/synth.py"", line 24, in <module>
    templates = common_templates.java_library()
  File ""/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/gcp/common.py"", line 75, in java_library
    return self._generic_library(""java_library"", **kwargs)
  File ""/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/gcp/common.py"", line 43, in _generic_library
    if not kwargs[""metadata""][""samples""]:
KeyError: 'samples'

Synthesis failed

```

Google internal developers can see the full log [here](https://sponge/7769bc45-4de7-4c4e-8e43-b07e6b6eba12).
",0,synthesis failed for java conformance tests   hello  autosynth couldn t regenerate java conformance tests   broken heart   here s the output from running  synth py        cloning into  working repo     switched to branch  autosynth  running synthtool   synthtool   executing  tmpfs src git autosynth working repo synth py  on branch autosynth nothing to commit  working tree clean head detached at fetch head nothing to commit  working tree clean synthtool   ensuring dependencies  synthtool   pulling artman image  latest  pulling from googleapis artman digest      status  image is up to date for googleapis artman latest synthtool   wrote metadata to synth metadata  traceback  most recent call last     file   home kbuilder  pyenv versions       lib     runpy py   line    in  run module as main        main     mod spec    file   home kbuilder  pyenv versions       lib     runpy py   line    in  run code     exec code  run globals    file   tmpfs src git autosynth env lib     site packages synthtool   main   py   line    in       main     file   tmpfs src git autosynth env lib     site packages click core py   line    in   call       return self main  args    kwargs    file   tmpfs src git autosynth env lib     site packages click core py   line    in main     rv   self invoke ctx    file   tmpfs src git autosynth env lib     site packages click core py   line    in invoke     return ctx invoke self callback    ctx params    file   tmpfs src git autosynth env lib     site packages click core py   line    in invoke     return callback  args    kwargs    file   tmpfs src git autosynth env lib     site packages synthtool   main   py   line    in main     spec loader exec module synth module     type  ignore   file      line    in exec module   file      line    in  call with frames removed   file   tmpfs src git autosynth working repo synth py   line    in       templates   common templates java library     file   tmpfs src git autosynth env lib     site packages synthtool gcp common py   line    in java library     return self  generic library  java library     kwargs    file   tmpfs src git autosynth env lib     site packages synthtool gcp common py   line    in  generic library     if not kwargs    keyerror   samples   synthesis failed       google internal developers can see the full log     ,0
138012,12804091440.0,IssuesEvent,2020-07-03 03:13:50,golang/go,https://api.github.com/repos/golang/go,closed,"doc: in Go memory model ""threads"" should read ""goroutines""",Documentation NeedsInvestigation,"`doc/go_mem.html` uses `threads` instead of `goroutines` in two places. I think they should read ""goroutines""

```
diff --git a/doc/go_mem.html b/doc/go_mem.html
index 143f3b2ff2..c1ec9e3c47 100644
--- a/doc/go_mem.html
+++ b/doc/go_mem.html
@@ -385,7 +385,7 @@ before call <i>n</i>+1 to <code>l.Lock</code>.
 The <code>sync</code> package provides a safe mechanism for
 initialization in the presence of multiple goroutines
 through the use of the <code>Once</code> type.
-Multiple threads can execute <code>once.Do(f)</code> for a particular <code>f</code>,
+Multiple goroutines can execute <code>once.Do(f)</code> for a particular <code>f</code>,
 but only one will run <code>f()</code>, and the other calls block
 until <code>f()</code> has returned.
 </p>
@@ -525,7 +525,7 @@ implies observing the write to <code>a</code>, so this program could
 print an empty string too.
 Worse, there is no guarantee that the write to <code>done</code> will ever
 be observed by <code>main</code>, since there are no synchronization
-events between the two threads.  The loop in <code>main</code> is not
+events between the two goroutines.  The loop in <code>main</code> is not
 guaranteed to finish.
 </p>
```

",1.0,"doc: in Go memory model ""threads"" should read ""goroutines"" - `doc/go_mem.html` uses `threads` instead of `goroutines` in two places. I think they should read ""goroutines""

```
diff --git a/doc/go_mem.html b/doc/go_mem.html
index 143f3b2ff2..c1ec9e3c47 100644
--- a/doc/go_mem.html
+++ b/doc/go_mem.html
@@ -385,7 +385,7 @@ before call <i>n</i>+1 to <code>l.Lock</code>.
 The <code>sync</code> package provides a safe mechanism for
 initialization in the presence of multiple goroutines
 through the use of the <code>Once</code> type.
-Multiple threads can execute <code>once.Do(f)</code> for a particular <code>f</code>,
+Multiple goroutines can execute <code>once.Do(f)</code> for a particular <code>f</code>,
 but only one will run <code>f()</code>, and the other calls block
 until <code>f()</code> has returned.
 </p>
@@ -525,7 +525,7 @@ implies observing the write to <code>a</code>, so this program could
 print an empty string too.
 Worse, there is no guarantee that the write to <code>done</code> will ever
 be observed by <code>main</code>, since there are no synchronization
-events between the two threads.  The loop in <code>main</code> is not
+events between the two goroutines.  The loop in <code>main</code> is not
 guaranteed to finish.
 </p>
```

",1,doc  in go memory model  threads  should read  goroutines     doc go mem html  uses  threads  instead of  goroutines  in two places  i think they should read  goroutines          diff   git a doc go mem html b doc go mem html  index             a doc go mem html      b doc go mem html                  before call  n    to  l lock     the  sync  package provides a safe mechanism for   initialization in the presence of multiple goroutines   through the use of the  once  type    multiple threads can execute  once do f   for a particular  f     multiple goroutines can execute  once do f   for a particular  f     but only one will run  f     and the other calls block   until  f    has returned                       implies observing the write to  a   so this program could   print an empty string too    worse  there is no guarantee that the write to  done  will ever   be observed by  main   since there are no synchronization   events between the two threads   the loop in  main  is not   events between the two goroutines   the loop in  main  is not   guaranteed to finish              ,1
5748,2966644198.0,IssuesEvent,2015-07-12 03:23:03,golang/go,https://api.github.com/repos/golang/go,closed,flag: Document that FlagSet.Arg(int) and Arg(int) returns empty string if arg doesn't exist,Documentation,I thought it wasn't obvious these functions should return empty string rather than have some other behavior like panic (as would happen when trying to access a non-existent member of os.Args[]),1.0,flag: Document that FlagSet.Arg(int) and Arg(int) returns empty string if arg doesn't exist - I thought it wasn't obvious these functions should return empty string rather than have some other behavior like panic (as would happen when trying to access a non-existent member of os.Args[]),1,flag  document that flagset arg int  and arg int  returns empty string if arg doesn t exist   i thought it wasn t obvious these functions should return empty string rather than have some other behavior like panic  as would happen when trying to access a non existent member of os args  ,1
183267,6685731079.0,IssuesEvent,2017-10-07 00:14:22,samsung-cnct/kraken,https://api.github.com/repos/samsung-cnct/kraken,closed,"release tarballs for kraken cli tool are now getting created with a capital ""K""",bug kraken priority-p1,"This seems to be new. The following list is not exhaustive and I surmise that given the sampling below the issue is systemic in the build now.

`$ for f in {k,g}*gz;do echo $f;tar tvfz $f;done`
```
k2cli_1.1.0_darwin_amd64.tar.gz
-rwxr-xr-x root/root  11862592 2017-09-15 13:35 Kraken
k2cli-release_1.0.9_linux_amd64.tar.gz . # <<--- old build which is lower case
-rwxr-xr-x root/root  11843443 2017-08-25 11:11 k2cli
kraken-rel_1.1.0_linux_amd64.tar.gz
-rwxr-xr-x root/root  11871460 2017-09-15 13:35 Kraken
gox_1.1.0_darwin_amd64.tar.gz
-rwxr-xr-x root/root   3121424 2017-09-15 13:35 Kraken
```",1.0,"release tarballs for kraken cli tool are now getting created with a capital ""K"" - This seems to be new. The following list is not exhaustive and I surmise that given the sampling below the issue is systemic in the build now.

`$ for f in {k,g}*gz;do echo $f;tar tvfz $f;done`
```
k2cli_1.1.0_darwin_amd64.tar.gz
-rwxr-xr-x root/root  11862592 2017-09-15 13:35 Kraken
k2cli-release_1.0.9_linux_amd64.tar.gz . # <<--- old build which is lower case
-rwxr-xr-x root/root  11843443 2017-08-25 11:11 k2cli
kraken-rel_1.1.0_linux_amd64.tar.gz
-rwxr-xr-x root/root  11871460 2017-09-15 13:35 Kraken
gox_1.1.0_darwin_amd64.tar.gz
-rwxr-xr-x root/root   3121424 2017-09-15 13:35 Kraken
```",0,release tarballs for kraken cli tool are now getting created with a capital  k    this seems to be new  the following list is not exhaustive and i surmise that given the sampling below the issue is systemic in the build now        for f in  k g  gz do echo  f tar tvfz  f done                darwin   tar gz   rwxr xr x root root              kraken    release       linux   tar gz           old build which is lower case   rwxr xr x root root                 kraken rel       linux   tar gz   rwxr xr x root root              kraken  gox       darwin   tar gz   rwxr xr x root root               kraken     ,0
47146,24888896671.0,IssuesEvent,2022-10-28 10:09:07,oracle/truffleruby,https://api.github.com/repos/oracle/truffleruby,opened,Ripper is slow on TruffleRuby,performance sulong-issue,"The cause is pretty clear, here it's from running the `ruby-lsp` benchmark (with `gem ""syntax_tree"", ""4.0.2""`):
```
ruby --engine.TraceCompilation -Iharness benchmarks/ruby-lsp/benchmark.rb |& grep 'opt fail'
[engine] opt failed id=72976 Lexer#advance                                      |Tier 1|Time  560(-2478665+2479225)ms|Reason: org.graalvm.compiler.truffle.compiler.GraphTooBigBailoutException: Graph too big to safely compile. Node count: 114422. Graph Size: 150001. Limit: 150000.|Timestamp 2479225288001|Src lexer.rb:11303
[engine] opt failed id=72976 Lexer#advance                                      |Tier 1|Time  431(-2479231+2479661)ms|Reason: org.graalvm.compiler.truffle.compiler.GraphTooBigBailoutException: Graph too big to safely compile. Node count: 114420. Graph Size: 150001. Limit: 150000.|Timestamp 2479661412740|Src lexer.rb:11303

[engine] opt failed id=18998 ripper_yyparse                                     |Tier 1|Time 5389(-2477447+2482836)ms|Reason: org.graalvm.compiler.truffle.compiler.GraphTooBigBailoutException: Graph too big to safely compile. Node count: 142162. Graph Size: 150003. Limit: 150000.|Timestamp 2482836050637|Src ripper.c:6157
[engine] opt failed id=18998 ripper_yyparse                                     |Tier 1|Time 6142(-2482840+2488982)ms|Reason: org.graalvm.compiler.truffle.compiler.GraphTooBigBailoutException: Graph too big to safely compile. Node count: 142364. Graph Size: 150002. Limit: 150000.|Timestamp 2488982502244|Src ripper.c:6157
```
The first two relate to https://github.com/oracle/truffleruby/issues/2290#issuecomment-1277796067 / https://github.com/whitequark/parser/issues/871, a separate issue.

```
$ ruby --vm.XX:+PrintGCSummary --cpusampler --cpusampler.Delay=15000 --cpusampler.ShowTiers=true -Iharness benchmarks/ruby-lsp/benchmark.rb
...
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Thread[main,5,main]
 Name                                                                                                 ||             Total Time    |   T0   |   T1   |   T2   ||              Self Time    |   T0   |   T1   |   T2   || Location             
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 ripper_yyparse                                                                                       ||            16750ms  56.5% | 100.0% |   0.0% |   0.0% ||            10880ms  36.7% | 100.0% |   0.0% |   0.0% || ripper.c~6157:0
 RB_TYPE_P                                                                                            ||             2850ms   9.6% |   0.0% |  47.0% |  53.0% ||             2150ms   7.2% |   0.0% |  29.8% |  70.2% || object.c~21:0
 Lexer#advance                                                                                        ||             3120ms  10.5% | 100.0% |   0.0% |   0.0% ||             1760ms   5.9% | 100.0% |   0.0% |   0.0% || ../../.rubies/truffleruby-dev/lib/gems/gems/parser-3.1.2.1/lib/parser/lexer.rb~11303-24828:470723-833042
 Kernel#class                                                                                         ||              830ms   2.8% |   0.0% | 100.0% |   0.0% ||              830ms   2.8% |   0.0% | 100.0% |   0.0% || (core)~1:0
 BasicObject#!=                                                                                       ||              850ms   2.9% |  10.6% |  89.4% |   0.0% ||              770ms   2.6% |   3.9% |  96.1% |   0.0% || (core)~1:0
 Hash#[]                                                                                              ||              760ms   2.6% |  46.1% |  47.4% |   6.6% ||              440ms   1.5% |  45.5% |  43.2% |  11.4% || (core)~1:0
 Ripper#lineno                                                                                        ||              710ms   2.4% |  45.1% |  54.9% |   0.0% ||              350ms   1.2% |  40.0% |  60.0% |   0.0% || ../../.rubies/truffleruby-dev/lib/truffle/truffle/cext_ruby.rb~22:930-1002
 Hash#[]=                                                                                             ||              300ms   1.0% |  53.3% |  46.7% |   0.0% ||              290ms   1.0% |  51.7% |  48.3% |   0.0% || (core)~1:0
 Array#empty?                                                                                         ||              290ms   1.0% |   0.0% | 100.0% |   0.0% ||              290ms   1.0% |   0.0% | 100.0% |   0.0% || resource:/truffleruby/core/array.rb~398-400:9414-9445
```

@rschatz Does Sulong use [BlockNode](https://www.graalvm.org/truffle/javadoc/com/oracle/truffle/api/nodes/BlockNode.html) or could it? Maybe only for basic blocks without control flow? But I'm not sure it would help then.

BTW, it'd be useful if Sulong shows the end line of functions (even if it's an approximation), because `ripper.c~6157:0` doesn't tell us.",True,"Ripper is slow on TruffleRuby - The cause is pretty clear, here it's from running the `ruby-lsp` benchmark (with `gem ""syntax_tree"", ""4.0.2""`):
```
ruby --engine.TraceCompilation -Iharness benchmarks/ruby-lsp/benchmark.rb |& grep 'opt fail'
[engine] opt failed id=72976 Lexer#advance                                      |Tier 1|Time  560(-2478665+2479225)ms|Reason: org.graalvm.compiler.truffle.compiler.GraphTooBigBailoutException: Graph too big to safely compile. Node count: 114422. Graph Size: 150001. Limit: 150000.|Timestamp 2479225288001|Src lexer.rb:11303
[engine] opt failed id=72976 Lexer#advance                                      |Tier 1|Time  431(-2479231+2479661)ms|Reason: org.graalvm.compiler.truffle.compiler.GraphTooBigBailoutException: Graph too big to safely compile. Node count: 114420. Graph Size: 150001. Limit: 150000.|Timestamp 2479661412740|Src lexer.rb:11303

[engine] opt failed id=18998 ripper_yyparse                                     |Tier 1|Time 5389(-2477447+2482836)ms|Reason: org.graalvm.compiler.truffle.compiler.GraphTooBigBailoutException: Graph too big to safely compile. Node count: 142162. Graph Size: 150003. Limit: 150000.|Timestamp 2482836050637|Src ripper.c:6157
[engine] opt failed id=18998 ripper_yyparse                                     |Tier 1|Time 6142(-2482840+2488982)ms|Reason: org.graalvm.compiler.truffle.compiler.GraphTooBigBailoutException: Graph too big to safely compile. Node count: 142364. Graph Size: 150002. Limit: 150000.|Timestamp 2488982502244|Src ripper.c:6157
```
The first two relate to https://github.com/oracle/truffleruby/issues/2290#issuecomment-1277796067 / https://github.com/whitequark/parser/issues/871, a separate issue.

```
$ ruby --vm.XX:+PrintGCSummary --cpusampler --cpusampler.Delay=15000 --cpusampler.ShowTiers=true -Iharness benchmarks/ruby-lsp/benchmark.rb
...
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Thread[main,5,main]
 Name                                                                                                 ||             Total Time    |   T0   |   T1   |   T2   ||              Self Time    |   T0   |   T1   |   T2   || Location             
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 ripper_yyparse                                                                                       ||            16750ms  56.5% | 100.0% |   0.0% |   0.0% ||            10880ms  36.7% | 100.0% |   0.0% |   0.0% || ripper.c~6157:0
 RB_TYPE_P                                                                                            ||             2850ms   9.6% |   0.0% |  47.0% |  53.0% ||             2150ms   7.2% |   0.0% |  29.8% |  70.2% || object.c~21:0
 Lexer#advance                                                                                        ||             3120ms  10.5% | 100.0% |   0.0% |   0.0% ||             1760ms   5.9% | 100.0% |   0.0% |   0.0% || ../../.rubies/truffleruby-dev/lib/gems/gems/parser-3.1.2.1/lib/parser/lexer.rb~11303-24828:470723-833042
 Kernel#class                                                                                         ||              830ms   2.8% |   0.0% | 100.0% |   0.0% ||              830ms   2.8% |   0.0% | 100.0% |   0.0% || (core)~1:0
 BasicObject#!=                                                                                       ||              850ms   2.9% |  10.6% |  89.4% |   0.0% ||              770ms   2.6% |   3.9% |  96.1% |   0.0% || (core)~1:0
 Hash#[]                                                                                              ||              760ms   2.6% |  46.1% |  47.4% |   6.6% ||              440ms   1.5% |  45.5% |  43.2% |  11.4% || (core)~1:0
 Ripper#lineno                                                                                        ||              710ms   2.4% |  45.1% |  54.9% |   0.0% ||              350ms   1.2% |  40.0% |  60.0% |   0.0% || ../../.rubies/truffleruby-dev/lib/truffle/truffle/cext_ruby.rb~22:930-1002
 Hash#[]=                                                                                             ||              300ms   1.0% |  53.3% |  46.7% |   0.0% ||              290ms   1.0% |  51.7% |  48.3% |   0.0% || (core)~1:0
 Array#empty?                                                                                         ||              290ms   1.0% |   0.0% | 100.0% |   0.0% ||              290ms   1.0% |   0.0% | 100.0% |   0.0% || resource:/truffleruby/core/array.rb~398-400:9414-9445
```

@rschatz Does Sulong use [BlockNode](https://www.graalvm.org/truffle/javadoc/com/oracle/truffle/api/nodes/BlockNode.html) or could it? Maybe only for basic blocks without control flow? But I'm not sure it would help then.

BTW, it'd be useful if Sulong shows the end line of functions (even if it's an approximation), because `ripper.c~6157:0` doesn't tell us.",0,ripper is slow on truffleruby   the cause is pretty clear  here it s from running the  ruby lsp  benchmark  with  gem  syntax tree                    ruby   engine tracecompilation  iharness benchmarks ruby lsp benchmark rb    grep  opt fail     opt failed id   lexer advance                                       tier   time         ms reason  org graalvm compiler truffle compiler graphtoobigbailoutexception  graph too big to safely compile  node count     graph size     limit     timestamp   src lexer rb      opt failed id   lexer advance                                       tier   time         ms reason  org graalvm compiler truffle compiler graphtoobigbailoutexception  graph too big to safely compile  node count     graph size     limit     timestamp   src lexer rb        opt failed id   ripper yyparse                                      tier   time        ms reason  org graalvm compiler truffle compiler graphtoobigbailoutexception  graph too big to safely compile  node count     graph size     limit     timestamp   src ripper c      opt failed id   ripper yyparse                                      tier   time        ms reason  org graalvm compiler truffle compiler graphtoobigbailoutexception  graph too big to safely compile  node count     graph size     limit     timestamp   src ripper c         the first two relate to       a separate issue            ruby   vm xx  printgcsummary   cpusampler   cpusampler delay     cpusampler showtiers true  iharness benchmarks ruby lsp benchmark rb                                                                                                                                                                                                                                                       thread    name                                                                                                                total time                                            self time                               location                                                                                                                                                                                                                                                                ripper yyparse                                                                                                                                                                                        ripper c       rb type p                                                                                                                                                                                                 object c       lexer advance                                                                                                                                                                                                   rubies truffleruby dev lib gems gems parser         lib parser lexer rb           kernel class                                                                                                                                                                                                 core        basicobject                                                                                                                                                                                                   core        hash                                                                                                                                                                                                       core        ripper lineno                                                                                                                                                                                                      rubies truffleruby dev lib truffle truffle cext ruby rb         hash                                                                                                                                                                                                        core        array empty                                                                                                                                                                                                 resource  truffleruby core array rb                  rschatz does sulong use     or could it  maybe only for basic blocks without control flow  but i m not sure it would help then     btw  it d be useful if sulong shows the end line of functions  even if it s an approximation   because  ripper c      doesn t tell us ,0
123072,10252364099.0,IssuesEvent,2019-08-21 08:51:36,brave/brave-browser,https://api.github.com/repos/brave/brave-browser,opened,incorrect favicon in Tipping banner for Vimeo pubs,QA/Test-Plan-Specified QA/Yes bug feature/rewards,"<!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue. 

PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE. 
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->

## Description 
<!--Provide a brief description of the issue-->
incorrect favicon in Tipping banner for Vimeo pubs

## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->

   1. Open brave 0.68.131
   2. Open few verified and not verified Vimeo pubs
   3. Send a one-time tip or monthly tip to Vimeo pubs 
   4. Incorrect favicon displayed in tipping banner

## Actual result:
<!--Please add screenshots if needed-->

https://vimeo.com/willchristiansen
![image](https://user-images.githubusercontent.com/38657976/63416651-6f2fa580-c41d-11e9-9c21-2133cf46592d.png)

![image](https://user-images.githubusercontent.com/38657976/63416720-94bcaf00-c41d-11e9-96ec-398c67afbfb5.png)

https://vimeo.com/user91022604
![image](https://user-images.githubusercontent.com/38657976/63417371-c124fb00-c41e-11e9-98c5-65bca796e26d.png)

![image](https://user-images.githubusercontent.com/38657976/63417398-ce41ea00-c41e-11e9-9445-b6025c564a73.png)


## Expected result:
The correct favicon should display in Tipping banner

## Reproduces how often: 
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->

Always
## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->

Brave | 0.68.131 Chromium: 76.0.3809.100 (Official Build) (64-bit)
-- | --
Revision | ed9d447d30203dc5069e540f05079e493fc1c132-refs/branch-heads/3809@{#990}
OS | Windows 10 OS Version 1803 (Build 17134.523)



## Version/Channel Information:
<!--Does this issue happen on any other channels? Or is it specific to a certain channel?-->

- Can you reproduce this issue with the current release? Yes
- Can you reproduce this issue with the beta channel? Yes
- Can you reproduce this issue with the dev channel? Yes
- Can you reproduce this issue with the nightly channel? Yes

## Other Additional Information:

- Does the issue resolve itself when disabling Brave Shields? NA
- Does the issue resolve itself when disabling Brave Rewards? NA
- Is the issue reproducible on the latest version of Chrome? NA

## Miscellaneous Information:
<!--Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue-->
@brave/legacy_qa @NejcZdovc ",1.0,"incorrect favicon in Tipping banner for Vimeo pubs - <!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue. 

PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE. 
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->

## Description 
<!--Provide a brief description of the issue-->
incorrect favicon in Tipping banner for Vimeo pubs

## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->

   1. Open brave 0.68.131
   2. Open few verified and not verified Vimeo pubs
   3. Send a one-time tip or monthly tip to Vimeo pubs 
   4. Incorrect favicon displayed in tipping banner

## Actual result:
<!--Please add screenshots if needed-->

https://vimeo.com/willchristiansen
![image](https://user-images.githubusercontent.com/38657976/63416651-6f2fa580-c41d-11e9-9c21-2133cf46592d.png)

![image](https://user-images.githubusercontent.com/38657976/63416720-94bcaf00-c41d-11e9-96ec-398c67afbfb5.png)

https://vimeo.com/user91022604
![image](https://user-images.githubusercontent.com/38657976/63417371-c124fb00-c41e-11e9-98c5-65bca796e26d.png)

![image](https://user-images.githubusercontent.com/38657976/63417398-ce41ea00-c41e-11e9-9445-b6025c564a73.png)


## Expected result:
The correct favicon should display in Tipping banner

## Reproduces how often: 
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->

Always
## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->

Brave | 0.68.131 Chromium: 76.0.3809.100 (Official Build) (64-bit)
-- | --
Revision | ed9d447d30203dc5069e540f05079e493fc1c132-refs/branch-heads/3809@{#990}
OS | Windows 10 OS Version 1803 (Build 17134.523)



## Version/Channel Information:
<!--Does this issue happen on any other channels? Or is it specific to a certain channel?-->

- Can you reproduce this issue with the current release? Yes
- Can you reproduce this issue with the beta channel? Yes
- Can you reproduce this issue with the dev channel? Yes
- Can you reproduce this issue with the nightly channel? Yes

## Other Additional Information:

- Does the issue resolve itself when disabling Brave Shields? NA
- Does the issue resolve itself when disabling Brave Rewards? NA
- Is the issue reproducible on the latest version of Chrome? NA

## Miscellaneous Information:
<!--Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue-->
@brave/legacy_qa @NejcZdovc ",0,incorrect favicon in tipping banner for vimeo pubs        have you searched for similar issues  before submitting this issue  please check the open issues and add a note before logging a new issue      please use the template below to provide information about the issue    insufficient info will get the issue closed  it will only be reopened after sufficient info is provided          description      incorrect favicon in tipping banner for vimeo pubs       steps to reproduce             open brave              open few verified and not verified vimeo pubs        send a one time tip or monthly tip to vimeo pubs         incorrect favicon displayed in tipping banner       actual result                                                   expected result   the correct favicon should display in tipping banner       reproduces how often         always     brave version  brave   version info        brave         chromium           official build     bit            revision     refs branch heads         os   windows   os version    build                version channel information          can you reproduce this issue with the current release  yes    can you reproduce this issue with the beta channel  yes    can you reproduce this issue with the dev channel  yes    can you reproduce this issue with the nightly channel  yes       other additional information       does the issue resolve itself when disabling brave shields  na    does the issue resolve itself when disabling brave rewards  na    is the issue reproducible on the latest version of chrome  na       miscellaneous information       brave legacy qa  nejczdovc ,0
57131,8141877906.0,IssuesEvent,2018-08-21 04:55:54,golang/go,https://api.github.com/repos/golang/go,closed,"net/http, security: http.FileServer may inadvertently expose sensitive directories",Documentation NeedsDecision Security,"The default `http.FileServer(http.Dir("".""))` implementation exposes all files and folders in the working directory. This includes directories like `.git` or `.svn`, which an attacker can use to recover the source code comprising the server, if for example people deploy by running a ""git clone"" and a ""go install."" This is how Heroku handles Go deployments and I am sure others do as well; it's common if you run Macs locally but deploy on Linux.

This is not a hypothetical attack, one estimate found 9700 of the Alexa top 1 million sites expose the `.git` directory: https://en.internetwache.org/dont-publicly-expose-git-or-how-we-downloaded-your-websites-sourcecode-an-analysis-of-alexas-1m-28-07-2015/

I am wondering whether the Go standard library should do anything to help prevent these inadvertent directory exposures. Our hands are slightly tied by the current API, which exposes everything and can't change.

Some options:

- Do nothing

- Document the potential vulnerability and leave it at that.

- Add `http.SafeDir` or similar, that 404's on any file beginning with a `.`. This should cover most private files, including `.htpasswd`.

- Add `SafeDir` to httputil.

- Modify `http.Dir` to exclude files that begin with a `.`. This would break backwards compatibility, and seems like a bad idea.",1.0,"net/http, security: http.FileServer may inadvertently expose sensitive directories - The default `http.FileServer(http.Dir("".""))` implementation exposes all files and folders in the working directory. This includes directories like `.git` or `.svn`, which an attacker can use to recover the source code comprising the server, if for example people deploy by running a ""git clone"" and a ""go install."" This is how Heroku handles Go deployments and I am sure others do as well; it's common if you run Macs locally but deploy on Linux.

This is not a hypothetical attack, one estimate found 9700 of the Alexa top 1 million sites expose the `.git` directory: https://en.internetwache.org/dont-publicly-expose-git-or-how-we-downloaded-your-websites-sourcecode-an-analysis-of-alexas-1m-28-07-2015/

I am wondering whether the Go standard library should do anything to help prevent these inadvertent directory exposures. Our hands are slightly tied by the current API, which exposes everything and can't change.

Some options:

- Do nothing

- Document the potential vulnerability and leave it at that.

- Add `http.SafeDir` or similar, that 404's on any file beginning with a `.`. This should cover most private files, including `.htpasswd`.

- Add `SafeDir` to httputil.

- Modify `http.Dir` to exclude files that begin with a `.`. This would break backwards compatibility, and seems like a bad idea.",1,net http  security  http fileserver may inadvertently expose sensitive directories   the default  http fileserver http dir        implementation exposes all files and folders in the working directory  this includes directories like   git  or   svn   which an attacker can use to recover the source code comprising the server  if for example people deploy by running a  git clone  and a  go install   this is how heroku handles go deployments and i am sure others do as well  it s common if you run macs locally but deploy on linux     this is not a hypothetical attack  one estimate found   of the alexa top   million sites expose the   git  directory       i am wondering whether the go standard library should do anything to help prevent these inadvertent directory exposures  our hands are slightly tied by the current api  which exposes everything and can t change     some options       do nothing      document the potential vulnerability and leave it at that       add  http safedir  or similar  that   s on any file beginning with a      this should cover most private files  including   htpasswd        add  safedir  to httputil       modify  http dir  to exclude files that begin with a      this would break backwards compatibility  and seems like a bad idea ,1
778,10277090780.0,IssuesEvent,2019-08-25 00:21:16,SanderMertens/flecs,https://api.github.com/repos/SanderMertens/flecs,closed,Remove `bake.utils` dependency,portability,"* Substitute all `ut_*` function with `ecs_os_api_*` callbacks.
* Move [bake.utils](https://github.com/SanderMertens/flecs/blob/master/src/os_api.c#L21) to separate `flecs.bake` module. It will setup os api within module import function. 
* Remove `bake.utils` dependency from all modules use os api instead.",True,"Remove `bake.utils` dependency - * Substitute all `ut_*` function with `ecs_os_api_*` callbacks.
* Move [bake.utils](https://github.com/SanderMertens/flecs/blob/master/src/os_api.c#L21) to separate `flecs.bake` module. It will setup os api within module import function. 
* Remove `bake.utils` dependency from all modules use os api instead.",0,remove  bake utils  dependency     substitute all  ut    function with  ecs os api    callbacks     move     to separate  flecs bake  module  it will setup os api within module import function      remove  bake utils  dependency from all modules use os api instead ,0
351464,32001688120.0,IssuesEvent,2023-09-21 12:40:38,unifyai/ivy,https://api.github.com/repos/unifyai/ivy,closed,Fix changing_array_shape.test_numpy_asarray_chkfinite,NumPy Frontend Sub Task Failing Test,"|   |   |
|---|---|
|numpy|<a href=""https://github.com/unifyai/ivy/actions/runs/6260474083/job/16998577885""><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href=""https://github.com/unifyai/ivy/actions/runs/6260474083/job/16998577885""><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href=""https://github.com/unifyai/ivy/actions/runs/6260474083/job/16998577885""><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href=""https://github.com/unifyai/ivy/actions/runs/6260474083/job/16998577885""><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href=""https://github.com/unifyai/ivy/actions/runs/6260474083/job/16998577885""><img src=https://img.shields.io/badge/-success-success></a>
",1.0,"Fix changing_array_shape.test_numpy_asarray_chkfinite - |   |   |
|---|---|
|numpy|<a href=""https://github.com/unifyai/ivy/actions/runs/6260474083/job/16998577885""><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href=""https://github.com/unifyai/ivy/actions/runs/6260474083/job/16998577885""><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href=""https://github.com/unifyai/ivy/actions/runs/6260474083/job/16998577885""><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href=""https://github.com/unifyai/ivy/actions/runs/6260474083/job/16998577885""><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href=""https://github.com/unifyai/ivy/actions/runs/6260474083/job/16998577885""><img src=https://img.shields.io/badge/-success-success></a>
",0,fix changing array shape test numpy asarray chkfinite                          numpy  a href    src     jax  a href    src     tensorflow  a href    src     torch  a href    src     paddle  a href    src    ,0
11005,3452288861.0,IssuesEvent,2015-12-17 02:52:57,golang/go,https://api.github.com/repos/golang/go,opened,archive/tar: mention changes in go1.6 docs,Documentation,"http://tip.golang.org/doc/go1.6 does not mention archive/tar at all, but tons of work went into in this cycle.

@dsnet, can you help summarize the notable parts?",1.0,"archive/tar: mention changes in go1.6 docs - http://tip.golang.org/doc/go1.6 does not mention archive/tar at all, but tons of work went into in this cycle.

@dsnet, can you help summarize the notable parts?",1,archive tar  mention changes in     docs     does not mention archive tar at all  but tons of work went into in this cycle      dsnet  can you help summarize the notable parts ,1
423170,12292096602.0,IssuesEvent,2020-05-10 13:13:17,RaenonX/Jelly-Bot,https://api.github.com/repos/RaenonX/Jelly-Bot,opened,Prevent Discord bot handling single messages multiple times ,Priority: 9 Tag: Bot Tag: System Type: Bug,"## Description
As title.

## Expected Behavior
Handle a message exactly once.

## Current Status
Not fixed.

## How to reproduce
1. Send any message that will cause the bot to reply

## Origin
Unknown

## Notes
Possibly because IIS is running multiple processes simultaneously, each of them are all handling the request.
Should **NOT** fix by setting the working process to only one because if there's any time-consuming call, then it may block other requests.

## Solution
Not yet resolved. Fixing commit to be mentioned after this had been fixed.
",1.0,"Prevent Discord bot handling single messages multiple times  - ## Description
As title.

## Expected Behavior
Handle a message exactly once.

## Current Status
Not fixed.

## How to reproduce
1. Send any message that will cause the bot to reply

## Origin
Unknown

## Notes
Possibly because IIS is running multiple processes simultaneously, each of them are all handling the request.
Should **NOT** fix by setting the working process to only one because if there's any time-consuming call, then it may block other requests.

## Solution
Not yet resolved. Fixing commit to be mentioned after this had been fixed.
",0,prevent discord bot handling single messages multiple times       description  as title        expected behavior  handle a message exactly once        current status  not fixed        how to reproduce     send any message that will cause the bot to reply       origin  unknown       notes  possibly because iis is running multiple processes simultaneously  each of them are all handling the request   should   not   fix by setting the working process to only one because if there s any time consuming call  then it may block other requests        solution  not yet resolved  fixing commit to be mentioned after this had been fixed   ,0
68550,13153906060.0,IssuesEvent,2020-08-10 05:14:39,DS-13-Dev-Team/DS13,https://api.github.com/repos/DS-13-Dev-Team/DS13,closed,"[BUG] branch, root and propagator nodes spawn double corruption",Bug Code,"
Description of issue:
Corruption spreading nodes don't check for their own tile, and spawn an extra corruption underneath themselves, this may apply to shards and the marker as well.

Steps to reproduce:
Spawn a node on corruption.
",1.0,"[BUG] branch, root and propagator nodes spawn double corruption - 
Description of issue:
Corruption spreading nodes don't check for their own tile, and spawn an extra corruption underneath themselves, this may apply to shards and the marker as well.

Steps to reproduce:
Spawn a node on corruption.
",0,  branch  root and propagator nodes spawn double corruption     description of issue   corruption spreading nodes don t check for their own tile  and spawn an extra corruption underneath themselves  this may apply to shards and the marker as well     steps to reproduce   spawn a node on corruption   ,0
426767,12379015987.0,IssuesEvent,2020-05-19 11:45:07,ansible/galaxy_ng,https://api.github.com/repos/ansible/galaxy_ng,closed,Use pulp viewsets for 'v3',area/api priority/high sprint/4 status/ready-for-QE type/enhancement,Adds the ability to expose repository distribution endpoints via the v3 API.,1.0,Use pulp viewsets for 'v3' - Adds the ability to expose repository distribution endpoints via the v3 API.,0,use pulp viewsets for       adds the ability to expose repository distribution endpoints via the   api ,0
143986,5533658362.0,IssuesEvent,2017-03-21 13:52:14,mozilla/addons-server,https://api.github.com/repos/mozilla/addons-server,closed,"When confirming the delete of an add-on, the entered text should escape space in front and at the back",priority: enhancement,"*Environment*
Firefox: Nightly 54.0a1
Server: -dev
OS: Windows 10

*Steps to reproduce*
1. Go to AMO page.
2. Go to Tools > Manage My Submissions and click on an add-on.
3. Go to Manage & Status versions. 
4. Click Delete Add-on button.
5. On the confirmation prompt, enter the required text with spaces in front and/or at back and confirm the operation. Observe the behavior.

*Expected results*
The spaces should be escaped and the operation should be completed successfully.

*Actual results*
The spaces are treated as characters so the string won’t match, thus an error is thrown for entering the correct text.

*Notes*
1. Reproducibility: 5/5.
2. The issue is reproducible also on production on release build (51.0.1).
",1.0,"When confirming the delete of an add-on, the entered text should escape space in front and at the back - *Environment*
Firefox: Nightly 54.0a1
Server: -dev
OS: Windows 10

*Steps to reproduce*
1. Go to AMO page.
2. Go to Tools > Manage My Submissions and click on an add-on.
3. Go to Manage & Status versions. 
4. Click Delete Add-on button.
5. On the confirmation prompt, enter the required text with spaces in front and/or at back and confirm the operation. Observe the behavior.

*Expected results*
The spaces should be escaped and the operation should be completed successfully.

*Actual results*
The spaces are treated as characters so the string won’t match, thus an error is thrown for entering the correct text.

*Notes*
1. Reproducibility: 5/5.
2. The issue is reproducible also on production on release build (51.0.1).
",0,when confirming the delete of an add on  the entered text should escape space in front and at the back    environment   firefox  nightly      server   dev  os  windows       steps to reproduce      go to amo page      go to tools   manage my submissions and click on an add on      go to manage   status versions       click delete add on button      on the confirmation prompt  enter the required text with spaces in front and or at back and confirm the operation  observe the behavior      expected results   the spaces should be escaped and the operation should be completed successfully      actual results   the spaces are treated as characters so the string won’t match  thus an error is thrown for entering the correct text      notes      reproducibility           the issue is reproducible also on production on release build           ,0
3536,3195156728.0,IssuesEvent,2015-09-30 15:25:28,g4gaurang/bcbsmaissuestracker,https://api.github.com/repos/g4gaurang/bcbsmaissuestracker,closed,Header from previous custom plan generated remains on header - AB-146,auto-migrated Build-P19.5.11.16 Environment-Pclient5 HR_FixType-HR_Product Milestone-Release1.1 Priority-High Status- BCBSMA Retest Type-Defect,"```
What steps will reproduce the problem?
1. Log on to production as a BCBSMA Administrator
2. Click on Manage Plan
3. Search for any custom plan
4. Create a Custom Plan
5. Generate Final PDF with disclosures
6. Go back to manage plan interface
7. Search for a standard plan
8. Hover over plan, click plan document options
9. Generate Final PDF with disclosures

Actual Result:
See screenshot. Notice how header from previous custom plan is still there.

Expected Result:
This should not replicate from previous plan generated.

```

Original issue reported on code.google.com by `wcd82...@gmail.com` on 2 Jul 2015 at 6:41

Attachments:
* [Screen Shot 2015-07-02 at 2.30.14 PM.png](https://storage.googleapis.com/google-code-attachments/bcbsmaissuestracker/issue-221/comment-0/Screen Shot 2015-07-02 at 2.30.14 PM.png)
",1.0,"Header from previous custom plan generated remains on header - AB-146 - ```
What steps will reproduce the problem?
1. Log on to production as a BCBSMA Administrator
2. Click on Manage Plan
3. Search for any custom plan
4. Create a Custom Plan
5. Generate Final PDF with disclosures
6. Go back to manage plan interface
7. Search for a standard plan
8. Hover over plan, click plan document options
9. Generate Final PDF with disclosures

Actual Result:
See screenshot. Notice how header from previous custom plan is still there.

Expected Result:
This should not replicate from previous plan generated.

```

Original issue reported on code.google.com by `wcd82...@gmail.com` on 2 Jul 2015 at 6:41

Attachments:
* [Screen Shot 2015-07-02 at 2.30.14 PM.png](https://storage.googleapis.com/google-code-attachments/bcbsmaissuestracker/issue-221/comment-0/Screen Shot 2015-07-02 at 2.30.14 PM.png)
",0,header from previous custom plan generated remains on header   ab         what steps will reproduce the problem     log on to production as a bcbsma administrator    click on manage plan    search for any custom plan    create a custom plan    generate final pdf with disclosures    go back to manage plan interface    search for a standard plan    hover over plan  click plan document options    generate final pdf with disclosures  actual result  see screenshot  notice how header from previous custom plan is still there   expected result  this should not replicate from previous plan generated        original issue reported on code google com by       gmail com  on   jul   at      attachments        shot       at       pm png  ,0
191712,22215833330.0,IssuesEvent,2022-06-08 01:28:19,Nivaskumark/kernel_v4.1.15,https://api.github.com/repos/Nivaskumark/kernel_v4.1.15,reopened,CVE-2016-6136 (Medium) detected in linuxlinux-4.6,security vulnerability,"## CVE-2016-6136 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.6</b></p></summary>
<p>

<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Nivaskumark/kernel_v4.1.15/commit/00db4e8795bcbec692fb60b19160bdd763ad42e3"">00db4e8795bcbec692fb60b19160bdd763ad42e3</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/kernel/auditsc.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/kernel/auditsc.c</b>
</p>
</details>
<p></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>  
  
Race condition in the audit_log_single_execve_arg function in kernel/auditsc.c in the Linux kernel through 4.7 allows local users to bypass intended character-set restrictions or disrupt system-call auditing by changing a certain string, aka a ""double fetch"" vulnerability.

<p>Publish Date: 2016-08-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-6136>CVE-2016-6136</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>4.7</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: High
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: High
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-6136"">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-6136</a></p>
<p>Release Date: 2016-08-06</p>
<p>Fix Resolution: v4.8-rc1</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2016-6136 (Medium) detected in linuxlinux-4.6 - ## CVE-2016-6136 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.6</b></p></summary>
<p>

<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Nivaskumark/kernel_v4.1.15/commit/00db4e8795bcbec692fb60b19160bdd763ad42e3"">00db4e8795bcbec692fb60b19160bdd763ad42e3</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/kernel/auditsc.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/kernel/auditsc.c</b>
</p>
</details>
<p></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>  
  
Race condition in the audit_log_single_execve_arg function in kernel/auditsc.c in the Linux kernel through 4.7 allows local users to bypass intended character-set restrictions or disrupt system-call auditing by changing a certain string, aka a ""double fetch"" vulnerability.

<p>Publish Date: 2016-08-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-6136>CVE-2016-6136</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>4.7</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: High
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: High
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-6136"">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-6136</a></p>
<p>Release Date: 2016-08-06</p>
<p>Fix Resolution: v4.8-rc1</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      medium  detected in linuxlinux          cve       medium severity vulnerability     vulnerable library    linuxlinux            the linux kernel   library home page   a href    found in head commit   a href      found in base branch   master             vulnerable source files                  kernel auditsc c        kernel auditsc c                    vulnerability details         race condition in the audit log single execve arg function in kernel auditsc c in the linux kernel through     allows local users to bypass intended character set restrictions or disrupt system call auditing by changing a certain string  aka a  double fetch  vulnerability    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  local     attack complexity  high     privileges required  low     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  high     availability impact  none   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                      step up your open source security game with whitesource    ,0
11411,30449424828.0,IssuesEvent,2023-07-16 05:01:15,facebook/react-native,https://api.github.com/repos/facebook/react-native,closed,Add support to turbo module codegen for WritableMap type.,Stale Needs: Author Feedback Type: New Architecture Needs: Version Info,"### Description

Currently there is no support to **codegen** return a specific data structure as **WritableMap**.

### This is currently supported

For example on a Turbo Module with name ""example"".
```ts

type SomeType: {
  id: string 
}

export interface Spec extends TurboModule{
  someMethod(): SomeType[]; 
}
```

That should generate a should generate a turbo module method called ""public WritableArray someMethod(){}"" definition on Java Turbo Module.

### This is not currently supported

```ts

type SomeType: {
  id: string 
}

export interface Spec extends TurboModule{
  someMethod(): SomeType 
}
```

That should generate a should generate a turbo module method called ""public WritableMap someMethod(){}"" definition on Java Turbo Module. 
But actually gives the following error building on js codegen task:

```ts
 nodes: [
    Node {
      type: 'TSTypeReference',
      start: 3645,
      end: 3667,
      loc: SourceLocation {
        start: Position { line: 117, column: 49, index: 3645 },
        end: Position { line: 117, column: 71, index: 3667 },
        filename: undefined,
        identifierName: undefined
      },
      typeName: Node {
        type: 'Identifier',
        start: 3645,
        end: 3667,
        loc: SourceLocation {
          start: Position { line: 117, column: 49, index: 3645 },
          end: Position { line: 117, column: 71, index: 3667 },
          filename: undefined,
          identifierName: 'SomeType'
        },
        name: 'SomeType'
      }
    }
  ]
```

I think maybe the Turbo Module codegen does not have support to non primitive types only supporting: number, fuction, strings, arrays and objects. But the codegen could generate a Java structure that could have type safety for named properties javascript objects, or just accept a WritableMap as return type.





### React Native Version

0.74.4

### Output of `npx react-native info`

System:
    OS: Linux 5.19 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)
    CPU: (16) x64 AMD Ryzen 7 5700X 8-Core Processor
    Memory: 4.48 GB / 15.52 GB
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 19.9.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.6.3 - /usr/local/bin/npm
    Watchman: Not Found
  SDKs:
    Android SDK:
      API Levels: 28, 30, 33, 33
      Build Tools: 30.0.3, 33.0.0, 33.0.2
      System Images: android-30 | Google APIs Intel x86 Atom, android-33 | Google APIs Intel x86_64 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: Not Found
  Languages:
    Java: 11.0.19 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 18.2.0 => 18.2.0 
    react-native: 0.71.4 => 0.71.4 
  npmGlobalPackages:
    *react-native*: Not Found


### Steps to reproduce

Declare a turbo module that implement this simple feature.
Should crash on build time.

type SomeType: {
  id: string 
}

export interface Spec extends TurboModule{
  someMethod(): SomeType 
}
```


### Snack, code example, screenshot, or link to a repository

![Screenshot from 2023-06-09 19-34-28](https://github.com/facebook/react-native/assets/29023475/655ee758-eb41-487a-988b-2d9afab6322a)
![Screenshot from 2023-06-09 19-34-42](https://github.com/facebook/react-native/assets/29023475/40a6c1ee-d951-4436-b89e-6836d1a7d332)
![Screenshot from 2023-06-09 19-34-54](https://github.com/facebook/react-native/assets/29023475/68724dbb-f138-4e45-b73c-8a3dbddd2a32)

",1.0,"Add support to turbo module codegen for WritableMap type. - ### Description

Currently there is no support to **codegen** return a specific data structure as **WritableMap**.

### This is currently supported

For example on a Turbo Module with name ""example"".
```ts

type SomeType: {
  id: string 
}

export interface Spec extends TurboModule{
  someMethod(): SomeType[]; 
}
```

That should generate a should generate a turbo module method called ""public WritableArray someMethod(){}"" definition on Java Turbo Module.

### This is not currently supported

```ts

type SomeType: {
  id: string 
}

export interface Spec extends TurboModule{
  someMethod(): SomeType 
}
```

That should generate a should generate a turbo module method called ""public WritableMap someMethod(){}"" definition on Java Turbo Module. 
But actually gives the following error building on js codegen task:

```ts
 nodes: [
    Node {
      type: 'TSTypeReference',
      start: 3645,
      end: 3667,
      loc: SourceLocation {
        start: Position { line: 117, column: 49, index: 3645 },
        end: Position { line: 117, column: 71, index: 3667 },
        filename: undefined,
        identifierName: undefined
      },
      typeName: Node {
        type: 'Identifier',
        start: 3645,
        end: 3667,
        loc: SourceLocation {
          start: Position { line: 117, column: 49, index: 3645 },
          end: Position { line: 117, column: 71, index: 3667 },
          filename: undefined,
          identifierName: 'SomeType'
        },
        name: 'SomeType'
      }
    }
  ]
```

I think maybe the Turbo Module codegen does not have support to non primitive types only supporting: number, fuction, strings, arrays and objects. But the codegen could generate a Java structure that could have type safety for named properties javascript objects, or just accept a WritableMap as return type.





### React Native Version

0.74.4

### Output of `npx react-native info`

System:
    OS: Linux 5.19 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)
    CPU: (16) x64 AMD Ryzen 7 5700X 8-Core Processor
    Memory: 4.48 GB / 15.52 GB
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 19.9.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.6.3 - /usr/local/bin/npm
    Watchman: Not Found
  SDKs:
    Android SDK:
      API Levels: 28, 30, 33, 33
      Build Tools: 30.0.3, 33.0.0, 33.0.2
      System Images: android-30 | Google APIs Intel x86 Atom, android-33 | Google APIs Intel x86_64 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: Not Found
  Languages:
    Java: 11.0.19 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 18.2.0 => 18.2.0 
    react-native: 0.71.4 => 0.71.4 
  npmGlobalPackages:
    *react-native*: Not Found


### Steps to reproduce

Declare a turbo module that implement this simple feature.
Should crash on build time.

type SomeType: {
  id: string 
}

export interface Spec extends TurboModule{
  someMethod(): SomeType 
}
```


### Snack, code example, screenshot, or link to a repository

![Screenshot from 2023-06-09 19-34-28](https://github.com/facebook/react-native/assets/29023475/655ee758-eb41-487a-988b-2d9afab6322a)
![Screenshot from 2023-06-09 19-34-42](https://github.com/facebook/react-native/assets/29023475/40a6c1ee-d951-4436-b89e-6836d1a7d332)
![Screenshot from 2023-06-09 19-34-54](https://github.com/facebook/react-native/assets/29023475/68724dbb-f138-4e45-b73c-8a3dbddd2a32)

",0,add support to turbo module codegen for writablemap type        description    currently there is no support to   codegen   return a specific data structure as   writablemap           this is currently supported    for example on a turbo module with name  example       ts    type sometype       id  string        export interface spec extends turbomodule     somemethod    sometype               that should generate a should generate a turbo module method called  public writablearray somemethod      definition on java turbo module         this is not currently supported       ts    type sometype       id  string        export interface spec extends turbomodule     somemethod    sometype             that should generate a should generate a turbo module method called  public writablemap somemethod      definition on java turbo module    but actually gives the following error building on js codegen task        ts   nodes         node          type   tstypereference          start            end            loc  sourcelocation            start  position   line     column     index                end  position   line     column     index                filename  undefined           identifiername  undefined                  typename  node            type   identifier            start              end              loc  sourcelocation              start  position   line     column     index                  end  position   line     column     index                  filename  undefined             identifiername   sometype                       name   sometype                               i think maybe the turbo module codegen does not have support to non primitive types only supporting  number  fuction  strings  arrays and objects  but the codegen could generate a java structure that could have type safety for named properties javascript objects  or just accept a writablemap as return type                 react native version                 output of  npx react native info     system       os  linux     ubuntu       lts       lts  jammy jellyfish       cpu        amd ryzen       core processor      memory      gb       gb      shell           bin bash    binaries       node           usr local bin node      yarn           usr local bin yarn      npm           usr local bin npm      watchman  not found    sdks       android sdk         api levels                    build tools                             system images  android     google apis intel   atom  android     google apis intel     atom        android ndk  not found    ides       android studio  not found    languages       java           usr bin javac    npmpackages        react native community cli  not found      react                       react native                     npmglobalpackages        react native   not found          steps to reproduce    declare a turbo module that implement this simple feature   should crash on build time     type sometype       id  string        export interface spec extends turbomodule     somemethod    sometype                   snack  code example  screenshot  or link to a repository                        ,0
5205,2914298480.0,IssuesEvent,2015-06-23 03:19:02,golang/go,https://api.github.com/repos/golang/go,closed,text/template: Better doc for ParseFiles and Execute behaviour.,Documentation,"Hello.

I recently spent some time trying to figure why a template with Funcmaps would work with Parse() but not with ParseFiles() when using Execute (instead of ExecuteTemplate with the name). 

I found the answer in Stack Overflow http://stackoverflow.com/questions/10199219/go-template-function but the question also appeared in golang-nuts, for example here https://groups.google.com/forum/#!topic/golang-nuts/CI9WdC_sk00 and here https://groups.google.com/forum/#!topic/golang-nuts/vmZHHfLsH8M

Please consider if it should be better documented to make it less error-prone for inexperienced users.

Thank you.
",1.0,"text/template: Better doc for ParseFiles and Execute behaviour. - Hello.

I recently spent some time trying to figure why a template with Funcmaps would work with Parse() but not with ParseFiles() when using Execute (instead of ExecuteTemplate with the name). 

I found the answer in Stack Overflow http://stackoverflow.com/questions/10199219/go-template-function but the question also appeared in golang-nuts, for example here https://groups.google.com/forum/#!topic/golang-nuts/CI9WdC_sk00 and here https://groups.google.com/forum/#!topic/golang-nuts/vmZHHfLsH8M

Please consider if it should be better documented to make it less error-prone for inexperienced users.

Thank you.
",1,text template  better doc for parsefiles and execute behaviour    hello     i recently spent some time trying to figure why a template with funcmaps would work with parse   but not with parsefiles   when using execute  instead of executetemplate with the name       i found the answer in stack overflow   but the question also appeared in golang nuts  for example here   and here      please consider if it should be better documented to make it less error prone for inexperienced users     thank you   ,1
235992,19479616595.0,IssuesEvent,2021-12-25 01:07:20,Jesterhearts/tracing-rc,https://api.github.com/repos/Jesterhearts/tracing-rc,opened,Add loom testing,testing,It would be nice to add permutation testing through `loom` for the `Agc` and related `collect` implementations. This is hindered by the fact that `loom` doesn't support `std::sync::Weak` or `parking_lot::RwLock`.  (We can't simply substitute `std::sync::RwLock` for `parking_lot::RwLock` since we want to leak a `WriteGuard` and doing so would cause undefined behavior).,1.0,Add loom testing - It would be nice to add permutation testing through `loom` for the `Agc` and related `collect` implementations. This is hindered by the fact that `loom` doesn't support `std::sync::Weak` or `parking_lot::RwLock`.  (We can't simply substitute `std::sync::RwLock` for `parking_lot::RwLock` since we want to leak a `WriteGuard` and doing so would cause undefined behavior).,0,add loom testing   it would be nice to add permutation testing through  loom  for the  agc  and related  collect  implementations  this is hindered by the fact that  loom  doesn t support  std  sync  weak  or  parking lot  rwlock     we can t simply substitute  std  sync  rwlock  for  parking lot  rwlock  since we want to leak a  writeguard  and doing so would cause undefined behavior  ,0
5994,2997254325.0,IssuesEvent,2015-07-23 05:51:15,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: document the vendoring setup,Documentation,"The 1.5 go command has an experimental vendoring feature but it is undocumented in the go command, or anywhere else other than an out of date design doc.

",1.0,"cmd/go: document the vendoring setup - The 1.5 go command has an experimental vendoring feature but it is undocumented in the go command, or anywhere else other than an out of date design doc.

",1,cmd go  document the vendoring setup   the     go command has an experimental vendoring feature but it is undocumented in the go command  or anywhere else other than an out of date design doc     ,1
44547,7113023345.0,IssuesEvent,2018-01-17 19:00:26,golang/go,https://api.github.com/repos/golang/go,closed,proposal: spec: the integer division exception rule should be moved to the integer overflow section,Documentation,"In Go spec:
```
As an exception to this rule,
if the dividend x is the most negative value for the int type of x, 
the quotient q = x / -1 is equal to x (and r = 0).

			 x, q
int8                     -128
int16                  -32768
int32             -2147483648
int64    -9223372036854775808
```
The above content is in the ""Integer operators"" section,
but I think it should be moved to the ""Integer overflow"" section.

And it is not an exception. It is just a normal overflow,
the ""wrap around"" behavior is the same as other overflows.
I think it can just be shown as one line example to show how ""wrap around"" works.

The benefit of the proposal is to make people know `int8( -128)/int(-1)` is exactly an overflow.
",1.0,"proposal: spec: the integer division exception rule should be moved to the integer overflow section - In Go spec:
```
As an exception to this rule,
if the dividend x is the most negative value for the int type of x, 
the quotient q = x / -1 is equal to x (and r = 0).

			 x, q
int8                     -128
int16                  -32768
int32             -2147483648
int64    -9223372036854775808
```
The above content is in the ""Integer operators"" section,
but I think it should be moved to the ""Integer overflow"" section.

And it is not an exception. It is just a normal overflow,
the ""wrap around"" behavior is the same as other overflows.
I think it can just be shown as one line example to show how ""wrap around"" works.

The benefit of the proposal is to make people know `int8( -128)/int(-1)` is exactly an overflow.
",1,proposal  spec  the integer division exception rule should be moved to the integer overflow section   in go spec        as an exception to this rule   if the dividend x is the most negative value for the int type of x    the quotient q   x      is equal to x  and r          			 x  q                                                                                   the above content is in the  integer operators  section   but i think it should be moved to the  integer overflow  section     and it is not an exception  it is just a normal overflow   the  wrap around  behavior is the same as other overflows   i think it can just be shown as one line example to show how  wrap around  works     the benefit of the proposal is to make people know         int      is exactly an overflow   ,1
18608,25913755473.0,IssuesEvent,2022-12-15 15:48:23,FrozenBlock/WilderWild,https://api.github.com/repos/FrozenBlock/WilderWild,closed,Crash on startup after updating to 1.1.5,bug crash mod compatibility awaiting response,"**Description of the Bug Encountered**
Update from 1.1.2 to 1.1.5 and the game crashes on startup appears to be a conflict with prefab

**Steps To Reproduce**
1. Update from 1.1.2 to 1.1.5
2. Start game
3. Crash

**Expected Behavior**
Start game and not crash.

**Screenshots**

**Logs**
[crash-2022-12-09_14.25.09-client.txt](https://github.com/FrozenBlock/WilderWild/files/10195689/crash-2022-12-09_14.25.09-client.txt)


**Additional context**
Add any other context about the problem here.
",True,"Crash on startup after updating to 1.1.5 - **Description of the Bug Encountered**
Update from 1.1.2 to 1.1.5 and the game crashes on startup appears to be a conflict with prefab

**Steps To Reproduce**
1. Update from 1.1.2 to 1.1.5
2. Start game
3. Crash

**Expected Behavior**
Start game and not crash.

**Screenshots**

**Logs**
[crash-2022-12-09_14.25.09-client.txt](https://github.com/FrozenBlock/WilderWild/files/10195689/crash-2022-12-09_14.25.09-client.txt)


**Additional context**
Add any other context about the problem here.
",0,crash on startup after updating to           description of the bug encountered    update from       to       and the game crashes on startup appears to be a conflict with prefab      steps to reproduce       update from       to           start game     crash      expected behavior    start game and not crash       screenshots        logs               additional context    add any other context about the problem here   ,0
753679,26358033367.0,IssuesEvent,2023-01-11 11:12:12,dotnet/razor,https://api.github.com/repos/dotnet/razor,closed,Blazor Transpiler issue with named Tuples,bug triaged area-razor.compiler Priority:1,"When Blazor attempts at transpiling the following lines of code into a RenderFragment it combines the tuple type and name which generates a type that does not exists.

`
		[Parameter]
		public Action<(ApiBase Sender, TResponse Response)> WhenSuccessful { get; set; } 
`


Looking at the “razor.g.cs” file you will find the following transpiled code which is incorrect. Interestingly enough this happens to all, but the last parameter of the tuple.

`
        public static void CreateApi_1<TRequest, TResponse>(global::Microsoft.AspNetCore.Components.Rendering.RenderTreeBuilder __builder, int seq, int __seq0, TRequest __arg0, int __seq1, global::System.Net.Http.HttpMethod __arg1, int __seq2, global::System.String __arg2, int __seq3, global::System.Action<(global::ZoyaOpticalEHR.Common.Controls.Apis.ApiBaseSender, TResponse Response)> __arg3, int __seq4, TResponse __arg4, int __seq5, global::Microsoft.AspNetCore.Components.EventCallback<TResponse> __arg5, int __seq6, global::Microsoft.AspNetCore.Components.RenderFragment __arg6)
`

Notice in the generated code it combines the type and the name of the tuple property.

Using .Net 5.0, and the latest stable version of Visual Studio 2019 (Version 16.8.3)",1.0,"Blazor Transpiler issue with named Tuples - When Blazor attempts at transpiling the following lines of code into a RenderFragment it combines the tuple type and name which generates a type that does not exists.

`
		[Parameter]
		public Action<(ApiBase Sender, TResponse Response)> WhenSuccessful { get; set; } 
`


Looking at the “razor.g.cs” file you will find the following transpiled code which is incorrect. Interestingly enough this happens to all, but the last parameter of the tuple.

`
        public static void CreateApi_1<TRequest, TResponse>(global::Microsoft.AspNetCore.Components.Rendering.RenderTreeBuilder __builder, int seq, int __seq0, TRequest __arg0, int __seq1, global::System.Net.Http.HttpMethod __arg1, int __seq2, global::System.String __arg2, int __seq3, global::System.Action<(global::ZoyaOpticalEHR.Common.Controls.Apis.ApiBaseSender, TResponse Response)> __arg3, int __seq4, TResponse __arg4, int __seq5, global::Microsoft.AspNetCore.Components.EventCallback<TResponse> __arg5, int __seq6, global::Microsoft.AspNetCore.Components.RenderFragment __arg6)
`

Notice in the generated code it combines the type and the name of the tuple property.

Using .Net 5.0, and the latest stable version of Visual Studio 2019 (Version 16.8.3)",0,blazor transpiler issue with named tuples   when blazor attempts at transpiling the following lines of code into a renderfragment it combines the tuple type and name which generates a type that does not exists        		   		public action  whensuccessful   get  set             looking at the “razor g cs” file you will find the following transpiled code which is incorrect  interestingly enough this happens to all  but the last parameter of the tuple                public static void createapi    global  microsoft aspnetcore components rendering rendertreebuilder   builder  int seq  int      trequest      int      global  system net http httpmethod      int      global  system string      int      global  system action       int      tresponse      int      global  microsoft aspnetcore components eventcallback       int      global  microsoft aspnetcore components renderfragment            notice in the generated code it combines the type and the name of the tuple property     using  net      and the latest stable version of visual studio    version       ,0
169610,14225523262.0,IssuesEvent,2020-11-17 21:23:20,golang/go,https://api.github.com/repos/golang/go,opened,"x/sys/windows: clarify safety of Proc.Call, LazyProc.Call",Documentation,"https://godoc.org/golang.org/x/sys/windows#LazyProc.Call and https://godoc.org/golang.org/x/sys/windows#Proc.Call are syscall.SysCall wrappers but take a bunch of uintptrs.

I assume that those wrappers are not covered by the uintptr(unsafe.Pointer) conversion exception number (4) from https://golang.org/pkg/unsafe/#Pointer, correct?

Could we document that either way in x/sys/windows?

I assume that many callers will require runtime.KeepAlive?

/cc @ianlancetaylor @mdempsky @alexbrainman @josharian @crawshaw ",1.0,"x/sys/windows: clarify safety of Proc.Call, LazyProc.Call - https://godoc.org/golang.org/x/sys/windows#LazyProc.Call and https://godoc.org/golang.org/x/sys/windows#Proc.Call are syscall.SysCall wrappers but take a bunch of uintptrs.

I assume that those wrappers are not covered by the uintptr(unsafe.Pointer) conversion exception number (4) from https://golang.org/pkg/unsafe/#Pointer, correct?

Could we document that either way in x/sys/windows?

I assume that many callers will require runtime.KeepAlive?

/cc @ianlancetaylor @mdempsky @alexbrainman @josharian @crawshaw ",1,x sys windows  clarify safety of proc call  lazyproc call     and   are syscall syscall wrappers but take a bunch of uintptrs     i assume that those wrappers are not covered by the uintptr unsafe pointer  conversion exception number     from   correct     could we document that either way in x sys windows     i assume that many callers will require runtime keepalive      cc  ianlancetaylor  mdempsky  alexbrainman  josharian  crawshaw ,1
64138,8712540762.0,IssuesEvent,2018-12-06 22:34:56,golang/go,https://api.github.com/repos/golang/go,closed,math: docs omit mention of IEEE 754 endianness,Documentation NeedsFix help wanted,"### What version of Go are you using (`go version`)?

1.11 (but N/A)

### Does this issue reproduce with the latest release?

yes

### What operating system and processor architecture are you using (`go env`)?

amd64 (but N/A)

### What did you do?

Read pkg/math's documentation.

### What did you expect to see?

Enough information to determine what bits to expect from `Float64bits` and/or `Float32bits` (and the bits going the other way, too).

### What did you see instead?

Just enough information to guess that it's almost certainly either little-endian or big-endian, and may or may not depend on the host architecture.

What I'd like to know is, to a first approximation: Will the sign bit be 0x80, 0x1, or 0x8000000? Probably! My default guess would be that byte order would be the same as it is for ints, thus, 0x80000000. But it'd be nice to have that explicit. If I weren't used to Intel, I'd expect the sign bit to be the first bit ""in memory"", meaning that out of a 64-bit float, it would be the bit in the byte with the same address as the whole float, which would be 0x80. It's not, apparently, according to go playground. And that makes sense for Intel CPUs, but I don't know whether it's portable to non-x86 (don't have a go arm64 handy to test on), and I don't know whether it's actually specified or just happens to work out that way.",1.0,"math: docs omit mention of IEEE 754 endianness - ### What version of Go are you using (`go version`)?

1.11 (but N/A)

### Does this issue reproduce with the latest release?

yes

### What operating system and processor architecture are you using (`go env`)?

amd64 (but N/A)

### What did you do?

Read pkg/math's documentation.

### What did you expect to see?

Enough information to determine what bits to expect from `Float64bits` and/or `Float32bits` (and the bits going the other way, too).

### What did you see instead?

Just enough information to guess that it's almost certainly either little-endian or big-endian, and may or may not depend on the host architecture.

What I'd like to know is, to a first approximation: Will the sign bit be 0x80, 0x1, or 0x8000000? Probably! My default guess would be that byte order would be the same as it is for ints, thus, 0x80000000. But it'd be nice to have that explicit. If I weren't used to Intel, I'd expect the sign bit to be the first bit ""in memory"", meaning that out of a 64-bit float, it would be the bit in the byte with the same address as the whole float, which would be 0x80. It's not, apparently, according to go playground. And that makes sense for Intel CPUs, but I don't know whether it's portable to non-x86 (don't have a go arm64 handy to test on), and I don't know whether it's actually specified or just happens to work out that way.",1,math  docs omit mention of ieee   endianness       what version of go are you using   go version            but n a         does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env          but n a         what did you do     read pkg math s documentation         what did you expect to see     enough information to determine what bits to expect from     and or      and the bits going the other way  too          what did you see instead     just enough information to guess that it s almost certainly either little endian or big endian  and may or may not depend on the host architecture     what i d like to know is  to a first approximation  will the sign bit be       or    probably  my default guess would be that byte order would be the same as it is for ints  thus     but it d be nice to have that explicit  if i weren t used to intel  i d expect the sign bit to be the first bit  in memory   meaning that out of a   bit float  it would be the bit in the byte with the same address as the whole float  which would be    it s not  apparently  according to go playground  and that makes sense for intel cpus  but i don t know whether it s portable to non    don t have a go   handy to test on   and i don t know whether it s actually specified or just happens to work out that way ,1
39036,6717980047.0,IssuesEvent,2017-10-15 06:04:20,golang/go,https://api.github.com/repos/golang/go,closed,fmt: documentation on Printf * modifier is misleading,Documentation,"### What version of Go are you using (`go version`)?

`go version go1.9 darwin/amd64`

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/dpinela/dev/go""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.9/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.9/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/41/2xpv_r1j5n5bnflwb7s1hv580000gp/T/go-build477584587=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
```

### What did you do?

Run this program: https://play.golang.org/p/uBOhH86MEv

### What did you expect to see?

The program prints:
```
$%!(BADWIDTH)%!g(int=8)
$00001.68
```

### What did you see instead?

It prints the following instead:

```
$00001.68
$%!(BADWIDTH)%!g(int=8)
```

---

The documentation says this about the behaviour of the `*` modifier (emphasis mine):

> Width and precision are measured in units of Unicode code points, that is, runes. (This differs from C's printf where the units are always measured in bytes.) Either or both of the flags may be replaced with the character '*', causing their values to be obtained from the **next** operand, which must be of type int.

I was therefore expecting that `Printf` would get the width from the argument following the one to be formatted, rather than the preceding one. I think the wording could be clarified, such as by specifying ""causing their values to be obtained from the next operand, _before obtaining the value to be formatted_"", and/or by adding an example.",1.0,"fmt: documentation on Printf * modifier is misleading - ### What version of Go are you using (`go version`)?

`go version go1.9 darwin/amd64`

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/dpinela/dev/go""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.9/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.9/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/41/2xpv_r1j5n5bnflwb7s1hv580000gp/T/go-build477584587=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
```

### What did you do?

Run this program: https://play.golang.org/p/uBOhH86MEv

### What did you expect to see?

The program prints:
```
$%!(BADWIDTH)%!g(int=8)
$00001.68
```

### What did you see instead?

It prints the following instead:

```
$00001.68
$%!(BADWIDTH)%!g(int=8)
```

---

The documentation says this about the behaviour of the `*` modifier (emphasis mine):

> Width and precision are measured in units of Unicode code points, that is, runes. (This differs from C's printf where the units are always measured in bytes.) Either or both of the flags may be replaced with the character '*', causing their values to be obtained from the **next** operand, which must be of type int.

I was therefore expecting that `Printf` would get the width from the argument following the one to be formatted, rather than the preceding one. I think the wording could be clarified, such as by specifying ""causing their values to be obtained from the next operand, _before obtaining the value to be formatted_"", and/or by adding an example.",1,fmt  documentation on printf   modifier is misleading       what version of go are you using   go version        go version     darwin           does this issue reproduce with the latest release     yes         what operating system and processor architecture are you using   go env            goarch      gobin     goexe     gohostarch      gohostos  darwin   goos  darwin   gopath   users dpinela dev go   gorace     goroot   usr local cellar go     libexec   gotooldir   usr local cellar go     libexec pkg tool darwin     gccgo  gccgo   cc  clang   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders       t go    tmp go build  gno record gcc switches  fno common   cxx  clang     cgo enabled      cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config              what did you do     run this program           what did you expect to see     the program prints            badwidth   g int                      what did you see instead     it prints the following instead                    badwidth   g int                   the documentation says this about the behaviour of the     modifier  emphasis mine        width and precision are measured in units of unicode code points  that is  runes   this differs from c s printf where the units are always measured in bytes   either or both of the flags may be replaced with the character      causing their values to be obtained from the   next   operand  which must be of type int     i was therefore expecting that  printf  would get the width from the argument following the one to be formatted  rather than the preceding one  i think the wording could be clarified  such as by specifying  causing their values to be obtained from the next operand   before obtaining the value to be formatted    and or by adding an example ,1
414245,27982451500.0,IssuesEvent,2023-03-26 10:13:32,golang/go,https://api.github.com/repos/golang/go,closed,sync/map: misleading documentation about the map.LoadOrStore functions,Documentation,"<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
1.20.1
</pre>

### Does this issue reproduce with the latest release?

Yep

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env

</pre></details>

Not super relevant, this is an issue with the documentation

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->



### What did you expect to see?

The documentation for LoadOrStore says the following:

> LoadOrStore returns the existing value for the key if present. Otherwise, it stores and returns the given value.
> The loaded result is true if the value was loaded, false if stored.

However, this is very misleading: while TECHNICALLY this is correct, it's very easy to understand it backwards. look at this test:

```
func Test(t *testing.T) {
   exampleMap := new(sync.Map)
   val, x := policyEnablement.LoadOrStore(""key1"", true)
   fmt.Println(val, x)
   val, x = policyEnablement.LoadOrStore(""key1"", false)
   fmt.Println(val, x)
}
```

The output is:

```
=== RUN   Test
true false // <--------- ""false if stored"" 
true true  // <--------- ""true if the value was loaded"" 
```

I think that clarifying the documentation with slightly more verbose explanation would help.

### What did you see instead?


",1.0,"sync/map: misleading documentation about the map.LoadOrStore functions - <!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
1.20.1
</pre>

### Does this issue reproduce with the latest release?

Yep

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env

</pre></details>

Not super relevant, this is an issue with the documentation

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->



### What did you expect to see?

The documentation for LoadOrStore says the following:

> LoadOrStore returns the existing value for the key if present. Otherwise, it stores and returns the given value.
> The loaded result is true if the value was loaded, false if stored.

However, this is very misleading: while TECHNICALLY this is correct, it's very easy to understand it backwards. look at this test:

```
func Test(t *testing.T) {
   exampleMap := new(sync.Map)
   val, x := policyEnablement.LoadOrStore(""key1"", true)
   fmt.Println(val, x)
   val, x = policyEnablement.LoadOrStore(""key1"", false)
   fmt.Println(val, x)
}
```

The output is:

```
=== RUN   Test
true false // <--------- ""false if stored"" 
true true  // <--------- ""true if the value was loaded"" 
```

I think that clarifying the documentation with slightly more verbose explanation would help.

### What did you see instead?


",1,sync map  misleading documentation about the map loadorstore functions         please answer these questions before submitting your issue  thanks              what version of go are you using   go version            go version                  does this issue reproduce with the latest release     yep        what operating system and processor architecture are you using   go env          go env  output       go env          not super relevant  this is an issue with the documentation        what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on go dev play is best                  what did you expect to see     the documentation for loadorstore says the following       loadorstore returns the existing value for the key if present  otherwise  it stores and returns the given value     the loaded result is true if the value was loaded  false if stored     however  this is very misleading  while technically this is correct  it s very easy to understand it backwards  look at this test          func test t  testing t        examplemap    new sync map      val  x    policyenablement loadorstore      true      fmt println val  x      val  x   policyenablement loadorstore      false      fmt println val  x             the output is              run   test  true false                false if stored    true true                 true if the value was loaded           i think that clarifying the documentation with slightly more verbose explanation would help         what did you see instead       ,1
181890,6665092946.0,IssuesEvent,2017-10-02 22:56:35,InfiniteFlightAirportEditing/Airports,https://api.github.com/repos/InfiniteFlightAirportEditing/Airports,closed,YHOT,Being Redone Low Priority,"Highest airport in Australia, in a poor condition, I shall get it done in the next few hours to a day",1.0,"YHOT - Highest airport in Australia, in a poor condition, I shall get it done in the next few hours to a day",0,yhot   highest airport in australia  in a poor condition  i shall get it done in the next few hours to a day,0
175472,14530066888.0,IssuesEvent,2020-12-14 18:42:36,golang/go,https://api.github.com/repos/golang/go,closed,x/pkgsite: document that GitHub PRs are accepted in the CONTRIBUTING.md,Documentation NeedsFix Suggested help wanted pkgsite,"Per https://golang.org/doc/contribute.html#sending_a_change_github, x/pkgsite accepts PRs. 

We should add this to the [CONTRIBUTING.md](https://github.com/golang/pkgsite/blob/master/CONTRIBUTING.md#getting-started), so that new contributors are aware of this option for contributing. 

",1.0,"x/pkgsite: document that GitHub PRs are accepted in the CONTRIBUTING.md - Per https://golang.org/doc/contribute.html#sending_a_change_github, x/pkgsite accepts PRs. 

We should add this to the [CONTRIBUTING.md](https://github.com/golang/pkgsite/blob/master/CONTRIBUTING.md#getting-started), so that new contributors are aware of this option for contributing. 

",1,x pkgsite  document that github prs are accepted in the contributing md   per   x pkgsite accepts prs      we should add this to the     so that new contributors are aware of this option for contributing      ,1
77324,26922691180.0,IssuesEvent,2023-02-07 11:37:20,vector-im/element-ios,https://api.github.com/repos/vector-im/element-ios,closed,The space switcher shows the same avatar for all spaces,T-Defect,"### Steps to reproduce

1. Use an account with multiple spaces.
2. Open up the space switcher.

### Outcome

#### What did you expect?
Each space icon to match the space.

#### What happened instead?
All the spaces have the same icon (each time you open this changes) 🎰


### Your phone model

iPhone 13 Mini

### Operating system version

iOs 16.3

### Application version

1.9.16 TF

### Homeserver

_No response_

### Will you send logs?

No",1.0,"The space switcher shows the same avatar for all spaces - ### Steps to reproduce

1. Use an account with multiple spaces.
2. Open up the space switcher.

### Outcome

#### What did you expect?
Each space icon to match the space.

#### What happened instead?
All the spaces have the same icon (each time you open this changes) 🎰


### Your phone model

iPhone 13 Mini

### Operating system version

iOs 16.3

### Application version

1.9.16 TF

### Homeserver

_No response_

### Will you send logs?

No",0,the space switcher shows the same avatar for all spaces       steps to reproduce     use an account with multiple spaces      open up the space switcher       outcome       what did you expect   each space icon to match the space          what happened instead   all the spaces have the same icon  each time you open this changes  🎰        your phone model  iphone   mini      operating system version  ios          application version        tf      homeserver   no response       will you send logs   no,0
80116,10152326526.0,IssuesEvent,2019-08-05 23:13:56,golang/go,https://api.github.com/repos/golang/go,closed,doc: describe/summarize error value features in the Go 1.13 release notes,Documentation NeedsDecision release-blocker,"The error value changes landing in Go 1.13 are one piece of the headline Go 2 ""better error handling"" improvements. However, [the only mention in the Go 1.13 release notes](https://tip.golang.org/doc/go1.13#errors) right now is a short list of the new functions in the ""Minor changes to the library"" section.

I think these changes are important enough to warrant a description/summary at the top level of the release notes. Perhaps we should link to the design or mention the expected upcoming changes that will also tie in. Additionally, if we expect people to be adopting these features widely, perhaps we should include some prescriptive language to that end. (Or will there be a blog post?)

This is related to #33364, where the new features are also inadequately described in the package documentation.

/cc @jba @neild ",1.0,"doc: describe/summarize error value features in the Go 1.13 release notes - The error value changes landing in Go 1.13 are one piece of the headline Go 2 ""better error handling"" improvements. However, [the only mention in the Go 1.13 release notes](https://tip.golang.org/doc/go1.13#errors) right now is a short list of the new functions in the ""Minor changes to the library"" section.

I think these changes are important enough to warrant a description/summary at the top level of the release notes. Perhaps we should link to the design or mention the expected upcoming changes that will also tie in. Additionally, if we expect people to be adopting these features widely, perhaps we should include some prescriptive language to that end. (Or will there be a blog post?)

This is related to #33364, where the new features are also inadequately described in the package documentation.

/cc @jba @neild ",1,doc  describe summarize error value features in the go     release notes   the error value changes landing in go     are one piece of the headline go    better error handling  improvements  however      right now is a short list of the new functions in the  minor changes to the library  section     i think these changes are important enough to warrant a description summary at the top level of the release notes  perhaps we should link to the design or mention the expected upcoming changes that will also tie in  additionally  if we expect people to be adopting these features widely  perhaps we should include some prescriptive language to that end   or will there be a blog post      this is related to     where the new features are also inadequately described in the package documentation      cc  jba  neild ,1
48107,7374641636.0,IssuesEvent,2018-03-13 21:00:25,golang/go,https://api.github.com/repos/golang/go,closed,"compress/{gzip,zlib}: Writer documentation naming inconsistency",Documentation NeedsFix,"The documentation for both gzip.NewWriter and zlib.NewWriter contains the sentence ""It is the caller's responsibility to call Close on the WriteCloser when done"", yet both functions return a type named Writer, and it is referred to by that name everywhere else it appears.",1.0,"compress/{gzip,zlib}: Writer documentation naming inconsistency - The documentation for both gzip.NewWriter and zlib.NewWriter contains the sentence ""It is the caller's responsibility to call Close on the WriteCloser when done"", yet both functions return a type named Writer, and it is referred to by that name everywhere else it appears.",1,compress  gzip zlib   writer documentation naming inconsistency   the documentation for both gzip newwriter and zlib newwriter contains the sentence  it is the caller s responsibility to call close on the writecloser when done   yet both functions return a type named writer  and it is referred to by that name everywhere else it appears ,1
611913,18984329258.0,IssuesEvent,2021-11-21 13:04:19,Together-Java/TJ-Bot,https://api.github.com/repos/Together-Java/TJ-Bot,closed,VC activity command UX - Direct message towards audience,good first issue enhance command priority: low,"I think we could improve the vc activity command text. It is a bit random to other readers who lack context.

It would be better if it would say like **""user x wants to start activity y. feel free to join by clicking z, enjoy""**

Right now it's directed towards the message author but it should be directed to the actual audience, other people.

![akvKddi](https://user-images.githubusercontent.com/13614011/140027173-611ef6f9-e09f-4ee9-ab87-2868050b7dc1.png)
",1.0,"VC activity command UX - Direct message towards audience - I think we could improve the vc activity command text. It is a bit random to other readers who lack context.

It would be better if it would say like **""user x wants to start activity y. feel free to join by clicking z, enjoy""**

Right now it's directed towards the message author but it should be directed to the actual audience, other people.

![akvKddi](https://user-images.githubusercontent.com/13614011/140027173-611ef6f9-e09f-4ee9-ab87-2868050b7dc1.png)
",0,vc activity command ux   direct message towards audience   i think we could improve the vc activity command text  it is a bit random to other readers who lack context     it would be better if it would say like    user x wants to start activity y  feel free to join by clicking z  enjoy       right now it s directed towards the message author but it should be directed to the actual audience  other people           ,0
16156,4020814257.0,IssuesEvent,2016-05-16 19:46:19,golang/go,https://api.github.com/repos/golang/go,closed,encoding/json: document that object keys are sorted,Documentation,"If you call json.Marshal with a map, it sorts the keys. If you do a search, you will find a Stack Overflow page explaining this[1]. However, this behavior isn't mentioned in the godoc.

It's useful to assume that the emitted JSON will be deterministic, since then you can use string equality or compare hashes to look for duplicates and compare the emitted JSON to a golden copy in tests. But since this property isn't mentioned, it's unclear whether users can rely on the emitted JSON remaining the same in new versions of Go. 

Many people will do it anyway, so perhaps we should make it official?

[1] http://stackoverflow.com/questions/18668652/how-to-produce-json-with-sorted-keys-in-go
",1.0,"encoding/json: document that object keys are sorted - If you call json.Marshal with a map, it sorts the keys. If you do a search, you will find a Stack Overflow page explaining this[1]. However, this behavior isn't mentioned in the godoc.

It's useful to assume that the emitted JSON will be deterministic, since then you can use string equality or compare hashes to look for duplicates and compare the emitted JSON to a golden copy in tests. But since this property isn't mentioned, it's unclear whether users can rely on the emitted JSON remaining the same in new versions of Go. 

Many people will do it anyway, so perhaps we should make it official?

[1] http://stackoverflow.com/questions/18668652/how-to-produce-json-with-sorted-keys-in-go
",1,encoding json  document that object keys are sorted   if you call json marshal with a map  it sorts the keys  if you do a search  you will find a stack overflow page explaining this   however  this behavior isn t mentioned in the godoc     it s useful to assume that the emitted json will be deterministic  since then you can use string equality or compare hashes to look for duplicates and compare the emitted json to a golden copy in tests  but since this property isn t mentioned  it s unclear whether users can rely on the emitted json remaining the same in new versions of go      many people will do it anyway  so perhaps we should make it official          ,1
102710,22062648720.0,IssuesEvent,2022-05-30 20:23:43,graphql/graphiql,https://api.github.com/repos/graphql/graphiql,closed,Emojis in paths are not recognized,vscode-graphql,"I have a file in a path like the following:
/Users/yair/Workspace/firebase-microservices/functions/src/microservice/retailer/⚡️onRetailerDB/index.ts

## Actual Behavior

It replaces the ⚡️ in the path with `%E2%9A%A1%EF%B8%8F`.


## Expected Behavior

To read the path with emojis correctly .

## Steps to Reproduce the Problem Or Description

Place a fragment in a folder which has an emoji in his name.

## Specifications

  - GraphQL for VSCode Extension Version: GraphQL Insiders v0.3.5
  - VSCode Version: 1.62.3
  - OS Name: Darwin x64
  - OS Version: 21.1.0
  - graphql config filename and format example:
```javascript
module.exports = {
	schema: ""https://..."",
	documents: ""functions/**/*.{graphql,js,ts,jsx,tsx}"",
	extensions: {
		endpoints: {
			default: {
				url: ""https://..."",
				headers: {
					""secret"": ""....""
				},
			}
		}
	}
};
```

## Logs Of TS Server || GraphQL Language Service

![image](https://user-images.githubusercontent.com/8110568/144844781-6c8cea34-66af-4ce1-b001-814a124f4956.png)
",1.0,"Emojis in paths are not recognized - I have a file in a path like the following:
/Users/yair/Workspace/firebase-microservices/functions/src/microservice/retailer/⚡️onRetailerDB/index.ts

## Actual Behavior

It replaces the ⚡️ in the path with `%E2%9A%A1%EF%B8%8F`.


## Expected Behavior

To read the path with emojis correctly .

## Steps to Reproduce the Problem Or Description

Place a fragment in a folder which has an emoji in his name.

## Specifications

  - GraphQL for VSCode Extension Version: GraphQL Insiders v0.3.5
  - VSCode Version: 1.62.3
  - OS Name: Darwin x64
  - OS Version: 21.1.0
  - graphql config filename and format example:
```javascript
module.exports = {
	schema: ""https://..."",
	documents: ""functions/**/*.{graphql,js,ts,jsx,tsx}"",
	extensions: {
		endpoints: {
			default: {
				url: ""https://..."",
				headers: {
					""secret"": ""....""
				},
			}
		}
	}
};
```

## Logs Of TS Server || GraphQL Language Service

![image](https://user-images.githubusercontent.com/8110568/144844781-6c8cea34-66af-4ce1-b001-814a124f4956.png)
",0,emojis in paths are not recognized   i have a file in a path like the following    users yair workspace firebase microservices functions src microservice retailer ⚡️onretailerdb index ts       actual behavior    it replaces the ⚡️ in the path with         ef               expected behavior    to read the path with emojis correctly         steps to reproduce the problem or description    place a fragment in a folder which has an emoji in his name        specifications        graphql for vscode extension version  graphql insiders            vscode version             os name  darwin        os version             graphql config filename and format example      javascript  module exports      	schema      	documents   functions       graphql js ts jsx tsx     	extensions     		endpoints     			default     				url      				headers     					 secret           				    			   		   	                 logs of ts server    graphql language service          ,0
123080,12191788361.0,IssuesEvent,2020-04-29 11:48:21,golang/go,https://api.github.com/repos/golang/go,closed,image: NewUniform doesn't have documentation,Documentation NeedsFix,"The [`image.NewUniform`](https://golang.org/pkg/image/#NewUniform) function is exported and should have a comment per https://golang.org/doc/effective_go.html#commentary.

This came up when I realized it's not clear whether it's better to write `image.NewUniform(c)` or `&image.Uniform{c}`. I thought maybe `image.NewUniform` is deprecated like `image.ZP`, but that's not the case given it doesn't even have a comment. But it's not easy to feel confident using an exported method in the Go standard library when it's not documented.

https://blog.golang.org/image-draw prefers `&image.Uniform{c}` style, but it's also from 2011. `NewUniform` was renamed from `NewColorImage` in 2011, so it has existed for quite a while.

/cc @nigeltao @robpike",1.0,"image: NewUniform doesn't have documentation - The [`image.NewUniform`](https://golang.org/pkg/image/#NewUniform) function is exported and should have a comment per https://golang.org/doc/effective_go.html#commentary.

This came up when I realized it's not clear whether it's better to write `image.NewUniform(c)` or `&image.Uniform{c}`. I thought maybe `image.NewUniform` is deprecated like `image.ZP`, but that's not the case given it doesn't even have a comment. But it's not easy to feel confident using an exported method in the Go standard library when it's not documented.

https://blog.golang.org/image-draw prefers `&image.Uniform{c}` style, but it's also from 2011. `NewUniform` was renamed from `NewColorImage` in 2011, so it has existed for quite a while.

/cc @nigeltao @robpike",1,image  newuniform doesn t have documentation   the     function is exported and should have a comment per      this came up when i realized it s not clear whether it s better to write  image newuniform c   or   image uniform c    i thought maybe  image newuniform  is deprecated like  image zp   but that s not the case given it doesn t even have a comment  but it s not easy to feel confident using an exported method in the go standard library when it s not documented       prefers   image uniform c   style  but it s also from     newuniform  was renamed from  newcolorimage  in    so it has existed for quite a while      cc  nigeltao  robpike,1
60441,17023426001.0,IssuesEvent,2021-07-03 01:58:15,tomhughes/trac-tickets,https://api.github.com/repos/tomhughes/trac-tickets,closed,Rails should auto-select the last language I blogged in as the language for new blog posts by default,Component: website Priority: major Resolution: fixed Type: defect,"**[Submitted to the original trac issue database at 1.15am, Wednesday, 17th June 2009]**

My UI language != my blogging language.",1.0,"Rails should auto-select the last language I blogged in as the language for new blog posts by default - **[Submitted to the original trac issue database at 1.15am, Wednesday, 17th June 2009]**

My UI language != my blogging language.",0,rails should auto select the last language i blogged in as the language for new blog posts by default          my ui language    my blogging language ,0
85860,10466780926.0,IssuesEvent,2019-09-21 21:47:14,golang/go,https://api.github.com/repos/golang/go,closed,strings: EqualFold doc could be clearer,Documentation NeedsFix help wanted,"The doc for EqualFold says:

> EqualFold reports whether s and t, interpreted as UTF-8 strings, are equal under Unicode case-folding.

I have been using Go for over five years now and had no idea what ""Unicode case-folding"" was until about three minutes ago. Previously I had implemented this by calling `strings.ToLower` on each side, which is slow and unnecessary. More commonly I believe the EqualFold functionality is known as ""case insensitive matching."" Users who are searching the strings documentation for the phrase ""case insensitive"" will find nothing, when they should be finding this function. 

Scanning Github this seems like a common mistake:

https://github.com/sachin-varade/network/blob/5d4ab4a3757603b8c0ba9a9df7bc9e0ff92ad102/app/utils/setup/chaincode/processors/read_ledger.go#L172
https://github.com/projectriri/bot-gateway/blob/d4402bd4ac0d4478bd86e585ca83e9d3fc1c140e/converters/cqhttp-ubm-conv/cqhttp-ubm-conv.go#L79

Several Go vetters/linters have checks for this construction that suggest using EqualFold instead:

https://github.com/dominikh/go-tools/blob/1da3061645b400d55be4855f104d8a68ca0a61e5/staticcheck/testdata/src/CheckToLowerToUpperComparison/CheckToLowerToUpperComparison.go

StackOverflow answers suggesting the use of EqualFold have 35,000 views and 10,000 views, respectively. 

https://stackoverflow.com/q/24836044/329700
https://stackoverflow.com/q/30196780/329700",1.0,"strings: EqualFold doc could be clearer - The doc for EqualFold says:

> EqualFold reports whether s and t, interpreted as UTF-8 strings, are equal under Unicode case-folding.

I have been using Go for over five years now and had no idea what ""Unicode case-folding"" was until about three minutes ago. Previously I had implemented this by calling `strings.ToLower` on each side, which is slow and unnecessary. More commonly I believe the EqualFold functionality is known as ""case insensitive matching."" Users who are searching the strings documentation for the phrase ""case insensitive"" will find nothing, when they should be finding this function. 

Scanning Github this seems like a common mistake:

https://github.com/sachin-varade/network/blob/5d4ab4a3757603b8c0ba9a9df7bc9e0ff92ad102/app/utils/setup/chaincode/processors/read_ledger.go#L172
https://github.com/projectriri/bot-gateway/blob/d4402bd4ac0d4478bd86e585ca83e9d3fc1c140e/converters/cqhttp-ubm-conv/cqhttp-ubm-conv.go#L79

Several Go vetters/linters have checks for this construction that suggest using EqualFold instead:

https://github.com/dominikh/go-tools/blob/1da3061645b400d55be4855f104d8a68ca0a61e5/staticcheck/testdata/src/CheckToLowerToUpperComparison/CheckToLowerToUpperComparison.go

StackOverflow answers suggesting the use of EqualFold have 35,000 views and 10,000 views, respectively. 

https://stackoverflow.com/q/24836044/329700
https://stackoverflow.com/q/30196780/329700",1,strings  equalfold doc could be clearer   the doc for equalfold says       equalfold reports whether s and t  interpreted as utf   strings  are equal under unicode case folding     i have been using go for over five years now and had no idea what  unicode case folding  was until about three minutes ago  previously i had implemented this by calling  strings tolower  on each side  which is slow and unnecessary  more commonly i believe the equalfold functionality is known as  case insensitive matching   users who are searching the strings documentation for the phrase  case insensitive  will find nothing  when they should be finding this function      scanning github this seems like a common mistake             several go vetters linters have checks for this construction that suggest using equalfold instead          stackoverflow answers suggesting the use of equalfold have     views and     views  respectively          ,1
282099,24449966424.0,IssuesEvent,2022-10-06 21:42:26,pytorch/pytorch,https://api.github.com/repos/pytorch/pytorch,opened,DISABLED test_grad_linalg_lu_cuda_float32 (__main__.TestOperatorsCUDA),module: flaky-tests skipped module: unknown,"Platforms: linux

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_grad_linalg_lu_cuda_float32&suite=TestOperatorsCUDA) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/8748650143).

Over the past 3 hours, it has been determined flaky in 1 workflow(s) with 1 failures and 1 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT BE ALARMED IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_grad_linalg_lu_cuda_float32`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.
",1.0,"DISABLED test_grad_linalg_lu_cuda_float32 (__main__.TestOperatorsCUDA) - Platforms: linux

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_grad_linalg_lu_cuda_float32&suite=TestOperatorsCUDA) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/8748650143).

Over the past 3 hours, it has been determined flaky in 1 workflow(s) with 1 failures and 1 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT BE ALARMED IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_grad_linalg_lu_cuda_float32`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.
",0,disabled test grad linalg lu cuda      main   testoperatorscuda    platforms  linux  this test was disabled because it is failing in ci  see     and the most recent trunk      over the past   hours  it has been determined flaky in   workflow s  with   failures and   successes     debugging instructions  after clicking on the recent samples link     do not be alarmed if the ci is green  we now shield flaky tests from developers so ci will thus be green but it will be harder to parse the logs  to find relevant log snippets     click on the workflow logs linked above    click on the test step of the job so that it is expanded  otherwise  the grepping will not work     grep for  test grad linalg lu cuda       there should be several instances run  as flaky tests are rerun in ci  from which you can study the logs  ,0
5677,3265797717.0,IssuesEvent,2015-10-22 17:49:59,code-cracker/code-cracker,https://api.github.com/repos/code-cracker/code-cracker,closed,UnusedParametersCodeFixProvider crashing when removing params,2 - Working bug C# code-fix VB,"Related to #533.

This will throw an error on the code fix provider:

````vb
Class Foo
    Sub Baz()
        go(1, 2)
    End Sub
    Function go(i As Integer, j As Integer, ParamArray xs As Integer())
        i += 1
        Return 1
    End Function
End Class
````

Params and ParamArray are working, but when trying to remove a parameter that has no argument passed to it (see above that the invocation to `Go(1,2)` does not pass an argument to `xs`) it throws.
Affects C# and VB. Both need fixing, and the fix is likely the same.",1.0,"UnusedParametersCodeFixProvider crashing when removing params - Related to #533.

This will throw an error on the code fix provider:

````vb
Class Foo
    Sub Baz()
        go(1, 2)
    End Sub
    Function go(i As Integer, j As Integer, ParamArray xs As Integer())
        i += 1
        Return 1
    End Function
End Class
````

Params and ParamArray are working, but when trying to remove a parameter that has no argument passed to it (see above that the invocation to `Go(1,2)` does not pass an argument to `xs`) it throws.
Affects C# and VB. Both need fixing, and the fix is likely the same.",0,unusedparameterscodefixprovider crashing when removing params   related to        this will throw an error on the code fix provider         vb  class foo      sub baz            go            end sub      function go i as integer  j as integer  paramarray xs as integer             i               return        end function  end class          params and paramarray are working  but when trying to remove a parameter that has no argument passed to it  see above that the invocation to  go       does not pass an argument to  xs   it throws   affects c  and vb  both need fixing  and the fix is likely the same ,0
113733,11813127410.0,IssuesEvent,2020-03-19 21:38:35,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: explain automatic vendoring in 'go help modules',Documentation NeedsFix modules,"[`go help modules`](https://golang.org/cmd/go/#hdr-Modules_and_vendoring) states that the `go` command ignores `vendor` directories in module mode unless the `-mod=vendor` flag is given. This is not accurate. Since #33848 was implemented in Go 1.14, `-mod=vendor` may be enabled automatically. We should describe that.

Thanks to @myitcv for pointing this out.

cc @bcmills @matloob 

",1.0,"cmd/go: explain automatic vendoring in 'go help modules' - [`go help modules`](https://golang.org/cmd/go/#hdr-Modules_and_vendoring) states that the `go` command ignores `vendor` directories in module mode unless the `-mod=vendor` flag is given. This is not accurate. Since #33848 was implemented in Go 1.14, `-mod=vendor` may be enabled automatically. We should describe that.

Thanks to @myitcv for pointing this out.

cc @bcmills @matloob 

",1,cmd go  explain automatic vendoring in  go help modules        states that the  go  command ignores  vendor  directories in module mode unless the   mod vendor  flag is given  this is not accurate  since    was implemented in go        mod vendor  may be enabled automatically  we should describe that     thanks to  myitcv for pointing this out     cc  bcmills  matloob     ,1
63653,8689964195.0,IssuesEvent,2018-12-03 20:10:41,golang/go,https://api.github.com/repos/golang/go,closed,net/http: reference CanonicalHeaderKey from Header docs,Documentation,"https://golang.org/pkg/net/http/#Header should say something about CanonicalHeaderKey

",1.0,"net/http: reference CanonicalHeaderKey from Header docs - https://golang.org/pkg/net/http/#Header should say something about CanonicalHeaderKey

",1,net http  reference canonicalheaderkey from header docs     should say something about canonicalheaderkey    ,1
54912,7930420940.0,IssuesEvent,2018-07-06 18:46:41,golang/go,https://api.github.com/repos/golang/go,closed,doc: update the Go faq about versioning,Documentation,"At the moment the Go faq says :

https://golang.org/doc/faq#get_version

> Work is underway on an experimental package management tool, dep, to learn more about how tooling can help package management. More information can be found in the dep FAQ.

I believe it should be updated to mention `vgo`",1.0,"doc: update the Go faq about versioning - At the moment the Go faq says :

https://golang.org/doc/faq#get_version

> Work is underway on an experimental package management tool, dep, to learn more about how tooling can help package management. More information can be found in the dep FAQ.

I believe it should be updated to mention `vgo`",1,doc  update the go faq about versioning   at the moment the go faq says             work is underway on an experimental package management tool  dep  to learn more about how tooling can help package management  more information can be found in the dep faq     i believe it should be updated to mention  vgo ,1
49612,7523410403.0,IssuesEvent,2018-04-13 00:51:03,golang/go,https://api.github.com/repos/golang/go,closed,time: Sub is inaccurate after computer has slept,Documentation NeedsFix,"Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?

`go version go1.9.2 darwin/amd64`

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/pmoore/go""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.9.2/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.9.2/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/v9/mll6p_rj5h94dt_m5m8j0f9c0000gn/T/go-build287238210=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
```

```
$ sw_vers
ProductName:	Mac OS X
ProductVersion:	10.13.1
BuildVersion:	17B1003
```

### What did you do?

I ran the following program, and then waited for my iMac sleep. I woke it up again.

```
$ cat main.go 
package main

import (
	""fmt""
	""time""
)

func main() {
	start := time.Now()
	for {
		time.Sleep(time.Second)
		end := time.Now()
		fmt.Printf(""Start: %v, End: %v, Duration: %v\n"", start, end, end.Sub(start))
	}
}
$ go run main.go 
....
....
Start: 2017-12-19 14:03:49.50865 +0100 CET m=+0.000389566, End: 2017-12-19 14:06:22.691501 +0100 CET m=+153.190165077, Duration: 2m33.189775511s
Start: 2017-12-19 14:03:49.50865 +0100 CET m=+0.000389566, End: 2017-12-19 14:06:23.691737 +0100 CET m=+154.190447504, Duration: 2m34.190057938s
Start: 2017-12-19 14:03:49.50865 +0100 CET m=+0.000389566, End: 2017-12-19 14:06:24.691824 +0100 CET m=+155.190580407, Duration: 2m35.190190841s
Start: 2017-12-19 14:03:49.50865 +0100 CET m=+0.000389566, End: 2017-12-19 14:06:25.692191 +0100 CET m=+156.190990386, Duration: 2m36.19060082s
Start: 2017-12-19 14:03:49.50865 +0100 CET m=+0.000389566, End: 2017-12-19 14:06:26.692307 +0100 CET m=+157.191153372, Duration: 2m37.190763806s
Start: 2017-12-19 14:03:49.50865 +0100 CET m=+0.000389566, End: 2017-12-19 14:14:33.892169 +0100 CET m=+158.581754838, Duration: 2m38.581365272s
Start: 2017-12-19 14:03:49.50865 +0100 CET m=+0.000389566, End: 2017-12-19 14:14:34.893832 +0100 CET m=+159.583462000, Duration: 2m39.583072434s
Start: 2017-12-19 14:03:49.50865 +0100 CET m=+0.000389566, End: 2017-12-19 14:14:35.894375 +0100 CET m=+160.584051261, Duration: 2m40.583661695s
Start: 2017-12-19 14:03:49.50865 +0100 CET m=+0.000389566, End: 2017-12-19 14:14:36.895479 +0100 CET m=+161.585199077, Duration: 2m41.584809511s
Start: 2017-12-19 14:03:49.50865 +0100 CET m=+0.000389566, End: 2017-12-19 14:14:37.895651 +0100 CET m=+162.585417039, Duration: 2m42.585027473s
```


### What did you expect to see?

I expected the log output for Duration to equal the difference between the timestamps logged for Start and End. For example, the last line is:
```
Start: 2017-12-19 14:03:49.50865 +0100 CET m=+0.000389566, End: 2017-12-19 14:14:37.895651 +0100 CET m=+162.585417039, Duration: 2m42.585027473s
```
If start is 14:03:49.5 and end is 14:14:37.9 then duration should be 10m48.4s not 2m42.6s.

Note, the 8 minute jump in end time from 14:06:26.7 to 14:14:33.9 was when the computer was sleeping.

### What did you see instead?

The duration calculation seemed to match the amount of _awake_ time between start and end time. Notice how when the end time jumps eight minutes (due to the computer being asleep), the duration only increments by around one second, as if no sleep had occurred.",1.0,"time: Sub is inaccurate after computer has slept - Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?

`go version go1.9.2 darwin/amd64`

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/pmoore/go""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.9.2/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.9.2/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/v9/mll6p_rj5h94dt_m5m8j0f9c0000gn/T/go-build287238210=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
```

```
$ sw_vers
ProductName:	Mac OS X
ProductVersion:	10.13.1
BuildVersion:	17B1003
```

### What did you do?

I ran the following program, and then waited for my iMac sleep. I woke it up again.

```
$ cat main.go 
package main

import (
	""fmt""
	""time""
)

func main() {
	start := time.Now()
	for {
		time.Sleep(time.Second)
		end := time.Now()
		fmt.Printf(""Start: %v, End: %v, Duration: %v\n"", start, end, end.Sub(start))
	}
}
$ go run main.go 
....
....
Start: 2017-12-19 14:03:49.50865 +0100 CET m=+0.000389566, End: 2017-12-19 14:06:22.691501 +0100 CET m=+153.190165077, Duration: 2m33.189775511s
Start: 2017-12-19 14:03:49.50865 +0100 CET m=+0.000389566, End: 2017-12-19 14:06:23.691737 +0100 CET m=+154.190447504, Duration: 2m34.190057938s
Start: 2017-12-19 14:03:49.50865 +0100 CET m=+0.000389566, End: 2017-12-19 14:06:24.691824 +0100 CET m=+155.190580407, Duration: 2m35.190190841s
Start: 2017-12-19 14:03:49.50865 +0100 CET m=+0.000389566, End: 2017-12-19 14:06:25.692191 +0100 CET m=+156.190990386, Duration: 2m36.19060082s
Start: 2017-12-19 14:03:49.50865 +0100 CET m=+0.000389566, End: 2017-12-19 14:06:26.692307 +0100 CET m=+157.191153372, Duration: 2m37.190763806s
Start: 2017-12-19 14:03:49.50865 +0100 CET m=+0.000389566, End: 2017-12-19 14:14:33.892169 +0100 CET m=+158.581754838, Duration: 2m38.581365272s
Start: 2017-12-19 14:03:49.50865 +0100 CET m=+0.000389566, End: 2017-12-19 14:14:34.893832 +0100 CET m=+159.583462000, Duration: 2m39.583072434s
Start: 2017-12-19 14:03:49.50865 +0100 CET m=+0.000389566, End: 2017-12-19 14:14:35.894375 +0100 CET m=+160.584051261, Duration: 2m40.583661695s
Start: 2017-12-19 14:03:49.50865 +0100 CET m=+0.000389566, End: 2017-12-19 14:14:36.895479 +0100 CET m=+161.585199077, Duration: 2m41.584809511s
Start: 2017-12-19 14:03:49.50865 +0100 CET m=+0.000389566, End: 2017-12-19 14:14:37.895651 +0100 CET m=+162.585417039, Duration: 2m42.585027473s
```


### What did you expect to see?

I expected the log output for Duration to equal the difference between the timestamps logged for Start and End. For example, the last line is:
```
Start: 2017-12-19 14:03:49.50865 +0100 CET m=+0.000389566, End: 2017-12-19 14:14:37.895651 +0100 CET m=+162.585417039, Duration: 2m42.585027473s
```
If start is 14:03:49.5 and end is 14:14:37.9 then duration should be 10m48.4s not 2m42.6s.

Note, the 8 minute jump in end time from 14:06:26.7 to 14:14:33.9 was when the computer was sleeping.

### What did you see instead?

The duration calculation seemed to match the amount of _awake_ time between start and end time. Notice how when the end time jumps eight minutes (due to the computer being asleep), the duration only increments by around one second, as if no sleep had occurred.",1,time  sub is inaccurate after computer has slept   please answer these questions before submitting your issue  thanks           what version of go are you using   go version        go version       darwin           does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env            goarch      gobin     goexe     gohostarch      gohostos  darwin   goos  darwin   gopath   users pmoore go   gorace     goroot   usr local cellar go       libexec   gotooldir   usr local cellar go       libexec pkg tool darwin     gccgo  gccgo   cc  clang   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders         t go    tmp go build  gno record gcc switches  fno common   cxx  clang     cgo enabled      cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config                 sw vers  productname 	mac os x  productversion 	       buildversion 	              what did you do     i ran the following program  and then waited for my imac sleep  i woke it up again            cat main go   package main    import    	 fmt   	 time        func main      	start    time now    	for    		time sleep time second   		end    time now    		fmt printf  start   v  end   v  duration   v n   start  end  end sub start    	        go run main go               start                   cet m       end                   cet m       duration       start                   cet m       end                   cet m       duration       start                   cet m       end                   cet m       duration       start                   cet m       end                   cet m       duration       start                   cet m       end                   cet m       duration       start                   cet m       end                   cet m       duration       start                   cet m       end                   cet m       duration       start                   cet m       end                   cet m       duration       start                   cet m       end                   cet m       duration       start                   cet m       end                   cet m       duration                    what did you expect to see     i expected the log output for duration to equal the difference between the timestamps logged for start and end  for example  the last line is        start                   cet m       end                   cet m       duration            if start is         and end is         then duration should be     not         note  the   minute jump in end time from         to         was when the computer was sleeping         what did you see instead     the duration calculation seemed to match the amount of  awake  time between start and end time  notice how when the end time jumps eight minutes  due to the computer being asleep   the duration only increments by around one second  as if no sleep had occurred ,1
815661,30566541508.0,IssuesEvent,2023-07-20 18:14:22,googleapis/retry-request,https://api.github.com/repos/googleapis/retry-request,closed,retry-request: has an initial delay when currentRetryAttempt > 0 failed,type: bug priority: p1 flakybot: issue flakybot: flaky,"This test failed!

To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/main/packages/flakybot).

If I'm commenting on this issue too often, add the `flakybot: quiet` label and
I will stop commenting.

---

commit: 2fc51de310363b7d87c0cc503f6a9a94647dff6f
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/f8c20c39-6466-4e38-b84f-9e7f5a5baa9d), [Sponge](http://sponge2/f8c20c39-6466-4e38-b84f-9e7f5a5baa9d)
status: failed
<details><summary>Test output</summary><br><pre>The expression evaluated to a falsy value:

  assert(totalTime >= 2000 && totalTime < 3000)


      + expected - actual

      -false
      +true
      
AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:

  assert(totalTime >= 2000 && totalTime < 3000)

    at /workspace/test.js:437:7
    at onResponse (index.js:240:7)
    at Object.request (test.js:431:9)
    at Timeout.makeRequest [as _onTimeout] (index.js:171:28)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)</pre></details>",1.0,"retry-request: has an initial delay when currentRetryAttempt > 0 failed - This test failed!

To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/main/packages/flakybot).

If I'm commenting on this issue too often, add the `flakybot: quiet` label and
I will stop commenting.

---

commit: 2fc51de310363b7d87c0cc503f6a9a94647dff6f
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/f8c20c39-6466-4e38-b84f-9e7f5a5baa9d), [Sponge](http://sponge2/f8c20c39-6466-4e38-b84f-9e7f5a5baa9d)
status: failed
<details><summary>Test output</summary><br><pre>The expression evaluated to a falsy value:

  assert(totalTime >= 2000 && totalTime < 3000)


      + expected - actual

      -false
      +true
      
AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:

  assert(totalTime >= 2000 && totalTime < 3000)

    at /workspace/test.js:437:7
    at onResponse (index.js:240:7)
    at Object.request (test.js:431:9)
    at Timeout.makeRequest [as _onTimeout] (index.js:171:28)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)</pre></details>",0,retry request  has an initial delay when currentretryattempt     failed   this test failed   to configure my behavior  see      if i m commenting on this issue too often  add the  flakybot  quiet  label and i will stop commenting        commit    buildurl          status  failed   test output   the expression evaluated to a falsy value     assert totaltime         totaltime                expected   actual         false        true        assertionerror    the expression evaluated to a falsy value     assert totaltime         totaltime           at  workspace test js         at onresponse  index js          at object request  test js          at timeout makerequest    index js          at listontimeout  internal timers js          at processtimers  internal timers js       ,0
102461,4155917072.0,IssuesEvent,2016-06-16 16:16:34,18F/web-design-standards,https://api.github.com/repos/18F/web-design-standards,closed,"[Medium Footer] Inconsistent text line breaks in footer in IE 11, 1024x768 screen",[Category] Front end [Priority] Major [Status] In progress [Type] Bug,"**Steps to recreate**

1. Open the site in IE 11, set screen to 1024x768 and navigate to the medium footer
2. Note that the text links have inconsistent line breaks

<img width=""540"" alt=""screen shot 2015-09-09 at 10 33 39 am"" src=""https://cloud.githubusercontent.com/assets/10144074/9772970/840dffdc-570d-11e5-9c0a-67ade0cfe312.png"">

**Expected behavior**
I would expect that the links would line break consistently. 

**Tested on**
IE 11
Windows 10
SauceLabs",1.0,"[Medium Footer] Inconsistent text line breaks in footer in IE 11, 1024x768 screen - **Steps to recreate**

1. Open the site in IE 11, set screen to 1024x768 and navigate to the medium footer
2. Note that the text links have inconsistent line breaks

<img width=""540"" alt=""screen shot 2015-09-09 at 10 33 39 am"" src=""https://cloud.githubusercontent.com/assets/10144074/9772970/840dffdc-570d-11e5-9c0a-67ade0cfe312.png"">

**Expected behavior**
I would expect that the links would line break consistently. 

**Tested on**
IE 11
Windows 10
SauceLabs",0,  inconsistent text line breaks in footer in ie      screen     steps to recreate         open the site in ie    set screen to   and navigate to the medium footer     note that the text links have inconsistent line breaks     img width     alt  screen shot       at       am  src         expected behavior    i would expect that the links would line break consistently        tested on    ie    windows    saucelabs,0
216943,16675122578.0,IssuesEvent,2021-06-07 15:18:31,golang/go,https://api.github.com/repos/golang/go,closed,"fmt: package documentation doesn't have linkable subheadings under top-level ""Printing"" and ""Scanning"" sections",Documentation NeedsFix,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.16.3 windows/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes, including on tip.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
set GO111MODULE=on
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\zephyr\AppData\Local\go-build
set GOENV=C:\Users\zephyr\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=E:\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=E:\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=c:\go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=c:\go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.16.3
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=NUL
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\zephyr\AppData\Local\Temp
\go-build1861236026=/tmp/go-build -gno-record-gcc-switches
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

I explained the explicit argument syntax for printf formatting verbs to someone, then tried to get a useful link to an authoritative source in golang.org/pkg/fmt to explain more thoroughly.

### What did you expect to see?

An anchored section on explicit argument indices in the package documentation.

### What did you see instead?

A ""section"" on explicit argument indices, but not one recognized by godoc because the line ends with punctuation:

https://github.com/golang/go/blob/6e189afd3e7a3722c72b320ef604bf2910aee9e7/src/fmt/doc.go#L191-L193

It seems plausible that this is intentional, as the current structure leaves ""Printing"" and ""Scanning"" as the only proper sections. However, not having explicit sections for this particular topic – which seems to be underused – makes it harder to explain and promote its usefulness, particularly because there is no hyperlink to it.

The current document also flows less effectively as a result of these broken sections. There is another subsequent pseudo-section like this on ""Format errors:"", but also many earlier lines describing the flags for various types; those lines follow this format, but they do not seem to be intended to be distinct subsections. The explicit argument indices section itself is shortly preceded by the line ""convert the value before recurring:"", which makes it hard to recognize that the former is a distinct section.",1.0,"fmt: package documentation doesn't have linkable subheadings under top-level ""Printing"" and ""Scanning"" sections - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.16.3 windows/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes, including on tip.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
set GO111MODULE=on
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\zephyr\AppData\Local\go-build
set GOENV=C:\Users\zephyr\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=E:\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=E:\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=c:\go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=c:\go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.16.3
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=NUL
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\zephyr\AppData\Local\Temp
\go-build1861236026=/tmp/go-build -gno-record-gcc-switches
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

I explained the explicit argument syntax for printf formatting verbs to someone, then tried to get a useful link to an authoritative source in golang.org/pkg/fmt to explain more thoroughly.

### What did you expect to see?

An anchored section on explicit argument indices in the package documentation.

### What did you see instead?

A ""section"" on explicit argument indices, but not one recognized by godoc because the line ends with punctuation:

https://github.com/golang/go/blob/6e189afd3e7a3722c72b320ef604bf2910aee9e7/src/fmt/doc.go#L191-L193

It seems plausible that this is intentional, as the current structure leaves ""Printing"" and ""Scanning"" as the only proper sections. However, not having explicit sections for this particular topic – which seems to be underused – makes it harder to explain and promote its usefulness, particularly because there is no hyperlink to it.

The current document also flows less effectively as a result of these broken sections. There is another subsequent pseudo-section like this on ""Format errors:"", but also many earlier lines describing the flags for various types; those lines follow this format, but they do not seem to be intended to be distinct subsections. The explicit argument indices section itself is shortly preceded by the line ""convert the value before recurring:"", which makes it hard to recognize that the former is a distinct section.",1,fmt  package documentation doesn t have linkable subheadings under top level  printing  and  scanning  sections         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version            go version  go version       windows             does this issue reproduce with the latest release     yes  including on tip         what operating system and processor architecture are you using   go env          go env  output       go env  set   on  set goarch    set gobin   set gocache c  users zephyr appdata local go build  set goenv c  users zephyr appdata roaming go env  set goexe  exe  set goflags   set gohostarch    set gohostos windows  set goinsecure   set gomodcache e  go pkg mod  set gonoproxy   set gonosumdb   set goos windows  set gopath e  go  set goprivate   set goproxy    set goroot c  go  set gosumdb sum golang org  set gotmpdir   set gotooldir c  go pkg tool windows    set govcs   set goversion        set gccgo gccgo  set ar ar  set cc gcc  set cxx g    set cgo enabled    set gomod nul  set cgo cflags  g     set cgo cppflags   set cgo cxxflags  g     set cgo fflags  g     set cgo ldflags  g     set pkg config pkg config  set gogccflags     mthreads  fmessage length    fdebug prefix map c  users zephyr appdata local temp   go    tmp go build  gno record gcc switches            what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best          i explained the explicit argument syntax for printf formatting verbs to someone  then tried to get a useful link to an authoritative source in golang org pkg fmt to explain more thoroughly         what did you expect to see     an anchored section on explicit argument indices in the package documentation         what did you see instead     a  section  on explicit argument indices  but not one recognized by godoc because the line ends with punctuation          it seems plausible that this is intentional  as the current structure leaves  printing  and  scanning  as the only proper sections  however  not having explicit sections for this particular topic – which seems to be underused – makes it harder to explain and promote its usefulness  particularly because there is no hyperlink to it     the current document also flows less effectively as a result of these broken sections  there is another subsequent pseudo section like this on  format errors    but also many earlier lines describing the flags for various types  those lines follow this format  but they do not seem to be intended to be distinct subsections  the explicit argument indices section itself is shortly preceded by the line  convert the value before recurring    which makes it hard to recognize that the former is a distinct section ,1
725384,24960910492.0,IssuesEvent,2022-11-01 15:27:14,o3de/o3de,https://api.github.com/repos/o3de/o3de,closed,Action Manager: Attempting to customize the default Tool Bar with the Action Manager enabled crashes the Editor,feature/editor kind/bug sig/content triage/accepted priority/critical,"**Describe the bug**
Attempting to customize the default Tool Bar with the Action Manager enabled crashes the Editor.

```
Call Stack Trace:
25) 00007FFB4B2F0057 (KERNELBASE) : UnhandledExceptionFilter
24) 00007FFB4D4F5470 (ntdll) : memset
23) 00007FFB4D4DC7B6 (ntdll) : _C_specific_handler
22) 00007FFB4D4F235F (ntdll) : _chkstk
21) 00007FFB4D4A14A4 (ntdll) : RtlRaiseException
20) 00007FFB4D4F0E8E (ntdll) : KiUserExceptionDispatcher
19) D:\GitHub\o3de\Code\Editor\ToolbarCustomizationDialog.cpp (52) : ToolbarCustomizationDialog::ToolbarCustomizationDialog
18) D:\GitHub\o3de\Code\Editor\MainWindow.cpp (2017) : MainWindow::ShowCustomizeToolbarDialog
17) 00007FFAD30909AA (Qt5Core) : QObject::qt_static_metacall
16) 00007FFACA165DBF (Qt5Widgets) : QAction::activate
15) 00007FFACA2BBFC8 (Qt5Widgets) : QMenu::actionGeometry
14) 00007FFACA2BBDA3 (Qt5Widgets) : QMenu::actionGeometry
13) 00007FFACA2C1561 (Qt5Widgets) : QMenu::mouseReleaseEvent
12) 00007FFACA197912 (Qt5Widgets) : QWidget::event
11) 00007FFACA2BD567 (Qt5Widgets) : QMenu::event
10) 00007FFACA1749A1 (Qt5Widgets) : QApplicationPrivate::notify_helper
 9) 00007FFACA1728C0 (Qt5Widgets) : QApplication::notify
 8) 00007FFAD30717CB (Qt5Core) : QCoreApplication::notifyInternal2
 7) 00007FFACA175BB5 (Qt5Widgets) : QApplicationPrivate::sendMouseEvent
 6) 00007FFACA1C0013 (Qt5Widgets) : QSizePolicy::QSizePolicy
 5) 00007FFACA1BE5FE (Qt5Widgets) : QSizePolicy::QSizePolicy
 4) 00007FFACA1749A1 (Qt5Widgets) : QApplicationPrivate::notify_helper
 3) 00007FFACA173A23 (Qt5Widgets) : QApplication::notify
 2) 00007FFAD30717CB (Qt5Core) : QCoreApplication::notifyInternal2
 1) 00007FFAC4514915 (Qt5Gui) : QGuiApplicationPrivate::processMouseEvent
```

**Steps to reproduce**
1. Launch the Editor with the new Action Manager created Menus active:
```
Editor.exe --regset=O3DE/ActionManager/EnableNewActionManager=true
```
2. Right-click the toolbar below the menu bar.
3. Click ""Customize...""

**Expected behavior**
Customization dialog opens.

**Actual behavior**
Editor crashes with the call stack posted above.

**Found in Branch**
development@ 221cd9e5c29ecc480d9cb0155c00a6280e678c2f

**Desktop/Device:**
 - Device: PC
 - OS: Windows 10 21H1
 - CPU: Ryzen 5950x
 - GPU: Nvidia 2070
 - Memory: 64GB",1.0,"Action Manager: Attempting to customize the default Tool Bar with the Action Manager enabled crashes the Editor - **Describe the bug**
Attempting to customize the default Tool Bar with the Action Manager enabled crashes the Editor.

```
Call Stack Trace:
25) 00007FFB4B2F0057 (KERNELBASE) : UnhandledExceptionFilter
24) 00007FFB4D4F5470 (ntdll) : memset
23) 00007FFB4D4DC7B6 (ntdll) : _C_specific_handler
22) 00007FFB4D4F235F (ntdll) : _chkstk
21) 00007FFB4D4A14A4 (ntdll) : RtlRaiseException
20) 00007FFB4D4F0E8E (ntdll) : KiUserExceptionDispatcher
19) D:\GitHub\o3de\Code\Editor\ToolbarCustomizationDialog.cpp (52) : ToolbarCustomizationDialog::ToolbarCustomizationDialog
18) D:\GitHub\o3de\Code\Editor\MainWindow.cpp (2017) : MainWindow::ShowCustomizeToolbarDialog
17) 00007FFAD30909AA (Qt5Core) : QObject::qt_static_metacall
16) 00007FFACA165DBF (Qt5Widgets) : QAction::activate
15) 00007FFACA2BBFC8 (Qt5Widgets) : QMenu::actionGeometry
14) 00007FFACA2BBDA3 (Qt5Widgets) : QMenu::actionGeometry
13) 00007FFACA2C1561 (Qt5Widgets) : QMenu::mouseReleaseEvent
12) 00007FFACA197912 (Qt5Widgets) : QWidget::event
11) 00007FFACA2BD567 (Qt5Widgets) : QMenu::event
10) 00007FFACA1749A1 (Qt5Widgets) : QApplicationPrivate::notify_helper
 9) 00007FFACA1728C0 (Qt5Widgets) : QApplication::notify
 8) 00007FFAD30717CB (Qt5Core) : QCoreApplication::notifyInternal2
 7) 00007FFACA175BB5 (Qt5Widgets) : QApplicationPrivate::sendMouseEvent
 6) 00007FFACA1C0013 (Qt5Widgets) : QSizePolicy::QSizePolicy
 5) 00007FFACA1BE5FE (Qt5Widgets) : QSizePolicy::QSizePolicy
 4) 00007FFACA1749A1 (Qt5Widgets) : QApplicationPrivate::notify_helper
 3) 00007FFACA173A23 (Qt5Widgets) : QApplication::notify
 2) 00007FFAD30717CB (Qt5Core) : QCoreApplication::notifyInternal2
 1) 00007FFAC4514915 (Qt5Gui) : QGuiApplicationPrivate::processMouseEvent
```

**Steps to reproduce**
1. Launch the Editor with the new Action Manager created Menus active:
```
Editor.exe --regset=O3DE/ActionManager/EnableNewActionManager=true
```
2. Right-click the toolbar below the menu bar.
3. Click ""Customize...""

**Expected behavior**
Customization dialog opens.

**Actual behavior**
Editor crashes with the call stack posted above.

**Found in Branch**
development@ 221cd9e5c29ecc480d9cb0155c00a6280e678c2f

**Desktop/Device:**
 - Device: PC
 - OS: Windows 10 21H1
 - CPU: Ryzen 5950x
 - GPU: Nvidia 2070
 - Memory: 64GB",0,action manager  attempting to customize the default tool bar with the action manager enabled crashes the editor     describe the bug    attempting to customize the default tool bar with the action manager enabled crashes the editor          call stack trace         kernelbase    unhandledexceptionfilter        ntdll    memset        ntdll     c specific handler        ntdll     chkstk        ntdll    rtlraiseexception        ntdll    kiuserexceptiondispatcher     d  github   code editor toolbarcustomizationdialog cpp       toolbarcustomizationdialog  toolbarcustomizationdialog     d  github   code editor mainwindow cpp       mainwindow  showcustomizetoolbardialog             qobject  qt static metacall             qaction  activate             qmenu  actiongeometry             qmenu  actiongeometry             qmenu  mousereleaseevent             qwidget  event             qmenu  event             qapplicationprivate  notify helper              qapplication  notify              qcoreapplication                 qapplicationprivate  sendmouseevent              qsizepolicy  qsizepolicy              qsizepolicy  qsizepolicy              qapplicationprivate  notify helper              qapplication  notify              qcoreapplication                 qguiapplicationprivate  processmouseevent           steps to reproduce       launch the editor with the new action manager created menus active        editor exe   regset   actionmanager enablenewactionmanager true          right click the toolbar below the menu bar      click  customize          expected behavior    customization dialog opens       actual behavior    editor crashes with the call stack posted above       found in branch    development         desktop device        device  pc     os  windows         cpu  ryzen       gpu  nvidia       memory   ,0
18314,4256240854.0,IssuesEvent,2016-07-10 00:36:24,golang/go,https://api.github.com/repos/golang/go,closed,fmt: define what %p means (or doesn't mean) on interfaces,Documentation,"(split from https://github.com/golang/go/issues/16230#issuecomment-231563421)

What does %p mean in the `fmt` package for interface values?

It seems to do something, but the documentation says nothing.

/cc @josharian @robpike ",1.0,"fmt: define what %p means (or doesn't mean) on interfaces - (split from https://github.com/golang/go/issues/16230#issuecomment-231563421)

What does %p mean in the `fmt` package for interface values?

It seems to do something, but the documentation says nothing.

/cc @josharian @robpike ",1,fmt  define what  p means  or doesn t mean  on interfaces    split from      what does  p mean in the  fmt  package for interface values     it seems to do something  but the documentation says nothing      cc  josharian  robpike ,1
123303,17772205416.0,IssuesEvent,2021-08-30 14:51:10,kapseliboi/RDocumentation-app,https://api.github.com/repos/kapseliboi/RDocumentation-app,opened,CVE-2017-16116 (High) detected in multiple libraries,security vulnerability,"## CVE-2017-16116 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>underscore.string-2.3.3.tgz</b>, <b>underscore.string-2.3.1.tgz</b>, <b>underscore.string-3.2.3.tgz</b>, <b>underscore.string-2.4.0.tgz</b>, <b>string-3.3.3.tgz</b>, <b>underscore.string-2.2.1.tgz</b></p></summary>
<p>

<details><summary><b>underscore.string-2.3.3.tgz</b></p></summary>

<p>String manipulation extensions for Underscore.js javascript library.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/underscore.string/-/underscore.string-2.3.3.tgz"">https://registry.npmjs.org/underscore.string/-/underscore.string-2.3.3.tgz</a></p>
<p>Path to dependency file: RDocumentation-app/package.json</p>
<p>Path to vulnerable library: RDocumentation-app/node_modules/sails-generate-controller/node_modules/underscore.string/package.json,RDocumentation-app/node_modules/sails-generate-model/node_modules/underscore.string/package.json,RDocumentation-app/node_modules/grunt-legacy-log/node_modules/underscore.string/package.json,RDocumentation-app/node_modules/sails-hook-sequelize-blueprints/node_modules/underscore.string/package.json,RDocumentation-app/node_modules/grunt-legacy-log-utils/node_modules/underscore.string/package.json,RDocumentation-app/node_modules/sails-util/node_modules/underscore.string/package.json</p>
<p>

Dependency Hierarchy:
  - grunt-0.4.5.tgz (Root Library)
    - grunt-legacy-log-0.1.3.tgz
      - :x: **underscore.string-2.3.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>underscore.string-2.3.1.tgz</b></p></summary>

<p>String manipulation extensions for Underscore.js javascript library.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/underscore.string/-/underscore.string-2.3.1.tgz"">https://registry.npmjs.org/underscore.string/-/underscore.string-2.3.1.tgz</a></p>
<p>Path to dependency file: RDocumentation-app/package.json</p>
<p>Path to vulnerable library: RDocumentation-app/node_modules/include-all/node_modules/underscore.string/package.json</p>
<p>

Dependency Hierarchy:
  - include-all-0.1.6.tgz (Root Library)
    - :x: **underscore.string-2.3.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>underscore.string-3.2.3.tgz</b></p></summary>

<p>String manipulation extensions for Underscore.js javascript library.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/underscore.string/-/underscore.string-3.2.3.tgz"">https://registry.npmjs.org/underscore.string/-/underscore.string-3.2.3.tgz</a></p>
<p>Path to dependency file: RDocumentation-app/package.json</p>
<p>Path to vulnerable library: RDocumentation-app/node_modules/sails/node_modules/underscore.string/package.json</p>
<p>

Dependency Hierarchy:
  - sails-0.12.11.tgz (Root Library)
    - grunt-1.0.1.tgz
      - grunt-legacy-log-1.0.0.tgz
        - :x: **underscore.string-3.2.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>underscore.string-2.4.0.tgz</b></p></summary>

<p>String manipulation extensions for Underscore.js javascript library.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/underscore.string/-/underscore.string-2.4.0.tgz"">https://registry.npmjs.org/underscore.string/-/underscore.string-2.4.0.tgz</a></p>
<p>Path to dependency file: RDocumentation-app/package.json</p>
<p>Path to vulnerable library: RDocumentation-app/node_modules/grunt/node_modules/argparse/node_modules/underscore.string/package.json</p>
<p>

Dependency Hierarchy:
  - grunt-0.4.5.tgz (Root Library)
    - js-yaml-2.0.5.tgz
      - argparse-0.1.16.tgz
        - :x: **underscore.string-2.4.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>string-3.3.3.tgz</b></p></summary>

<p>string contains methods that aren't included in the vanilla JavaScript string such as escaping html, decoding html entities, stripping tags, etc.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/string/-/string-3.3.3.tgz"">https://registry.npmjs.org/string/-/string-3.3.3.tgz</a></p>
<p>Path to dependency file: RDocumentation-app/package.json</p>
<p>Path to vulnerable library: RDocumentation-app/node_modules/string/package.json</p>
<p>

Dependency Hierarchy:
  - broken-link-checker-0.7.7.tgz (Root Library)
    - bhttp-1.2.4.tgz
      - :x: **string-3.3.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>underscore.string-2.2.1.tgz</b></p></summary>

<p>String manipulation extensions for Underscore.js javascript library.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/underscore.string/-/underscore.string-2.2.1.tgz"">https://registry.npmjs.org/underscore.string/-/underscore.string-2.2.1.tgz</a></p>
<p>Path to dependency file: RDocumentation-app/package.json</p>
<p>Path to vulnerable library: RDocumentation-app/node_modules/underscore.string/package.json</p>
<p>

Dependency Hierarchy:
  - grunt-0.4.5.tgz (Root Library)
    - :x: **underscore.string-2.2.1.tgz** (Vulnerable Library)
</details>

<p>Found in HEAD commit: <a href=""https://github.com/kapseliboi/RDocumentation-app/commit/ea1d4334329f74384d2d1b67f98e875da0b95310"">ea1d4334329f74384d2d1b67f98e875da0b95310</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The string module is a module that provides extra string operations. The string module is vulnerable to regular expression denial of service when specifically crafted untrusted user input is passed into the underscore or unescapeHTML methods.

<p>Publish Date: 2018-06-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16116>CVE-2017-16116</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://www.npmjs.com/advisories/745"">https://www.npmjs.com/advisories/745</a></p>
<p>Release Date: 2018-06-07</p>
<p>Fix Resolution: 3.3.5</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-2017-16116 (High) detected in multiple libraries - ## CVE-2017-16116 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>underscore.string-2.3.3.tgz</b>, <b>underscore.string-2.3.1.tgz</b>, <b>underscore.string-3.2.3.tgz</b>, <b>underscore.string-2.4.0.tgz</b>, <b>string-3.3.3.tgz</b>, <b>underscore.string-2.2.1.tgz</b></p></summary>
<p>

<details><summary><b>underscore.string-2.3.3.tgz</b></p></summary>

<p>String manipulation extensions for Underscore.js javascript library.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/underscore.string/-/underscore.string-2.3.3.tgz"">https://registry.npmjs.org/underscore.string/-/underscore.string-2.3.3.tgz</a></p>
<p>Path to dependency file: RDocumentation-app/package.json</p>
<p>Path to vulnerable library: RDocumentation-app/node_modules/sails-generate-controller/node_modules/underscore.string/package.json,RDocumentation-app/node_modules/sails-generate-model/node_modules/underscore.string/package.json,RDocumentation-app/node_modules/grunt-legacy-log/node_modules/underscore.string/package.json,RDocumentation-app/node_modules/sails-hook-sequelize-blueprints/node_modules/underscore.string/package.json,RDocumentation-app/node_modules/grunt-legacy-log-utils/node_modules/underscore.string/package.json,RDocumentation-app/node_modules/sails-util/node_modules/underscore.string/package.json</p>
<p>

Dependency Hierarchy:
  - grunt-0.4.5.tgz (Root Library)
    - grunt-legacy-log-0.1.3.tgz
      - :x: **underscore.string-2.3.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>underscore.string-2.3.1.tgz</b></p></summary>

<p>String manipulation extensions for Underscore.js javascript library.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/underscore.string/-/underscore.string-2.3.1.tgz"">https://registry.npmjs.org/underscore.string/-/underscore.string-2.3.1.tgz</a></p>
<p>Path to dependency file: RDocumentation-app/package.json</p>
<p>Path to vulnerable library: RDocumentation-app/node_modules/include-all/node_modules/underscore.string/package.json</p>
<p>

Dependency Hierarchy:
  - include-all-0.1.6.tgz (Root Library)
    - :x: **underscore.string-2.3.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>underscore.string-3.2.3.tgz</b></p></summary>

<p>String manipulation extensions for Underscore.js javascript library.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/underscore.string/-/underscore.string-3.2.3.tgz"">https://registry.npmjs.org/underscore.string/-/underscore.string-3.2.3.tgz</a></p>
<p>Path to dependency file: RDocumentation-app/package.json</p>
<p>Path to vulnerable library: RDocumentation-app/node_modules/sails/node_modules/underscore.string/package.json</p>
<p>

Dependency Hierarchy:
  - sails-0.12.11.tgz (Root Library)
    - grunt-1.0.1.tgz
      - grunt-legacy-log-1.0.0.tgz
        - :x: **underscore.string-3.2.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>underscore.string-2.4.0.tgz</b></p></summary>

<p>String manipulation extensions for Underscore.js javascript library.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/underscore.string/-/underscore.string-2.4.0.tgz"">https://registry.npmjs.org/underscore.string/-/underscore.string-2.4.0.tgz</a></p>
<p>Path to dependency file: RDocumentation-app/package.json</p>
<p>Path to vulnerable library: RDocumentation-app/node_modules/grunt/node_modules/argparse/node_modules/underscore.string/package.json</p>
<p>

Dependency Hierarchy:
  - grunt-0.4.5.tgz (Root Library)
    - js-yaml-2.0.5.tgz
      - argparse-0.1.16.tgz
        - :x: **underscore.string-2.4.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>string-3.3.3.tgz</b></p></summary>

<p>string contains methods that aren't included in the vanilla JavaScript string such as escaping html, decoding html entities, stripping tags, etc.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/string/-/string-3.3.3.tgz"">https://registry.npmjs.org/string/-/string-3.3.3.tgz</a></p>
<p>Path to dependency file: RDocumentation-app/package.json</p>
<p>Path to vulnerable library: RDocumentation-app/node_modules/string/package.json</p>
<p>

Dependency Hierarchy:
  - broken-link-checker-0.7.7.tgz (Root Library)
    - bhttp-1.2.4.tgz
      - :x: **string-3.3.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>underscore.string-2.2.1.tgz</b></p></summary>

<p>String manipulation extensions for Underscore.js javascript library.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/underscore.string/-/underscore.string-2.2.1.tgz"">https://registry.npmjs.org/underscore.string/-/underscore.string-2.2.1.tgz</a></p>
<p>Path to dependency file: RDocumentation-app/package.json</p>
<p>Path to vulnerable library: RDocumentation-app/node_modules/underscore.string/package.json</p>
<p>

Dependency Hierarchy:
  - grunt-0.4.5.tgz (Root Library)
    - :x: **underscore.string-2.2.1.tgz** (Vulnerable Library)
</details>

<p>Found in HEAD commit: <a href=""https://github.com/kapseliboi/RDocumentation-app/commit/ea1d4334329f74384d2d1b67f98e875da0b95310"">ea1d4334329f74384d2d1b67f98e875da0b95310</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The string module is a module that provides extra string operations. The string module is vulnerable to regular expression denial of service when specifically crafted untrusted user input is passed into the underscore or unescapeHTML methods.

<p>Publish Date: 2018-06-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16116>CVE-2017-16116</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://www.npmjs.com/advisories/745"">https://www.npmjs.com/advisories/745</a></p>
<p>Release Date: 2018-06-07</p>
<p>Fix Resolution: 3.3.5</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in multiple libraries      cve       high severity vulnerability     vulnerable libraries    underscore string       tgz    underscore string       tgz    underscore string       tgz    underscore string       tgz    string       tgz    underscore string       tgz          underscore string       tgz      string manipulation extensions for underscore js javascript library    library home page   a href     path to dependency file  rdocumentation app package json   path to vulnerable library  rdocumentation app node modules sails generate controller node modules underscore string package json rdocumentation app node modules sails generate model node modules underscore string package json rdocumentation app node modules grunt legacy log node modules underscore string package json rdocumentation app node modules sails hook sequelize blueprints node modules underscore string package json rdocumentation app node modules grunt legacy log utils node modules underscore string package json rdocumentation app node modules sails util node modules underscore string package json     dependency hierarchy      grunt       tgz  root library        grunt legacy log       tgz          x    underscore string       tgz    vulnerable library       underscore string       tgz      string manipulation extensions for underscore js javascript library    library home page   a href     path to dependency file  rdocumentation app package json   path to vulnerable library  rdocumentation app node modules include all node modules underscore string package json     dependency hierarchy      include all       tgz  root library         x    underscore string       tgz    vulnerable library       underscore string       tgz      string manipulation extensions for underscore js javascript library    library home page   a href     path to dependency file  rdocumentation app package json   path to vulnerable library  rdocumentation app node modules sails node modules underscore string package json     dependency hierarchy      sails       tgz  root library        grunt       tgz         grunt legacy log       tgz            x    underscore string       tgz    vulnerable library       underscore string       tgz      string manipulation extensions for underscore js javascript library    library home page   a href     path to dependency file  rdocumentation app package json   path to vulnerable library  rdocumentation app node modules grunt node modules argparse node modules underscore string package json     dependency hierarchy      grunt       tgz  root library        js yaml       tgz         argparse       tgz            x    underscore string       tgz    vulnerable library       string       tgz      string contains methods that aren t included in the vanilla javascript string such as escaping html  decoding html entities  stripping tags  etc    library home page   a href     path to dependency file  rdocumentation app package json   path to vulnerable library  rdocumentation app node modules string package json     dependency hierarchy      broken link checker       tgz  root library        bhttp       tgz          x    string       tgz    vulnerable library       underscore string       tgz      string manipulation extensions for underscore js javascript library    library home page   a href     path to dependency file  rdocumentation app package json   path to vulnerable library  rdocumentation app node modules underscore string package json     dependency hierarchy      grunt       tgz  root library         x    underscore string       tgz    vulnerable library      found in head commit   a href     found in base branch   master              vulnerability details         the string module is a module that provides extra string operations  the string module is vulnerable to regular expression denial of service when specifically crafted untrusted user input is passed into the underscore or unescapehtml methods    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                      step up your open source security game with whitesource    ,0
30445,5796681474.0,IssuesEvent,2017-05-02 20:03:51,golang/go,https://api.github.com/repos/golang/go,closed,doc: CLA instructions are out of date,Documentation NeedsFix,"https://golang.org/doc/contribute.html#cla suggests to navigate to Settings -> Agreements in gerrit. There is no menu entry called ""Agreements"" for me on https://go-review.googlesource.com/settings.",1.0,"doc: CLA instructions are out of date - https://golang.org/doc/contribute.html#cla suggests to navigate to Settings -> Agreements in gerrit. There is no menu entry called ""Agreements"" for me on https://go-review.googlesource.com/settings.",1,doc  cla instructions are out of date     suggests to navigate to settings    agreements in gerrit  there is no menu entry called  agreements  for me on  ,1
363174,25411994606.0,IssuesEvent,2022-11-22 19:51:49,golang/go,https://api.github.com/repos/golang/go,opened,x/sync/semaphore: document ordering of Weighted.Acquire,Documentation Proposal,"I was debugging a sluggish system and the problem came down to the ordering of how `Acquire` was satisfied.

The current behavior of `Weighted.Acquire` is that it serves acquisitions in order. This is a reasonable behavior, but it should be documented as it is significant performance implications. In particular, this behavior leads to head-of-line blocking where a large acquisition will prevent smaller acquisitions from making progress. The alternate behavior to satisfy any possible acquisition out-of-order, but that would lead to live-lock situations where a continuous stream of small acquisitions prevent a large acquisition from ever making progress.

My solution ended up splitting the semaphore into two parts:
* a semaphore for small requests
* a semaphore for large requests.

However, it was not obvious to me that I should do this since I had originally assumed that the semaphore allowed for out-of-order acquisitions.",1.0,"x/sync/semaphore: document ordering of Weighted.Acquire - I was debugging a sluggish system and the problem came down to the ordering of how `Acquire` was satisfied.

The current behavior of `Weighted.Acquire` is that it serves acquisitions in order. This is a reasonable behavior, but it should be documented as it is significant performance implications. In particular, this behavior leads to head-of-line blocking where a large acquisition will prevent smaller acquisitions from making progress. The alternate behavior to satisfy any possible acquisition out-of-order, but that would lead to live-lock situations where a continuous stream of small acquisitions prevent a large acquisition from ever making progress.

My solution ended up splitting the semaphore into two parts:
* a semaphore for small requests
* a semaphore for large requests.

However, it was not obvious to me that I should do this since I had originally assumed that the semaphore allowed for out-of-order acquisitions.",1,x sync semaphore  document ordering of weighted acquire   i was debugging a sluggish system and the problem came down to the ordering of how  acquire  was satisfied     the current behavior of  weighted acquire  is that it serves acquisitions in order  this is a reasonable behavior  but it should be documented as it is significant performance implications  in particular  this behavior leads to head of line blocking where a large acquisition will prevent smaller acquisitions from making progress  the alternate behavior to satisfy any possible acquisition out of order  but that would lead to live lock situations where a continuous stream of small acquisitions prevent a large acquisition from ever making progress     my solution ended up splitting the semaphore into two parts     a semaphore for small requests    a semaphore for large requests     however  it was not obvious to me that i should do this since i had originally assumed that the semaphore allowed for out of order acquisitions ,1
52713,13224961584.0,IssuesEvent,2020-08-17 20:12:20,icecube-trac/tix4,https://api.github.com/repos/icecube-trac/tix4,closed,Bayesian fits fail in OnlineL2 filter at pole (Trac #208),Migrated from Trac defect jeb + pnf,"All Bayesian fits in the OnlineL2 filtered events fail at the pole (I3Particle fit status: FailedToConverge) because the likelihood is not correctly defined for these fits. Only the bayesian prior is used, it is not combined with the Pandel likelihood.
Patch is attached.

<details>
 <summary><em>Migrated from <a href=""https://code.icecube.wisc.edu/projects/icecube/ticket/208"">https://code.icecube.wisc.edu/projects/icecube/ticket/208</a>, reported by rfrankeand owned by blaufuss</em></summary>
<p>

```json
{
    ""status"": ""closed"",
    ""changetime"": ""2010-06-16T16:52:27"",
    ""_ts"": ""1276707147000000"",
    ""description"": ""All Bayesian fits in the OnlineL2 filtered events fail at the pole (I3Particle fit status: FailedToConverge) because the likelihood is not correctly defined for these fits. Only the bayesian prior is used, it is not combined with the Pandel likelihood.\nPatch is attached."",
    ""reporter"": ""rfranke"",
    ""cc"": ""anna.franckowiak@googlemail.com, andreas.homeier@googlemail.com"",
    ""resolution"": ""fixed"",
    ""time"": ""2010-06-16T15:04:34"",
    ""component"": ""jeb + pnf"",
    ""summary"": ""Bayesian fits fail in OnlineL2 filter at pole"",
    ""priority"": ""normal"",
    ""keywords"": """",
    ""milestone"": """",
    ""owner"": ""blaufuss"",
    ""type"": ""defect""
}
```

</p>
</details>
",1.0,"Bayesian fits fail in OnlineL2 filter at pole (Trac #208) - All Bayesian fits in the OnlineL2 filtered events fail at the pole (I3Particle fit status: FailedToConverge) because the likelihood is not correctly defined for these fits. Only the bayesian prior is used, it is not combined with the Pandel likelihood.
Patch is attached.

<details>
 <summary><em>Migrated from <a href=""https://code.icecube.wisc.edu/projects/icecube/ticket/208"">https://code.icecube.wisc.edu/projects/icecube/ticket/208</a>, reported by rfrankeand owned by blaufuss</em></summary>
<p>

```json
{
    ""status"": ""closed"",
    ""changetime"": ""2010-06-16T16:52:27"",
    ""_ts"": ""1276707147000000"",
    ""description"": ""All Bayesian fits in the OnlineL2 filtered events fail at the pole (I3Particle fit status: FailedToConverge) because the likelihood is not correctly defined for these fits. Only the bayesian prior is used, it is not combined with the Pandel likelihood.\nPatch is attached."",
    ""reporter"": ""rfranke"",
    ""cc"": ""anna.franckowiak@googlemail.com, andreas.homeier@googlemail.com"",
    ""resolution"": ""fixed"",
    ""time"": ""2010-06-16T15:04:34"",
    ""component"": ""jeb + pnf"",
    ""summary"": ""Bayesian fits fail in OnlineL2 filter at pole"",
    ""priority"": ""normal"",
    ""keywords"": """",
    ""milestone"": """",
    ""owner"": ""blaufuss"",
    ""type"": ""defect""
}
```

</p>
</details>
",0,bayesian fits fail in   filter at pole  trac       all bayesian fits in the   filtered events fail at the pole    fit status  failedtoconverge  because the likelihood is not correctly defined for these fits  only the bayesian prior is used  it is not combined with the pandel likelihood  patch is attached        migrated from          json        status    closed        changetime                      ts             description    all bayesian fits in the   filtered events fail at the pole    fit status  failedtoconverge  because the likelihood is not correctly defined for these fits  only the bayesian prior is used  it is not combined with the pandel likelihood  npatch is attached         reporter    rfranke        cc    anna franckowiak googlemail com  andreas homeier googlemail com        resolution    fixed        time                     component    jeb   pnf        summary    bayesian fits fail in   filter at pole        priority    normal        keywords            milestone            owner    blaufuss        type    defect             ,0
124900,26556338240.0,IssuesEvent,2023-01-20 12:21:50,UnitTestBot/UTBotJava,https://api.github.com/repos/UnitTestBot/UTBotJava,closed,Incorrect type for variable caused by name clashes leads to compilation errors,ctg-bug comp-codegen,"**Description**

Consider a case when we have a custom class named like something standard. It cause compilation errors if we try to create a variable of this type.

**To Reproduce**

Consider the following class

```java
class FileNotFoundException {
    public FileReader getFileReader(String fileName) throws java.io.FileNotFoundException {
        File file = new File(fileName);
        return new FileReader(file);
    }
}
```

The generated test looks like as follows:

```java
@Test
@DisplayName(""getFileReader: file = new File(fileName) -> ThrowNullPointerException"")
public void testGetFileReader_ThrowNullPointerException() throws FileNotFoundException {
    FileNotFoundException fileNotFoundException = new FileNotFoundException();
    
    /* This test fails because method [java_lang.exception.io.FileNotFoundException.getFileReader] produces [java.lang.NullPointerException]
        java.base/java.io.File.<init>(File.java:278)
        java_lang.exception.io.FileNotFoundException.getFileReader(FileNotFoundException.java:8) */
    fileNotFoundException.getFileReader(null);
}
```

This code fails to compile because variable `fileNotFoundException` is rendered with an incorrect type.
",1.0,"Incorrect type for variable caused by name clashes leads to compilation errors - **Description**

Consider a case when we have a custom class named like something standard. It cause compilation errors if we try to create a variable of this type.

**To Reproduce**

Consider the following class

```java
class FileNotFoundException {
    public FileReader getFileReader(String fileName) throws java.io.FileNotFoundException {
        File file = new File(fileName);
        return new FileReader(file);
    }
}
```

The generated test looks like as follows:

```java
@Test
@DisplayName(""getFileReader: file = new File(fileName) -> ThrowNullPointerException"")
public void testGetFileReader_ThrowNullPointerException() throws FileNotFoundException {
    FileNotFoundException fileNotFoundException = new FileNotFoundException();
    
    /* This test fails because method [java_lang.exception.io.FileNotFoundException.getFileReader] produces [java.lang.NullPointerException]
        java.base/java.io.File.<init>(File.java:278)
        java_lang.exception.io.FileNotFoundException.getFileReader(FileNotFoundException.java:8) */
    fileNotFoundException.getFileReader(null);
}
```

This code fails to compile because variable `fileNotFoundException` is rendered with an incorrect type.
",0,incorrect type for variable caused by name clashes leads to compilation errors     description      consider a case when we have a custom class named like something standard  it cause compilation errors if we try to create a variable of this type       to reproduce      consider the following class       java  class filenotfoundexception        public filereader getfilereader string filename  throws java io filenotfoundexception            file file   new file filename            return new filereader file                     the generated test looks like as follows        java   test   displayname  getfilereader  file   new file filename     thrownullpointerexception    public void testgetfilereader thrownullpointerexception   throws filenotfoundexception        filenotfoundexception filenotfoundexception   new filenotfoundexception                  this test fails because method   produces            java base java io file   file java             java lang exception io filenotfoundexception getfilereader filenotfoundexception java            filenotfoundexception getfilereader null              this code fails to compile because variable  filenotfoundexception  is rendered with an incorrect type   ,0
165222,6265662295.0,IssuesEvent,2017-07-16 19:19:38,WaterCodeMelons/FlappyBirdUnity,https://api.github.com/repos/WaterCodeMelons/FlappyBirdUnity,opened,Ground needs to be obstacle,HighPriority Support,"# Hello
Ground has to be obstacle for bird and also it has to be an limiter for bottom",1.0,"Ground needs to be obstacle - # Hello
Ground has to be obstacle for bird and also it has to be an limiter for bottom",0,ground needs to be obstacle     hello  ground has to be obstacle for bird and also it has to be an limiter for bottom,0
39235,5052615684.0,IssuesEvent,2016-12-21 03:12:53,darkwoodsgames/CanaryWars,https://api.github.com/repos/darkwoodsgames/CanaryWars,opened,Criar design das cartas,design,"Criar as imagens que servirão de base para as cartas. 
São três tipos:
- Ataque
- Magia
- Equipamento
E o fundo da carta também.",1.0,"Criar design das cartas - Criar as imagens que servirão de base para as cartas. 
São três tipos:
- Ataque
- Magia
- Equipamento
E o fundo da carta também.",0,criar design das cartas   criar as imagens que servirão de base para as cartas    são três tipos     ataque    magia    equipamento  e o fundo da carta também ,0
53776,7855804557.0,IssuesEvent,2018-06-21 04:11:22,golang/go,https://api.github.com/repos/golang/go,reopened,time: document Location's effect on Time more?,Documentation,"Using Go 1.9

Documenation states:
```
func (t Time) In(loc *Location) Time
In returns t with the location information set to loc.
```

My interpretation is that the function `In` will change the location information but keep all other details the same. The consequence is that it will have a different Unix time usually since they represent different points in time.


```
startDate := ....   //startDate (time.Time) 2018-01-01 00:00:00 +1100 AEDT
_startDate := time.Date(startDate.Year(), startDate.Month(), startDate.Day(), startDate.Hour(), startDate.Minute(), startDate.Second(), startDate.Nanosecond(), time.UTC)
fmt.Println(""startDate"", spew.Sdump(startDate), spew.Sdump(startDate.In(time.UTC)), spew.Sdump(_startDate))
```

Output:

```
startDate (time.Time) 2018-01-01 00:00:00 +1100 AEDT
 (time.Time) 2017-12-31 13:00:00 +0000 UTC
 (time.Time) 2018-01-01 00:00:00 +0000 UTC
```

Expected output:
`startDate.In(time.UTC))` and `_startDate`  should produce same result
  ",1.0,"time: document Location's effect on Time more? - Using Go 1.9

Documenation states:
```
func (t Time) In(loc *Location) Time
In returns t with the location information set to loc.
```

My interpretation is that the function `In` will change the location information but keep all other details the same. The consequence is that it will have a different Unix time usually since they represent different points in time.


```
startDate := ....   //startDate (time.Time) 2018-01-01 00:00:00 +1100 AEDT
_startDate := time.Date(startDate.Year(), startDate.Month(), startDate.Day(), startDate.Hour(), startDate.Minute(), startDate.Second(), startDate.Nanosecond(), time.UTC)
fmt.Println(""startDate"", spew.Sdump(startDate), spew.Sdump(startDate.In(time.UTC)), spew.Sdump(_startDate))
```

Output:

```
startDate (time.Time) 2018-01-01 00:00:00 +1100 AEDT
 (time.Time) 2017-12-31 13:00:00 +0000 UTC
 (time.Time) 2018-01-01 00:00:00 +0000 UTC
```

Expected output:
`startDate.In(time.UTC))` and `_startDate`  should produce same result
  ",1,time  document location s effect on time more    using go        documenation states        func  t time  in loc  location  time  in returns t with the location information set to loc          my interpretation is that the function  in  will change the location information but keep all other details the same  the consequence is that it will have a different unix time usually since they represent different points in time            startdate             startdate  time time                 aedt   startdate    time date startdate year    startdate month    startdate day    startdate hour    startdate minute    startdate second    startdate nanosecond    time utc   fmt println  startdate   spew sdump startdate   spew sdump startdate in time utc    spew sdump  startdate           output          startdate  time time                 aedt    time time                 utc    time time                 utc         expected output    startdate in time utc    and   startdate   should produce same result    ,1
47630,7334666905.0,IssuesEvent,2018-03-05 23:48:40,golang/go,https://api.github.com/repos/golang/go,closed,os/exec: document that you must call Wait before accessing copied output,Documentation NeedsFix help wanted,"### What version of Go are you using (`go version`)?
    go version go1.10 linux/amd64

### Does this issue reproduce with the latest release?
The bug does not appear in 1.9.4, therefore it seems to be a regression in 1.10.

### What operating system and processor architecture are you using (`go env`)?
<pre>
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/howard/.cache/go-build""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/howard/gopath""
GORACE=""""
GOROOT=""/home/howard/go""
GOTMPDIR=""""
GOTOOLDIR=""/home/howard/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build479455967=/tmp/go-build -gno-record-gcc-switches""
</pre>

### What did you do?

Run the following piece of code:
<pre>
package main

import (
	""os/exec""
	""bytes""
	""time""
	""fmt""
)

func main() {
	c := exec.Command(""/bin/bash"", ""-c"", ""echo abc && sleep 10"")
	var outBuf bytes.Buffer
	c.Stdout = &outBuf

	if err := c.Start(); err != nil {
		panic(err)
	}

	time.Sleep(3 * time.Second)
	if err := c.Process.Kill(); err != nil {
		panic(err)
	}

	fmt.Println(outBuf.Bytes())
}
</pre>

Using previous go 1.9.4, the output correctly shows individual bytes in string `abc\n`:

    [97 98 99 10] 

However, using go 1.10, the output shows:

    [97 98 99 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]

Oddly, if the bash command does not say `&& sleep 10`, which means the bash program exits normally before it is killed, both 1.10 and 1.9.4 will collect the correct output `[97 98 99 10]`.

This is potentially a regression in 1.10.
",1.0,"os/exec: document that you must call Wait before accessing copied output - ### What version of Go are you using (`go version`)?
    go version go1.10 linux/amd64

### Does this issue reproduce with the latest release?
The bug does not appear in 1.9.4, therefore it seems to be a regression in 1.10.

### What operating system and processor architecture are you using (`go env`)?
<pre>
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/howard/.cache/go-build""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/howard/gopath""
GORACE=""""
GOROOT=""/home/howard/go""
GOTMPDIR=""""
GOTOOLDIR=""/home/howard/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build479455967=/tmp/go-build -gno-record-gcc-switches""
</pre>

### What did you do?

Run the following piece of code:
<pre>
package main

import (
	""os/exec""
	""bytes""
	""time""
	""fmt""
)

func main() {
	c := exec.Command(""/bin/bash"", ""-c"", ""echo abc && sleep 10"")
	var outBuf bytes.Buffer
	c.Stdout = &outBuf

	if err := c.Start(); err != nil {
		panic(err)
	}

	time.Sleep(3 * time.Second)
	if err := c.Process.Kill(); err != nil {
		panic(err)
	}

	fmt.Println(outBuf.Bytes())
}
</pre>

Using previous go 1.9.4, the output correctly shows individual bytes in string `abc\n`:

    [97 98 99 10] 

However, using go 1.10, the output shows:

    [97 98 99 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]

Oddly, if the bash command does not say `&& sleep 10`, which means the bash program exits normally before it is killed, both 1.10 and 1.9.4 will collect the correct output `[97 98 99 10]`.

This is potentially a regression in 1.10.
",1,os exec  document that you must call wait before accessing copied output       what version of go are you using   go version         go version     linux          does this issue reproduce with the latest release   the bug does not appear in        therefore it seems to be a regression in             what operating system and processor architecture are you using   go env        goarch      gobin     gocache   home howard  cache go build   goexe     gohostarch      gohostos  linux   goos  linux   gopath   home howard gopath   gorace     goroot   home howard go   gotmpdir     gotooldir   home howard go pkg tool linux     gccgo  gccgo   cc  gcc   cxx  g     cgo enabled      cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches            what did you do     run the following piece of code      package main    import    	 os exec   	 bytes   	 time   	 fmt        func main      	c    exec command   bin bash     c    echo abc    sleep      	var outbuf bytes buffer  	c stdout    outbuf    	if err    c start    err    nil    		panic err   	     	time sleep     time second   	if err    c process kill    err    nil    		panic err   	     	fmt println outbuf bytes             using previous go        the output correctly shows individual bytes in string  abc n                however  using go      the output shows              oddly  if the bash command does not say     sleep     which means the bash program exits normally before it is killed  both     and       will collect the correct output         this is potentially a regression in       ,1
55774,8029919049.0,IssuesEvent,2018-07-27 17:43:34,golang/go,https://api.github.com/repos/golang/go,closed,syscall: improve NewCallback documentation and panic message,Documentation OS-Windows help wanted,"### What version of Go are you using (`go version`)?
Tip (commit 65d55a13a92a3)

### Does this issue reproduce with the latest release?
Yes.

`syscall.NewCallback` (and `syscall.NewCallbackCDecl`) don't describe what's expected of the type of their argument beyond ""it must be a function"". But they do have requirements. For example, if you pass a function with no argument and no results, they panic with ""compileCallback: function must have one output parameter"". I don't actually know what this means a priori, and the `NewCallback` documentation doesn't tell me. The term ""output parameter"" doesn't appear in the Go spec, and it could (and does in this case) mean a result value, or it could mean a C-style output parameter which is actually an input argument that points to where to put the result.

We should document `NewCallback*`'s requirements and clarify the panic message for when they're violated.

/cc @alexbrainman ",1.0,"syscall: improve NewCallback documentation and panic message - ### What version of Go are you using (`go version`)?
Tip (commit 65d55a13a92a3)

### Does this issue reproduce with the latest release?
Yes.

`syscall.NewCallback` (and `syscall.NewCallbackCDecl`) don't describe what's expected of the type of their argument beyond ""it must be a function"". But they do have requirements. For example, if you pass a function with no argument and no results, they panic with ""compileCallback: function must have one output parameter"". I don't actually know what this means a priori, and the `NewCallback` documentation doesn't tell me. The term ""output parameter"" doesn't appear in the Go spec, and it could (and does in this case) mean a result value, or it could mean a C-style output parameter which is actually an input argument that points to where to put the result.

We should document `NewCallback*`'s requirements and clarify the panic message for when they're violated.

/cc @alexbrainman ",1,syscall  improve newcallback documentation and panic message       what version of go are you using   go version     tip  commit           does this issue reproduce with the latest release   yes      syscall newcallback   and  syscall newcallbackcdecl   don t describe what s expected of the type of their argument beyond  it must be a function   but they do have requirements  for example  if you pass a function with no argument and no results  they panic with  compilecallback  function must have one output parameter   i don t actually know what this means a priori  and the  newcallback  documentation doesn t tell me  the term  output parameter  doesn t appear in the go spec  and it could  and does in this case  mean a result value  or it could mean a c style output parameter which is actually an input argument that points to where to put the result     we should document  newcallback   s requirements and clarify the panic message for when they re violated      cc  alexbrainman ,1
174087,14446294178.0,IssuesEvent,2020-12-08 00:55:14,golang/go,https://api.github.com/repos/golang/go,closed,"You can only export basic function signatures. @ianlancetaylor, are the rules documented somewhere?",Documentation,"You can only export basic function signatures. @ianlancetaylor, are the rules documented somewhere?

_Originally posted by @bradfitz in https://github.com/golang/go/issues/18412#issuecomment-268796091_

FUCK THAT SHIT, GOOGLE CODERS ARE MONKEYS",1.0,"You can only export basic function signatures. @ianlancetaylor, are the rules documented somewhere? - You can only export basic function signatures. @ianlancetaylor, are the rules documented somewhere?

_Originally posted by @bradfitz in https://github.com/golang/go/issues/18412#issuecomment-268796091_

FUCK THAT SHIT, GOOGLE CODERS ARE MONKEYS",1,you can only export basic function signatures   ianlancetaylor  are the rules documented somewhere    you can only export basic function signatures   ianlancetaylor  are the rules documented somewhere      originally posted by  bradfitz in      fuck that shit  google coders are monkeys,1
183802,14256655067.0,IssuesEvent,2020-11-20 01:33:00,MarlinFirmware/Marlin,https://api.github.com/repos/MarlinFirmware/Marlin,closed,HOTEND_IDLE_TIMEOUT shuts down hot end in while printing,Bug: Potential ? C: Temperatures Needs: Testing stale-closing-soon,"[Marlin 2.6.1]

Hi,
I just enabled HOTEND_IDLE_TIMEOUT with the following default settings

```cpp
#define HOTEND_IDLE_TIMEOUT 
#if ENABLED(HOTEND_IDLE_TIMEOUT)
  #define HOTEND_IDLE_TIMEOUT_SEC (5*60)
  #define HOTEND_IDLE_MIN_TRIGGER   170
  #define HOTEND_IDLE_NOZZLE_TARGET   0
  #define HOTEND_IDLE_BED_TARGET      0
#endif
```
(printing PLA at 215C)
The time it takes for the nozzle and bed to heat up plus for ABL to complete is about 3 minutes, so 2 minutes into the print the nozzle shuts down and cools, thus failing the first layers.
Disabling the feature allows me to print normally again.

(Sidewinder X1 with stock TFT + SKR 1.4 turbo + TMC2209)",1.0,"HOTEND_IDLE_TIMEOUT shuts down hot end in while printing - [Marlin 2.6.1]

Hi,
I just enabled HOTEND_IDLE_TIMEOUT with the following default settings

```cpp
#define HOTEND_IDLE_TIMEOUT 
#if ENABLED(HOTEND_IDLE_TIMEOUT)
  #define HOTEND_IDLE_TIMEOUT_SEC (5*60)
  #define HOTEND_IDLE_MIN_TRIGGER   170
  #define HOTEND_IDLE_NOZZLE_TARGET   0
  #define HOTEND_IDLE_BED_TARGET      0
#endif
```
(printing PLA at 215C)
The time it takes for the nozzle and bed to heat up plus for ABL to complete is about 3 minutes, so 2 minutes into the print the nozzle shuts down and cools, thus failing the first layers.
Disabling the feature allows me to print normally again.

(Sidewinder X1 with stock TFT + SKR 1.4 turbo + TMC2209)",0,hotend idle timeout shuts down hot end in while printing        hi   i just enabled hotend idle timeout with the following default settings       cpp   define hotend idle timeout    if enabled hotend idle timeout      define hotend idle timeout sec           define hotend idle min trigger         define hotend idle nozzle target         define hotend idle bed target          endif        printing pla at     the time it takes for the nozzle and bed to heat up plus for abl to complete is about   minutes  so   minutes into the print the nozzle shuts down and cools  thus failing the first layers   disabling the feature allows me to print normally again      sidewinder   with stock tft   skr     turbo     ,0
178959,21509595086.0,IssuesEvent,2022-04-28 01:58:22,raindigi/snippet-generator,https://api.github.com/repos/raindigi/snippet-generator,closed,CVE-2021-23424 (High) detected in ansi-html-0.0.7.tgz - autoclosed,security vulnerability,"## CVE-2021-23424 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ansi-html-0.0.7.tgz</b></p></summary>

<p>An elegant lib that converts the chalked (ANSI) text to HTML.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/ansi-html/-/ansi-html-0.0.7.tgz"">https://registry.npmjs.org/ansi-html/-/ansi-html-0.0.7.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/ansi-html/package.json</p>
<p>

Dependency Hierarchy:
  - webpack-dev-server-3.1.4.tgz (Root Library)
    - :x: **ansi-html-0.0.7.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://api.github.com/repos/raindigi/snippet-generator/git/commits/454f93af75ebeae520f02650a808a4b8ea4e691b"">454f93af75ebeae520f02650a808a4b8ea4e691b</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
This affects all versions of package ansi-html. If an attacker provides a malicious string, it will get stuck processing the input for an extremely long time.

<p>Publish Date: 2021-08-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23424>CVE-2021-23424</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2021-23424 (High) detected in ansi-html-0.0.7.tgz - autoclosed - ## CVE-2021-23424 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ansi-html-0.0.7.tgz</b></p></summary>

<p>An elegant lib that converts the chalked (ANSI) text to HTML.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/ansi-html/-/ansi-html-0.0.7.tgz"">https://registry.npmjs.org/ansi-html/-/ansi-html-0.0.7.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/ansi-html/package.json</p>
<p>

Dependency Hierarchy:
  - webpack-dev-server-3.1.4.tgz (Root Library)
    - :x: **ansi-html-0.0.7.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://api.github.com/repos/raindigi/snippet-generator/git/commits/454f93af75ebeae520f02650a808a4b8ea4e691b"">454f93af75ebeae520f02650a808a4b8ea4e691b</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
This affects all versions of package ansi-html. If an attacker provides a malicious string, it will get stuck processing the input for an extremely long time.

<p>Publish Date: 2021-08-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23424>CVE-2021-23424</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in ansi html       tgz   autoclosed      cve       high severity vulnerability     vulnerable library    ansi html       tgz      an elegant lib that converts the chalked  ansi  text to html    library home page   a href     path to dependency file   package json   path to vulnerable library   node modules ansi html package json     dependency hierarchy      webpack dev server       tgz  root library         x    ansi html       tgz    vulnerable library   found in head commit   a href               vulnerability details         this affects all versions of package ansi html  if an attacker provides a malicious string  it will get stuck processing the input for an extremely long time    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  high   for more information on   scores  click  a href                step up your open source security game with whitesource    ,0
15761,3974440852.0,IssuesEvent,2016-05-04 22:12:26,golang/go,https://api.github.com/repos/golang/go,closed,net/http: MethodPatch references the wrong RFC,Documentation,"Please answer these questions before submitting your issue. Thanks!

1. What version of Go are you using (`go version`)?

`go version go1.6.2 darwin/amd64`

2. What operating system and processor architecture are you using (`go env`)?

```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/dmaze/Diffeo/go""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.6.2/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.6.2/libexec/pkg/tool/darwin_amd64""
GO15VENDOREXPERIMENT=""1""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
```
3. What did you do?

Run `godoc net/http MethodPatch`; or visited https://godoc.org/net/http#MethodPatch or http://localhost:6060/pkg/net/http#MethodPatch.

4. What did you expect to see?

A reference to [RFC 5789, ""PATCH Method for HTTP""](https://tools.ietf.org/html/rfc5789).

5. What did you see instead?

A reference to [RFC 5741, ""RFC Streams, Headers, and Boilerplates""](https://tools.ietf.org/html/rfc5741), the meta-RFC that defines the format of RFCs.",1.0,"net/http: MethodPatch references the wrong RFC - Please answer these questions before submitting your issue. Thanks!

1. What version of Go are you using (`go version`)?

`go version go1.6.2 darwin/amd64`

2. What operating system and processor architecture are you using (`go env`)?

```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/dmaze/Diffeo/go""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.6.2/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.6.2/libexec/pkg/tool/darwin_amd64""
GO15VENDOREXPERIMENT=""1""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
```
3. What did you do?

Run `godoc net/http MethodPatch`; or visited https://godoc.org/net/http#MethodPatch or http://localhost:6060/pkg/net/http#MethodPatch.

4. What did you expect to see?

A reference to [RFC 5789, ""PATCH Method for HTTP""](https://tools.ietf.org/html/rfc5789).

5. What did you see instead?

A reference to [RFC 5741, ""RFC Streams, Headers, and Boilerplates""](https://tools.ietf.org/html/rfc5741), the meta-RFC that defines the format of RFCs.",1,net http  methodpatch references the wrong rfc   please answer these questions before submitting your issue  thanks        what version of go are you using   go version        go version       darwin          what operating system and processor architecture are you using   go env            goarch      gobin     goexe     gohostarch      gohostos  darwin   goos  darwin   gopath   users dmaze diffeo go   gorace     goroot   usr local cellar go       libexec   gotooldir   usr local cellar go       libexec pkg tool darwin            cc  clang   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fno common   cxx  clang     cgo enabled              what did you do     run  godoc net http methodpatch   or visited   or         what did you expect to see     a reference to           what did you see instead     a reference to     the meta rfc that defines the format of rfcs ,1
750884,26223143658.0,IssuesEvent,2023-01-04 16:20:17,azerothcore/azerothcore-wotlk,https://api.github.com/repos/azerothcore/azerothcore-wotlk,opened,The Brokering of Peace quest not triggering yell upon completion (Timbermaw rep),Confirmed Quest 40-49 60 Priority-Trivial,"Original Issue: https://github.com/chromiecraft/chromiecraft/issues/4499

### What client do you play on?

enUS

### Faction

Both

### Content Phase:

Generic

### Current Behaviour

King Magni did not yell when I turned in The Brokering of Peace (quest ID: 8484).
Thrall did not yell when I turned in The Brokering of Peace (quest ID: 8485).

### Expected Blizzlike Behaviour

Upon turning in The Brokering of Peace (quest ID: 8484), King Magni is supposed to yell: 

`King Magni Bronzebeard yells: Let it be known that <name> - Alliance <class> - has earned the undying respect of Ironforge and the Alliance as a whole. <He/She> has engaged in great diplomacy with Timbermaw Hold and performed valiant actions for them on our behalf. <He/She> has gone above and beyond the call of duty. Three cheers for <name> - a true hero of the Alliance!`

I'm unsure if this is a server wide announcement, Alliance only, or proximity based yell, but it is supposed to trigger in some fashion.  The Horde equivalent is The Brokering of Peace (quest ID: 8485).  I'm also unsure if this one properly triggers or not, but the completion text should be.

`Thrall yells: Let it be known that <name> - Horde <class> - has earned the undying respect of the Warchief. He has engaged in great diplomacy with Timbermaw Hold and performed valiant actions for them on our behalf. He has gone above and beyond the call of duty. Three cheers for <name> - a true hero of the Horde!`

### Source

https://wowpedia.fandom.com/wiki/The_Brokering_of_Peace_(Alliance)#Notes
https://wowpedia.fandom.com/wiki/The_Brokering_of_Peace_(Horde)#Notes

These discuss the text of the yell.

https://www.wowhead.com/wotlk/quest=8484/the-brokering-of-peace#comments
https://www.wowhead.com/wotlk/quest=8485/the-brokering-of-peace#comments

These include comments mentioning the yell (present during TBC) along with a screenshot (for the Horde side).

https://i47.photobucket.com/albums/f180/orcbeauty/WoWScrnShot_120606_012021.jpg

### Steps to reproduce the problem

`.modify reputation 576 50000` (Timbermaw Hold)
`.quest add 8481`
`.quest complete 8481`
`.quest add 8484` / `.quest add 8485`
`.go c 2088` / `.go c 4770`

### Extra Notes

_No response_

### AC rev. hash/commit

3ad652d8ab96 2023-01-03


### Operating system

Ubuntu 20.04 - Windows 10 x64


### Modules

- [mod-ah-bot](https://github.com/azerothcore/mod-ah-bot)
- [mod-bg-item-reward](https://github.com/azerothcore/mod-bg-item-reward)
- [mod-cfbg](https://github.com/azerothcore/mod-cfbg)
- [mod-chat-transmitter](https://github.com/azerothcore/mod-chat-transmitter)
- [mod-chromie-xp](https://github.com/azerothcore/mod-chromie-xp)
- [mod-cta-switch](https://github.com/azerothcore/mod-cta-switch)
- [mod-desertion-warnings](https://github.com/azerothcore/mod-desertion-warnings)
- [mod-dmf-switch](https://github.com/azerothcore/mod-dmf-switch)
- [mod-duel-reset](https://github.com/azerothcore/mod-duel-reset)
- [mod-eluna](https://github.com/azerothcore/mod-eluna)
- [mod-ip-tracker](https://github.com/azerothcore/mod-ip-tracker)
- [mod-low-level-arena](https://github.com/azerothcore/mod-low-level-arena)
- [mod-low-level-rbg](https://github.com/azerothcore/mod-low-level-rbg)
- [mod-multi-client-check](https://github.com/azerothcore/mod-multi-client-check)
- [mod-progression-system](https://github.com/azerothcore/mod-progression-system)
- [mod-pvp-titles](https://github.com/azerothcore/mod-pvp-titles)
- [mod-pvpstats-announcer](https://github.com/azerothcore/mod-pvpstats-announcer)
- [mod-queue-list-cache](https://github.com/azerothcore/mod-queue-list-cache)
- [mod-rdf-expansion](https://github.com/azerothcore/mod-rdf-expansion)
- [mod-transmog](https://github.com/azerothcore/mod-transmog)
- [mod-weekend-xp](https://github.com/azerothcore/mod-weekend-xp)
- [mod-instanced-worldbosses](https://github.com/nyeriah/mod-instanced-worldbosses)
- [lua-carbon-copy](https://github.com/55Honey/Acore_CarbonCopy)
- [lua-exchange-npc](https://github.com/55Honey/Acore_ExchangeNpc)
- [lua-custom-worldboss](https://github.com/55Honey/Acore_CustomWorldboss)
- [lua-level-up-reward](https://github.com/55Honey/Acore_LevelUpReward)
- [lua-recruit-a-friend](https://github.com/55Honey/Acore_RecruitAFriend)
- [lua-send-and-bind](https://github.com/55Honey/Acore_SendAndBind)
- [lua-temp-announcements](https://github.com/55Honey/Acore_TempAnnouncements)
- [lua-zonecheck](https://github.com/55Honey/acore_Zonecheck)
- [lua-zone-debuff](https://github.com/55Honey/Acore_ZoneDebuff)


### Customizations

None


### Server

ChromieCraft
",1.0,"The Brokering of Peace quest not triggering yell upon completion (Timbermaw rep) - Original Issue: https://github.com/chromiecraft/chromiecraft/issues/4499

### What client do you play on?

enUS

### Faction

Both

### Content Phase:

Generic

### Current Behaviour

King Magni did not yell when I turned in The Brokering of Peace (quest ID: 8484).
Thrall did not yell when I turned in The Brokering of Peace (quest ID: 8485).

### Expected Blizzlike Behaviour

Upon turning in The Brokering of Peace (quest ID: 8484), King Magni is supposed to yell: 

`King Magni Bronzebeard yells: Let it be known that <name> - Alliance <class> - has earned the undying respect of Ironforge and the Alliance as a whole. <He/She> has engaged in great diplomacy with Timbermaw Hold and performed valiant actions for them on our behalf. <He/She> has gone above and beyond the call of duty. Three cheers for <name> - a true hero of the Alliance!`

I'm unsure if this is a server wide announcement, Alliance only, or proximity based yell, but it is supposed to trigger in some fashion.  The Horde equivalent is The Brokering of Peace (quest ID: 8485).  I'm also unsure if this one properly triggers or not, but the completion text should be.

`Thrall yells: Let it be known that <name> - Horde <class> - has earned the undying respect of the Warchief. He has engaged in great diplomacy with Timbermaw Hold and performed valiant actions for them on our behalf. He has gone above and beyond the call of duty. Three cheers for <name> - a true hero of the Horde!`

### Source

https://wowpedia.fandom.com/wiki/The_Brokering_of_Peace_(Alliance)#Notes
https://wowpedia.fandom.com/wiki/The_Brokering_of_Peace_(Horde)#Notes

These discuss the text of the yell.

https://www.wowhead.com/wotlk/quest=8484/the-brokering-of-peace#comments
https://www.wowhead.com/wotlk/quest=8485/the-brokering-of-peace#comments

These include comments mentioning the yell (present during TBC) along with a screenshot (for the Horde side).

https://i47.photobucket.com/albums/f180/orcbeauty/WoWScrnShot_120606_012021.jpg

### Steps to reproduce the problem

`.modify reputation 576 50000` (Timbermaw Hold)
`.quest add 8481`
`.quest complete 8481`
`.quest add 8484` / `.quest add 8485`
`.go c 2088` / `.go c 4770`

### Extra Notes

_No response_

### AC rev. hash/commit

3ad652d8ab96 2023-01-03


### Operating system

Ubuntu 20.04 - Windows 10 x64


### Modules

- [mod-ah-bot](https://github.com/azerothcore/mod-ah-bot)
- [mod-bg-item-reward](https://github.com/azerothcore/mod-bg-item-reward)
- [mod-cfbg](https://github.com/azerothcore/mod-cfbg)
- [mod-chat-transmitter](https://github.com/azerothcore/mod-chat-transmitter)
- [mod-chromie-xp](https://github.com/azerothcore/mod-chromie-xp)
- [mod-cta-switch](https://github.com/azerothcore/mod-cta-switch)
- [mod-desertion-warnings](https://github.com/azerothcore/mod-desertion-warnings)
- [mod-dmf-switch](https://github.com/azerothcore/mod-dmf-switch)
- [mod-duel-reset](https://github.com/azerothcore/mod-duel-reset)
- [mod-eluna](https://github.com/azerothcore/mod-eluna)
- [mod-ip-tracker](https://github.com/azerothcore/mod-ip-tracker)
- [mod-low-level-arena](https://github.com/azerothcore/mod-low-level-arena)
- [mod-low-level-rbg](https://github.com/azerothcore/mod-low-level-rbg)
- [mod-multi-client-check](https://github.com/azerothcore/mod-multi-client-check)
- [mod-progression-system](https://github.com/azerothcore/mod-progression-system)
- [mod-pvp-titles](https://github.com/azerothcore/mod-pvp-titles)
- [mod-pvpstats-announcer](https://github.com/azerothcore/mod-pvpstats-announcer)
- [mod-queue-list-cache](https://github.com/azerothcore/mod-queue-list-cache)
- [mod-rdf-expansion](https://github.com/azerothcore/mod-rdf-expansion)
- [mod-transmog](https://github.com/azerothcore/mod-transmog)
- [mod-weekend-xp](https://github.com/azerothcore/mod-weekend-xp)
- [mod-instanced-worldbosses](https://github.com/nyeriah/mod-instanced-worldbosses)
- [lua-carbon-copy](https://github.com/55Honey/Acore_CarbonCopy)
- [lua-exchange-npc](https://github.com/55Honey/Acore_ExchangeNpc)
- [lua-custom-worldboss](https://github.com/55Honey/Acore_CustomWorldboss)
- [lua-level-up-reward](https://github.com/55Honey/Acore_LevelUpReward)
- [lua-recruit-a-friend](https://github.com/55Honey/Acore_RecruitAFriend)
- [lua-send-and-bind](https://github.com/55Honey/Acore_SendAndBind)
- [lua-temp-announcements](https://github.com/55Honey/Acore_TempAnnouncements)
- [lua-zonecheck](https://github.com/55Honey/acore_Zonecheck)
- [lua-zone-debuff](https://github.com/55Honey/Acore_ZoneDebuff)


### Customizations

None


### Server

ChromieCraft
",0,the brokering of peace quest not triggering yell upon completion  timbermaw rep    original issue           what client do you play on     enus        faction    both        content phase     generic        current behaviour    king magni did not yell when i turned in the brokering of peace  quest id       thrall did not yell when i turned in the brokering of peace  quest id             expected blizzlike behaviour    upon turning in the brokering of peace  quest id      king magni is supposed to yell       king magni bronzebeard yells  let it be known that     alliance     has earned the undying respect of ironforge and the alliance as a whole    has engaged in great diplomacy with timbermaw hold and performed valiant actions for them on our behalf    has gone above and beyond the call of duty  three cheers for     a true hero of the alliance      i m unsure if this is a server wide announcement  alliance only  or proximity based yell  but it is supposed to trigger in some fashion   the horde equivalent is the brokering of peace  quest id       i m also unsure if this one properly triggers or not  but the completion text should be      thrall yells  let it be known that     horde     has earned the undying respect of the warchief  he has engaged in great diplomacy with timbermaw hold and performed valiant actions for them on our behalf  he has gone above and beyond the call of duty  three cheers for     a true hero of the horde          source            these discuss the text of the yell             these include comments mentioning the yell  present during tbc  along with a screenshot  for the horde side               steps to reproduce the problem      modify reputation       timbermaw hold     quest add       quest complete       quest add        quest add       go c        go c           extra notes     no response         ac rev  hash commit                     operating system    ubuntu       windows              modules                                                                                                                                                                                                                                     customizations    none          server    chromiecraft  ,0
7827,7110752587.0,IssuesEvent,2018-01-17 11:48:40,neopostmodern/structure,https://api.github.com/repos/neopostmodern/structure,closed,Check compatibility of API versions,infrastructure,Should force users to update otherwise since compatibility checks require too much engineering,1.0,Check compatibility of API versions - Should force users to update otherwise since compatibility checks require too much engineering,0,check compatibility of api versions   should force users to update otherwise since compatibility checks require too much engineering,0
35160,12321104685.0,IssuesEvent,2020-05-13 08:10:35,tamirverthim/Training,https://api.github.com/repos/tamirverthim/Training,opened,CVE-2011-4969 (Medium) detected in GH_Training Unmatched Source Files,security vulnerability,"## CVE-2011-4969 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>null</b></p></summary>
<p>

<p>Unmatched Source Files</p>
<p>Found in HEAD commit: <a href=""https://api.github.com/repos/tamirverthim/Training/commits/6d859668c8bf281326b8155dd5220078d0c23a0b"">6d859668c8bf281326b8155dd5220078d0c23a0b</a></p>
</p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Library Source Files (14)</summary>
<p></p>
<p> * The source files were matched to this source library based on a best effort match. Source libraries are selected from a list of probable public libraries.</p>
<p>

  - /Training/Backboneapp/Scripts/backbone.js
  - /Training/Functions/Scripts/init-time-branching.js
  - /Training/Patterns/Scripts/Factory.js
  - /Training/Functions/Scripts/definitions.js
  - /Training/jsInheritance/Scripts/Sample.js
  - /Training/jsInheritance/Scripts/Inheritance.js
  - /Training/JsObserver/Scripts/sample.js
  - /Training/Patterns/Scripts/Mediator.js
  - /Training/Backboneapp/Scripts/jquery-1.6.2.min.js
  - /Training/Backboneapp/Scripts/Jquery.tmpl.min.js
  - /Training/MixIn/Scripts/Sample.js
  - /Training/Backboneapp/Scripts/Backboneapp.js
  - /Training/MixIn/Scripts/Mixin.js
  - /Training/Patterns/Scripts/Decorator.js
</p>
</details>
<p></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>  
  
Cross-site scripting (XSS) vulnerability in jQuery before 1.6.3, when using location.hash to select elements, allows remote attackers to inject arbitrary web script or HTML via a crafted tag.

<p>Publish Date: 2013-03-08
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2011-4969>CVE-2011-4969</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>4.3</b>)</summary>
<p>

Base Score Metrics not available</p>

</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2011-4969"">https://nvd.nist.gov/vuln/detail/CVE-2011-4969</a></p>
<p>Release Date: 2013-03-08</p>
<p>Fix Resolution: 1.6.3</p>

</p>
</details>
<p></p>
",True,"CVE-2011-4969 (Medium) detected in GH_Training Unmatched Source Files - ## CVE-2011-4969 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>null</b></p></summary>
<p>

<p>Unmatched Source Files</p>
<p>Found in HEAD commit: <a href=""https://api.github.com/repos/tamirverthim/Training/commits/6d859668c8bf281326b8155dd5220078d0c23a0b"">6d859668c8bf281326b8155dd5220078d0c23a0b</a></p>
</p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Library Source Files (14)</summary>
<p></p>
<p> * The source files were matched to this source library based on a best effort match. Source libraries are selected from a list of probable public libraries.</p>
<p>

  - /Training/Backboneapp/Scripts/backbone.js
  - /Training/Functions/Scripts/init-time-branching.js
  - /Training/Patterns/Scripts/Factory.js
  - /Training/Functions/Scripts/definitions.js
  - /Training/jsInheritance/Scripts/Sample.js
  - /Training/jsInheritance/Scripts/Inheritance.js
  - /Training/JsObserver/Scripts/sample.js
  - /Training/Patterns/Scripts/Mediator.js
  - /Training/Backboneapp/Scripts/jquery-1.6.2.min.js
  - /Training/Backboneapp/Scripts/Jquery.tmpl.min.js
  - /Training/MixIn/Scripts/Sample.js
  - /Training/Backboneapp/Scripts/Backboneapp.js
  - /Training/MixIn/Scripts/Mixin.js
  - /Training/Patterns/Scripts/Decorator.js
</p>
</details>
<p></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>  
  
Cross-site scripting (XSS) vulnerability in jQuery before 1.6.3, when using location.hash to select elements, allows remote attackers to inject arbitrary web script or HTML via a crafted tag.

<p>Publish Date: 2013-03-08
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2011-4969>CVE-2011-4969</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>4.3</b>)</summary>
<p>

Base Score Metrics not available</p>

</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2011-4969"">https://nvd.nist.gov/vuln/detail/CVE-2011-4969</a></p>
<p>Release Date: 2013-03-08</p>
<p>Fix Resolution: 1.6.3</p>

</p>
</details>
<p></p>
",0,cve      medium  detected in gh training unmatched source files      cve       medium severity vulnerability     vulnerable library    null        unmatched source files   found in head commit   a href               library source files             the source files were matched to this source library based on a best effort match  source libraries are selected from a list of probable public libraries           training backboneapp scripts backbone js      training functions scripts init time branching js      training patterns scripts factory js      training functions scripts definitions js      training jsinheritance scripts sample js      training jsinheritance scripts inheritance js      training jsobserver scripts sample js      training patterns scripts mediator js      training backboneapp scripts jquery       min js      training backboneapp scripts jquery tmpl min js      training mixin scripts sample js      training backboneapp scripts backboneapp js      training mixin scripts mixin js      training patterns scripts decorator js                   vulnerability details         cross site scripting  xss  vulnerability in jquery before        when using location hash to select elements  allows remote attackers to inject arbitrary web script or html via a crafted tag    publish date         url   a href              cvss   score details             base score metrics not available              suggested fix      type  upgrade version   origin   a href     release date          fix resolution                 ,0
63862,8697874703.0,IssuesEvent,2018-12-04 21:34:19,golang/go,https://api.github.com/repos/golang/go,closed,"net/http: document Transport errors more, types of errors returned, how to check canceled, etc",Documentation NeedsFix,"At the moment the only wat to know if an `http.Request` was canceled is to check the error string. If `http.errRequestCanceled` is exported this becomes much easier.

I can submit a change to gerrit if needed?
",1.0,"net/http: document Transport errors more, types of errors returned, how to check canceled, etc - At the moment the only wat to know if an `http.Request` was canceled is to check the error string. If `http.errRequestCanceled` is exported this becomes much easier.

I can submit a change to gerrit if needed?
",1,net http  document transport errors more  types of errors returned  how to check canceled  etc   at the moment the only wat to know if an  http request  was canceled is to check the error string  if  http errrequestcanceled  is exported this becomes much easier   i can submit a change to gerrit if needed  ,1
345568,10369559428.0,IssuesEvent,2019-09-08 04:26:02,ballerina-platform/ballerina-lang,https://api.github.com/repos/ballerina-platform/ballerina-lang,closed,Add the missing implementations in lang lib functions,Area/Language Priority/Blocker Type/Task,"Some of the lang lib function implementations were left out for the alpha. For example, `removeAll()` in arrays. Need to provide implementations for these. ",1.0,"Add the missing implementations in lang lib functions - Some of the lang lib function implementations were left out for the alpha. For example, `removeAll()` in arrays. Need to provide implementations for these. ",0,add the missing implementations in lang lib functions   some of the lang lib function implementations were left out for the alpha  for example   removeall    in arrays  need to provide implementations for these  ,0
25110,5132878075.0,IssuesEvent,2017-01-11 00:47:10,golang/go,https://api.github.com/repos/golang/go,opened,testing: are T.Run and B.Run safe for concurrent use?,Documentation,"I do not see any documentation specifying if T.Run is safe for concurrent use. I see the following doc for [testing.T](https://tip.golang.org/pkg/testing/#T), which does not mention T.Run:

> A test ends when its Test function returns or calls any of the methods FailNow, Fatal, Fatalf, SkipNow, Skip, or Skipf. Those methods, as well as the Parallel method, must be called only from the goroutine running the Test function.
>
> The other reporting methods, such as the variations of Log and Error, may be called simultaneously from multiple goroutines.

There is a similar doc for [testing.B](https://tip.golang.org/pkg/testing/#B).

I ask because I believe T.Run was safe for concurrent use in go 1.7. Then, [this line](https://github.com/golang/go/blob/7fb16406139e934d84f7ec66ba440a772747270a/src/testing/testing.go#L663) was added in go 1.8, which made T.Run no longer safe for concurrent use. I don't particularly care whether T.Run is safe for concurrent use, but I think the semantics should be clarified.

Optimistically labeling this go1.8.",1.0,"testing: are T.Run and B.Run safe for concurrent use? - I do not see any documentation specifying if T.Run is safe for concurrent use. I see the following doc for [testing.T](https://tip.golang.org/pkg/testing/#T), which does not mention T.Run:

> A test ends when its Test function returns or calls any of the methods FailNow, Fatal, Fatalf, SkipNow, Skip, or Skipf. Those methods, as well as the Parallel method, must be called only from the goroutine running the Test function.
>
> The other reporting methods, such as the variations of Log and Error, may be called simultaneously from multiple goroutines.

There is a similar doc for [testing.B](https://tip.golang.org/pkg/testing/#B).

I ask because I believe T.Run was safe for concurrent use in go 1.7. Then, [this line](https://github.com/golang/go/blob/7fb16406139e934d84f7ec66ba440a772747270a/src/testing/testing.go#L663) was added in go 1.8, which made T.Run no longer safe for concurrent use. I don't particularly care whether T.Run is safe for concurrent use, but I think the semantics should be clarified.

Optimistically labeling this go1.8.",1,testing  are t run and b run safe for concurrent use    i do not see any documentation specifying if t run is safe for concurrent use  i see the following doc for     which does not mention t run       a test ends when its test function returns or calls any of the methods failnow  fatal  fatalf  skipnow  skip  or skipf  those methods  as well as the parallel method  must be called only from the goroutine running the test function        the other reporting methods  such as the variations of log and error  may be called simultaneously from multiple goroutines     there is a similar doc for        i ask because i believe t run was safe for concurrent use in go      then      was added in go      which made t run no longer safe for concurrent use  i don t particularly care whether t run is safe for concurrent use  but i think the semantics should be clarified     optimistically labeling this     ,1
308408,23247007861.0,IssuesEvent,2022-08-03 21:18:41,golang/go,https://api.github.com/repos/golang/go,closed,doc: doc/articles/wiki clarification,Documentation help wanted NeedsFix,"### What version of Go are you using (`go version`)?
go version go1.10.1 windows/amd64

### Does this issue reproduce with the latest release?
N/A

### What operating system and processor architecture are you using (`go env`)?
```sh
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\sfmjp.WFC\AppData\Local\go-build
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\Users\sfmjp.WFC\go
set GORACE=
set GOROOT=C:\Go
set GOTMPDIR=
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\sfmjp.WFC\AppData\Local\Temp\go-build919863594=/tmp/go-build -gno-record-gcc-switches
```
### What did you do?
Following the [wiki](https://golang.org/doc/articles/wiki/) docs, I ran into an issue when getting to the following section: Using net/http to serve wiki pages.

The code sample explicitly says to add ""net/http"" to the import statement. It doesn't state to add ""log"", though it's also necessary. So when following along, a user will get a compilation error saying that log doesn't exist. It isn't until the user navigates to the [""code so far""](https://golang.org/doc/articles/wiki/part2.go) link does it show the need to add the import statement for log.  

### What did you expect to see?
I would expect the documentation to reflect the need to import both net/http and log at this point. If you're experienced in Go, then it may be obvious that you need to add an import statement for log. As a newer Gopher, this caused a situation where it's not entirely obvious that it was necessary to add until I looked at the code so far link. ",1.0,"doc: doc/articles/wiki clarification - ### What version of Go are you using (`go version`)?
go version go1.10.1 windows/amd64

### Does this issue reproduce with the latest release?
N/A

### What operating system and processor architecture are you using (`go env`)?
```sh
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\sfmjp.WFC\AppData\Local\go-build
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\Users\sfmjp.WFC\go
set GORACE=
set GOROOT=C:\Go
set GOTMPDIR=
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\sfmjp.WFC\AppData\Local\Temp\go-build919863594=/tmp/go-build -gno-record-gcc-switches
```
### What did you do?
Following the [wiki](https://golang.org/doc/articles/wiki/) docs, I ran into an issue when getting to the following section: Using net/http to serve wiki pages.

The code sample explicitly says to add ""net/http"" to the import statement. It doesn't state to add ""log"", though it's also necessary. So when following along, a user will get a compilation error saying that log doesn't exist. It isn't until the user navigates to the [""code so far""](https://golang.org/doc/articles/wiki/part2.go) link does it show the need to add the import statement for log.  

### What did you expect to see?
I would expect the documentation to reflect the need to import both net/http and log at this point. If you're experienced in Go, then it may be obvious that you need to add an import statement for log. As a newer Gopher, this caused a situation where it's not entirely obvious that it was necessary to add until I looked at the code so far link. ",1,doc  doc articles wiki clarification       what version of go are you using   go version     go version       windows          does this issue reproduce with the latest release   n a        what operating system and processor architecture are you using   go env        sh  set goarch    set gobin   set gocache c  users sfmjp wfc appdata local go build  set goexe  exe  set gohostarch    set gohostos windows  set goos windows  set gopath c  users sfmjp wfc go  set gorace   set goroot c  go  set gotmpdir   set gotooldir c  go pkg tool windows    set gccgo gccgo  set cc gcc  set cxx g    set cgo enabled    set cgo cflags  g     set cgo cppflags   set cgo cxxflags  g     set cgo fflags  g     set cgo ldflags  g     set pkg config pkg config  set gogccflags     mthreads  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map c  users sfmjp wfc appdata local temp go    tmp go build  gno record gcc switches           what did you do   following the     docs  i ran into an issue when getting to the following section  using net http to serve wiki pages     the code sample explicitly says to add  net http  to the import statement  it doesn t state to add  log   though it s also necessary  so when following along  a user will get a compilation error saying that log doesn t exist  it isn t until the user navigates to the     link does it show the need to add the import statement for log           what did you expect to see   i would expect the documentation to reflect the need to import both net http and log at this point  if you re experienced in go  then it may be obvious that you need to add an import statement for log  as a newer gopher  this caused a situation where it s not entirely obvious that it was necessary to add until i looked at the code so far link  ,1
98997,11102513446.0,IssuesEvent,2019-12-17 00:19:11,golang/go,https://api.github.com/repos/golang/go,closed,time: Timer.Stop documentation not covering all the cases,Documentation WaitingForInfo,"Hello,
In the section where the Stop method of a timer object is described there is a snippet about ensuring to drain the channel in case this method returns False.
However, it does not mention explicitly that this code snippet works only when the Stop returns False in case the timer has already expired. Because only in this case the channel read will not block.
If the timer is already stopped , this operation will block indefinitely, therefore will not drain the channel since no value will be ever sent.
",1.0,"time: Timer.Stop documentation not covering all the cases - Hello,
In the section where the Stop method of a timer object is described there is a snippet about ensuring to drain the channel in case this method returns False.
However, it does not mention explicitly that this code snippet works only when the Stop returns False in case the timer has already expired. Because only in this case the channel read will not block.
If the timer is already stopped , this operation will block indefinitely, therefore will not drain the channel since no value will be ever sent.
",1,time  timer stop documentation not covering all the cases   hello   in the section where the stop method of a timer object is described there is a snippet about ensuring to drain the channel in case this method returns false   however  it does not mention explicitly that this code snippet works only when the stop returns false in case the timer has already expired  because only in this case the channel read will not block   if the timer is already stopped   this operation will block indefinitely  therefore will not drain the channel since no value will be ever sent   ,1
130949,27794264732.0,IssuesEvent,2023-03-17 11:15:40,microsoft/devicescript,https://api.github.com/repos/microsoft/devicescript,closed,development gateway should show cloud ApiRoot,vscode,otherwise you don't know which one you're connected to,1.0,development gateway should show cloud ApiRoot - otherwise you don't know which one you're connected to,0,development gateway should show cloud apiroot   otherwise you don t know which one you re connected to,0
211099,16419425204.0,IssuesEvent,2021-05-19 10:43:22,golang/go,https://api.github.com/repos/golang/go,closed,@mislav Documentation changes are fine.,Documentation,"@mislav Documentation changes are fine.

@dawidgolunski As far as I can tell `exec.LookPath` on Windows does not search the directory from which the application loaded at all.  It searches the current directory, then the directories on the environment variable `path`.

I could imagine a `exec.LookPathStrict` proposal.  Do you want to write one (https://golang.org/s/proposal)?  It could perhaps ignore `.` or any relative directory on the `PATH`/`path`.

_Originally posted by @ianlancetaylor in https://github.com/golang/go/issues/38736#issuecomment-718870248_",1.0,"@mislav Documentation changes are fine. - @mislav Documentation changes are fine.

@dawidgolunski As far as I can tell `exec.LookPath` on Windows does not search the directory from which the application loaded at all.  It searches the current directory, then the directories on the environment variable `path`.

I could imagine a `exec.LookPathStrict` proposal.  Do you want to write one (https://golang.org/s/proposal)?  It could perhaps ignore `.` or any relative directory on the `PATH`/`path`.

_Originally posted by @ianlancetaylor in https://github.com/golang/go/issues/38736#issuecomment-718870248_",1, mislav documentation changes are fine     mislav documentation changes are fine      dawidgolunski as far as i can tell  exec lookpath  on windows does not search the directory from which the application loaded at all   it searches the current directory  then the directories on the environment variable  path      i could imagine a  exec lookpathstrict  proposal   do you want to write one     it could perhaps ignore     or any relative directory on the  path   path       originally posted by  ianlancetaylor in  ,1
443495,12794974942.0,IssuesEvent,2020-07-02 07:57:38,moja-global/FLINT,https://api.github.com/repos/moja-global/FLINT,closed,Add pull request template ,Enhancement New Feature Priority = High X = Easy,"**Is your feature request related to a problem? Please describe.**
Adding a pull request template will make it easier for contributors and maintainers to review the code since they will first have to meet the checklist provided in the pull request template to be eligible for the review.

**Describe the solution you'd like**
Add pull request template markdown file to .github folder.

",1.0,"Add pull request template  - **Is your feature request related to a problem? Please describe.**
Adding a pull request template will make it easier for contributors and maintainers to review the code since they will first have to meet the checklist provided in the pull request template to be eligible for the review.

**Describe the solution you'd like**
Add pull request template markdown file to .github folder.

",0,add pull request template      is your feature request related to a problem  please describe     adding a pull request template will make it easier for contributors and maintainers to review the code since they will first have to meet the checklist provided in the pull request template to be eligible for the review       describe the solution you d like    add pull request template markdown file to  github folder     ,0
74,2492966558.0,IssuesEvent,2015-01-05 09:12:09,golang/go,https://api.github.com/repos/golang/go,closed,reflect: Value's == behavior changed between 1.3 and 1.4,documentation repo-main,"the following code snippet has different behavior when I run it on 1.3 and 1.4 respectively.
code are in https://play.golang.org/p/yfy7ZKqU1Y

when I run on 1.3, we have the following response:
```
false
0
0x0
true
```

while, It report false in the last println in golang 1.4
```
false
0
0x0
false
```

not sure whether it is a bug or something",1.0,"reflect: Value's == behavior changed between 1.3 and 1.4 - the following code snippet has different behavior when I run it on 1.3 and 1.4 respectively.
code are in https://play.golang.org/p/yfy7ZKqU1Y

when I run on 1.3, we have the following response:
```
false
0
0x0
true
```

while, It report false in the last println in golang 1.4
```
false
0
0x0
false
```

not sure whether it is a bug or something",1,reflect  value s    behavior changed between     and       the following code snippet has different behavior when i run it on     and     respectively   code are in      when i run on      we have the following response        false        true         while  it report false in the last println in golang           false        false         not sure whether it is a bug or something,1
210898,16389357800.0,IssuesEvent,2021-05-17 14:22:02,golang/go,https://api.github.com/repos/golang/go,closed,embed: Files starting with : (double dots) are not embedded (undocumented behavior),Documentation,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.16.4 linux/amd64
</pre>

### Does this issue reproduce with the latest release?



### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/baryshnikov/.cache/go-build""
GOENV=""/home/baryshnikov/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/baryshnikov/Develop/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/baryshnikov/Develop/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/opt/go/latest""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/opt/go/latest/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""go1.16.4""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build1338096382=/tmp/go-build -gno-record-gcc-switches""

</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

[demo-fs.tar.gz](https://github.com/golang/go/files/6493199/demo-fs.tar.gz)
<details><summary>Source code (see attachment)

</summary><br>
<pre>
package main

import (
	""embed""
	""fmt""
	""os""
)

//go:embed assets
var assets embed.FS

func main() {
	files := []string{
		""assets/root.txt"",
		""assets/:normal"",
		""assets/:alsonormal/file2.txt"",
	}

	// check in real file system
	for _, file := range files {
		_, err := os.Open(file)
		if err != nil {
			fmt.Println(""[FAILED ] failed open"", file, ""in real file system:"", err)
		} else {
			fmt.Println(""[SUCCESS] open"", file, ""in real file system"")
		}
	}

	// check in embedded
	for _, file := range files {
		_, err := assets.Open(file)
		if err != nil {
			fmt.Println(""[FAILED ] failed open"", file, ""in embedded file system"", "":"", err)
		} else {
			fmt.Println(""[SUCCESS] open"", file, ""in embedded file system"")
		}
	}
}

</pre>
</details>


### What did you expect to see?

Embedded files with `:` in names were included.

(from demo)

```
[SUCCESS] open assets/root.txt in real file system
[SUCCESS] open assets/:normal in real file system
[SUCCESS] open assets/:alsonormal/file2.txt in real file system
[SUCCESS] open assets/root.txt in embedded file system
[SUCCESS] open assets/:normal in embedded file system
[SUCCESS] open assets/:alsonormal/file2.txt in embedded file system
```

### What did you see instead?

Embedded files with `:` in names  were not included.

(from demo)

```
[SUCCESS] open assets/root.txt in real file system
[SUCCESS] open assets/:normal in real file system
[SUCCESS] open assets/:alsonormal/file2.txt in real file system
[SUCCESS] open assets/root.txt in embedded file system
[FAILED ] failed open assets/:normal in embedded file system : open assets/:normal: file does not exist
[FAILED ] failed open assets/:alsonormal/file2.txt in embedded file system : open assets/:alsonormal/file2.txt: file does not exist
```

### Analysis

Likely related to  https://github.com/golang/go/issues/45447.
Embedded files names restriction should be relaxed and/or documented.
",1.0,"embed: Files starting with : (double dots) are not embedded (undocumented behavior) - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.16.4 linux/amd64
</pre>

### Does this issue reproduce with the latest release?



### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/baryshnikov/.cache/go-build""
GOENV=""/home/baryshnikov/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/baryshnikov/Develop/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/baryshnikov/Develop/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/opt/go/latest""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/opt/go/latest/pkg/tool/linux_amd64""
GOVCS=""""
GOVERSION=""go1.16.4""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build1338096382=/tmp/go-build -gno-record-gcc-switches""

</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

[demo-fs.tar.gz](https://github.com/golang/go/files/6493199/demo-fs.tar.gz)
<details><summary>Source code (see attachment)

</summary><br>
<pre>
package main

import (
	""embed""
	""fmt""
	""os""
)

//go:embed assets
var assets embed.FS

func main() {
	files := []string{
		""assets/root.txt"",
		""assets/:normal"",
		""assets/:alsonormal/file2.txt"",
	}

	// check in real file system
	for _, file := range files {
		_, err := os.Open(file)
		if err != nil {
			fmt.Println(""[FAILED ] failed open"", file, ""in real file system:"", err)
		} else {
			fmt.Println(""[SUCCESS] open"", file, ""in real file system"")
		}
	}

	// check in embedded
	for _, file := range files {
		_, err := assets.Open(file)
		if err != nil {
			fmt.Println(""[FAILED ] failed open"", file, ""in embedded file system"", "":"", err)
		} else {
			fmt.Println(""[SUCCESS] open"", file, ""in embedded file system"")
		}
	}
}

</pre>
</details>


### What did you expect to see?

Embedded files with `:` in names were included.

(from demo)

```
[SUCCESS] open assets/root.txt in real file system
[SUCCESS] open assets/:normal in real file system
[SUCCESS] open assets/:alsonormal/file2.txt in real file system
[SUCCESS] open assets/root.txt in embedded file system
[SUCCESS] open assets/:normal in embedded file system
[SUCCESS] open assets/:alsonormal/file2.txt in embedded file system
```

### What did you see instead?

Embedded files with `:` in names  were not included.

(from demo)

```
[SUCCESS] open assets/root.txt in real file system
[SUCCESS] open assets/:normal in real file system
[SUCCESS] open assets/:alsonormal/file2.txt in real file system
[SUCCESS] open assets/root.txt in embedded file system
[FAILED ] failed open assets/:normal in embedded file system : open assets/:normal: file does not exist
[FAILED ] failed open assets/:alsonormal/file2.txt in embedded file system : open assets/:alsonormal/file2.txt: file does not exist
```

### Analysis

Likely related to  https://github.com/golang/go/issues/45447.
Embedded files names restriction should be relaxed and/or documented.
",1,embed  files starting with    double dots  are not embedded  undocumented behavior          please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version            go version  go version       linux             does this issue reproduce with the latest release             what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   home baryshnikov  cache go build   goenv   home baryshnikov  config go env   goexe     goflags     gohostarch      gohostos  linux   goinsecure     gomodcache   home baryshnikov develop go pkg mod   gonoproxy     gonosumdb     goos  linux   gopath   home baryshnikov develop go   goprivate     goproxy     goroot   opt go latest   gosumdb  sum golang org   gotmpdir     gotooldir   opt go latest pkg tool linux     govcs     goversion          gccgo  gccgo   ar  ar   cc  gcc   cxx  g     cgo enabled      gomod   dev null   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches               what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best                 source code  see attachment            package main    import    	 embed   	 fmt   	 os          go embed assets  var assets embed fs    func main      	files     string   		 assets root txt    		 assets  normal    		 assets  alsonormal   txt    	     	   check in real file system  	for    file    range files    		   err    os open file   		if err    nil    			fmt println    failed open   file   in real file system    err   		  else    			fmt println    open   file   in real file system    		   	     	   check in embedded  	for    file    range files    		   err    assets open file   		if err    nil    			fmt println    failed open   file   in embedded file system        err   		  else    			fmt println    open   file   in embedded file system    		   	                      what did you expect to see     embedded files with     in names were included      from demo            open assets root txt in real file system    open assets  normal in real file system    open assets  alsonormal   txt in real file system    open assets root txt in embedded file system    open assets  normal in embedded file system    open assets  alsonormal   txt in embedded file system             what did you see instead     embedded files with     in names  were not included      from demo            open assets root txt in real file system    open assets  normal in real file system    open assets  alsonormal   txt in real file system    open assets root txt in embedded file system    failed open assets  normal in embedded file system   open assets  normal  file does not exist    failed open assets  alsonormal   txt in embedded file system   open assets  alsonormal   txt  file does not exist             analysis    likely related to     embedded files names restriction should be relaxed and or documented   ,1
53641,28358809620.0,IssuesEvent,2023-04-12 09:16:12,yamoo9/likelion-FEQA,https://api.github.com/repos/yamoo9/likelion-FEQA,closed,[LAB-18] 성능개선을 위한 코드리뷰 요청,React 프로젝트 Q/A Performance Review,"## 질문 작성자

김동률

## 문제 상황
- 성능 개선을 위해 browser-image-compression 라이브러리, Recoil-Persist 등을 사용하여 어느 정도 개선을 시켰으나, 만족할만한 성능까지 올라오진 않은 상황입니다. 이에 전반적인 코드 리뷰를 요청 드리면서, 추가로 성능을 개선할 수 있는 부분이 있을지 조언을 받아보고 싶습니다.
- 현재 브라우저 inspect → 리액트 컴포넌트 툴로 확인해보면 파란색으로 리렌더링이 되는 영역이 많게 느껴졌습니다. 저희는 이 큰 리렌더링 영역이 성능저하의 주요 원인 중 하나라고 생각하고 있으나, 이를 어떻게 어떤 식으로 수정해나가야 할 지 방향을 잡는 데에 어려움을 갖고 있습니다. 관련된 조언을 부탁드립니다.
- Recoil를 상태관리를 했는데, 공통적으로 재사용하는 상태를 로그인 여부와 로그인된 회원의 정보 등 총 4가지로 잡았습니다. 상태관리와 Recoil이 처음이다보니, 저희가 작성한 코드처럼 활용하는 것이 맞는 방법인지, 또 이 4가지 외에 추가로 상태관리 해야하면 좋을 부분이 있을지도 여쭤보고 싶습니다.
- 현재 성능 점수 (Lighthouse 이용)
    - home : 68점
    - HotArticles : 83점
    - writeArticle : 86점
    - detailArticle : 76점
    - Mypage : 72점

**추가로 궁금한 사항**

- [x] 지난주에는 각 팀원별로 타입스크립트 공부를 진행했고, 이번주부터는 공부 내용을 서로 공유하면서, 감자마켓 프로젝트를 마이그레이션 해보려고 합니다. 마이그레이션 시 `let`, `const` 로 선언한 변수들의 타입을 지정하는 것 이외에 특히 유의해야하는 부분이 있을까요?
- [x] 로그아웃 버튼을 구현하는 코드 중, 권한 정보를 초기화하고, 홈 도메인(’/’)으로 이동하는 작업을 하고자 리액트 라우터의 `useNavigate` 메서드를 활용하고자 하였으나 오류메시지도 뜨지않고 동작하지 않습니다. 그래서 `window.location.replace` 메서드로 구현하였는데, `useNavigate`가 해당 코드에서 동작하지 않는 이유가 무엇일까요?

```jsx
src/component/LogoutButton.jsx 내

const handleLogout = async () => {
    try {
      await auth.signOut();
      setUserUid(null);
      setUserInfo({
        location: """",
        agree: """",
        email: """",
        nickname: """",
        phoneNumber: """",
        profileImage: """",
      });
      setShowToggle(false);
      window.location.replace(""/""); // 이 부분을 리액트라우터의 navigate('/')로 했을 때는 동작하지 않습니다.  
    } catch (error) {
      console.error(error);
    }
  }
```

## 프로젝트 저장소 URL
[POTATO-MARKET-main.zip](https://github.com/yamoo9/likelion-FEQA/files/11183331/POTATO-MARKET-main.zip)
- https://github.com/PROJECT-LAB18/POTATO-MARKET
- [https://potato-market-lab18.web.app/](https://potato-market-lab18.web.app/)

## 환경 정보

- 운영체제 정보: Windows, macOS
- Node.js 정보: v18.12.1
- 라이브러리 정보
    - React v18.2.0
    - React-router v6.8.2
    - Recoil v0.7.7
    - Firebase v9.17.2
",True,"[LAB-18] 성능개선을 위한 코드리뷰 요청 - ## 질문 작성자

김동률

## 문제 상황
- 성능 개선을 위해 browser-image-compression 라이브러리, Recoil-Persist 등을 사용하여 어느 정도 개선을 시켰으나, 만족할만한 성능까지 올라오진 않은 상황입니다. 이에 전반적인 코드 리뷰를 요청 드리면서, 추가로 성능을 개선할 수 있는 부분이 있을지 조언을 받아보고 싶습니다.
- 현재 브라우저 inspect → 리액트 컴포넌트 툴로 확인해보면 파란색으로 리렌더링이 되는 영역이 많게 느껴졌습니다. 저희는 이 큰 리렌더링 영역이 성능저하의 주요 원인 중 하나라고 생각하고 있으나, 이를 어떻게 어떤 식으로 수정해나가야 할 지 방향을 잡는 데에 어려움을 갖고 있습니다. 관련된 조언을 부탁드립니다.
- Recoil를 상태관리를 했는데, 공통적으로 재사용하는 상태를 로그인 여부와 로그인된 회원의 정보 등 총 4가지로 잡았습니다. 상태관리와 Recoil이 처음이다보니, 저희가 작성한 코드처럼 활용하는 것이 맞는 방법인지, 또 이 4가지 외에 추가로 상태관리 해야하면 좋을 부분이 있을지도 여쭤보고 싶습니다.
- 현재 성능 점수 (Lighthouse 이용)
    - home : 68점
    - HotArticles : 83점
    - writeArticle : 86점
    - detailArticle : 76점
    - Mypage : 72점

**추가로 궁금한 사항**

- [x] 지난주에는 각 팀원별로 타입스크립트 공부를 진행했고, 이번주부터는 공부 내용을 서로 공유하면서, 감자마켓 프로젝트를 마이그레이션 해보려고 합니다. 마이그레이션 시 `let`, `const` 로 선언한 변수들의 타입을 지정하는 것 이외에 특히 유의해야하는 부분이 있을까요?
- [x] 로그아웃 버튼을 구현하는 코드 중, 권한 정보를 초기화하고, 홈 도메인(’/’)으로 이동하는 작업을 하고자 리액트 라우터의 `useNavigate` 메서드를 활용하고자 하였으나 오류메시지도 뜨지않고 동작하지 않습니다. 그래서 `window.location.replace` 메서드로 구현하였는데, `useNavigate`가 해당 코드에서 동작하지 않는 이유가 무엇일까요?

```jsx
src/component/LogoutButton.jsx 내

const handleLogout = async () => {
    try {
      await auth.signOut();
      setUserUid(null);
      setUserInfo({
        location: """",
        agree: """",
        email: """",
        nickname: """",
        phoneNumber: """",
        profileImage: """",
      });
      setShowToggle(false);
      window.location.replace(""/""); // 이 부분을 리액트라우터의 navigate('/')로 했을 때는 동작하지 않습니다.  
    } catch (error) {
      console.error(error);
    }
  }
```

## 프로젝트 저장소 URL
[POTATO-MARKET-main.zip](https://github.com/yamoo9/likelion-FEQA/files/11183331/POTATO-MARKET-main.zip)
- https://github.com/PROJECT-LAB18/POTATO-MARKET
- [https://potato-market-lab18.web.app/](https://potato-market-lab18.web.app/)

## 환경 정보

- 운영체제 정보: Windows, macOS
- Node.js 정보: v18.12.1
- 라이브러리 정보
    - React v18.2.0
    - React-router v6.8.2
    - Recoil v0.7.7
    - Firebase v9.17.2
",0,  성능개선을 위한 코드리뷰 요청      질문 작성자    김동률       문제 상황    성능 개선을 위해 browser image compression 라이브러리  recoil persist 등을 사용하여 어느 정도 개선을 시켰으나  만족할만한 성능까지 올라오진 않은 상황입니다  이에 전반적인 코드 리뷰를 요청 드리면서  추가로 성능을 개선할 수 있는 부분이 있을지 조언을 받아보고 싶습니다     현재 브라우저 inspect → 리액트 컴포넌트 툴로 확인해보면 파란색으로 리렌더링이 되는 영역이 많게 느껴졌습니다  저희는 이 큰 리렌더링 영역이 성능저하의 주요 원인 중 하나라고 생각하고 있으나  이를 어떻게 어떤 식으로 수정해나가야 할 지 방향을 잡는 데에 어려움을 갖고 있습니다  관련된 조언을 부탁드립니다     recoil를 상태관리를 했는데  공통적으로 재사용하는 상태를 로그인 여부와 로그인된 회원의 정보 등 총   잡았습니다  상태관리와 recoil이 처음이다보니  저희가 작성한 코드처럼 활용하는 것이 맞는 방법인지  또 이   외에 추가로 상태관리 해야하면 좋을 부분이 있을지도 여쭤보고 싶습니다     현재 성능 점수  lighthouse 이용         home            hotarticles            writearticle            detailarticle            mypage          추가로 궁금한 사항          지난주에는 각 팀원별로 타입스크립트 공부를 진행했고  이번주부터는 공부 내용을 서로 공유하면서  감자마켓 프로젝트를 마이그레이션 해보려고 합니다  마이그레이션 시  let    const  로 선언한 변수들의 타입을 지정하는 것 이외에 특히 유의해야하는 부분이 있을까요       로그아웃 버튼을 구현하는 코드 중  권한 정보를 초기화하고  홈 도메인 ’ ’ 으로 이동하는 작업을 하고자 리액트 라우터의  usenavigate  메서드를 활용하고자 하였으나 오류메시지도 뜨지않고 동작하지 않습니다  그래서  window location replace  메서드로 구현하였는데   usenavigate 가 해당 코드에서 동작하지 않는 이유가 무엇일까요        jsx  src component logoutbutton jsx 내    const handlelogout   async              try          await auth signout           setuseruid null          setuserinfo            location               agree               email               nickname               phonenumber               profileimage                        setshowtoggle false          window location replace          이 부분을 리액트라우터의 navigate     로 했을 때는 동작하지 않습니다           catch  error           console error error                          프로젝트 저장소 url                        환경 정보      운영체제 정보  windows  macos    node js 정보           라이브러리 정보        react              react router              recoil              firebase        ,0
387185,26715071814.0,IssuesEvent,2023-01-28 11:53:30,golang/go,https://api.github.com/repos/golang/go,closed,doc: clarify fetching Go 1.4 from git,Documentation help wanted NeedsFix,"A decision seems to have been made to no longer provide version controlled 1.4.x source code for doing a clean Go bootstrap on macOS. Is this true? You need a special tarball?  How should the the current state of affairs for source code bootstrapping be characterized?

I think the comment that kinda shook me was:
@ianlancetaylor 
`I suppose I am mildly in favor of doing a 1.4.4 release for better Darwin support going forward.`

Currently to get close to a clean bootstrap you have to download a special tarball. A doc change was made to fix the bootstrap issue. But on my system that *special version* of 1.4.3 builds but doesn't pass tests. It will build 10.2 however.

**What really gets me in the craw is the atavistic reversion  to a tarball instead of using git and version control.**

Yes, I know I could have used my existing Go 10.1 to compile 10.2. Is that what everyone else does now?

Perhaps the pain level of maintaining the 1.4 bootstrap has been reached? Maybe it is time to retire the 1.4 bootstrap and just use archived binaries of previous versions of Go? I think there is some risk and complexity with that approach too, but it's a valid approach, and I could live with it. Whatever the decision is, it should be an explicit decision, not something the team slumps into because no one wants to maintain the bootstrap anymore.

tl;dr version below.
I recently got a new MacBook Pro. Previously I was running macOS 10.10 on my beloved MBP 17""  but the new laptop came with High Sierra, macOS 10.13.5 and the Go team had just issued 10.2. Time to update. I am a build from source kinda guy so I did the `git pull` and `all.bash`.

    Building Go cmd/dist using /Volumes/std/usr/leb/go1.4.
    failed MSpanList_Insert 0x783000 0xffd30d60dd0 0x0
    fatal error: MSpanList_Insert

Check to see if there is a newer bootstrap version. There is a 1.4.3. Get that. Build it. Same thing.

Look around, it's a High Sierra issue and Go issue 16352 seems to have the answers.

https://github.com/golang/go/issues/16352
https://github.com/golang/go/issues/17335
https://github.com/golang/go/issues/17182

So now I need to download a tarball to bootstrap? That's what the doc says. Oh, they fixed it with a tarball and a doc change.

    To build a bootstrap toolchain from source, use either the git branch release-branch.go1.4 or
    go1.4-bootstrap-20171003.tar.gz, which contains the Go 1.4 source code plus accumulated fixes to keep
    the tools running on newer operating systems.

Download the tarball. Have some kind of issue but I update Xcode and all is OK. At least it builds this time but now it fails with a timezone issue.

    ok  	text/template/parse	0.015s
    --- FAIL: TestParseInLocation-11 (0.00s)
	format_test.go:202: ParseInLocation(Feb 01 2013 AST, Baghdad) = 2013-02-01 00:00:00 +0000 AST,     want 2013-02-01 00:00:00 +0300 +03

Check that error out. It's a known issue because the timezone data changed and the test isn't fixed in the tarball. 

https://github.com/golang/go/issues/19457

I replace the `TestParseInLocation in the tarball with the one from 10.2 and it works.

**Wow this was painful and when building 10.2 I still get an error on my machine.**

    --- FAIL: TestRespectSetgidDir (0.00s)
        build_test.go:225:     
    moveOrCopyFile(""/var/folders/95/zwjzrdwc8xj7yg001s6slck80000gn/T/SetGroupID592840517/setgid"",     
    ""/var/folders/95/zwjzrdwc8xj7yg001s6slck80000gn/T/pkgfile074436576""): want ""cp 
    /var/folders/95/zwjzrdwc8xj7yg001s6slck80000gn/T/pkgfile074436576 
    /var/folders/95/zwjzrdwc8xj7yg001s6slck80000gn/T/SetGroupID592840517/setgid"", got ""mv 
    /var/folders/95/zwjzrdwc8xj7yg001s6slck80000gn/T/pkgfile074436576 
    /var/folders/95/zwjzrdwc8xj7yg001s6slck80000gn/T/SetGroupID592840517/setgid""
    FAIL
    FAIL    cmd/go/internal/work    0.025s

which is also supposedly fixed but has been failing on my previous  laptop even with 10.10. I will try to figure out what is going on with that. Maybe something to do with being a member of multiple groups? IDK. That's a different issue and I get the feeling it may be specific to my setup.",1.0,"doc: clarify fetching Go 1.4 from git - A decision seems to have been made to no longer provide version controlled 1.4.x source code for doing a clean Go bootstrap on macOS. Is this true? You need a special tarball?  How should the the current state of affairs for source code bootstrapping be characterized?

I think the comment that kinda shook me was:
@ianlancetaylor 
`I suppose I am mildly in favor of doing a 1.4.4 release for better Darwin support going forward.`

Currently to get close to a clean bootstrap you have to download a special tarball. A doc change was made to fix the bootstrap issue. But on my system that *special version* of 1.4.3 builds but doesn't pass tests. It will build 10.2 however.

**What really gets me in the craw is the atavistic reversion  to a tarball instead of using git and version control.**

Yes, I know I could have used my existing Go 10.1 to compile 10.2. Is that what everyone else does now?

Perhaps the pain level of maintaining the 1.4 bootstrap has been reached? Maybe it is time to retire the 1.4 bootstrap and just use archived binaries of previous versions of Go? I think there is some risk and complexity with that approach too, but it's a valid approach, and I could live with it. Whatever the decision is, it should be an explicit decision, not something the team slumps into because no one wants to maintain the bootstrap anymore.

tl;dr version below.
I recently got a new MacBook Pro. Previously I was running macOS 10.10 on my beloved MBP 17""  but the new laptop came with High Sierra, macOS 10.13.5 and the Go team had just issued 10.2. Time to update. I am a build from source kinda guy so I did the `git pull` and `all.bash`.

    Building Go cmd/dist using /Volumes/std/usr/leb/go1.4.
    failed MSpanList_Insert 0x783000 0xffd30d60dd0 0x0
    fatal error: MSpanList_Insert

Check to see if there is a newer bootstrap version. There is a 1.4.3. Get that. Build it. Same thing.

Look around, it's a High Sierra issue and Go issue 16352 seems to have the answers.

https://github.com/golang/go/issues/16352
https://github.com/golang/go/issues/17335
https://github.com/golang/go/issues/17182

So now I need to download a tarball to bootstrap? That's what the doc says. Oh, they fixed it with a tarball and a doc change.

    To build a bootstrap toolchain from source, use either the git branch release-branch.go1.4 or
    go1.4-bootstrap-20171003.tar.gz, which contains the Go 1.4 source code plus accumulated fixes to keep
    the tools running on newer operating systems.

Download the tarball. Have some kind of issue but I update Xcode and all is OK. At least it builds this time but now it fails with a timezone issue.

    ok  	text/template/parse	0.015s
    --- FAIL: TestParseInLocation-11 (0.00s)
	format_test.go:202: ParseInLocation(Feb 01 2013 AST, Baghdad) = 2013-02-01 00:00:00 +0000 AST,     want 2013-02-01 00:00:00 +0300 +03

Check that error out. It's a known issue because the timezone data changed and the test isn't fixed in the tarball. 

https://github.com/golang/go/issues/19457

I replace the `TestParseInLocation in the tarball with the one from 10.2 and it works.

**Wow this was painful and when building 10.2 I still get an error on my machine.**

    --- FAIL: TestRespectSetgidDir (0.00s)
        build_test.go:225:     
    moveOrCopyFile(""/var/folders/95/zwjzrdwc8xj7yg001s6slck80000gn/T/SetGroupID592840517/setgid"",     
    ""/var/folders/95/zwjzrdwc8xj7yg001s6slck80000gn/T/pkgfile074436576""): want ""cp 
    /var/folders/95/zwjzrdwc8xj7yg001s6slck80000gn/T/pkgfile074436576 
    /var/folders/95/zwjzrdwc8xj7yg001s6slck80000gn/T/SetGroupID592840517/setgid"", got ""mv 
    /var/folders/95/zwjzrdwc8xj7yg001s6slck80000gn/T/pkgfile074436576 
    /var/folders/95/zwjzrdwc8xj7yg001s6slck80000gn/T/SetGroupID592840517/setgid""
    FAIL
    FAIL    cmd/go/internal/work    0.025s

which is also supposedly fixed but has been failing on my previous  laptop even with 10.10. I will try to figure out what is going on with that. Maybe something to do with being a member of multiple groups? IDK. That's a different issue and I get the feeling it may be specific to my setup.",1,doc  clarify fetching go     from git   a decision seems to have been made to no longer provide version controlled     x source code for doing a clean go bootstrap on macos  is this true  you need a special tarball   how should the the current state of affairs for source code bootstrapping be characterized     i think the comment that kinda shook me was    ianlancetaylor    i suppose i am mildly in favor of doing a       release for better darwin support going forward      currently to get close to a clean bootstrap you have to download a special tarball  a doc change was made to fix the bootstrap issue  but on my system that  special version  of       builds but doesn t pass tests  it will build     however       what really gets me in the craw is the atavistic reversion  to a tarball instead of using git and version control       yes  i know i could have used my existing go     to compile      is that what everyone else does now     perhaps the pain level of maintaining the     bootstrap has been reached  maybe it is time to retire the     bootstrap and just use archived binaries of previous versions of go  i think there is some risk and complexity with that approach too  but it s a valid approach  and i could live with it  whatever the decision is  it should be an explicit decision  not something the team slumps into because no one wants to maintain the bootstrap anymore     tl dr version below   i recently got a new macbook pro  previously i was running macos     on my beloved mbp     but the new laptop came with high sierra  macos       and the go team had just issued      time to update  i am a build from source kinda guy so i did the  git pull  and  all bash          building go cmd dist using  volumes std usr leb           failed mspanlist insert            fatal error  mspanlist insert    check to see if there is a newer bootstrap version  there is a        get that  build it  same thing     look around  it s a high sierra issue and go issue   seems to have the answers                so now i need to download a tarball to bootstrap  that s what the doc says  oh  they fixed it with a tarball and a doc change         to build a bootstrap toolchain from source  use either the git branch release branch     or          bootstrap   tar gz  which contains the go     source code plus accumulated fixes to keep      the tools running on newer operating systems     download the tarball  have some kind of issue but i update xcode and all is ok  at least it builds this time but now it fails with a timezone issue         ok  	text template parse	             fail  testparseinlocation          	format test go    parseinlocation feb     ast  baghdad                   ast      want                      check that error out  it s a known issue because the timezone data changed and the test isn t fixed in the tarball           i replace the  testparseinlocation in the tarball with the one from     and it works       wow this was painful and when building     i still get an error on my machine               fail  testrespectsetgiddir                build test go              moveorcopyfile   var folders     t   setgid               var folders     t      want  cp        var folders     t          var folders     t   setgid   got  mv        var folders     t          var folders     t   setgid       fail      fail    cmd go internal work           which is also supposedly fixed but has been failing on my previous  laptop even with      i will try to figure out what is going on with that  maybe something to do with being a member of multiple groups  idk  that s a different issue and i get the feeling it may be specific to my setup ,1
53655,13262061513.0,IssuesEvent,2020-08-20 21:01:58,icecube-trac/tix4,https://api.github.com/repos/icecube-trac/tix4,closed,L1 filter for 2014 and 2015 (Trac #1828),Migrated from Trac cmake defect,"Running offline filter for 2014 and 2015:
/cvmfs/icecube.opensciencegrid.org/py2-v1/RHEL_6_x86_64/metaprojects/icerec/IC2014-L2_V14-02-00/lib/icecube/filterscripts/offlineL2/level1_SimulationFiltering.py

I receive the following error:
`RuntimeError: dlopen() dynamic loading error: /data/user/saxani/environments/buildfwd/lib/libpfauxiliary.so: cannot open shared object file: No such file or directory`


<details>
 <summary><em>Migrated from <a href=""https://code.icecube.wisc.edu/projects/icecube/ticket/1828"">https://code.icecube.wisc.edu/projects/icecube/ticket/1828</a>, reported by saxani</summary>
<p>

```json
{
    ""status"": ""closed"",
    ""changetime"": ""2016-08-18T21:39:38"",
    ""_ts"": ""1471556378950850"",
    ""description"": ""Running offline filter for 2014 and 2015:\n/cvmfs/icecube.opensciencegrid.org/py2-v1/RHEL_6_x86_64/metaprojects/icerec/IC2014-L2_V14-02-00/lib/icecube/filterscripts/offlineL2/level1_SimulationFiltering.py\n\nI receive the following error:\n`RuntimeError: dlopen() dynamic loading error: /data/user/saxani/environments/buildfwd/lib/libpfauxiliary.so: cannot open shared object file: No such file or directory`\n"",
    ""reporter"": ""saxani"",
    ""cc"": """",
    ""resolution"": ""fixed"",
    ""time"": ""2016-08-18T21:29:33"",
    ""component"": ""cmake"",
    ""summary"": ""L1 filter for 2014 and 2015"",
    ""priority"": ""normal"",
    ""keywords"": """",
    ""milestone"": """",
    ""owner"": """",
    ""type"": ""defect""
}
```

</p>
</details>
",1.0,"L1 filter for 2014 and 2015 (Trac #1828) - Running offline filter for 2014 and 2015:
/cvmfs/icecube.opensciencegrid.org/py2-v1/RHEL_6_x86_64/metaprojects/icerec/IC2014-L2_V14-02-00/lib/icecube/filterscripts/offlineL2/level1_SimulationFiltering.py

I receive the following error:
`RuntimeError: dlopen() dynamic loading error: /data/user/saxani/environments/buildfwd/lib/libpfauxiliary.so: cannot open shared object file: No such file or directory`


<details>
 <summary><em>Migrated from <a href=""https://code.icecube.wisc.edu/projects/icecube/ticket/1828"">https://code.icecube.wisc.edu/projects/icecube/ticket/1828</a>, reported by saxani</summary>
<p>

```json
{
    ""status"": ""closed"",
    ""changetime"": ""2016-08-18T21:39:38"",
    ""_ts"": ""1471556378950850"",
    ""description"": ""Running offline filter for 2014 and 2015:\n/cvmfs/icecube.opensciencegrid.org/py2-v1/RHEL_6_x86_64/metaprojects/icerec/IC2014-L2_V14-02-00/lib/icecube/filterscripts/offlineL2/level1_SimulationFiltering.py\n\nI receive the following error:\n`RuntimeError: dlopen() dynamic loading error: /data/user/saxani/environments/buildfwd/lib/libpfauxiliary.so: cannot open shared object file: No such file or directory`\n"",
    ""reporter"": ""saxani"",
    ""cc"": """",
    ""resolution"": ""fixed"",
    ""time"": ""2016-08-18T21:29:33"",
    ""component"": ""cmake"",
    ""summary"": ""L1 filter for 2014 and 2015"",
    ""priority"": ""normal"",
    ""keywords"": """",
    ""milestone"": """",
    ""owner"": """",
    ""type"": ""defect""
}
```

</p>
</details>
",0,  filter for   and    trac       running offline filter for   and     cvmfs icecube opensciencegrid org     rhel       metaprojects icerec           lib icecube filterscripts     simulationfiltering py  i receive the following error   runtimeerror  dlopen   dynamic loading error   data user saxani environments buildfwd lib libpfauxiliary so  cannot open shared object file  no such file or directory         migrated from         json        status    closed        changetime                      ts             description    running offline filter for   and    n cvmfs icecube opensciencegrid org     rhel       metaprojects icerec           lib icecube filterscripts     simulationfiltering py n ni receive the following error  n runtimeerror  dlopen   dynamic loading error   data user saxani environments buildfwd lib libpfauxiliary so  cannot open shared object file  no such file or directory  n        reporter    saxani        cc            resolution    fixed        time                     component    cmake        summary      filter for   and          priority    normal        keywords            milestone            owner            type    defect             ,0
53958,13262559276.0,IssuesEvent,2020-08-20 22:03:14,icecube-trac/tix4,https://api.github.com/repos/icecube-trac/tix4,closed,PROPOSAL x-sections error (Trac #2392),Migrated from Trac combo simulation defect,"In testing the simulation chain I ran into the following exception:

FATAL (PROPOSAL): No Cross Section was found!!! (Propagator.cxx:740 in void PROPOSAL::Propagator::ChooseCurrentCollection(const PROPOSAL::Vector3D&, const PROPOSAL::Vector3D&))
ERROR (I3Module): propagator_propagator: Exception thrown (I3Module.cxx:123 in void I3Module::Do(void (I3Module::*)()))

This happens both with the I3_TESTDATA and when generating tables by hand.

This error was produced while processing a corsika 5-component simulation. Similar test with NuGen did not reproduce the error.

The input file used for this test can be found in cobalt:/data/user/juancarlos/PROPOSAL-test/cors.i3

Execution script from simprod-scripts:

python simprod-scripts/resources/scripts/clsim.py --gcdfile /cvmfs/icecube.opensciencegrid.org/data/GCD/GeoCalibDetectorStatus_AVG_55697-57531_PASS2_SPE_withStdNoise.i3.gz --inputfile nugen.i3.zst --outputfile photons.i3 --UseGPUs  --UseGSLRNG

<details>
 <summary><em>Migrated from <a href=""https://code.icecube.wisc.edu/projects/icecube/ticket/2392"">https://code.icecube.wisc.edu/projects/icecube/ticket/2392</a>, reported by juancarlosand owned by jsoedingrekso</em></summary>
<p>

```json
{
    ""status"": ""closed"",
    ""changetime"": ""2019-12-20T13:05:24"",
    ""_ts"": ""1576847124392693"",
    ""description"": ""In testing the simulation chain I ran into the following exception:\n\nFATAL (PROPOSAL): No Cross Section was found!!! (Propagator.cxx:740 in void PROPOSAL::Propagator::ChooseCurrentCollection(const PROPOSAL::Vector3D&, const PROPOSAL::Vector3D&))\nERROR (I3Module): propagator_propagator: Exception thrown (I3Module.cxx:123 in void I3Module::Do(void (I3Module::*)()))\n\nThis happens both with the I3_TESTDATA and when generating tables by hand.\n\nThis error was produced while processing a corsika 5-component simulation. Similar test with NuGen did not reproduce the error.\n\nThe input file used for this test can be found in cobalt:/data/user/juancarlos/PROPOSAL-test/cors.i3\n\nExecution script from simprod-scripts:\n\npython simprod-scripts/resources/scripts/clsim.py --gcdfile /cvmfs/icecube.opensciencegrid.org/data/GCD/GeoCalibDetectorStatus_AVG_55697-57531_PASS2_SPE_withStdNoise.i3.gz --inputfile nugen.i3.zst --outputfile photons.i3 --UseGPUs  --UseGSLRNG"",
    ""reporter"": ""juancarlos"",
    ""cc"": """",
    ""resolution"": ""fixed"",
    ""time"": ""2019-12-19T17:00:09"",
    ""component"": ""combo simulation"",
    ""summary"": ""PROPOSAL x-sections error"",
    ""priority"": ""blocker"",
    ""keywords"": ""PROPOSAL"",
    ""milestone"": """",
    ""owner"": ""jsoedingrekso"",
    ""type"": ""defect""
}
```

</p>
</details>
",1.0,"PROPOSAL x-sections error (Trac #2392) - In testing the simulation chain I ran into the following exception:

FATAL (PROPOSAL): No Cross Section was found!!! (Propagator.cxx:740 in void PROPOSAL::Propagator::ChooseCurrentCollection(const PROPOSAL::Vector3D&, const PROPOSAL::Vector3D&))
ERROR (I3Module): propagator_propagator: Exception thrown (I3Module.cxx:123 in void I3Module::Do(void (I3Module::*)()))

This happens both with the I3_TESTDATA and when generating tables by hand.

This error was produced while processing a corsika 5-component simulation. Similar test with NuGen did not reproduce the error.

The input file used for this test can be found in cobalt:/data/user/juancarlos/PROPOSAL-test/cors.i3

Execution script from simprod-scripts:

python simprod-scripts/resources/scripts/clsim.py --gcdfile /cvmfs/icecube.opensciencegrid.org/data/GCD/GeoCalibDetectorStatus_AVG_55697-57531_PASS2_SPE_withStdNoise.i3.gz --inputfile nugen.i3.zst --outputfile photons.i3 --UseGPUs  --UseGSLRNG

<details>
 <summary><em>Migrated from <a href=""https://code.icecube.wisc.edu/projects/icecube/ticket/2392"">https://code.icecube.wisc.edu/projects/icecube/ticket/2392</a>, reported by juancarlosand owned by jsoedingrekso</em></summary>
<p>

```json
{
    ""status"": ""closed"",
    ""changetime"": ""2019-12-20T13:05:24"",
    ""_ts"": ""1576847124392693"",
    ""description"": ""In testing the simulation chain I ran into the following exception:\n\nFATAL (PROPOSAL): No Cross Section was found!!! (Propagator.cxx:740 in void PROPOSAL::Propagator::ChooseCurrentCollection(const PROPOSAL::Vector3D&, const PROPOSAL::Vector3D&))\nERROR (I3Module): propagator_propagator: Exception thrown (I3Module.cxx:123 in void I3Module::Do(void (I3Module::*)()))\n\nThis happens both with the I3_TESTDATA and when generating tables by hand.\n\nThis error was produced while processing a corsika 5-component simulation. Similar test with NuGen did not reproduce the error.\n\nThe input file used for this test can be found in cobalt:/data/user/juancarlos/PROPOSAL-test/cors.i3\n\nExecution script from simprod-scripts:\n\npython simprod-scripts/resources/scripts/clsim.py --gcdfile /cvmfs/icecube.opensciencegrid.org/data/GCD/GeoCalibDetectorStatus_AVG_55697-57531_PASS2_SPE_withStdNoise.i3.gz --inputfile nugen.i3.zst --outputfile photons.i3 --UseGPUs  --UseGSLRNG"",
    ""reporter"": ""juancarlos"",
    ""cc"": """",
    ""resolution"": ""fixed"",
    ""time"": ""2019-12-19T17:00:09"",
    ""component"": ""combo simulation"",
    ""summary"": ""PROPOSAL x-sections error"",
    ""priority"": ""blocker"",
    ""keywords"": ""PROPOSAL"",
    ""milestone"": """",
    ""owner"": ""jsoedingrekso"",
    ""type"": ""defect""
}
```

</p>
</details>
",0,proposal x sections error  trac       in testing the simulation chain i ran into the following exception   fatal  proposal   no cross section was found     propagator cxx   in void proposal  propagator  choosecurrentcollection const proposal      const proposal       error      propagator propagator  exception thrown    cxx   in void    do void             this happens both with the   testdata and when generating tables by hand   this error was produced while processing a corsika   component simulation  similar test with nugen did not reproduce the error   the input file used for this test can be found in cobalt  data user juancarlos proposal test cors    execution script from simprod scripts   python simprod scripts resources scripts clsim py   gcdfile  cvmfs icecube opensciencegrid org data gcd geocalibdetectorstatus avg       spe withstdnoise   gz   inputfile nugen   zst   outputfile photons     usegpus    usegslrng       migrated from          json        status    closed        changetime                      ts             description    in testing the simulation chain i ran into the following exception  n nfatal  proposal   no cross section was found     propagator cxx   in void proposal  propagator  choosecurrentcollection const proposal      const proposal       nerror      propagator propagator  exception thrown    cxx   in void    do void            n nthis happens both with the   testdata and when generating tables by hand  n nthis error was produced while processing a corsika   component simulation  similar test with nugen did not reproduce the error  n nthe input file used for this test can be found in cobalt  data user juancarlos proposal test cors   n nexecution script from simprod scripts  n npython simprod scripts resources scripts clsim py   gcdfile  cvmfs icecube opensciencegrid org data gcd geocalibdetectorstatus avg       spe withstdnoise   gz   inputfile nugen   zst   outputfile photons     usegpus    usegslrng        reporter    juancarlos        cc            resolution    fixed        time                     component    combo simulation        summary    proposal x sections error        priority    blocker        keywords    proposal        milestone            owner    jsoedingrekso        type    defect             ,0
36229,6520997092.0,IssuesEvent,2017-08-28 18:46:23,golang/go,https://api.github.com/repos/golang/go,opened,docs: add support for languages other than English,Documentation,"Right now the docs are only in English. There's [some support](https://github.com/golang/go/wiki/NonEnglish) for languages other than English, but the wiki page is merely a footnote.

Other projects—[like React](https://crowdin.com/project/react)—are attempting this as well. Not only does it give newcomers a (somewhat) easy way to contribute to Go, it also makes Go a more welcoming and inclusive place for non-English speakers. Obviously the English version would remain the ""master"" version of the docs.

Ideally, golang.org would respect the `Accept-Language` header or support some sort of `en/`, `fr/`, etc. URL path option.

I'm not sure how much of a proposal this needs to be, but it's something I'm willing to put further thought into if needed. (It's not a language change or anything, so I didn't write out a full proposal.)",1.0,"docs: add support for languages other than English - Right now the docs are only in English. There's [some support](https://github.com/golang/go/wiki/NonEnglish) for languages other than English, but the wiki page is merely a footnote.

Other projects—[like React](https://crowdin.com/project/react)—are attempting this as well. Not only does it give newcomers a (somewhat) easy way to contribute to Go, it also makes Go a more welcoming and inclusive place for non-English speakers. Obviously the English version would remain the ""master"" version of the docs.

Ideally, golang.org would respect the `Accept-Language` header or support some sort of `en/`, `fr/`, etc. URL path option.

I'm not sure how much of a proposal this needs to be, but it's something I'm willing to put further thought into if needed. (It's not a language change or anything, so I didn't write out a full proposal.)",1,docs  add support for languages other than english   right now the docs are only in english  there s     for languages other than english  but the wiki page is merely a footnote     other projects—    attempting this as well  not only does it give newcomers a  somewhat  easy way to contribute to go  it also makes go a more welcoming and inclusive place for non english speakers  obviously the english version would remain the  master  version of the docs     ideally  golang org would respect the  accept language  header or support some sort of  en     fr    etc  url path option     i m not sure how much of a proposal this needs to be  but it s something i m willing to put further thought into if needed   it s not a language change or anything  so i didn t write out a full proposal  ,1
70950,9462993574.0,IssuesEvent,2019-04-17 16:39:11,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: go mod why lies,Documentation NeedsInvestigation WaitingForInfo modules,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
go version go1.12.1 darwin/amd64

</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/me/Library/Caches/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/me/go""
GOPROXY=""""
GORACE=""""
GOROOT=""/Users/me/sdk/go1.12.1""
GOTMPDIR=""""
GOTOOLDIR=""/Users/me/sdk/go1.12.1/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/me/orbital/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/sp/06p28g2d0vs7gd2vhf26wl9m0000gn/T/go-build849154512=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?

<pre>
$ grep bson go.mod 
$ grep labix go.mod
        labix.org/v2/mgo v0.0.0-20140701140051-000000000287 // indirect
$ go mod why labix.org/v2/mgo
# labix.org/v2/mgo
(main module does not need package labix.org/v2/mgo)
$ go mod why labix.org/v2/mgo/bson
# labix.org/v2/mgo/bson
/very/important/package
github.com/nats-io/go-nats-streaming
github.com/nats-io/go-nats-streaming.test
github.com/nats-io/nats-streaming-server/server
github.com/hashicorp/go-msgpack/codec
github.com/hashicorp/go-msgpack/codec.test
labix.org/v2/mgo/bson
$ go mod vendor
$ find vendor -name bson
$
</pre>



### What did you expect to see?

At least some mention of the package ""bson"" anywhere in go mod's output.

### What did you see instead?

Zero mention of the package ""bson"" anywhere in go mod's output.",1.0,"cmd/go: go mod why lies - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
go version go1.12.1 darwin/amd64

</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/me/Library/Caches/go-build""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/me/go""
GOPROXY=""""
GORACE=""""
GOROOT=""/Users/me/sdk/go1.12.1""
GOTMPDIR=""""
GOTOOLDIR=""/Users/me/sdk/go1.12.1/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/Users/me/orbital/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/sp/06p28g2d0vs7gd2vhf26wl9m0000gn/T/go-build849154512=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?

<pre>
$ grep bson go.mod 
$ grep labix go.mod
        labix.org/v2/mgo v0.0.0-20140701140051-000000000287 // indirect
$ go mod why labix.org/v2/mgo
# labix.org/v2/mgo
(main module does not need package labix.org/v2/mgo)
$ go mod why labix.org/v2/mgo/bson
# labix.org/v2/mgo/bson
/very/important/package
github.com/nats-io/go-nats-streaming
github.com/nats-io/go-nats-streaming.test
github.com/nats-io/nats-streaming-server/server
github.com/hashicorp/go-msgpack/codec
github.com/hashicorp/go-msgpack/codec.test
labix.org/v2/mgo/bson
$ go mod vendor
$ find vendor -name bson
$
</pre>



### What did you expect to see?

At least some mention of the package ""bson"" anywhere in go mod's output.

### What did you see instead?

Zero mention of the package ""bson"" anywhere in go mod's output.",1,cmd go  go mod why lies            what version of go are you using   go version          go version       darwin               does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env          go env  output       go env  goarch      gobin     gocache   users me library caches go build   goexe     goflags     gohostarch      gohostos  darwin   goos  darwin   gopath   users me go   goproxy     gorace     goroot   users me sdk         gotmpdir     gotooldir   users me sdk       pkg tool darwin     gccgo  gccgo   cc  clang   cxx  clang     cgo enabled      gomod   users me orbital go mod   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders sp   t go    tmp go build  gno record gcc switches  fno common             what did you do          grep bson go mod     grep labix go mod          labix org   mgo              indirect    go mod why labix org   mgo    labix org   mgo   main module does not need package labix org   mgo     go mod why labix org   mgo bson    labix org   mgo bson   very important package  github com nats io go nats streaming  github com nats io go nats streaming test  github com nats io nats streaming server server  github com hashicorp go msgpack codec  github com hashicorp go msgpack codec test  labix org   mgo bson    go mod vendor    find vendor  name bson                  what did you expect to see     at least some mention of the package  bson  anywhere in go mod s output         what did you see instead     zero mention of the package  bson  anywhere in go mod s output ,1
389906,26838745176.0,IssuesEvent,2023-02-02 21:55:34,golang/go,https://api.github.com/repos/golang/go,closed,x/website: doc/modules/managing-dependencies: markdown link is broken,Documentation NeedsFix website,"<!--
Please answer these questions before submitting your issue. Thanks!
-->
 
### What is the URL of the page with the issue?
 https://go.dev/doc/modules/managing-dependencies 
 
### What is your user agent?
 
Microsoft Edge
Version 96.0.1054.53 (Official build) (64-bit) 
 
### Screenshot
#### Broken Link
![image](https://user-images.githubusercontent.com/4377454/146906473-c972f697-55c4-40bd-b9a5-07e2113ba468.png)
 
 #### Duplicated sentences
![image](https://user-images.githubusercontent.com/4377454/146906627-9c8cb103-2996-4370-841d-6c918dd514b9.png)

### What did you do?
 
<!--
If possible, provide a recipe for reproducing the error.
-->
 
 
 
### What did you expect to see?
It's supposed to be a correct markdown link.
 
 
### What did you see instead?



",1.0,"x/website: doc/modules/managing-dependencies: markdown link is broken - <!--
Please answer these questions before submitting your issue. Thanks!
-->
 
### What is the URL of the page with the issue?
 https://go.dev/doc/modules/managing-dependencies 
 
### What is your user agent?
 
Microsoft Edge
Version 96.0.1054.53 (Official build) (64-bit) 
 
### Screenshot
#### Broken Link
![image](https://user-images.githubusercontent.com/4377454/146906473-c972f697-55c4-40bd-b9a5-07e2113ba468.png)
 
 #### Duplicated sentences
![image](https://user-images.githubusercontent.com/4377454/146906627-9c8cb103-2996-4370-841d-6c918dd514b9.png)

### What did you do?
 
<!--
If possible, provide a recipe for reproducing the error.
-->
 
 
 
### What did you expect to see?
It's supposed to be a correct markdown link.
 
 
### What did you see instead?



",1,x website  doc modules managing dependencies  markdown link is broken         please answer these questions before submitting your issue  thanks               what is the url of the page with the issue               what is your user agent      microsoft edge  version          official build     bit           screenshot       broken link                 duplicated sentences              what did you do            if possible  provide a recipe for reproducing the error                     what did you expect to see   it s supposed to be a correct markdown link             what did you see instead         ,1
636912,20612896148.0,IssuesEvent,2022-03-07 10:22:31,vmware/singleton,https://api.github.com/repos/vmware/singleton,opened,"[BUG] [Ruby Client]Can't return to fr translation when requesting locale is ""fr_CA"" in offline mode.",kind/bug priority/medium area/ruby-client,"**Describe the bug**
build: 'singleton-client', '~> 0.7.4'
Can't return to fr translation when requesting locale is ""fr_CA"" in offline mode.
It is reproducible in get component/string translation.

**To Reproduce**
Steps to reproduce the behavior:
1. Call the code as below: there is fr translation file and no fr_CA/fr-CA translation file in offlinebundle.
```
@Result = SgtnClient::Translation.getString(""JAVA"", ""helloworld"", ""fr_CA"")
puts ""@Result: #@Result""
@Result = SgtnClient::Translation.getString(""JAVA"", ""helloworld"", ""fr_FR"")
puts ""@Result: #@Result""
```
2. See output as below:
```
@Result: s_Hello world
@Result: s_Hello world
```

**Expected behavior**
Should get fr translation rather than source.

",1.0,"[BUG] [Ruby Client]Can't return to fr translation when requesting locale is ""fr_CA"" in offline mode. - **Describe the bug**
build: 'singleton-client', '~> 0.7.4'
Can't return to fr translation when requesting locale is ""fr_CA"" in offline mode.
It is reproducible in get component/string translation.

**To Reproduce**
Steps to reproduce the behavior:
1. Call the code as below: there is fr translation file and no fr_CA/fr-CA translation file in offlinebundle.
```
@Result = SgtnClient::Translation.getString(""JAVA"", ""helloworld"", ""fr_CA"")
puts ""@Result: #@Result""
@Result = SgtnClient::Translation.getString(""JAVA"", ""helloworld"", ""fr_FR"")
puts ""@Result: #@Result""
```
2. See output as below:
```
@Result: s_Hello world
@Result: s_Hello world
```

**Expected behavior**
Should get fr translation rather than source.

",0,   can t return to fr translation when requesting locale is  fr ca  in offline mode      describe the bug    build   singleton client               can t return to fr translation when requesting locale is  fr ca  in offline mode   it is reproducible in get component string translation       to reproduce    steps to reproduce the behavior      call the code as below  there is fr translation file and no fr ca fr ca translation file in offlinebundle         result   sgtnclient  translation getstring  java    helloworld    fr ca    puts   result    result    result   sgtnclient  translation getstring  java    helloworld    fr fr    puts   result    result           see output as below         result  s hello world   result  s hello world           expected behavior    should get fr translation rather than source     ,0
334914,10147255867.0,IssuesEvent,2019-08-05 10:06:01,ahmedkaludi/accelerated-mobile-pages,https://api.github.com/repos/ahmedkaludi/accelerated-mobile-pages,closed,"Lightbox effect not working with ""Tablepress"" when ""Link To"" option is selected in Attachment display settings",NEED FAST REVIEW [Priority: HIGH] bug," Helpscout Link: https://secure.helpscout.net/conversation/899646080/73277?folderId=2770545

Steps to recreate:

1. Install the Tablepress plugin and see the given video link:

https://monosnap.com/file/wdK9AZrBeFwf8JQv5eMlKIqMFh6vF1",1.0,"Lightbox effect not working with ""Tablepress"" when ""Link To"" option is selected in Attachment display settings -  Helpscout Link: https://secure.helpscout.net/conversation/899646080/73277?folderId=2770545

Steps to recreate:

1. Install the Tablepress plugin and see the given video link:

https://monosnap.com/file/wdK9AZrBeFwf8JQv5eMlKIqMFh6vF1",0,lightbox effect not working with  tablepress  when  link to  option is selected in attachment display settings    helpscout link       steps to recreate        install the tablepress plugin and see the given video link      ,0
75193,9212140076.0,IssuesEvent,2019-03-09 21:27:16,codeforgso/GoVote,https://api.github.com/repos/codeforgso/GoVote,closed,Create project wiki,beginner design semi-technical,"should include:
-MVP design and some proposed features
-build instructions
-Resources (PMs, Contributors, Community Stakeholders)
-Community Requirements
",1.0,"Create project wiki - should include:
-MVP design and some proposed features
-build instructions
-Resources (PMs, Contributors, Community Stakeholders)
-Community Requirements
",0,create project wiki   should include    mvp design and some proposed features   build instructions   resources  pms  contributors  community stakeholders    community requirements  ,0
150943,13386314344.0,IssuesEvent,2020-09-02 14:34:39,golang/go,https://api.github.com/repos/golang/go,closed,x/website: error and suggestion for tutorials pages,Documentation NeedsFix,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
1.15
</pre>

### Does this issue reproduce with the latest release?
yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env

GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/josh/.cache/go-build""
GOENV=""/home/josh/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/josh/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/josh/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/josh/projects/go/greetings/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build087138363=/tmp/go-build -gno-record-gcc-switches""

</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

I noticed two errors on the tutorial site:

1. https://golang.org/doc/tutorial/call-module-code - Step 3, the line should read:

fmt.Println(message) and not (greeting)

2. https://golang.org/doc/tutorial/handle-errors - Step 1, the ""nil"" being returned with ""message"" should probably be blue and bold to match the other new lines of code to be added.


### What did you expect to see?

1. message being printed instead of greeting
2. bolding of new code


### What did you see instead?

as reported above",1.0,"x/website: error and suggestion for tutorials pages - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
1.15
</pre>

### Does this issue reproduce with the latest release?
yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env

GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/josh/.cache/go-build""
GOENV=""/home/josh/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOINSECURE=""""
GOMODCACHE=""/home/josh/go/pkg/mod""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/josh/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""/home/josh/projects/go/greetings/go.mod""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build087138363=/tmp/go-build -gno-record-gcc-switches""

</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

I noticed two errors on the tutorial site:

1. https://golang.org/doc/tutorial/call-module-code - Step 3, the line should read:

fmt.Println(message) and not (greeting)

2. https://golang.org/doc/tutorial/handle-errors - Step 1, the ""nil"" being returned with ""message"" should probably be blue and bold to match the other new lines of code to be added.


### What did you expect to see?

1. message being printed instead of greeting
2. bolding of new code


### What did you see instead?

as reported above",1,x website  error and suggestion for tutorials pages         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version            go version                does this issue reproduce with the latest release   yes          what operating system and processor architecture are you using   go env          go env  output       go env          goarch      gobin     gocache   home josh  cache go build   goenv   home josh  config go env   goexe     goflags     gohostarch      gohostos  linux   goinsecure     gomodcache   home josh go pkg mod   gonoproxy     gonosumdb     goos  linux   gopath   home josh go   goprivate     goproxy     goroot   usr local go   gosumdb  sum golang org   gotmpdir     gotooldir   usr local go pkg tool linux     gccgo  gccgo   ar  ar   cc  gcc   cxx  g     cgo enabled      gomod   home josh projects go greetings go mod   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches               what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best          i noticed two errors on the tutorial site            step    the line should read     fmt println message  and not  greeting            step    the  nil  being returned with  message  should probably be blue and bold to match the other new lines of code to be added           what did you expect to see        message being printed instead of greeting     bolding of new code          what did you see instead     as reported above,1
222584,24709177726.0,IssuesEvent,2022-10-19 22:08:18,lukebrogan-mend/Umbraco-CMS,https://api.github.com/repos/lukebrogan-mend/Umbraco-CMS,closed,CVE-2020-28481 (Medium) detected in socket.io-2.1.1.tgz - autoclosed,security vulnerability,"## CVE-2020-28481 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>socket.io-2.1.1.tgz</b></p></summary>

<p>node.js realtime framework server</p>
<p>Library home page: <a href=""https://registry.npmjs.org/socket.io/-/socket.io-2.1.1.tgz"">https://registry.npmjs.org/socket.io/-/socket.io-2.1.1.tgz</a></p>
<p>Path to dependency file: /src/Umbraco.Web.UI.Client/package.json</p>
<p>Path to vulnerable library: /src/Umbraco.Web.UI.Client/node_modules/socket.io/package.json</p>
<p>

Dependency Hierarchy:
  - karma-4.4.1.tgz (Root Library)
    - :x: **socket.io-2.1.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/lukebroganws/Umbraco-CMS/commit/24bd18757bbbe3324d85424fdabf1d6bdaf1695e"">24bd18757bbbe3324d85424fdabf1d6bdaf1695e</a></p>
<p>Found in base branch: <b>v8/contrib</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>  
  
The package socket.io before 2.4.0 are vulnerable to Insecure Defaults due to CORS Misconfiguration. All domains are whitelisted by default.

<p>Publish Date: 2021-01-19
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28481>CVE-2020-28481</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>4.3</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: None
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28481"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28481</a></p>
<p>Release Date: 2021-01-19</p>
<p>Fix Resolution (socket.io): 2.4.0</p>
<p>Direct dependency fix Resolution (karma): 5.0.8</p>

</p>
</details>
<p></p>

***
:rescue_worker_helmet: Automatic Remediation is available for this issue",True,"CVE-2020-28481 (Medium) detected in socket.io-2.1.1.tgz - autoclosed - ## CVE-2020-28481 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>socket.io-2.1.1.tgz</b></p></summary>

<p>node.js realtime framework server</p>
<p>Library home page: <a href=""https://registry.npmjs.org/socket.io/-/socket.io-2.1.1.tgz"">https://registry.npmjs.org/socket.io/-/socket.io-2.1.1.tgz</a></p>
<p>Path to dependency file: /src/Umbraco.Web.UI.Client/package.json</p>
<p>Path to vulnerable library: /src/Umbraco.Web.UI.Client/node_modules/socket.io/package.json</p>
<p>

Dependency Hierarchy:
  - karma-4.4.1.tgz (Root Library)
    - :x: **socket.io-2.1.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/lukebroganws/Umbraco-CMS/commit/24bd18757bbbe3324d85424fdabf1d6bdaf1695e"">24bd18757bbbe3324d85424fdabf1d6bdaf1695e</a></p>
<p>Found in base branch: <b>v8/contrib</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>  
  
The package socket.io before 2.4.0 are vulnerable to Insecure Defaults due to CORS Misconfiguration. All domains are whitelisted by default.

<p>Publish Date: 2021-01-19
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28481>CVE-2020-28481</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>4.3</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: None
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28481"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28481</a></p>
<p>Release Date: 2021-01-19</p>
<p>Fix Resolution (socket.io): 2.4.0</p>
<p>Direct dependency fix Resolution (karma): 5.0.8</p>

</p>
</details>
<p></p>

***
:rescue_worker_helmet: Automatic Remediation is available for this issue",0,cve      medium  detected in socket io       tgz   autoclosed      cve       medium severity vulnerability     vulnerable library    socket io       tgz      node js realtime framework server   library home page   a href     path to dependency file   src umbraco web ui client package json   path to vulnerable library   src umbraco web ui client node modules socket io package json     dependency hierarchy      karma       tgz  root library         x    socket io       tgz    vulnerable library   found in head commit   a href     found in base branch     contrib              vulnerability details         the package socket io before       are vulnerable to insecure defaults due to cors misconfiguration  all domains are whitelisted by default    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  low     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  low     integrity impact  none     availability impact  none   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  socket io           direct dependency fix resolution  karma                        rescue worker helmet  automatic remediation is available for this issue,0
229501,17570820774.0,IssuesEvent,2021-08-14 16:56:44,golang/go,https://api.github.com/repos/golang/go,closed,sync/atomic: CompareAndSwapPointer should be CompareAndSwap,Documentation NeedsFix,"The comment states CompareAndSwapPointer but it should be name of the function, CompareAndSwap:
https://github.com/golang/go/blob/2422c5eae5dc6539b4b7657ef7bfe58a65acb61d/src/sync/atomic/value.go#L129-L134",1.0,"sync/atomic: CompareAndSwapPointer should be CompareAndSwap - The comment states CompareAndSwapPointer but it should be name of the function, CompareAndSwap:
https://github.com/golang/go/blob/2422c5eae5dc6539b4b7657ef7bfe58a65acb61d/src/sync/atomic/value.go#L129-L134",1,sync atomic  compareandswappointer should be compareandswap   the comment states compareandswappointer but it should be name of the function  compareandswap    ,1
62145,8577586029.0,IssuesEvent,2018-11-13 00:43:24,golang/go,https://api.github.com/repos/golang/go,closed,spec: documentation of len() in string type unclear,Documentation NeedsInvestigation,"https://github.com/golang/go/blob/f58b02a29c395b5ec28bb548b1fd3ca18e2b3a4f/doc/go_spec.html#L833

The documentation on how specifically `len()` can be used to determine the size of a string type in bytes can be confusing as this would make you expect that `len(""go"")` would return `16` (like `unsafe.Sizeof(""go"")` would) but actually gives you `2`

I would like to ask for a better phrasing of how to use `len()` on string type in the docs",1.0,"spec: documentation of len() in string type unclear - https://github.com/golang/go/blob/f58b02a29c395b5ec28bb548b1fd3ca18e2b3a4f/doc/go_spec.html#L833

The documentation on how specifically `len()` can be used to determine the size of a string type in bytes can be confusing as this would make you expect that `len(""go"")` would return `16` (like `unsafe.Sizeof(""go"")` would) but actually gives you `2`

I would like to ask for a better phrasing of how to use `len()` on string type in the docs",1,spec  documentation of len   in string type unclear        the documentation on how specifically  len    can be used to determine the size of a string type in bytes can be confusing as this would make you expect that  len  go    would return      like  unsafe sizeof  go    would  but actually gives you        i would like to ask for a better phrasing of how to use  len    on string type in the docs,1
54137,7875095915.0,IssuesEvent,2018-06-25 19:14:22,golang/go,https://api.github.com/repos/golang/go,closed,net/http: document and test behavior of ServeMux with ports,Documentation NeedsFix Testing help wanted,"Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
1.9.2 and 1.10beta1

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/knorton/Library/Caches/go-build""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/knorton/Documents/2018/01/underpants""
GORACE=""""
GOROOT=""/Users/knorton/Documents/2018/01/underpants/go1.10""
GOTMPDIR=""""
GOTOOLDIR=""/Users/knorton/Documents/2018/01/underpants/go1.10/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/9k/yc77pqm56jj79pp163xszgn00000gn/T/go-build934488457=/tmp/go-build -gno-record-gcc-switches -fno-common""
```

### What did you do?

Consider this Go program:

```
package main

import (
	""fmt""
	""log""
	""net/http""
)

func main() {
	m := http.NewServeMux()

	m.HandleFunc(""localhost:8080/"",
		func(w http.ResponseWriter, r *http.Request) {
			fmt.Fprintln(w, ""locahost:8080"")
		})

	log.Panic(http.ListenAndServe("":8080"", m))
}
```
If you use Go 1.8.5:
 1. `go run example.go`
 2. Visit http://localhost:8080/
 3. You will see the text ""localhost:8080"" display in the browser.

If you use Go 1.10beta1 and Go 1.9.2:
 1. `go run example.go`
 2. Visit http://localhost:8080/
 3. You will get a 404 NotFound.

### What did you expect to see?
I expect that compiling the example in 1.9.2 should behave as it did in 1.8.5.

More specifically, I would expect Go 1.9.2 to call the handler that I explicitly added for the host `localhost:8080`.

### What did you see instead?
Instead, this program called with Go 1.9.2 returns a 404 instead of calling the handler that I added for the host localhost:8080.

### More Details
This change seems to have been reviewed at: https://go-review.googlesource.com/c/go/+/38194

This change strips the port from the host only when it is trying to locate a handler. It does not strip the port when the user adds a handler for a host that includes a port number. As a result, trying to add handlers for hosts that include the port no longer works.

To make matters worse, these change makes it hard to write http code for hosts with ports that works on both Go 1.9 and Go <1.9.

In Go 1.9, the route has to be setup with `m.HandleFunc(""localhost"", ...)`
And in Go < 1.9, the route has to be setup with `m.HandleFunc(""localhost:8080"", ...)`.

To make the code work on all versions of Go, the handler function needs to be registered for both ""localhost"" and ""localhost:8080""

  
  ",1.0,"net/http: document and test behavior of ServeMux with ports - Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
1.9.2 and 1.10beta1

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/knorton/Library/Caches/go-build""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/knorton/Documents/2018/01/underpants""
GORACE=""""
GOROOT=""/Users/knorton/Documents/2018/01/underpants/go1.10""
GOTMPDIR=""""
GOTOOLDIR=""/Users/knorton/Documents/2018/01/underpants/go1.10/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/9k/yc77pqm56jj79pp163xszgn00000gn/T/go-build934488457=/tmp/go-build -gno-record-gcc-switches -fno-common""
```

### What did you do?

Consider this Go program:

```
package main

import (
	""fmt""
	""log""
	""net/http""
)

func main() {
	m := http.NewServeMux()

	m.HandleFunc(""localhost:8080/"",
		func(w http.ResponseWriter, r *http.Request) {
			fmt.Fprintln(w, ""locahost:8080"")
		})

	log.Panic(http.ListenAndServe("":8080"", m))
}
```
If you use Go 1.8.5:
 1. `go run example.go`
 2. Visit http://localhost:8080/
 3. You will see the text ""localhost:8080"" display in the browser.

If you use Go 1.10beta1 and Go 1.9.2:
 1. `go run example.go`
 2. Visit http://localhost:8080/
 3. You will get a 404 NotFound.

### What did you expect to see?
I expect that compiling the example in 1.9.2 should behave as it did in 1.8.5.

More specifically, I would expect Go 1.9.2 to call the handler that I explicitly added for the host `localhost:8080`.

### What did you see instead?
Instead, this program called with Go 1.9.2 returns a 404 instead of calling the handler that I added for the host localhost:8080.

### More Details
This change seems to have been reviewed at: https://go-review.googlesource.com/c/go/+/38194

This change strips the port from the host only when it is trying to locate a handler. It does not strip the port when the user adds a handler for a host that includes a port number. As a result, trying to add handlers for hosts that include the port no longer works.

To make matters worse, these change makes it hard to write http code for hosts with ports that works on both Go 1.9 and Go <1.9.

In Go 1.9, the route has to be setup with `m.HandleFunc(""localhost"", ...)`
And in Go < 1.9, the route has to be setup with `m.HandleFunc(""localhost:8080"", ...)`.

To make the code work on all versions of Go, the handler function needs to be registered for both ""localhost"" and ""localhost:8080""

  
  ",1,net http  document and test behavior of servemux with ports   please answer these questions before submitting your issue  thanks           what version of go are you using   go version           and            does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env          goarch      gobin     gocache   users knorton library caches go build   goexe     gohostarch      gohostos  darwin   goos  darwin   gopath   users knorton documents     underpants   gorace     goroot   users knorton documents     underpants       gotmpdir     gotooldir   users knorton documents     underpants     pkg tool darwin     gccgo  gccgo   cc  clang   cxx  clang     cgo enabled      cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders     t go    tmp go build  gno record gcc switches  fno common              what did you do     consider this go program          package main    import    	 fmt   	 log   	 net http        func main      	m    http newservemux      	m handlefunc  localhost       		func w http responsewriter  r  http request     			fmt fprintln w   locahost      		      	log panic http listenandserve       m            if you use go              go run example go       visit        you will see the text  localhost    display in the browser     if you use go     and go              go run example go       visit        you will get a   notfound         what did you expect to see   i expect that compiling the example in       should behave as it did in           more specifically  i would expect go       to call the handler that i explicitly added for the host  localhost            what did you see instead   instead  this program called with go       returns a   instead of calling the handler that i added for the host localhost           more details  this change seems to have been reviewed at       this change strips the port from the host only when it is trying to locate a handler  it does not strip the port when the user adds a handler for a host that includes a port number  as a result  trying to add handlers for hosts that include the port no longer works     to make matters worse  these change makes it hard to write http code for hosts with ports that works on both go     and go          in go      the route has to be setup with  m handlefunc  localhost          and in go        the route has to be setup with  m handlefunc  localhost               to make the code work on all versions of go  the handler function needs to be registered for both  localhost  and  localhost             ,1
247329,20972620897.0,IssuesEvent,2022-03-28 12:47:43,jvegax/Acme-Toolkits,https://api.github.com/repos/jvegax/Acme-Toolkits,opened,Task-067 : Test Operations by inventors on toolkits (Task-046),test🧪,"- [ ] test : list their own toolkits
- [ ] test : show their own toolkits and their information",1.0,"Task-067 : Test Operations by inventors on toolkits (Task-046) - - [ ] test : list their own toolkits
- [ ] test : show their own toolkits and their information",0,task     test operations by inventors on toolkits  task          test   list their own toolkits      test   show their own toolkits and their information,0
32483,4773152411.0,IssuesEvent,2016-10-26 23:15:36,dotnet/roslyn,https://api.github.com/repos/dotnet/roslyn,closed,Need additional tests for expression variables defined in a switch case expression,Area-Compilers New Language Feature - Out Variable Declaration New Language Feature - Pattern Matching Resolution-Fixed Test,"... including the behavior of SemanticModel.

Such tests would have caught https://github.com/dotnet/roslyn/issues/14717 earlier.",1.0,"Need additional tests for expression variables defined in a switch case expression - ... including the behavior of SemanticModel.

Such tests would have caught https://github.com/dotnet/roslyn/issues/14717 earlier.",0,need additional tests for expression variables defined in a switch case expression       including the behavior of semanticmodel     such tests would have caught   earlier ,0
223623,7459216683.0,IssuesEvent,2018-03-30 14:23:45,craftercms/craftercms,https://api.github.com/repos/craftercms/craftercms,opened,[engine] Dump cache stats API,enhancement priority: low,"Please create an API doc spec for a new API to dump cache statistics.
Please build the API once the doc is approved.",1.0,"[engine] Dump cache stats API - Please create an API doc spec for a new API to dump cache statistics.
Please build the API once the doc is approved.",0,  dump cache stats api   please create an api doc spec for a new api to dump cache statistics   please build the api once the doc is approved ,0
44714,7125828430.0,IssuesEvent,2018-01-20 01:58:53,golang/go,https://api.github.com/repos/golang/go,closed,doc: unclear if maps are ok for concurrent reads,Documentation,"It isn't specified anywhere in the docs if concurrent reads from a map (or any other type for that matter) are ok in Go. While this may be obvious to some, it would be good to put it somewhere.

Potential candidates:
https://golang.org/ref/mem
https://golang.org/doc/faq#atomic_maps

Some context:
https://groups.google.com/forum/m/#!topic/golang-nuts/3FVAs9dPR8k",1.0,"doc: unclear if maps are ok for concurrent reads - It isn't specified anywhere in the docs if concurrent reads from a map (or any other type for that matter) are ok in Go. While this may be obvious to some, it would be good to put it somewhere.

Potential candidates:
https://golang.org/ref/mem
https://golang.org/doc/faq#atomic_maps

Some context:
https://groups.google.com/forum/m/#!topic/golang-nuts/3FVAs9dPR8k",1,doc  unclear if maps are ok for concurrent reads   it isn t specified anywhere in the docs if concurrent reads from a map  or any other type for that matter  are ok in go  while this may be obvious to some  it would be good to put it somewhere     potential candidates           some context    ,1
12237,3059797592.0,IssuesEvent,2015-08-14 16:56:32,mozilla/thimble.webmaker.org,https://api.github.com/repos/mozilla/thimble.webmaker.org,closed,Visual Tweaks & Adjustments,design P2 UI,"Some adjustments to tighten up the UI:

* [ ] Make the file tray slide in and out instead of appear and disappear
* [ ] Adjust position of file tray toggle #630
* [ ] Remove (or increase the speed of the transition) on hover styles - app feels slow
* [ ] Reduce size of the undo & redo icons within their dark circles
* [ ] Add slight background color behind the phone on the mobile preview
* [ ] Add hover state to the file tray expand / collapse arrow
* [ ] Add hover state to the reload icon in the preview
* [ ] Center + and - button labels on the font size controls
* [ ] Center the thimble logo and project title so it looks better aligned
* [ ] Add additional padding on the project title hover state so it looks even
* [ ] Add cursor:pointer style to the dark / light theme toggle
* [ ] Resolve theme toggle styling
  * [ ] Icon color change effect
  * [ ] More consistent borders around toggle element
* [ ] Add tooltips to various controls (via title='blah') in case they're <a> elements",1.0,"Visual Tweaks & Adjustments - Some adjustments to tighten up the UI:

* [ ] Make the file tray slide in and out instead of appear and disappear
* [ ] Adjust position of file tray toggle #630
* [ ] Remove (or increase the speed of the transition) on hover styles - app feels slow
* [ ] Reduce size of the undo & redo icons within their dark circles
* [ ] Add slight background color behind the phone on the mobile preview
* [ ] Add hover state to the file tray expand / collapse arrow
* [ ] Add hover state to the reload icon in the preview
* [ ] Center + and - button labels on the font size controls
* [ ] Center the thimble logo and project title so it looks better aligned
* [ ] Add additional padding on the project title hover state so it looks even
* [ ] Add cursor:pointer style to the dark / light theme toggle
* [ ] Resolve theme toggle styling
  * [ ] Icon color change effect
  * [ ] More consistent borders around toggle element
* [ ] Add tooltips to various controls (via title='blah') in case they're <a> elements",0,visual tweaks   adjustments   some adjustments to tighten up the ui         make the file tray slide in and out instead of appear and disappear      adjust position of file tray toggle         remove  or increase the speed of the transition  on hover styles   app feels slow      reduce size of the undo   redo icons within their dark circles      add slight background color behind the phone on the mobile preview      add hover state to the file tray expand   collapse arrow      add hover state to the reload icon in the preview      center   and   button labels on the font size controls      center the thimble logo and project title so it looks better aligned      add additional padding on the project title hover state so it looks even      add cursor pointer style to the dark   light theme toggle      resolve theme toggle styling        icon color change effect        more consistent borders around toggle element      add tooltips to various controls  via title  blah   in case they re   elements,0
51672,13635178013.0,IssuesEvent,2020-09-25 02:07:32,nasifimtiazohi/openmrs-module-uicommons-2.12.0,https://api.github.com/repos/nasifimtiazohi/openmrs-module-uicommons-2.12.0,opened,"CVE-2019-3881 (High) detected in bundler-1.1.4.gem, bundlerv1.1.4",security vulnerability,"## CVE-2019-3881 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>bundler-1.1.4.gem</b>, <b>bundlerv1.1.4</b></p></summary>
<p>

<details><summary><b>bundler-1.1.4.gem</b></p></summary>

<p>Bundler manages an application's dependencies through its entire life, across many machines, systematically and repeatably</p>
<p>Library home page: <a href=""https://rubygems.org/gems/bundler-1.1.4.gem"">https://rubygems.org/gems/bundler-1.1.4.gem</a></p>
<p>Path to vulnerable library: ems/cache/bundler-1.1.4.gem</p>
<p>

Dependency Hierarchy:
  - :x: **bundler-1.1.4.gem** (Vulnerable Library)
</details>

<p>Found in HEAD commit: <a href=""https://github.com/nasifimtiazohi/openmrs-module-uicommons-2.12.0/commit/fead80bcaaf45fb296ae81ed441fcc7b7f67a341"">fead80bcaaf45fb296ae81ed441fcc7b7f67a341</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>  
  
Bundler prior to 2.1.0 uses a predictable path in /tmp/, created with insecure permissions as a storage location for gems, if locations under the user's home directory are not available. If Bundler is used in a scenario where the user does not have a writable home directory, an attacker could place malicious code in this directory that would be later loaded and executed.

<p>Publish Date: 2020-09-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-3881>CVE-2019-3881</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.0</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: High
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: 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=1651826"">https://bugzilla.redhat.com/show_bug.cgi?id=1651826</a></p>
<p>Release Date: 2020-07-21</p>
<p>Fix Resolution: v2.1.0.pre.3</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2019-3881 (High) detected in bundler-1.1.4.gem, bundlerv1.1.4 - ## CVE-2019-3881 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>bundler-1.1.4.gem</b>, <b>bundlerv1.1.4</b></p></summary>
<p>

<details><summary><b>bundler-1.1.4.gem</b></p></summary>

<p>Bundler manages an application's dependencies through its entire life, across many machines, systematically and repeatably</p>
<p>Library home page: <a href=""https://rubygems.org/gems/bundler-1.1.4.gem"">https://rubygems.org/gems/bundler-1.1.4.gem</a></p>
<p>Path to vulnerable library: ems/cache/bundler-1.1.4.gem</p>
<p>

Dependency Hierarchy:
  - :x: **bundler-1.1.4.gem** (Vulnerable Library)
</details>

<p>Found in HEAD commit: <a href=""https://github.com/nasifimtiazohi/openmrs-module-uicommons-2.12.0/commit/fead80bcaaf45fb296ae81ed441fcc7b7f67a341"">fead80bcaaf45fb296ae81ed441fcc7b7f67a341</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>  
  
Bundler prior to 2.1.0 uses a predictable path in /tmp/, created with insecure permissions as a storage location for gems, if locations under the user's home directory are not available. If Bundler is used in a scenario where the user does not have a writable home directory, an attacker could place malicious code in this directory that would be later loaded and executed.

<p>Publish Date: 2020-09-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-3881>CVE-2019-3881</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.0</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: High
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: 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=1651826"">https://bugzilla.redhat.com/show_bug.cgi?id=1651826</a></p>
<p>Release Date: 2020-07-21</p>
<p>Fix Resolution: v2.1.0.pre.3</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in bundler       gem             cve       high severity vulnerability     vulnerable libraries    bundler       gem                   bundler       gem      bundler manages an application s dependencies through its entire life  across many machines  systematically and repeatably   library home page   a href     path to vulnerable library  ems cache bundler       gem     dependency hierarchy       x    bundler       gem    vulnerable library      found in head commit   a href     found in base branch   master              vulnerability details         bundler prior to       uses a predictable path in  tmp   created with insecure permissions as a storage location for gems  if locations under the user s home directory are not available  if bundler is used in a scenario where the user does not have a writable home directory  an attacker could place malicious code in this directory that would be later loaded and executed    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  local     attack complexity  high     privileges required  low     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  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        pre                 step up your open source security game with whitesource    ,0
6435,3022485562.0,IssuesEvent,2015-07-31 20:39:03,golang/go,https://api.github.com/repos/golang/go,closed,spec: minor changes to examples,Documentation,"Three small suggestions for the examples in the Go Specification:

In the ```TimeZone``` type, the line
```
return fmt.Sprintf(""GMT+%dh"", tz)
```
returns something like ```GMT+-5h```. I think it would be better to change ```+%``` to ```%+```:
```
return fmt.Sprintf(""GMT%+dh"", tz)
```
so the result is ```GMT-5h```.

In ```findMarker```, if a return statement were added, the loop would only check every other item in the channel, because it uses both a for/range and a channel receive operation. The example would be less confusing with just one of those. For/range hasn't been introduced yet, so that's what I would remove.

In the Selectors section, the anonymous field ```T0``` of type ```T2``` is already a pointer. So the line
```
p.M0()       // ((&(*p).T0)).M0()   M0 expects *T0 receiver, see section on Calls
```
isn't an example of a shorthand reference to an addressable value. I think the comment should be:
```
p.M0()       // ((*p).T0).M0()   M0 expects *T0 receiver
```
A shorthand example could be added:
```
t.M2()      // (&t).M2()     M2 expects *T2 receiver, see section on Calls
```

These suggestions are current as of Go 1.5 beta 3.",1.0,"spec: minor changes to examples - Three small suggestions for the examples in the Go Specification:

In the ```TimeZone``` type, the line
```
return fmt.Sprintf(""GMT+%dh"", tz)
```
returns something like ```GMT+-5h```. I think it would be better to change ```+%``` to ```%+```:
```
return fmt.Sprintf(""GMT%+dh"", tz)
```
so the result is ```GMT-5h```.

In ```findMarker```, if a return statement were added, the loop would only check every other item in the channel, because it uses both a for/range and a channel receive operation. The example would be less confusing with just one of those. For/range hasn't been introduced yet, so that's what I would remove.

In the Selectors section, the anonymous field ```T0``` of type ```T2``` is already a pointer. So the line
```
p.M0()       // ((&(*p).T0)).M0()   M0 expects *T0 receiver, see section on Calls
```
isn't an example of a shorthand reference to an addressable value. I think the comment should be:
```
p.M0()       // ((*p).T0).M0()   M0 expects *T0 receiver
```
A shorthand example could be added:
```
t.M2()      // (&t).M2()     M2 expects *T2 receiver, see section on Calls
```

These suggestions are current as of Go 1.5 beta 3.",1,spec  minor changes to examples   three small suggestions for the examples in the go specification     in the    timezone    type  the line       return fmt sprintf  gmt  dh   tz        returns something like    gmt        i think it would be better to change          to                 return fmt sprintf  gmt  dh   tz        so the result is    gmt          in    findmarker     if a return statement were added  the loop would only check every other item in the channel  because it uses both a for range and a channel receive operation  the example would be less confusing with just one of those  for range hasn t been introduced yet  so that s what i would remove     in the selectors section  the anonymous field         of type         is already a pointer  so the line       p                   p              expects    receiver  see section on calls       isn t an example of a shorthand reference to an addressable value  i think the comment should be        p                 p             expects    receiver       a shorthand example could be added        t               t            expects    receiver  see section on calls         these suggestions are current as of go     beta   ,1
8053,3133635928.0,IssuesEvent,2015-09-10 03:34:36,golang/go,https://api.github.com/repos/golang/go,closed,hash: should document byte order of Hash.Sum,Documentation,"Using ```go1.5```

The hash/* libraries [output a slice with the hash in big endian byte order](https://play.golang.org/p/UxXsVEvNNG) when the Hash.Sum([]byte) method is called. This is fine, but it should be documented.

This does not apply to crypto hashes since those hashes are long enough (and don't fit in native integer types) that nobody mistakes the byte order.",1.0,"hash: should document byte order of Hash.Sum - Using ```go1.5```

The hash/* libraries [output a slice with the hash in big endian byte order](https://play.golang.org/p/UxXsVEvNNG) when the Hash.Sum([]byte) method is called. This is fine, but it should be documented.

This does not apply to crypto hashes since those hashes are long enough (and don't fit in native integer types) that nobody mistakes the byte order.",1,hash  should document byte order of hash sum   using              the hash   libraries     when the hash sum  byte  method is called  this is fine  but it should be documented     this does not apply to crypto hashes since those hashes are long enough  and don t fit in native integer types  that nobody mistakes the byte order ,1
426862,29667408152.0,IssuesEvent,2023-06-11 00:58:09,golang/go,https://api.github.com/repos/golang/go,reopened,math: Min()/Max() don't agree with builtin min()/max(),Documentation NeedsFix,"### What version of Go are you using (`go version`)?

<pre>
https://go.dev/play/?v=gotip
devel go1.21-05293d6b49 Mon Jun 5 14:01:09 2023 +0000
</pre>

### What did you do?

https://go.dev/play/p/Sf_G8Lt9dHy?v=gotip

```
	x := math.NaN()
	y := math.Inf(-1)

	fmt.Println(min(x, y))
	fmt.Println(math.Min(x, y))
```
Reports different output.

### What did you expect to see?

I expected all output to be `NaN`.

### What did you see instead?

`min()`/`max()` are returning `NaN` and `math.Min()`/`math.Max()` are returning `-Inf`/`+Inf`.

I think the output of the `math` versions is wrong as it should check for `NaN` before the infinities, but I don't have a copy of 754 right now and what min/max is under 754 is special (e.g. see minNum in IEEE 754-2008 vs. minimum & minimumNumber in IEEE 754-2019.",1.0,"math: Min()/Max() don't agree with builtin min()/max() - ### What version of Go are you using (`go version`)?

<pre>
https://go.dev/play/?v=gotip
devel go1.21-05293d6b49 Mon Jun 5 14:01:09 2023 +0000
</pre>

### What did you do?

https://go.dev/play/p/Sf_G8Lt9dHy?v=gotip

```
	x := math.NaN()
	y := math.Inf(-1)

	fmt.Println(min(x, y))
	fmt.Println(math.Min(x, y))
```
Reports different output.

### What did you expect to see?

I expected all output to be `NaN`.

### What did you see instead?

`min()`/`max()` are returning `NaN` and `math.Min()`/`math.Max()` are returning `-Inf`/`+Inf`.

I think the output of the `math` versions is wrong as it should check for `NaN` before the infinities, but I don't have a copy of 754 right now and what min/max is under 754 is special (e.g. see minNum in IEEE 754-2008 vs. minimum & minimumNumber in IEEE 754-2019.",1,math  min   max   don t agree with builtin min   max         what version of go are you using   go version             devel       mon jun                        what did you do               	x    math nan    	y    math inf        	fmt println min x  y    	fmt println math min x  y         reports different output         what did you expect to see     i expected all output to be  nan          what did you see instead      min     max    are returning  nan  and  math min     math max    are returning   inf    inf      i think the output of the  math  versions is wrong as it should check for  nan  before the infinities  but i don t have a copy of   right now and what min max is under   is special  e g  see minnum in ieee     vs  minimum   minimumnumber in ieee     ,1
35089,6412119574.0,IssuesEvent,2017-08-08 01:48:27,golang/go,https://api.github.com/repos/golang/go,closed,flag: global Usage func disregards FlagSet.SetOutput,Documentation NeedsDecision,"### What version of Go are you using (`go version`)?
```
go version go1.8.2 darwin/amd64
```

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/vpoturaev/golang""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.8.2/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.8.2/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/p5/fnl90gfx5_5f9599s3hpthfw0000gq/T/go-build760766867=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
PKG_CONFIG=""pkg-config""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
```

### What did you do?
```go
package main

import (
	""flag""
	""io/ioutil""
	""os""
)

func main() {
	var i int
	flag.IntVar(&i, ""i"", 2, ""sample int"")
	flag.CommandLine.SetOutput(ioutil.Discard)
	os.Args = []string{""app"", ""-i=1"", ""-unknown""}
	flag.Parse()
}
```
https://play.golang.org/p/05pwqQu-3-
### What did you expect to see?

No output

### What did you see instead?

STDERR:
```
Usage of app:
```

`/usr/local/Cellar/go/1.8.2/libexec/src/flag/flag.go`
```go
var Usage = func() {
	fmt.Fprintf(os.Stderr, ""Usage of %s:\n"", os.Args[0])
	PrintDefaults()
}
```
`Usage` function disregards `f.Out()` in favour of `os.Stderr`.

The correct code should be:
```go
var Usage = func() {
	fmt.Fprintf(f.out(), ""Usage of %s:\n"", os.Args[0])
	PrintDefaults()
}
```",1.0,"flag: global Usage func disregards FlagSet.SetOutput - ### What version of Go are you using (`go version`)?
```
go version go1.8.2 darwin/amd64
```

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/vpoturaev/golang""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.8.2/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.8.2/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/p5/fnl90gfx5_5f9599s3hpthfw0000gq/T/go-build760766867=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
PKG_CONFIG=""pkg-config""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
```

### What did you do?
```go
package main

import (
	""flag""
	""io/ioutil""
	""os""
)

func main() {
	var i int
	flag.IntVar(&i, ""i"", 2, ""sample int"")
	flag.CommandLine.SetOutput(ioutil.Discard)
	os.Args = []string{""app"", ""-i=1"", ""-unknown""}
	flag.Parse()
}
```
https://play.golang.org/p/05pwqQu-3-
### What did you expect to see?

No output

### What did you see instead?

STDERR:
```
Usage of app:
```

`/usr/local/Cellar/go/1.8.2/libexec/src/flag/flag.go`
```go
var Usage = func() {
	fmt.Fprintf(os.Stderr, ""Usage of %s:\n"", os.Args[0])
	PrintDefaults()
}
```
`Usage` function disregards `f.Out()` in favour of `os.Stderr`.

The correct code should be:
```go
var Usage = func() {
	fmt.Fprintf(f.out(), ""Usage of %s:\n"", os.Args[0])
	PrintDefaults()
}
```",1,flag  global usage func disregards flagset setoutput       what version of go are you using   go version          go version       darwin               what operating system and processor architecture are you using   go env          goarch      gobin     goexe     gohostarch      gohostos  darwin   goos  darwin   gopath   users vpoturaev golang   gorace     goroot   usr local cellar go       libexec   gotooldir   usr local cellar go       libexec pkg tool darwin     gccgo  gccgo   cc  clang   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders       t go    tmp go build  gno record gcc switches  fno common   cxx  clang     cgo enabled      pkg config  pkg config   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g                 what did you do      go  package main    import    	 flag   	 io ioutil   	 os        func main      	var i int  	flag intvar  i   i       sample int    	flag commandline setoutput ioutil discard   	os args    string  app     i       unknown    	flag parse                   what did you expect to see     no output        what did you see instead     stderr        usage of app            usr local cellar go       libexec src flag flag go      go  var usage   func      	fmt fprintf os stderr   usage of  s  n   os args    	printdefaults             usage  function disregards  f out    in favour of  os stderr      the correct code should be      go  var usage   func      	fmt fprintf f out     usage of  s  n   os args    	printdefaults          ,1
7434,6960388361.0,IssuesEvent,2017-12-08 03:08:48,eslint/eslint,https://api.github.com/repos/eslint/eslint,closed,"Should we rename ""beginner"" label to ""good first issue""?",accepted infrastructure,"**TSC Summary**:

Per [this article](https://help.github.com/articles/helping-new-contributors-find-your-project-with-labels/) on GitHub Help, it seems that GitHub is flagging issues with the ""help wanted"" or ""good first issue"" label for new contributors.

We're already using ""help wanted"", and ""beginner"" seems semantically equivalent. So I'd like to propose changing the label from ""beginner"" to ""good first issue"" to take advantage. (Also, as a small side benefit, it avoids any risk that the ""beginner"" label could seem pejorative to someone who has experience coding but has not contributed to this repository before.)

**TSC Question**:

Should we do this for the ESLint repo? Should we do this for other repos in the ESLint organization?",1.0,"Should we rename ""beginner"" label to ""good first issue""? - **TSC Summary**:

Per [this article](https://help.github.com/articles/helping-new-contributors-find-your-project-with-labels/) on GitHub Help, it seems that GitHub is flagging issues with the ""help wanted"" or ""good first issue"" label for new contributors.

We're already using ""help wanted"", and ""beginner"" seems semantically equivalent. So I'd like to propose changing the label from ""beginner"" to ""good first issue"" to take advantage. (Also, as a small side benefit, it avoids any risk that the ""beginner"" label could seem pejorative to someone who has experience coding but has not contributed to this repository before.)

**TSC Question**:

Should we do this for the ESLint repo? Should we do this for other repos in the ESLint organization?",0,should we rename  beginner  label to  good first issue       tsc summary       per     on github help  it seems that github is flagging issues with the  help wanted  or  good first issue  label for new contributors     we re already using  help wanted   and  beginner  seems semantically equivalent  so i d like to propose changing the label from  beginner  to  good first issue  to take advantage   also  as a small side benefit  it avoids any risk that the  beginner  label could seem pejorative to someone who has experience coding but has not contributed to this repository before        tsc question       should we do this for the eslint repo  should we do this for other repos in the eslint organization ,0
21770,4745725236.0,IssuesEvent,2016-10-21 08:31:44,golang/go,https://api.github.com/repos/golang/go,closed,database/sql: sql argument counts are off by one when reporting an error,Documentation NeedsFix,"I know this is pretty trivial, but when reporting an error the sql package seems to report arguments by counting them starting at zero.

Since SQL arguments are generally numbered from 1 -- and indeed, for PostgreSQL they are numbered $1, $2, $3... in the SQL itself -- this confused me.

e.g. sql: converting Exec argument #3's type: unsupported type main.Date, a struct
It was actually argument #4 ($4 in the SQL statement).

go version go1.6.2 linux/amd64

GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/meta/go/tecdocs""
GORACE=""""
GOROOT=""/usr/local/go""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_amd64""
GO15VENDOREXPERIMENT=""1""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0""
CXX=""g++""
CGO_ENABLED=""1""
",1.0,"database/sql: sql argument counts are off by one when reporting an error - I know this is pretty trivial, but when reporting an error the sql package seems to report arguments by counting them starting at zero.

Since SQL arguments are generally numbered from 1 -- and indeed, for PostgreSQL they are numbered $1, $2, $3... in the SQL itself -- this confused me.

e.g. sql: converting Exec argument #3's type: unsupported type main.Date, a struct
It was actually argument #4 ($4 in the SQL statement).

go version go1.6.2 linux/amd64

GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/home/meta/go/tecdocs""
GORACE=""""
GOROOT=""/usr/local/go""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_amd64""
GO15VENDOREXPERIMENT=""1""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0""
CXX=""g++""
CGO_ENABLED=""1""
",1,database sql  sql argument counts are off by one when reporting an error   i know this is pretty trivial  but when reporting an error the sql package seems to report arguments by counting them starting at zero     since sql arguments are generally numbered from      and indeed  for postgresql they are numbered               in the sql itself    this confused me     e g  sql  converting exec argument    s type  unsupported type main date  a struct  it was actually argument        in the sql statement      go version       linux      goarch      gobin     goexe     gohostarch      gohostos  linux   goos  linux   gopath   home meta go tecdocs   gorace     goroot   usr local go   gotooldir   usr local go pkg tool linux            cc  gcc   gogccflags   fpic     pthread  fmessage length     cxx  g     cgo enabled      ,1
61738,8554322590.0,IssuesEvent,2018-11-08 05:42:37,golang/go,https://api.github.com/repos/golang/go,closed,time: document that a marshaled time does not include location name,Documentation Proposal Proposal-Accepted help wanted,"As is, `time.Time` is not transmittable/storable on its own where it will preserve its location. All of the Marshal/Unmarshal implementations and all the supported string formats encode only the offset or the timezone abbreviation. When parsed or unmarshalled, you often end up with a `time.Time` in a fixed offset, rather than the original location. In particular, this can lead to unexpected results when performing some operations around Daylight Savings Time because the fixed offset `time.Time` may or may not observe DST when the original location-laden `time.Time` would have. Depending on the server location, it's also possible to end up applying DST when it shouldn't apply because of `time.Parse`'s behavior to use `time.Local` if the local offset matches the parsed timestamp.

As a hallmark example of the problem here is to ask: what month will it be if you add 2840 hours to the reference time used for string formatting? See: https://play.golang.org/p/XQiDRKpKtSa

Overall, this subtlety breaks assumptions that encoded timestamps convey all the information on the original `time.Time`, and that a decoded `time.Time` will behave consistently no matter where it's decoded. While a workaround is possible by always separately storing/transmitting the location string in addition to the timestamp, the time package could make that more transparent or at least alert users that the encode/decode may behave unexpectedly with regard to precise timezone rules. 

The proposal is to do one or more of the following options. Note that as the author here, my current thinking is option 2 plus option 5 would be the best way forward, but I've listed more possibilities for completeness.

1. Add the IANA location to what `MarshalBinary` and `UnmarshalBinary` do

This will allow `gob` to losslessly transmit timestamps that will behave the same after encoding/decoding. There are a couple considerations that may rule out this idea:

- The change might be backward incompatible. I'm not sure if there are Go programs relying on the fact that currently the encoding format results in fixed-offset times after decode.
- The ""improved"" parser would still need to handle encoded data from before the change
- The IANA information might not be useful on systems that don't have tzdata (noting #21881)


2. Add a Format/Parse directive that includes the IANA location string

This idea is less transparent than the Binary/Gob approach because it requires specifically using a format that includes location. This means it's backward compatible and introduces minimal additional API surface. This possibility still must tackle the problem of how to proceed on systems without available tzdata.

3. Add an exported struct field to `time.Time` to toggle encoding behavior

Because the current JSON/text encoding mechanisms for `time.Time` specify RFC3339, they cannot be changed outright to include the actual location. However, a field could be added to time.Time to alter the encoding behavior. Because the default state of this field could be to encode as the existing format, backward compatibility would be preserved. The decoding routines would need to account for all possible formats and could set that field as necessary. 

The two major downsides to this approach I can think of:

- Additional memory required by `time.Time` objects
- That `==` comparisons would include this field, which seems beyond its intended purpose 

4. Break compatibility in Go2 and include the IANA location in all `Marshal`/`Unmarshal` encodings

The big benefit here would be to make `time.Time`, as an implementation of package `encoding`'s interfaces, to be more true to those interfaces. While package `encoding` doesn't currently specify whether or not implementations must _completely_ represent the receiver's contents, one might assume they do since generally the process is often treated such that `x = decode(encode(x))`. 

5. Document this behavior

It's worth warning people that existing encoding methods do not preserve the full location information and that if the program needs to do calendrical operations which may be affected by changes like DST, to transmit/store both the encoded `time.Time` and its location separately. In particular, since the docs don't specify any format or specifics about the data, one might assume the binary/Gob encoding preserves the full state of the `time.Time`, when it actually doesn't. While technically this fact is implied for the JSON/text encodings, it's probably a common misconception that the offset in RFC3339 adequately represents location via the offset.

edit: added some formatting",1.0,"time: document that a marshaled time does not include location name - As is, `time.Time` is not transmittable/storable on its own where it will preserve its location. All of the Marshal/Unmarshal implementations and all the supported string formats encode only the offset or the timezone abbreviation. When parsed or unmarshalled, you often end up with a `time.Time` in a fixed offset, rather than the original location. In particular, this can lead to unexpected results when performing some operations around Daylight Savings Time because the fixed offset `time.Time` may or may not observe DST when the original location-laden `time.Time` would have. Depending on the server location, it's also possible to end up applying DST when it shouldn't apply because of `time.Parse`'s behavior to use `time.Local` if the local offset matches the parsed timestamp.

As a hallmark example of the problem here is to ask: what month will it be if you add 2840 hours to the reference time used for string formatting? See: https://play.golang.org/p/XQiDRKpKtSa

Overall, this subtlety breaks assumptions that encoded timestamps convey all the information on the original `time.Time`, and that a decoded `time.Time` will behave consistently no matter where it's decoded. While a workaround is possible by always separately storing/transmitting the location string in addition to the timestamp, the time package could make that more transparent or at least alert users that the encode/decode may behave unexpectedly with regard to precise timezone rules. 

The proposal is to do one or more of the following options. Note that as the author here, my current thinking is option 2 plus option 5 would be the best way forward, but I've listed more possibilities for completeness.

1. Add the IANA location to what `MarshalBinary` and `UnmarshalBinary` do

This will allow `gob` to losslessly transmit timestamps that will behave the same after encoding/decoding. There are a couple considerations that may rule out this idea:

- The change might be backward incompatible. I'm not sure if there are Go programs relying on the fact that currently the encoding format results in fixed-offset times after decode.
- The ""improved"" parser would still need to handle encoded data from before the change
- The IANA information might not be useful on systems that don't have tzdata (noting #21881)


2. Add a Format/Parse directive that includes the IANA location string

This idea is less transparent than the Binary/Gob approach because it requires specifically using a format that includes location. This means it's backward compatible and introduces minimal additional API surface. This possibility still must tackle the problem of how to proceed on systems without available tzdata.

3. Add an exported struct field to `time.Time` to toggle encoding behavior

Because the current JSON/text encoding mechanisms for `time.Time` specify RFC3339, they cannot be changed outright to include the actual location. However, a field could be added to time.Time to alter the encoding behavior. Because the default state of this field could be to encode as the existing format, backward compatibility would be preserved. The decoding routines would need to account for all possible formats and could set that field as necessary. 

The two major downsides to this approach I can think of:

- Additional memory required by `time.Time` objects
- That `==` comparisons would include this field, which seems beyond its intended purpose 

4. Break compatibility in Go2 and include the IANA location in all `Marshal`/`Unmarshal` encodings

The big benefit here would be to make `time.Time`, as an implementation of package `encoding`'s interfaces, to be more true to those interfaces. While package `encoding` doesn't currently specify whether or not implementations must _completely_ represent the receiver's contents, one might assume they do since generally the process is often treated such that `x = decode(encode(x))`. 

5. Document this behavior

It's worth warning people that existing encoding methods do not preserve the full location information and that if the program needs to do calendrical operations which may be affected by changes like DST, to transmit/store both the encoded `time.Time` and its location separately. In particular, since the docs don't specify any format or specifics about the data, one might assume the binary/Gob encoding preserves the full state of the `time.Time`, when it actually doesn't. While technically this fact is implied for the JSON/text encodings, it's probably a common misconception that the offset in RFC3339 adequately represents location via the offset.

edit: added some formatting",1,time  document that a marshaled time does not include location name   as is   time time  is not transmittable storable on its own where it will preserve its location  all of the marshal unmarshal implementations and all the supported string formats encode only the offset or the timezone abbreviation  when parsed or unmarshalled  you often end up with a  time time  in a fixed offset  rather than the original location  in particular  this can lead to unexpected results when performing some operations around daylight savings time because the fixed offset  time time  may or may not observe dst when the original location laden  time time  would have  depending on the server location  it s also possible to end up applying dst when it shouldn t apply because of  time parse  s behavior to use  time local  if the local offset matches the parsed timestamp     as a hallmark example of the problem here is to ask  what month will it be if you add   hours to the reference time used for string formatting  see       overall  this subtlety breaks assumptions that encoded timestamps convey all the information on the original  time time   and that a decoded  time time  will behave consistently no matter where it s decoded  while a workaround is possible by always separately storing transmitting the location string in addition to the timestamp  the time package could make that more transparent or at least alert users that the encode decode may behave unexpectedly with regard to precise timezone rules      the proposal is to do one or more of the following options  note that as the author here  my current thinking is option   plus option   would be the best way forward  but i ve listed more possibilities for completeness        add the iana location to what  marshalbinary  and  unmarshalbinary  do    this will allow  gob  to losslessly transmit timestamps that will behave the same after encoding decoding  there are a couple considerations that may rule out this idea       the change might be backward incompatible  i m not sure if there are go programs relying on the fact that currently the encoding format results in fixed offset times after decode     the  improved  parser would still need to handle encoded data from before the change    the iana information might not be useful on systems that don t have tzdata  noting             add a format parse directive that includes the iana location string    this idea is less transparent than the binary gob approach because it requires specifically using a format that includes location  this means it s backward compatible and introduces minimal additional api surface  this possibility still must tackle the problem of how to proceed on systems without available tzdata        add an exported struct field to  time time  to toggle encoding behavior    because the current json text encoding mechanisms for  time time  specify    they cannot be changed outright to include the actual location  however  a field could be added to time time to alter the encoding behavior  because the default state of this field could be to encode as the existing format  backward compatibility would be preserved  the decoding routines would need to account for all possible formats and could set that field as necessary      the two major downsides to this approach i can think of       additional memory required by  time time  objects    that      comparisons would include this field  which seems beyond its intended purpose        break compatibility in   and include the iana location in all  marshal   unmarshal  encodings    the big benefit here would be to make  time time   as an implementation of package  encoding  s interfaces  to be more true to those interfaces  while package  encoding  doesn t currently specify whether or not implementations must  completely  represent the receiver s contents  one might assume they do since generally the process is often treated such that  x   decode encode x            document this behavior    it s worth warning people that existing encoding methods do not preserve the full location information and that if the program needs to do calendrical operations which may be affected by changes like dst  to transmit store both the encoded  time time  and its location separately  in particular  since the docs don t specify any format or specifics about the data  one might assume the binary gob encoding preserves the full state of the  time time   when it actually doesn t  while technically this fact is implied for the json text encodings  it s probably a common misconception that the offset in   adequately represents location via the offset     edit  added some formatting,1
92390,10742227488.0,IssuesEvent,2019-10-29 22:01:08,golang/go,https://api.github.com/repos/golang/go,closed,go/types: some small problems in docs,Documentation ExpertNeeded NeedsFix,"In the docs of the [selections](https://golang.org/pkg/go/types/#Selection):
```
Selector    Kind          Recv    Obj    Type               Index     Indirect

p.x         FieldVal      T       x      int                {0}       true
p.m         MethodVal     *T      m      func (e *T) m()    {1, 0}    true
T.m         MethodExpr    T       m      func m(_ T)        {1, 0}    fals
```
Should the `Type` columns for the second and third line be `func()` and `func(_ T)`?
",1.0,"go/types: some small problems in docs - In the docs of the [selections](https://golang.org/pkg/go/types/#Selection):
```
Selector    Kind          Recv    Obj    Type               Index     Indirect

p.x         FieldVal      T       x      int                {0}       true
p.m         MethodVal     *T      m      func (e *T) m()    {1, 0}    true
T.m         MethodExpr    T       m      func m(_ T)        {1, 0}    fals
```
Should the `Type` columns for the second and third line be `func()` and `func(_ T)`?
",1,go types  some small problems in docs   in the docs of the           selector    kind          recv    obj    type               index     indirect    p x         fieldval      t       x      int                          true  p m         methodval      t      m      func  e  t  m                true  t m         methodexpr    t       m      func m   t                   fals       should the  type  columns for the second and third line be  func    and  func   t     ,1
166054,20711387363.0,IssuesEvent,2022-03-12 01:15:43,snowflakedb/snowflake-jdbc,https://api.github.com/repos/snowflakedb/snowflake-jdbc,closed,SNOW-558853: CVE-2020-36180 (High) detected in jackson-databind-2.9.8.jar - autoclosed,security vulnerability,"## CVE-2020-36180 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.8.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: /tmp/ws-ua_20220312003410_KQQKCS/archiveExtraction_BELGGC/FUIDAN/20220312003410/snowflake-jdbc_depth_0/dependencies/arrow-vector-0.15.1/META-INF/maven/org.apache.arrow/arrow-vector/pom.xml</p>
<p>Path to vulnerable library: /sitory/com/fasterxml/jackson/core/jackson-databind/2.9.8/jackson-databind-2.9.8.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.9.8.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/snowflakedb/snowflake-jdbc/commit/8560bcca9d395d1ee02123536c2e958f7d386fe0"">8560bcca9d395d1ee02123536c2e958f7d386fe0</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>  
  
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.dbcp2.cpdsadapter.DriverAdapterCPDS.

<p>Publish Date: 2021-01-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36180>CVE-2020-36180</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>8.1</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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/FasterXML/jackson-databind/issues/3004"">https://github.com/FasterXML/jackson-databind/issues/3004</a></p>
<p>Release Date: 2021-01-07</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.9.10.8</p>

</p>
</details>
<p></p>

***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""com.fasterxml.jackson.core"",""packageName"":""jackson-databind"",""packageVersion"":""2.9.8"",""packageFilePaths"":[""/tmp/ws-ua_20220312003410_KQQKCS/archiveExtraction_BELGGC/FUIDAN/20220312003410/snowflake-jdbc_depth_0/dependencies/arrow-vector-0.15.1/META-INF/maven/org.apache.arrow/arrow-vector/pom.xml""],""isTransitiveDependency"":false,""dependencyTree"":""com.fasterxml.jackson.core:jackson-databind:2.9.8"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""com.fasterxml.jackson.core:jackson-databind:2.9.10.8"",""isBinary"":false}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""CVE-2020-36180"",""vulnerabilityDetails"":""FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.dbcp2.cpdsadapter.DriverAdapterCPDS."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36180"",""cvss3Severity"":""high"",""cvss3Score"":""8.1"",""cvss3Metrics"":{""A"":""High"",""AC"":""High"",""PR"":""None"",""S"":""Unchanged"",""C"":""High"",""UI"":""None"",""AV"":""Network"",""I"":""High""},""extraData"":{}}</REMEDIATE> -->",True,"SNOW-558853: CVE-2020-36180 (High) detected in jackson-databind-2.9.8.jar - autoclosed - ## CVE-2020-36180 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.8.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: /tmp/ws-ua_20220312003410_KQQKCS/archiveExtraction_BELGGC/FUIDAN/20220312003410/snowflake-jdbc_depth_0/dependencies/arrow-vector-0.15.1/META-INF/maven/org.apache.arrow/arrow-vector/pom.xml</p>
<p>Path to vulnerable library: /sitory/com/fasterxml/jackson/core/jackson-databind/2.9.8/jackson-databind-2.9.8.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.9.8.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/snowflakedb/snowflake-jdbc/commit/8560bcca9d395d1ee02123536c2e958f7d386fe0"">8560bcca9d395d1ee02123536c2e958f7d386fe0</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>  
  
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.dbcp2.cpdsadapter.DriverAdapterCPDS.

<p>Publish Date: 2021-01-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36180>CVE-2020-36180</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>8.1</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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/FasterXML/jackson-databind/issues/3004"">https://github.com/FasterXML/jackson-databind/issues/3004</a></p>
<p>Release Date: 2021-01-07</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.9.10.8</p>

</p>
</details>
<p></p>

***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""com.fasterxml.jackson.core"",""packageName"":""jackson-databind"",""packageVersion"":""2.9.8"",""packageFilePaths"":[""/tmp/ws-ua_20220312003410_KQQKCS/archiveExtraction_BELGGC/FUIDAN/20220312003410/snowflake-jdbc_depth_0/dependencies/arrow-vector-0.15.1/META-INF/maven/org.apache.arrow/arrow-vector/pom.xml""],""isTransitiveDependency"":false,""dependencyTree"":""com.fasterxml.jackson.core:jackson-databind:2.9.8"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""com.fasterxml.jackson.core:jackson-databind:2.9.10.8"",""isBinary"":false}],""baseBranches"":[""master""],""vulnerabilityIdentifier"":""CVE-2020-36180"",""vulnerabilityDetails"":""FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.dbcp2.cpdsadapter.DriverAdapterCPDS."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36180"",""cvss3Severity"":""high"",""cvss3Score"":""8.1"",""cvss3Metrics"":{""A"":""High"",""AC"":""High"",""PR"":""None"",""S"":""Unchanged"",""C"":""High"",""UI"":""None"",""AV"":""Network"",""I"":""High""},""extraData"":{}}</REMEDIATE> -->",0,snow    cve      high  detected in jackson databind       jar   autoclosed      cve       high severity vulnerability     vulnerable library    jackson databind       jar      general data binding functionality for jackson  works on core streaming api   library home page   a href     path to dependency file   tmp ws ua   kqqkcs archiveextraction belggc fuidan   snowflake jdbc depth   dependencies arrow vector       meta inf maven org apache arrow arrow vector pom xml   path to vulnerable library   sitory 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 commons   cpdsadapter driveradaptercpds    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  com fasterxml jackson core jackson databind                        rescue worker helmet  automatic remediation is available for this issue    isopenpronvulnerability  true  ispackagebased  true  isdefaultbranch  true  packages     istransitivedependency  false  dependencytree   com fasterxml jackson core jackson databind         isminimumfixversionavailable  true  minimumfixversion   com fasterxml jackson core jackson databind           isbinary  false    basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   fasterxml jackson databind   x before         mishandles the interaction between serialization gadgets and typing  related to org apache commons   cpdsadapter driveradaptercpds    vulnerabilityurl        ,0
419701,12227183137.0,IssuesEvent,2020-05-03 14:15:30,wevote/WeVoteServer,https://api.github.com/repos/wevote/WeVoteServer,opened,Import Polling Locations from Spreadsheet,Difficulty: Medium Priority 1,"We are able to import a variety of data, like Measures and Candidates. Please extend this system to import polling locations from an uploaded CSV.

This is a related page in the admin interface: https://api.wevoteusa.org/import_export_batches/batch_list/?kind_of_batch=MEASURE&google_civic_election_id=0&state_code=",1.0,"Import Polling Locations from Spreadsheet - We are able to import a variety of data, like Measures and Candidates. Please extend this system to import polling locations from an uploaded CSV.

This is a related page in the admin interface: https://api.wevoteusa.org/import_export_batches/batch_list/?kind_of_batch=MEASURE&google_civic_election_id=0&state_code=",0,import polling locations from spreadsheet   we are able to import a variety of data  like measures and candidates  please extend this system to import polling locations from an uploaded csv     this is a related page in the admin interface   ,0
441425,12717669522.0,IssuesEvent,2020-06-24 05:50:03,webcompat/web-bugs,https://api.github.com/repos/webcompat/web-bugs,closed,4pda.ru - see bug description,browser-firefox engine-gecko ml-needsdiagnosis-false ml-probability-high priority-normal,"<!-- @browser: Firefox 78.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0 -->
<!-- @reported_with: desktop-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/54507 -->

**URL**: https://4pda.ru/

**Browser / Version**: Firefox 78.0
**Operating System**: Windows 10
**Tested Another Browser**: Yes Chrome

**Problem type**: Something else
**Description**: Instead of site content, html code is displayed.
**Steps to Reproduce**:
I just went to the site and saw this.
<details>
      <summary>View the screenshot</summary>
      <img alt=""Screenshot"" src=""https://webcompat.com/uploads/2020/6/0d70dd59-3671-4ae1-bc43-06541e648e15.jpeg"">
      </details>

<details>
<summary>Browser Configuration</summary>
<ul>
  <li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20200619002543</li><li>channel: beta</li><li>hasTouchScreen: false</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>

[View console log messages](https://webcompat.com/console_logs/2020/6/598955a8-f3b9-4d8a-af58-fe8cad822f05)

_From [webcompat.com](https://webcompat.com/) with ❤️_",1.0,"4pda.ru - see bug description - <!-- @browser: Firefox 78.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0 -->
<!-- @reported_with: desktop-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/54507 -->

**URL**: https://4pda.ru/

**Browser / Version**: Firefox 78.0
**Operating System**: Windows 10
**Tested Another Browser**: Yes Chrome

**Problem type**: Something else
**Description**: Instead of site content, html code is displayed.
**Steps to Reproduce**:
I just went to the site and saw this.
<details>
      <summary>View the screenshot</summary>
      <img alt=""Screenshot"" src=""https://webcompat.com/uploads/2020/6/0d70dd59-3671-4ae1-bc43-06541e648e15.jpeg"">
      </details>

<details>
<summary>Browser Configuration</summary>
<ul>
  <li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20200619002543</li><li>channel: beta</li><li>hasTouchScreen: false</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>

[View console log messages](https://webcompat.com/console_logs/2020/6/598955a8-f3b9-4d8a-af58-fe8cad822f05)

_From [webcompat.com](https://webcompat.com/) with ❤️_",0,  ru   see bug description              url         browser   version    firefox       operating system    windows     tested another browser    yes chrome    problem type    something else   description    instead of site content  html code is displayed    steps to reproduce    i just went to the site and saw this             view the screenshot          img alt  screenshot  src                 browser configuration       gfx webrender all  false  gfx webrender blob images  true  gfx webrender enabled  false  image mem shared  true  buildid     channel  beta  hastouchscreen  false  mixed active content blocked  false  mixed passive content blocked  false  tracking content blocked  false             from     with ❤️ ,0
564066,16707118460.0,IssuesEvent,2021-06-09 11:21:19,googleapis/google-api-ruby-client,https://api.github.com/repos/googleapis/google-api-ruby-client,closed,Synthesis failed for searchconsole-v1,autosynth failure priority: p1 type: bug,"Hello! Autosynth couldn't regenerate searchconsole-v1. :broken_heart:

Please investigate and fix this issue within 5 business days.  While it remains broken,
this library cannot be updated with changes to the searchconsole-v1 API, and the library grows
stale.

See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md
for trouble shooting tips.

Here's the output from running `synth.py`:

```
2021-06-08 03:30:59,800 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/google-api-ruby-client
2021-06-08 03:31:00,609 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2021-06-08 03:31:00,611 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2021-06-08 03:31:00,613 autosynth [DEBUG] > Running: git config user.email yoshi-automation@google.com
2021-06-08 03:31:00,615 autosynth [DEBUG] > Running: git config push.default simple
2021-06-08 03:31:00,618 autosynth [DEBUG] > Running: git branch -f autosynth-searchconsole-v1
2021-06-08 03:31:00,620 autosynth [DEBUG] > Running: git checkout autosynth-searchconsole-v1
Switched to branch 'autosynth-searchconsole-v1'
2021-06-08 03:31:00,828 autosynth [INFO] > Running synthtool
2021-06-08 03:31:00,828 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'generated/google-apis-searchconsole_v1/synth.metadata', 'synth.py', '--']
2021-06-08 03:31:00,828 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/google-api-ruby-client/searchconsole/v1/sponge_log.log
2021-06-08 03:31:00,830 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata generated/google-apis-searchconsole_v1/synth.metadata synth.py -- searchconsole v1
2021-06-08 03:31:01,023 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/google-api-ruby-client/synth.py.
On branch autosynth-searchconsole-v1
nothing to commit, working tree clean
2021-06-08 03:31:01,079 synthtool [DEBUG] > Running: docker run --rm -v/home/kbuilder/.cache/synthtool/google-api-ruby-client:/workspace -v/var/run/docker.sock:/var/run/docker.sock -w /workspace -e USER_GROUP=1000:1000 --entrypoint script/synth.rb gcr.io/cloud-devrel-kokoro-resources/yoshi-ruby/autosynth searchconsole v1
DEBUG:synthtool:Running: docker run --rm -v/home/kbuilder/.cache/synthtool/google-api-ruby-client:/workspace -v/var/run/docker.sock:/var/run/docker.sock -w /workspace -e USER_GROUP=1000:1000 --entrypoint script/synth.rb gcr.io/cloud-devrel-kokoro-resources/yoshi-ruby/autosynth searchconsole v1
git clean -df
bundle install
Don't run Bundler as root. Bundler can ask for sudo if it is needed, and
installing your bundle as root will break this application for all non-root
users on this machine.
Fetching source index from https://rubygems.org/
Retrying fetcher due to error (2/4): Bundler::HTTPError Could not fetch specs from https://rubygems.org/ due to underlying error <bad response Gateway Error 502 (https://rubygems.org/specs.4.8.gz)>

Net::HTTPServiceUnavailable: 
<?xml version=""1.0"" encoding=""utf-8""?>
<!DOCTYPE html PUBLIC ""-//W3C//DTD XHTML 1.0 Strict//EN""
 ""http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"">
<html>
  <head>
    <title>503 Service Unavailable</title>
  </head>
  <body>
    <h1>Error 503 Service Unavailable</h1>
    <p>Service Unavailable</p>
    <h3>Guru Mediation:</h3>
    <p>Details: cache-sea4476-SEA 1623148269 1475416862</p>
    <hr>
    <p>Varnish cache server</p>
  </body>
</html>
chown -R 1000:1000 /workspace/generated
2021-06-08 03:31:09,380 synthtool [ERROR] > Failed executing docker run --rm -v/home/kbuilder/.cache/synthtool/google-api-ruby-client:/workspace -v/var/run/docker.sock:/var/run/docker.sock -w /workspace -e USER_GROUP=1000:1000 --entrypoint script/synth.rb gcr.io/cloud-devrel-kokoro-resources/yoshi-ruby/autosynth searchconsole v1:

None
ERROR:synthtool:Failed executing docker run --rm -v/home/kbuilder/.cache/synthtool/google-api-ruby-client:/workspace -v/var/run/docker.sock:/var/run/docker.sock -w /workspace -e USER_GROUP=1000:1000 --entrypoint script/synth.rb gcr.io/cloud-devrel-kokoro-resources/yoshi-ruby/autosynth searchconsole v1:

None
Traceback (most recent call last):
  File ""/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py"", line 193, in _run_module_as_main
    ""__main__"", mod_spec)
  File ""/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py"", line 85, in _run_code
    exec(code, run_globals)
  File ""/tmpfs/src/github/synthtool/synthtool/__main__.py"", line 102, in <module>
    main()
  File ""/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py"", line 1137, in __call__
    return self.main(*args, **kwargs)
  File ""/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py"", line 1062, in main
    rv = self.invoke(ctx)
  File ""/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py"", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File ""/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py"", line 763, in invoke
    return __callback(*args, **kwargs)
  File ""/tmpfs/src/github/synthtool/synthtool/__main__.py"", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File ""<frozen importlib._bootstrap_external>"", line 678, in exec_module
  File ""<frozen importlib._bootstrap>"", line 219, in _call_with_frames_removed
  File ""/home/kbuilder/.cache/synthtool/google-api-ruby-client/synth.py"", line 41, in <module>
    shell.run(command, hide_output=False)
  File ""/tmpfs/src/github/synthtool/synthtool/shell.py"", line 39, in run
    raise exc
  File ""/tmpfs/src/github/synthtool/synthtool/shell.py"", line 33, in run
    encoding=""utf-8"",
  File ""/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py"", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['docker', 'run', '--rm', '-v/home/kbuilder/.cache/synthtool/google-api-ruby-client:/workspace', '-v/var/run/docker.sock:/var/run/docker.sock', '-w', '/workspace', '-e', 'USER_GROUP=1000:1000', '--entrypoint', 'script/synth.rb', 'gcr.io/cloud-devrel-kokoro-resources/yoshi-ruby/autosynth', 'searchconsole', 'v1']' returned non-zero exit status 1.
2021-06-08 03:31:09,411 autosynth [ERROR] > Synthesis failed
2021-06-08 03:31:09,412 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File ""/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py"", line 193, in _run_module_as_main
    ""__main__"", mod_spec)
  File ""/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py"", line 85, in _run_code
    exec(code, run_globals)
  File ""/tmpfs/src/github/synthtool/autosynth/synth.py"", line 356, in <module>
    main()
  File ""/tmpfs/src/github/synthtool/autosynth/synth.py"", line 191, in main
    return _inner_main(temp_dir)
  File ""/tmpfs/src/github/synthtool/autosynth/synth.py"", line 293, in _inner_main
    ).synthesize(synth_log_path / ""sponge_log.log"")
  File ""/tmpfs/src/github/synthtool/autosynth/synthesizer.py"", line 120, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File ""/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py"", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'generated/google-apis-searchconsole_v1/synth.metadata', 'synth.py', '--', 'searchconsole', 'v1']' returned non-zero exit status 1.

```

Google internal developers can see the full log [here](http://sponge2/results/invocations/bdd2ce63-997e-4095-81b3-cd54e5fccbe4/targets/github%2Fsynthtool;config=default/tests;query=google-api-ruby-client;failed=false).
",1.0,"Synthesis failed for searchconsole-v1 - Hello! Autosynth couldn't regenerate searchconsole-v1. :broken_heart:

Please investigate and fix this issue within 5 business days.  While it remains broken,
this library cannot be updated with changes to the searchconsole-v1 API, and the library grows
stale.

See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md
for trouble shooting tips.

Here's the output from running `synth.py`:

```
2021-06-08 03:30:59,800 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/google-api-ruby-client
2021-06-08 03:31:00,609 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2021-06-08 03:31:00,611 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2021-06-08 03:31:00,613 autosynth [DEBUG] > Running: git config user.email yoshi-automation@google.com
2021-06-08 03:31:00,615 autosynth [DEBUG] > Running: git config push.default simple
2021-06-08 03:31:00,618 autosynth [DEBUG] > Running: git branch -f autosynth-searchconsole-v1
2021-06-08 03:31:00,620 autosynth [DEBUG] > Running: git checkout autosynth-searchconsole-v1
Switched to branch 'autosynth-searchconsole-v1'
2021-06-08 03:31:00,828 autosynth [INFO] > Running synthtool
2021-06-08 03:31:00,828 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'generated/google-apis-searchconsole_v1/synth.metadata', 'synth.py', '--']
2021-06-08 03:31:00,828 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/google-api-ruby-client/searchconsole/v1/sponge_log.log
2021-06-08 03:31:00,830 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata generated/google-apis-searchconsole_v1/synth.metadata synth.py -- searchconsole v1
2021-06-08 03:31:01,023 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/google-api-ruby-client/synth.py.
On branch autosynth-searchconsole-v1
nothing to commit, working tree clean
2021-06-08 03:31:01,079 synthtool [DEBUG] > Running: docker run --rm -v/home/kbuilder/.cache/synthtool/google-api-ruby-client:/workspace -v/var/run/docker.sock:/var/run/docker.sock -w /workspace -e USER_GROUP=1000:1000 --entrypoint script/synth.rb gcr.io/cloud-devrel-kokoro-resources/yoshi-ruby/autosynth searchconsole v1
DEBUG:synthtool:Running: docker run --rm -v/home/kbuilder/.cache/synthtool/google-api-ruby-client:/workspace -v/var/run/docker.sock:/var/run/docker.sock -w /workspace -e USER_GROUP=1000:1000 --entrypoint script/synth.rb gcr.io/cloud-devrel-kokoro-resources/yoshi-ruby/autosynth searchconsole v1
git clean -df
bundle install
Don't run Bundler as root. Bundler can ask for sudo if it is needed, and
installing your bundle as root will break this application for all non-root
users on this machine.
Fetching source index from https://rubygems.org/
Retrying fetcher due to error (2/4): Bundler::HTTPError Could not fetch specs from https://rubygems.org/ due to underlying error <bad response Gateway Error 502 (https://rubygems.org/specs.4.8.gz)>

Net::HTTPServiceUnavailable: 
<?xml version=""1.0"" encoding=""utf-8""?>
<!DOCTYPE html PUBLIC ""-//W3C//DTD XHTML 1.0 Strict//EN""
 ""http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"">
<html>
  <head>
    <title>503 Service Unavailable</title>
  </head>
  <body>
    <h1>Error 503 Service Unavailable</h1>
    <p>Service Unavailable</p>
    <h3>Guru Mediation:</h3>
    <p>Details: cache-sea4476-SEA 1623148269 1475416862</p>
    <hr>
    <p>Varnish cache server</p>
  </body>
</html>
chown -R 1000:1000 /workspace/generated
2021-06-08 03:31:09,380 synthtool [ERROR] > Failed executing docker run --rm -v/home/kbuilder/.cache/synthtool/google-api-ruby-client:/workspace -v/var/run/docker.sock:/var/run/docker.sock -w /workspace -e USER_GROUP=1000:1000 --entrypoint script/synth.rb gcr.io/cloud-devrel-kokoro-resources/yoshi-ruby/autosynth searchconsole v1:

None
ERROR:synthtool:Failed executing docker run --rm -v/home/kbuilder/.cache/synthtool/google-api-ruby-client:/workspace -v/var/run/docker.sock:/var/run/docker.sock -w /workspace -e USER_GROUP=1000:1000 --entrypoint script/synth.rb gcr.io/cloud-devrel-kokoro-resources/yoshi-ruby/autosynth searchconsole v1:

None
Traceback (most recent call last):
  File ""/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py"", line 193, in _run_module_as_main
    ""__main__"", mod_spec)
  File ""/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py"", line 85, in _run_code
    exec(code, run_globals)
  File ""/tmpfs/src/github/synthtool/synthtool/__main__.py"", line 102, in <module>
    main()
  File ""/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py"", line 1137, in __call__
    return self.main(*args, **kwargs)
  File ""/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py"", line 1062, in main
    rv = self.invoke(ctx)
  File ""/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py"", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File ""/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py"", line 763, in invoke
    return __callback(*args, **kwargs)
  File ""/tmpfs/src/github/synthtool/synthtool/__main__.py"", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File ""<frozen importlib._bootstrap_external>"", line 678, in exec_module
  File ""<frozen importlib._bootstrap>"", line 219, in _call_with_frames_removed
  File ""/home/kbuilder/.cache/synthtool/google-api-ruby-client/synth.py"", line 41, in <module>
    shell.run(command, hide_output=False)
  File ""/tmpfs/src/github/synthtool/synthtool/shell.py"", line 39, in run
    raise exc
  File ""/tmpfs/src/github/synthtool/synthtool/shell.py"", line 33, in run
    encoding=""utf-8"",
  File ""/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py"", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['docker', 'run', '--rm', '-v/home/kbuilder/.cache/synthtool/google-api-ruby-client:/workspace', '-v/var/run/docker.sock:/var/run/docker.sock', '-w', '/workspace', '-e', 'USER_GROUP=1000:1000', '--entrypoint', 'script/synth.rb', 'gcr.io/cloud-devrel-kokoro-resources/yoshi-ruby/autosynth', 'searchconsole', 'v1']' returned non-zero exit status 1.
2021-06-08 03:31:09,411 autosynth [ERROR] > Synthesis failed
2021-06-08 03:31:09,412 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File ""/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py"", line 193, in _run_module_as_main
    ""__main__"", mod_spec)
  File ""/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py"", line 85, in _run_code
    exec(code, run_globals)
  File ""/tmpfs/src/github/synthtool/autosynth/synth.py"", line 356, in <module>
    main()
  File ""/tmpfs/src/github/synthtool/autosynth/synth.py"", line 191, in main
    return _inner_main(temp_dir)
  File ""/tmpfs/src/github/synthtool/autosynth/synth.py"", line 293, in _inner_main
    ).synthesize(synth_log_path / ""sponge_log.log"")
  File ""/tmpfs/src/github/synthtool/autosynth/synthesizer.py"", line 120, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File ""/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py"", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'generated/google-apis-searchconsole_v1/synth.metadata', 'synth.py', '--', 'searchconsole', 'v1']' returned non-zero exit status 1.

```

Google internal developers can see the full log [here](http://sponge2/results/invocations/bdd2ce63-997e-4095-81b3-cd54e5fccbe4/targets/github%2Fsynthtool;config=default/tests;query=google-api-ruby-client;failed=false).
",0,synthesis failed for searchconsole     hello  autosynth couldn t regenerate searchconsole     broken heart   please investigate and fix this issue within   business days   while it remains broken  this library cannot be updated with changes to the searchconsole   api  and the library grows stale   see   for trouble shooting tips   here s the output from running  synth py                      autosynth     logs will be written to   tmpfs src logs google api ruby client               autosynth     running  git config   global core excludesfile  home kbuilder  autosynth gitignore               autosynth     running  git config user name yoshi automation               autosynth     running  git config user email yoshi automation google com               autosynth     running  git config push default simple               autosynth     running  git branch  f autosynth searchconsole                 autosynth     running  git checkout autosynth searchconsole   switched to branch  autosynth searchconsole                  autosynth     running synthtool               autosynth                     autosynth     log file path   tmpfs src logs google api ruby client searchconsole   sponge log log               autosynth     running   tmpfs src github synthtool env bin    m synthtool   metadata generated google apis searchconsole   synth metadata synth py    searchconsole                 synthtool     executing  home kbuilder  cache synthtool google api ruby client synth py  on branch autosynth searchconsole   nothing to commit  working tree clean               synthtool     running  docker run   rm  v home kbuilder  cache synthtool google api ruby client  workspace  v var run docker sock  var run docker sock  w  workspace  e user group       entrypoint script synth rb gcr io cloud devrel kokoro resources yoshi ruby autosynth searchconsole   debug synthtool running  docker run   rm  v home kbuilder  cache synthtool google api ruby client  workspace  v var run docker sock  var run docker sock  w  workspace  e user group       entrypoint script synth rb gcr io cloud devrel kokoro resources yoshi ruby autosynth searchconsole   git clean  df bundle install don t run bundler as root  bundler can ask for sudo if it is needed  and installing your bundle as root will break this application for all non root users on this machine  fetching source index from   retrying fetcher due to error        bundler  httperror could not fetch specs from   due to underlying error  bad response gateway error       net  httpserviceunavailable       doctype html public        dtd xhtml     strict  en                   service unavailable               error   service unavailable       service unavailable       guru mediation        details  cache   sea                 varnish cache server        chown  r      workspace generated               synthtool     failed executing docker run   rm  v home kbuilder  cache synthtool google api ruby client  workspace  v var run docker sock  var run docker sock  w  workspace  e user group       entrypoint script synth rb gcr io cloud devrel kokoro resources yoshi ruby autosynth searchconsole     none error synthtool failed executing docker run   rm  v home kbuilder  cache synthtool google api ruby client  workspace  v var run docker sock  var run docker sock  w  workspace  e user group       entrypoint script synth rb gcr io cloud devrel kokoro resources yoshi ruby autosynth searchconsole     none traceback  most recent call last     file   home kbuilder  pyenv versions       lib     runpy py   line    in  run module as main        main     mod spec    file   home kbuilder  pyenv versions       lib     runpy py   line    in  run code     exec code  run globals    file   tmpfs src github synthtool synthtool   main   py   line    in       main     file   tmpfs src github synthtool env lib     site packages click core py   line    in   call       return self main  args    kwargs    file   tmpfs src github synthtool env lib     site packages click core py   line    in main     rv   self invoke ctx    file   tmpfs src github synthtool env lib     site packages click core py   line    in invoke     return ctx invoke self callback    ctx params    file   tmpfs src github synthtool env lib     site packages click core py   line    in invoke     return   callback  args    kwargs    file   tmpfs src github synthtool synthtool   main   py   line    in main     spec loader exec module synth module     type  ignore   file      line    in exec module   file      line    in  call with frames removed   file   home kbuilder  cache synthtool google api ruby client synth py   line    in       shell run command  hide output false    file   tmpfs src github synthtool synthtool shell py   line    in run     raise exc   file   tmpfs src github synthtool synthtool shell py   line    in run     encoding  utf       file   home kbuilder  pyenv versions       lib     subprocess py   line    in run     output stdout  stderr stderr  subprocess calledprocesserror  command     returned non zero exit status                  autosynth     synthesis failed               autosynth     running  git clean  fdx removing   pycache    traceback  most recent call last     file   home kbuilder  pyenv versions       lib     runpy py   line    in  run module as main        main     mod spec    file   home kbuilder  pyenv versions       lib     runpy py   line    in  run code     exec code  run globals    file   tmpfs src github synthtool autosynth synth py   line    in       main     file   tmpfs src github synthtool autosynth synth py   line    in main     return  inner main temp dir    file   tmpfs src github synthtool autosynth synth py   line    in  inner main       synthesize synth log path    sponge log log     file   tmpfs src github synthtool autosynth synthesizer py   line    in synthesize     synth proc check returncode      raise an exception    file   home kbuilder  pyenv versions       lib     subprocess py   line    in check returncode     self stderr  subprocess calledprocesserror  command     returned non zero exit status          google internal developers can see the full log     ,0
100610,11200291038.0,IssuesEvent,2020-01-03 21:17:55,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: go module fetching gives unexpected stderr output,Documentation NeedsInvestigation,"### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.13.5 windows/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\username\AppData\Local\go-build
set GOENV=C:\Users\username\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\username\dev
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=C:\Program Files\Go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=C:\Program Files\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=0
set GOMOD=C:\Users\username\Dev\src\path\to\repo\go.mod
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\username\AppData\Local\Temp\go-build955724962=/tmp/go-build -gno-record-gcc-switches
</pre></details>

### What did you do?
`go mod download`

### What did you expect to see?
As per the documentation of the command,
>By default, download reports errors to standard error but is otherwise silent.

I expected no output on success. 

### What did you see instead?
A line to stderr for each module as it is cached:
>go: finding golang.org/x/sys v0.0.0-20190507160741-ecd444e8653b

### Discussion
This appears to come from here: https://github.com/golang/go/blob/dcd3b2c173b77d93be1c391e3b5f932e0779fb1f/src/cmd/go/internal/modfetch/cache.go#L171

This is an issue since many many CI tools will fail the build on output to stderr. We could redirect to stdout, but then *actual* errors might be missed (although that probably triggers a fail based on exit code). 

The smallest possible fix would be to update the documentation so that it mentions that caching will also write to stderr, but a ""better"" fix from my point of view would be to either move the caching logs to stdout, and/or hide them completely unless a verbose flag is passed?",1.0,"cmd/go: go module fetching gives unexpected stderr output - ### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.13.5 windows/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\username\AppData\Local\go-build
set GOENV=C:\Users\username\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\username\dev
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=C:\Program Files\Go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=C:\Program Files\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=0
set GOMOD=C:\Users\username\Dev\src\path\to\repo\go.mod
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\username\AppData\Local\Temp\go-build955724962=/tmp/go-build -gno-record-gcc-switches
</pre></details>

### What did you do?
`go mod download`

### What did you expect to see?
As per the documentation of the command,
>By default, download reports errors to standard error but is otherwise silent.

I expected no output on success. 

### What did you see instead?
A line to stderr for each module as it is cached:
>go: finding golang.org/x/sys v0.0.0-20190507160741-ecd444e8653b

### Discussion
This appears to come from here: https://github.com/golang/go/blob/dcd3b2c173b77d93be1c391e3b5f932e0779fb1f/src/cmd/go/internal/modfetch/cache.go#L171

This is an issue since many many CI tools will fail the build on output to stderr. We could redirect to stdout, but then *actual* errors might be missed (although that probably triggers a fail based on exit code). 

The smallest possible fix would be to update the documentation so that it mentions that caching will also write to stderr, but a ""better"" fix from my point of view would be to either move the caching logs to stdout, and/or hide them completely unless a verbose flag is passed?",1,cmd go  go module fetching gives unexpected stderr output       what version of go are you using   go version            go version  go version       windows             does this issue reproduce with the latest release   yes          what operating system and processor architecture are you using   go env          go env  output       go env  set     set goarch    set gobin   set gocache c  users username appdata local go build  set goenv c  users username appdata roaming go env  set goexe  exe  set goflags   set gohostarch    set gohostos windows  set gonoproxy   set gonosumdb   set goos windows  set gopath c  users username dev  set goprivate   set goproxy    set goroot c  program files go  set gosumdb sum golang org  set gotmpdir   set gotooldir c  program files go pkg tool windows    set gccgo gccgo  set ar ar  set cc gcc  set cxx g    set cgo enabled    set gomod c  users username dev src path to repo go mod  set cgo cflags  g     set cgo cppflags   set cgo cxxflags  g     set cgo fflags  g     set cgo ldflags  g     set pkg config pkg config  set gogccflags     fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map c  users username appdata local temp go    tmp go build  gno record gcc switches            what did you do    go mod download         what did you expect to see   as per the documentation of the command    by default  download reports errors to standard error but is otherwise silent     i expected no output on success          what did you see instead   a line to stderr for each module as it is cached    go  finding golang org x sys                  discussion  this appears to come from here       this is an issue since many many ci tools will fail the build on output to stderr  we could redirect to stdout  but then  actual  errors might be missed  although that probably triggers a fail based on exit code       the smallest possible fix would be to update the documentation so that it mentions that caching will also write to stderr  but a  better  fix from my point of view would be to either move the caching logs to stdout  and or hide them completely unless a verbose flag is passed ,1
253529,27300667096.0,IssuesEvent,2023-02-24 01:27:46,panasalap/linux-4.19.72_1,https://api.github.com/repos/panasalap/linux-4.19.72_1,closed,CVE-2022-3629 (Low) detected in linux-yoctov5.4.51 - autoclosed,security vulnerability,"## CVE-2022-3629 - Low Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yoctov5.4.51</b></p></summary>
<p>

<p>Yocto Linux Embedded kernel</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto>https://git.yoctoproject.org/git/linux-yocto</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/panasalap/linux-4.19.72/commit/c5a08fe8179013aad614165d792bc5b436591df6"">c5a08fe8179013aad614165d792bc5b436591df6</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/vmw_vsock/af_vsock.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
A vulnerability was found in Linux Kernel. It has been declared as problematic. This vulnerability affects the function vsock_connect of the file net/vmw_vsock/af_vsock.c. The manipulation leads to memory leak. It is recommended to apply a patch to fix this issue. VDB-211930 is the identifier assigned to this vulnerability.

<p>Publish Date: 2022-10-21
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-3629>CVE-2022-3629</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>3.3</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: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://www.linuxkernelcves.com/cves/CVE-2022-3629"">https://www.linuxkernelcves.com/cves/CVE-2022-3629</a></p>
<p>Release Date: 2022-10-21</p>
<p>Fix Resolution: v4.9.326,v4.14.291,v4.19.256,v5.4.211,v5.10.138,v5.15.63</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2022-3629 (Low) detected in linux-yoctov5.4.51 - autoclosed - ## CVE-2022-3629 - Low Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yoctov5.4.51</b></p></summary>
<p>

<p>Yocto Linux Embedded kernel</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto>https://git.yoctoproject.org/git/linux-yocto</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/panasalap/linux-4.19.72/commit/c5a08fe8179013aad614165d792bc5b436591df6"">c5a08fe8179013aad614165d792bc5b436591df6</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/vmw_vsock/af_vsock.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
A vulnerability was found in Linux Kernel. It has been declared as problematic. This vulnerability affects the function vsock_connect of the file net/vmw_vsock/af_vsock.c. The manipulation leads to memory leak. It is recommended to apply a patch to fix this issue. VDB-211930 is the identifier assigned to this vulnerability.

<p>Publish Date: 2022-10-21
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-3629>CVE-2022-3629</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>3.3</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: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://www.linuxkernelcves.com/cves/CVE-2022-3629"">https://www.linuxkernelcves.com/cves/CVE-2022-3629</a></p>
<p>Release Date: 2022-10-21</p>
<p>Fix Resolution: v4.9.326,v4.14.291,v4.19.256,v5.4.211,v5.10.138,v5.15.63</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      low  detected in linux         autoclosed      cve       low severity vulnerability     vulnerable library    linux              yocto linux embedded kernel   library home page   a href    found in head commit   a href      found in base branch   master             vulnerable source files                  net vmw vsock af vsock c                    vulnerability details         a vulnerability was found in linux kernel  it has been declared as problematic  this vulnerability affects the function vsock connect of the file net vmw vsock af vsock c  the manipulation leads to memory leak  it is recommended to apply a patch to fix this issue  vdb   is the identifier assigned to this vulnerability    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  low   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 mend    ,0
35134,6416420042.0,IssuesEvent,2017-08-08 14:46:57,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/cmd/callgraph: usage text suggests invalid code,Documentation,"The [usage](https://github.com/golang/tools/blob/bf4b54dc687c73b6ef63de8b8abf0ad3951e3edc/cmd/callgraph/main.go#L117) text of `x/tools/cmd/callgraph` command mentions:

> e.g. Caller.Pkg.Object.Path yields the import path of the enclosing package.
> Consult the go/ssa API documentation for details.

> Examples:
>
>     callgraph -format '{{.Caller.Pkg.Object.Path}} -> {{.Callee.Pkg.Object.Path}}' \
>       $GOROOT/src/net/http/triv.go | sort | uniq

`Caller` is [`*ssa.Function`](https://godoc.org/golang.org/x/tools/go/ssa#Function). Its `Pkg` field is [`*ssa.Package`](https://godoc.org/golang.org/x/tools/go/ssa#Package). But `ssa.Package` struct doesn't contain either field or method named `Object`.

So one gets the following error:

```
$ callgraph -format '{{.Caller.Pkg.Object.Path}} -> {{.Callee.Pkg.Object.Path}}' $(go env GOROOT)/src/net/http/triv.go | sort | uniq
callgraph: template: -format:1:9: executing ""-format"" at <.Caller.Pkg.Object.P...>: can't evaluate field Object in type *ssa.Package
```

I'm guessing that instead of `Caller.Pkg.Object.Path`, it should be `Caller.Pkg.Pkg.Path`:

https://godoc.org/golang.org/x/tools/go/ssa#Package.Pkg

That works as expected in my testing.

My environment details:

<details>

### What version of Go are you using (`go version`)?

```
$ go version
go version go1.8.1 darwin/amd64
```

### What operating system and processor architecture are you using (`go env`)?

```bash
$ go env
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/Dmitri/Dropbox/Work/2013/GoLanding:/Users/Dmitri/Dropbox/Work/2013/GoLand""
GORACE=""""
GOROOT=""/usr/local/go""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/tw/kgz4v2kn4n7d7ryg5k_z3dk40000gn/T/go-build822597389=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
PKG_CONFIG=""pkg-config""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2"" 
```

</details>",1.0,"x/tools/cmd/callgraph: usage text suggests invalid code - The [usage](https://github.com/golang/tools/blob/bf4b54dc687c73b6ef63de8b8abf0ad3951e3edc/cmd/callgraph/main.go#L117) text of `x/tools/cmd/callgraph` command mentions:

> e.g. Caller.Pkg.Object.Path yields the import path of the enclosing package.
> Consult the go/ssa API documentation for details.

> Examples:
>
>     callgraph -format '{{.Caller.Pkg.Object.Path}} -> {{.Callee.Pkg.Object.Path}}' \
>       $GOROOT/src/net/http/triv.go | sort | uniq

`Caller` is [`*ssa.Function`](https://godoc.org/golang.org/x/tools/go/ssa#Function). Its `Pkg` field is [`*ssa.Package`](https://godoc.org/golang.org/x/tools/go/ssa#Package). But `ssa.Package` struct doesn't contain either field or method named `Object`.

So one gets the following error:

```
$ callgraph -format '{{.Caller.Pkg.Object.Path}} -> {{.Callee.Pkg.Object.Path}}' $(go env GOROOT)/src/net/http/triv.go | sort | uniq
callgraph: template: -format:1:9: executing ""-format"" at <.Caller.Pkg.Object.P...>: can't evaluate field Object in type *ssa.Package
```

I'm guessing that instead of `Caller.Pkg.Object.Path`, it should be `Caller.Pkg.Pkg.Path`:

https://godoc.org/golang.org/x/tools/go/ssa#Package.Pkg

That works as expected in my testing.

My environment details:

<details>

### What version of Go are you using (`go version`)?

```
$ go version
go version go1.8.1 darwin/amd64
```

### What operating system and processor architecture are you using (`go env`)?

```bash
$ go env
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/Dmitri/Dropbox/Work/2013/GoLanding:/Users/Dmitri/Dropbox/Work/2013/GoLand""
GORACE=""""
GOROOT=""/usr/local/go""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/tw/kgz4v2kn4n7d7ryg5k_z3dk40000gn/T/go-build822597389=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
PKG_CONFIG=""pkg-config""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2"" 
```

</details>",1,x tools cmd callgraph  usage text suggests invalid code   the     text of  x tools cmd callgraph  command mentions       e g  caller pkg object path yields the import path of the enclosing package     consult the go ssa api documentation for details       examples            callgraph  format     caller pkg object path         callee pkg object path                goroot src net http triv go   sort   uniq     caller  is     its  pkg  field is     but  ssa package  struct doesn t contain either field or method named  object      so one gets the following error            callgraph  format     caller pkg object path         callee pkg object path      go env goroot  src net http triv go   sort   uniq  callgraph  template   format      executing   format  at    can t evaluate field object in type  ssa package         i m guessing that instead of  caller pkg object path   it should be  caller pkg pkg path           that works as expected in my testing     my environment details              what version of go are you using   go version              go version  go version       darwin               what operating system and processor architecture are you using   go env          bash    go env  goarch      gobin     goexe     gohostarch      gohostos  darwin   goos  darwin   gopath   users dmitri dropbox work   golanding  users dmitri dropbox work   goland   gorace     goroot   usr local go   gotooldir   usr local go pkg tool darwin     gccgo  gccgo   cc  clang   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders tw     t go    tmp go build  gno record gcc switches  fno common   cxx  clang     cgo enabled      pkg config  pkg config   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g               ,1
179661,13893737859.0,IssuesEvent,2020-10-19 13:53:14,WM-SEMERU/ds4se,https://api.github.com/repos/WM-SEMERU/ds4se,closed,Add Exp Flags and Add Facade Flags,Testing Domain,Edit the settings.ini to incorporate the flaggin system used by testing.,1.0,Add Exp Flags and Add Facade Flags - Edit the settings.ini to incorporate the flaggin system used by testing.,0,add exp flags and add facade flags   edit the settings ini to incorporate the flaggin system used by testing ,0
83574,10331809800.0,IssuesEvent,2019-09-02 19:58:03,golang/go,https://api.github.com/repos/golang/go,closed,"doc/go1.13: release notes refer to ""resolve.conf""",Documentation NeedsFix,"See https://tip.golang.org/doc/go1.13#net:

> On Unix systems where use-vc is set in resolve.conf, TCP is used for DNS resolution.

Should that not be ""resolv.conf"" (perhaps even ""/etc/resolv.conf"")?",1.0,"doc/go1.13: release notes refer to ""resolve.conf"" - See https://tip.golang.org/doc/go1.13#net:

> On Unix systems where use-vc is set in resolve.conf, TCP is used for DNS resolution.

Should that not be ""resolv.conf"" (perhaps even ""/etc/resolv.conf"")?",1,doc      release notes refer to  resolve conf    see        on unix systems where use vc is set in resolve conf  tcp is used for dns resolution     should that not be  resolv conf   perhaps even   etc resolv conf   ,1
264425,20020124049.0,IssuesEvent,2022-02-01 15:41:11,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: spelling error,Documentation NeedsFix release-blocker,"<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.18beta2 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env

</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->

run `go1.18beta2 work` and it shows help:

```
Go workspace provides access to operations on workspaces.

Note that support for workspaces is built into many other commands, not
just 'go work'.

See 'go help modules' for information about Go's module system of which
workspaces are a part.

A workspace is specified by a go.work file that specifies a set of
module directories with the ""use"" directive. These modules are used as
root modules by the go command for builds and related operations.  A
workspace that does not specify modules to be used cannot be used to do
builds from local modules.

go.work files are line-oriented. Each line holds a single directive,
made up of a keyword followed by aruments. For example:
...
```

In the last line of the above, `aruments` is spelled wrong

https://github.com/golang/go/blob/master/src/cmd/go/internal/workcmd/work.go#L30

### What did you expect to see?


`aruments` should be `arguments`


",1.0,"cmd/go: spelling error - <!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.18beta2 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env

</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->

run `go1.18beta2 work` and it shows help:

```
Go workspace provides access to operations on workspaces.

Note that support for workspaces is built into many other commands, not
just 'go work'.

See 'go help modules' for information about Go's module system of which
workspaces are a part.

A workspace is specified by a go.work file that specifies a set of
module directories with the ""use"" directive. These modules are used as
root modules by the go command for builds and related operations.  A
workspace that does not specify modules to be used cannot be used to do
builds from local modules.

go.work files are line-oriented. Each line holds a single directive,
made up of a keyword followed by aruments. For example:
...
```

In the last line of the above, `aruments` is spelled wrong

https://github.com/golang/go/blob/master/src/cmd/go/internal/workcmd/work.go#L30

### What did you expect to see?


`aruments` should be `arguments`


",1,cmd go  spelling error         please answer these questions before submitting your issue  thanks              what version of go are you using   go version            go version  go version     linux             does this issue reproduce with the latest release     yes        what operating system and processor architecture are you using   go env          go env  output       go env              what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on go dev play is best          run      work  and it shows help          go workspace provides access to operations on workspaces     note that support for workspaces is built into many other commands  not  just  go work      see  go help modules  for information about go s module system of which  workspaces are a part     a workspace is specified by a go work file that specifies a set of  module directories with the  use  directive  these modules are used as  root modules by the go command for builds and related operations   a  workspace that does not specify modules to be used cannot be used to do  builds from local modules     go work files are line oriented  each line holds a single directive   made up of a keyword followed by aruments  for example               in the last line of the above   aruments  is spelled wrong             what did you expect to see        aruments  should be  arguments       ,1
173173,14404094946.0,IssuesEvent,2020-12-03 16:51:23,golang/go,https://api.github.com/repos/golang/go,opened,doc/go1.16: document changes to the language for Go 1.16,Documentation NeedsInvestigation release-blocker,"As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

```HTML
<h2 id=""language"">Changes to the language</h2>

<p>
  TODO
</p>
```

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

@griesemer Will it be ""There are no changes to the language."", or are there changes in Go 1.16?",1.0,"doc/go1.16: document changes to the language for Go 1.16 - As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

```HTML
<h2 id=""language"">Changes to the language</h2>

<p>
  TODO
</p>
```

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

@griesemer Will it be ""There are no changes to the language."", or are there changes in Go 1.16?",1,doc      document changes to the language for go       as of filing this issue  the     contained the following html        html   changes to the language          todo                   per     it s a release blocker for go     beta   to have a complete draft of the eventual release notes  and so the todo needs to be resolved      griesemer will it be  there are no changes to the language    or are there changes in go     ,1
173234,14405922071.0,IssuesEvent,2020-12-03 19:26:31,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.16: document path and path/filepath changes for Go 1.16,Documentation NeedsInvestigation release-blocker,"As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

<dl id=""path""><dt><a href=""/pkg/path/"">path</a></dt>
  <dd>
    <p><!-- CL 264397 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/264397"">https://golang.org/cl/264397</a>: validate patterns in Match, Glob
    </p>
  </dd>
</dl><!-- path -->
<dl id=""path/filepath""><dt><a href=""/pkg/path/filepath/"">path/filepath</a></dt>
  <dd>
    <p><!-- CL 264397 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/264397"">https://golang.org/cl/264397</a>: validate patterns in Match, Glob
    </p>
  </dd>
</dl><!-- path/filepath -->

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.",1.0,"doc/go1.16: document path and path/filepath changes for Go 1.16 - As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

<dl id=""path""><dt><a href=""/pkg/path/"">path</a></dt>
  <dd>
    <p><!-- CL 264397 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/264397"">https://golang.org/cl/264397</a>: validate patterns in Match, Glob
    </p>
  </dd>
</dl><!-- path -->
<dl id=""path/filepath""><dt><a href=""/pkg/path/filepath/"">path/filepath</a></dt>
  <dd>
    <p><!-- CL 264397 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/264397"">https://golang.org/cl/264397</a>: validate patterns in Match, Glob
    </p>
  </dd>
</dl><!-- path/filepath -->

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.",1,doc      document path and path filepath changes for go       as of filing this issue  the     contained the following html        path                        todo    a href    validate patterns in match  glob                     path filepath                        todo    a href    validate patterns in match  glob                           per     it s a release blocker for go     beta   to have a complete draft of the eventual release notes  and so the todo needs to be resolved     a sequence of steps to resolve this issue may be        come up with a draft release note entry in this issue  then move the issue to needsfix state      send a cl with  doc           and include  for     fixes   this issue    in the body ,1
358196,25182126125.0,IssuesEvent,2022-11-11 14:35:44,golang/go,https://api.github.com/repos/golang/go,closed,net/netip: documentation: p.IP() should say p.Addr(),Documentation NeedsFix,"### What version of Go are you using (`go version`)?

Any 1.18+

### Does this issue reproduce with the latest release?

N/A

### What operating system and processor architecture are you using (`go env`)?

N/A

### What did you do?

Read the documentation for net/netip package online.

https://pkg.go.dev/net/netip#AddrPort.IsValid
> ""IsValid reports whether p.IP() is valid.""

https://pkg.go.dev/net/netip#Prefix.IsValid
> ""IsValid reports whether p.Bits() has a valid range for p.IP()""

However, neither AddrPort nor Prefix has an `IP()` method.

### What did you expect to see?

I think p.IP() should say p.Addr() in both cases

### What did you see instead?

See above",1.0,"net/netip: documentation: p.IP() should say p.Addr() - ### What version of Go are you using (`go version`)?

Any 1.18+

### Does this issue reproduce with the latest release?

N/A

### What operating system and processor architecture are you using (`go env`)?

N/A

### What did you do?

Read the documentation for net/netip package online.

https://pkg.go.dev/net/netip#AddrPort.IsValid
> ""IsValid reports whether p.IP() is valid.""

https://pkg.go.dev/net/netip#Prefix.IsValid
> ""IsValid reports whether p.Bits() has a valid range for p.IP()""

However, neither AddrPort nor Prefix has an `IP()` method.

### What did you expect to see?

I think p.IP() should say p.Addr() in both cases

### What did you see instead?

See above",1,net netip  documentation  p ip   should say p addr         what version of go are you using   go version       any             does this issue reproduce with the latest release     n a        what operating system and processor architecture are you using   go env       n a        what did you do     read the documentation for net netip package online           isvalid reports whether p ip   is valid            isvalid reports whether p bits   has a valid range for p ip       however  neither addrport nor prefix has an  ip    method         what did you expect to see     i think p ip   should say p addr   in both cases        what did you see instead     see above,1
79918,10145708086.0,IssuesEvent,2019-08-05 05:45:30,golang/go,https://api.github.com/repos/golang/go,closed,net/http: another typo in Response.Body field docs,Documentation NeedsFix help wanted,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go1.12.7 windows/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=amd64
GOOS=windows
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

Read the documentation in file: ~/src/net/http/response.go
Found grammatical issue in field Body of struct Response, around line 68

### What did you expect to see?

// As of Go 1.12, the Body will also implement io.Writer

### What did you see instead?

// As of Go 1.12, the Body will be also implement io.Writer",1.0,"net/http: another typo in Response.Body field docs - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go1.12.7 windows/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH=amd64
GOOS=windows
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

Read the documentation in file: ~/src/net/http/response.go
Found grammatical issue in field Body of struct Response, around line 68

### What did you expect to see?

// As of Go 1.12, the Body will also implement io.Writer

### What did you see instead?

// As of Go 1.12, the Body will be also implement io.Writer",1,net http  another typo in response body field docs            what version of go are you using   go version            go version        windows             does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env          go env  output       go env  goarch    goos windows            what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best          read the documentation in file    src net http response go  found grammatical issue in field body of struct response  around line          what did you expect to see        as of go      the body will also implement io writer        what did you see instead        as of go      the body will be also implement io writer,1
285192,8755498007.0,IssuesEvent,2018-12-14 15:02:25,SunwellWoW/Sunwell-TBC-Bugtracker,https://api.github.com/repos/SunwellWoW/Sunwell-TBC-Bugtracker,closed,Blade's Edge Mountains Quest: Fire At Will!,High Priority Quest/RP Resolved - fix NOT live yet,"Description: Quest in Blade's Edge Mountains


How it works: When you use Naturalized Ammuniton on the Fel Cannons it just says ""You have no target""


How it should work: 


Source (you should point out proofs of your report, please give us some source): 
123",1.0,"Blade's Edge Mountains Quest: Fire At Will! - Description: Quest in Blade's Edge Mountains


How it works: When you use Naturalized Ammuniton on the Fel Cannons it just says ""You have no target""


How it should work: 


Source (you should point out proofs of your report, please give us some source): 
123",0,blade s edge mountains quest  fire at will    description  quest in blade s edge mountains      how it works  when you use naturalized ammuniton on the fel cannons it just says  you have no target       how it should work        source  you should point out proofs of your report  please give us some source      ,0
57150,8147679940.0,IssuesEvent,2018-08-22 01:10:56,golang/go,https://api.github.com/repos/golang/go,closed,web: remove content other than documentation from primary Go source tree,Documentation NeedsDecision,"Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
1.9

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?
every

### What did you do?
```
$ du -h SRC/blog

19M     blog/content
19M     blog
```

If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.


### What did you expect to see?
no blog content

### What did you see instead?
no

Now the Go blog content takes about 19MB in source code repos.
As I'd tried to remove blog directory and repack the whole GOROOT, the pkg reduce about 16MB. 

-rw-r--r--  1 root staff  82M Sep 18 11:29 go1.9.linux-amd64..no_blog.tar.gz
-rw-r--r--  1 root root   98M Aug 25 06:44 go1.9.linux-amd64.tar.gz",1.0,"web: remove content other than documentation from primary Go source tree - Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
1.9

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?
every

### What did you do?
```
$ du -h SRC/blog

19M     blog/content
19M     blog
```

If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.


### What did you expect to see?
no blog content

### What did you see instead?
no

Now the Go blog content takes about 19MB in source code repos.
As I'd tried to remove blog directory and repack the whole GOROOT, the pkg reduce about 16MB. 

-rw-r--r--  1 root staff  82M Sep 18 11:29 go1.9.linux-amd64..no_blog.tar.gz
-rw-r--r--  1 root root   98M Aug 25 06:44 go1.9.linux-amd64.tar.gz",1,web  remove content other than documentation from primary go source tree   please answer these questions before submitting your issue  thanks         what version of go are you using   go version                does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env     every        what did you do          du  h src blog          blog content        blog         if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best           what did you expect to see   no blog content        what did you see instead   no    now the go blog content takes about   in source code repos   as i d tried to remove blog directory and repack the whole goroot  the pkg reduce about         rw r  r      root staff    sep           linux    no blog tar gz   rw r  r      root root     aug           linux   tar gz,1
234443,25853465649.0,IssuesEvent,2022-12-13 12:05:00,MatBenfield/news,https://api.github.com/repos/MatBenfield/news,closed,[SecurityWeek] Device Exploits Earn Hackers Nearly $1 Million at Pwn2Own Toronto 2022,SecurityWeek Stale,"

**The Zero Day Initiative’s Pwn2Own Toronto 2022 hacking contest has come to an end, with participants earning nearly $1 million for exploits targeting smartphones, printers, routers, NAS devices, and smart speakers.**

[read more](https://www.securityweek.com/device-exploits-earn-hackers-nearly-1-million-pwn2own-toronto-2022)



<https://www.securityweek.com/device-exploits-earn-hackers-nearly-1-million-pwn2own-toronto-2022>

",True,"[SecurityWeek] Device Exploits Earn Hackers Nearly $1 Million at Pwn2Own Toronto 2022 - 

**The Zero Day Initiative’s Pwn2Own Toronto 2022 hacking contest has come to an end, with participants earning nearly $1 million for exploits targeting smartphones, printers, routers, NAS devices, and smart speakers.**

[read more](https://www.securityweek.com/device-exploits-earn-hackers-nearly-1-million-pwn2own-toronto-2022)



<https://www.securityweek.com/device-exploits-earn-hackers-nearly-1-million-pwn2own-toronto-2022>

",0,  device exploits earn hackers nearly    million at   toronto         the zero day initiative’s   toronto   hacking contest has come to an end  with participants earning nearly    million for exploits targeting smartphones  printers  routers  nas devices  and smart speakers                ,0
5028,5437592225.0,IssuesEvent,2017-03-06 07:39:08,ushahidi/platform,https://api.github.com/repos/ushahidi/platform,opened,USH-005 Open Port 22 SSH,Stage: Tech Spec Theme: Security and privacy,"### Expected behaviour
- Implement a bruteforce protection (for instance fail2ban or log2iptables)
- Create firewall rules who can access SSH. (only internal access for instance)
- Use a different port for SSH. (this will evade automatic portscanners that only scan for SSH on the
default port
- Use portknocking to open the port on demand
### Actual behaviour
- The Nmap scan reveals an open SSH port 22 on ushahidi.com.
### Steps to reproduce the behaviour/error
",True,"USH-005 Open Port 22 SSH - ### Expected behaviour
- Implement a bruteforce protection (for instance fail2ban or log2iptables)
- Create firewall rules who can access SSH. (only internal access for instance)
- Use a different port for SSH. (this will evade automatic portscanners that only scan for SSH on the
default port
- Use portknocking to open the port on demand
### Actual behaviour
- The Nmap scan reveals an open SSH port 22 on ushahidi.com.
### Steps to reproduce the behaviour/error
",0,ush   open port   ssh       expected behaviour    implement a bruteforce protection  for instance   or       create firewall rules who can access ssh   only internal access for instance     use a different port for ssh   this will evade automatic portscanners that only scan for ssh on the  default port    use portknocking to open the port on demand      actual behaviour    the nmap scan reveals an open ssh port   on ushahidi com       steps to reproduce the behaviour error  ,0
213577,16527644796.0,IssuesEvent,2021-05-26 22:45:08,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.17: document net/http changes for Go 1.17,Documentation NeedsInvestigation help wanted release-blocker,"As of filing this issue, the [Go 1.17 draft release notes](https://tip.golang.org/doc/go1.17) contained the following HTML:

<dl id=""net/http""><dt><a href=""/pkg/net/http/"">net/http</a></dt>
  <dd>
    <p><!-- CL 295370 -->
      The <a href=""/pkg/net/http/""><code>net/http</code></a> package now uses the new
      <a href=""/pkg/crypto/tls#Conn.HandshakeContext""><code>(*tls.Conn).HandshakeContext</code></a>
      with the <a href=""/pkg/net/http/#Request""><code>Request</code></a> context
      when performing TLS handshakes in the client or server.
    </p>
    <p><!-- CL 235437 -->
      TODO: <a href=""https://golang.org/cl/235437"">https://golang.org/cl/235437</a>: add to deadlines only when positive
    </p>
    <p><!-- CL 308952 -->
      TODO: <a href=""https://golang.org/cl/308952"">https://golang.org/cl/308952</a>: make ReadRequest return an error when requests have multiple Host headers
    </p>
  </dd>
</dl>

---

This TODO needs to be resolved by July 1 so that we can have complete release notes for [Beta 1](https://golang.org/s/release#june-1--december-1-beta-1-issued).

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.17:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.17) and include ""For #44513. Fixes #46015."" in the body.",1.0,"doc/go1.17: document net/http changes for Go 1.17 - As of filing this issue, the [Go 1.17 draft release notes](https://tip.golang.org/doc/go1.17) contained the following HTML:

<dl id=""net/http""><dt><a href=""/pkg/net/http/"">net/http</a></dt>
  <dd>
    <p><!-- CL 295370 -->
      The <a href=""/pkg/net/http/""><code>net/http</code></a> package now uses the new
      <a href=""/pkg/crypto/tls#Conn.HandshakeContext""><code>(*tls.Conn).HandshakeContext</code></a>
      with the <a href=""/pkg/net/http/#Request""><code>Request</code></a> context
      when performing TLS handshakes in the client or server.
    </p>
    <p><!-- CL 235437 -->
      TODO: <a href=""https://golang.org/cl/235437"">https://golang.org/cl/235437</a>: add to deadlines only when positive
    </p>
    <p><!-- CL 308952 -->
      TODO: <a href=""https://golang.org/cl/308952"">https://golang.org/cl/308952</a>: make ReadRequest return an error when requests have multiple Host headers
    </p>
  </dd>
</dl>

---

This TODO needs to be resolved by July 1 so that we can have complete release notes for [Beta 1](https://golang.org/s/release#june-1--december-1-beta-1-issued).

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.17:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.17) and include ""For #44513. Fixes #46015."" in the body.",1,doc      document net http changes for go       as of filing this issue  the     contained the following html      net http                    the   net http   package now uses the new           tls conn  handshakecontext         with the   request   context       when performing tls handshakes in the client or server                     todo   a href    add to deadlines only when positive                    todo   a href    make readrequest return an error when requests have multiple host headers                   this todo needs to be resolved by july   so that we can have complete release notes for      a sequence of steps to resolve this issue may be      come up with a draft release note entry in this issue  then move the issue to needsfix state     send a cl with  doc           and include  for     fixes      in the body ,1
89837,25907374061.0,IssuesEvent,2022-12-15 11:17:26,Crocoblock/suggestions,https://api.github.com/repos/Crocoblock/suggestions,closed,Custom icon for single rating and product grid & product list widget / jet woobuilder,JetWooBuilder,"Please add the possibility of inserting a custom icon (svg) to the rating stars of single rating, product grid and product list widgets.",1.0,"Custom icon for single rating and product grid & product list widget / jet woobuilder - Please add the possibility of inserting a custom icon (svg) to the rating stars of single rating, product grid and product list widgets.",0,custom icon for single rating and product grid   product list widget   jet woobuilder   please add the possibility of inserting a custom icon  svg  to the rating stars of single rating  product grid and product list widgets ,0
38802,6705554891.0,IssuesEvent,2017-10-12 01:03:48,golang/go,https://api.github.com/repos/golang/go,closed,all: can't build go1.4,Documentation,"Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
n/a

### What operating system and processor architecture are you using (`go env`)?
Arch Linux 64bit
```
➤ gcc --version
gcc (GCC) 7.1.1 20170630
➤ clang --version
clang version 4.0.1 (tags/RELEASE_401/final)
```

### What did you do?
```
➤ git clone https://github.com/golang/go
➤ git checkout release-branch.go1.4
➤ cd src && ./make.bash 
➤ env CC=clang ./make.bash 
```

### What did you expect to see?
Working go1.4

### What did you see instead?
Can't compile it with neither clang nor gcc.

With clang:
```
/usr/bin/ld: -r and -pie may not be used together
clang-4.0: error: linker command failed with exit code 1 (use -v to see invocation)
```

And with gcc:

```
os/user
# net
cannot load DWARF output from $WORK/net/_obj//_cgo_.o: decoding dwarf section info at offset 0x4: unsupported version 0
# os/user
cannot load DWARF output from $WORK/os/user/_obj//_cgo_.o: decoding dwarf section info at offset 0x4: unsupported version 0
```

https://gist.github.com/OneOfOne/a9116d4c85c32141282fcf9a2973fbd2


Discovered while trying to diagnose #21042
",1.0,"all: can't build go1.4 - Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
n/a

### What operating system and processor architecture are you using (`go env`)?
Arch Linux 64bit
```
➤ gcc --version
gcc (GCC) 7.1.1 20170630
➤ clang --version
clang version 4.0.1 (tags/RELEASE_401/final)
```

### What did you do?
```
➤ git clone https://github.com/golang/go
➤ git checkout release-branch.go1.4
➤ cd src && ./make.bash 
➤ env CC=clang ./make.bash 
```

### What did you expect to see?
Working go1.4

### What did you see instead?
Can't compile it with neither clang nor gcc.

With clang:
```
/usr/bin/ld: -r and -pie may not be used together
clang-4.0: error: linker command failed with exit code 1 (use -v to see invocation)
```

And with gcc:

```
os/user
# net
cannot load DWARF output from $WORK/net/_obj//_cgo_.o: decoding dwarf section info at offset 0x4: unsupported version 0
# os/user
cannot load DWARF output from $WORK/os/user/_obj//_cgo_.o: decoding dwarf section info at offset 0x4: unsupported version 0
```

https://gist.github.com/OneOfOne/a9116d4c85c32141282fcf9a2973fbd2


Discovered while trying to diagnose #21042
",1,all  can t build       please answer these questions before submitting your issue  thanks         what version of go are you using   go version     n a        what operating system and processor architecture are you using   go env     arch linux         ➤ gcc   version  gcc  gcc           ➤ clang   version  clang version        tags release   final              what did you do        ➤ git clone    ➤ git checkout release branch      ➤ cd src      make bash   ➤ env cc clang   make bash              what did you expect to see   working            what did you see instead   can t compile it with neither clang nor gcc     with clang         usr bin ld   r and  pie may not be used together  clang      error  linker command failed with exit code    use  v to see invocation          and with gcc          os user    net  cannot load dwarf output from  work net  obj   cgo  o  decoding dwarf section info at offset    unsupported version      os user  cannot load dwarf output from  work os user  obj   cgo  o  decoding dwarf section info at offset    unsupported version                  discovered while trying to diagnose     ,1
51193,13207391381.0,IssuesEvent,2020-08-14 22:55:39,icecube-trac/tix4,https://api.github.com/repos/icecube-trac/tix4,opened,"""Pass-through"" frame objects (Trac #21)",IceTray Incomplete Migration Migrated from Trac defect,"<details>
 <summary><em>Migrated from <a href=""https://code.icecube.wisc.edu/projects/icecube/ticket/21"">https://code.icecube.wisc.edu/projects/icecube/ticket/21</a>, reported by troyand owned by troy</em></summary>
<p>

```json
{
    ""status"": ""closed"",
    ""changetime"": ""2007-11-11T03:51:18"",
    ""_ts"": ""1194753078000000"",
    ""description"": ""If i have frames that contain objects that I dont' have code for, i should be able to pass them through my tray w/o SkipFrame?-ing them."",
    ""reporter"": ""troy"",
    ""cc"": """",
    ""resolution"": ""fixed"",
    ""time"": ""2007-06-03T16:37:21"",
    ""component"": ""IceTray"",
    ""summary"": ""\""Pass-through\"" frame objects"",
    ""priority"": ""normal"",
    ""keywords"": """",
    ""milestone"": """",
    ""owner"": ""troy"",
    ""type"": ""defect""
}
```

</p>
</details>
",1.0,"""Pass-through"" frame objects (Trac #21) - <details>
 <summary><em>Migrated from <a href=""https://code.icecube.wisc.edu/projects/icecube/ticket/21"">https://code.icecube.wisc.edu/projects/icecube/ticket/21</a>, reported by troyand owned by troy</em></summary>
<p>

```json
{
    ""status"": ""closed"",
    ""changetime"": ""2007-11-11T03:51:18"",
    ""_ts"": ""1194753078000000"",
    ""description"": ""If i have frames that contain objects that I dont' have code for, i should be able to pass them through my tray w/o SkipFrame?-ing them."",
    ""reporter"": ""troy"",
    ""cc"": """",
    ""resolution"": ""fixed"",
    ""time"": ""2007-06-03T16:37:21"",
    ""component"": ""IceTray"",
    ""summary"": ""\""Pass-through\"" frame objects"",
    ""priority"": ""normal"",
    ""keywords"": """",
    ""milestone"": """",
    ""owner"": ""troy"",
    ""type"": ""defect""
}
```

</p>
</details>
",0, pass through  frame objects  trac            migrated from          json        status    closed        changetime                      ts             description    if i have frames that contain objects that i dont  have code for  i should be able to pass them through my tray w o skipframe  ing them         reporter    troy        cc            resolution    fixed        time                     component    icetray        summary      pass through   frame objects        priority    normal        keywords            milestone            owner    troy        type    defect             ,0
494034,14243789506.0,IssuesEvent,2020-11-19 05:25:15,ajency/Dhanda-App,https://api.github.com/repos/ajency/Dhanda-App,opened,"Case: When admin is removed by the owner, he can still continue to use the app. He is only directed to business pages once the app cache is cleared/ uninstalled",Priority: High missing,"Expected: Can we have a way, that when the admin is removed by the owner, the user/ admins account is locked and he cannot use it anymore. I will need to do a screen in this area. Let's discuss if it can be done.",1.0,"Case: When admin is removed by the owner, he can still continue to use the app. He is only directed to business pages once the app cache is cleared/ uninstalled - Expected: Can we have a way, that when the admin is removed by the owner, the user/ admins account is locked and he cannot use it anymore. I will need to do a screen in this area. Let's discuss if it can be done.",0,case  when admin is removed by the owner  he can still continue to use the app  he is only directed to business pages once the app cache is cleared  uninstalled   expected  can we have a way  that when the admin is removed by the owner  the user  admins account is locked and he cannot use it anymore  i will need to do a screen in this area  let s discuss if it can be done ,0
273311,23745284481.0,IssuesEvent,2022-08-31 15:27:32,Azure/azure-sdk-for-python,https://api.github.com/repos/Azure/azure-sdk-for-python,closed,Azure monitor Readme issues,Docs Monitor Client test-manual-pass Monitor - Ingestion,"1.
Section [link](https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/cognitivelanguage/ai-language-text#custom-single-label-classification):
![image](https://user-images.githubusercontent.com/57166602/187159018-03e5b1ae-1a45-443f-abab-1acaad6bf7f9.png)

Suggestion:
Add link for `[azure_monitor_create_using_portal]`:
https://docs.microsoft.com//azure/azure-monitor/logs/log-analytics-workspace-overview

@lmazuel , @scottaddie , @srnagar , @hectorhdzg for notification.",1.0,"Azure monitor Readme issues - 1.
Section [link](https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/cognitivelanguage/ai-language-text#custom-single-label-classification):
![image](https://user-images.githubusercontent.com/57166602/187159018-03e5b1ae-1a45-443f-abab-1acaad6bf7f9.png)

Suggestion:
Add link for `[azure_monitor_create_using_portal]`:
https://docs.microsoft.com//azure/azure-monitor/logs/log-analytics-workspace-overview

@lmazuel , @scottaddie , @srnagar , @hectorhdzg for notification.",0,azure monitor readme issues       section              suggestion   add link for             lmazuel    scottaddie    srnagar    hectorhdzg for notification ,0
180911,14839283871.0,IssuesEvent,2021-01-16 00:14:08,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/gopls: improve documentation,Documentation Tools gopls,"Our current documentation is not very user-friendly and rarely updated.
We should add more information about workflows, features, example configurations, etc.
We should also try to autogenerate as much as possible (https://github.com/golang/go/issues/33544).",1.0,"x/tools/gopls: improve documentation - Our current documentation is not very user-friendly and rarely updated.
We should add more information about workflows, features, example configurations, etc.
We should also try to autogenerate as much as possible (https://github.com/golang/go/issues/33544).",1,x tools gopls  improve documentation   our current documentation is not very user friendly and rarely updated   we should add more information about workflows  features  example configurations  etc   we should also try to autogenerate as much as possible   ,1
140322,12891489221.0,IssuesEvent,2020-07-13 17:49:45,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: include GOMODCACHE in documented list of environment variables,Documentation NeedsFix release-blocker,"Go 1.15 adds the `GOMODCACHE` environment variable (#34527). It's mentioned in the release notes ([CL 230537](https://golang.org/cl/230537)). Should it also be included in the list at https://tip.golang.org/cmd/go/#hdr-Environment_variables?

/cc @jayconrod @matloob @bcmills",1.0,"cmd/go: include GOMODCACHE in documented list of environment variables - Go 1.15 adds the `GOMODCACHE` environment variable (#34527). It's mentioned in the release notes ([CL 230537](https://golang.org/cl/230537)). Should it also be included in the list at https://tip.golang.org/cmd/go/#hdr-Environment_variables?

/cc @jayconrod @matloob @bcmills",1,cmd go  include gomodcache in documented list of environment variables   go     adds the  gomodcache  environment variable       it s mentioned in the release notes      should it also be included in the list at       cc  jayconrod  matloob  bcmills,1
256512,19425201120.0,IssuesEvent,2021-12-21 03:55:10,golang/go,https://api.github.com/repos/golang/go,closed,net/http: broken link to ResponseWriter trailers example,Documentation NeedsFix,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.17.3 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/reilly/Library/Caches/go-build""
GOENV=""/Users/reilly/Library/Application Support/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/reilly/go/pkg/mod""
GONOPROXY=""github.com/EverlongProject""
GONOSUMDB=""github.com/EverlongProject""
GOOS=""darwin""
GOPATH=""/Users/reilly/go""
GOPRIVATE=""github.com/EverlongProject""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GOVCS=""""
GOVERSION=""go1.17.3""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/gz/4ytqr0r12q1fbx8ct_w3k_880000gn/T/go-build2936231312=/tmp/go-build -gno-record-gcc-switches -fno-common""
GOROOT/bin/go version: go version go1.17.3 darwin/amd64
GOROOT/bin/go tool compile -V: compile version go1.17.3
uname -v: Darwin Kernel Version 21.2.0: Sun Nov 28 20:28:54 PST 2021; root:xnu-8019.61.5~1/RELEASE_X86_64
ProductName:	macOS
ProductVersion:	12.1
BuildVersion:	21C52
lldb --version: lldb-1300.0.42.3
Swift version 5.5.2-dev
</pre></details>

### What did you do?

Tried to follow the ""example_ResponseWriter_trailers"" link just after the text ""the normal Go trailers mechanism is preferred"" in the ""Constants"" section of the doc.

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->



### What did you expect to see?
The relevant example


### What did you see instead?
The top of the page.

The link on the page is https://golang.org/pkg/net/http/#example_ResponseWriter_trailers.

The actual anchor attached to the example is `#example-ResponseWriter-Trailers`.",1.0,"net/http: broken link to ResponseWriter trailers example - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.17.3 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/reilly/Library/Caches/go-build""
GOENV=""/Users/reilly/Library/Application Support/go/env""
GOEXE=""""
GOEXPERIMENT=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOINSECURE=""""
GOMODCACHE=""/Users/reilly/go/pkg/mod""
GONOPROXY=""github.com/EverlongProject""
GONOSUMDB=""github.com/EverlongProject""
GOOS=""darwin""
GOPATH=""/Users/reilly/go""
GOPRIVATE=""github.com/EverlongProject""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GOVCS=""""
GOVERSION=""go1.17.3""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/gz/4ytqr0r12q1fbx8ct_w3k_880000gn/T/go-build2936231312=/tmp/go-build -gno-record-gcc-switches -fno-common""
GOROOT/bin/go version: go version go1.17.3 darwin/amd64
GOROOT/bin/go tool compile -V: compile version go1.17.3
uname -v: Darwin Kernel Version 21.2.0: Sun Nov 28 20:28:54 PST 2021; root:xnu-8019.61.5~1/RELEASE_X86_64
ProductName:	macOS
ProductVersion:	12.1
BuildVersion:	21C52
lldb --version: lldb-1300.0.42.3
Swift version 5.5.2-dev
</pre></details>

### What did you do?

Tried to follow the ""example_ResponseWriter_trailers"" link just after the text ""the normal Go trailers mechanism is preferred"" in the ""Constants"" section of the doc.

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->



### What did you expect to see?
The relevant example


### What did you see instead?
The top of the page.

The link on the page is https://golang.org/pkg/net/http/#example_ResponseWriter_trailers.

The actual anchor attached to the example is `#example-ResponseWriter-Trailers`.",1,net http  broken link to responsewriter trailers example            what version of go are you using   go version            go version  go version       darwin             does this issue reproduce with the latest release   yes        what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   users reilly library caches go build   goenv   users reilly library application support go env   goexe     goexperiment     goflags     gohostarch      gohostos  darwin   goinsecure     gomodcache   users reilly go pkg mod   gonoproxy  github com everlongproject   gonosumdb  github com everlongproject   goos  darwin   gopath   users reilly go   goprivate  github com everlongproject   goproxy     goroot   usr local go   gosumdb  sum golang org   gotmpdir     gotooldir   usr local go pkg tool darwin     govcs     goversion          gccgo  gccgo   ar  ar   cc  clang   cxx  clang     cgo enabled      gomod   dev null   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic  arch         pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders gz       t go    tmp go build  gno record gcc switches  fno common   goroot bin go version  go version       darwin    goroot bin go tool compile  v  compile version        uname  v  darwin kernel version        sun nov         pst    root xnu         release      productname 	macos  productversion 	     buildversion 	   lldb   version  lldb          swift version       dev            what did you do     tried to follow the  example responsewriter trailers  link just after the text  the normal go trailers mechanism is preferred  in the  constants  section of the doc           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on play golang org is best                  what did you expect to see   the relevant example          what did you see instead   the top of the page     the link on the page is      the actual anchor attached to the example is   example responsewriter trailers  ,1
339134,24611489018.0,IssuesEvent,2022-10-14 22:08:24,golang/go,https://api.github.com/repos/golang/go,closed,x/website: Missing Retract field and ModPath struct in GoMod module reference docs,Documentation help wanted NeedsFix modules,"<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

n/a

### Does this issue reproduce with the latest release?

n/a

### What operating system and processor architecture are you using (`go env`)?

n/a

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->
Reviewed https://go.dev/ref/mod#go-mod-edit (source: https://github.com/golang/website/blob/master/_content/ref/mod.md#go-mod-edit-go-mod-edit)


### What did you expect to see?

The description of the `-json` output should include the `Retract []Retract` field in the GoMod struct and include the `ModPath` struct (and the Module field should be of type ModPath).
This field and struct are present in the `go help mod edit` documentation.

### What did you see instead?

Missing Retract field and ModPath struct.
",1.0,"x/website: Missing Retract field and ModPath struct in GoMod module reference docs - <!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

n/a

### Does this issue reproduce with the latest release?

n/a

### What operating system and processor architecture are you using (`go env`)?

n/a

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->
Reviewed https://go.dev/ref/mod#go-mod-edit (source: https://github.com/golang/website/blob/master/_content/ref/mod.md#go-mod-edit-go-mod-edit)


### What did you expect to see?

The description of the `-json` output should include the `Retract []Retract` field in the GoMod struct and include the `ModPath` struct (and the Module field should be of type ModPath).
This field and struct are present in the `go help mod edit` documentation.

### What did you see instead?

Missing Retract field and ModPath struct.
",1,x website  missing retract field and modpath struct in gomod module reference docs         please answer these questions before submitting your issue  thanks              what version of go are you using   go version       n a        does this issue reproduce with the latest release     n a        what operating system and processor architecture are you using   go env       n a        what did you do           if possible  provide a recipe for reproducing the error   a complete runnable program is good   a link on go dev play is best        reviewed    source             what did you expect to see     the description of the   json  output should include the  retract  retract  field in the gomod struct and include the  modpath  struct  and the module field should be of type modpath    this field and struct are present in the  go help mod edit  documentation         what did you see instead     missing retract field and modpath struct   ,1
14787,3886324190.0,IssuesEvent,2016-04-14 00:13:36,golang/go,https://api.github.com/repos/golang/go,closed,fmt: documentation unclear regarding %g precision formatting,Documentation,"Current go 1.5 documentation is not clear regarding the %g formatting. In particular, it states

> For floating-point values, width sets the minimum width of the field and precision sets the number of places after the decimal, if appropriate, except that for %g/%G it sets the total number of digits. For example, given 123.45 the format %6.2f prints 123.45 while %.4g prints 123.5. The default precision for %e and %f is 6; for %g it is the smallest number of digits necessary to identify the value uniquely. 

This seems to imply that width for %g/%G is the total number of digits that will be outputted, while it is the number of significant digits, therefore leading zeroes does not contribute to the count. For example, formatting 0.001234 with %.3g will be printed without changes, 0.001234, while from the docs it seems that only 0.001 should be printed.

I propose to change the documentation and change the following:

> except that for %g/%G it sets the total number of digits. For example, given 123.45 the format %6.2f prints 123.45 while %.4g prints 123.5.

with the following (bold used to mark the changes)

> except that for %g/%G it sets the total number of **significant** digits. For example, given 123.45 the format %6.2f prints 123.45 while %.4g prints 123.5**, and 0.00123 is printed as 0.001 by %.3f, but printed as 0.00123 by %.3g**.

Or with a better statement and/or example if the one I provided are not accurate enough.",1.0,"fmt: documentation unclear regarding %g precision formatting - Current go 1.5 documentation is not clear regarding the %g formatting. In particular, it states

> For floating-point values, width sets the minimum width of the field and precision sets the number of places after the decimal, if appropriate, except that for %g/%G it sets the total number of digits. For example, given 123.45 the format %6.2f prints 123.45 while %.4g prints 123.5. The default precision for %e and %f is 6; for %g it is the smallest number of digits necessary to identify the value uniquely. 

This seems to imply that width for %g/%G is the total number of digits that will be outputted, while it is the number of significant digits, therefore leading zeroes does not contribute to the count. For example, formatting 0.001234 with %.3g will be printed without changes, 0.001234, while from the docs it seems that only 0.001 should be printed.

I propose to change the documentation and change the following:

> except that for %g/%G it sets the total number of digits. For example, given 123.45 the format %6.2f prints 123.45 while %.4g prints 123.5.

with the following (bold used to mark the changes)

> except that for %g/%G it sets the total number of **significant** digits. For example, given 123.45 the format %6.2f prints 123.45 while %.4g prints 123.5**, and 0.00123 is printed as 0.001 by %.3f, but printed as 0.00123 by %.3g**.

Or with a better statement and/or example if the one I provided are not accurate enough.",1,fmt  documentation unclear regarding  g precision formatting   current go     documentation is not clear regarding the  g formatting  in particular  it states      for floating point values  width sets the minimum width of the field and precision sets the number of places after the decimal  if appropriate  except that for  g  g it sets the total number of digits  for example  given     the format      prints     while     prints      the default precision for  e and  f is    for  g it is the smallest number of digits necessary to identify the value uniquely      this seems to imply that width for  g  g is the total number of digits that will be outputted  while it is the number of significant digits  therefore leading zeroes does not contribute to the count  for example  formatting     with     will be printed without changes       while from the docs it seems that only     should be printed     i propose to change the documentation and change the following       except that for  g  g it sets the total number of digits  for example  given     the format      prints     while     prints         with the following  bold used to mark the changes       except that for  g  g it sets the total number of   significant   digits  for example  given     the format      prints     while     prints        and     is printed as     by      but printed as     by           or with a better statement and or example if the one i provided are not accurate enough ,1
65645,19620668342.0,IssuesEvent,2022-01-07 05:52:31,pymc-devs/pymc,https://api.github.com/repos/pymc-devs/pymc,closed,Theano Issue with NumPy 1.22.0,defects theano-related v3,"## BLAS issue with the latest release of NumPy

Had this issue directly after importing `pymc3` or `theano`.

<details><summary>Complete error traceback</summary>

```python
Traceback (most recent call last):
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/theano/configparser.py"", line 238, in fetch_val_for_key
    return self._theano_cfg.get(section, option)
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/configparser.py"", line 781, in get
    d = self._unify_values(section, vars)
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/configparser.py"", line 1149, in _unify_values
    raise NoSectionError(section) from None
configparser.NoSectionError: No section: 'blas'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/theano/configparser.py"", line 354, in __get__
    val_str = cls.fetch_val_for_key(self.name, delete_key=delete_key)
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/theano/configparser.py"", line 242, in fetch_val_for_key
    raise KeyError(key)
KeyError: 'blas__ldflags'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File ""<stdin>"", line 1, in <module>
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/pymc3/__init__.py"", line 23, in <module>
    import theano
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/theano/__init__.py"", line 83, in <module>
    from theano import scalar, tensor
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/theano/tensor/__init__.py"", line 20, in <module>
    from theano.tensor import nnet  # used for softmax, sigmoid, etc.
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/theano/tensor/nnet/__init__.py"", line 3, in <module>
    from . import opt
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/theano/tensor/nnet/opt.py"", line 32, in <module>
    from theano.tensor.nnet.conv import ConvOp, conv2d
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/theano/tensor/nnet/conv.py"", line 20, in <module>
    from theano.tensor import blas
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/theano/tensor/blas.py"", line 163, in <module>
    from theano.tensor.blas_headers import blas_header_text, blas_header_version
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/theano/tensor/blas_headers.py"", line 1016, in <module>
    if not config.blas__ldflags:
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/theano/configparser.py"", line 358, in __get__
    val_str = self.default()
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/theano/link/c/cmodule.py"", line 2621, in default_blas_ldflags
    blas_info = numpy.distutils.__config__.blas_opt_info
AttributeError: module 'numpy.distutils.__config__' has no attribute 'blas_opt_info'
```

</details>

## Versions and main components

* PyMC/PyMC3 Version: 3.11.4
* Aesara/Theano Version: 1.1.2
* Python Version: 3.8
* Operating system: macOS Big Sur
* How did you install PyMC/PyMC3: conda
",1.0,"Theano Issue with NumPy 1.22.0 - ## BLAS issue with the latest release of NumPy

Had this issue directly after importing `pymc3` or `theano`.

<details><summary>Complete error traceback</summary>

```python
Traceback (most recent call last):
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/theano/configparser.py"", line 238, in fetch_val_for_key
    return self._theano_cfg.get(section, option)
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/configparser.py"", line 781, in get
    d = self._unify_values(section, vars)
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/configparser.py"", line 1149, in _unify_values
    raise NoSectionError(section) from None
configparser.NoSectionError: No section: 'blas'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/theano/configparser.py"", line 354, in __get__
    val_str = cls.fetch_val_for_key(self.name, delete_key=delete_key)
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/theano/configparser.py"", line 242, in fetch_val_for_key
    raise KeyError(key)
KeyError: 'blas__ldflags'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File ""<stdin>"", line 1, in <module>
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/pymc3/__init__.py"", line 23, in <module>
    import theano
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/theano/__init__.py"", line 83, in <module>
    from theano import scalar, tensor
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/theano/tensor/__init__.py"", line 20, in <module>
    from theano.tensor import nnet  # used for softmax, sigmoid, etc.
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/theano/tensor/nnet/__init__.py"", line 3, in <module>
    from . import opt
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/theano/tensor/nnet/opt.py"", line 32, in <module>
    from theano.tensor.nnet.conv import ConvOp, conv2d
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/theano/tensor/nnet/conv.py"", line 20, in <module>
    from theano.tensor import blas
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/theano/tensor/blas.py"", line 163, in <module>
    from theano.tensor.blas_headers import blas_header_text, blas_header_version
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/theano/tensor/blas_headers.py"", line 1016, in <module>
    if not config.blas__ldflags:
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/theano/configparser.py"", line 358, in __get__
    val_str = self.default()
  File ""/Users/ali.septiandri/anaconda/lib/python3.8/site-packages/theano/link/c/cmodule.py"", line 2621, in default_blas_ldflags
    blas_info = numpy.distutils.__config__.blas_opt_info
AttributeError: module 'numpy.distutils.__config__' has no attribute 'blas_opt_info'
```

</details>

## Versions and main components

* PyMC/PyMC3 Version: 3.11.4
* Aesara/Theano Version: 1.1.2
* Python Version: 3.8
* Operating system: macOS Big Sur
* How did you install PyMC/PyMC3: conda
",0,theano issue with numpy            blas issue with the latest release of numpy    had this issue directly after importing     or  theano        complete error traceback        python  traceback  most recent call last      file   users ali septiandri anaconda lib     site packages theano configparser py   line    in fetch val for key      return self  theano cfg get section  option     file   users ali septiandri anaconda lib     configparser py   line    in get      d   self  unify values section  vars     file   users ali septiandri anaconda lib     configparser py   line    in  unify values      raise nosectionerror section  from none  configparser nosectionerror  no section   blas   during handling of the above exception  another exception occurred   traceback  most recent call last      file   users ali septiandri anaconda lib     site packages theano configparser py   line    in   get        val str   cls fetch val for key self name  delete key delete key     file   users ali septiandri anaconda lib     site packages theano configparser py   line    in fetch val for key      raise keyerror key   keyerror   blas  ldflags   during handling of the above exception  another exception occurred   traceback  most recent call last      file      line    in      file   users ali septiandri anaconda lib     site packages     init   py   line    in        import theano    file   users ali septiandri anaconda lib     site packages theano   init   py   line    in        from theano import scalar  tensor    file   users ali septiandri anaconda lib     site packages theano tensor   init   py   line    in        from theano tensor import nnet    used for softmax  sigmoid  etc     file   users ali septiandri anaconda lib     site packages theano tensor nnet   init   py   line    in        from   import opt    file   users ali septiandri anaconda lib     site packages theano tensor nnet opt py   line    in        from theano tensor nnet conv import convop       file   users ali septiandri anaconda lib     site packages theano tensor nnet conv py   line    in        from theano tensor import blas    file   users ali septiandri anaconda lib     site packages theano tensor blas py   line    in        from theano tensor blas headers import blas header text  blas header version    file   users ali septiandri anaconda lib     site packages theano tensor blas headers py   line    in        if not config blas  ldflags     file   users ali septiandri anaconda lib     site packages theano configparser py   line    in   get        val str   self default      file   users ali septiandri anaconda lib     site packages theano link c cmodule py   line    in default blas ldflags      blas info   numpy distutils   config   blas opt info  attributeerror  module  numpy distutils   config    has no attribute  blas opt info                  versions and main components      pymc   version           aesara theano version           python version         operating system  macos big sur    how did you install pymc    conda  ,0
348273,24910256349.0,IssuesEvent,2022-10-29 19:23:59,golang/go,https://api.github.com/repos/golang/go,opened,x/website: newer examples for security policy PRIVATE issues,Documentation website,"The security policy page https://go.dev/security/policy lists examples of PRIVATE issues.
These are examples listed in the new security policy discussion #44918 , before the policy was in place.

I've witnessed confusion on what PRIVATE means, as some of the issues listed there were open for quite some time before being fixed.

Newer PRIVATE issues follow a different process with placeholder issues linking to a private tracker that is updated when it becomes public, ex: #53416 #53616 #54658 #56284 .

The security policy would benefit from newer examples that follow the process laid out by it.

cc @golang/security 

",1.0,"x/website: newer examples for security policy PRIVATE issues - The security policy page https://go.dev/security/policy lists examples of PRIVATE issues.
These are examples listed in the new security policy discussion #44918 , before the policy was in place.

I've witnessed confusion on what PRIVATE means, as some of the issues listed there were open for quite some time before being fixed.

Newer PRIVATE issues follow a different process with placeholder issues linking to a private tracker that is updated when it becomes public, ex: #53416 #53616 #54658 #56284 .

The security policy would benefit from newer examples that follow the process laid out by it.

cc @golang/security 

",1,x website  newer examples for security policy private issues   the security policy page   lists examples of private issues   these are examples listed in the new security policy discussion      before the policy was in place     i ve witnessed confusion on what private means  as some of the issues listed there were open for quite some time before being fixed     newer private issues follow a different process with placeholder issues linking to a private tracker that is updated when it becomes public  ex                   the security policy would benefit from newer examples that follow the process laid out by it     cc  golang security     ,1
387041,11455035403.0,IssuesEvent,2020-02-06 18:16:06,HackIllinois/android,https://api.github.com/repos/HackIllinois/android,closed,Homepage shows UPCOMING when there are no upcoming events,UI bug bug priority,We shouldn't include this if it's empty,1.0,Homepage shows UPCOMING when there are no upcoming events - We shouldn't include this if it's empty,0,homepage shows upcoming when there are no upcoming events   we shouldn t include this if it s empty,0
52037,7744100769.0,IssuesEvent,2018-05-29 14:34:26,golang/go,https://api.github.com/repos/golang/go,closed,Doc: State that Request.ParseForm() does not parse JSON payloads,Documentation,"### What did you expect to see?

I spent a good deal of time trying to determine why my XHR-style ""forms"" (actually JSON) were coming in blank.

### What did you see instead?

After much debugging, head-desking, and searching, I discovered that this doesn't work that way. I've learned, but other people who have used other server frameworks may make the same mistake I did. In fact, I discovered it on Stack Overflow through someone else having the same problem.

I realize that a change to `ParseForm` would need to go through the language change proposal process. Obviously, nothing needs to be added to the language to be able to parse JSON payloads. However, I believe that a short note in [this comment](https://github.com/golang/go/blob/master/src/net/http/request.go#L1143) would help people understand that they'll need to parse JSON bodies themselves.

I'd be happy to update the comment to that effect, but before I go through that effort, I wanted to ask the team if that sort of thing would be welcome. So - let me know. :) (and thank you for your time)
",1.0,"Doc: State that Request.ParseForm() does not parse JSON payloads - ### What did you expect to see?

I spent a good deal of time trying to determine why my XHR-style ""forms"" (actually JSON) were coming in blank.

### What did you see instead?

After much debugging, head-desking, and searching, I discovered that this doesn't work that way. I've learned, but other people who have used other server frameworks may make the same mistake I did. In fact, I discovered it on Stack Overflow through someone else having the same problem.

I realize that a change to `ParseForm` would need to go through the language change proposal process. Obviously, nothing needs to be added to the language to be able to parse JSON payloads. However, I believe that a short note in [this comment](https://github.com/golang/go/blob/master/src/net/http/request.go#L1143) would help people understand that they'll need to parse JSON bodies themselves.

I'd be happy to update the comment to that effect, but before I go through that effort, I wanted to ask the team if that sort of thing would be welcome. So - let me know. :) (and thank you for your time)
",1,doc  state that request parseform   does not parse json payloads       what did you expect to see     i spent a good deal of time trying to determine why my xhr style  forms   actually json  were coming in blank         what did you see instead     after much debugging  head desking  and searching  i discovered that this doesn t work that way  i ve learned  but other people who have used other server frameworks may make the same mistake i did  in fact  i discovered it on stack overflow through someone else having the same problem     i realize that a change to  parseform  would need to go through the language change proposal process  obviously  nothing needs to be added to the language to be able to parse json payloads  however  i believe that a short note in     would help people understand that they ll need to parse json bodies themselves     i d be happy to update the comment to that effect  but before i go through that effort  i wanted to ask the team if that sort of thing would be welcome  so   let me know      and thank you for your time   ,1
58839,8306417044.0,IssuesEvent,2018-09-22 18:30:59,golang/go,https://api.github.com/repos/golang/go,closed,doc: mention how to add GOPATH\bin to PATH for Windows users,Documentation NeedsFix OS-Windows,[GOPATH variable section](https://tip.golang.org/doc/code.html#GOPATH) is not mentioning that GOPATH\bin needs to be added to PATH for convince. Create a wiki page with platform specific instructions how to add the bin directory to the PATH and add instructions for Windows.,1.0,doc: mention how to add GOPATH\bin to PATH for Windows users - [GOPATH variable section](https://tip.golang.org/doc/code.html#GOPATH) is not mentioning that GOPATH\bin needs to be added to PATH for convince. Create a wiki page with platform specific instructions how to add the bin directory to the PATH and add instructions for Windows.,1,doc  mention how to add gopath bin to path for windows users       is not mentioning that gopath bin needs to be added to path for convince  create a wiki page with platform specific instructions how to add the bin directory to the path and add instructions for windows ,1
214675,16604164675.0,IssuesEvent,2021-06-02 00:28:10,microsoft/azure-pipelines-tasks,https://api.github.com/repos/microsoft/azure-pipelines-tasks,closed,PublishTestResult does not show where the error was,Area: Test Area: TestManagement enhancement stale,"## Required Information

**Question, Bug, or Feature?**  
*Type*: Feature

This seems such a basic functionality which is missing that I'm tempted to call it a bug: Test results don't currently show which file/class failed!

**Enter Task Name**: Publish Test Results
lines-tasks/tree/master/Tasks

## Environment
- Server - Azure Pipelines
       
    - If using Azure Pipelines, provide the account name, team project name, build definition name/build number: Sensitive information **********

## Issue Description

As you can see it's currently not possible to see where (in what file) a test failed:
![image](https://user-images.githubusercontent.com/498834/99297354-71fb8f00-2848-11eb-8405-d5c8a0221aa9.png)

The `classname` information (see XML output below) is just missing.

## XML Junit Output
```xml
<testsuite package=""org.eslint"" time=""0"" tests=""1"" errors=""1"" name=""/home/vsts/work/1/s/some/component.vue"">
  <testcase time=""0"" name=""org.eslint.no-trailing-spaces"" classname=""/home/vsts/work/1/s/some/component"">
    <failure message=""Trailing spaces not allowed."">
      <![CDATA[line 147, col 23, Error - Trailing spaces not allowed. (no-trailing-spaces)]]>
    </failure>
  </testcase>
</testsuite>
```

## To Reproduce
```
npx vue-cli-service lint --max-warnings 0 --no-fix --silent --format junit > junit.xml
```",2.0,"PublishTestResult does not show where the error was - ## Required Information

**Question, Bug, or Feature?**  
*Type*: Feature

This seems such a basic functionality which is missing that I'm tempted to call it a bug: Test results don't currently show which file/class failed!

**Enter Task Name**: Publish Test Results
lines-tasks/tree/master/Tasks

## Environment
- Server - Azure Pipelines
       
    - If using Azure Pipelines, provide the account name, team project name, build definition name/build number: Sensitive information **********

## Issue Description

As you can see it's currently not possible to see where (in what file) a test failed:
![image](https://user-images.githubusercontent.com/498834/99297354-71fb8f00-2848-11eb-8405-d5c8a0221aa9.png)

The `classname` information (see XML output below) is just missing.

## XML Junit Output
```xml
<testsuite package=""org.eslint"" time=""0"" tests=""1"" errors=""1"" name=""/home/vsts/work/1/s/some/component.vue"">
  <testcase time=""0"" name=""org.eslint.no-trailing-spaces"" classname=""/home/vsts/work/1/s/some/component"">
    <failure message=""Trailing spaces not allowed."">
      <![CDATA[line 147, col 23, Error - Trailing spaces not allowed. (no-trailing-spaces)]]>
    </failure>
  </testcase>
</testsuite>
```

## To Reproduce
```
npx vue-cli-service lint --max-warnings 0 --no-fix --silent --format junit > junit.xml
```",0,publishtestresult does not show where the error was      required information      question  bug  or feature        type   feature    this seems such a basic functionality which is missing that i m tempted to call it a bug  test results don t currently show which file class failed       enter task name    publish test results  lines tasks tree master tasks       environment    server   azure pipelines                 if using azure pipelines  provide the account name  team project name  build definition name build number  sensitive information                  issue description    as you can see it s currently not possible to see where  in what file  a test failed           the  classname  information  see xml output below  is just missing        xml junit output     xml                                                   to reproduce       npx vue cli service lint   max warnings     no fix   silent   format junit   junit xml     ,0
36832,6552416210.0,IssuesEvent,2017-09-05 18:16:24,golang/go,https://api.github.com/repos/golang/go,reopened,"time: Round(0), Truncate(0) strip monotonic clock readings but documentation still says it returns t unchanged",Documentation NeedsFix,"Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?

go version go1.9rc2 darwin/amd64

this does not happen, for contrast, with go1.8.3 darwin/amd64

This change is documented at the top of the new go1.9rc2 time/time.go file:

~~~
// For debugging, the result of t.String does include the monotonic                                             
// clock reading if present. If t != u because of different monotonic clock readings,                           
// that difference will be visible when printing t.String() and u.String().                                     
~~~

This is actually a rather drastic proposed change. I refer not the use of the monotone clock, but the display of it in timestamps formated via String(). Many of us use String() for many purposes other than debugging. For debugging, a separate new StringWithMonotone() should be provided.

### What operating system and processor architecture are you using (`go env`)?

go env:
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/jaten/go""
GORACE=""""
GOROOT=""/usr/local/go1.9rc2""
GOTOOLDIR=""/usr/local/go1.9rc2/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/6s/zdc0hvvx7kqcglg5yqm3kl4r0000gn/T/go-build055854381=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""


### What did you do?

Here code to reproduce the issue, `serialize_time.go`. It is extracted from the time.Time serialization in a popular msgpack serialization package. e.g. getunix() and putunix() are here https://github.com/tinylib/msgp/blob/ad0ff2e232ad2e37faf67087fb24bf8d04a8ce20/msgp/integers.go#L113

~~~
package main

import (
	""fmt""
	""time""
)

func main() {

	// time to bytes
	t := time.Now()
	fmt.Printf(""original  t='%s'\n"", t.String())
	t = t.UTC()
	fmt.Printf(""original  t='%s' in UTC\n"", t.String())
	var b [12]byte
	putUnix(b[:], t.Unix(), int32(t.Nanosecond()))

	// bytes to time:
	sec, nsec := getUnix(b[:])
	t2 := time.Unix(sec, int64(nsec)).Local()

	fmt.Printf(""restored t2='%s'\n"", t2.String())
}

/* output of main:

original  t='2017-08-16 19:35:41.958759249 -0400 EDT m=+0.000241395'
original  t='2017-08-16 23:35:41.958759249 +0000 UTC' in UTC
restored t2='2017-08-16 19:35:41.958759249 -0400 EDT'

*/

func getUnix(b []byte) (sec int64, nsec int32) {
	sec = (int64(b[0]) << 56) | (int64(b[1]) << 48) |
		(int64(b[2]) << 40) | (int64(b[3]) << 32) |
		(int64(b[4]) << 24) | (int64(b[5]) << 16) |
		(int64(b[6]) << 8) | (int64(b[7]))

	nsec = (int32(b[8]) << 24) | (int32(b[9]) << 16) | (int32(b[10]) << 8) | (int32(b[11]))
	return
}

func putUnix(b []byte, sec int64, nsec int32) {
	b[0] = byte(sec >> 56)
	b[1] = byte(sec >> 48)
	b[2] = byte(sec >> 40)
	b[3] = byte(sec >> 32)
	b[4] = byte(sec >> 24)
	b[5] = byte(sec >> 16)
	b[6] = byte(sec >> 8)
	b[7] = byte(sec)
	b[8] = byte(nsec >> 24)
	b[9] = byte(nsec >> 16)
	b[10] = byte(nsec >> 8)
	b[11] = byte(nsec)
}
~~~

In summary, in go1.9rc2, time.Time.String() may produce:

`2017-08-16 18:41:39.184829495 -0400 EDT m=+0.057013769` 

whereas in go1.83, the String() applied to the same value produces always:

`2017-08-16 18:41:39.184829495 -0400 EDT`

While not a language consistency issue, this is a backwards-compatibility issue for programs that expected one thing from their time.Time values. For example, my tests in a fork of the tinylib/msgp lib cited above are suddenly broken under go1.9rc2.  So these changes may break many programs unexpectedly when moving from go1.8.3 to go1.9.

I'm glad for the new monotonic time feature under the covers, as it solves bugs with walltime going through leap seconds, but does it have to surface itself into the string representation of time in a non-backcompatible way? For the new info, how about adding a separate stringification method if one needs both timestamps?  Perhaps: StringWithMonotone() alongside the old fashioned String().

In summary, while useful, features meant for debugging the new time.Time values should not break backwards compatibility, when they can trivially be provided alongside in a separate new method.",1.0,"time: Round(0), Truncate(0) strip monotonic clock readings but documentation still says it returns t unchanged - Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?

go version go1.9rc2 darwin/amd64

this does not happen, for contrast, with go1.8.3 darwin/amd64

This change is documented at the top of the new go1.9rc2 time/time.go file:

~~~
// For debugging, the result of t.String does include the monotonic                                             
// clock reading if present. If t != u because of different monotonic clock readings,                           
// that difference will be visible when printing t.String() and u.String().                                     
~~~

This is actually a rather drastic proposed change. I refer not the use of the monotone clock, but the display of it in timestamps formated via String(). Many of us use String() for many purposes other than debugging. For debugging, a separate new StringWithMonotone() should be provided.

### What operating system and processor architecture are you using (`go env`)?

go env:
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/jaten/go""
GORACE=""""
GOROOT=""/usr/local/go1.9rc2""
GOTOOLDIR=""/usr/local/go1.9rc2/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/6s/zdc0hvvx7kqcglg5yqm3kl4r0000gn/T/go-build055854381=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""


### What did you do?

Here code to reproduce the issue, `serialize_time.go`. It is extracted from the time.Time serialization in a popular msgpack serialization package. e.g. getunix() and putunix() are here https://github.com/tinylib/msgp/blob/ad0ff2e232ad2e37faf67087fb24bf8d04a8ce20/msgp/integers.go#L113

~~~
package main

import (
	""fmt""
	""time""
)

func main() {

	// time to bytes
	t := time.Now()
	fmt.Printf(""original  t='%s'\n"", t.String())
	t = t.UTC()
	fmt.Printf(""original  t='%s' in UTC\n"", t.String())
	var b [12]byte
	putUnix(b[:], t.Unix(), int32(t.Nanosecond()))

	// bytes to time:
	sec, nsec := getUnix(b[:])
	t2 := time.Unix(sec, int64(nsec)).Local()

	fmt.Printf(""restored t2='%s'\n"", t2.String())
}

/* output of main:

original  t='2017-08-16 19:35:41.958759249 -0400 EDT m=+0.000241395'
original  t='2017-08-16 23:35:41.958759249 +0000 UTC' in UTC
restored t2='2017-08-16 19:35:41.958759249 -0400 EDT'

*/

func getUnix(b []byte) (sec int64, nsec int32) {
	sec = (int64(b[0]) << 56) | (int64(b[1]) << 48) |
		(int64(b[2]) << 40) | (int64(b[3]) << 32) |
		(int64(b[4]) << 24) | (int64(b[5]) << 16) |
		(int64(b[6]) << 8) | (int64(b[7]))

	nsec = (int32(b[8]) << 24) | (int32(b[9]) << 16) | (int32(b[10]) << 8) | (int32(b[11]))
	return
}

func putUnix(b []byte, sec int64, nsec int32) {
	b[0] = byte(sec >> 56)
	b[1] = byte(sec >> 48)
	b[2] = byte(sec >> 40)
	b[3] = byte(sec >> 32)
	b[4] = byte(sec >> 24)
	b[5] = byte(sec >> 16)
	b[6] = byte(sec >> 8)
	b[7] = byte(sec)
	b[8] = byte(nsec >> 24)
	b[9] = byte(nsec >> 16)
	b[10] = byte(nsec >> 8)
	b[11] = byte(nsec)
}
~~~

In summary, in go1.9rc2, time.Time.String() may produce:

`2017-08-16 18:41:39.184829495 -0400 EDT m=+0.057013769` 

whereas in go1.83, the String() applied to the same value produces always:

`2017-08-16 18:41:39.184829495 -0400 EDT`

While not a language consistency issue, this is a backwards-compatibility issue for programs that expected one thing from their time.Time values. For example, my tests in a fork of the tinylib/msgp lib cited above are suddenly broken under go1.9rc2.  So these changes may break many programs unexpectedly when moving from go1.8.3 to go1.9.

I'm glad for the new monotonic time feature under the covers, as it solves bugs with walltime going through leap seconds, but does it have to surface itself into the string representation of time in a non-backcompatible way? For the new info, how about adding a separate stringification method if one needs both timestamps?  Perhaps: StringWithMonotone() alongside the old fashioned String().

In summary, while useful, features meant for debugging the new time.Time values should not break backwards compatibility, when they can trivially be provided alongside in a separate new method.",1,time  round     truncate    strip monotonic clock readings but documentation still says it returns t unchanged   please answer these questions before submitting your issue  thanks         what version of go are you using   go version       go version     darwin      this does not happen  for contrast  with       darwin      this change is documented at the top of the new     time time go file             for debugging  the result of t string does include the monotonic                                                  clock reading if present  if t    u because of different monotonic clock readings                                 that difference will be visible when printing t string   and u string                                                 this is actually a rather drastic proposed change  i refer not the use of the monotone clock  but the display of it in timestamps formated via string    many of us use string   for many purposes other than debugging  for debugging  a separate new stringwithmonotone   should be provided         what operating system and processor architecture are you using   go env       go env   goarch      gobin     goexe     gohostarch      gohostos  darwin   goos  darwin   gopath   users jaten go   gorace     goroot   usr local       gotooldir   usr local     pkg tool darwin     gccgo  gccgo   cc  clang   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders     t go    tmp go build  gno record gcc switches  fno common   cxx  clang     cgo enabled      cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config           what did you do     here code to reproduce the issue   serialize time go   it is extracted from the time time serialization in a popular msgpack serialization package  e g  getunix   and putunix   are here           package main    import    	 fmt   	 time        func main        	   time to bytes  	t    time now    	fmt printf  original  t   s  n   t string     	t   t utc    	fmt printf  original  t   s  in utc n   t string     	var b  byte  	putunix b   t unix      t nanosecond        	   bytes to time   	sec  nsec    getunix b    	     time unix sec    nsec   local      	fmt printf  restored     s  n     string             output of main     original  t                   edt m        original  t                   utc  in utc  restored                     edt           func getunix b  byte   sec    nsec       	sec      b              b            		   b              b            		   b              b            		   b              b       	nsec      b              b              b              b     	return       func putunix b  byte  sec    nsec       	b    byte sec        	b    byte sec        	b    byte sec        	b    byte sec        	b    byte sec        	b    byte sec        	b    byte sec        	b    byte sec   	b    byte nsec        	b    byte nsec        	b    byte nsec        	b    byte nsec             in summary  in      time time string   may produce                       edt m           whereas in      the string   applied to the same value produces always                       edt     while not a language consistency issue  this is a backwards compatibility issue for programs that expected one thing from their time time values  for example  my tests in a fork of the tinylib msgp lib cited above are suddenly broken under       so these changes may break many programs unexpectedly when moving from       to         i m glad for the new monotonic time feature under the covers  as it solves bugs with walltime going through leap seconds  but does it have to surface itself into the string representation of time in a non backcompatible way  for the new info  how about adding a separate stringification method if one needs both timestamps   perhaps  stringwithmonotone   alongside the old fashioned string       in summary  while useful  features meant for debugging the new time time values should not break backwards compatibility  when they can trivially be provided alongside in a separate new method ,1
693764,23789676807.0,IssuesEvent,2022-09-02 13:29:14,thin-edge/community,https://api.github.com/repos/thin-edge/community,closed,build and sync community,Ongoing to do high priority,"here an initial  list of actions which should be taken. created by Phil and Hans Based on discussions during thin-edge.io summit in Dusseldorf.

(this will be split in issues with priorityand assignees)

[Actions community sync .docx](https://github.com/thin-edge/community/files/9138025/Actions.community.sync.docx)
",1.0,"build and sync community - here an initial  list of actions which should be taken. created by Phil and Hans Based on discussions during thin-edge.io summit in Dusseldorf.

(this will be split in issues with priorityand assignees)

[Actions community sync .docx](https://github.com/thin-edge/community/files/9138025/Actions.community.sync.docx)
",0,build and sync community   here an initial  list of actions which should be taken  created by phil and hans based on discussions during thin edge io summit in dusseldorf      this will be split in issues with priorityand assignees          ,0
136506,18739704763.0,IssuesEvent,2021-11-04 12:11:59,samisalamiws/gradle-with-private-dep,https://api.github.com/repos/samisalamiws/gradle-with-private-dep,opened,CVE-2021-25329 (High) detected in tomcat-embed-core-9.0.2.jar,security vulnerability,"## CVE-2021-25329 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tomcat-embed-core-9.0.2.jar</b></p></summary>

<p>Core Tomcat implementation</p>
<p>Library home page: <a href=""http://tomcat.apache.org/"">http://tomcat.apache.org/</a></p>
<p>Path to dependency file: gradle-with-private-dep/ProjectDependencieesVul/ATproject/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.tomcat.embed/tomcat-embed-core/9.0.2/3cfebe91cb7917a203f3a7d0cefc314dbb59c74/tomcat-embed-core-9.0.2.jar</p>
<p>

Dependency Hierarchy:
  - tomcat-embed-jasper-9.0.2.jar (Root Library)
    - :x: **tomcat-embed-core-9.0.2.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samisalamiws/gradle-with-private-dep/commit/2e7af6009593feb19f20391ff3d59022ea3cefc5"">2e7af6009593feb19f20391ff3d59022ea3cefc5</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>  
  
The fix for CVE-2020-9484 was incomplete. When using Apache Tomcat 10.0.0-M1 to 10.0.0, 9.0.0.M1 to 9.0.41, 8.5.0 to 8.5.61 or 7.0.0. to 7.0.107 with a configuration edge case that was highly unlikely to be used, the Tomcat instance was still vulnerable to CVE-2020-9494. Note that both the previously published prerequisites for CVE-2020-9484 and the previously published mitigations for CVE-2020-9484 also apply to this issue.

<p>Publish Date: 2021-03-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-25329>CVE-2021-25329</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.0</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: High
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: 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://lists.apache.org/thread.html/rfe62fbf9d4c314f166fe8c668e50e5d9dd882a99447f26f0367474bf%40%3Cannounce.tomcat.apache.org%3E"">https://lists.apache.org/thread.html/rfe62fbf9d4c314f166fe8c668e50e5d9dd882a99447f26f0367474bf%40%3Cannounce.tomcat.apache.org%3E</a></p>
<p>Release Date: 2021-03-01</p>
<p>Fix Resolution: org.apache.tomcat:tomcat:7.0.108, org.apache.tomcat:tomcat:8.5.63, org.apache.tomcat:tomcat:9.0.43,org.apache.tomcat:tomcat:10.0.2</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":false,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""org.apache.tomcat.embed"",""packageName"":""tomcat-embed-core"",""packageVersion"":""9.0.2"",""packageFilePaths"":[""/ProjectDependencieesVul/ATproject/build.gradle""],""isTransitiveDependency"":true,""dependencyTree"":""org.apache.tomcat.embed:tomcat-embed-jasper:9.0.2;org.apache.tomcat.embed:tomcat-embed-core:9.0.2"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""org.apache.tomcat:tomcat:7.0.108, org.apache.tomcat:tomcat:8.5.63, org.apache.tomcat:tomcat:9.0.43,org.apache.tomcat:tomcat:10.0.2""}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2021-25329"",""vulnerabilityDetails"":""The fix for CVE-2020-9484 was incomplete. When using Apache Tomcat 10.0.0-M1 to 10.0.0, 9.0.0.M1 to 9.0.41, 8.5.0 to 8.5.61 or 7.0.0. to 7.0.107 with a configuration edge case that was highly unlikely to be used, the Tomcat instance was still vulnerable to CVE-2020-9494. Note that both the previously published prerequisites for CVE-2020-9484 and the previously published mitigations for CVE-2020-9484 also apply to this issue."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-25329"",""cvss3Severity"":""high"",""cvss3Score"":""7.0"",""cvss3Metrics"":{""A"":""High"",""AC"":""High"",""PR"":""Low"",""S"":""Unchanged"",""C"":""High"",""UI"":""None"",""AV"":""Local"",""I"":""High""},""extraData"":{}}</REMEDIATE> -->",True,"CVE-2021-25329 (High) detected in tomcat-embed-core-9.0.2.jar - ## CVE-2021-25329 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tomcat-embed-core-9.0.2.jar</b></p></summary>

<p>Core Tomcat implementation</p>
<p>Library home page: <a href=""http://tomcat.apache.org/"">http://tomcat.apache.org/</a></p>
<p>Path to dependency file: gradle-with-private-dep/ProjectDependencieesVul/ATproject/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.tomcat.embed/tomcat-embed-core/9.0.2/3cfebe91cb7917a203f3a7d0cefc314dbb59c74/tomcat-embed-core-9.0.2.jar</p>
<p>

Dependency Hierarchy:
  - tomcat-embed-jasper-9.0.2.jar (Root Library)
    - :x: **tomcat-embed-core-9.0.2.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samisalamiws/gradle-with-private-dep/commit/2e7af6009593feb19f20391ff3d59022ea3cefc5"">2e7af6009593feb19f20391ff3d59022ea3cefc5</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>  
  
The fix for CVE-2020-9484 was incomplete. When using Apache Tomcat 10.0.0-M1 to 10.0.0, 9.0.0.M1 to 9.0.41, 8.5.0 to 8.5.61 or 7.0.0. to 7.0.107 with a configuration edge case that was highly unlikely to be used, the Tomcat instance was still vulnerable to CVE-2020-9494. Note that both the previously published prerequisites for CVE-2020-9484 and the previously published mitigations for CVE-2020-9484 also apply to this issue.

<p>Publish Date: 2021-03-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-25329>CVE-2021-25329</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.0</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: High
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: 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://lists.apache.org/thread.html/rfe62fbf9d4c314f166fe8c668e50e5d9dd882a99447f26f0367474bf%40%3Cannounce.tomcat.apache.org%3E"">https://lists.apache.org/thread.html/rfe62fbf9d4c314f166fe8c668e50e5d9dd882a99447f26f0367474bf%40%3Cannounce.tomcat.apache.org%3E</a></p>
<p>Release Date: 2021-03-01</p>
<p>Fix Resolution: org.apache.tomcat:tomcat:7.0.108, org.apache.tomcat:tomcat:8.5.63, org.apache.tomcat:tomcat:9.0.43,org.apache.tomcat:tomcat:10.0.2</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":false,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""org.apache.tomcat.embed"",""packageName"":""tomcat-embed-core"",""packageVersion"":""9.0.2"",""packageFilePaths"":[""/ProjectDependencieesVul/ATproject/build.gradle""],""isTransitiveDependency"":true,""dependencyTree"":""org.apache.tomcat.embed:tomcat-embed-jasper:9.0.2;org.apache.tomcat.embed:tomcat-embed-core:9.0.2"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""org.apache.tomcat:tomcat:7.0.108, org.apache.tomcat:tomcat:8.5.63, org.apache.tomcat:tomcat:9.0.43,org.apache.tomcat:tomcat:10.0.2""}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2021-25329"",""vulnerabilityDetails"":""The fix for CVE-2020-9484 was incomplete. When using Apache Tomcat 10.0.0-M1 to 10.0.0, 9.0.0.M1 to 9.0.41, 8.5.0 to 8.5.61 or 7.0.0. to 7.0.107 with a configuration edge case that was highly unlikely to be used, the Tomcat instance was still vulnerable to CVE-2020-9494. Note that both the previously published prerequisites for CVE-2020-9484 and the previously published mitigations for CVE-2020-9484 also apply to this issue."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-25329"",""cvss3Severity"":""high"",""cvss3Score"":""7.0"",""cvss3Metrics"":{""A"":""High"",""AC"":""High"",""PR"":""Low"",""S"":""Unchanged"",""C"":""High"",""UI"":""None"",""AV"":""Local"",""I"":""High""},""extraData"":{}}</REMEDIATE> -->",0,cve      high  detected in tomcat embed core       jar      cve       high severity vulnerability     vulnerable library    tomcat embed core       jar      core tomcat implementation   library home page   a href     path to dependency file  gradle with private dep projectdependencieesvul atproject build gradle   path to vulnerable library   home wss scanner  gradle caches modules   files     org apache tomcat embed tomcat embed core         tomcat embed core       jar     dependency hierarchy      tomcat embed jasper       jar  root library         x    tomcat embed core       jar    vulnerable library   found in head commit   a href     found in base branch   main              vulnerability details         the fix for cve     was incomplete  when using apache tomcat         to                to              to       or        to       with a configuration edge case that was highly unlikely to be used  the tomcat instance was still vulnerable to cve      note that both the previously published prerequisites for cve     and the previously published mitigations for cve     also apply to this issue    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  local     attack complexity  high     privileges required  low     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  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 tomcat tomcat        org apache tomcat tomcat        org apache tomcat tomcat       org apache tomcat tomcat                    isopenpronvulnerability  false  ispackagebased  true  isdefaultbranch  true  packages     istransitivedependency  true  dependencytree   org apache tomcat embed tomcat embed jasper       org apache tomcat embed tomcat embed core         isminimumfixversionavailable  true  minimumfixversion   org apache tomcat tomcat        org apache tomcat tomcat        org apache tomcat tomcat       org apache tomcat tomcat           basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   the fix for cve     was incomplete  when using apache tomcat         to                to              to       or        to       with a configuration edge case that was highly unlikely to be used  the tomcat instance was still vulnerable to cve      note that both the previously published prerequisites for cve     and the previously published mitigations for cve     also apply to this issue    vulnerabilityurl        ,0
162420,20188222252.0,IssuesEvent,2022-02-11 01:19:19,samq-ghdemo/Java-Demo,https://api.github.com/repos/samq-ghdemo/Java-Demo,opened,esapi-2.1.0.1.jar: 16 vulnerabilities (highest severity is: 9.8),security vulnerability,"<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>esapi-2.1.0.1.jar</b></p></summary>

<p></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-fileupload/commons-fileupload/1.3.1/commons-fileupload-1.3.1.jar</p>
<p>


<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p></details>

## Vulnerabilities

| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2016-1000031](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-1000031) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | commons-fileupload-1.3.1.jar | Transitive | N/A | ❌ |
| [CVE-2016-2510](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2510) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.1 | bsh-core-2.0b4.jar | Transitive | N/A | ❌ |
| [CVE-2016-3092](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-3092) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | commons-fileupload-1.3.1.jar | Transitive | N/A | ❌ |
| [CVE-2012-0881](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-0881) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | xercesImpl-2.8.0.jar | Transitive | N/A | ❌ |
| [WS-2014-0034](https://commons.apache.org/proper/commons-fileupload/changes-report.html) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | commons-fileupload-1.3.1.jar | Transitive | N/A | ❌ |
| [CVE-2014-0107](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-0107) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.3 | xalan-2.7.0.jar | Transitive | N/A | ❌ |
| [CVE-2019-10086](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10086) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.3 | commons-beanutils-core-1.8.3.jar | Transitive | N/A | ❌ |
| [CVE-2014-0114](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-0114) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.3 | commons-beanutils-core-1.8.3.jar | Transitive | N/A | ❌ |
| [CVE-2022-23437](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23437) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | xercesImpl-2.8.0.jar | Transitive | N/A | ❌ |
| [CVE-2016-10006](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-10006) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | antisamy-1.5.3.jar | Transitive | N/A | ❌ |
| [CVE-2021-35043](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35043) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | antisamy-1.5.3.jar | Transitive | N/A | ❌ |
| [CVE-2017-14735](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-14735) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | antisamy-1.5.3.jar | Transitive | N/A | ❌ |
| [CVE-2013-4002](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-4002) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.9 | xercesImpl-2.8.0.jar | Transitive | N/A | ❌ |
| [CVE-2009-2625](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2009-2625) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | xercesImpl-2.8.0.jar | Transitive | N/A | ❌ |
| [CVE-2021-29425](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29425) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 4.8 | commons-io-2.2.jar | Transitive | N/A | ❌ |
| [CVE-2012-5783](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-5783) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low | 3.7 | commons-httpclient-3.1.jar | Transitive | N/A | ❌ |


## Details

<details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2016-1000031</summary>


###  Vulnerable Library - <b>commons-fileupload-1.3.1.jar</b></p>

<p>The Apache Commons FileUpload component provides a simple yet flexible means of adding support for multipart
    file upload functionality to servlets and web applications.</p>
<p>Library home page: <a href=""http://commons.apache.org/proper/commons-fileupload/"">http://commons.apache.org/proper/commons-fileupload/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-fileupload/commons-fileupload/1.3.1/commons-fileupload-1.3.1.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - :x: **commons-fileupload-1.3.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
Apache Commons FileUpload before 1.3.3 DiskFileItem File Manipulation Remote Code Execution

<p>Publish Date: 2016-10-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-1000031>CVE-2016-1000031</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>9.8</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: 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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000031"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000031</a></p>
<p>Release Date: 2016-10-25</p>
<p>Fix Resolution: 1.3.3</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2016-2510</summary>


###  Vulnerable Library - <b>bsh-core-2.0b4.jar</b></p>

<p>BeanShell core</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/beanshell/bsh-core/2.0b4/bsh-core-2.0b4.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - :x: **bsh-core-2.0b4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
BeanShell (bsh) before 2.0b6, when included on the classpath by an application that uses Java serialization or XStream, allows remote attackers to execute arbitrary code via crafted serialized data, related to XThis.Handler.

<p>Publish Date: 2016-04-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2510>CVE-2016-2510</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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://nvd.nist.gov/vuln/detail/CVE-2016-2510"">https://nvd.nist.gov/vuln/detail/CVE-2016-2510</a></p>
<p>Release Date: 2016-04-07</p>
<p>Fix Resolution: 2.0b6</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2016-3092</summary>


###  Vulnerable Library - <b>commons-fileupload-1.3.1.jar</b></p>

<p>The Apache Commons FileUpload component provides a simple yet flexible means of adding support for multipart
    file upload functionality to servlets and web applications.</p>
<p>Library home page: <a href=""http://commons.apache.org/proper/commons-fileupload/"">http://commons.apache.org/proper/commons-fileupload/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-fileupload/commons-fileupload/1.3.1/commons-fileupload-1.3.1.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - :x: **commons-fileupload-1.3.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
The MultipartStream class in Apache Commons Fileupload before 1.3.2, as used in Apache Tomcat 7.x before 7.0.70, 8.x before 8.0.36, 8.5.x before 8.5.3, and 9.x before 9.0.0.M7 and other products, allows remote attackers to cause a denial of service (CPU consumption) via a long boundary string.

<p>Publish Date: 2016-07-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-3092>CVE-2016-3092</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3092"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3092</a></p>
<p>Release Date: 2016-07-04</p>
<p>Fix Resolution: org.apache.tomcat.embed:tomcat-embed-core:9.0.0.M8,8.5.3,8.0.36,7.0.70,org.apache.tomcat:tomcat-coyote:9.0.0.M8,8.5.3,8.0.36,7.0.70,commons-fileupload:commons-fileupload:1.3.2</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2012-0881</summary>


###  Vulnerable Library - <b>xercesImpl-2.8.0.jar</b></p>

<p>Xerces2 is the next generation of high performance, fully compliant XML parsers in the
    Apache Xerces family. This new version of Xerces introduces the Xerces Native Interface (XNI),
    a complete framework for building parser components and configurations that is extremely
    modular and easy to program.</p>
<p>Library home page: <a href=""http://xerces.apache.org/xerces2-j"">http://xerces.apache.org/xerces2-j</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/xerces/xercesImpl/2.8.0/xercesImpl-2.8.0.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - xom-1.2.5.jar
      - :x: **xercesImpl-2.8.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
Apache Xerces2 Java Parser before 2.12.0 allows remote attackers to cause a denial of service (CPU consumption) via a crafted message to an XML service, which triggers hash table collisions.

<p>Publish Date: 2017-10-30
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-0881>CVE-2012-0881</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0881"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0881</a></p>
<p>Release Date: 2017-10-30</p>
<p>Fix Resolution: 2.12.0</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2014-0034</summary>


###  Vulnerable Library - <b>commons-fileupload-1.3.1.jar</b></p>

<p>The Apache Commons FileUpload component provides a simple yet flexible means of adding support for multipart
    file upload functionality to servlets and web applications.</p>
<p>Library home page: <a href=""http://commons.apache.org/proper/commons-fileupload/"">http://commons.apache.org/proper/commons-fileupload/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-fileupload/commons-fileupload/1.3.1/commons-fileupload-1.3.1.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - :x: **commons-fileupload-1.3.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
The class FileUploadBase in Apache Commons Fileupload before 1.4 has potential resource leak - InputStream not closed on exception.

<p>Publish Date: 2014-02-17
<p>URL: <a href=https://commons.apache.org/proper/commons-fileupload/changes-report.html>WS-2014-0034</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: None
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/apache/commons-fileupload/commit/5b4881d7f75f439326f54fa554a9ca7de6d60814"">https://github.com/apache/commons-fileupload/commit/5b4881d7f75f439326f54fa554a9ca7de6d60814</a></p>
<p>Release Date: 2014-02-17</p>
<p>Fix Resolution: 1.4</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2014-0107</summary>


###  Vulnerable Library - <b>xalan-2.7.0.jar</b></p>

<p></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/xalan/xalan/2.7.0/xalan-2.7.0.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - xom-1.2.5.jar
      - :x: **xalan-2.7.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
The TransformerFactory in Apache Xalan-Java before 2.7.2 does not properly restrict access to certain properties when FEATURE_SECURE_PROCESSING is enabled, which allows remote attackers to bypass expected restrictions and load arbitrary classes or access external resources via a crafted (1) xalan:content-header, (2) xalan:entities, (3) xslt:content-header, or (4) xslt:entities property, or a Java property that is bound to the XSLT 1.0 system-property function.

<p>Publish Date: 2014-04-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-0107>CVE-2014-0107</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.3</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: Low
</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0107"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0107</a></p>
<p>Release Date: 2014-04-15</p>
<p>Fix Resolution: 2.7.2</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-10086</summary>


###  Vulnerable Library - <b>commons-beanutils-core-1.8.3.jar</b></p>

<p>The Apache Software Foundation provides support for the Apache community of open-source software projects.
    The Apache projects are characterized by a collaborative, consensus based development process, an open and
    pragmatic software license, and a desire to create high quality software that leads the way in its field.
    We consider ourselves not simply a group of projects sharing a server, but rather a community of developers
    and users.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-beanutils/commons-beanutils-core/1.8.3/commons-beanutils-core-1.8.3.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - :x: **commons-beanutils-core-1.8.3.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
In Apache Commons Beanutils 1.9.2, a special BeanIntrospector class was added which allows suppressing the ability for an attacker to access the classloader via the class property available on all Java objects. We, however were not using this by default characteristic of the PropertyUtilsBean.

<p>Publish Date: 2019-08-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10086>CVE-2019-10086</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.3</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: Low
</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/victims/victims-cve-db/commit/16a669c84d95bbbd4294f30e609049a36700847f"">https://github.com/victims/victims-cve-db/commit/16a669c84d95bbbd4294f30e609049a36700847f</a></p>
<p>Release Date: 2019-08-20</p>
<p>Fix Resolution: commons-beanutils:commons-beanutils:1.9.4</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2014-0114</summary>


###  Vulnerable Library - <b>commons-beanutils-core-1.8.3.jar</b></p>

<p>The Apache Software Foundation provides support for the Apache community of open-source software projects.
    The Apache projects are characterized by a collaborative, consensus based development process, an open and
    pragmatic software license, and a desire to create high quality software that leads the way in its field.
    We consider ourselves not simply a group of projects sharing a server, but rather a community of developers
    and users.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-beanutils/commons-beanutils-core/1.8.3/commons-beanutils-core-1.8.3.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - :x: **commons-beanutils-core-1.8.3.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
Apache Commons BeanUtils, as distributed in lib/commons-beanutils-1.8.0.jar in Apache Struts 1.x through 1.3.10 and in other products requiring commons-beanutils through 1.9.2, does not suppress the class property, which allows remote attackers to ""manipulate"" the ClassLoader and execute arbitrary code via the class parameter, as demonstrated by the passing of this parameter to the getClass method of the ActionForm object in Struts 1.

<p>Publish Date: 2014-04-30
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-0114>CVE-2014-0114</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.3</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: Low
</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0114"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0114</a></p>
<p>Release Date: 2014-04-30</p>
<p>Fix Resolution: commons-beanutils:commons-beanutils:1.9.4;org.apache.struts:struts2-core:2.0.5</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-23437</summary>


###  Vulnerable Library - <b>xercesImpl-2.8.0.jar</b></p>

<p>Xerces2 is the next generation of high performance, fully compliant XML parsers in the
    Apache Xerces family. This new version of Xerces introduces the Xerces Native Interface (XNI),
    a complete framework for building parser components and configurations that is extremely
    modular and easy to program.</p>
<p>Library home page: <a href=""http://xerces.apache.org/xerces2-j"">http://xerces.apache.org/xerces2-j</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/xerces/xercesImpl/2.8.0/xercesImpl-2.8.0.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - xom-1.2.5.jar
      - :x: **xercesImpl-2.8.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
There's a vulnerability within the Apache Xerces Java (XercesJ) XML parser when handling specially crafted XML document payloads. This causes, the XercesJ XML parser to wait in an infinite loop, which may sometimes consume system resources for prolonged duration. This vulnerability is present within XercesJ version 2.12.1 and the previous versions.

<p>Publish Date: 2022-01-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23437>CVE-2022-23437</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>6.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/advisories/GHSA-h65f-jvqw-m9fj"">https://github.com/advisories/GHSA-h65f-jvqw-m9fj</a></p>
<p>Release Date: 2022-01-24</p>
<p>Fix Resolution: xerces:xercesImpl:2.12.2</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2016-10006</summary>


###  Vulnerable Library - <b>antisamy-1.5.3.jar</b></p>

<p>The OWASP AntiSamy project is a collection of APIs for safely allowing users to supply their own HTML
        and CSS without exposing the site to XSS vulnerabilities.</p>
<p>Library home page: <a href=""http://www.owasp.org/index.php/Category:OWASP_AntiSamy_Project"">http://www.owasp.org/index.php/Category:OWASP_AntiSamy_Project</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/owasp/antisamy/antisamy/1.5.3/antisamy-1.5.3.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - :x: **antisamy-1.5.3.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
In OWASP AntiSamy before 1.5.5, by submitting a specially crafted input (a tag that supports style with active content), you could bypass the library protections and supply executable code. The impact is XSS.

<p>Publish Date: 2016-12-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-10006>CVE-2016-10006</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>6.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Changed
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10006"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10006</a></p>
<p>Release Date: 2016-12-24</p>
<p>Fix Resolution: 1.5.5</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2021-35043</summary>


###  Vulnerable Library - <b>antisamy-1.5.3.jar</b></p>

<p>The OWASP AntiSamy project is a collection of APIs for safely allowing users to supply their own HTML
        and CSS without exposing the site to XSS vulnerabilities.</p>
<p>Library home page: <a href=""http://www.owasp.org/index.php/Category:OWASP_AntiSamy_Project"">http://www.owasp.org/index.php/Category:OWASP_AntiSamy_Project</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/owasp/antisamy/antisamy/1.5.3/antisamy-1.5.3.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - :x: **antisamy-1.5.3.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
OWASP AntiSamy before 1.6.4 allows XSS via HTML attributes when using the HTML output serializer (XHTML is not affected). This was demonstrated by a javascript: URL with &#00058 as the replacement for the : character.

<p>Publish Date: 2021-07-19
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35043>CVE-2021-35043</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>6.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Changed
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-35043"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-35043</a></p>
<p>Release Date: 2021-07-19</p>
<p>Fix Resolution: org.owasp.antisamy:antisamy:1.6.4</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2017-14735</summary>


###  Vulnerable Library - <b>antisamy-1.5.3.jar</b></p>

<p>The OWASP AntiSamy project is a collection of APIs for safely allowing users to supply their own HTML
        and CSS without exposing the site to XSS vulnerabilities.</p>
<p>Library home page: <a href=""http://www.owasp.org/index.php/Category:OWASP_AntiSamy_Project"">http://www.owasp.org/index.php/Category:OWASP_AntiSamy_Project</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/owasp/antisamy/antisamy/1.5.3/antisamy-1.5.3.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - :x: **antisamy-1.5.3.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
OWASP AntiSamy before 1.5.7 allows XSS via HTML5 entities, as demonstrated by use of &colon; to construct a javascript: URL.

<p>Publish Date: 2017-09-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-14735>CVE-2017-14735</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>6.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Changed
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14735"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14735</a></p>
<p>Release Date: 2017-09-25</p>
<p>Fix Resolution: 1.5.7</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2013-4002</summary>


###  Vulnerable Library - <b>xercesImpl-2.8.0.jar</b></p>

<p>Xerces2 is the next generation of high performance, fully compliant XML parsers in the
    Apache Xerces family. This new version of Xerces introduces the Xerces Native Interface (XNI),
    a complete framework for building parser components and configurations that is extremely
    modular and easy to program.</p>
<p>Library home page: <a href=""http://xerces.apache.org/xerces2-j"">http://xerces.apache.org/xerces2-j</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/xerces/xercesImpl/2.8.0/xercesImpl-2.8.0.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - xom-1.2.5.jar
      - :x: **xercesImpl-2.8.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
XMLscanner.java in Apache Xerces2 Java Parser before 2.12.0, as used in the Java Runtime Environment (JRE) in IBM Java 5.0 before 5.0 SR16-FP3, 6 before 6 SR14, 6.0.1 before 6.0.1 SR6, and 7 before 7 SR5 as well as Oracle Java SE 7u40 and earlier, Java SE 6u60 and earlier, Java SE 5.0u51 and earlier, JRockit R28.2.8 and earlier, JRockit R27.7.6 and earlier, Java SE Embedded 7u40 and earlier, and possibly other products allows remote attackers to cause a denial of service via vectors related to XML attribute names.

<p>Publish Date: 2013-07-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-4002>CVE-2013-4002</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>5.9</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-4002"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-4002</a></p>
<p>Release Date: 2013-07-23</p>
<p>Fix Resolution: xerces:xercesImpl:Xerces-J_2_12_0</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2009-2625</summary>


###  Vulnerable Library - <b>xercesImpl-2.8.0.jar</b></p>

<p>Xerces2 is the next generation of high performance, fully compliant XML parsers in the
    Apache Xerces family. This new version of Xerces introduces the Xerces Native Interface (XNI),
    a complete framework for building parser components and configurations that is extremely
    modular and easy to program.</p>
<p>Library home page: <a href=""http://xerces.apache.org/xerces2-j"">http://xerces.apache.org/xerces2-j</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/xerces/xercesImpl/2.8.0/xercesImpl-2.8.0.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - xom-1.2.5.jar
      - :x: **xercesImpl-2.8.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
XMLScanner.java in Apache Xerces2 Java, as used in Sun Java Runtime Environment (JRE) in JDK and JRE 6 before Update 15 and JDK and JRE 5.0 before Update 20, and in other products, allows remote attackers to cause a denial of service (infinite loop and application hang) via malformed XML input, as demonstrated by the Codenomicon XML fuzzing framework.

<p>Publish Date: 2009-08-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2009-2625>CVE-2009-2625</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>5.3</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: Low
</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://nvd.nist.gov/vuln/detail/CVE-2009-2625"">https://nvd.nist.gov/vuln/detail/CVE-2009-2625</a></p>
<p>Release Date: 2009-08-06</p>
<p>Fix Resolution: apache-xerces:xercesImpl - 2.9.1;xerces:xercesImpl - 2.3.0,2.9.1-NODEP,2.9.0;org.apache.servicemix.bundles:org.apache.servicemix.bundles.xerces - 2.10.0_1</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2021-29425</summary>


###  Vulnerable Library - <b>commons-io-2.2.jar</b></p>

<p>The Commons IO library contains utility classes, stream implementations, file filters, 
file comparators, endian transformation classes, and much more.</p>
<p>Library home page: <a href=""http://commons.apache.org/io/"">http://commons.apache.org/io/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-io/commons-io/2.2/commons-io-2.2.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - commons-fileupload-1.3.1.jar
      - :x: **commons-io-2.2.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like ""//../foo"", or ""\\..\foo"", the result would be the same value, thus possibly providing access to files in the parent directory, but not further above (thus ""limited"" path traversal), if the calling code would use the result to construct a path value.

<p>Publish Date: 2021-04-13
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29425>CVE-2021-29425</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>4.8</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-29425"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-29425</a></p>
<p>Release Date: 2021-04-13</p>
<p>Fix Resolution: commons-io:commons-io:2.7</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> CVE-2012-5783</summary>


###  Vulnerable Library - <b>commons-httpclient-3.1.jar</b></p>

<p>The HttpClient  component supports the client-side of RFC 1945 (HTTP/1.0)  and RFC 2616 (HTTP/1.1) , several related specifications (RFC 2109 (Cookies) , RFC 2617 (HTTP Authentication) , etc.), and provides a framework by which new request types (methods) or HTTP extensions can be created easily.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - antisamy-1.5.3.jar
      - :x: **commons-httpclient-3.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
Apache Commons HttpClient 3.x, as used in Amazon Flexible Payments Service (FPS) merchant Java SDK and other products, does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.

<p>Publish Date: 2012-11-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-5783>CVE-2012-5783</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>3.7</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2012-5783"">https://nvd.nist.gov/vuln/detail/CVE-2012-5783</a></p>
<p>Release Date: 2012-11-04</p>
<p>Fix Resolution: commons-httpclient:commons-httpclient - 3.1-jenkins-1,3.1-redhat-3,3.1-HTTPCLIENT-1265</p>

</p>

<p></p>

</details>
<!-- <REMEDIATE>[{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""commons-fileupload"",""packageName"":""commons-fileupload"",""packageVersion"":""1.3.1"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;commons-fileupload:commons-fileupload:1.3.1"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""1.3.3"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2016-1000031"",""vulnerabilityDetails"":""Apache Commons FileUpload before 1.3.3 DiskFileItem File Manipulation Remote Code Execution"",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-1000031"",""cvss3Severity"":""high"",""cvss3Score"":""9.8"",""cvss3Metrics"":{""A"":""High"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""High"",""UI"":""None"",""AV"":""Network"",""I"":""High""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""org.beanshell"",""packageName"":""bsh-core"",""packageVersion"":""2.0b4"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;org.beanshell:bsh-core:2.0b4"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""2.0b6"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2016-2510"",""vulnerabilityDetails"":""BeanShell (bsh) before 2.0b6, when included on the classpath by an application that uses Java serialization or XStream, allows remote attackers to execute arbitrary code via crafted serialized data, related to XThis.Handler."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2510"",""cvss3Severity"":""high"",""cvss3Score"":""8.1"",""cvss3Metrics"":{""A"":""High"",""AC"":""High"",""PR"":""None"",""S"":""Unchanged"",""C"":""High"",""UI"":""None"",""AV"":""Network"",""I"":""High""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""commons-fileupload"",""packageName"":""commons-fileupload"",""packageVersion"":""1.3.1"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;commons-fileupload:commons-fileupload:1.3.1"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""org.apache.tomcat.embed:tomcat-embed-core:9.0.0.M8,8.5.3,8.0.36,7.0.70,org.apache.tomcat:tomcat-coyote:9.0.0.M8,8.5.3,8.0.36,7.0.70,commons-fileupload:commons-fileupload:1.3.2"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2016-3092"",""vulnerabilityDetails"":""The MultipartStream class in Apache Commons Fileupload before 1.3.2, as used in Apache Tomcat 7.x before 7.0.70, 8.x before 8.0.36, 8.5.x before 8.5.3, and 9.x before 9.0.0.M7 and other products, allows remote attackers to cause a denial of service (CPU consumption) via a long boundary string."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-3092"",""cvss3Severity"":""high"",""cvss3Score"":""7.5"",""cvss3Metrics"":{""A"":""High"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""None"",""AV"":""Network"",""I"":""None""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""xerces"",""packageName"":""xercesImpl"",""packageVersion"":""2.8.0"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;xom:xom:1.2.5;xerces:xercesImpl:2.8.0"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""2.12.0"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2012-0881"",""vulnerabilityDetails"":""Apache Xerces2 Java Parser before 2.12.0 allows remote attackers to cause a denial of service (CPU consumption) via a crafted message to an XML service, which triggers hash table collisions."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-0881"",""cvss3Severity"":""high"",""cvss3Score"":""7.5"",""cvss3Metrics"":{""A"":""High"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""None"",""AV"":""Network"",""I"":""None""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""commons-fileupload"",""packageName"":""commons-fileupload"",""packageVersion"":""1.3.1"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;commons-fileupload:commons-fileupload:1.3.1"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""1.4"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""WS-2014-0034"",""vulnerabilityDetails"":""The class FileUploadBase in Apache Commons Fileupload before 1.4 has potential resource leak - InputStream not closed on exception."",""vulnerabilityUrl"":""https://commons.apache.org/proper/commons-fileupload/changes-report.html"",""cvss3Severity"":""high"",""cvss3Score"":""7.5"",""cvss3Metrics"":{""A"":""None"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""High"",""UI"":""None"",""AV"":""Network"",""I"":""None""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""xalan"",""packageName"":""xalan"",""packageVersion"":""2.7.0"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;xom:xom:1.2.5;xalan:xalan:2.7.0"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""2.7.2"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2014-0107"",""vulnerabilityDetails"":""The TransformerFactory in Apache Xalan-Java before 2.7.2 does not properly restrict access to certain properties when FEATURE_SECURE_PROCESSING is enabled, which allows remote attackers to bypass expected restrictions and load arbitrary classes or access external resources via a crafted (1) xalan:content-header, (2) xalan:entities, (3) xslt:content-header, or (4) xslt:entities property, or a Java property that is bound to the XSLT 1.0 system-property function."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-0107"",""cvss3Severity"":""high"",""cvss3Score"":""7.3"",""cvss3Metrics"":{""A"":""Low"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""Low"",""UI"":""None"",""AV"":""Network"",""I"":""Low""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""commons-beanutils"",""packageName"":""commons-beanutils-core"",""packageVersion"":""1.8.3"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;commons-beanutils:commons-beanutils-core:1.8.3"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""commons-beanutils:commons-beanutils:1.9.4"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2019-10086"",""vulnerabilityDetails"":""In Apache Commons Beanutils 1.9.2, a special BeanIntrospector class was added which allows suppressing the ability for an attacker to access the classloader via the class property available on all Java objects. We, however were not using this by default characteristic of the PropertyUtilsBean."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10086"",""cvss3Severity"":""high"",""cvss3Score"":""7.3"",""cvss3Metrics"":{""A"":""Low"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""Low"",""UI"":""None"",""AV"":""Network"",""I"":""Low""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""commons-beanutils"",""packageName"":""commons-beanutils-core"",""packageVersion"":""1.8.3"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;commons-beanutils:commons-beanutils-core:1.8.3"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""commons-beanutils:commons-beanutils:1.9.4;org.apache.struts:struts2-core:2.0.5"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2014-0114"",""vulnerabilityDetails"":""Apache Commons BeanUtils, as distributed in lib/commons-beanutils-1.8.0.jar in Apache Struts 1.x through 1.3.10 and in other products requiring commons-beanutils through 1.9.2, does not suppress the class property, which allows remote attackers to \""manipulate\"" the ClassLoader and execute arbitrary code via the class parameter, as demonstrated by the passing of this parameter to the getClass method of the ActionForm object in Struts 1."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-0114"",""cvss3Severity"":""high"",""cvss3Score"":""7.3"",""cvss3Metrics"":{""A"":""Low"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""Low"",""UI"":""None"",""AV"":""Network"",""I"":""Low""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""xerces"",""packageName"":""xercesImpl"",""packageVersion"":""2.8.0"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;xom:xom:1.2.5;xerces:xercesImpl:2.8.0"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""xerces:xercesImpl:2.12.2"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2022-23437"",""vulnerabilityDetails"":""There\u0027s a vulnerability within the Apache Xerces Java (XercesJ) XML parser when handling specially crafted XML document payloads. This causes, the XercesJ XML parser to wait in an infinite loop, which may sometimes consume system resources for prolonged duration. This vulnerability is present within XercesJ version 2.12.1 and the previous versions."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23437"",""cvss3Severity"":""medium"",""cvss3Score"":""6.5"",""cvss3Metrics"":{""A"":""High"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""Required"",""AV"":""Network"",""I"":""None""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""org.owasp.antisamy"",""packageName"":""antisamy"",""packageVersion"":""1.5.3"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;org.owasp.antisamy:antisamy:1.5.3"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""1.5.5"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2016-10006"",""vulnerabilityDetails"":""In OWASP AntiSamy before 1.5.5, by submitting a specially crafted input (a tag that supports style with active content), you could bypass the library protections and supply executable code. The impact is XSS."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-10006"",""cvss3Severity"":""medium"",""cvss3Score"":""6.1"",""cvss3Metrics"":{""A"":""None"",""AC"":""Low"",""PR"":""None"",""S"":""Changed"",""C"":""Low"",""UI"":""Required"",""AV"":""Network"",""I"":""Low""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""org.owasp.antisamy"",""packageName"":""antisamy"",""packageVersion"":""1.5.3"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;org.owasp.antisamy:antisamy:1.5.3"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""org.owasp.antisamy:antisamy:1.6.4"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2021-35043"",""vulnerabilityDetails"":""OWASP AntiSamy before 1.6.4 allows XSS via HTML attributes when using the HTML output serializer (XHTML is not affected). This was demonstrated by a javascript: URL with \u0026#00058 as the replacement for the : character."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35043"",""cvss3Severity"":""medium"",""cvss3Score"":""6.1"",""cvss3Metrics"":{""A"":""None"",""AC"":""Low"",""PR"":""None"",""S"":""Changed"",""C"":""Low"",""UI"":""Required"",""AV"":""Network"",""I"":""Low""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""org.owasp.antisamy"",""packageName"":""antisamy"",""packageVersion"":""1.5.3"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;org.owasp.antisamy:antisamy:1.5.3"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""1.5.7"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2017-14735"",""vulnerabilityDetails"":""OWASP AntiSamy before 1.5.7 allows XSS via HTML5 entities, as demonstrated by use of \u0026colon; to construct a javascript: URL."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-14735"",""cvss3Severity"":""medium"",""cvss3Score"":""6.1"",""cvss3Metrics"":{""A"":""None"",""AC"":""Low"",""PR"":""None"",""S"":""Changed"",""C"":""Low"",""UI"":""Required"",""AV"":""Network"",""I"":""Low""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""xerces"",""packageName"":""xercesImpl"",""packageVersion"":""2.8.0"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;xom:xom:1.2.5;xerces:xercesImpl:2.8.0"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""xerces:xercesImpl:Xerces-J_2_12_0"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2013-4002"",""vulnerabilityDetails"":""XMLscanner.java in Apache Xerces2 Java Parser before 2.12.0, as used in the Java Runtime Environment (JRE) in IBM Java 5.0 before 5.0 SR16-FP3, 6 before 6 SR14, 6.0.1 before 6.0.1 SR6, and 7 before 7 SR5 as well as Oracle Java SE 7u40 and earlier, Java SE 6u60 and earlier, Java SE 5.0u51 and earlier, JRockit R28.2.8 and earlier, JRockit R27.7.6 and earlier, Java SE Embedded 7u40 and earlier, and possibly other products allows remote attackers to cause a denial of service via vectors related to XML attribute names."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-4002"",""cvss3Severity"":""medium"",""cvss3Score"":""5.9"",""cvss3Metrics"":{""A"":""High"",""AC"":""High"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""None"",""AV"":""Network"",""I"":""None""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""xerces"",""packageName"":""xercesImpl"",""packageVersion"":""2.8.0"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;xom:xom:1.2.5;xerces:xercesImpl:2.8.0"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""apache-xerces:xercesImpl - 2.9.1;xerces:xercesImpl - 2.3.0,2.9.1-NODEP,2.9.0;org.apache.servicemix.bundles:org.apache.servicemix.bundles.xerces - 2.10.0_1"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2009-2625"",""vulnerabilityDetails"":""XMLScanner.java in Apache Xerces2 Java, as used in Sun Java Runtime Environment (JRE) in JDK and JRE 6 before Update 15 and JDK and JRE 5.0 before Update 20, and in other products, allows remote attackers to cause a denial of service (infinite loop and application hang) via malformed XML input, as demonstrated by the Codenomicon XML fuzzing framework."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2009-2625"",""cvss3Severity"":""medium"",""cvss3Score"":""5.3"",""cvss3Metrics"":{""A"":""Low"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""None"",""AV"":""Network"",""I"":""None""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""commons-io"",""packageName"":""commons-io"",""packageVersion"":""2.2"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;commons-fileupload:commons-fileupload:1.3.1;commons-io:commons-io:2.2"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""commons-io:commons-io:2.7"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2021-29425"",""vulnerabilityDetails"":""In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like \""//../foo\"", or \""\\\\..\\foo\"", the result would be the same value, thus possibly providing access to files in the parent directory, but not further above (thus \""limited\"" path traversal), if the calling code would use the result to construct a path value."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29425"",""cvss3Severity"":""medium"",""cvss3Score"":""4.8"",""cvss3Metrics"":{""A"":""None"",""AC"":""High"",""PR"":""None"",""S"":""Unchanged"",""C"":""Low"",""UI"":""None"",""AV"":""Network"",""I"":""Low""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""commons-httpclient"",""packageName"":""commons-httpclient"",""packageVersion"":""3.1"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;org.owasp.antisamy:antisamy:1.5.3;commons-httpclient:commons-httpclient:3.1"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""commons-httpclient:commons-httpclient - 3.1-jenkins-1,3.1-redhat-3,3.1-HTTPCLIENT-1265"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2012-5783"",""vulnerabilityDetails"":""Apache Commons HttpClient 3.x, as used in Amazon Flexible Payments Service (FPS) merchant Java SDK and other products, does not verify that the server hostname matches a domain name in the subject\u0027s Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-5783"",""cvss3Severity"":""low"",""cvss3Score"":""3.7"",""cvss3Metrics"":{""A"":""None"",""AC"":""High"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""None"",""AV"":""Network"",""I"":""Low""},""extraData"":{}}]</REMEDIATE> -->",True,"esapi-2.1.0.1.jar: 16 vulnerabilities (highest severity is: 9.8) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>esapi-2.1.0.1.jar</b></p></summary>

<p></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-fileupload/commons-fileupload/1.3.1/commons-fileupload-1.3.1.jar</p>
<p>


<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p></details>

## Vulnerabilities

| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2016-1000031](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-1000031) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | commons-fileupload-1.3.1.jar | Transitive | N/A | ❌ |
| [CVE-2016-2510](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2510) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.1 | bsh-core-2.0b4.jar | Transitive | N/A | ❌ |
| [CVE-2016-3092](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-3092) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | commons-fileupload-1.3.1.jar | Transitive | N/A | ❌ |
| [CVE-2012-0881](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-0881) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | xercesImpl-2.8.0.jar | Transitive | N/A | ❌ |
| [WS-2014-0034](https://commons.apache.org/proper/commons-fileupload/changes-report.html) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | commons-fileupload-1.3.1.jar | Transitive | N/A | ❌ |
| [CVE-2014-0107](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-0107) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.3 | xalan-2.7.0.jar | Transitive | N/A | ❌ |
| [CVE-2019-10086](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10086) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.3 | commons-beanutils-core-1.8.3.jar | Transitive | N/A | ❌ |
| [CVE-2014-0114](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-0114) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.3 | commons-beanutils-core-1.8.3.jar | Transitive | N/A | ❌ |
| [CVE-2022-23437](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23437) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | xercesImpl-2.8.0.jar | Transitive | N/A | ❌ |
| [CVE-2016-10006](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-10006) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | antisamy-1.5.3.jar | Transitive | N/A | ❌ |
| [CVE-2021-35043](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35043) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | antisamy-1.5.3.jar | Transitive | N/A | ❌ |
| [CVE-2017-14735](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-14735) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | antisamy-1.5.3.jar | Transitive | N/A | ❌ |
| [CVE-2013-4002](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-4002) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.9 | xercesImpl-2.8.0.jar | Transitive | N/A | ❌ |
| [CVE-2009-2625](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2009-2625) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | xercesImpl-2.8.0.jar | Transitive | N/A | ❌ |
| [CVE-2021-29425](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29425) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 4.8 | commons-io-2.2.jar | Transitive | N/A | ❌ |
| [CVE-2012-5783](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-5783) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low | 3.7 | commons-httpclient-3.1.jar | Transitive | N/A | ❌ |


## Details

<details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2016-1000031</summary>


###  Vulnerable Library - <b>commons-fileupload-1.3.1.jar</b></p>

<p>The Apache Commons FileUpload component provides a simple yet flexible means of adding support for multipart
    file upload functionality to servlets and web applications.</p>
<p>Library home page: <a href=""http://commons.apache.org/proper/commons-fileupload/"">http://commons.apache.org/proper/commons-fileupload/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-fileupload/commons-fileupload/1.3.1/commons-fileupload-1.3.1.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - :x: **commons-fileupload-1.3.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
Apache Commons FileUpload before 1.3.3 DiskFileItem File Manipulation Remote Code Execution

<p>Publish Date: 2016-10-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-1000031>CVE-2016-1000031</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>9.8</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: 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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000031"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000031</a></p>
<p>Release Date: 2016-10-25</p>
<p>Fix Resolution: 1.3.3</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2016-2510</summary>


###  Vulnerable Library - <b>bsh-core-2.0b4.jar</b></p>

<p>BeanShell core</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/beanshell/bsh-core/2.0b4/bsh-core-2.0b4.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - :x: **bsh-core-2.0b4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
BeanShell (bsh) before 2.0b6, when included on the classpath by an application that uses Java serialization or XStream, allows remote attackers to execute arbitrary code via crafted serialized data, related to XThis.Handler.

<p>Publish Date: 2016-04-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2510>CVE-2016-2510</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>8.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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://nvd.nist.gov/vuln/detail/CVE-2016-2510"">https://nvd.nist.gov/vuln/detail/CVE-2016-2510</a></p>
<p>Release Date: 2016-04-07</p>
<p>Fix Resolution: 2.0b6</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2016-3092</summary>


###  Vulnerable Library - <b>commons-fileupload-1.3.1.jar</b></p>

<p>The Apache Commons FileUpload component provides a simple yet flexible means of adding support for multipart
    file upload functionality to servlets and web applications.</p>
<p>Library home page: <a href=""http://commons.apache.org/proper/commons-fileupload/"">http://commons.apache.org/proper/commons-fileupload/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-fileupload/commons-fileupload/1.3.1/commons-fileupload-1.3.1.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - :x: **commons-fileupload-1.3.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
The MultipartStream class in Apache Commons Fileupload before 1.3.2, as used in Apache Tomcat 7.x before 7.0.70, 8.x before 8.0.36, 8.5.x before 8.5.3, and 9.x before 9.0.0.M7 and other products, allows remote attackers to cause a denial of service (CPU consumption) via a long boundary string.

<p>Publish Date: 2016-07-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-3092>CVE-2016-3092</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3092"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3092</a></p>
<p>Release Date: 2016-07-04</p>
<p>Fix Resolution: org.apache.tomcat.embed:tomcat-embed-core:9.0.0.M8,8.5.3,8.0.36,7.0.70,org.apache.tomcat:tomcat-coyote:9.0.0.M8,8.5.3,8.0.36,7.0.70,commons-fileupload:commons-fileupload:1.3.2</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2012-0881</summary>


###  Vulnerable Library - <b>xercesImpl-2.8.0.jar</b></p>

<p>Xerces2 is the next generation of high performance, fully compliant XML parsers in the
    Apache Xerces family. This new version of Xerces introduces the Xerces Native Interface (XNI),
    a complete framework for building parser components and configurations that is extremely
    modular and easy to program.</p>
<p>Library home page: <a href=""http://xerces.apache.org/xerces2-j"">http://xerces.apache.org/xerces2-j</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/xerces/xercesImpl/2.8.0/xercesImpl-2.8.0.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - xom-1.2.5.jar
      - :x: **xercesImpl-2.8.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
Apache Xerces2 Java Parser before 2.12.0 allows remote attackers to cause a denial of service (CPU consumption) via a crafted message to an XML service, which triggers hash table collisions.

<p>Publish Date: 2017-10-30
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-0881>CVE-2012-0881</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0881"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0881</a></p>
<p>Release Date: 2017-10-30</p>
<p>Fix Resolution: 2.12.0</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2014-0034</summary>


###  Vulnerable Library - <b>commons-fileupload-1.3.1.jar</b></p>

<p>The Apache Commons FileUpload component provides a simple yet flexible means of adding support for multipart
    file upload functionality to servlets and web applications.</p>
<p>Library home page: <a href=""http://commons.apache.org/proper/commons-fileupload/"">http://commons.apache.org/proper/commons-fileupload/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-fileupload/commons-fileupload/1.3.1/commons-fileupload-1.3.1.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - :x: **commons-fileupload-1.3.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
The class FileUploadBase in Apache Commons Fileupload before 1.4 has potential resource leak - InputStream not closed on exception.

<p>Publish Date: 2014-02-17
<p>URL: <a href=https://commons.apache.org/proper/commons-fileupload/changes-report.html>WS-2014-0034</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: None
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/apache/commons-fileupload/commit/5b4881d7f75f439326f54fa554a9ca7de6d60814"">https://github.com/apache/commons-fileupload/commit/5b4881d7f75f439326f54fa554a9ca7de6d60814</a></p>
<p>Release Date: 2014-02-17</p>
<p>Fix Resolution: 1.4</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2014-0107</summary>


###  Vulnerable Library - <b>xalan-2.7.0.jar</b></p>

<p></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/xalan/xalan/2.7.0/xalan-2.7.0.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - xom-1.2.5.jar
      - :x: **xalan-2.7.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
The TransformerFactory in Apache Xalan-Java before 2.7.2 does not properly restrict access to certain properties when FEATURE_SECURE_PROCESSING is enabled, which allows remote attackers to bypass expected restrictions and load arbitrary classes or access external resources via a crafted (1) xalan:content-header, (2) xalan:entities, (3) xslt:content-header, or (4) xslt:entities property, or a Java property that is bound to the XSLT 1.0 system-property function.

<p>Publish Date: 2014-04-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-0107>CVE-2014-0107</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.3</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: Low
</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0107"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0107</a></p>
<p>Release Date: 2014-04-15</p>
<p>Fix Resolution: 2.7.2</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-10086</summary>


###  Vulnerable Library - <b>commons-beanutils-core-1.8.3.jar</b></p>

<p>The Apache Software Foundation provides support for the Apache community of open-source software projects.
    The Apache projects are characterized by a collaborative, consensus based development process, an open and
    pragmatic software license, and a desire to create high quality software that leads the way in its field.
    We consider ourselves not simply a group of projects sharing a server, but rather a community of developers
    and users.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-beanutils/commons-beanutils-core/1.8.3/commons-beanutils-core-1.8.3.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - :x: **commons-beanutils-core-1.8.3.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
In Apache Commons Beanutils 1.9.2, a special BeanIntrospector class was added which allows suppressing the ability for an attacker to access the classloader via the class property available on all Java objects. We, however were not using this by default characteristic of the PropertyUtilsBean.

<p>Publish Date: 2019-08-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10086>CVE-2019-10086</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.3</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: Low
</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/victims/victims-cve-db/commit/16a669c84d95bbbd4294f30e609049a36700847f"">https://github.com/victims/victims-cve-db/commit/16a669c84d95bbbd4294f30e609049a36700847f</a></p>
<p>Release Date: 2019-08-20</p>
<p>Fix Resolution: commons-beanutils:commons-beanutils:1.9.4</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2014-0114</summary>


###  Vulnerable Library - <b>commons-beanutils-core-1.8.3.jar</b></p>

<p>The Apache Software Foundation provides support for the Apache community of open-source software projects.
    The Apache projects are characterized by a collaborative, consensus based development process, an open and
    pragmatic software license, and a desire to create high quality software that leads the way in its field.
    We consider ourselves not simply a group of projects sharing a server, but rather a community of developers
    and users.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-beanutils/commons-beanutils-core/1.8.3/commons-beanutils-core-1.8.3.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - :x: **commons-beanutils-core-1.8.3.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
Apache Commons BeanUtils, as distributed in lib/commons-beanutils-1.8.0.jar in Apache Struts 1.x through 1.3.10 and in other products requiring commons-beanutils through 1.9.2, does not suppress the class property, which allows remote attackers to ""manipulate"" the ClassLoader and execute arbitrary code via the class parameter, as demonstrated by the passing of this parameter to the getClass method of the ActionForm object in Struts 1.

<p>Publish Date: 2014-04-30
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-0114>CVE-2014-0114</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>7.3</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: Low
</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0114"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0114</a></p>
<p>Release Date: 2014-04-30</p>
<p>Fix Resolution: commons-beanutils:commons-beanutils:1.9.4;org.apache.struts:struts2-core:2.0.5</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-23437</summary>


###  Vulnerable Library - <b>xercesImpl-2.8.0.jar</b></p>

<p>Xerces2 is the next generation of high performance, fully compliant XML parsers in the
    Apache Xerces family. This new version of Xerces introduces the Xerces Native Interface (XNI),
    a complete framework for building parser components and configurations that is extremely
    modular and easy to program.</p>
<p>Library home page: <a href=""http://xerces.apache.org/xerces2-j"">http://xerces.apache.org/xerces2-j</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/xerces/xercesImpl/2.8.0/xercesImpl-2.8.0.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - xom-1.2.5.jar
      - :x: **xercesImpl-2.8.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
There's a vulnerability within the Apache Xerces Java (XercesJ) XML parser when handling specially crafted XML document payloads. This causes, the XercesJ XML parser to wait in an infinite loop, which may sometimes consume system resources for prolonged duration. This vulnerability is present within XercesJ version 2.12.1 and the previous versions.

<p>Publish Date: 2022-01-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23437>CVE-2022-23437</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>6.5</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/advisories/GHSA-h65f-jvqw-m9fj"">https://github.com/advisories/GHSA-h65f-jvqw-m9fj</a></p>
<p>Release Date: 2022-01-24</p>
<p>Fix Resolution: xerces:xercesImpl:2.12.2</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2016-10006</summary>


###  Vulnerable Library - <b>antisamy-1.5.3.jar</b></p>

<p>The OWASP AntiSamy project is a collection of APIs for safely allowing users to supply their own HTML
        and CSS without exposing the site to XSS vulnerabilities.</p>
<p>Library home page: <a href=""http://www.owasp.org/index.php/Category:OWASP_AntiSamy_Project"">http://www.owasp.org/index.php/Category:OWASP_AntiSamy_Project</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/owasp/antisamy/antisamy/1.5.3/antisamy-1.5.3.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - :x: **antisamy-1.5.3.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
In OWASP AntiSamy before 1.5.5, by submitting a specially crafted input (a tag that supports style with active content), you could bypass the library protections and supply executable code. The impact is XSS.

<p>Publish Date: 2016-12-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-10006>CVE-2016-10006</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>6.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Changed
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10006"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10006</a></p>
<p>Release Date: 2016-12-24</p>
<p>Fix Resolution: 1.5.5</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2021-35043</summary>


###  Vulnerable Library - <b>antisamy-1.5.3.jar</b></p>

<p>The OWASP AntiSamy project is a collection of APIs for safely allowing users to supply their own HTML
        and CSS without exposing the site to XSS vulnerabilities.</p>
<p>Library home page: <a href=""http://www.owasp.org/index.php/Category:OWASP_AntiSamy_Project"">http://www.owasp.org/index.php/Category:OWASP_AntiSamy_Project</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/owasp/antisamy/antisamy/1.5.3/antisamy-1.5.3.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - :x: **antisamy-1.5.3.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
OWASP AntiSamy before 1.6.4 allows XSS via HTML attributes when using the HTML output serializer (XHTML is not affected). This was demonstrated by a javascript: URL with &#00058 as the replacement for the : character.

<p>Publish Date: 2021-07-19
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35043>CVE-2021-35043</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>6.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Changed
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-35043"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-35043</a></p>
<p>Release Date: 2021-07-19</p>
<p>Fix Resolution: org.owasp.antisamy:antisamy:1.6.4</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2017-14735</summary>


###  Vulnerable Library - <b>antisamy-1.5.3.jar</b></p>

<p>The OWASP AntiSamy project is a collection of APIs for safely allowing users to supply their own HTML
        and CSS without exposing the site to XSS vulnerabilities.</p>
<p>Library home page: <a href=""http://www.owasp.org/index.php/Category:OWASP_AntiSamy_Project"">http://www.owasp.org/index.php/Category:OWASP_AntiSamy_Project</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/owasp/antisamy/antisamy/1.5.3/antisamy-1.5.3.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - :x: **antisamy-1.5.3.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
OWASP AntiSamy before 1.5.7 allows XSS via HTML5 entities, as demonstrated by use of &colon; to construct a javascript: URL.

<p>Publish Date: 2017-09-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-14735>CVE-2017-14735</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>6.1</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: Required
  - Scope: Changed
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14735"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14735</a></p>
<p>Release Date: 2017-09-25</p>
<p>Fix Resolution: 1.5.7</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2013-4002</summary>


###  Vulnerable Library - <b>xercesImpl-2.8.0.jar</b></p>

<p>Xerces2 is the next generation of high performance, fully compliant XML parsers in the
    Apache Xerces family. This new version of Xerces introduces the Xerces Native Interface (XNI),
    a complete framework for building parser components and configurations that is extremely
    modular and easy to program.</p>
<p>Library home page: <a href=""http://xerces.apache.org/xerces2-j"">http://xerces.apache.org/xerces2-j</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/xerces/xercesImpl/2.8.0/xercesImpl-2.8.0.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - xom-1.2.5.jar
      - :x: **xercesImpl-2.8.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
XMLscanner.java in Apache Xerces2 Java Parser before 2.12.0, as used in the Java Runtime Environment (JRE) in IBM Java 5.0 before 5.0 SR16-FP3, 6 before 6 SR14, 6.0.1 before 6.0.1 SR6, and 7 before 7 SR5 as well as Oracle Java SE 7u40 and earlier, Java SE 6u60 and earlier, Java SE 5.0u51 and earlier, JRockit R28.2.8 and earlier, JRockit R27.7.6 and earlier, Java SE Embedded 7u40 and earlier, and possibly other products allows remote attackers to cause a denial of service via vectors related to XML attribute names.

<p>Publish Date: 2013-07-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-4002>CVE-2013-4002</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>5.9</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-4002"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-4002</a></p>
<p>Release Date: 2013-07-23</p>
<p>Fix Resolution: xerces:xercesImpl:Xerces-J_2_12_0</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2009-2625</summary>


###  Vulnerable Library - <b>xercesImpl-2.8.0.jar</b></p>

<p>Xerces2 is the next generation of high performance, fully compliant XML parsers in the
    Apache Xerces family. This new version of Xerces introduces the Xerces Native Interface (XNI),
    a complete framework for building parser components and configurations that is extremely
    modular and easy to program.</p>
<p>Library home page: <a href=""http://xerces.apache.org/xerces2-j"">http://xerces.apache.org/xerces2-j</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/xerces/xercesImpl/2.8.0/xercesImpl-2.8.0.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - xom-1.2.5.jar
      - :x: **xercesImpl-2.8.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
XMLScanner.java in Apache Xerces2 Java, as used in Sun Java Runtime Environment (JRE) in JDK and JRE 6 before Update 15 and JDK and JRE 5.0 before Update 20, and in other products, allows remote attackers to cause a denial of service (infinite loop and application hang) via malformed XML input, as demonstrated by the Codenomicon XML fuzzing framework.

<p>Publish Date: 2009-08-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2009-2625>CVE-2009-2625</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>5.3</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: Low
</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://nvd.nist.gov/vuln/detail/CVE-2009-2625"">https://nvd.nist.gov/vuln/detail/CVE-2009-2625</a></p>
<p>Release Date: 2009-08-06</p>
<p>Fix Resolution: apache-xerces:xercesImpl - 2.9.1;xerces:xercesImpl - 2.3.0,2.9.1-NODEP,2.9.0;org.apache.servicemix.bundles:org.apache.servicemix.bundles.xerces - 2.10.0_1</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2021-29425</summary>


###  Vulnerable Library - <b>commons-io-2.2.jar</b></p>

<p>The Commons IO library contains utility classes, stream implementations, file filters, 
file comparators, endian transformation classes, and much more.</p>
<p>Library home page: <a href=""http://commons.apache.org/io/"">http://commons.apache.org/io/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-io/commons-io/2.2/commons-io-2.2.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - commons-fileupload-1.3.1.jar
      - :x: **commons-io-2.2.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like ""//../foo"", or ""\\..\foo"", the result would be the same value, thus possibly providing access to files in the parent directory, but not further above (thus ""limited"" path traversal), if the calling code would use the result to construct a path value.

<p>Publish Date: 2021-04-13
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29425>CVE-2021-29425</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>4.8</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-29425"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-29425</a></p>
<p>Release Date: 2021-04-13</p>
<p>Fix Resolution: commons-io:commons-io:2.7</p>

</p>

<p></p>

</details><details>

<summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> CVE-2012-5783</summary>


###  Vulnerable Library - <b>commons-httpclient-3.1.jar</b></p>

<p>The HttpClient  component supports the client-side of RFC 1945 (HTTP/1.0)  and RFC 2616 (HTTP/1.1) , several related specifications (RFC 2109 (Cookies) , RFC 2617 (HTTP Authentication) , etc.), and provides a framework by which new request types (methods) or HTTP extensions can be created easily.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar</p>
<p>

Dependency Hierarchy:
  - esapi-2.1.0.1.jar (Root Library)
    - antisamy-1.5.3.jar
      - :x: **commons-httpclient-3.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/samq-ghdemo/Java-Demo/commit/3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b"">3b7ec3e7ea9fbe9c04f1fc2396cec3c5b5ac198b</a></p>
<p>Found in base branch: <b>main</b></p>
</p>

<p></p>

###  Vulnerability Details
<p>  
  
Apache Commons HttpClient 3.x, as used in Amazon Flexible Payments Service (FPS) merchant Java SDK and other products, does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.

<p>Publish Date: 2012-11-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-5783>CVE-2012-5783</a></p>
</p>

<p></p>

###  CVSS 3 Score Details (<b>3.7</b>)
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: Low
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>

<p></p>

###  Suggested Fix
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2012-5783"">https://nvd.nist.gov/vuln/detail/CVE-2012-5783</a></p>
<p>Release Date: 2012-11-04</p>
<p>Fix Resolution: commons-httpclient:commons-httpclient - 3.1-jenkins-1,3.1-redhat-3,3.1-HTTPCLIENT-1265</p>

</p>

<p></p>

</details>
<!-- <REMEDIATE>[{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""commons-fileupload"",""packageName"":""commons-fileupload"",""packageVersion"":""1.3.1"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;commons-fileupload:commons-fileupload:1.3.1"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""1.3.3"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2016-1000031"",""vulnerabilityDetails"":""Apache Commons FileUpload before 1.3.3 DiskFileItem File Manipulation Remote Code Execution"",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-1000031"",""cvss3Severity"":""high"",""cvss3Score"":""9.8"",""cvss3Metrics"":{""A"":""High"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""High"",""UI"":""None"",""AV"":""Network"",""I"":""High""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""org.beanshell"",""packageName"":""bsh-core"",""packageVersion"":""2.0b4"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;org.beanshell:bsh-core:2.0b4"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""2.0b6"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2016-2510"",""vulnerabilityDetails"":""BeanShell (bsh) before 2.0b6, when included on the classpath by an application that uses Java serialization or XStream, allows remote attackers to execute arbitrary code via crafted serialized data, related to XThis.Handler."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2510"",""cvss3Severity"":""high"",""cvss3Score"":""8.1"",""cvss3Metrics"":{""A"":""High"",""AC"":""High"",""PR"":""None"",""S"":""Unchanged"",""C"":""High"",""UI"":""None"",""AV"":""Network"",""I"":""High""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""commons-fileupload"",""packageName"":""commons-fileupload"",""packageVersion"":""1.3.1"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;commons-fileupload:commons-fileupload:1.3.1"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""org.apache.tomcat.embed:tomcat-embed-core:9.0.0.M8,8.5.3,8.0.36,7.0.70,org.apache.tomcat:tomcat-coyote:9.0.0.M8,8.5.3,8.0.36,7.0.70,commons-fileupload:commons-fileupload:1.3.2"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2016-3092"",""vulnerabilityDetails"":""The MultipartStream class in Apache Commons Fileupload before 1.3.2, as used in Apache Tomcat 7.x before 7.0.70, 8.x before 8.0.36, 8.5.x before 8.5.3, and 9.x before 9.0.0.M7 and other products, allows remote attackers to cause a denial of service (CPU consumption) via a long boundary string."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-3092"",""cvss3Severity"":""high"",""cvss3Score"":""7.5"",""cvss3Metrics"":{""A"":""High"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""None"",""AV"":""Network"",""I"":""None""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""xerces"",""packageName"":""xercesImpl"",""packageVersion"":""2.8.0"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;xom:xom:1.2.5;xerces:xercesImpl:2.8.0"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""2.12.0"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2012-0881"",""vulnerabilityDetails"":""Apache Xerces2 Java Parser before 2.12.0 allows remote attackers to cause a denial of service (CPU consumption) via a crafted message to an XML service, which triggers hash table collisions."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-0881"",""cvss3Severity"":""high"",""cvss3Score"":""7.5"",""cvss3Metrics"":{""A"":""High"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""None"",""AV"":""Network"",""I"":""None""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""commons-fileupload"",""packageName"":""commons-fileupload"",""packageVersion"":""1.3.1"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;commons-fileupload:commons-fileupload:1.3.1"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""1.4"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""WS-2014-0034"",""vulnerabilityDetails"":""The class FileUploadBase in Apache Commons Fileupload before 1.4 has potential resource leak - InputStream not closed on exception."",""vulnerabilityUrl"":""https://commons.apache.org/proper/commons-fileupload/changes-report.html"",""cvss3Severity"":""high"",""cvss3Score"":""7.5"",""cvss3Metrics"":{""A"":""None"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""High"",""UI"":""None"",""AV"":""Network"",""I"":""None""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""xalan"",""packageName"":""xalan"",""packageVersion"":""2.7.0"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;xom:xom:1.2.5;xalan:xalan:2.7.0"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""2.7.2"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2014-0107"",""vulnerabilityDetails"":""The TransformerFactory in Apache Xalan-Java before 2.7.2 does not properly restrict access to certain properties when FEATURE_SECURE_PROCESSING is enabled, which allows remote attackers to bypass expected restrictions and load arbitrary classes or access external resources via a crafted (1) xalan:content-header, (2) xalan:entities, (3) xslt:content-header, or (4) xslt:entities property, or a Java property that is bound to the XSLT 1.0 system-property function."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-0107"",""cvss3Severity"":""high"",""cvss3Score"":""7.3"",""cvss3Metrics"":{""A"":""Low"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""Low"",""UI"":""None"",""AV"":""Network"",""I"":""Low""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""commons-beanutils"",""packageName"":""commons-beanutils-core"",""packageVersion"":""1.8.3"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;commons-beanutils:commons-beanutils-core:1.8.3"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""commons-beanutils:commons-beanutils:1.9.4"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2019-10086"",""vulnerabilityDetails"":""In Apache Commons Beanutils 1.9.2, a special BeanIntrospector class was added which allows suppressing the ability for an attacker to access the classloader via the class property available on all Java objects. We, however were not using this by default characteristic of the PropertyUtilsBean."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10086"",""cvss3Severity"":""high"",""cvss3Score"":""7.3"",""cvss3Metrics"":{""A"":""Low"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""Low"",""UI"":""None"",""AV"":""Network"",""I"":""Low""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""commons-beanutils"",""packageName"":""commons-beanutils-core"",""packageVersion"":""1.8.3"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;commons-beanutils:commons-beanutils-core:1.8.3"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""commons-beanutils:commons-beanutils:1.9.4;org.apache.struts:struts2-core:2.0.5"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2014-0114"",""vulnerabilityDetails"":""Apache Commons BeanUtils, as distributed in lib/commons-beanutils-1.8.0.jar in Apache Struts 1.x through 1.3.10 and in other products requiring commons-beanutils through 1.9.2, does not suppress the class property, which allows remote attackers to \""manipulate\"" the ClassLoader and execute arbitrary code via the class parameter, as demonstrated by the passing of this parameter to the getClass method of the ActionForm object in Struts 1."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-0114"",""cvss3Severity"":""high"",""cvss3Score"":""7.3"",""cvss3Metrics"":{""A"":""Low"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""Low"",""UI"":""None"",""AV"":""Network"",""I"":""Low""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""xerces"",""packageName"":""xercesImpl"",""packageVersion"":""2.8.0"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;xom:xom:1.2.5;xerces:xercesImpl:2.8.0"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""xerces:xercesImpl:2.12.2"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2022-23437"",""vulnerabilityDetails"":""There\u0027s a vulnerability within the Apache Xerces Java (XercesJ) XML parser when handling specially crafted XML document payloads. This causes, the XercesJ XML parser to wait in an infinite loop, which may sometimes consume system resources for prolonged duration. This vulnerability is present within XercesJ version 2.12.1 and the previous versions."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23437"",""cvss3Severity"":""medium"",""cvss3Score"":""6.5"",""cvss3Metrics"":{""A"":""High"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""Required"",""AV"":""Network"",""I"":""None""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""org.owasp.antisamy"",""packageName"":""antisamy"",""packageVersion"":""1.5.3"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;org.owasp.antisamy:antisamy:1.5.3"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""1.5.5"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2016-10006"",""vulnerabilityDetails"":""In OWASP AntiSamy before 1.5.5, by submitting a specially crafted input (a tag that supports style with active content), you could bypass the library protections and supply executable code. The impact is XSS."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-10006"",""cvss3Severity"":""medium"",""cvss3Score"":""6.1"",""cvss3Metrics"":{""A"":""None"",""AC"":""Low"",""PR"":""None"",""S"":""Changed"",""C"":""Low"",""UI"":""Required"",""AV"":""Network"",""I"":""Low""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""org.owasp.antisamy"",""packageName"":""antisamy"",""packageVersion"":""1.5.3"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;org.owasp.antisamy:antisamy:1.5.3"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""org.owasp.antisamy:antisamy:1.6.4"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2021-35043"",""vulnerabilityDetails"":""OWASP AntiSamy before 1.6.4 allows XSS via HTML attributes when using the HTML output serializer (XHTML is not affected). This was demonstrated by a javascript: URL with \u0026#00058 as the replacement for the : character."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35043"",""cvss3Severity"":""medium"",""cvss3Score"":""6.1"",""cvss3Metrics"":{""A"":""None"",""AC"":""Low"",""PR"":""None"",""S"":""Changed"",""C"":""Low"",""UI"":""Required"",""AV"":""Network"",""I"":""Low""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""org.owasp.antisamy"",""packageName"":""antisamy"",""packageVersion"":""1.5.3"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;org.owasp.antisamy:antisamy:1.5.3"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""1.5.7"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2017-14735"",""vulnerabilityDetails"":""OWASP AntiSamy before 1.5.7 allows XSS via HTML5 entities, as demonstrated by use of \u0026colon; to construct a javascript: URL."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-14735"",""cvss3Severity"":""medium"",""cvss3Score"":""6.1"",""cvss3Metrics"":{""A"":""None"",""AC"":""Low"",""PR"":""None"",""S"":""Changed"",""C"":""Low"",""UI"":""Required"",""AV"":""Network"",""I"":""Low""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""xerces"",""packageName"":""xercesImpl"",""packageVersion"":""2.8.0"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;xom:xom:1.2.5;xerces:xercesImpl:2.8.0"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""xerces:xercesImpl:Xerces-J_2_12_0"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2013-4002"",""vulnerabilityDetails"":""XMLscanner.java in Apache Xerces2 Java Parser before 2.12.0, as used in the Java Runtime Environment (JRE) in IBM Java 5.0 before 5.0 SR16-FP3, 6 before 6 SR14, 6.0.1 before 6.0.1 SR6, and 7 before 7 SR5 as well as Oracle Java SE 7u40 and earlier, Java SE 6u60 and earlier, Java SE 5.0u51 and earlier, JRockit R28.2.8 and earlier, JRockit R27.7.6 and earlier, Java SE Embedded 7u40 and earlier, and possibly other products allows remote attackers to cause a denial of service via vectors related to XML attribute names."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-4002"",""cvss3Severity"":""medium"",""cvss3Score"":""5.9"",""cvss3Metrics"":{""A"":""High"",""AC"":""High"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""None"",""AV"":""Network"",""I"":""None""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""xerces"",""packageName"":""xercesImpl"",""packageVersion"":""2.8.0"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;xom:xom:1.2.5;xerces:xercesImpl:2.8.0"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""apache-xerces:xercesImpl - 2.9.1;xerces:xercesImpl - 2.3.0,2.9.1-NODEP,2.9.0;org.apache.servicemix.bundles:org.apache.servicemix.bundles.xerces - 2.10.0_1"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2009-2625"",""vulnerabilityDetails"":""XMLScanner.java in Apache Xerces2 Java, as used in Sun Java Runtime Environment (JRE) in JDK and JRE 6 before Update 15 and JDK and JRE 5.0 before Update 20, and in other products, allows remote attackers to cause a denial of service (infinite loop and application hang) via malformed XML input, as demonstrated by the Codenomicon XML fuzzing framework."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2009-2625"",""cvss3Severity"":""medium"",""cvss3Score"":""5.3"",""cvss3Metrics"":{""A"":""Low"",""AC"":""Low"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""None"",""AV"":""Network"",""I"":""None""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""commons-io"",""packageName"":""commons-io"",""packageVersion"":""2.2"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;commons-fileupload:commons-fileupload:1.3.1;commons-io:commons-io:2.2"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""commons-io:commons-io:2.7"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2021-29425"",""vulnerabilityDetails"":""In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like \""//../foo\"", or \""\\\\..\\foo\"", the result would be the same value, thus possibly providing access to files in the parent directory, but not further above (thus \""limited\"" path traversal), if the calling code would use the result to construct a path value."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29425"",""cvss3Severity"":""medium"",""cvss3Score"":""4.8"",""cvss3Metrics"":{""A"":""None"",""AC"":""High"",""PR"":""None"",""S"":""Unchanged"",""C"":""Low"",""UI"":""None"",""AV"":""Network"",""I"":""Low""},""extraData"":{}},{""isOpenPROnVulnerability"":true,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""Java"",""groupId"":""commons-httpclient"",""packageName"":""commons-httpclient"",""packageVersion"":""3.1"",""packageFilePaths"":[""/pom.xml""],""isTransitiveDependency"":true,""dependencyTree"":""org.owasp.esapi:esapi:2.1.0.1;org.owasp.antisamy:antisamy:1.5.3;commons-httpclient:commons-httpclient:3.1"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""commons-httpclient:commons-httpclient - 3.1-jenkins-1,3.1-redhat-3,3.1-HTTPCLIENT-1265"",""isBinary"":false}],""baseBranches"":[""main""],""vulnerabilityIdentifier"":""CVE-2012-5783"",""vulnerabilityDetails"":""Apache Commons HttpClient 3.x, as used in Amazon Flexible Payments Service (FPS) merchant Java SDK and other products, does not verify that the server hostname matches a domain name in the subject\u0027s Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-5783"",""cvss3Severity"":""low"",""cvss3Score"":""3.7"",""cvss3Metrics"":{""A"":""None"",""AC"":""High"",""PR"":""None"",""S"":""Unchanged"",""C"":""None"",""UI"":""None"",""AV"":""Network"",""I"":""Low""},""extraData"":{}}]</REMEDIATE> -->",0,esapi         jar    vulnerabilities  highest severity is             vulnerable library    esapi         jar         path to dependency file   pom xml   path to vulnerable library   home wss scanner    repository commons fileupload commons fileupload       commons fileupload       jar       found in head commit   a href        vulnerabilities    cve   severity     cvss   dependency   type   fixed in   remediation available                                                                                   high         commons fileupload       jar   transitive   n a   ❌             high         bsh core     jar   transitive   n a   ❌             high         commons fileupload       jar   transitive   n a   ❌             high         xercesimpl       jar   transitive   n a   ❌             high         commons fileupload       jar   transitive   n a   ❌             high         xalan       jar   transitive   n a   ❌             high         commons beanutils core       jar   transitive   n a   ❌             high         commons beanutils core       jar   transitive   n a   ❌             medium         xercesimpl       jar   transitive   n a   ❌             medium         antisamy       jar   transitive   n a   ❌             medium         antisamy       jar   transitive   n a   ❌             medium         antisamy       jar   transitive   n a   ❌             medium         xercesimpl       jar   transitive   n a   ❌             medium         xercesimpl       jar   transitive   n a   ❌             medium         commons io     jar   transitive   n a   ❌             low         commons httpclient     jar   transitive   n a   ❌        details        cve             vulnerable library    commons fileupload       jar     the apache commons fileupload component provides a simple yet flexible means of adding support for multipart     file upload functionality to servlets and web applications    library home page   a href     path to dependency file   pom xml   path to vulnerable library   home wss scanner    repository commons fileupload commons fileupload       commons fileupload       jar     dependency hierarchy      esapi         jar  root library         x    commons fileupload       jar    vulnerable library   found in head commit   a href     found in base branch   main               vulnerability details        apache commons fileupload before       diskfileitem file manipulation remote code execution   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                        cve             vulnerable library    bsh core     jar     beanshell core   path to dependency file   pom xml   path to vulnerable library   home wss scanner    repository org beanshell bsh core     bsh core     jar     dependency hierarchy      esapi         jar  root library         x    bsh core     jar    vulnerable library   found in head commit   a href     found in base branch   main               vulnerability details        beanshell  bsh  before      when included on the classpath by an application that uses java serialization or xstream  allows remote attackers to execute arbitrary code via crafted serialized data  related to xthis handler    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  high   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution                      cve             vulnerable library    commons fileupload       jar     the apache commons fileupload component provides a simple yet flexible means of adding support for multipart     file upload functionality to servlets and web applications    library home page   a href     path to dependency file   pom xml   path to vulnerable library   home wss scanner    repository commons fileupload commons fileupload       commons fileupload       jar     dependency hierarchy      esapi         jar  root library         x    commons fileupload       jar    vulnerable library   found in head commit   a href     found in base branch   main               vulnerability details        the multipartstream class in apache commons fileupload before        as used in apache tomcat   x before          x before            x before        and   x before         and other products  allows remote attackers to cause a denial of service  cpu consumption  via a long boundary string    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  org apache tomcat embed tomcat embed core                           org apache tomcat tomcat coyote                           commons fileupload commons fileupload                       cve             vulnerable library    xercesimpl       jar       is the next generation of high performance  fully compliant xml parsers in the     apache xerces family  this new version of xerces introduces the xerces native interface  xni       a complete framework for building parser components and configurations that is extremely     modular and easy to program    library home page   a href     path to dependency file   pom xml   path to vulnerable library   home wss scanner    repository xerces xercesimpl       xercesimpl       jar     dependency hierarchy      esapi         jar  root library        xom       jar          x    xercesimpl       jar    vulnerable library   found in head commit   a href     found in base branch   main               vulnerability details        apache   java parser before       allows remote attackers to cause a denial of service  cpu consumption  via a crafted message to an xml service  which triggers hash table collisions    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                        ws             vulnerable library    commons fileupload       jar     the apache commons fileupload component provides a simple yet flexible means of adding support for multipart     file upload functionality to servlets and web applications    library home page   a href     path to dependency file   pom xml   path to vulnerable library   home wss scanner    repository commons fileupload commons fileupload       commons fileupload       jar     dependency hierarchy      esapi         jar  root library         x    commons fileupload       jar    vulnerable library   found in head commit   a href     found in base branch   main               vulnerability details        the class fileuploadbase in apache commons fileupload before     has potential resource leak   inputstream not closed on exception    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  none     availability impact  none   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution                      cve             vulnerable library    xalan       jar        path to dependency file   pom xml   path to vulnerable library   home wss scanner    repository xalan xalan       xalan       jar     dependency hierarchy      esapi         jar  root library        xom       jar          x    xalan       jar    vulnerable library   found in head commit   a href     found in base branch   main               vulnerability details        the transformerfactory in apache xalan java before       does not properly restrict access to certain properties when feature secure processing is enabled  which allows remote attackers to bypass expected restrictions and load arbitrary classes or access external resources via a crafted     xalan content header      xalan entities      xslt content header  or     xslt entities property  or a java property that is bound to the xslt     system property function    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  low     integrity impact  low     availability impact  low   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution                        cve             vulnerable library    commons beanutils core       jar     the apache software foundation provides support for the apache community of open source software projects      the apache projects are characterized by a collaborative  consensus based development process  an open and     pragmatic software license  and a desire to create high quality software that leads the way in its field      we consider ourselves not simply a group of projects sharing a server  but rather a community of developers     and users    path to dependency file   pom xml   path to vulnerable library   home wss scanner    repository commons beanutils commons beanutils core       commons beanutils core       jar     dependency hierarchy      esapi         jar  root library         x    commons beanutils core       jar    vulnerable library   found in head commit   a href     found in base branch   main               vulnerability details        in apache commons beanutils        a special beanintrospector class was added which allows suppressing the ability for an attacker to access the classloader via the class property available on all java objects  we  however were not using this by default characteristic of the propertyutilsbean    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  low     integrity impact  low     availability impact  low   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution  commons beanutils commons beanutils                       cve             vulnerable library    commons beanutils core       jar     the apache software foundation provides support for the apache community of open source software projects      the apache projects are characterized by a collaborative  consensus based development process  an open and     pragmatic software license  and a desire to create high quality software that leads the way in its field      we consider ourselves not simply a group of projects sharing a server  but rather a community of developers     and users    path to dependency file   pom xml   path to vulnerable library   home wss scanner    repository commons beanutils commons beanutils core       commons beanutils core       jar     dependency hierarchy      esapi         jar  root library         x    commons beanutils core       jar    vulnerable library   found in head commit   a href     found in base branch   main               vulnerability details        apache commons beanutils  as distributed in lib commons beanutils       jar in apache struts   x through       and in other products requiring commons beanutils through        does not suppress the class property  which allows remote attackers to  manipulate  the classloader and execute arbitrary code via the class parameter  as demonstrated by the passing of this parameter to the getclass method of the actionform object in struts      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  low     integrity impact  low     availability impact  low   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution  commons beanutils commons beanutils       org apache struts   core                       cve             vulnerable library    xercesimpl       jar       is the next generation of high performance  fully compliant xml parsers in the     apache xerces family  this new version of xerces introduces the xerces native interface  xni       a complete framework for building parser components and configurations that is extremely     modular and easy to program    library home page   a href     path to dependency file   pom xml   path to vulnerable library   home wss scanner    repository xerces xercesimpl       xercesimpl       jar     dependency hierarchy      esapi         jar  root library        xom       jar          x    xercesimpl       jar    vulnerable library   found in head commit   a href     found in base branch   main               vulnerability details        there s a vulnerability within the apache xerces java  xercesj  xml parser when handling specially crafted xml document payloads  this causes  the xercesj xml parser to wait in an infinite loop  which may sometimes consume system resources for prolonged duration  this vulnerability is present within xercesj version       and the previous versions    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  required     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  high   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution  xerces xercesimpl                       cve             vulnerable library    antisamy       jar     the owasp antisamy project is a collection of apis for safely allowing users to supply their own html         and css without exposing the site to xss vulnerabilities    library home page   a href     path to dependency file   pom xml   path to vulnerable library   home wss scanner    repository org owasp antisamy antisamy       antisamy       jar     dependency hierarchy      esapi         jar  root library         x    antisamy       jar    vulnerable library   found in head commit   a href     found in base branch   main               vulnerability details        in owasp antisamy before        by submitting a specially crafted input  a tag that supports style with active content   you could bypass the library protections and supply executable code  the impact is xss    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  required     scope  changed   impact metrics      confidentiality impact  low     integrity impact  low     availability impact  none   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution                        cve             vulnerable library    antisamy       jar     the owasp antisamy project is a collection of apis for safely allowing users to supply their own html         and css without exposing the site to xss vulnerabilities    library home page   a href     path to dependency file   pom xml   path to vulnerable library   home wss scanner    repository org owasp antisamy antisamy       antisamy       jar     dependency hierarchy      esapi         jar  root library         x    antisamy       jar    vulnerable library   found in head commit   a href     found in base branch   main               vulnerability details        owasp antisamy before       allows xss via html attributes when using the html output serializer  xhtml is not affected   this was demonstrated by a javascript  url with     as the replacement for the   character    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  required     scope  changed   impact metrics      confidentiality impact  low     integrity impact  low     availability impact  none   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution  org owasp antisamy antisamy                       cve             vulnerable library    antisamy       jar     the owasp antisamy project is a collection of apis for safely allowing users to supply their own html         and css without exposing the site to xss vulnerabilities    library home page   a href     path to dependency file   pom xml   path to vulnerable library   home wss scanner    repository org owasp antisamy antisamy       antisamy       jar     dependency hierarchy      esapi         jar  root library         x    antisamy       jar    vulnerable library   found in head commit   a href     found in base branch   main               vulnerability details        owasp antisamy before       allows xss via   entities  as demonstrated by use of  colon  to construct a javascript  url    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  required     scope  changed   impact metrics      confidentiality impact  low     integrity impact  low     availability impact  none   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution                        cve             vulnerable library    xercesimpl       jar       is the next generation of high performance  fully compliant xml parsers in the     apache xerces family  this new version of xerces introduces the xerces native interface  xni       a complete framework for building parser components and configurations that is extremely     modular and easy to program    library home page   a href     path to dependency file   pom xml   path to vulnerable library   home wss scanner    repository xerces xercesimpl       xercesimpl       jar     dependency hierarchy      esapi         jar  root library        xom       jar          x    xercesimpl       jar    vulnerable library   found in head commit   a href     found in base branch   main               vulnerability details        xmlscanner java in apache   java parser before        as used in the java runtime environment  jre  in ibm java     before            before            before          and   before     as well as oracle java se   and earlier  java se   and earlier  java se     and earlier  jrockit       and earlier  jrockit       and earlier  java se embedded   and earlier  and possibly other products allows remote attackers to cause a denial of service via vectors related to xml attribute names    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  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  xerces xercesimpl xerces j                       cve             vulnerable library    xercesimpl       jar       is the next generation of high performance  fully compliant xml parsers in the     apache xerces family  this new version of xerces introduces the xerces native interface  xni       a complete framework for building parser components and configurations that is extremely     modular and easy to program    library home page   a href     path to dependency file   pom xml   path to vulnerable library   home wss scanner    repository xerces xercesimpl       xercesimpl       jar     dependency hierarchy      esapi         jar  root library        xom       jar          x    xercesimpl       jar    vulnerable library   found in head commit   a href     found in base branch   main               vulnerability details        xmlscanner java in apache   java  as used in sun java runtime environment  jre  in jdk and jre   before update   and jdk and jre     before update    and in other products  allows remote attackers to cause a denial of service  infinite loop and application hang  via malformed xml input  as demonstrated by the codenomicon xml fuzzing framework    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  low   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution  apache xerces xercesimpl         xerces xercesimpl               nodep       org apache servicemix bundles org apache servicemix bundles xerces                           cve             vulnerable library    commons io     jar     the commons io library contains utility classes  stream implementations  file filters   file comparators  endian transformation classes  and much more    library home page   a href     path to dependency file   pom xml   path to vulnerable library   home wss scanner    repository commons io commons io     commons io     jar     dependency hierarchy      esapi         jar  root library        commons fileupload       jar          x    commons io     jar    vulnerable library   found in head commit   a href     found in base branch   main               vulnerability details        in apache commons io before      when invoking the method filenameutils normalize with an improper input string  like       foo   or       foo   the result would be the same value  thus possibly providing access to files in the parent directory  but not further above  thus  limited  path traversal   if the calling code would use the result to construct a path value    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  low     integrity impact  low     availability impact  none   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution  commons io commons io                     cve             vulnerable library    commons httpclient     jar     the httpclient  component supports the client side of rfc    http       and rfc    http        several related specifications  rfc    cookies    rfc    http authentication    etc    and provides a framework by which new request types  methods  or http extensions can be created easily    path to dependency file   pom xml   path to vulnerable library   home wss scanner    repository commons httpclient commons httpclient     commons httpclient     jar     dependency hierarchy      esapi         jar  root library        antisamy       jar          x    commons httpclient     jar    vulnerable library   found in head commit   a href     found in base branch   main               vulnerability details        apache commons httpclient   x  as used in amazon flexible payments service  fps  merchant java sdk and other products  does not verify that the server hostname matches a domain name in the subject s common name  cn  or subjectaltname field of the x   certificate  which allows man in the middle attackers to spoof ssl servers via an arbitrary valid certificate    publish date         url   a href               cvss   score details            base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  low     availability impact  none   for more information on   scores  click  a href                suggested fix     type  upgrade version   origin   a href     release date          fix resolution  commons httpclient commons httpclient       jenkins       redhat       httpclient                  istransitivedependency  true  dependencytree   org owasp esapi esapi         commons fileupload commons fileupload         isminimumfixversionavailable  true  minimumfixversion           isbinary  false    basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   apache commons fileupload before       diskfileitem file manipulation remote code execution   vulnerabilityurl       istransitivedependency  true  dependencytree   org owasp esapi esapi         org beanshell bsh core       isminimumfixversionavailable  true  minimumfixversion         isbinary  false    basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   beanshell  bsh  before      when included on the classpath by an application that uses java serialization or xstream  allows remote attackers to execute arbitrary code via crafted serialized data  related to xthis handler    vulnerabilityurl       istransitivedependency  true  dependencytree   org owasp esapi esapi         commons fileupload commons fileupload         isminimumfixversionavailable  true  minimumfixversion   org apache tomcat embed tomcat embed core                           org apache tomcat tomcat coyote                           commons fileupload commons fileupload         isbinary  false    basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   the multipartstream class in apache commons fileupload before        as used in apache tomcat   x before          x before            x before        and   x before         and other products  allows remote attackers to cause a denial of service  cpu consumption  via a long boundary string    vulnerabilityurl       istransitivedependency  true  dependencytree   org owasp esapi esapi         xom xom       xerces xercesimpl         isminimumfixversionavailable  true  minimumfixversion           isbinary  false    basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   apache   java parser before       allows remote attackers to cause a denial of service  cpu consumption  via a crafted message to an xml service  which triggers hash table collisions    vulnerabilityurl       istransitivedependency  true  dependencytree   org owasp esapi esapi         commons fileupload commons fileupload         isminimumfixversionavailable  true  minimumfixversion         isbinary  false    basebranches     vulnerabilityidentifier   ws       vulnerabilitydetails   the class fileuploadbase in apache commons fileupload before     has potential resource leak   inputstream not closed on exception    vulnerabilityurl       istransitivedependency  true  dependencytree   org owasp esapi esapi         xom xom       xalan xalan         isminimumfixversionavailable  true  minimumfixversion           isbinary  false    basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   the transformerfactory in apache xalan java before       does not properly restrict access to certain properties when feature secure processing is enabled  which allows remote attackers to bypass expected restrictions and load arbitrary classes or access external resources via a crafted     xalan content header      xalan entities      xslt content header  or     xslt entities property  or a java property that is bound to the xslt     system property function    vulnerabilityurl       istransitivedependency  true  dependencytree   org owasp esapi esapi         commons beanutils commons beanutils core         isminimumfixversionavailable  true  minimumfixversion   commons beanutils commons beanutils         isbinary  false    basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   in apache commons beanutils        a special beanintrospector class was added which allows suppressing the ability for an attacker to access the classloader via the class property available on all java objects  we  however were not using this by default characteristic of the propertyutilsbean    vulnerabilityurl       istransitivedependency  true  dependencytree   org owasp esapi esapi         commons beanutils commons beanutils core         isminimumfixversionavailable  true  minimumfixversion   commons beanutils commons beanutils       org apache struts   core         isbinary  false    basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   apache commons beanutils  as distributed in lib commons beanutils       jar in apache struts   x through       and in other products requiring commons beanutils through        does not suppress the class property  which allows remote attackers to   manipulate   the classloader and execute arbitrary code via the class parameter  as demonstrated by the passing of this parameter to the getclass method of the actionform object in struts      vulnerabilityurl       istransitivedependency  true  dependencytree   org owasp esapi esapi         xom xom       xerces xercesimpl         isminimumfixversionavailable  true  minimumfixversion   xerces xercesimpl         isbinary  false    basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   there   a vulnerability within the apache xerces java  xercesj  xml parser when handling specially crafted xml document payloads  this causes  the xercesj xml parser to wait in an infinite loop  which may sometimes consume system resources for prolonged duration  this vulnerability is present within xercesj version       and the previous versions    vulnerabilityurl       istransitivedependency  true  dependencytree   org owasp esapi esapi         org owasp antisamy antisamy         isminimumfixversionavailable  true  minimumfixversion           isbinary  false    basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   in owasp antisamy before        by submitting a specially crafted input  a tag that supports style with active content   you could bypass the library protections and supply executable code  the impact is xss    vulnerabilityurl       istransitivedependency  true  dependencytree   org owasp esapi esapi         org owasp antisamy antisamy         isminimumfixversionavailable  true  minimumfixversion   org owasp antisamy antisamy         isbinary  false    basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   owasp antisamy before       allows xss via html attributes when using the html output serializer  xhtml is not affected   this was demonstrated by a javascript  url with      as the replacement for the   character    vulnerabilityurl       istransitivedependency  true  dependencytree   org owasp esapi esapi         org owasp antisamy antisamy         isminimumfixversionavailable  true  minimumfixversion           isbinary  false    basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   owasp antisamy before       allows xss via   entities  as demonstrated by use of     to construct a javascript  url    vulnerabilityurl       istransitivedependency  true  dependencytree   org owasp esapi esapi         xom xom       xerces xercesimpl         isminimumfixversionavailable  true  minimumfixversion   xerces xercesimpl xerces j         isbinary  false    basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   xmlscanner java in apache   java parser before        as used in the java runtime environment  jre  in ibm java     before            before            before          and   before     as well as oracle java se   and earlier  java se   and earlier  java se     and earlier  jrockit       and earlier  jrockit       and earlier  java se embedded   and earlier  and possibly other products allows remote attackers to cause a denial of service via vectors related to xml attribute names    vulnerabilityurl       istransitivedependency  true  dependencytree   org owasp esapi esapi         xom xom       xerces xercesimpl         isminimumfixversionavailable  true  minimumfixversion   apache xerces xercesimpl         xerces xercesimpl               nodep       org apache servicemix bundles org apache servicemix bundles xerces             isbinary  false    basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   xmlscanner java in apache   java  as used in sun java runtime environment  jre  in jdk and jre   before update   and jdk and jre     before update    and in other products  allows remote attackers to cause a denial of service  infinite loop and application hang  via malformed xml input  as demonstrated by the codenomicon xml fuzzing framework    vulnerabilityurl       istransitivedependency  true  dependencytree   org owasp esapi esapi         commons fileupload commons fileupload       commons io commons io       isminimumfixversionavailable  true  minimumfixversion   commons io commons io       isbinary  false    basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   in apache commons io before      when invoking the method filenameutils normalize with an improper input string  like        foo    or           foo    the result would be the same value  thus possibly providing access to files in the parent directory  but not further above  thus   limited   path traversal   if the calling code would use the result to construct a path value    vulnerabilityurl       istransitivedependency  true  dependencytree   org owasp esapi esapi         org owasp antisamy antisamy       commons httpclient commons httpclient       isminimumfixversionavailable  true  minimumfixversion   commons httpclient commons httpclient       jenkins       redhat       httpclient     isbinary  false    basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   apache commons httpclient   x  as used in amazon flexible payments service  fps  merchant java sdk and other products  does not verify that the server hostname matches a domain name in the subject   common name  cn  or subjectaltname field of the x   certificate  which allows man in the middle attackers to spoof ssl servers via an arbitrary valid certificate    vulnerabilityurl        ,0
338108,24571806268.0,IssuesEvent,2022-10-13 09:13:28,golang/go,https://api.github.com/repos/golang/go,closed,x/website: documentation no longer suggests to add $GOPATH/bin to the user's PATH,Documentation NeedsFix website,"

### Does this issue reproduce with the latest release?

Yes

### 

</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->

I went to the installation page.

### What did you expect to see?

That adding `$HOME/go/bin` to your path was necessary to make `go install` function as expected.

### What did you see instead?

A lot of bug reports on my project that they can't run the project binary after installing.
",1.0,"x/website: documentation no longer suggests to add $GOPATH/bin to the user's PATH - 

### Does this issue reproduce with the latest release?

Yes

### 

</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->

I went to the installation page.

### What did you expect to see?

That adding `$HOME/go/bin` to your path was necessary to make `go install` function as expected.

### What did you see instead?

A lot of bug reports on my project that they can't run the project binary after installing.
",1,x website  documentation no longer suggests to add  gopath bin to the user s path         does this issue reproduce with the latest release   yes                what did you do        if possible  provide a recipe for reproducing the error  a complete runnable program is good  a link on go dev play is best       i went to the installation page       what did you expect to see   that adding   home go bin  to your path was necessary to make  go install  function as expected       what did you see instead   a lot of bug reports on my project that they can t run the project binary after installing  ,1
21888,4757087245.0,IssuesEvent,2016-10-24 15:39:20,golang/go,https://api.github.com/repos/golang/go,closed,log: document Print and Printf adding newlines more,Documentation NeedsFix,"Please answer these questions before submitting your issue. Thanks!

1. What version of Go are you using (`go version`)?
go version go1.6.3 linux/386

2. What operating system and processor architecture are you using (`go env`)?
GOARCH=""386""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""386""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/usr2/ps/isp/go""
GORACE=""""
GOROOT=""/usr/local/go""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_386""
GO15VENDOREXPERIMENT=""1""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m32 -pthread -fmessage-length=0""
CXX=""g++""
CGO_ENABLED=""1""

3. What did you do?
https://play.golang.org/p/qF9NrwS_2Y

4. What did you expect to see?
2009/11/10 23:00:00 1st Line.
2009/11/10 23:00:00 2nd Line. I want on 2nd line as well.
2009/11/10 23:00:00 3rd Line.I want on the 3rd line

5. What did you see instead?
2009/11/10 23:00:00 1st Line.
2009/11/10 23:00:00 2nd Line.
2009/11/10 23:00:00  I want on 2nd line as well.
2009/11/10 23:00:00 3rd Line.
2009/11/10 23:00:00 I want on the 3rd line

",1.0,"log: document Print and Printf adding newlines more - Please answer these questions before submitting your issue. Thanks!

1. What version of Go are you using (`go version`)?
go version go1.6.3 linux/386

2. What operating system and processor architecture are you using (`go env`)?
GOARCH=""386""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""386""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/usr2/ps/isp/go""
GORACE=""""
GOROOT=""/usr/local/go""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_386""
GO15VENDOREXPERIMENT=""1""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m32 -pthread -fmessage-length=0""
CXX=""g++""
CGO_ENABLED=""1""

3. What did you do?
https://play.golang.org/p/qF9NrwS_2Y

4. What did you expect to see?
2009/11/10 23:00:00 1st Line.
2009/11/10 23:00:00 2nd Line. I want on 2nd line as well.
2009/11/10 23:00:00 3rd Line.I want on the 3rd line

5. What did you see instead?
2009/11/10 23:00:00 1st Line.
2009/11/10 23:00:00 2nd Line.
2009/11/10 23:00:00  I want on 2nd line as well.
2009/11/10 23:00:00 3rd Line.
2009/11/10 23:00:00 I want on the 3rd line

",1,log  document print and printf adding newlines more   please answer these questions before submitting your issue  thanks        what version of go are you using   go version     go version       linux         what operating system and processor architecture are you using   go env     goarch      gobin     goexe     gohostarch      gohostos  linux   goos  linux   gopath     ps isp go   gorace     goroot   usr local go   gotooldir   usr local go pkg tool linux            cc  gcc   gogccflags   fpic     pthread  fmessage length     cxx  g     cgo enabled           what did you do           what did you expect to see                 line                 line  i want on   line as well                 line i want on the   line       what did you see instead                 line                 line                i want on   line as well                 line               i want on the   line    ,1
218294,16982724316.0,IssuesEvent,2021-06-30 10:53:30,elastic/elasticsearch,https://api.github.com/repos/elastic/elasticsearch,opened,Reproducible Failure in org.elasticsearch.http.snapshots.RestGetSnapshotsCancellationIT.testGetSnapshotsCancellation,:Distributed/Snapshot/Restore >test-failure,"```
./gradlew ':qa:smoke-test-http:integTest' --tests ""org.elasticsearch.http.snapshots.RestGetSnapshotsCancellationIT.testGetSnapshotsCancellation"" -Dtests.seed=D9402B0D9FE0E9A5 -Dtests.locale=ar-LY -Dtests.timezone=America/Aruba -Druntime.java=11
```

reproducibly fails in ~1% of runs (adding details in a sec).
",1.0,"Reproducible Failure in org.elasticsearch.http.snapshots.RestGetSnapshotsCancellationIT.testGetSnapshotsCancellation - ```
./gradlew ':qa:smoke-test-http:integTest' --tests ""org.elasticsearch.http.snapshots.RestGetSnapshotsCancellationIT.testGetSnapshotsCancellation"" -Dtests.seed=D9402B0D9FE0E9A5 -Dtests.locale=ar-LY -Dtests.timezone=America/Aruba -Druntime.java=11
```

reproducibly fails in ~1% of runs (adding details in a sec).
",0,reproducible failure in org elasticsearch http snapshots restgetsnapshotscancellationit testgetsnapshotscancellation          gradlew   qa smoke test http integtest    tests  org elasticsearch http snapshots restgetsnapshotscancellationit testgetsnapshotscancellation   dtests seed    dtests locale ar ly  dtests timezone america aruba  druntime java           reproducibly fails in     of runs  adding details in a sec    ,0
42493,6986040990.0,IssuesEvent,2017-12-14 00:59:04,golang/go,https://api.github.com/repos/golang/go,closed,testing: clarity of -timeout flag,Documentation,"This is directly related to #20090, opening a new issue because I'm not sure whether closed issues are supposed to be reopened.

The description of the `-timeout` flag has changed twice for Go 1.9. The first change (done by me) was intended to clarify that the timeout applies per package. The latest revision, referring to ""a test binary"", is certainly correct, but in my experience many gophers do not know that the tests from each package is executed as a separate test binary. This can be inferred from the help text, but it's not explicit and likely to be ambiguous to many.

There may well be a better description than what I provided. I'd just like for the documentation to be clear without needing to understand exactly how test binaries are built and executed.

Original Text:

> -timeout t
>     If a test runs longer than t, panic.
>     The default is 10 minutes (10m).


https://golang.org/cl/45816:

> -timeout d
>     If the **cumulative test time for a package** runs longer than
>     duration d, panic. Timeout is disabled if set to 0.
>     The default is 10 minutes (10m).

https://golang.org/cl/47571:

> -timeout d
>     If **a test binary** runs longer than duration d, panic.
>     The default is 10 minutes (10m).

Notes:
* Emphasis added.
* The ""Timeout is disabled if set to 0"" text can be ignored. It was a mistake on my part.",1.0,"testing: clarity of -timeout flag - This is directly related to #20090, opening a new issue because I'm not sure whether closed issues are supposed to be reopened.

The description of the `-timeout` flag has changed twice for Go 1.9. The first change (done by me) was intended to clarify that the timeout applies per package. The latest revision, referring to ""a test binary"", is certainly correct, but in my experience many gophers do not know that the tests from each package is executed as a separate test binary. This can be inferred from the help text, but it's not explicit and likely to be ambiguous to many.

There may well be a better description than what I provided. I'd just like for the documentation to be clear without needing to understand exactly how test binaries are built and executed.

Original Text:

> -timeout t
>     If a test runs longer than t, panic.
>     The default is 10 minutes (10m).


https://golang.org/cl/45816:

> -timeout d
>     If the **cumulative test time for a package** runs longer than
>     duration d, panic. Timeout is disabled if set to 0.
>     The default is 10 minutes (10m).

https://golang.org/cl/47571:

> -timeout d
>     If **a test binary** runs longer than duration d, panic.
>     The default is 10 minutes (10m).

Notes:
* Emphasis added.
* The ""Timeout is disabled if set to 0"" text can be ignored. It was a mistake on my part.",1,testing  clarity of  timeout flag   this is directly related to     opening a new issue because i m not sure whether closed issues are supposed to be reopened     the description of the   timeout  flag has changed twice for go      the first change  done by me  was intended to clarify that the timeout applies per package  the latest revision  referring to  a test binary   is certainly correct  but in my experience many gophers do not know that the tests from each package is executed as a separate test binary  this can be inferred from the help text  but it s not explicit and likely to be ambiguous to many     there may well be a better description than what i provided  i d just like for the documentation to be clear without needing to understand exactly how test binaries are built and executed     original text        timeout t        if a test runs longer than t  panic         the default is   minutes                   timeout d        if the   cumulative test time for a package   runs longer than        duration d  panic  timeout is disabled if set to           the default is   minutes                 timeout d        if   a test binary   runs longer than duration d  panic         the default is   minutes         notes     emphasis added     the  timeout is disabled if set to    text can be ignored  it was a mistake on my part ,1
50575,10526488435.0,IssuesEvent,2019-09-30 17:12:23,nmap/nmap,https://api.github.com/repos/nmap/nmap,closed,npcap diag generator regex doesn't handle continuation lines properly,Npcap enhancement have code,"I used npcap to generate a diag file and it was full of lines that were whited out at the beginning, for example:
~~~
HKLM:\SYSTEM\CurrentControlSet\Services\npcap:


                   M\CurrentControlSet\Services\npcap
                   M\CurrentControlSet\Services
Type             : 1
Start            : 1
ErrorControl     : 1
Tag              : 92
ImagePath        : system32\DRIVERS\npcap.sys
DisplayName      : Npcap Packet Driver (NPCAP)
Group            : NDIS
Description      : Npcap Packet Driver (NPCAP)
NdisMajorVersion : 6
NdisMinorVersion : 1

~~~

~~~
                   M\CurrentControlSet\Services\npcap
                   M\CurrentControlSet\Services
~~~
they're continuation lines the start line filtered by `? { $_ -NOTMATCH '^ps.+' }`:
~~~
PSPath           : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTE
                   M\CurrentControlSet\Services\npcap
PSParentPath     : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTE
                   M\CurrentControlSet\Services
~~~
that's because out-string is using terminal width (I think). there's no unwrap option but you can specify width Int32 max like object | out-string -stream -Width 2147483647 | regex
~~~
write_report (""HKLM:\SYSTEM\CurrentControlSet\Services\npcap:"")
(Get-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Services\npcap | out-string -stream -Width 2147483647 | ? { $_ -NOTMATCH '^ps.+' })
~~~

Windows 7 x64 Ultimate, Wireshark 3.0.5, npcap .09983

",1.0,"npcap diag generator regex doesn't handle continuation lines properly - I used npcap to generate a diag file and it was full of lines that were whited out at the beginning, for example:
~~~
HKLM:\SYSTEM\CurrentControlSet\Services\npcap:


                   M\CurrentControlSet\Services\npcap
                   M\CurrentControlSet\Services
Type             : 1
Start            : 1
ErrorControl     : 1
Tag              : 92
ImagePath        : system32\DRIVERS\npcap.sys
DisplayName      : Npcap Packet Driver (NPCAP)
Group            : NDIS
Description      : Npcap Packet Driver (NPCAP)
NdisMajorVersion : 6
NdisMinorVersion : 1

~~~

~~~
                   M\CurrentControlSet\Services\npcap
                   M\CurrentControlSet\Services
~~~
they're continuation lines the start line filtered by `? { $_ -NOTMATCH '^ps.+' }`:
~~~
PSPath           : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTE
                   M\CurrentControlSet\Services\npcap
PSParentPath     : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTE
                   M\CurrentControlSet\Services
~~~
that's because out-string is using terminal width (I think). there's no unwrap option but you can specify width Int32 max like object | out-string -stream -Width 2147483647 | regex
~~~
write_report (""HKLM:\SYSTEM\CurrentControlSet\Services\npcap:"")
(Get-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Services\npcap | out-string -stream -Width 2147483647 | ? { $_ -NOTMATCH '^ps.+' })
~~~

Windows 7 x64 Ultimate, Wireshark 3.0.5, npcap .09983

",0,npcap diag generator regex doesn t handle continuation lines properly   i used npcap to generate a diag file and it was full of lines that were whited out at the beginning  for example        hklm  system currentcontrolset services npcap                          m currentcontrolset services npcap                     m currentcontrolset services  type                  start                 errorcontrol          tag                   imagepath            drivers npcap sys  displayname        npcap packet driver  npcap   group              ndis  description        npcap packet driver  npcap   ndismajorversion      ndisminorversion                                       m currentcontrolset services npcap                     m currentcontrolset services       they re continuation lines the start line filtered by          notmatch   ps              pspath             microsoft powershell core registry  hkey local machine syste                     m currentcontrolset services npcap  psparentpath       microsoft powershell core registry  hkey local machine syste                     m currentcontrolset services       that s because out string is using terminal width  i think   there s no unwrap option but you can specify width   max like object   out string  stream  width     regex       write report   hklm  system currentcontrolset services npcap      get itemproperty hklm  system currentcontrolset services npcap   out string  stream  width             notmatch   ps               windows     ultimate  wireshark        npcap       ,0
23773,4974258524.0,IssuesEvent,2016-12-06 05:31:25,golang/go,https://api.github.com/repos/golang/go,opened,doc: installation docs don't list all OS architectures,Documentation,"https://beta.golang.org/doc/install says:

Operating System: ""Linux 2.6.23 or later with glibc"" .... Architectures: ""amd64, 386, arm""

That's missing a bunch.

Also, for FreeBSD, it only lists amd64, but 386 and arm are also supported.

/cc @minux ",1.0,"doc: installation docs don't list all OS architectures - https://beta.golang.org/doc/install says:

Operating System: ""Linux 2.6.23 or later with glibc"" .... Architectures: ""amd64, 386, arm""

That's missing a bunch.

Also, for FreeBSD, it only lists amd64, but 386 and arm are also supported.

/cc @minux ",1,doc  installation docs don t list all os architectures     says     operating system   linux       or later with glibc       architectures         arm     that s missing a bunch     also  for freebsd  it only lists    but   and arm are also supported      cc  minux ,1
310831,9524700171.0,IssuesEvent,2019-04-28 06:04:36,projectacrn/acrn-hypervisor,https://api.github.com/repos/projectacrn/acrn-hypervisor,closed, [APL/KBL/UP2][HV][ACRN-UNIT-TEST]  ,priority: P2-High status: Assigned type: bug,"Environment
 MRB with hypervisor & acrn-unit-test : apic.flat & ioapic.flat_
 static void test_physical_broadcast(void) @ apic.c 
 static void test_ioapic_level_retrigger(void) @ioapic.c

HW/Board

MRB

Build link

Image info

DM version is: 0.5-unstable-22b0a15a-dirty (daily tag:), build by root@2019-03-13 05:39:25_

sos:Linux clearlinux 4.19.23-quilt-2e5dc0ac-04933-g6273870f3fcf #1 SMP PREEMPT Wed Mar 13 03:42:54 UTC 2019 x86_64 GNU/Linux_

Steps
 @apic.c  static void test_physical_broadcast(void) failed_
 on smp system. one cpu hang when executing ""hlt"" instruction_ 
 writing ipi message to apic chip_

Expected result

should awake hang cpu

Actual result

test failed . it seems that vcpu which hang does not awake._

Reproduce rate

100%_

Debugging info

aging enabled_
_0 = 80010011_
_cr3 = 459000_
_cr4 = 20_
_apic version: 60010_
_PASS: apic existence_
_PASS: xapic id matches cpuid_
_FAIL: writeable xapic id_
_[6440508832us][cpu=1][sev=3][seq=84]:vlapic: vm_apicid2vcpu_id: bad lapicid 255P_
_ASS: non-writeable x2apic id_
_PASS: sane x2apic id_
_PASS: x2apic id matches cpuid_
_PASS: correct xapic id after reset_
_PASS: self ipi_
_starting broadcast (x2apic)_
_FAIL: APIC physical broadcast address_
_PASS: APIC physical broadcast shorthand_
_PASS: nmi-after-sti_
_FAIL: multiple nmi_
_PASS: APIC LVT timer one shot_
_starting apic change mode_
_PASS: TMICT value reset_
_PASS: TMCCT should have a non-zero value_
_PASS: TMCCT should have reached 0_",1.0," [APL/KBL/UP2][HV][ACRN-UNIT-TEST]   - Environment
 MRB with hypervisor & acrn-unit-test : apic.flat & ioapic.flat_
 static void test_physical_broadcast(void) @ apic.c 
 static void test_ioapic_level_retrigger(void) @ioapic.c

HW/Board

MRB

Build link

Image info

DM version is: 0.5-unstable-22b0a15a-dirty (daily tag:), build by root@2019-03-13 05:39:25_

sos:Linux clearlinux 4.19.23-quilt-2e5dc0ac-04933-g6273870f3fcf #1 SMP PREEMPT Wed Mar 13 03:42:54 UTC 2019 x86_64 GNU/Linux_

Steps
 @apic.c  static void test_physical_broadcast(void) failed_
 on smp system. one cpu hang when executing ""hlt"" instruction_ 
 writing ipi message to apic chip_

Expected result

should awake hang cpu

Actual result

test failed . it seems that vcpu which hang does not awake._

Reproduce rate

100%_

Debugging info

aging enabled_
_0 = 80010011_
_cr3 = 459000_
_cr4 = 20_
_apic version: 60010_
_PASS: apic existence_
_PASS: xapic id matches cpuid_
_FAIL: writeable xapic id_
_[6440508832us][cpu=1][sev=3][seq=84]:vlapic: vm_apicid2vcpu_id: bad lapicid 255P_
_ASS: non-writeable x2apic id_
_PASS: sane x2apic id_
_PASS: x2apic id matches cpuid_
_PASS: correct xapic id after reset_
_PASS: self ipi_
_starting broadcast (x2apic)_
_FAIL: APIC physical broadcast address_
_PASS: APIC physical broadcast shorthand_
_PASS: nmi-after-sti_
_FAIL: multiple nmi_
_PASS: APIC LVT timer one shot_
_starting apic change mode_
_PASS: TMICT value reset_
_PASS: TMCCT should have a non-zero value_
_PASS: TMCCT should have reached 0_",0,         environment   mrb with hypervisor   acrn unit test   apic flat   ioapic flat    static void test physical broadcast void    apic c    static void test ioapic level retrigger void   ioapic c    hw board    mrb    build link    image info    dm version is      unstable   dirty  daily tag    build by root                 sos linux clearlinux       quilt          smp preempt wed mar         utc       gnu linux     steps    apic c  static void test physical broadcast void  failed    on smp system  one cpu hang when executing  hlt  instruction     writing ipi message to apic chip     expected result    should awake hang cpu    actual result    test failed   it seems that vcpu which hang does not awake      reproduce rate           debugging info    aging enabled                               apic version       pass  apic existence    pass  xapic id matches cpuid    fail  writeable xapic id         vlapic  vm   id  bad lapicid      ass  non writeable   id    pass  sane   id    pass    id matches cpuid    pass  correct xapic id after reset    pass  self ipi    starting broadcast        fail  apic physical broadcast address    pass  apic physical broadcast shorthand    pass  nmi after sti    fail  multiple nmi    pass  apic lvt timer one shot    starting apic change mode    pass  tmict value reset    pass  tmcct should have a non zero value    pass  tmcct should have reached   ,0
82521,10293662551.0,IssuesEvent,2019-08-27 16:55:24,golang/go,https://api.github.com/repos/golang/go,closed,errors: better document Go 1.13 Is/As/Unwrap features,Documentation NeedsDecision release-blocker,"See the current version of the Go 1.13 documentation for the errors package here: https://tip.golang.org/pkg/errors/

If I hadn't read the [error values design](https://go.googlesource.com/proposal/+/master/design/go2draft-error-inspection.md) and related discussion, I think I'd have a hard time understanding the new APIs. Some questions I might have include:

* Is and As documentation refers to ""err's chain"". What is a chain?
* Is, As, and Unwrap all refer to optional interface methods of the same names. When should errors implement those interfaces?
* What is the relationship between Is, As, and Unwrap?
* As an application developer, how should I be using Is, As, and Unwrap? How about as the author of a package others use?",1.0,"errors: better document Go 1.13 Is/As/Unwrap features - See the current version of the Go 1.13 documentation for the errors package here: https://tip.golang.org/pkg/errors/

If I hadn't read the [error values design](https://go.googlesource.com/proposal/+/master/design/go2draft-error-inspection.md) and related discussion, I think I'd have a hard time understanding the new APIs. Some questions I might have include:

* Is and As documentation refers to ""err's chain"". What is a chain?
* Is, As, and Unwrap all refer to optional interface methods of the same names. When should errors implement those interfaces?
* What is the relationship between Is, As, and Unwrap?
* As an application developer, how should I be using Is, As, and Unwrap? How about as the author of a package others use?",1,errors  better document go     is as unwrap features   see the current version of the go     documentation for the errors package here       if i hadn t read the     and related discussion  i think i d have a hard time understanding the new apis  some questions i might have include       is and as documentation refers to  err s chain   what is a chain     is  as  and unwrap all refer to optional interface methods of the same names  when should errors implement those interfaces     what is the relationship between is  as  and unwrap     as an application developer  how should i be using is  as  and unwrap  how about as the author of a package others use ,1
82651,10302240572.0,IssuesEvent,2019-08-28 16:20:35,golang/go,https://api.github.com/repos/golang/go,closed,math/big: Rat.Denom has side effects,Documentation NeedsInvestigation,"From here: https://github.com/ericlagergren/decimal/issues/138

My package divides `(*Rat).Num` by `(*Rat).Denom` to produce a decimal number. It turns out that `(*Rat).Denom` lazily sets its denominator, meaning it cannot be used concurrently.

Since the receiver is `x` not `z`, I assumed that the method simply read the denominator.

The receiver name should be updated to indicate side effects and/or the documentation for `big.Rat` should mention this side effect. I assume that the 7 years this has spent in the tree is too long to be reverted 😄. And, at any rate, not materializing the denominator can save allocations for whole numbers, which is a good thing.

I can send a CL if you want.",1.0,"math/big: Rat.Denom has side effects - From here: https://github.com/ericlagergren/decimal/issues/138

My package divides `(*Rat).Num` by `(*Rat).Denom` to produce a decimal number. It turns out that `(*Rat).Denom` lazily sets its denominator, meaning it cannot be used concurrently.

Since the receiver is `x` not `z`, I assumed that the method simply read the denominator.

The receiver name should be updated to indicate side effects and/or the documentation for `big.Rat` should mention this side effect. I assume that the 7 years this has spent in the tree is too long to be reverted 😄. And, at any rate, not materializing the denominator can save allocations for whole numbers, which is a good thing.

I can send a CL if you want.",1,math big  rat denom has side effects   from here       my package divides    rat  num  by    rat  denom  to produce a decimal number  it turns out that    rat  denom  lazily sets its denominator  meaning it cannot be used concurrently     since the receiver is  x  not  z   i assumed that the method simply read the denominator     the receiver name should be updated to indicate side effects and or the documentation for  big rat  should mention this side effect  i assume that the   years this has spent in the tree is too long to be reverted 😄  and  at any rate  not materializing the denominator can save allocations for whole numbers  which is a good thing     i can send a cl if you want ,1
692356,23731308329.0,IssuesEvent,2022-08-31 02:09:08,SETI/pds-opus,https://api.github.com/repos/SETI/pds-opus,closed,Allow selection of production version in cart download,A-Enhancement Effort 1 Hard B-OPUS Django Priority 4 Useful,"For some datasets there are multiple versions of the products available. We should make it possible to download the old versions as part of the shopping cart process.

The OPUS search criteria will always be based on the most recent version.

See
    pdsf.associated_parallel(..., rank=something)
to get access to the different 'version ranks' of a file or volume.

A version rank is an integer that encodes the version number or status of a volume or product. The latest version is 999999. In lien resolution translates to 990400. For other than the latest version, the rank is an encoded form of the version number, e.g., _v2.1 = 201000.

Each PdsFile object has a property version_ranks that returns the sorted list of all versions of this volume or file. 
",1.0,"Allow selection of production version in cart download - For some datasets there are multiple versions of the products available. We should make it possible to download the old versions as part of the shopping cart process.

The OPUS search criteria will always be based on the most recent version.

See
    pdsf.associated_parallel(..., rank=something)
to get access to the different 'version ranks' of a file or volume.

A version rank is an integer that encodes the version number or status of a volume or product. The latest version is 999999. In lien resolution translates to 990400. For other than the latest version, the rank is an encoded form of the version number, e.g., _v2.1 = 201000.

Each PdsFile object has a property version_ranks that returns the sorted list of all versions of this volume or file. 
",0,allow selection of production version in cart download   for some datasets there are multiple versions of the products available  we should make it possible to download the old versions as part of the shopping cart process     the opus search criteria will always be based on the most recent version     see      pdsf associated parallel      rank something   to get access to the different  version ranks  of a file or volume     a version rank is an integer that encodes the version number or status of a volume or product  the latest version is    in lien resolution translates to    for other than the latest version  the rank is an encoded form of the version number  e g                each pdsfile object has a property version ranks that returns the sorted list of all versions of this volume or file    ,0
18280,12731614143.0,IssuesEvent,2020-06-25 09:07:19,dbwebb-se/website,https://api.github.com/repos/dbwebb-se/website,closed,Gravatar är http istället för https,enhancement usability,"När jag är inne på dbwebb.se/forum finns min gravatar uppe i hörnet, men den går över http istället för http**s** så jag får en konstant varning om att sidan bara är partially encrypted.

Jag provade att lägga till ett s i adressen och den funkar fortfarande, så det borde vara lätt att uppdatera om jag bara kunde hitta forumkoden...

Exempelfil som fungerar med https:
https://www.gravatar.com/avatar/f902f74bd5a291d33ba4eac7845b52dc?r=pg&s=40&d=wavatar
",True,"Gravatar är http istället för https - När jag är inne på dbwebb.se/forum finns min gravatar uppe i hörnet, men den går över http istället för http**s** så jag får en konstant varning om att sidan bara är partially encrypted.

Jag provade att lägga till ett s i adressen och den funkar fortfarande, så det borde vara lätt att uppdatera om jag bara kunde hitta forumkoden...

Exempelfil som fungerar med https:
https://www.gravatar.com/avatar/f902f74bd5a291d33ba4eac7845b52dc?r=pg&s=40&d=wavatar
",0,gravatar är http istället för https   när jag är inne på dbwebb se forum finns min gravatar uppe i hörnet  men den går över http istället för http  s   så jag får en konstant varning om att sidan bara är partially encrypted   jag provade att lägga till ett s i adressen och den funkar fortfarande  så det borde vara lätt att uppdatera om jag bara kunde hitta forumkoden     exempelfil som fungerar med https    ,0
103664,11362315117.0,IssuesEvent,2020-01-26 20:29:40,golang/go,https://api.github.com/repos/golang/go,closed,strconv: QuoteToGraphic documentation on ASCII is wrong,Documentation,"> QuoteToGraphic returns a double-quoted Go string literal representing s. The returned string uses Go escape sequences (\t, \n, \xFF, \u0100) for non-ASCII characters and non-printable characters as defined by IsGraphic.

The documentation reads like non-ASCII characters are escaped, and they are not. I'm not even sure that the mention of ASCII was ment to say here.",1.0,"strconv: QuoteToGraphic documentation on ASCII is wrong - > QuoteToGraphic returns a double-quoted Go string literal representing s. The returned string uses Go escape sequences (\t, \n, \xFF, \u0100) for non-ASCII characters and non-printable characters as defined by IsGraphic.

The documentation reads like non-ASCII characters are escaped, and they are not. I'm not even sure that the mention of ASCII was ment to say here.",1,strconv  quotetographic documentation on ascii is wrong     quotetographic returns a double quoted go string literal representing s  the returned string uses go escape sequences   t   n   xff      for non ascii characters and non printable characters as defined by isgraphic     the documentation reads like non ascii characters are escaped  and they are not  i m not even sure that the mention of ascii was ment to say here ,1
208931,23665457648.0,IssuesEvent,2022-08-26 20:20:16,JohnDeere/work-tracker-examples,https://api.github.com/repos/JohnDeere/work-tracker-examples,closed,CVE-2020-36179 (High) detected in jackson-databind-2.9.10.3.jar - autoclosed,security vulnerability,"## CVE-2020-36179 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.10.3.jar</b></p></summary>

<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href=""http://github.com/FasterXML/jackson"">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /java-example/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.10.3/jackson-databind-2.9.10.3.jar,/com/fasterxml/jackson/core/jackson-databind/2.9.10.3/jackson-databind-2.9.10.3.jar,/home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.10.3/jackson-databind-2.9.10.3.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.9.10.3.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/JohnDeere/work-tracker-examples/commit/3b29c95f8346b60c5c53ea089a4f440f17011402"">3b29c95f8346b60c5c53ea089a4f440f17011402</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>  
  
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to oadd.org.apache.commons.dbcp.cpdsadapter.DriverAdapterCPDS.

<p>Publish Date: 2021-01-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36179>CVE-2020-36179</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>8.1</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-07</p>
<p>Fix Resolution: 2.9.10.8</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2020-36179 (High) detected in jackson-databind-2.9.10.3.jar - autoclosed - ## CVE-2020-36179 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.10.3.jar</b></p></summary>

<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href=""http://github.com/FasterXML/jackson"">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /java-example/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.10.3/jackson-databind-2.9.10.3.jar,/com/fasterxml/jackson/core/jackson-databind/2.9.10.3/jackson-databind-2.9.10.3.jar,/home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.10.3/jackson-databind-2.9.10.3.jar</p>
<p>

Dependency Hierarchy:
  - :x: **jackson-databind-2.9.10.3.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/JohnDeere/work-tracker-examples/commit/3b29c95f8346b60c5c53ea089a4f440f17011402"">3b29c95f8346b60c5c53ea089a4f440f17011402</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>  
  
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to oadd.org.apache.commons.dbcp.cpdsadapter.DriverAdapterCPDS.

<p>Publish Date: 2021-01-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36179>CVE-2020-36179</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>8.1</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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>Release Date: 2021-01-07</p>
<p>Fix Resolution: 2.9.10.8</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in jackson databind         jar   autoclosed      cve       high severity vulnerability     vulnerable library    jackson databind         jar      general data binding functionality for jackson  works on core streaming api   library home page   a href     path to dependency file   java example pom xml   path to vulnerable library   home wss scanner    repository com fasterxml jackson core jackson databind         jackson databind         jar  com fasterxml jackson core jackson databind         jackson databind         jar  home wss scanner    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 oadd org apache commons dbcp cpdsadapter driveradaptercpds    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   release date          fix resolution                        step up your open source security game with mend    ,0
17658,4184064989.0,IssuesEvent,2016-06-23 04:31:09,golang/go,https://api.github.com/repos/golang/go,closed,html/template: Security Model definition link broken,Documentation,"The [Security Model section](https://golang.org/pkg/html/template/#hdr-Security_Model) links to a document defining ""safe"" template behavior (http://js-quasis-libraries-and-repl.googlecode.com/svn/trunk/safetemplate.html#problem_definition) which is not available anymore.
Does this document still exist? 
`tip: version devel +eaf4ad6 and go1.6.2`



",1.0,"html/template: Security Model definition link broken - The [Security Model section](https://golang.org/pkg/html/template/#hdr-Security_Model) links to a document defining ""safe"" template behavior (http://js-quasis-libraries-and-repl.googlecode.com/svn/trunk/safetemplate.html#problem_definition) which is not available anymore.
Does this document still exist? 
`tip: version devel +eaf4ad6 and go1.6.2`



",1,html template  security model definition link broken   the     links to a document defining  safe  template behavior    which is not available anymore   does this document still exist     tip  version devel    and               ,1
43508,7048557683.0,IssuesEvent,2018-01-02 18:11:33,golang/go,https://api.github.com/repos/golang/go,closed,"math: wrong result for Pow(±0, .5) contrary to documentation",Documentation,"Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?

go version go1.9.2 linux/amd64

### Does this issue reproduce with the latest release?

I believe go1.9.2 is the latest release.

### What operating system and processor architecture are you using (`go env`)?

GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/usr/local/google/home/majnemer/go""
GORACE=""""
GOROOT=""/usr/lib/google-golang""
GOTOOLDIR=""/usr/lib/google-golang/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build846653371=/tmp/go-build -gno-record-gcc-switches""
CXX=""g++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""

### What did you do?

I ran the following program: https://play.golang.org/p/_lUAaRG9D-P

### What did you expect to see?

The [documentation for math.Pow](https://golang.org/pkg/math/#Pow) says the following:

> Pow(±0, y) = +0 for finite y > 0 and not an odd integer

.5 is finite and not an odd integer which means math.Pow should give back +0.

### What did you see instead?

math.Pow gave back -0.",1.0,"math: wrong result for Pow(±0, .5) contrary to documentation - Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?

go version go1.9.2 linux/amd64

### Does this issue reproduce with the latest release?

I believe go1.9.2 is the latest release.

### What operating system and processor architecture are you using (`go env`)?

GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GOOS=""linux""
GOPATH=""/usr/local/google/home/majnemer/go""
GORACE=""""
GOROOT=""/usr/lib/google-golang""
GOTOOLDIR=""/usr/lib/google-golang/pkg/tool/linux_amd64""
GCCGO=""gccgo""
CC=""gcc""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build846653371=/tmp/go-build -gno-record-gcc-switches""
CXX=""g++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""

### What did you do?

I ran the following program: https://play.golang.org/p/_lUAaRG9D-P

### What did you expect to see?

The [documentation for math.Pow](https://golang.org/pkg/math/#Pow) says the following:

> Pow(±0, y) = +0 for finite y > 0 and not an odd integer

.5 is finite and not an odd integer which means math.Pow should give back +0.

### What did you see instead?

math.Pow gave back -0.",1,math  wrong result for pow ±       contrary to documentation   please answer these questions before submitting your issue  thanks           what version of go are you using   go version       go version       linux          does this issue reproduce with the latest release     i believe       is the latest release         what operating system and processor architecture are you using   go env       goarch      gobin     goexe     gohostarch      gohostos  linux   goos  linux   gopath   usr local google home majnemer go   gorace     goroot   usr lib google golang   gotooldir   usr lib google golang pkg tool linux     gccgo  gccgo   cc  gcc   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches   cxx  g     cgo enabled      cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config         what did you do     i ran the following program           what did you expect to see     the     says the following       pow ±   y       for finite y     and not an odd integer       is finite and not an odd integer which means math pow should give back            what did you see instead     math pow gave back    ,1
209172,7166000970.0,IssuesEvent,2018-01-29 15:59:39,zephyrproject-rtos/zephyr,https://api.github.com/repos/zephyrproject-rtos/zephyr,closed,CDC_ACM is limited to 4 bytes at a time for Arduino 101,area: USB bug priority: medium,"**_Reported by Brian Jones:_**

Due to GH-3515, CDC_ACM on the Arduino 101 is limited to sending 4 bytes at a time.  This should be fixed in the long term as its inefficient to send such a small amount multiple times when larger buffers are being sent.

(Imported from Jira ZEP-2401)",1.0,"CDC_ACM is limited to 4 bytes at a time for Arduino 101 - **_Reported by Brian Jones:_**

Due to GH-3515, CDC_ACM on the Arduino 101 is limited to sending 4 bytes at a time.  This should be fixed in the long term as its inefficient to send such a small amount multiple times when larger buffers are being sent.

(Imported from Jira ZEP-2401)",0,cdc acm is limited to   bytes at a time for arduino        reported by brian jones      due to gh    cdc acm on the arduino   is limited to sending   bytes at a time   this should be fixed in the long term as its inefficient to send such a small amount multiple times when larger buffers are being sent    imported from jira zep   ,0
27327,28116874400.0,IssuesEvent,2023-03-31 11:27:20,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Adding a signal to a C# class in a namespace creates the signal outside of the class/namespace,bug topic:editor confirmed usability topic:dotnet,"**Godot version:** 3.1.1.1 (Mono)
**Issue description:** When adding a signal to a C# class in a namespace, the signal appears at the bottom of the file (outside the namespace/class). It's simple enough to move it into the namespace. 

i.e. if I have this:

```
namespace Foo.Bar {
  public class MainScene extends Godot.Node2D {
    override public function _Ready() { } 
    // ...
  }
}
```

Adding a signal `NewGameClicked` on a button gives me this:

```
namespace Foo.Bar {
  public class MainScene extends Godot.Node2D {
    override public function _Ready() { } 
    // ...
  }
}

public void NewGameClicked() { }
```

It should give me this:

```
namespace Foo.Bar {
  public class MainScene extends Godot.Node2D {
    override public function _Ready() { } 
    // ...

    public void NewGameClicked() { }
  }
}
```

**Steps to reproduce:**
- Create a new Mono project
- Create a scene
- Create a `.cs` file script for the scene
- Edit the `.cs` file to put a namspace in it
- Add any control in the scene `.tscn` and bind to any signal

Expected: the newly-created function is in the namespace/class
Actual: the newly-created function is outside the namespace/class
",True,"Adding a signal to a C# class in a namespace creates the signal outside of the class/namespace - **Godot version:** 3.1.1.1 (Mono)
**Issue description:** When adding a signal to a C# class in a namespace, the signal appears at the bottom of the file (outside the namespace/class). It's simple enough to move it into the namespace. 

i.e. if I have this:

```
namespace Foo.Bar {
  public class MainScene extends Godot.Node2D {
    override public function _Ready() { } 
    // ...
  }
}
```

Adding a signal `NewGameClicked` on a button gives me this:

```
namespace Foo.Bar {
  public class MainScene extends Godot.Node2D {
    override public function _Ready() { } 
    // ...
  }
}

public void NewGameClicked() { }
```

It should give me this:

```
namespace Foo.Bar {
  public class MainScene extends Godot.Node2D {
    override public function _Ready() { } 
    // ...

    public void NewGameClicked() { }
  }
}
```

**Steps to reproduce:**
- Create a new Mono project
- Create a scene
- Create a `.cs` file script for the scene
- Edit the `.cs` file to put a namspace in it
- Add any control in the scene `.tscn` and bind to any signal

Expected: the newly-created function is in the namespace/class
Actual: the newly-created function is outside the namespace/class
",0,adding a signal to a c  class in a namespace creates the signal outside of the class namespace     godot version             mono     issue description    when adding a signal to a c  class in a namespace  the signal appears at the bottom of the file  outside the namespace class   it s simple enough to move it into the namespace      i e  if i have this          namespace foo bar      public class mainscene extends godot          override public function  ready                                    adding a signal  newgameclicked  on a button gives me this          namespace foo bar      public class mainscene extends godot          override public function  ready                               public void newgameclicked               it should give me this          namespace foo bar      public class mainscene extends godot          override public function  ready                           public void newgameclicked                         steps to reproduce       create a new mono project    create a scene    create a   cs  file script for the scene    edit the   cs  file to put a namspace in it    add any control in the scene   tscn  and bind to any signal    expected  the newly created function is in the namespace class  actual  the newly created function is outside the namespace class  ,0
173137,14403476434.0,IssuesEvent,2020-12-03 16:06:12,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.16: document os/signal changes for Go 1.16,Documentation NeedsInvestigation help wanted release-blocker,"As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

<dl id=""os/signal""><dt><a href=""/pkg/os/signal/"">os/signal</a></dt>
  <dd>
    <p><!-- CL 219640 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/219640"">https://golang.org/cl/219640</a>: add NotifyContext to cancel context using system signals
    </p>
  </dd>
</dl><!-- os/signal -->

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.",1.0,"doc/go1.16: document os/signal changes for Go 1.16 - As of filing this issue, the [Go 1.16 draft release notes](https://tip.golang.org/doc/go1.16) contained the following HTML:

<dl id=""os/signal""><dt><a href=""/pkg/os/signal/"">os/signal</a></dt>
  <dd>
    <p><!-- CL 219640 -->
      <strong>TODO:</strong> <a href=""https://golang.org/cl/219640"">https://golang.org/cl/219640</a>: add NotifyContext to cancel context using system signals
    </p>
  </dd>
</dl><!-- os/signal -->

---

Per [golang.org/s/release](https://golang.org/s/release), it's a release blocker for Go 1.16 Beta 1 to have a complete draft of the eventual release notes, and so the TODO needs to be resolved.

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.16:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.16) and include ""For #40700. Fixes #{this issue}."" in the body.",1,doc      document os signal changes for go       as of filing this issue  the     contained the following html        os signal                        todo    a href    add notifycontext to cancel context using system signals                           per     it s a release blocker for go     beta   to have a complete draft of the eventual release notes  and so the todo needs to be resolved     a sequence of steps to resolve this issue may be        come up with a draft release note entry in this issue  then move the issue to needsfix state      send a cl with  doc           and include  for     fixes   this issue    in the body ,1
25178,5142238813.0,IssuesEvent,2017-01-12 12:37:58,golang/go,https://api.github.com/repos/golang/go,opened,cmd/go: go bug help message is outdated,Documentation NeedsFix,"```
$ gotip version
go version devel +39e31d5ec0 Thu Jan 12 04:50:46 2017 +0000 linux/amd64
```

Change 896ac677b5e3e80278cc1ce179d8a077ac3a6d2f modified the `bug` subcommand to make it open the system browser and pre-fill an issue template (instead of just dumping the infos to the screen), but the subcommand help string was not updated accordingly.

It is certainly unexpected that a command that is currently documented as such:

```
$ gotip bug -h
usage: bug

Bug prints information that helps file effective bug reports.

Bugs may be reported at https://golang.org/issue/new.
```

opens my browser and uses it to display a pre-filled github page.",1.0,"cmd/go: go bug help message is outdated - ```
$ gotip version
go version devel +39e31d5ec0 Thu Jan 12 04:50:46 2017 +0000 linux/amd64
```

Change 896ac677b5e3e80278cc1ce179d8a077ac3a6d2f modified the `bug` subcommand to make it open the system browser and pre-fill an issue template (instead of just dumping the infos to the screen), but the subcommand help string was not updated accordingly.

It is certainly unexpected that a command that is currently documented as such:

```
$ gotip bug -h
usage: bug

Bug prints information that helps file effective bug reports.

Bugs may be reported at https://golang.org/issue/new.
```

opens my browser and uses it to display a pre-filled github page.",1,cmd go  go bug help message is outdated          gotip version  go version devel    thu jan              linux           change   modified the  bug  subcommand to make it open the system browser and pre fill an issue template  instead of just dumping the infos to the screen   but the subcommand help string was not updated accordingly     it is certainly unexpected that a command that is currently documented as such            gotip bug  h  usage  bug    bug prints information that helps file effective bug reports     bugs may be reported at           opens my browser and uses it to display a pre filled github page ,1
99961,11167696261.0,IssuesEvent,2019-12-27 18:16:10,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/gopls: improve textDocument/documentLink,Documentation NeedsFix gopls help wanted,"Some additional features we should add support for in `textDocument/documentLink`:

- ~~Links missing `http://` or `https://` should be treated as links. For example, `golang.org/issue/12345`.~~ (Completed via [golang.org/cl/194661](https://go-review.googlesource.com/c/tools/+/194661)).
- ~~Links to the Go issue tracker should be treated as links. For example, `golang/go#12345`~~.

Please add any others as ideas come up.",1.0,"x/tools/gopls: improve textDocument/documentLink - Some additional features we should add support for in `textDocument/documentLink`:

- ~~Links missing `http://` or `https://` should be treated as links. For example, `golang.org/issue/12345`.~~ (Completed via [golang.org/cl/194661](https://go-review.googlesource.com/c/tools/+/194661)).
- ~~Links to the Go issue tracker should be treated as links. For example, `golang/go#12345`~~.

Please add any others as ideas come up.",1,x tools gopls  improve textdocument documentlink   some additional features we should add support for in  textdocument documentlink          links missing    or    should be treated as links  for example   golang org issue        completed via          links to the go issue tracker should be treated as links  for example   golang go          please add any others as ideas come up ,1
433971,30389035580.0,IssuesEvent,2023-07-13 05:02:01,golang/go,https://api.github.com/repos/golang/go,closed,x/vuln: outdated govulncheck documentation,Documentation vulncheck or vulndb,"<!--
Please answer these questions before submitting your issue. Thanks!

To add a new vulnerability to the Go vulnerability database
(https://vuln.go.dev), see https://go.dev/s/vulndb-report-new.

To report an issue about a report, see https://go.dev/s/vulndb-report-feedback.
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.20.5 darwin/arm64
</pre>

### Does this issue reproduce at the latest version of golang.org/x/vuln?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env

</pre></details>

### What did you do?
Executed the following commands based on the latest documentation: https://pkg.go.dev/golang.org/x/vuln/cmd/govulncheck
```
go install golang.org/x/vuln/cmd/govulncheck@v0.2.0
govulncheck -v -test ./...
```


### What did you expect to see?

```
govulncheck is an experimental tool. Share feedback at https://go.dev/s/govulncheck-feedback.

Using go1.20.5 and govulncheck@v0.2.0 with
vulnerability data from https://vuln.go.dev (last modified 2023-06-26 16:56:57 +0000 UTC).

Scanning your code and 638 packages across 140 dependent modules for known vulnerabilities...
No vulnerabilities found.
```

### What did you see instead?

```
flag provided but not defined: -v
Govulncheck reports known vulnerabilities in dependencies.

Usage:

	govulncheck [flags] [patterns]
	govulncheck -mode=binary [flags] [binary]

  -C dir
    	change to dir before running govulncheck
  -db url
    	vulnerability database url (default ""https://vuln.go.dev/"")
  -json
    	output JSON
  -mode string
    	supports source or binary (default ""source"")
  -scan-level string
    	set the scanning level desired, one of module, package or symbol (default ""symbol"")
  -show list
    	enable display of additional information specified by list
  -tags list
    	comma-separated list of build tags
  -test
    	analyze test files (only valid for source mode)

For details, see https://pkg.go.dev/golang.org/x/vuln/cmd/govulncheck.
flag provided but not defined: -v
```

",1.0,"x/vuln: outdated govulncheck documentation - <!--
Please answer these questions before submitting your issue. Thanks!

To add a new vulnerability to the Go vulnerability database
(https://vuln.go.dev), see https://go.dev/s/vulndb-report-new.

To report an issue about a report, see https://go.dev/s/vulndb-report-feedback.
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.20.5 darwin/arm64
</pre>

### Does this issue reproduce at the latest version of golang.org/x/vuln?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env

</pre></details>

### What did you do?
Executed the following commands based on the latest documentation: https://pkg.go.dev/golang.org/x/vuln/cmd/govulncheck
```
go install golang.org/x/vuln/cmd/govulncheck@v0.2.0
govulncheck -v -test ./...
```


### What did you expect to see?

```
govulncheck is an experimental tool. Share feedback at https://go.dev/s/govulncheck-feedback.

Using go1.20.5 and govulncheck@v0.2.0 with
vulnerability data from https://vuln.go.dev (last modified 2023-06-26 16:56:57 +0000 UTC).

Scanning your code and 638 packages across 140 dependent modules for known vulnerabilities...
No vulnerabilities found.
```

### What did you see instead?

```
flag provided but not defined: -v
Govulncheck reports known vulnerabilities in dependencies.

Usage:

	govulncheck [flags] [patterns]
	govulncheck -mode=binary [flags] [binary]

  -C dir
    	change to dir before running govulncheck
  -db url
    	vulnerability database url (default ""https://vuln.go.dev/"")
  -json
    	output JSON
  -mode string
    	supports source or binary (default ""source"")
  -scan-level string
    	set the scanning level desired, one of module, package or symbol (default ""symbol"")
  -show list
    	enable display of additional information specified by list
  -tags list
    	comma-separated list of build tags
  -test
    	analyze test files (only valid for source mode)

For details, see https://pkg.go.dev/golang.org/x/vuln/cmd/govulncheck.
flag provided but not defined: -v
```

",1,x vuln  outdated govulncheck documentation         please answer these questions before submitting your issue  thanks     to add a new vulnerability to the go vulnerability database     see      to report an issue about a report  see               what version of go are you using   go version            go version  go version       darwin             does this issue reproduce at the latest version of golang org x vuln   yes          what operating system and processor architecture are you using   go env          go env  output       go env              what did you do   executed the following commands based on the latest documentation          go install golang org x vuln cmd govulncheck        govulncheck  v  test                     what did you expect to see          govulncheck is an experimental tool  share feedback at      using       and govulncheck       with  vulnerability data from    last modified                utc      scanning your code and   packages across   dependent modules for known vulnerabilities     no vulnerabilities found              what did you see instead          flag provided but not defined   v  govulncheck reports known vulnerabilities in dependencies     usage     	govulncheck      	govulncheck  mode binary           c dir      	change to dir before running govulncheck     db url      	vulnerability database url  default        json      	output json     mode string      	supports source or binary  default  source       scan level string      	set the scanning level desired  one of module  package or symbol  default  symbol       show list      	enable display of additional information specified by list     tags list      	comma separated list of build tags     test      	analyze test files  only valid for source mode     for details  see    flag provided but not defined   v         ,1
244947,7880707591.0,IssuesEvent,2018-06-26 16:41:53,aowen87/FOO,https://api.github.com/repos/aowen87/FOO,closed,Scatter plot wizard no longer populates variable menus,Likelihood: 3 - Occasional OS: All Priority: Normal Severity: 3 - Major Irritation Support Group: Any Target Version: 2.13.0 bug version: 2.12.3,"The variable selection buttons in the wizard do not have the variable menu populated.
This is newly introduced in 2.12.3.

This may be related to the bug reported on the user list, though the description of the problem is different than I described.

https://elist.ornl.gov/pipermail/visit-users/2017-July/020335.html",1.0,"Scatter plot wizard no longer populates variable menus - The variable selection buttons in the wizard do not have the variable menu populated.
This is newly introduced in 2.12.3.

This may be related to the bug reported on the user list, though the description of the problem is different than I described.

https://elist.ornl.gov/pipermail/visit-users/2017-July/020335.html",0,scatter plot wizard no longer populates variable menus   the variable selection buttons in the wizard do not have the variable menu populated   this is newly introduced in           this may be related to the bug reported on the user list  though the description of the problem is different than i described      ,0
811089,30274079391.0,IssuesEvent,2023-07-07 17:54:10,yugabyte/yugabyte-db,https://api.github.com/repos/yugabyte/yugabyte-db,closed,"[DocDB] Potential empty wal segment header, leading to bootstrap failure",kind/bug area/docdb priority/high 2.14 Backport Required 2.16 Backport Required 2.18 Backport Required,"Jira Link: [DB-6732](https://yugabyte.atlassian.net/browse/DB-6732)
### Description

When allocating a new wal segment, we follow below steps:
1. Create a placeholder segment asynchronously.
2. When allocation is done, rename the placeholder segment to the actual segment name.
3. write the header.

It's possible that tserver crashed between step 2 and 3. And during restart of the tablet, it may read the empty segment and cause it fail to bootstrap the tablet.

We can create a unit test by crashing the tserver between step2 and step3 and restart to verify this ***(restart-test)***.
e.g. write several rows, set a test gflag `TEST_crash_before_wal_header_is_written`, roll the log (server should crash), restart the server to see if following error shows up:
W0519 11:03:55.940025 1184317 catalog_manager.cc:7532] Tablet XXX has failed on TS XXX: IO error (yb/util/env_util.cc:155): Failed log replay. Reason: Failed to open new log: Unable to open readable log segment: XXX: Unable to initialize segment: EOF trying to read 12 bytes at offset 0

The issue results in a crash loop as the tablet bootstrap doesn't succeed.

### Warning: Please confirm that this issue does not contain any sensitive information

- [X] I confirm this issue does not contain any sensitive information.

[DB-6732]: https://yugabyte.atlassian.net/browse/DB-6732?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ",1.0,"[DocDB] Potential empty wal segment header, leading to bootstrap failure - Jira Link: [DB-6732](https://yugabyte.atlassian.net/browse/DB-6732)
### Description

When allocating a new wal segment, we follow below steps:
1. Create a placeholder segment asynchronously.
2. When allocation is done, rename the placeholder segment to the actual segment name.
3. write the header.

It's possible that tserver crashed between step 2 and 3. And during restart of the tablet, it may read the empty segment and cause it fail to bootstrap the tablet.

We can create a unit test by crashing the tserver between step2 and step3 and restart to verify this ***(restart-test)***.
e.g. write several rows, set a test gflag `TEST_crash_before_wal_header_is_written`, roll the log (server should crash), restart the server to see if following error shows up:
W0519 11:03:55.940025 1184317 catalog_manager.cc:7532] Tablet XXX has failed on TS XXX: IO error (yb/util/env_util.cc:155): Failed log replay. Reason: Failed to open new log: Unable to open readable log segment: XXX: Unable to initialize segment: EOF trying to read 12 bytes at offset 0

The issue results in a crash loop as the tablet bootstrap doesn't succeed.

### Warning: Please confirm that this issue does not contain any sensitive information

- [X] I confirm this issue does not contain any sensitive information.

[DB-6732]: https://yugabyte.atlassian.net/browse/DB-6732?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ",0,  potential empty wal segment header  leading to bootstrap failure   jira link           description    when allocating a new wal segment  we follow below steps      create a placeholder segment asynchronously      when allocation is done  rename the placeholder segment to the actual segment name      write the header     it s possible that tserver crashed between step   and    and during restart of the tablet  it may read the empty segment and cause it fail to bootstrap the tablet     we can create a unit test by crashing the tserver between   and   and restart to verify this     restart test       e g  write several rows  set a test gflag  test crash before wal header is written   roll the log  server should crash   restart the server to see if following error shows up               catalog manager cc    tablet xxx has failed on ts xxx  io error  yb util env util cc     failed log replay  reason  failed to open new log  unable to open readable log segment  xxx  unable to initialize segment  eof trying to read   bytes at offset      the issue results in a crash loop as the tablet bootstrap doesn t succeed         warning  please confirm that this issue does not contain any sensitive information        i confirm this issue does not contain any sensitive information         ,0
85693,15755163919.0,IssuesEvent,2021-03-31 01:17:47,LevyForchh/gvisor,https://api.github.com/repos/LevyForchh/gvisor,opened,CVE-2021-23337 (High) detected in lodash-4.17.15.tgz,security vulnerability,"## CVE-2021-23337 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-4.17.15.tgz</b></p></summary>

<p>Lodash modular utilities.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz"">https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz</a></p>
<p>Path to dependency file: gvisor/benchmarks/workloads/node_template/package.json</p>
<p>Path to vulnerable library: gvisor/benchmarks/workloads/node_template/node_modules/lodash/package.json</p>
<p>

Dependency Hierarchy:
  - hbs-4.0.4.tgz (Root Library)
    - handlebars-4.0.14.tgz
      - async-2.6.2.tgz
        - :x: **lodash-4.17.15.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>  
  
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.

<p>Publish Date: 2021-02-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337>CVE-2021-23337</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.2</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: High
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c"">https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c</a></p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution: lodash - 4.17.21</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":false,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""lodash"",""packageVersion"":""4.17.15"",""packageFilePaths"":[""/benchmarks/workloads/node_template/package.json""],""isTransitiveDependency"":true,""dependencyTree"":""hbs:4.0.4;handlebars:4.0.14;async:2.6.2;lodash:4.17.15"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""lodash - 4.17.21""}],""baseBranches"":[],""vulnerabilityIdentifier"":""CVE-2021-23337"",""vulnerabilityDetails"":""Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337"",""cvss3Severity"":""high"",""cvss3Score"":""7.2"",""cvss3Metrics"":{""A"":""High"",""AC"":""Low"",""PR"":""High"",""S"":""Unchanged"",""C"":""High"",""UI"":""None"",""AV"":""Network"",""I"":""High""},""extraData"":{}}</REMEDIATE> -->",True,"CVE-2021-23337 (High) detected in lodash-4.17.15.tgz - ## CVE-2021-23337 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-4.17.15.tgz</b></p></summary>

<p>Lodash modular utilities.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz"">https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz</a></p>
<p>Path to dependency file: gvisor/benchmarks/workloads/node_template/package.json</p>
<p>Path to vulnerable library: gvisor/benchmarks/workloads/node_template/node_modules/lodash/package.json</p>
<p>

Dependency Hierarchy:
  - hbs-4.0.4.tgz (Root Library)
    - handlebars-4.0.14.tgz
      - async-2.6.2.tgz
        - :x: **lodash-4.17.15.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>  
  
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.

<p>Publish Date: 2021-02-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337>CVE-2021-23337</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.2</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: High
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c"">https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c</a></p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution: lodash - 4.17.21</p>

</p>
</details>
<p></p>

<!-- <REMEDIATE>{""isOpenPROnVulnerability"":false,""isPackageBased"":true,""isDefaultBranch"":true,""packages"":[{""packageType"":""javascript/Node.js"",""packageName"":""lodash"",""packageVersion"":""4.17.15"",""packageFilePaths"":[""/benchmarks/workloads/node_template/package.json""],""isTransitiveDependency"":true,""dependencyTree"":""hbs:4.0.4;handlebars:4.0.14;async:2.6.2;lodash:4.17.15"",""isMinimumFixVersionAvailable"":true,""minimumFixVersion"":""lodash - 4.17.21""}],""baseBranches"":[],""vulnerabilityIdentifier"":""CVE-2021-23337"",""vulnerabilityDetails"":""Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function."",""vulnerabilityUrl"":""https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337"",""cvss3Severity"":""high"",""cvss3Score"":""7.2"",""cvss3Metrics"":{""A"":""High"",""AC"":""Low"",""PR"":""High"",""S"":""Unchanged"",""C"":""High"",""UI"":""None"",""AV"":""Network"",""I"":""High""},""extraData"":{}}</REMEDIATE> -->",0,cve      high  detected in lodash       tgz      cve       high severity vulnerability     vulnerable library    lodash       tgz      lodash modular utilities    library home page   a href     path to dependency file  gvisor benchmarks workloads node template package json   path to vulnerable library  gvisor benchmarks workloads node template node modules lodash package json     dependency hierarchy      hbs       tgz  root library        handlebars       tgz         async       tgz            x    lodash       tgz    vulnerable library             vulnerability details         lodash versions prior to       are vulnerable to command injection via the template function    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  high     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  lodash                      isopenpronvulnerability  false  ispackagebased  true  isdefaultbranch  true  packages     istransitivedependency  true  dependencytree   hbs       handlebars       async       lodash         isminimumfixversionavailable  true  minimumfixversion   lodash             basebranches     vulnerabilityidentifier   cve       vulnerabilitydetails   lodash versions prior to       are vulnerable to command injection via the template function    vulnerabilityurl        ,0
5758,2967596508.0,IssuesEvent,2015-07-13 01:35:47,golang/go,https://api.github.com/repos/golang/go,closed,time: document that time.Tick causes a resource leak,Documentation,"Calling `time.Tick` causes a `Ticker` to leak because there is no interface to `Stop()` it.

Here is a demonstration which starts 100,000 go routines each of which calls `time.Tick` then closes the go routines down again in an orderly fashion

http://play.golang.org/p/zy5X4hAq0I

It sleeps at the end so you can run top or equivalent and see that it will be using 100% of a CPU core keeping the `Ticker`s up to date even though the user no longer has access to them.

This is unfortunate but it was decided in #8001 that it was too difficicult to `Stop` the `Ticker`s when they are garbage collected.

The documentation for `NewTicker` got changed after this, but not the documentation for `Tick`.

It currently reads 

> Tick is a convenience wrapper for NewTicker providing access to the ticking channel only. Useful for clients that have no need to shut down the ticker.

It doesn't say why you might want to shut the Ticker down.

My suggestion for a re-word is this

> Tick is a convenience wrapper for NewTicker providing access to the ticking channel only. Note that this leaks associated resources; use NewTicker and Stop to avoid that.

That is possibly too alarmist, but I wanted the docs to note clearly that using `time.Tick` is leaking something which can't be recovered.
",1.0,"time: document that time.Tick causes a resource leak - Calling `time.Tick` causes a `Ticker` to leak because there is no interface to `Stop()` it.

Here is a demonstration which starts 100,000 go routines each of which calls `time.Tick` then closes the go routines down again in an orderly fashion

http://play.golang.org/p/zy5X4hAq0I

It sleeps at the end so you can run top or equivalent and see that it will be using 100% of a CPU core keeping the `Ticker`s up to date even though the user no longer has access to them.

This is unfortunate but it was decided in #8001 that it was too difficicult to `Stop` the `Ticker`s when they are garbage collected.

The documentation for `NewTicker` got changed after this, but not the documentation for `Tick`.

It currently reads 

> Tick is a convenience wrapper for NewTicker providing access to the ticking channel only. Useful for clients that have no need to shut down the ticker.

It doesn't say why you might want to shut the Ticker down.

My suggestion for a re-word is this

> Tick is a convenience wrapper for NewTicker providing access to the ticking channel only. Note that this leaks associated resources; use NewTicker and Stop to avoid that.

That is possibly too alarmist, but I wanted the docs to note clearly that using `time.Tick` is leaking something which can't be recovered.
",1,time  document that time tick causes a resource leak   calling  time tick  causes a  ticker  to leak because there is no interface to  stop    it     here is a demonstration which starts     go routines each of which calls  time tick  then closes the go routines down again in an orderly fashion         it sleeps at the end so you can run top or equivalent and see that it will be using    of a cpu core keeping the  ticker s up to date even though the user no longer has access to them     this is unfortunate but it was decided in    that it was too difficicult to  stop  the  ticker s when they are garbage collected     the documentation for  newticker  got changed after this  but not the documentation for  tick      it currently reads       tick is a convenience wrapper for newticker providing access to the ticking channel only  useful for clients that have no need to shut down the ticker     it doesn t say why you might want to shut the ticker down     my suggestion for a re word is this      tick is a convenience wrapper for newticker providing access to the ticking channel only  note that this leaks associated resources  use newticker and stop to avoid that     that is possibly too alarmist  but i wanted the docs to note clearly that using  time tick  is leaking something which can t be recovered   ,1
253434,19101002693.0,IssuesEvent,2021-11-29 22:32:43,golang/go,https://api.github.com/repos/golang/go,closed,encoding/xml: mismatching namespace error misses a space char,Documentation NeedsFix,"### What version of Go are you using (`go version`)?

<pre>
1.17
</pre>

### Does this issue reproduce with the latest release?

Reproducible on the tip.

### What operating system and processor architecture are you using (`go env`)?

linux/amd64.

### What did you do?

`go run example.go` (https://play.golang.org/p/dU4NQ2vTVyF):

```go
package main

import (
	""fmt""
	""encoding/xml""
	""strings""
)

func main() {
	const input = `<a:foo></b:foo>`
	d := xml.NewDecoder(strings.NewReader(input))
	d.Token() // read StartElement
	_, err := d.Token() // read EndElement
	fmt.Println(err)
}
```

### What did you expect to see?

```
XML syntax error on line 1: element <foo> in space a closed by </foo> in space b
```

### What did you see instead?

```
XML syntax error on line 1: element <foo> in space aclosed by </foo> in space b
```

Note the diff:
```diff
- XML syntax error on line 1: element <foo> in space aclosed by </foo> in space b
+ XML syntax error on line 1: element <foo> in space a closed by </foo> in space b
```
",1.0,"encoding/xml: mismatching namespace error misses a space char - ### What version of Go are you using (`go version`)?

<pre>
1.17
</pre>

### Does this issue reproduce with the latest release?

Reproducible on the tip.

### What operating system and processor architecture are you using (`go env`)?

linux/amd64.

### What did you do?

`go run example.go` (https://play.golang.org/p/dU4NQ2vTVyF):

```go
package main

import (
	""fmt""
	""encoding/xml""
	""strings""
)

func main() {
	const input = `<a:foo></b:foo>`
	d := xml.NewDecoder(strings.NewReader(input))
	d.Token() // read StartElement
	_, err := d.Token() // read EndElement
	fmt.Println(err)
}
```

### What did you expect to see?

```
XML syntax error on line 1: element <foo> in space a closed by </foo> in space b
```

### What did you see instead?

```
XML syntax error on line 1: element <foo> in space aclosed by </foo> in space b
```

Note the diff:
```diff
- XML syntax error on line 1: element <foo> in space aclosed by </foo> in space b
+ XML syntax error on line 1: element <foo> in space a closed by </foo> in space b
```
",1,encoding xml  mismatching namespace error misses a space char       what version of go are you using   go version                        does this issue reproduce with the latest release     reproducible on the tip         what operating system and processor architecture are you using   go env       linux           what did you do      go run example go           go  package main    import    	 fmt   	 encoding xml   	 strings        func main      	const input         	d    xml newdecoder strings newreader input    	d token      read startelement  	   err    d token      read endelement  	fmt println err                 what did you expect to see          xml syntax error on line    element   in space a closed by   in space b             what did you see instead          xml syntax error on line    element   in space aclosed by   in space b         note the diff      diff    xml syntax error on line    element   in space aclosed by   in space b    xml syntax error on line    element   in space a closed by   in space b       ,1
14586,3868515918.0,IssuesEvent,2016-04-10 00:35:30,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: fix documentation typo in findInternal,Documentation,`Four cases...` at https://github.com/golang/go/blob/c31fdd4ee9fccd24a274cebd82dcc7123ad43d0e/src/cmd/go/pkg.go#L563 should be `Three cases...`.,1.0,cmd/go: fix documentation typo in findInternal - `Four cases...` at https://github.com/golang/go/blob/c31fdd4ee9fccd24a274cebd82dcc7123ad43d0e/src/cmd/go/pkg.go#L563 should be `Three cases...`.,1,cmd go  fix documentation typo in findinternal    four cases     at   should be  three cases     ,1
22473,4806701408.0,IssuesEvent,2016-11-02 19:17:27,golang/go,https://api.github.com/repos/golang/go,closed,net: connecting to 0.0.0.0 fails on windows,Documentation NeedsFix OS-Windows,"<pre>What steps will reproduce the problem?

run this program on windows

package main

import (
    &quot;log&quot;
    &quot;net&quot;
)

func dial() error {
    l, err := net.Listen(&quot;tcp&quot;, &quot;:0&quot;)
    if err != nil {
        return err
    }

    go func() {
        c, err := l.Accept()
        if err != nil {
            return
        }
        c.Close()
    }()

    c, err := net.Dial(&quot;tcp&quot;, l.Addr().String())
    if err != nil {
        return err
    }
    c.Close()
    return nil
}

func main() {
    err := dial()
    if err != nil {
        log.Fatal(err)
    }
}


What is the expected output?

Should output noting.

What do you see instead?

2013/08/30 16:43:22 dial tcp 0.0.0.0:1406: ConnectEx tcp: The format of the specified
network name is invalid.

Please use labels and text to provide additional information.

The problem seems to be that l.Addr().String() returns '0.0.0.0', but connecting to that
address is not allowed on windows. From
<a href=""http://msdn.microsoft.com/en-us/library/aa923167.aspx"">http://msdn.microsoft.com/en-us/library/aa923167.aspx</a>

&quot; ... If the address member of the structure specified by the name parameter is
all zeroes, connect will return the error WSAEADDRNOTAVAIL. ...&quot;</pre>
",1.0,"net: connecting to 0.0.0.0 fails on windows - <pre>What steps will reproduce the problem?

run this program on windows

package main

import (
    &quot;log&quot;
    &quot;net&quot;
)

func dial() error {
    l, err := net.Listen(&quot;tcp&quot;, &quot;:0&quot;)
    if err != nil {
        return err
    }

    go func() {
        c, err := l.Accept()
        if err != nil {
            return
        }
        c.Close()
    }()

    c, err := net.Dial(&quot;tcp&quot;, l.Addr().String())
    if err != nil {
        return err
    }
    c.Close()
    return nil
}

func main() {
    err := dial()
    if err != nil {
        log.Fatal(err)
    }
}


What is the expected output?

Should output noting.

What do you see instead?

2013/08/30 16:43:22 dial tcp 0.0.0.0:1406: ConnectEx tcp: The format of the specified
network name is invalid.

Please use labels and text to provide additional information.

The problem seems to be that l.Addr().String() returns '0.0.0.0', but connecting to that
address is not allowed on windows. From
<a href=""http://msdn.microsoft.com/en-us/library/aa923167.aspx"">http://msdn.microsoft.com/en-us/library/aa923167.aspx</a>

&quot; ... If the address member of the structure specified by the name parameter is
all zeroes, connect will return the error WSAEADDRNOTAVAIL. ...&quot;</pre>
",1,net  connecting to         fails on windows    what steps will reproduce the problem   run this program on windows  package main  import        quot log quot       quot net quot     func dial   error       l  err    net listen  quot tcp quot    quot    quot       if err    nil           return err            go func             c  err    l accept           if err    nil               return                   c close                c  err    net dial  quot tcp quot   l addr   string        if err    nil           return err           c close       return nil    func main         err    dial       if err    nil           log fatal err            what is the expected output   should output noting   what do you see instead               dial tcp            connectex tcp  the format of the specified network name is invalid   please use labels and text to provide additional information   the problem seems to be that l addr   string   returns            but connecting to that address is not allowed on windows  from  a href      quot      if the address member of the structure specified by the name parameter is all zeroes  connect will return the error wsaeaddrnotavail      quot   ,1
130691,18107280853.0,IssuesEvent,2021-09-22 20:40:17,WordPress/gutenberg,https://api.github.com/repos/WordPress/gutenberg,closed,Text color icon appears and disappears,[Type] Enhancement [Feature] Rich Text Needs Design Feedback,"Continuing discussion from:
""Add option to add text color to specific text inside RichText""
https://github.com/WordPress/gutenberg/pull/16014

Into a new issue. Where we can focus.
1. Text color icon appears and disappears from toolbar. 
2. Bring colors by the block for some blocks: https://github.com/WordPress/gutenberg/issues/20197
3. Background color issue here: https://github.com/WordPress/gutenberg/issues/20835

![Text-color-icon-appear-disappear](https://user-images.githubusercontent.com/5323259/76598917-2861e400-6504-11ea-9c12-823c0a88bcc0.gif)

Comments from:
@ellatrix 
https://github.com/WordPress/gutenberg/pull/16014#pullrequestreview-354428911

> Looks good to me. Not sure if I like the conditional placement of the button, but we can experiment with that. Also think it would be nicer to consolidate the custom color popover, but also could be adjusted later.

@mapk 
https://github.com/WordPress/gutenberg/pull/16014#pullrequestreview-354627103

> I totally agree with @ellatrix's comment. Having it appear and disappear is somewhat odd. But I just tested this out and it was working great. I'm all for getting this in and iterating later.

@afercia 
https://github.com/WordPress/gutenberg/pull/16014#issuecomment-594010817

> Saw this new feature today and I'd totally second that. I would expect to find controls where I saw them the first time. Instead, they just disappear and appear in a new place. Not to mention that, from an accessibility perspective, the accessibility team has pointed out several times that the continuous appearing / disappearing of controls is highly confusing.
> 
> I'd definitely recommend to further iterate on this soon.

---------------

",1.0,"Text color icon appears and disappears - Continuing discussion from:
""Add option to add text color to specific text inside RichText""
https://github.com/WordPress/gutenberg/pull/16014

Into a new issue. Where we can focus.
1. Text color icon appears and disappears from toolbar. 
2. Bring colors by the block for some blocks: https://github.com/WordPress/gutenberg/issues/20197
3. Background color issue here: https://github.com/WordPress/gutenberg/issues/20835

![Text-color-icon-appear-disappear](https://user-images.githubusercontent.com/5323259/76598917-2861e400-6504-11ea-9c12-823c0a88bcc0.gif)

Comments from:
@ellatrix 
https://github.com/WordPress/gutenberg/pull/16014#pullrequestreview-354428911

> Looks good to me. Not sure if I like the conditional placement of the button, but we can experiment with that. Also think it would be nicer to consolidate the custom color popover, but also could be adjusted later.

@mapk 
https://github.com/WordPress/gutenberg/pull/16014#pullrequestreview-354627103

> I totally agree with @ellatrix's comment. Having it appear and disappear is somewhat odd. But I just tested this out and it was working great. I'm all for getting this in and iterating later.

@afercia 
https://github.com/WordPress/gutenberg/pull/16014#issuecomment-594010817

> Saw this new feature today and I'd totally second that. I would expect to find controls where I saw them the first time. Instead, they just disappear and appear in a new place. Not to mention that, from an accessibility perspective, the accessibility team has pointed out several times that the continuous appearing / disappearing of controls is highly confusing.
> 
> I'd definitely recommend to further iterate on this soon.

---------------

",0,text color icon appears and disappears   continuing discussion from    add option to add text color to specific text inside richtext        into a new issue  where we can focus      text color icon appears and disappears from toolbar       bring colors by the block for some blocks        background color issue here               comments from    ellatrix          looks good to me  not sure if i like the conditional placement of the button  but we can experiment with that  also think it would be nicer to consolidate the custom color popover  but also could be adjusted later      mapk          i totally agree with  ellatrix s comment  having it appear and disappear is somewhat odd  but i just tested this out and it was working great  i m all for getting this in and iterating later      afercia          saw this new feature today and i d totally second that  i would expect to find controls where i saw them the first time  instead  they just disappear and appear in a new place  not to mention that  from an accessibility perspective  the accessibility team has pointed out several times that the continuous appearing   disappearing of controls is highly confusing         i d definitely recommend to further iterate on this soon                        ,0
63461,14656729388.0,IssuesEvent,2020-12-28 14:04:11,fu1771695yongxie/taro,https://api.github.com/repos/fu1771695yongxie/taro,opened,CVE-2020-1912 (High) detected in hermes-engine-0.2.1.tgz,security vulnerability,"## CVE-2020-1912 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hermes-engine-0.2.1.tgz</b></p></summary>

<p>A JavaScript engine optimized for running React Native on Android</p>
<p>Library home page: <a href=""https://registry.npmjs.org/hermes-engine/-/hermes-engine-0.2.1.tgz"">https://registry.npmjs.org/hermes-engine/-/hermes-engine-0.2.1.tgz</a></p>
<p>Path to dependency file: taro/package.json</p>
<p>Path to vulnerable library: taro/node_modules/hermes-engine/package.json</p>
<p>

Dependency Hierarchy:
  - react-native-0.61.5.tgz (Root Library)
    - :x: **hermes-engine-0.2.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/fu1771695yongxie/taro/commit/d6b9282bf207231f27f7ba5779aaa86a96d1e110"">d6b9282bf207231f27f7ba5779aaa86a96d1e110</a></p>
<p>Found in base branch: <b>next</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
An out-of-bounds read/write vulnerability when executing lazily compiled inner generator functions in Facebook Hermes prior to commit 091835377369c8fd5917d9b87acffa721ad2a168 allows attackers to potentially execute arbitrary code via crafted JavaScript. Note that this is only exploitable if the application using Hermes permits evaluation of untrusted JavaScript. Hence, most React Native applications are not affected.

<p>Publish Date: 2020-09-09
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-1912>CVE-2020-1912</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>8.1</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2020-1912 (High) detected in hermes-engine-0.2.1.tgz - ## CVE-2020-1912 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hermes-engine-0.2.1.tgz</b></p></summary>

<p>A JavaScript engine optimized for running React Native on Android</p>
<p>Library home page: <a href=""https://registry.npmjs.org/hermes-engine/-/hermes-engine-0.2.1.tgz"">https://registry.npmjs.org/hermes-engine/-/hermes-engine-0.2.1.tgz</a></p>
<p>Path to dependency file: taro/package.json</p>
<p>Path to vulnerable library: taro/node_modules/hermes-engine/package.json</p>
<p>

Dependency Hierarchy:
  - react-native-0.61.5.tgz (Root Library)
    - :x: **hermes-engine-0.2.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/fu1771695yongxie/taro/commit/d6b9282bf207231f27f7ba5779aaa86a96d1e110"">d6b9282bf207231f27f7ba5779aaa86a96d1e110</a></p>
<p>Found in base branch: <b>next</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
An out-of-bounds read/write vulnerability when executing lazily compiled inner generator functions in Facebook Hermes prior to commit 091835377369c8fd5917d9b87acffa721ad2a168 allows attackers to potentially execute arbitrary code via crafted JavaScript. Note that this is only exploitable if the application using Hermes permits evaluation of untrusted JavaScript. Hence, most React Native applications are not affected.

<p>Publish Date: 2020-09-09
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-1912>CVE-2020-1912</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>8.1</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: High
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in hermes engine       tgz      cve       high severity vulnerability     vulnerable library    hermes engine       tgz      a javascript engine optimized for running react native on android   library home page   a href     path to dependency file  taro package json   path to vulnerable library  taro node modules hermes engine package json     dependency hierarchy      react native       tgz  root library         x    hermes engine       tgz    vulnerable library   found in head commit   a href     found in base branch   next              vulnerability details         an out of bounds read write vulnerability when executing lazily compiled inner generator functions in facebook hermes prior to commit   allows attackers to potentially execute arbitrary code via crafted javascript  note that this is only exploitable if the application using hermes permits evaluation of untrusted javascript  hence  most react native applications are not affected    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  high     availability impact  high   for more information on   scores  click  a href                step up your open source security game with whitesource    ,0
105692,23095000010.0,IssuesEvent,2022-07-26 18:36:56,moinmalek/ar-car,https://api.github.com/repos/moinmalek/ar-car,opened,Replace public UI elements from scripts with a better solution,optimize code,"There are many public items declared in scripts, for [example](https://github.com/moinmalek/ar-car/blob/main/AR%20Car%20Project/Assets/Scripts/RepairCar.cs). They require manual drag & drop in editor. Replace them with a better solution.
",1.0,"Replace public UI elements from scripts with a better solution - There are many public items declared in scripts, for [example](https://github.com/moinmalek/ar-car/blob/main/AR%20Car%20Project/Assets/Scripts/RepairCar.cs). They require manual drag & drop in editor. Replace them with a better solution.
",0,replace public ui elements from scripts with a better solution   there are many public items declared in scripts  for     they require manual drag   drop in editor  replace them with a better solution   ,0
140185,5398388480.0,IssuesEvent,2017-02-27 16:49:36,HBHWoolacotts/RPii,https://api.github.com/repos/HBHWoolacotts/RPii,closed,"Changing ""Charge Type"" Issues",Priority - High,"When they change a charge type from Standard Chargeable to Warranty, the job sheet does not update - so the engineers do not see this change.
Also the charge customer doesn't change.  This is usually only ever a problem when the system does not detect an item under warranty.  Therefore it's usually only ever changed from Chargeable to Warranty or Extended Warranty.  The issue is that if you change it to Warranty, when the job is complete and invoiced, the Customer still gets the invoice because the customers aren't being updated.  It's causing a big problem because the customer then gets a bill and the manufacturer doesn't - Maggie has to go in and change each one manually in POS.

![image](https://cloud.githubusercontent.com/assets/10868496/18584342/0712a6c4-7c08-11e6-9c7a-2dd51ce2f755.png)
",1.0,"Changing ""Charge Type"" Issues - When they change a charge type from Standard Chargeable to Warranty, the job sheet does not update - so the engineers do not see this change.
Also the charge customer doesn't change.  This is usually only ever a problem when the system does not detect an item under warranty.  Therefore it's usually only ever changed from Chargeable to Warranty or Extended Warranty.  The issue is that if you change it to Warranty, when the job is complete and invoiced, the Customer still gets the invoice because the customers aren't being updated.  It's causing a big problem because the customer then gets a bill and the manufacturer doesn't - Maggie has to go in and change each one manually in POS.

![image](https://cloud.githubusercontent.com/assets/10868496/18584342/0712a6c4-7c08-11e6-9c7a-2dd51ce2f755.png)
",0,changing  charge type  issues   when they change a charge type from standard chargeable to warranty  the job sheet does not update   so the engineers do not see this change  also the charge customer doesn t change   this is usually only ever a problem when the system does not detect an item under warranty   therefore it s usually only ever changed from chargeable to warranty or extended warranty   the issue is that if you change it to warranty  when the job is complete and invoiced  the customer still gets the invoice because the customers aren t being updated   it s causing a big problem because the customer then gets a bill and the manufacturer doesn t   maggie has to go in and change each one manually in pos        ,0
50170,7571077201.0,IssuesEvent,2018-04-23 11:01:45,golang/go,https://api.github.com/repos/golang/go,closed,x/crypto/ssh/agent: broken link in documentation,Documentation NeedsFix,"The following reference link in the package documentation is broken:

    [PROTOCOL.agent]:    http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/PROTOCOL.agent?rev=HEAD",1.0,"x/crypto/ssh/agent: broken link in documentation - The following reference link in the package documentation is broken:

    [PROTOCOL.agent]:    http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/PROTOCOL.agent?rev=HEAD",1,x crypto ssh agent  broken link in documentation   the following reference link in the package documentation is broken                ,1
32667,6102267002.0,IssuesEvent,2017-06-20 16:08:08,golang/go,https://api.github.com/repos/golang/go,closed,doc: FAQ versioning question out of date,Documentation,https://golang.org/doc/faq#get_version mentions Go 1.5 and vendoring but not dep. It needs to be updated.,1.0,doc: FAQ versioning question out of date - https://golang.org/doc/faq#get_version mentions Go 1.5 and vendoring but not dep. It needs to be updated.,1,doc  faq versioning question out of date     mentions go     and vendoring but not dep  it needs to be updated ,1
86704,10514800390.0,IssuesEvent,2019-09-28 03:46:52,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/cmd/godoc: Malformed links in variable definition,Documentation,"The documentation for [`http.DefaultTransport`](https://golang.org/pkg/net/http/#RoundTripper) currently looks like this:

![screen shot 2015-01-16 at 1 21 10 pm](https://cloud.githubusercontent.com/assets/13026/5781662/9706c7d0-9d82-11e4-8485-bc112cfbbebf.png)

There are a bunch of things linked that should not be, including all of the field names and the `Dial` method.
",1.0,"x/tools/cmd/godoc: Malformed links in variable definition - The documentation for [`http.DefaultTransport`](https://golang.org/pkg/net/http/#RoundTripper) currently looks like this:

![screen shot 2015-01-16 at 1 21 10 pm](https://cloud.githubusercontent.com/assets/13026/5781662/9706c7d0-9d82-11e4-8485-bc112cfbbebf.png)

There are a bunch of things linked that should not be, including all of the field names and the `Dial` method.
",1,x tools cmd godoc  malformed links in variable definition   the documentation for     currently looks like this         there are a bunch of things linked that should not be  including all of the field names and the  dial  method  ,1
28061,13518822750.0,IssuesEvent,2020-09-15 00:13:01,xamarin/Xamarin.Forms,https://api.github.com/repos/xamarin/Xamarin.Forms,closed,"[Android, iOS] NavigationPage.PopAsync() cause memory leak by still holding on popped Page",a/performance e/4 :clock4: i/high in-progress p/Android p/iOS 🍎 s/needs-info ❓ t/bug :bug:,"Migrated from https://bugzilla.xamarin.com/show_bug.cgi?id=31171

### Description
Found with profiler that Task<Page> holds popped Page from the CurrentNavigationTask property of NavigationPage. 

Potential PR was closed and not merged. https://github.com/xamarin/Xamarin.Forms/pull/625

### Steps to Reproduce
Simple test case:
1) get start with Page1
2) navigate to Page2,
3) get back to Page1 with PopAsync() or back button.



### Basic Information

- Version with issue: 1.4.3

### Reproduction Link
[PagePopMemory.zip](https://github.com/xamarin/Xamarin.Forms/files/2369102/PagePopMemory.zip)

[XamarinFormsBugs.zip](https://github.com/xamarin/Xamarin.Forms/files/1573715/XamarinFormsBugs.zip)
",True,"[Android, iOS] NavigationPage.PopAsync() cause memory leak by still holding on popped Page - Migrated from https://bugzilla.xamarin.com/show_bug.cgi?id=31171

### Description
Found with profiler that Task<Page> holds popped Page from the CurrentNavigationTask property of NavigationPage. 

Potential PR was closed and not merged. https://github.com/xamarin/Xamarin.Forms/pull/625

### Steps to Reproduce
Simple test case:
1) get start with Page1
2) navigate to Page2,
3) get back to Page1 with PopAsync() or back button.



### Basic Information

- Version with issue: 1.4.3

### Reproduction Link
[PagePopMemory.zip](https://github.com/xamarin/Xamarin.Forms/files/2369102/PagePopMemory.zip)

[XamarinFormsBugs.zip](https://github.com/xamarin/Xamarin.Forms/files/1573715/XamarinFormsBugs.zip)
",0,  navigationpage popasync   cause memory leak by still holding on popped page   migrated from          description  found with profiler that task  holds popped page from the currentnavigationtask property of navigationpage      potential pr was closed and not merged           steps to reproduce  simple test case      get start with       navigate to        get back to   with popasync   or back button             basic information      version with issue               reproduction link              ,0
472247,13621521403.0,IssuesEvent,2020-09-24 00:56:31,magento/magento2,https://api.github.com/repos/magento/magento2,closed,Tier pricing tax shows only including tax,Component: Tax Fixed in 2.4.x Issue: Clear Description Issue: Confirmed Issue: Format is valid Issue: Ready for Work Priority: P3 Progress: ready for dev Reproduced on 2.4.x Severity: S3,"### Preconditions (*)
Magento 2.2, 2.3, 2.4-develop

### Steps to reproduce (*)

1. Go to Sales > Tax >Price display settings.
2. Configure to show the including and excluding tax price.
3. Go to a configurable product on the frontend with tier pricing.
4. You will see tier price including tax.
5. There is no way to change that to excluding price.

### Expected result (*)
An extra option which one has first priority, including or excluding tax.

### Actual result (*)
![screenshot_1](https://user-images.githubusercontent.com/22836339/32751647-edc03ddc-c8c6-11e7-8f1c-9ac0f791ec00.png)
The tier price only shows the including tax while I need exactly the opposit. Excluding price first, also for tier pricing.",1.0,"Tier pricing tax shows only including tax - ### Preconditions (*)
Magento 2.2, 2.3, 2.4-develop

### Steps to reproduce (*)

1. Go to Sales > Tax >Price display settings.
2. Configure to show the including and excluding tax price.
3. Go to a configurable product on the frontend with tier pricing.
4. You will see tier price including tax.
5. There is no way to change that to excluding price.

### Expected result (*)
An extra option which one has first priority, including or excluding tax.

### Actual result (*)
![screenshot_1](https://user-images.githubusercontent.com/22836339/32751647-edc03ddc-c8c6-11e7-8f1c-9ac0f791ec00.png)
The tier price only shows the including tax while I need exactly the opposit. Excluding price first, also for tier pricing.",0,tier pricing tax shows only including tax       preconditions      magento               develop        steps to reproduce           go to sales   tax  price display settings      configure to show the including and excluding tax price      go to a configurable product on the frontend with tier pricing      you will see tier price including tax      there is no way to change that to excluding price         expected result      an extra option which one has first priority  including or excluding tax         actual result            the tier price only shows the including tax while i need exactly the opposit  excluding price first  also for tier pricing ,0
558669,16540134295.0,IssuesEvent,2021-05-27 15:49:15,Kong/kubernetes-ingress-controller,https://api.github.com/repos/Kong/kubernetes-ingress-controller,closed,KIC 2.0: handle kong-custom-entities-secret flag,priority/medium,"`--kong-custom-entities-secret` specifes a Secret that contains custom entities. In DB-less mode, the [contents of this Secret are retrieved and provided to PerformUpdate](https://github.com/Kong/kubernetes-ingress-controller/blob/v1.2.0/internal/ingress/controller/kong.go#L40-L58), which appends them onto configuration generated from other Kubernetes resources.",1.0,"KIC 2.0: handle kong-custom-entities-secret flag - `--kong-custom-entities-secret` specifes a Secret that contains custom entities. In DB-less mode, the [contents of this Secret are retrieved and provided to PerformUpdate](https://github.com/Kong/kubernetes-ingress-controller/blob/v1.2.0/internal/ingress/controller/kong.go#L40-L58), which appends them onto configuration generated from other Kubernetes resources.",0,kic      handle kong custom entities secret flag      kong custom entities secret  specifes a secret that contains custom entities  in db less mode  the     which appends them onto configuration generated from other kubernetes resources ,0
611400,18954235607.0,IssuesEvent,2021-11-18 18:16:16,treecreate/webstore,https://api.github.com/repos/treecreate/webstore,opened,Set correct order ID,bug medium priority,"## Goal

<!-- What is this user story supposed to achieve, and what is the context -->

The new payments have a orderId that corresponds to the environment

## Requirements

<!--
    What the user story needs to include in order to be completed.
    The requirements can contain subsections to provide further information.
    Testing (both unit/integration and e2e tests) is implicitly required as per the definition of done. If you don't want them to be a requirement, state so explicitly
 -->
 
 - The generated `OrderId` (OrderService, call to `createOrderId`) should get the environment from the custom properties
 - When an order is generated in a production environment, the `orderId` should start with `P`. Otherwise it should be `B`

## Extra notes

<!-- If there is something special about the issue like a dependency, potential solutions or reference material it should be included -->
- There is a TODO for this issue",1.0,"Set correct order ID - ## Goal

<!-- What is this user story supposed to achieve, and what is the context -->

The new payments have a orderId that corresponds to the environment

## Requirements

<!--
    What the user story needs to include in order to be completed.
    The requirements can contain subsections to provide further information.
    Testing (both unit/integration and e2e tests) is implicitly required as per the definition of done. If you don't want them to be a requirement, state so explicitly
 -->
 
 - The generated `OrderId` (OrderService, call to `createOrderId`) should get the environment from the custom properties
 - When an order is generated in a production environment, the `orderId` should start with `P`. Otherwise it should be `B`

## Extra notes

<!-- If there is something special about the issue like a dependency, potential solutions or reference material it should be included -->
- There is a TODO for this issue",0,set correct order id      goal         the new payments have a orderid that corresponds to the environment       requirements              what the user story needs to include in order to be completed       the requirements can contain subsections to provide further information       testing  both unit integration and   tests  is implicitly required as per the definition of done  if you don t want them to be a requirement  state so explicitly              the generated  orderid   orderservice  call to  createorderid   should get the environment from the custom properties     when an order is generated in a production environment  the  orderid  should start with  p   otherwise it should be  b        extra notes         there is a todo for this issue,0
522917,15169581154.0,IssuesEvent,2021-02-12 21:25:16,MaowImpl/Optionals,https://api.github.com/repos/MaowImpl/Optionals,closed,@Optional attributes don't support arrays,annotation enhancement javac low priority,"Currently, the attributes in `@Optional` do not include any arrays. This will require a bit more condition checking in the Javac side of things, but it seems doable for now.",1.0,"@Optional attributes don't support arrays - Currently, the attributes in `@Optional` do not include any arrays. This will require a bit more condition checking in the Javac side of things, but it seems doable for now.",0, optional attributes don t support arrays   currently  the attributes in   optional  do not include any arrays  this will require a bit more condition checking in the javac side of things  but it seems doable for now ,0
132472,18268710226.0,IssuesEvent,2021-10-04 11:32:39,artsking/linux-3.0.35,https://api.github.com/repos/artsking/linux-3.0.35,opened,CVE-2016-3140 (Medium) detected in linux-stable-rtv3.8.6,security vulnerability,"## CVE-2016-3140 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv3.8.6</b></p></summary>
<p>

<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/artsking/linux-3.0.35/commit/5992fa81c6ac1b4e9db13f5408d914525c5b7875"">5992fa81c6ac1b4e9db13f5408d914525c5b7875</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (3)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/usb/serial/digi_acceleport.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/usb/serial/digi_acceleport.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/usb/serial/digi_acceleport.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The digi_port_init function in drivers/usb/serial/digi_acceleport.c in the Linux kernel before 4.5.1 allows physically proximate attackers to cause a denial of service (NULL pointer dereference and system crash) via a crafted endpoints value in a USB device descriptor.

<p>Publish Date: 2016-05-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-3140>CVE-2016-3140</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>4.6</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Physical
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2016-3140"">https://nvd.nist.gov/vuln/detail/CVE-2016-3140</a></p>
<p>Release Date: 2016-05-02</p>
<p>Fix Resolution: 4.5.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-2016-3140 (Medium) detected in linux-stable-rtv3.8.6 - ## CVE-2016-3140 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv3.8.6</b></p></summary>
<p>

<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/artsking/linux-3.0.35/commit/5992fa81c6ac1b4e9db13f5408d914525c5b7875"">5992fa81c6ac1b4e9db13f5408d914525c5b7875</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (3)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/usb/serial/digi_acceleport.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/usb/serial/digi_acceleport.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/usb/serial/digi_acceleport.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
The digi_port_init function in drivers/usb/serial/digi_acceleport.c in the Linux kernel before 4.5.1 allows physically proximate attackers to cause a denial of service (NULL pointer dereference and system crash) via a crafted endpoints value in a USB device descriptor.

<p>Publish Date: 2016-05-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-3140>CVE-2016-3140</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>4.6</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Physical
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2016-3140"">https://nvd.nist.gov/vuln/detail/CVE-2016-3140</a></p>
<p>Release Date: 2016-05-02</p>
<p>Fix Resolution: 4.5.1</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      medium  detected in linux stable            cve       medium severity vulnerability     vulnerable library    linux stable              julia cartwright s fork of linux stable rt git   library home page   a href    found in head commit   a href      found in base branch   master             vulnerable source files                  drivers usb serial digi acceleport c        drivers usb serial digi acceleport c        drivers usb serial digi acceleport c                    vulnerability details         the digi port init function in drivers usb serial digi acceleport c in the linux kernel before       allows physically proximate attackers to cause a denial of service  null pointer dereference and system crash  via a crafted endpoints value in a usb device descriptor    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  physical     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                      step up your open source security game with whitesource    ,0
507636,14680148955.0,IssuesEvent,2020-12-31 09:12:04,k8smeetup/website-tasks,https://api.github.com/repos/k8smeetup/website-tasks,opened,/docs/tasks/configmap-secret/managing-secret-using-kubectl.md,lang/zh priority/P0 sync/update version/master welcome,"Source File: [/docs/tasks/configmap-secret/managing-secret-using-kubectl.md](https://github.com/kubernetes/website/blob/master/content/en/docs/tasks/configmap-secret/managing-secret-using-kubectl.md)

Diff 命令参考:

```bash
# 查看原始文档与翻译文档更新差异
git diff --no-index  -- content/en/docs/tasks/configmap-secret/managing-secret-using-kubectl.md content/zh/docs/tasks/configmap-secret/managing-secret-using-kubectl.md

# 跨分支持查看原始文档更新差异
git diff release-1.19 master -- content/en/docs/tasks/configmap-secret/managing-secret-using-kubectl.md
```",1.0,"/docs/tasks/configmap-secret/managing-secret-using-kubectl.md - Source File: [/docs/tasks/configmap-secret/managing-secret-using-kubectl.md](https://github.com/kubernetes/website/blob/master/content/en/docs/tasks/configmap-secret/managing-secret-using-kubectl.md)

Diff 命令参考:

```bash
# 查看原始文档与翻译文档更新差异
git diff --no-index  -- content/en/docs/tasks/configmap-secret/managing-secret-using-kubectl.md content/zh/docs/tasks/configmap-secret/managing-secret-using-kubectl.md

# 跨分支持查看原始文档更新差异
git diff release-1.19 master -- content/en/docs/tasks/configmap-secret/managing-secret-using-kubectl.md
```",0, docs tasks configmap secret managing secret using kubectl md   source file       diff 命令参考      bash   查看原始文档与翻译文档更新差异 git diff   no index     content en docs tasks configmap secret managing secret using kubectl md content zh docs tasks configmap secret managing secret using kubectl md    跨分支持查看原始文档更新差异 git diff release     master    content en docs tasks configmap secret managing secret using kubectl md    ,0
105577,11454795771.0,IssuesEvent,2020-02-06 17:46:36,golang/go,https://api.github.com/repos/golang/go,closed,doc/install: update “Test your installation” step to be agnostic to module mode,Documentation NeedsFix modules,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.13.7 darwin/amd64
</pre>


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""on""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/xxxx/Library/Caches/go-build""
GOENV=""/Users/xxxx/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/xxxx/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/5k/x27nkdh9605dcjwmgmxbdr0c0000gn/T/go-build407033626=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?
I tried to create a go environment and proceeded according to the tutorial.

https://golang.org/doc/install?download=go1.13.7.darwin-amd64.pkg

Do you need `go mod init` before `go build`??
or execute `go build hello.go`.

<pre>
$ pwd
/Users/xxxx/go/src/hello
$ ls
hello.go
$ go build
go: cannot find main module; see 'go help modules'

$ cat hello.go
package main

import ""fmt""

func main() {
	fmt.Printf(""hello, world\n"")
}
</pre>
",1.0,"doc/install: update “Test your installation” step to be agnostic to module mode - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.13.7 darwin/amd64
</pre>


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""on""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/Users/xxxx/Library/Caches/go-build""
GOENV=""/Users/xxxx/Library/Application Support/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""darwin""
GOPATH=""/Users/xxxx/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""clang""
CXX=""clang++""
CGO_ENABLED=""1""
GOMOD=""/dev/null""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/5k/x27nkdh9605dcjwmgmxbdr0c0000gn/T/go-build407033626=/tmp/go-build -gno-record-gcc-switches -fno-common""
</pre></details>

### What did you do?
I tried to create a go environment and proceeded according to the tutorial.

https://golang.org/doc/install?download=go1.13.7.darwin-amd64.pkg

Do you need `go mod init` before `go build`??
or execute `go build hello.go`.

<pre>
$ pwd
/Users/xxxx/go/src/hello
$ ls
hello.go
$ go build
go: cannot find main module; see 'go help modules'

$ cat hello.go
package main

import ""fmt""

func main() {
	fmt.Printf(""hello, world\n"")
}
</pre>
",1,doc install  update “test your installation” step to be agnostic to module mode         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version            go version  go version       darwin               what operating system and processor architecture are you using   go env          go env  output       go env     on   goarch      gobin     gocache   users xxxx library caches go build   goenv   users xxxx library application support go env   goexe     goflags     gohostarch      gohostos  darwin   gonoproxy     gonosumdb     goos  darwin   gopath   users xxxx go   goprivate     goproxy     goroot   usr local go   gosumdb  sum golang org   gotmpdir     gotooldir   usr local go pkg tool darwin     gccgo  gccgo   ar  ar   cc  clang   cxx  clang     cgo enabled      gomod   dev null   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders     t go    tmp go build  gno record gcc switches  fno common             what did you do   i tried to create a go environment and proceeded according to the tutorial          do you need  go mod init  before  go build     or execute  go build hello go           pwd   users xxxx go src hello    ls  hello go    go build  go  cannot find main module  see  go help modules       cat hello go  package main    import  fmt     func main      	fmt printf  hello  world n          ,1
135131,12675703673.0,IssuesEvent,2020-06-19 02:36:33,golang/go,https://api.github.com/repos/golang/go,closed,x/tools/gopls: DocumentHighlight incorrectly highlights outer scope,Documentation Tools gopls,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14.3 darwin/amd64
$ go list -m golang.org/x/tools golang.org/x/tools/gopls
golang.org/x/tools v0.0.0-20200509030707-2212a7e161a5
golang.org/x/tools/gopls v0.0.0-20200509030707-2212a7e161a5
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
n/a
</pre></details>

### What did you do?
```go
1: package main
2: func main() {
3: 	var foo int
4: 	for {
5: 		switch foo {
6: 		case 1:
7: 			break
8: 		}
9: 	}
10: }
```
When calling `textDocument/documentHighlight` with the cursor on `break` in the code above, it incorrectly returns the outer for-loop:

```
[Trace - 16:44:47.947 PM] Sending request 'textDocument/documentHighlight - (6)'.
Params: {""textDocument"":{""uri"":""file:///private/var/folders/xm/ls208xd174v95pgd20rn_qbh0000gn/T/tmp.QM3GDnFr/main.go""},""position"":{""line"":7,""character"":3}}


[Trace - 16:44:47.948 PM] Received response 'textDocument/documentHighlight - (6)' in 1ms.
Result: [{""range"":{""start"":{""line"":7,""character"":3},""end"":{""line"":7,""character"":8}},""kind"":1},{""range"":{""start"":{""line"":4,""character"":1},""end"":{""line"":4,""character"":4}},""kind"":1}]
```

### What did you expect to see?
I expect the `switch` statement to be highlighted instead of `for`.",1.0,"x/tools/gopls: DocumentHighlight incorrectly highlights outer scope - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14.3 darwin/amd64
$ go list -m golang.org/x/tools golang.org/x/tools/gopls
golang.org/x/tools v0.0.0-20200509030707-2212a7e161a5
golang.org/x/tools/gopls v0.0.0-20200509030707-2212a7e161a5
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
n/a
</pre></details>

### What did you do?
```go
1: package main
2: func main() {
3: 	var foo int
4: 	for {
5: 		switch foo {
6: 		case 1:
7: 			break
8: 		}
9: 	}
10: }
```
When calling `textDocument/documentHighlight` with the cursor on `break` in the code above, it incorrectly returns the outer for-loop:

```
[Trace - 16:44:47.947 PM] Sending request 'textDocument/documentHighlight - (6)'.
Params: {""textDocument"":{""uri"":""file:///private/var/folders/xm/ls208xd174v95pgd20rn_qbh0000gn/T/tmp.QM3GDnFr/main.go""},""position"":{""line"":7,""character"":3}}


[Trace - 16:44:47.948 PM] Received response 'textDocument/documentHighlight - (6)' in 1ms.
Result: [{""range"":{""start"":{""line"":7,""character"":3},""end"":{""line"":7,""character"":8}},""kind"":1},{""range"":{""start"":{""line"":4,""character"":1},""end"":{""line"":4,""character"":4}},""kind"":1}]
```

### What did you expect to see?
I expect the `switch` statement to be highlighted instead of `for`.",1,x tools gopls  documenthighlight incorrectly highlights outer scope         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version            go version  go version       darwin      go list  m golang org x tools golang org x tools gopls  golang org x tools            golang org x tools gopls                     does this issue reproduce with the latest release   yes          what operating system and processor architecture are you using   go env          go env  output       go env  n a            what did you do      go     package main     func main         	var foo int     	for       		switch foo       		case        			break     		      	              when calling  textdocument documenthighlight  with the cursor on  break  in the code above  it incorrectly returns the outer for loop            sending request  textdocument documenthighlight          params    textdocument    uri   file    private var folders xm     t tmp   main go    position    line     character             received response  textdocument documenthighlight        in     result                what did you expect to see   i expect the  switch  statement to be highlighted instead of  for  ,1
32175,6037238832.0,IssuesEvent,2017-06-09 18:10:05,golang/go,https://api.github.com/repos/golang/go,closed,os/exec: docs bugs sections points to an issue with unsupported OS version,Documentation,"https://golang.org/pkg/os/exec/#pkg-note-BUG points to a bug which exists in an unsupported macosx version 10.6 only (I suppose). (https://github.com/golang/go/wiki/MinimumRequirements)

Should this be removed?",1.0,"os/exec: docs bugs sections points to an issue with unsupported OS version - https://golang.org/pkg/os/exec/#pkg-note-BUG points to a bug which exists in an unsupported macosx version 10.6 only (I suppose). (https://github.com/golang/go/wiki/MinimumRequirements)

Should this be removed?",1,os exec  docs bugs sections points to an issue with unsupported os version     points to a bug which exists in an unsupported macosx version     only  i suppose         should this be removed ,1
199070,15732993636.0,IssuesEvent,2021-03-29 18:59:26,golang/go,https://api.github.com/repos/golang/go,closed,x/crypto/openpgp: encrypt private key documentation missing,Documentation,"Please answer these questions before submitting your issue. Thanks!
### What version of Go are you using (`go version`)?

go version go1.7 darwin/amd64
### What operating system and processor architecture are you using (`go env`)?

GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/acasajus/Devel/gospace""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.7/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.7/libexec/pkg/tool/darwin_amd64""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/_m/s8xbjvsx05d7g5vm9b0wlsc00000gn/T/go-build341779350=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
### What did you do?

Tried to encrypt a openpgp.packet.PrivateKey and dump it in a PGP armor. 
### What did you expect to see?

An example on how to do it. I haven't found any way to do it. I would like a pointer in how to export a private key encrypting it with a passphrase. The inverse of openpgp.packet.PrivateKey.Decrypt.
### What did you see instead?

No information on how to do it.
",1.0,"x/crypto/openpgp: encrypt private key documentation missing - Please answer these questions before submitting your issue. Thanks!
### What version of Go are you using (`go version`)?

go version go1.7 darwin/amd64
### What operating system and processor architecture are you using (`go env`)?

GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/acasajus/Devel/gospace""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.7/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.7/libexec/pkg/tool/darwin_amd64""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/_m/s8xbjvsx05d7g5vm9b0wlsc00000gn/T/go-build341779350=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
### What did you do?

Tried to encrypt a openpgp.packet.PrivateKey and dump it in a PGP armor. 
### What did you expect to see?

An example on how to do it. I haven't found any way to do it. I would like a pointer in how to export a private key encrypting it with a passphrase. The inverse of openpgp.packet.PrivateKey.Decrypt.
### What did you see instead?

No information on how to do it.
",1,x crypto openpgp  encrypt private key documentation missing   please answer these questions before submitting your issue  thanks      what version of go are you using   go version     go version     darwin       what operating system and processor architecture are you using   go env     goarch     gobin    goexe    gohostarch     gohostos  darwin  goos  darwin  gopath   users acasajus devel gospace  gorace    goroot   usr local cellar go     libexec  gotooldir   usr local cellar go     libexec pkg tool darwin    cc  clang  gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders  m   t go    tmp go build  gno record gcc switches  fno common  cxx  clang    cgo enabled         what did you do   tried to encrypt a openpgp packet privatekey and dump it in a pgp armor       what did you expect to see   an example on how to do it  i haven t found any way to do it  i would like a pointer in how to export a private key encrypting it with a passphrase  the inverse of openpgp packet privatekey decrypt      what did you see instead   no information on how to do it  ,1
82063,10268250761.0,IssuesEvent,2019-08-23 05:33:24,golang/go,https://api.github.com/repos/golang/go,closed,unsafe docs and SliceHeader: I am not sure what is defined here,Documentation,"### What version of Go are you using (`go version`)?

1.12, but N/A

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

N/A

### What did you do?

Read the documentation for `unsafe`.

### What did you expect to see?

Something that did not confuse me.

### What did you see instead?

Something that confused me.

> In general, `reflect.SliceHeader and` `reflect.StringHeader` should be used only as `*reflect.SliceHeader` and `*reflect.StringHeader` pointing at actual slices or strings, never as plain structs. A program should not declare or allocate variables of these struct types.

This has an accompanying example:

```
// INVALID: a directly-declared header will not hold Data as a reference.
var hdr reflect.StringHeader
hdr.Data = uintptr(unsafe.Pointer(p))
hdr.Len = n
s := *(*string)(unsafe.Pointer(&hdr)) // p possibly already lost
```

What's not obvious to me: Is the *only* reason this is ""INVALID"" that p might already be lost, such that a `runtime.KeepAlive(p)` after the last line would have saved it? Or is this also intended to cover the possibility that some future version of Go may have additional unspecified magic in a slice object which is not in the `SliceHeader` parts, such that simply creating a SliceHeader (or a StringHeader) doesn't actually make a thing which could be a valid object?

I've been writing code which has a pointer (which is persistent, and in a data structure which survives past the current scope, thus at no risk of being garbage collected), and which does something to the effect of:

```
asUint16 := *(*[]uint16)(unsafe.Pointer(&reflect.SliceHeader{Data: uintptr(unsafe.Pointer(obj.ptr)), Len: int(obj.len), Cap: int(obj.len)}))
```

In fact, obj.ptr isn't going away, so I'm not worried about garbage collection. But if an actual Slice were not exactly the same size as a SliceHeader, but rather, the SliceHeader were just a *prefix* of the actual internal slice representation... This code would in fact be just plain wrong, because other code might try to access the ""rest"" of the slice object, and not find it.

Instead, I'd need to do something like:

```
var u []uint16
h := (*reflect.SliceHeader)&u
h.Data, h.Len, h.Cap = uintptr(obj.ptr), obj.len, obj.len
```

Which is, I suppose, certainly no harder to read, but I'm not sure whether it offers any semantic difference, apart from `u` holding the reference to the pointer, in a way that a temporary slice header object wouldn't.

(Related-ish: #20171, #19367.)
",1.0,"unsafe docs and SliceHeader: I am not sure what is defined here - ### What version of Go are you using (`go version`)?

1.12, but N/A

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

N/A

### What did you do?

Read the documentation for `unsafe`.

### What did you expect to see?

Something that did not confuse me.

### What did you see instead?

Something that confused me.

> In general, `reflect.SliceHeader and` `reflect.StringHeader` should be used only as `*reflect.SliceHeader` and `*reflect.StringHeader` pointing at actual slices or strings, never as plain structs. A program should not declare or allocate variables of these struct types.

This has an accompanying example:

```
// INVALID: a directly-declared header will not hold Data as a reference.
var hdr reflect.StringHeader
hdr.Data = uintptr(unsafe.Pointer(p))
hdr.Len = n
s := *(*string)(unsafe.Pointer(&hdr)) // p possibly already lost
```

What's not obvious to me: Is the *only* reason this is ""INVALID"" that p might already be lost, such that a `runtime.KeepAlive(p)` after the last line would have saved it? Or is this also intended to cover the possibility that some future version of Go may have additional unspecified magic in a slice object which is not in the `SliceHeader` parts, such that simply creating a SliceHeader (or a StringHeader) doesn't actually make a thing which could be a valid object?

I've been writing code which has a pointer (which is persistent, and in a data structure which survives past the current scope, thus at no risk of being garbage collected), and which does something to the effect of:

```
asUint16 := *(*[]uint16)(unsafe.Pointer(&reflect.SliceHeader{Data: uintptr(unsafe.Pointer(obj.ptr)), Len: int(obj.len), Cap: int(obj.len)}))
```

In fact, obj.ptr isn't going away, so I'm not worried about garbage collection. But if an actual Slice were not exactly the same size as a SliceHeader, but rather, the SliceHeader were just a *prefix* of the actual internal slice representation... This code would in fact be just plain wrong, because other code might try to access the ""rest"" of the slice object, and not find it.

Instead, I'd need to do something like:

```
var u []uint16
h := (*reflect.SliceHeader)&u
h.Data, h.Len, h.Cap = uintptr(obj.ptr), obj.len, obj.len
```

Which is, I suppose, certainly no harder to read, but I'm not sure whether it offers any semantic difference, apart from `u` holding the reference to the pointer, in a way that a temporary slice header object wouldn't.

(Related-ish: #20171, #19367.)
",1,unsafe docs and sliceheader  i am not sure what is defined here       what version of go are you using   go version            but n a        does this issue reproduce with the latest release     yes         what operating system and processor architecture are you using   go env       n a        what did you do     read the documentation for  unsafe          what did you expect to see     something that did not confuse me         what did you see instead     something that confused me       in general   reflect sliceheader and   reflect stringheader  should be used only as   reflect sliceheader  and   reflect stringheader  pointing at actual slices or strings  never as plain structs  a program should not declare or allocate variables of these struct types     this has an accompanying example             invalid  a directly declared header will not hold data as a reference   var hdr reflect stringheader  hdr data   uintptr unsafe pointer p    hdr len   n  s       string  unsafe pointer  hdr      p possibly already lost         what s not obvious to me  is the  only  reason this is  invalid  that p might already be lost  such that a  runtime keepalive p   after the last line would have saved it  or is this also intended to cover the possibility that some future version of go may have additional unspecified magic in a slice object which is not in the  sliceheader  parts  such that simply creating a sliceheader  or a stringheader  doesn t actually make a thing which could be a valid object     i ve been writing code which has a pointer  which is persistent  and in a data structure which survives past the current scope  thus at no risk of being garbage collected   and which does something to the effect of                      unsafe pointer  reflect sliceheader data  uintptr unsafe pointer obj ptr    len  int obj len   cap  int obj len             in fact  obj ptr isn t going away  so i m not worried about garbage collection  but if an actual slice were not exactly the same size as a sliceheader  but rather  the sliceheader were just a  prefix  of the actual internal slice representation    this code would in fact be just plain wrong  because other code might try to access the  rest  of the slice object  and not find it     instead  i d need to do something like          var u     h      reflect sliceheader  u  h data  h len  h cap   uintptr obj ptr   obj len  obj len         which is  i suppose  certainly no harder to read  but i m not sure whether it offers any semantic difference  apart from  u  holding the reference to the pointer  in a way that a temporary slice header object wouldn t      related ish            ,1
273347,20782794798.0,IssuesEvent,2022-03-16 16:08:55,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: clarify the meaning of `-workfile`,Documentation NeedsInvestigation,"### What version of Go are you using (`go version`)?

<pre>
$ go version
go version devel go1.18-5bd734839d Sun Feb 13 02:11:11 2022 +0000 darwin/amd64
</pre>

### What did you do?

From [the original proposal](https://go.googlesource.com/proposal/+/master/design/45713-workspace.md#proposal-the-flag), I thought `-workfile` would accept a path to other .work file.

> If -workfile is set to off, workspace mode will be disabled. If it is auto (the default), workspace mode will be enabled if a file named go.work is found in the current directory (or any of its parent directories), and disabled otherwise. If -workfile names a path to an existing file that ends in .work, workspace mode will be enabled. Any other value is an error.

But with the description of `-workfile` from `go help build`, it's unclear to me that is implemented or not. 

* Let's either document it if implemented, or update the proposal if that's not implemented.

```
$ go help build
    ...
        -workfile file
                in module aware mode, use the given go.work file as a workspace file.
                By default or when -workfile is ""auto"", the go command searches for a
                file named go.work in the current directory and then containing directories
                until one is found. If a valid go.work file is found, the modules
                specified will collectively be used as the main modules. If -workfile
                is ""off"", or a go.work file is not found in ""auto"" mode, workspace
                mode is disabled.
``` 

* If implemented, clarify the workfile should be an absolute path.

* Consider to mention the `-workfile` flag in the documentation of `go help work`. Currently there is no mention of this flag.

cc @matloob ",1.0,"cmd/go: clarify the meaning of `-workfile` - ### What version of Go are you using (`go version`)?

<pre>
$ go version
go version devel go1.18-5bd734839d Sun Feb 13 02:11:11 2022 +0000 darwin/amd64
</pre>

### What did you do?

From [the original proposal](https://go.googlesource.com/proposal/+/master/design/45713-workspace.md#proposal-the-flag), I thought `-workfile` would accept a path to other .work file.

> If -workfile is set to off, workspace mode will be disabled. If it is auto (the default), workspace mode will be enabled if a file named go.work is found in the current directory (or any of its parent directories), and disabled otherwise. If -workfile names a path to an existing file that ends in .work, workspace mode will be enabled. Any other value is an error.

But with the description of `-workfile` from `go help build`, it's unclear to me that is implemented or not. 

* Let's either document it if implemented, or update the proposal if that's not implemented.

```
$ go help build
    ...
        -workfile file
                in module aware mode, use the given go.work file as a workspace file.
                By default or when -workfile is ""auto"", the go command searches for a
                file named go.work in the current directory and then containing directories
                until one is found. If a valid go.work file is found, the modules
                specified will collectively be used as the main modules. If -workfile
                is ""off"", or a go.work file is not found in ""auto"" mode, workspace
                mode is disabled.
``` 

* If implemented, clarify the workfile should be an absolute path.

* Consider to mention the `-workfile` flag in the documentation of `go help work`. Currently there is no mention of this flag.

cc @matloob ",1,cmd go  clarify the meaning of   workfile        what version of go are you using   go version            go version  go version devel       sun feb              darwin             what did you do     from     i thought   workfile  would accept a path to other  work file       if  workfile is set to off  workspace mode will be disabled  if it is auto  the default   workspace mode will be enabled if a file named go work is found in the current directory  or any of its parent directories   and disabled otherwise  if  workfile names a path to an existing file that ends in  work  workspace mode will be enabled  any other value is an error     but with the description of   workfile  from  go help build   it s unclear to me that is implemented or not        let s either document it if implemented  or update the proposal if that s not implemented            go help build                    workfile file                  in module aware mode  use the given go work file as a workspace file                   by default or when  workfile is  auto   the go command searches for a                  file named go work in the current directory and then containing directories                  until one is found  if a valid go work file is found  the modules                  specified will collectively be used as the main modules  if  workfile                  is  off   or a go work file is not found in  auto  mode  workspace                  mode is disabled             if implemented  clarify the workfile should be an absolute path       consider to mention the   workfile  flag in the documentation of  go help work   currently there is no mention of this flag     cc  matloob ,1
127000,26959685773.0,IssuesEvent,2023-02-08 17:13:23,aws-amplify/amplify-flutter,https://api.github.com/repos/aws-amplify/amplify-flutter,closed,Missing concrete implementations of 'ModelProviderInterface.getModelTypeByModelName',Question Codegen GraphQL API pending-response,"### Description

Hello, 
this is a new issue, as the [old issue](https://github.com/aws-amplify/amplify-flutter/issues/1455) is set as resolved, but I could not find any evidence that it actually is and the comments over there suggest otherwise, too.

### Categories

- [ ] Analytics
- [ ] API (REST)
- [X] API (GraphQL)
- [ ] Auth
- [ ] Authenticator
- [ ] DataStore
- [ ] Storage

### Steps to Reproduce

1. Create a Flutter app
2. Init amplify and add api
3. Add a simpel GraphQL schema
4. Update dependencies with amplify_flutter: ^^1.0.0-next.0 and amplify_api: ^^1.0.0-next.0
5. Run amplify codegen models

### Screenshots

![image](https://user-images.githubusercontent.com/45431210/211068175-6f89eba2-ca7c-472b-b81c-deb5d23a38ad.png)
![image](https://user-images.githubusercontent.com/45431210/211068832-d03f4858-b003-4b0d-9c3f-7eabbf413fee.png)


### Platforms

- [X] iOS
- [X] Android
- [X] Web
- [X] macOS
- [X] Windows
- [X] Linux

### Android Device/Emulator API Level

_No response_

### Environment

```bash
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.3.9, on macOS 13.1 22C65 darwin-x64, locale de-DE)
[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.

[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
[✗] Chrome - develop for the web (Cannot find Chrome executable at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[!] Android Studio (not installed)
[✓] VS Code (version 1.74.2)
[✓] Connected device (1 available)
[✓] HTTP Host Availability
```


### Dependencies

```bash
Dart SDK 2.18.5
Flutter SDK 3.3.9
stt_app 1.0.0+1

dependencies:
- amplify_auth_cognito 1.0.0-next.2+1 [amplify_auth_cognito_android amplify_auth_cognito_dart amplify_auth_cognito_ios amplify_core amplify_flutter amplify_secure_storage async flutter flutter_web_plugins meta path plugin_platform_interface]
- amplify_flutter 1.0.0-next.2 [amplify_core amplify_datastore_plugin_interface amplify_flutter_android amplify_flutter_ios amplify_secure_storage aws_common collection flutter meta plugin_platform_interface]
- cupertino_icons 1.0.5
- flutter 0.0.0 [characters collection material_color_utilities meta vector_math sky_engine]
- flutter_riverpod 2.0.2 [collection flutter meta riverpod state_notifier]
- font_awesome_flutter 10.2.1 [flutter]
- riverpod_annotation 1.0.4 [meta riverpod]

transitive dependencies:
- amplify_auth_cognito_android 1.0.0-next.2 [flutter]
- amplify_auth_cognito_dart 0.3.1 [amplify_core amplify_secure_storage_dart async aws_common aws_signature_v4 built_collection built_value collection convert crypto fixnum http intl js json_annotation meta oauth2 path smithy smithy_aws stream_transform uuid worker_bee]
- amplify_auth_cognito_ios 1.0.0-next.2 [amplify_core flutter]
- amplify_core 1.0.0-next.2+1 [async aws_common aws_signature_v4 collection intl json_annotation logging meta retry uuid]
- amplify_datastore_plugin_interface 1.0.0-next.2 [amplify_core collection flutter meta]
- amplify_flutter_android 1.0.0-next.2 [flutter]
- amplify_flutter_ios 1.0.0-next.2 [amplify_core flutter]
- amplify_secure_storage 0.1.4 [amplify_secure_storage_dart async file flutter meta path path_provider]
- amplify_secure_storage_dart 0.1.4 [async aws_common built_collection built_value ffi file js meta path win32 worker_bee]
- async 2.9.0 [collection meta]
- aws_common 0.3.5 [async built_collection built_value collection http2 js json_annotation logging meta mime os_detect path stream_transform uuid]
- aws_signature_v4 0.3.1 [async aws_common collection convert crypto json_annotation meta path]
- built_collection 5.1.1
- built_value 8.4.1 [built_collection collection fixnum meta]
- characters 1.2.1
- clock 1.1.1
- collection 1.16.0
- convert 3.1.1 [typed_data]
- crclib 3.0.0 [meta tuple]
- crypto 3.0.2 [typed_data]
- ffi 2.0.1
- file 6.1.4 [meta path]
- fixnum 1.0.1
- flutter_web_plugins 0.0.0 [flutter js characters collection material_color_utilities meta vector_math]
- http 0.13.5 [async http_parser meta path]
- http2 2.0.1
- http_parser 4.0.2 [collection source_span string_scanner typed_data]
- intl 0.17.0 [clock path]
- js 0.6.4
- json_annotation 4.7.0 [meta]
- logging 1.1.0
- material_color_utilities 0.1.5
- meta 1.8.0
- mime 1.0.2
- oauth2 2.0.1 [collection crypto http http_parser]
- os_detect 2.0.1
- path 1.8.2
- path_provider 2.0.11 [flutter path_provider_android path_provider_ios path_provider_linux path_provider_macos path_provider_platform_interface path_provider_windows]
- path_provider_android 2.0.22 [flutter path_provider_platform_interface]
- path_provider_ios 2.0.11 [flutter path_provider_platform_interface]
- path_provider_linux 2.1.7 [ffi flutter path path_provider_platform_interface xdg_directories]
- path_provider_macos 2.0.6 [flutter path_provider_platform_interface]
- path_provider_platform_interface 2.0.5 [flutter platform plugin_platform_interface]
- path_provider_windows 2.1.3 [ffi flutter path path_provider_platform_interface win32]
- petitparser 5.1.0 [meta]
- platform 3.1.0
- plugin_platform_interface 2.1.3 [meta]
- process 4.2.4 [file path platform]
- retry 3.1.0
- riverpod 2.0.2 [collection meta stack_trace state_notifier]
- shelf 1.4.0 [async collection http_parser path stack_trace stream_channel]
- sky_engine 0.0.99
- smithy 0.3.2 [async aws_common built_collection built_value collection convert crypto fixnum http_parser intl json_annotation meta path retry shelf typed_data xml]
- smithy_aws 0.3.2 [aws_common aws_signature_v4 built_collection built_value collection convert crclib crypto intl json_annotation meta path smithy xml]
- source_span 1.9.0 [collection path term_glyph]
- stack_trace 1.10.0 [path]
- state_notifier 0.7.2+1 [meta]
- stream_channel 2.1.0 [async]
- stream_transform 2.0.1
- string_scanner 1.1.1 [source_span]
- term_glyph 1.2.1
- tuple 2.0.1
- typed_data 1.3.1 [collection]
- uuid 3.0.6 [crypto]
- vector_math 2.1.2
- win32 3.1.3 [ffi]
- worker_bee 0.1.3 [async aws_common built_collection built_value collection js meta path stack_trace stream_channel stream_transform]
- xdg_directories 0.2.0+2 [meta path process]
- xml 6.1.0 [collection meta petitparser]
```


### Device

N/A

### OS

N/A

### Deployment Method

Amplify CLI

### CLI Version

10.6.1

### Additional Context

_No response_

### Amplify Config

{
  ""features"": {
    ""graphqltransformer"": {
      ""addmissingownerfields"": true,
      ""improvepluralization"": false,
      ""validatetypenamereservedwords"": true,
      ""useexperimentalpipelinedtransformer"": true,
      ""enableiterativegsiupdates"": true,
      ""secondarykeyasgsi"": true,
      ""skipoverridemutationinputtypes"": true,
      ""transformerversion"": 2,
      ""suppressschemamigrationprompt"": true,
      ""securityenhancementnotification"": false,
      ""showfieldauthnotification"": false,
      ""usesubusernamefordefaultidentityclaim"": true,
      ""usefieldnameforprimarykeyconnectionfield"": false,
      ""enableautoindexquerynames"": true,
      ""respectprimarykeyattributesonconnectionfield"": true,
      ""shoulddeepmergedirectiveconfigdefaults"": false,
      ""populateownerfieldforstaticgroupauth"": true
    },
    ""frontend-ios"": {
      ""enablexcodeintegration"": true
    },
    ""auth"": {
      ""enablecaseinsensitivity"": true,
      ""useinclusiveterminology"": true,
      ""breakcirculardependency"": true,
      ""forcealiasattributes"": false,
      ""useenabledmfas"": true
    },
    ""codegen"": {
      ""useappsyncmodelgenplugin"": true,
      ""usedocsgeneratorplugin"": true,
      ""usetypesgeneratorplugin"": true,
      ""cleangeneratedmodelsdirectory"": true,
      ""retaincasestyle"": true,
      ""addtimestampfields"": true,
      ""handlelistnullabilitytransparently"": true,
      ""emitauthprovider"": true,
      ""generateindexrules"": true,
      ""enabledartnullsafety"": true
    },
    ""appsync"": {
      ""generategraphqlpermissions"": true
    },
    ""latestregionsupport"": {
      ""pinpoint"": 1,
      ""translate"": 1,
      ""transcribe"": 1,
      ""rekognition"": 1,
      ""textract"": 1,
      ""comprehend"": 1
    },
    ""project"": {
      ""overrides"": true
    }
  },
  ""debug"": {
    ""shareProjectConfig"": false
  }
}",1.0,"Missing concrete implementations of 'ModelProviderInterface.getModelTypeByModelName' - ### Description

Hello, 
this is a new issue, as the [old issue](https://github.com/aws-amplify/amplify-flutter/issues/1455) is set as resolved, but I could not find any evidence that it actually is and the comments over there suggest otherwise, too.

### Categories

- [ ] Analytics
- [ ] API (REST)
- [X] API (GraphQL)
- [ ] Auth
- [ ] Authenticator
- [ ] DataStore
- [ ] Storage

### Steps to Reproduce

1. Create a Flutter app
2. Init amplify and add api
3. Add a simpel GraphQL schema
4. Update dependencies with amplify_flutter: ^^1.0.0-next.0 and amplify_api: ^^1.0.0-next.0
5. Run amplify codegen models

### Screenshots

![image](https://user-images.githubusercontent.com/45431210/211068175-6f89eba2-ca7c-472b-b81c-deb5d23a38ad.png)
![image](https://user-images.githubusercontent.com/45431210/211068832-d03f4858-b003-4b0d-9c3f-7eabbf413fee.png)


### Platforms

- [X] iOS
- [X] Android
- [X] Web
- [X] macOS
- [X] Windows
- [X] Linux

### Android Device/Emulator API Level

_No response_

### Environment

```bash
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.3.9, on macOS 13.1 22C65 darwin-x64, locale de-DE)
[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.

[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
[✗] Chrome - develop for the web (Cannot find Chrome executable at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[!] Android Studio (not installed)
[✓] VS Code (version 1.74.2)
[✓] Connected device (1 available)
[✓] HTTP Host Availability
```


### Dependencies

```bash
Dart SDK 2.18.5
Flutter SDK 3.3.9
stt_app 1.0.0+1

dependencies:
- amplify_auth_cognito 1.0.0-next.2+1 [amplify_auth_cognito_android amplify_auth_cognito_dart amplify_auth_cognito_ios amplify_core amplify_flutter amplify_secure_storage async flutter flutter_web_plugins meta path plugin_platform_interface]
- amplify_flutter 1.0.0-next.2 [amplify_core amplify_datastore_plugin_interface amplify_flutter_android amplify_flutter_ios amplify_secure_storage aws_common collection flutter meta plugin_platform_interface]
- cupertino_icons 1.0.5
- flutter 0.0.0 [characters collection material_color_utilities meta vector_math sky_engine]
- flutter_riverpod 2.0.2 [collection flutter meta riverpod state_notifier]
- font_awesome_flutter 10.2.1 [flutter]
- riverpod_annotation 1.0.4 [meta riverpod]

transitive dependencies:
- amplify_auth_cognito_android 1.0.0-next.2 [flutter]
- amplify_auth_cognito_dart 0.3.1 [amplify_core amplify_secure_storage_dart async aws_common aws_signature_v4 built_collection built_value collection convert crypto fixnum http intl js json_annotation meta oauth2 path smithy smithy_aws stream_transform uuid worker_bee]
- amplify_auth_cognito_ios 1.0.0-next.2 [amplify_core flutter]
- amplify_core 1.0.0-next.2+1 [async aws_common aws_signature_v4 collection intl json_annotation logging meta retry uuid]
- amplify_datastore_plugin_interface 1.0.0-next.2 [amplify_core collection flutter meta]
- amplify_flutter_android 1.0.0-next.2 [flutter]
- amplify_flutter_ios 1.0.0-next.2 [amplify_core flutter]
- amplify_secure_storage 0.1.4 [amplify_secure_storage_dart async file flutter meta path path_provider]
- amplify_secure_storage_dart 0.1.4 [async aws_common built_collection built_value ffi file js meta path win32 worker_bee]
- async 2.9.0 [collection meta]
- aws_common 0.3.5 [async built_collection built_value collection http2 js json_annotation logging meta mime os_detect path stream_transform uuid]
- aws_signature_v4 0.3.1 [async aws_common collection convert crypto json_annotation meta path]
- built_collection 5.1.1
- built_value 8.4.1 [built_collection collection fixnum meta]
- characters 1.2.1
- clock 1.1.1
- collection 1.16.0
- convert 3.1.1 [typed_data]
- crclib 3.0.0 [meta tuple]
- crypto 3.0.2 [typed_data]
- ffi 2.0.1
- file 6.1.4 [meta path]
- fixnum 1.0.1
- flutter_web_plugins 0.0.0 [flutter js characters collection material_color_utilities meta vector_math]
- http 0.13.5 [async http_parser meta path]
- http2 2.0.1
- http_parser 4.0.2 [collection source_span string_scanner typed_data]
- intl 0.17.0 [clock path]
- js 0.6.4
- json_annotation 4.7.0 [meta]
- logging 1.1.0
- material_color_utilities 0.1.5
- meta 1.8.0
- mime 1.0.2
- oauth2 2.0.1 [collection crypto http http_parser]
- os_detect 2.0.1
- path 1.8.2
- path_provider 2.0.11 [flutter path_provider_android path_provider_ios path_provider_linux path_provider_macos path_provider_platform_interface path_provider_windows]
- path_provider_android 2.0.22 [flutter path_provider_platform_interface]
- path_provider_ios 2.0.11 [flutter path_provider_platform_interface]
- path_provider_linux 2.1.7 [ffi flutter path path_provider_platform_interface xdg_directories]
- path_provider_macos 2.0.6 [flutter path_provider_platform_interface]
- path_provider_platform_interface 2.0.5 [flutter platform plugin_platform_interface]
- path_provider_windows 2.1.3 [ffi flutter path path_provider_platform_interface win32]
- petitparser 5.1.0 [meta]
- platform 3.1.0
- plugin_platform_interface 2.1.3 [meta]
- process 4.2.4 [file path platform]
- retry 3.1.0
- riverpod 2.0.2 [collection meta stack_trace state_notifier]
- shelf 1.4.0 [async collection http_parser path stack_trace stream_channel]
- sky_engine 0.0.99
- smithy 0.3.2 [async aws_common built_collection built_value collection convert crypto fixnum http_parser intl json_annotation meta path retry shelf typed_data xml]
- smithy_aws 0.3.2 [aws_common aws_signature_v4 built_collection built_value collection convert crclib crypto intl json_annotation meta path smithy xml]
- source_span 1.9.0 [collection path term_glyph]
- stack_trace 1.10.0 [path]
- state_notifier 0.7.2+1 [meta]
- stream_channel 2.1.0 [async]
- stream_transform 2.0.1
- string_scanner 1.1.1 [source_span]
- term_glyph 1.2.1
- tuple 2.0.1
- typed_data 1.3.1 [collection]
- uuid 3.0.6 [crypto]
- vector_math 2.1.2
- win32 3.1.3 [ffi]
- worker_bee 0.1.3 [async aws_common built_collection built_value collection js meta path stack_trace stream_channel stream_transform]
- xdg_directories 0.2.0+2 [meta path process]
- xml 6.1.0 [collection meta petitparser]
```


### Device

N/A

### OS

N/A

### Deployment Method

Amplify CLI

### CLI Version

10.6.1

### Additional Context

_No response_

### Amplify Config

{
  ""features"": {
    ""graphqltransformer"": {
      ""addmissingownerfields"": true,
      ""improvepluralization"": false,
      ""validatetypenamereservedwords"": true,
      ""useexperimentalpipelinedtransformer"": true,
      ""enableiterativegsiupdates"": true,
      ""secondarykeyasgsi"": true,
      ""skipoverridemutationinputtypes"": true,
      ""transformerversion"": 2,
      ""suppressschemamigrationprompt"": true,
      ""securityenhancementnotification"": false,
      ""showfieldauthnotification"": false,
      ""usesubusernamefordefaultidentityclaim"": true,
      ""usefieldnameforprimarykeyconnectionfield"": false,
      ""enableautoindexquerynames"": true,
      ""respectprimarykeyattributesonconnectionfield"": true,
      ""shoulddeepmergedirectiveconfigdefaults"": false,
      ""populateownerfieldforstaticgroupauth"": true
    },
    ""frontend-ios"": {
      ""enablexcodeintegration"": true
    },
    ""auth"": {
      ""enablecaseinsensitivity"": true,
      ""useinclusiveterminology"": true,
      ""breakcirculardependency"": true,
      ""forcealiasattributes"": false,
      ""useenabledmfas"": true
    },
    ""codegen"": {
      ""useappsyncmodelgenplugin"": true,
      ""usedocsgeneratorplugin"": true,
      ""usetypesgeneratorplugin"": true,
      ""cleangeneratedmodelsdirectory"": true,
      ""retaincasestyle"": true,
      ""addtimestampfields"": true,
      ""handlelistnullabilitytransparently"": true,
      ""emitauthprovider"": true,
      ""generateindexrules"": true,
      ""enabledartnullsafety"": true
    },
    ""appsync"": {
      ""generategraphqlpermissions"": true
    },
    ""latestregionsupport"": {
      ""pinpoint"": 1,
      ""translate"": 1,
      ""transcribe"": 1,
      ""rekognition"": 1,
      ""textract"": 1,
      ""comprehend"": 1
    },
    ""project"": {
      ""overrides"": true
    }
  },
  ""debug"": {
    ""shareProjectConfig"": false
  }
}",0,missing concrete implementations of  modelproviderinterface getmodeltypebymodelname        description    hello    this is a new issue  as the     is set as resolved  but i could not find any evidence that it actually is and the comments over there suggest otherwise  too         categories        analytics      api  rest       api  graphql       auth      authenticator      datastore      storage        steps to reproduce       create a flutter app     init amplify and add api     add a simpel graphql schema     update dependencies with amplify flutter          next   and amplify api          next       run amplify codegen models        screenshots                        platforms        ios      android      web      macos      windows      linux        android device emulator api level     no response         environment       bash  doctor summary  to see all details  run flutter doctor  v      flutter  channel stable         on macos       darwin    locale de de     android toolchain   develop for android devices      ✗ unable to locate android sdk         install android studio from           on first launch it will assist you in installing the android sdk components          or visit   for detailed instructions          if the android sdk has been installed to a custom location  please use         flutter config   android sdk  to update to that location       xcode   develop for ios and macos  xcode         chrome   develop for the web  cannot find chrome executable at  applications google chrome app contents macos google chrome         cannot find chrome  try setting chrome executable to a chrome executable     android studio  not installed     vs code  version           connected device    available     http host availability               dependencies       bash  dart sdk        flutter sdk        stt app            dependencies     amplify auth cognito       next          amplify flutter       next        cupertino icons          flutter            flutter riverpod            font awesome flutter            riverpod annotation            transitive dependencies     amplify auth cognito android       next        amplify auth cognito dart            amplify auth cognito ios       next        amplify core       next          amplify datastore plugin interface       next        amplify flutter android       next        amplify flutter ios       next        amplify secure storage            amplify secure storage dart            async            aws common            aws signature              built collection          built value            characters          clock          collection          convert            crclib            crypto            ffi          file            fixnum          flutter web plugins            http                       http parser            intl            js          json annotation            logging          material color utilities          meta          mime                       os detect          path          path provider            path provider android            path provider ios            path provider linux            path provider macos            path provider platform interface            path provider windows            petitparser            platform          plugin platform interface            process            retry          riverpod            shelf            sky engine          smithy            smithy aws            source span            stack trace            state notifier              stream channel            stream transform          string scanner            term glyph          tuple          typed data            uuid            vector math                       worker bee            xdg directories              xml                       device    n a        os    n a        deployment method    amplify cli        cli version                 additional context     no response         amplify config          features           graphqltransformer             addmissingownerfields   true          improvepluralization   false          validatetypenamereservedwords   true          useexperimentalpipelinedtransformer   true          enableiterativegsiupdates   true          secondarykeyasgsi   true          skipoverridemutationinputtypes   true          transformerversion              suppressschemamigrationprompt   true          securityenhancementnotification   false          showfieldauthnotification   false          usesubusernamefordefaultidentityclaim   true          usefieldnameforprimarykeyconnectionfield   false          enableautoindexquerynames   true          respectprimarykeyattributesonconnectionfield   true          shoulddeepmergedirectiveconfigdefaults   false          populateownerfieldforstaticgroupauth   true               frontend ios             enablexcodeintegration   true               auth             enablecaseinsensitivity   true          useinclusiveterminology   true          breakcirculardependency   true          forcealiasattributes   false          useenabledmfas   true               codegen             useappsyncmodelgenplugin   true          usedocsgeneratorplugin   true          usetypesgeneratorplugin   true          cleangeneratedmodelsdirectory   true          retaincasestyle   true          addtimestampfields   true          handlelistnullabilitytransparently   true          emitauthprovider   true          generateindexrules   true          enabledartnullsafety   true               appsync             generategraphqlpermissions   true               latestregionsupport             pinpoint              translate              transcribe              rekognition              textract              comprehend                   project             overrides   true                  debug           shareprojectconfig   false        ,0
213574,16527619053.0,IssuesEvent,2021-05-26 22:42:08,golang/go,https://api.github.com/repos/golang/go,closed,doc/go1.17: document mime changes for Go 1.17,Documentation NeedsInvestigation help wanted release-blocker,"As of filing this issue, the [Go 1.17 draft release notes](https://tip.golang.org/doc/go1.17) contained the following HTML:

<dl id=""mime""><dt><a href=""/pkg/mime/"">mime</a></dt>
  <dd>
    <p><!-- CL 305230 -->
      TODO: <a href=""https://golang.org/cl/305230"">https://golang.org/cl/305230</a>: support reading shared mime-info database on unix systems
    </p>
  </dd>
</dl>

---

This TODO needs to be resolved by July 1 so that we can have complete release notes for [Beta 1](https://golang.org/s/release#june-1--december-1-beta-1-issued).

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.17:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.17) and include ""For #44513. Fixes #46013."" in the body.",1.0,"doc/go1.17: document mime changes for Go 1.17 - As of filing this issue, the [Go 1.17 draft release notes](https://tip.golang.org/doc/go1.17) contained the following HTML:

<dl id=""mime""><dt><a href=""/pkg/mime/"">mime</a></dt>
  <dd>
    <p><!-- CL 305230 -->
      TODO: <a href=""https://golang.org/cl/305230"">https://golang.org/cl/305230</a>: support reading shared mime-info database on unix systems
    </p>
  </dd>
</dl>

---

This TODO needs to be resolved by July 1 so that we can have complete release notes for [Beta 1](https://golang.org/s/release#june-1--december-1-beta-1-issued).

A sequence of steps to resolve this issue may be:

1. Come up with a draft release note entry in this issue, then move the issue to NeedsFix state.
2. Send a CL with ""doc/go1.17:"" [prefix](https://go-review.googlesource.com/q/project:go+doc/go1.17) and include ""For #44513. Fixes #46013."" in the body.",1,doc      document mime changes for go       as of filing this issue  the     contained the following html      mime                    todo   a href    support reading shared mime info database on unix systems                   this todo needs to be resolved by july   so that we can have complete release notes for      a sequence of steps to resolve this issue may be      come up with a draft release note entry in this issue  then move the issue to needsfix state     send a cl with  doc           and include  for     fixes      in the body ,1
13162,3689549422.0,IssuesEvent,2016-02-25 16:48:30,golang/go,https://api.github.com/repos/golang/go,closed,expvar: document Get miss behavior,Documentation,"Spent some time today debugging an issue, which came down to trying to Get an expvar key that doesn't exist.

I would expect expvar.Get(""unregistered-key"") to panic, just like trying to publish a duplicate key would do. If not, the documentation should be more explicit that Getting a non-existing key will return nil.",1.0,"expvar: document Get miss behavior - Spent some time today debugging an issue, which came down to trying to Get an expvar key that doesn't exist.

I would expect expvar.Get(""unregistered-key"") to panic, just like trying to publish a duplicate key would do. If not, the documentation should be more explicit that Getting a non-existing key will return nil.",1,expvar  document get miss behavior   spent some time today debugging an issue  which came down to trying to get an expvar key that doesn t exist     i would expect expvar get  unregistered key   to panic  just like trying to publish a duplicate key would do  if not  the documentation should be more explicit that getting a non existing key will return nil ,1
58616,8289435903.0,IssuesEvent,2018-09-19 14:41:10,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: provide advice for authors of existing packages with version v2.0+,Documentation NeedsInvestigation modules,"Hi,
I was testing vgo the other day, trying to import some 3rd party dependencies that have version v2.0 or higher released on Github, but I couldn't figure out how.

Example:
Given [github.com/go-chi/chi](https://github.com/go-chi/chi) has latest version v3.3.2 released as a [git tag](https://github.com/go-chi/chi/releases/tag/v3.3.2) on Github,
I'd like to import `github.com/go-chi/chi/v3` in my project, develop against it and eventually vendor it via `vgo vendor`.

```go
package main

import ""github.com/go-chi/chi/v3""

func main() {
	_ = chi.NewRouter()
}
```

But since github.com/go-chi/chi didn't release a v3 module yet, I get this error:
```bash
$ vgo run main.go
vgo: creating new go.mod: module github.com/VojtechVitek/vgo-test
vgo: resolving import ""github.com/go-chi/chi/v3""
vgo: finding github.com/go-chi/chi (latest)
vgo: adding github.com/go-chi/chi v1.0.0
vgo: import ""github.com/go-chi/chi/v3"" [/Users/vojtechvitek/go/src/v/github.com/go-chi/chi@v1.0.0/v3]: open /Users/vojtechvitek/go/src/v/github.com/go-chi/chi@v1.0.0/v3: no such file or directory
```

vgo found version v1.0.0 but couldn't find ""v3"" subpkg. So I added an explicit version to my go.mod file and tried again:
```
$ cat go.mod
module github.com/VojtechVitek/vgo-test

require (
	github.com/go-chi/chi v3.3.2
)
```

running vgo again caused a silent side effect:
```diff
module github.com/VojtechVitek/vgo-test

require (
- 	github.com/go-chi/chi v3.3.2
+ 	github.com/go-chi/chi v0.0.0-20171222161133-e83ac2304db3
)
```

Hmm, seems like vgo doesn't see any v2.0+ tags? After reading some more blog posts on https://research.swtch.com (since `vgo` CLI help didn't seem to be very helpful / novice user friendly), I confirmed with:
```
$ vgo list -t github.com/go-chi/chi
github.com/go-chi/chi
	v0.9.0
	v1.0.0
```

Now, I might be missing something, but it's not really clear to me how can I import v2.0+ or v3.0+ of a package (should I say module?) that I don't have any control over and ""is not ready yet"".

Are there any guidelines for package consumers about this? Are there any guidelines for package authors? I couldn't find anything useful neither in research.swtch.com/vgo-module, nor in the accepted proposal or in the [wiki](https://github.com/golang/go/wiki/vgo).


// EDIT:
```
$ vgo list -t github.com/go-chi/chi/v3
github.com/go-chi/chi/v3
	v3.0.0
	v3.1.0
	v3.1.1
	v3.1.2
	v3.1.3
	v3.1.4
	v3.1.5
	v3.2.0
	v3.2.1
	v3.3.0
	v3.3.1
	v3.3.2
```

Ahaa, so I can list v3.0+ tags. But how do I use them in my monorepo properly?

```
$ vgo get github.com/go-chi/chi/v3
vgo: creating new go.mod: module github.com/VojtechVitek/vgo-test
vgo: github.com/go-chi/chi/v3 v3.3.2: missing or invalid go.mod
vgo get: missing or invalid go.mod
```",1.0,"cmd/go: provide advice for authors of existing packages with version v2.0+ - Hi,
I was testing vgo the other day, trying to import some 3rd party dependencies that have version v2.0 or higher released on Github, but I couldn't figure out how.

Example:
Given [github.com/go-chi/chi](https://github.com/go-chi/chi) has latest version v3.3.2 released as a [git tag](https://github.com/go-chi/chi/releases/tag/v3.3.2) on Github,
I'd like to import `github.com/go-chi/chi/v3` in my project, develop against it and eventually vendor it via `vgo vendor`.

```go
package main

import ""github.com/go-chi/chi/v3""

func main() {
	_ = chi.NewRouter()
}
```

But since github.com/go-chi/chi didn't release a v3 module yet, I get this error:
```bash
$ vgo run main.go
vgo: creating new go.mod: module github.com/VojtechVitek/vgo-test
vgo: resolving import ""github.com/go-chi/chi/v3""
vgo: finding github.com/go-chi/chi (latest)
vgo: adding github.com/go-chi/chi v1.0.0
vgo: import ""github.com/go-chi/chi/v3"" [/Users/vojtechvitek/go/src/v/github.com/go-chi/chi@v1.0.0/v3]: open /Users/vojtechvitek/go/src/v/github.com/go-chi/chi@v1.0.0/v3: no such file or directory
```

vgo found version v1.0.0 but couldn't find ""v3"" subpkg. So I added an explicit version to my go.mod file and tried again:
```
$ cat go.mod
module github.com/VojtechVitek/vgo-test

require (
	github.com/go-chi/chi v3.3.2
)
```

running vgo again caused a silent side effect:
```diff
module github.com/VojtechVitek/vgo-test

require (
- 	github.com/go-chi/chi v3.3.2
+ 	github.com/go-chi/chi v0.0.0-20171222161133-e83ac2304db3
)
```

Hmm, seems like vgo doesn't see any v2.0+ tags? After reading some more blog posts on https://research.swtch.com (since `vgo` CLI help didn't seem to be very helpful / novice user friendly), I confirmed with:
```
$ vgo list -t github.com/go-chi/chi
github.com/go-chi/chi
	v0.9.0
	v1.0.0
```

Now, I might be missing something, but it's not really clear to me how can I import v2.0+ or v3.0+ of a package (should I say module?) that I don't have any control over and ""is not ready yet"".

Are there any guidelines for package consumers about this? Are there any guidelines for package authors? I couldn't find anything useful neither in research.swtch.com/vgo-module, nor in the accepted proposal or in the [wiki](https://github.com/golang/go/wiki/vgo).


// EDIT:
```
$ vgo list -t github.com/go-chi/chi/v3
github.com/go-chi/chi/v3
	v3.0.0
	v3.1.0
	v3.1.1
	v3.1.2
	v3.1.3
	v3.1.4
	v3.1.5
	v3.2.0
	v3.2.1
	v3.3.0
	v3.3.1
	v3.3.2
```

Ahaa, so I can list v3.0+ tags. But how do I use them in my monorepo properly?

```
$ vgo get github.com/go-chi/chi/v3
vgo: creating new go.mod: module github.com/VojtechVitek/vgo-test
vgo: github.com/go-chi/chi/v3 v3.3.2: missing or invalid go.mod
vgo get: missing or invalid go.mod
```",1,cmd go  provide advice for authors of existing packages with version        hi   i was testing vgo the other day  trying to import some   party dependencies that have version     or higher released on github  but i couldn t figure out how     example   given     has latest version       released as a     on github   i d like to import  github com go chi chi    in my project  develop against it and eventually vendor it via  vgo vendor         go  package main    import  github com go chi chi       func main      	    chi newrouter              but since github com go chi chi didn t release a   module yet  i get this error      bash    vgo run main go  vgo  creating new go mod  module github com vojtechvitek vgo test  vgo  resolving import  github com go chi chi     vgo  finding github com go chi chi  latest   vgo  adding github com go chi chi        vgo  import  github com go chi chi       open  users vojtechvitek go src v github com go chi chi          no such file or directory         vgo found version       but couldn t find     subpkg  so i added an explicit version to my go mod file and tried again          cat go mod  module github com vojtechvitek vgo test    require    	github com go chi chi                  running vgo again caused a silent side effect      diff  module github com vojtechvitek vgo test    require      	github com go chi chi          	github com go chi chi                      hmm  seems like vgo doesn t see any      tags  after reading some more blog posts on    since  vgo  cli help didn t seem to be very helpful   novice user friendly   i confirmed with          vgo list  t github com go chi chi  github com go chi chi  	       	              now  i might be missing something  but it s not really clear to me how can i import      or      of a package  should i say module   that i don t have any control over and  is not ready yet      are there any guidelines for package consumers about this  are there any guidelines for package authors  i couldn t find anything useful neither in research swtch com vgo module  nor in the accepted proposal or in the             edit          vgo list  t github com go chi chi    github com go chi chi    	       	       	       	       	       	       	       	       	       	       	       	              ahaa  so i can list      tags  but how do i use them in my monorepo properly            vgo get github com go chi chi    vgo  creating new go mod  module github com vojtechvitek vgo test  vgo  github com go chi chi          missing or invalid go mod  vgo get  missing or invalid go mod     ,1
494168,14246338429.0,IssuesEvent,2020-11-19 09:56:13,wso2/product-apim,https://api.github.com/repos/wso2/product-apim,closed,Cannot Deploy-As-Prototype with Prototype Inline Scripts,Priority/Highest Type/Bug,"### Description:

Gives below error when doing Deploy-As-Prototype for an API which was created by importing a swagger and endpoint type is inline implementation type.

![errorSwaggerProto](https://user-images.githubusercontent.com/1591316/90516077-24a44e80-e181-11ea-88b5-6a6745d01df1.gif)


### Steps to reproduce:

1. Login to Publisher
2. Create an API -> I have an existing API
3. Use an OpenAPI URL/File : https://raw.githubusercontent.com/OAI/OpenAPI-Specification/master/examples/v3.0/petstore.yaml
4. In the API go to Endpoints -> Prototype Implementation
5. Save the inline scripts
6. Publish the API as prototyped.

```
[2020-08-18 18:23:32,312] ERROR - APIExecutor Failed to publish service gateway while executing APIExecutor. 
org.wso2.carbon.apimgt.api.FaultGatewaysException: null
	at org.wso2.carbon.apimgt.impl.APIProviderImpl.updateAPIforStateChange_aroundBody104(APIProviderImpl.java:2244) ~[org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.APIProviderImpl.updateAPIforStateChange(APIProviderImpl.java:2151) ~[org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.UserAwareAPIProvider.updateAPIforStateChange_aroundBody32(UserAwareAPIProvider.java:207) ~[org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.UserAwareAPIProvider.updateAPIforStateChange(UserAwareAPIProvider.java:204) ~[org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.executors.APIExecutor.changeLifeCycle_aroundBody4(APIExecutor.java:200) ~[org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.executors.APIExecutor.changeLifeCycle(APIExecutor.java:158) ~[org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.executors.APIExecutor.execute_aroundBody2(APIExecutor.java:132) [org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.executors.APIExecutor.execute(APIExecutor.java:93) [org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.governance.registry.extensions.aspects.DefaultLifeCycle.runCustomExecutorsCode(DefaultLifeCycle.java:712) [org.wso2.carbon.governance.registry.extensions_4.8.19.jar:?]
	at org.wso2.carbon.governance.registry.extensions.aspects.DefaultLifeCycle.invoke(DefaultLifeCycle.java:450) [org.wso2.carbon.governance.registry.extensions_4.8.19.jar:?]
	at org.wso2.carbon.governance.registry.eventing.handlers.GovernanceEventingHandler.invokeAspect(GovernanceEventingHandler.java:366) [org.wso2.carbon.governance.registry.eventing_4.8.19.jar:?]
	at org.wso2.carbon.registry.core.jdbc.handlers.HandlerManager.invokeAspect(HandlerManager.java:2794) [org.wso2.carbon.registry.core_4.6.0.jar:?]
	at org.wso2.carbon.registry.core.jdbc.handlers.HandlerLifecycleManager.invokeAspect(HandlerLifecycleManager.java:518) [org.wso2.carbon.registry.core_4.6.0.jar:?]
	at org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.invokeAspect(EmbeddedRegistry.java:2607) [org.wso2.carbon.registry.core_4.6.0.jar:?]
	at org.wso2.carbon.registry.core.caching.CacheBackedRegistry.invokeAspect(CacheBackedRegistry.java:510) [org.wso2.carbon.registry.core_4.6.0.jar:?]
	at org.wso2.carbon.registry.core.session.UserRegistry.invokeAspect(UserRegistry.java:1964) [org.wso2.carbon.registry.core_4.6.0.jar:?]
	at org.wso2.carbon.governance.api.common.dataobjects.GovernanceArtifactImpl.invokeAction(GovernanceArtifactImpl.java:829) [org.wso2.carbon.governance.api_4.8.19.jar:?]
	at org.wso2.carbon.governance.api.common.dataobjects.GovernanceArtifactImpl.invokeAction(GovernanceArtifactImpl.java:808) [org.wso2.carbon.governance.api_4.8.19.jar:?]
	at org.wso2.carbon.apimgt.impl.APIProviderImpl.changeLifeCycleStatus_aroundBody270(APIProviderImpl.java:5632) [org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.APIProviderImpl.changeLifeCycleStatus(APIProviderImpl.java:5555) [org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.UserAwareAPIProvider.changeLifeCycleStatus_aroundBody74(UserAwareAPIProvider.java:358) [org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.UserAwareAPIProvider.changeLifeCycleStatus(UserAwareAPIProvider.java:354) [org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.rest.api.publisher.v1.impl.ApisApiServiceImpl.apisChangeLifecyclePost(ApisApiServiceImpl.java:3932) [classes/:?]
	at org.wso2.carbon.apimgt.rest.api.publisher.v1.ApisApi.apisChangeLifecyclePost(ApisApi.java:875) [classes/:?]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_231]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_231]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_231]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_231]
	at org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:179) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:193) [cxf-rt-frontend-jaxrs-3.2.8.jar:3.2.8]
	at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:103) [cxf-rt-frontend-jaxrs-3.2.8.jar:3.2.8]
	at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:96) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:267) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:216) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:301) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:220) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:660) [tomcat-servlet-api_9.0.31.wso2v1.jar:?]
	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:276) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) [tomcat_9.0.31.wso2v1.jar:?]
	at org.wso2.carbon.identity.context.rewrite.valve.TenantContextRewriteValve.invoke(TenantContextRewriteValve.java:86) [org.wso2.carbon.identity.context.rewrite.valve_1.4.0.jar:?]
	at org.wso2.carbon.identity.authz.valve.AuthorizationValve.invoke(AuthorizationValve.java:110) [org.wso2.carbon.identity.authz.valve_1.4.0.jar:?]
	at org.wso2.carbon.identity.auth.valve.AuthenticationValve.invoke(AuthenticationValve.java:75) [org.wso2.carbon.identity.auth.valve_1.4.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:145) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:688) [tomcat_9.0.31.wso2v1.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.RequestCorrelationIdValve.invoke(RequestCorrelationIdValve.java:119) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:367) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1639) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat_9.0.31.wso2v1.jar:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_231]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_231]
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat_9.0.31.wso2v1.jar:?]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_231]
[2020-08-18 18:23:32,314] ERROR - DefaultLifeCycle org.wso2.carbon.registry.core.exceptions.RegistryException: Execution failed for action : Deploy as a Prototype Embedded error : FaultGatewaysException:{""PUBLISHED"":{""Production and Sandbox"":""Error while Deploying API ""},""UNPUBLISHED"":{}}
[2020-08-18 18:23:32,317] ERROR - GovernanceArtifactImpl Invoking lifecycle action ""Deploy as a Prototype"" failed. Execution failed for action : Deploy as a Prototype Embedded error : FaultGatewaysException:{""PUBLISHED"":{""Production and Sandbox"":""Error while Deploying API ""},""UNPUBLISHED"":{}}
org.wso2.carbon.registry.core.exceptions.RegistryException: Execution failed for action : Deploy as a Prototype Embedded error : FaultGatewaysException:{""PUBLISHED"":{""Production and Sandbox"":""Error while Deploying API ""},""UNPUBLISHED"":{}}
	at org.wso2.carbon.governance.registry.extensions.aspects.DefaultLifeCycle.invoke(DefaultLifeCycle.java:482) ~[org.wso2.carbon.governance.registry.extensions_4.8.19.jar:?]
	at org.wso2.carbon.governance.registry.eventing.handlers.GovernanceEventingHandler.invokeAspect(GovernanceEventingHandler.java:366) ~[org.wso2.carbon.governance.registry.eventing_4.8.19.jar:?]
	at org.wso2.carbon.registry.core.jdbc.handlers.HandlerManager.invokeAspect(HandlerManager.java:2794) ~[org.wso2.carbon.registry.core_4.6.0.jar:?]
	at org.wso2.carbon.registry.core.jdbc.handlers.HandlerLifecycleManager.invokeAspect(HandlerLifecycleManager.java:518) ~[org.wso2.carbon.registry.core_4.6.0.jar:?]
	at org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.invokeAspect(EmbeddedRegistry.java:2607) ~[org.wso2.carbon.registry.core_4.6.0.jar:?]
	at org.wso2.carbon.registry.core.caching.CacheBackedRegistry.invokeAspect(CacheBackedRegistry.java:510) ~[org.wso2.carbon.registry.core_4.6.0.jar:?]
	at org.wso2.carbon.registry.core.session.UserRegistry.invokeAspect(UserRegistry.java:1964) ~[org.wso2.carbon.registry.core_4.6.0.jar:?]
	at org.wso2.carbon.governance.api.common.dataobjects.GovernanceArtifactImpl.invokeAction(GovernanceArtifactImpl.java:829) [org.wso2.carbon.governance.api_4.8.19.jar:?]
	at org.wso2.carbon.governance.api.common.dataobjects.GovernanceArtifactImpl.invokeAction(GovernanceArtifactImpl.java:808) [org.wso2.carbon.governance.api_4.8.19.jar:?]
	at org.wso2.carbon.apimgt.impl.APIProviderImpl.changeLifeCycleStatus_aroundBody270(APIProviderImpl.java:5632) [org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.APIProviderImpl.changeLifeCycleStatus(APIProviderImpl.java:5555) [org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.UserAwareAPIProvider.changeLifeCycleStatus_aroundBody74(UserAwareAPIProvider.java:358) [org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.UserAwareAPIProvider.changeLifeCycleStatus(UserAwareAPIProvider.java:354) [org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.rest.api.publisher.v1.impl.ApisApiServiceImpl.apisChangeLifecyclePost(ApisApiServiceImpl.java:3932) [classes/:?]
	at org.wso2.carbon.apimgt.rest.api.publisher.v1.ApisApi.apisChangeLifecyclePost(ApisApi.java:875) [classes/:?]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_231]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_231]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_231]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_231]
	at org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:179) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:193) [cxf-rt-frontend-jaxrs-3.2.8.jar:3.2.8]
	at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:103) [cxf-rt-frontend-jaxrs-3.2.8.jar:3.2.8]
	at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:96) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:267) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:216) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:301) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:220) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:660) [tomcat-servlet-api_9.0.31.wso2v1.jar:?]
	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:276) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) [tomcat_9.0.31.wso2v1.jar:?]
	at org.wso2.carbon.identity.context.rewrite.valve.TenantContextRewriteValve.invoke(TenantContextRewriteValve.java:86) [org.wso2.carbon.identity.context.rewrite.valve_1.4.0.jar:?]
	at org.wso2.carbon.identity.authz.valve.AuthorizationValve.invoke(AuthorizationValve.java:110) [org.wso2.carbon.identity.authz.valve_1.4.0.jar:?]
	at org.wso2.carbon.identity.auth.valve.AuthenticationValve.invoke(AuthenticationValve.java:75) [org.wso2.carbon.identity.auth.valve_1.4.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:145) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:688) [tomcat_9.0.31.wso2v1.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.RequestCorrelationIdValve.invoke(RequestCorrelationIdValve.java:119) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:367) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1639) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat_9.0.31.wso2v1.jar:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_231]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_231]
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat_9.0.31.wso2v1.jar:?]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_231]
[2020-08-18 18:23:32,319] ERROR - ApisApiServiceImpl Error while updating the API in Gateway e95420d4-c22d-475f-a6e0-3443c2c9f784
org.wso2.carbon.apimgt.api.FaultGatewaysException: null
	at org.wso2.carbon.apimgt.impl.APIProviderImpl.changeLifeCycleStatus_aroundBody270(APIProviderImpl.java:5712) ~[org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.APIProviderImpl.changeLifeCycleStatus(APIProviderImpl.java:5555) ~[org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.UserAwareAPIProvider.changeLifeCycleStatus_aroundBody74(UserAwareAPIProvider.java:358) ~[org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.UserAwareAPIProvider.changeLifeCycleStatus(UserAwareAPIProvider.java:354) ~[org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.rest.api.publisher.v1.impl.ApisApiServiceImpl.apisChangeLifecyclePost(ApisApiServiceImpl.java:3932) [classes/:?]
	at org.wso2.carbon.apimgt.rest.api.publisher.v1.ApisApi.apisChangeLifecyclePost(ApisApi.java:875) [classes/:?]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_231]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_231]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_231]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_231]
	at org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:179) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:193) [cxf-rt-frontend-jaxrs-3.2.8.jar:3.2.8]
	at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:103) [cxf-rt-frontend-jaxrs-3.2.8.jar:3.2.8]
	at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:96) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:267) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:216) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:301) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:220) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:660) [tomcat-servlet-api_9.0.31.wso2v1.jar:?]
	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:276) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) [tomcat_9.0.31.wso2v1.jar:?]
	at org.wso2.carbon.identity.context.rewrite.valve.TenantContextRewriteValve.invoke(TenantContextRewriteValve.java:86) [org.wso2.carbon.identity.context.rewrite.valve_1.4.0.jar:?]
	at org.wso2.carbon.identity.authz.valve.AuthorizationValve.invoke(AuthorizationValve.java:110) [org.wso2.carbon.identity.authz.valve_1.4.0.jar:?]
	at org.wso2.carbon.identity.auth.valve.AuthenticationValve.invoke(AuthenticationValve.java:75) [org.wso2.carbon.identity.auth.valve_1.4.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:145) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:688) [tomcat_9.0.31.wso2v1.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.RequestCorrelationIdValve.invoke(RequestCorrelationIdValve.java:119) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:367) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1639) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat_9.0.31.wso2v1.jar:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_231]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_231]
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat_9.0.31.wso2v1.jar:?]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_231]

```

### Affected Product Version:
<!-- Members can use Affected/*** labels -->

### Environment details (with versions):
- OS:
- Client:
- Env (Docker/K8s):

---
### Optional Fields
#### Related Issues:
<!-- Any related issues from this/other repositories-->

#### Suggested Labels:
<!--Only to be used by non-members-->

#### Suggested Assignees:
<!--Only to be used by non-members-->",1.0,"Cannot Deploy-As-Prototype with Prototype Inline Scripts - ### Description:

Gives below error when doing Deploy-As-Prototype for an API which was created by importing a swagger and endpoint type is inline implementation type.

![errorSwaggerProto](https://user-images.githubusercontent.com/1591316/90516077-24a44e80-e181-11ea-88b5-6a6745d01df1.gif)


### Steps to reproduce:

1. Login to Publisher
2. Create an API -> I have an existing API
3. Use an OpenAPI URL/File : https://raw.githubusercontent.com/OAI/OpenAPI-Specification/master/examples/v3.0/petstore.yaml
4. In the API go to Endpoints -> Prototype Implementation
5. Save the inline scripts
6. Publish the API as prototyped.

```
[2020-08-18 18:23:32,312] ERROR - APIExecutor Failed to publish service gateway while executing APIExecutor. 
org.wso2.carbon.apimgt.api.FaultGatewaysException: null
	at org.wso2.carbon.apimgt.impl.APIProviderImpl.updateAPIforStateChange_aroundBody104(APIProviderImpl.java:2244) ~[org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.APIProviderImpl.updateAPIforStateChange(APIProviderImpl.java:2151) ~[org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.UserAwareAPIProvider.updateAPIforStateChange_aroundBody32(UserAwareAPIProvider.java:207) ~[org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.UserAwareAPIProvider.updateAPIforStateChange(UserAwareAPIProvider.java:204) ~[org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.executors.APIExecutor.changeLifeCycle_aroundBody4(APIExecutor.java:200) ~[org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.executors.APIExecutor.changeLifeCycle(APIExecutor.java:158) ~[org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.executors.APIExecutor.execute_aroundBody2(APIExecutor.java:132) [org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.executors.APIExecutor.execute(APIExecutor.java:93) [org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.governance.registry.extensions.aspects.DefaultLifeCycle.runCustomExecutorsCode(DefaultLifeCycle.java:712) [org.wso2.carbon.governance.registry.extensions_4.8.19.jar:?]
	at org.wso2.carbon.governance.registry.extensions.aspects.DefaultLifeCycle.invoke(DefaultLifeCycle.java:450) [org.wso2.carbon.governance.registry.extensions_4.8.19.jar:?]
	at org.wso2.carbon.governance.registry.eventing.handlers.GovernanceEventingHandler.invokeAspect(GovernanceEventingHandler.java:366) [org.wso2.carbon.governance.registry.eventing_4.8.19.jar:?]
	at org.wso2.carbon.registry.core.jdbc.handlers.HandlerManager.invokeAspect(HandlerManager.java:2794) [org.wso2.carbon.registry.core_4.6.0.jar:?]
	at org.wso2.carbon.registry.core.jdbc.handlers.HandlerLifecycleManager.invokeAspect(HandlerLifecycleManager.java:518) [org.wso2.carbon.registry.core_4.6.0.jar:?]
	at org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.invokeAspect(EmbeddedRegistry.java:2607) [org.wso2.carbon.registry.core_4.6.0.jar:?]
	at org.wso2.carbon.registry.core.caching.CacheBackedRegistry.invokeAspect(CacheBackedRegistry.java:510) [org.wso2.carbon.registry.core_4.6.0.jar:?]
	at org.wso2.carbon.registry.core.session.UserRegistry.invokeAspect(UserRegistry.java:1964) [org.wso2.carbon.registry.core_4.6.0.jar:?]
	at org.wso2.carbon.governance.api.common.dataobjects.GovernanceArtifactImpl.invokeAction(GovernanceArtifactImpl.java:829) [org.wso2.carbon.governance.api_4.8.19.jar:?]
	at org.wso2.carbon.governance.api.common.dataobjects.GovernanceArtifactImpl.invokeAction(GovernanceArtifactImpl.java:808) [org.wso2.carbon.governance.api_4.8.19.jar:?]
	at org.wso2.carbon.apimgt.impl.APIProviderImpl.changeLifeCycleStatus_aroundBody270(APIProviderImpl.java:5632) [org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.APIProviderImpl.changeLifeCycleStatus(APIProviderImpl.java:5555) [org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.UserAwareAPIProvider.changeLifeCycleStatus_aroundBody74(UserAwareAPIProvider.java:358) [org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.UserAwareAPIProvider.changeLifeCycleStatus(UserAwareAPIProvider.java:354) [org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.rest.api.publisher.v1.impl.ApisApiServiceImpl.apisChangeLifecyclePost(ApisApiServiceImpl.java:3932) [classes/:?]
	at org.wso2.carbon.apimgt.rest.api.publisher.v1.ApisApi.apisChangeLifecyclePost(ApisApi.java:875) [classes/:?]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_231]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_231]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_231]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_231]
	at org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:179) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:193) [cxf-rt-frontend-jaxrs-3.2.8.jar:3.2.8]
	at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:103) [cxf-rt-frontend-jaxrs-3.2.8.jar:3.2.8]
	at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:96) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:267) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:216) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:301) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:220) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:660) [tomcat-servlet-api_9.0.31.wso2v1.jar:?]
	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:276) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) [tomcat_9.0.31.wso2v1.jar:?]
	at org.wso2.carbon.identity.context.rewrite.valve.TenantContextRewriteValve.invoke(TenantContextRewriteValve.java:86) [org.wso2.carbon.identity.context.rewrite.valve_1.4.0.jar:?]
	at org.wso2.carbon.identity.authz.valve.AuthorizationValve.invoke(AuthorizationValve.java:110) [org.wso2.carbon.identity.authz.valve_1.4.0.jar:?]
	at org.wso2.carbon.identity.auth.valve.AuthenticationValve.invoke(AuthenticationValve.java:75) [org.wso2.carbon.identity.auth.valve_1.4.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:145) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:688) [tomcat_9.0.31.wso2v1.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.RequestCorrelationIdValve.invoke(RequestCorrelationIdValve.java:119) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:367) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1639) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat_9.0.31.wso2v1.jar:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_231]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_231]
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat_9.0.31.wso2v1.jar:?]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_231]
[2020-08-18 18:23:32,314] ERROR - DefaultLifeCycle org.wso2.carbon.registry.core.exceptions.RegistryException: Execution failed for action : Deploy as a Prototype Embedded error : FaultGatewaysException:{""PUBLISHED"":{""Production and Sandbox"":""Error while Deploying API ""},""UNPUBLISHED"":{}}
[2020-08-18 18:23:32,317] ERROR - GovernanceArtifactImpl Invoking lifecycle action ""Deploy as a Prototype"" failed. Execution failed for action : Deploy as a Prototype Embedded error : FaultGatewaysException:{""PUBLISHED"":{""Production and Sandbox"":""Error while Deploying API ""},""UNPUBLISHED"":{}}
org.wso2.carbon.registry.core.exceptions.RegistryException: Execution failed for action : Deploy as a Prototype Embedded error : FaultGatewaysException:{""PUBLISHED"":{""Production and Sandbox"":""Error while Deploying API ""},""UNPUBLISHED"":{}}
	at org.wso2.carbon.governance.registry.extensions.aspects.DefaultLifeCycle.invoke(DefaultLifeCycle.java:482) ~[org.wso2.carbon.governance.registry.extensions_4.8.19.jar:?]
	at org.wso2.carbon.governance.registry.eventing.handlers.GovernanceEventingHandler.invokeAspect(GovernanceEventingHandler.java:366) ~[org.wso2.carbon.governance.registry.eventing_4.8.19.jar:?]
	at org.wso2.carbon.registry.core.jdbc.handlers.HandlerManager.invokeAspect(HandlerManager.java:2794) ~[org.wso2.carbon.registry.core_4.6.0.jar:?]
	at org.wso2.carbon.registry.core.jdbc.handlers.HandlerLifecycleManager.invokeAspect(HandlerLifecycleManager.java:518) ~[org.wso2.carbon.registry.core_4.6.0.jar:?]
	at org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.invokeAspect(EmbeddedRegistry.java:2607) ~[org.wso2.carbon.registry.core_4.6.0.jar:?]
	at org.wso2.carbon.registry.core.caching.CacheBackedRegistry.invokeAspect(CacheBackedRegistry.java:510) ~[org.wso2.carbon.registry.core_4.6.0.jar:?]
	at org.wso2.carbon.registry.core.session.UserRegistry.invokeAspect(UserRegistry.java:1964) ~[org.wso2.carbon.registry.core_4.6.0.jar:?]
	at org.wso2.carbon.governance.api.common.dataobjects.GovernanceArtifactImpl.invokeAction(GovernanceArtifactImpl.java:829) [org.wso2.carbon.governance.api_4.8.19.jar:?]
	at org.wso2.carbon.governance.api.common.dataobjects.GovernanceArtifactImpl.invokeAction(GovernanceArtifactImpl.java:808) [org.wso2.carbon.governance.api_4.8.19.jar:?]
	at org.wso2.carbon.apimgt.impl.APIProviderImpl.changeLifeCycleStatus_aroundBody270(APIProviderImpl.java:5632) [org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.APIProviderImpl.changeLifeCycleStatus(APIProviderImpl.java:5555) [org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.UserAwareAPIProvider.changeLifeCycleStatus_aroundBody74(UserAwareAPIProvider.java:358) [org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.UserAwareAPIProvider.changeLifeCycleStatus(UserAwareAPIProvider.java:354) [org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.rest.api.publisher.v1.impl.ApisApiServiceImpl.apisChangeLifecyclePost(ApisApiServiceImpl.java:3932) [classes/:?]
	at org.wso2.carbon.apimgt.rest.api.publisher.v1.ApisApi.apisChangeLifecyclePost(ApisApi.java:875) [classes/:?]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_231]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_231]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_231]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_231]
	at org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:179) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:193) [cxf-rt-frontend-jaxrs-3.2.8.jar:3.2.8]
	at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:103) [cxf-rt-frontend-jaxrs-3.2.8.jar:3.2.8]
	at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:96) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:267) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:216) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:301) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:220) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:660) [tomcat-servlet-api_9.0.31.wso2v1.jar:?]
	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:276) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) [tomcat_9.0.31.wso2v1.jar:?]
	at org.wso2.carbon.identity.context.rewrite.valve.TenantContextRewriteValve.invoke(TenantContextRewriteValve.java:86) [org.wso2.carbon.identity.context.rewrite.valve_1.4.0.jar:?]
	at org.wso2.carbon.identity.authz.valve.AuthorizationValve.invoke(AuthorizationValve.java:110) [org.wso2.carbon.identity.authz.valve_1.4.0.jar:?]
	at org.wso2.carbon.identity.auth.valve.AuthenticationValve.invoke(AuthenticationValve.java:75) [org.wso2.carbon.identity.auth.valve_1.4.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:145) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:688) [tomcat_9.0.31.wso2v1.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.RequestCorrelationIdValve.invoke(RequestCorrelationIdValve.java:119) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:367) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1639) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat_9.0.31.wso2v1.jar:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_231]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_231]
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat_9.0.31.wso2v1.jar:?]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_231]
[2020-08-18 18:23:32,319] ERROR - ApisApiServiceImpl Error while updating the API in Gateway e95420d4-c22d-475f-a6e0-3443c2c9f784
org.wso2.carbon.apimgt.api.FaultGatewaysException: null
	at org.wso2.carbon.apimgt.impl.APIProviderImpl.changeLifeCycleStatus_aroundBody270(APIProviderImpl.java:5712) ~[org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.APIProviderImpl.changeLifeCycleStatus(APIProviderImpl.java:5555) ~[org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.UserAwareAPIProvider.changeLifeCycleStatus_aroundBody74(UserAwareAPIProvider.java:358) ~[org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.impl.UserAwareAPIProvider.changeLifeCycleStatus(UserAwareAPIProvider.java:354) ~[org.wso2.carbon.apimgt.impl_6.7.192.jar:?]
	at org.wso2.carbon.apimgt.rest.api.publisher.v1.impl.ApisApiServiceImpl.apisChangeLifecyclePost(ApisApiServiceImpl.java:3932) [classes/:?]
	at org.wso2.carbon.apimgt.rest.api.publisher.v1.ApisApi.apisChangeLifecyclePost(ApisApi.java:875) [classes/:?]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_231]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_231]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_231]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_231]
	at org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:179) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:193) [cxf-rt-frontend-jaxrs-3.2.8.jar:3.2.8]
	at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:103) [cxf-rt-frontend-jaxrs-3.2.8.jar:3.2.8]
	at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:96) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) [cxf-core-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:267) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:216) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:301) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:220) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:660) [tomcat-servlet-api_9.0.31.wso2v1.jar:?]
	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:276) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) [tomcat_9.0.31.wso2v1.jar:?]
	at org.wso2.carbon.identity.context.rewrite.valve.TenantContextRewriteValve.invoke(TenantContextRewriteValve.java:86) [org.wso2.carbon.identity.context.rewrite.valve_1.4.0.jar:?]
	at org.wso2.carbon.identity.authz.valve.AuthorizationValve.invoke(AuthorizationValve.java:110) [org.wso2.carbon.identity.authz.valve_1.4.0.jar:?]
	at org.wso2.carbon.identity.auth.valve.AuthenticationValve.invoke(AuthenticationValve.java:75) [org.wso2.carbon.identity.auth.valve_1.4.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:145) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:688) [tomcat_9.0.31.wso2v1.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.wso2.carbon.tomcat.ext.valves.RequestCorrelationIdValve.invoke(RequestCorrelationIdValve.java:119) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:367) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1639) [tomcat_9.0.31.wso2v1.jar:?]
	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat_9.0.31.wso2v1.jar:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_231]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_231]
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat_9.0.31.wso2v1.jar:?]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_231]

```

### Affected Product Version:
<!-- Members can use Affected/*** labels -->

### Environment details (with versions):
- OS:
- Client:
- Env (Docker/K8s):

---
### Optional Fields
#### Related Issues:
<!-- Any related issues from this/other repositories-->

#### Suggested Labels:
<!--Only to be used by non-members-->

#### Suggested Assignees:
<!--Only to be used by non-members-->",0,cannot deploy as prototype with prototype inline scripts       description     gives below error when doing deploy as prototype for an api which was created by importing a swagger and endpoint type is inline implementation type                   steps to reproduce        login to publisher     create an api    i have an existing api     use an openapi url file         in the api go to endpoints    prototype implementation     save the inline scripts     publish the api as prototyped            error   apiexecutor failed to publish service gateway while executing apiexecutor    org   carbon apimgt api faultgatewaysexception  null  	at org   carbon apimgt impl apiproviderimpl updateapiforstatechange   apiproviderimpl java        	at org   carbon apimgt impl apiproviderimpl updateapiforstatechange apiproviderimpl java        	at org   carbon apimgt impl userawareapiprovider updateapiforstatechange   userawareapiprovider java        	at org   carbon apimgt impl userawareapiprovider updateapiforstatechange userawareapiprovider java        	at org   carbon apimgt impl executors apiexecutor changelifecycle   apiexecutor java        	at org   carbon apimgt impl executors apiexecutor changelifecycle apiexecutor java        	at org   carbon apimgt impl executors apiexecutor execute   apiexecutor java       	at org   carbon apimgt impl executors apiexecutor execute apiexecutor java       	at org   carbon governance registry extensions aspects defaultlifecycle runcustomexecutorscode defaultlifecycle java       	at org   carbon governance registry extensions aspects defaultlifecycle invoke defaultlifecycle java       	at org   carbon governance registry eventing handlers governanceeventinghandler invokeaspect governanceeventinghandler java       	at org   carbon registry core jdbc handlers handlermanager invokeaspect handlermanager java       	at org   carbon registry core jdbc handlers handlerlifecyclemanager invokeaspect handlerlifecyclemanager java       	at org   carbon registry core jdbc embeddedregistry invokeaspect embeddedregistry java       	at org   carbon registry core caching cachebackedregistry invokeaspect cachebackedregistry java       	at org   carbon registry core session userregistry invokeaspect userregistry java       	at org   carbon governance api common dataobjects governanceartifactimpl invokeaction governanceartifactimpl java       	at org   carbon governance api common dataobjects governanceartifactimpl invokeaction governanceartifactimpl java       	at org   carbon apimgt impl apiproviderimpl changelifecyclestatus   apiproviderimpl java       	at org   carbon apimgt impl apiproviderimpl changelifecyclestatus apiproviderimpl java       	at org   carbon apimgt impl userawareapiprovider changelifecyclestatus   userawareapiprovider java       	at org   carbon apimgt impl userawareapiprovider changelifecyclestatus userawareapiprovider java       	at org   carbon apimgt rest api publisher   impl apisapiserviceimpl apischangelifecyclepost apisapiserviceimpl java       	at org   carbon apimgt rest api publisher   apisapi apischangelifecyclepost apisapi java       	at sun reflect nativemethodaccessorimpl   native method      	at sun reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java        	at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java        	at java lang reflect method invoke method java        	at org apache cxf service invoker abstractinvoker performinvocation abstractinvoker java       	at org apache cxf service invoker abstractinvoker invoke abstractinvoker java       	at org apache cxf jaxrs jaxrsinvoker invoke jaxrsinvoker java       	at org apache cxf jaxrs jaxrsinvoker invoke jaxrsinvoker java       	at org apache cxf interceptor serviceinvokerinterceptor   run serviceinvokerinterceptor java       	at org apache cxf interceptor serviceinvokerinterceptor handlemessage serviceinvokerinterceptor java       	at org apache cxf phase phaseinterceptorchain dointercept phaseinterceptorchain java       	at org apache cxf transport chaininitiationobserver onmessage chaininitiationobserver java       	at org apache cxf transport http abstracthttpdestination invoke abstracthttpdestination java       	at org apache cxf transport servlet servletcontroller invokedestination servletcontroller java       	at org apache cxf transport servlet servletcontroller invoke servletcontroller java       	at org apache cxf transport servlet servletcontroller invoke servletcontroller java       	at org apache cxf transport servlet cxfnonspringservlet invoke cxfnonspringservlet java       	at org apache cxf transport servlet abstracthttpservlet handlerequest abstracthttpservlet java       	at org apache cxf transport servlet abstracthttpservlet dopost abstracthttpservlet java       	at javax servlet http httpservlet service httpservlet java       	at org apache cxf transport servlet abstracthttpservlet service abstracthttpservlet java       	at org apache catalina core applicationfilterchain internaldofilter applicationfilterchain java       	at org apache catalina core applicationfilterchain dofilter applicationfilterchain java       	at org apache tomcat websocket server wsfilter dofilter wsfilter java       	at org apache catalina core applicationfilterchain internaldofilter applicationfilterchain java       	at org apache catalina core applicationfilterchain dofilter applicationfilterchain java       	at org apache catalina core standardwrappervalve invoke standardwrappervalve java       	at org apache catalina core standardcontextvalve invoke standardcontextvalve java       	at org apache catalina authenticator authenticatorbase invoke authenticatorbase java       	at org apache catalina core standardhostvalve invoke standardhostvalve java       	at org apache catalina valves errorreportvalve invoke errorreportvalve java       	at org   carbon identity context rewrite valve tenantcontextrewritevalve invoke tenantcontextrewritevalve java       	at org   carbon identity authz valve authorizationvalve invoke authorizationvalve java       	at org   carbon identity auth valve authenticationvalve invoke authenticationvalve java       	at org   carbon tomcat ext valves compositevalve continueinvocation compositevalve java       	at org   carbon tomcat ext valves tomcatvalvecontainer invokevalves tomcatvalvecontainer java       	at org   carbon tomcat ext valves compositevalve invoke compositevalve java       	at org   carbon tomcat ext valves carbonstuckthreaddetectionvalve invoke carbonstuckthreaddetectionvalve java       	at org apache catalina valves abstractaccesslogvalve invoke abstractaccesslogvalve java       	at org   carbon tomcat ext valves carboncontextcreatorvalve invoke carboncontextcreatorvalve java       	at org   carbon tomcat ext valves requestcorrelationidvalve invoke requestcorrelationidvalve java       	at org apache catalina core standardenginevalve invoke standardenginevalve java       	at org apache catalina connector coyoteadapter service coyoteadapter java       	at org apache coyote     service   java       	at org apache coyote abstractprocessorlight process abstractprocessorlight java       	at org apache coyote abstractprotocol connectionhandler process abstractprotocol java       	at org apache tomcat util net nioendpoint socketprocessor dorun nioendpoint java       	at org apache tomcat util net socketprocessorbase run socketprocessorbase java       	at java util concurrent threadpoolexecutor runworker threadpoolexecutor java       	at java util concurrent threadpoolexecutor worker run threadpoolexecutor java       	at org apache tomcat util threads taskthread wrappingrunnable run taskthread java       	at java lang thread run thread java         error   defaultlifecycle org   carbon registry core exceptions registryexception  execution failed for action   deploy as a prototype embedded error   faultgatewaysexception   published    production and sandbox   error while deploying api     unpublished         error   governanceartifactimpl invoking lifecycle action  deploy as a prototype  failed  execution failed for action   deploy as a prototype embedded error   faultgatewaysexception   published    production and sandbox   error while deploying api     unpublished       org   carbon registry core exceptions registryexception  execution failed for action   deploy as a prototype embedded error   faultgatewaysexception   published    production and sandbox   error while deploying api     unpublished       	at org   carbon governance registry extensions aspects defaultlifecycle invoke defaultlifecycle java        	at org   carbon governance registry eventing handlers governanceeventinghandler invokeaspect governanceeventinghandler java        	at org   carbon registry core jdbc handlers handlermanager invokeaspect handlermanager java        	at org   carbon registry core jdbc handlers handlerlifecyclemanager invokeaspect handlerlifecyclemanager java        	at org   carbon registry core jdbc embeddedregistry invokeaspect embeddedregistry java        	at org   carbon registry core caching cachebackedregistry invokeaspect cachebackedregistry java        	at org   carbon registry core session userregistry invokeaspect userregistry java        	at org   carbon governance api common dataobjects governanceartifactimpl invokeaction governanceartifactimpl java       	at org   carbon governance api common dataobjects governanceartifactimpl invokeaction governanceartifactimpl java       	at org   carbon apimgt impl apiproviderimpl changelifecyclestatus   apiproviderimpl java       	at org   carbon apimgt impl apiproviderimpl changelifecyclestatus apiproviderimpl java       	at org   carbon apimgt impl userawareapiprovider changelifecyclestatus   userawareapiprovider java       	at org   carbon apimgt impl userawareapiprovider changelifecyclestatus userawareapiprovider java       	at org   carbon apimgt rest api publisher   impl apisapiserviceimpl apischangelifecyclepost apisapiserviceimpl java       	at org   carbon apimgt rest api publisher   apisapi apischangelifecyclepost apisapi java       	at sun reflect nativemethodaccessorimpl   native method      	at sun reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java        	at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java        	at java lang reflect method invoke method java        	at org apache cxf service invoker abstractinvoker performinvocation abstractinvoker java       	at org apache cxf service invoker abstractinvoker invoke abstractinvoker java       	at org apache cxf jaxrs jaxrsinvoker invoke jaxrsinvoker java       	at org apache cxf jaxrs jaxrsinvoker invoke jaxrsinvoker java       	at org apache cxf interceptor serviceinvokerinterceptor   run serviceinvokerinterceptor java       	at org apache cxf interceptor serviceinvokerinterceptor handlemessage serviceinvokerinterceptor java       	at org apache cxf phase phaseinterceptorchain dointercept phaseinterceptorchain java       	at org apache cxf transport chaininitiationobserver onmessage chaininitiationobserver java       	at org apache cxf transport http abstracthttpdestination invoke abstracthttpdestination java       	at org apache cxf transport servlet servletcontroller invokedestination servletcontroller java       	at org apache cxf transport servlet servletcontroller invoke servletcontroller java       	at org apache cxf transport servlet servletcontroller invoke servletcontroller java       	at org apache cxf transport servlet cxfnonspringservlet invoke cxfnonspringservlet java       	at org apache cxf transport servlet abstracthttpservlet handlerequest abstracthttpservlet java       	at org apache cxf transport servlet abstracthttpservlet dopost abstracthttpservlet java       	at javax servlet http httpservlet service httpservlet java       	at org apache cxf transport servlet abstracthttpservlet service abstracthttpservlet java       	at org apache catalina core applicationfilterchain internaldofilter applicationfilterchain java       	at org apache catalina core applicationfilterchain dofilter applicationfilterchain java       	at org apache tomcat websocket server wsfilter dofilter wsfilter java       	at org apache catalina core applicationfilterchain internaldofilter applicationfilterchain java       	at org apache catalina core applicationfilterchain dofilter applicationfilterchain java       	at org apache catalina core standardwrappervalve invoke standardwrappervalve java       	at org apache catalina core standardcontextvalve invoke standardcontextvalve java       	at org apache catalina authenticator authenticatorbase invoke authenticatorbase java       	at org apache catalina core standardhostvalve invoke standardhostvalve java       	at org apache catalina valves errorreportvalve invoke errorreportvalve java       	at org   carbon identity context rewrite valve tenantcontextrewritevalve invoke tenantcontextrewritevalve java       	at org   carbon identity authz valve authorizationvalve invoke authorizationvalve java       	at org   carbon identity auth valve authenticationvalve invoke authenticationvalve java       	at org   carbon tomcat ext valves compositevalve continueinvocation compositevalve java       	at org   carbon tomcat ext valves tomcatvalvecontainer invokevalves tomcatvalvecontainer java       	at org   carbon tomcat ext valves compositevalve invoke compositevalve java       	at org   carbon tomcat ext valves carbonstuckthreaddetectionvalve invoke carbonstuckthreaddetectionvalve java       	at org apache catalina valves abstractaccesslogvalve invoke abstractaccesslogvalve java       	at org   carbon tomcat ext valves carboncontextcreatorvalve invoke carboncontextcreatorvalve java       	at org   carbon tomcat ext valves requestcorrelationidvalve invoke requestcorrelationidvalve java       	at org apache catalina core standardenginevalve invoke standardenginevalve java       	at org apache catalina connector coyoteadapter service coyoteadapter java       	at org apache coyote     service   java       	at org apache coyote abstractprocessorlight process abstractprocessorlight java       	at org apache coyote abstractprotocol connectionhandler process abstractprotocol java       	at org apache tomcat util net nioendpoint socketprocessor dorun nioendpoint java       	at org apache tomcat util net socketprocessorbase run socketprocessorbase java       	at java util concurrent threadpoolexecutor runworker threadpoolexecutor java       	at java util concurrent threadpoolexecutor worker run threadpoolexecutor java       	at org apache tomcat util threads taskthread wrappingrunnable run taskthread java       	at java lang thread run thread java         error   apisapiserviceimpl error while updating the api in gateway            org   carbon apimgt api faultgatewaysexception  null  	at org   carbon apimgt impl apiproviderimpl changelifecyclestatus   apiproviderimpl java        	at org   carbon apimgt impl apiproviderimpl changelifecyclestatus apiproviderimpl java        	at org   carbon apimgt impl userawareapiprovider changelifecyclestatus   userawareapiprovider java        	at org   carbon apimgt impl userawareapiprovider changelifecyclestatus userawareapiprovider java        	at org   carbon apimgt rest api publisher   impl apisapiserviceimpl apischangelifecyclepost apisapiserviceimpl java       	at org   carbon apimgt rest api publisher   apisapi apischangelifecyclepost apisapi java       	at sun reflect nativemethodaccessorimpl   native method      	at sun reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java        	at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java        	at java lang reflect method invoke method java        	at org apache cxf service invoker abstractinvoker performinvocation abstractinvoker java       	at org apache cxf service invoker abstractinvoker invoke abstractinvoker java       	at org apache cxf jaxrs jaxrsinvoker invoke jaxrsinvoker java       	at org apache cxf jaxrs jaxrsinvoker invoke jaxrsinvoker java       	at org apache cxf interceptor serviceinvokerinterceptor   run serviceinvokerinterceptor java       	at org apache cxf interceptor serviceinvokerinterceptor handlemessage serviceinvokerinterceptor java       	at org apache cxf phase phaseinterceptorchain dointercept phaseinterceptorchain java       	at org apache cxf transport chaininitiationobserver onmessage chaininitiationobserver java       	at org apache cxf transport http abstracthttpdestination invoke abstracthttpdestination java       	at org apache cxf transport servlet servletcontroller invokedestination servletcontroller java       	at org apache cxf transport servlet servletcontroller invoke servletcontroller java       	at org apache cxf transport servlet servletcontroller invoke servletcontroller java       	at org apache cxf transport servlet cxfnonspringservlet invoke cxfnonspringservlet java       	at org apache cxf transport servlet abstracthttpservlet handlerequest abstracthttpservlet java       	at org apache cxf transport servlet abstracthttpservlet dopost abstracthttpservlet java       	at javax servlet http httpservlet service httpservlet java       	at org apache cxf transport servlet abstracthttpservlet service abstracthttpservlet java       	at org apache catalina core applicationfilterchain internaldofilter applicationfilterchain java       	at org apache catalina core applicationfilterchain dofilter applicationfilterchain java       	at org apache tomcat websocket server wsfilter dofilter wsfilter java       	at org apache catalina core applicationfilterchain internaldofilter applicationfilterchain java       	at org apache catalina core applicationfilterchain dofilter applicationfilterchain java       	at org apache catalina core standardwrappervalve invoke standardwrappervalve java       	at org apache catalina core standardcontextvalve invoke standardcontextvalve java       	at org apache catalina authenticator authenticatorbase invoke authenticatorbase java       	at org apache catalina core standardhostvalve invoke standardhostvalve java       	at org apache catalina valves errorreportvalve invoke errorreportvalve java       	at org   carbon identity context rewrite valve tenantcontextrewritevalve invoke tenantcontextrewritevalve java       	at org   carbon identity authz valve authorizationvalve invoke authorizationvalve java       	at org   carbon identity auth valve authenticationvalve invoke authenticationvalve java       	at org   carbon tomcat ext valves compositevalve continueinvocation compositevalve java       	at org   carbon tomcat ext valves tomcatvalvecontainer invokevalves tomcatvalvecontainer java       	at org   carbon tomcat ext valves compositevalve invoke compositevalve java       	at org   carbon tomcat ext valves carbonstuckthreaddetectionvalve invoke carbonstuckthreaddetectionvalve java       	at org apache catalina valves abstractaccesslogvalve invoke abstractaccesslogvalve java       	at org   carbon tomcat ext valves carboncontextcreatorvalve invoke carboncontextcreatorvalve java       	at org   carbon tomcat ext valves requestcorrelationidvalve invoke requestcorrelationidvalve java       	at org apache catalina core standardenginevalve invoke standardenginevalve java       	at org apache catalina connector coyoteadapter service coyoteadapter java       	at org apache coyote     service   java       	at org apache coyote abstractprocessorlight process abstractprocessorlight java       	at org apache coyote abstractprotocol connectionhandler process abstractprotocol java       	at org apache tomcat util net nioendpoint socketprocessor dorun nioendpoint java       	at org apache tomcat util net socketprocessorbase run socketprocessorbase java       	at java util concurrent threadpoolexecutor runworker threadpoolexecutor java       	at java util concurrent threadpoolexecutor worker run threadpoolexecutor java       	at org apache tomcat util threads taskthread wrappingrunnable run taskthread java       	at java lang thread run thread java                    affected product version            environment details  with versions      os     client     env  docker                 optional fields       related issues             suggested labels             suggested assignees    ,0
52069,7746121957.0,IssuesEvent,2018-05-29 20:36:54,golang/go,https://api.github.com/repos/golang/go,closed,net/http: Closing Hijacked Conn doesn't cancel Request Context,Documentation NeedsFix,"After a server Handler Hijacks and returns the underlying net.Conn, I'd expect the Handler's Request.Context to be Done when that Conn is closed. It appears that the Context is Done when the original handler routine returns, but closing the Conn after a Hijack no longer triggers it too.

Here's a test demonstrating it. It gets stuck at the linked line. https://github.com/anacrolix/wat/blob/master/http_test.go#L63

$ go version
go version devel +2da8a16cbc Thu Oct 19 23:34:02 2017 +0000 darwin/amd64",1.0,"net/http: Closing Hijacked Conn doesn't cancel Request Context - After a server Handler Hijacks and returns the underlying net.Conn, I'd expect the Handler's Request.Context to be Done when that Conn is closed. It appears that the Context is Done when the original handler routine returns, but closing the Conn after a Hijack no longer triggers it too.

Here's a test demonstrating it. It gets stuck at the linked line. https://github.com/anacrolix/wat/blob/master/http_test.go#L63

$ go version
go version devel +2da8a16cbc Thu Oct 19 23:34:02 2017 +0000 darwin/amd64",1,net http  closing hijacked conn doesn t cancel request context   after a server handler hijacks and returns the underlying net conn  i d expect the handler s request context to be done when that conn is closed  it appears that the context is done when the original handler routine returns  but closing the conn after a hijack no longer triggers it too     here s a test demonstrating it  it gets stuck at the linked line         go version  go version devel    thu oct              darwin  ,1
42499,6986349488.0,IssuesEvent,2017-12-14 02:52:54,golang/go,https://api.github.com/repos/golang/go,closed,testing: t.Fatal does not fatal tests if defers do not complete,Documentation,"### What version of Go are you using (`go version`)?
`go version go1.9.2 darwin/amd64`

### Does this issue reproduce with the latest release?
Yes.

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/zwass/dev/go""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.9.2/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.9.2/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/4k/2q3ctn7d5_xb03_zsb3v6lgr0000gn/T/go-build085156185=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
```

### What did you do?
`test_test.go`
```
package test

import (
	""sync""
	""testing""
	""time""
)

func TestTest(t *testing.T) {
	var m sync.Mutex
	defer m.Lock()
	go func() {
		for {
			time.Sleep(1 * time.Second)
		}
	}()

	m.Lock()
	t.Fatal(""foobar"")
}
```

### What did you expect to see?
```
go test -v
=== RUN   TestTest
--- FAIL: TestTest (0.00s)
	test_test.go:19: foobar
FAIL
exit status 1
FAIL	test	0.007s
```

### What did you see instead?
```
go test -v
=== RUN   TestTest
panic: test timed out after 10m 0s

goroutine 17 [running]:
testing.startAlarm.func1()
	/usr/local/Cellar/go/1.9.2/libexec/src/testing/testing.go:1145 +0xf9
created by time.goFunc
	/usr/local/Cellar/go/1.9.2/libexec/src/time/sleep.go:170 +0x44

goroutine 1 [chan receive]:
testing.(*T).Run(0xc420094000, 0x1135230, 0x8, 0x113d640, 0x10688b6)
	/usr/local/Cellar/go/1.9.2/libexec/src/testing/testing.go:790 +0x2fc
testing.runTests.func1(0xc420094000)
	/usr/local/Cellar/go/1.9.2/libexec/src/testing/testing.go:1004 +0x64
testing.tRunner(0xc420094000, 0xc420043de0)
	/usr/local/Cellar/go/1.9.2/libexec/src/testing/testing.go:746 +0xd0
testing.runTests(0xc42000a060, 0x11db860, 0x1, 0x1, 0xc42004c3b0)
	/usr/local/Cellar/go/1.9.2/libexec/src/testing/testing.go:1002 +0x2d8
testing.(*M).Run(0xc420043f18, 0xc420043f70)
	/usr/local/Cellar/go/1.9.2/libexec/src/testing/testing.go:921 +0x111
main.main()
	test/_test/_testmain.go:44 +0xdb

goroutine 6 [semacquire]:
sync.runtime_SemacquireMutex(0xc4200140ec, 0xc420048e00)
	/usr/local/Cellar/go/1.9.2/libexec/src/runtime/sema.go:71 +0x3d
sync.(*Mutex).Lock(0xc4200140e8)
	/usr/local/Cellar/go/1.9.2/libexec/src/sync/mutex.go:134 +0xee
runtime.Goexit()
	/usr/local/Cellar/go/1.9.2/libexec/src/runtime/panic.go:366 +0x147
testing.(*common).FailNow(0xc4200940f0)
	/usr/local/Cellar/go/1.9.2/libexec/src/testing/testing.go:544 +0x39
testing.(*common).Fatal(0xc4200940f0, 0xc420030788, 0x1, 0x1)
	/usr/local/Cellar/go/1.9.2/libexec/src/testing/testing.go:582 +0x6f
test.TestTest(0xc4200940f0)
	/Users/zwass/dev/go/src/test/test_test.go:19 +0xdc
testing.tRunner(0xc4200940f0, 0x113d640)
	/usr/local/Cellar/go/1.9.2/libexec/src/testing/testing.go:746 +0xd0
created by testing.(*T).Run
	/usr/local/Cellar/go/1.9.2/libexec/src/testing/testing.go:789 +0x2de

goroutine 7 [sleep]:
time.Sleep(0x3b9aca00)
	/usr/local/Cellar/go/1.9.2/libexec/src/runtime/time.go:65 +0x130
test.TestTest.func1()
	/Users/zwass/dev/go/src/test/test_test.go:14 +0x2a
created by test.TestTest
	/Users/zwass/dev/go/src/test/test_test.go:12 +0x78
exit status 2
FAIL	test	600.010s
```

The above example is obviously broken, but this hanging behavior from the test runner causes quite a confusing experience when there are more subtle issues going on.

It's also worth noting that there is no way to determine from the dumped goroutines what is causing the hang.

From what I can tell, this is due to `t.FailNow()` using `runtime.GoExit()` which waits for defers to complete.

The docs for `t.FailNow()` say the following:

> FailNow marks the function as having failed and stops its execution. Execution will continue at the next test or benchmark. FailNow must be called from the goroutine running the test or benchmark function, not from other goroutines created during the test. Calling FailNow does not stop those other goroutines.",1.0,"testing: t.Fatal does not fatal tests if defers do not complete - ### What version of Go are you using (`go version`)?
`go version go1.9.2 darwin/amd64`

### Does this issue reproduce with the latest release?
Yes.

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/zwass/dev/go""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.9.2/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.9.2/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/4k/2q3ctn7d5_xb03_zsb3v6lgr0000gn/T/go-build085156185=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
```

### What did you do?
`test_test.go`
```
package test

import (
	""sync""
	""testing""
	""time""
)

func TestTest(t *testing.T) {
	var m sync.Mutex
	defer m.Lock()
	go func() {
		for {
			time.Sleep(1 * time.Second)
		}
	}()

	m.Lock()
	t.Fatal(""foobar"")
}
```

### What did you expect to see?
```
go test -v
=== RUN   TestTest
--- FAIL: TestTest (0.00s)
	test_test.go:19: foobar
FAIL
exit status 1
FAIL	test	0.007s
```

### What did you see instead?
```
go test -v
=== RUN   TestTest
panic: test timed out after 10m 0s

goroutine 17 [running]:
testing.startAlarm.func1()
	/usr/local/Cellar/go/1.9.2/libexec/src/testing/testing.go:1145 +0xf9
created by time.goFunc
	/usr/local/Cellar/go/1.9.2/libexec/src/time/sleep.go:170 +0x44

goroutine 1 [chan receive]:
testing.(*T).Run(0xc420094000, 0x1135230, 0x8, 0x113d640, 0x10688b6)
	/usr/local/Cellar/go/1.9.2/libexec/src/testing/testing.go:790 +0x2fc
testing.runTests.func1(0xc420094000)
	/usr/local/Cellar/go/1.9.2/libexec/src/testing/testing.go:1004 +0x64
testing.tRunner(0xc420094000, 0xc420043de0)
	/usr/local/Cellar/go/1.9.2/libexec/src/testing/testing.go:746 +0xd0
testing.runTests(0xc42000a060, 0x11db860, 0x1, 0x1, 0xc42004c3b0)
	/usr/local/Cellar/go/1.9.2/libexec/src/testing/testing.go:1002 +0x2d8
testing.(*M).Run(0xc420043f18, 0xc420043f70)
	/usr/local/Cellar/go/1.9.2/libexec/src/testing/testing.go:921 +0x111
main.main()
	test/_test/_testmain.go:44 +0xdb

goroutine 6 [semacquire]:
sync.runtime_SemacquireMutex(0xc4200140ec, 0xc420048e00)
	/usr/local/Cellar/go/1.9.2/libexec/src/runtime/sema.go:71 +0x3d
sync.(*Mutex).Lock(0xc4200140e8)
	/usr/local/Cellar/go/1.9.2/libexec/src/sync/mutex.go:134 +0xee
runtime.Goexit()
	/usr/local/Cellar/go/1.9.2/libexec/src/runtime/panic.go:366 +0x147
testing.(*common).FailNow(0xc4200940f0)
	/usr/local/Cellar/go/1.9.2/libexec/src/testing/testing.go:544 +0x39
testing.(*common).Fatal(0xc4200940f0, 0xc420030788, 0x1, 0x1)
	/usr/local/Cellar/go/1.9.2/libexec/src/testing/testing.go:582 +0x6f
test.TestTest(0xc4200940f0)
	/Users/zwass/dev/go/src/test/test_test.go:19 +0xdc
testing.tRunner(0xc4200940f0, 0x113d640)
	/usr/local/Cellar/go/1.9.2/libexec/src/testing/testing.go:746 +0xd0
created by testing.(*T).Run
	/usr/local/Cellar/go/1.9.2/libexec/src/testing/testing.go:789 +0x2de

goroutine 7 [sleep]:
time.Sleep(0x3b9aca00)
	/usr/local/Cellar/go/1.9.2/libexec/src/runtime/time.go:65 +0x130
test.TestTest.func1()
	/Users/zwass/dev/go/src/test/test_test.go:14 +0x2a
created by test.TestTest
	/Users/zwass/dev/go/src/test/test_test.go:12 +0x78
exit status 2
FAIL	test	600.010s
```

The above example is obviously broken, but this hanging behavior from the test runner causes quite a confusing experience when there are more subtle issues going on.

It's also worth noting that there is no way to determine from the dumped goroutines what is causing the hang.

From what I can tell, this is due to `t.FailNow()` using `runtime.GoExit()` which waits for defers to complete.

The docs for `t.FailNow()` say the following:

> FailNow marks the function as having failed and stops its execution. Execution will continue at the next test or benchmark. FailNow must be called from the goroutine running the test or benchmark function, not from other goroutines created during the test. Calling FailNow does not stop those other goroutines.",1,testing  t fatal does not fatal tests if defers do not complete       what version of go are you using   go version      go version       darwin           does this issue reproduce with the latest release   yes         what operating system and processor architecture are you using   go env          goarch      gobin     goexe     gohostarch      gohostos  darwin   goos  darwin   gopath   users zwass dev go   gorace     goroot   usr local cellar go       libexec   gotooldir   usr local cellar go       libexec pkg tool darwin     gccgo  gccgo   cc  clang   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders         t go    tmp go build  gno record gcc switches  fno common   cxx  clang     cgo enabled      cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config              what did you do    test test go        package test    import    	 sync   	 testing   	 time        func testtest t  testing t     	var m sync mutex  	defer m lock    	go func      		for    			time sleep     time second   		   	       	m lock    	t fatal  foobar                  what did you expect to see        go test  v      run   testtest      fail  testtest        	test test go    foobar  fail  exit status    fail	test	                what did you see instead        go test  v      run   testtest  panic  test timed out after        goroutine       testing startalarm      	 usr local cellar go       libexec src testing testing go       created by time gofunc  	 usr local cellar go       libexec src time sleep go         goroutine       testing   t  run                 	 usr local cellar go       libexec src testing testing go       testing runtests       	 usr local cellar go       libexec src testing testing go       testing trunner        	 usr local cellar go       libexec src testing testing go       testing runtests                 	 usr local cellar go       libexec src testing testing go       testing   m  run        	 usr local cellar go       libexec src testing testing go       main main    	test  test  testmain go         goroutine       sync runtime semacquiremutex        	 usr local cellar go       libexec src runtime sema go       sync   mutex  lock     	 usr local cellar go       libexec src sync mutex go       runtime goexit    	 usr local cellar go       libexec src runtime panic go       testing   common  failnow     	 usr local cellar go       libexec src testing testing go       testing   common  fatal              	 usr local cellar go       libexec src testing testing go       test testtest     	 users zwass dev go src test test test go       testing trunner        	 usr local cellar go       libexec src testing testing go       created by testing   t  run  	 usr local cellar go       libexec src testing testing go         goroutine       time sleep     	 usr local cellar go       libexec src runtime time go       test testtest      	 users zwass dev go src test test test go       created by test testtest  	 users zwass dev go src test test test go       exit status    fail	test	            the above example is obviously broken  but this hanging behavior from the test runner causes quite a confusing experience when there are more subtle issues going on     it s also worth noting that there is no way to determine from the dumped goroutines what is causing the hang     from what i can tell  this is due to  t failnow    using  runtime goexit    which waits for defers to complete     the docs for  t failnow    say the following       failnow marks the function as having failed and stops its execution  execution will continue at the next test or benchmark  failnow must be called from the goroutine running the test or benchmark function  not from other goroutines created during the test  calling failnow does not stop those other goroutines ,1
676726,23135637829.0,IssuesEvent,2022-07-28 14:07:36,pystardust/ani-cli,https://api.github.com/repos/pystardust/ani-cli,closed,ani-cli Video player not opening issue,type: bug priority 2: medium,"**Metadata (please complete the following information)**
Version: [e.g. 3.3.1]
OS: [Android-Termux]
Shell: [bashl]


**Describe the bug**
ani-cli is not asking which video player to use, it shows the video is playing and i have multiple video player in my phones but ani-cli is not even opening one of them. so all i have is a screen that is showing me option to quit,next, previous.

**Steps To Reproduce**

1. Run `ani-cli`
2. select anime and episode number

**Expected behavior**
A video player should play the anime.

**Screenshots (if applicable; you can just drag the image onto github)**
![image](https://user-images.githubusercontent.com/32749921/181510647-2a0f0980-af15-49b5-8711-fab546c62db0.png)

So this is all i am getting, and no video player is starting to play the anime.

",1.0,"ani-cli Video player not opening issue - **Metadata (please complete the following information)**
Version: [e.g. 3.3.1]
OS: [Android-Termux]
Shell: [bashl]


**Describe the bug**
ani-cli is not asking which video player to use, it shows the video is playing and i have multiple video player in my phones but ani-cli is not even opening one of them. so all i have is a screen that is showing me option to quit,next, previous.

**Steps To Reproduce**

1. Run `ani-cli`
2. select anime and episode number

**Expected behavior**
A video player should play the anime.

**Screenshots (if applicable; you can just drag the image onto github)**
![image](https://user-images.githubusercontent.com/32749921/181510647-2a0f0980-af15-49b5-8711-fab546c62db0.png)

So this is all i am getting, and no video player is starting to play the anime.

",0,ani cli video player not opening issue     metadata  please complete the following information     version     os     shell           describe the bug    ani cli is not asking which video player to use  it shows the video is playing and i have multiple video player in my phones but ani cli is not even opening one of them  so all i have is a screen that is showing me option to quit next  previous       steps to reproduce         run  ani cli      select anime and episode number      expected behavior    a video player should play the anime       screenshots  if applicable  you can just drag the image onto github             so this is all i am getting  and no video player is starting to play the anime     ,0
11043,3454719393.0,IssuesEvent,2015-12-17 17:00:15,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: document 'go generate' flags -n -v -x,Documentation,"Looking at https://tip.golang.org/cmd/go/#hdr-Generate_Go_files_by_processing_source right now:

> Usage:
>
> ```
> go generate [-run regexp] [file.go... | packages]
> ```

However, at the bottom it mentions:

> It also accepts the standard build flags -v, -n, and -x. The -v flag prints the names of packages and files as they are processed. The -n flag prints commands that would be executed. The -x flag prints commands as they are executed.

The usage line should be updated to mention those additional flags:

```diff
-go generate [-run regexp] [file.go... | packages]
+go generate [-v] [-n] [-x] [-run regexp] [file.go... | packages]
```

Other commands have their usage complete and do not skip -n and -x flags that are available, for example:

```
go clean [-i] [-r] [-n] [-x] [build flags] [packages]
go fmt [-n] [-x] [packages]
go tool [-n] command [args...]
go vet [-n] [-x] [build flags] [packages]
go get [-d] [-f] [-fix] [-insecure] [-t] [-u] [build flags] [packages]
```

It seems -v is never included even if available, so maybe it's most consistent to do:

```
go generate [-n] [-x] [-run regexp] [file.go... | packages]
```",1.0,"cmd/go: document 'go generate' flags -n -v -x - Looking at https://tip.golang.org/cmd/go/#hdr-Generate_Go_files_by_processing_source right now:

> Usage:
>
> ```
> go generate [-run regexp] [file.go... | packages]
> ```

However, at the bottom it mentions:

> It also accepts the standard build flags -v, -n, and -x. The -v flag prints the names of packages and files as they are processed. The -n flag prints commands that would be executed. The -x flag prints commands as they are executed.

The usage line should be updated to mention those additional flags:

```diff
-go generate [-run regexp] [file.go... | packages]
+go generate [-v] [-n] [-x] [-run regexp] [file.go... | packages]
```

Other commands have their usage complete and do not skip -n and -x flags that are available, for example:

```
go clean [-i] [-r] [-n] [-x] [build flags] [packages]
go fmt [-n] [-x] [packages]
go tool [-n] command [args...]
go vet [-n] [-x] [build flags] [packages]
go get [-d] [-f] [-fix] [-insecure] [-t] [-u] [build flags] [packages]
```

It seems -v is never included even if available, so maybe it's most consistent to do:

```
go generate [-n] [-x] [-run regexp] [file.go... | packages]
```",1,cmd go  document  go generate  flags  n  v  x   looking at   right now       usage               go generate               however  at the bottom it mentions       it also accepts the standard build flags  v   n  and  x  the  v flag prints the names of packages and files as they are processed  the  n flag prints commands that would be executed  the  x flag prints commands as they are executed     the usage line should be updated to mention those additional flags        diff   go generate       go generate                   other commands have their usage complete and do not skip  n and  x flags that are available  for example          go clean              go fmt        go tool   command    go vet          go get                         it seems  v is never included even if available  so maybe it s most consistent to do          go generate             ,1
10342,8901049490.0,IssuesEvent,2019-01-17 00:32:00,Azure/azure-powershell,https://api.github.com/repos/Azure/azure-powershell,closed,Remove-AzureRmResourceGroup does not bubble up errors if the operation fails,Resource Manager Service Attention,"Also, the following error message is given out -
ResourceGroupDeletionFailed: The deletion of resource group 'ms-dev' did not finish within allowed time. Resource group provisioning state rolled back. Please check audit logs for more details. 
The above implies that the resource group state was rolled back which is not the case.
Fix the error message too. And Update help to point out that the resources inside the RG will be deleted and what will happen if operation fails.
",1.0,"Remove-AzureRmResourceGroup does not bubble up errors if the operation fails - Also, the following error message is given out -
ResourceGroupDeletionFailed: The deletion of resource group 'ms-dev' did not finish within allowed time. Resource group provisioning state rolled back. Please check audit logs for more details. 
The above implies that the resource group state was rolled back which is not the case.
Fix the error message too. And Update help to point out that the resources inside the RG will be deleted and what will happen if operation fails.
",0,remove azurermresourcegroup does not bubble up errors if the operation fails   also  the following error message is given out   resourcegroupdeletionfailed  the deletion of resource group  ms dev  did not finish within allowed time  resource group provisioning state rolled back  please check audit logs for more details   the above implies that the resource group state was rolled back which is not the case  fix the error message too  and update help to point out that the resources inside the rg will be deleted and what will happen if operation fails  ,0
260646,22637608891.0,IssuesEvent,2022-06-30 20:44:29,tgstation/tgstation,https://api.github.com/repos/tgstation/tgstation,closed,Tree cutting doesn't work with chainsaws and eswords don't need to be on,Bug Tested/Reproduced,"## Round ID:
Tested locally

## Testmerges:
N/A

## Reproduction:
![image](https://user-images.githubusercontent.com/51932756/168963070-3ca218c6-15a6-490c-98ab-f06a3e8ab50d.png)
Spawn a tree, a chainsaw, wield the chainsaw, and click it - it takes brute damage
Spawn a hatchet and click it - progress bar
Spawn an esword, pick it up, don't turn it on, click it - progress bar
https://github.com/tgstation/tgstation/blob/5d264fbea0124e5af511af3fed24203e196d108b/code/__DEFINES/flora.dm#L1

I hate refactors! I hate refactors!!",1.0,"Tree cutting doesn't work with chainsaws and eswords don't need to be on - ## Round ID:
Tested locally

## Testmerges:
N/A

## Reproduction:
![image](https://user-images.githubusercontent.com/51932756/168963070-3ca218c6-15a6-490c-98ab-f06a3e8ab50d.png)
Spawn a tree, a chainsaw, wield the chainsaw, and click it - it takes brute damage
Spawn a hatchet and click it - progress bar
Spawn an esword, pick it up, don't turn it on, click it - progress bar
https://github.com/tgstation/tgstation/blob/5d264fbea0124e5af511af3fed24203e196d108b/code/__DEFINES/flora.dm#L1

I hate refactors! I hate refactors!!",0,tree cutting doesn t work with chainsaws and eswords don t need to be on      round id   tested locally       testmerges   n a       reproduction         spawn a tree  a chainsaw  wield the chainsaw  and click it   it takes brute damage  spawn a hatchet and click it   progress bar  spawn an esword  pick it up  don t turn it on  click it   progress bar       i hate refactors  i hate refactors  ,0
61356,25481533862.0,IssuesEvent,2022-11-25 22:04:57,boto/boto3,https://api.github.com/repos/boto/boto3,closed,describe_connection_aliases does not work,response-requested service-api closed-for-staleness workspaces p3,"### Describe the bug

Calling `describe_connection_aliases` on the `workspaces` client with valid non-null parameter values fails.


### Expected Behavior

No error.

### Current Behavior

The following error occurs:

```
Traceback (most recent call last):
  File ""<stdin>"", line 1, in <module>
  File ""/Users/nick.chadwick/Projects/msd/miniconda3/lib/python3.7/site-packages/botocore/client.py"", line 357, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File ""/Users/nick.chadwick/Projects/msd/miniconda3/lib/python3.7/site-packages/botocore/client.py"", line 676, in _make_api_call
    raise error_class(parsed_response, operation_name)
botocore.errorfactory.InvalidParameterValuesException: An error occurred (InvalidParameterValuesException) when calling the DescribeConnectionAliases operation: The value for the connection alias is null. Provide a value for the connection alias, and then try again.
```

### Reproduction Steps

```
import boto3
client = boto3.client('workspaces')
client.describe_connection_aliases(AliasIds = [ '<valid alias id>' ], ResourceId = '<valid directory id>')
```

### Possible Solution

_No response_

### Additional Information/Context

_No response_

### SDK version used

1.22.8

### Environment details (OS name and version, etc.)

Lambda function",1.0,"describe_connection_aliases does not work - ### Describe the bug

Calling `describe_connection_aliases` on the `workspaces` client with valid non-null parameter values fails.


### Expected Behavior

No error.

### Current Behavior

The following error occurs:

```
Traceback (most recent call last):
  File ""<stdin>"", line 1, in <module>
  File ""/Users/nick.chadwick/Projects/msd/miniconda3/lib/python3.7/site-packages/botocore/client.py"", line 357, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File ""/Users/nick.chadwick/Projects/msd/miniconda3/lib/python3.7/site-packages/botocore/client.py"", line 676, in _make_api_call
    raise error_class(parsed_response, operation_name)
botocore.errorfactory.InvalidParameterValuesException: An error occurred (InvalidParameterValuesException) when calling the DescribeConnectionAliases operation: The value for the connection alias is null. Provide a value for the connection alias, and then try again.
```

### Reproduction Steps

```
import boto3
client = boto3.client('workspaces')
client.describe_connection_aliases(AliasIds = [ '<valid alias id>' ], ResourceId = '<valid directory id>')
```

### Possible Solution

_No response_

### Additional Information/Context

_No response_

### SDK version used

1.22.8

### Environment details (OS name and version, etc.)

Lambda function",0,describe connection aliases does not work       describe the bug    calling  describe connection aliases  on the  workspaces  client with valid non null parameter values fails           expected behavior    no error         current behavior    the following error occurs          traceback  most recent call last      file      line    in      file   users nick chadwick projects msd   lib     site packages botocore client py   line    in  api call      return self  make api call operation name  kwargs     file   users nick chadwick projects msd   lib     site packages botocore client py   line    in  make api call      raise error class parsed response  operation name   botocore errorfactory invalidparametervaluesexception  an error occurred  invalidparametervaluesexception  when calling the describeconnectionaliases operation  the value for the connection alias is null  provide a value for the connection alias  and then try again              reproduction steps         import    client     client  workspaces    client describe connection aliases aliasids      resourceid                    possible solution     no response         additional information context     no response         sdk version used                 environment details  os name and version  etc      lambda function,0
512441,14896970050.0,IssuesEvent,2021-01-21 11:06:06,thehyve/delphyne,https://api.github.com/repos/thehyve/delphyne,closed,Add method for dropping STCM vocabularies,STCM high priority,"Problem: in `delphyne-template`, the custom vocabularies are updated before stcm:
```
        # Load vocabularies and source_to_concept_map tables
        self.vocab_manager.load_standard_vocabularies()
        self.vocab_manager.load_custom_vocabularies()
        self.vocab_manager.load_stcm()
```
this can break FK constraint in stcm, and to prevent that, currently you have to drop the stcm tables.

TODO:
- add method to drop stcm records related to custom vocabularies that will be updated.
- remove FK constraint in stcm table and reapply it after custom vocabs update? -> #128",1.0,"Add method for dropping STCM vocabularies - Problem: in `delphyne-template`, the custom vocabularies are updated before stcm:
```
        # Load vocabularies and source_to_concept_map tables
        self.vocab_manager.load_standard_vocabularies()
        self.vocab_manager.load_custom_vocabularies()
        self.vocab_manager.load_stcm()
```
this can break FK constraint in stcm, and to prevent that, currently you have to drop the stcm tables.

TODO:
- add method to drop stcm records related to custom vocabularies that will be updated.
- remove FK constraint in stcm table and reapply it after custom vocabs update? -> #128",0,add method for dropping stcm vocabularies   problem  in  delphyne template   the custom vocabularies are updated before stcm                  load vocabularies and source to concept map tables          self vocab manager load standard vocabularies            self vocab manager load custom vocabularies            self vocab manager load stcm         this can break fk constraint in stcm  and to prevent that  currently you have to drop the stcm tables     todo     add method to drop stcm records related to custom vocabularies that will be updated     remove fk constraint in stcm table and reapply it after custom vocabs update       ,0
110445,11700999551.0,IssuesEvent,2020-03-06 18:43:15,golang/go,https://api.github.com/repos/golang/go,closed,doc: missing documentation of quoting the URL of url.Errors in go1.14 release notes [1.14 backport],CherryPickApproved Documentation,"@dmitshur requested issue #37614 to be considered for backport to the next 1.14 minor release.

> This needs to be fixed on master branch first, then it can be backported to Go 1.14.x.
> 
> @gopherbot Please open a backport issue for Go 1.14; this is a documentation fix.
",1.0,"doc: missing documentation of quoting the URL of url.Errors in go1.14 release notes [1.14 backport] - @dmitshur requested issue #37614 to be considered for backport to the next 1.14 minor release.

> This needs to be fixed on master branch first, then it can be backported to Go 1.14.x.
> 
> @gopherbot Please open a backport issue for Go 1.14; this is a documentation fix.
",1,doc  missing documentation of quoting the url of url errors in     release notes      dmitshur requested issue    to be considered for backport to the next     minor release     this needs to be fixed on master branch first  then it can be backported to go     x          gopherbot please open a backport issue for go      this is a documentation fix  ,1
68135,21514566590.0,IssuesEvent,2022-04-28 08:42:31,primefaces/primefaces,https://api.github.com/repos/primefaces/primefaces,opened,Autocomplete: Dropdown panel messed up when dynamic=true && querymode=server,defect," Open the dropdown, then close it without picking. Write something that does not match any values, and then open the dropdown. 

Only happens when querymode=true and queryMode=server

```
    <c:set var=""dropdown"" value=""#{cell.dropdown}""/>
    <p:autoComplete id=""#{cellId}dd""
                    style=""#{cell.cellStyle}""
                    value=""#{dropdown.value}""
                    completeMethod=""#{dropdown.getRowList}""
                    queryMode=""server""
                    var=""rowItem""
                    converter=""dropdownConverter""
                    forceSelection=""true""
                    itemValue=""#{rowItem}""
                    itemLabel=""#{empty rowItem or rowItem['class'].simpleName eq 'String' ? rowItem : rowItem.getCell(dropdown.popupReturnColumnName).formattedDataValue}""
                    dropdown=""true""
                    scrollHeight=""#{dropdown.popupHeight}""
                    emptyMessage=""#{dropdown.emptyMessage}""
                    styleClass=""ECCell #{cell.dynamicStyleClasses}""
                    panelStyleClass=""ECMenuPanel""
                    pt:data-tooltip=""#{cell.verificationStatusMessage}""
                    rendered=""#{'DROPDOWN' == cell.renderType}""
                    onfocus=""EC.focus.handleFocus(event)""
                    widgetVar=""#{component.clientId}wv""
                    dynamic=""true""

    >

        <f:attribute name=""screenletId"" value=""#{cell.parentRow.dataModel.screenlet.uniqueId}"" />
        <f:attribute name=""EC_CELL"" value=""#{cell}"" />
        <p:ajax event=""change""     partialSubmit=""true"" process=""#{cellId}dd"" listener=""#{dropdown.onValueChange}"" oncomplete=""changeStyleClass('#{component.clientId}');""
                update=""#{cellId}dd"" onstart=""PF('#{component.clientId}wv').preventInputChangeEvent = false;"" />
        <p:ajax event=""query""      partialSubmit=""true"" process=""#{cellId}dd"" />

        <p:column id=""#{cellId}ddC""><h:outputText value=""#{rowItem.cellMap[rowItem.visibleCellNames[0]].formattedDataValue}""/>
            <ui:repeat id=""#{cellId}ddR"" rendered=""#{rowItem != null and rowItem.visibleCellNames.size() gt 1}"" value=""#{rowItem.visibleCellNames}"" var=""colName"" offset=""#{rowItem.visibleCellNames.size() gt 1 ? 1 : 0}""  varStatus=""status""><td>#{rowItem.cellMap[colName].formattedDataValue}</td></ui:repeat>
        </p:column>

    </p:autoComplete>
</ui:composition>
```
![image](https://user-images.githubusercontent.com/104558606/165713560-60de1d99-99b1-4e16-83cd-890329aad577.png)



PF version 10.4



",1.0,"Autocomplete: Dropdown panel messed up when dynamic=true && querymode=server -  Open the dropdown, then close it without picking. Write something that does not match any values, and then open the dropdown. 

Only happens when querymode=true and queryMode=server

```
    <c:set var=""dropdown"" value=""#{cell.dropdown}""/>
    <p:autoComplete id=""#{cellId}dd""
                    style=""#{cell.cellStyle}""
                    value=""#{dropdown.value}""
                    completeMethod=""#{dropdown.getRowList}""
                    queryMode=""server""
                    var=""rowItem""
                    converter=""dropdownConverter""
                    forceSelection=""true""
                    itemValue=""#{rowItem}""
                    itemLabel=""#{empty rowItem or rowItem['class'].simpleName eq 'String' ? rowItem : rowItem.getCell(dropdown.popupReturnColumnName).formattedDataValue}""
                    dropdown=""true""
                    scrollHeight=""#{dropdown.popupHeight}""
                    emptyMessage=""#{dropdown.emptyMessage}""
                    styleClass=""ECCell #{cell.dynamicStyleClasses}""
                    panelStyleClass=""ECMenuPanel""
                    pt:data-tooltip=""#{cell.verificationStatusMessage}""
                    rendered=""#{'DROPDOWN' == cell.renderType}""
                    onfocus=""EC.focus.handleFocus(event)""
                    widgetVar=""#{component.clientId}wv""
                    dynamic=""true""

    >

        <f:attribute name=""screenletId"" value=""#{cell.parentRow.dataModel.screenlet.uniqueId}"" />
        <f:attribute name=""EC_CELL"" value=""#{cell}"" />
        <p:ajax event=""change""     partialSubmit=""true"" process=""#{cellId}dd"" listener=""#{dropdown.onValueChange}"" oncomplete=""changeStyleClass('#{component.clientId}');""
                update=""#{cellId}dd"" onstart=""PF('#{component.clientId}wv').preventInputChangeEvent = false;"" />
        <p:ajax event=""query""      partialSubmit=""true"" process=""#{cellId}dd"" />

        <p:column id=""#{cellId}ddC""><h:outputText value=""#{rowItem.cellMap[rowItem.visibleCellNames[0]].formattedDataValue}""/>
            <ui:repeat id=""#{cellId}ddR"" rendered=""#{rowItem != null and rowItem.visibleCellNames.size() gt 1}"" value=""#{rowItem.visibleCellNames}"" var=""colName"" offset=""#{rowItem.visibleCellNames.size() gt 1 ? 1 : 0}""  varStatus=""status""><td>#{rowItem.cellMap[colName].formattedDataValue}</td></ui:repeat>
        </p:column>

    </p:autoComplete>
</ui:composition>
```
![image](https://user-images.githubusercontent.com/104558606/165713560-60de1d99-99b1-4e16-83cd-890329aad577.png)



PF version 10.4



",0,autocomplete  dropdown panel messed up when dynamic true    querymode server    open the dropdown  then close it without picking  write something that does not match any values  and then open the dropdown      only happens when querymode true and querymode server                     p autocomplete id    cellid dd                       style    cell cellstyle                        value    dropdown value                        completemethod    dropdown getrowlist                        querymode  server                       var  rowitem                       converter  dropdownconverter                       forceselection  true                       itemvalue    rowitem                        itemlabel    empty rowitem or rowitem  simplename eq  string    rowitem   rowitem getcell dropdown popupreturncolumnname  formatteddatavalue                        dropdown  true                       scrollheight    dropdown popupheight                        emptymessage    dropdown emptymessage                        styleclass  eccell   cell dynamicstyleclasses                        panelstyleclass  ecmenupanel                       pt data tooltip    cell verificationstatusmessage                        rendered     dropdown     cell rendertype                        onfocus  ec focus handlefocus event                        widgetvar    component clientid wv                       dynamic  true                                             p ajax event  change      partialsubmit  true  process    cellid dd  listener    dropdown onvaluechange   oncomplete  changestyleclass    component clientid                       update    cellid dd  onstart  pf    component clientid wv   preventinputchangeevent   false                                                rowitem cellmap  formatteddatavalue                                             pf version            ,0
96063,10917950288.0,IssuesEvent,2019-11-21 16:01:38,golang/go,https://api.github.com/repos/golang/go,closed,net/url: comment of split function is wrong,Documentation NeedsFix,"### What did you expect to see?
```
// split slices s into two substrings separated by the first occurrence of
// sep. If cutc is true then sep is excluded from the second substring.
// If sep does not occur in s then s and the empty string is returned.
func split(s string, sep byte, cutc bool) (string, string) {
	i := strings.IndexByte(s, sep)
	if i < 0 {
		return s, """"
	}
	if cutc {
		return s[:i], s[i+1:]
	}
	return s[:i], s[i:]
}
```

### What did you see instead?
```
// split slices s into two substrings separated by the first occurrence of
// sep. If cutc is true then sep is included with the second substring.
// If sep does not occur in s then s and the empty string is returned.
func split(s string, sep byte, cutc bool) (string, string) {
	i := strings.IndexByte(s, sep)
	if i < 0 {
		return s, """"
	}
	if cutc {
		return s[:i], s[i+1:]
	}
	return s[:i], s[i:]
}
```
https://github.com/golang/go/blob/39a9cb4b5dbf1e518b0c66fa3a7b4175f90226fc/src/net/url/url.go#L454-L466",1.0,"net/url: comment of split function is wrong - ### What did you expect to see?
```
// split slices s into two substrings separated by the first occurrence of
// sep. If cutc is true then sep is excluded from the second substring.
// If sep does not occur in s then s and the empty string is returned.
func split(s string, sep byte, cutc bool) (string, string) {
	i := strings.IndexByte(s, sep)
	if i < 0 {
		return s, """"
	}
	if cutc {
		return s[:i], s[i+1:]
	}
	return s[:i], s[i:]
}
```

### What did you see instead?
```
// split slices s into two substrings separated by the first occurrence of
// sep. If cutc is true then sep is included with the second substring.
// If sep does not occur in s then s and the empty string is returned.
func split(s string, sep byte, cutc bool) (string, string) {
	i := strings.IndexByte(s, sep)
	if i < 0 {
		return s, """"
	}
	if cutc {
		return s[:i], s[i+1:]
	}
	return s[:i], s[i:]
}
```
https://github.com/golang/go/blob/39a9cb4b5dbf1e518b0c66fa3a7b4175f90226fc/src/net/url/url.go#L454-L466",1,net url  comment of split function is wrong       what did you expect to see           split slices s into two substrings separated by the first occurrence of     sep  if cutc is true then sep is excluded from the second substring      if sep does not occur in s then s and the empty string is returned   func split s string  sep byte  cutc bool   string  string     	i    strings indexbyte s  sep   	if i        		return s      	   	if cutc    		return s   s   	   	return s   s                 what did you see instead           split slices s into two substrings separated by the first occurrence of     sep  if cutc is true then sep is included with the second substring      if sep does not occur in s then s and the empty string is returned   func split s string  sep byte  cutc bool   string  string     	i    strings indexbyte s  sep   	if i        		return s      	   	if cutc    		return s   s   	   	return s   s            ,1
23737,4971681206.0,IssuesEvent,2016-12-05 19:23:49,golang/go,https://api.github.com/repos/golang/go,closed,"cmd/compile: mips: document requirements, Illegal instruction on mips router: GL-AR300M and GL-AR150",Documentation NeedsFix,"### What version of Go are you using (`go version`)?

```
go version go1.8beta1 windows/amd64
```

### What operating system and processor architecture are you using (`go env`)?

Building on `windows-amd64` for `linux-mips`.

```
set GOARCH=mips
set GOBIN=
set GOEXE=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=linux
set GOPATH=C:\Users\cetin\go
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set GOGCCFLAGS=-fPIC -fmessage-length=0
set CXX=g++
set CGO_ENABLED=0
set PKG_CONFIG=pkg-config
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
```

### What did you do?

Windows PC (`cmd.exe`):

```
set GOOS=linux&&set GOARCH=mips&&go build
```

MIPS Router:

```
./hello
Illegal instruction
```

### What did you expect to see?

```
Hello world!
```

### What did you see instead?

```
Illegal instruction
```

---

What kind of hardware products does the recent mips support merge target then?",1.0,"cmd/compile: mips: document requirements, Illegal instruction on mips router: GL-AR300M and GL-AR150 - ### What version of Go are you using (`go version`)?

```
go version go1.8beta1 windows/amd64
```

### What operating system and processor architecture are you using (`go env`)?

Building on `windows-amd64` for `linux-mips`.

```
set GOARCH=mips
set GOBIN=
set GOEXE=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=linux
set GOPATH=C:\Users\cetin\go
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set GOGCCFLAGS=-fPIC -fmessage-length=0
set CXX=g++
set CGO_ENABLED=0
set PKG_CONFIG=pkg-config
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
```

### What did you do?

Windows PC (`cmd.exe`):

```
set GOOS=linux&&set GOARCH=mips&&go build
```

MIPS Router:

```
./hello
Illegal instruction
```

### What did you expect to see?

```
Hello world!
```

### What did you see instead?

```
Illegal instruction
```

---

What kind of hardware products does the recent mips support merge target then?",1,cmd compile  mips  document requirements  illegal instruction on mips router  gl   and gl         what version of go are you using   go version            go version     windows               what operating system and processor architecture are you using   go env       building on  windows    for  linux mips           set goarch mips  set gobin   set goexe   set gohostarch    set gohostos windows  set goos linux  set gopath c  users cetin go  set gorace   set goroot c  go  set gotooldir c  go pkg tool windows    set gccgo gccgo  set cc gcc  set gogccflags  fpic  fmessage length    set cxx g    set cgo enabled    set pkg config pkg config  set cgo cflags  g     set cgo cppflags   set cgo cxxflags  g     set cgo fflags  g     set cgo ldflags  g                what did you do     windows pc   cmd exe            set goos linux  set goarch mips  go build         mips router            hello  illegal instruction             what did you expect to see          hello world              what did you see instead          illegal instruction                what kind of hardware products does the recent mips support merge target then ,1
74674,3442169618.0,IssuesEvent,2015-12-14 21:29:20,dkpro/dkpro-core,https://api.github.com/repos/dkpro/dkpro-core,closed,Writers should have a parameter for merging the output in one file,enhancement Module-api.resources Priority-Medium,"```
CoNLL Writers should also the offer the possibility for merging the output into one
single file.
```

Original issue reported on code.google.com by `pedrobssantos` on 2014-10-20 09:42:20",1.0,"Writers should have a parameter for merging the output in one file - ```
CoNLL Writers should also the offer the possibility for merging the output into one
single file.
```

Original issue reported on code.google.com by `pedrobssantos` on 2014-10-20 09:42:20",0,writers should have a parameter for merging the output in one file       conll writers should also the offer the possibility for merging the output into one single file       original issue reported on code google com by  pedrobssantos  on            ,0
49288,6020958826.0,IssuesEvent,2017-06-07 17:37:05,appium/appium,https://api.github.com/repos/appium/appium,closed,[XCUITest] NO scrolling to center of element,XCUITest,"## The problem

With version 1.6.4 when I perform a scroll using TouchActions it scrolls till the center of the element is visible. Then I could do a click, which is as standard at the center of the element.
After update to 1.6.5 it scrolls only till the top of the element is visible. So if I perform a click to the element it does not work, since the center of the element is not visible(clickable). 

## Environment

* Appium version (or git revision) that exhibits the issue: 1.6.4-beta + 1.6.4-beta2. + 1.6.5
* Last Appium version that did not exhibit the issue (if applicable): 1.6.4
* Desktop OS/version used to run Appium: Mac OS 10.12.5
* Node.js version (unless using Appium.app|exe):  6.9.1
* Mobile platform/version under test: iOS 10.3
* Real device or emulator/simulator: simulator
* Appium CLI or Appium.app|exe: CLI


## Link to Appium logs

[gist NOT working v1.6.5](https://gist.github.com/derunewige/cc78fa08a60e5a20b1dcca0d3f3e3f8f) 

[gist working v1.6.4](https://gist.github.com/derunewige/dcbe0df4ce1b8f90a410c22ee63d135a) 

## Code To Reproduce Issue [ Good To Have ]

```
public static void waitForVisibilityAndClick(By locator, long timeout) {
		AppiumDriver<IOSElement> driver = null;
		try {
			driver = AppiumDriverBuilder.getIOSDriver();
		} catch (MalformedURLException e) {
			e.printStackTrace();
		}
		WebDriverWait wait = new WebDriverWait(driver, timeout);

		IOSElement elem = (IOSElement) wait.until(ExpectedConditions.presenceOfElementLocated(locator));

		if (!elem.isDisplayed()) {
			try {
				driver.performTouchAction(new IOSTouchAction(driver).press(0, 0).moveTo(elem).release());
				// log.debug(""after scrolling"");
			} catch (WebDriverException e) {
				if (!e.getMessage().contains(""Failed to find scrollable visible parent with 2 visible children"")) {
					e.printStackTrace();
					throw new WebDriverException(e);
				} else {
					log.warn(""Failed to find scrollable visible parent with 2 visible children"");
				}
			}
		}
	 wait.until(ExpectedConditions.visibilityOf(elem)).click();
	}
```",1.0,"[XCUITest] NO scrolling to center of element - ## The problem

With version 1.6.4 when I perform a scroll using TouchActions it scrolls till the center of the element is visible. Then I could do a click, which is as standard at the center of the element.
After update to 1.6.5 it scrolls only till the top of the element is visible. So if I perform a click to the element it does not work, since the center of the element is not visible(clickable). 

## Environment

* Appium version (or git revision) that exhibits the issue: 1.6.4-beta + 1.6.4-beta2. + 1.6.5
* Last Appium version that did not exhibit the issue (if applicable): 1.6.4
* Desktop OS/version used to run Appium: Mac OS 10.12.5
* Node.js version (unless using Appium.app|exe):  6.9.1
* Mobile platform/version under test: iOS 10.3
* Real device or emulator/simulator: simulator
* Appium CLI or Appium.app|exe: CLI


## Link to Appium logs

[gist NOT working v1.6.5](https://gist.github.com/derunewige/cc78fa08a60e5a20b1dcca0d3f3e3f8f) 

[gist working v1.6.4](https://gist.github.com/derunewige/dcbe0df4ce1b8f90a410c22ee63d135a) 

## Code To Reproduce Issue [ Good To Have ]

```
public static void waitForVisibilityAndClick(By locator, long timeout) {
		AppiumDriver<IOSElement> driver = null;
		try {
			driver = AppiumDriverBuilder.getIOSDriver();
		} catch (MalformedURLException e) {
			e.printStackTrace();
		}
		WebDriverWait wait = new WebDriverWait(driver, timeout);

		IOSElement elem = (IOSElement) wait.until(ExpectedConditions.presenceOfElementLocated(locator));

		if (!elem.isDisplayed()) {
			try {
				driver.performTouchAction(new IOSTouchAction(driver).press(0, 0).moveTo(elem).release());
				// log.debug(""after scrolling"");
			} catch (WebDriverException e) {
				if (!e.getMessage().contains(""Failed to find scrollable visible parent with 2 visible children"")) {
					e.printStackTrace();
					throw new WebDriverException(e);
				} else {
					log.warn(""Failed to find scrollable visible parent with 2 visible children"");
				}
			}
		}
	 wait.until(ExpectedConditions.visibilityOf(elem)).click();
	}
```",0,  no scrolling to center of element      the problem    with version       when i perform a scroll using touchactions it scrolls till the center of the element is visible  then i could do a click  which is as standard at the center of the element   after update to       it scrolls only till the top of the element is visible  so if i perform a click to the element it does not work  since the center of the element is not visible clickable          environment      appium version  or git revision  that exhibits the issue        beta                       last appium version that did not exhibit the issue  if applicable            desktop os version used to run appium  mac os          node js version  unless using appium app exe             mobile platform version under test  ios        real device or emulator simulator  simulator    appium cli or appium app exe  cli         link to appium logs                       code to reproduce issue           public static void waitforvisibilityandclick by locator  long timeout     		appiumdriver  driver   null   		try    			driver   appiumdriverbuilder getiosdriver     		  catch  malformedurlexception e     			e printstacktrace     		   		webdriverwait wait   new webdriverwait driver  timeout      		ioselement elem    ioselement  wait until expectedconditions presenceofelementlocated locator       		if   elem isdisplayed       			try    				driver performtouchaction new iostouchaction driver  press       moveto elem  release      				   log debug  after scrolling     			  catch  webdriverexception e     				if   e getmessage   contains  failed to find scrollable visible parent with   visible children       					e printstacktrace     					throw new webdriverexception e    				  else    					log warn  failed to find scrollable visible parent with   visible children     				   			   		   	 wait until expectedconditions visibilityof elem   click     	      ,0
59030,8319732722.0,IssuesEvent,2018-09-25 18:03:40,golang/go,https://api.github.com/repos/golang/go,closed,doc: broken link in FAQ,Documentation,"Under the question ""[Why do garbage collection? Won't it be too expensive?][1]"", there is a link to https://talks.golang.org/2018/ismmkeynote, which does not exist. It should link to https://blog.golang.org/ismmkeynote.

[1]: https://golang.org/doc/faq#garbage_collection",1.0,"doc: broken link in FAQ - Under the question ""[Why do garbage collection? Won't it be too expensive?][1]"", there is a link to https://talks.golang.org/2018/ismmkeynote, which does not exist. It should link to https://blog.golang.org/ismmkeynote.

[1]: https://golang.org/doc/faq#garbage_collection",1,doc  broken link in faq   under the question       there is a link to   which does not exist  it should link to          ,1
232218,17776404556.0,IssuesEvent,2021-08-30 19:50:30,golang/go,https://api.github.com/repos/golang/go,opened,dl: switch to go install path@latest syntax in documentation,Documentation NeedsFix modules,"Now that Go 1.17 is released and Go 1.15 in unsupported per [release policy](https://golang.org/doc/devel/release#policy), we should update documentation of [`golang.org/dl/go1.N` commands](https://pkg.go.dev/golang.org/dl#section-directories) to suggest the new `go install path@latest` installation syntax instead of `go get` per #43684.

It should be okay to update documentation for all `golang.org/dl/...` commands, even pre-1.15 ones, since they're still meant to serve supported Go versions, all of which by now support the new syntax.

CC @golang/release, @bcmills, @jayconrod, @matloob.",1.0,"dl: switch to go install path@latest syntax in documentation - Now that Go 1.17 is released and Go 1.15 in unsupported per [release policy](https://golang.org/doc/devel/release#policy), we should update documentation of [`golang.org/dl/go1.N` commands](https://pkg.go.dev/golang.org/dl#section-directories) to suggest the new `go install path@latest` installation syntax instead of `go get` per #43684.

It should be okay to update documentation for all `golang.org/dl/...` commands, even pre-1.15 ones, since they're still meant to serve supported Go versions, all of which by now support the new syntax.

CC @golang/release, @bcmills, @jayconrod, @matloob.",1,dl  switch to go install path latest syntax in documentation   now that go     is released and go     in unsupported per     we should update documentation of     to suggest the new  go install path latest  installation syntax instead of  go get  per        it should be okay to update documentation for all  golang org dl      commands  even pre     ones  since they re still meant to serve supported go versions  all of which by now support the new syntax     cc  golang release   bcmills   jayconrod   matloob ,1
43306,7037406856.0,IssuesEvent,2017-12-28 14:40:44,golang/go,https://api.github.com/repos/golang/go,closed,doc: add Go to the list of languages at syntax-across-languages-per-language,Documentation help wanted,"Looks like Go is missing from the list:
http://rigaux.org/language-study/syntax-across-languages-per-language/what-is-missing.html",1.0,"doc: add Go to the list of languages at syntax-across-languages-per-language - Looks like Go is missing from the list:
http://rigaux.org/language-study/syntax-across-languages-per-language/what-is-missing.html",1,doc  add go to the list of languages at syntax across languages per language   looks like go is missing from the list    ,1
79412,10121943279.0,IssuesEvent,2019-07-31 16:44:17,golang/go,https://api.github.com/repos/golang/go,closed,doc: syscall: document Setrlimit behavior change on Go 1.13 on macOS,Documentation NeedsInvestigation OS-Darwin release-blocker,"We've noticed a while back that when setting the file descriptor allowance on macos, Go restricts it to a lower value than requested:

```go
package main

import (
	""fmt""
	""syscall""
)

func main() {
	// Get the current file descriptor limit
	var limit syscall.Rlimit
	if err := syscall.Getrlimit(syscall.RLIMIT_NOFILE, &limit); err != nil {
		panic(err)
	}
	// Try to update the limit to the max allowance
	limit.Cur = limit.Max
	if err := syscall.Setrlimit(syscall.RLIMIT_NOFILE, &limit); err != nil {
		panic(err)
	}
	// Try to get the limit again and see where it's at
	if err := syscall.Getrlimit(syscall.RLIMIT_NOFILE, &limit); err != nil {
		panic(err)
	}
	fmt.Println(limit.Cur)
}
```

The above code on Linux works as expected, setting the limit to the max returned by the syscall package.

On macos with Go 1.11.5 (and prior) it silently set it to the minimum of `limit.Max` and 10240. We had to patch our code to explicitly check the actual value set instead of relying on no-error-returned since we falsely alloted more fds to databases than available.

On macos with Go 1.12, our code again started to blow up, now returning `invalid argument` errors instead of the silent capping previously.

I'd probably say both behaviors are bad, but the new one is a **lot** worse than the previous. Now it only tells us it's invalid, but unless you know the magic number defined in the **your own kernel version**, there's no way for user code to figure out how many fds are actually available.",1.0,"doc: syscall: document Setrlimit behavior change on Go 1.13 on macOS - We've noticed a while back that when setting the file descriptor allowance on macos, Go restricts it to a lower value than requested:

```go
package main

import (
	""fmt""
	""syscall""
)

func main() {
	// Get the current file descriptor limit
	var limit syscall.Rlimit
	if err := syscall.Getrlimit(syscall.RLIMIT_NOFILE, &limit); err != nil {
		panic(err)
	}
	// Try to update the limit to the max allowance
	limit.Cur = limit.Max
	if err := syscall.Setrlimit(syscall.RLIMIT_NOFILE, &limit); err != nil {
		panic(err)
	}
	// Try to get the limit again and see where it's at
	if err := syscall.Getrlimit(syscall.RLIMIT_NOFILE, &limit); err != nil {
		panic(err)
	}
	fmt.Println(limit.Cur)
}
```

The above code on Linux works as expected, setting the limit to the max returned by the syscall package.

On macos with Go 1.11.5 (and prior) it silently set it to the minimum of `limit.Max` and 10240. We had to patch our code to explicitly check the actual value set instead of relying on no-error-returned since we falsely alloted more fds to databases than available.

On macos with Go 1.12, our code again started to blow up, now returning `invalid argument` errors instead of the silent capping previously.

I'd probably say both behaviors are bad, but the new one is a **lot** worse than the previous. Now it only tells us it's invalid, but unless you know the magic number defined in the **your own kernel version**, there's no way for user code to figure out how many fds are actually available.",1,doc  syscall  document setrlimit behavior change on go     on macos   we ve noticed a while back that when setting the file descriptor allowance on macos  go restricts it to a lower value than requested        go  package main    import    	 fmt   	 syscall        func main      	   get the current file descriptor limit  	var limit syscall rlimit  	if err    syscall getrlimit syscall rlimit nofile   limit   err    nil    		panic err   	   	   try to update the limit to the max allowance  	limit cur   limit max  	if err    syscall setrlimit syscall rlimit nofile   limit   err    nil    		panic err   	   	   try to get the limit again and see where it s at  	if err    syscall getrlimit syscall rlimit nofile   limit   err    nil    		panic err   	   	fmt println limit cur             the above code on linux works as expected  setting the limit to the max returned by the syscall package     on macos with go        and prior  it silently set it to the minimum of  limit max  and    we had to patch our code to explicitly check the actual value set instead of relying on no error returned since we falsely alloted more fds to databases than available     on macos with go      our code again started to blow up  now returning  invalid argument  errors instead of the silent capping previously     i d probably say both behaviors are bad  but the new one is a   lot   worse than the previous  now it only tells us it s invalid  but unless you know the magic number defined in the   your own kernel version    there s no way for user code to figure out how many fds are actually available ,1
353129,25103105059.0,IssuesEvent,2022-11-08 14:55:11,golang/go,https://api.github.com/repos/golang/go,closed,"net: make LookupCNAME consistent between Unix and Windows, document",Documentation OS-Windows Proposal Proposal-Accepted Proposal-FinalCommentPeriod,"LookupCNAME is pretty weird right now.

Despite the name, it entirely ignores CNAME records on Unix. It launches `A` and `AAAA` record lookups to recursive resolvers and returns the first response name found in the `A` and `AAAA`, skipping over any `CNAME`. (and not even asking for a `CNAME`)

But it documents that it does that...

https://pkg.go.dev/net#LookupCNAME

> A canonical name is the final name after following zero or more CNAME records. LookupCNAME does not return an error if host does not contain DNS ""CNAME"" records, as long as host resolves to address records.

OTOH, on Windows, it does what you would expect from the name itself: it looks up CNAME records:

```go
func (*Resolver) lookupCNAME(ctx context.Context, name string) (string, error) {
        // TODO(bradfitz): finish ctx plumbing. Nothing currently depends on this.
        acquireThread()
        defer releaseThread()
        var r *syscall.DNSRecord
        e := syscall.DnsQuery(name, syscall.DNS_TYPE_CNAME, 0, nil, &r, nil)
```

Here's a demo of a program behaving differently:

```go
func main() {
	txt, err := net.LookupTXT(""cname-to-txt.go4.org"")
	log.Printf(""LookupTXT = %q, %v"", txt, err)

	cname, err := net.LookupCNAME(""cname-to-txt.go4.org"")
	log.Printf(""cname = %q, %v"", cname, err)
}
```

On Linux/Mac:

```
2021/12/10 21:19:45 LookupTXT = [""foo=bar""], <nil>
2021/12/10 21:19:45 cname = """", lookup cname-to-txt.go4.org: no such host
```

On Windows:

```
2021/12/10 21:11:45 LookupTXT = [""foo=bar""], <nil>
2021/12/10 21:11:45 cname = ""test-txt-record.go4.org."", <nil>
```

I like the Windows behavior better, FWIW. That's what I was looking for, but apparently it doesn't exist.

Can we either:

1. add `LookupCNAMERecord` that actually looks up a CNAME record
2. redefine `LookupCNAME` to be like Windows, perhaps adding a `LookupCanonicalName` with the current weird Unix behavior of `LookupCNAME`?

But at minimum: document whatever the rules are and make Unix and Windows match? At least in `Resolver.PreferGo` mode?",1.0,"net: make LookupCNAME consistent between Unix and Windows, document - LookupCNAME is pretty weird right now.

Despite the name, it entirely ignores CNAME records on Unix. It launches `A` and `AAAA` record lookups to recursive resolvers and returns the first response name found in the `A` and `AAAA`, skipping over any `CNAME`. (and not even asking for a `CNAME`)

But it documents that it does that...

https://pkg.go.dev/net#LookupCNAME

> A canonical name is the final name after following zero or more CNAME records. LookupCNAME does not return an error if host does not contain DNS ""CNAME"" records, as long as host resolves to address records.

OTOH, on Windows, it does what you would expect from the name itself: it looks up CNAME records:

```go
func (*Resolver) lookupCNAME(ctx context.Context, name string) (string, error) {
        // TODO(bradfitz): finish ctx plumbing. Nothing currently depends on this.
        acquireThread()
        defer releaseThread()
        var r *syscall.DNSRecord
        e := syscall.DnsQuery(name, syscall.DNS_TYPE_CNAME, 0, nil, &r, nil)
```

Here's a demo of a program behaving differently:

```go
func main() {
	txt, err := net.LookupTXT(""cname-to-txt.go4.org"")
	log.Printf(""LookupTXT = %q, %v"", txt, err)

	cname, err := net.LookupCNAME(""cname-to-txt.go4.org"")
	log.Printf(""cname = %q, %v"", cname, err)
}
```

On Linux/Mac:

```
2021/12/10 21:19:45 LookupTXT = [""foo=bar""], <nil>
2021/12/10 21:19:45 cname = """", lookup cname-to-txt.go4.org: no such host
```

On Windows:

```
2021/12/10 21:11:45 LookupTXT = [""foo=bar""], <nil>
2021/12/10 21:11:45 cname = ""test-txt-record.go4.org."", <nil>
```

I like the Windows behavior better, FWIW. That's what I was looking for, but apparently it doesn't exist.

Can we either:

1. add `LookupCNAMERecord` that actually looks up a CNAME record
2. redefine `LookupCNAME` to be like Windows, perhaps adding a `LookupCanonicalName` with the current weird Unix behavior of `LookupCNAME`?

But at minimum: document whatever the rules are and make Unix and Windows match? At least in `Resolver.PreferGo` mode?",1,net  make lookupcname consistent between unix and windows  document   lookupcname is pretty weird right now     despite the name  it entirely ignores cname records on unix  it launches  a  and  aaaa  record lookups to recursive resolvers and returns the first response name found in the  a  and  aaaa   skipping over any  cname    and not even asking for a  cname      but it documents that it does that              a canonical name is the final name after following zero or more cname records  lookupcname does not return an error if host does not contain dns  cname  records  as long as host resolves to address records     otoh  on windows  it does what you would expect from the name itself  it looks up cname records        go  func   resolver  lookupcname ctx context context  name string   string  error                todo bradfitz   finish ctx plumbing  nothing currently depends on this           acquirethread            defer releasethread            var r  syscall dnsrecord          e    syscall dnsquery name  syscall dns type cname     nil   r  nil          here s a demo of a program behaving differently        go  func main      	txt  err    net lookuptxt  cname to txt   org    	log printf  lookuptxt    q   v   txt  err     	cname  err    net lookupcname  cname to txt   org    	log printf  cname    q   v   cname  err             on linux mac                      lookuptxt                     cname       lookup cname to txt   org  no such host         on windows                      lookuptxt                     cname    test txt record   org              i like the windows behavior better  fwiw  that s what i was looking for  but apparently it doesn t exist     can we either        add  lookupcnamerecord  that actually looks up a cname record     redefine  lookupcname  to be like windows  perhaps adding a  lookupcanonicalname  with the current weird unix behavior of  lookupcname      but at minimum  document whatever the rules are and make unix and windows match  at least in  resolver prefergo  mode ,1
175948,14546069068.0,IssuesEvent,2020-12-15 20:38:31,golang/go,https://api.github.com/repos/golang/go,closed,x/pkgsite: replace links to godoc.org in x/* repos,Documentation NeedsFix pkgsite,"A number of packages within x/ repos still link to self-documentation hosted on godoc.org (for example: x/tools/cmd/stringer, x/tools/cmd/present).  Given that the plan is to eventually redirect this traffic to pkg.go.dev (https://blog.golang.org/pkg.go.dev-2020), we should proactively update these links to point to pkg.go.dev.

CC @julieqiu ",1.0,"x/pkgsite: replace links to godoc.org in x/* repos - A number of packages within x/ repos still link to self-documentation hosted on godoc.org (for example: x/tools/cmd/stringer, x/tools/cmd/present).  Given that the plan is to eventually redirect this traffic to pkg.go.dev (https://blog.golang.org/pkg.go.dev-2020), we should proactively update these links to point to pkg.go.dev.

CC @julieqiu ",1,x pkgsite  replace links to godoc org in x   repos   a number of packages within x  repos still link to self documentation hosted on godoc org  for example  x tools cmd stringer  x tools cmd present    given that the plan is to eventually redirect this traffic to pkg go dev    we should proactively update these links to point to pkg go dev     cc  julieqiu ,1
311867,23408042280.0,IssuesEvent,2022-08-12 14:38:29,golang/go,https://api.github.com/repos/golang/go,closed,cmd/compile: Update compiler phases information in README,Documentation NeedsFix,"In the latest releases of go, it seems like step 2 `Type-checking and AST transformations` is nolonger happening in `cmd/compile/internal/gc` but instead starts from `cmd/compile/internal/noder` coupled with `cmd/compile/internal/types2`

I am proposing that the README is updated if necessary.


",1.0,"cmd/compile: Update compiler phases information in README - In the latest releases of go, it seems like step 2 `Type-checking and AST transformations` is nolonger happening in `cmd/compile/internal/gc` but instead starts from `cmd/compile/internal/noder` coupled with `cmd/compile/internal/types2`

I am proposing that the README is updated if necessary.


",1,cmd compile  update compiler phases information in readme   in the latest releases of go  it seems like step    type checking and ast transformations  is nolonger happening in  cmd compile internal gc  but instead starts from  cmd compile internal noder  coupled with  cmd compile internal       i am proposing that the readme is updated if necessary       ,1
101973,21890486707.0,IssuesEvent,2022-05-20 00:39:33,PreTeXtBook/pretext,https://api.github.com/repos/PreTeXtBook/pretext,opened,LaTeX: gracefully migrate to v3 of the siunitx package,code cleanup,"siunitx  released a v3 major upgrade.  Macro names have changed, etc.  Infrastructure is in place to handle v2 and v3 simultaneously.  So we can maybe define an internal macro (several) with different definitions in each case, to be the right macro from the package version.

https://github.com/PreTeXtBook/pretext/blob/abe66f6138c50a976c5a501d72c1f1df7acf024e/xsl/pretext-latex.xsl#L1059-L1075",1.0,"LaTeX: gracefully migrate to v3 of the siunitx package - siunitx  released a v3 major upgrade.  Macro names have changed, etc.  Infrastructure is in place to handle v2 and v3 simultaneously.  So we can maybe define an internal macro (several) with different definitions in each case, to be the right macro from the package version.

https://github.com/PreTeXtBook/pretext/blob/abe66f6138c50a976c5a501d72c1f1df7acf024e/xsl/pretext-latex.xsl#L1059-L1075",0,latex  gracefully migrate to   of the siunitx package   siunitx  released a   major upgrade   macro names have changed  etc   infrastructure is in place to handle   and   simultaneously   so we can maybe define an internal macro  several  with different definitions in each case  to be the right macro from the package version      ,0
60429,12110432026.0,IssuesEvent,2020-04-21 10:24:17,home-assistant/brands,https://api.github.com/repos/home-assistant/brands,closed,Flock is missing brand images,domain-missing has-codeowner,"


## The problem


The Flock integration does not have brand images in
this repository.

We recently started this Brands repository, to create a centralized storage of all brand-related images. These images are used on our website and the Home Assistant frontend.


The following images are missing and would ideally be added:

- `src/flock/icon.png`
- `src/flock/logo.png`
- `src/flock/icon@2x.png`
- `src/flock/logo@2x.png`

For image specifications and requirements, please see [README.md](https://github.com/home-assistant/brands/blob/master/README.md).
## Updating the documentation repository

Our documentation repository already has a logo for this integration, however, it does not meet the image requirements of this new Brands repository.

If adding images to this repository, please open up a PR to the documentation repository as well, removing the `logo: flock.png` line from this file:

<https://github.com/home-assistant/home-assistant.io/blob/current/source/_integrations/flock.markdown>

**Note**: The documentation PR needs to be opened against the `current` branch.
**Note2**: Please leave the actual logo file in the documentation repository. It will be cleaned up differently.


## Additional information

For more information about this repository, read the [README.md](https://github.com/home-assistant/brands/blob/master/README.md) file of this repository. It contains information on how this repository works, and image specification and requirements.


## Codeowner mention

Hi there, @fabaff! Mind taking a look at this issue as it is with an integration (flock) you are listed as a [codeowner](https://github.com/home-assistant/core/blob/dev/homeassistant/components/flock/manifest.json) for? Thanks!

Resolving this issue is not limited to codeowners! If you want to help us out, feel free to resolve this issue! Thanks already!
",1.0,"Flock is missing brand images - 


## The problem


The Flock integration does not have brand images in
this repository.

We recently started this Brands repository, to create a centralized storage of all brand-related images. These images are used on our website and the Home Assistant frontend.


The following images are missing and would ideally be added:

- `src/flock/icon.png`
- `src/flock/logo.png`
- `src/flock/icon@2x.png`
- `src/flock/logo@2x.png`

For image specifications and requirements, please see [README.md](https://github.com/home-assistant/brands/blob/master/README.md).
## Updating the documentation repository

Our documentation repository already has a logo for this integration, however, it does not meet the image requirements of this new Brands repository.

If adding images to this repository, please open up a PR to the documentation repository as well, removing the `logo: flock.png` line from this file:

<https://github.com/home-assistant/home-assistant.io/blob/current/source/_integrations/flock.markdown>

**Note**: The documentation PR needs to be opened against the `current` branch.
**Note2**: Please leave the actual logo file in the documentation repository. It will be cleaned up differently.


## Additional information

For more information about this repository, read the [README.md](https://github.com/home-assistant/brands/blob/master/README.md) file of this repository. It contains information on how this repository works, and image specification and requirements.


## Codeowner mention

Hi there, @fabaff! Mind taking a look at this issue as it is with an integration (flock) you are listed as a [codeowner](https://github.com/home-assistant/core/blob/dev/homeassistant/components/flock/manifest.json) for? Thanks!

Resolving this issue is not limited to codeowners! If you want to help us out, feel free to resolve this issue! Thanks already!
",0,flock is missing brand images         the problem   the flock integration does not have brand images in this repository   we recently started this brands repository  to create a centralized storage of all brand related images  these images are used on our website and the home assistant frontend    the following images are missing and would ideally be added      src flock icon png     src flock logo png     src flock icon   png     src flock logo   png   for image specifications and requirements  please see        updating the documentation repository  our documentation repository already has a logo for this integration  however  it does not meet the image requirements of this new brands repository   if adding images to this repository  please open up a pr to the documentation repository as well  removing the  logo  flock png  line from this file         note    the documentation pr needs to be opened against the  current  branch         please leave the actual logo file in the documentation repository  it will be cleaned up differently       additional information  for more information about this repository  read the     file of this repository  it contains information on how this repository works  and image specification and requirements       codeowner mention  hi there   fabaff  mind taking a look at this issue as it is with an integration  flock  you are listed as a     for  thanks   resolving this issue is not limited to codeowners  if you want to help us out  feel free to resolve this issue  thanks already  ,0
318739,23737822591.0,IssuesEvent,2022-08-31 09:39:21,golang/go,https://api.github.com/repos/golang/go,closed,net/http/pprof: document all available default profiles,Documentation NeedsFix,"The docs at the moment only mention a few of the available profiles.

See https://golang.org/pkg/net/http/pprof/

But there are plenty more:

```
var profileDescriptions = map[string]string{
  	""allocs"":       ""A sampling of all past memory allocations"",
  	""block"":        ""Stack traces that led to blocking on synchronization primitives"",
  	""cmdline"":      ""The command line invocation of the current program"",
  	""goroutine"":    ""Stack traces of all current goroutines"",
  	""heap"":         ""A sampling of memory allocations of live objects. You can specify the gc GET parameter to run GC before taking the heap sample."",
  	""mutex"":        ""Stack traces of holders of contended mutexes"",
  	""profile"":      ""CPU profile. You can specify the duration in the seconds GET parameter. After you get the profile file, use the go tool pprof command to investigate the profile."",
  	""threadcreate"": ""Stack traces that led to the creation of new OS threads"",
  	""trace"":        ""A trace of execution of the current program. You can specify the duration in the seconds GET parameter. After you get the trace file, use the go tool trace command to investigate the trace."",
  }
```

Should also document the behaviour of the `""debug""` query parameter controlling the response content type.",1.0,"net/http/pprof: document all available default profiles - The docs at the moment only mention a few of the available profiles.

See https://golang.org/pkg/net/http/pprof/

But there are plenty more:

```
var profileDescriptions = map[string]string{
  	""allocs"":       ""A sampling of all past memory allocations"",
  	""block"":        ""Stack traces that led to blocking on synchronization primitives"",
  	""cmdline"":      ""The command line invocation of the current program"",
  	""goroutine"":    ""Stack traces of all current goroutines"",
  	""heap"":         ""A sampling of memory allocations of live objects. You can specify the gc GET parameter to run GC before taking the heap sample."",
  	""mutex"":        ""Stack traces of holders of contended mutexes"",
  	""profile"":      ""CPU profile. You can specify the duration in the seconds GET parameter. After you get the profile file, use the go tool pprof command to investigate the profile."",
  	""threadcreate"": ""Stack traces that led to the creation of new OS threads"",
  	""trace"":        ""A trace of execution of the current program. You can specify the duration in the seconds GET parameter. After you get the trace file, use the go tool trace command to investigate the trace."",
  }
```

Should also document the behaviour of the `""debug""` query parameter controlling the response content type.",1,net http pprof  document all available default profiles   the docs at the moment only mention a few of the available profiles     see      but there are plenty more          var profiledescriptions   map string     	 allocs          a sampling of all past memory allocations      	 block           stack traces that led to blocking on synchronization primitives      	 cmdline         the command line invocation of the current program      	 goroutine       stack traces of all current goroutines      	 heap            a sampling of memory allocations of live objects  you can specify the gc get parameter to run gc before taking the heap sample       	 mutex           stack traces of holders of contended mutexes      	 profile         cpu profile  you can specify the duration in the seconds get parameter  after you get the profile file  use the go tool pprof command to investigate the profile       	 threadcreate    stack traces that led to the creation of new os threads      	 trace           a trace of execution of the current program  you can specify the duration in the seconds get parameter  after you get the trace file  use the go tool trace command to investigate the trace                 should also document the behaviour of the   debug   query parameter controlling the response content type ,1
70350,30639273959.0,IssuesEvent,2023-07-24 20:24:54,cityofaustin/atd-data-tech,https://api.github.com/repos/cityofaustin/atd-data-tech,opened,IT Support: [Fill in the action],Type: IT Support Service: Tech Services,"## Device & User Information (first name and last initial, no last names)
Martinez
## What's the problem?
Need to have the various former PWD teams test the link
\\coacd.org\dfstest\TPW
",2.0,"IT Support: [Fill in the action] - ## Device & User Information (first name and last initial, no last names)
Martinez
## What's the problem?
Need to have the various former PWD teams test the link
\\coacd.org\dfstest\TPW
",0,it support         device   user information  first name and last initial  no last names   martinez     what s the problem   need to have the various former pwd teams test the link    coacd org dfstest tpw  ,0
4983,2893770551.0,IssuesEvent,2015-06-15 19:43:53,golang/go,https://api.github.com/repos/golang/go,reopened,net/http: Server.Serve returns an error when the Listener is closed,Documentation,"net/http.Server.Serve returns an error when the Listener argument is closed, which means you cannot gracefully stop the server (no error returned). It should instead check if the Listener is closed and return nil if so.",1.0,"net/http: Server.Serve returns an error when the Listener is closed - net/http.Server.Serve returns an error when the Listener argument is closed, which means you cannot gracefully stop the server (no error returned). It should instead check if the Listener is closed and return nil if so.",1,net http  server serve returns an error when the listener is closed   net http server serve returns an error when the listener argument is closed  which means you cannot gracefully stop the server  no error returned   it should instead check if the listener is closed and return nil if so ,1
420330,12236538242.0,IssuesEvent,2020-05-04 16:30:25,LSCOIT/LegalNavigator,https://api.github.com/repos/LSCOIT/LegalNavigator,closed,Add Alaska Courts Systems to Alaska view of Legal Navigator,"Bug Glenn Guided Assist Priority: Medium Size: ""2""","Background: You had wondered if Alaska Court System could be added to bottom of the first page where it talks about “information you can trust” and lists LSC and probono.net.  As mentioned in 11, below, Alaska Court System is currently listed when a person gets a PAP.  It may be that is the place they plan to list state partners.

Issue submitted by Stacey Marz (AK)

See the output for Hawaii Action Plan.",1.0,"Add Alaska Courts Systems to Alaska view of Legal Navigator - Background: You had wondered if Alaska Court System could be added to bottom of the first page where it talks about “information you can trust” and lists LSC and probono.net.  As mentioned in 11, below, Alaska Court System is currently listed when a person gets a PAP.  It may be that is the place they plan to list state partners.

Issue submitted by Stacey Marz (AK)

See the output for Hawaii Action Plan.",0,add alaska courts systems to alaska view of legal navigator   background  you had wondered if alaska court system could be added to bottom of the first page where it talks about “information you can trust” and lists lsc and probono net   as mentioned in    below  alaska court system is currently listed when a person gets a pap   it may be that is the place they plan to list state partners     issue submitted by stacey marz  ak     see the output for hawaii action plan ,0
81458,10238938901.0,IssuesEvent,2019-08-19 17:00:58,golang/go,https://api.github.com/repos/golang/go,opened,"doc/go1.13: missing note about ""go build -o"" directory targets",Documentation NeedsFix release-blocker,"In  b48bda9 (#14295) `go build -o` was made to accept directory targets, and to build multiple binaries in that case. The behavior was updated in 081bc62 (#31296).

This is still described in `gotip help build`.

> The -o flag forces build to write the resulting executable or object to the named output file or directory, instead of the default behavior described in the last two paragraphs. If the named output is a directory that exists, then any resulting executables will be written to that directory.

This is missing from the release notes AFAICT.",1.0,"doc/go1.13: missing note about ""go build -o"" directory targets - In  b48bda9 (#14295) `go build -o` was made to accept directory targets, and to build multiple binaries in that case. The behavior was updated in 081bc62 (#31296).

This is still described in `gotip help build`.

> The -o flag forces build to write the resulting executable or object to the named output file or directory, instead of the default behavior described in the last two paragraphs. If the named output is a directory that exists, then any resulting executables will be written to that directory.

This is missing from the release notes AFAICT.",1,doc      missing note about  go build  o  directory targets   in          go build  o  was made to accept directory targets  and to build multiple binaries in that case  the behavior was updated in            this is still described in  gotip help build        the  o flag forces build to write the resulting executable or object to the named output file or directory  instead of the default behavior described in the last two paragraphs  if the named output is a directory that exists  then any resulting executables will be written to that directory     this is missing from the release notes afaict ,1
278886,30702419452.0,IssuesEvent,2023-07-27 01:28:36,Nivaskumark/CVE-2020-0074-frameworks_base,https://api.github.com/repos/Nivaskumark/CVE-2020-0074-frameworks_base,reopened,CVE-2020-0121 (Medium) detected in baseandroid-11.0.0_r39,Mend: dependency security vulnerability,"## CVE-2020-0121 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>baseandroid-11.0.0_r39</b></p></summary>
<p>

<p>Android framework classes and services</p>
<p>Library home page: <a href=https://android.googlesource.com/platform/frameworks/base>https://android.googlesource.com/platform/frameworks/base</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Nivaskumark/CVE-2020-0074-frameworks_base/commit/f63c00c11df9fe4c62ee2ed7d5f72e3a7ebec027"">f63c00c11df9fe4c62ee2ed7d5f72e3a7ebec027</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/services/core/java/com/android/server/appop/AppOpsService.java</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>  
  
In updateUidProcState of AppOpsService.java, there is a possible permission bypass due to a logic error. This could lead to local information disclosure of location data with User execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10Android ID: A-148180766

<p>Publish Date: 2020-06-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-0121>CVE-2020-0121</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: High
  - Integrity Impact: None
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://source.android.com/security/bulletin/2020-06-01"">https://source.android.com/security/bulletin/2020-06-01</a></p>
<p>Release Date: 2020-06-02</p>
<p>Fix Resolution: android-10.0.0_r37</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2020-0121 (Medium) detected in baseandroid-11.0.0_r39 - ## CVE-2020-0121 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>baseandroid-11.0.0_r39</b></p></summary>
<p>

<p>Android framework classes and services</p>
<p>Library home page: <a href=https://android.googlesource.com/platform/frameworks/base>https://android.googlesource.com/platform/frameworks/base</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/Nivaskumark/CVE-2020-0074-frameworks_base/commit/f63c00c11df9fe4c62ee2ed7d5f72e3a7ebec027"">f63c00c11df9fe4c62ee2ed7d5f72e3a7ebec027</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/services/core/java/com/android/server/appop/AppOpsService.java</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>  
  
In updateUidProcState of AppOpsService.java, there is a possible permission bypass due to a logic error. This could lead to local information disclosure of location data with User execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10Android ID: A-148180766

<p>Publish Date: 2020-06-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-0121>CVE-2020-0121</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: High
  - Integrity Impact: None
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://source.android.com/security/bulletin/2020-06-01"">https://source.android.com/security/bulletin/2020-06-01</a></p>
<p>Release Date: 2020-06-02</p>
<p>Fix Resolution: android-10.0.0_r37</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      medium  detected in baseandroid              cve       medium severity vulnerability     vulnerable library    baseandroid                android framework classes and services   library home page   a href    found in head commit   a href      found in base branch   master             vulnerable source files                  services core java com android server appop appopsservice java                    vulnerability details         in updateuidprocstate of appopsservice java  there is a possible permission bypass due to a logic error  this could lead to local information disclosure of location data with user execution privileges needed  user interaction is not needed for exploitation product  androidversions  android   id  a     publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  local     attack complexity  low     privileges required  low     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  none     availability impact  none   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  android                       step up your open source security game with mend    ,0
56042,8047425643.0,IssuesEvent,2018-08-01 00:36:01,golang/go,https://api.github.com/repos/golang/go,closed,cmd/go: go list and rooted paths,Documentation,"go help packages says:

```
An import path that is a rooted path or that begins with
a . or .. element is interpreted as a file system path and
denotes the package in that directory.
```

The way I interpret it is that

```
go list /home/manlio/go/github/perillo/goprint
```

should list the goprint package; however go list reports an error:

```
can't load package: package /home/manlio/go/src/github.com/perillo/goprint: import ""/home/manlio/go/src/github.com/perillo/goprint"": cannot import absolute path
```
",1.0,"cmd/go: go list and rooted paths - go help packages says:

```
An import path that is a rooted path or that begins with
a . or .. element is interpreted as a file system path and
denotes the package in that directory.
```

The way I interpret it is that

```
go list /home/manlio/go/github/perillo/goprint
```

should list the goprint package; however go list reports an error:

```
can't load package: package /home/manlio/go/src/github.com/perillo/goprint: import ""/home/manlio/go/src/github.com/perillo/goprint"": cannot import absolute path
```
",1,cmd go  go list and rooted paths   go help packages says       an import path that is a rooted path or that begins with a   or    element is interpreted as a file system path and denotes the package in that directory       the way i interpret it is that      go list  home manlio go github perillo goprint      should list the goprint package  however go list reports an error       can t load package  package  home manlio go src github com perillo goprint  import   home manlio go src github com perillo goprint   cannot import absolute path     ,1
781029,27419360856.0,IssuesEvent,2023-03-01 15:44:39,WordPress/openverse,https://api.github.com/repos/WordPress/openverse,opened,HMR is broken after the monorepo move,🟧 priority: high 🛠 goal: fix 🤖 aspect: dx 🧱 stack: frontend,"## Description

<!-- Concisely describe the bug. Compare your experience with what you expected to happen. -->
<!-- For example: ""I clicked the 'submit' button and instead of seeing a thank you message, I saw a blank page."" -->

## Reproduction

<!-- Provide detailed steps to reproduce the bug. -->

1. <!-- Step 1 ... -->Start the Nuxt app by running `just frontend/run dev`
2. <!-- Step 2 ... -->Delete one of the imports. The app will re-build and will show an error.
3. <!-- Step 3 ... -->Re-add the deleted import. The app should re-build and start working again.
4. See the build error:
```
in ./src/styles/tailwind.css (../node_modules/.pnpm/css-loader@5.2.7_webpack@4.46.0/node_modules/css-loader/dist/cjs.js??ref--4-oneOf-1-1!../node_modules/.pnpm/postcss-loader@4.3.0_4dftvqknpgmotzmzzqmnfvmmye/node_modules/postcss-loader/dist/cjs.js??ref--4-oneOf-1-2!./src/styles/tailwind.css)
Module build failed (from ../node_modules/.pnpm/postcss-loader@4.3.0_4dftvqknpgmotzmzzqmnfvmmye/node_modules/postcss-loader/dist/cjs.js):
SyntaxError
```

## Screenshots

<!-- Add screenshots to show the problem; or delete the section entirely. -->

## Environment

<!-- Please complete this, unless you are certain the problem is not environment specific. -->

- Device: <!-- (_eg._ iPhone Xs; laptop) -->
- OS: <!-- (_eg._ iOS 13.5; Fedora 32) -->
- Browser: <!-- (_eg._ Safari; Firefox) -->
- Version: <!-- (_eg._ 13; 73) -->
- Other info: <!-- (_eg._ display resolution, ease-of-access settings) -->

## Additional context

<!-- Add any other context about the problem here; or delete the section entirely. -->

<!-- If you would like to work on this, please comment below separately. -->
",1.0,"HMR is broken after the monorepo move - ## Description

<!-- Concisely describe the bug. Compare your experience with what you expected to happen. -->
<!-- For example: ""I clicked the 'submit' button and instead of seeing a thank you message, I saw a blank page."" -->

## Reproduction

<!-- Provide detailed steps to reproduce the bug. -->

1. <!-- Step 1 ... -->Start the Nuxt app by running `just frontend/run dev`
2. <!-- Step 2 ... -->Delete one of the imports. The app will re-build and will show an error.
3. <!-- Step 3 ... -->Re-add the deleted import. The app should re-build and start working again.
4. See the build error:
```
in ./src/styles/tailwind.css (../node_modules/.pnpm/css-loader@5.2.7_webpack@4.46.0/node_modules/css-loader/dist/cjs.js??ref--4-oneOf-1-1!../node_modules/.pnpm/postcss-loader@4.3.0_4dftvqknpgmotzmzzqmnfvmmye/node_modules/postcss-loader/dist/cjs.js??ref--4-oneOf-1-2!./src/styles/tailwind.css)
Module build failed (from ../node_modules/.pnpm/postcss-loader@4.3.0_4dftvqknpgmotzmzzqmnfvmmye/node_modules/postcss-loader/dist/cjs.js):
SyntaxError
```

## Screenshots

<!-- Add screenshots to show the problem; or delete the section entirely. -->

## Environment

<!-- Please complete this, unless you are certain the problem is not environment specific. -->

- Device: <!-- (_eg._ iPhone Xs; laptop) -->
- OS: <!-- (_eg._ iOS 13.5; Fedora 32) -->
- Browser: <!-- (_eg._ Safari; Firefox) -->
- Version: <!-- (_eg._ 13; 73) -->
- Other info: <!-- (_eg._ display resolution, ease-of-access settings) -->

## Additional context

<!-- Add any other context about the problem here; or delete the section entirely. -->

<!-- If you would like to work on this, please comment below separately. -->
",0,hmr is broken after the monorepo move      description               reproduction             start the nuxt app by running  just frontend run dev       delete one of the imports  the app will re build and will show an error       re add the deleted import  the app should re build and start working again      see the build error        in   src styles tailwind css     node modules  pnpm css loader       webpack       node modules css loader dist cjs js  ref    oneof        node modules  pnpm postcss loader         node modules postcss loader dist cjs js  ref    oneof       src styles tailwind css   module build failed  from    node modules  pnpm postcss loader         node modules postcss loader dist cjs js    syntaxerror            screenshots            environment           device       os       browser       version       other info          additional context            ,0
120176,17644026009.0,IssuesEvent,2021-08-20 01:29:46,AkshayMukkavilli/Tensorflow,https://api.github.com/repos/AkshayMukkavilli/Tensorflow,opened,CVE-2021-29619 (Medium) detected in tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl,security vulnerability,"## CVE-2021-29619 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl</b></p></summary>

<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href=""https://files.pythonhosted.org/packages/d2/ea/ab2c8c0e81bd051cc1180b104c75a865ab0fc66c89be992c4b20bbf6d624/tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl"">https://files.pythonhosted.org/packages/d2/ea/ab2c8c0e81bd051cc1180b104c75a865ab0fc66c89be992c4b20bbf6d624/tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl</a></p>
<p>Path to dependency file: /Tensorflow/src/requirements.txt</p>
<p>Path to vulnerable library: teSource-ArchiveExtractor_5ea86033-7612-4210-97f3-8edb65806ddf/20190525011619_2843/20190525011537_depth_0/2/tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64/tensorflow-1.13.1.data/purelib/tensorflow</p>
<p>

Dependency Hierarchy:
  - :x: **tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl** (Vulnerable Library)
</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. Passing invalid arguments (e.g., discovered via fuzzing) to `tf.raw_ops.SparseCountSparseOutput` results in segfault. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.

<p>Publish Date: 2021-05-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29619>CVE-2021-29619</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-wvjw-p9f5-vq28"">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-wvjw-p9f5-vq28</a></p>
<p>Release Date: 2021-05-14</p>
<p>Fix Resolution: tensorflow - 2.5.0, tensorflow-cpu - 2.5.0, tensorflow-gpu - 2.5.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-29619 (Medium) detected in tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl - ## CVE-2021-29619 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl</b></p></summary>

<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href=""https://files.pythonhosted.org/packages/d2/ea/ab2c8c0e81bd051cc1180b104c75a865ab0fc66c89be992c4b20bbf6d624/tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl"">https://files.pythonhosted.org/packages/d2/ea/ab2c8c0e81bd051cc1180b104c75a865ab0fc66c89be992c4b20bbf6d624/tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl</a></p>
<p>Path to dependency file: /Tensorflow/src/requirements.txt</p>
<p>Path to vulnerable library: teSource-ArchiveExtractor_5ea86033-7612-4210-97f3-8edb65806ddf/20190525011619_2843/20190525011537_depth_0/2/tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64/tensorflow-1.13.1.data/purelib/tensorflow</p>
<p>

Dependency Hierarchy:
  - :x: **tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl** (Vulnerable Library)
</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. Passing invalid arguments (e.g., discovered via fuzzing) to `tf.raw_ops.SparseCountSparseOutput` results in segfault. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.

<p>Publish Date: 2021-05-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29619>CVE-2021-29619</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-wvjw-p9f5-vq28"">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-wvjw-p9f5-vq28</a></p>
<p>Release Date: 2021-05-14</p>
<p>Fix Resolution: tensorflow - 2.5.0, tensorflow-cpu - 2.5.0, tensorflow-gpu - 2.5.0</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,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   tensorflow src requirements txt   path to vulnerable library  tesource archiveextractor                 depth     tensorflow                 tensorflow       data purelib tensorflow     dependency hierarchy       x    tensorflow                 whl    vulnerable library             vulnerability details         tensorflow is an end to end open source platform for machine learning  passing invalid arguments  e g   discovered via fuzzing  to  tf raw ops sparsecountsparseoutput  results in segfault  the fix will be included in tensorflow        we will also cherrypick this commit on tensorflow        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
665908,22334804896.0,IssuesEvent,2022-06-14 17:29:34,submariner-io/cloud-prepare,https://api.github.com/repos/submariner-io/cloud-prepare,closed,OSP: Subctl cloud prepare not happening sometimes,bug UX priority:high backport,"When running ""subctl cloud prepare osp ..."" on a fresh cluster, it properly configures the gateway node, creates the necessary Security Group rules and associates the SG to the nodes. However, if one of the existing nodes is already labelled as a gateway node and we run ""subctl cloud prepare osp ..."" it assumes that necessary steps are already done and is not associating the required Security Group rules on the nodes. 

Workaround:

- With `subctl` driven deployment:  delete the `submariner.io/gateway=true` label and re-run the `subctl cloud-prepare` command. 
- With ACM: uninstall the `submariner-addon` from the ManagedCluster and re-install it.",1.0,"OSP: Subctl cloud prepare not happening sometimes - When running ""subctl cloud prepare osp ..."" on a fresh cluster, it properly configures the gateway node, creates the necessary Security Group rules and associates the SG to the nodes. However, if one of the existing nodes is already labelled as a gateway node and we run ""subctl cloud prepare osp ..."" it assumes that necessary steps are already done and is not associating the required Security Group rules on the nodes. 

Workaround:

- With `subctl` driven deployment:  delete the `submariner.io/gateway=true` label and re-run the `subctl cloud-prepare` command. 
- With ACM: uninstall the `submariner-addon` from the ManagedCluster and re-install it.",0,osp  subctl cloud prepare not happening sometimes   when running  subctl cloud prepare osp      on a fresh cluster  it properly configures the gateway node  creates the necessary security group rules and associates the sg to the nodes  however  if one of the existing nodes is already labelled as a gateway node and we run  subctl cloud prepare osp      it assumes that necessary steps are already done and is not associating the required security group rules on the nodes      workaround       with  subctl  driven deployment   delete the  submariner io gateway true  label and re run the  subctl cloud prepare  command      with acm  uninstall the  submariner addon  from the managedcluster and re install it ,0
260201,22600375129.0,IssuesEvent,2022-06-29 08:36:37,bitlap/smt,https://api.github.com/repos/bitlap/smt,closed,Add benchmark for `@cacheEvict`,good first issue test,"1. redis cache
2. caffeine cache
3. no cache

refer to  #162
",1.0,"Add benchmark for `@cacheEvict` - 1. redis cache
2. caffeine cache
3. no cache

refer to  #162
",0,add benchmark for   cacheevict       redis cache     caffeine cache     no cache    refer to      ,0
255268,27484832893.0,IssuesEvent,2023-03-04 01:23:56,panasalap/linux-4.1.15,https://api.github.com/repos/panasalap/linux-4.1.15,opened,CVE-2020-27820 (Medium) detected in linuxlinux-4.1.17,security vulnerability,"## CVE-2020-27820 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.1.17</b></p></summary>
<p>

<p>Apache Software Foundation (ASF)</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/gpu/drm/nouveau/nouveau_drm.c</b>
</p>
</details>
<p></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>  
  
A vulnerability was found in Linux kernel, where a use-after-frees in nouveau's postclose() handler could happen if removing device (that is not common to remove video card physically without power-off, but same happens if ""unbind"" the driver).

<p>Publish Date: 2021-11-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-27820>CVE-2020-27820</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>4.7</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: High
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2020-27820"">https://nvd.nist.gov/vuln/detail/CVE-2020-27820</a></p>
<p>Release Date: 2021-11-03</p>
<p>Fix Resolution: linux-libc-headers - 5.13;linux-yocto - 5.4.20+gitAUTOINC+c11911d4d1_f4d7dbafb1,4.8.26+gitAUTOINC+1c60e003c7_27efc3ba68</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2020-27820 (Medium) detected in linuxlinux-4.1.17 - ## CVE-2020-27820 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.1.17</b></p></summary>
<p>

<p>Apache Software Foundation (ASF)</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/gpu/drm/nouveau/nouveau_drm.c</b>
</p>
</details>
<p></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>  
  
A vulnerability was found in Linux kernel, where a use-after-frees in nouveau's postclose() handler could happen if removing device (that is not common to remove video card physically without power-off, but same happens if ""unbind"" the driver).

<p>Publish Date: 2021-11-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-27820>CVE-2020-27820</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>4.7</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: High
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://nvd.nist.gov/vuln/detail/CVE-2020-27820"">https://nvd.nist.gov/vuln/detail/CVE-2020-27820</a></p>
<p>Release Date: 2021-11-03</p>
<p>Fix Resolution: linux-libc-headers - 5.13;linux-yocto - 5.4.20+gitAUTOINC+c11911d4d1_f4d7dbafb1,4.8.26+gitAUTOINC+1c60e003c7_27efc3ba68</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      medium  detected in linuxlinux            cve       medium severity vulnerability     vulnerable library    linuxlinux              apache software foundation  asf    library home page   a href     found in base branch   master             vulnerable source files                  drivers gpu drm nouveau nouveau drm c                    vulnerability details         a vulnerability was found in linux kernel  where a use after frees in nouveau s postclose   handler could happen if removing device  that is not common to remove video card physically without power off  but same happens if  unbind  the driver     publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  local     attack complexity  high     privileges required  low     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  linux libc headers       linux yocto         gitautoinc           gitautoinc                   step up your open source security game with mend    ,0
237120,26078809512.0,IssuesEvent,2022-12-25 01:18:13,n-devs/reactJSTest,https://api.github.com/repos/n-devs/reactJSTest,opened,CVE-2022-23540 (Medium) detected in jsonwebtoken-7.4.3.tgz,security vulnerability,"## CVE-2022-23540 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jsonwebtoken-7.4.3.tgz</b></p></summary>

<p>JSON Web Token implementation (symmetric and asymmetric)</p>
<p>Library home page: <a href=""https://registry.npmjs.org/jsonwebtoken/-/jsonwebtoken-7.4.3.tgz"">https://registry.npmjs.org/jsonwebtoken/-/jsonwebtoken-7.4.3.tgz</a></p>
<p>Path to dependency file: /reactJSTest/package.json</p>
<p>Path to vulnerable library: /node_modules/firebase-functions/node_modules/jsonwebtoken/package.json</p>
<p>

Dependency Hierarchy:
  - firebase-functions-0.5.9.tgz (Root Library)
    - :x: **jsonwebtoken-7.4.3.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
In versions `<=8.5.1` of `jsonwebtoken` library, lack of algorithm definition in the `jwt.verify()` function can lead to signature validation bypass due to defaulting to the `none` algorithm for signature verification. Users are affected if you do not specify algorithms in the `jwt.verify()` function. This issue has been fixed, please update to version 9.0.0 which removes the default support for the none algorithm in the `jwt.verify()` method. There will be no impact, if you update to version 9.0.0 and you don’t need to allow for the `none` algorithm. If you need 'none' algorithm, you have to explicitly specify that in `jwt.verify()` options.

<p>Publish Date: 2022-12-22
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23540>CVE-2022-23540</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.4</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: High
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://www.cve.org/CVERecord?id=CVE-2022-23540"">https://www.cve.org/CVERecord?id=CVE-2022-23540</a></p>
<p>Release Date: 2022-12-22</p>
<p>Fix Resolution: jsonwebtoken - 9.0.0</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2022-23540 (Medium) detected in jsonwebtoken-7.4.3.tgz - ## CVE-2022-23540 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jsonwebtoken-7.4.3.tgz</b></p></summary>

<p>JSON Web Token implementation (symmetric and asymmetric)</p>
<p>Library home page: <a href=""https://registry.npmjs.org/jsonwebtoken/-/jsonwebtoken-7.4.3.tgz"">https://registry.npmjs.org/jsonwebtoken/-/jsonwebtoken-7.4.3.tgz</a></p>
<p>Path to dependency file: /reactJSTest/package.json</p>
<p>Path to vulnerable library: /node_modules/firebase-functions/node_modules/jsonwebtoken/package.json</p>
<p>

Dependency Hierarchy:
  - firebase-functions-0.5.9.tgz (Root Library)
    - :x: **jsonwebtoken-7.4.3.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
In versions `<=8.5.1` of `jsonwebtoken` library, lack of algorithm definition in the `jwt.verify()` function can lead to signature validation bypass due to defaulting to the `none` algorithm for signature verification. Users are affected if you do not specify algorithms in the `jwt.verify()` function. This issue has been fixed, please update to version 9.0.0 which removes the default support for the none algorithm in the `jwt.verify()` method. There will be no impact, if you update to version 9.0.0 and you don’t need to allow for the `none` algorithm. If you need 'none' algorithm, you have to explicitly specify that in `jwt.verify()` options.

<p>Publish Date: 2022-12-22
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23540>CVE-2022-23540</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.4</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: Low
  - Integrity Impact: High
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://www.cve.org/CVERecord?id=CVE-2022-23540"">https://www.cve.org/CVERecord?id=CVE-2022-23540</a></p>
<p>Release Date: 2022-12-22</p>
<p>Fix Resolution: jsonwebtoken - 9.0.0</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      medium  detected in jsonwebtoken       tgz      cve       medium severity vulnerability     vulnerable library    jsonwebtoken       tgz      json web token implementation  symmetric and asymmetric    library home page   a href     path to dependency file   reactjstest package json   path to vulnerable library   node modules firebase functions node modules jsonwebtoken package json     dependency hierarchy      firebase functions       tgz  root library         x    jsonwebtoken       tgz    vulnerable library             vulnerability details         in versions           of  jsonwebtoken  library  lack of algorithm definition in the  jwt verify    function can lead to signature validation bypass due to defaulting to the  none  algorithm for signature verification  users are affected if you do not specify algorithms in the  jwt verify    function  this issue has been fixed  please update to version       which removes the default support for the none algorithm in the  jwt verify    method  there will be no impact  if you update to version       and you don’t need to allow for the  none  algorithm  if you need  none  algorithm  you have to explicitly specify that in  jwt verify    options    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  low     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  low     integrity impact  high     availability impact  low   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  jsonwebtoken                       step up your open source security game with mend    ,0
111837,24204720695.0,IssuesEvent,2022-09-25 03:33:42,Q1mi/BlogComments,https://api.github.com/repos/Q1mi/BlogComments,opened,Go单测从零到溜系列6—编写可测试的代码 | 李文周的博客,Gitalk ?code=0ff4e382ebe16397686,"https://www.liwenzhou.com/posts/Go/golang-unit-test-6/? 

 李文周的博客介绍了Go语言测试,单元测试怎么写,go test 执行测试,单元测试,SOLID原则,编写可测试的代码,单元测试教程,如何编写单元测试",1.0,"Go单测从零到溜系列6—编写可测试的代码 | 李文周的博客 - https://www.liwenzhou.com/posts/Go/golang-unit-test-6/? 

 李文周的博客介绍了Go语言测试,单元测试怎么写,go test 执行测试,单元测试,SOLID原则,编写可测试的代码,单元测试教程,如何编写单元测试",0, —编写可测试的代码   李文周的博客        李文周的博客介绍了go语言测试 单元测试怎么写 go test 执行测试 单元测试 solid原则 编写可测试的代码 单元测试教程 如何编写单元测试,0
586264,17573865364.0,IssuesEvent,2021-08-15 08:05:32,darktable-org/darktable,https://api.github.com/repos/darktable-org/darktable,closed,cannot use 'w' key on french keyboard,priority: high bug: pending,"
**Describe the bug/issue**

The w key seems dead.

**To Reproduce**
1. Go to 'shortcut' in preference
2. Double-click on any action
3. Clic on '`w`' to define this key as shortcut for the action 
4. See error, nothing happens
5. Clic on `atl+w` to define this key as shortcut for the action
6. See error, the key shortcut is defined as `alt+`

**Expected behavior**

The `w` key should be active and properly used to define a shortcut. 

**Platform**
* darktable version : current master
* OS                : Linux / GNOME 3.38
* Linux - Distro    : Debian/sid
",1.0,"cannot use 'w' key on french keyboard - 
**Describe the bug/issue**

The w key seems dead.

**To Reproduce**
1. Go to 'shortcut' in preference
2. Double-click on any action
3. Clic on '`w`' to define this key as shortcut for the action 
4. See error, nothing happens
5. Clic on `atl+w` to define this key as shortcut for the action
6. See error, the key shortcut is defined as `alt+`

**Expected behavior**

The `w` key should be active and properly used to define a shortcut. 

**Platform**
* darktable version : current master
* OS                : Linux / GNOME 3.38
* Linux - Distro    : Debian/sid
",0,cannot use  w  key on french keyboard       describe the bug issue      the w key seems dead       to reproduce       go to  shortcut  in preference     double click on any action     clic on   w   to define this key as shortcut for the action      see error  nothing happens     clic on  atl w  to define this key as shortcut for the action     see error  the key shortcut is defined as  alt        expected behavior      the  w  key should be active and properly used to define a shortcut        platform      darktable version   current master    os                  linux   gnome        linux   distro      debian sid  ,0
18206,12677715386.0,IssuesEvent,2020-06-19 08:18:59,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,There should be runtime error when using EditorPlugin in runtime,enhancement topic:core usability,"**Godot version:**
3.0.3

**Issue description:**
Since EditorPlugin can't be used in non-tools builds, there should be a runtime error in the editor when running a game using it. Not having this error can lead to potentially hard to debug problems on user ends when releasing the game (coming from #19649)

**Steps to reproduce:**
1. Create main scene of the project with a script
2.  Add such code in script ready function:
```
editorPlugin = EditorPlugin.new();
add_child(editorPlugin);
```
3. Run the scene, observe that there is no indication that something is not right
",True,"There should be runtime error when using EditorPlugin in runtime - **Godot version:**
3.0.3

**Issue description:**
Since EditorPlugin can't be used in non-tools builds, there should be a runtime error in the editor when running a game using it. Not having this error can lead to potentially hard to debug problems on user ends when releasing the game (coming from #19649)

**Steps to reproduce:**
1. Create main scene of the project with a script
2.  Add such code in script ready function:
```
editorPlugin = EditorPlugin.new();
add_child(editorPlugin);
```
3. Run the scene, observe that there is no indication that something is not right
",0,there should be runtime error when using editorplugin in runtime     godot version                issue description     since editorplugin can t be used in non tools builds  there should be a runtime error in the editor when running a game using it  not having this error can lead to potentially hard to debug problems on user ends when releasing the game  coming from          steps to reproduce        create main scene of the project with a script      add such code in script ready function        editorplugin   editorplugin new     add child editorplugin            run the scene  observe that there is no indication that something is not right  ,0
91958,26537680613.0,IssuesEvent,2023-01-19 16:46:20,NixOS/nixpkgs,https://api.github.com/repos/NixOS/nixpkgs,opened,Flutter vendorHashes are indeterministic,0.kind: enhancement 6.topic: reproducible builds,"Packages built with Flutter work at first, but drift away from the original `vendorHash` at some point. The cause of this issue has not been determined yet, but it increases maintenance burden and makes packages suddenly red, even without changes and therefore is of utmost importance.
**FluffyChat**, for example, **randomly broke** between 2022-08-11 and 2022-08-15, despite there being **no commits modifying it**: https://hydra.nixos.org/build/205552823


Some investigation already happened on https://github.com/NixOS/nixpkgs/pull/210287 by @NickCao. ",1.0,"Flutter vendorHashes are indeterministic - Packages built with Flutter work at first, but drift away from the original `vendorHash` at some point. The cause of this issue has not been determined yet, but it increases maintenance burden and makes packages suddenly red, even without changes and therefore is of utmost importance.
**FluffyChat**, for example, **randomly broke** between 2022-08-11 and 2022-08-15, despite there being **no commits modifying it**: https://hydra.nixos.org/build/205552823


Some investigation already happened on https://github.com/NixOS/nixpkgs/pull/210287 by @NickCao. ",0,flutter vendorhashes are indeterministic   packages built with flutter work at first  but drift away from the original  vendorhash  at some point  the cause of this issue has not been determined yet  but it increases maintenance burden and makes packages suddenly red  even without changes and therefore is of utmost importance     fluffychat    for example    randomly broke   between       and        despite there being   no commits modifying it           some investigation already happened on   by  nickcao  ,0
630388,20107827455.0,IssuesEvent,2022-02-07 12:19:42,space-wizards/space-station-14,https://api.github.com/repos/space-wizards/space-station-14,opened,IconSmoothing doesn't handle rotation events well,Type: Bug Priority: 2-Before Release Difficulty: 2-Medium,I used fixrotationms on an old map and all of the walls looked incorrect until they re-entered PVS again.,1.0,IconSmoothing doesn't handle rotation events well - I used fixrotationms on an old map and all of the walls looked incorrect until they re-entered PVS again.,0,iconsmoothing doesn t handle rotation events well   i used fixrotationms on an old map and all of the walls looked incorrect until they re entered pvs again ,0
155033,19765652772.0,IssuesEvent,2022-01-17 01:39:43,tuanducdesign/email-sending-verification,https://api.github.com/repos/tuanducdesign/email-sending-verification,closed,CVE-2021-23362 (Medium) detected in hosted-git-info-2.8.8.tgz,security vulnerability,"## CVE-2021-23362 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hosted-git-info-2.8.8.tgz</b></p></summary>

<p>Provides metadata and conversions from repository urls for Github, Bitbucket and Gitlab</p>
<p>Library home page: <a href=""https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.8.8.tgz"">https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.8.8.tgz</a></p>
<p>Path to dependency file: /client/package.json</p>
<p>Path to vulnerable library: /client/node_modules/hosted-git-info/package.json</p>
<p>

Dependency Hierarchy:
  - react-scripts-4.0.0.tgz (Root Library)
    - eslint-plugin-import-2.22.1.tgz
      - read-pkg-up-2.0.0.tgz
        - read-pkg-2.0.0.tgz
          - normalize-package-data-2.5.0.tgz
            - :x: **hosted-git-info-2.8.8.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/tuanducdesign/email-sending-verification/commit/32dadb9dc48a6a414ae10df3189fbc9fd128eac4"">32dadb9dc48a6a414ae10df3189fbc9fd128eac4</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>  
  
The package hosted-git-info before 3.0.8 are vulnerable to Regular Expression Denial of Service (ReDoS) via regular expression shortcutMatch in the fromUrl function in index.js. The affected regular expression exhibits polynomial worst-case time complexity.

<p>Publish Date: 2021-03-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23362>CVE-2021-23362</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/advisories/GHSA-43f8-2h32-f4cj"">https://github.com/advisories/GHSA-43f8-2h32-f4cj</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: hosted-git-info - 2.8.9,3.0.8</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-23362 (Medium) detected in hosted-git-info-2.8.8.tgz - ## CVE-2021-23362 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hosted-git-info-2.8.8.tgz</b></p></summary>

<p>Provides metadata and conversions from repository urls for Github, Bitbucket and Gitlab</p>
<p>Library home page: <a href=""https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.8.8.tgz"">https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.8.8.tgz</a></p>
<p>Path to dependency file: /client/package.json</p>
<p>Path to vulnerable library: /client/node_modules/hosted-git-info/package.json</p>
<p>

Dependency Hierarchy:
  - react-scripts-4.0.0.tgz (Root Library)
    - eslint-plugin-import-2.22.1.tgz
      - read-pkg-up-2.0.0.tgz
        - read-pkg-2.0.0.tgz
          - normalize-package-data-2.5.0.tgz
            - :x: **hosted-git-info-2.8.8.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href=""https://github.com/tuanducdesign/email-sending-verification/commit/32dadb9dc48a6a414ae10df3189fbc9fd128eac4"">32dadb9dc48a6a414ae10df3189fbc9fd128eac4</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>  
  
The package hosted-git-info before 3.0.8 are vulnerable to Regular Expression Denial of Service (ReDoS) via regular expression shortcutMatch in the fromUrl function in index.js. The affected regular expression exhibits polynomial worst-case time complexity.

<p>Publish Date: 2021-03-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23362>CVE-2021-23362</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: Low
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: None
  - Integrity Impact: None
  - Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://github.com/advisories/GHSA-43f8-2h32-f4cj"">https://github.com/advisories/GHSA-43f8-2h32-f4cj</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: hosted-git-info - 2.8.9,3.0.8</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      medium  detected in hosted git info       tgz      cve       medium severity vulnerability     vulnerable library    hosted git info       tgz      provides metadata and conversions from repository urls for github  bitbucket and gitlab   library home page   a href     path to dependency file   client package json   path to vulnerable library   client node modules hosted git info package json     dependency hierarchy      react scripts       tgz  root library        eslint plugin import       tgz         read pkg up       tgz           read pkg       tgz             normalize package data       tgz                x    hosted git info       tgz    vulnerable library   found in head commit   a href     found in base branch   master              vulnerability details         the package hosted git info before       are vulnerable to regular expression denial of service  redos  via regular expression shortcutmatch in the fromurl function in index js  the affected regular expression exhibits polynomial worst case time complexity    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  low     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  none     integrity impact  none     availability impact  low   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  hosted git info                             step up your open source security game with whitesource    ,0
29392,5631652496.0,IssuesEvent,2017-04-05 14:58:55,golang/go,https://api.github.com/repos/golang/go,closed,crypto/cipher: example legally but confusingly uses CryptBlocks input as its output,Documentation,"Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
1.8

### What operating system and processor architecture are you using (`go env`)?
GOARCH=""amd64""
GOBIN=""/usr/local/go/bin""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/tim/go""
GORACE=""""
GOROOT=""/usr/local/go""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/ny/78hxt5md5d9129ys2b43yq700000gn/T/go-build126828932=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
PKG_CONFIG=""pkg-config""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""

### What did you do?

Used the sample code in https://golang.org/src/crypto/cipher/example_test.go but didn't notice that ExampleNewCBCDecrypter used mode.CryptBlocks(ciphertext, ciphertext) effectively overwriting the source array.

### What did you expect to see?

The sample code should really be the most safe rather than the most performant. Something like:

```
// CryptBlocks can work in-place if the two arguments are the same (i.e. mode.CryptBlocks(ciphertext, ciphertext)) or can use a new array.
cleartext := make([]byte, len(ciphertext))
mode.CryptBlocks(cleartext, ciphertext)
```
### What did you see instead?

Add a new array, plaintext, that's the same size as ciphertext and have the comment say that mode.CryptBlocks(dst, src) can use the same array for both src and dst.",1.0,"crypto/cipher: example legally but confusingly uses CryptBlocks input as its output - Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
1.8

### What operating system and processor architecture are you using (`go env`)?
GOARCH=""amd64""
GOBIN=""/usr/local/go/bin""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/tim/go""
GORACE=""""
GOROOT=""/usr/local/go""
GOTOOLDIR=""/usr/local/go/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/ny/78hxt5md5d9129ys2b43yq700000gn/T/go-build126828932=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
PKG_CONFIG=""pkg-config""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""

### What did you do?

Used the sample code in https://golang.org/src/crypto/cipher/example_test.go but didn't notice that ExampleNewCBCDecrypter used mode.CryptBlocks(ciphertext, ciphertext) effectively overwriting the source array.

### What did you expect to see?

The sample code should really be the most safe rather than the most performant. Something like:

```
// CryptBlocks can work in-place if the two arguments are the same (i.e. mode.CryptBlocks(ciphertext, ciphertext)) or can use a new array.
cleartext := make([]byte, len(ciphertext))
mode.CryptBlocks(cleartext, ciphertext)
```
### What did you see instead?

Add a new array, plaintext, that's the same size as ciphertext and have the comment say that mode.CryptBlocks(dst, src) can use the same array for both src and dst.",1,crypto cipher  example legally but confusingly uses cryptblocks input as its output   please answer these questions before submitting your issue  thanks         what version of go are you using   go version                what operating system and processor architecture are you using   go env     goarch      gobin   usr local go bin   goexe     gohostarch      gohostos  darwin   goos  darwin   gopath   users tim go   gorace     goroot   usr local go   gotooldir   usr local go pkg tool darwin     gccgo  gccgo   cc  clang   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders ny   t go    tmp go build  gno record gcc switches  fno common   cxx  clang     cgo enabled      pkg config  pkg config   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g            what did you do     used the sample code in   but didn t notice that examplenewcbcdecrypter used mode cryptblocks ciphertext  ciphertext  effectively overwriting the source array         what did you expect to see     the sample code should really be the most safe rather than the most performant  something like             cryptblocks can work in place if the two arguments are the same  i e  mode cryptblocks ciphertext  ciphertext   or can use a new array   cleartext    make  byte  len ciphertext    mode cryptblocks cleartext  ciphertext            what did you see instead     add a new array  plaintext  that s the same size as ciphertext and have the comment say that mode cryptblocks dst  src  can use the same array for both src and dst ,1
717312,24670998538.0,IssuesEvent,2022-10-18 13:46:18,WordPress/openverse-frontend,https://api.github.com/repos/WordPress/openverse-frontend,closed,Content switcher mobile modal tabs and close button should have interaction styles,🟨 priority: medium ✨ goal: improvement 🕹 aspect: interface,"## Description
<!-- Concisely describe the bug. Compare your experience with what you expected to happen. -->
<!-- For example: ""I clicked the 'submit' button and instead of seeing a thank you message, I saw a blank page."" -->
The mobile content switcher modal needs to have interaction styles.

<img width=""386"" alt=""Screen Shot 2022-10-11 at 10 58 16 AM"" src=""https://user-images.githubusercontent.com/15233243/195032299-89b892af-bd16-4728-916a-f30ecdd91b76.png"">

The tabs need to have a `dark-charcoal-10` background on hover ([Figma mockup](https://www.figma.com/file/GIIQ4sDbaToCfFQyKMvzr8/Openverse-Design-Library?node-id=2960%3A8682))

<img width=""443"" alt=""Screen Shot 2022-10-11 at 10 52 47 AM"" src=""https://user-images.githubusercontent.com/15233243/195030998-196ad464-3ee4-4d1a-92eb-6f6d5ec3923c.png"">

Close button needs to have `dark-charcoal` background and white text on hover ([Figma mockup](https://www.figma.com/file/GIIQ4sDbaToCfFQyKMvzr8/Openverse-Design-Library?node-id=2956%3A6854)):

<img width=""198"" alt=""Screen Shot 2022-10-11 at 10 53 58 AM"" src=""https://user-images.githubusercontent.com/15233243/195031237-44fb12f1-36be-4292-8957-7bb35b25fc2f.png"">

## Resolution
<!-- Replace the [ ] with [x] to check the box. -->
- [x] 🙋 I would be interested in resolving this bug.
",1.0,"Content switcher mobile modal tabs and close button should have interaction styles - ## Description
<!-- Concisely describe the bug. Compare your experience with what you expected to happen. -->
<!-- For example: ""I clicked the 'submit' button and instead of seeing a thank you message, I saw a blank page."" -->
The mobile content switcher modal needs to have interaction styles.

<img width=""386"" alt=""Screen Shot 2022-10-11 at 10 58 16 AM"" src=""https://user-images.githubusercontent.com/15233243/195032299-89b892af-bd16-4728-916a-f30ecdd91b76.png"">

The tabs need to have a `dark-charcoal-10` background on hover ([Figma mockup](https://www.figma.com/file/GIIQ4sDbaToCfFQyKMvzr8/Openverse-Design-Library?node-id=2960%3A8682))

<img width=""443"" alt=""Screen Shot 2022-10-11 at 10 52 47 AM"" src=""https://user-images.githubusercontent.com/15233243/195030998-196ad464-3ee4-4d1a-92eb-6f6d5ec3923c.png"">

Close button needs to have `dark-charcoal` background and white text on hover ([Figma mockup](https://www.figma.com/file/GIIQ4sDbaToCfFQyKMvzr8/Openverse-Design-Library?node-id=2956%3A6854)):

<img width=""198"" alt=""Screen Shot 2022-10-11 at 10 53 58 AM"" src=""https://user-images.githubusercontent.com/15233243/195031237-44fb12f1-36be-4292-8957-7bb35b25fc2f.png"">

## Resolution
<!-- Replace the [ ] with [x] to check the box. -->
- [x] 🙋 I would be interested in resolving this bug.
",0,content switcher mobile modal tabs and close button should have interaction styles      description        the mobile content switcher modal needs to have interaction styles      img width     alt  screen shot       at       am  src       the tabs need to have a  dark charcoal    background on hover          img width     alt  screen shot       at       am  src       close button needs to have  dark charcoal  background and white text on hover          img width     alt  screen shot       at       am  src          resolution         🙋 i would be interested in resolving this bug   ,0
191444,6829015295.0,IssuesEvent,2017-11-08 22:29:30,tsgrp/OpenAnnotate,https://api.github.com/repos/tsgrp/OpenAnnotate,closed,"Highlight Annotations Cannot be ""reopened"" after using the new OK button",High Priority Issue,"Steps to reproduce:

1. Open a document with highlights in it.
1. Click on the highlight to bring up the dialog
1. Click on ""Ok"" button to dismiss the dialog
1. Try to click on the highlight again (hint: you can't...)

![issuegif3](https://user-images.githubusercontent.com/4850976/32556769-f0295b36-c465-11e7-905d-c8c4db189aec.gif)

Seems like if you just click off of the dialog rather than using the ""OK"" button that it works fine, so we are likely just not firing the right events when the ""ok button is clicked for the ""Highlight"" annotation type. Note: using the annotation summary always seems to work

Things to check while we are in there:
- [ ] All other annotation types
- [ ] It also seems like you cannot open this annotation as the ""first"" one that you click on when coming in for the first time. Once you open a different annotation, you can then open this one up.",1.0,"Highlight Annotations Cannot be ""reopened"" after using the new OK button - Steps to reproduce:

1. Open a document with highlights in it.
1. Click on the highlight to bring up the dialog
1. Click on ""Ok"" button to dismiss the dialog
1. Try to click on the highlight again (hint: you can't...)

![issuegif3](https://user-images.githubusercontent.com/4850976/32556769-f0295b36-c465-11e7-905d-c8c4db189aec.gif)

Seems like if you just click off of the dialog rather than using the ""OK"" button that it works fine, so we are likely just not firing the right events when the ""ok button is clicked for the ""Highlight"" annotation type. Note: using the annotation summary always seems to work

Things to check while we are in there:
- [ ] All other annotation types
- [ ] It also seems like you cannot open this annotation as the ""first"" one that you click on when coming in for the first time. Once you open a different annotation, you can then open this one up.",0,highlight annotations cannot be  reopened  after using the new ok button   steps to reproduce        open a document with highlights in it      click on the highlight to bring up the dialog     click on  ok  button to dismiss the dialog     try to click on the highlight again  hint  you can t                seems like if you just click off of the dialog rather than using the  ok  button that it works fine  so we are likely just not firing the right events when the  ok button is clicked for the  highlight  annotation type  note  using the annotation summary always seems to work    things to check while we are in there       all other annotation types      it also seems like you cannot open this annotation as the  first  one that you click on when coming in for the first time  once you open a different annotation  you can then open this one up ,0
33507,9166449284.0,IssuesEvent,2019-03-02 03:23:25,upaytech/as-server,https://api.github.com/repos/upaytech/as-server,opened,Create seeds for the database when docker container runs for the first time,Component: build infrastructure Difficulty: starter,"**Description**: Use [knex seeds](https://knexjs.org/#Seeds-CLI) to create the seed file in the src/config directory. Insert 1-3 records in all the tables.

**Reference**: Run the seed command in the `npm run dev` [script](https://github.com/upaytech/as-server/blob/master/package.json#L10). Can create a new script to keep the `dev` script lean.

**Another thing, please check if the seeds work properly on every `docker-compose up`. If there seems to be some issue with docker-compose, raise an issue related to that**",1.0,"Create seeds for the database when docker container runs for the first time - **Description**: Use [knex seeds](https://knexjs.org/#Seeds-CLI) to create the seed file in the src/config directory. Insert 1-3 records in all the tables.

**Reference**: Run the seed command in the `npm run dev` [script](https://github.com/upaytech/as-server/blob/master/package.json#L10). Can create a new script to keep the `dev` script lean.

**Another thing, please check if the seeds work properly on every `docker-compose up`. If there seems to be some issue with docker-compose, raise an issue related to that**",0,create seeds for the database when docker container runs for the first time     description    use     to create the seed file in the src config directory  insert     records in all the tables       reference    run the seed command in the  npm run dev      can create a new script to keep the  dev  script lean       another thing  please check if the seeds work properly on every  docker compose up   if there seems to be some issue with docker compose  raise an issue related to that  ,0
2541,2695314347.0,IssuesEvent,2015-04-02 03:54:14,golang/go,https://api.github.com/repos/golang/go,closed,go/ast: incorrect docs for Inspect,documentation repo-main,"I am not good in Engilsh.

The documents of ast.Inspect says:

```
If f returns true, Inspect invokes f  for all the non-nil children of node, recursively.
```

see the play http://play.golang.org/p/HID53LSwv_


",1.0,"go/ast: incorrect docs for Inspect - I am not good in Engilsh.

The documents of ast.Inspect says:

```
If f returns true, Inspect invokes f  for all the non-nil children of node, recursively.
```

see the play http://play.golang.org/p/HID53LSwv_


",1,go ast  incorrect docs for inspect   i am not good in engilsh     the documents of ast inspect says          if f returns true  inspect invokes f  for all the non nil children of node  recursively          see the play        ,1
172005,27218844844.0,IssuesEvent,2023-02-21 02:12:08,hackforla/tdm-calculator,https://api.github.com/repos/hackforla/tdm-calculator,closed,Additional functions after project submission,level: medium priority: SHOULD HAVE p-Feature - Final Summary Page pg 5 role: ui/ux design User Test #2 Team discussion needed p-Feature: print/download,"### Overview
Users wonder what can be done with the information after submission, add prompt to print, save as pdf, send via email, contacts for questions


### Action Items
- [x] #1313 - interim
- [ ] Mock up page 5 (separate to above) with a download PDF button (could be called print button - design decides)
- [ ] Mock up what PDF should like 

### Resources/Instructions
5/3/2022 Slide deck, slide no.10:
https://docs.google.com/presentation/d/1L-jjtspbw7Re_rNgncN0QRciu7iyxFicbGCSoMLzNbk/edit#slide=id.g126b7371ae7_1_270

###Zoom Recording Timestamp

00:36:10
https://drive.google.com/file/d/1eTkhtTLAsi5fJPOqUSCOB0k78pg-06oq/view | 

Video Transcription
[Video Transcription](https://docs.google.com/document/d/1W3p604ZOqW1B-Jpe65tiPuSBa7JhBV5IU6hG6u00SfQ/edit?usp=sharing)",1.0,"Additional functions after project submission - ### Overview
Users wonder what can be done with the information after submission, add prompt to print, save as pdf, send via email, contacts for questions


### Action Items
- [x] #1313 - interim
- [ ] Mock up page 5 (separate to above) with a download PDF button (could be called print button - design decides)
- [ ] Mock up what PDF should like 

### Resources/Instructions
5/3/2022 Slide deck, slide no.10:
https://docs.google.com/presentation/d/1L-jjtspbw7Re_rNgncN0QRciu7iyxFicbGCSoMLzNbk/edit#slide=id.g126b7371ae7_1_270

###Zoom Recording Timestamp

00:36:10
https://drive.google.com/file/d/1eTkhtTLAsi5fJPOqUSCOB0k78pg-06oq/view | 

Video Transcription
[Video Transcription](https://docs.google.com/document/d/1W3p604ZOqW1B-Jpe65tiPuSBa7JhBV5IU6hG6u00SfQ/edit?usp=sharing)",0,additional functions after project submission       overview  users wonder what can be done with the information after submission  add prompt to print  save as pdf  send via email  contacts for questions          action items           interim      mock up page    separate to above  with a download pdf button  could be called print button   design decides       mock up what pdf should like         resources instructions        slide deck  slide no             zoom recording timestamp                   video transcription     ,0
537098,15723054118.0,IssuesEvent,2021-03-29 06:54:49,kubesphere/kubesphere,https://api.github.com/repos/kubesphere/kubesphere,closed,The application repository cannot be deleted after the application is deployed through the application repository,area/app-management kind/bug priority/high,"
**Describe the Bug**

The application repository cannot be deleted after the application is deployed through the application repository
![image](https://user-images.githubusercontent.com/36271543/111132048-db4f9c80-85b3-11eb-9145-38c59f9a919a.png)

**steps:**
1. Deployed the application through the application repository 'repo1'
2. Delete application repository 'repo1'

**Expected results:**
The application repository 'repo1' can be deleted successfully

**Actual results:**
The repo could not be removed successfully; The following prompt message pops up: repo xxx has releases not deleted

/kind bug
/assign @xyz-li 
/priority high
/milestone 3.1.0
/area app-management",1.0,"The application repository cannot be deleted after the application is deployed through the application repository - 
**Describe the Bug**

The application repository cannot be deleted after the application is deployed through the application repository
![image](https://user-images.githubusercontent.com/36271543/111132048-db4f9c80-85b3-11eb-9145-38c59f9a919a.png)

**steps:**
1. Deployed the application through the application repository 'repo1'
2. Delete application repository 'repo1'

**Expected results:**
The application repository 'repo1' can be deleted successfully

**Actual results:**
The repo could not be removed successfully; The following prompt message pops up: repo xxx has releases not deleted

/kind bug
/assign @xyz-li 
/priority high
/milestone 3.1.0
/area app-management",0,the application repository cannot be deleted after the application is deployed through the application repository       describe the bug      the application repository cannot be deleted after the application is deployed through the application repository            steps        deployed the application through the application repository         delete application repository          expected results     the application repository     can be deleted successfully      actual results     the repo could not be removed successfully  the following prompt message pops up  repo xxx has releases not deleted     kind bug   assign  xyz li    priority high   milestone         area app management,0
228653,17468402250.0,IssuesEvent,2021-08-06 20:44:44,golang/go,https://api.github.com/repos/golang/go,closed,"doc: do not refer to ""lazy module loading""",Documentation NeedsFix release-blocker,"I think we agreed to call the new module logic something like ""fast module loading"" or ""reduced module graphs"" instead of ""lazy module loading"". The problem with ""lazy module loading"" is it will mean approximately nothing to anyone.

We need to fix the docs - at least /doc/go1.17 but maybe other places - before the actual release.

/cc @bcmills @jayconrod",1.0,"doc: do not refer to ""lazy module loading"" - I think we agreed to call the new module logic something like ""fast module loading"" or ""reduced module graphs"" instead of ""lazy module loading"". The problem with ""lazy module loading"" is it will mean approximately nothing to anyone.

We need to fix the docs - at least /doc/go1.17 but maybe other places - before the actual release.

/cc @bcmills @jayconrod",1,doc  do not refer to  lazy module loading    i think we agreed to call the new module logic something like  fast module loading  or  reduced module graphs  instead of  lazy module loading   the problem with  lazy module loading  is it will mean approximately nothing to anyone   we need to fix the docs   at least  doc     but maybe other places   before the actual release    cc  bcmills  jayconrod,1
824435,31156197876.0,IssuesEvent,2023-08-16 13:17:02,woowacourse-teams/2023-emmsale,https://api.github.com/repos/woowacourse-teams/2023-emmsale,closed,[FEAT] 프로필 조회 화면에서 차단 및 신고 기능 추가,안드로이드 기능 추가 Low Priority,"## 📌 어떤 기능인가요?
> 추가하려는 기능에 대해 간결하게 설명해주세요

프로필 조회 화면에서 차단 및 신고 기능 추가

## 📜 작업 상세 내용
- [ ] 차단하기 구현
- [ ] 신고하기 구현

## 예상 소요 시간
> 이슈를 완료하기까지 예상되는 소요 시간을 분 or 시간 or 일 단위로 작성해주세요.

4시간


## 🔍 참고할만한 자료(선택)
",1.0,"[FEAT] 프로필 조회 화면에서 차단 및 신고 기능 추가 - ## 📌 어떤 기능인가요?
> 추가하려는 기능에 대해 간결하게 설명해주세요

프로필 조회 화면에서 차단 및 신고 기능 추가

## 📜 작업 상세 내용
- [ ] 차단하기 구현
- [ ] 신고하기 구현

## 예상 소요 시간
> 이슈를 완료하기까지 예상되는 소요 시간을 분 or 시간 or 일 단위로 작성해주세요.

4시간


## 🔍 참고할만한 자료(선택)
",0,  프로필 조회 화면에서 차단 및 신고 기능 추가      📌 어떤 기능인가요     추가하려는 기능에 대해 간결하게 설명해주세요    프로필 조회 화면에서 차단 및 신고 기능 추가       📜 작업 상세 내용      차단하기 구현      신고하기 구현       예상 소요 시간    이슈를 완료하기까지 예상되는 소요 시간을 분 or 시간 or 일 단위로 작성해주세요               🔍 참고할만한 자료 선택   ,0
284158,30913598101.0,IssuesEvent,2023-08-05 02:21:15,hshivhare67/kernel_v4.19.72,https://api.github.com/repos/hshivhare67/kernel_v4.19.72,reopened,CVE-2020-8648 (High) detected in linuxlinux-4.19.282,Mend: dependency security vulnerability,"## CVE-2020-8648 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.19.282</b></p></summary>
<p>

<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/hshivhare67/kernel_v4.19.72/commit/139c4e073703974ca0b05255c4cff6dcd52a8e31"">139c4e073703974ca0b05255c4cff6dcd52a8e31</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/tty/vt/selection.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/tty/vt/selection.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>  
  
There is a use-after-free vulnerability in the Linux kernel through 5.5.2 in the n_tty_receive_buf_common function in drivers/tty/n_tty.c.

<p>Publish Date: 2020-02-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-8648>CVE-2020-8648</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.1</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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://www.linuxkernelcves.com/cves/CVE-2020-8648"">https://www.linuxkernelcves.com/cves/CVE-2020-8648</a></p>
<p>Release Date: 2020-02-06</p>
<p>Fix Resolution: v3.16.83,v4.14.173,v4.19.109,v4.4.216,v4.9.216,v5.4.25,v5.5.9,v5.6-rc3</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2020-8648 (High) detected in linuxlinux-4.19.282 - ## CVE-2020-8648 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.19.282</b></p></summary>
<p>

<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href=""https://github.com/hshivhare67/kernel_v4.19.72/commit/139c4e073703974ca0b05255c4cff6dcd52a8e31"">139c4e073703974ca0b05255c4cff6dcd52a8e31</a></p>

<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>

  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/tty/vt/selection.c</b>
  <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/tty/vt/selection.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>  
  
There is a use-after-free vulnerability in the Linux kernel through 5.5.2 in the n_tty_receive_buf_common function in drivers/tty/n_tty.c.

<p>Publish Date: 2020-02-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-8648>CVE-2020-8648</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.1</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Local
  - Attack Complexity: Low
  - Privileges Required: Low
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: 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://www.linuxkernelcves.com/cves/CVE-2020-8648"">https://www.linuxkernelcves.com/cves/CVE-2020-8648</a></p>
<p>Release Date: 2020-02-06</p>
<p>Fix Resolution: v3.16.83,v4.14.173,v4.19.109,v4.4.216,v4.9.216,v5.4.25,v5.5.9,v5.6-rc3</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      high  detected in linuxlinux            cve       high severity vulnerability     vulnerable library    linuxlinux              the linux kernel   library home page   a href    found in head commit   a href      found in base branch   master             vulnerable source files                  drivers tty vt selection c        drivers tty vt selection c                    vulnerability details         there is a use after free vulnerability in the linux kernel through       in the n tty receive buf common function in drivers tty n tty c    publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  local     attack complexity  low     privileges required  low     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  none     availability impact  high   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution                                                                step up your open source security game with mend    ,0
307839,23219161876.0,IssuesEvent,2022-08-02 16:29:09,golang/go,https://api.github.com/repos/golang/go,closed,doc: write Go 1.19 release notes,Documentation NeedsFix umbrella,"Tracking bug for writing the Go 1.19 Release Notes.

The latest state on tip can be viewed at https://tip.golang.org/doc/go1.19.

When the Go 1.19 Release Notes are complete, this should be closed, and a similar issue should be made for the next release. Previous issues are #47694, https://github.com/golang/go/issues/44513, https://github.com/golang/go/issues/40700, https://github.com/golang/go/issues/37419, https://github.com/golang/go/issues/36878, https://github.com/golang/go/issues/17929, https://github.com/golang/go/issues/15810, https://github.com/golang/go/issues/5929, etc.",1.0,"doc: write Go 1.19 release notes - Tracking bug for writing the Go 1.19 Release Notes.

The latest state on tip can be viewed at https://tip.golang.org/doc/go1.19.

When the Go 1.19 Release Notes are complete, this should be closed, and a similar issue should be made for the next release. Previous issues are #47694, https://github.com/golang/go/issues/44513, https://github.com/golang/go/issues/40700, https://github.com/golang/go/issues/37419, https://github.com/golang/go/issues/36878, https://github.com/golang/go/issues/17929, https://github.com/golang/go/issues/15810, https://github.com/golang/go/issues/5929, etc.",1,doc  write go     release notes   tracking bug for writing the go     release notes     the latest state on tip can be viewed at      when the go     release notes are complete  this should be closed  and a similar issue should be made for the next release  previous issues are                   etc ,1
80437,7747637773.0,IssuesEvent,2018-05-30 04:39:00,openbmc/openbmc-test-automation,https://api.github.com/repos/openbmc/openbmc-test-automation,closed,BMC file mirroring to ALT,Test,"```
root@witherspoon:~# ls /etc/synclist
/etc/synclist
root@witherspoon:~# cat /etc/synclist
/etc/dropbear/
/etc/group
/etc/gshadow
/etc/hostname
/etc/machine-id
/etc/passwd
/etc/shadow
/etc/ssl/
/etc/ssl/certs/nginx/
/etc/ssl/private/
/etc/systemd/network/
root@witherspoon:~# 

root@witherspoon:~# ls /media/alt/var/persist/etc/
group       group-      gshadow     gshadow-    machine-id  ssl         systemd
root@witherspoon:~# cat /etc/hostname
witherspoon

Modify hostname since its in the sync list and verify

```",1.0,"BMC file mirroring to ALT - ```
root@witherspoon:~# ls /etc/synclist
/etc/synclist
root@witherspoon:~# cat /etc/synclist
/etc/dropbear/
/etc/group
/etc/gshadow
/etc/hostname
/etc/machine-id
/etc/passwd
/etc/shadow
/etc/ssl/
/etc/ssl/certs/nginx/
/etc/ssl/private/
/etc/systemd/network/
root@witherspoon:~# 

root@witherspoon:~# ls /media/alt/var/persist/etc/
group       group-      gshadow     gshadow-    machine-id  ssl         systemd
root@witherspoon:~# cat /etc/hostname
witherspoon

Modify hostname since its in the sync list and verify

```",0,bmc file mirroring to alt        root witherspoon    ls  etc synclist   etc synclist  root witherspoon    cat  etc synclist   etc dropbear    etc group   etc gshadow   etc hostname   etc machine id   etc passwd   etc shadow   etc ssl    etc ssl certs nginx    etc ssl private    etc systemd network   root witherspoon        root witherspoon    ls  media alt var persist etc   group       group       gshadow     gshadow     machine id  ssl         systemd  root witherspoon    cat  etc hostname  witherspoon    modify hostname since its in the sync list and verify       ,0
5308,2921604600.0,IssuesEvent,2015-06-25 03:02:05,golang/go,https://api.github.com/repos/golang/go,closed,net/http: document that conn.Hijack might have left-over read/write timeouts on net.Conn,Documentation,"<pre>What does 'go version' print?

Found with go-1.2rc3, present in go-1.3, and still present in the default branch as of
20272:90616fa61ef4.

What steps reproduce the problem?

Setting a ReadTimeout or WriteTimeout on an http.Server and then hijacking a http.conn
(passed as the ResponseWriter) from a request handler leaves the deadlines set on the
connection.

This causes unexpected read and write behavior, requiring an unnatural removal of the
deadlines after hijacking. I found this while implementing the server half of the HTML5
EventSource API, and it also affects any other hijack users (e.g. go.net's websocket
package does not have code to clear deadlines when it takes over a connection; I have
not tested it though.)

A simplified example of the issue is here (probably useful to derive a regression test
from): <a href=""http://play.golang.org/p/bRyjSayMJN"">http://play.golang.org/p/bRyjSayMJN</a>

Adding these two lines fixes the issue:

diff -r 90616fa61ef4 src/pkg/net/http/server.go
--- a/src/pkg/net/http/server.go	Fri Jun 27 18:30:09 2014 -0700
+++ b/src/pkg/net/http/server.go	Fri Jun 27 22:43:18 2014 -0700
@@ -128,18 +128,20 @@
 func (c *conn) hijack() (rwc net.Conn, buf *bufio.ReadWriter, err error) {
 	c.mu.Lock()
 	defer c.mu.Unlock()
 	if c.hijackedv {
 		return nil, nil, ErrHijacked
 	}
 	if c.closeNotifyc != nil {
 		return nil, nil, errors.New(&quot;http: Hijack is incompatible with use of CloseNotifier&quot;)
 	}
+	c.rwc.SetReadDeadline(time.Time{})
+	c.rwc.SetWriteDeadline(time.Time{})
 	c.hijackedv = true
 	rwc = c.rwc
 	buf = c.buf
 	c.rwc = nil
 	c.buf = nil
 	c.setState(rwc, StateHijacked)
 	return
 }</pre>",1.0,"net/http: document that conn.Hijack might have left-over read/write timeouts on net.Conn - <pre>What does 'go version' print?

Found with go-1.2rc3, present in go-1.3, and still present in the default branch as of
20272:90616fa61ef4.

What steps reproduce the problem?

Setting a ReadTimeout or WriteTimeout on an http.Server and then hijacking a http.conn
(passed as the ResponseWriter) from a request handler leaves the deadlines set on the
connection.

This causes unexpected read and write behavior, requiring an unnatural removal of the
deadlines after hijacking. I found this while implementing the server half of the HTML5
EventSource API, and it also affects any other hijack users (e.g. go.net's websocket
package does not have code to clear deadlines when it takes over a connection; I have
not tested it though.)

A simplified example of the issue is here (probably useful to derive a regression test
from): <a href=""http://play.golang.org/p/bRyjSayMJN"">http://play.golang.org/p/bRyjSayMJN</a>

Adding these two lines fixes the issue:

diff -r 90616fa61ef4 src/pkg/net/http/server.go
--- a/src/pkg/net/http/server.go	Fri Jun 27 18:30:09 2014 -0700
+++ b/src/pkg/net/http/server.go	Fri Jun 27 22:43:18 2014 -0700
@@ -128,18 +128,20 @@
 func (c *conn) hijack() (rwc net.Conn, buf *bufio.ReadWriter, err error) {
 	c.mu.Lock()
 	defer c.mu.Unlock()
 	if c.hijackedv {
 		return nil, nil, ErrHijacked
 	}
 	if c.closeNotifyc != nil {
 		return nil, nil, errors.New(&quot;http: Hijack is incompatible with use of CloseNotifier&quot;)
 	}
+	c.rwc.SetReadDeadline(time.Time{})
+	c.rwc.SetWriteDeadline(time.Time{})
 	c.hijackedv = true
 	rwc = c.rwc
 	buf = c.buf
 	c.rwc = nil
 	c.buf = nil
 	c.setState(rwc, StateHijacked)
 	return
 }</pre>",1,net http  document that conn hijack might have left over read write timeouts on net conn    what does  go version  print   found with go      present in go      and still present in the default branch as of       what steps reproduce the problem   setting a readtimeout or writetimeout on an http server and then hijacking a http conn  passed as the responsewriter  from a request handler leaves the deadlines set on the connection   this causes unexpected read and write behavior  requiring an unnatural removal of the deadlines after hijacking  i found this while implementing the server half of the   eventsource api  and it also affects any other hijack users  e g  go net s websocket package does not have code to clear deadlines when it takes over a connection  i have not tested it though    a simplified example of the issue is here  probably useful to derive a regression test from    a href     adding these two lines fixes the issue   diff  r   src pkg net http server go     a src pkg net http server go	fri jun                  b src pkg net http server go	fri jun                               func  c  conn  hijack    rwc net conn  buf  bufio readwriter  err error     	c mu lock    	defer c mu unlock    	if c hijackedv    		return nil  nil  errhijacked  	   	if c closenotifyc    nil    		return nil  nil  errors new  quot http  hijack is incompatible with use of closenotifier quot    	   	c rwc setreaddeadline time time     	c rwc setwritedeadline time time     	c hijackedv   true  	rwc   c rwc  	buf   c buf  	c rwc   nil  	c buf   nil  	c setstate rwc  statehijacked   	return    ,1
71783,18874173880.0,IssuesEvent,2021-11-13 18:26:55,project-chip/connectedhomeip,https://api.github.com/repos/project-chip/connectedhomeip,closed,"Missing IPv6 Support on Docker for macOS Blocks CHIP Internet Layer Abstraction Testing and, Eventually, CHIP Protocol Testing",bug build issue p1 V1.0 stale,"#### Problem
Issue #213 and its related pull request are currently blocked because TestInetLayerEndPoint needs IPv6 support and Docker on macOS does not support (and has not supported) IPv6 per [this](https://github.com/docker/for-mac/issues/1432).

#### Proposed Solution
Unknown.
",1.0,"Missing IPv6 Support on Docker for macOS Blocks CHIP Internet Layer Abstraction Testing and, Eventually, CHIP Protocol Testing - #### Problem
Issue #213 and its related pull request are currently blocked because TestInetLayerEndPoint needs IPv6 support and Docker on macOS does not support (and has not supported) IPv6 per [this](https://github.com/docker/for-mac/issues/1432).

#### Proposed Solution
Unknown.
",0,missing   support on docker for macos blocks chip internet layer abstraction testing and  eventually  chip protocol testing        problem  issue    and its related pull request are currently blocked because testinetlayerendpoint needs   support and docker on macos does not support  and has not supported    per             proposed solution  unknown   ,0
67182,12886262642.0,IssuesEvent,2020-07-13 09:13:01,microsoft/azure-tools-for-java,https://api.github.com/repos/microsoft/azure-tools-for-java,closed,Unstable integration test for redis cache: Address already in use,Code Refactor P3 fixed integration-test internal redis,"testRedisCache(com.microsoft.tooling.msservices.serviceexplorer.azure.rediscache.RedisCacheIntegrationTest): java.lang.RuntimeException: java.net.BindException: Address already in use


```
[main] WARN org.eclipse.jetty.util.component.AbstractLifeCycle - FAILED NetworkTrafficServerConnector@4088702d{HTTP/1.1}{localhost:3306}: java.net.BindException: Address already in use
java.net.BindException: Address already in use
	at sun.nio.ch.Net.bind0(Native Method)
	at sun.nio.ch.Net.bind(Net.java:433)
	at sun.nio.ch.Net.bind(Net.java:425)
	at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
	at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
	at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:321)
	at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
	at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
	at org.eclipse.jetty.server.Server.doStart(Server.java:366)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
	at com.github.tomakehurst.wiremock.jetty9.JettyHttpServer.start(JettyHttpServer.java:130)
	at com.github.tomakehurst.wiremock.WireMockServer.start(WireMockServer.java:143)
	at com.github.tomakehurst.wiremock.junit.WireMockRule$1.evaluate(WireMockRule.java:68)
	at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl$PowerMockJUnit47MethodRunner.evaluateStatement(PowerMockJUnit47RunnerDelegateImpl.java:107)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl$PowerMockJUnit47MethodRunner.executeTest(PowerMockJUnit47RunnerDelegateImpl.java:82)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$PowerMockJUnit44MethodRunner.runBeforesThenTestThenAfters(PowerMockJUnit44RunnerDelegateImpl.java:282)
	at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:87)
	at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:50)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.invokeTestMethod(PowerMockJUnit44RunnerDelegateImpl.java:202)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.runMethods(PowerMockJUnit44RunnerDelegateImpl.java:144)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$1.run(PowerMockJUnit44RunnerDelegateImpl.java:118)
	at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:34)
	at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:44)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.run(PowerMockJUnit44RunnerDelegateImpl.java:120)
	at org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.run(JUnit4TestSuiteChunkerImpl.java:121)
	at org.powermock.modules.junit4.common.internal.impl.AbstractCommonPowerMockRunner.run(AbstractCommonPowerMockRunner.java:53)
	at org.powermock.modules.junit4.PowerMockRunner.run(PowerMockRunner.java:59)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
	at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
	at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
[main] WARN org.eclipse.jetty.util.component.AbstractLifeCycle - FAILED org.eclipse.jetty.server.Server@6636448b: java.net.BindException: Address already in use
java.net.BindException: Address already in use
	at sun.nio.ch.Net.bind0(Native Method)
	at sun.nio.ch.Net.bind(Net.java:433)
	at sun.nio.ch.Net.bind(Net.java:425)
	at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
	at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
	at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:321)
	at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
	at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
	at org.eclipse.jetty.server.Server.doStart(Server.java:366)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
	at com.github.tomakehurst.wiremock.jetty9.JettyHttpServer.start(JettyHttpServer.java:130)
	at com.github.tomakehurst.wiremock.WireMockServer.start(WireMockServer.java:143)
	at com.github.tomakehurst.wiremock.junit.WireMockRule$1.evaluate(WireMockRule.java:68)
	at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl$PowerMockJUnit47MethodRunner.evaluateStatement(PowerMockJUnit47RunnerDelegateImpl.java:107)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl$PowerMockJUnit47MethodRunner.executeTest(PowerMockJUnit47RunnerDelegateImpl.java:82)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$PowerMockJUnit44MethodRunner.runBeforesThenTestThenAfters(PowerMockJUnit44RunnerDelegateImpl.java:282)
	at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:87)
	at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:50)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.invokeTestMethod(PowerMockJUnit44RunnerDelegateImpl.java:202)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.runMethods(PowerMockJUnit44RunnerDelegateImpl.java:144)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$1.run(PowerMockJUnit44RunnerDelegateImpl.java:118)
	at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:34)
	at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:44)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.run(PowerMockJUnit44RunnerDelegateImpl.java:120)
	at org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.run(JUnit4TestSuiteChunkerImpl.java:121)
	at org.powermock.modules.junit4.common.internal.impl.AbstractCommonPowerMockRunner.run(AbstractCommonPowerMockRunner.java:53)
	at org.powermock.modules.junit4.PowerMockRunner.run(PowerMockRunner.java:59)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
	at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
	at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.84 sec <<< FAILURE!
testRedisCache(com.microsoft.tooling.msservices.serviceexplorer.azure.rediscache.RedisCacheIntegrationTest)  Time elapsed: 0.125 sec  <<< ERROR!
com.github.tomakehurst.wiremock.common.FatalStartupException: java.lang.RuntimeException: java.net.BindException: Address already in use
	at com.github.tomakehurst.wiremock.WireMockServer.start(WireMockServer.java:145)
	at com.github.tomakehurst.wiremock.junit.WireMockRule$1.evaluate(WireMockRule.java:68)
	at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl$PowerMockJUnit47MethodRunner.evaluateStatement(PowerMockJUnit47RunnerDelegateImpl.java:107)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl$PowerMockJUnit47MethodRunner.executeTest(PowerMockJUnit47RunnerDelegateImpl.java:82)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$PowerMockJUnit44MethodRunner.runBeforesThenTestThenAfters(PowerMockJUnit44RunnerDelegateImpl.java:282)
	at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:87)
	at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:50)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.invokeTestMethod(PowerMockJUnit44RunnerDelegateImpl.java:202)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.runMethods(PowerMockJUnit44RunnerDelegateImpl.java:144)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$1.run(PowerMockJUnit44RunnerDelegateImpl.java:118)
	at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:34)
	at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:44)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.run(PowerMockJUnit44RunnerDelegateImpl.java:120)
	at org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.run(JUnit4TestSuiteChunkerImpl.java:121)
	at org.powermock.modules.junit4.common.internal.impl.AbstractCommonPowerMockRunner.run(AbstractCommonPowerMockRunner.java:53)
	at org.powermock.modules.junit4.PowerMockRunner.run(PowerMockRunner.java:59)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
	at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
	at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
Caused by: java.lang.RuntimeException: java.net.BindException: Address already in use
	at com.github.tomakehurst.wiremock.jetty9.JettyHttpServer.start(JettyHttpServer.java:132)
	at com.github.tomakehurst.wiremock.WireMockServer.start(WireMockServer.java:143)
	... 28 more
Caused by: java.net.BindException: Address already in use
	at sun.nio.ch.Net.bind0(Native Method)
	at sun.nio.ch.Net.bind(Net.java:433)
	at sun.nio.ch.Net.bind(Net.java:425)
	at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
	at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
	at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:321)
	at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
	at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
	at org.eclipse.jetty.server.Server.doStart(Server.java:366)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
	at com.github.tomakehurst.wiremock.jetty9.JettyHttpServer.start(JettyHttpServer.java:130)
	... 29 more
Running com.microsoft.tooling.msservices.serviceexplorer.azure.rediscache.RedisExplorerIntegrationTest
[main] INFO org.eclipse.jetty.util.log - Logging initialized @34317ms
[main] INFO org.eclipse.jetty.server.Server - jetty-9.2.13.v20150730
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@620f7a39{/__admin,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@1715193f{/,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Started NetworkTrafficServerConnector@59b8ce1f{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.Server - Started @34514ms
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Stopped NetworkTrafficServerConnector@59b8ce1f{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@1715193f{/,null,UNAVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@620f7a39{/__admin,null,UNAVAILABLE}
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp375019897{STOPPING,8<=8<=10,i=4,q=4} Couldn't stop Thread[qtp375019897-192,5,]
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp375019897{STOPPING,8<=8<=10,i=0,q=3} Couldn't stop Thread[qtp375019897-193,5,]
[main] INFO org.eclipse.jetty.server.Server - jetty-9.2.13.v20150730
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@c7cbc2d{/__admin,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@48d14ea0{/,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Started NetworkTrafficServerConnector@21251e43{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.Server - Started @34826ms
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Stopped NetworkTrafficServerConnector@21251e43{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@48d14ea0{/,null,UNAVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@c7cbc2d{/__admin,null,UNAVAILABLE}
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp1436741771{STOPPING,8<=8<=10,i=0,q=5} Couldn't stop Thread[qtp1436741771-208,5,main]
[main] INFO org.eclipse.jetty.server.Server - jetty-9.2.13.v20150730
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@5f69462f{/__admin,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@560c3758{/,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Started NetworkTrafficServerConnector@43414b88{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.Server - Started @34948ms
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Stopped NetworkTrafficServerConnector@43414b88{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@560c3758{/,null,UNAVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@5f69462f{/__admin,null,UNAVAILABLE}
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp1060786847{STOPPING,8<=8<=10,i=5,q=7} Couldn't stop Thread[qtp1060786847-210,5,main]
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp1060786847{STOPPING,8<=8<=10,i=5,q=7} Couldn't stop Thread[qtp1060786847-211,5,main]
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp1060786847{STOPPING,8<=8<=10,i=4,q=7} Couldn't stop Thread[qtp1060786847-213,5,main]
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp1060786847{STOPPING,8<=8<=10,i=4,q=7} Couldn't stop Thread[qtp1060786847-217,5,main]
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp1060786847{STOPPING,8<=8<=10,i=4,q=7} Couldn't stop Thread[qtp1060786847-218,5,main]
[main] INFO org.eclipse.jetty.server.Server - jetty-9.2.13.v20150730
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@17e4beda{/__admin,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@61627c9d{/,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Started NetworkTrafficServerConnector@53c21c05{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.Server - Started @35021ms
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Stopped NetworkTrafficServerConnector@53c21c05{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@61627c9d{/,null,UNAVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@17e4beda{/__admin,null,UNAVAILABLE}
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp1477312973{STOPPING,8<=8<=10,i=3,q=6} Couldn't stop Thread[qtp1477312973-222,5,]
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp1477312973{STOPPING,8<=8<=10,i=0,q=5} Couldn't stop Thread[qtp1477312973-223,5,]
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp1477312973{STOPPING,8<=8<=10,i=0,q=5} Couldn't stop Thread[qtp1477312973-227,5,main]
[main] INFO org.eclipse.jetty.server.Server - jetty-9.2.13.v20150730
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@3f67f5ff{/__admin,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@20e7152a{/,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Started NetworkTrafficServerConnector@202fd4c4{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.Server - Started @35067ms
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Stopped NetworkTrafficServerConnector@202fd4c4{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@20e7152a{/,null,UNAVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@3f67f5ff{/__admin,null,UNAVAILABLE}
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp993640162{STOPPING,8<=8<=10,i=0,q=4} Couldn't stop Thread[qtp993640162-230,5,main]
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp993640162{STOPPING,8<=8<=10,i=0,q=4} Couldn't stop Thread[qtp993640162-236,5,main]
[main] INFO org.eclipse.jetty.server.Server - jetty-9.2.13.v20150730
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@27ea552d{/__admin,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@2be208db{/,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Started NetworkTrafficServerConnector@5ed463b7{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.Server - Started @35098ms
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Stopped NetworkTrafficServerConnector@5ed463b7{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@2be208db{/,null,UNAVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@27ea552d{/__admin,null,UNAVAILABLE}
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp1882802109{STOPPING,8<=8<=10,i=1,q=6} Couldn't stop Thread[qtp1882802109-238,5,]
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp1882802109{STOPPING,8<=8<=10,i=0,q=6} Couldn't stop Thread[qtp1882802109-240,5,]
[main] INFO org.eclipse.jetty.server.Server - jetty-9.2.13.v20150730
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@26361572{/__admin,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@33d08a24{/,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Started NetworkTrafficServerConnector@255b84a9{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.Server - Started @35145ms
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Stopped NetworkTrafficServerConnector@255b84a9{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@33d08a24{/,null,UNAVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@26361572{/__admin,null,UNAVAILABLE}
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp1609448604{STOPPING,8<=8<=10,i=0,q=1} Couldn't stop Thread[qtp1609448604-248-selector-ServerConnectorManager@46fc0556/1,5,main]
[main] INFO org.eclipse.jetty.server.Server - jetty-9.2.13.v20150730
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@9e4388d{/__admin,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@2a6871ad{/,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Started NetworkTrafficServerConnector@260043d{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.Server - Started @35206ms
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Stopped NetworkTrafficServerConnector@260043d{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@2a6871ad{/,null,UNAVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@9e4388d{/__admin,null,UNAVAILABLE}
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp552186123{STOPPING,8<=8<=10,i=0,q=4} Couldn't stop Thread[qtp552186123-256,5,]
[main] INFO org.eclipse.jetty.server.Server - jetty-9.2.13.v20150730
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@463746eb{/__admin,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@428e9be2{/,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Started NetworkTrafficServerConnector@3e729d46{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.Server - Started @35251ms
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Stopped NetworkTrafficServerConnector@3e729d46{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@428e9be2{/,null,UNAVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@463746eb{/__admin,null,UNAVAILABLE}
[main] INFO org.eclipse.jetty.server.Server - jetty-9.2.13.v20150730
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@1a3a6216{/__admin,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@dc24732{/,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Started NetworkTrafficServerConnector@44a1ae4e{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.Server - Started @35279ms
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Stopped NetworkTrafficServerConnector@44a1ae4e{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@dc24732{/,null,UNAVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@1a3a6216{/__admin,null,UNAVAILABLE}
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp684948803{STOPPING,8<=8<=10,i=0,q=5} Couldn't stop Thread[qtp684948803-281,5,main]
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.988 sec
Results :
Tests in error: 
  testRedisCache(com.microsoft.tooling.msservices.serviceexplorer.azure.rediscache.RedisCacheIntegrationTest): java.lang.RuntimeException: java.net.BindException: Address already in use
Tests run: 37, Failures: 0, Errors: 1, Skipped: 0
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test (default-test) on project azure-explorer-common: There are test failures.
[ERROR] 
[ERROR] Please refer to /home/travis/build/Microsoft/azure-tools-for-java/Utils/azure-explorer-common/target/surefire-reports for the individual test results.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :azure-explorer-common
```",1.0,"Unstable integration test for redis cache: Address already in use - testRedisCache(com.microsoft.tooling.msservices.serviceexplorer.azure.rediscache.RedisCacheIntegrationTest): java.lang.RuntimeException: java.net.BindException: Address already in use


```
[main] WARN org.eclipse.jetty.util.component.AbstractLifeCycle - FAILED NetworkTrafficServerConnector@4088702d{HTTP/1.1}{localhost:3306}: java.net.BindException: Address already in use
java.net.BindException: Address already in use
	at sun.nio.ch.Net.bind0(Native Method)
	at sun.nio.ch.Net.bind(Net.java:433)
	at sun.nio.ch.Net.bind(Net.java:425)
	at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
	at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
	at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:321)
	at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
	at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
	at org.eclipse.jetty.server.Server.doStart(Server.java:366)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
	at com.github.tomakehurst.wiremock.jetty9.JettyHttpServer.start(JettyHttpServer.java:130)
	at com.github.tomakehurst.wiremock.WireMockServer.start(WireMockServer.java:143)
	at com.github.tomakehurst.wiremock.junit.WireMockRule$1.evaluate(WireMockRule.java:68)
	at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl$PowerMockJUnit47MethodRunner.evaluateStatement(PowerMockJUnit47RunnerDelegateImpl.java:107)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl$PowerMockJUnit47MethodRunner.executeTest(PowerMockJUnit47RunnerDelegateImpl.java:82)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$PowerMockJUnit44MethodRunner.runBeforesThenTestThenAfters(PowerMockJUnit44RunnerDelegateImpl.java:282)
	at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:87)
	at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:50)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.invokeTestMethod(PowerMockJUnit44RunnerDelegateImpl.java:202)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.runMethods(PowerMockJUnit44RunnerDelegateImpl.java:144)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$1.run(PowerMockJUnit44RunnerDelegateImpl.java:118)
	at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:34)
	at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:44)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.run(PowerMockJUnit44RunnerDelegateImpl.java:120)
	at org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.run(JUnit4TestSuiteChunkerImpl.java:121)
	at org.powermock.modules.junit4.common.internal.impl.AbstractCommonPowerMockRunner.run(AbstractCommonPowerMockRunner.java:53)
	at org.powermock.modules.junit4.PowerMockRunner.run(PowerMockRunner.java:59)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
	at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
	at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
[main] WARN org.eclipse.jetty.util.component.AbstractLifeCycle - FAILED org.eclipse.jetty.server.Server@6636448b: java.net.BindException: Address already in use
java.net.BindException: Address already in use
	at sun.nio.ch.Net.bind0(Native Method)
	at sun.nio.ch.Net.bind(Net.java:433)
	at sun.nio.ch.Net.bind(Net.java:425)
	at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
	at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
	at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:321)
	at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
	at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
	at org.eclipse.jetty.server.Server.doStart(Server.java:366)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
	at com.github.tomakehurst.wiremock.jetty9.JettyHttpServer.start(JettyHttpServer.java:130)
	at com.github.tomakehurst.wiremock.WireMockServer.start(WireMockServer.java:143)
	at com.github.tomakehurst.wiremock.junit.WireMockRule$1.evaluate(WireMockRule.java:68)
	at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl$PowerMockJUnit47MethodRunner.evaluateStatement(PowerMockJUnit47RunnerDelegateImpl.java:107)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl$PowerMockJUnit47MethodRunner.executeTest(PowerMockJUnit47RunnerDelegateImpl.java:82)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$PowerMockJUnit44MethodRunner.runBeforesThenTestThenAfters(PowerMockJUnit44RunnerDelegateImpl.java:282)
	at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:87)
	at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:50)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.invokeTestMethod(PowerMockJUnit44RunnerDelegateImpl.java:202)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.runMethods(PowerMockJUnit44RunnerDelegateImpl.java:144)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$1.run(PowerMockJUnit44RunnerDelegateImpl.java:118)
	at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:34)
	at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:44)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.run(PowerMockJUnit44RunnerDelegateImpl.java:120)
	at org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.run(JUnit4TestSuiteChunkerImpl.java:121)
	at org.powermock.modules.junit4.common.internal.impl.AbstractCommonPowerMockRunner.run(AbstractCommonPowerMockRunner.java:53)
	at org.powermock.modules.junit4.PowerMockRunner.run(PowerMockRunner.java:59)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
	at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
	at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.84 sec <<< FAILURE!
testRedisCache(com.microsoft.tooling.msservices.serviceexplorer.azure.rediscache.RedisCacheIntegrationTest)  Time elapsed: 0.125 sec  <<< ERROR!
com.github.tomakehurst.wiremock.common.FatalStartupException: java.lang.RuntimeException: java.net.BindException: Address already in use
	at com.github.tomakehurst.wiremock.WireMockServer.start(WireMockServer.java:145)
	at com.github.tomakehurst.wiremock.junit.WireMockRule$1.evaluate(WireMockRule.java:68)
	at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl$PowerMockJUnit47MethodRunner.evaluateStatement(PowerMockJUnit47RunnerDelegateImpl.java:107)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl$PowerMockJUnit47MethodRunner.executeTest(PowerMockJUnit47RunnerDelegateImpl.java:82)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$PowerMockJUnit44MethodRunner.runBeforesThenTestThenAfters(PowerMockJUnit44RunnerDelegateImpl.java:282)
	at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:87)
	at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:50)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.invokeTestMethod(PowerMockJUnit44RunnerDelegateImpl.java:202)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.runMethods(PowerMockJUnit44RunnerDelegateImpl.java:144)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$1.run(PowerMockJUnit44RunnerDelegateImpl.java:118)
	at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:34)
	at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:44)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.run(PowerMockJUnit44RunnerDelegateImpl.java:120)
	at org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.run(JUnit4TestSuiteChunkerImpl.java:121)
	at org.powermock.modules.junit4.common.internal.impl.AbstractCommonPowerMockRunner.run(AbstractCommonPowerMockRunner.java:53)
	at org.powermock.modules.junit4.PowerMockRunner.run(PowerMockRunner.java:59)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
	at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
	at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
Caused by: java.lang.RuntimeException: java.net.BindException: Address already in use
	at com.github.tomakehurst.wiremock.jetty9.JettyHttpServer.start(JettyHttpServer.java:132)
	at com.github.tomakehurst.wiremock.WireMockServer.start(WireMockServer.java:143)
	... 28 more
Caused by: java.net.BindException: Address already in use
	at sun.nio.ch.Net.bind0(Native Method)
	at sun.nio.ch.Net.bind(Net.java:433)
	at sun.nio.ch.Net.bind(Net.java:425)
	at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
	at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
	at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:321)
	at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
	at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
	at org.eclipse.jetty.server.Server.doStart(Server.java:366)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
	at com.github.tomakehurst.wiremock.jetty9.JettyHttpServer.start(JettyHttpServer.java:130)
	... 29 more
Running com.microsoft.tooling.msservices.serviceexplorer.azure.rediscache.RedisExplorerIntegrationTest
[main] INFO org.eclipse.jetty.util.log - Logging initialized @34317ms
[main] INFO org.eclipse.jetty.server.Server - jetty-9.2.13.v20150730
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@620f7a39{/__admin,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@1715193f{/,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Started NetworkTrafficServerConnector@59b8ce1f{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.Server - Started @34514ms
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Stopped NetworkTrafficServerConnector@59b8ce1f{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@1715193f{/,null,UNAVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@620f7a39{/__admin,null,UNAVAILABLE}
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp375019897{STOPPING,8<=8<=10,i=4,q=4} Couldn't stop Thread[qtp375019897-192,5,]
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp375019897{STOPPING,8<=8<=10,i=0,q=3} Couldn't stop Thread[qtp375019897-193,5,]
[main] INFO org.eclipse.jetty.server.Server - jetty-9.2.13.v20150730
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@c7cbc2d{/__admin,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@48d14ea0{/,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Started NetworkTrafficServerConnector@21251e43{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.Server - Started @34826ms
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Stopped NetworkTrafficServerConnector@21251e43{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@48d14ea0{/,null,UNAVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@c7cbc2d{/__admin,null,UNAVAILABLE}
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp1436741771{STOPPING,8<=8<=10,i=0,q=5} Couldn't stop Thread[qtp1436741771-208,5,main]
[main] INFO org.eclipse.jetty.server.Server - jetty-9.2.13.v20150730
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@5f69462f{/__admin,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@560c3758{/,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Started NetworkTrafficServerConnector@43414b88{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.Server - Started @34948ms
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Stopped NetworkTrafficServerConnector@43414b88{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@560c3758{/,null,UNAVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@5f69462f{/__admin,null,UNAVAILABLE}
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp1060786847{STOPPING,8<=8<=10,i=5,q=7} Couldn't stop Thread[qtp1060786847-210,5,main]
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp1060786847{STOPPING,8<=8<=10,i=5,q=7} Couldn't stop Thread[qtp1060786847-211,5,main]
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp1060786847{STOPPING,8<=8<=10,i=4,q=7} Couldn't stop Thread[qtp1060786847-213,5,main]
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp1060786847{STOPPING,8<=8<=10,i=4,q=7} Couldn't stop Thread[qtp1060786847-217,5,main]
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp1060786847{STOPPING,8<=8<=10,i=4,q=7} Couldn't stop Thread[qtp1060786847-218,5,main]
[main] INFO org.eclipse.jetty.server.Server - jetty-9.2.13.v20150730
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@17e4beda{/__admin,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@61627c9d{/,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Started NetworkTrafficServerConnector@53c21c05{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.Server - Started @35021ms
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Stopped NetworkTrafficServerConnector@53c21c05{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@61627c9d{/,null,UNAVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@17e4beda{/__admin,null,UNAVAILABLE}
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp1477312973{STOPPING,8<=8<=10,i=3,q=6} Couldn't stop Thread[qtp1477312973-222,5,]
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp1477312973{STOPPING,8<=8<=10,i=0,q=5} Couldn't stop Thread[qtp1477312973-223,5,]
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp1477312973{STOPPING,8<=8<=10,i=0,q=5} Couldn't stop Thread[qtp1477312973-227,5,main]
[main] INFO org.eclipse.jetty.server.Server - jetty-9.2.13.v20150730
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@3f67f5ff{/__admin,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@20e7152a{/,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Started NetworkTrafficServerConnector@202fd4c4{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.Server - Started @35067ms
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Stopped NetworkTrafficServerConnector@202fd4c4{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@20e7152a{/,null,UNAVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@3f67f5ff{/__admin,null,UNAVAILABLE}
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp993640162{STOPPING,8<=8<=10,i=0,q=4} Couldn't stop Thread[qtp993640162-230,5,main]
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp993640162{STOPPING,8<=8<=10,i=0,q=4} Couldn't stop Thread[qtp993640162-236,5,main]
[main] INFO org.eclipse.jetty.server.Server - jetty-9.2.13.v20150730
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@27ea552d{/__admin,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@2be208db{/,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Started NetworkTrafficServerConnector@5ed463b7{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.Server - Started @35098ms
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Stopped NetworkTrafficServerConnector@5ed463b7{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@2be208db{/,null,UNAVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@27ea552d{/__admin,null,UNAVAILABLE}
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp1882802109{STOPPING,8<=8<=10,i=1,q=6} Couldn't stop Thread[qtp1882802109-238,5,]
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp1882802109{STOPPING,8<=8<=10,i=0,q=6} Couldn't stop Thread[qtp1882802109-240,5,]
[main] INFO org.eclipse.jetty.server.Server - jetty-9.2.13.v20150730
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@26361572{/__admin,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@33d08a24{/,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Started NetworkTrafficServerConnector@255b84a9{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.Server - Started @35145ms
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Stopped NetworkTrafficServerConnector@255b84a9{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@33d08a24{/,null,UNAVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@26361572{/__admin,null,UNAVAILABLE}
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp1609448604{STOPPING,8<=8<=10,i=0,q=1} Couldn't stop Thread[qtp1609448604-248-selector-ServerConnectorManager@46fc0556/1,5,main]
[main] INFO org.eclipse.jetty.server.Server - jetty-9.2.13.v20150730
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@9e4388d{/__admin,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@2a6871ad{/,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Started NetworkTrafficServerConnector@260043d{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.Server - Started @35206ms
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Stopped NetworkTrafficServerConnector@260043d{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@2a6871ad{/,null,UNAVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@9e4388d{/__admin,null,UNAVAILABLE}
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp552186123{STOPPING,8<=8<=10,i=0,q=4} Couldn't stop Thread[qtp552186123-256,5,]
[main] INFO org.eclipse.jetty.server.Server - jetty-9.2.13.v20150730
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@463746eb{/__admin,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@428e9be2{/,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Started NetworkTrafficServerConnector@3e729d46{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.Server - Started @35251ms
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Stopped NetworkTrafficServerConnector@3e729d46{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@428e9be2{/,null,UNAVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@463746eb{/__admin,null,UNAVAILABLE}
[main] INFO org.eclipse.jetty.server.Server - jetty-9.2.13.v20150730
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@1a3a6216{/__admin,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@dc24732{/,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Started NetworkTrafficServerConnector@44a1ae4e{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.Server - Started @35279ms
[main] INFO org.eclipse.jetty.server.NetworkTrafficServerConnector - Stopped NetworkTrafficServerConnector@44a1ae4e{HTTP/1.1}{localhost:3008}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@dc24732{/,null,UNAVAILABLE}
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@1a3a6216{/__admin,null,UNAVAILABLE}
[main] WARN org.eclipse.jetty.util.thread.QueuedThreadPool - qtp684948803{STOPPING,8<=8<=10,i=0,q=5} Couldn't stop Thread[qtp684948803-281,5,main]
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.988 sec
Results :
Tests in error: 
  testRedisCache(com.microsoft.tooling.msservices.serviceexplorer.azure.rediscache.RedisCacheIntegrationTest): java.lang.RuntimeException: java.net.BindException: Address already in use
Tests run: 37, Failures: 0, Errors: 1, Skipped: 0
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test (default-test) on project azure-explorer-common: There are test failures.
[ERROR] 
[ERROR] Please refer to /home/travis/build/Microsoft/azure-tools-for-java/Utils/azure-explorer-common/target/surefire-reports for the individual test results.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :azure-explorer-common
```",0,unstable integration test for redis cache  address already in use   testrediscache com microsoft tooling msservices serviceexplorer azure rediscache rediscacheintegrationtest   java lang runtimeexception  java net bindexception  address already in use             warn org eclipse jetty util component abstractlifecycle   failed networktrafficserverconnector   http      localhost     java net bindexception  address already in use  java net bindexception  address already in use  	at sun nio ch net   native method   	at sun nio ch net bind net java     	at sun nio ch net bind net java     	at sun nio ch serversocketchannelimpl bind serversocketchannelimpl java     	at sun nio ch serversocketadaptor bind serversocketadaptor java     	at org eclipse jetty server serverconnector open serverconnector java     	at org eclipse jetty server abstractnetworkconnector dostart abstractnetworkconnector java     	at org eclipse jetty server serverconnector dostart serverconnector java     	at org eclipse jetty util component abstractlifecycle start abstractlifecycle java     	at org eclipse jetty server server dostart server java     	at org eclipse jetty util component abstractlifecycle start abstractlifecycle java     	at com github tomakehurst wiremock   jettyhttpserver start jettyhttpserver java     	at com github tomakehurst wiremock wiremockserver start wiremockserver java     	at com github tomakehurst wiremock junit wiremockrule   evaluate wiremockrule java     	at org junit rules testwatcher   evaluate testwatcher java     	at org powermock modules   internal impl     evaluatestatement   java     	at org powermock modules   internal impl     executetest   java     	at org powermock modules   internal impl     runbeforesthentestthenafters   java     	at org junit internal runners methodroadie runtest methodroadie java     	at org junit internal runners methodroadie run methodroadie java     	at org powermock modules   internal impl   invoketestmethod   java     	at org powermock modules   internal impl   runmethods   java     	at org powermock modules   internal impl     run   java     	at org junit internal runners classroadie rununprotected classroadie java     	at org junit internal runners classroadie runprotected classroadie java     	at org powermock modules   internal impl   run   java     	at org powermock modules   common internal impl   run   java     	at org powermock modules   common internal impl abstractcommonpowermockrunner run abstractcommonpowermockrunner java     	at org powermock modules   powermockrunner run powermockrunner java     	at org apache maven surefire     execute   java     	at org apache maven surefire     executetestset   java     	at org apache maven surefire     invoke   java     	at sun reflect nativemethodaccessorimpl   native method   	at sun reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java     	at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java     	at java lang reflect method invoke method java     	at org apache maven surefire util reflectionutils invokemethodwitharray reflectionutils java     	at org apache maven surefire booter providerfactory providerproxy invoke providerfactory java     	at org apache maven surefire booter providerfactory invokeprovider providerfactory java     	at org apache maven surefire booter forkedbooter runsuitesinprocess forkedbooter java     	at org apache maven surefire booter forkedbooter main forkedbooter java       warn org eclipse jetty util component abstractlifecycle   failed org eclipse jetty server server    java net bindexception  address already in use  java net bindexception  address already in use  	at sun nio ch net   native method   	at sun nio ch net bind net java     	at sun nio ch net bind net java     	at sun nio ch serversocketchannelimpl bind serversocketchannelimpl java     	at sun nio ch serversocketadaptor bind serversocketadaptor java     	at org eclipse jetty server serverconnector open serverconnector java     	at org eclipse jetty server abstractnetworkconnector dostart abstractnetworkconnector java     	at org eclipse jetty server serverconnector dostart serverconnector java     	at org eclipse jetty util component abstractlifecycle start abstractlifecycle java     	at org eclipse jetty server server dostart server java     	at org eclipse jetty util component abstractlifecycle start abstractlifecycle java     	at com github tomakehurst wiremock   jettyhttpserver start jettyhttpserver java     	at com github tomakehurst wiremock wiremockserver start wiremockserver java     	at com github tomakehurst wiremock junit wiremockrule   evaluate wiremockrule java     	at org junit rules testwatcher   evaluate testwatcher java     	at org powermock modules   internal impl     evaluatestatement   java     	at org powermock modules   internal impl     executetest   java     	at org powermock modules   internal impl     runbeforesthentestthenafters   java     	at org junit internal runners methodroadie runtest methodroadie java     	at org junit internal runners methodroadie run methodroadie java     	at org powermock modules   internal impl   invoketestmethod   java     	at org powermock modules   internal impl   runmethods   java     	at org powermock modules   internal impl     run   java     	at org junit internal runners classroadie rununprotected classroadie java     	at org junit internal runners classroadie runprotected classroadie java     	at org powermock modules   internal impl   run   java     	at org powermock modules   common internal impl   run   java     	at org powermock modules   common internal impl abstractcommonpowermockrunner run abstractcommonpowermockrunner java     	at org powermock modules   powermockrunner run powermockrunner java     	at org apache maven surefire     execute   java     	at org apache maven surefire     executetestset   java     	at org apache maven surefire     invoke   java     	at sun reflect nativemethodaccessorimpl   native method   	at sun reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java     	at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java     	at java lang reflect method invoke method java     	at org apache maven surefire util reflectionutils invokemethodwitharray reflectionutils java     	at org apache maven surefire booter providerfactory providerproxy invoke providerfactory java     	at org apache maven surefire booter providerfactory invokeprovider providerfactory java     	at org apache maven surefire booter forkedbooter runsuitesinprocess forkedbooter java     	at org apache maven surefire booter forkedbooter main forkedbooter java     tests run     failures     errors     skipped     time elapsed      sec     failure   testrediscache com microsoft tooling msservices serviceexplorer azure rediscache rediscacheintegrationtest   time elapsed      sec      error   com github tomakehurst wiremock common fatalstartupexception  java lang runtimeexception  java net bindexception  address already in use  	at com github tomakehurst wiremock wiremockserver start wiremockserver java     	at com github tomakehurst wiremock junit wiremockrule   evaluate wiremockrule java     	at org junit rules testwatcher   evaluate testwatcher java     	at org powermock modules   internal impl     evaluatestatement   java     	at org powermock modules   internal impl     executetest   java     	at org powermock modules   internal impl     runbeforesthentestthenafters   java     	at org junit internal runners methodroadie runtest methodroadie java     	at org junit internal runners methodroadie run methodroadie java     	at org powermock modules   internal impl   invoketestmethod   java     	at org powermock modules   internal impl   runmethods   java     	at org powermock modules   internal impl     run   java     	at org junit internal runners classroadie rununprotected classroadie java     	at org junit internal runners classroadie runprotected classroadie java     	at org powermock modules   internal impl   run   java     	at org powermock modules   common internal impl   run   java     	at org powermock modules   common internal impl abstractcommonpowermockrunner run abstractcommonpowermockrunner java     	at org powermock modules   powermockrunner run powermockrunner java     	at org apache maven surefire     execute   java     	at org apache maven surefire     executetestset   java     	at org apache maven surefire     invoke   java     	at sun reflect nativemethodaccessorimpl   native method   	at sun reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java     	at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java     	at java lang reflect method invoke method java     	at org apache maven surefire util reflectionutils invokemethodwitharray reflectionutils java     	at org apache maven surefire booter providerfactory providerproxy invoke providerfactory java     	at org apache maven surefire booter providerfactory invokeprovider providerfactory java     	at org apache maven surefire booter forkedbooter runsuitesinprocess forkedbooter java     	at org apache maven surefire booter forkedbooter main forkedbooter java     caused by  java lang runtimeexception  java net bindexception  address already in use  	at com github tomakehurst wiremock   jettyhttpserver start jettyhttpserver java     	at com github tomakehurst wiremock wiremockserver start wiremockserver java     	      more  caused by  java net bindexception  address already in use  	at sun nio ch net   native method   	at sun nio ch net bind net java     	at sun nio ch net bind net java     	at sun nio ch serversocketchannelimpl bind serversocketchannelimpl java     	at sun nio ch serversocketadaptor bind serversocketadaptor java     	at org eclipse jetty server serverconnector open serverconnector java     	at org eclipse jetty server abstractnetworkconnector dostart abstractnetworkconnector java     	at org eclipse jetty server serverconnector dostart serverconnector java     	at org eclipse jetty util component abstractlifecycle start abstractlifecycle java     	at org eclipse jetty server server dostart server java     	at org eclipse jetty util component abstractlifecycle start abstractlifecycle java     	at com github tomakehurst wiremock   jettyhttpserver start jettyhttpserver java     	      more  running com microsoft tooling msservices serviceexplorer azure rediscache redisexplorerintegrationtest    info org eclipse jetty util log   logging initialized       info org eclipse jetty server server   jetty            info org eclipse jetty server handler contexthandler   started o e j s servletcontexthandler      admin null available     info org eclipse jetty server handler contexthandler   started o e j s servletcontexthandler     null available     info org eclipse jetty server networktrafficserverconnector   started networktrafficserverconnector   http      localhost       info org eclipse jetty server server   started       info org eclipse jetty server networktrafficserverconnector   stopped networktrafficserverconnector   http      localhost       info org eclipse jetty server handler contexthandler   stopped o e j s servletcontexthandler     null unavailable     info org eclipse jetty server handler contexthandler   stopped o e j s servletcontexthandler      admin null unavailable     warn org eclipse jetty util thread queuedthreadpool     stopping         i   q    couldn t stop thread     warn org eclipse jetty util thread queuedthreadpool     stopping         i   q    couldn t stop thread     info org eclipse jetty server server   jetty            info org eclipse jetty server handler contexthandler   started o e j s servletcontexthandler      admin null available     info org eclipse jetty server handler contexthandler   started o e j s servletcontexthandler     null available     info org eclipse jetty server networktrafficserverconnector   started networktrafficserverconnector   http      localhost       info org eclipse jetty server server   started       info org eclipse jetty server networktrafficserverconnector   stopped networktrafficserverconnector   http      localhost       info org eclipse jetty server handler contexthandler   stopped o e j s servletcontexthandler     null unavailable     info org eclipse jetty server handler contexthandler   stopped o e j s servletcontexthandler      admin null unavailable     warn org eclipse jetty util thread queuedthreadpool     stopping         i   q    couldn t stop thread     info org eclipse jetty server server   jetty            info org eclipse jetty server handler contexthandler   started o e j s servletcontexthandler      admin null available     info org eclipse jetty server handler contexthandler   started o e j s servletcontexthandler     null available     info org eclipse jetty server networktrafficserverconnector   started networktrafficserverconnector   http      localhost       info org eclipse jetty server server   started       info org eclipse jetty server networktrafficserverconnector   stopped networktrafficserverconnector   http      localhost       info org eclipse jetty server handler contexthandler   stopped o e j s servletcontexthandler     null unavailable     info org eclipse jetty server handler contexthandler   stopped o e j s servletcontexthandler      admin null unavailable     warn org eclipse jetty util thread queuedthreadpool     stopping         i   q    couldn t stop thread     warn org eclipse jetty util thread queuedthreadpool     stopping         i   q    couldn t stop thread     warn org eclipse jetty util thread queuedthreadpool     stopping         i   q    couldn t stop thread     warn org eclipse jetty util thread queuedthreadpool     stopping         i   q    couldn t stop thread     warn org eclipse jetty util thread queuedthreadpool     stopping         i   q    couldn t stop thread     info org eclipse jetty server server   jetty            info org eclipse jetty server handler contexthandler   started o e j s servletcontexthandler      admin null available     info org eclipse jetty server handler contexthandler   started o e j s servletcontexthandler     null available     info org eclipse jetty server networktrafficserverconnector   started networktrafficserverconnector   http      localhost       info org eclipse jetty server server   started       info org eclipse jetty server networktrafficserverconnector   stopped networktrafficserverconnector   http      localhost       info org eclipse jetty server handler contexthandler   stopped o e j s servletcontexthandler     null unavailable     info org eclipse jetty server handler contexthandler   stopped o e j s servletcontexthandler      admin null unavailable     warn org eclipse jetty util thread queuedthreadpool     stopping         i   q    couldn t stop thread     warn org eclipse jetty util thread queuedthreadpool     stopping         i   q    couldn t stop thread     warn org eclipse jetty util thread queuedthreadpool     stopping         i   q    couldn t stop thread     info org eclipse jetty server server   jetty            info org eclipse jetty server handler contexthandler   started o e j s servletcontexthandler      admin null available     info org eclipse jetty server handler contexthandler   started o e j s servletcontexthandler     null available     info org eclipse jetty server networktrafficserverconnector   started networktrafficserverconnector   http      localhost       info org eclipse jetty server server   started       info org eclipse jetty server networktrafficserverconnector   stopped networktrafficserverconnector   http      localhost       info org eclipse jetty server handler contexthandler   stopped o e j s servletcontexthandler     null unavailable     info org eclipse jetty server handler contexthandler   stopped o e j s servletcontexthandler      admin null unavailable     warn org eclipse jetty util thread queuedthreadpool     stopping         i   q    couldn t stop thread     warn org eclipse jetty util thread queuedthreadpool     stopping         i   q    couldn t stop thread     info org eclipse jetty server server   jetty            info org eclipse jetty server handler contexthandler   started o e j s servletcontexthandler      admin null available     info org eclipse jetty server handler contexthandler   started o e j s servletcontexthandler     null available     info org eclipse jetty server networktrafficserverconnector   started networktrafficserverconnector   http      localhost       info org eclipse jetty server server   started       info org eclipse jetty server networktrafficserverconnector   stopped networktrafficserverconnector   http      localhost       info org eclipse jetty server handler contexthandler   stopped o e j s servletcontexthandler     null unavailable     info org eclipse jetty server handler contexthandler   stopped o e j s servletcontexthandler      admin null unavailable     warn org eclipse jetty util thread queuedthreadpool     stopping         i   q    couldn t stop thread     warn org eclipse jetty util thread queuedthreadpool     stopping         i   q    couldn t stop thread     info org eclipse jetty server server   jetty            info org eclipse jetty server handler contexthandler   started o e j s servletcontexthandler      admin null available     info org eclipse jetty server handler contexthandler   started o e j s servletcontexthandler     null available     info org eclipse jetty server networktrafficserverconnector   started networktrafficserverconnector   http      localhost       info org eclipse jetty server server   started       info org eclipse jetty server networktrafficserverconnector   stopped networktrafficserverconnector   http      localhost       info org eclipse jetty server handler contexthandler   stopped o e j s servletcontexthandler     null unavailable     info org eclipse jetty server handler contexthandler   stopped o e j s servletcontexthandler      admin null unavailable     warn org eclipse jetty util thread queuedthreadpool     stopping         i   q    couldn t stop thread     info org eclipse jetty server server   jetty            info org eclipse jetty server handler contexthandler   started o e j s servletcontexthandler      admin null available     info org eclipse jetty server handler contexthandler   started o e j s servletcontexthandler     null available     info org eclipse jetty server networktrafficserverconnector   started networktrafficserverconnector   http      localhost       info org eclipse jetty server server   started       info org eclipse jetty server networktrafficserverconnector   stopped networktrafficserverconnector   http      localhost       info org eclipse jetty server handler contexthandler   stopped o e j s servletcontexthandler     null unavailable     info org eclipse jetty server handler contexthandler   stopped o e j s servletcontexthandler      admin null unavailable     warn org eclipse jetty util thread queuedthreadpool     stopping         i   q    couldn t stop thread     info org eclipse jetty server server   jetty            info org eclipse jetty server handler contexthandler   started o e j s servletcontexthandler      admin null available     info org eclipse jetty server handler contexthandler   started o e j s servletcontexthandler     null available     info org eclipse jetty server networktrafficserverconnector   started networktrafficserverconnector   http      localhost       info org eclipse jetty server server   started       info org eclipse jetty server networktrafficserverconnector   stopped networktrafficserverconnector   http      localhost       info org eclipse jetty server handler contexthandler   stopped o e j s servletcontexthandler     null unavailable     info org eclipse jetty server handler contexthandler   stopped o e j s servletcontexthandler      admin null unavailable     info org eclipse jetty server server   jetty            info org eclipse jetty server handler contexthandler   started o e j s servletcontexthandler      admin null available     info org eclipse jetty server handler contexthandler   started o e j s servletcontexthandler     null available     info org eclipse jetty server networktrafficserverconnector   started networktrafficserverconnector   http      localhost       info org eclipse jetty server server   started       info org eclipse jetty server networktrafficserverconnector   stopped networktrafficserverconnector   http      localhost       info org eclipse jetty server handler contexthandler   stopped o e j s servletcontexthandler     null unavailable     info org eclipse jetty server handler contexthandler   stopped o e j s servletcontexthandler      admin null unavailable     warn org eclipse jetty util thread queuedthreadpool     stopping         i   q    couldn t stop thread   tests run     failures     errors     skipped     time elapsed      sec  results    tests in error      testrediscache com microsoft tooling msservices serviceexplorer azure rediscache rediscacheintegrationtest   java lang runtimeexception  java net bindexception  address already in use  tests run     failures     errors     skipped       failed to execute goal org apache maven plugins maven surefire plugin       test  default test  on project azure explorer common  there are test failures         please refer to  home travis build microsoft azure tools for java utils azure explorer common target surefire reports for the individual test results                 to see the full stack trace of the errors  re run maven with the  e switch     re run maven using the  x switch to enable full debug logging         for more information about the errors and possible solutions  please read the following articles                after correcting the problems  you can resume the build with the command      mvn    rf  azure explorer common     ,0
333023,10114218783.0,IssuesEvent,2019-07-30 18:38:30,Templarian/MaterialDesign,https://api.github.com/repos/Templarian/MaterialDesign,closed,Add hulkhaugen as a Contributor,High Priority :grey_exclamation: Icon Request,"- [x] Add @hulkhaugen as contributor
- [x] twitter
- [x] website
- [x] github
- [x] short bio (like 250 words max).

---

Icons to assign:

- [ ] led-strip-variant (#3836)
- [ ] floor-lamp-variant (#3836)
- [ ] floor-lamp-dual (#3836)
- [ ] coach-lamp (#3836)
- [ ] outdoor-lamp (#3836)",1.0,"Add hulkhaugen as a Contributor - - [x] Add @hulkhaugen as contributor
- [x] twitter
- [x] website
- [x] github
- [x] short bio (like 250 words max).

---

Icons to assign:

- [ ] led-strip-variant (#3836)
- [ ] floor-lamp-variant (#3836)
- [ ] floor-lamp-dual (#3836)
- [ ] coach-lamp (#3836)
- [ ] outdoor-lamp (#3836)",0,add hulkhaugen as a contributor       add  hulkhaugen as contributor      twitter      website      github      short bio  like   words max             icons to assign         led strip variant           floor lamp variant           floor lamp dual           coach lamp           outdoor lamp     ,0
812425,30333768720.0,IssuesEvent,2023-07-11 08:16:48,2023-Summer-Bootcamp-Team-G/backend,https://api.github.com/repos/2023-Summer-Bootcamp-Team-G/backend,closed,[feat#2] 회원가입 API 구현,Priority: Low Status: Reviewing Type: Feature/Function,"## ✨ 구현 할 기능
- [ 회원가입 & 로그인 API 구현 ]
    ㄴ> POST Man을 통해 POST username, password를 입력해 회원가입과 로그인을 구현
    ㄴ> 회원가입을 하면 SQLite에 저장

<br>

### 📕 레퍼런스
",1.0,"[feat#2] 회원가입 API 구현 - ## ✨ 구현 할 기능
- [ 회원가입 & 로그인 API 구현 ]
    ㄴ> POST Man을 통해 POST username, password를 입력해 회원가입과 로그인을 구현
    ㄴ> 회원가입을 하면 SQLite에 저장

<br>

### 📕 레퍼런스
",0,  회원가입 api 구현      ✨ 구현 할 기능           ㄴ  post man을 통해 post username  password를 입력해 회원가입과 로그인을 구현      ㄴ  회원가입을 하면 sqlite에 저장             📕 레퍼런스  ,0
269231,8433631065.0,IssuesEvent,2018-10-17 07:55:22,webcompat/web-bugs,https://api.github.com/repos/webcompat/web-bugs,closed,tools.usps.com - site is not usable,browser-firefox-mobile priority-important,"<!-- @browser: Firefox Mobile 62.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:62.0) Gecko/62.0 Firefox/62.0 -->
<!-- @reported_with:  -->

**URL**: https://tools.usps.com/go/TrackConfirmAction.action?tLabels=9405511899223759559358

**Browser / Version**: Firefox Mobile 62.0
**Operating System**: Android
**Tested Another Browser**: Yes

**Problem type**: Site is not usable
**Description**: Package tracking site shows Access Denied
**Steps to Reproduce**:
Followed the given link from an email. Seems to work as expected in Fennec Nightly Android, but not in Focus Beta.

Access Denied
You don't have permission to access ""http://tools.usps.com/go/TrackConfirmAction.action?"" on this server.

Reference #18.6c03d417.1539449707.6fb1fa7 



_From [webcompat.com](https://webcompat.com/) with ❤️_",1.0,"tools.usps.com - site is not usable - <!-- @browser: Firefox Mobile 62.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:62.0) Gecko/62.0 Firefox/62.0 -->
<!-- @reported_with:  -->

**URL**: https://tools.usps.com/go/TrackConfirmAction.action?tLabels=9405511899223759559358

**Browser / Version**: Firefox Mobile 62.0
**Operating System**: Android
**Tested Another Browser**: Yes

**Problem type**: Site is not usable
**Description**: Package tracking site shows Access Denied
**Steps to Reproduce**:
Followed the given link from an email. Seems to work as expected in Fennec Nightly Android, but not in Focus Beta.

Access Denied
You don't have permission to access ""http://tools.usps.com/go/TrackConfirmAction.action?"" on this server.

Reference #18.6c03d417.1539449707.6fb1fa7 



_From [webcompat.com](https://webcompat.com/) with ❤️_",0,tools usps com   site is not usable            url         browser   version    firefox mobile       operating system    android   tested another browser    yes    problem type    site is not usable   description    package tracking site shows access denied   steps to reproduce    followed the given link from an email  seems to work as expected in fennec nightly android  but not in focus beta     access denied  you don t have permission to access    on this server     reference               from     with ❤️ ,0
425170,29194147352.0,IssuesEvent,2023-05-20 00:41:30,golang/go,https://api.github.com/repos/golang/go,closed,"net/http/pprof: missing documentation of the ""seconds"" parameter",Documentation help wanted NeedsFix compiler/runtime,"cc @aalexand

```
$ go version
Go 1.21-dev
```

### What did you do?

Navigate to https://pkg.go.dev/net/http/pprof and read.

### What did you expect to see?

I expected to see a mention of the ""seconds"" parameter for all profiles types that implement delta profiling:

https://github.com/golang/go/blob/508f445a28b08ed8c881572652c47139e669c19d/src/net/http/pprof/pprof.go#L341-L348

### What did you see instead?

No mention. This feature was first worked on in https://github.com/golang/go/issues/23401 AFAICT. It's been in Go for a while.",1.0,"net/http/pprof: missing documentation of the ""seconds"" parameter - cc @aalexand

```
$ go version
Go 1.21-dev
```

### What did you do?

Navigate to https://pkg.go.dev/net/http/pprof and read.

### What did you expect to see?

I expected to see a mention of the ""seconds"" parameter for all profiles types that implement delta profiling:

https://github.com/golang/go/blob/508f445a28b08ed8c881572652c47139e669c19d/src/net/http/pprof/pprof.go#L341-L348

### What did you see instead?

No mention. This feature was first worked on in https://github.com/golang/go/issues/23401 AFAICT. It's been in Go for a while.",1,net http pprof  missing documentation of the  seconds  parameter   cc  aalexand           go version  go     dev             what did you do     navigate to   and read         what did you expect to see     i expected to see a mention of the  seconds  parameter for all profiles types that implement delta profiling              what did you see instead     no mention  this feature was first worked on in   afaict  it s been in go for a while ,1
651080,21464793833.0,IssuesEvent,2022-04-26 01:47:02,Abumpus1/overlook,https://api.github.com/repos/Abumpus1/overlook,closed,Dashboard accessibility,priority: mid experience,"Accessibility audit on dashboard should be 100%
Should be able to use app without trackpad
ensure clarity for screenreaders (ARIA attributes where needed)",1.0,"Dashboard accessibility - Accessibility audit on dashboard should be 100%
Should be able to use app without trackpad
ensure clarity for screenreaders (ARIA attributes where needed)",0,dashboard accessibility   accessibility audit on dashboard should be     should be able to use app without trackpad  ensure clarity for screenreaders  aria attributes where needed ,0
211476,16446718086.0,IssuesEvent,2021-05-20 20:32:32,golang/go,https://api.github.com/repos/golang/go,opened,doc/go1.17: document go/parser changes for Go 1.17,Documentation NeedsFix release-blocker,"`+pkg go/parser, const SkipObjectResolution = 64                                                          
+pkg go/parser, const SkipObjectResolution Mode`

The `SkipObjectResolution` mode was added to allow skipping the object resolution phase of parsing.

CC @griesemer ",1.0,"doc/go1.17: document go/parser changes for Go 1.17 - `+pkg go/parser, const SkipObjectResolution = 64                                                          
+pkg go/parser, const SkipObjectResolution Mode`

The `SkipObjectResolution` mode was added to allow skipping the object resolution phase of parsing.

CC @griesemer ",1,doc      document go parser changes for go         pkg go parser  const skipobjectresolution                                                                 pkg go parser  const skipobjectresolution mode     the  skipobjectresolution  mode was added to allow skipping the object resolution phase of parsing     cc  griesemer ,1
20172,4511828037.0,IssuesEvent,2016-09-03 08:20:39,golang/go,https://api.github.com/repos/golang/go,opened,time: document when UnixNano overflows,Documentation,"When I use the UnixNano method, I have to do some math to discover that the value will overflow in the year 2262 (I never seem to remember this). While 2262 is very far out for most applications, perhaps we should document that is the maximum representable date as an int64 since Unix epoch?

I dont feel a need to do a similar statement in the Unix method since the overflow date for that is beyond anything reasonable.",1.0,"time: document when UnixNano overflows - When I use the UnixNano method, I have to do some math to discover that the value will overflow in the year 2262 (I never seem to remember this). While 2262 is very far out for most applications, perhaps we should document that is the maximum representable date as an int64 since Unix epoch?

I dont feel a need to do a similar statement in the Unix method since the overflow date for that is beyond anything reasonable.",1,time  document when unixnano overflows   when i use the unixnano method  i have to do some math to discover that the value will overflow in the year    i never seem to remember this   while   is very far out for most applications  perhaps we should document that is the maximum representable date as an   since unix epoch     i dont feel a need to do a similar statement in the unix method since the overflow date for that is beyond anything reasonable ,1
84609,16523227344.0,IssuesEvent,2021-05-26 16:42:06,mozilla/foundation.mozilla.org,https://api.github.com/repos/mozilla/foundation.mozilla.org,closed,"Determine whether we still need Tags for our content, given what we use them for.",backend code cleanup engineering,"In order to make the site more responsive, we need to tighten up our blog pages, including the tag code, but this raises questions about what we want to do with tags: we currently use them to decide what qualifies as ""related content"" for blog/campaigns/etc, but we don't surface those tags on the site in any way, so as far as users are concerned: tags don't exist.

If we're only using them to generate ""related content"" links, would it make more sense to let content editors explicitly set a number of related posts manually, on the admin side, similar to how PNI deals with related products?",1.0,"Determine whether we still need Tags for our content, given what we use them for. - In order to make the site more responsive, we need to tighten up our blog pages, including the tag code, but this raises questions about what we want to do with tags: we currently use them to decide what qualifies as ""related content"" for blog/campaigns/etc, but we don't surface those tags on the site in any way, so as far as users are concerned: tags don't exist.

If we're only using them to generate ""related content"" links, would it make more sense to let content editors explicitly set a number of related posts manually, on the admin side, similar to how PNI deals with related products?",0,determine whether we still need tags for our content  given what we use them for    in order to make the site more responsive  we need to tighten up our blog pages  including the tag code  but this raises questions about what we want to do with tags  we currently use them to decide what qualifies as  related content  for blog campaigns etc  but we don t surface those tags on the site in any way  so as far as users are concerned  tags don t exist     if we re only using them to generate  related content  links  would it make more sense to let content editors explicitly set a number of related posts manually  on the admin side  similar to how pni deals with related products ,0
130269,12425750074.0,IssuesEvent,2020-05-24 17:47:38,golang/go,https://api.github.com/repos/golang/go,closed,syscall/js: document more clearly how early js.Func can be released,Arch-Wasm Documentation NeedsFix OS-JS,"The documentation for [`js.Func`](https://pkg.go.dev/syscall/js#Func) currently says:

> Func.Release must be called to free up resources when the function will not be used any more.

> Release frees up resources allocated for the function. The function must not be invoked after calling Release.

Based on [a comment](https://go-review.googlesource.com/c/go/+/226204/2/src/net/http/roundtrip_js.go#113) from @neelance and my understanding of the code, it seems the intention is for it to be safe to release a `js.Func` at a time when no future invocations of the `js.Func` will be made. An invocation here means the time the execution begins. So, if a `js.Func` will only be invoked once, it is safe to release a `js.Func` right away in the Go function that will be executing:

```Go
var f js.Func
f = js.FuncOf(func(this js.Value, args []js.Value) interface{} {
    f.Release() // okay, even though this Go function is still in the middle of executing
    ...
```

I believe the documentation needs to make this more clear, so that users can rely on this behavior.

/cc @neelance @hajimehoshi @johanbrandhorst",1.0,"syscall/js: document more clearly how early js.Func can be released - The documentation for [`js.Func`](https://pkg.go.dev/syscall/js#Func) currently says:

> Func.Release must be called to free up resources when the function will not be used any more.

> Release frees up resources allocated for the function. The function must not be invoked after calling Release.

Based on [a comment](https://go-review.googlesource.com/c/go/+/226204/2/src/net/http/roundtrip_js.go#113) from @neelance and my understanding of the code, it seems the intention is for it to be safe to release a `js.Func` at a time when no future invocations of the `js.Func` will be made. An invocation here means the time the execution begins. So, if a `js.Func` will only be invoked once, it is safe to release a `js.Func` right away in the Go function that will be executing:

```Go
var f js.Func
f = js.FuncOf(func(this js.Value, args []js.Value) interface{} {
    f.Release() // okay, even though this Go function is still in the middle of executing
    ...
```

I believe the documentation needs to make this more clear, so that users can rely on this behavior.

/cc @neelance @hajimehoshi @johanbrandhorst",1,syscall js  document more clearly how early js func can be released   the documentation for     currently says       func release must be called to free up resources when the function will not be used any more       release frees up resources allocated for the function  the function must not be invoked after calling release     based on     from  neelance and my understanding of the code  it seems the intention is for it to be safe to release a  js func  at a time when no future invocations of the  js func  will be made  an invocation here means the time the execution begins  so  if a  js func  will only be invoked once  it is safe to release a  js func  right away in the go function that will be executing        go  var f js func  f   js funcof func this js value  args  js value  interface          f release      okay  even though this go function is still in the middle of executing                  i believe the documentation needs to make this more clear  so that users can rely on this behavior      cc  neelance  hajimehoshi  johanbrandhorst,1
259820,27728651864.0,IssuesEvent,2023-03-15 05:47:07,vasind/try-ember,https://api.github.com/repos/vasind/try-ember,closed,CVE-2022-0536 (Medium) detected in follow-redirects-1.11.0.tgz,security vulnerability no-issue-activity,"## CVE-2022-0536 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>follow-redirects-1.11.0.tgz</b></p></summary>

<p>HTTP and HTTPS modules that follow redirects.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.11.0.tgz"">https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.11.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/follow-redirects/package.json</p>
<p>

Dependency Hierarchy:
  - ember-cli-3.7.1.tgz (Root Library)
    - http-proxy-1.18.0.tgz
      - :x: **follow-redirects-1.11.0.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
Exposure of Sensitive Information to an Unauthorized Actor in NPM follow-redirects prior to 1.14.8.

<p>Publish Date: 2022-02-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-0536>CVE-2022-0536</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.9</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: None
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0536"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0536</a></p>
<p>Release Date: 2022-02-09</p>
<p>Fix Resolution (follow-redirects): 1.14.8</p>
<p>Direct dependency fix Resolution (ember-cli): 3.8.0</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2022-0536 (Medium) detected in follow-redirects-1.11.0.tgz - ## CVE-2022-0536 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>follow-redirects-1.11.0.tgz</b></p></summary>

<p>HTTP and HTTPS modules that follow redirects.</p>
<p>Library home page: <a href=""https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.11.0.tgz"">https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.11.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/follow-redirects/package.json</p>
<p>

Dependency Hierarchy:
  - ember-cli-3.7.1.tgz (Root Library)
    - http-proxy-1.18.0.tgz
      - :x: **follow-redirects-1.11.0.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>  
  
Exposure of Sensitive Information to an Unauthorized Actor in NPM follow-redirects prior to 1.14.8.

<p>Publish Date: 2022-02-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-0536>CVE-2022-0536</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.9</b>)</summary>
<p>

Base Score Metrics:
- Exploitability Metrics:
  - Attack Vector: Network
  - Attack Complexity: High
  - Privileges Required: None
  - User Interaction: None
  - Scope: Unchanged
- Impact Metrics:
  - Confidentiality Impact: High
  - Integrity Impact: None
  - Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href=""https://www.first.org/cvss/calculator/3.0"">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>

<p>Type: Upgrade version</p>
<p>Origin: <a href=""https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0536"">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0536</a></p>
<p>Release Date: 2022-02-09</p>
<p>Fix Resolution (follow-redirects): 1.14.8</p>
<p>Direct dependency fix Resolution (ember-cli): 3.8.0</p>

</p>
</details>
<p></p>

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve      medium  detected in follow redirects       tgz      cve       medium severity vulnerability     vulnerable library    follow redirects       tgz      http and https modules that follow redirects    library home page   a href     path to dependency file   package json   path to vulnerable library   node modules follow redirects package json     dependency hierarchy      ember cli       tgz  root library        http proxy       tgz          x    follow redirects       tgz    vulnerable library             vulnerability details         exposure of sensitive information to an unauthorized actor in npm follow redirects prior to          publish date         url   a href              cvss   score details             base score metrics    exploitability metrics      attack vector  network     attack complexity  high     privileges required  none     user interaction  none     scope  unchanged   impact metrics      confidentiality impact  high     integrity impact  none     availability impact  none   for more information on   scores  click  a href               suggested fix      type  upgrade version   origin   a href     release date          fix resolution  follow redirects           direct dependency fix resolution  ember cli                       step up your open source security game with mend    ,0
369754,25866816397.0,IssuesEvent,2022-12-13 21:41:26,golang/go,https://api.github.com/repos/golang/go,closed,x/net/websocket: remove Gorilla recommendation in docs,Documentation NeedsInvestigation,"### What version of Go are you using (`go version`)?
1.18

### Does this issue reproduce with the latest release?
No Issue


### What operating system and processor architecture are you using (`go env`)?


### What did you do?
Read the docs


### What did you expect to see?
How to use the x/net/websocket library


### What did you see instead?
https://github.com/golang/net/blob/e1ec361d0b39748d321472b2be7298211e05a3b6/websocket/websocket.go#L11
Gorilla recommendation which is now archived

",1.0,"x/net/websocket: remove Gorilla recommendation in docs - ### What version of Go are you using (`go version`)?
1.18

### Does this issue reproduce with the latest release?
No Issue


### What operating system and processor architecture are you using (`go env`)?


### What did you do?
Read the docs


### What did you expect to see?
How to use the x/net/websocket library


### What did you see instead?
https://github.com/golang/net/blob/e1ec361d0b39748d321472b2be7298211e05a3b6/websocket/websocket.go#L11
Gorilla recommendation which is now archived

",1,x net websocket  remove gorilla recommendation in docs       what version of go are you using   go version                does this issue reproduce with the latest release   no issue          what operating system and processor architecture are you using   go env             what did you do   read the docs          what did you expect to see   how to use the x net websocket library          what did you see instead      gorilla recommendation which is now archived    ,1
330790,28485820638.0,IssuesEvent,2023-04-18 07:48:06,unifyai/ivy,https://api.github.com/repos/unifyai/ivy,reopened,Fix jax_numpy_manipulation.test_jax_expand_dims,JAX Frontend Sub Task Failing Test,"|   |   |
|---|---|
|tensorflow|<a href=""https://github.com/unifyai/ivy/actions/runs/4586062504/jobs/8098629047"" rel=""noopener noreferrer"" target=""_blank""><img src=https://img.shields.io/badge/-failure-red></a>
|torch|<a href=""https://github.com/unifyai/ivy/actions/runs/4586062504/jobs/8098632534"" rel=""noopener noreferrer"" target=""_blank""><img src=https://img.shields.io/badge/-failure-red></a>
|numpy|<a href=""https://github.com/unifyai/ivy/actions/runs/4586154204/jobs/8098798549"" rel=""noopener noreferrer"" target=""_blank""><img src=https://img.shields.io/badge/-failure-red></a>
|jax|<a href=""https://github.com/unifyai/ivy/actions/runs/4586003022/jobs/8098526466"" rel=""noopener noreferrer"" target=""_blank""><img src=https://img.shields.io/badge/-failure-red></a>


<details>
<summary>Not found</summary>

Not found
</details>
<details>
<summary>Not found</summary>

Not found
</details>
<details>
<summary>Not found</summary>

Not found
</details>
<details>
<summary>Not found</summary>

Not found
</details>
",1.0,"Fix jax_numpy_manipulation.test_jax_expand_dims - |   |   |
|---|---|
|tensorflow|<a href=""https://github.com/unifyai/ivy/actions/runs/4586062504/jobs/8098629047"" rel=""noopener noreferrer"" target=""_blank""><img src=https://img.shields.io/badge/-failure-red></a>
|torch|<a href=""https://github.com/unifyai/ivy/actions/runs/4586062504/jobs/8098632534"" rel=""noopener noreferrer"" target=""_blank""><img src=https://img.shields.io/badge/-failure-red></a>
|numpy|<a href=""https://github.com/unifyai/ivy/actions/runs/4586154204/jobs/8098798549"" rel=""noopener noreferrer"" target=""_blank""><img src=https://img.shields.io/badge/-failure-red></a>
|jax|<a href=""https://github.com/unifyai/ivy/actions/runs/4586003022/jobs/8098526466"" rel=""noopener noreferrer"" target=""_blank""><img src=https://img.shields.io/badge/-failure-red></a>


<details>
<summary>Not found</summary>

Not found
</details>
<details>
<summary>Not found</summary>

Not found
</details>
<details>
<summary>Not found</summary>

Not found
</details>
<details>
<summary>Not found</summary>

Not found
</details>
",0,fix jax numpy manipulation test jax expand dims                          tensorflow   img src     torch   img src     numpy   img src     jax   img src            not found     not found         not found     not found         not found     not found         not found     not found     ,0
36547,6539270835.0,IssuesEvent,2017-09-01 10:22:56,golang/go,https://api.github.com/repos/golang/go,closed,strconv: incorrect rounding to nearest even,Documentation NeedsDecision,"The following statements
```
fmt.Printf(""x = %.1f\n"", 0.35)
fmt.Printf(""x = %.1f\n"", 0.45)
fmt.Printf(""x = %.1f\n"", 0.55)
fmt.Printf(""x = %.1f\n"", 0.65)
```
produce
```
x = 0.3
x = 0.5
x = 0.6
x = 0.7
```
(https://play.golang.org/p/kLC7Ap0cpP).

However, assuming rounding to nearest even, one would expect the result to be
```
x = 0.4
x = 0.4
x = 0.6
x = 0.6
```
(The examples use fmt.Printf but the culprit is in the underlying strconv code. The documentation doesn't explicitly state that it rounds to nearest even, but that is definitively the intent of the implementation which contains code and comments to that effect.).

The problem of course is that these numbers cannot be accurately represented in binary form and when it comes to the rounding decision, what should be `.5` is sometimes below or above that value.

That said, the correct result could in fact be obtained if rounding were done on the shortest decimal representation that produces the incoming number, that is if rounding where done on the output of using the ""%g"" format (or `strconv.FormatFloat` with precision -1). Unfortunately, computing that representation is much more expensive than what happens now.

We can probably not fix this. For one, it's been like this forever. Also, a corresponding C program
```
#include <stdio.h>

int main() {
	printf(""x = %.1f\n"", 0.35);
	printf(""x = %.1f\n"", 0.45);
	printf(""x = %.1f\n"", 0.55);
	printf(""x = %.1f\n"", 0.65);
	return 0;
}
```
produces the same (incorrect) result. And so does `math/big.Float` formatting with the same arguments (since the code mirrors the strconv code).

But we should probably document it and perhaps even provide a ""correct"" routine for cases where this truly matters.
",1.0,"strconv: incorrect rounding to nearest even - The following statements
```
fmt.Printf(""x = %.1f\n"", 0.35)
fmt.Printf(""x = %.1f\n"", 0.45)
fmt.Printf(""x = %.1f\n"", 0.55)
fmt.Printf(""x = %.1f\n"", 0.65)
```
produce
```
x = 0.3
x = 0.5
x = 0.6
x = 0.7
```
(https://play.golang.org/p/kLC7Ap0cpP).

However, assuming rounding to nearest even, one would expect the result to be
```
x = 0.4
x = 0.4
x = 0.6
x = 0.6
```
(The examples use fmt.Printf but the culprit is in the underlying strconv code. The documentation doesn't explicitly state that it rounds to nearest even, but that is definitively the intent of the implementation which contains code and comments to that effect.).

The problem of course is that these numbers cannot be accurately represented in binary form and when it comes to the rounding decision, what should be `.5` is sometimes below or above that value.

That said, the correct result could in fact be obtained if rounding were done on the shortest decimal representation that produces the incoming number, that is if rounding where done on the output of using the ""%g"" format (or `strconv.FormatFloat` with precision -1). Unfortunately, computing that representation is much more expensive than what happens now.

We can probably not fix this. For one, it's been like this forever. Also, a corresponding C program
```
#include <stdio.h>

int main() {
	printf(""x = %.1f\n"", 0.35);
	printf(""x = %.1f\n"", 0.45);
	printf(""x = %.1f\n"", 0.55);
	printf(""x = %.1f\n"", 0.65);
	return 0;
}
```
produces the same (incorrect) result. And so does `math/big.Float` formatting with the same arguments (since the code mirrors the strconv code).

But we should probably document it and perhaps even provide a ""correct"" routine for cases where this truly matters.
",1,strconv  incorrect rounding to nearest even   the following statements       fmt printf  x       n         fmt printf  x       n         fmt printf  x       n         fmt printf  x       n              produce       x        x        x        x                   however  assuming rounding to nearest even  one would expect the result to be       x        x        x        x              the examples use fmt printf but the culprit is in the underlying strconv code  the documentation doesn t explicitly state that it rounds to nearest even  but that is definitively the intent of the implementation which contains code and comments to that effect       the problem of course is that these numbers cannot be accurately represented in binary form and when it comes to the rounding decision  what should be      is sometimes below or above that value     that said  the correct result could in fact be obtained if rounding were done on the shortest decimal representation that produces the incoming number  that is if rounding where done on the output of using the   g  format  or  strconv formatfloat  with precision      unfortunately  computing that representation is much more expensive than what happens now     we can probably not fix this  for one  it s been like this forever  also  a corresponding c program        include      int main      	printf  x       n          	printf  x       n          	printf  x       n          	printf  x       n          	return             produces the same  incorrect  result  and so does  math big float  formatting with the same arguments  since the code mirrors the strconv code      but we should probably document it and perhaps even provide a  correct  routine for cases where this truly matters   ,1
13873,9100706628.0,IssuesEvent,2019-02-20 09:16:49,oceanprotocol/ocean,https://api.github.com/repos/oceanprotocol/ocean,closed,Keeper v0.6 to v0.7 plan,Keeper Network Deployment Security enhancement epic help wanted,"# Keeper v0.7 Plan

## Ocean Token

- [X] Document the requirements and high-level architecture (28/Jan)
- [X] Document the keeper tasks to accomplish (28/Jan)
- [x] Implement/Adapt the Ocean Token (https://github.com/oceanprotocol/keeper-contracts/issues/303)
- [x] Dispenser
- [x] DIDRegistry

## Token Bridge

TokenBridge needs to be tested in all the scenarios. The main task is to understand how to operate the bridge in a live environment scenario. What happens if the complete network is down? How to recover the system? Are funds lost? How to distribute the agents?

Tasks:
- [ ] Preparation of Token Bridge for running in Production: https://github.com/oceanprotocol/poc-token-bridge/issues/6
- [ ] Test Governance and Roles


## Service Execution Agreements (SEA)


- [X] Document the requirements and high-level architecture (28/Jan)
- [X] Document the keeper tasks to accomplish (28/Jan)
- [x] Implement/Adapt the extended Service Execution Agreements (https://github.com/oceanprotocol/keeper-contracts/issues/309)

Conditions
- [x] Hashlock
- [x] Access
- [x] LockReward
- [x] SignCondition

Rewards
- [x] EscrowReward

Libraries
- [x] Epoch
- [x] Agreement
- [x] Condition
- [x] Template

Controllers (Storage)
- [x] Agreements
- [x] Conditions
- [x] Templates

## Governance

- [x] Deploy
- [x] Upgrades
- [x] RBAC concept
- [x] Define and implement pending Roles using the Zeppelin-eth library
- [x] Modularize deployment of Token and MultiSigWallet
- [x] Genesis Minting
- [x] ZeppelinOS
- [x] MultiSigWallet integration
- [x] Influence of governance and changed addresses on the bridge
- [x] Influence of governance and changed addresses on the SEA content based IDs

## Tests

- [x] Unit
- [x] Integration
- [x] Upgrade

## Documentation

- [x] Add Documentation

## Execution Plan

It's necessary to formalize this plan in DevOcean.

- Define requirements
- Define architecture
- Define public interfaces
- Define tasks
- Define tests in plain English
- Formalize tests
- Start writing code
- Check tests
- E2E

",True,"Keeper v0.6 to v0.7 plan - # Keeper v0.7 Plan

## Ocean Token

- [X] Document the requirements and high-level architecture (28/Jan)
- [X] Document the keeper tasks to accomplish (28/Jan)
- [x] Implement/Adapt the Ocean Token (https://github.com/oceanprotocol/keeper-contracts/issues/303)
- [x] Dispenser
- [x] DIDRegistry

## Token Bridge

TokenBridge needs to be tested in all the scenarios. The main task is to understand how to operate the bridge in a live environment scenario. What happens if the complete network is down? How to recover the system? Are funds lost? How to distribute the agents?

Tasks:
- [ ] Preparation of Token Bridge for running in Production: https://github.com/oceanprotocol/poc-token-bridge/issues/6
- [ ] Test Governance and Roles


## Service Execution Agreements (SEA)


- [X] Document the requirements and high-level architecture (28/Jan)
- [X] Document the keeper tasks to accomplish (28/Jan)
- [x] Implement/Adapt the extended Service Execution Agreements (https://github.com/oceanprotocol/keeper-contracts/issues/309)

Conditions
- [x] Hashlock
- [x] Access
- [x] LockReward
- [x] SignCondition

Rewards
- [x] EscrowReward

Libraries
- [x] Epoch
- [x] Agreement
- [x] Condition
- [x] Template

Controllers (Storage)
- [x] Agreements
- [x] Conditions
- [x] Templates

## Governance

- [x] Deploy
- [x] Upgrades
- [x] RBAC concept
- [x] Define and implement pending Roles using the Zeppelin-eth library
- [x] Modularize deployment of Token and MultiSigWallet
- [x] Genesis Minting
- [x] ZeppelinOS
- [x] MultiSigWallet integration
- [x] Influence of governance and changed addresses on the bridge
- [x] Influence of governance and changed addresses on the SEA content based IDs

## Tests

- [x] Unit
- [x] Integration
- [x] Upgrade

## Documentation

- [x] Add Documentation

## Execution Plan

It's necessary to formalize this plan in DevOcean.

- Define requirements
- Define architecture
- Define public interfaces
- Define tasks
- Define tests in plain English
- Formalize tests
- Start writing code
- Check tests
- E2E

",0,keeper     to     plan     keeper     plan       ocean token        document the requirements and high level architecture    jan       document the keeper tasks to accomplish    jan       implement adapt the ocean token         dispenser      didregistry       token bridge    tokenbridge needs to be tested in all the scenarios  the main task is to understand how to operate the bridge in a live environment scenario  what happens if the complete network is down  how to recover the system  are funds lost  how to distribute the agents     tasks       preparation of token bridge for running in production         test governance and roles         service execution agreements  sea           document the requirements and high level architecture    jan       document the keeper tasks to accomplish    jan       implement adapt the extended service execution agreements       conditions      hashlock      access      lockreward      signcondition    rewards      escrowreward    libraries      epoch      agreement      condition      template    controllers  storage       agreements      conditions      templates       governance        deploy      upgrades      rbac concept      define and implement pending roles using the zeppelin eth library      modularize deployment of token and multisigwallet      genesis minting      zeppelinos      multisigwallet integration      influence of governance and changed addresses on the bridge      influence of governance and changed addresses on the sea content based ids       tests        unit      integration      upgrade       documentation        add documentation       execution plan    it s necessary to formalize this plan in devocean       define requirements    define architecture    define public interfaces    define tasks    define tests in plain english    formalize tests    start writing code    check tests         ,0
23200,4893247064.0,IssuesEvent,2016-11-18 22:25:54,golang/go,https://api.github.com/repos/golang/go,opened,net: document net.Conn operation after deadline is exceeded,Documentation,"The current phrasing on `net.Conn.SetDeadline` is:
> A deadline is an absolute time after which I/O operations fail with a timeout (see type Error) instead of blocking. The deadline applies to all future and pending I/O, not just the immediately following call to Read or Write.
>
> An idle timeout can be implemented by repeatedly extending the deadline after successful Read or Write calls.
>
> A zero value for t means I/O operations will not time out.

I'm debugging some non-compliant implementations of `net.Conn` due to the clarification made in ([CL/30164](http://golang.org/cl/30164)). While fixing them, I noticed another discrepancy of some `net.Conn` implementations as compared to `net.TCPConn` and would like some clarification on expected behavior. 

The `net.TCPConn` implementation allows a deadline to be exceeded, which unblocks any pending IO operations. However, it also allows the user to extend the deadline to be in the future, essentially allowing IO operations to function again.

In some of the implementations I'm fixing, once the deadline has been exceeded, the underlying connection is destroyed and it does not matter if the deadline is set to be in the future again; all IO operations henceforth are dead.

Is ""refreshable"" deadlines an expected behavior of `net.Conn`? Does any logic in the standard library depend on it?

/cc @bradfitz ",1.0,"net: document net.Conn operation after deadline is exceeded - The current phrasing on `net.Conn.SetDeadline` is:
> A deadline is an absolute time after which I/O operations fail with a timeout (see type Error) instead of blocking. The deadline applies to all future and pending I/O, not just the immediately following call to Read or Write.
>
> An idle timeout can be implemented by repeatedly extending the deadline after successful Read or Write calls.
>
> A zero value for t means I/O operations will not time out.

I'm debugging some non-compliant implementations of `net.Conn` due to the clarification made in ([CL/30164](http://golang.org/cl/30164)). While fixing them, I noticed another discrepancy of some `net.Conn` implementations as compared to `net.TCPConn` and would like some clarification on expected behavior. 

The `net.TCPConn` implementation allows a deadline to be exceeded, which unblocks any pending IO operations. However, it also allows the user to extend the deadline to be in the future, essentially allowing IO operations to function again.

In some of the implementations I'm fixing, once the deadline has been exceeded, the underlying connection is destroyed and it does not matter if the deadline is set to be in the future again; all IO operations henceforth are dead.

Is ""refreshable"" deadlines an expected behavior of `net.Conn`? Does any logic in the standard library depend on it?

/cc @bradfitz ",1,net  document net conn operation after deadline is exceeded   the current phrasing on  net conn setdeadline  is     a deadline is an absolute time after which i o operations fail with a timeout  see type error  instead of blocking  the deadline applies to all future and pending i o  not just the immediately following call to read or write        an idle timeout can be implemented by repeatedly extending the deadline after successful read or write calls        a zero value for t means i o operations will not time out     i m debugging some non compliant implementations of  net conn  due to the clarification made in      while fixing them  i noticed another discrepancy of some  net conn  implementations as compared to  net tcpconn  and would like some clarification on expected behavior      the  net tcpconn  implementation allows a deadline to be exceeded  which unblocks any pending io operations  however  it also allows the user to extend the deadline to be in the future  essentially allowing io operations to function again     in some of the implementations i m fixing  once the deadline has been exceeded  the underlying connection is destroyed and it does not matter if the deadline is set to be in the future again  all io operations henceforth are dead     is  refreshable  deadlines an expected behavior of  net conn   does any logic in the standard library depend on it      cc  bradfitz ,1
78563,10073179353.0,IssuesEvent,2019-07-24 09:02:45,golang/go,https://api.github.com/repos/golang/go,closed,net/http: documentation unclear about when request body is closed,Documentation,"It is currently possible for a request body to be read, even _after_ `http.Client.Do` returns. This can be a source of potential race conditions. It is currently unclear in the documentation that this can happen. To the contrary, the documentation is hinting at the fact that the request body _will_ be closed after the function returns, at least to my understanding. To illustrate, the attached playground example reproduces the problem, when compiled with the `-race` flag:

https://play.golang.org/p/Z0t0QEawcev

Furthermore, I'm unsure about the correctness of reading from an `io.ReadCloser` (the request body) after a call to `Close`.

The purpose of this issue is to clarify whether:

* This is a bug?
* Documentation can be improved?

Useful links:

* [http.RoundTripper documentation](https://github.com/golang/go/blob/go1.12/src/net/http/client.go#L133-L137)
* [http.Client.Do documentation](https://github.com/golang/go/blob/go1.12/src/net/http/client.go#L486-L487)",1.0,"net/http: documentation unclear about when request body is closed - It is currently possible for a request body to be read, even _after_ `http.Client.Do` returns. This can be a source of potential race conditions. It is currently unclear in the documentation that this can happen. To the contrary, the documentation is hinting at the fact that the request body _will_ be closed after the function returns, at least to my understanding. To illustrate, the attached playground example reproduces the problem, when compiled with the `-race` flag:

https://play.golang.org/p/Z0t0QEawcev

Furthermore, I'm unsure about the correctness of reading from an `io.ReadCloser` (the request body) after a call to `Close`.

The purpose of this issue is to clarify whether:

* This is a bug?
* Documentation can be improved?

Useful links:

* [http.RoundTripper documentation](https://github.com/golang/go/blob/go1.12/src/net/http/client.go#L133-L137)
* [http.Client.Do documentation](https://github.com/golang/go/blob/go1.12/src/net/http/client.go#L486-L487)",1,net http  documentation unclear about when request body is closed   it is currently possible for a request body to be read  even  after   http client do  returns  this can be a source of potential race conditions  it is currently unclear in the documentation that this can happen  to the contrary  the documentation is hinting at the fact that the request body  will  be closed after the function returns  at least to my understanding  to illustrate  the attached playground example reproduces the problem  when compiled with the   race  flag          furthermore  i m unsure about the correctness of reading from an  io readcloser   the request body  after a call to  close      the purpose of this issue is to clarify whether       this is a bug     documentation can be improved     useful links                 ,1
20311,4536254747.0,IssuesEvent,2016-09-08 19:51:20,golang/go,https://api.github.com/repos/golang/go,closed,encoding/hex: Suggestions for doc improvements,Documentation,"Quoting from https://groups.google.com/d/msg/golang-nuts/eV3uNlEFPrc/KeHIjyN2oVEJ (not all of this is appropriate in my opinion, but it is useful information from a Go newbie):

Now, let's look at a specific package, e.g. https://golang.org/pkg/encoding/hex/

Already, we can see there are no examples here, making it tough for a newcomer to follow along with.  For example, it's not clear that the functions that are listed here need to be prefixed with the ""hex."" prefix.  Yes, that's a simple language thing, but if it's not re-enforced in the documentation with a few examples, it takes that much longer to learn.

Consider this (BAD/CONFUSING):
var ErrLength = errors.New(""encoding/hex: odd length hex string"")

What is that?  My first assumption is that this is some type of package variable because it's under the ""Variables"" heading.  It's only by comparing this to other packages that I can guess that this is a reference to a particular error message.  But without an example to see how it might arise, I have no idea what to do with this info or what exactly it pertains to.

BETTER: include an example of working with the returned variables to see how/why they might be relevant or omit this entirely and just list the message strings.  

BAD: func Dumper

This ""crosses the beams"" by referencing another package: ""io"".  Without an example to work off of, it's not clear how one might instantiate an io.Writer or what might be done with an io.WriteCloser.  We end up banging our heads on a different wall over at the ""io"" docs.

BETTER: include an example here so we aren't on a wild goose chase to figure out how to instantiate io.Writer objects.

BAD: func DecodeString

Again, no example, so immediately I have to pay the toll of fiddling with this to see how it works.  Perhaps an example like this:

    bytes, _ := hex.DecodeString(""AE"")
    fmt.Println(hex.EncodeToString(bytes)) // ae (lowercase)


It might be worth mentioning that the output is always lowercase, and it would be good to explain the behavior that pops up if your input is out of range, e.g. ""XX"".  This is why it would be useful to describe the parameters and output in their own dedicated sections.

BAD: func Decode

The explanation includes ""Decode decodes src into DecodedLen(len(src)) bytes"" -- nesting like that is more concise, but it's harder to follow.  I'm not entirely sure I understand what this function does.  Again, an example would help clarify this more than paragraphs of text.

BETTER: ???",1.0,"encoding/hex: Suggestions for doc improvements - Quoting from https://groups.google.com/d/msg/golang-nuts/eV3uNlEFPrc/KeHIjyN2oVEJ (not all of this is appropriate in my opinion, but it is useful information from a Go newbie):

Now, let's look at a specific package, e.g. https://golang.org/pkg/encoding/hex/

Already, we can see there are no examples here, making it tough for a newcomer to follow along with.  For example, it's not clear that the functions that are listed here need to be prefixed with the ""hex."" prefix.  Yes, that's a simple language thing, but if it's not re-enforced in the documentation with a few examples, it takes that much longer to learn.

Consider this (BAD/CONFUSING):
var ErrLength = errors.New(""encoding/hex: odd length hex string"")

What is that?  My first assumption is that this is some type of package variable because it's under the ""Variables"" heading.  It's only by comparing this to other packages that I can guess that this is a reference to a particular error message.  But without an example to see how it might arise, I have no idea what to do with this info or what exactly it pertains to.

BETTER: include an example of working with the returned variables to see how/why they might be relevant or omit this entirely and just list the message strings.  

BAD: func Dumper

This ""crosses the beams"" by referencing another package: ""io"".  Without an example to work off of, it's not clear how one might instantiate an io.Writer or what might be done with an io.WriteCloser.  We end up banging our heads on a different wall over at the ""io"" docs.

BETTER: include an example here so we aren't on a wild goose chase to figure out how to instantiate io.Writer objects.

BAD: func DecodeString

Again, no example, so immediately I have to pay the toll of fiddling with this to see how it works.  Perhaps an example like this:

    bytes, _ := hex.DecodeString(""AE"")
    fmt.Println(hex.EncodeToString(bytes)) // ae (lowercase)


It might be worth mentioning that the output is always lowercase, and it would be good to explain the behavior that pops up if your input is out of range, e.g. ""XX"".  This is why it would be useful to describe the parameters and output in their own dedicated sections.

BAD: func Decode

The explanation includes ""Decode decodes src into DecodedLen(len(src)) bytes"" -- nesting like that is more concise, but it's harder to follow.  I'm not entirely sure I understand what this function does.  Again, an example would help clarify this more than paragraphs of text.

BETTER: ???",1,encoding hex  suggestions for doc improvements   quoting from    not all of this is appropriate in my opinion  but it is useful information from a go newbie      now  let s look at a specific package  e g       already  we can see there are no examples here  making it tough for a newcomer to follow along with   for example  it s not clear that the functions that are listed here need to be prefixed with the  hex   prefix   yes  that s a simple language thing  but if it s not re enforced in the documentation with a few examples  it takes that much longer to learn     consider this  bad confusing    var errlength   errors new  encoding hex  odd length hex string      what is that   my first assumption is that this is some type of package variable because it s under the  variables  heading   it s only by comparing this to other packages that i can guess that this is a reference to a particular error message   but without an example to see how it might arise  i have no idea what to do with this info or what exactly it pertains to     better  include an example of working with the returned variables to see how why they might be relevant or omit this entirely and just list the message strings       bad  func dumper    this  crosses the beams  by referencing another package   io    without an example to work off of  it s not clear how one might instantiate an io writer or what might be done with an io writecloser   we end up banging our heads on a different wall over at the  io  docs     better  include an example here so we aren t on a wild goose chase to figure out how to instantiate io writer objects     bad  func decodestring    again  no example  so immediately i have to pay the toll of fiddling with this to see how it works   perhaps an example like this         bytes       hex decodestring  ae        fmt println hex encodetostring bytes      ae  lowercase       it might be worth mentioning that the output is always lowercase  and it would be good to explain the behavior that pops up if your input is out of range  e g   xx    this is why it would be useful to describe the parameters and output in their own dedicated sections     bad  func decode    the explanation includes  decode decodes src into decodedlen len src   bytes     nesting like that is more concise  but it s harder to follow   i m not entirely sure i understand what this function does   again  an example would help clarify this more than paragraphs of text     better     ,1
248052,20991690689.0,IssuesEvent,2022-03-29 09:51:48,ubtue/tuefind,https://api.github.com/repos/ubtue/tuefind,closed,Mehrfache Wiederholung von Angaben (ISSN-Blöcke in JOP),ready for testing,"Die online Verfügbarkeit der ""Zeitschrift für die alttestamentliche Wissenschaft"" wird in IxTheo mehrfach wiederholt (siehe Langtitelanzeige https://ixtheo.de/Record/129461423). 
Sind vielleicht andere Zeitschriften von diesem Fehler betroffen?  ",1.0,"Mehrfache Wiederholung von Angaben (ISSN-Blöcke in JOP) - Die online Verfügbarkeit der ""Zeitschrift für die alttestamentliche Wissenschaft"" wird in IxTheo mehrfach wiederholt (siehe Langtitelanzeige https://ixtheo.de/Record/129461423). 
Sind vielleicht andere Zeitschriften von diesem Fehler betroffen?  ",0,mehrfache wiederholung von angaben  issn blöcke in jop    die online verfügbarkeit der  zeitschrift für die alttestamentliche wissenschaft  wird in ixtheo mehrfach wiederholt  siehe langtitelanzeige     sind vielleicht andere zeitschriften von diesem fehler betroffen   ,0
40356,2868669878.0,IssuesEvent,2015-06-05 20:18:12,openshift/origin,https://api.github.com/repos/openshift/origin,closed,SDN assigns duplicate subnets,component/networking kind/bug priority/P2,"When adding additional nodes to a running cluster, we are seeing that duplicate subnets are being defined.

output of osc get hostSubnet prior to adding nodes:
ip-172-19-48-236.ec2.internal   ip-172-19-48-236.ec2.internal   172.19.48.236   10.0.0.0/16
ip-172-19-53-204.ec2.internal   ip-172-19-53-204.ec2.internal   172.19.53.204   10.3.0.0/16
ip-172-19-53-205.ec2.internal   ip-172-19-53-205.ec2.internal   172.19.53.205   10.2.0.0/16
ip-172-19-53-206.ec2.internal   ip-172-19-53-206.ec2.internal   172.19.53.206   10.5.0.0/16
ip-172-19-53-207.ec2.internal   ip-172-19-53-207.ec2.internal   172.19.53.207   10.4.0.0/16
ip-172-19-53-208.ec2.internal   ip-172-19-53-208.ec2.internal   172.19.53.208   10.1.0.0/16
ip-172-19-60-228.ec2.internal   ip-172-19-60-228.ec2.internal   172.19.60.228   10.6.0.0/16

output of osc get hostSubnet after adding nodes:
ip-172-19-46-156.ec2.internal   ip-172-19-46-156.ec2.internal   172.19.46.156   10.10.0.0/16
ip-172-19-46-157.ec2.internal   ip-172-19-46-157.ec2.internal   172.19.46.157   10.1.0.0/16
ip-172-19-46-158.ec2.internal   ip-172-19-46-158.ec2.internal   172.19.46.158   10.5.0.0/16
ip-172-19-46-159.ec2.internal   ip-172-19-46-159.ec2.internal   172.19.46.159   10.7.0.0/16
ip-172-19-46-160.ec2.internal   ip-172-19-46-160.ec2.internal   172.19.46.160   10.4.0.0/16
ip-172-19-46-161.ec2.internal   ip-172-19-46-161.ec2.internal   172.19.46.161   10.0.0.0/16
ip-172-19-46-162.ec2.internal   ip-172-19-46-162.ec2.internal   172.19.46.162   10.3.0.0/16
ip-172-19-46-163.ec2.internal   ip-172-19-46-163.ec2.internal   172.19.46.163   10.8.0.0/16
ip-172-19-46-164.ec2.internal   ip-172-19-46-164.ec2.internal   172.19.46.164   10.11.0.0/16
ip-172-19-46-165.ec2.internal   ip-172-19-46-165.ec2.internal   172.19.46.165   10.9.0.0/16
ip-172-19-46-166.ec2.internal   ip-172-19-46-166.ec2.internal   172.19.46.166   10.6.0.0/16
ip-172-19-46-167.ec2.internal   ip-172-19-46-167.ec2.internal   172.19.46.167   10.2.0.0/16
ip-172-19-48-236.ec2.internal   ip-172-19-48-236.ec2.internal   172.19.48.236   10.0.0.0/16
ip-172-19-53-204.ec2.internal   ip-172-19-53-204.ec2.internal   172.19.53.204   10.3.0.0/16
ip-172-19-53-205.ec2.internal   ip-172-19-53-205.ec2.internal   172.19.53.205   10.2.0.0/16
ip-172-19-53-206.ec2.internal   ip-172-19-53-206.ec2.internal   172.19.53.206   10.5.0.0/16
ip-172-19-53-207.ec2.internal   ip-172-19-53-207.ec2.internal   172.19.53.207   10.4.0.0/16
ip-172-19-53-208.ec2.internal   ip-172-19-53-208.ec2.internal   172.19.53.208   10.1.0.0/16
ip-172-19-60-228.ec2.internal   ip-172-19-60-228.ec2.internal   172.19.60.228   10.6.0.0/16
",1.0,"SDN assigns duplicate subnets - When adding additional nodes to a running cluster, we are seeing that duplicate subnets are being defined.

output of osc get hostSubnet prior to adding nodes:
ip-172-19-48-236.ec2.internal   ip-172-19-48-236.ec2.internal   172.19.48.236   10.0.0.0/16
ip-172-19-53-204.ec2.internal   ip-172-19-53-204.ec2.internal   172.19.53.204   10.3.0.0/16
ip-172-19-53-205.ec2.internal   ip-172-19-53-205.ec2.internal   172.19.53.205   10.2.0.0/16
ip-172-19-53-206.ec2.internal   ip-172-19-53-206.ec2.internal   172.19.53.206   10.5.0.0/16
ip-172-19-53-207.ec2.internal   ip-172-19-53-207.ec2.internal   172.19.53.207   10.4.0.0/16
ip-172-19-53-208.ec2.internal   ip-172-19-53-208.ec2.internal   172.19.53.208   10.1.0.0/16
ip-172-19-60-228.ec2.internal   ip-172-19-60-228.ec2.internal   172.19.60.228   10.6.0.0/16

output of osc get hostSubnet after adding nodes:
ip-172-19-46-156.ec2.internal   ip-172-19-46-156.ec2.internal   172.19.46.156   10.10.0.0/16
ip-172-19-46-157.ec2.internal   ip-172-19-46-157.ec2.internal   172.19.46.157   10.1.0.0/16
ip-172-19-46-158.ec2.internal   ip-172-19-46-158.ec2.internal   172.19.46.158   10.5.0.0/16
ip-172-19-46-159.ec2.internal   ip-172-19-46-159.ec2.internal   172.19.46.159   10.7.0.0/16
ip-172-19-46-160.ec2.internal   ip-172-19-46-160.ec2.internal   172.19.46.160   10.4.0.0/16
ip-172-19-46-161.ec2.internal   ip-172-19-46-161.ec2.internal   172.19.46.161   10.0.0.0/16
ip-172-19-46-162.ec2.internal   ip-172-19-46-162.ec2.internal   172.19.46.162   10.3.0.0/16
ip-172-19-46-163.ec2.internal   ip-172-19-46-163.ec2.internal   172.19.46.163   10.8.0.0/16
ip-172-19-46-164.ec2.internal   ip-172-19-46-164.ec2.internal   172.19.46.164   10.11.0.0/16
ip-172-19-46-165.ec2.internal   ip-172-19-46-165.ec2.internal   172.19.46.165   10.9.0.0/16
ip-172-19-46-166.ec2.internal   ip-172-19-46-166.ec2.internal   172.19.46.166   10.6.0.0/16
ip-172-19-46-167.ec2.internal   ip-172-19-46-167.ec2.internal   172.19.46.167   10.2.0.0/16
ip-172-19-48-236.ec2.internal   ip-172-19-48-236.ec2.internal   172.19.48.236   10.0.0.0/16
ip-172-19-53-204.ec2.internal   ip-172-19-53-204.ec2.internal   172.19.53.204   10.3.0.0/16
ip-172-19-53-205.ec2.internal   ip-172-19-53-205.ec2.internal   172.19.53.205   10.2.0.0/16
ip-172-19-53-206.ec2.internal   ip-172-19-53-206.ec2.internal   172.19.53.206   10.5.0.0/16
ip-172-19-53-207.ec2.internal   ip-172-19-53-207.ec2.internal   172.19.53.207   10.4.0.0/16
ip-172-19-53-208.ec2.internal   ip-172-19-53-208.ec2.internal   172.19.53.208   10.1.0.0/16
ip-172-19-60-228.ec2.internal   ip-172-19-60-228.ec2.internal   172.19.60.228   10.6.0.0/16
",0,sdn assigns duplicate subnets   when adding additional nodes to a running cluster  we are seeing that duplicate subnets are being defined     output of osc get hostsubnet prior to adding nodes   ip           internal   ip           internal                        ip           internal   ip           internal                        ip           internal   ip           internal                        ip           internal   ip           internal                        ip           internal   ip           internal                        ip           internal   ip           internal                        ip           internal   ip           internal                          output of osc get hostsubnet after adding nodes   ip           internal   ip           internal                        ip           internal   ip           internal                        ip           internal   ip           internal                        ip           internal   ip           internal                        ip           internal   ip           internal                        ip           internal   ip           internal                        ip           internal   ip           internal                        ip           internal   ip           internal                        ip           internal   ip           internal                        ip           internal   ip           internal                        ip           internal   ip           internal                        ip           internal   ip           internal                        ip           internal   ip           internal                        ip           internal   ip           internal                        ip           internal   ip           internal                        ip           internal   ip           internal                        ip           internal   ip           internal                        ip           internal   ip           internal                        ip           internal   ip           internal                        ,0
220015,16869414132.0,IssuesEvent,2021-06-22 00:51:19,golang/go,https://api.github.com/repos/golang/go,closed,"text/template: doc: `define` action is not listed and described in ""Actions"" section",Documentation NeedsDecision,"<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.16.3 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What did you expect to see?

In text/template [doc page](https://golang.org/pkg/text/template/), `define` action should be officially listed in 'Actions' section.

### What did you see instead?

In text/template [doc page](https://golang.org/pkg/text/template/), `define` action is described in a separate section, named [""Nested template definitions""](https://golang.org/pkg/text/template/#hdr-Nested_template_definitions), however, as an action, it's not listed in the [""Actions""](https://golang.org/pkg/text/template/#hdr-Actions) section as other actions do. It should also be there.
",1.0,"text/template: doc: `define` action is not listed and described in ""Actions"" section - <!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.16.3 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What did you expect to see?

In text/template [doc page](https://golang.org/pkg/text/template/), `define` action should be officially listed in 'Actions' section.

### What did you see instead?

In text/template [doc page](https://golang.org/pkg/text/template/), `define` action is described in a separate section, named [""Nested template definitions""](https://golang.org/pkg/text/template/#hdr-Nested_template_definitions), however, as an action, it's not listed in the [""Actions""](https://golang.org/pkg/text/template/#hdr-Actions) section as other actions do. It should also be there.
",1,text template  doc   define  action is not listed and described in  actions  section         please answer these questions before submitting your issue  thanks   for questions please use one of our forums                what version of go are you using   go version            go version  go version       linux             does this issue reproduce with the latest release     yes         what did you expect to see     in text template      define  action should be officially listed in  actions  section         what did you see instead     in text template      define  action is described in a separate section  named     however  as an action  it s not listed in the     section as other actions do  it should also be there   ,1
99613,11149987008.0,IssuesEvent,2019-12-23 20:43:06,golang/go,https://api.github.com/repos/golang/go,closed,"testing: B logs are printed on stdout, but doc says they go to stderr",Documentation NeedsFix,"<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.13 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
It's an issue at the documentation so the question is irrelavent


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/nimrod/.cache/go-build""
GOENV=""/home/nimrod/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/nimrod/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build403478965=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?
Read the testing pkg documentation and saw that its incorrect at https://golang.org/pkg/testing/#B

### What did you expect to see?
""Like in tests, benchmark logs are accumulated during execution and dumped to standard output when done.""

### What did you see instead?
The following is a quote from the third paragraph on Type B:
""Like in tests, benchmark logs are accumulated during execution and dumped to **standard error** when done.""

It's incorrect as it state that the benchmark logs are dumped to standard error

",1.0,"testing: B logs are printed on stdout, but doc says they go to stderr - <!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.13 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
It's an issue at the documentation so the question is irrelavent


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""""
GOARCH=""amd64""
GOBIN=""""
GOCACHE=""/home/nimrod/.cache/go-build""
GOENV=""/home/nimrod/.config/go/env""
GOEXE=""""
GOFLAGS=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""linux""
GONOPROXY=""""
GONOSUMDB=""""
GOOS=""linux""
GOPATH=""/home/nimrod/go""
GOPRIVATE=""""
GOPROXY=""https://proxy.golang.org,direct""
GOROOT=""/usr/local/go""
GOSUMDB=""sum.golang.org""
GOTMPDIR=""""
GOTOOLDIR=""/usr/local/go/pkg/tool/linux_amd64""
GCCGO=""gccgo""
AR=""ar""
CC=""gcc""
CXX=""g++""
CGO_ENABLED=""1""
GOMOD=""""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""
PKG_CONFIG=""pkg-config""
GOGCCFLAGS=""-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build403478965=/tmp/go-build -gno-record-gcc-switches""
</pre></details>

### What did you do?
Read the testing pkg documentation and saw that its incorrect at https://golang.org/pkg/testing/#B

### What did you expect to see?
""Like in tests, benchmark logs are accumulated during execution and dumped to standard output when done.""

### What did you see instead?
The following is a quote from the third paragraph on Type B:
""Like in tests, benchmark logs are accumulated during execution and dumped to **standard error** when done.""

It's incorrect as it state that the benchmark logs are dumped to standard error

",1,testing  b logs are printed on stdout  but doc says they go to stderr            what version of go are you using   go version            go version  go version     linux             does this issue reproduce with the latest release   it s an issue at the documentation so the question is irrelavent          what operating system and processor architecture are you using   go env          go env  output       go env        goarch      gobin     gocache   home nimrod  cache go build   goenv   home nimrod  config go env   goexe     goflags     gohostarch      gohostos  linux   gonoproxy     gonosumdb     goos  linux   gopath   home nimrod go   goprivate     goproxy     goroot   usr local go   gosumdb  sum golang org   gotmpdir     gotooldir   usr local go pkg tool linux     gccgo  gccgo   ar  ar   cc  gcc   cxx  g     cgo enabled      gomod     cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g      pkg config  pkg config   gogccflags   fpic     pthread  fmessage length    fdebug prefix map  tmp go    tmp go build  gno record gcc switches             what did you do   read the testing pkg documentation and saw that its incorrect at          what did you expect to see    like in tests  benchmark logs are accumulated during execution and dumped to standard output when done          what did you see instead   the following is a quote from the third paragraph on type b    like in tests  benchmark logs are accumulated during execution and dumped to   standard error   when done      it s incorrect as it state that the benchmark logs are dumped to standard error    ,1
69022,9239247735.0,IssuesEvent,2019-03-14 00:33:31,golang/go,https://api.github.com/repos/golang/go,closed,spec: apparent contradiction for passing of slice argument to variadic parameter,Documentation NeedsFix WaitingForInfo,"```
Version of November 16, 2018
```

Section [""Passing arguments to ... parameters""](https://golang.org/ref/spec#Passing_arguments_to_..._parameters) says:

> If the final argument is assignable to a slice type []T, it may be passed unchanged as the value for a ...T parameter if the argument is followed by .... In this case no new slice is created.

Notice the use of the word ""may"". This appears to contradict what I understand to be the case in practice (i.e. that it _will_ be passed unchanged, for reasons of efficiency) but also the example that follows:

> ... who will have the same value as s with the same underlying array.

Notice the use of the word ""will"".

cc @griesemer 

FYI @mvdan @rogpeppe ",1.0,"spec: apparent contradiction for passing of slice argument to variadic parameter - ```
Version of November 16, 2018
```

Section [""Passing arguments to ... parameters""](https://golang.org/ref/spec#Passing_arguments_to_..._parameters) says:

> If the final argument is assignable to a slice type []T, it may be passed unchanged as the value for a ...T parameter if the argument is followed by .... In this case no new slice is created.

Notice the use of the word ""may"". This appears to contradict what I understand to be the case in practice (i.e. that it _will_ be passed unchanged, for reasons of efficiency) but also the example that follows:

> ... who will have the same value as s with the same underlying array.

Notice the use of the word ""will"".

cc @griesemer 

FYI @mvdan @rogpeppe ",1,spec  apparent contradiction for passing of slice argument to variadic parameter        version of november              section     says       if the final argument is assignable to a slice type  t  it may be passed unchanged as the value for a    t parameter if the argument is followed by      in this case no new slice is created     notice the use of the word  may   this appears to contradict what i understand to be the case in practice  i e  that it  will  be passed unchanged  for reasons of efficiency  but also the example that follows           who will have the same value as s with the same underlying array     notice the use of the word  will      cc  griesemer     fyi  mvdan  rogpeppe ,1
31979,6022657744.0,IssuesEvent,2017-06-07 21:35:57,golang/go,https://api.github.com/repos/golang/go,closed,"sync: clarify Cond ""created as part of other structures"" documentation",Documentation,"### What version of Go are you using (`go version`)?

go version go1.8.1 darwin/amd64

### What operating system and processor architecture are you using (`go env`)?

```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/joneskoo""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.8.1/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.8.1/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/p9/8mb6mhcx7p3br8f18crtczzw0000gn/T/go-build980179018=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
PKG_CONFIG=""pkg-config""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""

```

### What did you do?

I'm creating a sync.Cond as part of a struct. [Documentation explicitly says this is ok](https://tip.golang.org/pkg/sync/#Cond).

https://play.golang.org/p/k0EkYJPC4A

### What did you expect to see?

Wait for Cond until Broadcast is called one second later.

### What did you see instead?

```
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0xffffffff addr=0x0 pc=0x82ffb]

goroutine 1 [running]:
sync.(*Cond).Wait(0x104401a0, 0x0)
	/usr/local/go/src/sync/cond.go:56 +0x7b
main.main()
	/tmp/sandbox578695461/main.go:17 +0x120
```

There isn't an example for sync.Cond in the documentation and it's hardly used in the standard library.

Should the documentation explain that the locker must be set if the Cond is created as part of a structure? If yes, then what does this really mean:

> A Cond can be created as part of other structures. A Cond must not be copied after first use.

Please update title if this turns out to be a documentation issue. A simple example and where the Cond might be useful would be nice.",1.0,"sync: clarify Cond ""created as part of other structures"" documentation - ### What version of Go are you using (`go version`)?

go version go1.8.1 darwin/amd64

### What operating system and processor architecture are you using (`go env`)?

```
GOARCH=""amd64""
GOBIN=""""
GOEXE=""""
GOHOSTARCH=""amd64""
GOHOSTOS=""darwin""
GOOS=""darwin""
GOPATH=""/Users/joneskoo""
GORACE=""""
GOROOT=""/usr/local/Cellar/go/1.8.1/libexec""
GOTOOLDIR=""/usr/local/Cellar/go/1.8.1/libexec/pkg/tool/darwin_amd64""
GCCGO=""gccgo""
CC=""clang""
GOGCCFLAGS=""-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/p9/8mb6mhcx7p3br8f18crtczzw0000gn/T/go-build980179018=/tmp/go-build -gno-record-gcc-switches -fno-common""
CXX=""clang++""
CGO_ENABLED=""1""
PKG_CONFIG=""pkg-config""
CGO_CFLAGS=""-g -O2""
CGO_CPPFLAGS=""""
CGO_CXXFLAGS=""-g -O2""
CGO_FFLAGS=""-g -O2""
CGO_LDFLAGS=""-g -O2""

```

### What did you do?

I'm creating a sync.Cond as part of a struct. [Documentation explicitly says this is ok](https://tip.golang.org/pkg/sync/#Cond).

https://play.golang.org/p/k0EkYJPC4A

### What did you expect to see?

Wait for Cond until Broadcast is called one second later.

### What did you see instead?

```
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0xffffffff addr=0x0 pc=0x82ffb]

goroutine 1 [running]:
sync.(*Cond).Wait(0x104401a0, 0x0)
	/usr/local/go/src/sync/cond.go:56 +0x7b
main.main()
	/tmp/sandbox578695461/main.go:17 +0x120
```

There isn't an example for sync.Cond in the documentation and it's hardly used in the standard library.

Should the documentation explain that the locker must be set if the Cond is created as part of a structure? If yes, then what does this really mean:

> A Cond can be created as part of other structures. A Cond must not be copied after first use.

Please update title if this turns out to be a documentation issue. A simple example and where the Cond might be useful would be nice.",1,sync  clarify cond  created as part of other structures  documentation       what version of go are you using   go version       go version       darwin          what operating system and processor architecture are you using   go env            goarch      gobin     goexe     gohostarch      gohostos  darwin   goos  darwin   gopath   users joneskoo   gorace     goroot   usr local cellar go       libexec   gotooldir   usr local cellar go       libexec pkg tool darwin     gccgo  gccgo   cc  clang   gogccflags   fpic     pthread  fno caret diagnostics  qunused arguments  fmessage length    fdebug prefix map  var folders     t go    tmp go build  gno record gcc switches  fno common   cxx  clang     cgo enabled      pkg config  pkg config   cgo cflags   g      cgo cppflags     cgo cxxflags   g      cgo fflags   g      cgo ldflags   g                   what did you do     i m creating a sync cond as part of a struct                  what did you expect to see     wait for cond until broadcast is called one second later         what did you see instead          panic  runtime error  invalid memory address or nil pointer dereference       goroutine       sync   cond  wait        	 usr local go src sync cond go       main main    	 tmp   main go              there isn t an example for sync cond in the documentation and it s hardly used in the standard library     should the documentation explain that the locker must be set if the cond is created as part of a structure  if yes  then what does this really mean       a cond can be created as part of other structures  a cond must not be copied after first use     please update title if this turns out to be a documentation issue  a simple example and where the cond might be useful would be nice ,1
11750,7695063451.0,IssuesEvent,2018-05-18 10:52:38,tarantool/tarantool,https://api.github.com/repos/tarantool/tarantool,opened,Avoid reads from vinyl on initial join,performance vinyl,"During initial join we relay the last checkpoint rows hence there can't be duplicates and so we don't need to issue any reads before applying a row, nevertheless we do. Eliminating those reads can significantly speed up initial join of a vinyl replica.",True,"Avoid reads from vinyl on initial join - During initial join we relay the last checkpoint rows hence there can't be duplicates and so we don't need to issue any reads before applying a row, nevertheless we do. Eliminating those reads can significantly speed up initial join of a vinyl replica.",0,avoid reads from vinyl on initial join   during initial join we relay the last checkpoint rows hence there can t be duplicates and so we don t need to issue any reads before applying a row  nevertheless we do  eliminating those reads can significantly speed up initial join of a vinyl replica ,0